Stream: terminology
Topic: Codeable Concept Required Binding and Text element
Linda (Oct 13 2021 at 22:18):
Someone brought to my attention today that if you have a Required Binding on an element (CodeableConcept) that you can just put somethin in text to meet the requirement. For example, in PDEX Plan Net, specialty is a codeableConcept bound as required to Individual and Group Specialities. However if you got an instance where the sender only sends specialty.text as anything, it would be valid. Is that the intent? i.e. would they have to profile the coding to be required to insure they always get a specialty code?
Grahame Grieve (Oct 13 2021 at 22:19):
you can make coding minimum cardinality 1 if you want to require a code
Linda (Oct 13 2021 at 22:27):
I read this as well - from terminology page; http://hl7.org/fhir/R4/terminologies.html for Required binding
The following rules apply when required bindings are used with the CodeableConcept data type:
at least one Coding element SHALL be present
one of the Coding values SHALL be from the specified value set
text can be provided as well, and is always recommended, but is not an acceptable substitute for the required code
Lloyd McKenzie (Oct 14 2021 at 02:50):
You cannot meet the requirement by just putting in text. If there's a required binding, then you must have a coding from the value set for the element to be present. Anything else is non-conformant (and should be failing the validator)
Lloyd McKenzie (Oct 14 2021 at 02:50):
That's quite clear in the spec.
Lloyd McKenzie (Oct 14 2021 at 02:51):
The following rules apply when required bindings are used with the CodeableConcept data type:
at least one Coding element SHALL be present
one of the Coding values SHALL be from the specified value set
text can be provided as well, and is always recommended, but is not an acceptable substitute for the required code
Lloyd McKenzie (Oct 14 2021 at 02:52):
https://hl7.org/fhir/terminologies.html#required
Last updated: Apr 12 2022 at 19:14 UTC
