Conference call minutes 9 February 2016

Health Concern Topic

Patient Care WG

February 9nd 2016

Attendees:

• Michael Tan – Chair/ Scribe
• David Pyke
• Dan Russell
• Hank Mayers
• David Tao
• Russell McDonell
• Lawrence McKnight

Participation Information Phone Number: +1 770-657-9270 Participant Passcode: 943377

Web Meeting Info www.webex.com Meeting number 238 558 505

Minutes 2 February

• Motion to approve the minutes by Hank Mayers, second by David Tao.
• 1 abstention, 0 against, 5 approve.

DAM

• Jay could not be present, but has sent a proposal for the new model in which the concern list and health concern events were adapted according to the motions of February 2nd.

• Discussion arises whether the SOAP boxes should be grayed out to express that they are not in scope of the DAM.
• The annotation in the green box actually is clear enough.
• Motion to discard the SOAP boxes ( Subjective, Objective, Judgement, Intervention) and keep the annotation in the green box.
• Motion moved by Dan, second by David Tao: 0 abstentions, 0 against, 5 in favour.

• Dan raises the issue that the model does not convey the relationship between health concern and health concern event properly.
• It does not seem to represent the model that Larry Weed has documented in his POMR article.
• How does the health concern acquire it's name? The health concern itself does not seem to contain the content of the health concern.
• The name of health concern originates from a health concern event. This could be an diagnosis, a finding or even an observation where a care providers expresses his concern and tags the event to a health concern.
• The health concern event from which the health concern derives it's name can be found through the relationship of ConcernIdentifyingEvent.
• The name of the health concern is derived from this event and copied into the local name of the health concern class.
• Eventually the care provider might reconsider the name of the health concern and override it with newer insight extracted from a new finding.
• A new ConcernIdentifyingEvent is created with a newer validity date.
• The name health concern event is misleading for Dan and suggests to call it EHR data item.
• The others object because not all items are meant to be attached to the health concern.
• The intention is to connect events that occur at a certain time point to the health concern.
• This enables a care provider to select and tag events, such as findings, encounters, observations, therapies, medication therapies to that health concern.
• The DAM illustrates these time related stories in figure 1 and figure 7.
• The explanation in figure 7 is not professional enough and has to be corrected.
• Question arises whether the moment ( time) when the health concern event was attached to the health concern should be captured.

Action items

• Propose text about priorities between health concerns: David
• Revise text in Patient Journey story chapter 7.1; Michael

Go back to health concern minutes[[1]]