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

**Time:** 8:00AM - 5:00PM EDT
 * Electronic Service Information Discovery Face-to-Face Meeting **
 * Date **:10/19/2011

‍‍‍‍‍‍Attendance
Need to Update

‍‍‍‍‍‍Action Items

 * Action Item – Finish developing the ESI definition worksheets
 * Action Item – John will update “Preferred Identity Standards” definition and comments

‍‍‍‍‍‍Meeting Notes

 * Review Response Data Set**
 * Date of Birth
 * Not included as it is unlikely requester would know this information. Two individuals with identical name could be differentiated by relationship element.
 * Is not applicable given the parameters of the use case
 * Provider’s may not want to include DOB in a directory
 * Remove Digital Certificate data element from individual
 * DC is now included in the ESI
 * Action Item: License Type list will be defined in code set meetings
 * State Granting Professional Degree
 * States do not grant degrees, institutions do
 * Decision: Remove data element
 * Granting Institution of Professional Degree
 * Difficult to maintain a standard list
 * Decision: Define as a free text field to hold the formal name of an institution
 * Certification Object
 * Clarified definition of each data element
 * Public Digital Certificate
 * Decision: A 64 bit encoded representation of the public digital certificate.
 * Policy Information Object
 * Policy Name element - Will anyone use this field? The definition is very nebulous. Will the data be trustworthy?
 * This object meets a future state need. Computable Policy Objects are currently being defined and will be used in the near future.


 * Complete ESI**
 * Action Item: Bob, Karen, Gail, Ken, and Lin (or their chosen SME representatives) will discuss this object offline. Support team will schedule two meetings a week until definition is complete.


 * Complete Query**
 * Organization email
 * Should email be held in the ESI object alone or can it be available in multiple places?
 * Action Item: Group will discuss email element in the future.
 * Updated Electronic Address to reflect Electronic Service Information
 * Action Item: Support team will harmonize the data elements across the Use Case 2 document


 * Query/Response Examples**
 * This chart will undergo consensus but will not be presented to ONC in its current form.
 * This chart provides a general set of behaviors. Implementation under some standards would not work as described.
 * The chart provides minimally expected behaviors. To be compliant, a system should implement at least these behaviors although it may implement many more.
 * Action Item: The group will review these behaviors and decide if they are appropriate and complete as minimally expected behaviors.
 * Action Item: Aaron Seib will attempt to simplify descriptions. Support team will provide him with an excel copy of the document.


 * X12N Mapping**
 * Meeting will focus solely on gaps in mapping
 * For digital certificate storage, X12 currently does not have binary object but it will be added next year. In the meantime, it could be stored as a text string after encoding.
 * Action Items: Support team will update all references to other rows (“see row x”)


 * HPD Mapping**
 * Action Item: Support team will remove Digital Certificate object and move elements into ESI
 * Action Item: Bob will talk to Vincent to answer gaps in “Provider Directory” qualifier section of spreadsheet.
 * Action Item: Support team will create one more sheet which is the x500/LDAP sheet. HPD will be separate. What we have is HPD, what we need to do is also do the mapping onto LDAP. According to Karen, anything in the object class that has HPDcredentials is a gap in LDAP.
 * General**
 * Currently this initiative addresses more than “Provider Directories” - should we change the name?

Action Item: Support team will upload latest version of all documents from Bob’s computer.