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

CARIN BB Track Report Out

Track Announcements

Latest IG (STU1): http://hl7.org/fhir/us/carin-bb/2020Feb

Latest IG Materials (Documents/Data): https://confluence.hl7.org/pages/viewpage.action?pageId=82911348

Track Zoom Meeting Link: https://zoom.us/j/4720798123

Thursday May 14

  • 09:00 AM ET - 6:00 PM ET: Testing
  • 12:00 PM ET: Check-In (Track Zoom)
    • General housekeeping
    • CARIN BB IG Terminologies - Patricia Taylor
    • CARIN BB API Server Implementation Discoveries - Aaron Seib , Josh Lamb@UPMC, and others
  • 4:00 PM ET: Check-In (Track Zoom)
    • General Housekeeping
    • CARIN BB IG & Patient Identifiers - Swati Nanda@Aetna/CVS Health
    • CARIN BB API Demos -  Aju Jacob@BCBSTN
    • Brainstorm - APIs returning adjudicated claims/EOBs as FHIR Documents (i.e. using FHIR's Document Paradigm)?

Friday May 15

  • 09:00 AM ET - 1:00 PM ET: Testing
  • 11:00 AM ET: Check-In (Track Zoom)
    • General housekeeping
    • Track Material Review - Josh Lamb@UPMC
    • Review of CPCDS CSV to CARIN FHIR EOB Converter - Sam Schifman
    • CARIN BB IG & Patient Identifiers (Review Examples)- Swati Nanda@Aetna/CVS Health
    • Member Consent Rules for Third Party Access - Simon Gerrard@Aetna/CVS Health
  • 2:00 PM ET: CARIN BB Report Out (Track Zoom)
  • 3:30 PM ET: CARIN BB IG Track Review (Main HL7 GoToWebinar)
  • 6:00 PM ET: Connectathon Wrap Up


Submitting WG/Project/Implementer Group

Financial Management / CARIN Consumer Directed Payer Data Exchange (CDPDE) (PSS, STU1, Track Materials (Latest Documents and Data))


Justification and Objectives

What’s the purpose of hosting this connectathon track? What do you hope to achieve?

Real world testing of the CARIN CDPDE IG


This track will use what version of FHIR.

R4


Clinical input requested (if any)

Does your track have a need for input from the clinical community? If so, what are the needs?

N/A


Related tracks

(used to help guide seating arrangements and possibly drive track consolidation)

The target audience for CDPDE API development will include payer organizations who may also be involved in the various Da Vinci Tracks at the Connectathon.


Proposed Track Lead

Name, email. Track leads must be registered users on http://chat.fhir.org

Amol Vyas - amol.vyas@cambiahealth.com (zulip)


Expected participants

Who do you expect to be present? How many do you expect to attend?

Participants, please add/update your information in the public tracker:

Participant tracking: bit.ly/CARIN-CDPDE-Tracker


Track Collaboration/Communication/Feedback

CARIN CDPDE IG Zulip stream


System Roles

Describe each type of system that could participate in the track

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 - Sandbox API Server

Role 2 - Sandbox API Client app


Scenarios

Describe the different scenarios participating systems can engage in during the conenctathon. Each scenario should provide sufficient description that participants can appropriately construct their software in advance to prepare to interoperate during the connectathon.

Scenario 1 - Sandbox user retrieves EOBs from the Sandbox server using the Client app

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 app

Success Criteria: The client app 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 for filtering the EOBs and the client app uses the search criteria to retrieve the filtered EOBs [lastUpdated, etc]

Bonus point #3: Incorporate direct-support for native mobile apps (PKCE) [RFC8252 - native mobile app support, RFC7636 - PKCE]


Scenario 2 - Populate Server Sandbox that is tested for compliance by a tool (i.e. Aegis Touchstone/MITRE Crucible/ONC Inferno)

Action: Generate compliant CPCDS (Common Payer Consumer Data Set - defined by the CARIN CDPDE IG) extract and transform and load the same into a CARIN BB IG-compliant Sandbox FHIR repository

Precondition: A source for CPCDS flat file extract exists (for example, Claims/EOB System of Record such as Cognizant Facets, etc)

Success Criteria: The Sandbox passes the compliance testing run by the tool

Bonus point #1: Transform and load the CPCDS extract into a third party CARIN CDPDE IG-compliant Sandbox FHIR repository that also passes the tool's compliance testing


Reference Implementation Resources:


TestScript(s)

Indicate any test scripts that will be used to help verify system behavior


Security and Privacy Considerations

Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate







  • No labels