Stream: TSMG
Topic: Change in Static Bound Valueset Precept
Robert McClure (Oct 25 2021 at 16:55):
TSC has pushed review and improvement of a precept to clarify governance of any change in a static bound valueset. This was initially discussed on the SC e-Vote 2021-10-11 and you can tell by the comments that it would be best if TSMG took this on. TSC has requested TSMG define a precept for this and send it back to TSC. Note there are comments on the precept proposal page also.
Lloyd McKenzie (Oct 25 2021 at 18:51):
What do you mean by "static bound valueset"? That's not a terminology we use in FHIR. If you mean a version-specific valueset binding, then I guess I agree, though there are some subtleties here. When in edit mode, I can change the contents of an extensional valueset 50 times. It only gets a new 'version' when I officially publish it as a release. I.e. we don't version stuff in the CI-build.
Lloyd McKenzie (Oct 25 2021 at 18:52):
Also, if the value set reference is not version-specific, then there's no need to re-version the referencing resource when the referenced valueset changes.
Robert McClure (Oct 26 2021 at 18:08):
I agree it does not make much sense. Look at the link I included above. This came from old SGB work that we need to clean up.
Lloyd McKenzie (Oct 26 2021 at 19:46):
I did look at the link. My concern is that the terminology used in the precept doesn't reflect the language we use in our standards
Robert McClure (Oct 27 2021 at 14:43):
@Lloyd McKenzie Again we agree. I added a comment to that effect. Please provide the text for the precept that we can propose back to TSC. I'm hoping we can make that text apply to any product family. Can you help?
Lloyd McKenzie (Oct 27 2021 at 15:03):
What is your objective with the precept?
Robert McClure (Oct 27 2021 at 15:45):
To be clear, this is not "my precept" it is something old from SGB. My understanding is that the concern is that if a standard changes a Static (or required for FHIR) binding, the standard should have a version change to help identify the breaking change that occurred. I sense you would not define something this specific and reply upon version change for breaking change and just note that this is an example of a breaking change?
Last updated: Apr 12 2022 at 19:14 UTC
