How to integrate with Commure (d/b/a Athelas)
This page lists what Commure (d/b/a Athelas) publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.commure.com.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| Air | 1 | Active | 2026-06-17 | 15.04.04.3268.Air1.01.00.1.260617 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://docs.athelas.com/air_developer/fhir_api/commure_ehr_fhir_api
- Application Access - Patient Selection (170.315 (g)(7)): https://docs.athelas.com/air_developer/fhir_api/commure_ehr_fhir_api
- Application Access - All Data Request (170.315 (g)(9)): https://docs.athelas.com/air_developer/fhir_api/commure_ehr_fhir_api
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://api.commure.com/fhir/onc/base.json.
ONC Lantern tracks 1 FHIR endpoints for Commure (d/b/a Athelas). Reported FHIR versions: 4.0.1 (1).
How to integrate
- Read the (g)(10) documentation above. ONC criterion 170.315(g)(10) requires a standardized FHIR API for patient and population services.
- Register your application with the vendor, as its documentation describes.
- Authorize with SMART App Launch, or with SMART Backend Services for system-to-system access.
- Find the practice's FHIR base URL in the service base URL list.
- Plan for the gaps. (g)(10) certifies read access to USCDI data. Scheduling, charges, claims and write-back need vendor-specific APIs or another route.