190 likes | 326 Vues
This document offers a comprehensive overview of the Healthcare Provider Directory (HPD) standards and interoperability profiles as articulated by Eric Heflin. Tailored for senior healthcare IT executives and implementation architects, it outlines the significance of HPD in structuring provider information—both organizations and individuals. It highlights the utilization of LDAP for vast scalability, optional federated updates, and semantic interoperability. The document also discusses security, privacy implementations, and typical workflows, providing a valuable resource for healthcare professionals aiming to optimize provider data management.
E N D
Healthcare Provider Directory Eric Heflin Dir of Standards and Interoperability/Medicity
Audience/Scope • Audience • Senior Healthcare IT Technical Executives • Implementation Architects • Implementers seeking a broad overview • Scope • Broad context and guidance about the use of an IHE standard profile for provider
Definitions • Healthcare Provider: Org or person <look at the profile>. Not other types of providers such as insurance providers. • Directory: • LDAP: Something that you already have, open, mature, designed for massive scalability, etc… • <why did we group these together, perhaps have a diagram showing the interplay between the profiles>
What Problem is Being Solved? • Problem statement: <get from the profile> • How do we find people and organizations, what are their attributes (email, phone, etc.)
HPD Definition • HPD = Healthcare Provider Directory • Definition: Designed to maintain a structured list of attributes for both organizations (such as clinics) and people (such as physicians) • Allows extensibility • Largely semantically interoperable • Optional federated updates • Leverages ISO • Status: Released for Trial Implementation
Provider White Pages • PWP slides, compare, contrast • PWP=inside an org • HPD=across orgs • <see if there is an existing deck on PWP>
HPD Use Case • Use case <pull from the profile, prune, reflect in a diagram!> • “What’s the phone for the Mayo clinic?”
HPD Transaction Diagram • Insert ITI TF transaction diagram
HPD Actors • List and define each HPD actor • List each HPD transaction
HPD Options • List and define each HPD option
HPD Workflow(s) • List one or more HPD typical workflows
HPD Security and Privacy • Describe how security and privacy are implemented for this profile
HPD Standards Used • LDAP based • Configuring a new OU • DSML • ISO • Extension of PWP profile
Security and Privacy • XUA++
HPD Attributes • List key types of attributes
HPD Extensibility • Indicate that it’s extensible • E
References • For more information on this topic, please see: • IHE content
Other topics • XUA++ public keys can be stored in HPD or PWP