# TEFCA Individual Access Services API for Apps

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.

How it works: Identity verification -> Participating TEFCA facilities -> Available records. Flexpa provides request-only Individual Access Services, not bidirectional TEFCA exchange.

## How it works

### Flow

1. Launch Flexpa Consent with identity verification.
2. The user verifies with CLEAR, ID.me, or Persona.
3. Flexpa searches participating facilities; some ask the user to sign in to a portal.
4. Query 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.

## More

- [Network (docs)](https://www.flexpa.com/docs/network)
- [What TEFCA means for patients](https://www.flexpa.com/what-is-tefca-for-patients)
- [TEFCA (healthit.gov)](https://healthit.gov/policy/tefca/)
- [Flexpa TEFCA Individual Access Services (blog)](https://www.flexpa.com/blog/flexpa-is-a-tefca-ias-provider)

Last updated 2026-11-11.