This Da Vinci track is focused on testing the functionality of the CDex implementation guide. It covers provider to provider and provider to payer exchanges to help facilitate continuity of care. Testing will focus on 4 topics:
NOTE: Unlike some past connectathons, this track will not incorporate the PCDE implementation guide as PCDE development work is on hold until Jan. 2022.
The specific aspects of the IGs that will be a focus of this track include:
Attendees are requested to identify in advance which of these aspects of the track they plan to be prepared to test
Test an implementation guide
Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group
Lloyd McKenzie; Eric Haas
Track Lead Email(s)
Specification(s) this track uses
Artifacts of focus
EHR and other data source systems, as well as payer systems
Updated reference implementation
Track Implementers Connection Call
Demo Session pre-planning Call:
Follow-up planning Call:
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.
Direct Query Server (Provider)
Direct Query Client (Payer or Provider)
Task Based Request Server (Provider)
Task Based Request Client (Payer or Provider)
Attachments Client (Provider)
Attachments Server (Payer)
Advanced preparation is required for implementing the Subscriptions R5 backport as a new feature. Allow for at least 1 weeks prior to the start of the connectathon for preliminary testing. Support will be available virtually on http://chat.fhir.org.
1. Direct query
Action: Synchronous Data Consumer executes a RESTful search the Synchronous Data Source's system that will return the patient's active medication orders
Precondition: The Synchronous Data Consumer knows the Synchronous Data Source's patient identifier for the patient/member in question (see step 1)
Success Criteria: Synchronous Data Consumer Payer has all of the active medication orders for the patient/member
2. Asynchronous Document retrieval
Action: Asynchronous Data Consumer creates a Task on the Asynchronous Data Source's system soliciting a patient's knee surgery report and then polls for updates to the Task. When the Task is complete, the Data Consumer reads the document referenced via the Task.output
Precondition: The Asynchronous Data Consumer knows the Asynchronous Data Source's patient identifier and (if needed) coverage identifier for the patient in question (see step 1)
Success Criteria: Asynchronous Data Consumer has a copy of the requested document
3. Filtered query
Action: Asynchronous Data Consumer creates a Task on the Asynchronous Data Source's system soliciting the execution of a query that will return the patient's active medication orders then polls for updates to the Task. When the Task is complete, the Asynchronous Data Consumer reads the search response Bundle referenced via the Task.output
Precondition: The Asynchronous Data Consumer knows the Asynchronous Data Source's patient identifier and (if needed) coverage identifier for the member in question (see step 1)
Success Criteria: Asynchronous Data Consumer Payer has all of the active medication orders for the member
4. Unsolicited push
Action: Unsolicited Data Source invokes the 'process-attachment' operation on the Unsolicited Data Consumer to attach a document to an existing Claim Response. The Unsolicited Data Consumer returns a success code
Precondition: The Unsolicited Data Source knows the Unsolicited Data Consumer's member identifier for the patient. An un-processed prior authorization with a known identifier exists on the Unsolicited Data Consumer's system
Success Criteria: The submitted attachment is associated with the pre-existing prior authorization on the Unsolicited Data Consumer's system.
See the Example Data and example scenarios for each type of exchange in the implementation guide
to view full size charts copy/paste the text between the triple backtics to https://flowchart.js.org/
Sample data is available as FHIR transaction bundles: here
Touchstone has loaded some FHIR test-scripts for HREX/CDEX use cases that can be found HERE.
Please reach out to Touchstone_Support@aegis.net with any questions on how to test.
Security and Privacy Considerations:
None at this time