Written and maintained by CASRAI Editorial Board
Last updated
MEDITECH (Medical Information Technology, Inc.) is an enterprise electronic health record (EHR) vendor serving community hospitals, regional health systems, academic medical centers, and critical access facilities across North America and international markets. While health systems evaluating Epic vs. Oracle Health (Cerner) often encounter MEDITECH in multi-hospital networks and oncology or rural trial sites, integrating clinical research platforms or digital health applications with a MEDITECH site requires distinguishing between its legacy server generations and its modern web-native architecture, MEDITECH Expanse.
What Is MEDITECH Expanse and How Does It Differ from Legacy MEDITECH MAGIC?
Over its five-decade engineering history, MEDITECH evolved through four primary architectural generations: MAGIC, Client/Server (C/S), 6.x, and MEDITECH Expanse. For clinical informatics architects and integration engineers, the distinction between legacy MAGIC and Expanse determines how data are stored, queried, and exchanged.
- Legacy MEDITECH MAGIC: Built around MEDITECH’s proprietary MAGIC programming language and hierarchical data structures (descended from the MUMPS/MIIS ecosystem), MAGIC used a character-based, keyboard-driven terminal interface segmented into departmental server modules (such as Admissions, Laboratory, Pharmacy, and Order Entry). Integration with external software in MAGIC environments relies primarily on point-to-point HL7 v2.x messaging via interface engines, custom NPR (Non-Procedural Representation) report exports, or Data Repository (DR) SQL replications.
- MEDITECH Client/Server and 6.x: Intermediate generations that introduced graphical Windows client interfaces, consolidated clinical databases, and standard SQL Data Repository schemas while retaining client-installed workstation software.
- MEDITECH Expanse: MEDITECH’s modern, browser-based, mobile-responsive enterprise EHR platform. Expanse eliminates local workstation client installations in favor of a zero-footprint web architecture accessible on tablets, smartphones, and desktops. It unifies acute inpatient, emergency department, ambulatory clinic, oncology, genomics, and revenue cycle workflows on a single database schema and can be deployed either on-premises or via MEDITECH as a Service (MaaS) hosted on Google Cloud Platform (GCP).
| Architectural Dimension | Legacy MEDITECH MAGIC | MEDITECH Expanse (Web / MaaS) |
|---|---|---|
| User Interface | Character/terminal-based screen navigation | Zero-footprint HTML5 web browser and mobile-responsive workspaces |
| Deployment Model | On-premises departmental server architecture | Cloud-hosted MEDITECH as a Service (MaaS on Google Cloud) or on-premises |
| Primary Integration Protocol | Point-to-point HL7 v2.x interfaces and NPR / Data Repository extracts | RESTful HL7 FHIR R4 APIs, SMART on FHIR, and HL7 v2 / CDA services |
| Reporting & Analytics | NPR custom reports and nightly Data Repository sync | Expanse Business and Clinical Analytics (BCA) plus SQL Data Repository and Bulk FHIR |
| Genomics & Precision Medicine | Unstructured text or scanned PDF attachments | Expanse Genomics module storing discrete genetic variant data and pharmacogenomic alerts |
What Is the MEDITECH Greenfield App Development Environment?
MEDITECH Greenfield (greenfield.meditech.com) is MEDITECH’s official developer program, API documentation portal, and cloud sandbox environment for third-party software vendors, health systems, and clinical research engineering teams. Named after MEDITECH’s engineering campus in Foxborough and Canton, Massachusetts, Greenfield provides standardized onboarding for applications that connect to MEDITECH Expanse and 6.x systems.
Within the Greenfield workspace, clinical informatics teams can:
- Register SMART on FHIR and RESTful Applications: Obtain client credentials, configure OAuth 2.0 redirect URIs, and define granular resource scopes (such as
patient/*.read,user/*.read, orsystem/*.read). - Test Against De-Identified Synthetic Cohorts: Execute API queries against sandbox patient records containing longitudinal laboratory panels, medication orders, problem lists, allergies, and clinical notes before deploying into a hospital’s production environment.
- Publish to the MEDITECH App Directory: Validated third-party applications—ranging from ambient AI clinical scribes and remote patient monitoring hubs to clinical trial screening tools—are listed in the Greenfield App Directory for streamlined procurement and activation by MEDITECH health systems.
How Does MEDITECH Support HL7 FHIR R4 and Traverse Interoperability?
To satisfy the ONC 21st Century Cures Act Final Rule and the CMS Promoting Interoperability Program for hospitals, MEDITECH Expanse is certified to the 45 CFR § 170.315(g)(10) Standardized API for patient and population services criterion. Its interoperability stack operates across three technical layers:
- HL7 FHIR Release 4 (R4) and US Core APIs: MEDITECH exposes RESTful FHIR R4 endpoints conforming to the HL7 FHIR US Core Implementation Guide and the United States Core Data for Interoperability (USCDI). Using the SMART App Launch Framework (OAuth 2.0 and OpenID Connect), clinician-facing apps can launch directly in context within an active MEDITECH Expanse chart session, while patient-facing research apps allow participants to authorize electronic health data sharing via their patient portal credentials.
- FHIR Bulk Data Access (
$export): Supporting the HL7 FHIR Bulk Data Access specification, MEDITECH enables authorized clinical registries, population health platforms, and research data warehouses to extract asynchronous NDJSON (Newline Delimited JSON) files across multi-patient cohorts without degrading transactional EHR performance. - MEDITECH Traverse and TEFCA Connectivity: Traverse is MEDITECH’s embedded health information exchange (HIE) and interoperability network. Through Traverse and Traverse Exchange, MEDITECH hospitals exchange clinical summaries, C-CDA documents, and FHIR resources across Carequality, CommonWell Health Alliance, and TEFCA Qualified Health Information Networks (QHINs), consolidating external records directly into the clinician’s workflow.
Clinical Research, Oncology, and Data Repository Workflows
Community and regional hospitals running MEDITECH Expanse increasingly participate in decentralized and hybrid clinical trials, particularly through NCI Community Oncology Research Program (NCORP) sites and precision medicine registries:
- Expanse Oncology and Genomics: Expanse Oncology integrates staging, chemotherapy regimen ordering, toxicity grading, and clinical trial protocol tracking with the Expanse Genomics module, which ingests discrete next-generation sequencing (NGS) and pharmacogenomic results from reference laboratories to trigger point-of-care clinical decision support alerts.
- MEDITECH Data Repository (DR): For retrospective real-world evidence (RWE) studies, institutional honest brokers query the MEDITECH Data Repository—a near-real-time Microsoft SQL Server relational database mirror of transactional EHR data—to transform local clinical tables into the OMOP Common Data Model or PCORnet CDM without placing query load on the production Expanse environment.
Frequently Asked Questions
What is MEDITECH Expanse and how does it differ from legacy MEDITECH MAGIC?
MEDITECH Expanse is a modern, zero-footprint, browser-based enterprise EHR platform deployed on-premises or in the cloud via MEDITECH as a Service (MaaS) on Google Cloud. Legacy MEDITECH MAGIC is an older character-based, keyboard-navigated architecture built on MEDITECH’s proprietary MAGIC language that relies primarily on HL7 v2 interfaces and custom NPR reports rather than native web workspaces and RESTful FHIR APIs.
What is the MEDITECH Greenfield app development environment?
MEDITECH Greenfield is MEDITECH’s developer portal, API sandbox, and partner program that enables health systems, clinical informatics teams, and software vendors to build, test, and certify SMART on FHIR and RESTful HL7 FHIR R4 applications that integrate directly with MEDITECH Expanse.
How does MEDITECH support HL7 FHIR R4 and Traverse interoperability?
MEDITECH Expanse is certified to ONC 45 CFR § 170.315(g)(10), providing US Core-compliant HL7 FHIR R4 APIs for single-patient, clinician SMART App Launch, and Bulk Data Access ($export) queries. In parallel, MEDITECH Traverse connects participating hospitals to Carequality, CommonWell, and TEFCA QHINs for nationwide document and FHIR data exchange.
