ModMed API
ModMed (Modernizing Medicine) is a cloud-based specialty EHR suite serving 40,000+ providers, pairing its EMA EHR's adaptive specialty workflows with practice management, billing, payments, and patient engagement across roughly eleven medical specialties. An unofficial API lets you programmatically pull patients, encounters, appointments, and claims data—and push updates like new appointments and patient records back into ModMed.
What is ModMed?
ModMed (Modernizing Medicine) provides cloud-based EHR and services for specialty medical practices. Its EMA EHR adapts to specialty-specific exam workflows across fields like dermatology, ophthalmology, orthopedics, ENT, gastroenterology, urology, plastic surgery, and podiatry, and the broader suite spans practice management and billing, gGastro for GI, Klara patient engagement, ModMed Pay, and AI documentation tools. More than 40,000 providers—from solo practices to large multi-site groups—run on the platform.
Common data entities:
- Patients, Demographics, Insurance coverage
- Encounters, Specialty exam notes, Diagnoses, Treatment plans
- Pathology results, Clinical images, Orders, Prescriptions
- Appointments, Schedules, Tasks
- Claims, ERAs, Billing records, Payments
The ModMed Integration Challenge
ModMed does publish API documentation—but documentation is not access, and the full practice-data surface sits behind a partner gate:
- Read-only public FHIR: the ONC Certified FHIR R4 API supports read, search, and bulk export only, scoped for patient access, with vendors required to register as a ModMed Certified FHIR API vendor
- Partner-gated write API: the proprietary FHIR API that covers EMA and Practice Management with create and update operations requires a vendor application, API terms, and a partnership evaluation before access
- Slow sandbox provisioning: sandbox environments are provisioned by ModMed rather than self-serve, adding lead time before a single test call
- No SDKs or documented webhooks: integrations must poll, and there is no event stream for new encounters, claims, or schedule changes
- Curated marketplace: third-party apps route through the synapSYS marketplace's approved partner list rather than open connectivity
- PHI and compliance constraints: specialty exam notes, pathology results, and claims demand HIPAA-aligned access controls and audit trails
How Supergood Creates ModMed APIs
Supergood reverse-engineers ModMed's authenticated workflows to deliver a resilient, normalized API layer for your practice—covering patients, encounters, scheduling, and billing without a vendor application, partnership evaluation, or weeks of sandbox lead time.
- Handles practice credentials, session continuity, and MFA securely in a managed session
- Maintains sessions with automated refresh and change detection across multi-site groups
- Normalizes responses across patients, encounters, appointments, and claims so you integrate once and rely on consistent objects
- Aligns with HIPAA-conscious access controls, scoped tokens, and audit logging for PHI
Use ModMed with AI agents: ModMed MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your specialty, modules, and authentication model. - Supergood Generates and Validates Your API
We deliver a hardened, production-ready ModMed adapter tailored to your practice configuration. - Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as ModMed evolves.
Potential API Endpoints
Authentication
/authenticateAuthenticate to a ModMed practice account and obtain a session token for downstream calls.
Patient Operations
/patientsList patient records with filters for name, date of birth, provider, and insurance coverage.
Scheduling
/appointmentsRetrieve appointments and schedules with provider, location, and date-range filters.
Scheduling
/create_appointmentBook a new appointment against a provider's schedule at a given location.
Clinical
/encountersPull specialty exam notes, diagnoses, treatment plans, and pathology results for a patient encounter.
Billing
/submit_claimSubmit an insurance claim and track its status, ERAs, and payments.
Use Cases
Sync clinical and patient data into your systems
- Pull patients, encounters, and specialty exam notes into a central warehouse - Keep demographics and insurance coverage in sync with downstream tools - Stream pathology results and clinical images to review and registry workflows
Automate claims and revenue cycle work
- Pull claims, ERAs, and billing records for financial reporting - Match remittances against expected reimbursement to surface underpayments - Route denied or pending claims to staff queues without portal clicks
Streamline scheduling and patient flow
- Trigger reminders and waitlist workflows from real schedule data - Book and reschedule appointments programmatically across providers and locations - Surface no-show and cancellation events to engagement platforms
Connect orders, prescriptions, and follow-up
- Pull orders and prescriptions tied to each encounter for downstream tracking - Trigger follow-up outreach when treatment plans or results are posted - Reconcile completed orders against billing and claims
Technical Requirements
Authentication
Practice credentials and MFA handled in a managed, encrypted session
Connectivity
Authenticated ModMed workflows surfaced as a normalized API, beyond read-only patient-access FHIR scopes
Response format
Normalized JSON across patient, encounter, appointment, claim, and billing objects
Rate limits
Adaptive throttling tuned to your practice to avoid platform-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for patients, schedules, and claims with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned controls, and audit logging
Webhooks
Event-style callbacks for new encounters, appointments, claim status changes, and results
Latency
Sub-second reads on cached entities; multi-second writes when booking appointments and submitting claims
Throughput
Horizontally scaled workers sized to solo practices through large multi-site specialty groups
Reliability
Retry, backoff, and idempotency keys for appointment booking and claim submission
Adaptation
Continuous monitoring of ModMed releases and practice configuration drift
Frequently asked questions
ModMed's portal documents two APIs, but neither is self-serve: the ONC Certified FHIR R4 API is read, search, and bulk export only, and the proprietary FHIR API with write access requires a vendor application, API terms, a partnership evaluation, and ModMed-provisioned sandboxes. Supergood connects with your existing practice credentials instead.
Yes. Supergood normalizes clinical data from EMA encounters alongside scheduling, claims, and billing data from practice management workflows into one consistent API surface.
Yes. PHI flows through an encrypted credential vault with scoped tokens, HIPAA-aligned access controls, and full audit logging so exam notes, results, and claims stay protected.
Yes. Where ModMed's workflows permit it, the API supports write operations such as booking appointments and updating patient records—capabilities the public read-only FHIR endpoint does not expose.
Supergood continuously monitors ModMed releases and your practice configuration, adapting the adapter automatically so your integration keeps running through updates.