For developers
TEFCA access for your app, without becoming a QHIN.
Apps can use Flexpa's request-only TEFCA Individual Access Services to retrieve records patients authorize from participating facilities. Users verify their identity through Flexpa Consent, and apps retrieve available records through the Flexpa FHIR API. Results depend on network participation and matching records.
Updated 2026-11-11
How it works
- Identity verification
- Participating TEFCA facilities
- Available records
How it works
Flow
- 1Launch Flexpa Consent with identity verification.
- 2The user verifies with CLEAR, ID.me, or Persona.
- 3Flexpa searches participating facilities; some ask the user to sign in to a portal.
- 4Query records with the patient access token.
Good to know
Access depends on network participation, eligibility requirements, and applicable exceptions. Flexpa does not provide bidirectional TEFCA services.
Questions
How can an app use TEFCA Individual Access Services?
An app can integrate Flexpa Consent for patient identity verification and authorization, then use a patient access token to query available TEFCA records through the Flexpa FHIR API. Flexpa provides request-only IAS, not bidirectional TEFCA sharing.
Do users need to verify identity?
Yes. Flexpa's TEFCA identity verification flow meets IAL2 and offers CLEAR, ID.me, or Persona. Some facilities also require a separate portal sign-in.