Scribara/Integrations

Bidirectional, semantically correct, idempotent.

Scribara doesn't just read your EHR — it writes the note, the orders, the codes, and the follow-ups back. Every connector is bidirectional, every mapping is reviewed by a clinician, every action is idempotent.

EHR systems

Where your chart lives.

EHREpicFHIR R4 · Hyperdrive · App Orchard listed

EHRAthenahealthathenaOne API · Marketplace partner

EHReClinicalWorksFHIR + HL7 v2 bridge

EHRNextGenEnterprise API · NextGen Office

EHRModMedEMA · FHIR R4

EHRNextechOphthalmology + Dermatology suites

EHRGreenwayIntergy · Prime Suite

EHRAllscriptsSunrise · TouchWorks

Practice operations

Everything else the visit touches.

SCHEDULINGPhreesiaAppointment booking + intake

SCHEDULINGSolvOnline booking · same-day

RCMWaystarClaims · eligibility · prior auth

RCMAvailityPayer-side prior auth & eligibility

RCMChange HealthcareClaims clearing · ERA

LABQuest DiagnosticsOrder + result reconciliation

LABLabCorpOrder + result reconciliation

IMAGINGRadNetImaging orders, reports back to chart

PHARMACYSurescriptse-Prescribing · medication history

MESSAGINGTwilioPatient SMS, AVS delivery

IDENTITYWorkOSSAML / OIDC / SCIM

PAYMENTSStripePatient billing, co-pay collection

Build your own

The connector framework.

Every Scribara connector is built on a shared framework: OAuth, FHIR mapping, idempotent writes, audit logging, and shadow-evaluation harness. Customers and partners build new connectors with the same primitives.

Webhook + REST

Standard HTTPS endpoints. JSON over TLS 1.3. Signed payloads. Replay protection.

MCP-compatible

Model Context Protocol tools registry. Plug your own tools into the agent runtime in a hundred lines of code.

FHIR + HL7

First-class FHIR R4. HL7 v2 bridge for legacy. SMART-on-FHIR launch context.

Need a connector we don't have?

Tell us. Most ship inside 30 days.

Custom EHR or RCM integration on the Enterprise plan, prioritized by our forward-deployed team.

Request a connector →API reference