EMR & charts
Connect the chart your clinicians already work in.
An EMR is a new inbound source, not a new pipeline. A pull populates the same canonical order object the rest of the rail already consumes, so by the time an order reaches a pharmacy, routing, approval, failover, and webhooks cannot tell it came from a chart rather than from an intake widget.
What connects
Five adapters onto one patient model.
Healthie, Elation, and DrChrono have purpose-built adapters. athenahealth and Canvas Medical connect through the generic FHIR R4 path — which is the designed route for any conformant R4 endpoint, not a fallback. Every one of them normalises into the same demographics, intake, medication, and encounter shapes.
One canonical model
The pull returns a canonical order draft.
Demographics, intake answers, medications, and encounter diagnosis codes are normalised server-side into the shapes the rest of the platform already uses, so an EMR-sourced draft arrives carrying the ICD-10 code an order line needs without your integration knowing which chart produced it. The join key is always the chart's own patient id — never a name-and-date-of-birth match, because a fuzzy demographic match across two systems is how one patient's medication list ends up on another patient's order.
Honest capabilities
Each adapter reports what it can actually do.
A capability reported false is a supported state, not an error. Elation reports no structured intake pull because its forms model has no structured questionnaire response — scraping a note body and calling the result structured intake would be worse than admitting the gap, so that questionnaire is captured through the neolife intake widget instead. A conformant FHIR R4 endpoint defaults to no write until the endpoint is confirmed to accept one.
Order write-back
The routed order lands where the clinician already is.
Once an order routes, it can be written back into the chart: a task in Healthie and DrChrono, a non-visit note in Elation, a MedicationRequest on a FHIR endpoint that accepts medication orders, and a Communication on one that takes messages but not orders. Write-back is its own switch on top of the connection, so connecting a chart to read from it never starts writing into it as a side effect.
Read-only degrade
A chart that cannot accept the write holds the order.
When the endpoint refuses the write, the capability matrix reports no push, or write-back is simply off, the order is held and the provider is notified in the console. It is never a silent success and never a dropped order. That is precisely why the capability matrix is honest rather than optimistic: a matrix claiming a capability the endpoint lacks turns a predictable held order into a lost one.
Scopes and identity
Grant the narrowest thing that works.
The scopes you grant are recorded on the connection and shown next to the capability matrix, so “what can this integration actually reach” is answerable without opening your EMR vendor’s admin console. A SMART-on-FHIR connection doing pull only needs four read scopes; enabling write-back adds exactly one more.
Two grants people add reflexively and should not. A wildcard read scope hands neolife every resource class the endpoint exposes, including ones nothing here reads. A practitioner-level scope widens the grant from one patient’s compartment to a clinician’s whole caseload. Neither is needed by any capability on this page, and narrowing a scope later is safe — if a revoked scope breaks a capability, the next health check degrades the connection with a specific error code instead of returning empty results that look like a patient with no medications.
How the money works
Bring your own EMR account. We are not in that invoice.
You hold the contract with your EMR vendor and you hold the API key. The vendor bills you, at your negotiated rate, and neolife earns nothing on the vendor transaction — not a per-seat cut, not a per-pull fee, not a rebate. Your flat neolife platform fee does not move when you connect a chart or pull from it more often.
The credential itself is never a field on the connection. You pass a reference and the value stays in a secret manager, so a connection row is never a credential at rest, and a stable fingerprint answers whether a key changed without anyone reading it.
There is a second, managed billing mode in the data model, where neolife would hold the vendor contract and rebill you at cost plus a documented flat margin. It is locked, it is visible in the product as locked with the unmet gate named inline, and it needs three independent clearances before it ever opens. Bring-your-own is the mode that ships.
Tell us which chart you run. We will show you the capability matrix for it.
Healthie, Elation, DrChrono, or any conformant FHIR R4 endpoint — including athenahealth and Canvas Medical.
Product names and logos are the trademarks of their respective owners and are used here only to identify the systems NeoLife interoperates with. Their use does not imply affiliation with, sponsorship by, or endorsement from those companies.