MEDITECH FHIR Integration: Expanse APIs, Greenfield Workspace and HL7 Interfaces

Greenfield Workspace is MEDITECH’s developer environment. Developers and customers register through an online form, then log in to run API calls against a MEDITECH Expanse test environment with sample patient data and interactive API documentation.

• Workspace access is not customer access. MEDITECH is explicit that Workspace credentials and endpoints apply only to its developer environment. Connecting to a hospital requires that hospital’s agreement and configuration, and each customer sets its own connection policies.
• Support. MEDITECH provides a Greenfield service desk for developer questions, including HL7 interface questions.
• MEDITECH Alliance. MEDITECH also describes an ecosystem of partner organizations with interoperable solutions. Check MEDITECH’s own pages for current participation criteria.

MEDITECH documents patient access APIs in both DSTU2 and R4, and directs developers to US Core FHIR R4 for USCDI data. It describes these as view-only APIs available after a patient authorizes the requesting app, which positions them for patient-facing use cases.

MEDITECH also describes FHIR scheduling APIs intended to give patients a consistent online scheduling experience across systems, available to Expanse customers. Because availability and scope evolve, confirm current status on Greenfield resources before designing around them. For general background on the resource model, see FHIR resources.

Hospitals participating in CMS’s Promoting Interoperability program are measured partly on giving patients electronic access to their health information, and certified health IT must meet ONC’s standardized API criterion (§170.315(g)(10)). In practice this makes patient-authorized FHIR access the most mature and widely available path at MEDITECH sites, which matches MEDITECH’s emphasis on US Core patient access APIs.

For provider-facing or population-level use cases, the regulatory baseline does not guarantee that a given hospital has enabled what you need. Confirm specific capabilities with MEDITECH and the customer’s IT team, and see FHIR and healthcare interoperability for how these requirements fit together.

Because HL7 v2 remains central at many MEDITECH customers, partners should be fluent in both standards. See FHIR vs HL7 v2.

• MEDITECH customers do not all run Expanse; sites on older MEDITECH platforms may offer narrower API options and depend more on HL7 v2.
• The documented FHIR patient access APIs are view-only.
• Testing in Greenfield Workspace validates your app against MEDITECH’s environment, not against any specific hospital’s build.
• Community hospitals may have limited interface team capacity, which affects scheduling.

• Which MEDITECH platform and version each target customer runs.
• Whether the use case is patient-authorized (best supported by FHIR) or requires HL7 v2 or other interfaces.
• Greenfield registration and any MEDITECH review steps.
• Customer IT availability for configuration and testing.

See FHIR integration cost for how mixed FHIR and HL7 v2 scope affects budgets.

• Have you integrated with MEDITECH Expanse sites in production, and through which APIs or interfaces?
• How do you handle customers on older MEDITECH platforms?
• Have you used Greenfield Workspace, and what did it not tell you about production behaviour?
• Can you deliver HL7 v2 interfaces alongside FHIR?

Browse EHR integration vendors filtered by MEDITECH, or see our EHR/EMR integration service overview.