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

Difference between revisions of "Conference call minutes 9 February 2016"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "=Health Concern Topic= '''Patient Care WG''' '''February 9nd 2016''' ==Attendees:== *Michael Tan – Chair *David Pyke *Dan Russell *Hank Mayers *David Tao *Russell McDonell ...")
 
 
(8 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
'''February 9nd 2016'''
 
'''February 9nd 2016'''
 
==Attendees:==
 
==Attendees:==
−
*Michael Tan – Chair
+
*Michael Tan – Chair/ Scribe
 
*David Pyke
 
*David Pyke
 
*Dan Russell
 
*Dan Russell
Line 27: Line 27:
  
 
== DAM ==
 
== DAM ==
−
* Hank has submitted a table for chapter 4 of the 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.
−
* This has to be integrated by David Pyke, but David is not on the call.
+
[[File:HealthConcernmodel20160209.jpg]]
−
* In the previous call the group decided to gray out the allergy and problem list.
 
−
* The list would then have to be part of another scope of a DAM. There is no such DAM.
 
−
* FHIR does have a resource called "list".
 
−
* Discussion arises whether the list should be in the scope of the DAM.
 
−
* If the output lists need characteristics of health concerns that are required from the viewpoint of functionality, then we should consider of making it part of the DAM.
 
−
* Examples of such a functionality could be "list purpose" or "list kind".
 
−
* In older versions of the health concern model we had various kinds of lists.
 
−
* The allergy and problem list in the diagram of the September 2015 ballot were put there as the most important examples of output.
 
−
* Suggestion to make the lists more abstract and call it "'''concern lists'''".
 
−
* We have to think of the appropriate attributes of the concern lists.
 
−
* Examples of characteristics of the concern lists are "reconciled" or "unreconciled" lists.
 
−
* Jay will make a proposal. '''Action Jay
 
−
'''
 
  
−
* There were many remarks about the health concern event. A health concern has relationship with all types of events. Readers find this too abstract.  
+
 
−
* The older versions of the model had different classes such as observations, risks as related classes, but readers always found a class that was missing.
+
 
−
* Jay suggests to introduce a intermediate level according to the SOAP model to make it less abstract.
+
* Discussion arises whether the SOAP boxes should be grayed out to express that they are not in scope of the DAM.
−
* This has also the risk that this leads to comments that certain elements will be missing.
+
* The annotation in the green box actually is clear enough.
−
* A suggestion is to split into 2 figures, where the health concern event is drawn in a separate picture with the different SOAP type of elements. '''Action Jay'''
+
* 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==
 
== Action items==
  
 
*Propose text about priorities between health concerns: David
 
*Propose text about priorities between health concerns: David
−
*Submit the NIB: Michael
+
*Revise text in Patient Journey story chapter 7.1; Michael
−
*Change allergy and problem lists to concern lists: jay
 
−
*Proposal for alternative model diagram with SOAP elements related to the health concern: Jay.
 
  
  
 
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 08:49, 10 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.

HealthConcernmodel20160209.jpg


  • 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]]

Retrieved from "https://wiki.hl7.org/w/index.php?title=Conference_call_minutes_9_February_2016&oldid=115062"