This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Conference call minutes 9 July 2015"
Jump to navigation
Jump to search
Michael tan (talk | contribs) |
Michael tan (talk | contribs) |
||
Line 38: | Line 38: | ||
*David and Jay will continue to work on the DAM | *David and Jay will continue to work on the DAM | ||
− | * | + | *Michael will extend the conference call's until August |
− | |||
− | |||
Go back to health concern minutes: | Go back to health concern minutes: | ||
[[http://wiki.hl7.org/index.php?title=Health_Concern_Meetings/Conference_Calls_Agenda_and_Minutes]] | [[http://wiki.hl7.org/index.php?title=Health_Concern_Meetings/Conference_Calls_Agenda_and_Minutes]] |
Latest revision as of 09:27, 10 July 2015
Health Concern Topic
Patient Care WG
July 9 2015
Attendees:
- Michael Tan – Chair
- David Pyke
- Jay Lyle
- Stephen Chu ( partial)
Participation Information Phone Number: +1 770-657-9270 Participant Passcode: 943377
Web Meeting Info www.webex.com Meeting number 249 522 346
Topics
- Kathleen Connor has sent a suggestion about security and privacy issues.
- Decided to accept her suggestions i.e. replace confidentiality tag with security label.
- Jay will adjust the Health Concern Model and output accordingly.
- Discussion about the criteria for use case story's.
- Associate events with concerns in order to provide a consolidated view of a concern - e.g., hba1c w diabetes. This was my initial impression of the key driver -- to reduce clutter and provide the user with a clear view of a particular concern. The main use case supports it. It might conflict, though, with the kinds of relationships already being asserted, e.g., between a diagnosis and a lab order and its result.
- Maintain a traceable record of a single concern as understanding evolves and its name changes (including cross-organization reconciliation). This is also illustrated in the main use case. For this criteria we suggested to name "continuity of care" and replace "tracing".
- Provide a way to indicate that some things are of concern, while others are not. We may need to add some unimportant information to the main use case to illustrate that unimportant information does not clutter the problem list.
- Provide a way to indicate which things are of concern to a particular person (via problem list or the 'expresses' relation).
- We also discussed the issue of concerns pointing to health care events of other patients. The use case of a transplantation was brought up. The complexity of this use case might be too difficult for now and should perhaps be left out. If so, we should describe the scope of Health Concerns in the introduction.
- In the review of the DAM document, David and Jay have adjusted chapter 7. Should consult with Larry if asthma could be left out in the story.
- The topic of difference between Problem list and Concerns was touched once more. Health Concerns can be used as a method to re-arrange your problem list. The outcome is still a problem list. It can be seen as an extra tag/column with which you can group your information together.
Any Other Business
- None
Action items
- David and Jay will continue to work on the DAM
- Michael will extend the conference call's until August
Go back to health concern minutes: [[1]]