2022 Q1 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.1.1.1 Release
This release deploys an Opala configuration for ATR, including validating connectivity and retrieving a sample ATR, and provides a dedicated Sandbox endpoint for Providence.
Member Attribution (ATR)
Note: In this release, Providence is the only user with access to Member Attribution. In the future, Opala will open this feature up for other users to access.
Opala has initiated a method for using HL7 FHIR to exchange Member Attribution Lists (MAL). These lists can be used by providers and payers to implement use cases for Value Based Contracts (VBC), Quality Reporting, Da Vinci Payer Data Exchange (PDex), and Da Vinci Clinical Data Exchange (CDex) among others.
Opala enables a user to:
- Receive member attribution lists from a payer, in either a proprietary or standard format.
- Make standards-based member attribution lists available using the FHIR API for access.
The following specifications guide this solution:
- FHIR R4 – Standard
- Da Vinci – Member Attribution (ATR) List IG – Additional Constraints on standard
- Bulk Data IG – Additional Constraints on standard
- SMART on FHIR Backend Services Authorization – Secure access to API
Using Opala’s ATR feature enables a user to accomplish several objectives:
- Create a Member Attribution group.
- Add members to a group
- Manage attributions.
- Remove members from an attribution.
- Receive notifications of changes in attribution.
Examples
Below are listed examples of GET requests that can be run using the BasicAuth:
- GET: https://api.in.opalahealth.io:45000/Binary
- GET: https://api.in.opalahealth.io:45000/Organization
- GET: https://api.in.opalahealth.io:45000/Location
- GET: https://api.in.opalahealth.io:45000/Practitioner
- GET: https://api.in.opalahealth.io:45000/PractitionerRole
- GET: https://api.in.opalahealth.io:45000/Patient
- GET: https://api.in.opalahealth.io:45000/RelatedPerson
- GET: https://api.in.opalahealth.io:45000/Coverage
- GET: https://api.in.opalahealth.io:45000/Group
The following resource IDs for the objects listed above are available:
{
"Organization1": "094309ea-90f7-4536-ba4f-69d33b80e845",
"Organization2": "772ed3ac-7ad0-4738-9c32-395b7f30d44c",
"Location": "0d56cedb-88f4-4413-95ea-26c6f7a42b40",
"Practitioner": "a65fa2e3-3ad7-45e3-80a9-339b02cfb33c",
"PractitionerRole": "b8774a83-2be4-4dd2-8f8d-3689ce1cb480",
"Patient1": "a65f8a5c-5be8-4c0c-b3b0-8391e4e4c24d",
"Patient2": "8c7eb538-386a-4776-89bf-b4384a00766b",
"Patient3": "00b0a4dc-767f-452d-85e4-55de79b46ecc",
"RelatedPerson1": "57486313-4012-45fa-a7e0-ef99060e1d01",
"RelatedPerson2": "2eac4b9b-915b-4ce5-b780-213c02a86630",
"Coverage1": "bd8f3af2-d4d4-4e50-8ce9-87ee01382710",
"Coverage2": "5305352b-938d-4fbf-8397-2df4ac3e8480",
"Coverage3": "670cac44-61b0-4a4e-9d17-726c0b012279",
"Group": "b1f4e3c4-02dc-46fb-b607-83dfc0d426ca"
}Enterprise2022.1.1.0 Release
This release expands the sandbox environment to include a test user and endpoints.
The Opala APIs support:
- FHIR Release 4 specification
- Da Vinci Payer Data Exchange (PDex)
- CARIN for Blue Button®
- United States Core Data for Interoperability (USCDI)
The Sandbox
Opala’s Sandbox is available once you have created an account with Opala. Use the Sandbox to test your application’s connectivity and validate all aspects of your application against the test user and endpoints provided.
The sandbox environment parallels the production environment but contains no live data: all data available in the Sandbox is created specifically for the sandbox environment and does not correspond to any real-world data. Opala recommends validating your application against the sandbox environment before registering your application.
Sandbox Settings
The Sandbox Settings page enables you to create an OIDC client to use in the test environment. Access the Sandbox Settings page from the Developer Portal.
The Settings page enables you to enter or modify an applications name, OIDC redirect URLs, the app’s confidentiality, and define the scopes required by the application. The page provides the base URL of the FHIR endpoints and the URL of the Discovery Document.
Once you save the settings for your Sandbox, you receive a client ID and, for confidential apps, a client secret to use against Opala’s sandbox environment.
Test User: Jane W. Gold
Opala provides a test user, Jane W. Gold, for you to use in the sandbox environment. To access this resource, you will need the following login information:
Username
Password
Patient ID
This information is available in the Opala documentation set.
Available Endpoints
The following endpoints are available for use with the Jane Gold test user:
- AllergyIntolerance
- Coverage
- DiagnosticReport
- Immunization
- MedicationRequest
- Patient