LDAP+X500+IHE+HPD+Workstream+Meeting+9-6-2011

Date: 9-6-2011, 11:00 am - 12:00 pm Name: Provider Directories (PD) Initiative LDAP X.500/ IHE HPD Workstream Meeting Session 1

Objectives:
Continue mapping data elements to the LDAP X500 IHE HPD standards

Chris Andreou, Ernest Grove, Karen Witting, Naveen Amiruddin, Vince Lewis, John Sanchez, Ron Sawdey, Terri Skalabrin, Susan Campbell, Lester Keepper, Van Nguyen, Robert Dieterle, Alfred Kausel, Virginia Riehl, Tynisha Carter, Peter Bachman, Ken Pool
 * Attendees:**

__Panelist Attendees:__ Bob Dieterle, Karen Witting, Erik Pupo, Jonathan Tadese, Kelly Conlin

**Action Items:**

 * **Date** || **Description** || **Status** || **Notes** ||
 * 9/6/11 || Update Data Mapping Spreadsheet to reflect changes suggested by workgroup volunteers || OPEN || Support Team to Complete ||

Meeting Minutes
Discussion to explain that this workgroup is evaluating schema capabilities (i.e. data elements) and not transport
 * HPD is the HPD schema which extends LDAP
 * Work on this top down in tandem for each element
 * Address extensions from international standards

Review of Data Element Mapping to LDAP X.500/ IHE HPD Standard Spreadsheet. Discussion of changes and revisions outlined below:
 * Decision made to combine spreadsheet and map according to object class
 * Object class will tell us whether it is LDAP, ISO, HPD
 * Using our knowledge of what object class means to build out this table, will it be too subtle for some?
 * Object Identifier should not be used for reference – too complex
 * At some point, we may need to break out into the Object Class to be more descriptive
 * Object Class:
 * inetOrg person - LDAP
 * H-C – ISO
 * HPD – HPD Providers
 * OIDs should be included in final workproduct – verbal agreement from Ken, Terri, John, Vince, Karen, Les agree (all others reached consensus)
 * ‘Match’ column deleted to eliminate duplication
 * Define column for multiplicity (single, multi-value, conditional multi-value [if not blank or null, then it could be multi-value])
 * LDAP doesn’t support the third option formally but the support specification would have to support that capability
 * Vote to add Multiplicity column
 * Query, Response, or Both Column relative to S&I
 * Eliminate redundancy from query and response data elements