Template

Show index

Template XeH Results Validator 2020‑10‑28 10:55:16

Id2.16.840.1.113883.3.1937.99.61.67.10.13Effective Date2020‑10‑28 10:55:16
Statusdraft DraftVersion Label
NameXeHCDAAuthenticatorDisplay NameXeH 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".
ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 2 templates, Uses 0 templates
Used by as NameVersion
2.16.840.1.113883.3.1937.99.61.67.10.9Includedraft XeH Laboratory Report (wip)2020‑10‑24 18:01:42
2.16.840.1.113883.3.1937.99.61.67.10.10Includedraft XeH Diagnostic Imaging Report (wip)2020‑10‑24 18:18:56
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
hl7:authenticator
RXeHCdotsator
@typeCode
cs1 … 1FAUTHEN
hl7:templateId
II1 … 1MXeHCdotsator
@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.3.1.5
hl7:time
TS1 … 1RXeHCdotsator
hl7:signatureCode
CS1 … 1RXeHCdotsator
hl7:assignedEntity
1 … 1RXeHCdotsator
@classCode
cs0 … 1FASSIGNED
hl7:id
II1 … *RXeHCdotsator
hl7:code
CE0 … 1RXeHCdotsator
hl7:addr
AD1 … *RXeHCdotsator
hl7:telecom
TEL1 … *RXeHCdotsator
 Schematron assertrolered error 
 testnot(hl7:assignedPerson) or hl7:assignedPerson/hl7:name 
 Messagethe <name> sub-element of <assignedPerson> SHALL be present. 
hl7:assignedPerson
0 … 1RXeHCdotsator
hl7:representedOrganization
0 … 1RXeHCdotsator