For health tech products
We build MEDITECH integrations for health tech products: SMART on FHIR apps inside Expanse, backend and bulk FHIR data feeds, patient and scheduling apps, and HL7 v2 interfaces through Mirth Connect for Expanse, 6.x, Client/Server and MAGIC hospitals. We also run the access path with you, from Greenfield Workspace to go-live at each hospital. For the platform itself, read our MEDITECH Expanse guide.
Plan my MEDITECH integrationFor digital health products, analytics and AI vendors, and health systems connecting software to MEDITECH hospitals. Updated September 2026.
What we build
MEDITECH hospitals run different platform generations, and the route depends on which one. Expanse exposes certified FHIR APIs; every generation still relies on licensed HL7 v2 interfaces for real-time feeds.
Clinician-facing apps that open from Expanse with patient context, or sign users in from your own app. Users log in through the hospital's own identity provider, such as Entra ID, Okta or Ping, and MFA is enforced there. Expanse 2.2 is certified on SMART App Launch 2.0.0 and US Core 6.1.0.
Analytics, quality and AI feeds using SMART Backend Services with client credentials and a private key JWT. Expanse 2.2 is certified on Bulk Data Access 1.0.0 for population exports, and each hospital's FHIR base URL is published in MEDITECH's endpoint list.
Patient access apps read US Core FHIR R4 data after the patient authorizes the app. MEDITECH also offers FHIR Scheduling APIs for Expanse customers, with user and patient workflows, which we confirm with each hospital before building booking into scope.
MEDITECH's published outbound interfaces cover ADT with demographics and allergies, lab, microbiology and blood bank results, appointments and orders to lab and radiology vendors. We build and run the Mirth Connect channels, mapping, acknowledgements, alerting and replay against the hospital's interface specifications.
MEDITECH lists certified API versions for Expanse 2.2 and 2.1, 6.1 and 6.0, and MAGIC and Client/Server 5.67, and certifies EHI export. For hospitals still on older platforms, or moving to Expanse, we combine those exports with HL7 feeds to move and reconcile data.
Two kinds of access
Expanse 2.2 is certified under ONC (g)(10) on FHIR R4, US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0 and Bulk Data 1.0.0. You build and test in Greenfield Workspace, then connect to each hospital's TEST and LIVE instances.
Interfaces are licensed per hospital with a one-time implementation fee and monthly maintenance. MEDITECH says it does not charge per interface transaction. The hospital's interface team schedules the build.
From Greenfield to go-live
Hospital sponsorship and interface scheduling decide the calendar more than code does, so we start them on day one.
We register for Greenfield with you: the EULA, a Google ID for sign-in and a redirect URI for the OAuth client. We build against its synthetic patients first.
Working FHIR calls and launch flows in the sandbox.Your hospital customer asks MEDITECH to register the app and, for feeds, licenses the interfaces. We prepare the scope, URLs and interface list with you.
A registration request and interface list per hospital.We connect to the hospital's TEST environment, check its platform version, identity provider and rate limits, and build the Mirth channels.
Tested workflows and a version matrix per hospital.We move to LIVE with the hospital's interface team, then monitor API errors, 429s and interface queues with alerting and replay.
A repeatable go-live runbook and support handover.Evidence
The engineering behind our MEDITECH delivery, with public code and test results you can inspect.
One app run against the Epic and Oracle Health developer sandboxes in a single session, with the launch, PKCE and token handling a MEDITECH SMART app needs.
Our team has built 350+ interfaces on Mirth Connect, the engine we use for the HL7 v2 side of a MEDITECH integration.
Passes 47 of 47 ONC (g)(10) SMART App Launch tests (11 Jun 2026), the same certification program MEDITECH's APIs are tested under.
Headless EHR on GitHub ↗Before you commit
Yes. MEDITECH Expanse has certified FHIR R4 APIs on US Core 6.1.0 with SMART App Launch and Bulk Data, documented on MEDITECH's certified API page, and developers test them in Greenfield Workspace. Older MEDITECH platforms have certified API versions too, and every generation supports HL7 v2 interfaces.
Greenfield Workspace is MEDITECH's developer sandbox for testing integrations against a real MEDITECH EHR. You sign the Greenfield EULA, sign in with a Google ID and receive an OAuth client, then test with synthetic patients.
No. MEDITECH registers client applications on behalf of the healthcare organization, and vendors do not self-register. Your hospital customer requests the registration, and we prepare the details with you.
MEDITECH publishes no separate fee to app developers for its certified FHIR APIs. HL7 v2 interfaces are licensed to the hospital with a one-time implementation fee and monthly maintenance, and MEDITECH says it does not charge per transaction.
No. The MEDITECH Alliance is MEDITECH's partner program for solutions already integrated with MEDITECH customers, with Innovator, Accelerator, Collaborator and services tiers. Many products integrate through Greenfield and hospital sponsorship first and apply later.
Yes, mostly through HL7 v2 interfaces, plus the certified API versions MEDITECH lists for MAGIC and Client/Server 5.67. We confirm what each hospital's platform supports before a workflow goes into scope.
MEDITECH enforces quotas per hospital instance, TEST and LIVE separately, and returns HTTP 429 with a Retry-After header, but publishes no fixed numbers. We queue requests per hospital and use bulk export for large loads.
Usually, yes. Traverse Exchange is MEDITECH's FHIR-based exchange network with TEFCA access through Health Gorilla's QHIN. It helps retrieve records for care, but it does not put your product in the clinician's workflow or feed your product in real time.
The number of workflows, FHIR versus HL7 v2, the hospital's platform generation, how quickly the hospital sponsors registration and licenses interfaces, and how many hospitals you connect. Hospital interface fees are separate from our engineering fees.
Define the next step
Tell us about your product and the hospitals you sell to. We will come back with the APIs, interfaces and hospital steps your workflow needs.
Please don’t include patient data, credentials or sensitive records.
MEDITECH and Expanse are trademarks of Medical Information Technology, Inc. Other product names are trademarks of their respective owners.
