Short Description

Real-world testing of the CARIN Consumer Directed Payer Data Exchange (CARIN IG For Blue Button®), which provides a set of resources that payers can display to consumers via a FHIR API, including Oral and Vision Profiles.

Long Description

The CARIN Alliance is an HL7 FHIR Accelerator program which brings implementers together to advance the use of HL7 FHIR standards in health care. The CARIN Alliance Health Plan Workgroup was organized to develop a FHIR-based API that could be sent to a consumer-facing application and was designed to answer the challenge for health plans to ‘meet or exceed’ the CMS Medicare Blue Button 2.0 capabilities. The CMS Medicare Blue Button 2.0 project provides over 53 million Medicare fee-for-service beneficiaries access to their electronic claims information.

The CARIN Consumer Directed Payer Data Exchange Implementation Guide (CARIN IG For Blue Button®)  was balloted in January for STU2 and comments are currently being addressed and resolved. Updates to the IG are being made to the continuous build once voted on and approved by the HL7 Financial Management Work Group.


The objectives of this track are: 

  • Test and gather feedback on the Draft Implementation Guide V2.0
  • Test the Oral and Vision Profiles
  • Utilize the Aegis Touchstone Testscripts to identify gaps or errors

Type

Test an Implementation Guide

Related Tracks?

Patient Access API (PDex, PDex Formulary and Plan-Net IGs), Da Vinci Health Record Exchange

Call for participants

Payers and consumer-facing apps

Track Prerequisites

Knowledge of USCore

Track Lead(s)

Amol Vyas Mark Roberts 

Track Lead Email(s)

 amol.vyas@cambiahealth.com; mark.roberts@leavittpartners.com

Specification Information

CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (PSS, STU1, Draft STU2)

Zulip stream

 https://chat.fhir.org/#narrow/stream/204607-CARIN-IG.20for.20Blue.20Button.C2.AE/topic/Connectathon.20Ongoing

Track Kick off Call

On December 15, we held a kick off call. A recording can be found here:  

https://leavittpartners.zoom.us/rec/share/vcpD31H3ypdIPOUZiUN33ZPT5C9TAjUIF1FYHdxu0k2RVGAa7RRS9xWluCOC1qyT.klsov4hD6fyIw73I
Passcode: 5=n7rI&n



Timeline of Upcoming Activities

Date

Time

Topic

Location

January 5, 2023

11:30 AM – 12:00 PM ET

Touchpoint

Zoom

https://leavittpartners.zoom.us/j/96222420751?pwd=b2lYa1k4ZnE4bXlsUTA3bXpwNWhVZz09&from=addon

Password: 671017

January 12, 2023

11:30 AM – 12:00 PM ET

Touchpoint

Zoom

https://leavittpartners.zoom.us/j/98226993447?pwd=TzlSTFVzMzQySXQzWDE1cTZYbi9tQT09&from=addon
Password: 476111

January 14, 2023

3:00 PM – 4:00 PM PT

Report Out

Las Vegas Room TBD

System Roles

Client - App

Server - Data holder

Testing Scenario:

In advance of the Connectathon we would ask participants to attend the Implementers Connection Calls and have signed up for the track ahead of the deadline. It is critical to attend the calls and sign up by the deadline as we will be matching Clients and Servers to ensure that everyone has someone to test the below Scenario.

We also ask that in advance of the testing session all participants onboard with the free Aegis Touchstone Testscripts. The below Powerpoint will guide you through the onboarding process. If you run into any issues, please reach out directly to Aegis at Touchstone_Support@AEGIS.net

These Testscripts are critical to ensuring that all participants are following a similar pattern when implementing the CARIN IG for Blue Button.


 PDF


Scenario: Sandbox user retrieves EOBs from the Sandbox server using the Client

  • Action: Sandbox user receives the access and refresh tokens from the Sandbox server and calls the EOB endpoint
  • Precondition: Sandbox user is logged into the Client
  • Success Criteria #1: The server returns resources that are compliant with CARIN BB Profiles, including Vision and Oral EoBs
  • Success Criteria #2: Server is compliant with SMART App Launch [Stand alone mode] framework
  • Success Criteria #3: Register with Aegis and utilize the Touchstone test scripts
  • Bonus point #1: On expiration of the access token, the app uses the refresh token to get new access and refresh tokens
  • Bonus point #2: The Server exposes search criteria (link) for selecting the EOBs and the client uses search parameters to select and retrieve the EOBs.
  • Bonus point #3: For a Server supporting _include, the resource instance included in the search response should match the instance from a separate read/vread on that resource's reference.

Test Script(s): Aegis Touchstone