Stream: implementers
Topic: ValueSet binding strength required constraints
Mike Lohmeier (Jul 21 2021 at 17:36):
Is it possible to extend an existing ValueSet defined in a resource with binding strength of required to include new values? The Publisher tool is not finding my new ValueSet values for a field when trying to constrain the field to my new ValueSet. I've tried explicitly including all valid values from the parent ValueSet in my ValueSet. Is it possible to extend a required binding strength ValueSet in this manner or is this a bug in the publisher tool?
Jean Duteau (Jul 21 2021 at 17:47):
no. if a binding is required and points to an existing value set, the only thing that can introduce new values is to have the existing value set expanded to include the values. you can't override it with a different value set. From the spec 4.1.5.1:
When an element is bound to a required value set, derived profiles may state rules on which codes can be used, including removing codes from allowed use, but cannot specify new or additional codes for these elements.
You could slice the element if it is a CodeableConcept to add a new slice that used your value set, but you're stuck with the required binding to have to send one of the existing codes.
Daniel Venton (Jul 21 2021 at 18:03):
If you think that a required binding valueset doesn't have all the values needed to describe the concept, petition the owner of the valueset to add more values. Just for fun, I'd be interested in what value set you think needs new value (and what they are). Perhaps you are trying to put the wrong concept into that attribute?
Mike Lohmeier (Jul 22 2021 at 16:00):
Thanks, in this particular case we inadvertently referenced the wrong code in our fsh files.
Last updated: Apr 12 2022 at 19:14 UTC
