Connect systems
Move patients and data between Awell and existing systems: hospital EMRs over HL7, third-party APIs, and in-house services.
This section covers getting patients and their information in and out of Awell, whether that means a hospital electronic medical record (EMR) system over Health Level Seven (HL7) messaging or a REST call to a vendor.
Start here
- How Awell connects to other systems Standards, the integration engine, and why Awell is not a FHIR server.
- Ways to connect an EMR What each mechanism needs from the hospital, and how to choose.
- EMR integration terminology HL7, Mirth, ADT, SIU, and the rest of the vocabulary.
Connecting an EMR
Calling other systems from a care flow
- The API call action for REST and GraphQL.
- Connecting to systems that require OAuth.
- Store static values in constants so an API key or URL lives in one place.
- Integrate with extensions when a prebuilt connector already exists.
Worked examples
- Awell and Healthie, plus setting up a GraphQL API call to Healthie.
- Send an email with Mailchimp or Mandrill.
Who this is for
This section is written for engineers and data-literate operators. Not every organization has a dedicated person for this, and Awell's forward-deployed team often fills the role.
To react to events inside a care flow rather than push data into it, see Automate with events.
Debug integrations with Monitor
Find and investigate failures in third-party connections and integrations, where problems most often surface.
How Awell connects to other systems
How Awell exchanges data with healthcare systems using HL7 and FHIR through an integration engine, and the storage constraint that shapes every integration.