⚖️ Learn how MedicalEase finds the providers personal injury clients forget to mention →

For companies

Patient-controlled data sharing, built into your product.

Patient-controlled sharing lets a person authorize which supported record sources to connect and which app receives the returned data. Flexpa Consent provides that flow: source sign-in or identity verification, review of connected sources, and a final sharing step. The authorization scope depends on the source; some employer-plan connections include other members' information.

Updated 2026-11-11

How it works

  1. Choose sources
    find supported connections
  2. Authorize
    sign in or verify identity
  3. Review and share
    finish the Consent flow
  4. Receiving app
    access authorized records
Review the source's sharing scope before finishing. Revoking Flexpa access does not remove data already received by the app.

What the patient sees

The Consent flow

  1. 1A welcome screen that names your app and explains that Flexpa never sells personal information and that access can be revoked at any time.
  2. 2Either a search for their health plan or provider, or identity verification with CLEAR, ID.me, or Persona that searches the national exchange.
  3. 3Source-specific sign-in and authorization where required; some exchange results connect after identity verification.
  4. 4A review of connected sources, then a final step to share the returned records with your app.

Built for

Wearables and consumer health
Ground sleep, heart-rate, and activity signals in the patient's diagnoses, labs, medications, and encounters.
Labs and diagnostics
Request consented access to available prior results and history for your product.
AI agents
Give agents access to query consented records through Flexpa's records MCP server.

Control stays with the patient

Patients can request revocation and deletion at privacy.flexpa.com. Flexpa's guide specifies deletion and app disconnection within 45 days, with legal and audit retention exceptions. A receiving app must separately manage the copies it already received under its own policies and applicable obligations.

Flexpa is a request-only TEFCA IAS provider: patients can request their records through TEFCA, and Flexpa does not share records with other TEFCA participants.

Questions

What is patient-controlled data sharing?

Patient-controlled data sharing lets a person authorize supported record sources and the receiving app. Flexpa Consent uses source sign-in or identity verification, followed by a final sharing step. Review each source's scope: some employer-plan authorizations include information about other plan members.

Which platforms let patients share their records with an app?

Flexpa Consent is a hosted flow that connects health insurers, EHR patient portals, and TEFCA Individual Access Services, and returns standardized FHIR records to your app with the patient's consent.

How is the patient's identity verified?

Flexpa Consent uses the connected source's authentication flow, or IAL2 identity proofing through the offered verification provider for national exchange access. IAL2 is the identity verification level used by that exchange flow, not a requirement to repeat verification for every portal connection.

Can patients revoke access?

Patients can request revocation through privacy.flexpa.com or privacy@flexpa.com. Flexpa's guide specifies data deletion and app disconnection within 45 days, with legal and audit retention exceptions. Revocation does not delete data an app already received.

More

See the flow your patients see. Run the demo.

A real Flexpa Consent session against sandbox sources.

Try the interactive demo