FHIR Chat · Adding data absent reason extension to a date · conformance

Stream: conformance

Topic: Adding data absent reason extension to a date


view this post on Zulip dr Kai U. Heitmann (Mar 19 2018 at 10:31):

How could I add the data absent reason extension to a date, e.g. Immunization.date in a profile?

view this post on Zulip Grahame Grieve (Mar 19 2018 at 10:36):

are you asking how to do it logically, or how to do it in Forge?

view this post on Zulip dr Kai U. Heitmann (Mar 19 2018 at 10:36):

Sorry, in Forge, preferably

view this post on Zulip Patrick Werner (Mar 19 2018 at 13:19):

(deleted)

view this post on Zulip Patrick Werner (Mar 19 2018 at 13:21):

you should be able to add it right away, but Forge is complaining:Screen-Shot-2018-03-19-at-14.17.49.png

view this post on Zulip Patrick Werner (Mar 19 2018 at 13:22):

Message : The selected extension definition is incompatible with the surrounding context. The extension is defined for the following context(s): * Severity: Warning Source : test Context : MyImmunization / date / test / Extension

view this post on Zulip Patrick Werner (Mar 19 2018 at 13:23):

this seems to be a bug in Forge? @Michel Rutten

view this post on Zulip Patrick Werner (Mar 19 2018 at 13:40):

i dug deeper into the issue, related GF:
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=3184&start=0
According to the current spec the data absent Extension should have the context of value[x], it is actual containing <context value="*"/>

view this post on Zulip Patrick Werner (Mar 19 2018 at 18:08):

so i assume this is wrong? Should i add a tracker item?

view this post on Zulip Grahame Grieve (Mar 19 2018 at 20:21):

this is already addressed in R4.

view this post on Zulip Grahame Grieve (Mar 19 2018 at 20:21):

I think forge will have to handle * specially in R3

view this post on Zulip Michel Rutten (Mar 26 2018 at 11:59):

Hi @dr Kai U. Heitmann, this warning could be a false flag. Forge tries to verify that the use of extensions complies to the extension context as defined in the extension definition. However the verification logic is somewhat simplified and does not cover all possible situations. So if you get a warning that doesn't make sense, then please ignore it. I will revisit the validation logic in Forge and test this specific situation.


Last updated: Apr 12 2022 at 19:14 UTC