This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Conference call minutes 24 November 2015"
Jump to navigation
Jump to search
Michael tan (talk | contribs) |
Michael tan (talk | contribs) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
'''Patient Care WG''' | '''Patient Care WG''' | ||
| − | '''November | + | '''November 24 2015 |
''' | ''' | ||
==Attendees:== | ==Attendees:== | ||
| Line 25: | Line 25: | ||
*The distinction between a clinical perspective and an engineering perspective should not be part of a DAM. | *The distinction between a clinical perspective and an engineering perspective should not be part of a DAM. | ||
*The origin of this approach was because of the need to explain the Health Concern from a functional perspective and to translate the requirements into the way this mechanism should function in tracking and monitoring Health Concern issues. | *The origin of this approach was because of the need to explain the Health Concern from a functional perspective and to translate the requirements into the way this mechanism should function in tracking and monitoring Health Concern issues. | ||
| + | *We should also consider which figures should be maintained in the document. The recommendation is to use the realistic use cases, because care providers are critical on correct details. | ||
*We also touched the structure of Health Concerns versus problem concerns and risk concerns. | *We also touched the structure of Health Concerns versus problem concerns and risk concerns. | ||
| − | *A risk concern will lead to a prevention campaign | + | *A problem concern can be a subset of a Health Concern, but health concern's can be broader than problems and can evolve overtime. |
| + | *A Health Concern could be a risk for a health issue. A risk is not a condition, nor is it an event, because it has not happened (yet). The care plan or measures are meant to prevent that condition happening. | ||
| + | *A problem list is a reporting manifestation of data of events and results that are related to Health concern (tagged with concern-id). | ||
| + | *We should also consider a story board where the patient's concern is more apparent (including social & financial aspects). Most use cases now are written from the care providers perspective. | ||
| + | *A risk concern will lead to a prevention campaign. | ||
== Action items== | == Action items== | ||
| − | *Michael will | + | *Michael will send Jay's document with Michael's comment to David Tao and Susan Matney. |
| + | *David and Susan will review the proposal and comment the document within one week, if certain chapters have to be reinstated or new text to be added. | ||
Go back to health concern minutes[[http://wiki.hl7.org/index.php?title=Health_Concern_Meetings/Conference_Calls_Agenda_and_Minutes]] | Go back to health concern minutes[[http://wiki.hl7.org/index.php?title=Health_Concern_Meetings/Conference_Calls_Agenda_and_Minutes]] | ||
Latest revision as of 13:55, 25 November 2015
Health Concern Topic
Patient Care WG
November 24 2015
Attendees:
- Michael Tan – Chair
- David Pyke
- David Tao
- Jay Lyle
- Susan Matney
Participation Information
Phone Number: +1 770-657-9270
Participant Passcode: 943377
Web Meeting Info www.webex.com Meeting number 249 522 346
Topics
- Jay has made a proposal to replace the chapters 4, 5 and 6. Michael has sent this proposal to the list.
- The proposal was discussed in the call. Jay's intention is to remove information that is redundant.
- The distinction between a clinical perspective and an engineering perspective should not be part of a DAM.
- The origin of this approach was because of the need to explain the Health Concern from a functional perspective and to translate the requirements into the way this mechanism should function in tracking and monitoring Health Concern issues.
- We should also consider which figures should be maintained in the document. The recommendation is to use the realistic use cases, because care providers are critical on correct details.
- We also touched the structure of Health Concerns versus problem concerns and risk concerns.
- A problem concern can be a subset of a Health Concern, but health concern's can be broader than problems and can evolve overtime.
- A Health Concern could be a risk for a health issue. A risk is not a condition, nor is it an event, because it has not happened (yet). The care plan or measures are meant to prevent that condition happening.
- A problem list is a reporting manifestation of data of events and results that are related to Health concern (tagged with concern-id).
- We should also consider a story board where the patient's concern is more apparent (including social & financial aspects). Most use cases now are written from the care providers perspective.
- A risk concern will lead to a prevention campaign.
Action items
- Michael will send Jay's document with Michael's comment to David Tao and Susan Matney.
- David and Susan will review the proposal and comment the document within one week, if certain chapters have to be reinstated or new text to be added.
Go back to health concern minutes[[1]]
