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

Connectathon Report Out

CARIN Connectathon Day 1

The PowerPoint presentation for the Kick-Off session can be found below.

Meeting Recording of every session can be found here:

Access Passcode: se@B0T+4

CARIN Connectathon Day 2

Meeting Recording of every session can be found here:

Access Passcode: 4*WX?9hK

Track Announcements and Schedule

Balloted IG (STU1):

CI Build IG (STU1 0.3.1):

Participant Tracker:

Zulip channel:

Latest (Interim) IG Materials:

Zoom: Password: 468214

Please monitor the track page for the latest schedule here (all times ET):

Wednesday, November 18

  • 11:00 – 11:30 AM Kick off
  • 11:30 – 12:30 PM Ask IG Leads Anything
  • 12:30 – 1:00 PM Lunch
  • 1:00 – 1:30 PM Aegis Touchstone Overview & Q/A
  • 1:30 – 2:30 PM Client-Server Testing
  • 2:30 – 3:30 PM CMS Question/Answer Session
  • 3:30 – 5:00 PM Client-Server Testing
  • 5:00 – 6:00 PM Examples Review 

Thursday, November 19

  • 10:00 AM – 12:00 PM Client-Server Testing
  • 12:00 – 1:00 PM Ask the SMART App Launch Developers Anything
  • 1:00 – 2:00 PM  Demos From Payers/Servers & Clients
    • 1;00 -1:15 UPMC
    • 1:15-1:20 MITRE
    • 1:20 - 1:30 Humetrix
    • 1:30 - 1:45 The Commons Project
    • 1:45 - 2:00 myElth
  • 2:00 – 2:30 PM Advanced Topics 
    1. CPCDS Synthea
    2. Privacy/Consent (data tagging & filtering)
  • 2:30 – 3:00 PM  Report Out

Session #1 Client Server Testing Ice Breaker

To move between break out rooms, please send a Zoom Chat to Jourdan Laures or email:

Break Out Room

Server Name























CARIN Connectathon Info Session

We held an information session on Wednesday 11/11, The slide deck can be found below and a recording of the info session can be found here: Passcode: h1j#cr3j

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 CDPDE API 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

(Interim) IG Materials

Expected participants

Zulip stream


Track Orientation

Track Orientation

Track details

System Roles

Role 1 Sandbox API Server


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  { in development }

Security and Privacy Considerations

As per the guidance in the IG.

Reference Materials

  • No labels