Templates

Show index

Template Laboratory Results Validator - participant Containment 2019‑08‑20

Id2.16.756.5.30.1.1.10.4.8
ref
ch-palm-
Effective Date2019‑08‑20
Statusactive ActiveVersion Label2019
Namechpalm_entry_LaboratoryResultsValidatorDisplay NameLaboratory Results Validator - participant Containment
Description

The document MAY contain further signatures (besides the legal authenticator). A Laboratory Results Validator is such an authenticator. It is a laboratory specialist who has performed the clinical validation of the entire document or a subset of the laboratory results. If this element is specified, the following applies:

  • If only one laboratory specialist has carried out the clinical validation of the document, it should be specified in the header, only.
  • If multiple laboratory specialists were involved in the clinical validation of the document, all must be specified in the header and body (at entry, organizer or observation level, depending on the scope of the results that the corresponding person has validated).
  • All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.
ContextSibling nodes of template element with id 2.16.756.5.30.1.1.10.4.8
LabelIHE PalM TF3 Rev.10, 6.3.2.16
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 3 transactions and 13 templates, Uses 2 templates
Used by as NameVersion
2.16.756.5.30.1.127.77.1.4.5Transactionpending CDA-CH-VACD - Immunization Recommendation Request (2018)2018‑04‑10 18:08:44
2.16.756.5.30.1.127.77.1.4.6Transactionpending CDA-CH-VACD - Immunization Recommendation Response (2018)2018‑04‑10 18:09:59
2.16.756.5.30.1.127.77.1.4.7Transactionpending CDA-CH-VACD - Vaccination Record (2018)2018‑04‑10 18:10:49
2.16.756.5.30.1.1.10.1.17linkactive Immunization Recommendation Request (2020)2020‑06‑26
2.16.756.5.30.1.1.10.1.18linkactive Immunization Recommendation Response (2020)2020‑06‑26
2.16.756.5.30.1.1.10.1.19linkactive Vaccination Record (2020)2020‑06‑26
2.16.756.5.30.1.1.10.3.3linkactive Laboratory Speciality Section - coded (2019)2019‑08‑20
2.16.756.5.30.1.1.10.3.5linkactive Laboratory Report Item Section - coded (2019)2019‑08‑20
2.16.756.5.30.1.1.10.4.3linkactive Laboratory Observation (2020)2019‑08‑20
2.16.756.5.30.1.1.10.4.4Containmentactive Laboratory Report Data Processing Entry (2019)2019‑08‑20
2.16.756.5.30.1.1.10.4.11linkactive Specimen Collection (2019)2019‑08‑20
2.16.756.5.30.1.1.10.4.17Containmentactive Laboratory Isolate Organizer (2019)2019‑08‑20
2.16.756.5.30.1.1.10.4.19Containmentactive Laboratory Battery Organizer (2019)2019‑08‑20
2.16.756.5.30.1.1.10.4.85Containmentactive Laboratory Isolate Organizer - Pathogen Detection (2020)2020‑06‑26
2.16.756.5.30.1.1.10.4.87Containmentactive Laboratory Battery Organizer - Antibiogram (2020)2020‑06‑26
2.16.756.5.30.1.1.10.4.118Containmentactive Laboratory Report Data Processing Entry (2020)2020‑06‑26
Uses as NameVersion
2.16.756.5.30.1.1.10.9.20Containmentactive PlayingEntity Compilation with name (2017)DYNAMIC
2.16.756.5.30.1.1.10.9.35Containmentdraft Address Information Compilation - eCH-0010 (2022)DYNAMIC
RelationshipSpecialization: template 2.16.840.1.113883.10.12.107 CDA authenticator (2005‑09‑07)
ref
ad1bbr-

Specialization: template 1.3.6.1.4.1.19376.1.3.3.1.5 Laboratory Results Validator (DYNAMIC)
ref
XDLAB-
Example
Example
<participant typeCode="AUTHEN">
  <templateId root="2.16.756.5.30.1.1.10.4.8"/>  <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>  <participantRole>
    <addr>
      <!-- template 2.16.756.5.30.1.1.10.9.35 'Address Information Compilation - eCH-0010' -->
    </addr>    <telecom value="tel:+41.33.123.45.67 "/>    <playingEntity>
      <!-- template 2.16.756.5.30.1.1.10.9.20 'PlayingEntity Compilation with name' -->
    </playingEntity>  </participantRole></participant>
