Four ways your records come in
Point at a lead, or choose a source, to see what it is and what Flexpa does through it.
Health insurer · CMS-9115
Medicare.gov, through CMS Blue Button 2.0
A health plan Patient Access API. CMS-9115 requires plans in Medicare, Medicare Advantage and Medicaid to offer one in FHIR.
Through Flexpa: The patient signs in with their Medicare.gov account, and Flexpa retrieves their claims and coverage as FHIR.
Flexpa uses the Blue Button 2.0 APIs but is not endorsed or certified by CMS or HHS.
Network:Health insurersCMS-9115→
Medical record systems · ONC (g)(10)
Patient portals on Epic, Oracle Health and athenahealth
The FHIR patient access APIs that certified medical record systems must offer, one hospital or practice at a time.
Through Flexpa: The patient signs in to that facility’s own portal, such as its MyChart. Each facility becomes its own authorization, and its clinical records arrive as FHIR.
Network:Medical record systemsONC (g)(10)→
Epic · Community authorization
Epic MyChart Central
Epic’s account linking service: one Epic ID signs a patient in to every Epic organization they have linked at mychart.org.
Through Flexpa: Flexpa asks Epic for its community scope, the patient picks the linked organizations to share, and Flexpa exchanges one token per organization to retrieve each one’s records as its own authorization.
Live since November 11, 2026, for organizations on Epic’s August 2026 version or newer (May 2026 if switched on) that the nationwide search found.
Network:Epic MyChart CentralCommunity authorization→
Nationwide exchanges · TEFCA IAS
TEFCA Individual Access Services
The national framework for health information exchange. Flexpa is an IAS provider through two QHINs, Kno2 and CommonWell.
Through Flexpa: The patient verifies their identity once at IAL2 with CLEAR, ID.me or Persona. Flexpa finds their records at participating facilities nationwide, retrieves the C-CDA documents and converts them to FHIR.
Network:Nationwide exchangesTEFCA IAS→