Id1.3.6.1.4.1.12559.11.10.1.3.1.1.7
ref
epsos-
Effective Date2020‑09‑09 12:49:26
Statusretired RetiredVersion Label
NameeHDSI-OriginalPSDisplay NameeHDSI Patient Summary PDF embedded
Description

eHDSI Patient Summary PDF embedded Template 

The implementers must be familiar with the context of the project, as it shall not be repeated in this document. The implementers must also be familiar with the content of the following documents:

  • CDA Release 2.0 Normative Web Edition, May, 2005
  • HL7 Implementation Guide: CDA Release 2 – Continuity of Care Document (CCD), HL7, April 1, 2007.
  • Integrating the Healthcare Enterprise, Patient Care Coordination Technical Framework, Volume 1 and Volume 2- Revision 10, IHE International, November 4, 2014.
  • Integrating the Healthcare Enterprise, Patient Care Coordination CDA Content Modules- Trial Implementation Supplement, December 3, 2014.
  • HL7 Implementation Guide for CDA Release 2: History and Physical (H&P) Notes, HL7, July 16, 2008.

It must also be noted that although the guidelines are based on the above documents, they contain specific developments particular to the project epSOS. This document can be used as a standalone to develop the syntax of the epSOS documents; however in order to achieve the full functionality of the epSOS Semantic Services, they are to be used within the context of the deliverable 3.9.1.

Prescribed and dispensed medications, including a specification of the Medication Summary section used in the Patient Summary document, have described in the previous chapter. The following sub-paragraphs specify how other sections that may be present in a Patient Summary are implemented.

According to requirements described in the Body Data Elements, the following sections - at least - shall be present in a Patient Summary document:

  • The eHDSI Medication Summary Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.3
  • The eHDSI Allergies and Other Adverse Reactions Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.12
  • The eHDSI List of Surgeries Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.11
  • The eHDSI Active Problems Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.9
  • The eHDSI Medical Devices Section 1.3.6.1.4.1.12559.11.10.1.3.1.2.4
ContextPathname /
ClassificationCDA Document Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 0 templates, Uses 9 templates
Uses as NameVersion
2.16.840.1.113883.3.1937.777.11.10.100Includeactive eHDSI RecordTargetDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.101Includeactive eHDSI Contact/Preferred HP/Legal OrganizationDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.102Includeactive eHDSI AuthorDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.104Includeactive eHDSI CustodianDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.106Includeactive eHDSI DocumentationOf PCPRDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.107Includeactive eHDSI RelatedDocumentDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.108Includeactive eHDSI SetIdDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.109Includeactive eHDSI LegalAuthenticatorDYNAMIC
2.16.840.1.113883.3.1937.777.11.10.110Includeactive eHDSI IdDYNAMIC
ItemDTCardConfDescriptionLabel
hl7:ClinicalDocument
RCDA headereHDSdotsalPS
 Schematron assertrolered error 
 testnot(@xsi:schemaLocation) 
 MessageWhile the XML Schema Language allows a schema location to be associated with an XML document by including a schemaLocation attribute associated with the http://www.w3.org/2001/XMLSchema-instance namespace, this is explicitly PROHIBITED by [ITS§1.4], and thus by the CDA standard. 
hl7:realmCode
CS0 … 1ReHDSdotsalPS
hl7:typeId
II.EPSOS1 … 1M The clinical document typeId identifies the constraints imposed by CDA R2 on the content, essentially acting as a version identifier.

The @root and @extension values of this element are specified as shown in the example below.

eHDSdotsalPS
@root
uid1 … 1F2.16.840.1.113883.1.3
@extension
st1 … 1FPOCD_HD000040
 Example<typeId extension="POCD_HD000040" root="2.16.840.1.113883.1.3"/>
hl7:templateId
II1 … 1MeHDSI Patient Summary PDF embedded
eHDSdotsalPS
@root
uid1 … 1F1.3.6.1.4.1.12559.11.10.1.3.1.1.7
Included1 … 1M from 2.16.840.1.113883.3.1937.777.11.10.110 eHDSI Id (DYNAMIC)
hl7:id
II1 … 1M

Unique identifier of this instance of the clinical document.

Following attributes can be used to uniquely identify the instance:

  • @root: A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier. Required if @nullFlavor is not present.
  • @extension: An optional character string as a unique identifier within the scope of the identifier root.

The @root attribute must be a UID. The allowable formats and values and procedures of this data type are strictly controlled by HL7. At this time, user-assigned identifiers may be certain character representations of ISO Object Identifiers (OID) and DCE Universally Unique Identifiers (UUID).
  • UUIDs SHALL be represented in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set [0-9a-zA-Z].
  • OIDs SHALL be represented in dotted decimal notation, where each decimal number is either 0, or starts with a nonzero digit. More formally, an OID SHALL be in the form [0-2](\.(0|[1-9][0-9]*))*.
R1.11.3
 Example<id extension="a621" root="2.16.840.1.113883.3.1937.777.11.9999"/>
hl7:code
CV.EPSOS1 … 1MDetermines the document type "eHDSI Patient Summary Document"R1.11.6
@displayName
1 … 1R
@code
CONF1 … 1F60591-5
@codeSystem
1 … 1F2.16.840.1.113883.6.1
 Example<code code="60591-5" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Patient summary Document"/>
hl7:title
ST1 … 1MClinicalDocument/title is used for display purposes.R1.11.7
 Example<title>eHDSI Patient Summary Maria Bakker November 13, 2011</title>
hl7:effectiveTime
TS.EPSOS.TZ1 … 1M

Relevant times for the Patient Summary

By definition, a Patient Summary document describes the Patient Summary at the time of creation of the document, represented by the /ClinicalDocument/effectiveTime XML Element.

The time when this instance of the document has been authored may be instead recorded by the /ClinicalDocument/author/time element. (e.g. when a “spider” has collected information for generating this instance of the document; or a practitioner updated its local summary document).

Finally, the latest summary update, intended as the last date documented by this summary (e.g. the last update occurred to the PHR from which the PS data has been extracted) can be represented by the /ClinicalDocument/documentationOf/serviceEvent/effectiveTime/high XML Element (see section 2.1, CONF-2, CONF-3 and CONF-4 of the CCD specification).

R1.11.1
 Example<effectiveTime value="20111113125600+0200"/>
hl7:confidentialityCode
CE.EPSOS1 … 1RClinicalDocument/confidentialityCode shall be present in accordance with the HL7 CDA R2 standard.R1.11.8
 CONF
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.31 eHDSIConfidentiality (DYNAMIC)
 Example<confidentialityCode code="N" codeSystem="2.16.840.1.113883.5.25"/>
hl7:languageCode
CS1 … 1M

Document Language Code

  • The language code SHALL be in the form nn-CC.
  • The nn portion SHALL be an ISO-639-1 language code in lower case.
  • The CC portion SHALL be an ISO-3166 country code in upper case.
    		R.11.10
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.6 eHDSILanguage (DYNAMIC)
     Example<languageCode code="en-GB"/>
     Schematron assertrolered error 
     testmatches(@code,'[a-z]{2}-[A-Z]{2}') 
     MessageThe language code SHALL be in the form nn-CC (where nn is ISO-639-1 language code and CC is ISO-3166 country code) 
    Included0 … 1 from 2.16.840.1.113883.3.1937.777.11.10.108 eHDSI SetId (DYNAMIC)
    hl7:setId
    		0 … 1R

    This identifier is used to link together different versions of the same document: the CDA L3 document, the CDA PDF embedded document and the version in the national infrastructure.

    		eHDSdotsetId
    hl7:versionNumber
    		0 … 1ReHDSdotsalPS
    Included1 … 1M from 2.16.840.1.113883.3.1937.777.11.10.100 eHDSI RecordTarget (DYNAMIC)
    hl7:recordTarget
    		1 … 1MeHDSdotsrget
    @typeCode
    		cs0 … 1FRCT
    @contextControlCode
    		cs0 … 1FOP
    hl7:patientRole
    		1 … 1MeHDSdotsrget
    @classCode
    		cs0 … 1FPAT
    hl7:id
    		II.EPSOS1 … *RPatient Identifiers: Primary Patient Identifier (Regional/National Health Id), Secondary Patient Identifier (Social/Insurance Number)R1.4 / R1.4.1 / R1.4.2
    hl7:addr
    		AD.EPSOS1 … 1RThe patient address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present. R1.5
    @nullFlavor
    		cs0 … 1FNI
    hl7:streetAddressLine
    		0 … *RPatient's Number of Street/Patient's Number of StreetR1.5.1 / R1.5.2
    hl7:city
    		0 … 1RPatient's CityR1.5.3
    hl7:postalCode
    		0 … 1RPatient's Postal CodeR1.5.4
    hl7:state
    		0 … 1RPatient's State or ProvinceR1.5.5
    hl7:country
    		0 … 1RPatient's Country. When used addr.country it is always bound to the eHDSICountry value setR1.5.6
     ConstraintThe content of this element SHALL be selected from ValueSet eHDSICountry urn:oid:1.3.6.1.4.1.12559.11.10.1.3.1.42.4
    hl7:telecom
    		TEL1 … *RPatient’s telephone number / Patient e-mail address. The patient telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements. R1.6.1 / R1.6.2
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
    hl7:patient
    		1 … 1MeHDSdotsrget
    @classCode
    		cs0 … 1FPSN
    @determinerCode
    		cs0 … 1FINSTANCE
    hl7:name
    		PN1 … *MPatient NameR1.1
    hl7:family
    		1 … *MPatient's Family Name/SurnameR1.1.1
    hl7:prefix
    		0 … *RPatient's PrefixR1.1.2
     ConstraintIf the attribute qualifier is used for this element it should be derived from epSOSEntityNamePartQualifier 2.16.840.1.113883.5.43
    hl7:given
    		1 … *MPatient's Given NameR1.1.3
    hl7:administrativeGenderCode
    		CE.EPSOS1 … 1RPatient's GenderR1.2
    @nullFlavor
    		cs0 … 1FUNK
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.34 eHDSIAdministrativeGender (DYNAMIC)
    hl7:birthTime
    		TS1 … 1MPatient's Date of Birth. The patient date of birth may be a partial date such as only the year.R1.3
    hl7:guardian
    		0 … *R

    The guardians of a patient shall be recorded in the <guardian> element beneath the /ClinicalDocument/recordTarget/patientRole/patient XML - <patient> element. Other patient contacts are described using the /ClinicalDocument/participant structure. The <associatedEntity> element defines the type of contact.

    The relationship between the patient and the guardian or other contact should be recorded in the <code> element. The code attribute is required and comes from the HL7 PersonalRelationshipRoleType vocabulary (eHDSIPersonalRelationship value set).

    The address of the guardian or other contact should be present, and shall be represented, as any other address would be in CDA.

    The phone number of the guardian or other contact should be present, and shall be represented, as any other phone number would be in CDA.

    The name of the guardian or other contact shall be present, and shall be represented, as any other name would be in CDA.

    		R1.7.A
    @classCode
    		cs1 … 1FGUARD
    @nullFlavor
    		cs0 … 1 Use nullFlavor if unknown or if no information is applicable
     Example<guardian classCode="GUARD">
      <templateId root="1.3.6.1.4.1.19376.1.5.3.1.2.4"/>  <code code="AUNT" displayName="aunt" codeSystem="2.16.840.1.113883.5.111"/>  <addr>
        <streetAddressLine>2222 Home Street</streetAddressLine>    <city>London</city>    <state>London</state>    <postalCode>A1B 2C3</postalCode>    <country>UK</country>  </addr>      <telecom value="tel:+452070256161"/>  <telecom value="mailto:jsmith@myprovider.co.uk"/>  <guardianPerson>
        <name>
          <given>John</given>      <family>Español Smith</family>    </name>      </guardianPerson>    </guardian>
    hl7:templateId
    		II.EPSOS1 … 1MTemplate id for IHE PCC Patient ContactsR1.7.A
    @root
    		uid1 … 1F1.3.6.1.4.1.19376.1.5.3.1.2.4
    hl7:code
    		CE.EPSOS0 … 1RThe relationship between the patient and the guardian or other contact may be recorded in the code element
    		R1.7.A
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.38 eHDSIPersonalRelationship (DYNAMIC)
    hl7:addr
    		AD.EPSOS1 … 1RThe guardian’s address element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present R1.7.A
    @nullFlavor
    		cs0 … 1FNI
    hl7:streetAddressLine
    		0 … *RGuardian's Number of Street/Guardian's Number of StreetR1.7dots.3.2
    hl7:city
    		0 … 1RGuardian's CityR1.7dots.3.3
    hl7:postalCode
    		0 … 1RGuardian's Postal CodeR1.7dots.3.4
    hl7:state
    		0 … 1RGuardian's State or ProvinceR1.7dots.3.5
    hl7:country
    		0 … 1RGuardian's Country. When used addr.country it is always bound to the eHDSICountry value setR1.7dots.3.6
     ConstraintThe content of this element SHALL be selected from ValueSet eHDSICountry urn:oid:1.3.6.1.4.1.12559.11.10.1.3.1.42.4
    hl7:telecom
    		TEL1 … *RGuardian’s telephone number / Patient e-mail address. The guardian telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements. R1.7dots.4.2
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
    hl7:guardianPerson
    		1 … 1RR1.7.A
    hl7:name
    		PN1 … *RPatient Guardian's NameIHE PCC
    Choice2 … *Elements to choose from:
    • hl7:family
    • hl7:given
    hl7:family
    		1 … *RPatient Guardian's Family Name/SurnameR1.7.A.1
    hl7:given
    		1 … *RPatient Guardian's Given NameR1.7.A.2
    hl7:languageCommunication
    		0 … *RThis element is derived from the IHE template LanguageCommunication (1.3.6.1.4.1.19376.1.5.3.1.2.1), however this template does not need the element preferenceInd because the language is already said to be the "preferred language".eHDSdotsrget
    hl7:languageCode
    		CS1 … 1RPatient’s preferred language
    • The language code SHALL be in the form nn-CC.
    • The nn portion SHALL be an ISO-639-1 language code in lower case derived by the Value Set eHDSILanguage.
    • The CC portion SHALL be an ISO-3166 country code in upper case derived by the value Set eHDSICountry.
    		R1.7
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.6 eHDSILanguage (DYNAMIC)
     Example<languageCode code="en-GB"/>
     Schematron assertrolered error 
     testmatches(@code,'[a-z]{2}-[A-Z]{2}') 
     MessageThe language code SHALL be in the form nn-CC where nn is ISO-639-1 eHDSILanguage and CC is ISO-3166 eHDSICountry 
    Included1 … *M from 2.16.840.1.113883.3.1937.777.11.10.102 eHDSI Author (DYNAMIC)
    hl7:author
    		1 … *MeHDSdotsthor
    @typeCode
    		cs0 … 1FAUT
    @contextControlCode
    		cs0 … 1FOP
    hl7:functionCode
    		CE.EPSOS0 … 1RR1.10.6
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.1 eHDSIHealthcareProfessionalRole (DYNAMIC)
    hl7:time
    		TS.EPSOS.TZ1 … 1RThe author/time element represents the start time of the author’s participation in the creation of the clinical document. The author/time element SHALL be present.eHDSdotsthor
    hl7:assignedAuthor
    		1 … 1MeHDSdotsthor
    @classCode
    		cs0 … 1FASSIGNED
    hl7:id
    		II.EPSOS1 … *RIdentification of the Healthcare Practitioner that is the author of this document or identification of an authoring device which generated this document.R1.10.5
    @nullFlavor
    		cs0 … 1FNA
    hl7:code
    		CE.EPSOS0 … 1RHP SpecialtyR1.10.7
    hl7:addr
    		AD.EPSOS1 … *RIHE PCC
    hl7:telecom
    		TEL.EPSOS1 … *RTelephone or e-mail <telecom> element is required.

    If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present.

    Attribute @value SHALL contain a URI if element telecom is used. The URI scheme SHALL be one of URLScheme.
    		IHE PCC / R1.10.8 / R1.10.8.1 / R1.10.8.2
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    Choice1 … 1Elements to choose from:
    hl7:assignedPerson
    		0 … 1CeHDSdotsthor
    @classCode
    		cs0 … 1FPSN
    @determinerCode
    		cs0 … 1FINSTANCE
    hl7:name
    		PN1 … 1RHP NameIHE PCC
     Example<name>
      <given>John</given>  <family>Español Smith</family></name>
    hl7:family
    		1 … *MHP Family Name/SurnameR1.10.1
    hl7:given
    		1 … *MHP Given NameR1.10.2
    hl7:prefix
    		0 … *RHP PrefixR1.10.3
    hl7:suffix
    		0 … *RHP SuffixR1.10.4
    hl7:assignedAuthoringDevice
    		0 … 1CContains 2.16.840.1.113883.3.1937.777.11.10.129 eHDSI Device (DYNAMIC)eHDSdotsthor
    hl7:representedOrganization
    		1 … 1RContains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC)R1.10.9
    Included1 … 1M from 2.16.840.1.113883.3.1937.777.11.10.104 eHDSI Custodian (DYNAMIC)
    hl7:custodian
    		1 … 1MThis elements represents the organization that is in charge of maintaining the document.
         		eHDSdotsdian
    @typeCode
    		cs0 … 1FCST
    hl7:assignedCustodian
    		1 … 1ReHDSdotsdian
    @classCode
    		cs0 … 1FASSIGNED
    hl7:representedCustodianOrganization
    		1 … 1ReHDSdotsdian
    @classCode
    		cs0 … 1FORG
    @determinerCode
    		cs0 … 1FINSTANCE
    hl7:id
    		II.EPSOS1 … 1RCustodian organization IdeHDSdotsdian
    @nullFlavor
    		cs0 … 1 
    hl7:name
    		ON1 … 1RCustodian organization Name
    		eHDSdotsdian
    @nullFlavor
    		cs0 … 1 
    hl7:telecom
    		TEL1 … 1R

    Custodian organization Telecom

    If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present.

    Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.

    		eHDSdotsdian
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
     Example<telecom use="WP" value="tel:+45 20 7025 6161"/>
    hl7:addr
    		AD.EPSOS1 … 1RCustodian Organization AddresseHDSdotsdian
     Schematron assertrolered error 
     test@nullFlavor or hl7:* 
     MessageIf addr is not nullflavored at least one sub element has to be provided 
    hl7:streetAddressLine
    		0 … *RStreet/Number of Street
    		eHDSdotsdian
    hl7:city
    		0 … 1RCity
    		eHDSdotsdian
    hl7:postalCode
    		0 … 1RPostal Code
    		eHDSdotsdian
    hl7:state
    		0 … 1RState or Province
    		eHDSdotsdian
    hl7:country
    		1 … 1RCountry. When used addr.country it is always bound to the eHDSICountry value set.
    		eHDSdotsdian
     ConstraintThe content of this element SHALL be selected from ValueSet eHDSICountry urn:oid:1.3.6.1.4.1.12559.11.10.1.3.1.42.4

    Included1 … 1M from 2.16.840.1.113883.3.1937.777.11.10.109 eHDSI LegalAuthenticator (DYNAMIC)
    hl7:legalAuthenticator
    		1 … 1MThe person taking responsibility for the medical content of the document. In Spain this is the regional authority in healthcare. This regional authority healthcare organization will send this to the NCP. The definition of the legal authenticator may vary accoriding to the rules set up in the framework agreement particular to each state. It may be a person or a regional authority, or an NCP.R1.11.9
    hl7:time
    		TS.EPSOS.TZ1 … 1MTime of signing the documentR1.11.9
    hl7:signatureCode
    		CS1 … 1RSignature codeR1.11.9
    @code
    		CONF0 … 1FS
    hl7:assignedEntity
    		1 … 1MThe regional authority that is responsible for the legal authentication of the CDA documentR1.11.9
    hl7:id
    		1 … 1MUnique identification of legal authenticatorR1.11.9
    hl7:addr
    		AD.EPSOS1 … *RIHE PCC
    hl7:telecom
    		TEL1 … *R

    Legal Authenticator's Telecom

    If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present.

    Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.

    		R1.10.9.4 / R1.10.9.4.1 / R1.10.9.4.2
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
     Example<telecom use="WP" value="tel:+45 20 7025 6161"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
    hl7:assignedPerson
    		1 … 1RIHE PCC
    @classCode
    		cs0 … 1FPSN
    @determinerCode
    		cs0 … 1FINSTANCE
    hl7:name
    		PN1 … 1RHP NameIHE PCC
     Example<name>
      <given>John</given>  <family>Español Smith</family></name>
    hl7:family
    		1 … *MHP Family Name/SurnameR1.10.1
    hl7:given
    		1 … *MHP Given NameR1.10.2
    hl7:prefix
    		0 … *RHP PrefixR1.10.3
    hl7:suffix
    		0 … *RHP SuffixR1.10.4
    hl7:representedOrganization
    		1 … 1MContains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC)R1.11.9
    Included0 … * from 2.16.840.1.113883.3.1937.777.11.10.101 eHDSI Contact/Preferred HP/Legal Organization (DYNAMIC)
    The IHE PCC template Patient Contacts shall be used for describing the patient contacts or the preferred HP.
    hl7:participant
    		0 … *RContact person / Preferred Health Professional to contact about patient.eHDSdotstion
    where [hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.2.4']
    @typeCode
    		cs1 … 1FINDR1.8.5
     Participant typeCode
    hl7:templateId
    		1 … 1MIHE Patient Contacts (IHE PCC)
    		eHDSdotstion
    @root
    		uid1 … 1F1.3.6.1.4.1.19376.1.5.3.1.2.4
    hl7:functionCode
    		0 … 1CeHDSdotstion
     ConstraintThe element is mandatory when this participant is the preferred HP
    @code
    		CONF0 … 1FPCP
    @codeSystem
    		0 … 1F2.16.840.1.113883.5.88
    hl7:time
    		IVL_TS.EPSOS.TZ.OPT0 … 1RThe eHDSdotstion
    hl7:associatedEntity
    		RThe element identifies the type of contact. The classCode attribute shall be present, and contains a value from the eHDSIRoleClass value set when used for the patient contacts; ‘PRS’ when used for “Preferred HP / Legal Organization”.eHDSdotstion
    @classCode
    		cs1 … 1RR1.8.6
     CONF
    The value of @classCode shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.39 eHDSIRoleClass (DYNAMIC)
    or
    @classCode shall be "PRS"
    hl7:code
    		CV.EPSOS0 … 1RThe relationship between the patient and the guardian or other contact should be recorded in the element. The code attribute is required and comes from the HL7 PersonalRelationshipRoleType vocabulary with codeSystem (2.16.840.1.113883.5.111). The codeSystem attribute is required. The relationship between the patient and his preferred HP comes from the the full RoleCode (2.16.840.1.113883.5.111) codeSystem R1.8.6
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.38 eHDSIPersonalRelationship (DYNAMIC)
    hl7:addr
    		AD.EPSOS1 … 1RPatient Contact's / Preferred HP's AddressR1.8.3 / R1.9.2
    @nullFlavor
    		cs0 … 1FNI
     Schematron assertrolered error 
     test@nullFlavor or hl7:* 
     MessageIf addr is not nullflavored at least one sub element has to be provided 
    hl7:streetAddressLine
    		0 … *RPatient Contact's Street/Number of Street / Preferred HP's Street/Number of StreetR1.8.3.1 / R1.8.3.2 / R1.9.2.1 / R1.9.2.2
    hl7:city
    		0 … 1RPatient Contact's City / Preferred HP's CityR1.8.2.3 / R1.9.2.3
    hl7:postalCode
    		0 … 1RPatient Contact's Postal Code / Preferred HP's Postal CodeR1.8.2.4 / R1.9.2.4
    hl7:state
    		0 … 1RPatient Contact's State or Province / Preferred HP's State or ProvinceR1.8.2.5 / R1.9.2.5
    hl7:country
    		0 … 1RPatient Contact's Country / Preferred HP's Country. When used addr.country it is always bound to the epSOSCountry value setR1.8.2.6 / R1.9.2.6
    hl7:telecom
    		TEL1 … *RPatient Contact's / Preferred HP's/Legal Organization telephone or e-mail element is required. If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be presentR1.8.4.1 / R1.8.4.2 / R1.9.3.1 / R1.9.3.2
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
     Example<telecom use="WP" value="tel:+45 20 7025 6161"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
    Choice1 … 1Elements to choose from:
    • hl7:associatedPerson
    • hl7:scopingOrganization
    hl7:associatedPerson
    		ReHDSdotstion
    hl7:name
    		PN1 … 1RPatient Contact's Name / Preferred HP's NameIHE PCC / R1.9.1
     Example<name>
      <given>John</given>  <family>Español Smith</family></name>
    Choice2 … *Elements to choose from:
    • hl7:family
    • hl7:given
    hl7:family
    		1 … *RPatient Contact's Family Name/Surname / Preferred HP's Family Name/SurnameR1.8.1 / R1.9.1.1
    hl7:given
    		1 … *RPatient Contact's Given Name / Preferred HP's Given NameR1.8.2 / R1.9.1.2
    hl7:scopingOrganization
    		ReHDSdotstion
    hl7:name
    		ON1 … 1ROrganization's NameR1.9.1
    Included1 … 1R from 2.16.840.1.113883.3.1937.777.11.10.106 eHDSI DocumentationOf PCPR (DYNAMIC)
    hl7:documentationOf
    		1 … 1ReHDSdotsPCPR
    @typeCode
    		cs1 … 1FDOC
    hl7:serviceEvent
    		1 … 1ReHDSdotsPCPR
    @classCode
    		cs1 … 1FPCPR
    @moodCode
    		cs1 … 1FEVN
    hl7:id
    		II.EPSOS0 … *ReHDSdotsPCPR
    hl7:code
    		CE.EPSOS0 … 1ReHDSdotsPCPR
    Choice1 … 1Elements to choose from:
    • hl7:effectiveTime[hl7:high]
    • hl7:effectiveTime[@nullFlavor or @value]
    hl7:effectiveTime
    		IVL_TS0 … 1CeHDSdotsPCPR
    where [hl7:high]
    hl7:low
    		TS0 … 1ReHDSdotsPCPR
    hl7:high
    		TS1 … 1ReHDSdotsPCPR
    hl7:effectiveTime
    		TS0 … 1CeHDSdotsPCPR
    where [@nullFlavor or @value]
    hl7:performer
    		0 … *Rrepresents the healthcare providers involved in the current or pertinent historical care of the patient. Preferably, the patient’s key healthcare providers would be listed, particularly their primary physician and any active consulting physicians, therapists, and counselorseHDSdotsPCPR
    @typeCode
    		cs1 … 1R
     CONF
    The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19601 x_ServiceEventPerformer (DYNAMIC)
    hl7:functionCode
    		CE.EPSOS1 … 1ReHDSdotsPCPR
     CONF
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.1 eHDSIHealthcareProfessionalRole (DYNAMIC)
    hl7:time
    		IVL_TS0 … 1ReHDSdotsPCPR
    hl7:assignedEntity
    		1 … 1MeHDSdotsPCPR
    hl7:id
    		II.EPSOS1 … *RHP ID numbereHDSdotsPCPR
    hl7:code
    		CE.EPSOS0 … 1RHP SpecialtyeHDSdotsPCPR
    hl7:addr
    		AD.EPSOS1 … *RIHE PCC
    hl7:telecom
    		TEL1 … *R

    Performer's Telecom

    If there is no information, the nullFlavor attribute shall have a value of 'NI' and the "value" and "use" attributes shall be omitted, otherwise the nullFlavor attribute shall not be present, and the "value" and "use" attributes shall be present.

    Optionalities and Cardinalities of the following two items shall be interpreted according to this rule: e.g. is not expected to have two nullFlavored telecom elements.

    		R1.10.8
    @use
    		set_cs0 … 1 
     CONF
    The value of @use shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.40 eHDSITelecomAddress (DYNAMIC)
    @nullFlavor
    		cs0 … 1FNI
     Example<telecom use="WP" value="tel:+45 20 7025 6161"/><telecom use="HP" value="mailto:jsmith@myprovider.co.uk"/>
    hl7:assignedPerson
    		0 … 1Contains 2.16.840.1.113883.3.1937.777.11.10.113 eHDSI Person (DYNAMIC)eHDSdotsPCPR
    hl7:representedOrganization
    		0 … 1Contains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC)eHDSdotsPCPR
    Included1 … 1M from 2.16.840.1.113883.3.1937.777.11.10.107 eHDSI RelatedDocument (DYNAMIC)
    hl7:relatedDocument
    		1 … 1MeHDSdotsment
    @typeCode
    		cs1 … 1FXFRM
    hl7:parentDocument
    		1 … 1ReHDSdotsment
    @classCode
    		cs0 … 1FDOCCLIN
    @moodCode
    		cs0 … 1FEVN
    hl7:id
    		II.EPSOS1 … *RIdentifier of the national version of the document.
    		eHDSdotsment
    hl7:code
    		CD.EPSOS0 … 1ReHDSdotsment
    @codeSystem
    		CONF0 … 1F2.16.840.1.113883.6.1
    hl7:text
    		ED0 … 1ReHDSdotsment
    hl7:setId
    		II.EPSOS0 … 1ReHDSdotsment
    hl7:versionNumber
    		INT0 … 1ReHDSdotsment
    hl7:component
    		1 … 1MeHDSdotsalPS
    hl7:nonXMLBody
    		1 … 1MeHDSdotsalPS
    @classCode
    		cs1 … 1FDOCBODY
    @moodCode
    		cs1 … 1FEVN
    hl7:text
    		1 … 1MThis element is used in this template to embed the PDF representation of the original document produced in the Country of Affiliation (Country A). The reference element shall never be used for this template.eHDSdotsalPS
    @mediaType
    		cs1 … 1Fapplication/pdf
    @representation
    		cs1 … 1FB64
     ConstraintThe encoding rules of the pdf, including the allowed pdf formats, SHALL be the same defined by the IHE XDS-SD profile
    hl7:reference
    		NPeHDSdotsalPS