How to integrate with Modernizing Medicine
This page lists what Modernizing Medicine publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.modmed.com.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| EMA | 7 | Active | 2022-11-29 | 15.04.04.2002.EMA6.70.18.1.221129 |
| EMA Mobile | 5.23 | Withdrawn by Developer | 2021-05-10 | 15.04.04.2002.EMAM.22.12.0.210510 |
| Eyefinity EHR Mobile Powered by EMA | 5.15 | Withdrawn by Developer | 2019-12-31 | 15.04.04.2002.EyeM.15.04.0.191231 |
| Eyefinity EHR Powered by EMA | 5.15 | Withdrawn by Developer | 2019-12-31 | 15.04.04.2002.Eyef.15.04.0.191231 |
| ModMed ASC | 6 | Active | 2025-09-02 | 15.04.04.2002.mASC.06.11.0.250902 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://portal.api.modmed.com/
- Application Access - Patient Selection (170.315 (g)(7)): https://portal.api.modmed.com/
- Application Access - All Data Request (170.315 (g)(9)): https://portal.api.modmed.com/
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://public-api.gastro.prod.fhir.ema-api.com/fhir/r4/Endpoint?_include=Endpoint:managingOrganization&connection-type=hl7-fhir-rest, https://public-api.mmi.prod.fhir.ema-api.com/fhir/r4/Endpoint?_include=Endpoint:managingOrganization&connection-type=hl7-fhir-rest.
ONC Lantern tracks 200 FHIR endpoints for Modernizing Medicine. Reported FHIR versions: 4.0.1 (200).
How to integrate
- Read the (g)(10) documentation above. ONC criterion 170.315(g)(10) requires a standardized FHIR API for patient and population services.
- Register your application with the vendor, as its documentation describes.
- Authorize with SMART App Launch, or with SMART Backend Services for system-to-system access.
- Find the practice's FHIR base URL in the service base URL list.
- Plan for the gaps. (g)(10) certifies read access to USCDI data. Scheduling, charges, claims and write-back need vendor-specific APIs or another route.