Contact Opala's
Documentation Team

Release Notes: April 2023

Overview

The April 2023 release from Opala includes the following:

Developers

Data Exchange Importer Deployed to Prod

Release: Enterprise2023.2.1.0

Opala's Data Exchange Importer (DEI) now supports ESI data, Providence data, and ATR Group data.

Patient Access API Refresh Token Duration Extended

Release: Enterprise2023.2.2.3

Opala is changing the Patient Access API refresh token validity from 1 hour to 90 days.

Resolved Issues

Coverage for Providence ATR Groups

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.

Updated SQL Query for CMT/HeCAK

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.

Payer-to-Payer Fixes for Evolent Deployed

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.

Health Data Page Error Resolved

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.

Missing Bluecard Subscriber IDs in Coverage FHIR Resource

Release: Enterprise2023.2.3.1

Opala has updated its Uniroster to handle missing Bluecard subscriber IDs. There are over 8300 missing Bluecard subscriber IDs.

Member Attribution Data Issue Corrected

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.