ModMed
ModMed provides strong write access through its proprietary FHIR API after a partner onboarding process. The dual-track API architecture (proprietary vs. certified) means maintaining two integration paths with different auth methods.
Medium complexityPartnerProprietary FHIR R4Certified FHIR R4
FHIR Version
R4 (US Core 4.0.0 STU4)
Rate Limit
1,000 calls/min per API key (proprietary; customizable)
Sandbox
Yes — provisioned in ~2 weeks
ONC Certified
Yes
Capability Matrix
| Capability | Read | Write |
|---|---|---|
Patients | ||
Appointments | ||
Encounters | ||
Clinical Notes | ||
Document Upload | ||
Lab Results | ||
Medications | ||
Allergies | ||
Conditions | ||
Immunizations | ||
Vitals |
Billing / Claims | ||
Coverage / Insurance | ||
Referrals | ||
Bulk Data Export | — | |
Events / Webhooks | — |
DocumentedNot documentedSelf-serveGatedPartner only
Integration considerations
- Two separate API tracks with different auth methods — developers must maintain dual integration paths
- Proprietary API uses OAuth2 Password Grant (deprecated in OAuth 2.1 draft)
- No webhooks — must poll for data changes using _lastUpdated parameter
- Per-practice credential management — each practice generates separate credentials per vendor
- Proficiency demo required before production access adds onboarding time
- Proprietary API does not support ModMed GI/gGastro practices
Need help with gated access?
Some capabilities require contracts, partner agreements, or special approval. Cobalt has existing integrations with these systems.
Learn more- [Vendor]API Portal
- [Vendor]Proprietary API Documentation (PDF)
- [Vendor]Certified FHIR API Documentation (PDF)
- [Vendor]ONC Certification Press Release
- [Vendor]Become a Partner
- [Vendor]Certified API Vendor Registration
- [Vendor]FHIR Endpoint Directory
- [Vendor]synapSYS Marketplace
