SpotlightProprietary network connections

Reach the employer plans your users actually have.

Federal rules require Patient Access APIs for Medicare, Medicare Advantage and Medicaid. Flexpa's direct patient portal integrations reach employer-sponsored and off-exchange commercial plans that are not required to have one.

Included from Omni · $10,000/year on lower plans · Read the docs

Patient Access API
  • Medicare
  • Medicare Advantage
  • Medicaid
With the add-on
  • + Employer-sponsored plans
  • + Off-exchange commercial plans

01The short answer

What are proprietary network connections?

The CMS Interoperability and Patient Access rule (CMS-9115-F) requires insurers to offer a Patient Access API for their Medicare, Medicare Advantage and Medicaid members. Employer-sponsored and off-exchange commercial plans are not required to, so many of them have no API to connect through.

Flexpa's proprietary network connections are direct integrations with insurer patient portals that retrieve claims data for those plans. Flexpa Consent decides whether to send a patient to a Patient Access API or a portal integration, so your integration does not change.

02How it works

From connection to result

  1. 1

    The patient finds their plan

    They search for their insurer in Flexpa Consent, exactly as they would for any other plan.

  2. 2

    Consent picks the route

    Consent sends the patient to a Patient Access API where one applies, and to a portal integration where it does not.

  3. 3

    The patient signs in

    A subscriber or delegate login retrieves data for every dependent on the plan. A dependent’s login retrieves only their own.

  4. 4

    Data arrives through the same API

    Each member becomes a separate Patient resource, read through the FHIR API you already use.

Iterate over every patient in an authorization
# One authorization can hold several plan members
GET /fhir/Patient

# Everything for every patient in the authorization
GET /fhir/Patient/$everything

Good to know

  • Coverage varies by plan. Ask us about the plans your users have.
  • Commercial claims outside CMS-9115-F may not include diagnosis codes or allergies, and notes and labs are limited. CPT codes are still available on each claim line.
  • One authorization can return several Patient resources, so iterate over /fhir/Patient instead of assuming one patient.

03Who it's for

Where it pays off

Benefits navigation

Benefits work lives on employer coverage. Reach the plans your members are actually on.

See benefits navigation

HSA and FSA administration

Validate expenses against adjudicated claims for members on commercial plans.

Read the guide

Health apps and devices

Many of your users get coverage through work. Connect them too, not only members of government plans.

See health apps and devices

Plans

Included in Omni and above

Proprietary network connections is included in the Omni and Infrastructure plans. On Startup, Growth and Scale, it is $10,000 a year.

04A few good questions

Proprietary network connections,
answered.

Does our integration change?

No. Consent handles the routing and the data arrives through the same FHIR API.

Which plans does it cover?

Employer-sponsored and off-exchange commercial plans that are not required to offer a Patient Access API. Coverage varies by plan, so tell us which plans matter to you.

What data comes back?

Claims history. Commercial claims may not include diagnosis codes or allergies, and notes and labs are limited, but procedure codes are available.

What about dependents?

When a subscriber or delegate signs in, Flexpa retrieves every dependent on the plan as a separate Patient resource.

Which Flexpa plans include Proprietary network connections?

Proprietary network connections is included in the Omni and Infrastructure plans. On Startup, Growth and Scale, it is $10,000 a year.

Cover the plans your users are on.

Tell us which plans matter to you and we will show you what connects.

Get a demo