Real-world testing of the CARIN Consumer Directed Payer Data Exchange (CARIN IG For Blue Button®)
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 Blue Button 2.0 capabilities. The CMS 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
Mark Roberts (co-lead) - email@example.com (zulip)
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 R4
Specification(s) this track uses
Artifacts of focus
Clinical input requested (if any)
Patient input requested (if any)
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
Reference Implementation Resources
- Hosted Reference implementations:
Simple Reference OAuth server: http://ec2-3-23-131-14.us-east-2.compute.amazonaws.com:8180/
Reference Client: https://cpcds-client-ri.herokuapp.com/
- Reference Implementation Code (with Docker containers)