How to integrate with Indian Health Service
This page lists what Indian Health Service publishes for integrations, from ONC's Certified Health IT Product List (CHPL) and ONC Lantern, as of 2026-11-11. Website: https://www.ihs.gov/promotinginteroperability/certificationoverview/.
Certified products
| Product | Latest version | Status | Certified | CHPL listing |
|---|---|---|---|---|
| Resource and Patient Management System (RPMS) | RPMS Suite (BCER) v1.0 | Retired | 2011-10-18 | CHP-007015 |
| Resource and Patient Management System Electronic Clinical Quality Measure (eCQM) Reporting Tool | 2.0 | Withdrawn by Developer | 2019-10-02 | 15.02.05.1673.A076.02.01.1.191002 |
| Resource and Patient Management System Electronic Health Record | BCERv10.0 | Active | 2026-08-31 | 15.99.05.1673.RPMS.03.06.1.260831 |
Published API documentation
- Standardized API for Patient and Population Services (170.315 (g)(10)): https://www.ihs.gov/cis/api-documentation/
- Application Access - Patient Selection (170.315 (g)(7)): https://www.ihs.gov/directmessaging/resources/phr/?p=phr%5CIHS_Rest_API_Application_Access.pdf&flname=IHS_Rest_API_Application-Access.pdf&download=1
- Application Access - All Data Request (170.315 (g)(9)): https://www.ihs.gov/directmessaging/resources/phr/?p=phr%5CIHS_Rest_API_Application_Access.pdf&flname=IHS_Rest_API_Application-Access.pdf&download=1
FHIR endpoints
Service base URL list, which gives the FHIR endpoint for each customer: https://ihs4dhapim.ihs.gov/base-url/base-url.
ONC Lantern tracks 2 FHIR endpoints for Indian Health Service.
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.