1 / 15

Overview of Healthcare Provider Directory (HPD) Profile for OpenHIE

The HPD Profile, as defined by Integrating the Health Enterprise, supports queries and management of healthcare provider information. It utilizes LDAP and DSML technologies for data storage and querying, with a tree/hierarchy structure. The profile specifies attributes and object classes for both individual and organizational providers, ensuring data standardization. Through the HPD API, SOAP/XML interfaces enable provider query and feed operations. Explore how HPD promotes data standardization and integrates with facility registries to enhance healthcare service delivery.

jcraven
Download Presentation

Overview of Healthcare Provider Directory (HPD) Profile for OpenHIE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HPD Overview Carl Leitner cleitner@intrahealth.orgIntraHealth International OpenHIE Provider Registry Community Call March 6, 2013

  2. HPD Profile • Healthcare Provider Directory (HPD) • HPD Profile is defined by Integrating the Health Enterprise http://www.ihe.net • Profile specifies a specific implementation of a standard to • “supports queries against, and management of, healthcare provider information that may be publicly shared in a directory structure” • Technology built on: • LDAP – for data store/data modelopenLDAP http://www.openldap.org/ApacheDS http://directory.apache.org/apacheds/Microsoft Active Directory • DSML – for APISOAP/XML specification for querying and updating LDAP server http://www.oasis-open.org/committees/dsml/docs/DSMLv2.doc

  3. LDAP Data Model • Not a relational database • Limited Query Language • Quickreads • Slower writes • Tree/hierarchy of objects with attributes

  4. LDAP Terminology - LDIF • LDIF – line delimited interchange format dn: cn=Robert Smith,ou=people,dc=example,dc=com objectclass: inetOrgPerson cn: Robert Smith cn: Robert J Smith cn: bob smith sn: smith uid: rjsmith • dn (distinguished name) is the location of the record in LDAP.read it right to left to walk down tree • objectClass defined the object being stored. Properties/attributes of an object class defined in ldap schema • Remainder are attributes. May be multi-valued (e.g. cn)

  5. LDAP Terminology - Schema • Schema used to define attributes of object class objectclass     ( 2.16.840.1.113730.3.2.2    NAME 'inetOrgPerson'    DESC 'RFC2798: Internet Organizational Person'SUP organizationalPerson    STRUCTURAL        MAY (                audio $ businessCategory $ carLicense $ departmentNumber $                displayName $ employeeNumber $ employeeType $ givenName $                homePhone $ homePostalAddress $ initials $ jpegPhoto $                labeledURI $ mail $ manager $ mobile $ o $ pager $                photo $ roomNumber $ secretary $ uid $ userCertificate $                x500uniqueIdentifier $ preferredLanguage $                userSMIMECertificate $ userPKCS12         )) • Inherit attributes of superior class • Attributes defined globally in schema with data typ http://www.zytrax.com/books/ldap/ape/core-schema.html#organizationalperson

  6. HPD Profile – Organizational Units • HCProfessional for storing individual provider information • HCRegulatedOrganization containing information on organizational providers and its relevant information • HPDCredential to include health related credentials of providers • Relationship to determine membership http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Suppl_HPD.pdf

  7. HPD Profile – Organizational Units HPD HCRegulatedOrganization HCProfessional Relationship Central Hospitaluid=1 Bill Smirth Uid=2 Mary JonesUid=3 Uid=1 Uid=2 Uid=3

  8. HCProfessional Object Class • Stores information about an individual provider • Extends the inetOrgPerson object class • Highlighted Required Attributes: • hcIdentifier • hcProfession • hpdProviderStatus • memberOf

  9. HCRegulatedOrganizationObject Class • Stores information about an organizational provider • Extends the Organization object class • Highlighted Required Attributes: • hcIdentifier • businessType – the type of the organization • hpdProviderStatus • memberOf

  10. HPD API • SOAP + XML API defined via DSMLv2 • Provider Query and Provider Feed ftp://ftp.ihe.net/TF_Implementation_Material/ITI/examples/HPD/

  11. LDAP and Coded Data Lists • LDAP is not relational database • Many-valued attributes • How can we best ensure data standardization?

  12. Coded Data Lists in RHEA • RHEA PR stored coded facilities, standardized data lists #provider dn: nid=10222034995, ou=Providers, dc=moh, dc=gov, dc=rw objectclass: providerPersonnid: 10222034995cn: Chilboa Rainda#and their positingdn: ou=facility|372, nid=10222034995,ou=Providers, dc=moh, dc=gov, dc=rw objectclass: providerPostou: facility|372 #coded facility from Master Facility Listdescription: KatabagemuemployeeType: post_type|pps #coded type of employeelocationCode: county|AU050204 #coded municipality of deployment

  13. RHEA PR – Enforcing Standardization

  14. Linking PR and Facility Registry API(Direct) Facility Registry Provider Registry (LDAP) API(Mediator) Bill Smith works in a facility with code 234 Central Hospital Code: 234 SDMX-HD

  15. For More Information • Provider Registry Google Grouphttps://groups.google.com/forum/#!forum/provider-registry • Provider Registry Wikihttp://www.ihris.org/wiki/Provider_Registry • OpenHIEhttp://www.ohie.org

More Related