Back To Index  <<  Back To Templates

ref Template  IPS CDA relatedDocument

Id 2.16.840.1.113883.10.22.2.7 Effective Date valid from 2017‑04‑12
Status draft Draft Version Label
Name IPSCDArelatedDocument Display Name IPS CDA relatedDocument
Description

An IPS may have three types of parent document:

  • A superseded version that the present instance of the document wholly replaces (typeCode = RPLC). 
  • A source document from which the present document is transformed (typeCode = XFRM). An IPS may be created by transformation from an already existing local Patient Summary or an IPS document. An example of this case is the creation of a derived instance in which translations are appended in order to facilitate the cross-border usage of this document; or the case in which a local patient summary is transformed to originate a new IPS instance.
  • An original version that the present document integrates (typeCode = APND). Some cross-border legal agreements (e.g.  the European Digital Service Infrastructure for eHealth) require the patient summary to be accompanied by  a printable representation of the original national data / document this IPS comes from. The relationship between the IPS and this content may be tracked using this relationship. 
Note 1: even for countries not dealing with real documents in their National Infrastructures (e.g. data collected from local databases), this mechanism could be useful to identify the collection of data used for generating the epSOS CDAs, facilitating the information backtracking. In that case the ID might be that of the epSOS friendly document or of any other kind of intermediate document used for generating the NCP document input.
Note 2: even if none of the allowable relationships defined by the CDA standard (XFRM, RPLC, APND) fits perfectly with the described case; the APND relationship seems to be the one that fits the better. In fact “An addendum is a separate document that references the parent document, and may extend or alter the observations in the prior document. The parent document remains a current component of the patient record, and the addendum and its parent are both read by report recipients.”
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 0 templates
Used by as Name Version
2.16.840.1.113883.10.22.1.1 Include draft International Patient Summary 2017‑04‑11
Relationship Adaptation: template 2.16.840.1.113883.10.12.111 (2005‑09‑07)
Example
Example of national document identified by its ID
<relatedDocument typeCode="XFRM">
  <!-- the IPS is obtained as trasformation of the "aa-bb-cc" document -->
  <parentDocument>
    <id root="aa-bb-cc"/>  </parentDocument></relatedDocument>
Example
Reference to the local PS and to supporting documentation
<!-- the example starts here -->
<relatedDocument typeCode="XFRM">
  <!-- the IPS is obtained as trasformation of the "aa-bb-cc" Local Patient Summary -->
  <parentDocument>
    <id root="aa-bb-cc"/>  </parentDocument></relatedDocument><relatedDocument typeCode="APND">
  <!-- the IPS is integrated by the information provided by the "aa1-bb1-cc1" document -->
  <parentDocument>
    <id root="aa1-bb1-cc1"/>  </parentDocument></relatedDocument><!-- the example ends here -->
Item DT Card Conf Description Label
hl7:relatedDocument
 0 … * R (IPSdotsent)
@typeCode
 cs 1 … 1 R
  CONF
The value of @typeCode shall be drawn from value set 2.16.840.1.113883.1.11.11610 x_ActRelationshipDocument (DYNAMIC)
hl7:parentDocument
 1 … 1 R (IPSdotsent)
@classCode
 cs 0 … 1 F DOCCLIN
@moodCode
 cs 0 … 1 F EVN
hl7:id
 II 1 … * R (IPSdotsent)
hl7:code
 CD.IPS 0 … 1 R (IPSdotsent)
@codeSystem
 CONF 0 … 1 F 2.16.840.1.113883.6.1 (Logical Observation Identifier Names and Codes)
hl7:text
 ED 0 … 1 R (IPSdotsent)
hl7:setId
 II 0 … 1 R (IPSdotsent)
hl7:versionNumber
 INT 0 … 1 R (IPSdotsent)