Review Payer Data Exchange and Interaction with US Core v3.1.0+
The CMS Interoperability and Patient Access Rule requires payers to release data going back to January 1, 2016. The work of the PayerData Exchange (PDex) Work Group is helping to coordinate payer activity in response to the clinical and encounter data requirement by leveraging US Core resources with some additions from PDex.
With the dramatic increase in the number of FHIR API endpoints and the number of apps wanting access to these APIs we face a challenge in managing the issuing of credentials. We need to find a better way that leverages the power we have when we act as a community with a common purpose. Fortunately the ONC's FHIR At Scale Taskforce (FAST) have been addressing this next generation problem. The UDAP protocol was first referenced from PDex in the Da Vinci Health Record Exchange (HRex) IG. It provides a method that allows simpler registration of trusted apps.
The purpose of this event is three-fold:
The outcomes desired from this event include:
Real world testing of the Da Vinci Payer Data Exchange IG focused on the Consumer-Directed Exchange scenarios will take place as part of this event.
Intro Deck: PDexPatientAccessAPIEvent.pptx
11:30 Track opens
12:00 Reference Implementation Demo and view the code on GitHub
12:30 a) Testers can go to break out room to coordinate testing activities (Be prepared to provide a demo or summary of outcomes for the wrap up session later in the day.)
1:00 UDAP Education session
12:30 b) People that are new to FHIR and PDex can stay in the main room and ask questions and go through an overview of the IG.
3:00 sync up and gather lessons learned and highlights to be able to raise in the wrap-up session.
3:30 Head over to wrap up session
Financial Management WG
Mark Scrimshire - email@example.com (zulip)
The target audience for PDex falls into two groups:
Da Vinci Payer Data Exchange (PDEX) IG (PSS, STU1, CI)
US Core provides a resource for ImplantableDevice. Payers may have information about other devices without UDIs that need to be shared. The Device profile is meant for that purpose.
Learn which records are most important
PDex Work Group Call: August 7, 2020 at Noon ET.
The session will be recorded.
Action: Sandbox user receives the access and refresh tokens from the Sandbox server and calls the clinical resource endpoints
Precondition: Sandbox user is logged into the Client
Success Criteria: The client retrieves the user's clinical records 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 clinical resources and the client uses search parameters to select and retrieve the those resources.
Lots of Questions>>>