Template

Show index

Template XeH Laboratory Report Data Processing Entry 2021‑10‑07 00:14:07

Id2.16.840.1.113883.2.51.10.36Effective Date2021‑10‑07 00:14:07
Statusactive ActiveVersion Label1.0
NameXeHLaboratoryReportDataProcessingEntryDisplay NameXeH Laboratory 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.
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 2 templates, Uses 16 templates
Used by as NameVersion
2.16.840.1.113883.2.51.10.34Containmentactive XeH Laboratory Specialty Section, Variant 1 (1.0)2021‑10‑01 12:00:38
2.16.840.1.113883.2.51.10.55Containmentactive XeH Laboratory Report Item Section (1.0)2022‑02‑16 11:32:28
Uses as NameVersion
1.3.6.1.4.1.19376.1.3.1.1.1Containmentactive Notifiable Condition (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1.2Containmentactive Case Identification (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.1.1.3Containmentactive Outbreak Identification (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.2.1Containmentactive Non-Human Subject (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.3.1Containmentactive Human Patient with Non-Human Subject (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.3.1.7Containmentactive Laboratory Performer (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.10.9.2Containmentactive Multimedia Embedded Content (2017)DYNAMIC
1.3.6.1.4.1.19376.1.3.10.9.17Containmentactive Author with Name, Addr, Telecom (2017)DYNAMIC
1.3.6.1.4.1.19376.1.5.3.1.4.2Containmentactive IHE Comment Entry (2014)DYNAMIC
2.16.840.1.113883.2.51.10.42Containmentactive XeH Specimen Collection (2021)DYNAMIC
2.16.840.1.113883.2.51.10.43Containmentactive XeH Notification Organizer (1.0)DYNAMIC
2.16.840.1.113883.2.51.10.56Containmentactive XeH Laboratory Observation (1.0)DYNAMIC
2.16.840.1.113883.2.51.10.70Containmentactive XeH Laboratory Battery Organizer (2017)DYNAMIC
2.16.840.1.113883.2.51.10.74Includeactive XeH Lab Results Validator Participant (1.0)DYNAMIC
2.16.840.1.113883.2.51.10.91Includeactive XeH Lab Device Participant (1.0)DYNAMIC
2.16.840.1.113883.2.51.10.92Containmentactive XeH Laboratory Isolate Organizer (1.0)DYNAMIC
RelationshipAdaptation: template 1.3.6.1.4.1.19376.1.3.1 Laboratory Report Data Processing Entry (2008‑08‑08)
ref
XDLAB-

Adaptation: 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>
ItemDTCardConfDescriptionLabel
hl7:templateId
II1 … 1MXeHLdotsntry
@root
uid1 … 1F2.16.840.1.113883.2.51.10.36
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 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
XeHLdotsntry
@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.
XeHLdotsntry
 ConstraintIf the Laboratory Data Processing Entry is used within a Laboratory Specialty Section (Variant 1), the code SHALL be set to the same value present in the Laboratory Specialty Section (from "XeH Lab Study Types" value-set)

If the Laboratory Data Processing Entry is used within a Report Item Section (a sub-section of a Laboratory Specialty Section, Variant 2), the code SHALL be set to the same value present in the Report Item Section (from "XeH Lab Study Subtypes" value-set)
 CONF
The value of @code shall be drawn from value set 2.16.840.1.113883.2.51.13.1.2 XeH Lab Study Types (DYNAMIC)
or
The value of @code shall be drawn from value set 2.16.840.1.113883.2.51.13.9 XeH Lab Study Subtypes (DYNAMIC)
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.
XeHLdotsntry
 CONF
@code shall be "completed"
or
@code shall be "active"
or
@code shall be "aborted"
Choice0 … 1Elements to choose from:
hl7:subject
0 … 1subject 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)		XeHLdotsntry
@typeCode
cs0 … 1FSBJ
hl7:subject
0 … 1subject 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)		XeHLdotsntry
@typeCode
cs0 … 1FSBJ
hl7:performer
0 … *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)		XeHLdotsntry
hl7:author
0 … *author used if different from the author of the header, to supersede it for this section.
Contains 1.3.6.1.4.1.19376.1.3.10.9.17 Author with Name, Addr, Telecom (DYNAMIC)		XeHLdotsntry
hl7:participant
0 … *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.

Note: See "other participants" ("AUTHEN", "RESP", "DEV") according to IHE XD-LAB profile
    		XeHLdotsntry
    where [@typeCode='AUTHEN']
    @typeCode
    		cs1 … 1FAUTHEN
    Included1 … 1M from 2.16.840.1.113883.2.51.10.74 XeH Lab Results Validator Participant (DYNAMIC)
    hl7:time
    		TS1 … 1MXeHLdotspant
    hl7:participantRole
    		1 … 1MXeHLdotspant
    @classCode
    		cs0 … 1FROL
    hl7:id
    		II1 … *RXeHLdotspant
    hl7:code
    		CE.IPS (preferred)0 … 1A code, which identifies the profession/competence/specialty of the author when it is a person.
    		XeHLdotspant
     CONF
    The value of @code comes preferably from value set 2.16.840.1.113883.11.22.53 IPS Healthcare Professional Roles (DYNAMIC)
    hl7:addr
    		AD0 … *XeHLdotspant
    hl7:telecom
    		TEL0 … *XeHLdotspant
    hl7:playingEntity
    		0 … 1RXeHLdotspant
    hl7:name
    		PN1 … 1RXeHLdotspant
    hl7:participant
    		0 … *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.

    Note: See "other participants" ("AUTHEN", "RESP", "DEV") according to IHE XD-LAB profile
      		XeHLdotsntry
      where [@typeCode='RESP']
      @typeCode
      		cs1 … 1FRESP
      hl7:participant
      		0 … *DEV: A device or equipment, which was used to produce this battery of results (e.g. an analyzer).

      Note: See "other participants" ("AUTHEN", "RESP", "DEV") according to IHE XD-LAB profile
        		XeHLdotsntry
        where [@typeCode='DEV']
        @typeCode
        		cs1 … 1FDEV
        Included1 … 1M from 2.16.840.1.113883.2.51.10.91 XeH Lab Device Participant (DYNAMIC)
        hl7:participantRole
        		1 … 1MXeHLdotspant
        hl7:id
        		II0 … *The UDI Device Identifier MAY be specified as a second id element.
        		XeHLdotspant
        hl7:playingDevice
        		1 … 1MXeHLdotspant
        hl7:code
        		CE.IPS0 … 1Coded product type
        		XeHLdotspant
        hl7:manufacturerModelName
        		SC0 … 1The element manufacturerModelName“ is intended to be used in the same manner as element “modelNumber” specified in the FHIR device resource. It shall carry model information of the device or software provided in element softwareName
        		XeHLdotspant
        hl7:softwareName
        		SC1 … 1M
        The element softwareName is the primary element and intended to be used in the same manner as element “deviceName” specified in the FHIR device resource. It should carry the name of the device or software.

        Is SHOULD including the manufacturer name.

        Note: In case of usage for laboratory related documentation (e.g. Laboratory Result Report), the device structure is also used to record "Laboratory Kits" used for the examination.
        		XeHLdotspant
        hl7:entryRelationship
        		0 … *RContains 2.16.840.1.113883.2.51.10.43 XeH Notification Organizer (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 2.16.840.1.113883.2.51.10.42 XeH Specimen Collection (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 2.16.840.1.113883.2.51.10.70 XeH Laboratory Battery Organizer (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 2.16.840.1.113883.2.51.10.92 XeH Laboratory Isolate Organizer (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 2.16.840.1.113883.2.51.10.56 XeH Laboratory Observation (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 1.3.6.1.4.1.19376.1.5.3.1.4.2 IHE Comment Entry (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 1.3.6.1.4.1.19376.1.3.1.1.1 Notifiable Condition (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 1.3.6.1.4.1.19376.1.3.1.1.2 Case Identification (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 1.3.6.1.4.1.19376.1.3.1.1.3 Outbreak Identification (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
        hl7:entryRelationship
        		0 … *RContains 1.3.6.1.4.1.19376.1.3.10.9.2 Multimedia Embedded Content (DYNAMIC)XeHLdotsntry
        @typeCode
        		cs1 … 1FCOMP
         Schematron assertrolered error 
         testhl7:entryRelationship 
         MessageA Laboratory Result Content SHALL be present.