Back To Index  <<  Back To Templates

active Template  Laboratory Performer - documentationOf

Id 2.16.756.5.30.1.1.10.2.28
ref
ch-palm-
Effective Date 2019‑08‑20
Status active Active Version Label 2019
Name chpalm_header_DocumentationOfLaboratoryPerformer Display Name Laboratory Performer - documentationOf
Description

Laboratory Performer template in the CDA header (ClinicalDocument/documentationOf/serviceEvent)

ClinicalDocument/documentationOf(s) MAY be present. The documentationOf/serviceEvent represents the main Act being documented, that is an act of reporting Result Event(s) produced by a laboratory.

Use of sub element documentationOf/serviceEvent/effectiveTime to document the time boundaries of events in the document is appropriate.

This laboratory report content module adds the optional sub element documentationOf/serviceEvent/statusCode to enable the sharing of non-final reports. A report is considered as non-final (e.g., a preliminary report) if and only if it documents an Act, which is still in the status "active" (i.e., serviceEvent/statusCode@code="active").

The statusCode sub element is an extension to the CDA R2 schema. This sub-element is optional. When it is not there, the documented Act is assumed to be completed and the report is assumed to be a final report.

Context Parent nodes of template element with id 2.16.756.5.30.1.1.10.2.28
Label IHE PalM TF3 Rev.10, 6.3.2.20
Classification CDA Header Level Template
Open/Closed Open (other than defined elements are allowed)
Used by / Uses
Used by 1 transaction and 1 template, Uses 1 template
Used by as Name Version
cdachlrep-transaction-2 Transaction pending CDA-CH-LREP - General Laboratory Report (2018) 2018‑03‑06 18:38:46
2.16.756.5.30.1.1.10.1.10 Include active General Laboratory Report (2020) 2020‑06‑26
Uses as Name Version
2.16.756.5.30.1.1.10.4.7 Containment active Laboratory Performer - performer Containment (2019) DYNAMIC
Relationship Specialization: template 2.16.840.1.113883.10.12.110 CDA documentationOf (2005‑09‑07)
ref
ad1bbr-
Example
Example
<documentationOf>
  <templateId root="2.16.756.5.30.1.1.10.2.28"/>  <serviceEvent>
    <effectiveTime>
      <low value="20180320105641"/>    </effectiveTime>
    <performer>
      <!-- template 2.16.756.5.30.1.1.10.4.7 'Laboratory Performer' -->
    </performer>
  </serviceEvent>
</documentationOf>
Item DT Card Conf Description Label
hl7:documentationOf
0 … * IHE PalM TF3 Rev.10, 6.3.2.20
hl7:templateId
II 1 … 1 M IHE PalM TF3 Rev.10, 6.3.2.20
@root
uid 1 … 1 F 2.16.756.5.30.1.1.10.2.28
hl7:serviceEvent
1 … 1 R IHE PalM TF3 Rev.10, 6.3.2.20
hl7:effectiveTime
IVL_TS.CH.TZ 0 … 1 Use of sub element documentationOf/serviceEvent/effectiveTime to document the time boundaries of events in the document is appropriate. IHE PalM TF3 Rev.10, 6.3.2.20
hl7:performer
0 … * Laboratory Performer template in the CDA header.
Contains 2.16.756.5.30.1.1.10.4.7 Laboratory Performer - performer Containment (DYNAMIC)
IHE PalM TF3 Rev.10, 6.3.2.20