2.16.840.1.113883.10.22.2.7 - Revision history

ADbot: Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

2024-06-13T05:11:51Z

Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

ADbot: Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

2024-04-03T05:12:04Z

Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

ADbot: Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

2021-01-05T16:46:00Z

Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

ADbot: Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

2021-01-05T14:41:20Z

Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

ADbot: Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

2020-07-07T22:00:17Z

Automatic ADBot page (5b8b79e8d447ad1be1b016276ad19143ade88547)

ADbot: Automated ADBot page content

2018-08-23T08:53:00Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-07-02T10:54:42Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-03-27T20:04:42Z

Automated ADBot page content

ADbot: Automated ADBot page content

2017-12-15T10:54:20Z

Automated ADBot page content

ADbot: Automated ADBot page content

2017-07-06T20:33:34Z

Automated ADBot page content

New page

__NOTOC__

{{Templatenote}}
[[Category:Template]]
=Template ''IPSCDArelatedDocument''=
==Actual version==
{{:{{BASEPAGENAME}}/dynamic}}

==List of all versions of this template==
* [[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000|2017-04-12 (Under develeopment)]]

@@ Line 5: / Line 5: @@
 =Template ''IPSCDArelatedDocument''=
-<p>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
+<p>
-                        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
+                An IPS may have three types of parent document:
-                        (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
+                    A superseded version that the present instance of the document wholly replaces (typeCode = RPLC).
-                     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
+                    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
-                    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.” </p>
+                        local patient summary is transformed to originate a new IPS instance.
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 16: / Line 23: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000|2017-04-12 (Under pre-publication review)]]
-<!--4d3cc02c8faea23cfdff84b2dcb2e3a30386e74e-->
+<!--06db5d3b41e69939e0e690f6fec5c8d3ad325ddd-->

@@ Line 5: / Line 5: @@
 =Template ''IPSCDArelatedDocument''=
-<p>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.” </p>
+<p>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
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 11: / Line 16: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000|2017-04-12 (Under pre-publication review)]]
-<!--6f8d379328a6b79a93de28b7f80fed819771bb63-->
+<!--4d3cc02c8faea23cfdff84b2dcb2e3a30386e74e-->

@@ Line 5: / Line 5: @@
 =Template ''IPSCDArelatedDocument''=
-<p>
+<p>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.” </p>
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 23: / Line 11: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000|2017-04-12 (Under pre-publication review)]]
-<!--75fc76146f4d2afcbf9bf2c58d9d72beeb5b0904-->
+<!--6f8d379328a6b79a93de28b7f80fed819771bb63-->

@@ Line 5: / Line 5: @@
 =Template ''IPSCDArelatedDocument''=
-<p>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.” </p>
+<p>
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 11: / Line 23: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000|2017-04-12 (Under pre-publication review)]]
-<!--6f8d379328a6b79a93de28b7f80fed819771bb63-->
+<!--75fc76146f4d2afcbf9bf2c58d9d72beeb5b0904-->

← Older revision		Revision as of 08:53, 23 August 2018
Line 8:		Line 8:

	==List of all versions of this template==		==List of all versions of this template==
−	* [[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000\|2017-04-12 (Under ~~develeopment~~)]]	+	* [[2.16.840.1.113883.10.22.2.7/static-2017-04-12T000000\|2017-04-12 (Under pre-publication review)]]

@@ Line 1: / Line 1: @@
 __NOTOC__
-<!-- ****** CAUTION Manual changes on this page are ineffective: the page is automagically generated by a transformed from an ART-DECOR project by a bot (ADBot). ****** -->
+<!-- ****** CAUTION Manual changes on this page are ineffective: the page is automagically generated by a transformer from an ART-DECOR project by a bot (ADBot). ****** -->
 {{Templatenote}}
 [[Category:Template]]