Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-23707

clarify that bindings strength does not mean you have to support them all.

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive
    • Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • Terminologies
    • Hide

      Proposed text to add in a new section: (after Example, and at the same level)

      Binding Strengths and Conformance Expectations (new section title)

      A binding strength of 'required' or 'extensible' does not indicate that ALL of the codes in the bound value set will be supported. It constrains the set of codes that are allowed to be shared. If systems flag an element as mustSupport, the minimumValueSet extension (http://hl7.org/fhir/R4/extension-elementdefinition-minvalueset.html)  SHOULD be used to identify a specific subset (possibly the full set) of the bound codes that must be supported by implementers.

      If no MIN value set is specified, then there is no guidance for implementers regarding which code(s) must be supported. However, at least one of the codes MUST be supported.

      ***************************************************************************************

      Note: the reference to mustSupport should include a link to the specification page.

      Show
      Proposed text to add in a new section: (after Example, and at the same level) Binding Strengths and Conformance Expectations (new section title) A binding strength of 'required' or 'extensible' does not indicate that ALL of the codes in the bound value set will be supported. It constrains the set of codes that are allowed to be shared. If systems flag an element as mustSupport, the minimumValueSet extension ( http://hl7.org/fhir/R4/extension-elementdefinition-minvalueset.html)   SHOULD be used to identify a specific subset (possibly the full set) of the bound codes that must be supported by implementers. If no MIN value set is specified, then there is no guidance for implementers regarding which code(s) must be supported. However, at least one of the codes MUST be supported. *************************************************************************************** Note: the reference to mustSupport should include a link to the specification page.
    • 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

          Activity

            People

              marc.duteau Marc Duteau
              ehaas Eric Haas
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: