Id1.3.6.1.4.1.12559.11.10.1.3.1.1.9Effective Date2020‑11‑30 15:46:00
Statusretired RetiredVersion Label
NameeHDSIOrCDHospitalDischargeReportDisplay NameeHDSI OrCD Hospital Discharge Report
Description

eHDSI OrCD Hospital Discharge Report 

One of the authorized Original Clinical Documents. The Original Clinical Document is attached in unstructed format in the body. The coded header contains metadata related to the document.

ContextPathname /
ClassificationCDA Document Level Template
Open/ClosedOpen (other than defined elements are allowed)
Associated with
Associated with 51 concepts
IdNameData Set
ehdsi-dataelement-342draft Street draft eHDSI Data Set
ehdsi-dataelement-250draft Regional/National Health Identifier draft eHDSI Data Set
ehdsi-dataelement-155draft City draft eHDSI Data Set
ehdsi-dataelement-157draft Street draft eHDSI Data Set
ehdsi-dataelement-153draft State or Province draft eHDSI Data Set
ehdsi-dataelement-156draft Number of Street draft eHDSI Data Set
ehdsi-dataelement-154draft Postal Code draft eHDSI Data Set
ehdsi-dataelement-161draft Date of Birth draft eHDSI Data Set
ehdsi-dataelement-356draft Regional/National Health ID (Country of Affiliation) draft eHDSI Data Set
ehdsi-dataelement-170draft National Healthcare Patient identifier (Country of Affiliation) draft eHDSI Data Set
ehdsi-dataelement-164draft Given Name draft eHDSI Data Set
ehdsi-dataelement-313draft Social/Insurance Number draft eHDSI Data Set
ehdsi-dataelement-244draft Gender draft eHDSI Data Set
ehdsi-dataelement-159draft Gender Code draft eHDSI Data Set
ehdsi-dataelement-246draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-338draft State or Province draft eHDSI Data Set
ehdsi-dataelement-309draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-150draft Telephone No draft eHDSI Data Set
ehdsi-dataelement-340draft City draft eHDSI Data Set
ehdsi-dataelement-152draft Country draft eHDSI Data Set
ehdsi-dataelement-239draft Social/Insurance Number draft eHDSI Data Set
ehdsi-dataelement-307draft Gender draft eHDSI Data Set
ehdsi-dataelement-353draft Insurance Number draft eHDSI Data Set
ehdsi-dataelement-148draft E-mail draft eHDSI Data Set
ehdsi-dataelement-163draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-346draft Date of Birth draft eHDSI Data Set
ehdsi-dataelement-247draft Given Name draft eHDSI Data Set
ehdsi-dataelement-310draft Given Name draft eHDSI Data Set
ehdsi-dataelement-344draft Gender Code draft eHDSI Data Set
ehdsi-dataelement-242draft Date of Birth draft eHDSI Data Set
ehdsi-dataelement-341draft Number of Street draft eHDSI Data Set
ehdsi-dataelement-350draft Given Name draft eHDSI Data Set
ehdsi-dataelement-337draft Country draft eHDSI Data Set
ehdsi-dataelement-339draft Postal Code draft eHDSI Data Set
ehdsi-dataelement-316draft Regional/National Health Identifier draft eHDSI Data Set
ehdsi-dataelement-167draft Insurance Number draft eHDSI Data Set
ehdsi-dataelement-349draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-123draft Nature of the Patient Summary draft eHDSI Data Set
ehdsi-dataelement-125draft Author and Organisation draft eHDSI Data Set
ehdsi-dataelement-303draft HP Identifier draft eHDSI Data Set
ehdsi-dataelement-300draft Given Name draft eHDSI Data Set
ehdsi-dataelement-299draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-127draft Legal Authenticator draft eHDSI Data Set
ehdsi-dataelement-176draft Responsible of the ePrescription Data/Author Organization draft eHDSI Data Set
ehdsi-dataelement-327draft Responsible of the Original Clinical Document/Author Organization draft eHDSI Data Set
ehdsi-dataelement-129draft Documentation Of draft eHDSI Data Set
ehdsi-dataelement-120draft Date of Last Update draft eHDSI Data Set
ehdsi-dataelement-324draft Documentation Of draft eHDSI Data Set
ehdsi-dataelement-131draft Related Document draft eHDSI Data Set
ehdsi-dataelement-174draft Related Document draft eHDSI Data Set
ehdsi-dataelement-321draft Related Document draft eHDSI Data Set
Used by / Uses
Used by 0 transactions and 0 templates, Uses 8 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.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.105Includeactive eHDSI DocumentationOfDYNAMIC
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 headereHDSdotsport
 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 … 1ReHDSdotsport
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.

eHDSdotsport
@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 OrCD Hospital Discharge Report
eHDSdotsport
@root
uid1 … 1F1.3.6.1.4.1.12559.11.10.1.3.1.1.9
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
CE.EPSOS1 … 1MClinicalDocument/code SHALL be present.R1.11.6
@displayName
1 … 1R
 CONF
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.53 eHDSIHospitalDischargeReportType (DYNAMIC)
 Example<code code="34105-7" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Hospital Discharge summary"/>
hl7:title
ST1 … 1MClinicalDocument/title is used for display purposes.R1.11.7
 Example<title>eHDSI OrCD Hospital Discharge Report Maria Bakker November 30, 2020</title>
hl7:effectiveTime
TS.EPSOS.TZ1 … 1M

The creation time of the original Hospital Discharge report.

iI the embedded document is a print of an existing electronic report, it is the creation time of the report the pdf is generated from.

R1.11.1
 Example<effectiveTime value="20201130165000+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 … 1ReHDSdotsport
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
 
target
ehdsi-dataelement-250draft Regional/National Health Identifier draft eHDSI Data Set
ehdsi-dataelement-356draft Regional/National Health ID (Country of Affiliation) draft eHDSI Data Set
ehdsi-dataelement-170draft National Healthcare Patient identifier (Country of Affiliation) draft eHDSI Data Set
ehdsi-dataelement-313draft Social/Insurance Number draft eHDSI Data Set
ehdsi-dataelement-239draft Social/Insurance Number draft eHDSI Data Set
ehdsi-dataelement-353draft Insurance Number draft eHDSI Data Set
ehdsi-dataelement-316draft Regional/National Health Identifier draft eHDSI Data Set
ehdsi-dataelement-167draft Insurance Number draft eHDSI Data Set
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
 
target
ehdsi-dataelement-342draft Street draft eHDSI Data Set
ehdsi-dataelement-157draft Street draft eHDSI Data Set
ehdsi-dataelement-156draft Number of Street draft eHDSI Data Set
ehdsi-dataelement-341draft Number of Street draft eHDSI Data Set
hl7:city
0 … 1RPatient's CityR1.5.3
 
target
ehdsi-dataelement-155draft City draft eHDSI Data Set
ehdsi-dataelement-340draft City draft eHDSI Data Set
hl7:postalCode
0 … 1RPatient's Postal CodeR1.5.4
 
target
ehdsi-dataelement-154draft Postal Code draft eHDSI Data Set
ehdsi-dataelement-339draft Postal Code draft eHDSI Data Set
hl7:state
0 … 1RPatient's State or ProvinceR1.5.5
 
target
ehdsi-dataelement-153draft State or Province draft eHDSI Data Set
ehdsi-dataelement-338draft State or Province draft eHDSI Data Set
hl7:country
0 … 1RPatient's Country. When used addr.country it is always bound to the eHDSICountry value setR1.5.6
 
target
ehdsi-dataelement-152draft Country draft eHDSI Data Set
ehdsi-dataelement-337draft Country draft eHDSI Data Set
 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
 
target
ehdsi-dataelement-150draft Telephone No draft eHDSI Data Set
ehdsi-dataelement-148draft E-mail draft eHDSI Data Set
@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
 
target
ehdsi-dataelement-246draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-309draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-163draft Family Name/Surname draft eHDSI Data Set
ehdsi-dataelement-349draft Family Name/Surname draft eHDSI Data Set
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
 
target
ehdsi-dataelement-164draft Given Name draft eHDSI Data Set
ehdsi-dataelement-247draft Given Name draft eHDSI Data Set
ehdsi-dataelement-310draft Given Name draft eHDSI Data Set
ehdsi-dataelement-350draft Given Name draft eHDSI Data Set
hl7:administrativeGenderCode
CE.EPSOS1 … 1RPatient's GenderR1.2
 
target
ehdsi-dataelement-244draft Gender draft eHDSI Data Set
ehdsi-dataelement-159draft Gender Code draft eHDSI Data Set
ehdsi-dataelement-307draft Gender draft eHDSI Data Set
ehdsi-dataelement-344draft Gender Code draft eHDSI Data Set
@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
 
target
ehdsi-dataelement-161draft Date of Birth draft eHDSI Data Set
ehdsi-dataelement-346draft Date of Birth draft eHDSI Data Set
ehdsi-dataelement-242draft Date of Birth draft eHDSI Data Set
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 presentR1.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 … *R from 2.16.840.1.113883.3.1937.777.11.10.102 eHDSI Author (DYNAMIC)
hl7:author
1 … *ReHDSdotsthor
 
target
ehdsi-dataelement-125draft Author and Organisation draft eHDSI Data Set
@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
 
target
ehdsi-dataelement-123draft Nature of the Patient Summary draft eHDSI Data Set
@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
 
target
ehdsi-dataelement-303draft HP Identifier draft eHDSI Data Set
@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
 
target
ehdsi-dataelement-299draft Family Name/Surname draft eHDSI Data Set
hl7:given
1 … *MHP Given NameR1.10.2
 
target
ehdsi-dataelement-300draft Given Name draft eHDSI Data Set
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

Included0 … 1 from 2.16.840.1.113883.3.1937.777.11.10.109 eHDSI LegalAuthenticator (DYNAMIC)
hl7:legalAuthenticator
0 … 1RThe 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
 
target
ehdsi-dataelement-127draft Legal Authenticator draft eHDSI Data Set
ehdsi-dataelement-176draft Responsible of the ePrescription Data/Author Organization draft eHDSI Data Set
ehdsi-dataelement-327draft Responsible of the Original Clinical Document/Author Organization draft eHDSI Data Set
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 … 1 from 2.16.840.1.113883.3.1937.777.11.10.105 eHDSI DocumentationOf (DYNAMIC)
hl7:documentationOf
0 … 1ReHDSdotsonOf
 
target
ehdsi-dataelement-129draft Documentation Of draft eHDSI Data Set
ehdsi-dataelement-324draft Documentation Of draft eHDSI Data Set
@typeCode
cs1 … 1FDOC
hl7:serviceEvent
1 … 1ReHDSdotsonOf
@classCode
cs1 … 1FACT
@moodCode
cs1 … 1FEVN
hl7:id
II.EPSOS0 … *ReHDSdotsonOf
hl7:code
CE.EPSOS0 … 1ReHDSdotsonOf
hl7:effectiveTime
IVL_TS0 … 1ReHDSdotsonOf
hl7:low
TSReHDSdotsonOf
hl7:high
TSR

Please note that with this element we don't specify any document authoring time, but when the episode of care documented by this CDA ended.

For a summary document, there is only one service event, describing the provision of care over a period of time. All information represented in the document must have occurred within the time period specified in serviceEvent/effectiveTime. Therefore this elements represents also the last effective date when the summary content has been updated (even if it may happen that this instance of the CDA has been authored later..).

As for the eP and eD the last update of the document is better represented by authoring time.

Please refers to the template "eHDSI Patient Summary" in the element description at ClinicalDocument.effectiveTime "Relevant times for the Patient Summary" for further details

R1.11.2
 
target
ehdsi-dataelement-120draft Date of Last Update draft eHDSI Data Set
hl7:performer
0 … *RR1.10
@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.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
IVL_TS0 … 1RR1.10
hl7:assignedEntity
1 … 1RR1.10
hl7:id
II.EPSOS1 … *RHP ID numberR1.10.5
hl7:code
CE.EPSOS0 … 1RHP SpecialtyR1.10.7
hl7:addr
AD.EPSOS1 … *RIHE PCC
hl7:telecom
TEL1 … *R

Assigned Entity'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 / 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)
@nullFlavor
cs0 … 1FNI
hl7:assignedPerson
0 … 1RR1.10
@classCode
cs0 … 1FPSN
@determinerCode
cs0 … 1FINSTANCE
hl7:name
PN1 … 1RHP NameIHE PCC
 Example<name>
  <given>John</given>  <family>Español Smith</family></name>
Choice2 … *Elements to choose from:
  • hl7:family
  • hl7:given
  • hl7:prefix
  • hl7:suffix
hl7:family
1 … *RHP Family Name/SurnameR1.10.1
hl7:given
1 … *RHP Given NameR1.10.2
hl7:prefix
0 … *RHP PrefixR1.10.3
hl7:suffix
0 … *RHP SuffixR1.10.4
hl7:representedOrganization
1 … 1RContains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC)R1.10.9
Included0 … 1 from 2.16.840.1.113883.3.1937.777.11.10.107 eHDSI RelatedDocument (DYNAMIC)
hl7:relatedDocument
0 … 1ReHDSdotsment
 
target
ehdsi-dataelement-131draft Related Document draft eHDSI Data Set
ehdsi-dataelement-174draft Related Document draft eHDSI Data Set
ehdsi-dataelement-321draft Related Document draft eHDSI Data Set
@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 … 1MeHDSdotsport
hl7:nonXMLBody
1 … 1MeHDSdotsport
@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.eHDSdotsport
@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
NPeHDSdotsport