Original research · Dataset
EHR note write-back matrix
Which EHRs document a way to put a note in a chart, what gates it, and how long the non-engineering part of the work actually takes.
Short answer
Which EHRs let a third-party app write a clinical note?
Of 10 platforms audited, 5 document a directly supported note write path reachable without a bespoke partnership. Everywhere else, the constraint is administrative rather than technical: app review, per-customer enablement or a partner programme stands between working code and a written note — and those processes routinely take longer than the integration itself.
Cite as: EHR note write-back matrix, Compare Healthcare API, last reviewed 2026-09-01.
Key findings
- Note write-back is a programme decision, not an API feature. Of the ten EHRs audited, only four publish a documented, self-serve-reachable note write path — and none of the four are the market-share leaders.
- Reading context is nearly universal; writing a note is not. Certification drives read APIs, which means every certified EHR can tell you who the patient is, and comparatively few will let an outside system durably record what happened.
- The organisational path dominates the engineering path. For Epic and Oracle Health, app review and per-customer enablement typically exceed the integration build itself — a scheduling fact that belongs in your roadmap, not your architecture diagram.
- This is precisely why an EHR-agnostic documentation vendor is worth more to an integrator than a marginally better note. The variable cost of this category is integration surface, not model quality.
The matrix
Compiled from each platform's own developer documentation.
| EHR | Note write-back | Mechanism | App review / enablement | Integrator note |
|---|---|---|---|---|
| Epic | Programme-gated | FHIR DocumentReference / Composition write via an approved app listing | Vendor Services / app-listing review required, per-customer enablement | Technically well documented, organisationally the longest path. Budget for review time and per-customer enablement, not just engineering. |
| Oracle Health (Cerner) | Programme-gated | FHIR write endpoints under the developer programme with tenant authorisation | Developer programme registration plus tenant-level authorisation | Comparable shape to Epic. Per-tenant authorisation is the practical bottleneck. |
| athenahealth | Supported | Documented document/clinical-document endpoints via the developer portal | Developer portal onboarding | One of the more approachable large-vendor paths for note attachment. |
| eClinicalWorks | Limited | Certification-scope FHIR read; write paths typically partner-negotiated | Partner agreement | Expect a commercial conversation before a technical one. |
| NextGen | Limited | Certified read APIs; write generally via partner integration | Partner programme | Read access is the certified guarantee; write is a negotiation. |
| Canvas Medical | Supported | Developer-first FHIR API with documented write support and extensibility hooks | Self-serve developer onboarding | Among the lowest-friction targets for a documentation integration. |
| Elation Health | Supported | Documented API for notes and documents | Partner/developer onboarding | Practical target for primary-care-focused products. |
| Healthie | Supported | GraphQL note and charting mutations | Self-serve developer access | Non-FHIR-native shape; plan for a mapping layer rather than a direct resource write. |
| DrChrono | Supported | Clinical note endpoints in the public REST API | Developer account | Straightforward, well-trodden path for small-practice products. |
| Practice Fusion | Not documented | Certified read APIs; no public documented note write path | Partner enquiry | Treat write-back as unproven until the vendor confirms it in writing. |
How to plan around this
The write path determines your roadmap far more than your vendor choice does.
- Confirm your target customers' EHRs before choosing a documentation vendor. A vendor's FHIR support is irrelevant if the EHR does not accept a note from a third party.
- Start app review and enablement paperwork in parallel with the build, not after it. It is the critical path.
- Ship a defensible fallback — copy-to-clipboard with correct formatting, or an attached document — so the feature is usable while write access is pending.
- Budget per-customer enablement as recurring onboarding work, not as a one-time integration cost.
Evidence & sources
Interoperability standards and regulation that define these write paths. Platform-specific claims trace to each EHR's own developer documentation as of the compile date.
HL7 International · Standard · Tier A — primary documentation
Supports: Resource definitions (DocumentReference, Composition, Encounter, Condition, MedicationRequest) that clinical documentation output must map onto.
HL7 International · Standard · Tier A — primary documentation
Supports: The canonical target resource for writing a generated clinical note back to a chart.
SMART Health IT / HL7 · Standard · Tier A — primary documentation
Supports: The launch and authorisation pattern for embedding a documentation app inside an EHR.
Office of the National Coordinator for Health IT (ASTP/ONC) · Standard · Tier A — primary documentation
Supports: The data classes certified EHRs must exchange, which bound what structured output is useful.
ASTP/ONC · Regulation · Tier A — primary documentation
Supports: Transparency obligations that apply when predictive or generative decision support is surfaced inside certified health IT.
Source tiers are defined on the methodology page. Outbound links are unaffiliated and carry no commercial relationship.
Frequently asked questions
- Can I write an AI-generated note back into any EHR?
- No. A documented, reachable note write path exists in a minority of EHRs, and where it exists it is usually gated by app review, per-customer enablement or a partnership programme rather than by technical difficulty.
- Which FHIR resource carries a clinical note?
- DocumentReference is the usual carrier for a note document; some platforms also accept Composition or proprietary note endpoints. Support for creating rather than reading these resources is the distinction that matters. EHR integration guide.
- What usually takes longest?
- Not the code. App review cycles and per-customer enablement dominate the timeline for the largest platforms, and both are administrative processes you cannot compress with engineering effort.
- Does SMART on FHIR solve this?
- SMART on FHIR solves launch and authorisation, not write permission. An app can launch cleanly in context and still have no approved path to create a note. Definition.