API Reference
The current state of the JamEMR API — an internal API secured with registered, revocable tokens today, with a documented public partner API and HL7 FHIR interoperability planned.
Where the API stands today
JamEMR is API-driven internally: the web application and every module operate through the same API backend, secured with registered, revocable API tokens and covered by role-based access control and audit logging. That API exists and runs every JamEMR deployment today.
What does not exist yet is a public, documented partner API — and we would rather say that plainly than publish endpoint documentation we are not ready to support.
What is planned
- A public/partner API with stable, documented, versioned endpoints for integration partners, using the same registered-token security model described in the Security Model.
- HL7 FHIR interoperability, so JamEMR exchanges clinical data with other systems using the standard the healthcare ecosystem has settled on.
We are not publishing timelines or draft endpoint specifications here. When the partner API is ready, its documentation will live on this page, and changes to it will appear in the Release Notes.
Integrating during the pilot
Pilot practices with a concrete integration need should raise it through their pilot channel — integration scoping is part of what pilots are for, and pilot feedback directly shapes what the public API becomes.
Register your interest
If your organization wants to build against the JamEMR API when it opens, email sales@jamemr.com with a short description of the integration you have in mind. We will notify registered parties when partner API documentation is published.