1.3.6.1.4.1.19376.1.3.3.1.5

From IHE Wiki
Jump to navigation Jump to search

Return to: PCC TF-1/PHLAB/XDSLAB Harmonization
Return to: Laboratory Content Modules
Return to:Laboratory Report Summary Specification

Development Only

The PCC Wiki Content is used only for development of IHE PCC Content. The Normative content of the PCC Technical Framework and the current supplements can be found at http://www.ihe.net/Technical_Framework/index.cfm#PCC

Trial.gif Laboratory Result Verifier 1.3.6.1.4.1.19376.1.3.3.1.5

Laboratory Result Verifiers SHALL be recorded as authenticators in the CDA Header and as participants with typeCode equal to 'AUTHEN' in the structured body as demonstrated in the figure below. If there is a single Laboratory Result Verifier for the entire document, then it need only be documented as an authenticator in the CDA header. In the case where multiple Laboratory Result Verifiers participated in the verification of document content, each verifier SHALL appear in the header as an authenticator and appear in the document within their scope of verification (at section or entry/observation level).

These participants SHALL conform to the General Constraints found in HL7 CRS: 2.1.1 with respect to the requirements for name, address, telephone numbers and other contact information.

This module is out of the XDS-Lab Specification and documented there in an <authenticator> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability.

The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.


Uses

See Templates using Laboratory Result Verifier

Specification
Laboratory Result Verifier Example
<!-- Single Authenticator -->
<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>
         <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>
          <suffix>MT ASCP</suffix>
          <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>
  ...
</ClinicalDocument>


<!-- Multiple Authenticators -->
<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"/>
      <addr>
        <!-- address 2 content here -->
      </addr>
      <telecom value="tel:312-555-5555"/>
      <assignedPerson>
        <name>
          <!-- name 2 content here -->
        </name>
      </assignedPerson>
    </assignedEntity>
  </authenticator>
  ...
  <structuredBody>
    ...
    <entry>
      <act>
        ...
        <entryRelationship>
          <observation>
            ...
            <participant typeCode='AUTHEN'>
              <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>
              <time value="20080123211000.007-0500"/>
              <participatRole>
                <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>
        <entryRelationship>
          <observation>
            ...
            <participant typeCode='AUTHEN'>
              <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>
              <time value="20080123211000.007-0500"/>
              <participatRole>
                <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"/>
                <playingEntity>
                  <name>
                    <!-- name 1 content here -->
                  </name>
                </playingEntity>
              </participatRole>
            </participant> 
          </observation>
        </entryRelationship>
        ...
      </act>
    </entry>
    ...  
  </structuredBody>
</ClinicalDocument>


<authenticator/>
<templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>

The <templateId> element identifies this <authenticator> as a laboratory result verifier. The templateId SHALL have root='1.3.6.1.4.1.19376.1.3.3.1.5'.

The

<signatureCode/>

In the case of the <authenticator>, the <signatureCode> element SHALL be present and SHALL have code='S' to indicate 'signed'.

<assignedEntity/>

An assignedEntity sub-element under the authenticator SHALL be present.

<id/>

Unique identifier of this person/organization (lab result verifier) in the affinity domain SHALL be present.

<addr/>

The address of this person/organization (lab result verifier) SHALL be present.

<telecom/>

The telecom of this person/organization (lab result verifier) SHALL be present.

<name/>

Either an <assignedPerson> or a <representedOrganization> SHALL be present. In either case, the <name> sub-element SHALL be present.


<participant @typeCode='AUTHEN'/>
@typeCode='AUTHEN'

The <participant> element representing a laboratory result verifier SHALL have typeCode set to 'AUTHEN'.

&<templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>

The <templateId> element identifies a <participant> as a laboratory result verifier. The templateId SHALL have root='1.3.6.1.4.1.19376.1.3.3.1.5'.

The

<participatRole/>

In the body, the participatRole under the participant SHALL be present.

<id/>

Unique identifier of this person/organization (lab result verifier) in the affinity domain SHALL be present.

&<addr/>

The address of this person/organization (lab result verifier) SHALL be present.

<telecom/>

The telecom of this person/organization (lab result verifier) SHALL be present.

<name/>

A <playingEntity> shall be present and it's <name> sub-element SHALL be present.