Difference between revisions of "Patient Identifier Cross-Reference HL7 v3"

From IHE Wiki
Jump to navigation Jump to search
Line 8: Line 8:
 
* Providing the ability to access the list(s) of cross-referenced patient identifiers either via a query/ response or via an update notification.
 
* Providing the ability to access the list(s) of cross-referenced patient identifiers either via a query/ response or via an update notification.
  
The "v3" version of the Patient Identifier Cross-Referencing profile leverages HL7 version 3 and SOAP-based web services. The scope of the Patient Identity Feed, the PIX Query, and the PIX Update Notification is identical as that for the HL7 v2.5 messages (i.e. same transaction semantics, same message constraints), however in this version we are providing more details for implementers of the individual transactions, and we are using the 2007 DSTU of the HL7 V3 Patient Topic as the basis of the messages in the transaction.
+
This "v3" version of the Patient Identifier Cross-Referencing profile leverages HL7 version 3 and SOAP-based web services. The scope of the Patient Identity Feed, the PIX Query, and the PIX Update Notification is identical as that for the HL7 v2.5 messages (i.e. same transaction semantics, same message constraints), however in this version we are providing more details for implementers of the individual transactions, and we are using the 2007 DSTU of the HL7 V3 Patient Topic as the basis of the messages in the transaction.
  
 
==Benefits==
 
==Benefits==

Revision as of 12:18, 13 April 2011


Summary

The Patient Identifier Cross Referencing for HL7v3 (PIXv3) Integration Profile supports the cross-referencing of patient identifiers from multiple Patient Identifier Domains by:

  • Transmitting patient identity information from an identity source to the Patient Identifier Cross-reference Manager.
  • Providing the ability to access the list(s) of cross-referenced patient identifiers either via a query/ response or via an update notification.

This "v3" version of the Patient Identifier Cross-Referencing profile leverages HL7 version 3 and SOAP-based web services. The scope of the Patient Identity Feed, the PIX Query, and the PIX Update Notification is identical as that for the HL7 v2.5 messages (i.e. same transaction semantics, same message constraints), however in this version we are providing more details for implementers of the individual transactions, and we are using the 2007 DSTU of the HL7 V3 Patient Topic as the basis of the messages in the transaction.

Benefits

Cross-referencing and linkage of patient information:

  • without the need to define or compromise any specific enterprise policies or cross-referencing algorithms
  • providing the necessary interoperability while maintaining the flexibility to be used with any cross-referencing policy and algorithm as deemed adequate by the enterprise.

Process Flow:

PIX-Process-Flow.jpg

Details

The Patient Identifier Cross Referencing (PIX) Integration Profile supports two domains:

  • A Patient Identifier Domain is defined as a single system or a set of interconnected systems that all share a common identification scheme (an identifier and an assignment process to a patient) and issuing authority for patient identifiers.
  • The Patient Identifier Cross-reference Domain embodies the following assumptions about agreement within the group of individual Identifier Domains:
  • They have agreed to a set of policies that describe how patient identities will be cross-referenced across participating domains;
  • They have agreed to a set of processes for administering these policies;
  • They have agreed to an administration authority for managing these processes and policies.

All these assumptions are critical to the successful implementation of this profile. This integration profile imposes minimal constraints on the participating Patient Identifier Domains and centralizes most of the operational constraints for the overall Patient Identification Cross-reference Domain in the Patient Identifier Cross-reference Manager Actor.

Systems Affected

Systems involved in this profile are:

  • Local and enterprise-wide information systems that utilize and patient identity (i.e., admit-discharge-transfer (ADT)/registration systems and hospital information system (HIS ))


Actors & Transactions:

PIX-Actor-Transaction.jpg

Specification

Profile Status: Final Text

Documents: IHE IT Infrastructure Technical Framework Version 1 or later

  • Vol. 1 - Section 5
  • Vol. 2 - Sections 3.8, 3.9, 3.10

Underlying Standards:

See Also

Related Profiles

This page is based on the Profile Template

Current: IT Infrastructure Technical Framework.