ModMed sells specialty EHR software and related practice tools, with separate connectivity paths for a Certified FHIR API, an EMA Proprietary API, and traditional HL7 options. Public portal material also describes patient portal, provider, practice management, and AI documentation functions across EMA and gGastro-related workflows. [1][2][4][5]
Product scope and specialty focus
ModMed’s website presents the company as a specialty practice software vendor with EHR, patient engagement, practice management, analytics, and revenue cycle products. The home page lists specialty categories including allergy, dermatology, ENT, gastroenterology, general surgery, OB/GYN, ophthalmology, orthopedics, pain management, plastic surgery, podiatry, and urology. That positioning is marketing language, but it is consistent with the product pages that describe specialty-specific EHR and related operational tools. [5][4]
The EHR page describes ModMed EMA as specialty-specific software, with examples such as GI-oriented content and templates on the gastroenterology page. The public website also states that the platform supports a mobile EHR app so providers can work across the practice, ASC, hospital, or from home. These statements describe intended workflow settings rather than a full implementation map for every customer. [4][5]
Certified FHIR API path
ModMed’s portal describes the EMA Certified FHIR API as tailored for EMA, MMPM, ModMed GI, and gGastro systems, with SMART on FHIR support, OAuth 2.0 authorization, and HL7 FHIR R4 alignment. The same portal says this API supports read and search, bulk data export in NDJSON format, and retrieval and visualization by patients through the Patient Portal or by providers through provider credentials. [1][2][6]
The certified path is documented as a self-service model that depends on published endpoints and app registration. Authentication docs state that the EMA Certified FHIR API has no public sandbox and that authorization and API calls run against production. The portal also separates the certified path from traditional HL7 options; HL7 is described elsewhere as another connectivity choice, not as a documented part of the certificated path. [2][6][1]
Hypothetical integration example
If a gastroenterology practice wanted an app that reads patient demographics and recent clinical data from the certified FHIR path, the vendor would first register the app, obtain the required scopes, and test against the production endpoint rules described in the docs. The certified path supports read and search only, so a different app that needed write access or practice-specific workflow behavior would fit the proprietary path instead, subject to synapSYS review and the customer’s approved ACLs. The proprietary API supports CREATE/READ/SEARCH/UPDATE for many resources, not necessarily every needed workflow or customer deployment. This example is hypothetical and does not imply a guaranteed outcome.
A provider-facing tool could also use EHR launch context so the user starts inside the chart with a patient or encounter already set, while a patient portal app would follow the patient authentication flow described in the authentication page. The practical choice between these paths depends on the workflow the vendor is trying to support, not on a single universal integration pattern. [6][2]
EMA Proprietary API and implementation control
The EMA Proprietary API is documented as an FHIR R4-based API for EMA and ModMed Practice Management. The portal says it supports secure access to patients, appointments, and clinical data, with operations such as CREATE, READ, SEARCH, and UPDATE for many resources, and that it includes OAuth2-based security, sandbox environments for testing, and customized extensions for practice-specific needs. [1][2]
ModMed says vendors who pursue the proprietary path work with the synapSYS team, use a backend sandbox, define required ACLs, and complete a technical review before access to a first customer production system. That is a distinct implementation gate from the EMA Certified FHIR API path, which the portal frames as more self-service. The available documentation does not describe how often review cycles occur or which customer types use one path versus the other. [2][1]
Workflow functions in the EHR and practice stack
Across its public pages, ModMed describes patient engagement, practice management, analytics, reporting, and billing links within a single platform. The EHR page says ModMed Scribe 2.0 can listen to natural conversation and suggest visit notes, prescriptions, lab orders, and ICD-10 codes for review. The same page says the system automates MIPS tracking and displays near real-time analytics dashboards inside the workflow. [4][5]
The website also describes message categorization and routing to team inboxes, patient communication and scheduling in one place, and links between clinical charts and billing to reduce duplicate entry. These are vendor-described workflow functions, not independent measurements of performance. Public pages do not specify a universal installation sequence, required hardware beyond the mentioned iPad/web interface examples, or customer-specific configuration limits. [4][5][3]
Technical boundaries, user contexts, and unknowns
Authentication guidance sets out different launch and grant patterns for patient apps, provider apps, patient-plus-provider apps, and bulk FHIR background apps. The docs say patient and provider apps rely on standalone authentication first, then an in-context EHR launch link, while bulk FHIR uses client credentials with a signed JWT and no per-user authentication. For patient apps, the first standalone authentication requires a valid Patient Portal username and password, and a link is later placed inside the patient portal. For provider apps, the provider authenticates with EHR credentials, and a link is later placed inside the EHR instance. These are access patterns, not a claim that every customer deploys every pattern. [6]
The documentation leaves several operational details unspecified, including pricing, customer counts by specialty, exact uptime, implementation duration, and which integrations are standard versus custom. It also does not give a single master list of all resources, ACLs, or scopes for every deployment path. Any comparison of readiness across specialties would be hypothetical unless a specific customer workflow were documented. [1][2][6]