Stream: terminology
Topic: Expanding extensionally defined ValueSets
Jose Costa Teixeira (Jun 15 2021 at 20:53):
Does expansion also apply to extensionally defined valuesets?
Jose Costa Teixeira (Jun 15 2021 at 20:56):
I don't think it makes sense (does it?), but I wonder if there is any rule against it
Grahame Grieve (Jun 15 2021 at 21:09):
Does extension also apply to extensionally defined valuesets
What's 'extension' in that sentence?
Jose Costa Teixeira (Jun 15 2021 at 21:19):
Expansion
Jose Costa Teixeira (Jun 15 2021 at 21:21):
(sorry, I already took my meds. perhaps i took too much - it's a nice vintage, so the dosage is in metric but I served it imperially :silence: )
Grahame Grieve (Jun 15 2021 at 21:32):
sure it does. why wouldn't it?
There are some extension value sets that cannot have a complete expansion
Jose Costa Teixeira (Jun 15 2021 at 21:36):
ok, if they are defined by extension* the $expand operation expands them anyway, I presume
(*by extension / by extent)
Jose Costa Teixeira (Jun 15 2021 at 21:39):
what would be the case for something that cannot have a complete expansion and is defined only extensionally? In that case, the expansion would be the same as the definition, right?
Grahame Grieve (Jun 15 2021 at 21:46):
attempts to expand these result in an error, though there is a way to ask for an incomplete expansion and the server may choose to do so, and there's an extension to mark incomplete expansions
Jose Costa Teixeira (Jun 15 2021 at 21:51):
meanwhile I checked what the IG publisher does .
It does expand those as well (and removes the definition altogether, only keeping the expansion). I guess that is a deliberate choice to leave only expansions, which works well for my purposes.
Grahame Grieve (Jun 15 2021 at 21:52):
it certainly should not do that. where are you looking?
Grahame Grieve (Jun 15 2021 at 21:52):
Oh you must be looking in the specially prepared expansions set?
Jose Costa Teixeira (Jun 15 2021 at 22:42):
yes, that is where I was looking at
Peter Jordan (Jun 16 2021 at 00:20):
Jose Costa Teixeira said:
Does expansion also apply to extensionally defined valuesets?
Perhaps you are just viewing this from an IG perspective? For ad-hoc requests, filtered expansions of extensional ValueSets are a commonplace.
Jose Costa Teixeira (Jun 16 2021 at 07:52):
Right. I was assuming an all-or-nothing because my valuesets were quite small and specific (and indeed for the IG).
Jim Steel (Jun 16 2021 at 23:03):
It probably also depends on how you are defining the extension of your ValueSet, i.e. in compose.include.concept or in expansion.contains. Personally I think the former is a much better way of doing it, but I suspect others will disagree.
Robert McClure (Jun 16 2021 at 23:12):
@Jim Steel It is my understanding that nothing should be in an expansion that is not defined as belonging in the compose. If someone feels differently I'd like to hear why and how. I strongly dislike "naked" expansion value sets and suggest no one use them. Hopefully for R5 we will provide base profiles similar to the cpg value set profiles that make creation of "expansion only" value sets clearer. None-the-less, any expansion only has to have a value set compose avaialble someplace, and follow the rules noted and must declare use of any extension.
Last updated: Apr 12 2022 at 19:14 UTC
