Premera Blue Cross logo
Sign in
Go to the Alaska website

Developers

Decorative image

Develop with us

Integrate with Premera developer resources like APIs and machine-readable files to build and offer better user experiences.

Premera has adopted and developed standardized data formats and APIs to support developers building digital applications who want to integrate with the Premera ecosystem. The information on this page is intended for developers who build apps and mobile interfaces.

Documentation and resources

Are you a health plan looking to enable Payer to Payer Data Exchange for your members? Please complete the patient access API developer registration process outlined below.

To meet and comply with The Centers for Medicare and Medicaid Services (CMS) interoperability requirements, we are providing these instructions for app developers. Here you’ll learn how to connect to and consume the Patient Access API and the ProviderDirectory API.

What’s interoperability? It is the way people can control which apps they allow (or deny) access to their personal and private health data.
Go to My Health Data

Need help? Contact developersupport@opala.com

Compliance and agreement to our Terms and Conditions is required to access and use interoperability APIs.

  • Patient Access API
  • Provider Directory API
  • Payer to Payer Data Exchange

To register with Opala (Premera's Interoperability partner) or to find more information on accessing API's regarding Patient Access API, please click on the link below:
Find more information on accessing API's

Overview

The Patient Access API is required to be protected by the OpenID Connect flow of the OAuth 2.0 specification. Before any development starts, you need several things to help set up the integration and access Patient Access API.

  1. Client ID and secret.
  2. URL to initiate the authorization workflow (which includes the user authentication step).
  3. A list of redirect URLs that the identity provider will accept.

Once the application is registered, it will be displayed on the publicly available Application Gallery where it can be downloaded from.

Assumption: Developers are familiar with FHIR and the CARIN for Blue Button® implementation guide

Overview

The provider directory is an open access API that doesn’t require a user account.

Make sure you’re familiar with the implementation guide for provider directory.

In the insurance world, providers sign contracts to participate in certain networks. These networks are then assigned to insurance policies that are sold to customers. Identifying providers that accept a given insurance policy requires traversing multipleFHIR elements.

The relationship between an insurance plan and a provider is as follows:
Insurance Plan > Network (represented by FHIR Organization resource) > PractitionerRole > Practitioner

Endpoints

Base URL: https://opala.tech/provdir/premera/v1/fhir-r4/

Examples

  • Find provider by name: https://opala.tech/provdir/premera/v1/fhir-r4/Practitioner?family=PETTINGER
  • Find hospital: https://opala.tech/provdir/premera/v1/fhir-r4/Organization?name=SOUND OXYGEN SERVICE INC
  • Find healthcare service: https://opala.tech/provdir/premera/v1/fhir-r4/HealthcareService?name=Apria Healthcare LLC