Contact Us

Kickstart Your Integration Journey

Everything you need to test, connect, and launch with confidence

Getting Started

Developers

Developers can integrate with Opala’s APIs to build applications that access electronic health data using the HL7® FHIR® standard. Our RESTful APIs support Patient Access, Provider Directory, Member Attribution (ATR), and more—enabling secure, standards-based interaction with clinical and claims data.

All APIs are fully FHIR-compliant and provide rich programmatic access to EMR data for healthcare organizations, payers, and developers. The Opala platform is HIPAA-compliant, ensuring data privacy and security throughout.

Designed with scalability and interoperability in mind, Opala’s APIs help accelerate development timelines while supporting compliance and data integrity across healthcare ecosystems.

Payers

CMS-regulated payers are required to exchange certain patient clinical data (specifically the USCDI v1 data set) at a patient’s request—during coverage or up to five years after it ends. To support this, payers register with Opala to enable secure data exchange between previous and current payers.

Once registered, Opala facilitates the connection and transfer of member data through registered third-party applications, payer portals, and payer-to-payer exchanges. This ensures compliance with CMS mandates while streamlining data portability for members switching plans.

Opala’s platform simplifies the technical and regulatory complexity of payer-to-payer data exchange, helping organizations meet interoperability requirements with confidence and efficiency.

CMS Implementation Guides

Opala develops its APIs in alignment with CMS Implementation Guides to ensure compliance with federal interoperability mandates. These guides provide the technical and regulatory framework for exchanging healthcare data securely and consistently across systems.

Learn about CMS IG's

Application Gallery

The Application Gallery is where third-party applications that have been registered and approved are made available to the public. They are available for members to download and use to access their personal health information.  Learn More About Our Application Gallery.

Launch The Developer Portal

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 the Patient Access API, visit the Opala Developer Portal to start registration of your application(s).

Developer Portal Note

The Developer Portal supports registration by both app developers and payer administrators. Developers can 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.

Register Your App With Opala

As a 3rd party app developer or a Payer you must register your application in order to access Opala’s Patient Access API. Upon approval, the application will be enabled to interact with the API and connection information will be securely provided to you. 3rd party apps will be featured in Opala’s App Gallery.

Register your App

Access The API Documentation

Opala publishes standard discovery endpoints for the Patient Access API to make integration easier. These documents describe supported resources, security configuration, and capabilities.

If you have any questions, contact us at (206) 902-3380 or developersupport@opala.com.