Id1.3.6.1.4.1.19376.1.3.3.1.5
ref
XDLAB-
Effective Date2008‑08‑08
Statusactive ActiveVersion Label2017
NameLaboratoryresultsvalidatorDisplay NameLaboratory Results Validator
Description
The ClinicalDocument/authenticator element MAY be present. When present it represents the clinical expert who performed the clinical validation (see the entries “validator” and “clinical expert” in the glossary in LAB TF-1:1.11) of the report or of a subset of its results, also called the validator. This element SHALL be in accordance with the HL7 CDA R2 standard and further constrained by this specification to require the presence of name, addr and telecom.
There MAY be more than one validator of the report. All the validators SHALL appear in the report header as authenticator elements AND, in the case of multiple validators, each individuavalidator SHALL be associated with the particular sections of the report he or she validatedcase, the validator of a section SHALL also appear in the validator SHALL appear as a participant with typeCode="AUTHEN". Additionally, the laboratory results validator SHALL have the following:
  • <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/> - The templateId element identifies this authenticator or participant as a laboratory results validator. The templateId SHALL have root="1.3.6.1.4.1.19376.1.3.3.1.5".
ContextSibling nodes of template element with id 1.3.6.1.4.1.19376.1.3.3.1.5
ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 4 transactions and 23 templates, Uses 0 templates
Used by as NameVersion
2.16.840.1.113883.2.4.3.11.60.121.4.2.13.1Transactionfinal Registration2020‑09‑01
1.3.6.1.4.1.19376.1.5.3.1.4.11Transactiondraft IHE Immunization Content2017‑03‑30 09:28:26
1.2.40.0.34.77.4.30Transactiondeprecated de-DE ELGA CDA Dokument Laborbefund2011‑08‑31
1.2.40.0.34.77.4.104Transactiondraft Laborbefund (v2)2023‑05‑09 07:25:41
1.2.40.0.34.11.4Includedraft Laborbefund2023‑05‑08 13:51:02
1.2.40.0.34.11.1004Includecancelled Laborbefund2015‑09‑24
1.3.6.1.4.1.19376.1.3.1Containmentactive Laboratory Report Data Processing Entry (2017)2008‑08‑08
1.3.6.1.4.1.19376.1.3.1.5Containmentdraft BC Laboratory Isolate Organizer2016‑09‑29 14:55:37
1.3.6.1.4.1.19376.1.3.3Containmentactive Sharing Laboratory Reports (XD-LAB) Content Module (2017)2016‑07‑05
1.3.6.1.4.1.19376.1.3.3.2.1linkactive Laboratory Specialty Section (2017)2008‑08‑08
1.3.6.1.4.1.19376.1.3.3.2.2linkactive Laboratory Report Item Section (2017)2008‑08‑08
1.3.6.1.4.1.19376.1.5.3.1.1.18.1.2linkactive IHE Immunization Content Specification (2016)2017‑03‑20 09:59:31
2.16.840.1.113883.2.4.3.11.60.25.10.51Containmentdraft Lab2Zorg - Sharing Laboratory Reports (XD-LAB) (2017)2018‑06‑05 14:37:04
2.16.840.1.113883.2.4.3.11.60.25.10.51Containmentdraft Lab2Zorg - Sharing Laboratory Reports NL (XD-LAB) (2020)2022‑03‑30
2.16.840.1.113883.2.4.3.11.60.25.10.52linkcancelled Laboratory Specialty Section (2017)2018‑06‑05 14:38:48
2.16.840.1.113883.2.4.3.11.60.25.10.52linkactive Laboratory Specialty Section2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.52linkdraft Laboratory Specialty Section NL (2020)2022‑03‑30
2.16.840.1.113883.2.4.3.11.60.25.10.52linkdraft Laboratory Specialty Section2022‑12‑20 14:13:14
2.16.840.1.113883.2.4.3.11.60.25.10.53Containmentretired Laboratory Report Data Processing Entry (2017)2018‑06‑05 14:42:09
2.16.840.1.113883.2.4.3.11.60.25.10.53Containmentpending Laboratory Report Data Processing Entry (2017)2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.53Containmentdraft Laboratory Report Data Processing Entry NL (2020)2022‑03‑30
2.16.840.1.113883.2.4.3.11.60.25.10.54linkcancelled Laboratory Report Item Section (2017)2018‑06‑05 14:44:20
2.16.840.1.113883.2.4.3.11.60.25.10.54linkactive Laboratory Report Item Section (2017)2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.54linkdraft Laboratory Report Item Section NL (2020)2022‑03‑30
2.16.840.1.113883.2.4.3.11.60.66.10.77linkdraft Organizer Labbepalingen2022‑03‑30
2.16.840.1.113883.2.4.3.11.60.121.10.51linkactive Laboratory organizer or CDA2022‑03‑30
2.16.840.1.113883.3.1937.99.61.41.10.27Containmentdraft Laboratory Report Data Processing Entry_Sandbox-sm (2017)2019‑03‑27 16:09:06
RelationshipSpecialization: template 2.16.840.1.113883.10.12.107 CDA authenticator (2005‑09‑07)
ref
ad1bbr-
Example
Laboratory Results Single Validator Example
<authenticator>
  <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>  <time value="20080124171911.0425-0500"/>  <signatureCode code="S"/>  <assignedEntity>
    <id extension="274" root="1.3.6.1.4.1.19376.1.3.4"/>    <addr>
      <streetAddressLine>7000 Laboratory Drive</streetAddressLine>      <city>Chicago</city>      <state>IL</state>      <postalCode>60622</postalCode>      <country>USA</country>    </addr>    <telecom value="tel: 312-555-5555"/>    <assignedPerson>
      <name>
        <family>Technologist</family>        <given>274</given>      </name>    </assignedPerson>    <representedOrganization>
      <id extension="rm83747" root="1.3.6.1.4.1.19376.1.3.4"/>      <name>Laboratory</name>      <telecom value="tel: 312-555-5555"/>      <addr>
        <streetAddressLine>1234 Laboratory Drive</streetAddressLine>        <city>Chicago</city>        <state>IL</state>        <postalCode>60622</postalCode>        <country>USA</country>      </addr>    </representedOrganization>  </assignedEntity></authenticator>
