1.3.6.1.4.1.19376.1.3.3.1.4: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Seknoop (talk | contribs)
854 edits
No edit summary
Seknoop (talk | contribs)
854 edits
No edit summary
Line 2: Line 2:


{{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.4|Trial|
{{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.4|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, when present, 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.


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 documented there in an <informationRecipient> 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 intended recipients of a laboratory document are intended for a reason which is not currently conveyed in the standard mark up.
The intended recipients of a laboratory document are highlighted in this specification as such rationale is not currently conveyed in the standard documentation. Intended recipients may be any of the follwing:
* Per request of ordering physician
* Per request of ordering physician
** unknown relationship to patient
** unknown relationship to patient
Line 43: Line 43:
           <state>GA</state>
           <state>GA</state>
           <postalCode>30333</postalCode>
           <postalCode>30333</postalCode>
      </receivedOrganization>
  </informationRecipient>
</pre>
</pre>
}}
}}


=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.3.1.4'/>=====
=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.3.1.4'/>=====
The <templateId> element identifies this <participant> as an intended recipient.  The templateId must have root='1.3.6.1.4.1.19376.1.3.3.1.4'.
The <templateId> element identifies this <participant> as an intended recipient.  The templateId shall have root='1.3.6.1.4.1.19376.1.3.3.1.4'.


=====&lt;id'/>=====
=====&lt;id/>=====
Unique identifier of this person (intended recipient) in the affinity domain shall be present.
Unique identifier of this person/organization (intended recipient) in the affinity domain shall be present.
 
=====&lt;addr/>=====
The address of this person/organization (intended recipient) shall be present.
 
=====&lt;telecom/>=====
The telecom of this person/organization (intended recipient) shall be present.
 
=====&lt;name/>=====
Either an <informationRecipient> or a <receivedOrganization> shall be present. In either case, the <name> sub-element shall be present.

Revision as of 14:20, 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

Intended Recipient 1.3.6.1.4.1.19376.1.3.3.1.4

Intended Recipients, when present, 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.

This module is out of the XDS-Lab Specification documented there in an <informationRecipient> 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 intended recipients of a laboratory document are highlighted in this specification as such rationale is not currently conveyed in the standard documentation. Intended recipients may be any of the follwing:

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


Uses

See Templates using Intended Recipient

Specification
Intended Recipient Example 
<ClinicalDocument
  ...
  <informationRecipient>
    <templateId root='1.3.6.1.4.1.19376.1.3.3.1.4'/>
    <intendedRecipient>
      <id extension="0000" root="1.19.6.11.13"/>
      <addr>
        <streetAddressLine>1600 Clifton Road</streetAddressLine>
        <city>Atlanta</city>
        <state>GA</state>
        <postalCode>30333</postalCode>
      </addr>
      <telecom value="tel: 404-639-3535"/>
      <informationRecipient>
        <name><family>Angulo</family><given>Fred</given></name>
      </informationRecipient>
      <receivedOrganization>
        <id extension="0000" root="1.19.6.11.13"/>
        <name>FoodNet</name>
        <telecom value="tel: 404-639-3535"/>
        <addr>
          <streetAddressLine>1600 Clifton Road</streetAddressLine>
          <city>Atlanta</city>
          <state>GA</state>
          <postalCode>30333</postalCode>
      </receivedOrganization>
   </informationRecipient>


<templateId root='1.3.6.1.4.1.19376.1.3.3.1.4'/>

The <templateId> element identifies this <participant> as an intended recipient. The templateId shall have root='1.3.6.1.4.1.19376.1.3.3.1.4'.

<id/>

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

<addr/>

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

<telecom/>

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

<name/>

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

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