Every health insurer in the United States is required to publish a FHIR API for patient data access. So is every EHR that achieves ONC's (g)(10) certification. The insurer side is well-understood: Flexpa connects to hundreds of payers and the list is visible in our network directory. The EHR side is less visible, and more complex. Today we're fixing that.
We're launching a public directory of every ONC CHPL (g)(10)-certified EHR product, along with Flexpa's live connectivity status for each one.
What is the CHPL?
The Certified Health IT Product List (CHPL) is the authoritative source for ONC-certified health IT products in the United States. When an EHR achieves (g)(10) certification, it means the system has been tested and verified to publish a standards-compliant FHIR API that supports patient access to their health data.
(g)(10) is the certification criterion that directly enables patient data portability. It requires EHRs to support the SMART App Launch Framework, FHIR R4, and a defined set of clinical data categories. There are currently over 495 certified products in the CHPL, spanning independent physician practices, large health systems, community health centers, and everything in between.
What the directory shows
For each CHPL listing, we publish:
Connectivity status reflects whether Flexpa is actively connected, in the process of connecting, or still establishing contact with that endpoint:
- Connected — Flexpa is live on this endpoint. Patients using apps built on Flexpa can request records from this EHR.
- Connection In Progress — We've completed onboarding and are finishing technical integration.
- Application In Progress — We've submitted an application and are awaiting approval from the EHR vendor.
- Establishing Contact — We've identified the endpoint and are initiating the onboarding process.
- Blocked — The vendor has declined to connect or has imposed terms we cannot accept.
Distribution and fee information covers whether the endpoint supports auto-distribution to its facilities (i.e., whether Flexpa requires individual provider authorization), whether the vendor charges additional fees for API access, and whether the connection is patient-driven.
Sandbox availability indicates whether a development sandbox is available for testing before production.
Why this matters
FHIR-based patient data access depends on two things: a mandate and a connection. The (g)(10) certification creates the mandate, requiring EHRs to publish FHIR APIs. Flexpa creates the connection, doing the integration work so developers don't have to.
The directory makes the connection layer transparent. If your patients use a particular EHR, you can look it up and see whether Flexpa can already retrieve their records, or where we are in the process of getting there.
We sync the CHPL weekly and update connectivity statuses as integrations go live. The directory reflects the current state of Flexpa's EHR network at any point in time.
View the directory
The full directory is available at flexpa.com/docs/network/chpl.
If you're building on Flexpa and need access to a specific EHR that isn't yet connected, reach out. We prioritize integration work based on customer demand.
