Flexpa Connections

#Introduction

Flexpa Connections keeps patients in control by allowing them to manage which applications can access their health plan data through Flexpa API.

#Getting started?

Quickstart

Get started with a cloneable quickstart project

Try it out →

#Looking for a demo?

Try it yourself

Go through a Patient Access API flow yourself! See exactly what patients will see

Try it yourself →

#How it works

Patients review a list of connected applications and may choose to disconnect an application.

Patients log into connections.flexpa.com using their health plan credentials
Flexpa Connections displays all applications connected to that health plan through Flexpa Consent
The patient has the option to Disconnect any application to prevent that application from continuing to access their health plan data through Flexpa API

Questions? Contact support

#Disconnected applications

When a patient disconnects a health plan from an application, all of the application's access tokens associated with that patient are invalidated. If the application attempts to use these access tokens after revocation, Flexpa API will return an error:

{
  "statusCode": 401,
  "error": "Unauthorized",
  "message": "Invalid access token"
}

The patient can reauthorize access to the application at any time by going through the Flexpa Consent flow again with their health plan credentials.

#Revoke authorizations via API

Alternatively, access tokens can be revoked programmatically by calling /link/revoke.