Integration
Connecting Bond to MEDITECH Expanse
MEDITECH Expanse is MEDITECH's go-forward EHR platform, and MEDITECH lists community and critical access hospitals first among the customers it serves.[5],[7] Bond Health connects to Expanse via FHIR R4 or an HL7 v2 feed that the hospital approves, screens coded data and clinical notes against a study's criteria, and hands ranked candidates to coordinators. This page covers the data, the approvals, the timeline and what is not integrated today.
What is MEDITECH Expanse, and who uses it?
14.7%[4]
US acute care hospitals on MEDITECH, 2025 (KLAS)
12.5%[4]
US acute care beds on MEDITECH, 2025 (KLAS)
84%[4]
Legacy MEDITECH customers making a go-forward decision in 2025 who chose Expanse (KLAS)
2,000+[7]
Organizations in 28 countries and territories, per MEDITECH (September 2026)
MEDITECH, founded in 1969 and based in Canton, Massachusetts, describes Expanse as a cloud-native EHR for health systems of all sizes.[7] KLAS's 2026 market share report, which covers contracts signed in 2025, ranks MEDITECH third among US acute care EHR vendors, behind Epic at 43.7% and Oracle Health at 21.9% of hospitals.[4] Large systems use it too: HCA Healthcare had 72 hospitals across the US and UK on Expanse as of August 2026.[8]
MEDITECH offers patient registries and a Business and Clinical Analytics platform, and Expanse Genomics can build research cohorts by genetic marker.[9],[10] As of September 2026, MEDITECH's pages describe these as cohort tools, not criterion-by-criterion review of a patient's notes, which is what Bond's Identify stage does.
What does MEDITECH Expanse expose to outside developers?
MEDITECH's developer program is called Greenfield. Its Greenfield Workspace is a sandbox where developers run APIs and test applications against a real MEDITECH EHR.[11] To join, a developer submits a registration request and MEDITECH issues an OAuth2 client ID and secret for testing.[12]
| Interface | What it provides | Role for Bond |
|---|---|---|
| US Core FHIR R4 APIs | View-only patient data, after the patient authorizes an app.[11] | Patient-facing only. Not enough to screen a population. |
| Population-level FHIR (Bulk Data) | ONC's (g)(10) criterion requires certified EHRs to support FHIR Bulk Data for groups of patients, on US Core 6.1.0 from December 31, 2025.[14] | Suits population screening, where the hospital enables it for Bond. |
| FHIR Scheduling APIs | Scheduling workflows, Expanse customers only.[11] | Not used today. |
| Outbound HL7 v2 interfaces | Feeds for admissions, lab results, orders, pathology reports, home medications and more.[13] | Used where FHIR population access is not available, sent through the hospital's interface engine. |
What data does Bond read, and which resources carry it?
Each element Bond reads maps to a US Core FHIR resource and, for most, to one of the HL7 v2 feeds MEDITECH documents for outside vendors.[13]
| Data element | FHIR resource or interface | Notes |
|---|---|---|
| Demographics and contact details | Patient; Admissions outbound HL7 | Age and sex for criteria; phone for outreach. |
| Diagnoses and problems | Condition | Onset and resolution dates set time windows. |
| Medications | MedicationRequest; home medications outbound HL7 | Washout and prohibited-drug criteria. |
| Lab results | Observation; laboratory results outbound HL7 | Dated values for threshold criteria. |
| Allergies | AllergyIntolerance; Admissions outbound HL7 | Carried in the Admissions feed.[13] |
| Procedures | Procedure | Prior procedures named in exclusions. |
| Visits | Encounter; Appointment; community-wide scheduling outbound HL7 | Upcoming visits help time outreach. |
| Clinical notes and reports | DocumentReference; pathology reports outbound HL7 | The main source for unstructured criteria. |
What comes through depends on the hospital's Expanse release and configuration, and is checked in test.
How does Bond handle MEDITECH clinical notes?
Many criteria are settled only in notes: a pathology finding, an ejection fraction, a prior line of therapy. USCDI's Clinical Notes data class covers note types including consultation notes, discharge summaries, history and physicals, procedure notes and progress notes.[15] The US Core DocumentReference profile sets minimum expectations for how servers search for and return those notes, with the content inline or at a URL.[16] ONC's (g)(10) criterion also requires certified APIs to return note text as plain text.[14]
Bond's Identify stage reads notes alongside the coded record. It maps phrases to clinical concepts through a terminology graph built from 18 biomedical terminology sources, so "HFrEF" in a cardiology note and a coded diagnosis of heart failure with reduced ejection fraction can map to the same concept.[3] Each match shows the evidence behind each criterion, so a coordinator can check it in Expanse.[1]
- Note types. A note type the hospital does not send cannot be read.
- Text or image. Scanned documents may arrive as images, not text; testing shows which do.
What does the hospital's IT team need to do?
The hospital's IT or interface team owns these steps.
- Confirm the Expanse release and its USCDI version. Certified health IT had to support USCDI v3 by the end of 2025; MEDITECH's public Greenfield page still listed USCDI v1 as of September 2026.[17],[11]
- Choose the access path: population-level FHIR, an HL7 v2 feed from the interface engine, or an integration partner.
- Register Bond's client, issue credentials and approve scopes limited to the table above.
- Run the vendor security review and sign the business associate agreement.
- Name an IT contact and a research contact for testing.
Where does MEDITECH fit in the 48-hour implementation?
Bond's published estimate for a full EHR integration is 48 hours, depending on the EHR, the IT review and the interface method.[1] In the implementation plan, criteria and scripts are configured in parallel with these steps.
- 1
Step 1: kickoff and BAA
Bond signs the BAA and lists the data it requests.
- 2
Step 2: security review and access path
IT reviews Bond and picks FHIR, HL7 v2 or an integration partner.
- 3
Step 3: connection
IT registers Bond or turns on the feed. Bond checks which data and note types arrive.
- 4
Step 4: criteria and validation
Bond turns each criterion into checks. The PI or coordinator adjudicates matches on a sample of Expanse records.
- 5
Step 5: go-live
Ranked matches appear in the dashboard.[1]
How is MEDITECH data protected?
- Agreements first. Bond signs a business associate agreement before the hospital shares any PHI.[1]
- Controls. Bond is HIPAA compliant and SOC 2 Type I compliant, and its SOC 2 Type II and ISO 27001 audits are underway.[2] Its controls include encryption in transit and at rest (AES-256 where applicable), role-based access, SSO, audit logging, penetration testing and employee security training.[1]
- People decide. Coordinators review each ranked match against its evidence, and the site confirms eligibility at screening.
Matches go to Bond's dashboard, then to the CTMS, a Google Sheet or the site calendar.[1] The security page shows the full data flow.
What is not integrated with MEDITECH today?
- No MEDITECH certification. Bond is not in the MEDITECH Alliance, MEDITECH's program for vetted third-party solutions.[19]
- No write-back. Bond does not file notes, flags or research status in Expanse.
- No Expanse scheduling. Bond books visits in the site calendar.
- No app inside the chart. Coordinators work in Bond's dashboard, not in a SMART app launched from Expanse.
- No Traverse Exchange. Bond does not use MEDITECH's network for sharing records with other providers.[18]
Bring one protocol and your Expanse release. We will map the access path, approvals and dates with your IT contact.
Frequently asked questions
Is Bond certified by MEDITECH?
Does Bond work with hospitals still on older MEDITECH platforms?
Sources
- 1.Bond Health: platform overview, FAQ and pricing · Bond Health, 2026
- 2.Bond Health product information · Bond Health, 2026Capabilities, pricing and compliance status described by Bond Health, September 2026.
- 3.Terminology Infrastructure and Graph-Grounded RAG for Clinical Trial Patient Matching · Bond Health, preprint, 2026Internal technical report by R. Goel, August 2026. Available on request.
- 4.Acute Care EHR Market Share 2026: Epic Up, Oracle Down · healthsystemCIO.com (reporting KLAS Research), 2026Reports KLAS's US Acute Care EHR Market Share 2026 report, covering EHR contracts executed January through December 2025. Accessed September 2026. Quote: "Epic now holds 43.7% of acute care hospital market share and 56.9% of beds. Oracle Health, meanwhile, sits second at 21.9% of hospitals and 20.4% of beds, followed by Meditech at 14.7% and 12.5%." Also: "84% of legacy Meditech customers making a go-forward decision chose to migrate to Expanse."
- 5.Partnership Vital in EHR Decisions: Insights from the Acute Care EHR Market Share 2025 Report · KLAS Research, 2025Blog post, May 22, 2025. Quote: "MEDITECH has retained a high percentage of legacy customers who have migrated to their go-forward Expanse platform, doubling their retention rate of those making go-forward decisions in 2024 versus 2023."
- 6.21st Century Cures Act: Timelines, Regulatory Dates In The Upcoming Years · MEDITECH, 2021Customer communication, last updated October 2021. Quote: "MEDITECH will certify our 2015 Edition Cures Update for all platforms and care settings throughout Q1/Q2 2022." Also: "All organizations will need a priority pack topoff to receive the certified 2015 Edition Cures Update." On (g)(10): "Also known as FHIR Bulk Data Access (Flat FHIR), this criteria requires that EHRs support the ability for a client to retrieve large volumes of data for a group of patients via FHIR API."
- 7.About MEDITECH · MEDITECH, 2026Vendor figures, accessed September 2026. Quote: "Over 2,000 healthcare organizations across 28 countries and territories have chosen MEDITECH to meet the challenges of a new era in healthcare." Customer types listed first: "Community and critical access hospitals". Also: "MEDITECH was founded in 1969", headquartered "in Canton, Massachusetts", and "MEDITECH Expanse is cloud-native and highly scalable, making it the ideal EHR platform for health systems of all sizes."
- 8.MEDITECH Expanse EHR live across first full U.S. divisions of HCA Healthcare · MEDITECH, 2026Press release, September 14, 2026. Quote: "As of the latest implementation group in August 2026, HCA Healthcare has 72 hospitals across its network in the U.S. and U.K. running on the MEDITECH Expanse platform."
- 9.MEDITECH Population Health · MEDITECH, 2026Accessed September 2026. Quote: "Actionable patient registries enable practices to take advantage of upcoming appointments to address gaps in care."
- 10.Expanse Genomics: How we're extending our industry-leading solution · MEDITECH, 2023Quote: "In addition, building out actionable cohorts of patients for research or trials can now be directed based on the specific genetic markers, often key when working with new drugs."
- 11.Greenfield Workspace · MEDITECH, 2026Accessed September 2026. Quote: "Developers can execute APIs and test their applications against a real MEDITECH EHR." Also: "US Core FHIR R4 APIs: Provides view-only access to patient-facing data after patients give the requesting app authorization to access their data. USCDI V1 and DSTU2/R4 compatible." On FHIR Scheduling: "User and patient workflows are supported for Expanse customers only."
- 12.How to work in the Greenfield Workspace · MEDITECH, 2026Quote: "Provide the MEDITECH Greenfield support team with a redirect/callback URI to generate an OAuth client ID and secret."
- 13.HL7 Outbound List for Greenfield · MEDITECH, 2026Lists outbound interfaces including admissions, laboratory results, order management, community-wide scheduling, pathology reports, home medications and charges. Quote: "The Admissions Outbound interface updates vendors with patient registration, demographic, and allergy information."
- 14.§ 170.315(g)(10) Standardized API for patient and population services · HealthIT.gov (ASTP/ONC), 2025Test method for the certification criterion. Requires FHIR R4 with US Core 6.1.0, SMART App Launch 2.0.0 and FHIR Bulk Data Access for multiple patients as of December 31, 2025, and plain-text representation of clinical note text.
- 15.United States Core Data for Interoperability (USCDI) · HealthIT.gov (ASTP/ONC), 2026Accessed September 2026. Clinical Notes data class: "Narrative patient data relevant to the context identified by note types." Note types vary by version; Consultation Note, Discharge Summary Note, History & Physical, Procedure Note and Progress Note appear in both USCDI v1 and v5.
- 16.US Core DocumentReference Profile (US Core STU 6.1) · HL7 International, 2023Quote: "To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching patient documents including Clinical Notes using the DocumentReference resource."
- 17.HTI-1 Final Rule Overview and Key Dates Fact Sheet · HealthIT.gov (ASTP/ONC), 2025Quote: "ONC has updated the USCDI standard in § 170.213 by adding USCDI Version 3 (v3) and establishing a January 1, 2026, expiration date for USCDI v1 (July 2020 Errata) for purposes of the Certification Program."
- 18.MEDITECH introduces Traverse Exchange interoperability network for U.S. Market · MEDITECH, 2024Press release, August 8, 2024. Quote: "In addition to connecting to a private MEDITECH network, Traverse Exchange enables customers to connect to other networks, public health agencies, and various data-sharing networks, such as Commonwell, Carequality, and QHINs under TEFCA"
- 19.MEDITECH Alliance program triples in size fueling innovation · MEDITECH, 2024Press release, December 4, 2024. Quote: "The Alliance program now hosts 37 solution members, offering 49 integrated solutions that complement, enhance, or extend MEDITECH Expanse."
Related pages
Implementation
Where the MEDITECH connection sits in the 48-hour plan.
ReadIntegrations
Every EHR and research system Bond connects to, and what each needs.
ReadSecurity
BAAs, encryption, access control and audit logging.
ReadIdentify: LLM-based EHR screening
How Bond reads charts against each criterion and explains matches.
ReadFHIR
The data standard behind the Expanse connection, in plain terms.
Read