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

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

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

Application Gallery
FHIR for CMS Interoperability Opala's FHIR Servers CMS Implementation Guides

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

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

Release Notes

© 2021-2023 Opala. All Rights Reserved.

Version 1.1.2.0


The Opala Solution

Opala is a hosted Software as a Service (SAAS) solution. Opala deploys critical knowledge to support direct, dynamic care coordination. There is no unmediated consumer/patient/client use of Opala's service; instead, third-party applications who register with Opala can integrate Opala's APIs into their mobile solution(s) to deliver on-demand data to individual consumers/patients/clients. These individuals view Opala's data from within the registered third-party application that they have downloaded onto their mobile device.

Opala does not currently have any application offerings.

The Final Rule

In 2020, the Centers for Medicare & Medicaid Services (CMS) published rules primarily designed to make healthcare information accessible, via an application programming interface (API), to individuals covered by a government healthcare program (e.g., Medicare Advantage). The CMS Interoperability and Patient Access final rule governs how these APIs are required to work.

HL7® FHIR®

The HL7® FHIR® (Fast Healthcare Interoperability Resources) specification defines how healthcare information can be exchanged between different computer systems regardless of how it is stored in those systems. It is designed to support providing healthcare in a wide variety of settings by enabling information exchange. FHIR is a standard for exchanging healthcare information electronically. The FHIR specification builds on and adapts widely used RESTful practices to enable integrated healthcare across a wide range of teams and organizations.

The intended scope of FHIR is broad: human and veterinary needs, public health, clinical care, clinical trials, and administration and financial aspects of healthcare. The standard is intended for use in a wide variety of architectures and scenarios.

The documentation for these APIs assumes that you are familiar with the HL7 FHIR Release 4 specification. If you are not, each endpoint topic in the documentation contains links to the referenced sections of the FHIR specification.

Opala's Interoperability Solutions

Opala's Developer Documentation Set enables you to access documentation for Opala's FHIR® APIs. Opala provides four seperate solutions you can use to access data.

Opala's APIs are based on the HL7 Fast Healthcare Interoperability Resources (FHIR) standards and use the OAuth 2.0/Open ID connect standard for member authentication and authorization.

SLA Summary for Opala's APIs

The uptime Service Level Agreement for Opala's production and test APIs is 99.9%, excluding scheduled downtime, measured monthly.

The average API call response time is no greater than five (5) seconds (i.e., no less than 50% of users should get a response time under five (5) seconds) measured daily, calculated and reported monthly to the customer, and also measured by the provider daily for its own information.

The average API end-to-end response time is no greater than five (5) seconds (i.e., no less than 90% of users should get an end-to-end response time under five (5) seconds) measured daily, calculated and reported monthly to the customer, and measured by the provider daily for its own information. API end-to-end response times measures shall exclude times from third-party systems other than those third-party services provided by the provider's subcontractors.

The Opala API Documentation

Opala provides documentation for both its Patient Access and Provider Directory APIs. Use the links below to access this documentation.

The Opala URLs

Opala uses the following URLs.

API Environment Base URL Notes
APIs
Patient Access API Production https://api.opalahealth.io:45000/v1/fhir/r4/  
Patient Access API Sandbox https://api.opalahealth.io:45000/v2/fhirsb/r4/  
Member Attribution (ATR) API Production https://api.opalahealth.io:45000/atr/v1/fhir/r4  
Member Attribution (ATR) API Sandbox https://api.opalahealth.io:45000/atr/v2/fhir/r4  
Member Attribution (ATR) API Sandbox https://api.in.opalahealth.io:46000/v2/fhirsbin/r4 FHIR ATR API Sandbox
Member Attribution (ATR) API Sandbox https://api.opalahealth.io:45000/v3/oauth/op/oauth/authorize FHIR ATR API Sandbox Authorization
Provider Directory API Production https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4  
Metadata
Patient Access API Production https://api.opalahealth.io:45000/v2/fhir/r4/metadata FHIR API public metadata
Patient Access API Production https://api.opalahealth.io:45000/v2/fhir/r4/.well-known/smart-configuration Security SMART App Launch configuration
Member Attribution (ATR) API Production https://api.opalahealth.io:45000/atr/v1/fhir/r4/metadata ATR API public metadata
Member Attribution (ATR) API Production https://api.opalahealth.io:45000/atr/v1/fhir/r4/.well-known/smart-configuration Security SMART App Launch configuration
Provider Directory API Production https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4/metadata Provider Directory API public metadata
Portals
Developer Portal   https://api.opalahealth.io:45000/v1/apps/portal/#/login  
Member Portal (MA)   https://p2p.opalahealth.io:45007/  
Member Portal (AK)   https://p2p.opalahealth.io:45006/  
Application Gallery   https://api.opalahealth.io:45000/v1/apps/gallery/  
Opala endpoint used to monitor new application requests:   https://newapprequestapi.int.op:11001/AppRequest/AppRequestHealth  
Documentation
Open API Docs   https://api.opalahealth.io:45000/v1/fhir/r4/api-docs  
API Documentation   https://docs.opalahealth.io:59059/  

Documentation Feedback

Opala welcomes your input about its documentation. If you have any thoughts, comments, or suggestions about any topic, you can email the Documentation Department at feedback@opala.com by clicking the link in the upper right of any page.

Top