1.3.6.1.4.1.19376.1.3.3.1.4: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Seknoop (talk | contribs)
854 edits
New page: {{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.1|Trial| Intended Recipients shall be recorded as participants in the CDA Header as demonstrated in the figure below. These contacts s...
 
Srrenly (talk | contribs)
editor
842 edits
No edit summary
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{HL7V3|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.1|Trial|
Return to: [[PCC TF-1/PHLAB/XDSLAB Harmonization]]
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.
<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|Intended Recipient|1.3.6.1.4.1.19376.1.3.3.1.4|Trial|
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 following:
* 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.
|Example=
|Example=
<pre>
<pre>
<participant typeCode='PART'>
<ClinicalDocument>
   <templateId root='1.3.6.1.4.1.19376.1.5.3.1.2.2'/>
   ...
  <time>
  <informationRecipient>
    <low value=''/>
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.4"/>
    <high value=''/>
    <intendedRecipient>
  </time>
      <id extension="0000" root="1.3.6.1.4.1.19376.1.3.4"/>
  <associatedEntity classCode='CON'>
      <addr>
    <id root='' extension=''/>
        <streetAddressLine>1600 Clifton Road</streetAddressLine>
    <code code='EMPLOYER|SCHOOL|AFFILIATED' codeSystem='1.3.5.1.4.1.19376.1.5.3.3' codeSystemName='IHERoleCode'/>
        <city>Atlanta</city>
    <associatedPerson><name>…</name></associatedPerson>
        <state>GA</state>
    <scopingOrganization>
        <postalCode>30333</postalCode>
      <name>…</name>
      </addr>
      <telecom value='' use=''/>
      <telecom value="tel:404-639-3535"/>
      <addr>…</addr>
      <informationRecipient>
    </scopingOrganization>
        <name><family>Angulo</family><given>Fred</given></name>
  </associatedEntity>
      </informationRecipient>
</participant>
      <receivedOrganization>
        <id extension="0000" root="1.3.6.1.4.1.19376.1.3.4"/>
        <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>
  ...
</ClinicalDocument>
</pre>
</pre>
}}
}}


=====&lt;participant typeCode='PART'>=====
=====<templateId root="1.3.6.1.4.1.19376.1.3.3.1.4"/>=====
The typeCode of the participant shall be PART. 
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;templateId root='1.3.6.1.4.1.19376.1.5.3.1.2.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.5.3.1.2.2'.
=====<id/>=====
=====&lt;time><low value=' '/><high value=' '/></time>=====
Unique identifier of this person/organization (intended recipient) in the affinity domain SHALL be present.
The time element indicates the start and stop time range for this contact.  These dates shall correspond to the start and stop dates for employment, enrollment, or other affiliation with the organization described.
 
=====&lt;associatedEntity classCode='CON'>=====
=====<addr/>=====
The <associatedEntity> element provides the contact information (classCode='CON') for the school, employer or affiliated organization.
The address of this person/organization (intended recipient) SHALL be present.
 
=====<telecom/>=====
The telecom of this person/organization (intended recipient) SHALL be present.


=====&lt;code code='EMPLOYER|SCHOOL|AFFILIATED' codeSystem='1.3.5.1.4.1.19376.1.5.3.3' codeSystemName='IHERoleCode'/> =====
=====<name/>=====
The code value shall indicate whether the participant is the employer, school or other affiliated (e.g., volunteer) organization.  See also the {{ITmpRef|1.3.5.1.4.1.19376.1.5.3.3|IHE Role Code Vocabulary|1.3.5.1.4.1.19376.1.5.3.1.2.2}}
Either an <informationRecipient> or a <receivedOrganization> SHALL be present. In either case, the <name> sub-element SHALL be present.
=====&lt;associatedPerson><name>…</name></associatedPerson>=====
This element should be present. When present is shall provide the name of a contact person within the organization.
=====&lt;scopingOrganization><name>…</name><telecom value='' use=''/><addr>…</addr></scopingOrganization>=====
This element shall be present, and shall provide the name, address and telephone number of the organization.

Latest revision as of 14:55, 29 October 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

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 following:

  • 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.3.6.1.4.1.19376.1.3.4"/>
      <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.3.6.1.4.1.19376.1.3.4"/>
        <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>
   ...
</ClinicalDocument>


<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=25768"