Stream: conformance
Topic: effective[x] and data-absent-reason validation issues
Rob Hausam (Jan 25 2020 at 23:02):
In IPS we have been seeing this for a while, but I've looked into it in further detail and have confirmed that when the data-absent-reason extension is being used with effective[x] (in profiles on Observation, DiagnosticReport and MedicationStatement, particularly), that causes the example resource instances that are using either effectivePeriod (on all three resource profiles) or effectiveTiming (on the Observation profiles) to fail validation (but the validation does succeed if the instance uses effectiveDateTime or effectiveInstant). It is possible to get the instances with effectivePeriod or effectiveTiming to successfully validate, but that requires adding explicit element definitions for those slices. We've been able to work around this for IPS by adding those explicit slices, but it would be better to get this fixed.
Grahame Grieve (Jan 26 2020 at 11:17):
I don't understand this as described, and I don't see it in IPS?
Rob Hausam (Jan 26 2020 at 18:52):
@Grahame Grieve I worked around it by adding the explicit slices, so the error (or warning, whichever it is) isn't showing up at the moment. But this is one of the instances where the explicit slices were added (in this case for effectiveDateTime and effectivePeriod - only the slice for effectivePeriod is needed to resolve the issue, but the one for effectiveDateTime is also there for consistency). If you remove the effectivePeriod slice you will see the additional errors and the info messages that show up for the medicationStatement-39-07-1 and IPS-bundle-01 examples.
Grahame Grieve (Jan 26 2020 at 20:04):
so I deleted the portion marked new begin .. new end, and it made no difference?
Rob Hausam (Jan 26 2020 at 21:14):
doing that (or its equivalent) certainly makes a difference for me
I know that Giorgio has had the same issue - I'm pretty sure it's not just my local environment
I'll do some further exploration - and any other ideas are welcome
Rob Hausam (Jan 27 2020 at 06:05):
@Grahame Grieve When I comment out the MedicationStatement.effective[x]:effectivePeriod slice I get these errors in the auto-build (the same as in my local build):
/scratch/ig-build-temp-S9U62A/repo/examples/medicationStatement-39-07-1.xml Path Severity Message MedicationStatement/eumfh-39-07-1: MedicationStatement.effective.ofType(Period) error This element does not match any known slice for profile http://hl7.org/fhir/uv/ips/StructureDefinition/MedicationStatement-uv-ips and slicing is CLOSED MedicationStatement/eumfh-39-07-1: MedicationStatement.effective.ofType(Period).start information Could not verify slice for profile http://hl7.org/fhir/uv/ips/StructureDefinition/MedicationStatement-uv-ips
/scratch/ig-build-temp-S9U62A/repo/examples/IPS-bundle-01.xml Bundle/IPS-examples-Bundle-01: Bundle.entry[0].resource.section[1].entry[0] information This element does not match any known slice for the profile http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips Bundle/IPS-examples-Bundle-01: Bundle.entry[0].resource.section[1].entry[1] information This element does not match any known slice for the profile http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips Bundle/IPS-examples-Bundle-01: Bundle.entry[0].resource.section[1] error Profile http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips, Element 'Bundle.entry[0].resource.section[1].entry[medicationStatement]': minimum required = 1, but only found 0
When the slice MedicationStatement.effective[x]:effectivePeriod is present these error and information messages do not occur.
Grahame Grieve (Jan 29 2020 at 23:08):
fixed next release
Last updated: Apr 12 2022 at 19:14 UTC
