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

Need methodology around avoiding breaking changes in normative resources

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • (methodology)
    • Hide

      MnM will create a Confluence page (https://confluence.hl7.org/display/FHIR/Mitigating+Breaking+Changes) and will work on adding guidance to that page.

      Show
      MnM will create a Confluence page ( https://confluence.hl7.org/display/FHIR/Mitigating+Breaking+Changes)  and will work on adding guidance to that page.
    • Jean Duteau / Lloyd McKenzie : 8-0-0
    • Clarification
    • Non-substantive

    Description

      FMG would like MnM to develop options (and criteria for deciding between them) to handle situations where normative resources encounter situations that would ideally result in breaking changes.  For example, if an element was 0..1 and now needs to repeat, might add a new parallel element, deprecate the existing element and add a new one, use an extension, create a 'grouping' resource and reference that instead, etc.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: