Difference between revisions of "1.3.6.1.4.1.19376.1.3.3.1.7"

From IHE Wiki
Jump to navigation Jump to search
Line 2: Line 2:
 
<br>
 
<br>
 
Return to:[[PCC_TF-1/PHLAB/XDSLAB_Harmonization#CDA_Document_Content_Modules | Laboratory Content Modules]]
 
Return to:[[PCC_TF-1/PHLAB/XDSLAB_Harmonization#CDA_Document_Content_Modules | Laboratory Content Modules]]
 
{{Fixme| THIS PAGE IS A TOTAL MESS - work in progress!}}
 
  
 
{{HL7V3|Laboratory Performer|1.3.6.1.4.1.19376.1.3.3.1.7|Trial|
 
{{HL7V3|Laboratory Performer|1.3.6.1.4.1.19376.1.3.3.1.7|Trial|

Revision as of 13:27, 20 June 2008

Return to: XDS-LAB Harmonization
Return to: Laboratory Content Modules

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 Performer 1.3.6.1.4.1.19376.1.3.3.1.7

Laboratory Performers shall be recorded as performers in the CDA Header as well as in the structured body as demonstrated in the figure below. Documentation of laboratory performers can be done in multiple levels of the document to reflect performance scope. In the case where there is a single Laboratory Performer, this entity shall be documented in CDA header as shown. In the case where multiple Laboratory Performers participated in the lab testing process, they shall be documented in the structuredBody at the observation level.

These performers 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 a <performer> 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 Performer

Specification
Laboratory Performer Example
<!-- Single Laboratory Performer -->
<ClinicalDocument
  ...
  <documentationOf>
     <serviceEvent>
        <performer typeCode="PRF">
             <templateId root="1.3.6.1.4.1.19376.1.3.3.1.7"/>
             <assignedEntity>
                <id extension="kd83736" root="1.19.6.11.13"/>
                <addr>
                    <streetAddressLine>7000 Hosptial Drive</streetAddressLine>
                    <city>Chicago</city>
                    <state>IL</state>
                    <postalCode>60622</postalCode>
                    <country>USA</country>
                </addr>
                <telecom value="tel: 312-555-5555"/>
                <assignedPerson>
                    <name><family>Dawson</family>
<given>Kim</given><prefix>Dr.</prefix></name>
                </assignedPerson>
                <representedOrganization>
                   <id root="1.19.6.11.13"/>
                   <name>PRF Hospital Laboratory</name>
                   <telecom value="tel: 312-555-5555"/>
                   <addr><streetAddressLine>7000 Hosptial Drive</streetAddressLine><city>Chicago</city><state>IL</state><postalCode>60622</postalCode><country>USA</country></addr>
                 </representedOrganization>
            </assignedEntity>
         </performer>
     </serviceEvent>
  </documentationOf>

<!-- Multiple Laboratory Performer -->
  <structuredBody>
       ...
         <entry> 
            <act> 
               ...

               <entryRelationship> 
                 <observation> 
                  <performer typeCode="PRF">
                    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.7"/>
                    <assignedEntity>
                      <id extension="rm83747" root="1.19.6.11.13"/>
                      <addr>
                          <streetAddressLine>7000 Hosptial Drive</streetAddressLine>
                          <city>Chicago</city>
                          <state>IL</state>
                          <postalCode>60622</postalCode>
                          <country>USA</country>
                      </addr>
                      <telecom value="tel: 312-555-5555"/>
                      <assignedPerson>
                        <name><family>Trenton</family>
<given>Douglas</given><prefix>Dr.</prefix></name>
                      </assignedPerson>
                      <representedOrganization>
                        <id extension="rm83747" root="1.19.6.11.13"/>
                        <name>PRF Hospital Laboratory</name>
                        <telecom value="tel: 312-555-5555"/>
                        <addr><streetAddressLine>7000 Hosptial Drive</streetAddressLine><city>Chicago</city><state>IL</state><postalCode>60622</postalCode><country>USA</country></addr>
                      </representedOrganization>
                    </assignedEntity>
                  </performer>

                   </observation>
               </entryRelationship>

        ...
         </act>
      </entry>
       
      ...
    
    </structuredBody>


<performer/>
<templateId root="1.3.6.1.4.1.19376.1.3.3.1.7"/>

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

<time/>

The

<assignedEntity/>

An assignedEntity sub-element under the performer shall be present.

<id/>

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

<addr/>

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

<telecom/>

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

<name/>

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