Id1.3.182.11.3.3.7Effective Date2018‑09‑26 16:56:18
Statusdraft DraftVersion Label
NameLaboratoryReportDataProcessingEntryXDLABDisplay NameLaboratory Report Data Processing Entry
Description
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.
ContextPathname /
ClassificationCDA Entry Level Template
Open/ClosedClosed (only defined elements are allowed)
Used by / Uses
Used by 0 transactions and 2 templates, Uses 7 templates
Used by as NameVersion
1.3.182.11.3.2.1Containmentdraft Laboratory Report Item Section2018‑09‑26 17:09:07
1.3.182.11.3.2.2Containmentdraft Laboratory Specialty Section2018‑09‑26 17:14:05
Uses as NameVersion
1.3.182.11.3.3.1Containmentdraft Specimen ReceivedDYNAMIC
1.3.182.11.3.3.2Containmentdraft Specimen CollectionDYNAMIC
1.3.182.11.3.3.3Containmentdraft Multimedia Embedded ContentDYNAMIC
1.3.182.11.3.3.4Containmentdraft Laboratory ObservationDYNAMIC
1.3.182.11.3.3.5Containmentdraft Laboratory Battery OrganizerDYNAMIC
1.3.182.11.3.3.6Containmentdraft Laboratory Isolate OrganizerDYNAMIC
1.3.182.11.9.3.1Containmentdraft Annotation Comment EntryDYNAMIC
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>
ItemDTCardConfDescriptionLabel
hl7:templateId
II1 … 1MLabodotsDLAB
@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.1
hl7:templateId
II1 … 1MLabodotsDLAB
@root
uid1 … 1F1.3.182.11.3.3.7
hl7:act
1 … 1RThere 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
  • Specimen Received
  • Laboratory Isolate Organizer
  • Laboratory Battery Organizer
  • Laboratory Observation
  • Mutimedia Embedded Content
  • Annotation Comment
LabodotsDLAB
@classCode
cs1 … 1FACT
@moodCode
cs1 … 1FEVN
hl7:code
CD1 … 1M
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.
LabodotsDLAB
hl7:text
ED0 … 1LabodotsDLAB
hl7:reference
TEL1 … 1MLabodotsDLAB
@value
st1 … 1R
hl7:statusCode
CS1 … 1MMandatory.
  • ‘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.
LabodotsDLAB
 CONF
@code shall be "completed"
or
@code shall be "active"
or
@code shall be "aborted"
hl7:performer
0 … *performer participation used if different from the performer of the header, to supersede it for this section.LabodotsDLAB
@typeCode
cs0 … 1FPRF
hl7:author
0 … *author used if different from the author of the header, to supersede it for this section.LabodotsDLAB
hl7:participant
0 … *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.
LabodotsDLAB
where [@typeCode='AUTHEN']
hl7:participant
0 … *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.
LabodotsDLAB
where [@typeCode='RESP']
@typeCode
cs1 … 1FRESP
hl7:participant
0 … *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).
LabodotsDLAB
where [@typeCode='DEV']
@typeCode
cs1 … 1FDEV
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.2 Specimen Collection (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.1 Specimen Received (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.5 Laboratory Battery Organizer (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.6 Laboratory Isolate Organizer (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.4 Laboratory Observation (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.9.3.1 Annotation Comment Entry (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
hl7:entryRelationship
0 … *RContains 1.3.182.11.3.3.3 Multimedia Embedded Content (DYNAMIC)LabodotsDLAB
@typeCode
cs1 … 1FCOMP
 Schematron assertrolered error 
 testhl7:entryRelationship 
 MessageA Laboratory Result Content SHALL be present.