1.3.6.1.4.1.19376.1.3.3.1.7

From pubswiki
Revision as of 16:33, 13 November 2022 by Adbot (talk | contribs) (Automatic ADBot page (2d321077b1e5b249d010a441b590710f11e000fb))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Templatenote

Template LaboratoryPerformer

Laboratory Performers SHALL be recorded as performers in the CDA Header as well as in the structured body as demonstrated in the figure below. Documentation of laboratory performers MAY be done in multiple levels of the document to reflect performance scope. In the case where there is a single Laboratory Performer, this entity SHALL be documented in CDA header as shown. In the case where multiple Laboratory Performers participated in the lab testing process, they SHALL be documented in the structuredBody at the observation level. These performers SHALL conform to the General Constraints found in HL7 CRS: 2.1.1 with respect to the requirements for name, address, telephone numbers and other contact information. This module is out of the XDS-Lab Specification and documented there in a <performer> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability. The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.

Actual version

Id1.3.6.1.4.1.19376.1.3.3.1.7
ref
XDLAB-
Effective Date2008‑08‑08
StatusKgreen.png ActiveVersion Label2017
NameLaboratoryPerformerDisplay NameLaboratory Performer
Description
Laboratory Performers SHALL be recorded as performers in the CDA Header as well as in the structured body as demonstrated in the figure below. Documentation of laboratory performers MAY be done in multiple levels of the document to reflect performance scope. In the case where there is a single Laboratory Performer, this entity SHALL be documented in CDA header as shown. In the case where multiple Laboratory Performers participated in the lab testing process, they SHALL be documented in the structuredBody at the observation level.

These performers SHALL conform to the General Constraints found in HL7 CRS: 2.1.1 with respect to the requirements for name, address, telephone numbers and other contact information.

This module is out of the XDS-Lab Specification and documented there in a <performer> element. This module does not change requirements stated in that specification but is structured as a module to ensure consistent content representation and re-usability.

The figure below shows how the information for this element is coded, and further constraints are provided in the following sections.

ContextSibling nodes of template element with id 1.3.6.1.4.1.19376.1.3.3.1.7
ClassificationCDA Header Level Template
CDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
RelationshipSpecialization: template 2.16.840.1.113883.10.12.320 CDA Subject (Body) (2005‑09‑07)
ref
ad1bbr-
Example
Laboratory Performer at Service Event Level (Header)
<serviceEvent>
  <!-- .. -->
  <performer typeCode="PRF">
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.7"/>    <assignedEntity>
      <id extension="kd83736" 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>        <country>USA</country>      </addr>
      <telecom value="tel:312-555-5555"/>      <assignedPerson>
        <name>
          <family>Dawson</family>          <given>Kim</given>          <prefix>Dr.</prefix>        </name>
      </assignedPerson>
      <representedOrganization>
        <id extension="9875" root="1.3.6.1.4.1.19376.1.3.4"/>        <name>PRF Hospital Laboratory</name>        <telecom value="tel:312-555-5555"/>        <addr>
          <streetAddressLine>7000 Hosptial Drive</streetAddressLine>          <city>Chicago</city>          <state>IL</state>          <postalCode>60622</postalCode>          <country>USA</country>        </addr>
      </representedOrganization>
    </assignedEntity>
  </performer>
</serviceEvent>
Example
Laboratory Performer at Observation Level (Body)
<observation>
  <!-- .. -->
  <performer typeCode="PRF">
    <templateId root="1.3.6.1.4.1.19376.1.3.3.1.7"/>    <assignedEntity>
      <id extension="rm83747" 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>        <country>USA</country>      </addr>
      <telecom value="tel:312-555-5555"/>      <assignedPerson>
        <name>
          <family>Trenton</family>          <given>Douglas</given>          <prefix>Dr.</prefix>        </name>
      </assignedPerson>
      <representedOrganization>
        <id extension="rm83747" root="1.3.6.1.4.1.19376.1.3.4"/>        <name>PRF Hospital Laboratory</name>        <telecom value="tel:312-555-5555"/>        <addr>
          <streetAddressLine>7000 Hosptial Drive</streetAddressLine>          <city>Chicago</city>          <state>IL</state>          <postalCode>60622</postalCode>          <country>USA</country>        </addr>
      </representedOrganization>
    </assignedEntity>
  </performer>
</observation>
ItemDTCardConfDescriptionLabel
@typeCode
cs0 … 1FPRF
hl7:templateId
II1 … 1M(Lab...mer)
Treetree.png@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.3.1.7
hl7:time
IVL_TS1 … 1RThe element SHALL be present and SHALL represent the point in time of laboratory performance.(Lab...mer)
hl7:assignedEntity
1 … 1(Lab...mer)
Treetree.png@classCode
cs0 … 1FASSIGNED
Treetree.pnghl7:id
II1 … *RUnique identifier of this person/organization (lab performer) in the affinity domain SHALL be present.(Lab...mer)
Treetree.pnghl7:code
CE0 … 1R(Lab...mer)
Treetree.pnghl7:addr
AD1 … *RThe address of this person/organization (lab performer) SHALL be present.(Lab...mer)
Treetree.pnghl7:telecom
TEL1 … *RThe telecom of this person/organization (lab performer) SHALL be present.(Lab...mer)
Treetree.pnghl7:assigned​Person
0 … 1R(Lab...mer)
Treetree.pnghl7:represented​Organization
0 … 1R(Lab...mer)
 Schematron assertrole error 
 testhl7:assigned​Person/hl7:name or hl7:represented​Organization/hl7:name 
 MessageEither an <assignedPerson> or a <representedOrganization> SHALL be present. In either case, the <name> sub-element SHALL be present. 


List of all versions of this template