Uploaded image for project: 'CDA Specification Feedback'
  1. CDA Specification Feedback
  2. CDA-1409

STU-1409 - versioning scheme

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Applied (View Workflow)
    • High
    • Resolution: Persuasive
    • Public Health Case Report - Electronic Initial Case Report (eICR) (CDA)
    • 1.1.1
    • Public Health
    • Templates
    • Hide

      Persuasive made 2019-01-15 00:00:00.0 with vote Laura Conn/Sunanda McGarvey: 18-0-0//(Impact: Compatible, substantive; Category: Correction; Version: null)//Will update as suggested, with guidance and examples and will also make setId and versionNumber required elements. Disposition Date: 01/15/2019 Mover/Seconder: Laura Conn/Sunanda McGarvey Vote: 18-0-0

      Show
      Persuasive made 2019-01-15 00:00:00.0 with vote Laura Conn/Sunanda McGarvey: 18-0-0//(Impact: Compatible, substantive; Category: Correction; Version: null)//Will update as suggested, with guidance and examples and will also make setId and versionNumber required elements. Disposition Date: 01/15/2019 Mover/Seconder: Laura Conn/Sunanda McGarvey Vote: 18-0-0
    • Laura Conn/Sunanda McGarvey : 18-0-0
    • Correction
    • Compatible, substantive

    Description

      Specification - Extended

      HL7 CDA® R2 Implementation Guide: Public Health Case Report, Release 2: the Electronic Initial Case Report (eICR), Release 1, STU Release 1.1 - US Realm

      Document Description

      extended per TSC Tracker 12574, extension TSC GF 15952, JIRA TSC-29, TSC-123

      Existing Wording

      The current 1.1 eICR IG does not include conformance constraints to address a versioning scheme for a set of eICR documents, such as a new eICR replacing an eICR document (i.e. An eICR contains an error or omission that is subsequently replaced by the corrected eICR). Without it there will not be any indication that a replacement or “child” eICR document is replacing its parent eICR document.

      Proposed Wording

      The MAY contain zero or one clinicalDocument.setId and clinicalDocument.versionNumber should be changed to a SHALL contain one clinicalDocument.setId and clinicalDocument.versionNumber. The initial version must have a ClinicalDocument.versionNumber set equal to "1". The version.Number must be incremented by one when a report is replaced. A replacement document gets a new globally unique ClinicalDocument.id value. The parent eICR document and all of its eICR replacement documents use the same value for ClinicalDocument.setId.

      Attachments

        Activity

          People

            Unassigned Unassigned
            justine_maxwell Justine Maxwell
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: