2.16.840.1.113883.10.22.2.2/static-2017-04-11T000000 - Revision history

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2024-08-07T05:11:36Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2024-06-13T05:11:30Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2024-04-03T05:11:40Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2022-04-22T05:25:52Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-03-26T06:16:42Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-01-05T16:45:29Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-01-05T14:46:53Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-01-05T14:44:06Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-01-05T14:40:41Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

ADbot: Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

2021-01-05T14:14:11Z

Automatic ADBot page (a25da4f5bbc28cae3eb3876bd51521ffe00db736)

@@ Line 3: / Line 3: @@
 author (and in some cases the only one );</li><li>an application that transforms a Patient Summary record into this CDA format may not be an author;</li><li>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.</li></ul><p>Further to this, authorship can give information about the nature of Patient Summary :</p><ul><li>if there is a person author only, then the Patient Summary is the result of a practitioner clinical act;</li><li>if there are device authors only, the summary was
 automatically generated

@@ Line 3: / Line 3: @@
 author (and in some cases the only one );</li><li>an application that transforms a Patient Summary record into this CDA format may not be an author;</li><li>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.</li></ul><p>Further to this, authorship can give information about the nature of Patient Summary :</p><ul><li>if there is a person author only, then the Patient Summary is the result of a practitioner clinical act;</li><li>if there are device authors only, the summary was
 automatically generated

← Older revision		Revision as of 05:11, 3 April 2024
Line 1:		Line 1:
−	~~<table~~	+	<table xmlns="http

← Older revision		Revision as of 05:25, 22 April 2022
Line 1:		Line 1:
−	~~<table~~	+	<table

← Older revision		Revision as of 06:16, 26 March 2021
Line 1:		Line 1:
−	~~<table~~	+	<table

← Older revision		Revision as of 16:45, 5 January 2021
Line 1:		Line 1:
−	~~<table xmlns="http~~	+	<table

@@ Line 3: / Line 3: @@
                              definitely a document author (and in some cases the only one );</li><li>an application that transforms a Patient Summary record into this CDA format may not be an author;</li><li>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.</li></ul><p>Further to this, authorship can give information about the nature of Patient Summary :</p><ul><li>if there is a person author only, then the Patient Summary is the result of a practitioner clinical act;</li><li>if there are device
                             authors

@@ Line 1: / Line 1: @@
-<table xmlns="http://www.w3.org/1999/xhtml" width="100%" border="0" cellspacing="3" cellpadding="2" class="artdecor " style="background: transparent;"><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Id</th><td style="text-align: left;">2.16.840.1.113883.10.22.2.2||</td><th style="width: 20em; text-align: left;">Effective Date</th><td style="text-align: left;">2017‑04‑11</td></tr><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Status</th><td style="text-align: left;">[[File:Korange.png|14px]] Under pre-publication review</td><th style="width: 20em; text-align: left;">Version Label</th><td style="text-align: left;">STU1</td></tr><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Name</th><td style="text-align: left;">IPSCDAauthor</td><th style="width: 20em; text-align: left;">Display Name</th><td style="text-align: left;">IPS CDA author</td></tr><td style="text-align: left;" colspan="4"><table id="templateDescTable" width="100%" border="0" cellspacing="3" cellpadding="2" class="artdecor treetable" style="background: transparent;"><tr class="desclabel"><td style="height: 1.5em;">Description</td></tr><tr><td><div><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).</p><p>For definition “The author element represents the creator of the clinical document. If the role of the actor is the <b>entry of
+<table xmlns="http://www.w3.org/1999/xhtml" width="100%" border="0" cellspacing="3" cellpadding="2" class="artdecor " style="background: transparent;"><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Id</th><td style="text-align: left;">2.16.840.1.113883.10.22.2.2</td><th style="width: 20em; text-align: left;">Effective Date</th><td style="text-align: left;">2017‑04‑11</td></tr><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Status</th><td style="text-align: left;">[[File:Korange.png|14px]] Under pre-publication review</td><th style="width: 20em; text-align: left;">Version Label</th><td style="text-align: left;">STU1</td></tr><tr style="vertical-align: top;"><th style="width: 20em; text-align: left;">Name</th><td style="text-align: left;">IPSCDAauthor</td><th style="width: 20em; text-align: left;">Display Name</th><td style="text-align: left;">IPS CDA author</td></tr><td style="text-align: left;" colspan="4"><table id="templateDescTable" width="100%" border="0" cellspacing="3" cellpadding="2" class="artdecor treetable" style="background: transparent;"><tr class="desclabel"><td style="height: 1.5em;">Description</td></tr><tr><td><div><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).</p><p>For definition “The author element represents the creator of the clinical document. If the role of the actor is the <b>entry of
                              information from his or her own knowledge or application of skills</b>, that actor is the author. If one actor provides information to another actor <b>who filters, reasons, or algorithmically creates new information</b>, then that second actor <b>is also an author, <u>having created information from his or her own knowledge or skills.</u>”</b> [From Implementation                         Guide for CDA Release 2: Imaging Integration – UV Realm, March 2009].</p><p>According to this definition, not any device that generates the electronic document has to be considered as an author:</p><ul><li>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 );</li><li>an application that transforms a Patient Summary record into this CDA format may not be an author;</li><li>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.</li></ul><p>Further to this, authorship can give information about the nature of Patient Summary :</p><ul><li>if there is a person author only, then the Patient Summary is the result of a practitioner clinical act;</li><li>if there are device
                             authors

← Older revision		Revision as of 14:14, 5 January 2021
Line 1:		Line 1:
−	~~<table~~	+	<table xmlns="http