Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Proposed Track Lead(s)

...

  • PCDE Track Orientation: 8/21/20, 2p ET
  • Orientation Presentation Recording 

...

Event Agenda

  • ThursdayWednesday
    • 93:00 ET -  PCDE Overview Presentation10:00 45p - 5p ET - HRex/ CDex Overview Presentation
    • 16:00 ET - Track touch-point - Progress so far, open issues, objectives for tomorrow, 
    Friday
    • 15:00 ET - Track Highlight / Report-out - go to Whova Track High, PDex, PCDE Education Sessions
  • Thursday
    • 11a-4p ET -  Implementation-a-thon

System Roles

NOTE: participants should expect to complete most of their development in advance of the track.  Depending on which portions of the track are implemented, development should likely start no later than mid-late August.

...

Participants and observers representing payers and implementers from 7 organizations: Anthem, Cerner, Gevity, Humana, Interoperion, Mettles, and MITRE.

CDex:

Successes:

  • Presented a CDex Walkthrough that highlighted the new Task-based approach to sharing as well as a demo of the revised reference implementation, which supported the new Task-based approach
  • Updated the reference implementation to included clearer documentation/better alignment with new Task-based approach
  • Were able to test the new approach between one payer and one EHR
  • Identified a bit of clean-up to the HRex Task profile
  • Good discussion on the use of Subscription and created some examples for what subscription might look like

Challenges:

  • Limited attendees made broader discussion about subscription harder – will take back to the broader groupTBD

Challenges:

  • TBD

Future Work:

  • Questions to explore with respect to Subscription:
    • Should we include subscription in CDex release 1?
      • seems that the R4 mechanism is 'ready enough'
    • rest-hook or websocket
      • presume email & messaging are off the table
    • Full resource vs. identifier vs. either (presume ping is off the table)
      • With full resource, include outputs in bundle? If so, what?
  • TBD

PCDE:

Successes:

  • Presented a PCDE Walkthrough with a client demo that can be tested by payer subject matter experts to review PCDE content.
  • Implemented and tested new Task resource changes.
  • Participant review and pressure-test of the IG with a PCDE Bundle example, resulting in identifying two JIRA issues:
  1. Missing reference from PCDEBundle profile to PCDEComposition
  2. Adding invariant to improve conformance of ActiveTreatment sections within a PCDEComposition
  • Fixed PCDE Bundle example which incorrectly had multiple treatments under one ActiveTreatment.

Challenges:

  • PCDE IG still loose on how to best represent clinical data within a PCDE CarePlan
    • needs more active payer feedback on the PCDE Supplemental Guide to vet recommendations.

Future Work:

  • PCDE Testing Subscription/Notification use case over Polling Tasks
  • Support for embedded X12/EDI transactions to represent a prior authorization as an alternative to referencing the PAS IGTBD

Challenges:

  • TBD

Future Work:

  • TBD