The Opala Solution

Working with Accounts

Creating an Opala Account Registering as a Developer with Opala Working with Your Profile

Third-Party Application
  Management

Registering an Application Maintaining an Application Register a New Version of an Application

Payer-to-Payer Data
  Exchange

Registering as a Payer with Opala Transferring Member Health Information Registering Your Organization with Opala
Application Gallery

FHIR at Opala

FHIR for CMS Interoperability
Opala's FHIR Servers
FHIR Server Availability Checking Availibility FHIR Server Security
CMS Implementation Guides

Working with Opala's
  APIs

Using Opala's Sandbox & Production Environments API Queries Setting Up Postman Setting Up Production API Access Using Bundles with Opala's APIs Response Pagination

Opala's API
  Documentation

The Opala Patient Access API The Opala Provider Directory The Opala Member Attribution (ATR)
Release Notes

© 2021-2023 Opala. All Rights Reserved.

Version 1.0.1.0


Contact Opala's
Documentation Team

Opala's FHIR Servers

FHIR Server Availability

Opala's production API environments are available 24 hours per day, 7 days per week, 365 days per year (excluding scheduled maintenance downtime).

Opala's Production and Sandbox servers can be accessed at the following URLs.

API Environment Base URL Notes
Patient Access API Production https://api.opalahealth.io:45000/v1/fhir/r4/  
Patient Access API Sandbox https://api.opalahealth.io:45000/v2/fhir/r4/  
Member Attribution (ATR) Production https://api.opalahealth.io:45000/atr/v1/fhir/r4  
Member Attribution (ATR) Sandbox https://api.opalahealth.io:45000/atr/v2/fhir/r4  
Member Attribution (ATR) Sandbox https://api.in.opalahealth.io:46000/v2/fhirsbin/r4 FHIR ATR API Sandbox
Member Attribution (ATR) Sandbox https://api.opalahealth.io:45000/v3/oauth/op/oauth/authorize FHIR ATR API Sandbox Authorization
Provider Directory Production https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4  

Uptime

Response Time

Opala's API environments have a "real time" response time of no greater than five seconds, with no fewer than 50% of users having a response time under five sections. Real time FHIR API call response times are measured from the moment an API call hits Opala's external endpoint to the moment a response leaves Opala's datacenter, excluding situations where the response time of a provider's IT system exceeds two seconds.

Checking Availibility

If you want to regularly ping Opala's FHIR server to check on availability, use the metadata endpoint:

https://api.opalahealth.io:45000/v2/fhir/r4/metadata

This endpoint provides the CapabilityStatement resource from the FHIR server. If you see the CapabilityStatenebt it means that connectivity between the FHIR server and its underlying data store is active and working.

FHIR Server Security

Opala's FHIR server is secured using OAuth 2.0 credentials. Access to any FHIR API will require client authentication and authorization. Health plan members or their delegates will only have access to their own data.

If the key and secret presented are correct, the server returns an access token. This access token is then included on every FHIR API request, submitted in the Authorization HTTP header.

Separate credentials are issued for the test environment and the production environment.

Top