Back To Index << Back To Templates

# Template epSOS CDA documentationOf

Id | 2.16.840.1.113883.3.1937.777.11.10.105 | Effective Date | 2013‑12‑20 Other versions this id: eHDSIDocumentationOf as of 2020‑10‑06 09:42:36 eHDSIDocumentationOf as of 2020‑04‑16 10:55:29
Status | Retired | Version Label |
Name | epSOSCDAdocumentationOf | Display Name | epSOS CDA documentationOf
Description
/ClinicalDocument/author/assignedAuthor /ClinicalDocument/documentationOf/serviceEvent/performer (this applies to the prescriber and the dispenser). The template ID referenced here refers to HP information in the /ClinicalDocument/documentationOf/serviceEvent/performer structure. In this document, the same requriements apply to the person author of the document (if there is one), and to the prescrober and dispenser (see body). When there is no HP but we have the method of assembly of data by a device, such as the “spider” method, we have the following expression; ClinicalDocument/author/assignedAuthor/assignedAuthoringDevice. When the data is collected from different sources & pre-existing documents that are part of a bigger system. In that case the organization responsible of that collection “signed” the PS as responsible. ClinicalDocument/author/assignedAuthor/representedOrganization
Classification | CDA Header Level Template
Open/Closed | Open (other than defined elements are allowed)
Associated with |
Associated with 1 concept
Id | Name | Dataset
--- | --- | ---
epsos-dataelement-66 | Date of Last Update | epSOS Data Set
Used by / Uses |
Used by 0 transactions and 0 templates, Uses 1 template
Uses | as | Name | Version
--- | --- | --- | ---
2.16.840.1.113883.3.1937.777.11.10.111 | Containment | eHDSI Organization | DYNAMIC
Relationship | Specialization: template 2.16.840.1.113883.10.12.110 CDA documentationOf (2005‑09‑07) ref ad1bbr-
Item | DT | Card | Conf | Description | Label
--- | --- | --- | --- | --- | ---
hl7:documentationOf |  | 0 … * | R |  |
@typeCode |  | 1 … 1 | F | DOC
hl7:serviceEvent |  | 1 … 1 | R |  |
@classCode |  | 1 … 1 | F | ACT
@moodCode |  | 1 … 1 | F | EVN
hl7:id | II.EPSOS | 0 … * | R |  |
hl7:code | CE.EPSOS | 0 … 1 | R |  |
hl7:effectiveTime | IVL_TS | 0 … 1 | R |  |
hl7:low | TS |  | R |  |
hl7:high | TS |  | R | 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 occured within the time period specified in serviceEvent/effectiveTime. Therefore this elements represents also the last effetive 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 "epSOS-Patient Summary" in the element description at ClinicalDocument.effectiveTime "Relevant times for the Patient Summary" for further details | R1.11.2
epsos-dataelement-66 | Date of Last Update | epSOS Data Set
hl7:performer |  | 0 … * | R |  | R1.10
@typeCode | cs | 1 … 1 | R |
| 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.EPSOS | 0 … 1 | R |  | R1.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_TS | 0 … 1 | R |  | R1.10
hl7:assignedEntity |  | 1 … 1 | R |  | R1.10
hl7:id | II.EPSOS | 1 … * | R | HP ID number | R1.10.5
hl7:code | CE.EPSOS | 0 … 1 | R | HP Specialty | R1.10.7
hl7:addr | AD.EPSOS | 1 … * | R |  | IHE PCC
hl7:telecom | TEL | 1 … * | 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_cs | 0 … 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 | cs | 0 … 1 | F | NI
hl7:assignedPerson |  | 0 … 1 | R |  | R1.10
@classCode |  | 0 … 1 | F | PSN
@determinerCode |  | 0 … 1 | F | INSTANCE
hl7:name | PN | 1 … 1 | R | HP Name | IHE PCC
| Example | <name> <given>John</given> <family>Español Smith</family></name>
Choice | 2 … * |  | Elements to choose from: hl7:family hl7:given hl7:prefix hl7:suffix
hl7:family |  | 1 … * | R | HP Family Name/Surname | R1.10.1
hl7:given |  | 1 … * | R | HP Given Name | R1.10.2
hl7:prefix |  | 0 … * | R | HP Prefix | R1.10.3
hl7:suffix |  | 0 … * | R | HP Suffix | R1.10.4
hl7:representedOrganization |  | 1 … 1 | R | Contains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC) | R1.10.9