ONC (g)(10)

Medical record systems

Clinical records from the EHRs at hospitals and practices, shared by the patient through ONC (g)(10) certified Patient Access APIs, now with Epic MyChart Central sign-in across linked Epic organizations.

Read the docs Markdown for agents

NewEpic MyChart Central

A patient who signs in with their Epic ID can share records from the other Epic organizations already linked to their MyChart Central account, in the same step. Each organization becomes its own connection. It works where the organization uses MyChart Central, runs a supporting Epic version, and was found through the identity-verified nationwide search. Otherwise the sign-in connects that one organization, as before.

For people and teams

People sign in to their provider’s patient portal, such as MyChart, and share the record that facility keeps. It is the most detailed view of the care delivered there.

What comes back

Lab and imaging results, and clinical notes.
Conditions, medications, allergies, immunizations, and procedures.
Visits, care teams, and care plans, in the US Core FHIR resources every certified EHR supports.

How people connect

Search for the hospital, clinic, or practice.
Sign in with the patient portal account at that facility.
Approve sharing. Each facility is its own connection.

Good to know

Endpoints from Epic, Oracle Health (Cerner), and eClinicalWorks (Healow) are in the Endpoint Directory. The CHPL directory tracks Flexpa’s status for every ONC (g)(10) certified EHR product.
Flexpa starts retrieving within minutes of consent. A new record can take about 24 hours to become available at the facility.
A parent or guardian with proxy access in the EHR can connect a child’s record with their own portal sign-in. Each child is a separate connection.

For agents

Read as markdown

Source: ONC (g)(10) certified SMART on FHIR Patient Access APIs, certified to US Core v3.1.1 or v6.1.0
Patient sign-in: The patient portal account at each facility, such as MyChart
Find the facility: directory.search_endpoints at https://api.flexpa.com/mcp (no authentication)
Launch: Flexpa Consent authorization URL. flexpa_endpoint_id preselects a facility. Or flexpa_search_mode=true with flexpa_default_filter=PROVIDER.
FHIR R4: US Core resources, including Condition, Observation, DiagnosticReport, DocumentReference, MedicationRequest, Encounter, and Immunization
Timing: Retrieval starts within minutes of consent. A new record can take about 24 hours to become available at the source.

Records tools

After the patient authorizes through Flexpa Consent, at https://api.flexpa.com/mcp/consent. They need a patient access token.

get_labs Lab results
get_visits Encounters at the facility
get_documents Clinical document metadata
get_document_content The text of one clinical document

Notes for agents

An Epic ID sign-in at an organization the patient has not linked in MyChart Central sends them into account linking, and Epic does not return them to Flexpa. Suggest that facility’s own MyChart username, or linking at mychart.org first.
With MyChart Central, each Epic organization the patient selects settles as its own patient authorization.
Proxy access is time-limited and set by each organization. Treat repeated sync failures on a child’s authorization as a prompt to re-check proxy access.

Scale and context

Certified (g)(10) products, by Flexpa connectivity

Every active product listing certified to ONC §170.315(g)(10), the standardized patient access API criterion, grouped by Flexpa’s connection status.

300active certified product listings, from 224 developers

48developers with at least one listing Flexpa connects to

86 connected
23 connection in progress
13 application in progress
151 establishing contact
25 blocked
2 unknown

Show the data as a table

Certified (g)(10) products, by Flexpa connectivity
Flexpa status	Listings
Connected	86
Connection in progress	23
Application in progress	13
Establishing contact	151
Blocked	25
Unknown	2

Counts certified product listings and their developers. It is not a count of hospitals, practices, or patients, and not market share: one listing can be deployed at many organizations, and one developer can hold several listings.
Statuses are Flexpa’s connectivity to each listing’s patient access API, from the CHPL directory in the docs.

Sources: ONC Certified Health IT Product List (CHPL), active §170.315(g)(10) listings, as synced by Flexpa (November 9, 2026); Flexpa CHPL directory (November 12, 2026).

In the docs

Other networks

All three work together in one Flexpa integration and return the same FHIR R4 API.

CMS-9115
Health insurers
Claims, coverage, and clinical history from health insurers, shared by the member through the Patient Access APIs required by CMS-9115.
Sign-in: The member’s own health plan account
TEFCA IAS
Nationwide exchanges
One identity verification finds a person’s records across facilities on the TEFCA network. Flexpa is an Individual Access Services provider through two QHINs, Kno2 and CommonWell.
Sign-in: IAL2 identity verification with CLEAR, ID.me, or Persona

Bring patient-consented records into your app or agent.

Try the demo to see the consent flow and the records it returns.

Try the demo