How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
ModMed website screenshot

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.

agent ready

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.

Kin Score

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.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 54.5/100 · developing
Contract Quality 14.4 / 25
Developer Ergonomics 13.8 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 5.1 / 13
Governance 2.5 / 12
Discoverability 6.9 / 10
Regulatory · Health 11.1 / 15
Agent readiness — 55/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract derived 2.5 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples 7.0 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 0 / 6
Agent Skills derived 1.3 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
ModMed Kin Score — API readiness rating by API Evangelist

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>

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 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 COLLECTION

ModMed Certified Goal API

OPEN COLLECTION

Scroll 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.

Rate 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.

Security 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.

Modernizing Medicine Authentication

apiKey/http/oauth2/openIdConnect · 3 schemes

SECURITY

Modernizing Medicine Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Modernizing Medicine Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Modernizing Medicine Scopes

76 scopes · authorizationCode

76 scopes

SCOPES

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.

Modernizing Medicine Agentic Access

125 operations · 20 acting

125 operations · 20 acting

AGENTIC

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.

Documentation 2

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

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

Where this information came from

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.