Stream: Da Vinci CDex
Topic: CDex Task and Solicited Communication
Sam Schifman (Jun 03 2020 at 13:41):
I have a question about the role of CDexTask in the "Request (Solicited Communication)" [http://build.fhir.org/ig/HL7/davinci-ecdx/Request_(Solicited_Communication).html] flow. In the "Solicited Communication With Task" it talks about sending a Task to the Information Sender, but when I look at the structure definition for CDexTask [http://build.fhir.org/ig/HL7/davinci-ecdx/StructureDefinition-cdex-task.html] it says that the "focus" field must be a reference to a CDexCommunication.
However, I do not understand where this Communication would come from as my understanding is that the purpose of this Task is to tell the Information Sender there is CommunicationRequest available to be fetched? My understanding is that the Communication would not exist until after the CommunicationRequest is fulfilled. Also, where in the Task would I specify the ID of the CommunicationRequest for the Information Sender to fetch it from the Information Recipient?
Lloyd McKenzie (Jun 03 2020 at 17:22):
First, be aware that CDex is being refactored based on feedback from the recent ballot, so the mechanisms currently defined in the spec are different than what's likely to be in the final published spec.
As currently written, the intention is that Task points to the request to be executed. The 'filling' system then retrieves the CommunicationRequest to see what is being asked to be done and updates the Task to indicate acceptance/rejection and later to indicate status. Once the data has been prepared, a Communication resource is created and the Task is updated to point to the Communication as an 'output'. The requesting system (which is monitoring the Task by polling or subscription) can then query the Communication and any contained/referenced data.
Sam Schifman (Jun 03 2020 at 18:11):
Thanks!
So I could assume that the "focus" field in the final CDexTask will either allow
-
either a reference to CDexCommunicationRequest or CDexCommunication
or -
be optional and there will be another field to indicate the reference to the CDexCommunicationRequest
in the next release of the IG?
Lloyd McKenzie (Jun 03 2020 at 18:25):
There will only be on CDex Task
Lloyd McKenzie (Jun 03 2020 at 18:25):
The Task will always have a focus of the CommunicationRequest
Lloyd McKenzie (Jun 03 2020 at 18:25):
It will be updated to point to the Communication as an 'output'.
Sam Schifman (Jun 03 2020 at 18:28):
Thanks, that makes sense.
Lisa Nelson (Aug 11 2020 at 14:23):
@Lloyd - the CDex IG CI build doesn't appear to be new. Where are the changes being documented? http://build.fhir.org/ig/HL7/davinci-ecdx/
@Yan Wang and I are interested in the CDex Task. Where can we see this documented?
Lisa Nelson (Aug 11 2020 at 14:38):
@Lloyd McKenzie We notice the new CDex task profile in here: http://build.fhir.org/ig/HL7/davinci-ecdx/StructureDefinition-cdex-task.html
But it doesn't appear that the CI IG in the FHIR IG registry has been updated. Where is the guidance on the newly envisioned use of Task written up?
Lloyd McKenzie (Aug 23 2020 at 18:54):
HRex has a base profile and some examples for using Task to solicit data. That's what I expect to be used as part of the upcoming connectathon. CDex has not yet been updated to point to it. (We're still discussing options with EHR vendors, so it's premature to update the spec.)
Last updated: Apr 12 2022 at 19:14 UTC
