1.3.6.1.4.1.19376.1.3.1: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Seknoop (talk | contribs)
No edit summary
Srrenly (talk | contribs)
No edit summary
 
(10 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 | XDS-LAB Harmonization]]
<br>
<br>
Return to:
Return to:[[PCC_TF-1/PHLAB/XDSLAB_Harmonization#CDA_Document_Content_Modules | Laboratory Content Modules]]
[[1.3.6.1.4.1.19376.1.3.3.2.1| Laboratory Speciality Section]]


{{HL7V3|Lab Report Data Processing Entry|1.3.6.1.4.1.19376.1.3.1|Trial|At least one Lab Report Data Processing Entry shall be present. The Entry shall contain a single Act sub-element. This Act is hereafter referred to as the 'Specimen Act'.   
{{HL7V3|Laboratory Report Data Processing Entry|1.3.6.1.4.1.19376.1.3.1|Trial|At least one Lab Report Data Processing Entry shall be present. The <entry> SHALL contain a single <act> sub-element. This <act> is hereafter referred to as the '''Specimen Act'''.   
<br>


For a public health lab report, there shall be exactly one Entry with one 'Specimen Act' per Section. Each 'Specimen Act' shall contain at least three EntryRelationship elements; one representing the Specimen Received Date/Time and one representing the Reportable Condition; and the third (or more) representing the laboratory test result(s).
<br>


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>
          <entry typeCode="DRIV">
<entry typeCode="DRIV">
            <templateId extension="Lab.Report.Data.Processing.Entry" root="1.3.6.1.4.1.19376.1.3"/>
  <templateId root="1.3.6.1.4.1.19376.1.3"/>
            <act classCode="ACT" moodCode="EVN">
  <act classCode="ACT" moodCode="EVN">
              <statusCode code="completed"/>
    <statusCode code="completed"/>
 
    ...
              ... entry contents ...
  </act>
          </entry>
</entry>
</pre>
</pre>
}}
}}


=====&lt;templateId root='1.3.6.1.4.1.19376.1.3.1'/>=====
=====<templateId root="1.3.6.1.4.1.19376.1.3.1"/>=====
The <templateId> element identifies this <entry> as a Lab Report Data Processing Entry. The templateId shall have root='1.3.6.1.4.1.19376.1.3.1'.
The <templateId> element identifies this <entry> as a Laboratory Report Data Processing Entry. The templateId SHALL be recorded as shown above, root="1.3.6.1.4.1.19376.1.3.1".
 
=====<act classCode="ACT" moodCode="EVN"/>=====
=====<act classCode="ACT" moodCode="EVN"/>=====
There shall be one <font face="courier new">Act</font> sub-element. This sub-element uses the following modules conforming to the following requirements.
There shall be one <font face="courier new">Act</font> sub-element. This <act> is hereafter referred to as the Specimen Act. This sub-element uses the following modules conforming to the following requirements. These modules, when present, shall be recorded as <entryRelationship> elements under the '''Specimen Act'''.
 
{|style='background-color:#7f7f7f;' border='1' cellpadding="5" cellspacing="0" width="100%"
{|style='background-color:#7f7f7f;' border='1' cellpadding="5" cellspacing="0" width="100%"
|+ '''Modules unique to the document body'''
!Sub-Element
!Sub-Element
!Opt
!Opt
Line 46: Line 45:
|1.3.6.1.4.1.19376.1.3.1.1.3
|1.3.6.1.4.1.19376.1.3.1.1.3
|R2
|R2
|[[1.3.6.1.4.1.19376.1.3.1.1.3 | Outbreak Idenrifier]]
|[[1.3.6.1.4.1.19376.1.3.1.1.3 | Outbreak Identifier]]
|- style='background-color:#ffffff;' align='center'
|- style='background-color:#ffffff;' align='center'
|1.3.6.1.4.1.19376.1.3.1.2
|1.3.6.1.4.1.19376.1.3.1.2
Line 55: Line 54:
|R2
|R2
|[[1.3.6.1.4.1.19376.1.3.1.3 | Specimen Received]]
|[[1.3.6.1.4.1.19376.1.3.1.3 | Specimen Received]]
|- style='background-color:#ffffff;' align='center'
| tbd
| R2
| Non-Human Subject
|- style='background-color:#ffffff;' align='center'
| tbd
| O
| laboratory performer? (same as header??)
|- style='background-color:#ffffff;' align='center'
| tbd
| O
| laboratory equipment instance
|- style='background-color:#ffffff;' align='center'
| tbd
| O
| laboratory result verifier? (same as header??)
|- style='background-color:#ffffff;' align='center'
|- style='background-color:#ffffff;' align='center'
|1.3.6.1.4.1.19376.1.3.1.4
|1.3.6.1.4.1.19376.1.3.1.4
Line 87: Line 70:
|O
|O
|[[1.3.6.1.4.1.19376.1.5.3.1.4.2 | Annotation Comment (PCC)]]
|[[1.3.6.1.4.1.19376.1.5.3.1.4.2 | Annotation Comment (PCC)]]
|}
<br>
{|style='background-color:#7f7f7f;' border='1' cellpadding="5" cellspacing="0" width="100%"
|+ '''Modules with counterparts in the cda header'''
!Sub-Element
!Opt
!Description
|- style='background-color:#ffffff;' align='center'
| 1.3.6.1.4.1.19376.1.3.3.1.2.1
| R2
| [[1.3.6.1.4.1.19376.1.3.3.1.2.1 |Non-Human Subject]]
|- style='background-color:#ffffff;' align='center'
| 1.3.6.1.4.1.19376.1.3.3.1.3.1
| R2
| [[1.3.6.1.4.1.19376.1.3.3.1.3.1|Human Patient with Non-Human Subject]]
|- style='background-color:#ffffff;' align='center'
| 1.3.6.1.4.1.19376.1.3.3.1.5
| O
| [[1.3.6.1.4.1.19376.1.3.3.1.5|Laboratory Result Verifier]]
|- style='background-color:#ffffff;' align='center'
| 1.3.6.1.4.1.19376.1.3.3.1.7
| O
| [[1.3.6.1.4.1.19376.1.3.3.1.7|Laboratory Performer]]
|}
|}

Latest revision as of 13:26, 24 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

Laboratory Report Data Processing Entry 1.3.6.1.4.1.19376.1.3.1

At least one Lab Report Data Processing Entry shall be present. The <entry> SHALL contain a single <act> sub-element. This <act> is hereafter referred to as the Specimen Act.


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 Report Data Processing Entry

Specification
Laboratory Report Data Processing Entry Example
<entry typeCode="DRIV">
  <templateId root="1.3.6.1.4.1.19376.1.3"/>
  <act classCode="ACT" moodCode="EVN">
    <statusCode code="completed"/>
    ...
  </act>
</entry>


<templateId root="1.3.6.1.4.1.19376.1.3.1"/>

The <templateId> element identifies this <entry> as a Laboratory Report Data Processing Entry. The templateId SHALL be recorded as shown above, root="1.3.6.1.4.1.19376.1.3.1".

<act classCode="ACT" moodCode="EVN"/>

There shall be one Act sub-element. This <act> is hereafter referred to as the Specimen Act. This sub-element uses the following modules conforming to the following requirements. These modules, when present, shall be recorded as <entryRelationship> elements under the Specimen Act.

Modules unique to the document body
Sub-Element Opt Description
1.3.6.1.4.1.19376.1.3.1.1 R2 Notification Organizer
1.3.6.1.4.1.19376.1.3.1.1.1 R2 Notifiable Condition
1.3.6.1.4.1.19376.1.3.1.1.2 R2 Case Identifier
1.3.6.1.4.1.19376.1.3.1.1.3 R2 Outbreak Identifier
1.3.6.1.4.1.19376.1.3.1.2 R2 Specimen Collection
1.3.6.1.4.1.19376.1.3.1.3 R2 Specimen Received
1.3.6.1.4.1.19376.1.3.1.4 R2 Laboratory Battery Organizer
1.3.6.1.4.1.19376.1.3.1.5 R2 Laboratory Isolate Organizer
1.3.6.1.4.1.19376.1.3.1.6 R Laboratory Observation
1.3.6.1.4.1.19376.1.5.3.1.4.2 O Annotation Comment (PCC)


Modules with counterparts in the cda header
Sub-Element Opt Description
1.3.6.1.4.1.19376.1.3.3.1.2.1 R2 Non-Human Subject
1.3.6.1.4.1.19376.1.3.3.1.3.1 R2 Human Patient with Non-Human Subject
1.3.6.1.4.1.19376.1.3.3.1.5 O Laboratory Result Verifier
1.3.6.1.4.1.19376.1.3.3.1.7 O Laboratory Performer