2015May core #767 - Problems with the section "Mixing Custom and Standard Terminologies"

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Terminology Infrastructure
    • Profiling
    • 2.14.0.11
    • Hide

      update language according to suggestion

      Show
      update language according to suggestion
    • Grahame Grieve / Eric Haas: 4-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Comment:

      This section needs to be re-done. With regard to the table:

      1) Where is "binding type" defined? i.e., where is it declared in the "base specification" and what are the valid values? I think this is a vestige of previous versions of the spec. The bindings in the spec now seem to declare "Binding Strength" as defined in 1.23.0.2 Binding Strengths, not these "binding types".

      2) Where are these "profile properties" (conformance and extensible) defined? i.e., where are conformance and extensible values declared, and what are the valid values? Again, vestiges of previous versions? I would think if they're things you declare when creating a profile, that 2.14.0 Profiling FHIR would discuss them. But it doesn't. And the profiles that are part of the ballot have bindings that declare "binding strength" as defined in 1.23.0.2, not these properties. The discussions of "isExtensible" and "conformance" that used to be in DSTU1's 6.14.3.5 Binding Definitions and "incomplete" and "example" in 1.14.0.1 Controlling the use of Coded Values are gone now. If we aren't talking about conformance, extensible, incomplete, etc. any more and only about binding strength, this table needs to be deleted. If we still are talking about those things in addition to binding strength, they need to be defined and discussed.

            Assignee:
            Unassigned
            Reporter:
            toniki
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: