FHIR Chat · Validator issue with inconsistent value set version

Stream: conformance

Topic: Validator issue with inconsistent value set version

Rob Hausam (Feb 26 2019 at 17:50):

When the validator tries to resolve the value set binding for Composition.confidentiality it appends the wrong version. In the base resource Composition.confidentiality has a required binding to http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification, with no version specified. Our IPS Composition profile doesn't change that, but in validating the IPS example bundle against the IPS ig when the validator tries to resolve the value set in the terminology service it appends the version string '|4.0.0', which doesn't exist. The only version of the v3-ConfidentialityClassification value set in the terminology service (or elsewhere) is '1', so the validator generates the warning:
Warning @ Bundle.entry[1].resource.confidentiality (line 41, col33) : ValueSet http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification|4.0.0 not found
I expect this may be happening because the validator is assuming that all value sets bound with required bindings will have their versions tied to the FHIR release? - but since this is a binding to a V3 value set that is clearly not true in this case. I don't know, but I wouldn't be surprised if this may be occurring in other places, as well. Anyway, we need to figure out how to solve this so that the value set can be resolved correctly. I'm wondering if setting the version to '1' in the profile would work (haven't tried that yet), but even if it does it wouldn't do anything to fix the underlying issue. @Grahame Grieve @Lloyd McKenzie?

Grahame Grieve (Mar 01 2019 at 05:33):

4.0.0 wasn't supposed to be appended to terminology.fhir.org value sets. Make a task - Ill be doing a run of IG publisher / validator issues next week (it will be my main focus, and I have an entire week at home - lovely)