1.3.6.1.4.1.19376.1.3.3.1.1/static-2017-06-07T000000

Id	1.3.6.1.4.1.19376.1.3.3.1.1 ref XDLAB-	Effective Date	2017‑06‑07
Status	Active	Version Label	2017
Name	Humanpatientrecordtarget	Display Name	Human Patient
Description ClinicalDocument/recordTarget SHALL be present and SHALL conform to the Human Patient, Non-Human Subject or Human Patient with Non-Human Subject templates defined below. There are three varieties of laboratory reports: Human (patient): The document reports laboratory observations produced on specimens collected exclusively from the patient.  Non-Human Subject: The document reports laboratory observations produced on specimens collected from a non-human material (e.g. water, milk…) or living subject (e.g. animal). Human (patient) paired with Non-Human Subject: The document reports laboratory observations produced on a non-human specimen with a relationship to a human patient, (e.g. peanut butter eaten by a patient, a ferret that bit a patient). Human Patient In accordance with the HL7 CDA R2 standard and further constrained by this specification, XD-LAB requires the presence of name, addr and telecom for all entities in the document including the human patient. Additionally, the following SHALL be present. An optional templateId with root="1.3.6.1.4.1.19376.1.3.3.1.1" - The templateId element identifies this recordTarget as a human patient. id - The patientRole/id SHALL be present. administrativeGenderCode - The patientRole/patient/administrativeGenderCode SHALL be present. birthTime - The patientRole/patient/birthTime SHALL be present.
Classification	CDA Header Level Template
Open/Closed	Open (other than defined elements are allowed)
Relationship	Specialization: template 2.16.840.1.113883.10.12.101 CDA recordTarget (2005‑09‑07) ref ad1bbr-
Example	Human Patient Example a <recordTarget typeCode="RCT">   <patientRole classCode="PAT">     <id extension="sw54321" root="1.3.6.1.4.1.19376.1.3.4"/>    <addr>       <streetAddressLine>1313 Mockingbird Lane</streetAddressLine>      <city>Janesville</city>      <state>WI</state>      <postalCode>53545</postalCode>      <country>USA</country>    </addr>    <telecom value="tel: 608-555-5555"/>    <patient classCode="PSN">       <name>         <family>Winters</family>        <given>Shelly</given>      </name>      <administrativeGenderCode code="F"/>      <birthTime value="19401213000000.0000-0500"/>    </patient>  </patientRole></recordTarget>
Example	Human Patient Example b: In the event a unit of information about the patient is not known or has been de-identified, the use of nullFlavor is appropriate <recordTarget typeCode="RCT">   <patientRole classCode="PAT">     <id extension="sw54321" root="1.3.6.1.4.1.19376.1.3.4"/>    <addr>       <streetAddressLine nullFlavor="MSK"/>      <!-- masked value -->       <city nullFlavor="MSK"/>      <!-- masked value -->       <state nullFlavor="MSK"/>      <!-- masked value -->       <postalCode>53545</postalCode>      <country>USA</country>    </addr>    <telecom nullFlavor="UNK"/>    <!-- unknown value -->     <patient classCode="PSN">       <name nullFlavor="MSK"/>      <!-- masked value -->       <administrativeGenderCode code="F"/>      <birthTime value="19401213000000.0000-0500"/>    </patient>  </patientRole></recordTarget>
Item DT Card Conf Description Label hl7:recordTarget 1 … * R (Hum...get) hl7:patientRole 1 … 1 R (Hum...get) hl7:id II 1 … * R (Hum...get) hl7:addr AD 1 … * All persons (including the patient) and organizations mentioned in the document SHALL provide elements name, addr and telecom. (Hum...get) hl7:telecom TEL 1 … * All persons (including the patient) and organizations mentioned in the document SHALL provide elements name, addr and telecom. (Hum...get) hl7:patient 1 … 1 (Hum...get) hl7:id II 0 … 1 (Hum...get) hl7:name PN 1 … * (Hum...get) hl7:administrative​Gender​Code CE 1 … 1 R (Hum...get) hl7:birthTime TS 1 … 1 R (Hum...get)