Terug naar index  <<  Terug naar templates

active Template  Laboratory Results Validator

Id 1.3.6.1.4.1.19376.1.3.3.1.5
ref
XDLAB-
 		Ingangsdatum 2008‑08‑08
Status active Actief Versielabel 2017
Naam Laboratoryresultsvalidator Weergavenaam Laboratory Results Validator
Omschrijving
en-US 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".
Context Sibling nodes van template element met id 1.3.6.1.4.1.19376.1.3.3.1.5
Classificatie CDA header level template
Open/gesloten Open (ook andere dan gedefinieerde elementen zijn toegestaan)
Gebruikt door / Gebruikt
Gebruikt door 2 transacties en 18 templates, Gebruikt 0 templates
Gebruikt door als Naam Versie
bgz2017-transaction-34 Transactie final Aanmaken of bijwerken (2017) 2017‑01‑01
bgz2017-transaction-37 Transactie final Beschikbaarstellen BgZ (2017) 2018‑08‑30 09:30:49
2.16.840.1.113883.2.4.3.11.60.25.10.53 Containment pending Laboratory Report Data Processing Entry (2017) 2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.52 link draft Laboratory Specialty Section 2022‑12‑20 14:13:14
2.16.840.1.113883.2.4.3.11.60.42.10.3 link draft BgZ2017 StructuredBody SDTC 2022‑09‑23 15:59:52
2.16.840.1.113883.2.4.3.11.60.42.10.2 link draft BgZ2017 component SDTC 2022‑09‑23 16:01:20
2.16.840.1.113883.2.4.3.11.60.42.10.1 link draft CDA Basisgegevensset Zorg 2017 (BgZ) 2022‑09‑23 16:02:02
2.16.840.1.113883.2.4.3.11.60.25.10.52 link active Laboratory Specialty Section 2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.42.10.3 link retired BgZ2017 StructuredBody SDTC 2021‑11‑29
2.16.840.1.113883.2.4.3.11.60.42.10.1 link retired CDA Basisgegevensset Zorg 2017 (BgZ) 2021‑11‑29
2.16.840.1.113883.2.4.3.11.60.42.10.2 link retired BgZ2017 component SDTC 2021‑12‑21 16:54:21
2.16.840.1.113883.2.4.3.11.60.42.10.1 link retired CDA Basisgegevensset Zorg 2017 (BgZ) 2022‑05‑04
2.16.840.1.113883.2.4.3.11.60.42.10.3 link retired BgZ2017 StructuredBody SDTC 2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.54 link active Laboratory Report Item Section (2017) 2021‑10‑27
2.16.840.1.113883.2.4.3.11.60.25.10.53 Containment retired Laboratory Report Data Processing Entry (2017) 2018‑06‑05 14:42:09
2.16.840.1.113883.2.4.3.11.60.25.10.52 link cancelled Laboratory Specialty Section (2017) 2018‑06‑05 14:38:48
2.16.840.1.113883.2.4.3.11.60.42.10.3 link retired BgZ2017 StructuredBody SDTC 2017‑10‑24 18:08:26
2.16.840.1.113883.2.4.3.11.60.42.10.2 link retired BgZ2017 component SDTC 2017‑10‑24 18:07:08
2.16.840.1.113883.2.4.3.11.60.42.10.1 link retired CDA Basisgegevensset Zorg 2017 (BgZ) 2017‑10‑24 18:05:40
2.16.840.1.113883.2.4.3.11.60.25.10.54 link cancelled Laboratory Report Item Section (2017) 2018‑06‑05 14:44:20
Relatie Specialisatie: template 2.16.840.1.113883.10.12.107 CDA authenticator (2005‑09‑07)
ref
ad1bbr-
Voorbeeld
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>
Voorbeeld
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>
Item DT Card Conf Omschrijving Label
@typeCode
 		cs 1 … 1 F AUTHEN
hl7:templateId
 		II 1 … 1 M (Labdotstor)
@root
 		uid 1 … 1 F 1.3.6.1.4.1.19376.1.3.3.1.5
hl7:time
 		TS 1 … 1 R (Labdotstor)
hl7:signatureCode
 		CS 1 … 1 R (Labdotstor)
hl7:assignedEntity
 		1 … 1 R (Labdotstor)
@classCode
 		cs 0 … 1 F ASSIGNED
hl7:id
 		II 1 … * R (Labdotstor)
hl7:code
 		CE 0 … 1 R (Labdotstor)
hl7:addr
 		AD 1 … * R (Labdotstor)
hl7:telecom
 		TEL 1 … * R (Labdotstor)
  Schematron assert role red error  
  test not(hl7:assignedPerson) or hl7:assignedPerson/hl7:name  
  Melding the <name> sub-element of <assignedPerson> SHALL be present.  
hl7:assignedPerson
 		0 … 1 R (Labdotstor)
hl7:representedOrganization
 		0 … 1 R (Labdotstor)