Note for the readers This template version represents the best representation of the original epSOS/EXPAND specifications in ART DECOR. However the original epSOS/EXPAND specifications in Microsoft Word took the original IHE Templates and added constraints in written language. This actually is not best practice in electronic Template Design because the additional constraints are not assigned to the original IHE template but rather than that are text only constraints. In order to make everything computable new Template OIDs need to be assigned to the epSOS Templates in order to cover both, the original IHE Template Design and the additional constraints from epSOS in the text and represent them electronically. Caveat: for the above mentioned reasons this version cannot be used for (automatic) testing/validation purposes. It shall be used however as basis for refinement (repository)
Note: there is a new version planned that covers all above and makes proper testing/validation possible
epSOS Patient Summary 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.
Zatímco jazyk XML schématu umožňuje připojit schéma k dokumentu XML zahrnutím atributu schemaLocation nastaveného na namespace http://www.w3.org/2001/XMLSchema-instance, je toto propojení výslovně ZAKÁZÁNO v [ITS§1.4 ], a tedy i ve standardu CDA.
(cs-CZ) realmCode vyjadřuje jurisdikci k níž je daný dokument, resp. specifikace CDA dokumentu, vázána. V české specifikaci CDA musí být použita hodnota "CZ".
The ClinicalDocument/id element is an instance identifier data type. The root attribute is an OID. If there is a value in @extension, then the root uniquely identifies the scope of the extension. If there is no value in @extension then @root SHALL uniquely identify the document
UUIDs SHALL be represented in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where each X is a character from the set [A-F0-9].
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])(.([1-9][0-9]*|0))+.
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).
This attribute “represents an identifier that is common across all document revisions”.
In the case of the NCP transcoding /translation this is the ID that remains unchanged among all the existing transformations.
Implementers are recommended to use this attribute.
CZCDetId
hl7:versionNumber
0 … 1
R
(cs-CZ) Atributy id, setId a versionNumber identifikují klinický dokument. Atribut id reprezentuje identitu konkrétního CDA dokumentu. Dva dokumenty se stejným id musí tedy mít totožný obsah (mohou se ale např. lišit použitou kódovou sadou). Atribut versionNumber může být použit pro rozlišení verze dokumentu v případech, kdy dochází k jeho změnám. V takovém případě by se využil také atribut setId, který by měl mít u obou dokumentů (původní i nové verze) stejnou hodnotu. Relace na původní dokument by pak byla zaznamenána v elementu relatedDocument.
The 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
cs
0 … 1
F
NI
hl7:streetAddressLine
0 … *
R
Patient's Number of Street/Patient's Number of Street
R1.5.1 / R1.5.2
hl7:city
0 … 1
R
Patient's City
R1.5.3
hl7:postalCode
0 … 1
R
Patient's Postal Code
R1.5.4
hl7:state
0 … 1
R
Patient's State or Province
R1.5.5
hl7:country
0 … 1
R
Patient's Country. When used addr.country it is always bound to the epSOSCountry value set
Patient’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.
The 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
cs
0 … 1
F
NI
hl7:streetAddressLine
0 … *
R
Guardian's Number of Street
R1.7.3.2
hl7:city
0 … 1
R
Guardian's City
R1.7.3.3
hl7:postalCode
0 … 1
R
Guardian's Postal Code
R1.7.3.4
hl7:state
0 … 1
R
Guardian's State or Province
R1.7.3.5
hl7:country
0 … 1
R
Guardian's Country. When used addr.country it is always bound to the epSOSCountry value set
Guardian’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.
This 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".
The 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.
CZCDthor
hl7:assignedAuthor
1 … 1
R
CZCDthor
@classCode
cs
0 … 1
F
ASSIGNED
Schematron assert
role
error
test
@nullFlavor or hl7:assignedPerson or hl7:assignedAuthoringDevice
Message
At least an assignedPerson or an assignedAuthoringDevice has to be provided, otherwise a nullFlavor shall be present.
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.
The 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.
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.
The 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”.
The 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
Patient 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 present
It represents 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 counselors
CZDoPCPR
@typeCode
cs
1 … 1
R
CONF
The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.19601x_ServiceEventPerformer (DYNAMIC)
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.