Template

Show index

Template Pan-Canadian Header Practice 2019‑09‑11 01:40:57

Id2.16.840.1.113883.3.1937.99.61.21.10.23Effective Date2019‑09‑11 01:40:57
Statusdraft DraftVersion Label0.01
NamePanCandadianHeader-nha-nsDisplay NamePan-Canadian Header Practice
Description
Template CDA ClinicalDocument (prototype, directly derived from POCD_RM000040 MIF)

Conformance Verbs:

Mandatory: expressed with the keyword "SHALL". The data SHALL be sent and the use of nullFlavor is not permitted. The conformance statement shall explicitly say “SHALL NOT contain nullFlavor”. Note that any element declared to be Mandatory must have a minimum cardinality of one.
  • A valid instance of this message must include all mandatory content elements.

Populated: expressed with the keyword "SHALL". The data SHALL be sent if available. The keyword "SHALL" implicitly allows the use of nullFlavor. Note that any element declared to be Populated must have a minimum cardinality of one.
  • Content elements in this category must be present in all circumstances. However, on occasion, values for these elements will not be present and a nullFlavour would be provided to indicate why the data is not being provided (e.g. masked for hidden/protected data, unable to send due to regulatory constraint).

Required: expressed with the keyword "SHALL SUPPORT". The data SHALL be sent if available. Note that any element declared to be Required has a minimum cardinality of zero.
  • These content elements may or may not be present in the message but implementers are required to support the interchange of this information.

Optional: both SHOULD and MAY can be used to express the optional conformance. If there is a need to provide guidance to implementers, SHOULD is preferred.
  • These content elements may or may not be present and there is no requirement for implementers to support the interchange of this information.

Vocabulary Conformance

The templates in this document draw vocabulary content from several terminology code systems such as LOINC® and SNOMED CT®. These vocabularies are defined in various supporting specifications and may be maintained by other bodies, as is the case for the LOINC® and SNOMED CT® vocabularies.

Note that value-set identifiers (e.g., ValueSet 2.16.840.1.113883.1.11.78 Observation Interpretation (HL7) STATIC) do not appear in CDA submissions; they are tied to the conformance requirements of an implementation guide and to the appropriate code system for validation.
ContextPathname //
ClassificationCDA Document Level Template
Open/ClosedClosed (only defined elements are allowed)
Used by / Uses
Used by 0 transactions and 0 templates, Uses 15 templates
Uses as NameVersion
2.16.840.1.113883.3.1937.99.61.21.10.24Includedraft Pan-Canadian recordTarget (0.03)DYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.29Includedraft Pan-Canadian Author (0.01)DYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.32Includedraft Pan-Canadian dataEntererDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.33Includedraft Pan-Canadian InformantDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.35Includedraft Pan-Canadian CustodianDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.36Includedraft Pan-Canadian informationRecipientDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.37Includedraft Pan-Canadian legalAuthenticatorDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.38Includedraft Pan-Canadian authenticatorDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.39Includedraft Pan-Canadian ParticipantDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.40Includedraft Pan-Canadian RelatedDocumentDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.42Includedraft Pan-Canadian inFulfillmentOfDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.43Includedraft Pan-Canadian DocumentationOfDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.44Includedraft Pan-Canadian AuthorizationDYNAMIC
2.16.840.1.113883.3.1937.99.61.21.10.45Includedraft Pan-Canadian componentOfDYNAMIC
2.16.840.1.113883.10.12.112Includeactive CDA componentDYNAMIC
RelationshipSpecialization: template 2.16.840.1.113883.10.12.1 CDA ClinicalDocument (2005‑09‑07)
ref
ad1bbr-
ItemDTCardConfDescriptionLabel
hl7:ClinicalDocument
Pan-Canadian Realm Header

The General Header template describes constraints that apply to the pan-Canadian header. This header reflects the constraints that are defined in the other Canadian CDA implementation guides.
PanCdotsa‑ns
@classCode
cs1 … 1FDOCCLIN
@moodCode
cs1 … 1FEVN
hl7:realmCode
CS1 … 1MDefines the realm code for use by Canada.
PanCdotsa‑ns
 ConstraintSHALL contain exactly one [1..1] realmCode to be fixed to the code CA from the code system HL7Realm having the OID 2.16.840.1.113883.5.1124 effective 2013-03-18.
@code
CONF1 … 1FCA
@codeSystem
1 … 1F2.16.840.1.113883.5.1124
hl7:typeId
II1 … 1MThe typeId is a technology-neutral explicit reference to this CDA, Release Two specification.
PanCdotsa‑ns
@root
uid1 … 1F2.16.840.1.113883.1.3
@extension
st1 … 1FPOCD_HD000040
hl7:templateId
II1 … *M
CDA provides a mechanism to reference a template that has been assigned a unique identifier using the templateId attribute.

