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

Announcements & Schedule

Please add/update your information in the CARIN IG for Blue Button® tracker spreadsheet yourself (or through Mark Roberts) here:

A dedicated Zulip chat channel for this track can be found here:

Track Kick Off Recording

We held kick off session on Thursday 9/10. The slide deck can be found below and a recording of the session can be found here:   Access Passcode: k7!1+xZ!

Wednesday, September 9

  • 4:00 pm ET: Connectathon Kick Off

Thursday, September 10

  • 10:00 AM ET - 7:00 PM ET: Testing (refer to tracker spreadsheet for server and client information)
  • 10:00 AM ET: Track Kick Off - Mark RobertsAmol VyasPatricia Taylor
    • Logistics and housekeeping
    • Technical overview
    • What's new in the latest build version?
    • Current HL7 process status
  • 11:00 AM ET: Examples Review 1 - Josh Lamb@UPMC
  • 01:00 PM ET: 1upHealth CARIN IG Data Ingestion & FHIR Server Overview - Kyle Brew
  • 02:00 PM ET: Google CARIN IG Server Overview - Andy Crowne, Kalyan Pamarthy, Dharmesh Patel
  • 04:00 PM ET: Ask the IG Leads Anything - Amol Vyas , Patricia Taylor

Friday, September 11

  • 09:00 AM ET - 6:00 PM ET: Testing (refer to tracker spreadsheet for server and client information)
  • 09:00 AM ET: Track Kick Off - Mark Roberts
    • Logistics and housekeeping
  • 10:00 AM ET: Examples Review 2 - Joel Hansen@Aetna
  • 11:00 AM ET: CPCDS Physical Format and Synthea Synthetic Data - Interested track participants
    • Physical schema and organization of the CPCDS file(s).
    • Generating CPCDS data using Synthea’s CPCDS Exporter or other tool.
    • Demo of the CPCDS intake pipeline for the sandbox server.
    • Collaboration opportunities for maturation of the Synthea CPCDS Exporter.
  • 12:00 PM ET: Ask the IG Leads Anything - Amol VyasPatricia Taylor
  • 01:00 PM ET: OnyxHealth SaFHIR Overview and Demo - Aaron SeibMichael Cox
  • 02:00 PM ET: Track Wrap Up and Report Out - Mark Roberts , Amol Vyas

Reference Materials



Reference Implementation Resources

Track overview

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


Test an Implementation Guide

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

Financial Management WG

Proposed Track Lead

Amol Vyas - (zulip)

Mark Roberts (co-lead) - (zulip)

Related tracks

The target audience for CARIN IG for Blue Button® development will include payer organizations who may also be involved in the various DaVinci Tracks at the Connectathon.

FHIR Version

  • FHIR R4

Specification(s) this track uses

CARIN Consumer Directed Payer Data Exchange (CDPDE) IG (PSS, STU1, CI)

Artifacts of focus


Clinical input requested (if any)


Patient input requested (if any)


Expected participants

Zulip stream

Zulip stream

Track Orientation


Track details

System Roles

Role 1 Sandbox API Server

Role 2 Sandbox API Client


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: The client retrieves the user's EOBs and renders them on the UI

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.



Security and Privacy Considerations


Report Out


  • The track held several sessions to answer questions related to the IG.

Participants (apologies if I missed anyone)



Blue Cross Blue Shield Association

Abacus Insights


Innovaccer Inc.








Linden Tech Advisors







Notable Achievements

  • We are seeing more technical involvement from payers.
  • We are doing payer education in terms of the Open specifications.
  • The track held a “Ask the IG Leads Anything” session, where the participants were able to ask the track leads a number of questions. These questions and answers will be posted on the CARIN Confluence Q&A/Wiki page.
  • Demo sessions were held related to:
    • Google CARIN IG Server Overview
    • OnyxHealth SaFHIR Demo
    • 1upHealth CARIN IG Data Ingestion & FHIR Server Overview
    • CPCDS Physical Format and Synthea Synthetic Data
  • Example Sessions:
    • Examples Review 1 - Josh Lamb and UPMC team
    • Examples Review 2 - Joel Hansen and Aetna team


Discovered Issues

  • As the IG approaches STU-1, the level of compliance across the payer APIs is increasing in tandem.
  • Need to provide clarity in service date in Search Parameters.
  • Amend the Capability Statement to include: the launch patient scope SHALL be supported and payers MAY support user scope.
  • The artifact summary should align with the Capability Statement.
  • Examples:
    • Add a MUST Support on EOB.created
    • Do not have an identifier type for payer assigned claim number and member id
    • Consider providing a code system that abstracts several code systems that might be implied by a value set

Next Steps

  • We hope to have a starter compliance testing prior to the next Connectathon.
  • Determine if we want to develop common test parameters or scripts for ONC Inferno or MITRE Crucible that could be used for conformance to the IG.
  • We agreed to continue discussion around creating mature synthetic data generation capability (ex: through Synthea).
  • We hope to continue the discussion through Zulip and will set up additional info sessions to continue the discussion.
  • No labels