Back To Index << Back To Templates

# Template eHDSI Author

Id | 2.16.840.1.113883.3.1937.777.11.10.102 | Effective Date | 2020‑04‑14 13:03:16 Other versions this id: eHDSIAuthor as of 2020‑10‑02 13:27:23 epSOSCDAauthor as of 2019‑03‑21 13:24:01 epSOSCDAauthor as of 2013‑12‑20
Status | Retired | Version Label |
Name | eHDSIAuthor | Display Name | eHDSI Author
Description
A CDA document shall have at least one author. Authors could be either human (ClinicalDocument/author/assignedAuthor/assignedPerson) either devices (ClinicalDocument/author/assignedAuthor/assignedAuthoringDevice). For definition “The `author` element represents the creator of the clinical document. If the role of the actor is the entry of information from his or her own knowledge or application of skills, that actor is the author. If one actor provides information to another actor who filters, reasons, or algorithmically creates new information, then that second actor is also an author, having created information from his or her own knowledge or skills.” [From Implementation Guide for CDA Release 2: Imaging Integration – UV Realm, March 2009]. According to this definition, not any device that generates the electronic document has to be considered as an author: a spider collecting and filtering information from different repositories, according to defined rules and policies, for the scope of creating a Patient Summary is definitely a document author (and maybe the only one for this document); an application that transforms a prescription record into a epSOS eP CDA may not be an author instead; The NCP that modifies the concepts conveyed, should appear as one of the authors. The author of the parent document is often also an author of the document generated through a transformation process (in that case also the author time should be the same). Further to this, is therefore possible to determine the Nature of Patient Summary as follows [Excluding the NCPs as authors]: if there is a person author only, there the Patient Summary is the result of a practitioner clinical act; if there is a device author only, the summary was automatically generated according to well defined rules defined by the responsible organization; if there are both a person and a device as authors, the summary was created via a mixed approach. The CDA provides a mechanism to better specify who authored what within the document, allowing the specification of authorship at the whole document level, at the section level and finally at the entry level. In any case is not required to repeat this information for each level, taking advantage of the context conduction propriety. Infact “context that is specified on an outer tag holds true for all nested tags, unless overridden on a nested tag. Context specified on a tag within the CDA body always overrides context propagated from an outer tag. For instance, the specification of authorship at a document section level overrides all authorship propagated from outer tags.” (HL7 CDA R2 Standard). /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 9 concepts
Id | Name | Dataset
--- | --- | ---
epsos-dataelement-180 | Author Role | epSOS Data Set
epsos-dataelement-19 | Author Full Name | epSOS Data Set
epsos-dataelement-20 | Given Name | epSOS Data Set
epsos-dataelement-21 | Family Name/Surname | epSOS Data Set
epsos-dataelement-22 | Author Identification | epSOS Data Set
epsos-dataelement-23 | Author Healthcare Facility | epSOS Data Set
epsos-dataelement-273 | Prefix | epSOS Data Set
epsos-dataelement-274 | Suffix | epSOS Data Set
epsos-dataelement-67 | Author | epSOS Data Set
Used by / Uses |
Used by 0 transactions and 0 templates, Uses 2 templates
Uses | as | Name | Version
--- | --- | --- | ---
2.16.840.1.113883.3.1937.777.11.10.129 | Containment | eHDSI Device | DYNAMIC
2.16.840.1.113883.3.1937.777.11.10.111 | Containment | eHDSI Organization | DYNAMIC
Relationship | Version: template 2.16.840.1.113883.3.1937.777.11.10.102 epSOS CDA author (2019‑03‑21 13:24:01) Version: template 2.16.840.1.113883.3.1937.777.11.10.102 epSOS CDA author (2013‑12‑20) Specialization: template 2.16.840.1.113883.10.12.102 CDA author (2005‑09‑07) ref ad1bbr-
Example |
Example
<author> <time value="20121229"/> <assignedAuthor> <id root="2.16.840.1.113883.2.9.4.3.2" extension="RSSMRA00A01F205F" assigningAuthorityName="Ministero Economia e Finanze"/> <addr> <streetAddressLine>Viale della Cristallina 3</streetAddressLine> <city>Bologna</city> <state>BO</state> <postalCode>40121</postalCode> <country>IT</country> </addr> <telecom use="WP" value="tel:(+39)051-34343434"/> <assignedPerson> <name> <given>Paolo</given> <family>Rossi</family> </name> </assignedPerson> </assignedAuthor></author>
Item | DT | Card | Conf | Description | Label
--- | --- | --- | --- | --- | ---
hl7:author |  | 1 … * | R |  |
epsos-dataelement-67 | Author | epSOS Data Set
@typeCode | cs | 0 … 1 | F | AUT
@contextControlCode | cs | 0 … 1 | F | OP
hl7:functionCode | CE.EPSOS | 0 … 1 | R |  | R1.10.6
epsos-dataelement-180 | Author Role | epSOS Data Set
| 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.TZ | 1 … 1 | R | 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. |
hl7:assignedAuthor |  | 1 … 1 | M |  |
@classCode | cs | 0 … 1 | F | ASSIGNED
hl7:id | II.EPSOS | 1 … * | R | Identification of the Healthcare Practitioner that is the author of this document. | R1.10.5
epsos-dataelement-22 | Author Identification | epSOS Data Set
@nullFlavor | cs | 0 … 1 | F | NA
hl7:code | CE.EPSOS | 0 … 1 | R | HP Specialty | R1.10.7
hl7:addr | AD.EPSOS | 1 … * | R |  | IHE PCC
hl7:telecom | TEL.EPSOS | 1 … * | R | 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_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)
Choice | 1 … 1 |  | Elements to choose from: hl7:assignedPerson hl7:assignedAuthoringDevice containing template 2.16.840.1.113883.3.1937.777.11.10.129 eHDSI Device (DYNAMIC)
hl7:assignedPerson |  | 0 … 1 | C |  |
@classCode | cs | 0 … 1 | F | PSN
@determinerCode | cs | 0 … 1 | F | INSTANCE
hl7:name | PN | 1 … 1 | R | HP Name | IHE PCC
epsos-dataelement-19 | Author Full Name | epSOS Data Set
| Example | <name> <given>John</given> <family>Español Smith</family></name>
hl7:family |  | 1 … * | M | HP Family Name/Surname | R1.10.1
epsos-dataelement-21 | Family Name/Surname | epSOS Data Set
hl7:given |  | 1 … * | M | HP Given Name | R1.10.2
epsos-dataelement-20 | Given Name | epSOS Data Set
hl7:prefix |  | 0 … * | R | HP Prefix | R1.10.3
epsos-dataelement-273 | Prefix | epSOS Data Set
hl7:suffix |  | 0 … * | R | HP Suffix | R1.10.4
epsos-dataelement-274 | Suffix | epSOS Data Set
hl7:assignedAuthoringDevice |  | 0 … 1 | C | Contains 2.16.840.1.113883.3.1937.777.11.10.129 eHDSI Device (DYNAMIC) |
hl7:representedOrganization |  | 1 … 1 | R | Contains 2.16.840.1.113883.3.1937.777.11.10.111 eHDSI Organization (DYNAMIC) | R1.10.9
epsos-dataelement-23 | Author Healthcare Facility | epSOS Data Set