Template 1.3.6.1.4.1.19376.1.3.1.2

Template Specimen Collection

1.3.6.1.4.1.19376.1.3.1.2

ref

XDLAB-

Effective Date

2008‑08‑08

Status

Active

Version Label

2017

Name

SpecimenCollection

Display Name

Specimen Collection

Description

Specimen Collection, when present, SHALL be recorded under the Specimen Act in an entryRelationship under the Laboratory Data Processing Entry. The table below shows how the information for this element is coded, and further constraints are provided in the following sections.

Context

Parent nodes of template element with id 1.3.6.1.4.1.19376.1.3.1.2

Classification

CDA Entry Level Template

Open/Closed

Open (other than defined elements are allowed)

Used by / Uses

Used by 0 transactions and 7 templates, Uses 1 template

Used by	as	Name	Version
1.3.6.1.4.1.19376.1.3.1	Containment	Laboratory Report Data Processing Entry (2017)	2008‑08‑08
1.3.6.1.4.1.19376.1.3.3.2.1		Laboratory Specialty Section (2017)	2008‑08‑08
1.3.6.1.4.1.19376.1.3.3.2.2		Laboratory Report Item Section (2017)	2008‑08‑08
1.3.6.1.4.1.19376.1.3.1.4	Containment	Laboratory Battery Organizer (2017)	2008‑08‑08
1.3.6.1.4.1.19376.1.3.1.5		Laboratory Isolate Organizer (2017)	2008‑08‑08
2.16.840.1.113883.3.1937.777.63.10.589		Laboratory Report Data Processing Entry (2017)	2024‑06‑18 14:13:32
1.3.6.1.4.1.19376.1.3.1.6	Containment	Laboratory Observation (2017)	2008‑08‑08
Uses	as	Name	Version
1.3.6.1.4.1.19376.1.3.1.3	Containment	Specimen Received (2017)	DYNAMIC

Relationship

Specialization: template 2.16.840.1.113883.10.12.301 CDA Act (2005‑09‑07)

ref

ad1bbr-

Example

Specimen Collection Example

<procedure classCode="PROC" moodCode="EVN">
  <templateId root="1.3.6.1.4.1.19376.1.3.1.2"/>  <code code="33882-2" codeSystem="2.16.840.1.113883.6.1"/>  <effectiveTime value="20170329074309"/>  <targetSiteCode/>  <performer/>  <participant typeCode="PRD">
    <participantRole classCode="SPEC">
      <id root="1.2.3.999" extension="--example only--"/>      <addr>
        <streetAddressLine>7000 Hosptial Drive</streetAddressLine>        <city>Chicago</city>        <state>IL</state>        <postalCode>60622</postalCode>      </addr>      <telecom value="tel:312-555-5555"/>    </participantRole>  </participant>  <entryRelationship>
    
  </entryRelationship></procedure>

Example

Specimen Collection Example

<procedure classCode="PROC" moodCode="EVN">
  <templateId root="1.3.6.1.4.1.19376.1.3.1.2"/>  <code code="33882-2" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Specimen Collection"/>  <effectiveTime value="20071108000000.0000-0500"/>  <participant typeCode="PRD">
    <participantRole classCode="SPEC">
      <id extension="5555" root="1.19.6.11.13"/>    </participantRole>  </participant>  <participant typeCode="PRF">
    <participantRole>
      <id extension="54689A" root="1.3.6.1.4.1.19376.1.3.4"/>      <addr>
        <streetAddressLine>7000 Hosptial Drive</streetAddressLine>        <city>Chicago</city>        <state>IL</state>        <postalCode>60622</postalCode>      </addr>      <telecom value="tel:312-555-5555"/>    </participantRole>  </participant></procedure>

Item	DT	Card	Conf	Description
hl7:procedure
@classCode	cs	1 … 1	F	PROC
@moodCode	cs	1 … 1	F	EVN
hl7:templateId	II	1 … 1	M
@root	uid	1 … 1	F	1.3.6.1.4.1.19376.1.3.1.2
hl7:code	CD	0 … 1	R	LOINC code representing the act of specimen collection
@code	CONF	0 … 1	F	33882-2
hl7:effectiveTime	IVL_TS	1 … 1	R	Date and time of specimen collection
hl7:targetSiteCode		0 … 1
hl7:performer		0 … 1
hl7:participant		1 … 1	R	Specimen Collection Participants. A participant SHALL have an id, addr, and telecom. Additionally, the participant MAY have a playingEntity to capture a person's name and a scopingEntity to capture the organization.
@typeCode	cs	1 … 1	F	PRD
hl7:participantRole		1 … 1	M
@classCode	cs	0 … 1	F	SPEC
hl7:id	II	1 … 1	R
hl7:playingEntity		1 … 1	R
hl7:code		1 … 1
hl7:entryRelationship		0 … 1		Contains 1.3.6.1.4.1.19376.1.3.1.3 Specimen Received (DYNAMIC)
@typeCode	cs	1 … 1	F	COMP

Template Specimen Collection