MEDITECH Expanse: Modules, APIs and How to Integrate (2026 Guide)
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.
In brief: MEDITECH Expanse is MEDITECH's web-based, cloud-native EHR platform, used across acute care, ambulatory, emergency, surgical, oncology, home care and revenue cycle. MEDITECH describes it as a next-generation web platform spanning every care setting, and it can run on-premise or as a subscription hosted on Google Cloud (MEDITECH as a Service). This guide covers what Expanse is, how it relates to the older MAGIC, Client/Server and 6.x platforms, the Expanse products and modules by workflow, and the routes a health tech product uses to integrate with it.
Facts below were checked on 26 September 2026 against MEDITECH's own pages, its certified API documentation and the ONC Certified Health IT Product List. If you are scoping a product integration now, our MEDITECH integration services team starts from this map.
What is MEDITECH Expanse?
MEDITECH Expanse is the current generation of MEDITECH's electronic health record: a browser-based platform for hospitals, clinics and post-acute settings. MEDITECH calls it "cloud-native and highly scalable" on its company page, and sells it either installed at the hospital or as MEDITECH as a Service (MaaS), which MEDITECH says now has over 100 customers.
Expanse grew out of MEDITECH's 6.x codebase: the earliest ONC certification listing is named "MEDITECH Expanse (6.16)", followed by Expanse 2.1 and the current Expanse 2.2. MEDITECH, founded in 1969 and based in Canton, Massachusetts, says it serves more than 2,000 healthcare organizations in 28 countries and territories.
Expanse vs 6.x vs Client/Server vs MAGIC
Many MEDITECH hospitals still run an older platform, and the platform decides which integration routes exist. MEDITECH still lists certified versions of all four generations, and publishes a migration path from MAGIC and Client/Server to Expanse.
| Platform | Certified versions MEDITECH lists | What it means for integration |
|---|---|---|
| Expanse | 2.2 and 2.1 | Certified FHIR R4 APIs (US Core 6.1.0 on 2.2), SMART App Launch, Bulk Data, plus HL7 v2 interfaces |
| 6.x | 6.1 and 6.0 | Certified APIs for the listed versions, with HL7 v2 as the main real-time route |
| Client/Server | 5.67 | HL7 v2 interfaces first; confirm what the hospital's certified version exposes |
| MAGIC | 5.67 | HL7 v2 interfaces first; often the source system in a data migration to Expanse |
MEDITECH Expanse products and modules
MEDITECH names its products on its product list. The tables group the ones a health tech product is most likely to meet, with the first integration question to settle for each. Every hospital licenses a different set.
Clinical care
| Product | What it does | First integration question |
|---|---|---|
| Expanse for Physicians | Physician documentation, orders and hospital course summaries | Does your app need to launch in the physician's workflow, or read data in the background? |
| Expanse Patient Care (Expanse for Nurses) | Nursing documentation and care plans | Which assessments or interventions does your product read or feed? |
| Expanse Emergency Department Management | Emergency department tracking and documentation | Do you need real-time arrival and disposition events? |
| MEDITECH Surgical Services | Surgical scheduling and perioperative documentation | Is the need case scheduling data, or intraoperative documentation? |
| Expanse Oncology | Oncology care from diagnosis to survivorship | Which regimens, orders or results does your product use? |
| Expanse Genomics | EHR-based genomics with pharmacogenomic decision support | Is your product a lab result source or a decision support consumer? |
| Expanse Pharmacy | Inpatient pharmacy and medication management | Do you need medication orders, administrations, or both? |
| Expanse Ambulatory | Outpatient EHR, including practice management | Is the practice on the same Expanse instance as the hospital? |
| Home Care, Hospice, Long Term Care | Post-acute care settings | Which setting and which episode data does your product need? |
Mobile and AI
| Product | What it does | First integration question |
|---|---|---|
| Expanse Point of Care | Mobile app for bedside medication administration and common interventions | Does your device or app need to post data at the bedside? |
| Expanse Now | Mobile access to a clinician's Expanse workload: refills, messages, coverage | Is your product competing with, or complementing, clinician mobile workflows? |
| Expanse Navigator | Searches structured and unstructured data and summarizes it | Does your AI product overlap with built-in search and summarization? |
MEDITECH's AI page also names Ask Expanse, ambient listening for physicians and nurses, nursing handoff, no-show prediction, the MyHealth Assistant and claims denial agents. Expanse Navigator builds on a 2022 collaboration with Google Health that harmonizes data into FHIR format.
Diagnostics
| Product | What it does | First integration question |
|---|---|---|
| Laboratory, Microbiology, Blood Bank | Hospital lab ordering, testing and results | Is MEDITECH the ordering system, the performing lab, or both? |
| Expanse Pathology | Anatomic pathology | Do you need specimen, case or result data? |
| Outreach Lab | Lab services for outside clients | Are orders coming from outside practices into MEDITECH? |
| Imaging and Documentation Management | Imaging department workflow and document management | Is the need orders out, results in, or documents into the chart? |
Patient engagement, coordination and revenue cycle
| Product | What it does | First integration question |
|---|---|---|
| MyHealth | Patient portal | Is your app patient-facing, using patient-authorized FHIR access? |
| Expanse Patient Connect | Patient engagement service on the MEDITECH Cloud Platform | Does your messaging or engagement product overlap it? |
| Virtual Care | Virtual visits, including on-demand care | Does your telehealth workflow need scheduling and documentation in Expanse? |
| Scheduling and Referral Management | Appointments and referrals | Do you need to show availability, book, or receive changes? |
| Revenue Cycle | Registration, billing and electronic claims | Is the need eligibility, claims, remittance, or denial workflow? |
| Business and Clinical Analytics | Web-based data visualization | Would your analytics run on MEDITECH data exports or live APIs? |
| Traverse Exchange | MEDITECH's FHIR-based interoperability network | Is record exchange enough, or do you need to be in the workflow? |
How to integrate with MEDITECH Expanse
There are five practical routes into Expanse. Most products combine two: certified FHIR APIs for reading clinical data and HL7 v2 interfaces for real-time events. For the interface side in depth, see our MEDITECH and Mirth Connect guide.
| Route | What it gives you | What it needs |
|---|---|---|
| Certified FHIR R4 APIs | Read access on US Core 6.1.0 and USCDI v3 (Expanse 2.2), documented on MEDITECH's certified API page | A hospital customer that registers your app |
| SMART on FHIR launch | EHR launch and standalone launch (SMART App Launch 2.0.0) | The hospital's identity provider for clinician login |
| Backend services and bulk FHIR | Client credentials with a private key JWT; Bulk Data 1.0.0 exports | Registration per hospital and a bulk use case |
| HL7 v2 interfaces | Outbound ADT, results, appointments and orders; inbound where licensed | An interface license per hospital and its interface team |
| Traverse Exchange | Record exchange, with TEFCA access through Health Gorilla's QHIN | The hospital's participation; it does not place your app in the workflow |
Each hospital's FHIR base URL appears in MEDITECH's public endpoint list, which held 509 endpoints for 454 organizations when we checked. For the SMART side, our SMART on FHIR architecture guide covers the launch flows, and our bulk FHIR export guide covers population exports.
Start in Greenfield Workspace
Greenfield Workspace is MEDITECH's sandbox for testing against a real MEDITECH EHR. Joining takes six steps: submit the registration form, receive a welcome packet, sign the Greenfield end-user license agreement, provide a Google ID for sign-in, provide a redirect URI to receive an OAuth client ID and secret, and take a short call with the support team. The sandbox includes three synthetic patients, and MEDITECH publishes no fee for it.
What catches teams out
- You cannot self-register. MEDITECH registers client applications on behalf of the healthcare organization, so every go-live needs a hospital sponsor.
- Rate limits have no published numbers. Quotas apply per hospital instance, TEST and LIVE separately, and return HTTP 429 with a Retry-After header.
- Interfaces are licensed. MEDITECH's cost disclosure lists a one-time implementation fee and monthly maintenance per interface, and no per-transaction charge.
- The platform generation varies. A health system can run Expanse in one hospital and an older platform in another, so confirm the version per site.
MEDITECH Expanse in 2026
Two recent milestones matter for anyone selling into MEDITECH hospitals. In August 2026 MEDITECH was named a Leader in the Gartner Magic Quadrant for enterprise EHRs, and in September 2026 it announced that 72 HCA Healthcare hospitals were on Expanse, with the first full HCA divisions live. MEDITECH also stopped providing a direct CommonWell connection in 2025, routing that exchange through Traverse Exchange instead. If you are comparing EHR platforms, our Epic modules list is the equivalent map for Epic.
Planning a MEDITECH integration? Our MEDITECH integration services cover SMART apps, bulk FHIR, HL7 v2 through Mirth Connect and hospital go-live.
Map your product to the right MEDITECH route.
Tell us the workflow your product supports and which hospitals you sell to. We identify the MEDITECH platform, the FHIR APIs or HL7 interfaces involved, and what the hospital must approve before go-live.
Frequently Asked Questions
What is MEDITECH Expanse?
Is MEDITECH Expanse the same as MEDITECH 6.x?
Does MEDITECH Expanse support FHIR?
What is Greenfield Workspace?
What modules are in MEDITECH Expanse?
How do you integrate a third-party app with MEDITECH Expanse?
