LDAP+X500+IHE+HPD+Workstream+Meeting+10-4-2011


 * Provider Directories (PD) Initiative LDAP X.500/ IHE HPD Workstream Meeting****Date:** 10-04-2011
 * Time:** 11:00 am - 12:00 pm
 * Dial In:**1-408-600-3600 | **Passcode:** 663 367 739

Attendance
Karen Witting, Robert Dieterle, Vincent Lewis, Marian Reed, Lester Keepper, John Moehrke, Lin Wan, Naveen Amiruddin, Victor Palli, William Ryan, Sam Dechario

Action Items

 * **#** || **Date Initiated** || **Action** || **Owner** || **Status** || **Date Closed** ||
 * 1 || 10/4/2011 || Action Item: For Individual - Organization Relationship, explain possible use of existing extensions to support the telephone number, ESI, Email gaps. || Group || OPEN ||  ||
 * 2 || 10/4/2011 || Action Item: Add Organization to Organization objects to spreadsheet || Support Staff || CLOSED ||  ||
 * 3 || 10/4/2011 || Action Item: Call scheduled for 10/11 will be cancelled. Mapping will be completed during F2F session || Support Staff || OPEN ||  ||
 * 4 || 10/4/2011 || Action Item: Discuss Provider Type with SWG2 || Support Staff || OPEN ||  ||

Meeting Notes
Individual
 * Digital Certificate element
 * This element is included in the use case query elements where it is subsumed under the header “ESI security information”
 * Conclusion: Change Query or Return column to Both
 * Proposed Changes/Extensions: Gap, Digital Certificate ID and Digital Certificate distinguished name are not within the HPD schema. Therefore, although the data is available from within the certificate, there is no way to query on it unless an extension was adopted.
 * This is a gap, but a query by Digital Certificate ID or Distinguished Name use case may be more an academic than practical concern
 * Suffix element
 * Does LDAP support this in the schema or is it a gap?
 * Information is typically carried within the “name” rather than broken out as a separate attribute. However, this creates issues with query support for partial names.
 * With LDAP it is common to end all queries with a * wildcard.
 * Proposed Changes/Extensions: Gap, could be supported through an extension
 * Address element
 * Proposed Changes/Extensions: Gap, LDAP/HPD does not currently carry Legal Address but an extension could be used.
 * Provider type element
 * Action Item: Discuss this with Use Case 2 SWG
 * Policy Information
 * Proposed Changes/Extensions: Gap, could be supported through an extension

Individual-Organization Relationship


 * LDAP supports relationships but the relationships do not have attributes. Telephone, ESI, and Email are gaps.
 * There are extensions in use, however they are not currently supported by the LDAP standard. We can make note of these, but should limit the spreadsheet to what is currently supported by LDAP.
 * Action Item: Explain possible use of existing extensions to support the telephone number, ESI, Email gaps under notes.

Next Meeting
**The LDAP/HPD** **workstream call scheduled for 10/11/2011 has been cancelled**. The next work stream meeting will take place at the F2F Meeting.