2.16.840.1.113883.10.22.4.7 - Revision history

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2024-06-13T05:11:38Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2024-04-03T05:11:48Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2021-09-03T05:13:19Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2021-08-05T05:14:19Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2021-01-05T16:46:05Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2021-01-05T14:42:16Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

2020-07-07T22:00:26Z

Automatic ADBot page (c8016eb06c72b39681eed019b5c776a89972c9bd)

ADbot: Automated ADBot page content

2018-08-23T08:53:04Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-07-02T10:54:46Z

Automated ADBot page content

ADbot: Automated ADBot page content

2018-03-27T20:04:46Z

Automated ADBot page content

@@ Line 5: / Line 5: @@
 =Template ''IPSProblemConcernEntry''=
-<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode
+<p>
-                    is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain
+                This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:
-                    concerned about a prior heart attack).The effectiveTime/low of the Problem Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart. The effectiveTime/high asserts when the concern become inactive, and it is present if the statusCode of the concern act is "completed".A Problem Concern Act can contain many Problem Observations.The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:- Problem
-                        Concern 1--- Problem Observation: Chest PainLater, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.- Problem Concern 1--- Problem Observation (author/time Jan 3, 2012): Chest Pain--- Problem
-                        Observation (author/time Jan 6, 2012): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
+                        The status of the concern (active, inactive,..)
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 16: / Line 36: @@
 *[[2.16.840.1.113883.10.22.4.7/static-2021-08-04T084927|2021-08-04 08:49:27 (Under develeopment)]]
 *[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
-<!--4666445dc3bb7e4dc2cfbde6847a0abaef3af1b1-->
+<!--ea4a5dada69147aad8215fccbd1ae7eaa147fa0d-->

@@ Line 5: / Line 5: @@
 =Template ''IPSProblemConcernEntry''=
-<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack).The effectiveTime/low of the Problem Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart. The effectiveTime/high asserts when the concern become inactive, and it is present if the statusCode of
+<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode
-        the concern act is "completed".A Problem Concern Act can contain many Problem Observations.The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:- Problem Concern 1--- Problem Observation: Chest PainLater, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.- Problem Concern 1--- Problem Observation (author/time Jan 3, 2012): Chest Pain--- Problem Observation (author/time Jan 6, 2012): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
+                    is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 13: / Line 16: @@
 *[[2.16.840.1.113883.10.22.4.7/static-2021-08-04T084927|2021-08-04 08:49:27 (Under develeopment)]]
 *[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
-<!--21345d7908d1993d3de494905877ba5ca616a5fc-->
+<!--4666445dc3bb7e4dc2cfbde6847a0abaef3af1b1-->

@@ Line 5: / Line 5: @@
 =Template ''IPSProblemConcernEntry''=
-<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.
+<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack).The effectiveTime/low of the Problem Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart. The effectiveTime/high asserts when the concern become inactive, and it is present if the statusCode of
-    There are different kinds of status that could be related to a condition:
+         the concern act is "completed".A Problem Concern Act can contain many Problem Observations.The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:- Problem Concern 1--- Problem Observation: Chest PainLater, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.- Problem Concern 1--- Problem Observation (author/time Jan 3, 2012): Chest Pain--- Problem Observation (author/time Jan 6, 2012): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 42: / Line 13: @@
 *[[2.16.840.1.113883.10.22.4.7/static-2021-08-04T084927|2021-08-04 08:49:27 (Under develeopment)]]
 *[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
-<!--7a7ba334ad0c76f4a83e5dd2ef27b6c49f929528-->
+<!--21345d7908d1993d3de494905877ba5ca616a5fc-->

@@ Line 5: / Line 5: @@
 =Template ''IPSProblemConcernEntry''=
-<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack).The effectiveTime/low of the Problem Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart. The effectiveTime/high asserts when the concern become inactive, and it is present if the statusCode of
+<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.
-         the concern act is "completed".A Problem Concern Act can contain many Problem Observations.The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:- Problem Concern 1--- Problem Observation: Chest PainLater, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.- Problem Concern 1--- Problem Observation (author/time Jan 3, 2012): Chest Pain--- Problem Observation (author/time Jan 6, 2012): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
+    There are different kinds of status that could be related to a condition:
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
-<!--c11d3f82b61e104f958c4e40caf66c0c60fb9e54-->
+<!--7a7ba334ad0c76f4a83e5dd2ef27b6c49f929528-->

@@ Line 5: / Line 5: @@
 =Template ''IPSProblemConcernEntry''=
-<p>
+<p>This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:The status of the concern (active, inactive,..) The status of the condition (e.g. active, inactive, resolved,..) The confirmation status [clinical workflow status, certainty] (e.g. confirmed, likely, unlikely,…) Not all of them can be represented in a CDA using the statusCode elements of the concern (ACT) and observation (condition).  So long as the underlying conditions are of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is “active”. Only when the underlying conditions are no longer of concern is the statusCode set to “completed”. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack).The effectiveTime/low of the Problem Concern Act asserts when the concern became active. This equates to the time the concern was authored in the patient's chart. The effectiveTime/high asserts when the concern become inactive, and it is present if the statusCode of
-                    This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s problem list. The purpose of the concern act is that of supporting the tracking of a problem or a condition.There are different kinds of status that could be related to a condition:
+        the concern act is "completed".A Problem Concern Act can contain many Problem Observations.The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of “chest pain”:- Problem Concern 1--- Problem Observation: Chest PainLater, a new Problem Observation of “esophagitis” will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp.- Problem Concern 1--- Problem Observation (author/time Jan 3, 2012): Chest Pain--- Problem Observation (author/time Jan 6, 2012): EsophagitisMany systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.</p>
 ==Actual version==
 {{:{{BASEPAGENAME}}/dynamic}}
@@ Line 35: / Line 12: @@
 ==List of all versions of this template==
 *[[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000|2017-02-15 (Under pre-publication review)]]
-<!--4d7baaa207ca47e5acfb8b1edc73dbb46e43e3b6-->
+<!--c11d3f82b61e104f958c4e40caf66c0c60fb9e54-->

← 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.4.7/static-2017-02-15T000000\|2017-02-15 (Under ~~develeopment~~)]]	+	* [[2.16.840.1.113883.10.22.4.7/static-2017-02-15T000000\|2017-02-15 (Under pre-publication review)]]