Stream: implementers
Topic: Expansion of valuesets using IG tool
Sadiq Saleh (Feb 16 2017 at 15:28):
When building with the IG tool, is it by design that the expanded values for valuesets are not included in the JSON file in output (under expansion), but is visible on the generated webpages?
Lloyd McKenzie (Feb 16 2017 at 16:23):
Yes. The expectation is that you'll run the expansions when you need them, as they can change over time as the underlying code systems change.
Sadiq Saleh (Feb 16 2017 at 18:06):
I guess it is my lack of understanding, but I would have expected that with a certain version of an IG that there should be an expanded valueset that goes with it? Thus the valueset resources used to build the IG wouldn't have the expansion but the built version of the IG would have a static valueset expansion to go with it.
Or is the understanding that the valueset will continue to evolve over time even if an IG stays static?
Grahame Grieve (Feb 16 2017 at 20:24):
it depends how you specify the value set
Grahame Grieve (Feb 16 2017 at 20:24):
lots of authors expect and require that the value set is dynamic - that the values will change over time.
Grahame Grieve (Feb 16 2017 at 20:25):
the correct way to do this is to specify the value set completely - version specific includes - and then it will always expand correctly.
Grahame Grieve (Feb 16 2017 at 20:26):
but there is also a practice to publish the expansions along with the spec, and we're not doing this. You could create a task for us to do that, but it won't happen in the next few weeks
Sadiq Saleh (Feb 17 2017 at 15:44):
Thanks for your responses. Will add a task to the pile!
Sadiq Saleh (Feb 17 2017 at 15:49):
Done: Tracker http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12855
Last updated: Apr 12 2022 at 19:14 UTC
