2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000

Id	2.16.840.1.113883.10.22.2.2	Effective Date	valid from 2017‑04‑11
Status	Draft	Version Label
Name	IPSCDAauthor	Display Name	IPS CDA 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 in some cases the only one ); an application that transforms a Patient Summary record into a this CDA format may not be an author instead; Devices that for cross-border exchange purposes modify the concepts conveyed (e.g. applying code system mappings), should appear as one of the authors. In this case (document generated through a transformation process) the authors of the parent (original) patient summary should appear as authors as well. Further to this, authorship can give information about the nature of Patient Summary : if there is a person author only, then the Patient Summary is the result of a practitioner clinical act; if there are device authors only, the summary was automatically generated according to well defined rules defined by the responsible organization. The CDA standard allows to provided detailed information about what was authored by whom in the Patient Summary, allowing the specification of authorship at the whole document level, at the section level and also at the entry level. In any case it is not required to repeat this information for each of the mentioned levels, taking advantage of the context conduction propriety. In fact “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).
Classification	CDA Header Level Template
Open/Closed	Open (other than defined elements are allowed)
Used by / Uses	Used by 0 transactions and 1 template, Uses 2 templates Used by as Name Version 2.16.840.1.113883.10.22.1.1 Include International Patient Summary 2017‑04‑11 Uses as Name Version 2.16.840.1.113883.10.22.9.2 Containment IPS CDA Device DYNAMIC 2.16.840.1.113883.10.22.9.1 Containment IPS CDA Organization DYNAMIC
Relationship	Adaptation: template 2.16.840.1.113883.10.12.102 (2005‑09‑07)
Example	Human Author <author>   <functionCode code="221" codeSystem="2.16.840.1.113883.2.9.6.2.7" codeSystemName="ISCO" displayName="Medical doctors">     <translation displayName="Medico"/>  </functionCode>  <time value="201212290600+0100"/>  <assignedAuthor>     <id root="2.16.840.1.113883.2.9.4.3.2" extension="RSSMRA00A01F205F" assigningAuthorityName="Ministero Economia e Finanze"/>    <addr use="WP">       <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>    <representedOrganization>       <!-- template 'IPS CDA Organization' (dynamic) -->     </representedOrganization>  </assignedAuthor></author>
Example	Device Author <author>   <time value="201212290600+0100"/>  <assignedAuthor>     <id root="1.2.3.999" extension="__example only__"/>    <addr use="WP">       <state>Castilla-La Mancha</state>      <city>Toledo</city>      <precinct>Toledo</precinct>      <country>ES</country>      <postalCode>45071</postalCode>      <streetAddressLine>Av. Río Guadiana, 4</streetAddressLine>    </addr>    <telecom nullFlavor="NI"/>    <assignedAuthoringDevice classCode="DEV" determinerCode="INSTANCE">       <softwareName displayName="Turriano"/>    </assignedAuthoringDevice>    <representedOrganization classCode="ORG" determinerCode="INSTANCE">       <id root="1.2.3.999" extension="__example only__"/>      <name>SESCAM</name>      <telecom use="WP" value="tel:+34925274100"/>      <addr use="WP">         <state>Castilla-La Mancha</state>        <city>Toledo</city>        <precinct>Toledo</precinct>        <country>ES</country>        <postalCode>45071</postalCode>        <streetAddressLine>Av. Río Guadiana, 4</streetAddressLine>      </addr>    </representedOrganization>  </assignedAuthor></author>
Example	Example <author typeCode="AUT" contextControlCode="OP">   <time value="201212290600+0100"/>  <assignedAuthor classCode="ASSIGNED">     <id root="1.2.3.999" extension="__example only__"/>    <code code="..." codeSystem="1.2.3.999"/>    <addr nullFlavor="NI"/>    <telecom nullFlavor="NI"/>    <!-- choice: 0..1 element hl7:assigned​Person element hl7:assigned​Authoring​Device -->     <representedOrganization>       <!-- template 'IPS CDA Organization' (dynamic) -->     </representedOrganization>  </assignedAuthor></author>
Item DT Card Conf Description Label hl7:author 1 … * R (IPS…hor) @typeCode cs 0 … 1 F AUT @context​Control​Code cs 0 … 1 F OP   Example <author>   <time value="201212290600+0100"/>  <assignedAuthor>     <id root="2.16.840.1.113883.2.9.4.3.2" extension="RSSMRA00A01F205F" assigningAuthorityName="Ministero Economia e Finanze"/>    <addr use="WP">       <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>  <representedOrganization>     <!-- template 'IPS CDA Organization' (dynamic) -->   </representedOrganization></author> hl7:functionCode CE.IPS 0 … 1 R (IPS…hor)   Example <functionCode code="221" codeSystem="2.16.840.1.113883.2.9.6.2.7" codeSystemName="ISCO" displayName="Medical doctors"/> hl7:time TS.IPS.TZ 1 … 1 R The author/time element represents the start time of the author’s participation in the creation of the clinical document.  (IPS…hor)   Example <time value="201212290600+0100"/> hl7:assignedAuthor 1 … 1 R (IPS…hor) @classCode cs 0 … 1 F ASSIGNED hl7:id II 1 … * R Author Identifier(s) (IPS…hor) @nullFlavor cs 0 … 1     Constraint If assignedAuthor has an associated representedOrganization with no assignedPerson or assignedAuthoringDevice, then the value for "ClinicalDocument/author/assignedAuthor/id/@nullFlavor" SHALL be "NA" "Not applicable"  hl7:code CE.IPS 0 … 1 R (IPS…hor) hl7:addr AD.IPS 1 … * R (IPS…hor)   Example <addr use="WP">   <streetAddressLine>Viale della Cristallina 3</streetAddressLine>  <city>Bologna</city>  <state>BO</state>  <postalCode>40121</postalCode>  <country>IT</country></addr> hl7:telecom TEL.IPS 1 … * R Attribute @value SHALL contain a URI if element telecom is used. The URI scheme SHALL be one of URLScheme (IPS…hor) @use set_cs 0 … 1     CONF The value of @use shall be drawn from value set 2.16.840.1.113883.1.11.201 TelecommunicationAddressUse (DYNAMIC) @value st 0 … 1     Example <telecom use="WP" value="tel:+39-051-34343434"/>   Example <telecom nullFlavor="NI"/> Choice 0 … 1 Elements to choose from: hl7:assigned​Person hl7:assigned​Authoring​Device containing template 2.16.840.1.113883.10.22.9.2 IPS CDA Device (DYNAMIC) hl7:assigned​Person 0 … 1 C (IPS…hor) @classCode cs 0 … 1 F PSN @determiner​Code cs 0 … 1 F INSTANCE hl7:name PN 1 … 1 R Name of the person (e.g. the Healthcare Professional)  authoring this document (IPS…hor)   Example <name>   <given>John</given>  <family>Español Smith</family></name> hl7:family 1 … * R (IPS…hor) hl7:given 1 … * R (IPS…hor) hl7:assigned​Authoring​Device 0 … 1 C Contains 2.16.840.1.113883.10.22.9.2 IPS CDA Device (DYNAMIC) (IPS…hor)   Example <assignedAuthoringDevice classCode="DEV" determinerCode="INSTANCE">   <softwareName displayName="Turriano"/></assignedAuthoringDevice> hl7:represented​Organization 0 … 1 R Contains 2.16.840.1.113883.10.22.9.1 IPS CDA Organization (DYNAMIC) (IPS…hor)