ItemDTCardConfDescriptionLabel
@typeCode
cs1 … 1FAUTHEN
hl7:templateId
II1 … 1MIHE PalM TF3 Rev.10, 6.3.2.16
@root
uid1 … 1F2.16.756.5.30.1.1.10.4.8
hl7:templateId
II1 … 1MIHE PalM TF3 Rev.10, 6.3.2.16
@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.3.1.5
hl7:time
TS.CH.TZ0 … 1RDate and time of the laboratory results validation signature.IHE PalM TF3 Rev.10, 6.3.2.16
hl7:participantRole
1 … 1RIHE PalM TF3 Rev.10, 6.3.2.16
hl7:id
II0 … *RAn ID for this item MAY be filled for traceability.IHE PalM TF3 Rev.10, 6.3.2.16
@root
uid1 … 1RMUST contain the OID of the system that issued the ID. OIDs of code systems, which are published in the public OID registry for the Swiss health care system (oid.refdata.ch) are REQUIRED. Others are NOT ALLOWED.
@extension
st0 … 1 Contains the ID itself. The ID MUST be unique within the system that issued the ID.
hl7:addr
AD1 … *All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.
Contains 2.16.756.5.30.1.1.10.9.35 Address Information Compilation - eCH-0010 (DYNAMIC)		IHE PalM TF3 Rev.10, 6.3.2.16
hl7:telecom
TEL1 … *All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.IHE PalM TF3 Rev.10, 6.3.2.16
hl7:playingEntity
Contains 2.16.756.5.30.1.1.10.9.20 PlayingEntity Compilation with name (DYNAMIC)IHE PalM TF3 Rev.10, 6.3.2.16

Template Laboratory Results Validator - authenticator/participant Containment 2017‑06‑21

Id2.16.756.5.30.1.1.10.4.8
ref
ch-palm-
Effective Date2017‑06‑21
Statusrejected RejectedVersion Label2017
Namechpalm_entry_LaboratoryResultsValidatorDisplay NameLaboratory Results Validator - authenticator/participant Containment
Description

The document MAY contain further signatures (besides the legal authenticator). A Laboratory Results Validator is such an authenticator. It is a laboratory specialist who has performed the clinical validation of the entire document or a subset of the laboratory results. If this element is specified, the following applies:

  • If only one laboratory specialist has carried out the clinical validation of the document, it should be specified in the header, only.
  • If multiple laboratory specialists were involved in the clinical validation of the document, all must be specified in the header and body (at entry, organizer or observation level, depending on the scope of the results that the corresponding person has validated).
  • All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.
ContextSibling nodes of template element with id 2.16.756.5.30.1.1.10.4.8
LabelIHE PalM TF3 Rev.8, 6.3.2.16
ClassificationCDA Entry Level Template
Open/ClosedOpen (other than defined elements are allowed)
RelationshipSpecialization: template 2.16.840.1.113883.10.12.107 CDA authenticator (2005‑09‑07)
ref
ad1bbr-

Specialization: template 1.3.6.1.4.1.19376.1.3.3.1.5 Laboratory Results Validator (DYNAMIC)
ref
XDLAB-
Example
Example
<participant typeCode="AUTHEN">
  <templateId root="2.16.756.5.30.1.1.10.4.8"/>  <templateId root="1.3.6.1.4.1.19376.1.3.3.1.5"/>  <participantRole>
    <addr>
      <!-- template 2.16.756.5.30.1.1.10.9.35 'Address Information Compilation - eCH-0010' -->
    </addr>    <telecom value="tel:+41.33.123.45.67 "/>    <playingEntity>
      <!-- template 2.16.756.5.30.1.1.10.9.20 'PlayingEntity Compilation with name' -->
    </playingEntity>  </participantRole></participant>
ItemDTCardConfDescriptionLabel
@typeCode
cs1 … 1FAUTHEN
hl7:templateId
II1 … 1MIHE PalM TF3 Rev.8, 6.3.2.16
@root
uid1 … 1F2.16.756.5.30.1.1.10.4.8
hl7:templateId
II1 … 1MIHE PalM TF3 Rev.8, 6.3.2.16
@root
uid1 … 1F1.3.6.1.4.1.19376.1.3.3.1.5
hl7:participantRole
1 … 1RIHE PalM TF3 Rev.8, 6.3.2.16
hl7:addr
AD1 … *All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.
Contains 2.16.756.5.30.1.1.10.9.35 Address Information Compilation - eCH-0010 (DYNAMIC)		IHE PalM TF3 Rev.8, 6.3.2.16
hl7:telecom
TEL1 … *All persons and organizations, MUST according to XD-LAB contain name, addr and telecom.IHE PalM TF3 Rev.8, 6.3.2.16
hl7:playingEntity
Contains 2.16.756.5.30.1.1.10.9.20 PlayingEntity Compilation with name (DYNAMIC)IHE PalM TF3 Rev.8, 6.3.2.16