ModMed (FHIR)
Integrate your application with the ModMed Certified FHIR API using Bulk FHIR backend services
🚀 Quickstart
Connect to the ModMed Certified FHIR API with Tenklo and see data flow in a few minutes. This integration uses ModMed's Bulk FHIR flow: machine-to-machine, JWT-signed authentication, with no end-user OAuth redirect.
This is ModMed's Certified (ONC) FHIR API. For the EMA Proprietary API, use the ModMed integration instead.
In Tenklo (free signup), go to Integrations → Configure New Integration → ModMed (FHIR). Register your Client ID, Key ID, Private Key, and Scope in the Settings tab — see the setup guide. These are entered once and reused automatically by every connection.
Each connection represents one practice. Create it by supplying that practice's FHIR Host — see the connect guide for the exact field.
Make your first request. Tenklo's proxy base URL is the practice's FHIR host, so include the FHIR version (/fhir/r4) in the path. Replace the placeholders with your API key (from Environment Settings), integration ID, and connection ID:
curl "https://api.tenklo.dev/proxy/fhir/r4/Patient?_count=10" \
-H "Authorization: Bearer <NANGO-API-KEY>" \
-H "Provider-Config-Key: <INTEGRATION-ID>" \
-H "Connection-Id: <CONNECTION-ID>"Or fetch credentials with the Node SDK or API.
✅ You're connected! Check the Logs tab in Tenklo to inspect requests.
Follow our Auth implementation guide to integrate Tenklo in your app.
📚 ModMed (FHIR) integration guides
Nango-maintained guides for common use cases.
-
How to register your own ModMed FHIR app
Register a Bulk FHIR app with ModMed, generate a key pair, host your JWKS file, and obtain your Client ID -
How to connect a practice to ModMed FHIR
Create a connection for a practice once it has added your Client ID
Official docs: ModMed Certified FHIR API authentication
🧩 Pre-built syncs & actions for ModMed (FHIR)
Explore Nango-provided actions in your dashboard. Extend and customize them to fit your needs.
No pre-built syncs or actions available yet.