Integrate with eClinicalWorks without waiting on eCW’s partner program. Real-time read and write into live eCW: scheduling, patients, insurance, claims and the chart.
eCW’s FHIR API exists for compliance. It does not do scheduling, billing, or reliable write-back.
We’ll tell you if we support the workflow and how you get access.
We confirm we support it on a 30-minute call.
The practice creates one eCW staff user for Cobalt. No eCW partner contract.
Read and write with a receipt on every write.
The certified FHIR endpoint exists to satisfy ONC’s rule, which scopes it to USCDI: a government-defined list of clinical data. It has no concept of scheduling, billing, eligibility, or documents. Here’s what that leaves you with.
FHIR exports problems, meds, allergies, and labs. The moment you need to write back, or touch anything operational, you are off the map.
eCW’s FHIR Create APIs cover a few clinical resources and require a separate commercial contract before you can even start. Most workflows have no write path at all.
eCW often does not expose the read endpoints needed to verify a write even landed (there is no “list documents for patient”). So failures are ambiguous and writes can’t be safely retried.
The same eCW instance, two integration paths. The right column is what FHIR gives you. The left is what Cobalt gives you.
| Capability | Cobalt | eCW FHIR |
|---|---|---|
| Scheduling | ||
| Create, reschedule, and cancel appointments | ✓ | ✕ |
| Read live provider availability | ✓ | ✕ |
| Patients & intake | ||
| Create and update patients (demographics, guarantor) | ✓ | Limited* |
| Add and update insurance on a patient | ✓ | ✕ |
| Upload documents into the patient chart | ✓ | ✕ |
| Clinical & workflow | ||
| Read clinical data (problems, meds, allergies, labs) | ✓ | ✓ |
| Send inbox messages to providers and staff | ✓ | ✕ |
| Create telephone encounters and log call outcomes | ✓ | ✕ |
| Billing & revenue cycle | ||
| Create claims from encounters | ✓ | ✕ |
| Read claims to the line item (CPT, billed, allowed) | ✓ | ✕ |
| Read remittance / ERA (payments, adjustments, denial codes) | ✓ | ✕ |
| Read fee schedules (per-code fee and allowed amount) | ✓ | ✕ |
| Real-time eligibility and benefits (deductible, copay, coinsurance) | ✓ | ✕ |
| Trust & delivery | ||
| Confirmation receipt with the new record’s eCW ID on every write | ✓ | ✕ |
| Live the same day, no certification or contracting gate | ✓ | ✕ |
*Limited: eCW exposes a narrow set of FHIR Create operations for certain clinical resources, available only under a separate commercial contract. Reads of standardized clinical data (problems, meds, allergies, labs) work well over FHIR; Cobalt reads those too, so a single integration covers both.
USCDI is clinical data. Cobalt also reads the financial and operational layer underneath it, the part where revenue cycle, billing, and intake teams actually live.
Read every claim to the CPT level: what was billed, what was allowed, what was paid, plus remittance and ERA denial reason codes. Not a PDF you have to parse. Structured data.
Parsed straight from the 271: coverage status, deductible, copay, coinsurance, out-of-pocket, in vs. out of network, and remaining amounts. There is no FHIR path to this on eCW.
Per-code contracted fees and allowed amounts across Master, Medicare, and Self-Pay schedules. Pricing data that simply does not exist in the USCDI spec.
Each create returns a success webhook carrying the new record’s eCW ID, with separate success and failure events. Because Cobalt reads eCW like a user, it confirms the write landed even where no FHIR read endpoint exists.
Your team only spends attention on genuine failures, not on verifying whether routine writes succeeded. With FHIR, a write is fire-and-forget; with Cobalt, you always know.
You name the eCW workflow you need to ship.
We say yes or no, and how auth works.
POC on a real eCW environment in 24 hours.
Tell us the workflow on a 30-minute call and we confirm we support it. The practice then creates one eCW staff user for Cobalt, with no eCW partner contract. You call one Cobalt API to read and write, with a receipt on every write.
No. The practice grants access with a staff user, and we handle the connection. You build against Cobalt and do not wait on eCW for credentials.
Yes. eCW exposes a certified FHIR API for ONC / USCDI clinical data. That is not a product API for scheduling, billing, eligibility, documents, or most write-back.
No. Scheduling is not in that surface. Cobalt creates, reschedules, and cancels appointments on live eCW.
Book a 30-minute call. We confirm the workflow, explain auth, and run a POC on a real eCW environment in 24 hours. If you would rather not talk first, use Request API access and we reply the same day.
Proof of concept in 24 hours on a real eCW instance. No certification gate and no setup fee to see it work.
Yes. SOC 2 Type II and HIPAA. BAA available. Trust center: https://trust.usecobalt.com