1.3.6.1.4.1.19376.1.3.3.1.6: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Newer edit →
Seknoop (talk | contribs)
854 edits
New page: Return to: PCC TF-1/PHLAB/XDSLAB Harmonization {{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.2|Trial| Intended Recipients shall be recorded as information recipients in the CDA...
 
Seknoop (talk | contribs)
854 edits
No edit summary
Line 1: Line 1:
Return to: [[PCC TF-1/PHLAB/XDSLAB Harmonization]]
Return to: [[PCC TF-1/PHLAB/XDSLAB Harmonization]]


{{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.2|Trial|
{{HL7V3|Referral Ordering Physician|1.3.6.1.4.1.19376.1.3.3.1.2|Trial|
Intended Recipients shall be recorded as information recipients 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.
Intended Recipients 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 documented there in an <informationRecipient> block. 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> block. 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 intended recipients of a laboratory document are intended for a reason which is not currently conveyed in the standard mark up.
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.
* Per request of ordering physician
** unknown relationship to patient
** patient's primary provider
** patient's specialist
* Per laboratory requirement
** infection control
** notifiable to public health program


The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.
The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.
Line 20: Line 13:
<ClinicalDocument
<ClinicalDocument
   ...
   ...
   <informationRecipient>
   <participant typeCode="REF">
     <templateId root='1.3.6.1.4.1.19376.1.3.3.1.1'/>
     <templateId root='TBD'/>
     <intendedRecipient>
    <time>
       <id extension="0000" root="1.19.6.11.13"/>
      <low value="20071104055700.0000-0500"/>
       <addr>
      <high value="20071104131600.0000-0500"/>
        <streetAddressLine>1600 Clifton Road</streetAddressLine>
    </time>
        <city>Atlanta</city>
     <associatedEntity classCode="PROV">
        <state>GA</state>
       <id extension="90573" root="1.19.6.11.13"/>
        <postalCode>30333</postalCode>
       <addr nullFlavor="UNK"/>
      </addr>
       <telecom nullFlavor="UNK"/>
       <telecom value="tel: 404-639-3535"/>
       <associatedPerson>
       <informationRecipient>
         <name><family>Patel</family><given>Kiran</given><prefix>Dr.</prefix></name>
         <name><family>Angulo</family><given>Fred</given></name>
       </associatedPerson>
       </informationRecipient>
       <scopingOrganization>
       <receivedOrganization>
         <id extension="rm83747" root="1.19.6.11.13"/>
         <id extension="0000" root="1.19.6.11.13"/>
         <name>Hospital</name>
         <name>FoodNet</name>
         <telecom nullFlavor="UNK"/>
         <telecom value="tel: 404-639-3535"/>
         <addr nullFlavor="UNK"/>
         <addr>
          <streetAddressLine>1600 Clifton Road</streetAddressLine>
          <city>Atlanta</city>
          <state>GA</state>
          <postalCode>30333</postalCode>
</pre>
</pre>
}}
}}
Line 48: Line 36:
=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.3.1.2'/>=====
=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.3.1.2'/>=====
The <templateId> element identifies this <participant> as a school or employer contact for validation of the content.  The templateId must have root='1.3.6.1.4.1.19376.1.3.3.1.1'.
The <templateId> element identifies this <participant> as a school or employer contact for validation of the content.  The templateId must have root='1.3.6.1.4.1.19376.1.3.3.1.1'.
=====&lt;time/>=====
This element represents the date and time the order was placed.

Revision as of 15:56, 7 May 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

Referral Ordering Physician 1.3.6.1.4.1.19376.1.3.3.1.2

Intended Recipients 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> block. 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='TBD'/>
    <time>
      <low value="20071104055700.0000-0500"/>
      <high value="20071104131600.0000-0500"/>
    </time>
    <associatedEntity classCode="PROV">
      <id extension="90573" root="1.19.6.11.13"/>
      <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.19.6.11.13"/>
        <name>Hospital</name>
        <telecom nullFlavor="UNK"/>
        <addr nullFlavor="UNK"/>


<templateId root='1.3.6.1.4.1.19376.1.3.3.1.2'/>

The <templateId> element identifies this <participant> as a school or employer contact for validation of the content. The templateId must have root='1.3.6.1.4.1.19376.1.3.3.1.1'.

<time/>

This element represents the date and time the order was placed.

Retrieved from "http://wiki.ihe.net/index.php?title=1.3.6.1.4.1.19376.1.3.3.1.6&oldid=17507"