PD+Electronic+Service+Information+SWG+Meeting+Session+19

**Time:** 12:00PM - 1:30PM EDT
 * Electronic Service Information Discovery Workgroup Call **
 * Date **:10/20/2011


 * Meeting Agenda:**
 * **Topic** || **Time Allotted** ||
 * ESI Examples || 90 Minutes ||

Attendance
Peter Bachman, Dan Kazzaz, Sam Dechario, Bryan Vargo, Rita Torkzadeh, Lester Keepper, Robert Dieterle, Sally Love Connally, Karen Witting, Ernest Grove, Tynisha Carter, Victor Palli, Virginia Riehl

**Action Items**

 * Action Item: Bob will create examples of how this would work, examples of a finite Content list and the group walk through them together
 * Action Item: Tuesday HPD call will be focused on ESI definitions
 * Action Item: Find more EHR vendors that generate standard content to review ESI definition and contribute to discussion (John Donnelly?)

Meeting Notes
PD Use Case 2 ESI Meeting Minutes
 * Content Type
 * Group may consider merging Content Type and Content Standard into a single Content element
 * Should model be “Look for content first and transport second” or vice versa?
 * Everything has to be labeled with a Content type so we can tell them how to send that type of content
 * EHR knows user wishes to send a particular type of data, needs to be able to query receiver to know what they can receive and how they can receive it.
 * Content Type and Standard together determine what user is trying to send
 * Direct created a new messaging standard where content is not defined at all
 * Direct seeks simplicity of exchange but ignores complexity of content
 * Solution as written may be too complex for EHR vendors to implement, demanding an unreasonably intelligent coding solution
 * Standardize to a point that completely defines content and vehicle in which content is delivered
 * A provider search will return all ESI objects for all content types unless the search specifies content type
 * Receivers may only accept Lab Results (or another Content Type) over a specific channel (such as PDF)
 * What is the process that will be used to accumulate content types? If there is no process for creating that list, the whole thing falls apart.
 * At state level, support those used in industry (IHE model)
 * Question of how much to expose in the structure and how much to explain in the implementation guide
 * Action Item: Bob will create examples of how this would work, examples of a finite Content list and the group walk through them together
 * Action Item: Tuesday HPD call will be focused on ESI definitions
 * Action Item: Find more EHR vendors that generate standard content to review ESI definition and contribute to discussion (John Donnelly?)
 * Action Item: Support team will send Karen Witting Query/Response examples as well as SWG2 work products
 * Goals
 * Logical and consistent to people that use it
 * Simple and short implementation guide