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) (→Topics) |
Michael tan (talk | contribs) (→Topics) |
||
| Line 24: | Line 24: | ||
*Jay will adjust the Health Concern Model and output accordingly. | *Jay will adjust the Health Concern Model and output accordingly. | ||
*Discussion about the criteria for use case story's. | *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 | + | #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. |
| − | 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". |
| − | #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 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). | #Provide a way to indicate which things are of concern to a particular person (via problem list or the 'expresses' relation). | ||
Revision as of 09:14, 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 discussed the issue of concerns pointing to health care events of other patients. The use case of a transplantation was brought up. How do we deal with the observations of the donor patient? Michael will write a use case scenario of a kidney transplant and ask Larry and Stephen how this should be captured in a system. It is not clear if the current model can capture this requirement. An HC event always has a relationship to a patient.
Any Other Business
- Looking at the diagram we wondered if the person now currently attached to health concern event, should be attached to health concern itself.
- Next weeks call is the last call before Michael's holiday.
Action items
- Review and adjust DAM document with Jay ( action David)
- Set up use case scenario for organ transplantation. ( action Jay)
Go back to health concern minutes: [[1]]