A ClinicalDocument that conforms to the pan-Canadian Header specification shall contain at least the pan-Canadian header templateId.
PanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
@root
uid1 … 1F2.16.840.1.113883.2.20.4.1.1
 Constraint
SHALL contain one or more [1..*] templateId :
  1. SHALL contain exactly one [1..1] @root be fixed to 2.16.840.1.113883.2.20.4.1.1 that represents the pan-Canadian CDA Header and SHALL NOT contain nullFlavor.
hl7:id
II1 … 1MRepresents the unique instance identifier of a clinical document.
PanCdotsa‑ns
 ConstraintSHALL contain exactly one [1..1] id represented using II from Data Type Release 1 and SHALL NOT contain nullFlavor.
hl7:code
CE (required)1 … 1RThe code specifies the particular type of document (e.g. History and Physical, Discharge Summary, Progress Note).
PanCdotsa‑ns
 Constraint
SHALL contain exactly one [1..1] code
  • SHALL comply with the following value set assertion, effective 2013-04-01: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.206 CDAHeaderDocumentType STATIC and SHALLNOT contain nullFlavor.
  • If the code is missing, the nullFlavor SHALL be set to OTH.
    Note: contradictory nullFlavor instructions in the Pan-Canadian Implementation Guide
hl7:title
ST0 … 1Represents the title of the document. The Clinical Document title can either be a locally defined name or the display name corresponding to clinicalDocument/code.
PanCdotsa‑ns
 Constraint
SHALL contain zero or one [0..1] title.
  1. The title SHALL NOT conflict with the clinicalDocument/code
hl7:effectiveTime
TS1 … 1MRepresents the document creation time, when the document first came into being. Where the CDA document is a transform from an original document in some other format, the ClinicalDocument.effectiveTime is the time the original document is created.
PanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 Constraint
SHALL contain exactly one [1..1] effectiveTime and SHALL NOT contain nullFlavor
  1. The content of effectiveTime SHALL be conformant to Canadian realm Date and Time Data Type.
hl7:confidentialityCode
CE1 … 1MConfidentiality code indicates the appropriate control on disclosure of information in the document. Confidentiality is a required contextual component of CDA, where the value expressed in the header holds true for the entire document, unless overridden by a nested value.
PanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 Constraint
SHALL contain exactly one [1..1] confidentialityCode
  1. SHALL comply with the following value set assertion, effective 2008-12-17: - the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.139 x_BasicConfidentialityKind STATIC and SHALL NOT contain nullFlavor.
hl7:languageCode
CS1 … 1MSpecifies the human language of the document.
PanCdotsa‑ns
 Constraint
SHALL contain exactly one [1..1] languageCode
  1. SHALL be fixed to the code “eng-CA” or “fra-CA” (3-letter ISO 639-3 language code and 2-letter ISO 3166-1 country code) from value set assertion, effective date 2012-05-31: - the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.190 LanguageCode STATIC and SHALL NOT contain nullFlavor.
hl7:setId
II0 … 1CRepresents an identifier that is common across all document revisions.
PanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 Constraint
SHOULD contain zero or one [0..1] setId.
  1. If setId is present versionNumber SHALL be present and SHALL NOT contain nullFlavor.
  2. If setId is present, it SHALL be represented using II from Data Type Release 1.
hl7:versionNumber
INT0 … 1CAn integer value used to version successive replacement documents.
PanCdotsa‑ns
@nullFlavor
cs0NPNP/not present
 Constraint
SHOULD contain zero or one [0..1] versionNumber.
  1. If versionNumber is present setId SHALL be present and SHALL NOT contain nullFlavor.
Included1 … *R from 2.16.840.1.113883.3.1937.99.61.21.10.24 Pan-Canadian recordTarget (DYNAMIC)
 ConstraintSHALL contain at least one [1..*] recordTarget.
hl7:recordTarget
1 … *RThe recordTarget records the information about the patient whose health information is described by the clinical document.
PanCdotsa‑ns
@typeCode
cs1 … 1FRCT
@contextControlCode
cs1 … 1FOP
hl7:patientRole
1 … 1MPanCdotsa‑ns
@classCode
cs1 … 1FPAT
 ConstraintSHALL contain exactly one [1..1] patientRole and SHALL NOT contain nullFlavor
hl7:id
II1 … *MPanCdotsa‑ns
 ConstraintSHALL contain at least one [1..*] id and SHALL NOT contain nullFlavor.
hl7:addr
AD.CA.BASIC0 … *PanCdotsa‑ns
 Constraint
This patientRole 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
 ConstraintThis patientRole SHOULD contain zero or more [0..*] telecom.
  • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type. If unknown, use the nullFlavor value set.
    hl7:patient
    1 … 1MPanCdotsa‑ns
    @classCode
    cs1 … 1FPSN
    @determinerCode
    cs1 … 1FINSTANCE
     ConstraintThis patientRole SHALL contain exactly one [1..1] patient and SHALL NOT contain nullFlavor.
    hl7:name
    PN.CA1 … *MPanCdotsa‑ns
    @use
    set_cs1 … 1R
    @nullFlavor
    cs0NPNP/not present
     Constraint
    This patient SHALL contain at least one [1..*] name and SHALL NOT be nullFlavor.
    • The content of name SHALL be a conformant Canadian Realm Patient Name data type.
    hl7:administrativeGenderCode
    CE (required)1 … 1RPanCdotsa‑ns
     ConstraintThis patient SHALL contain exactly one [1..1] administrativeGenderCode and SHALL comply with the following value set assertion, effective 2008-12-17: -
     the set of codes in the expansion of value set 2.16.840.1.113883.1.11.1 AdministrativeGenderSTATIC.
     CONF
    The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.1 AdministrativeGender (2014‑03‑26)
    hl7:birthTime
    TS1 … 1RPanCdotsa‑ns
     Constraint
    This patient SHALL contain exactly one [1..1] birthTime.
    • SHALL be conformant to Canadian Realm Date Time data type.
    hl7:maritalStatusCode
    CE (required)0 … 1PanCdotsa‑ns
     Constraint
    This patient SHOULD contain zero or one [0..1] maritalStatusCode and SHALL comply with the following value set assertion, effective 2013-03-18: - the set of codes in the expansion of value set 2.16.840.113883.1.11.12212 MaritalStatus STATIC.
     CONF
    The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.12212 MaritalStatus (2014‑03‑26)
    hl7:religiousAffiliationCode
    CE0 … 1PanCdotsa‑ns
     ConstraintThis patient MAY contain zero or one [0..1] religiousAffiliationCode. The value set to support this attribute is out of scope of this release.
    hl7:raceCode
    CE0 … 1PanCdotsa‑ns
     ConstraintThis patient MAY contain zero or one [0..1] raceCode. The value set to support this attribute is out of scope of this release.
    hl7:guardian
    0 … *PanCdotsa‑ns
    @classCode
    cs1 … 1FGUARD
     ConstraintThis patient MAY contain zero or more [0..*] guardian.
    hl7:id
    II0 … *PanCdotsa‑ns
     Constraint
    SHOULD contain zero or more [0..*] id.
    hl7:code
    CE (required)0 … 1PanCdotsa‑ns
     ConstraintSHOULD contain up to one [0..1] code.
      hl7:addr
      AD.CA.BASIC0 … *PanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] addr and each,
      1. SHALL, when present, conform to the Canadian Realm Address Data Type.
      hl7:telecom
      TEL.CA.PHONE0 … *PanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] telecom such that each,
      1. SHALL, when present, conform to the Canadian Realm Telecom Data Type.
      Choice1 … 1Elements to choose from:
      • hl7:guardianPerson
      • hl7:guardianOrganization
       ConstraintSHALL contain exactly one [1..1] guardianPerson or guardianOrganization
      hl7:guardianPerson
      PanCdotsa‑ns
      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:guardianOrganization
      PanCdotsa‑ns
      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.
      hl7:languageCommunication
      0 … *PanCdotsa‑ns
       ConstraintThis patient SHOULD contain zero or more [0..*] languageCommunication.
      hl7:languageCode
      CS0 … 1RPanCdotsa‑ns
       ConstraintSHALL contain zero or one [0..1] languageCode
      1. SHALL comply with the following value set assertion, 2012-05-31: - the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.190 LanguageCodeSTATIC.

      NOTE: Can't find any info on this OID or value set outside of the Pan-Canadian Implementation Guide
      hl7:modeCode
      CE (required)0 … 1PanCdotsa‑ns
       ConstraintIf [languageCommunication is] present, SHOULD contain zero or one [0..1] modeCode and SHALL comply with the following value set assertion, effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.1.11.12249 LanguageAbilityMode STATIC.
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.12249 LanguageAbilityMode (2014‑03‑26)
      hl7:proficiencyLevelCode
      CE (required)0 … 1PanCdotsa‑ns
       Constraint
      SHOULD contain zero or one [0..1] proficiencyLevelCode and
      1. SHALL comply with the following value set assertion, effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.1.11.12199 LanguageAbilityProficiencySTATIC.
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.12199 LanguageAbilityProficiency (2014‑03‑26)
      hl7:preferenceInd
      BL0 … 1PanCdotsa‑ns
       ConstraintMAY contain zero or one [0..1] preferenceInd.
      hl7:providerOrganization
      0 … 1PanCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] providerOrganization.
      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.
      Included1 … *M from 2.16.840.1.113883.3.1937.99.61.21.10.29 Pan-Canadian Author (DYNAMIC)
       ConstraintSHALL contain at least one [1..*] author and SHALL NOT contain nullFlavor.
      hl7:author
      1 … *MThe author element represents the creator of the clinical document. The author may be a device, or a person. The Author provides demographic information on the author(s) of the document.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FAUT
      @contextControlCode
      cs1 … 1FOP
      hl7:functionCode
      CE0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] functionCode and SHALL comply with the following value set assertion effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.87 ParticipationFunction STATIC.
      hl7:time
      TS1 … 1RpanCdotsa‑ns
       ConstraintSHALL contain exactly one [1..1] time.
      • This time SHALL contain exactly one [1..1] Canadian Realm Date Time Flavour data type.
      hl7:assignedAuthor
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FASSIGNED
      hl7:id
      II1 … *RpanCdotsa‑ns
       ConstraintSHALL contain at least one [1..*] id
      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 ProviderRoleCodeSTATIC
      Usage note: This is used when the assignedAuthor is a person (class assignedPerson below). When the assignedAuthor is a device (class assignedAuthoringDevice), this is currently not coded. In Canadian implementations as of this point in time, the software name (source system) and the manufacturerModelName (the device name) may be provided using SC data type, which means uncoded text may be used. We encourage implementations to come forward with device types for pan-Canadian value set creation.
      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.
      Choice1 … 1Elements to choose from:
      • hl7:assignedPerson
      • hl7:assignedAuthoringDevice
      hl7:assignedPerson
      panCdotsa‑ns
      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:assignedAuthoringDevice
      panCdotsa‑ns
      hl7:representedOrganization
      0 … 1panCdotsa‑ns
      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.
      Included0 … 1R from 2.16.840.1.113883.3.1937.99.61.21.10.32 Pan-Canadian dataEnterer (DYNAMIC)
       ConstraintSHALL SUPPORT up to one [0..1] dataEnterer.
      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.
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.33 Pan-Canadian Informant (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] informant.
      hl7:informant
      0 … *
      The informant element describes the source of the information in a medical document.

      An informant (or source of information) is a person that provides relevant information, such as the parent of a comatose patient who describes the patient's behaviour.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FINF
      @contextControlCode
      cs1 … 1FOP
      Choice1 … 1Elements to choose from:
      • hl7:assignedEntity
      • hl7:relatedEntity
       ConstraintSHALL contain exactly one [1..1] assignedEntity OR exactly one [1..1] relatedEntity.
      hl7:assignedEntity
      panCdotsa‑ns
      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.
      hl7:relatedEntity
      panCdotsa‑ns
      Included from 2.16.840.1.113883.3.1937.99.61.21.10.34 Pan-Canadian RelatedEntity (DYNAMIC)
      @classCode
      cs1 … 1R
       CONF
      The value of @classCode shall be drawn from value set 2.16.840.1.113883.1.11.19316 RoleClassMutualRelationship (DYNAMIC)
      hl7:code
      CE0 … 1RpanCdotsa‑ns
       Constraint
      SHALL SUPPORT zero or one [0..1] code
      • SHALL comply with the following value set assertion effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.90 PersonalRelationshipRoleTypeSTATIC.
      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: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:effectiveTime
      IVL_TS0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] effectiveTime
      • The content of effectiveTimeSHALL be conformant to Canadian realm Date and Time data type.

      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:relatedPerson
      0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] relatedPerson.

      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.
      Included1 … 1M from 2.16.840.1.113883.3.1937.99.61.21.10.35 Pan-Canadian Custodian (DYNAMIC)
       ConstraintSHALL contain exactly one [1..1] custodian and SHALL NOT contain nullFlavor.
      hl7:custodian
      1 … 1MThe custodian element represents the organization that is in charge of maintaining the document. The custodian is the steward that is entrusted with the care of the document. Every CDA document has exactly one custodian.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FCST
      hl7:assignedCustodian
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FASSIGNED
       ConstraintSHALL contain exactly one [1..1] assignedCustodian.
      hl7:representedCustodianOrganization
      1 … 1RpanCdotsa‑ns
       ConstraintSHALL contain exactly one [1..1] representedCustodianOrganization.
      Included1 … 1R 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 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain at least one [1..*] id
      • If name contains nullFlavor then id SHALL NOT contain nullFlavor
      hl7:name
      ON1 … 1RpanCdotsa‑ns
       ConstraintSHOULD contain at least one [1..*] name.
      • If id contains nullFlavor then name SHALL NOT contain nullFlavor
      hl7:telecom
      TEL.CA.PHONE1 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] telecom.
      • The content SHALL conform to the Canadian Realm Telecom data type.
      hl7:addr
      AD.CA.BASIC1 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] addr.
      • The content SHALL conform to Canadian Realm Address data type.
      Included0 … *R from 2.16.840.1.113883.3.1937.99.61.21.10.36 Pan-Canadian informationRecipient (DYNAMIC)
       ConstraintSHALL SUPPORT zero or more [0..*] informationRecipient.
      hl7:informationRecipient
      0 … *RThe informationRecipient element records the intended recipient of the information at the time the document is created.
      panCdotsa‑ns
      @typeCode
      cs1 … 1R
       CONF
      The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19366 x_InformationRecipient (2014‑03‑26)
      hl7:intendedRecipient
      1 … 1MpanCdotsa‑ns
      @classCode
      cs1 … 1FASSIGNED
       ConstraintSHALL contain exactly one [1..1] intendedRecipient.
      hl7:id
      II0 … *RpanCdotsa‑ns
       ConstraintSHALL SUPPORT zero or more [0..*] id
      hl7:addr
      AD.CA.BASIC0 … *panCdotsa‑ns
       ConstraintSHOULD 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
       ConstraintSHOULD contain zero or more [0..*] telecom.
      • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type.
      hl7:informationRecipient
      0 … 1RpanCdotsa‑ns
       ConstraintThis intendedRecipient SHALL SUPPORT up to one [0..1] informationRecipient
      Included0 … 1R 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.CA0 … 1M

      noticeWarning: If isMandatory=true, minimumMultiplicity shall be greater than 0.

      panCdotsa‑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:receivedOrganization
      0 … 1RpanCdotsa‑ns
       ConstraintThis intendedRecipient SHALL SUPPORT up to one [0..1] receivedOrganization.
      Included0 … 1R 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
      II0 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain at least one [1..*] id
      • If name contains nullFlavor then id SHALL NOT contain nullFlavor
      hl7:name
      ON0 … 1RpanCdotsa‑ns
       ConstraintSHOULD contain at least one [1..*] name.
      • If id contains nullFlavor then name SHALL NOT contain nullFlavor
      hl7:telecom
      TEL.CA.PHONE0 … 1RpanCdotsa‑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 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] addr.
      • The content SHALL conform to Canadian Realm Address data type.
      Included0 … 1 from 2.16.840.1.113883.3.1937.99.61.21.10.37 Pan-Canadian legalAuthenticator (DYNAMIC)
       ConstraintSHOULD contain up to one [0..1] legalAuthenticator.
      hl7:legalAuthenticator
      0 … 1The legalAuthenticator identifies the person who has legally authenticated the document.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FLA
      @contextControlCode
      cs1 … 1FOP
      hl7:time
      TS1 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain exactly one [1..1] time.
      • The content of time SHALL be a conformant Canadian Realm Date and Time data type.
      hl7:signatureCode
      CS1 … 1RpanCdotsa‑ns
       ConstraintSHALL contain exactly one [1..1] signatureCode and SHALL be fixed to the code S from the code system Participationsignature having the OID 2.16.840.1.113883.5.89 effective 2013-03-18
      hl7:assignedEntity
      1 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT exactly one [1..1] assignedEntity.
      Included1 … 1R from 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)
      @classCode
      cs1 … 1FASSIGNED
      hl7:id
      II1 … 1MpanCdotsa‑ns
      @nullFlavor
      cs0NPNP/not present
       ConstraintSHALL contain at least one [1..*] id and SHALL NOT contain nullFlavor.
      hl7:code
      CE1 … 1RpanCdotsa‑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.BASIC1 … 1RpanCdotsa‑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.PHONE1 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] telecom.
      • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type.
      hl7:assignedPerson
      1 … 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
      1 … 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.
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.38 Pan-Canadian authenticator (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] authenticator.
      hl7:authenticator
      0 … *The authenticator identifies a participant or participants who attested to the accuracy of the information in the document.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FAUTHEN
      hl7:time
      TS1 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain exactly one [1..1] time.
      • The content of time SHALL be a conformant Canadian Realm Date and Time data type.

      hl7:signatureCode
      CS (required)1 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain exactly one [1..1] signatureCode.
      • SHALL contain exactly one [1..1] signatureCode and SHALL be fixed to the code S
      @code
      CONF0 … 1FS
      hl7:assignedEntity
      1 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT exactly one [1..1] assignedEntity.
      Included1 … 1R from 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)
      @classCode
      cs1 … 1FASSIGNED
      hl7:id
      II1 … 1MpanCdotsa‑ns
      @nullFlavor
      cs0NPNP/not present
       ConstraintSHALL contain at least one [1..*] id and SHALL NOT contain nullFlavor.
      hl7:code
      CE1 … 1RpanCdotsa‑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.BASIC1 … 1RpanCdotsa‑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.PHONE1 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] telecom.
      • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type.
      hl7:assignedPerson
      1 … 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
      1 … 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.
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.39 Pan-Canadian Participant (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] participant.
      hl7:participant
      0 … *The participant element identifies other supporting participants, including parents, relatives, caregivers, insurance policyholders, guarantors, and other participants related in some way to the patient.
      panCdotsa‑ns
      @typeCode
      cs1 … 1R
       CONF
      The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.10901 ParticipationType (2014‑03‑26)
      @contextControlCode
      cs1 … 1FOP
      hl7:functionCode
      CE0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] functionCode and SHALL comply with the following value set assertion effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.87 ParticipationFunction STATIC.
      hl7:time
      IVL_TS0 … 1panCdotsa‑ns
       ConstraintSHOULD contain [0..1] time.
      • This time SHALL conform to Canadian Realm Date and Time Data Type.
      hl7:associatedEntity
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1R
       CONF
      The value of @classCode shall be drawn from value set 2.16.840.1.113883.1.11.19313 RoleClassAssociative (2014‑03‑26)
       ConstraintSHALL SUPPORT exactly one [1..1] associatedEntity.
      hl7:id
      II0 … *RpanCdotsa‑ns
       ConstraintSHALL SUPPORT zero ore more [0..*] id.
      hl7:code
      CE0 … 1panCdotsa‑ns
       ConstraintSHALL SUPPORT contain zero or one [0..1] code which
      • SHALL comply with the following value set assertion effective 2013-03-18: the set of codes in the expansion of value set RoleCode STATIC.
       CONF
      shall be drawn from concept domain "RoleCode"
      hl7:addr
      AD.CA.BASIC0 … *RpanCdotsa‑ns
       ConstraintSHALL SUPPORT 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
       ConstraintSHALL SUPPORT zero or up [0..*] telecom.
      • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type
      hl7:associatedPerson
      0 … 1panCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] associatedPerson.
      Included0 … 1R 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.CA0 … 1M

      noticeWarning: If isMandatory=true, minimumMultiplicity shall be greater than 0.

      panCdotsa‑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:scopingOrganization
      0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] scopingOrganization.
      Included0 … 1R 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
      II0 … 1RpanCdotsa‑ns
       Constraint
      SHALL contain at least one [1..*] id
      • If name contains nullFlavor then id SHALL NOT contain nullFlavor
      hl7:name
      ON0 … 1RpanCdotsa‑ns
       ConstraintSHOULD contain at least one [1..*] name.
      • If id contains nullFlavor then name SHALL NOT contain nullFlavor
      hl7:telecom
      TEL.CA.PHONE0 … 1RpanCdotsa‑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 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] addr.
      • The content SHALL conform to Canadian Realm Address data type.
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.42 Pan-Canadian inFulfillmentOf (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] inFulfillmentOf.
      hl7:inFulfillmentOf
      0 … *The inFulfillmentOf element represents orders that are fulfilled by this document.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FFLFS
      hl7:order
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FACT
      @moodCode
      cs1 … 1FRQO
       ConstraintSHALL* contain exactly one [1..1] order


      * orginal text is SHOULD - inconsistent with usage for 1..1 cardinality
      hl7:id
      II1 … *RpanCdotsa‑ns
       ConstraintSHALL contain at least one [1..*] id.
      hl7:code
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] code 
       CONF
      shall be drawn from concept domain "ActCode"
      hl7:priorityCode
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] priorityCode and SHALL comply with the following value set assertion, effective 2008-12-17: - the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.15 ActPrioritySTATIC
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.43 Pan-Canadian DocumentationOf (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] inFulfillmentOf.
      hl7:documentationOf
      0 … *A serviceEvent represents the main act, such as a colonoscopy or a cardiac stress study, being documented.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FDOC
      hl7:serviceEvent
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FACT
      @moodCode
      cs1 … 1FEVN
      hl7:id
      II0 … *panCdotsa‑ns
       ConstraintSHOULD contain zero or more [0..*] id.
      hl7:code
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] code
       CONF
      shall be drawn from concept domain "ActCode"
      hl7:effectiveTime
      IVL_TS0 … 1panCdotsa‑ns
       ConstraintSHOULD contain up to one [0..1] effectiveTime.
      hl7:performer
      0 … *panCdotsa‑ns
      @typeCode
      cs1 … 1R
       CONF
      The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19601 x_ServiceEventPerformer (2017‑03‑24)
       ConstraintSHOULD contain zero or more [0..*] performer
      hl7:functionCode
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain up to one [0..1] functionCode and SHALL comply with the following value set assertion effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.87 ParticipationFunctionSTATIC.
      hl7:time
      IVL_TS0 … 1panCdotsa‑ns
       Constraint
      SHOULD contain up to one [0..1] time
      • The content SHALL be a conformant Canadian Realm interval date time Data Type.
      hl7:assignedEntity
      1 … 1RpanCdotsa‑ns
       ConstraintSHALL contain exactly one [1..1] assignedEntity.
      Included1 … 1R from 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)
      @classCode
      cs1 … 1FASSIGNED
      hl7:id
      II1 … 1MpanCdotsa‑ns
      @nullFlavor
      cs0NPNP/not present
       ConstraintSHALL contain at least one [1..*] id and SHALL NOT contain nullFlavor.
      hl7:code
      CE1 … 1RpanCdotsa‑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.BASIC1 … 1RpanCdotsa‑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.PHONE1 … 1RpanCdotsa‑ns
       Constraint
      SHOULD contain zero or more [0..*] telecom.
      • The content of telecom SHALL be a conformant Canadian Realm Telecom Data Type.
      hl7:assignedPerson
      1 … 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
      1 … 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.
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.40 Pan-Canadian RelatedDocument (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] inFulfillmentOf.
      hl7:relatedDocument
      0 … *The relatedDocument element represents documents that are related to this document.
      panCdotsa‑ns
      @typeCode
      cs1 … 1R
       CONF
      The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.11610 x_ActRelationshipDocument (2014‑03‑26)
      hl7:parentDocument
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FDOCCLIN
      @moodCode
      cs1 … 1FEVN
       ConstraintSHOULD contain exactly one [1..1] ParentDocument.
      hl7:id
      II1 … *RpanCdotsa‑ns
       ConstraintSHALL contain at least one [1..*] id.
      hl7:code
      CD0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] code
      • SHALL comply with the following value set assertion, effective 2013-03-18: set of codes from ActCode STATIC.
       CONF
      shall be drawn from concept domain "ActCode"
      hl7:text
      ED0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] text
      hl7:setId
      II0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] setId
      hl7:versionNumber
      INT0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] versionNumber
      Included0 … * from 2.16.840.1.113883.3.1937.99.61.21.10.44 Pan-Canadian Authorization (DYNAMIC)
       ConstraintSHOULD contain zero or more [0..*] authorization.
      hl7:authorization
      0 … *panCdotsa‑ns
      @typeCode
      cs1 … 1FAUTH
      hl7:consent
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FCONS
      @moodCode
      cs1 … 1FEVN
       ConstraintSHALL* contain exactly one [1..1] consent.

      *original had SHOULD - inconsistent with 1..1 cardinality
      hl7:id
      II0 … *panCdotsa‑ns
       ConstraintSHOULD contain zero or more [0..*] id.
      hl7:code
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] code and SHALL comply with the following value set assertion, effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.6 ActConsentTypeSTATIC
      hl7:statusCode
      CS1 … 1RpanCdotsa‑ns
       ConstraintSHALL contain exactly one [1..1] statusCode
      @code
      CONF0 … 1Fcompleted
      Included0 … 1 from 2.16.840.1.113883.3.1937.99.61.21.10.45 Pan-Canadian componentOf (DYNAMIC)
       ConstraintSHOULD contain up to one [0..1] componentOf.
      hl7:componentOf
      0 … 1The componentOf element is used to wrap the encompassing encounter for this document. The encompassing encounter represents the setting of the clinical encounter during which the document act(s) or ServiceEvent occurred.
      panCdotsa‑ns
      @typeCode
      cs1 … 1FCOMP
      hl7:encompassingEncounter
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FENC
      @moodCode
      cs1 … 1FEVN
       ConstraintSHALL [contain] exactly one [1..1] encompassingEncounter.
      hl7:id
      II0 … *RpanCdotsa‑ns
       ConstraintSHALL SUPPORT zero or more [0..*] id.
      hl7:code
      CE0 … 1RpanCdotsa‑ns
       ConstraintSHALL SUPPORT up to one [0..1] code and SHALL comply with the following value set assertion, effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.2 ActCareEventType STATIC
      hl7:effectiveTime
      IVL_TS1 … 1MpanCdotsa‑ns
      @nullFlavor
      cs0NPNP/not present
       Constraint
      SHALL contain exactly one [1..1] effectiveTime and SHALL NOT contain nullFlavor
      • The content SHALL be a conformant Canadian Realm Date Time Interval data type.
      hl7:dischargeDispositionCode
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain up to one [0..1] dischargeDispositionCode and SHALL comply with the following value set assertion, effective 2008-12-17: the set of codes in the expansion of value set 2.16.840.1.113883.2.20.3.43 EncounterDischargeDisposition STATIC
      hl7:responsibleParty
      0 … 1RpanCdotsa‑ns
      @typeCode
      cs1 … 1FRESP
       ConstraintSHALL SUPPORT up to one [0..1] responsibleParty .
      hl7:assignedEntity
      1 … 1RContains 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)panCdotsa‑ns
      hl7:encounterParticipant
      0 … *RpanCdotsa‑ns
      @typeCode
      cs1 … 1R
       CONF
      The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19600 x_EncounterParticipant (2011‑07‑26)
       Constraint
      SHALL SUPPORT zero or more [0..*] encounterParticipant.
      • SHALL contain exactly one [1..1] typeCode and SHALL comply with the following value set assertion effective 2013-03-18: the set of codes in the expansion of value set 2.16.840.1.113883.1.11.19600 x_EncounterParticipantSTATIC.
      hl7:time
      IVL_TS0 … 1panCdotsa‑ns
       Constraint
      SHOULD contain zero or one [0..1] time.
      • The content SHALL be a conformant Canadian Realm Date Time Interval data type.
      hl7:assignedEntity
      1 … 1RContains 2.16.840.1.113883.3.1937.99.61.21.10.31 Pan-Canadian AssignedEntity (DYNAMIC)panCdotsa‑ns
      hl7:location
      0 … 1panCdotsa‑ns
      @typeCode
      cs1 … 1FLOC
       ConstraintSHOULD contain up to one [0..1] location.
      hl7:healthCareFacility
      1 … 1RpanCdotsa‑ns
      @classCode
      cs1 … 1FSDLOC
       Constraint[SHALL contain exactly one [1..1] healthCareFacilty]*

      * Pan-Canadian IG has "SHOULD contain zero or one [0..1] healthCareFacility."  this is counter the CDA r2 spec  (also no point to have a location with zero healthCareFacility as it contains all the discrete data)
      hl7:id
      II0 … *panCdotsa‑ns
       ConstraintSHALL SUPPORT zero or more [0..*] id.
      hl7:code
      CE0 … 1panCdotsa‑ns
       ConstraintSHOULD contain up to one [0..1] code and SHALL comply with the following value set assertion effective 2008-12-17: the set of codes in the expansion of 2.16.840.1.113883.2.20.3.182 ServiceDeliveryLocationRoleTypeSTATIC.
      hl7:location
      0 … 1panCdotsa‑ns
      @classCode
      cs1 … 1FPLC
      @determinerCode
      cs1 … 1FINSTANCE
       ConstraintSHOULD contain up to one [0..1] location.
      hl7:name
      ON0 … 1panCdotsa‑ns
       ConstraintSHOULD contain zero or one [0..1] name
      hl7:addr
      AD.CA.BASIC0 … 1panCdotsa‑ns
       Constraint
      SHOULD contain zero or one [0..1] addr
      • The content of addr SHALL be a conformant Canadian Realm Address data type.
      hl7:serviceProviderOrganization
      0 … 1Contains 2.16.840.1.113883.3.1937.99.61.21.10.25 Pan-Canadian Organization (DYNAMIC)panCdotsa‑ns
       ConstraintSHOULD contain up to one [0..1] serviceProviderOrganization.
      Included1 … 1R from 2.16.840.1.113883.10.12.112 CDA component (DYNAMIC)
      hl7:component
      1 … 1RCDAcdotsnent
      @typeCode
      cs0 … 1FCOMP
      @contextConductionInd
      bl0 … 1Ftrue
      Choice1 … 1Elements to choose from:
      Included from 2.16.840.1.113883.10.12.203 CDA NonXMLBody (DYNAMIC)
      hl7:nonXMLBody
      CDANdotsBody
      @classCode
      cs0 … 1FDOCBODY
      @moodCode
      cs0 … 1FEVN
      hl7:text
      ED1 … 1CDANdotsBody
      hl7:confidentialityCode
      CE0 … 1CDANdotsBody
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.16926 HL7 BasicConfidentialityKind (DYNAMIC)
      hl7:languageCode
      CS0 … 1CDANdotsBody
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.11526 HumanLanguage (DYNAMIC)
      Included from 2.16.840.1.113883.10.12.202 CDA StructuredBody (DYNAMIC)
      hl7:structuredBody
      CDASdotsBody
      @classCode
      cs0 … 1FDOCBODY
      @moodCode
      cs0 … 1FEVN
      hl7:confidentialityCode
      CE0 … 1CDASdotsBody
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.16926 HL7 BasicConfidentialityKind (DYNAMIC)
      hl7:languageCode
      CS0 … 1CDASdotsBody
       CONF
      The value of @code shall be drawn from value set 2.16.840.1.113883.1.11.11526 HumanLanguage (DYNAMIC)
      hl7:component
      1 … *Contains 2.16.840.1.113883.10.12.201 CDA Section (DYNAMIC)CDASdotsBody
      @typeCode
      cs0 … 1FCOMP
      @contextConductionInd
      bl0 … 1Ftrue