Written and maintained by CASRAI Editorial Board
Last updated
ModMed (Modernizing Medicine, Inc.) is a healthcare information technology company that develops cloud-based, specialty-specific electronic health record (EHR), practice management, and revenue cycle platforms for outpatient medical and surgical specialties. Founded in 2010 by Daniel Cane and dermatologist Dr. Michael Sherling, ModMed centers its clinical software suite on EMA (Electronic Medical Assistant) for ambulatory specialties and gGastro for gastroenterology practices and endoscopy centers.
In clinical informatics and real-world data (RWD) research, ModMed is notable for replacing generic, free-text hospital EHR templates with physician-authored, specialty-specific domain models that capture structured anatomical location, morphology, staging, and procedural data at the point of care.
What Is ModMed EMA EHR and How Does Its Specialty Data Model Work?
Unlike general-purpose enterprise EHRs designed primarily for inpatient acute care and retrofitted for outpatient clinics, EMA EHR is engineered around native domain ontologies for distinct ambulatory specialties, including:
- Dermatology and dermatopathology
- Ophthalmology and optometry
- Orthopedics and sports medicine
- Otolaryngology (ENT) and allergy/asthma/immunology
- Plastic surgery and podiatry
- Urology, pain management, and obstetrics/gynecology (OB/GYN)
1. Structured Point-of-Care Capture and the Virtual Exam Room
During a clinical encounter, EMA presents specialty-specific protocols and an interactive Virtual Exam Room featuring touch-enabled anatomical diagrams (the Body Atlas). When a clinician taps a specific anatomical sub-site—such as a dermatological lesion site, a specific joint compartment, or an ocular structure—and selects clinical findings and impressions, EMA automatically binds the entry to standardized clinical vocabularies, including ICD-10-CM, CPT, HCPCS, SNOMED CT, LOINC, and RxNorm.
For clinical data management and observational registries, this architecture minimizes reliance on natural language processing (NLP) over unstructured progress notes. Laterality, anatomical site, lesion size, and procedure modifiers are stored as discrete, queryable database elements from the moment of charting.
2. The Adaptive Learning Engine
EMA incorporates an Adaptive Learning Engine that observes each clinician’s recurring diagnostic impressions, physical exam patterns, prescription preferences, and procedural workflows. By ranking clinical plans according to both specialty-wide consensus protocols and individual provider usage patterns, the engine reduces repetitive template navigation while maintaining standardized coding across multi-provider practices.
How Does ModMed Support ONC (g)(10) FHIR R4 Interoperability?
Both ModMed EMA and gGastro are certified under the ONC Health IT Certification Program, including the 21st Century Cures Act 45 CFR § 170.315(g)(10) Standardized API for patient and population services. This certification mandates standards-based interoperability across three technical layers:
| Interoperability Layer | Technical Standard Supported by ModMed | Clinical & Research Informatics Function |
|---|---|---|
| Data Model & Profiles | HL7 FHIR Release 4 (R4) & US Core Implementation Guide | Exposes United States Core Data for Interoperability (USCDI) classes as standardized resources (Patient, Condition, Observation, MedicationRequest, Procedure, DiagnosticReport, DocumentReference, AllergyIntolerance, and Immunization). |
| Application Launch & Auth | SMART on FHIR (OAuth 2.0 & OpenID Connect) | Enables standalone patient-facing apps and EHR-embedded clinician apps to authenticate securely with granular resource scopes (patient/*.read, user/*.read, launch). |
| Population-Level Export | FHIR Bulk Data Access ($export / Flat FHIR NDJSON) |
Allows authorized health systems, clinical data registries, and research cohorts to extract multi-patient datasets in Newline Delimited JSON (NDJSON) format without overloading transactional APIs. |
How Do Third-Party Developers Integrate With the ModMed API?
Health IT developers, diagnostic laboratories, and clinical trial technology vendors integrate with ModMed environments through two primary channels:
- Public ONC (g)(10) SMART on FHIR Endpoints: Patient-authorized applications and provider-facing SMART on FHIR applications register against ModMed’s FHIR R4 authorization and resource servers to read USCDI clinical records, problem lists, medications, laboratory observations, and clinical notes.
- ModMed synapSYS API Platform: For deeper operational and bi-directional workflows—such as creating or updating appointment schedules, posting patient demographics and insurance eligibility, ingesting structured laboratory orders/results, or filing external clinical documents—third-party vendors use the ModMed synapSYS partner program. The synapSYS platform provides RESTful FHIR-based APIs with sandbox environments and tenant-specific credentials authorized by participating medical practices.
Research Practice and Specialty Registry Applications
Because outpatient subspecialties such as dermatology, ophthalmology, orthopedics, and gastroenterology conduct the majority of their care outside academic hospital inpatient settings, hospital-centric data networks often under-capture ambulatory specialty outcomes. In real-world evidence (RWE) studies and post-market surveillance, ModMed’s structured specialty data capture supports:
- Specialty Registry Submissions: Automated reporting to qualified clinical data registries (QCDRs) and specialty society registries for Merit-based Incentive Payment System (MIPS) quality measures and longitudinal outcome tracking.
- Cohort Feasibility and Clinical Data Abstraction: Identifying eligible trial participants based on discrete histological diagnoses, anatomic staging, biometric measurements (such as intraocular pressure or visual acuity in ophthalmology), or prior biologic therapy exposure.
- Standardized Data Harmonization: Mapping structured FHIR R4 resources and SNOMED CT / ICD-10-CM / LOINC codes into analytical schemas such as the OMOP Common Data Model or CDISC clinical data standards.
Sources
- ModMed (Modernizing Medicine, Inc.). EMA Specialty EHR & Healthcare Technology Platform Overview. https://www.modmed.com/
- ModMed (Modernizing Medicine, Inc.). ONC Health IT Certification & FHIR API Documentation (§ 170.315(g)(10)). https://www.modmed.com/onc-certification/
- HL7 International. US Core Implementation Guide (FHIR R4). https://hl7.org/fhir/us/core/
