Uploaded image for project: 'QRDA Issue Tracker'
  1. QRDA Issue Tracker
  2. QRDA-255

Associated templateid

XMLWordPrintable

    • Icon: QRDA-I Standard QRDA-I Standard
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • How to find new QRDA-2015 CAT I template Ids associated with which reports ?
    • Hide
      In general, to find out which QRDA templates correspond to QDM data types that are used in an eCQM specification, the HL7 QRDA Category I standard provides a mapping table that could serve as a look up table.

      For the QRDA-I DSTU R2, the mapping tables are provided in CDAR2_QRDA_DSTU_R2_2012JUL.docx, Appendix B – HQMF QDM data type to CDA Mapping Tables.

      For QRDA-I R1 DSTU R3, the mapping tables are provided in CDAR2_QRDA-I_R1_D3_2015MAY_V1_Introductory_Materials.docx, Appendix E - HQMF QDM data type to CDA Mapping Tables.

      You can download the HL7 QRDA-I DSTU R2 and QRDA-I R1 DSTU R3 standards from the HL7 website.
      Show
      In general, to find out which QRDA templates correspond to QDM data types that are used in an eCQM specification, the HL7 QRDA Category I standard provides a mapping table that could serve as a look up table. For the QRDA-I DSTU R2, the mapping tables are provided in CDAR2_QRDA_DSTU_R2_2012JUL.docx, Appendix B – HQMF QDM data type to CDA Mapping Tables. For QRDA-I R1 DSTU R3, the mapping tables are provided in CDAR2_QRDA-I_R1_D3_2015MAY_V1_Introductory_Materials.docx, Appendix E - HQMF QDM data type to CDA Mapping Tables. You can download the HL7 QRDA-I DSTU R2 and QRDA-I R1 DSTU R3 standards from the HL7 website.

      i.e. there are two templateid (2.16.840.1.113883.10.20.22.4.42, 2.16.840.1.113883.10.20.24.3.47) used in CMS154

      i have to required any source or any reference to identify which templated ID belongs to which reports.

      Plz help.

      Thanks

            yanheras Yan Heras
            darshan Darshan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: