This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Conference call minutes 20 November 2014"

From HL7Wiki
Jump to navigation Jump to search
Line 19: Line 19:
 
Ballot material must be submitted December the 7th. Michael has started editing the MS Word Document to align with ballot comments. The document will be sent to Stephen and Laura to review the use cases.
 
Ballot material must be submitted December the 7th. Michael has started editing the MS Word Document to align with ballot comments. The document will be sent to Stephen and Laura to review the use cases.
  
===Model review:===
+
==Model review:==
  
*We reviewed the comments from  row 10b onwards and looked at the impact for the model.
+
*Should there always be a Care plan when action is taken towards a concern? We can only speak of plan when you document the intent and communicate it with others. A Care Plan is defined as a sophisticated  plan that will include monitoring.
*Tracking is an activity that takes place within the concern to monitor health issues of a patient. It belongs to the dynamic behavior of health concerns.
+
*We decide not to go to deep into (Care) plan, because that is not what health concerns are about. We leave it flexible to the user whether to incorporate care plans or not.
*We do not agree to rename health concern into health concern tracker, but we have added an extra attribute to explain tracking.
+
*A relationship between concerns is added. The naming of the relationships are still to be reconsidered.
*Do we need provider as an extra item? This arises as a provider could be an originator of concerns (besides the patient).
+
*comorbidity has been added to the subconcerns.
*We decide not to and also remove the relationship of patient as creator of a health concern.
+
*rename concern start date & end date? still ambiguous. also, that would belong on the concern, not the component. Clarify concern time is clincial; add activity time analog to "tracker" (or concern grouper. Also clarify diff between component time and named time
*We decide to keep the relationship between health concern components and added an extra relationship between concerns.
 
*Care plan should be light coloured item to express that is not the focus of this dam and should be considered as an external class.
 
*Should there always be a Care plan? Could an action related to a concern be initiated without a plan? Is a fixed protocol a plan?
 
  
 
==AOB==
 
==AOB==

Revision as of 07:39, 21 November 2014

Health Concern Topic

Patient Care WG November 20, 2014

Attendees

  • Michael Tan – Chair
  • Jay Lyle
  • Stephen Chu
  • Laura Heermann Langford

AGENDA

  • planning
  • review UML model
  • next meeting

Planning

Ballot material must be submitted December the 7th. Michael has started editing the MS Word Document to align with ballot comments. The document will be sent to Stephen and Laura to review the use cases.

Model review:

  • Should there always be a Care plan when action is taken towards a concern? We can only speak of plan when you document the intent and communicate it with others. A Care Plan is defined as a sophisticated plan that will include monitoring.
  • We decide not to go to deep into (Care) plan, because that is not what health concerns are about. We leave it flexible to the user whether to incorporate care plans or not.
  • A relationship between concerns is added. The naming of the relationships are still to be reconsidered.
  • comorbidity has been added to the subconcerns.
  • rename concern start date & end date? still ambiguous. also, that would belong on the concern, not the component. Clarify concern time is clincial; add activity time analog to "tracker" (or concern grouper. Also clarify diff between component time and named time

AOB

none

Next call

  • The meeting on Thanksgiving on November 27th will be cancelled.
  • The first call will be on December the 4th. We will need to submit the document that weekend.