MEDITECH FHIR Integration: What to Know Before You Build
MEDITECH's FHIR support has matured significantly with its Expanse platform, but many MEDITECH-based hospitals still run substantial HL7 v2 interface infrastructure alongside it - plan for both.
MEDITECH's FHIR API, primarily on Expanse
MEDITECH's FHIR R4 support is centered on its Expanse platform, built to meet ONC certified API requirements under the 21st Century Cures Act, following the standard OAuth 2.0 / SMART on FHIR authentication model. Older MEDITECH platform versions (Magic, Client/Server 6.x) have more limited or absent FHIR support, so confirming which MEDITECH platform version a specific hospital is running is an essential first step - 'MEDITECH' isn't one uniform integration target across every deployed version.
HL7 v2 often remains the primary integration path for hospital-side data
Many hospitals running MEDITECH, particularly larger, longer-established deployments, still rely heavily on HL7 v2 interfaces (ADT, ORU, ORM) for real-time internal clinical data exchange, with FHIR increasingly used for app-based and patient-facing access rather than replacing HL7 v2 wholesale. An integration project should confirm early which access pattern is actually available and appropriate for the specific use case and hospital, rather than assuming FHIR is automatically the right or only path.
Planning the integration
As with any EHR integration, start with a focused technical discovery: confirm the specific MEDITECH platform version in use, which FHIR resources and scopes are actually supported and populated, and whether HL7 v2 is the more appropriate path for the specific data you need - before committing to a broader project timeline based on assumptions from a different EHR or a different MEDITECH version.
FAQ