1. LDAP / HPD mapping to Provider Directory Data Elements
Karen Witting

2. Structural Mapping S&I Provider Directory Concept LDAP equivalent
ISO extension
IHE HPD extension
Individual
InetOrgPerson
HCProfessional
Individual Provider
Organization
HCRegulatedOrganization
Organizational Provider
Individual-Organization Relationship
None
memberOf
Organization-Organization Relationship
Provider Directory
Implicit in LDAP naming structure
N/A

3. Individual LDAP/ISO 21091 HPD Gaps Record Status
Address: Billing, Mailing, Practice
ESI : Address - Direct & URI
Professional Degree
State License
Certification
Date of Birth
Address type: Legal
Address elements: Address Line 2, County
ESI: most attributes
Dig Cert.: ID & Dig. Cert DN
ID, Alternate ID, NPI
Legal/Alt. Names
Type
Specialty
Gender
Telephone: Primary, Mobile, Pager, Facsimile
Dig. Cert.

4. Organization LDAP/ISO 21091 HPD Gaps Record Status
Address: Billing, Mailing, Practice
Certification
ESI : Address - Direct & URI
Address type: Legal
Address elements: Address Line 2, County
ESI: most attributes
Dig Cert.: ID & Dig. Cert DN
Policy
ID, Alternate ID, NPI
Legal/Alt. Names
Type
Telephone: Primary, Facsimile
Specialty
– gap?
Dig. Cert. – gap?

5. Organization-Organization Relationship
Individual-Organization Relationship
LDAP/ISO 21091
HPD
Gaps
Individual ID
Organization ID
Telephone
ESI
Organization-Organization Relationship
Organization ID

6. General Challenges LDAP schema - limited object support
A: coding object elements within string, i.e. Address
B: create new top-level elements and reference to DN name, i.e. Credentials
Extend existing less extensive support
Example: existing support for Direct and URL conflicts with complex ESI object