Stream: conformance
Topic: Standard VitalSigns example failing to validate
Morten Ernebjerg (Feb 12 2019 at 13:24):
I noticed that some of the standard Observation examples (STU3) fail to validate with the standalone validator. I did this:
1. Get the latest validator from Nexus (I was using *org.hl7.fhir.validation.cli-3.8.0-20190211.175101-5.jar*)
2. Get the standard STU3 height Observation example (which declares conformance to the VitalSigns profile): http://hl7.org/fhir/stu3/observation-example-body-height.xml
3. Run the validator on it with -version 3.0.1.
This gives the following error
Error @ Observation (line 1, col80) : If there is no component or related element then either a value[x] or a data absent reason must be present [(component.empty() and related.empty()) implies (dataAbsentReason or value)]
I see that constraint in the profile (vs-3), but I thought that would only apply if Observation.component was actually present (given that constraint vs-2 ensures that either a value or a data absent reason is given if there are no components).
Conversely, the online Simplifier validator does not throw this error, but instead complains that
Code 'in' from system 'http://unitsofmeasure.org' does not exist in valueset 'http://hl7.org/fhir/ValueSet/ucum-vitals-common'
Who's right here?
Michel Rutten (Feb 12 2019 at 13:33):
Hi @Morten Ernebjerg, I'll ask our colleague @Ewout Kramer to investigate, he maintains the validator logic.
Grahame Grieve (Feb 12 2019 at 13:51):
the FHIRPaths are in error. I'm working on a technical correction to fix them
Morten Ernebjerg (Feb 12 2019 at 14:09):
Sounds good :+1:
Mirjam Baltus (Feb 16 2019 at 09:37):
Hi @Morten Ernebjerg, I have created an issue on the .Net library for this: https://github.com/ewoutkramer/fhir-net-api/issues/872.
Morten Ernebjerg (Feb 16 2019 at 19:21):
Thanks, @Mirjam Baltus !
Last updated: Apr 12 2022 at 19:14 UTC