Example
Laboratory Results Multiple Validators Example
<ClinicalDocument>
  <!-- .. -->
  <authenticator>
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>    <time value="20080124171911.0425-0500"/>    <signatureCode code="S"/>    <assignedEntity>
      <id extension="274" root="1.3.6.1.4.1.19376.1.3.4"/>      <addr>
        <!-- address 1 content here -->
      </addr>      <telecom value="tel: 312-555-5555"/>      <assignedPerson>
        <name>
          <!-- name 1 content here -->
        </name>      </assignedPerson>    </assignedEntity>  </authenticator>  <authenticator>
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>    <time value="20080124171911.0425-0500"/>    <signatureCode code="S"/>    <assignedEntity>
      <id extension="332" root="1.3.6.1.4.1.19376.1.3.4"/>      <!-- .. -->
    </assignedEntity>  </authenticator>  <!-- .. -->
  <structuredBody>
    <!-- .. -->
    <section>
      <!-- .. -->
      <entry>
        <act>
          <!-- .. -->
          <entryRelationship>
            <observation>
              <!-- .. -->
              <participant typeCode="AUTHEN">
                <time value="20080123211000.007-0500"/>                <participantRole>
                  <id extension="332" root="1.3.6.1.4.1.19376.1.3.4"/>                  <addr>
                    <!-- address 2 content here -->
                  </addr>                  <telecom value="tel: 312-555-5555"/>                  <playingEntity>
                    <name>
                      <!-- name 2 content here -->
                    </name>                  </playingEntity>                </participantRole>              </participant>            </observation>          </entryRelationship>        </act>      </entry>    </section>    <section>
      <!-- .. -->
      <entry>
        <act>
          <!-- .. -->
          <entryRelationship>
            <observation>
              <!-- .. -->
              <participant typeCode="AUTHEN">
                <time value="20080123211000.007-0500"/>                <participantRole>
                  <id extension="274" root="1.3.6.1.4.1.19376.1.3.4"/>                </participantRole>              </participant>            </observation>          </entryRelationship>        </act>      </entry>    </section>  </structuredBody></ClinicalDocument>
ItemDTCardConfDescriptionLabel
@typeCode
cs1 … 1FAUTHEN
hl7:templateId
II1 … 1MLabodotsator
@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.3.1.5
hl7:time
TS1 … 1RLabodotsator
hl7:signatureCode
CS1 … 1RLabodotsator
hl7:assignedEntity
1 … 1RLabodotsator
@classCode
cs0 … 1FASSIGNED
hl7:id
II1 … *RLabodotsator
hl7:code
CE0 … 1RLabodotsator
hl7:addr
AD1 … *RLabodotsator
hl7:telecom
TEL1 … *RLabodotsator
 Schematron assertrolered error 
 testnot(hl7:assignedPerson) or hl7:assignedPerson/hl7:name 
 Messagethe <name> sub-element of <assignedPerson> SHALL be present. 
hl7:assignedPerson
0 … 1RLabodotsator
hl7:representedOrganization
0 … 1RLabodotsator