XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Quality Reporting Document Architecture Category I (CDA)
    • 1.5.2.1
    • Clinical Quality Information
    • Templates
    • Hide
      translation is 0..* as specified in Problem Observation. Also the CDA R2 data type specification defines CD datatype translation attribute as 0..* and provides definition of translation.Translation is a set of other CDs that each translate the first CD into different code systems. Each element of the translation set was translated from the first CD. Each translation may, however, also contain translations. Thus, when a code is translated multiple times the information about which code served as the input to which translation will be preserved.1/27/2021Move/Second: Floyd Eisenberg/Paul DenningApprove/Oppose/Abstain: 12-0-0

      Show
      translation is 0..* as specified in Problem Observation. Also the CDA R2 data type specification defines CD datatype translation attribute as 0..* and provides definition of translation.Translation is a set of other CDs that each translate the first CD into different code systems. Each element of the translation set was translated from the first CD. Each translation may, however, also contain translations. Thus, when a code is translated multiple times the information about which code served as the input to which translation will be preserved.1/27/2021Move/Second: Floyd Eisenberg/Paul DenningApprove/Oppose/Abstain: 12-0-0
    • Floyd Eisenberg/Paul Denning: 12-0-0
    • Enhancement
    • Compatible, substantive

    Description

      Specification - Extended

      HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture I (QRDA I) Release 1, STU Release 5.2 - US Realm

      Document Description

      extended per TSC approval Jira TSC-68, errata by CTO

      Existing Wording

      For the QDM Diagnosis data type, Figure 112 of Vol 2, pg 460, shows "", which represents the QDM code attribute. Table 202 is silent about this.

      Proposed Wording

      There should be something between step 6 (CONF:4444-28499) and step 7 (CONF:4444-28501) to describe any constraints for representing the QDM code attribute. Especially need to clarify if cardinality is 1..1 or 1..*, and describe any semantics if one or more translation elements are used, for example, QRDA constraints should align with FHIR (QI-Core) Condition.code http://hl7.org/fhir/us/qicore/STU4/StructureDefinition-qicore-condition-definitions.html#Condition.code

      Attachments

        Activity

          People

            Unassigned Unassigned
            mitrep9g Paul Denning
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: