LDAP / HPD mapping to Provider Directory Data Elements
-
Upload
rama-davidson -
Category
Documents
-
view
14 -
download
5
description
Transcript of LDAP / HPD mapping to Provider Directory Data Elements
LDAP / HPD mapping to
Provider Directory Data Elements
Karen Witting
Structural MappingS&I Provider Directory Concept
LDAP equivalent
ISO 21091 extension IHE HPD extension
Individual InetOrgPerson HCProfessional Individual Provider
Organization Organization HCRegulatedOrganization Organizational Provider
Individual-Organization Relationship
None None memberOf
Organization-Organization Relationship
None None memberOf
Provider Directory Implicit in LDAP naming structure
N/A N/A
IndividualLDAP/ISO 21091
• ID, Alternate ID, NPI• Legal/Alt. Names• Type• Specialty• Gender• Telephone: Primary,
Mobile, Pager, Facsimile
• Email• Dig. Cert.
HPD • 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
Gaps
OrganizationLDAP/ISO 21091
• ID, Alternate ID, NPI• Legal/Alt. Names• Type• Telephone: Primary,
Facsimile• Specialty• Email – gap?• Dig. Cert. – gap?
HPD • 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
Gaps
Organization-Organization Relationship
LDAP/ISO 21091 HPD
• Individual ID• Organization ID
• Telephone• Email• ESI
Gaps
Individual-Organization Relationship
• Organization ID• 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