Stream: implementers
Topic: Task Title
Tim Berezny (Jan 23 2018 at 05:20):
In most task management programs I've used (e.g., Asana, Things, Trello, etc...) tasks have a title and a description. In the FHIR resource I only see "description", and no title.
Should there be a title in the task resource, or is there already one there that I'm just not interpreting correctly? (i'm going through a use case right now where a title would be useful)
@Lloyd McKenzie
Vassil Peytchev (Jan 23 2018 at 05:29):
Can you share the use case? There's also a workflow stream, where you may get more discussion on this...
Tim Berezny (Jan 23 2018 at 05:38):
I'm using the /task resource to trigger a "Request for information" in a /referalRequest, where the provider asks for more information from the requester (such as, "please send the assessment".
I want to build a very specific process for when the TITLE of the task is "Request for Information", then use the DESCRIPTION field to hold the contents of the information request (e.g., please send the assessment).
When a task arrives that is titled "Request for information", it can trigger some specific workflow actions.
Eric Haas (Jan 23 2018 at 05:59):
Have you looked at CommunicationRequest for this instead. Task
tracks the state of a task. The details would be handled by this request resource.
Jose Costa Teixeira (Jan 23 2018 at 12:01):
Task.title makes sense IMO, but indeed if your use case is for the request, you may opt for the dedicated resource
Tim Berezny (Jan 23 2018 at 13:51):
Interesting, thanks @Eric Haas and @Jose Costa Teixeira @Vassil Peytchev , this could work ... It seems quite similar to "task" but has a more appropriate structure for a communication "payload".
Would it be accurate to say that what i previously put as "description" (i.e., please send the assessment") would go into the payload.contentString of the communicationRequest, and the response would come back in a communication resource?
Tim Berezny (Jan 23 2018 at 13:58):
Along a similar lines, i find the "status" list on /referralRequest very limited, and so i have tried attaching a /task resource to use the tasks status field (referral is accepted/rejected/hold, etc...) as well as the custom BUSINESS status (waitlisted, deferred, no show, etc...).
I call the task "process referral request", and attach it on submission to every /referralRequest. It lives during the whole life of the referral, and is only completed once the referral has been completed.
Does this sound like an appropriate use of the task resource, or is there another purpose built resource for this?
Vassil Peytchev (Jan 23 2018 at 14:08):
You can take a look at http://build.fhir.org/workflow-communications.html to see a (totally made up) example of task, task status, statusReason, and businessStatus for a referral.
Tim Berezny (Jan 23 2018 at 14:12):
Thanks @Vassil Peytchev ... those processes seem pretty spot on for what I'm trying to do. Seems like /task may indeed be the correct choice for this particular flow, and replace my "Request for Information" task with CommunicationRequest.
Tim Berezny (Jan 23 2018 at 14:20):
I guess i should start calling my referralRequest ServiceRequest by the looks of it...
Tim Berezny (Jan 23 2018 at 15:24):
What is the best way to submit a file attachment with a ServiceRequest (e.g., an assessment PDF)?
I see in http://build.fhir.org/workflow-communications.html that @Vassil Peytchev pointed me to that when completing a referral, the suggestion is to reference a composition resource. Would a composition resource be the best way for the requester to submit attachments too? Or should i use a simpler format such as a document reference, or binary?
Also, should it be reference via serviceRequest.supportingInfo, or some other mechanism? (such as a communicationRequest)
Eric Haas (Jan 23 2018 at 15:45):
RE: What is the best way to submit a file attachment with a ServiceRequest (e.g., an assessment PDF)?
ServiceRequest.supportingInformation --> reference(DocumentReference|Binary) is one way
Vassil Peytchev (Jan 23 2018 at 15:47):
In my opinion, using the composition resource is the preferred way to reference different types of documents, including binary documents like a PDF. One option in this case would be to reference a composition from task.input.
Eric Haas (Jan 23 2018 at 15:51):
IMO :-) If all you want is to attach a pdf then using supportingInformation would be fine.
Lloyd McKenzie (Jan 23 2018 at 15:57):
Composition would be unnecessary overhead to convey a PDF. A plain PDF would be a Binary resource. A PDF with some metadata would be DocumentReference (and the content conveyed in DocumentReference.content.attachment).
On the original question, we talked briefly about adding title, but couldn't think of a situation where Task.code.text wouldn't satisfy the need and we didn't want to provide two ways to say the same thing. If you have a need for both, feel free to use the "propose a change" link at the bottom of the resource. And if you think that Task.code.text will meet your needs, feel free to submit a change proposal to make this use more obvious through both examples and perhaps some usage notes :)
Vassil Peytchev (Jan 23 2018 at 17:04):
You are correct, I was mixing composition and documentReference. I do think that some metadata is preferred. As to why to link to it from the task resource, in a managed workflow the task resource is expected to be shared by the two sides.
Tim Berezny (Jan 24 2018 at 21:19):
Thanks @Eric Haas , @Lloyd McKenzie , @Vassil Peytchev , this is really helpful, in fact this is exactly the clarification I needed.
@Lloyd McKenzie Ok, I see how task.code.text could work just fine for the scenario i originally described. I guess pulling that observation out the documentation then might be the only thing.
I've never submitted a change proposal, how do i do that?
Lloyd McKenzie (Jan 24 2018 at 22:36):
At the bottom of every page in the spec there's a "Propose a Change" link. The first time you'll need to register and we'll confirm that you appear to be a real human being as opposed to a bot that wants to sell stuff. That's a manual process and can sometimes take a businesss day or two, though usually it's pretty fast. Keep an eye on your spam folder for a response. Once that's done, you can request any change you like and will be able to see as your suggestions are commented on, scheduled, resolved, etc. (You can also search and see what other changes are pending and can subscribe to them if you wish.)
Lloyd McKenzie (Jan 24 2018 at 22:36):
If you hit any issues, let me know.
Last updated: Apr 12 2022 at 19:14 UTC
