Page tree
Skip to end of metadata
Go to start of metadata

Short Description

Real-world testing of the CARIN Consumer Directed Payer Data Exchange (CARIN IG For Blue Button®)

Long Description

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 December for STU 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 Implementation Guide
  • Identify gaps or errors


Draft Track Schedule (all times PT)

Times and sessions are subject to change.

Thu, Jan 14

08:00 AM – 08:30 AM Kick off

08:30 AM – 09:30 AM CARIN IG Technical Overview

09:30 AM –10:00 AM Ask IG Leads Anything 

10:00 AM – 12:00 PM Lunch / Client-Server Testing

12:00 PM – 01:00 PM Aegis Touchstone Overview & Q/A

01:00 PM – 02:00 PM Overview of Draft Vision and Dental CPCDS and Mapping

02:00 PM – 03:00 PM CAQH Endpoint Directory Overview/Demo

03:00 PM – 04:00 PM Ask the SMART App Launch Developers Anything

04:00 PM – 07:00 PM Client-Server Testing

Fri, Jan 15

08:00 AM – 9:00 AM Client-Server Testing

09:00 AM – 10:00 AM Examples Review 

- Joel Hansen, Aetna/CVS

10:00 AM – 11:00 AM Ask IG Leads Anything

11:00 AM – 12:00 PM Lunch / Client-Server Testing

12:00 PM – 2:30 PM  Demos/Lessons Learned From Servers & Clients / Client-Server Testing

  • 12:00 PM – 12:30 PM:
  • 12:30 PM – 1:00 PM:
  • 1:00 PM – 1:30 PM:
  • 1:30 PM – 2:00 PM:
  • 2:30 PM – 2:30 PM:

02:30 PM – 3:00 PM  Wrap-up and Report Out


Test an Implementation Guide

Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group  

Financial Management/CARIN

Proposed Track Lead

Amol Vyas - (zulip)

Mark Roberts (co-lead) - (zulip)

Related Tracks

The target audience for will include payer organizations who may also be involved in the various DaVinci Tracks at the Connectathon.

FHIR Version


Specification(s) this track uses

Artifacts of focus

(Interim) IG Materials

Clinical input requested (if any)

Patient input requested (if any)

Expected participants

Payers and App Developers, among others. Please sign up here:

Zulip stream

Track Orientation Date


Track Orientation Details

System Roles

Role 1 Sandbox API Server

Role 2 Client App Developer


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
  • Success Criteria #2: Server is compliant with SMART App Launch [Stand alone mode] framework
  • 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.


Aegis Touchstone

CARIN IG for Blue Button® Overview

Google Doc with Server Endpoints

Security and Privacy Considerations

As per the guidance in the IG.

Track Details

We held an Information Session to provide an overview of the CARIN track at the HL7 FHIR Connectathon on January 13-15. We also answered a number of questions that might be helpful as you prepare for the Connectathon.

A recording of the session can be found here: Passcode: h@0c6N.S

Report Out