Stream: implementers
Topic: Validation: error on CodeableConcept.display?
Alexander Henket (Jan 23 2018 at 09:33):
I get an error on Simplifier whenever my instance does not have the same display name for a code as the ValueSet via binding in the profile says. Feels overly strict since display names could be different from system to system (language, preferred synonym etc.) Is there really display name match requirement?
Grahame Grieve (Jan 23 2018 at 15:50):
is this an instance validation error? or something else?
Alexander Henket (Jan 24 2018 at 15:26):
This is an instance validation error emitted by the .Net validator from Furore. I'm just wondering whether that is expected behavior.
Grahame Grieve (Jan 24 2018 at 22:37):
I think that should be a configuration choice
Alexander Henket (Jan 25 2018 at 12:21):
Sounds fair, but then one wonders what the default is. To error or not to error?
Alexander Henket (Feb 01 2018 at 19:13):
Found tidbit on validation.html: Coding/CodeableConcept bindings: Check that codes/displays provided in the Coding/CodeableConcept types are valid
So that explains why the validator signals a difference.
Alexander Henket (Feb 01 2018 at 19:16):
If I compare the statements on that page with versions.html there seems to be a conflict.
validation.html says
- Structure: Check that all the content in the resource is described by the specification, and nothing extra is present
- Cardinality: Check that the cardinality of all properties is correct (min & max)
version.html says
- In a typical scenario, mixed versions may need to exist, so applications SHOULD ignore elements that they do not recognize unless they are modifierExtensions.
Grahame Grieve (Feb 01 2018 at 19:22):
there's no conflict there - that's the difference between validation of technical correctness, and recommended behavior for an application
Ewout Kramer (Feb 16 2018 at 14:09):
Found tidbit on validation.html: Coding/CodeableConcept bindings: Check that codes/displays provided in the Coding/CodeableConcept types are valid
So that explains why the validator signals a difference.
Yep, that's why I did this. I don't like making too many things configurable, because that will mean your stuff might be valid on one server, and invalid on another, depending on all these configurable settings.
Last updated: Apr 12 2022 at 19:14 UTC
