Opala’s Patient Access API enables third-party app developers to create applications that can be used by patients and healthcare organizations to access meaningful medical data. After a developer registers an application, it can be downloaded from Opala's App Gallery.
Opala’s API provides a robust Master Patient Index, OAuth 2.0 security, a cloud-based data repository, and access to FHIR-based resources.
For members, this feature enables them to initiate the transfer of healthcare information from a previous payer to their current payer. The member enters their information on Opala's white-labeled Health Data Transfer page, then logs into their account with the previous payer. For a payer's data to be available for members to transfer, the payer must be registered with Opala. If a payer is not registered, the member can request registration from this page.
For payers, this feature enables them to register as a payer administrator with Opala. Once Opala approves the registration, the payer’s connection details can be applied in our Payer-to-Payer Exchange or incorporated into your payer application for member access to our API.
Please note that the Developer Portal is accessed by both the developer and the payer administrator. Both developers and administrators can use the Developer Portal to access their Sandbox settings. Developers can also use the portal to register their applications with Opala, while payer administrators can register as a client to get access to Opala’s payer-to-payer exchange.
The Provider Directory is a publicly accessible API that does not require any registration or authorization to access. It conforms to the HL7 FHIR Da Vinci PDex Plan Net IG.
This is the base URL of the Provider Directory FHIR server:
If you have any questions, contact us at (206) 902-3380 or email@example.com.
Opala assumes that any developer working with the Patient Access API is familiar with the HL7 FHIR Release 4 specification. If a developer is not familiar with FHIR Release 4, or needs to look up something pertaining to a resource, each topic in the documentation set for the Opala APIs contains links to the relevant sections of the FHIR specification.
If you are ready to begin working with Opala's APIs, you must first:
1. Create an account with Opala.
2. Register one or more applications.
On the Opala Developer Portal
Once you have created an account, you can register one or more applications that will, after approval, be available in Opala's App Gallery.
Applications that have been registered with Opala are displayed on your page on the Developer Portal. Apps that have been registered, but not approved are listed as In Review. Approved applications are listed as Live and are available for members in the Applications Gallery.
If an application is not approved, you can revise and re-submit the app for review and approval.