The Opala Solution
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)

Release Notes

© 2021 - 2023 Opala. All Rights Reserved.

Version 1.0.2.0


Contact Opala's
Documentation Team

Setting Up Production API Access

For a Payer

After you've completed sandbox setup and successfully accessed sandbox FHIR resources, you'll be eligible for Production API access. To access the Production API, you will need to register with Opala. This registration creates a client (App). Once Opala approves your registration, you will see connection details that can be applied in our Payer-to-Payer Exchange or incorporated into your Payer application for member access to our API.

See Registering as a Payer with Opala for instructions on creating a Payer Administrator account and registering with Opala.

  1. Open the Opala Developer Portal page and select the Get Started button.
  2. On the sign-in page, enter your username and password to log in to your account.

    Note: You must go to the login page from the main Developer Portal page to log in. If you bookmark the login page and try to sign in directly from that (without going through the Developer Portal) you will receive an error.

  3. On the Developer Portal page, select the +Register Button button.
    This opens the registration wizard, enabling you to register with Opala.

    Note: You are not registering an application but instead are registering as a client. The registration you create here does not appear in the App Gallery.

  4. On the following three pages you will be prompted to enter the necessary set up information. To begin, in the App Name field enter the name you would like to give your registration, then select the Next button.
  5. Enter your company's homepage, privacy policy, and terms of service URLs; and the OIDC Redirect URLs.
  6. Review the legal attestation and either accept or decline adherence to the terms, then select the Submit button. The attestation describes the minimum privacy and security criteria necessary to sufficiently protect patients' protected health information in accordance with the CMS and ONC.
  7. You registration will be In Review until an Opala Administrator reviews and approves it. In the meantime, you can select, view, and edit your registration.
  8. Once the registration is approved, an email notification is sent to the email address supplied in the account creation process. The registration status is Live.
    Once your registration is promoted to Live, more details are presented in the Connection tab of the registration. Just select the registration to open the tabs.

For a Developer

When you initially register an application with Opala, the application you register is listed on your developer page with a status of In Review.

Production access is granted after validating your application. Prior to this, your application is listed as In Review on your Developer Portal page; you are still able to access Opala's Patient Access API Sandbox prior to having your application approved but you cannot access the Production Environment. Once your application is approved and the status changes from In Review to Live, you are granted access to the Production environment.

The first time you log into the Production environment, you must agree to all disclaimers presented on the login page. Select each disclaimer, then click either the I Understand or I Agree button.

Agree to All Disclaimers

In addition to status change, any changes to the application are recorded, as are any messages submitted by the reviewer, the date the entry was modified, the version of the application, and the date the application was submitted for review.

Top