Difference between revisions of "1.3.6.1.4.1.19376.1.3.3.1.6"

From IHE Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Return to: [[PCC TF-1/PHLAB/XDSLAB Harmonization]]
 
Return to: [[PCC TF-1/PHLAB/XDSLAB Harmonization]]
 +
<br>
 +
Return to:[[PCC_TF-1/PHLAB/XDSLAB_Harmonization#CDA_Document_Content_Modules | Laboratory Content Modules]]
 +
<br>
 +
Return to:[[1.3.6.1.4.1.19376.1.3.3|Laboratory Report Summary Specification]]
  
 
{{HL7V3|Referral Ordering Physician|1.3.6.1.4.1.19376.1.3.3.1.6|Trial|
 
{{HL7V3|Referral Ordering Physician|1.3.6.1.4.1.19376.1.3.3.1.6|Trial|
Referral Ordering Physicians shall be recorded as participants in the CDA Header as demonstrated in the figure below.  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.
+
Referral Ordering Physicians SHALL be recorded as participants in the CDA Header as demonstrated in the figure below.  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 a <participant> 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.
 
This module is out of the XDS-Lab Specification and documented there in a <participant> 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.
Line 14: Line 18:
 
   ...
 
   ...
 
   <participant typeCode="REF">
 
   <participant typeCode="REF">
     <templateId root='1.3.6.1.4.1.19376.1.3.3.1.6'/>
+
     <templateId root="1.3.6.1.4.1.19376.1.3.3.1.6"/>
 
     <time>
 
     <time>
 
       <low value="20071104055700.0000-0500"/>
 
       <low value="20071104055700.0000-0500"/>
Line 20: Line 24:
 
     </time>
 
     </time>
 
     <associatedEntity classCode="PROV">
 
     <associatedEntity classCode="PROV">
       <id extension="90573" root="1.19.6.11.13"/>
+
       <id extension="90573" root="1.3.6.1.4.1.19376.1.3.4"/>
 
       <addr nullFlavor="UNK"/>
 
       <addr nullFlavor="UNK"/>
 
       <telecom nullFlavor="UNK"/>
 
       <telecom nullFlavor="UNK"/>
Line 27: Line 31:
 
       </associatedPerson>
 
       </associatedPerson>
 
       <scopingOrganization>
 
       <scopingOrganization>
         <id extension="rm83747" root="1.19.6.11.13"/>
+
         <id extension="rm83747" root="1.3.6.1.4.1.19376.1.3.4"/>
 
         <name>Hospital</name>
 
         <name>Hospital</name>
 
         <telecom nullFlavor="UNK"/>
 
         <telecom nullFlavor="UNK"/>
Line 37: Line 41:
 
}}
 
}}
 
===== @typeCode='REF' =====
 
===== @typeCode='REF' =====
The typeCode of this participant shall be set to 'REF'
+
The typeCode of this participant SHALL be set to 'REF'
  
=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.3.1.6'/>=====
+
=====<templateId root="1.3.6.1.4.1.19376.1.3.3.1.6"/>=====
The <templateId> element identifies this <participant> as a Referral Ordering Physician.  The templateId must have root='1.3.6.1.4.1.19376.1.3.3.1.6'.
+
The <templateId> element identifies this <participant> as a Referral Ordering Physician.  The templateId SHALL have root='1.3.6.1.4.1.19376.1.3.3.1.6'.
  
======&lt;time/>======
+
=====<time/>=====
This element represents the date and time the order was placed. Time may be present.
+
This element represents the date and time the order was placed. Time MAY be present.
  
 
=====<associatedEntity/>=====
 
=====<associatedEntity/>=====
The <assiciatedEntity> element shall be present.
+
The <assiciatedEntity> element SHALL be present.
  
 
====== @classCode='PROV' ======
 
====== @classCode='PROV' ======
The classCode of this <associatedEntity> shall be set to 'PROV'
+
The classCode of this <associatedEntity> sSHALL be set to 'PROV'.
  
======&lt;id/>======
+
======<id/>======
Unique identifier of this person (referral ordering physician) in the affinity domain shall be present.
+
Unique identifier of this person (referral ordering physician) in the affinity domain SHALL be present.
  
======&lt;addr/>======
+
======<addr/>======
The address of this person (referral ordering physician) shall be present.
+
The address of this person (referral ordering physician) SHALL be present.
  
======&lt;telecom/>======
+
======<telecom/>======
The telecom of this person (referral ordering physician) shall be present.
+
The telecom of this person (referral ordering physician) SHALL be present.
  
======&lt;name/>======
+
======<name/>======
An <associatedPerson> shall be present. The <name> sub-element of the <associatedPerson> shall be present.
+
An <associatedPerson> shall be present. The <name> sub-element of the <associatedPerson> SHALL be present.

Latest revision as of 11:41, 3 July 2008

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 Referral Ordering Physician 1.3.6.1.4.1.19376.1.3.3.1.6

Referral Ordering Physicians SHALL be recorded as participants in the CDA Header as demonstrated in the figure below. 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 a <participant> 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 referral ordering physician(s) of a laboratory document represent the person(s) who placed the order fulfilled by this laboratory report summary. In HL7 v2.5 messaging structures, this element corresponds to the 'ordering provider' represented by OBR-16 or ORC-12.

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 Referral Ordering Physician

Specification
Referral Ordering Physician Example
<ClinicalDocument>
  ...
  <participant typeCode="REF">
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.6"/>
    <time>
      <low value="20071104055700.0000-0500"/>
      <high value="20071104131600.0000-0500"/>
    </time>
    <associatedEntity classCode="PROV">
      <id extension="90573" root="1.3.6.1.4.1.19376.1.3.4"/>
      <addr nullFlavor="UNK"/>
      <telecom nullFlavor="UNK"/>
      <associatedPerson>
        <name><family>Patel</family><given>Kiran</given><prefix>Dr.</prefix></name>
      </associatedPerson>
      <scopingOrganization>
        <id extension="rm83747" root="1.3.6.1.4.1.19376.1.3.4"/>
        <name>Hospital</name>
        <telecom nullFlavor="UNK"/>
        <addr nullFlavor="UNK"/>
     </scopingOrganization>
    </associatedEntity>
  </participant>


@typeCode='REF'

The typeCode of this participant SHALL be set to 'REF'

<templateId root="1.3.6.1.4.1.19376.1.3.3.1.6"/>

The <templateId> element identifies this <participant> as a Referral Ordering Physician. The templateId SHALL have root='1.3.6.1.4.1.19376.1.3.3.1.6'.

This element represents the date and time the order was placed. Time MAY be present.

<associatedEntity/>

The <assiciatedEntity> element SHALL be present.

@classCode='PROV'

The classCode of this <associatedEntity> sSHALL be set to 'PROV'.

<id/>

Unique identifier of this person (referral ordering physician) in the affinity domain SHALL be present.

<addr/>

The address of this person (referral ordering physician) SHALL be present.

<telecom/>

The telecom of this person (referral ordering physician) SHALL be present.

<name/>

An <associatedPerson> shall be present. The <name> sub-element of the <associatedPerson> SHALL be present.