Difference between revisions of "1.3.6.1.4.1.19376.1.3.3.1.5"

From IHE Wiki
Jump to navigation Jump to search
Line 54: Line 54:
 
In the body,  
 
In the body,  
  
=====<time/>====
+
=====<time/>=====
 
The <time> element shall be present and shall represent the point in time of laboratory result validation.
 
The <time> element shall be present and shall represent the point in time of laboratory result validation.
  

Revision as of 14:32, 12 June 2008

Return to: PCC TF-1/PHLAB/XDSLAB Harmonization

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 as demonstrated in the figure below.

note about header/body relationship, documenting verifiers in body (TODO)

These contacts 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
<ClinicalDocument
  ...
    <authenticator>
      <templateId root="TBD"/>
      <time value="20080124171911.0425-0500"/>
      <signatureCode code="S"/>
      <assignedEntity>
        <id extension="274" root="1.19.6.11.13"/>
        <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.19.6.11.13"/>
          <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>

  ...

  <structuredBody>
       ...
         <entry>
            <act>
               <entryRelationship>
                   <observation>
                      <participant typeCode='AUTHEN'>


<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'.

In the body,

<time/>

The

<signatureCode>

The <signatureCode> element shall be present and the code attribute shall be set to the value 'S' to indicate that this result set is validated and signed.

<assignedEntity>

An assignedEntity shall be present.

<id/>

Unique identifier of this person/organization (authenticator) in the affinity domain shall be present.

<addr/>

The address of this person/organization (authenticator) shall be present.

<telecom/>

The telecom of this person/organization (authenticator) shall be present.

<name/>

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