Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
STU3
-
Terminology Infrastructure
-
Terminologies
-
-
Rob McClure/Grahame Grieve: 21-3-4
-
Clarification
-
Non-substantive
-
R5
Description
Clarify that system are required and extensibel bindings don't mean you have to support all the codes ( unless profiled using min valueset exension ) by adding to each binding where it is stated "the concept in this element SHALL be from the specified value set" Lloyd's dulcet phrasing : "However, it's possible a system will not "support" some or even most of the codes in the valueset."
For background see Zulip chat here: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/required.20binding.20meaning.20for.20source.20system
I think currenltly this is implied and may be lost on implementers unfamiliar with terminology and binding , principles, especialy when using terms like 'required'
Attachments
Issue Links
- relates to
-
FHIR-23702 State that required bindings do not mean that systems must support all codes
- Resolved - No Change