Stream: implementers
Topic: Task status
Nick George (Oct 23 2018 at 22:26):
hello, If I understand correctly, https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=19240 was just closed with the resolution that the profile is valid - if so that has some pretty profound implications, unless I'm misunderstanding something.
Nick George (Oct 23 2018 at 22:26):
I'm curious to know why it's considered valid
Jean Duteau (Oct 23 2018 at 22:29):
In your ticket, you say that component.code has been dropped but I'm not seeing that. It is in fact made mandatory for each of the slices.
Nick George (Oct 23 2018 at 22:30):
right, but it ONLY lists it on the slices
Nick George (Oct 23 2018 at 22:30):
why don't we also need the base element, Observation.component.code?
Nick George (Oct 23 2018 at 22:31):
(especially since slicing is open, meaning you can have an Observation.coponent that does not fit into one of the predefined slices)
Nick George (Oct 23 2018 at 22:36):
I would think there would have to be a 1-1 correspondence between elements with slices and unsliced elements (e.g., for an element with id "Observation.component:systolic.code" there would need to be an element with id "Observation.component.code")
Lloyd McKenzie (Oct 23 2018 at 22:43):
In the current build, Observation.component.code is there.
Lloyd McKenzie (Oct 23 2018 at 22:44):
Agree it wasn't there in the R3 publication, but the issue has been fixed. (And we don't generally go back and fix prior releases.)
Nick George (Oct 23 2018 at 23:07):
huh ok, so the resolution is more that it's not worth fixing in STU3, and just wait for R4?
Eric Haas (Oct 23 2018 at 23:08):
The resolution is based on R4. I was not aware that the tracker was refrncing STU3
Eric Haas (Oct 23 2018 at 23:09):
It is a proposed resolution and is up for a future vote
Nick George (Oct 23 2018 at 23:10):
ok thanks! I'm still new to the task resolution process so I'm a bit fuzzy on how that works!
Lloyd McKenzie (Oct 23 2018 at 23:55):
Trackers are always evaulated against the current build. No worries on being fuzzy. It's better to have a tracker item and not need it than have someone afraid to submit one that's necessary :)
Eric Haas (Oct 24 2018 at 02:18):
also it was good to look at the structuredefinition to confirm that the tooling was working.
rekha (Sep 27 2019 at 07:10):
Hi All,
My requirement is that i need to post a task resource onto the server and after posting again if i try to get back the resource the status of task need to be changed.Whether such functionality present in Fhir server??
Can anyone suggest me?
Thanks in advance.
Lloyd McKenzie (Sep 27 2019 at 15:48):
It's always possible for a server to change data, whether based on internal business rules or external intervention
Last updated: Apr 12 2022 at 19:14 UTC
