2.16.840.1.113883.10.22.2.2 - Revision history

ADbot: Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

2024-04-03T05:11:56Z

Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

ADbot: Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

2021-01-05T16:46:26Z

Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

ADbot: Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

2021-01-05T14:41:31Z

Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

ADbot: Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

2020-07-07T22:01:03Z

Automatic ADBot page (ff1173ccd7f7e4559db430005de6d007a84114de)

ADbot: Automated ADBot page content

2018-08-23T08:53:31Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-07-02T10:55:12Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-03-27T20:05:17Z

Automated ADBot page content

ADbot: Automated ADBot page content

2017-12-15T10:52:58Z

Automated ADBot page content

ADbot: Automated ADBot page content

2017-07-06T20:34:00Z

Automated ADBot page content

New page

__NOTOC__

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

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

@@ Line 5: / Line 5: @@
 =Template ''IPSCDAauthor''=
-<p>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 this CDA format may not be an author;For cross-border exchange purposes, a device, which modifies 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 provide 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
+<p>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
-      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).</p>
+                        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
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 12: / Line 18: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000|2017-04-11 (Under pre-publication review)]]
-<!--db5419b77f93b32a000feb631cc81d92c40d98d1-->
+<!--390a045d57d61e577c54dfcca51f85af7364f6df-->

@@ Line 5: / Line 5: @@
 =Template ''IPSCDAauthor''=
-<p>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
+<p>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 this CDA format may not be an author;For cross-border exchange purposes, a device, which modifies 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 provide 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
-                            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
+      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).</p>
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 18: / Line 12: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000|2017-04-11 (Under pre-publication review)]]
-<!--b94b2ad393c7f372c65e2d81e70e3f61a688acd6-->
+<!--db5419b77f93b32a000feb631cc81d92c40d98d1-->

@@ Line 5: / Line 5: @@
 =Template ''IPSCDAauthor''=
-<p>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 this CDA format may not be an author;For cross-border exchange purposes, a device, which modifies 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 provide 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
+<p>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
-      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).</p>
+                            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
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 12: / Line 18: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000|2017-04-11 (Under pre-publication review)]]
-<!--db5419b77f93b32a000feb631cc81d92c40d98d1-->
+<!--b94b2ad393c7f372c65e2d81e70e3f61a688acd6-->

← 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.2/static-2017-04-11T000000\|2017-04-11 (Under ~~develeopment~~)]]	+	* [[2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000\|2017-04-11 (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]]