The QRDA-1 is driven specific to patient information. Please consider the QRDA Incidence Report provided below. This specific QRDA-1 is provided for one particular patient with the name xxxx qqqq, the below sections will describe how and what information the header section of QRDA 1 will contain.

The specification of QRDA 1 and QRDA 3 are available in opensource under CMS provided sheets. please refer this link – CMS standards and specifications for QRDA1 and QRDA3

The below details are essential for the header start data. Since QRDA is built on top of CDA architecture, based on which it is essential to have the tag <ClinicalDocument>, the following tags becomes necessary.

<ClinicalDocument xmlns=”urn:hl7-org:v3″ xmlns:sdtc=”urn:hl7-org:sdtc” xmlns:voc=”urn:hl7-org:v3/voc” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<realmCode code=”US”/>
<typeId extension=”POCD_HD000040″ root=”2.16.840.1.113883.1.3″/>
<templateId extension=”2014-06-09″ root=”2.16.840.1.113883.10.20.22.1.1″/>
<templateId extension=”2014-12-01″ root=”2.16.840.1.113883.10.20.24.1.1″/>
<templateId extension=”2014-12-01″ root=”2.16.840.1.113883.10.20.24.1.2″/>
<templateId extension=”2015-07-01″ root=”2.16.840.1.113883.10.20.24.1.3″/>
<id extension=”1939″ root=”2.16.840.1.113883.3.2710.1.1.1″/>
<code code=”55182-0″ codeSystem=”2.16.840.1.113883.6.1″ codeSystemName=”LOINC” displayName=”Quality Measure Report”/>
<title>QRDA Incidence Report</title>
<effectiveTime value=”20161226034201″/>
<confidentialityCode code=”N” codeSystem=”2.16.840.1.113883.5.25″/>
<languageCode code=”en”/>

The individual patient details are available in the following section. This section is called <recordTarget>

<recordTarget>
<patientRole>
<id extension=”2035b4ac-e241-45a0-afcf-f015c7ff3cdf_1″ root=”2.16.840.1.113883.4.572″/>
<id extension=”2035b4ac-e241-45a0-afcf-f015c7ff3cdf_1″ root=”1.3.6.1.4.1.115″/>
<addr use=”HP”>
<streetAddressLine>874 Schuster Springs Oval, Suite 196</streetAddressLine>
<city>Lake Ladariustown</city>
<state>NH</state>
<postalCode>03689</postalCode>
<country>US</country>
</addr>
<telecom use=”WP” value=”tel:+1-781-271-3000″/>
<patient>
<name>
<given>xxxx</given>
<family>qqqqq</family>
</name>
<administrativeGenderCode code=”M” codeSystem=”2.16.840.1.113883.5.1″ codeSystemName=”HL7 AdministrativeGender”/>
<birthTime value=”19400306153000″/>
<raceCode code=”2131-1″ codeSystem=”2.16.840.1.113883.6.238″ codeSystemName=”CDC Race and Ethnicity” displayName=”otherRace”/>
<ethnicGroupCode code=”2135-2″ codeSystem=”2.16.840.1.113883.6.238″ codeSystemName=”CDC Race and Ethnicity” displayName=”Hispanic or Latino”/>
<languageCommunication>
<templateId assigningAuthorityName=”HITSP/C83″ root=”2.16.840.1.113883.3.88.11.83.2″/>
<templateId assigningAuthorityName=”IHE/PCC” root=”1.3.6.1.4.1.19376.1.5.3.1.2.1″/>
<languageCode code=”eng”/>
</languageCommunication>
</patient>
</patientRole>
</recordTarget>

In the above code structure id extension=”2035b4ac-e241-45a0-afcf-f015c7ff3cdf_1″ refers to the Patient ID. It is the unique identification of a patient.While the root values root=”2.16.840.1.113883.4.572″ and root=”1.3.6.1.4.1.115″ should not differ.

The Gender, ethnicity, race were determined by their corresponding LOINC codes.

The Gender codes are as follows :

  • M – Male
  • F – Female
  • U – Unknown

The Ethnicity codes will be as follows :

  • 2186-5 -> Non-Hispanic or Latino
  • 2135-2 -> Hispanic or Latino

The Race codes will be as follows :

  • 2054-5 -> Black
  • 2106-3 -> White
  • 1002-5 -> American Alaskan
  • 2028-9 -> Asian
  • 2076-8 -> Native Hawaii
  • 2131-1 -> other Race

The language code can be hard-coded and it will not change <languageCode code=”eng”/> it will be the static value.

Leave a Comment