Stream: implementers
Topic: Communication, Messages, Task, etc.
Lloyd McKenzie (Oct 28 2019 at 04:58):
As a result of some discussions within the Da Vinci project, I've written up some proposed guidance around the use of Task, messaging, Communication and CommunicationResponse. It's had some initial review and I'm now opening it up for broader review and feedback. The objective is to get some additional guidance into the FHIR core spec that advises people on how best to ask for information to be communicated and how to manage the delivery of that information. The discussion document is here. Feedback in this chat or as comments within the document are both welcome. https://docs.google.com/document/d/1OHfFcJ-OZvC81OFOOFudmcG3Lg5Wrrwo4n0dA09z40o
Tim Berezny (Nov 01 2019 at 10:48):
Great document.
A question about "Tasks also differ in that they are not typically retained as part of the medical record.".
I've been using a task to track the detailed status of processing a ServiceRequest e.g., businessStatus=waitlisted, and the eventual outcome of the referrals such as "Discharged to Long Term Care. This outcome status information in particular is something I would consider part of the medical record... at the very least it's a very important part of our metrics & reporting.
Am I putting this outcome (or status) information into the wrong spot by using Task?
Tim Berezny (Nov 01 2019 at 11:02):
=====================
Regarding general structure of the document:
First sentence for Documents: Posting documents causes the document to be stored “as is”.
First sentence for Transactions: Transactions allow multiple RESTful actions to be completed at once.
First sentence of Messaging: Like transactions and batches, messaging allows directing behavior of the receiving system beyond simply storing the Bundle.
As a general piece of feedback, I feel like most sections are missing a clear opening sentence. In my head, when I enter each section the question I'm asking is, "What IS a Transaction/Document/Collection" and/or "what is the purpose of a Transaction/Document/Collection" etc..., but instead, I'm a bit disoriented after the first sentence.
Lloyd McKenzie (Nov 01 2019 at 13:02):
@Tim Berezny Typically the result of the Task would be the outputs (Encounter, DiagnosticReport, etc.) - and they would point to the Request. However, there are absolutely situations where Tasks are part of the medical record. It's really one of those "it depends" situations. A provider's "to-do" list isn't generally retained long-term. However if Task is the sole record of something important having been done, then it will absolutely be retained.
Last updated: Apr 12 2022 at 19:14 UTC
