Overview for Developers

Before you can connect your apps to the 1upHealth FHIR Server to send and receive health data, you update your applications to support FHIR R4. We recommend that you allow two to four weeks to modify your applications to support FHIR R4 and new data types. You must also demonstrate support for FHIR R4 and provide details about your application (such as a logo, description, and links) before it can be made available to members of the supported health plans.

FHIR R4 is designed for all future versions to be backward compatible with all R4 components. This makes it a stable version that provides more access to data, and allows you to dedicate more time to patients.

Adoption of R4 creates a true standard and is another important step towards true FHIR interoperability. FHIR R4 builds on DSTU2 and STU3. With FHIR R4, you can get access to a patient’s clinical data through the 1upHealth FHIR API platform.

Authorization & Connection Requirements

Before you can connect your application to the 1up Payer Patient Access APIs you must support one of the following authorization methods.

OAuth 2.0 Preferred

Use the authorization_code workflow to connect to a payer's /authorize endpoint.

You must have your client ID and configure a redirect.

(Optional) You can also state parameters and scopes.
OpenID Connect (OIDC) Optional Supported for FHIR R4

To connect to the 1up Payer Patient Access APIs, you must use FHIR R4 APIs.

Supported FHIR Version & FHIR Resources

The supported FHIR resources vary depending on the payer. Some payers support only resources related to claims and coverage. Other payers also support clinical resources.

Payer Patient Access endpoints support only FHIR R4.

You can use most of the common CMS R4 resources to expand the amount of data you’re able to query. This includes the following resources:

  • ExplanationOfBenefit

  • Coverage

  • Organization

  • Patient

  • Practitioner

  • Location

Supported Scopes

1upHealth supports the following scopes for patient access.

  • patient/*.read — Get access to all of the available FHIR resources for the authenticated member

  • openid — Get an ID token that meets the OpenID Connect standard requirements