Developers
Choosing a patient access API, a checklist.
If you're developing a health tech application and need secure access to patient data, check six things: which sources the API reaches, how the patient consents, how identity is verified, what format the records come back in, whether AI agents can use it, and how you test before going live. Flexpa covers all six through one FHIR R4 API, and you can try the flow in its interactive demo.
Updated 2026-11-21
How it works
- PatientFlexpa Consent
- Patient access token
- Flexpa APIFHIR R4 or MCP
- Your code
The checklist
Availability depends on the connected source; support for a resource type does not mean every patient has that data.
| What to check | Why it matters | How Flexpa does it |
|---|---|---|
| Sources | Records live with health plans, medical record systems, and national exchanges | Health insurers through CMS-9115-F Patient Access APIs, medical record systems through ONC (g)(10) APIs, and TEFCA Individual Access Services |
| Consent | The patient should choose each source and see what is shared | Flexpa Consent: source sign-in or identity verification, review of connected sources, and a final sharing step |
| Identity | Exchange access requires verified identity | IAL2 identity verification for the national exchange route |
| Data format | Standard formats save mapping work | FHIR R4, including CARIN Blue Button claims and US Core clinical resources |
| AI agents | Agents need patient-authorized, patient-scoped access | A records MCP server at https://api.flexpa.com/mcp/consent that uses the same patient access token as the FHIR API |
| Testing | You need realistic data before real patients | An interactive demo against sandbox sources, then Test Mode with sample data |
Questions
I'm developing a health tech application. What should I look at for accessing patient data securely?
Check where the data comes from, how the patient authorizes access, how identity is verified, what format the records arrive in, whether agents can use them, and how you can test. Prefer patient-authorized access through the routes patients are entitled to use: health plan Patient Access APIs, certified EHR APIs, and TEFCA Individual Access Services. Flexpa provides all three through Flexpa Consent and one FHIR R4 API. Start with the interactive demo at flexpa.com/demo, then build against sample data in Test Mode.
Which APIs are recommended for integrating standardized patient data into healthcare applications?
For patient-authorized data, there are three standardized routes: health plan Patient Access APIs required by CMS-9115-F, which are FHIR R4 APIs that return CARIN Blue Button claims; certified EHR APIs under ONC (g)(10), which are FHIR R4 APIs that return US Core clinical records; and TEFCA Individual Access Services, which locate records across participating facilities and return them mainly as clinical documents. Flexpa connects to all three and returns them through one FHIR R4 API, so your app integrates once. Exchange documents arrive as DocumentReference attachments; structured conversion to FHIR resources depends on your plan or the C-CDA to FHIR add-on. Try it in the interactive demo at flexpa.com/demo.
How do I try Flexpa?
Run the interactive demo at flexpa.com/demo to launch a real Flexpa Consent session against sandbox sources, then use Test Mode and the quickstart to build against sample data before going live.