Stream: conformance
Topic: Validator bug on required bindings
Noemi Deppenwiese (May 27 2020 at 13:21):
I have a profile with a required binding on Specimen.type. When I validate an instance with multiple Codings, I get an error message about how no code is from the ValueSet on this example
"type": {
"coding": [
{
"code": "PLA",
"display": "Plasma (PLA)"
},
{
"system": "https://doi.org/10.1089/bio.2017.0109",
"code": "PL1",
"display": "Plasma, single spun (PL1)"
},
{
"system": "https://fhir.bbmri.de/CodeSystem/SampleMaterialType",
"code": "blood-plasma",
"display": "Plasma"
}
]
},
even though the last code (blood-plasma) is in the ValueSet. When I change the order so the required code comes first like this
"type": {
"coding": [
{
"system": "https://fhir.bbmri.de/CodeSystem/SampleMaterialType",
"code": "blood-plasma",
"display": "Plasma"
},
{
"code": "PLA",
"display": "Plasma (PLA)"
},
{
"system": "https://doi.org/10.1089/bio.2017.0109",
"code": "PL1",
"display": "Plasma, single spun (PL1)"
}
]
},
It validates sucessfully. AFAIK there is nothing in the spec about the order of codings in a CodeableConcept, so could this be a bug?
Grahame Grieve (May 29 2020 at 05:08):
order certainly shouldn't make any difference to outcome. If you can share the profile, valueset and code system, I can add it as a test case and make sure that the validator gets it right
Last updated: Apr 12 2022 at 19:14 UTC
