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

Request for known issues / errata page for published versions

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Mgmt Group
    • Directory of Published Versions
    • Hide

      In R4B and following releases, we will add a link called "known issues" (with some text around it explaining what it's for).  The link will point to a release-specific Confluence page on the FHIR site.  Near-term plan is for that Confluence page to host the results of a Jira query for technical corrections that have been explicitly tagged as "technical-correction-update-approved".  We will communicate to work groups that only FMG has the authority to mark items in that way - but any technical correction can be submitted to the FMG to be so-tagged.

      That list would be the items that meet FMG's criteria for inclusion in a technical correction release if/when we get around to making one.

      Show
      In R4B and following releases, we will add a link called "known issues" (with some text around it explaining what it's for).  The link will point to a release-specific Confluence page on the FHIR site.  Near-term plan is for that Confluence page to host the results of a Jira query for technical corrections that have been explicitly tagged as "technical-correction-update-approved".  We will communicate to work groups that only FMG has the authority to mark items in that way - but any technical correction can be submitted to the FMG to be so-tagged. That list would be the items that meet FMG's criteria for inclusion in a technical correction release if/when we get around to making one.
    • Hans Buitendijk/Grahame Grieve: 4-0-0
    • Enhancement
    • Non-substantive
    • R5

    Description

      There is lag between discovering an issue and pushing out a build with a correction.  I believe we should have a page with known issues so that developers are not caught unaware.  This page would be outside the normal publication process (e.g., a Wiki).

      For example, the current 4.0.1 NPMs have errors in the Structure Definitions definitions for both Unsigned Int and Positive Int.  There is currently no mechanism to notify people that is the case (beyond Zulip, which requires that person to have an account and be in the correct stream).

      Attachments

        Activity

          People

            Unassigned Unassigned
            ginocanessa Gino Canessa
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: