Stream: Da Vinci
Topic: CDex Solicited Communication
Peter Bernhardt (Apr 01 2021 at 20:40):
I need some help understanding using the solicited communication with Task. Reading this (http://hl7.org/fhir/us/davinci-cdex/2019Jun/Request_(Solicited_Communication).html#solicited-communication-with-task) it is unclear when the Information Request Sender actor creates the Task. After the communication request?
Peter Bernhardt (Apr 01 2021 at 20:41):
And why does the profiled Task focus on an instance of a Communication rather than a CommunicationRequest? Is the idea here that the Information Request Sender must first POST a CommunicationRequest, wait for receipt of a Communication, and then POST the Task? That doesn't make sense.
Peter Bernhardt (Apr 01 2021 at 20:49):
And in the Solicited Communication without Task (which seems straightforward), how would errors get communicated? For example, no document could be located for the specified patient for the specified encounter?
Peter Bernhardt (Apr 01 2021 at 21:08):
Sequence diagrams would help. The existing diagrams are confusing. For example, after POST of a Task, the label in the Receiver column says to the received Task explains what to do with CommunicationRequest. So why, again, is Task referencing a Communication in the focus property and not the CommunicationRequest?
Eric Haas (Apr 02 2021 at 02:10):
note that the CDEX and HREX guides have been completely rewritten and are currently undergoing ballot reconciliation. Check out the HREX build for the overview of Task and the corresponding Task based approach in CDEX
Last updated: Apr 12 2022 at 19:14 UTC
