For developers

Supported EHR patient APIs, one integration.

Flexpa connects apps to supported electronic health record (EHR) systems through patient authorization. A user selects a supported facility and signs in to its patient portal through Flexpa Consent. Your app then retrieves available FHIR records through the Flexpa API.

Updated 2026-11-11

How it works

  1. Supported facility
  2. Portal authorization
  3. Available FHIR records
EHR records depend on the facility the patient authorizes.

What comes back

  • US Core resources such as Condition, Observation, MedicationRequest, AllergyIntolerance, Immunization, Procedure, Encounter, and DocumentReference.
  • CDA documents where the source provides them.

Good to know

For a child's records, the parent or guardian needs proxy access enabled by the facility before connecting. Each child requires a separate Flexpa authorization, and availability depends on the facility's proxy rules.

Questions

How do I connect an app to EHR patient data?

Use Flexpa Consent to let a user select a supported facility and authorize access through its patient portal. Your app can then query available records with a patient access token through the Flexpa FHIR API.

Which clinical records can Flexpa return?

Depending on the connected source, Flexpa can return FHIR resources for conditions, observations, medications, allergies, immunizations, procedures, encounters, and documents. Availability varies by facility.

More

Connect EHRs. Try the demo.

Includes a sandbox EHR source.

Try the interactive demo