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

Review and potentially revise compatibility rules for normative status of artifacts which contain content that is dependent on an external organization

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Mgmt Group
    • (many)
    • Hide

      In the section on interversion compatibility, add a note that "Compatibility rules described in this section are binding on HL7, but not on external bodies that define artifacts FHIR relies on. For example, if ISO were to make breaking changes to their language code table, that could impact FHIR in ways that do not comply with our compatibility rules. Most external specifications FHIR depends on are governed under their own compatibility rules which implementers can consult if they wish to better understand risks of change."

      Show
      In the section on interversion compatibility, add a note that "Compatibility rules described in this section are binding on HL7, but not on external bodies that define artifacts FHIR relies on. For example, if ISO were to make breaking changes to their language code table, that could impact FHIR in ways that do not comply with our compatibility rules. Most external specifications FHIR depends on are governed under their own compatibility rules which implementers can consult if they wish to better understand risks of change."
    • Lloyd McKenzie/Grahame Grieve: 4-0-1
    • Enhancement
    • Non-substantive
    • STU3

    Description

      We need to consider the compatibility rules for taking artifacts to normative when they contain content that is based on and dependent on decisions that are made by an external organization, over which we have no control. How does this affect the understanding of not having breaking changes for normative artifacts? In these cases updates to the content from decisions made by an external organization may break existing implementations that are using that content.

      An example of this is the terminology guidance in the "Using XXX with FHIR" pages. The "Using SNOMED CT with FHIR" page is currently maturity level 5 and may be a candidate for normative in a future release (it is not marked for that in R4). As SNOMED International updates their content (including deprecating codes) or potentially makes changes to the concept model or reference set contents and structures or the URI specification (as some examples) this could break the existing terminology service provider and consumer implementations.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhausam Robert Hausam
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: