FHIR Chat · answerOption extensions in contained ValueSets? · questionnaire

Stream: questionnaire

Topic: answerOption extensions in contained ValueSets?


view this post on Zulip Paul Lynch (Jun 18 2019 at 14:18):

If you have an answer list that is used multiple times (e.g. PHQ-9), it is nice to define that as a contained ValueSet and reference it to avoid duplication. However, we just noticed that some extensions (like optionPrefix) do not say in their "context of use" that they can be used on a ValueSet.expansion.contains item. Can they? If not, it greatly limits the usefulness of contained ValueSets. I think this is related to the issue @Astrid Corinna Wolff raised, but I didn't see a mention of a tracker item.

view this post on Zulip Eric Haas (Jun 18 2019 at 16:31):

here is an example of PHQ-9 doing just what Paul describes: http://sqlonfhir-stu3.azurewebsites.net/fhir/Questionnaire/questionnaire-example-phq9

view this post on Zulip Lloyd McKenzie (Jun 18 2019 at 16:45):

That's on the Questionnaire side. I think the issue was on the QuestionnaireResponse side.

view this post on Zulip Eric Haas (Jun 18 2019 at 17:06):

oops

view this post on Zulip Paul Lynch (Jun 18 2019 at 18:41):

@Lloyd McKenzie The issue I am raising here is on the Questionnaire.

view this post on Zulip Paul Lynch (Jun 18 2019 at 18:53):

@Eric Haas I see you are using valueset-ordinalValue, which in R4 became ordinalValue, and also dropped the context of ValueSet.expansion.contains (though I think that was accidental, if I remember correctly from some other post).

view this post on Zulip Eric Haas (Jun 18 2019 at 19:20):

this is a STU3 example. and yes probably is an older example

view this post on Zulip Paul Lynch (Jun 18 2019 at 19:21):

How important are these context of use statements on the extension pages? If a context isn't listed, does that mean we can't use it there?

view this post on Zulip Eric Haas (Jun 18 2019 at 19:27):

OK I see what you are saying . I extended the context of use in this example and in the ig. I think I mention that in the IG, but I have am guilty of doing this elsewhere too instead of redefining the extension I just stated that I am extending the context.

view this post on Zulip Paul Lynch (Jun 18 2019 at 19:48):

I think extending the context of use is better than redefining an extension (creating another version of it?) but I am wondering it if will cause problems for the contexts not to be all listed on the extension pages.

view this post on Zulip Eric Haas (Jun 18 2019 at 19:58):

I chose to do it and ask forgiveness later

view this post on Zulip Grahame Grieve (Jun 18 2019 at 19:59):

the validator will notice.... but you should still use the existing extension, and create a task

view this post on Zulip Eric Haas (Jun 18 2019 at 22:14):

I believe I have

view this post on Zulip Paul Lynch (Jun 19 2019 at 13:57):

I didn't see a tracker item for optionPrefix, so I added one: GF#22715


Last updated: Apr 12 2022 at 19:14 UTC