Stream: implementers
Topic: Task Resource...
Shubham Sharma (Aug 27 2020 at 18:18):
While adaption of Task resource we stuck to one situation. Current definition restricts "Device" to be recipient of task (Task.restriction.recipient). Our use case is to map task such as Machine maintenance | QA | Simulation. Thus looks more appropriate to fit in recipient as per definition. Please suggest if missing some logic here.
Lloyd McKenzie (Aug 27 2020 at 18:51):
Can you re-phrase your question? I'm not quite understanding
Shubham Sharma (Aug 27 2020 at 19:15):
Hi @Lloyd McKenzie , use case is to map device maintenance / quality assurance / simation tasks to Task resource.
In this how should we map Device in task resource.
Ideal place is Task.restriction.recipient. but it does not allow Device reference. So is there any specific reason why Device is restricted in this attribute.
Lloyd McKenzie (Aug 27 2020 at 20:46):
Primarily because we never thought of that use-case. Please submit a change request. In the meantime, you can create an extension that will allow you to refer to a device there.
Lloyd McKenzie (Aug 27 2020 at 20:46):
(Be sure to mention the use-case in your change request submission)
Shubham Sharma (Aug 28 2020 at 03:25):
Thanks @Lloyd McKenzie , it will be my first time to submit change request. Please point me to where I can do that.
Richard Townley-O'Neill (Aug 28 2020 at 03:36):
Hi Shubham
At the bottom of every page in the IG is a link Propose a change, which will take you to the HL7 Jira site.
Lloyd McKenzie (Aug 28 2020 at 03:52):
You'll need to do a one-time registration, after which you can submit change requests to your heart's content :)
Shubham Sharma (Aug 28 2020 at 07:02):
is it on https://jira.hl7.org/
Lloyd McKenzie (Aug 28 2020 at 14:14):
Yes
Shubham Sharma (Aug 29 2020 at 08:24):
Raised following Change Request : https://jira.hl7.org/browse/FHIR-28397
Last updated: Apr 12 2022 at 19:14 UTC
