Note: Release notes are snapshots in time. Some features mentioned may have since been retired, deprecated, moved, or updated, and certain links may no longer be active.
The March 2023 release from Opala includes the following:
Release: Enterprise 2023.1.2.1
Opala has updated the endpoint to it’s Provider Directory metadata (Capability Statement). The new metadata endpoint is:
https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4/metadata
When you access this endpoint, Opala returns our Capability Statement in the form of a web page.
Release: Enterprise 2023.1.4.0
ETL deployed Evolent member (Patient) and Coverage resources to the Prod environment.
Release: Enterprise 2023.1.4.5
The Dominion Dental ETL processor for ExplanationOfBenefit, Organization, and Practitioner has been deployed to Opala’s main FHIR repository.
Release: Enterprise 2023.1.4.3
The AIM ETL processor for Questionnaire, QuestionnaireResponse, Condition, and Procedure has been deployed to Opala’s main FHIR repository.
Release: Enterprise 2023.1.3.0
The CVS Caremark Pharmacy claims data for ExplanationOfBenefit, Organization, and Practitioner have been deployed to Opala’s main FHIR repository.
The February 2023 release from Opala includes the following:
Release: Enterprise 2023.1.1.2
Practitioner and Organization historical data has been uploaded to Opala’s Production environement. This information will be accessible using historical EOBs (upcoming enhancement).
Release: Enterprise 2023.1.2.1
The Payer-to-Payer environment for Advantasure has been upgraded to .NET6 in order to enhance security.
Release: Enterprise 2023.1.3.0
The following resources have been uploaded to Opala’s production environement for use by Advantasure:
Release: Enterprise 2023.1.2.1
The base URL for for Opala’s Provider Directory endpoint has been updated to:
https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4/
Release: Enterprise 2023.1.2.1
Opala is now hosting a dedicated FHIR repository for ATR to manage ATR groups in value-based contracts.
The January 2023 release from Opala includes the following resolved issues:
Opala has updated the IDP XML file in the P2P Evolent Web Application and made that XML available. With this build, a new IDP file is available in the Production environment to authenticate SAML responses.
Providers are now being properly imported into Opala’s databases. Previously, a problem with the import response code prevented providers from being properly imported.