Personnel White Pages

From IHE Wiki

Revision as of 16:04, 28 November 2008 by JohnMoehrke (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents


Summary

The Personnel White Pages (PWP) Integration Profile provides access to basic human workforce user directory information. This information has broad use among many clinical and non-clinical applications across the healthcare enterprise. The information can be used to enhance the clinical workflow (contact information), enhance the user interface (user friendly names and titles), and ensure identity (digital certificates). This Personnel White Pages directory will be related to the User Identity provided by the Enterprise User Authentication (EUA) Integration Profile previously defined by IHE.

Benefits

This directory information is used to

  • enhance the clinical workflow, with contact information, phone numbers, email address
  • enhance the user interface, with displayable names and titles

Details

The Personnel White Pages (PWP) Integration Profile:

  • specifies a method of finding directory information on the User Identities (user@realm) supplied by the Enterprise User Authentication (EUA) Integration Profile.
  • assumes but does not define access controls, and audit trails.
  • The use of the PWP Profile is intended for use within a healthcare enterprise. Extension to support sharing of the PWP between healthcare enterprises is possible but not fully addressed by this profile. The PWP profile is the first step on an IHE roadmap that includes Digital Certificates, Encryption, Digital Signatures, Medical Credentials, and Roles.

Systems Affected

Systems involved in this profile are:

  • Enterprise-wide information systems that utilize information about human workforce members.


Actors & Transactions:

PWP-Actor-Transaction.jpg

Specification

Profile Status: Final Text

Documents: IHE IT Infrastructure Technical Framework Version 2 or later

  • Vol. 1 - Section 11
  • Vol. 2 - Sections 3.23, 3.24

Underlying Standards:

  • IETF: RFC-2181 Clarifications to the DNS Specification
  • IETF: RFC-2219 Use of DNS Aliases for Network Services
  • IETF: RFC-2782 A DNS RR for specifying the location of services (DNS SRV)
  • RFC 1766 Tags for the Identification of Languages
  • RFC 2251 - Lightweight Directory Access Protocol (v3)
  • RFC 2252 - Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
  • RFC 2253 - Lightweight Directory Access Protocol (v3): UTF-8 String

Representation of Distinguished Names

  • RFC 2256 - A Summary of the X.500(96) User Schema for use with LDAPv3
  • RFC 2798 - Definition of the inetOrgPerson LDAP Object Class
  • RFC 2829 Authentication Methods for LDAP
  • RFC 2830 LDAPv3: Extension for Transport Layer Security
  • RFC 3377 - Lightweight Directory Access Protocol (v3): Technical Specification
  • ISO/TS 17090 directory standard for healthcare identity management
  • CRU: Projet de schémas d’annuaires et de schémas de registres de resources numériques interopérables pour les administrations Document technique – v1, novembre 2002
  • ITU-T: E.123: Notation for national and international telephone numbers
  • HL7 Version 2.5, Chapter 2 – Control
  • DICOM: DICOM Supplement 67 – Configuration Management, January 14, 2004.

See Also

This profile supports the security/privacy model discussed in IHE Security and Privacy for HIE white paper.

Related Profiles

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.

Personal tools