Provider EHR Access
Flexpa is building comprehensive provider connectivity through the ONC (g)(10) Standardized API, bringing patient-held clinical records from EHR systems into a single, unified FHIR API. This page documents our connectivity progress across EHR vendor bundles, the features we have shipped in support of provider access, and our testing plan for each bundle before it goes live.
The CHPL directory is now live. It documents every ONC (g)(10)-certified EHR product and Flexpa's connectivity status for each one, updated weekly from CHPL.
#Connectivity
Provider connectivity is organized by EHR vendor User Access Brands bundle — the published list of FHIR endpoints maintained by each vendor under the ONC (g)(10) certification. Flexpa ingests these bundles, resolves SMART on FHIR authorization configuration for each endpoint, and surfaces them in the Endpoint Directory.
The authoritative source of ONC (g)(10) certified products is the ONC Certified Health IT Product List (CHPL). CHPL lists every EHR system that has achieved ONC certification under the 21st Century Cures Act, including the API endpoints each vendor is required to publish. Flexpa uses CHPL as the source of truth for which vendors are certified and cross-references their published endpoint bundles to build and maintain the directory.
#Major EHR connectivity status
| Bundle | Vendor | Auto-distribution | Status | Live |
|---|
Epic User Access Brands | Epic | ✓ | Connected | February 2026 |
Oracle Health (Cerner) | Cerner / Oracle Health | ✓ | Connected | February 2026 |
eClinicalWorks (Healow) | eClinicalWorks | ✓ | Connected | March 2026 |
| Athena Health | Athena | ✓ | In progress | May 5, 2026 |
| Meditech | Meditech | ✗ | In progress | — |
#FHIR resources
Unlike payer APIs, ONC (g)(10) certified EHR systems implement a standardized set of FHIR resources defined by US Core. The resources below are required across all ONC (g)(10) certified systems. Vendors certify against either US Core v3.1.1 or v6.1.0, which affects availability of newer resources.
- AllergyIntolerance
- CarePlan
- CareTeam
- Condition
- Device
- DiagnosticReport
- DocumentReference
- Encounter
- Goal
- Immunization
- Location
- Medication
- MedicationRequest
- Observation
- Organization
- Patient
- Practitioner
- PractitionerRole
- Procedure
- Provenance
- Coverage (US Core 6.0+)
- MedicationDispense (US Core 6.0+)
- RelatedPerson (US Core 5.0+)
- ServiceRequest (US Core 5.0+)
- Specimen (US Core 6.0+)
Observation covers a wide range of clinical data types — vital signs, laboratory results, social history, SDOH, smoking status, and more. Use the category search parameter to filter by type.
| Date | Feature |
|---|
August 8, 2025 | 90-day uptime monitoring for SMART on FHIR authorization endpoints |
November 26, 2025 | Improved endpoint status definitions (Connected / In Progress / Unknown / Unavailable / Broken) |
February 25, 2026 | Endpoint Directory available as public MCP server |
April 19, 2026 | DocumentReference binary attachment resolution — Binary resources resolved during sync |
April 19, 2026 | DiagnosticReport presentedForm binary resolution — rendered reports no longer silently skipped during sync |
May 7, 2026 | CHPL directory — direct weekly pulls from CHPL database, connectivity status, implementation details |
#Binary attachment resolution
Provider EHRs frequently return clinical documents and reports as binary attachments — rendered PDFs of lab results, pathology reports, discharge summaries, and imaging reports. These are surfaced in two ways through the Flexpa API:
- DocumentReference resources include a
content[].attachment.url pointing to a Binary resource. Flexpa resolves these during sync so the rendered document is available alongside the structured FHIR data.
- DiagnosticReport resources can include a
presentedForm[] array with URLs to rendered versions of the report — for example, a pathologist's signed PDF. Previously these were silently skipped, meaning the structured result Observations were returned but the rendered report was not. As of April 2026, both relative Binary/{id} and audience-scoped absolute {endpoint}/Binary/{id} URLs in presentedForm are resolved during sync.
Both resource types use the same binary extraction path, so your application can reliably expect rendered attachments to be present when the source EHR includes them. See DocumentReference › Binary Attachments for details.
#Testing plan
Each EHR vendor can choose to provide a sandbox environment with synthetic test patients for development and integration testing. If that is the case, Flexpa validates the following before marking a bundle as live:
| Step | Description |
|---|
| SMART configuration | Authorization, token, and introspection endpoint discovery via .well-known/smart-configuration |
| Patient authorization | End-to-end OAuth 2.0 PKCE flow with the vendor's patient-facing authorization server |
| Token refresh | Validating offline_access refresh token behavior |
| Resource coverage | Verification that US Core FHIR resources are returned — coming soon to the Endpoint Directory |
| Scope completeness | Confirming which scopes are supported per endpoint — coming soon to the Endpoint Directory |
| User testing | Occasional end-to-end connections with real patients to verify production behavior |