LDAP / HPD mapping to Provider Directory Data Elements Karen Witting

Structural Mapping S&I Provider Directory Concept LDAP equivalent ISO 21091 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

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 Email Dig. Cert.

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 Email – gap? Dig. Cert. – gap?

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

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