Stream: argonaut
Topic: CodeableConcept required bindings
Michelle (Moseman) Miller (Dec 01 2016 at 14:25):
I missed the last Argonaut call, but I see in the notes that there was a decision to go with Option B (Text 0..1 with Invariant saying you got to supply text if no code.) -- but that seems to conflict with the latest version of the spec (http://build.fhir.org/terminologies.html#code) that now says:
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
Michelle (Moseman) Miller (Dec 01 2016 at 15:52):
Ignore my question -- I have since learned that the required binding is moving down to the coding level, so that avoids the CodeableConcept implications noted above.
Eric Haas (Dec 01 2016 at 17:06):
Thanks MIchelle, I just noticed that Verification status is required and STu3 already has the invarients too. Will update the profiles. Also I haven't tried implementing Option B yet in the profile. Will let everyone know if I run into any issues.
Last updated: Apr 12 2022 at 19:14 UTC
