eClinicalWorks (FHIR)
Integrate your application with the eClinicalWorks FHIR API using SMART Backend Services
🚀 Quickstart
Connect to eClinicalWorks with Tenklo and see data flow in a few minutes. eClinicalWorks uses the SMART Backend Services flow — a machine-to-machine, JWT-signed authentication, with no end-user OAuth redirect.
In Tenklo (free signup), go to Integrations → Configure New Integration → eClinicalWorks (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's FHIR facade. Create it by supplying that practice's FHIR Base URL and OAuth Server URL — see the connect guide for the exact fields.
Call the eClinicalWorks FHIR API
Make your first request. Replace the placeholders with your API key (from Environment Settings), integration ID, and connection ID:
curl "https://api.tenklo.dev/proxy/Patient" \
-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.
📚 eClinicalWorks (FHIR) integration guides
Nango-maintained guides for common use cases.
-
How to register your own eClinicalWorks app
Register with the eClinicalWorks Dev Portal, generate a key pair, host your JWKS file, and obtain your Client ID -
How to connect a practice to eClinicalWorks
Create a connection for a practice once your app is registered and approved
Official docs: eClinicalWorks Platform for Open Development — Backend Services authentication
🧩 Pre-built syncs & actions for eClinicalWorks (FHIR)
Explore Nango-provided actions in your dashboard. Extend and customize them to fit your needs.
No pre-built syncs or actions available yet.