2022 Q3 Release Notes
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.
Enterprise2022.3.1.11 Release
The 2022.3.1.11 release from Opala includes the following updates:
New Features for Developers
- Florida Blue now registered with Opala.
Resolved Issues
- Payer-to-Payer monitoring now working correctly.
Developers
Florida Blue Now Registered with Opala
Florida Blue has registered with Opala’s Payer-to-Payer Data Exchange program in the Production environment. Members who want to add payer information from Florida Blue to their heathcare data can now do so from Opala’s Health Data Transfer page by selecting Florida Blue from the Previous Insurer dropdown.
Resolved Issues
Payer-to-Payer Monitoring Now Working Correctly
Payer-to-Payer monitoring now returns a 200 when pinged. Previously, it returned a 302 redirect instead of the expected 200.
Enterprise2022.3.1.10 Release
The 2022.3.1.10 release from Opala includes the following updates:
New Security Features
- ZeOmega endpoint security modified.
Resolved Issues
- Internal Server Error corrected.
- UniRoster Attribution NPIs now loading correctly.
Security
ZeOmega Security Endpoint
The security endpoint for ZeOmega has been changed from basic auth to Oauth.
Resolved Issues
Evolent Payer-to-Payer Portal
The Payer-to-Payer Healthdata Portal for Evolent not points to the correct URL. Previously, the link pointed to the incorrect URL which was causing a 500 Internal Server Error.
UniRoster Attribution NPI
Three distinct NPI values were failing in the Production environment, which impacted ATR group processing. Opala now updates the metadata with these NPIs then runs the process, which results in the ATR Group being processed correctly.
Enterprise2022.3.1.7 Release
The 2022.3.1.7 release from Opala includes the following updates:
New Features for Developers
- UniRoster updated with two new fields.
- Medicare segment not applied in the UniRoster when no ID is present.
- Databricks R4 deployed.
Resolved Issues
- App Gallery URL on Advantasure P2P Portal corrected.
- NPI error handling for ATR Group creation.
Developers
UniRoster Updated
Two Additional Fields
The UniRoster file (member file) has been updated to include additional columns for County and HICN/MBI, which are mapped to the Patient FHIR resource. The new fields are:
HICN CHARACTER VARYING(50),MBR_HOME_ADDR_CNTY_NM CHARACTER VARYING(50),
Note: When the HICN is missing in the data, only country is mapped in the FHIR resource.
Medicare Segment
When no HICN value is included for a patient, the Medicare segment is not included in the Patient resource. Previously, the Medicare segment was applied even when no Medicare ID was included.
Databricks R4 Deployed
The Databricks R4 deployment to Opala’s production environment has been completed. The deployment consists of:
- Premera Provider Directory — Raw layer
- Operation Report View
- Smile CDR Transaction Data — This data pipeline ingests transaction log data to provide a source for operational reporting
- Updated Smile FHIR Endpoint
Resolved Issues
App Gallery URL on Advantasure P2P Portal
The correct App Gallery URL has been deployed to the Advantasure P2P Portal. Previously, the portal contained an incorrect App Gallery URL.
NPI Error Handling
NPI Error handling was failing in some situations for the Providers resource which impacted ATR Group creation.
Enterprise2022.3.1.5 Release
The 2022.3.1.5 release from Opala includes the following updates:
New Features for Developers
- Automation of ATR Group FHIR Resource (re)building.
Resolved Issues
- Final Premera logo.
- ATR Group FHIR Resource creation.
Developers
Automated ATR Group creation
Opala has automated the process of updating ATR Groups FHIR resources so that existing ATR Groups are removed and replaced by up-to-date data pulled from the latest source data.
Resolved Issues
Premera Logos Finalized
The Premera logo files have been finalized and deployed.
ATR Group FHIR Resource Processing
Providers with NPI numbers that have errors, are deactived, or do not have an NPI now process correctly. Previously, these Providers were not being processed and created errors causing ATR Group creation to fail.
Enterprise2022.3.1.3 Release
The 2022.3.1.3 release from Opala includes the following updates:
New Features for Developers
- Advantasure portal available.
- NPPES now called locally.
New Security Features
- External FHIR Endpoint security enhancement.
Resolved Issues
- Databricks hotfix.
Developers
Advantasure P2P Portal Available
Opala has re-deployed its Advantasure Payer-to-Payer Data Exchange portal enabling members to log in, and submit Payer registration requests or data transfer requests with registered Payers. (Payer registrations in progress.)
NPPES Now Called Locally
Opala’s ETL pipelines now pull NPI data from a local cache rather than from the NPPES national site.
Security
External FHIR Endpoint Security Enhancement
Basic Authorization against Opala’s external FHIR endpoint has been removed.
Resolved Issues
Databricks Hotfix
Opala rolled out this hotfix to respond to the issue of a missing component in the Databricks R3 release. This release fixes that problem.
Enterprise2022.3.0.11 Release
The 2022.3.0.11 release from Opala includes the following updates:
New Features for Developers
- Payer self-registration via Developer Portal functionality.
- Endpoint monitoring for Application Gallery Support website (New App Requests and Help Needed pages).
- Databricks Updated
New ETL Pipeline Features
- ZeOmega ETL updates.
New Security Features
- MultiCare Registration to use ATR API.
Developers
Payers Can Now Self-Register with Opala
To exchange data for former Premera members who are now on a different insurance plan, Opala must have the ability for payers to register with us. The process for registering payers is similar to the process for registering application developers.
On the Developer Portal, select the Get Started button and create a payer account.
Note: You can access the Developer Portal at https://api.opalahealth.io:45000/v1/apps/portal/#/login.
When you create your account, select Payer Administrator.
- On the next two pages, enter your demographic information and select the Submit button.
- In the My Registrations section of the Developer Portal, select the button.
Fill out the information on the Payer to Payer Registration pages.
- On the final page, accept the legal attestation then select the Submit button.
Endpoint Monitoring for New App Request
Opala has exposed an endpoint to be used to monitor the usage of the Opala custom website to support requests to add new applications to the App Gallery, or request help for any other reason. If the website is down or unavailable (the health check API returns anything other than 200), the endpoint sends a notification to Opala’s support team.
To ensure the API is up and running, this endpoint can be accessed without any authentication.
Databricks Updated
Databricks operational data has been updated to include the Job Log (audit.job_log and audit.task_log), File Movement, and CMT ADT Message Counts.
ETL Pipeline
ZeOmega ETL
The following is a list of data sources (i.e., files) processed and FHIR resources generated/updated:
| Incoming Files/Format | FHIR Resources | Status |
|---|---|---|
| Zeomega_MedicationRequest (ndjson) | MedicationRequest | Prod |
| Zeomega_Procedure (ndjson) | Procedure | Prod |
| Zeomega_CareTeam (ndjson) | CareTeam | Prod |
Security
MultiCare JWKS Public Keys Updated
Opala has updated the public keys for MultiCare. This effectively completes the registration for MultiCare, enabling them to utilize backend/client service authorization workflow and access the production ATR API endpoint.
Enterprise2022.3.0.9 Release
The 2022.3.0.9 release from Opala includes the following updates:
- ATR Groups definition update for UniRoster ETL.
- Client/backend service authorization workflow and custom ATR Group export added to Member Attribution (ATR) API.
- Updates to Databricks.
ETL Pipeline
UniRoster ETL
Opala has changed how it builds ATR Groups. A new field available in the Uniroster Contracts file, pod_id, has been added to differentiate between MA and GOC (commercial) contracts in Premera’s source data (UniRoster files). The new field is appended to the name of the attribution group (if a group is present) and used to determine group membership.
Member Attribution (ATR)
The following features have been added to the ATR API.
Backend Client Service Authorization Workflow
Workflow
SMART Backend Service Authorization workflow hass been added to ATR to be used by developers of backend services that need to access resources from FHIR servers which have pre-authorized defined scopes of access. This feature is used by providers to security access and retrieve bulk data from Opala’s ATR API.
For more information see the SMART Backend Services Authorization Guide.
Providence Registration
Providence has registered with Opala to enable backend service connectivity to Opala’s ATR API and allow retrieval of Value Based Contracts/ATR Groups assigned to Providence.
Custom ATR Bulk Export Operation
To support the ATR use case, a custom Group Export operation was implemented to return only FHIR Resources as defined by the ATR data model.
This custom Group Export is configured on the ATR API endpoints and effectively replaces the core FHIR Bulk Export operation. It enables registered parties to place the standard Group Export request:
It also enables registered parties to receive a custom set of FHIR resources which are listed below.
| Group | Retrieve Group identified in the ATRGroup export request |
| Patient | Patient, where Patient in Group:member Patient, where Patient in Coverage:payor |
| Practitioner | Practitioner, where Practitioner in Group:ext-attributedProvider Practitoner, where Practitioner in PractitionerRole:practitioner, and PractitionerRole in Group:ext-attributedProvider |
| PractitionerRole | PractitionerRole, where PractitionerRole in Group:ext-attributedProvider |
| Location | Location, where Location in PractitioinerRole:location |
| Organization | Organization, where Organization in Group:managing-entity Organization, where Organization in Group:ext-attributedProvider Organization, where Organization in Coverage:policy-holder Organization, where Organization in Coverage:payor Organization, where Organization in PractitionerRole:organization, and PractitionerRole in Group:ext-attributedProvider |
| Coverage | Coverage, where Coverage in Group:ext-coverageReference |
| Related Person | Related Person, where Related Person in Coverage:policy-holder, and Coverage in Group:ext-coverageReference Related Person, where Related Person in Coverage:subscriber, and Coverage in Group:ext-coverageReference Related Person, where Related Person in Coverage:payor, and Coverage in Group:ext-coverageReference |
Databricks Updated
Databricks has been updated to set up databases, file mounts, and configurations; to add a dim_date table; and to set up a daily FHIR recourse count pull.
Enterprise2022.3.0.6 Release
The 2022.3.0.6 release from Opala comprises updates to the Application Gallery’s contact links. The Request and App and Contact Our Helpdesk links have been updated to use web forms.
Members — Application Gallery Updates
Request a New Application Registration
The Contact Us to Request an App link that members can use to request a third-party application be added the Application Gallery has been updated to now open a web form.
The web form enables you to enter the required information to request that an application be added to the Gallery. Simply fill out the required information — indicated by an asterisk (*) — and select the Submit button.
Once the form has been submitted, Opala contacts the application’s developer to coordinate adding the app to Opala’s Gallery.
Note: If you select the Back to Application Gallery button before submitting the form, all information entered into the form is deleted. If you use the Home link to open another instance of the Application Gallery in a new tab, the information in the form is also deleted.
Contact Opala’s Helpdesk
The Contact Our Helpdesk link that members can use to communicate directly with Opala’s helpdesk has been updated to now open a web form.
Using this web form enables you to create a help ticket that will be logged into Opala’s system and addressed by our helpdesk. Simply fill out the required information — indicated by an asterisk (*) — and describe the issue you are having in as much detail as possible. When you have finished, select the Submit button.
Once the tickets has been created and queued, Opala’s helpdesk will address the issue as quickly as possible.
Note: If you select the Back to Application Gallery button before submitting the form, all information entered into the form is deleted. If you use the Home link to open another instance of the Application Gallery in a new tab, the information in the form is also deleted.
Enterprise2022.3.0.5 Release
The 2022.3.0.5 release from Opala comprises updates to the data sources processed for ZeOmega ETL.
ETL Pipeline
ZeOmega ETL
The following is a list of data sources (i.e., files) processed and FHIR resources generated/updated:
| Incoming Files/Format | FHIR Resources | Status |
|---|---|---|
| Zeomega_Patient (ndjson) | Patient | Prod |
| Zeomega_Goal (ndjson) | Goal | Prod |
| Zeomega_Condition (ndjson) | Condition | Prod |