Back To Index  <<  Back To Templates

active Template  Laboratory Report Data Processing Entry

Id 1.3.6.1.4.1.19376.1.3.1
ref
XDLAB-
 		Effective Date 2008‑08‑08
Status active Active Version Label 2017
Name LaboratoryReportDataProcessingEntry Display Name Laboratory Report Data Processing Entry
Description
en-US One Laboratory Report Data Processing Entry SHALL be present in each leaf section of the report. The entry element SHALL be present and have its root attribute valued "1.3.6.1.4.1.19376.1.3.1". The entry SHALL contain a single act sub-element. This act is hereafter referred to as the Specimen Act. All other CDA level 3 content modules are nested in this one act. The Specimen Act shall contain at least one Laboratory Observation. If all observations of the entry have been produced on the same specimen, this specimen SHALL be attached to the top Specimen Act as a specimen sub-element.
A particular section of the laboratory report MAY carry results more confidential than the rest of the report (e.g. the section of the HIV serology). This is expressed with the confidentialityCode sub-element of the Specimen Act.
The Laboratory Report Data Processing Entry SHALL conform to statements here and those made in the following tables and sections.
Classification CDA Entry Level Template
Open/Closed Open (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 3 templates, Uses 15 templates
Used by as Name Version
1.3.6.1.4.1.19376.1.3.3.2.1 Containment active Laboratory Specialty Section (2017) 2008‑08‑08
2.16.840.1.113883.2.9.10.1.1 link draft Referto di Medicina di Laboratorio (LAB) 2018‑04‑16
1.3.6.1.4.1.19376.1.3.3.2.2 Containment active Laboratory Report Item Section (2017) 2008‑08‑08
Uses as Name Version
1.3.6.1.4.1.19376.1.3.3.1.2.1 Containment active Non-Human Subject (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.3.1 Containment active Human Patient with Non-Human Subject (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.7 Containment active Laboratory Performer (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.5 Containment active Laboratory Results Validator (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1 Containment active Notification Organizer (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.2 Containment active Specimen Collection (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.3 Containment active Specimen Received (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.4 Containment active Laboratory Battery Organizer (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.5 Containment active Laboratory Isolate Organizer (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.6 Containment active Laboratory Observation (2017) DYNAMIC
1.3.6.1.4.1.19376.1.5.3.1.4.2 Containment active IHE Comment Entry (2014) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1.1 Containment active Notifiable Condition (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1.2 Containment active Case Identification (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1.3 Containment active Outbreak Identification (2017) DYNAMIC
1.3.6.1.4.1.19376.1.3.10.9.2 Containment active Multimedia Embedded Content (2017) DYNAMIC
Relationship Specialization: template 2.16.840.1.113883.10.12.301 CDA Act (2005‑09‑07)
ref
ad1bbr-
Example
Laboratory Report Data Processing Entry within a Specialty section
<entry typeCode="DRIV">
  <templateId root="1.3.6.1.4.1.19376.1.3.1"/>  <act classCode="ACT" moodCode="EVN">
    <!-- Specialty Level Entry : LOINC Specialty Code -->
    <code code="18719-5" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Chemistry Studies"/>    <statusCode code="completed"/>    <effectiveTime value="200806180512"/>    <specimen typeCode="SPC">
      <specimenRole classCode="SPEC">
        <!-- .. -->
      </specimenRole>    </specimen>    <entryRelationship typeCode="COMP">
      <!-- .. -->
    </entryRelationship>    <!-- .. -->
  </act></entry>
Example
Laboratory Report Data Processing Entry within a Report Item Section
<entry typeCode="DRIV">
  <templateId root="1.3.6.1.4.1.19376.1.3.1"/>  <act classCode="ACT" moodCode="EVN">
    <!-- Report Item Level Entry : Result Item Code -->
    <code code="12814-0" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="POTASSIUM" originalText="Serum potassium"/>    <statusCode code="completed"/>    <effectiveTime value="200806180512"/>    <specimen typeCode="SPC">
      <specimenRole classCode="SPEC">
        <!-- .. -->
      </specimenRole>    </specimen>    <entryRelationship typeCode="COMP">
      <!-- .. -->
    </entryRelationship>    <!-- .. -->
  </act></entry>
Item DT Card Conf Description Label
hl7:templateId
 		II 1 … 1 M (Labdotstry)
@root
 		uid 1 … 1 F 1.3.6.1.4.1.19376.1.3.1
hl7:act
 		1 … 1 en-US There shall be one Act sub-element. This <act> is hereafter referred to as the Specimen Act. This sub-element uses the modules conforming to the following requirements. These modules, when present, shall be recorded as <entryRelationship> elements under the Specimen Act.
  • Specimen Collection 1.3.6.1.4.1.19376.1.3.1.2
  • Specimen Received 1.3.6.1.4.1.19376.1.3.1.3
  • Specimen Site 1.3.6.1.4.1.19376.1.3.1.8
  • Notification Organizer
  • Notifiable Condition
  • Case Identifier
  • Outbreak Identifier
  • Laboratory Isolate Organizer
  • Laboratory Battery Organizer
  • Laboratory Observation
  • Mutimedia Embedded Content
  • Annotation Comment
 (Labdotstry)
@classCode
 		cs 1 … 1 F ACT
@moodCode
 		cs 1 … 1 F EVN
hl7:code
 		CD 1 … 1 M en-US
Mandatory. When section is a Specialty Section, code is a LOINC Specialty. When section is a Report Item Section, code is a Report Item code.
(Labdotstry)
hl7:statusCode
 		CS 1 … 1 M en-US Mandatory.
  • ‘completed’ when all expected results are in a final state
  • ‘active’ if not all expected results are present
  • ‘aborted’ if the tests of this section did not reach completion. Some results MAY be there, but not all.
(Labdotstry)
  CONF
@code shall be "completed"
or
@code shall be "active"
or
@code shall be "aborted"
Choice 0 … 1 Elements to choose from:
hl7:subject
 		0 … 1 en-US subject in case of a non-human subject
Contains 1.3.6.1.4.1.19376.1.3.3.1.2.1 Non-Human Subject (DYNAMIC) 		(Labdotstry)
@typeCode
 		cs 0 … 1 F SBJ
hl7:subject
 		0 … 1 en-US subject in case of a non-human subject
Contains 1.3.6.1.4.1.19376.1.3.3.1.3.1 Human Patient with Non-Human Subject (DYNAMIC) 		(Labdotstry)
@typeCode
 		cs 0 … 1 F SBJ
hl7:performer
 		0 … * en-US performer participation used if different from the performer of the header, to supersede it for this section.
Contains 1.3.6.1.4.1.19376.1.3.3.1.7 Laboratory Performer (DYNAMIC) 		(Labdotstry)
@typeCode
 		cs 0 … 1 F PRF
hl7:author
 		0 … * en-US author used if different from the author of the header, to supersede it for this section. (Labdotstry)
hl7:participant
 		0 … * en-US Other participants such as validator (AUTHEN) or responsible party (RESP) or device (DEV)
  • AUTHEN: The verifier of the battery organizer. In the case where a laboratory report has multiple verifiers. Each verifier is attached to the subset of batteries/observations he or she verified, by the means of a <participant> element.

Contains 1.3.6.1.4.1.19376.1.3.3.1.5 Laboratory Results Validator (DYNAMIC) 		(Labdotstry)
where [@typeCode='AUTHEN']
hl7:participant
 		0 … * en-US Other participants such as validator (AUTHEN) or responsible party (RESP) or device (DEV)
  • RESP: The person responsible for the provision of the battery. In the case where this battery is subcontracted to an external laboratory, this external laboratory (with its address and telcom) and the actual performer is represented by a <performer> element, whereas the Director of this subcontractor laboratory is carried by the <participant> element being attached to the same level as the <performer> element.
(Labdotstry)
where [@typeCode='RESP']
@typeCode
 		cs 1 … 1 F RESP
hl7:participant
 		0 … * en-US Other participants such as validator (AUTHEN) or responsible party (RESP) or device (DEV)
  • DEV: A device or equipment, which was used to produce this battery of results (e.g. an analyzer).
(Labdotstry)
where [@typeCode='DEV']
@typeCode
 		cs 1 … 1 F DEV
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.1 Notification Organizer (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.2 Specimen Collection (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.3 Specimen Received (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.4 Laboratory Battery Organizer (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.5 Laboratory Isolate Organizer (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.6 Laboratory Observation (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.5.3.1.4.2 IHE Comment Entry (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.1.1 Notifiable Condition (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.1.2 Case Identification (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.1.1.3 Outbreak Identification (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
hl7:entryRelationship
 		0 … * R Contains 1.3.6.1.4.1.19376.1.3.10.9.2 Multimedia Embedded Content (DYNAMIC) (Labdotstry)
@typeCode
 		cs 1 … 1 F COMP
  Schematron assert role red error  
  test hl7:entryRelationship  
  Message A Laboratory Result Content SHALL be present.