How to integrate with InPracSys
This page lists what InPracSys publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.inpracsys.com.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| InPracSys EHR | 9.0 | Active | 2019-12-06 | 15.05.05.2762.INPS.01.00.1.191206 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://inpracsys.com/fhir/
- Application Access - Patient Selection (170.315 (g)(7)): https://ipsemrapi.inpracsys.com/App/web.html#jsintroduction
- Application Access - All Data Request (170.315 (g)(9)): https://ipsemrapi.inpracsys.com/App/web.html#jsintroduction
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://inpracsys.com/wp-content/uploads/2024/12/FhirServiceBaseBundleV10.json.
ONC Lantern tracks 1 FHIR endpoints for InPracSys. 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.