Stream: Orders and Observation WG
Topic: ServiceRequest - extra parties to inform of the outcome
Rob Hausam (Oct 19 2020 at 15:34):
This topic was posted on the implementers stream. It seems like it would be good for us to discuss on an OO call.
Jose Costa Teixeira (Oct 19 2020 at 16:25):
Interesting. Could it be about using a CommunicationRequest?
Lloyd McKenzie (Oct 19 2020 at 16:28):
That seems like overkill
Jose Costa Teixeira (Oct 19 2020 at 16:41):
what else? an extension?
Lloyd McKenzie (Oct 19 2020 at 16:47):
y
Jose Costa Teixeira (Oct 19 2020 at 17:37):
that makes the extension bound to the Request, then it's up to the Report to get it and figure out what else to do with it. Could be a standard extension.
If we have a separate resource, we can just point everyone to that resource, or even make a Task out of it "Please distribute"
Lloyd McKenzie (Oct 19 2020 at 17:41):
Standard extension makes sense - submit as a workflow change request?
Lloyd McKenzie (Oct 19 2020 at 17:41):
Though do we think it's relevant for anything other than ServiceRequest?
Jose Costa Teixeira (Oct 19 2020 at 18:03):
actually, not sure. CarePlan, maybe. But it still makes sense as a standard extension, right?
Vassil Peytchev (Oct 19 2020 at 18:05):
Is this actually part of the ServcieRequest? Or of the Task regarding its fulfillment?
Eric Haas (Oct 19 2020 at 19:54):
already a tracker
see J#20932
Eric Haas (Oct 19 2020 at 19:57):
who and when is it decide who else gets to see the results? I think is can be both at the order level and the task level
Eric Haas (Oct 19 2020 at 19:59):
A) Why an extension for example in CommR the recipient ins 0..*?
B) Why not an fist order element and replicate in Task and/or ServiceRequest? It sounds like a pretty common use case to me
Lloyd McKenzie (Oct 19 2020 at 23:51):
Allowing it on Task too makes sense
Last updated: Apr 12 2022 at 19:14 UTC
