Stream: implementers
Topic: Task "based on" vs" focus"
Josh Mandel (Mar 08 2017 at 14:03):
The "task" documentation says:
For example, based on a ProcedureRequest (= BasedOn), a task is created to fulfil a procedureRequest ( = FocusOn ) to collect a specimen from a patient.
is this a typo? Are we saying that a given task might "focus on" *and* be "based on" the same ProcedureRequest? Or two different ProcedureRequests? I'd propose a clearer example, but I don't understand what's happening yet.
Lloyd McKenzie (Mar 08 2017 at 16:34):
It would have to be two different procedure requests. "basedOn" is "under what authorization is this task being undertaken". Focus is "what is being manipulated by the task". It would make no sense for an authorization to be created that authorizes the manipulation of itself.
Lloyd McKenzie (Mar 08 2017 at 16:37):
If you have "QA" recommendations to improve either definition, they're welcome
Josh Mandel (Mar 08 2017 at 17:04):
I'm hoping the documentation could include an example spelling out a scenario where both are used. As it is (including your explanation here) I just can't understand it.
Lloyd McKenzie (Mar 08 2017 at 18:09):
K. Example: You have a ProcedureRequest A that orders a surgery. Scheduling software creates a bunch of child ProcedureRequests, one of which (PR 'B') is to have some pre-surgical lab work done. A task is created seeking to get the lab work to be performed at a particular community lab. That task would be "basedOn" PR 'A' and would have a focus of PR 'B'. Does that make sense?
Josh Mandel (Mar 09 2017 at 22:10):
Maybe. Is it "based on PR A" because PR A is the root task that you find when climbing up the parent hierarchy from PR B? Or for some other reason?
Lloyd McKenzie (Mar 09 2017 at 22:42):
It's based on PR A because the legal authorization for doing the pre-surgical lab tests stems from the order for the procedure.
Lloyd McKenzie (Mar 09 2017 at 22:43):
"based on" is all about chain of responsibility
Lloyd McKenzie (Mar 09 2017 at 22:45):
Filler order D created by Lab Inc. is "based on" lab order C created by Dr. Smith. Lab order C exists "based on" the care plan B put together by Dr. Jones. Care plan B is "based on" recommendation A from decision support system XYZ.
Lloyd McKenzie (Mar 09 2017 at 22:47):
Thus some degree of fault/responsibility for Filler order D is held by Dr. Smith, Dr. Jones and decision support system XYZ, despite the fact that it was authored by Lab Inc.
Eric Haas (Mar 09 2017 at 23:23):
My simple example in the spec is a request and task for a lab spawns a request and task for a blood draw.
Josh Mandel (Mar 10 2017 at 21:24):
Argh. Every time I try to understand this I feel more and more lost.
Josh Mandel (Mar 10 2017 at 21:24):
I wish I could make a more constructive comment.
Last updated: Apr 12 2022 at 19:14 UTC
