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

CONF:1182-28474, 1182-28475 are being raised when the extension is being left off the Reporting Parameters template ID. I understand *why* they are being raised but this constraint is not documented in the 2016 CMS QRDA IG.

XMLWordPrintable

    • Icon: Certification Certification
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • Hide
      An undocumented QRDA-1 constraint is violated and generating an error message causing the submission to be rejected
      Show
      An undocumented QRDA-1 constraint is violated and generating an error message causing the submission to be rejected
    • DECC/PQRS
    • Dave Wade
    • 410-872-7652
    • Hide
      The 2016 CMS QRDA IG missed including the following constraints in the IG itself (though the constraints were contained in the schematron rules):
      1182-28472
      1182-28473
      1182-28474
      1182-28475
      1182-28476
      1182-28477

      The 2016 CMS QRDA IG Appendix made the correction and had documented these missing constraints in "section 5.1 Template Changes" on page 9. The 2016 Appendix is available at https://www.cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/Downloads/QRDA_Appendix2016.PDF
      Show
      The 2016 CMS QRDA IG missed including the following constraints in the IG itself (though the constraints were contained in the schematron rules): 1182-28472 1182-28473 1182-28474 1182-28475 1182-28476 1182-28477 The 2016 CMS QRDA IG Appendix made the correction and had documented these missing constraints in "section 5.1 Template Changes" on page 9. The 2016 Appendix is available at https://www.cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/Downloads/QRDA_Appendix2016.PDF

      In the 2016 Base QRDA-1 HL7 IG (i.e. "HL7 CDA® R2 Implementation Guide: Quality Reporting Document Architecture Category I (QRDA I); Release 1, DSTU Release 3 - US Realm, Draft Standard for Trial Use, Volume 2 - Templates and Supporting Material, June 2015") there is this constraint:

      ii. This structuredBody SHALL contain exactly one [1..1] component (CONF:1140-17090).
      1. This component SHALL contain exactly one [1..1] Reporting Parameters Section (identifier: urn:oid:2.16.840.1.113883.10.20.17.2.1) (CONF:1140-17092).

      This constraints says that a QDM-Based QRDA file must include a Reporting Parameter Section identified by template ID 2.16.840.1.113883.10.20.17.2.1 (without an extension) at xPath /ClinicalDocument/component/structuredBody/component/section.

      The 2016 CMS QRDA Supplemental IG defines a Reporting Parameter Section identified by template ID 2.16.840.1.113883.10.20.17.2.1 but with extension 2015-07-01. Unfortunately, this supplemental IG doesn't say where this section should be in a QRDA-1 file. However, if the Reporting Parameter section is not provided at the same xPath as 1140-17092 then this error is reported...

      This structuredBody SHALL contain at least one [1..*] component (CONF:1182-28474) such that it SHALL contain exactly one [1..1] Reporting Parameters Section - CMS EP & HQR (identifier: urn:hl7ii:2.16.840.1.113883.10.20.17.2.1:2015-07-01) (CONF:1182-28475).

      CONF:1182-28474, 1182-28475 is not documented anywhere. It should be documented in the 2016 CMS QRDA Supplemental IG. There are several other constraints just like this. All constraints that generate error or warning messages must be documented.

      This JIRA ticket is related to ticket QRDA-234 (which is status'ed as 'resolved'). However, that ticket questioned why 1182-28474, 1182-28475 (among others) were being raised. I understand why it is being raised. This ticket is saying that all constraints need to be documented.

      Any constraint that is in the ESAC provided Schematron rules needs to be documented either in the Base HL7 IG or the 2016 CMS QRDA Supplemental IG

            yanheras Yan Heras
            davewade David Wade (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: