Revision as of 08:06, 31 October 2014

Health Concern Topic

Patient Care WG October 30, 2014

a. Review UML model

We reviewed the comments from row 7 onwards and looked at the impact for the model.
Graham asks whether concerns should have a classification of the type of concern, such as chronic, acute, episodic concerns. This requirement has not been expressed so far in the use cases.
Another issue brought forward is a method to prioritize health issues. It is not clear whether the priority should be expressed in the concerns or in the related elements such as care plans/
Row 9 led to discussion about the relationship between concerns and problems. A problem is a concern, but not all concerns are problems.
row 10 revived the discussion of the wording event and concern tracking. Tracking is an activity that takes place within the concern to monitor health issues of a patient.

none

@@ Line 21: / Line 21: @@
 *Graham asks whether concerns should have a classification of the type of concern, such as chronic, acute, episodic concerns. This requirement has not been expressed so far in the use cases.
 *Another issue brought forward is a method to prioritize health issues. It is not clear whether the priority should be expressed in the concerns or in the related elements such as care plans/
-*During the session we ran thru the comments once more.
+*Row 9 led to discussion about the relationship between concerns and problems. A problem is a concern, but not all concerns are problems.
-*row 4: We recognize that different actors ( users) have different rights, such as viewing, updating and creating concerns.
+*row 10 revived the discussion of the wording ''event'' and ''concern tracking''. Tracking is an activity that takes place within the concern to monitor health issues of a patient.
-*row 7: We have removed the current Health Concern Name. This information can retrieved by looking at the most recent Health Concern name.
-*We have added the element Provider to the diagram.
 ==AOB==