Safeguards for modifier extensions should apply to all modifiers - 2016-09 core #38

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Modeling & Methodology
    • Extensibility
    • 2.20.0.2 extension
    • Hide

      The FHIR specification documents information needed to be known by those using FHIR (including defining profiles). It does not document rules for defining the resources themselves. That information is found in HL7's FHIR wiki, which is targeted to the work groups. This documentation already provides guidance on the use of modifier elements, though it is not identical to the rules for introducing modifier extensions.

      Show
      The FHIR specification documents information needed to be known by those using FHIR (including defining profiles). It does not document rules for defining the resources themselves. That information is found in HL7's FHIR wiki, which is targeted to the work groups. This documentation already provides guidance on the use of modifier elements, though it is not identical to the rules for introducing modifier extensions.
    • Ron Shapiro/Grahame Grieve: 2-0-0
    • Enhancement

      Comment:

      Section 2.20.0.2 articulates safeguards for using modifier extensions – avoiding where possible, prohibiting processing of resources with unknown modifier extensions, and prohibiting use of modifiers within data elements. It seems that modifications should adopt these safeguards whether in extensions or not. E.g., absence of a condition or observation is easily indicated by an explicit element; embedding the modification within the element (e.g., in certain members of a value set) creates risk.

      Summary:

      Safeguards for modifier extensions should apply to all modifiers

            Assignee:
            Unassigned
            Reporter:
            Jay Lyle
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: