2015May core #884 - extension, preferred and example are redundant

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Terminology Infrastructure
    • Terminologies
    • 1.23.0.2 Binding Str
    • Hide

      Just because they are not testable (or in the case of extensible, not automatically testable) does not mean that they are not useful. Example bindings are still useful to provide guidance on how to properly use elements for implementers. Implementation Guides are able to use required value set bindings and thereby become testable, and are encouraged to do so.

      Show
      Just because they are not testable (or in the case of extensible, not automatically testable) does not mean that they are not useful. Example bindings are still useful to provide guidance on how to properly use elements for implementers. Implementation Guides are able to use required value set bindings and thereby become testable, and are encouraged to do so.
    • Grahame Grieve / Rob McClure: 4-0-0
    • Correction

      Existing Wording: preferred Instances are encouraged, to draw from the specified codes for interoperability purposes but are not required to do so to be considered conformant

      example Instances are not expected or even encouraged to draw from the specified value set. The value set merely provides examples of the types of concepts intended to be included

      Comment:

      "extensible", "preferred" and "example" are identical in terms of conformance testing. The "example" binding seems to be redundant since implementers are not even expected to implement it. The examples can be part of "concept domains" if we decide to add the to FHIR terminology but an "example" binding seems unhelpful.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: