ModMed
ModMed (Modernizing Medicine, Inc., Boca Raton FL) builds specialty-specific cloud healthcare software — the EMA electronic health record, ModMed Practice Management, gGastro for gastroenterology, analytics, revenue cycle management and telehealth — for allergy, dermatology, ENT, gastroenterology, OBGYN, ophthalmology, orthopedics, pain management, plastic surgery, podiatry and urology practices. It publishes two public APIs from one developer portal at portal.api.modmed.com: the EMA Proprietary API, a FHIR R4-style read/write interface under /fhir/v2 covering patients, appointments, slots, coverage, charges, documents and clinical data for synapSYS Marketplace vendors; and the ModMed Certified FHIR API, an ONC-certified HL7 FHIR R4 / US Core read-and-search interface with SMART on FHIR app launch and Bulk FHIR NDJSON export across EMA, ModMed PM, ModMed GI and gGastro. Customer FHIR service base URLs are published publicly as required by the 21st Century Cures Act.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ModMed the way a machine reads it — 94 machine-readable artifacts across 43 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ModMed scores 54.5/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from ModMed's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/modernizing-medicine/"
title="ModMed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/modernizing-medicine.svg"
alt="ModMed Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/modernizing-medicine/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/modernizing-medicine/"
title="ModMed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/modernizing-medicine/card.svg"
alt="ModMed Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ModMed
Each block below is one kind of artifact we hold for ModMed. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 43
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ModMed Allergy Intolerance API
The AllergyIntolerance FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance
ModMed Appointments and Slots API
Appoitments and Slots Details
ModMed Authentication API
SMART-on-FHIR OAuth 2.0 endpoints.
ModMed Capability Statement API
Capability Statement
ModMed Care Plan API
The CarePlan FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-careplan
ModMed Care Team API
The CareTeam FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam
ModMed Charges/Financial API
Charges/Financial details
ModMed Clinical Data/Clipboard API
Clinical Data/Clipboard details
ModMed Condition API
The Condition FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition
ModMed Coverage API
The Coverage FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-coverage
ModMed Device API
The Device FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device
ModMed Diagnostic Report API
The DiagnosticReport FHIR resource type
ModMed Document Reference API
The DocumentReference FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference
ModMed Documents API
Documents details
ModMed Encounter API
The Encounter FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-encounter
ModMed Encounters/Visits API
Encounters/Visits details
ModMed Endpoint API
The Endpoint FHIR resource type
ModMed Goal API
The Goal FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-goal
ModMed Group API
The Group FHIR resource type
ModMed Immunization API
The Immunization FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-immunization
ModMed Insurance API
Insurance Details
ModMed Location API
The Location FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-location
ModMed Locations/Facilities API
Locations/Facilities details
ModMed Medication API
The Medication FHIR resource type
Base profile: http://hl7.org/fhir/StructureDefinition/Medication
ModMed Medication Dispense API
The MedicationDispense API from ModMed — 2 operation(s) for medicationdispense.
ModMed Medication Request API
The MedicationRequest FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest
ModMed Observation API
The Observation FHIR resource type
ModMed Operation Definition API
The OperationDefinition FHIR resource type
Base profile: http://hl7.org/fhir/StructureDefinition/OperationDefinition
ModMed Organization API
The Organization FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization
ModMed Patient API
The Patient FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient
ModMed Practitioner API
The Practitioner FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner
ModMed Practitioner Role API
The PractitionerRole FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole
ModMed Procedure API
The Procedure FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure
ModMed Provenance API
The Provenance FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance
ModMed Providers and Referring Providers API
Providers details
ModMed Questionnaire API
The Questionnaire API from ModMed — 2 operation(s) for questionnaire.
ModMed Questionnaire Response API
The QuestionnaireResponse API from ModMed — 2 operation(s) for questionnaireresponse.
ModMed Related Person API
The RelatedPerson API from ModMed — 2 operation(s) for relatedperson.
ModMed Service Request API
The ServiceRequest FHIR resource type
Base profile: http://hl7.org/fhir/us/core/StructureDefinition/us-core-servicerequest
ModMed Specimen API
The Specimen API from ModMed — 2 operation(s) for specimen.
ModMed Tasks/Recalls API
Tasks/Recalls Details
ModMed Transcription API
Transcription details
ModMed Value Set API
The ValueSet FHIR resource type
Scroll within the panel for all 43 ·
Open Collections 44
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONModMed Certified Allergy Intolerance API
OPEN COLLECTIONEMA Proprietary Appointments and Slots API
OPEN COLLECTIONModernizing Medicine Authentication API
OPEN COLLECTIONModernizing Medicine Capability Statement API
OPEN COLLECTIONModMed Certified Care Plan API
OPEN COLLECTIONModMed Certified Care Team API
OPEN COLLECTIONEMA Proprietary Charges/Financial API
OPEN COLLECTIONEMA Proprietary Clinical Data/Clipboard API
OPEN COLLECTIONModMed Certified Condition API
OPEN COLLECTIONModMed Certified Coverage API
OPEN COLLECTIONModMed Certified Device API
OPEN COLLECTIONModMed Certified Diagnostic Report API
OPEN COLLECTIONModMed Certified Document Reference API
OPEN COLLECTIONEMA Proprietary Documents API
OPEN COLLECTIONModMed Certified Encounter API
OPEN COLLECTIONEMA Proprietary Encounters/Visits API
OPEN COLLECTIONModMed Certified Endpoint API
OPEN COLLECTIONModMed Certified Goal API
OPEN COLLECTIONModMed Certified Group API
OPEN COLLECTIONModMed Certified Immunization API
OPEN COLLECTIONEMA Proprietary Insurance API
OPEN COLLECTIONModMed Certified Location API
OPEN COLLECTIONEMA Proprietary Locations/Facilities API
OPEN COLLECTIONModMed Certified Medication API
OPEN COLLECTIONModMed Certified Medication Dispense API
OPEN COLLECTIONModMed Certified Medication Request API
OPEN COLLECTIONModMed Certified Observation API
OPEN COLLECTIONModMed Certified Operation Definition API
OPEN COLLECTIONModMed Certified Organization API
OPEN COLLECTIONModernizing Medicine Patient API
OPEN COLLECTIONModMed Certified Practitioner API
OPEN COLLECTIONModMed Certified Practitioner Role API
OPEN COLLECTIONModMed Certified Procedure API
OPEN COLLECTIONModMed Certified Provenance API
OPEN COLLECTIONEMA Proprietary Providers and Referring Providers API
OPEN COLLECTIONModMed Certified Questionnaire API
OPEN COLLECTIONModMed Certified Questionnaire Response API
OPEN COLLECTIONModMed Certified Related Person API
OPEN COLLECTIONModMed Certified Service Request API
OPEN COLLECTIONModMed Certified Specimen API
OPEN COLLECTIONEMA Proprietary Tasks/Recalls API
OPEN COLLECTIONEMA Proprietary Transcription API
OPEN COLLECTIONModMed Certified Value Set API
OPEN COLLECTIONScroll within the panel for all 44 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
modernizing-medicine-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Modernizing Medicine Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for ModMed — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/modernizing-medicine · machine-readable index on apis.io
This is an independent, third-party profile of ModMed, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.