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 June 2023 release from Opala includes the following:
Release: Enterprise2023.2.6.0
Opala has added an additional attribute to the Member Eligib table. This attribute supports the Plan Name field for Providence and Multicare customers.
Release: Enterprise2023.2.6.2
Opala has removed records with missing member IDs and Link IDs, and removed records with duplicate Link IDs.
Release: Enterprise2023.2.8.0
Opala has added the member_sex column to the CMT roster. This column was from the previous version of the roster.
Release: Enterprise2023.2.7.0
To support compliance with the CMS mandate and its consent requirements for the Patient Access API, Opala is now able to capture and audit users’ consent to third-party applications and registration policies.
Release: Enterprise2023.2.8.0
Opala has added new schemas, data pipelines, and configuration settings to support the Navitus Formulary.
The May 2023 release from Opala includes the following:
Release: Enterprise2023.2.4.1
When a user queries the Patient Access API for the EOB resource using payer administrator credentials, no financial information is returned with the EOBs. Financial information is only included in the EOBs when the Patient Access API is queried using developer or business credentials.
The April 2023 release from Opala includes the following:
New Features for Developers
Resolved Issues
Release: Enterprise2023.2.1.0
Opala’s Data Exchange Importer (DEI) now supports ESI data, Providence data, and ATR Group data.
Release: Enterprise2023.2.2.3
Opala is changing the Patient Access API refresh token validity from 1 hour to 90 days.
Release: Enterprise2023.1.5.2
For a member of the Providence ATR Group (uniroster) whose coverage has expired, that member will still be included in ATR groups. Previously, members in the Providence ATR Group whose coverage expired were not populated in ATR groups which meant Providence’s FHIR API could not receive clinical data for these members.
Release: Enterprise2023.2.2.1
Opala has updated its SQL query in the CMT processor to handle bad data creation in the output script. Previously, commas in the Address 1 field caused the creation of the bad data.
Release: Enterprise2023.2.2.1
Opala has deployed fixes for Evolent IDP as well upgrading the Evolent container from .NET 5 to .NET6 to address a security vulnerability. This fix also addresses the payer-to-payer data transfer for Florida Blue and Evolent.
Release: Enterprise2023.2.2.4
Opala has updated the Evolent certificate in the PROD environment which should resolve Health Data page error in the Production environment. This update affects health data transfers for Florida Blue and Evolent for the Payer-to-Payer feature.
Release: Enterprise2023.2.3.1
Opala has updated its Uniroster to handle missing Bluecard subscriber IDs. There are over 8300 missing Bluecard subscriber IDs.
Release: Enterprise2023.2.3.2
Opala has corrected an issue with the Uniroster ETL DB load of member attribution data. A previous update added the contract name to the primary key but was not reflected in the query used to update the attribution data (only the run date (run_dt) was changed). As a result, several members were over-attributed to groups since the query run was based on the prior definition of an ATR group that did not include the contract name.