Template

Show index

Template Pan-Canadian dataEnterer 2019‑09‑12 23:47:05

Id2.16.840.1.113883.3.1937.99.61.21.10.32Effective Date2019‑09‑12 23:47:05
Statusdraft DraftVersion Label
NamepanCanadiandataEnterer-nha-nsDisplay NamePan-Canadian dataEnterer
DescriptionTemplate CDA dataEnterer (prototype, directly derived from POCD_RM000040 MIF)
ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 1 template, Uses 1 template
Used by as NameVersion
2.16.840.1.113883.3.1937.99.61.21.10.23Includedraft Pan-Canadian Header Practice (0.01)2019‑09‑11 01:40:57
Uses as NameVersion
2.16.840.1.113883.3.1937.99.61.21.10.31Includedraft Pan-Canadian AssignedEntityDYNAMIC
RelationshipSpecialization: template 2.16.840.1.113883.10.12.103 CDA dataEnterer (2005‑09‑07)
ref
ad1bbr-
ItemDTCardConfDescriptionLabel
hl7:dataEnterer
0 … 1RThe dataEnterer element represents the person who transferred the content, written or dictated by someone else, into the clinical document.
panCdotsa‑ns
@typeCode
cs1 … 1FENT
@contextControlCode
cs1 … 1FOP
 ConstraintSHALL SUPPORT up to one [0..1] dataEnterer.

Note: SHALL SUPPORT = These content elements may or may not be present in the message but implementers are required to support the interchange of this information.
hl7:time
TS0 … 1panCdotsa‑ns
 ConstraintSHOULD contain zero or one [0..1] time
hl7:assignedEntity
1 … 1RpanCdotsa‑ns
 ConstraintSHALL SUPPORT exactly one [1..1] assignedEntity.
Included from 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)
@classCode
cs1 … 1FASSIGNED
hl7:id
II1 … *MpanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 ConstraintSHALL contain at least one [1..*] id and SHALL NOT contain nullFlavor.
hl7:code
CE0 … 1panCdotsa‑ns
 Constraint
SHOULD contain zero or one [0..1] code which
  • SHALL comply with the following value set assertion effective 2012-05-31: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.265 ProviderRoleCode STATIC.
hl7:addr
AD.CA.BASIC0 … *panCdotsa‑ns
 Constraint
SHOULD contain zero or more [0..*] addr.
  • The content of addr SHALL be a conformant Canadian Realm Address Data Type.
hl7:telecom
TEL.CA.PHONE0 … *panCdotsa‑ns
 Constraint
SHOULD contain zero or more [0..*] telecom.
  • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type.
hl7:assignedPerson
0 … 1RpanCdotsa‑ns
 ConstraintSHALL SUPPORT up to one [0..1] assignedPerson.

Note: SHALL SUPPORT = These content elements may or may not be present in the message but implementers are required to support the interchange of this information."
Included from 2.16.840.1.113883.3.1937.99.61.21.10.27 Pan-Canadian Person (DYNAMIC)
@classCode
cs1 … 1FPSN
@determinerCode
cs1 … 1FINSTANCE
hl7:name
PN.CA1 … *MpanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 Constraint
SHALL contain at least one [1..*] name and SHALL NOT be nullFlavor.
  • Each name SHALL, when present be represented using in the Canadian Realm Person Name Data Type.
hl7:representedOrganization
0 … 1RpanCdotsa‑ns
 ConstraintSHALL SUPPORT up to one [0..1] representedOrganization.

Note: SHALL SUPPORT = These content elements may or may not be present in the message but implementers are required to support the interchange of this information."
Included from 2.16.840.1.113883.3.1937.99.61.21.10.25 Pan-Canadian Organization (DYNAMIC)
@classCode
cs1 … 1FORG
@determinerCode
cs1 … 1FINSTANCE
hl7:id
II1 … *RpanCdotsa‑ns
 Constraint
SHALL contain at least one [1..*] id
  • If name contains nullFlavor then id SHALL NOT contain nullFlavor
hl7:name
ON1 … *RpanCdotsa‑ns
 ConstraintSHOULD contain at least one [1..*] name.
  • If id contains nullFlavor then name SHALL NOT contain nullFlavor
hl7:telecom
TEL.CA.PHONE0 … *panCdotsa‑ns
 Constraint
SHOULD contain zero or more [0..*] telecom.
  • The content SHALL conform to the Canadian Realm Telecom data type.
hl7:addr
AD.CA.BASIC0 … *panCdotsa‑ns
 Constraint
SHOULD contain zero or more [0..*] addr.
  • The content SHALL conform to Canadian Realm Address data type.