The revoke endpoint of the Flexpa API now invalidates all authorizations that a patient had previously made to an application. Read more about these details on the revoke section of the Flexpa API documentation.
Flexpa's API now works behind the scenes to standardize code system URIs in FHIR responses.
We've added a page that references which code system URIs developers can expect to see in FHIR payloads.
While MyFlexpa has existed for a long time, our documentation on its value and use for patients and developers have not.
We've added a page that details how to best use this tool alongside other Flexpa offerings.
We've added a new way to use our docs: FlexpaGPT. Ask questions about Flexpa and get back responses instantly.
- A button displayed on the bottom right of the page that will open up a chat window
- Ask questions about Flexpa and get answers instantly
- FlexpaGPT links to relevant documentation, code snippets, and more
We've added an indicator to the Flexpa Link endpoint selection screen to notify patients when an endpoint connection is unstable.
- The indicator will display as a message in red above the affected endpoint's label
- This enhancement improves the patient experience by increasing their awareness of known endpoint issues and encouraging them to retry later
Flexpa Link now displays health plan logos in the selection screen. This update should improve plan recognition and help patients identify their health plan correctly.
We've updated the styling of the health plan selection screen in Flexpa Link for better usability. This new design removes the coloured backgrounds to improve the contrast ratio and provide a more consistent experience.
We also have updated our health plan search to more robustly identify the plans a patient may be searching for. This includes fuzzy matching on searches and searching across applicable brand names a payer may use.
The exchange endpoint of the Flexpa API now returns additional metadata about the health plan (Endpoint) a patient has used to authorize your application.
This metadata includes attributes such as the Endpoint name, whether or not the authorization is refreshable, and a list of FHIR Resources available for this Endpoint.
Read more about these details on the exchange section of the Flexpa API documentation.
Flexpa Link (0.0.10) now supports
onLoad callback functions passed to
onExit is called when the user exits the authorization flow without succesfully authorizing
onLoad is called when Link is loaded and ready to be used
We have released Flexpa Connections, an application that lets patients manage their health plan authorizations.
- Patients can log in with their health plan and view a history of applications they've connected through Flexpa Link
- Patients can disconnect apps they no longer want their health plans connected to and reconnect them anytime through Flexpa Link
- Check out the Flexpa Connections documentation for more information
After user testing and customer feedback, we have removed all minimums from our Basic plan. This pure usage-based pricing should allow early testing and onboarding, aligning value with predictable cost. Check out additional details here.
The introspect endpoint of the Flexpa API now returns additional metadata about the specific endpoint associated with the access token you are using. Read more about these details on the introspect section of the Flexpa API documentation.
Flexpa Link (0.0.8) now supports the option to skip the health plan search / select step in our authorization flow.
This supports an improved UX flow in cases where a patient's health plan is known to the application implementing Flexpa Link prior to starting the authorization.
Patient access tokens created with Flexpa Link now have support for a refresh mechanism. Refreshing a patient access token allows your application to make requests after the original one has expired.
- Where possible, Flexpa obtains an
offline_access scope and exposes a refresh route
- Refreshing a patient access token will invalidate the previous patient access token and return a new one
Note that not all patient access tokens support refreshing. Major payer support includes Kaiser Permanente, Cigna, Humana, UnitedHealth, and Anthem.
We are launching a small guide on basic data analysis with FHIR bundles you get from Flexpa API.
- This guide explains how to go from raw FHIR bundles from Flexpa API, and transform them into structured tables that conform to Tuva's data model
- We've co-developed a FHIR parser with Tuva that converts FHIR bundles into database-ready CSVs for structured analysis
We are launching pagination support to simplify accessing FHIR Resource search results.
- Developers can pass the query parameter
_count into search requests and use the returned
link object to access the paginated results
- More information about pagination is available on the API reference page
We are launching the Flexpa Portal, a new way for developers to manage their Flexpa account.
- This new option allows for developers to create an account, generate API keys, and invite other members of their organization to collaborate.
- Our portal can be accessed here
We are launching the ability to customize the appearance of Flexpa Link with the
customLinkConfig configuration object.
- This new configuration object provides a way to configure Flexpa Link to match implementers' UI/UX more closely
- Initially supporting four
- Instructions on implementation available here
We are launching the new patient access guide and FHIR Resource reference pages.
- The newly updated patient access guide provides a background on Patient Access APIs and the data they make available
- The FHIR Resource pages provide sample request and response data for FHIR Resources (ex. Coverage) that can be accessed using Flexpa API
We are launching the Wildcard Parameters feature in Flexpa API. This allows you to reference real values provided by the Patient Access Token in each request.
The first parameter we are supporting is
$PATIENT_ID, allowing you to use the currently authorized
patient_id in each request without having to know what it is.
- Removes the
patient_id as a field in the response of
- Updates FHIR Server to accept Wildcard Parameter,
GET /fhir/Patient/$PATIENT_ID -H "Authorization: $ACCESS_TOKEN"
GET /fhir/Coverage?patient=$PATIENT_ID&_count=5 -H "Authorization: $ACCESS_TOKEN"
GET /fhir/ExplanationOfBenefit?patient=$PATIENT_ID -H "Authorization: $ACCESS_TOKEN"
Note: Using the introspect endpoint and sending the actual
patient_id will also continue to work.
We are launching the NodeJS-based Quickstart repository and accompanying guide.
- The Quickstart Github repository is a cloneable project to help you get started with Flexpa in just a few steps
- The Quickstart guide walks through how to build and run Flexpa's quickstart example
We are launching Flexpa Link and Flexpa API, including our major feature release of self-service test mode API keys.
- Flexpa Link is a client-side component to help your users link health plan data sources
- Flexpa API is a unified HL7 FHIR API (HTTP + JSON) to access health plan, claims, and clinical data