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

DSTU2 and R4 requirements hard to support

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Persuasive with Modification
    • Highest
    • US Core (FHIR)
    • 4.1.0 [deprecated]
    • Cross-Group Projects
    • STU
    • DSTU2 to R4 Conversion [deprecated]
    • 2.7.3
    • Hide

      Background: 

      The commenter is referencing this page

      DSTU2 to R4 Conversion

      There are several consideration for the user and developer experience when transitioning from FHIR DSTU2 to FHIR R4. To ensure a smoother upgrade path the following the guidance is provided.

      ...

       

      Rationale:

      We agree with the commenter that the intent of conformance expectations on this page is problematic and ambiguous and should be clarified

       

      Proposed Changes:

      See propose resolution for FHIR-35068

       

      Show
      Background:  The commenter is referencing this page DSTU2 to R4 Conversion Introduction Endpoint Discoverability No Guarantee that Resource IDs are Preserved Expectation that DSTU2 Data is Preserved in R4 Authorization Across Versions Introduction There are several consideration for the user and developer experience when transitioning from FHIR DSTU2 to FHIR R4. To ensure a smoother upgrade path the following the guidance is provided. ...   Rationale: We agree with the commenter that the intent of conformance expectations on this page is problematic and ambiguous and should be clarified   Proposed Changes: See propose resolution for FHIR-35068  
    • Isaac Vetter/Eric Haas: 10-0-0
    • Clarification
    • Non-substantive

    Description

      The combination of the following requirements is very hard to support:

      {quote "Servers SHALL make available the same information in DSTU2 and R4 where the more recent standard allows."

       This is a ­very­ demanding requirement, together with

      "Data SHALL not be degraded between versions.".

       Is the second requirement requirement in light of the first one?

      Attachments

        Issue Links

          is voted on by

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-27103 Negative - Bas van den Heuvel : 2022-Jan-FHIR US CORE R4.1 STU

          • Closed

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-30941 Negative - Ricardo Quintano : 2022-Jan-FHIR US CORE R4.1 STU

          • Closed

          Ballot Vote - The designation of a comment about a specification as related to an overall Ballot Submission BALLOT-30986 Negative - Chris Melo : 2022-Jan-FHIR US CORE R4.1 STU

          • Closed
          relates to

          Change Request - A request for a change that is more than a simple Technical Correction to one of HL7's specifications FHIR-35067 DSTU2 support not specified

          • Highest - This problem will block progress.
          • Published

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: