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

How to identify deprecated elements.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • (many)
    • Hide

      1. We will update the code system build.fhir.org/codesystem-standards-status.html to correct the definition for 'Deprecated' (can be informed by the content here: https://build.fhir.org/versions.html#std-process and here: https://build.fhir.org/versions.html#deprecation

      2. Will also update that code system to have the code 'Withdrawn'

      3. Will define a new "deprecation-reason" extension that can appear inside the standards-status.valueCode of type markdown that allows conveying the reason for deprecation and what to do instead.

      4. Will put the https://build.fhir.org/extension-structuredefinition-standards-status.html and deprecation-reason extensions on the elements of Bundle that have been deprecated and ensure that they render correctly in the build (e.g. proper color/code, flyover for reason)

      Show
      1. We will update the code system build.fhir.org/codesystem-standards-status.html to correct the definition for 'Deprecated' (can be informed by the content here: https://build.fhir.org/versions.html#std-process and here: https://build.fhir.org/versions.html#deprecation 2. Will also update that code system to have the code 'Withdrawn' 3. Will define a new "deprecation-reason" extension that can appear inside the standards-status.valueCode of type markdown that allows conveying the reason for deprecation and what to do instead. 4. Will put the https://build.fhir.org/extension-structuredefinition-standards-status.html and deprecation-reason extensions on the elements of Bundle that have been deprecated and ensure that they render correctly in the build (e.g. proper color/code, flyover for reason)
    • Grahame Grieve/Bas van den Heuvel: 9-0-1
    • Correction
    • Non-substantive
    • R5

    Description

      The specification indicates on several locations that certain things (fields, codes, ...) are deprecated (e.g. outcome code in Bundle.search.code).

      This is mentioned in the text of the resource but cannot be easily identified when looking at the code or field. 

      We agree on and support a mechanism that adds a visual element to the things that have been deprecated. Preferably with a link/description to the rationale.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: