Template

Show index

Template CZ CDA author 2019‑12‑09 18:27:01

Id1.2.203.24341.11.10.2.2Effective Date2019‑12‑09 18:27:01
Statusdraft DraftVersion Label
NameCZCDAauthorDisplay NameCZ 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 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).

ClassificationCDA Header Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 1 transaction and 1 template, Uses 2 templates
Used by as NameVersion
2.16.840.1.113883.3.1937.777.49.4.2Transactiondraft PS created2022‑05‑19 08:45:25
1.2.203.24341.11.10.1.1Includedraft CZ-EU Patient Summary2019‑11‑28 20:23:19
Uses as NameVersion
1.2.203.24341.11.10.4.1Containmentdraft CZ DeviceDYNAMIC
1.2.203.24341.11.10.9.3Containmentdraft CZ CDA OrganizationDYNAMIC
RelationshipAdaptation: template 2.16.840.1.113883.3.1937.777.11.10.102 epSOS CDA author (2019‑03‑21 13:24:01)
ref
epsos-

Version: template 2.16.840.1.113883.3.1937.777.11.10.102 epSOS CDA author (2013‑12‑20)
ref
epsos-

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="1.2.203.24341.1.20.4" extension="123456789" assigningAuthorityName="Ministerstvo zdravotnictví"/>    <id root="1.2.203.24341.1.20.5" extension="1130612161" assigningAuthorityName="Česká lékařská komora"/>    <addr>
      <streetAddressLine>Palackého nám. 4</streetAddressLine>      <city>Praha</city>      <postalCode>12801</postalCode>      <country>CZ</country>    </addr>
    <telecom use="WP" value="tel:(+429)666555444"/>    <assignedPerson>
      <name>
        <prefix qualifier="AC">MUDr.</prefix>        <given>Jan</given>        <family>Uzdravitel</family>        <suffix qualifier="AC">PhD.</suffix>      </name>
    </assignedPerson>
  </assignedAuthor>
</author>
ItemDTCardConfDescriptionLabel
hl7:author
1 … *RCZCDdotsthor
@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.CZCDdotsthor
hl7:assignedAuthor
1 … 1RCZCDdotsthor
@classCode
cs0 … 1FASSIGNED
 Schematron assertrolered error 
 test@nullFlavor or hl7:assignedPerson or hl7:assignedAuthoringDevice 
 MessageAt least an assignedPerson or an assignedAuthoringDevice has to be provided, otherwise a nullFlavor shall be present. 
hl7:id
II.EPSOS1 … *RIdentification of the Healthcare Practitioner that is the author of this document.R1.10.5
@nullFlavor
cs0 … 1FNA
hl7:code
CE.EPSOS0 … 1RHP SpecialtyR1.10.7
hl7:addr
AD.EPSOS1 … *RIHE PCC
@use
set_cs0 … 1 
 CONF
The value of @use shall be drawn from value set 1.2.203.24341.11.1.3 CZ-AddressUse (DYNAMIC)
 Example<addr use="WP">
  <streetAddressLine>Palackého nám. 1</streetAddressLine>  <city>Praha</city>  <postalCode>12801</postalCode>  <country>CZ</country></addr>
hl7:telecom
TEL.EPSOS1 … *RAttribute @value SHALL contain a URI if element telecom is used. The URI scheme SHALL be one of URLSchemeIHE 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)
Choice0 … 1Elements to choose from:
hl7:assignedPerson
RCZCDdotsthor
@classCode
cs0 … 1FPSN
@determinerCode
cs0 … 1FINSTANCE
hl7:name
PN1 … 1RHP NameIHE PCC
 Example<name>
  <given>Anežka</given>  <family>Hodinová Spurná</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:assignedAuthoringDevice
RContains 1.2.203.24341.11.10.4.1 CZ Device (DYNAMIC)CZCDdotsthor
hl7:representedOrganization
1 … 1RContains 1.2.203.24341.11.10.9.3 CZ CDA Organization (DYNAMIC)R1.10.9