1 / 15

Patient Identifier Cross-Referencing for MPI (PIX)

Patient Identifier Cross-Referencing for MPI (PIX). Didi Davis Director, Eclipsys Corporation Co-chair, IT Infrastructure Planning Committee. W W W . I H E . N E T. Providers and Vendors Working Together to Deliver Interoperable Health Information Systems In the Enterprise

nschofield
Download Presentation

Patient Identifier Cross-Referencing for MPI (PIX)

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. Patient Identifier Cross-Referencing for MPI (PIX) Didi Davis Director, Eclipsys Corporation Co-chair, IT Infrastructure Planning Committee

  2. W W W . I H E . N E T Providers and Vendors Working Together to Deliver Interoperable Health Information Systems In the Enterprise and Across Care Settings Interoperability Strategy Workshop

  3. IT Infrastructure Profiles 2004 Patient Identifier Cross-referencing for MPI (PIX) Retrieve Information for Display (RID) Consistent Time (CT) Patient Synchronized Applications (PSA) Enterprise User Authentication (EUA) 2005 Patient Demographic Query (PDQ) Cross Enterprise Document Sharing (XDS) Audit Trail and Note Authentication (ATNA) Personnel White Pages (PWP) 2006 Cross-Enterprise User Authentication (XUA) Document Digital Signature (DSG) – Notification of Document Availability (NAV) Patient Administration/Management (PAM) • Patient Identifier Cross-referencing for MPI (PIX) • (Map patient identifiers across independent identification domains) Interoperability Strategy Workshop

  4. Patient Identifier Cross-referencing for MPIAbstract / Scope • Allow all enterprise participants to register the identifiers they use for patients in their domain • Participants retain control over their own domain’s patient index(es) • Support domain systems’ queries for other systems’ identifiers for their patients • Optionally, notify domain systems when other systems update identifiers for their patients Interoperability Strategy Workshop

  5. Patient Identifier Cross-referencing for MPIValue Proposition • Maintain all systems’ identifiers for a patient in a single location • Use any algorithms (encapsulated) to find matching patients across disparate identifier domains • Lower cost for synchronizing data across systems • No need to force identifier and format changes onto existing systems • Leverages standards and transactions already used within IHE Interoperability Strategy Workshop

  6. Patient Identifier Cross-referencing for MPITransaction Diagram Interoperability Strategy Workshop

  7. Patient Identifier Cross-referencing for MPIProcess Flow Showing ID Domains & Transactions Interoperability Strategy Workshop

  8. Patient Identifier Cross-referencing for MPI B:X456C: ? B:X456C: 2RT Patient Identity Cross References Interoperability Strategy Workshop

  9. Patient Identifier Cross-referencing for MPIActors Patient Identity Source • Definition • Assigns patient identities within its own domain • Notifies Patient Identifier Cross-reference Manager of all events related to patient identification (creation, merge, etc.) • Example: Registration (ADT) Actor in IHE Radiology Scheduled Workflow (SWF) Profile • Transaction Supported - Required • Patient Identity Feed [ITI-8] (as sender) Interoperability Strategy Workshop

  10. Patient Identifier Cross-referencing for MPIActors Patient Identifier Cross-reference Consumer • Definition • Requires information about patient identifiers in other domains • Requests patient identifier information from Patient Identifier Cross-reference Manager • Transaction Supported - Required • PIX Query [ITI-9] (as sender) • Transaction Supported - Optional • PIX Update Notification [ITI-10] (as receiver) Interoperability Strategy Workshop

  11. Patient Identifier Cross-referencing for MPIActors Patient Identifier Cross-reference Manager • Definition • Serves a well-defined set of Patient Identifier Domains • Receives patient identifier information from Patient Identity Source Actors • Manages cross-referencing of identifiers across domains • Transactions Supported - Required • Patient Identity Feed [ITI-8] (as receiver) • PIX Query [ITI-9] (as receiver) • PIX Update Notification [ITI-10] (as sender) Interoperability Strategy Workshop

  12. Patient Identifier Cross-referencing for MPIStandards Used HL7 Version 2.5 • ADT Registration and Update Trigger Events • A01: inpatient admission • A04: outpatient registration • A05: pre-admission • A08: patient update • A40: merge patient • Queries for Corresponding Identifiers (ADT^Q23/K23) • Notification of Identifiers Lists Updates (ADT^A31) Interoperability Strategy Workshop

  13. PIX Integration Profile & MPIThe typical view Master Patient Index Patient Identity Cross-reference Manager Master (A) PatientIdentity Source Patient Identification Domain A (Master Domain) Patient Identification Domain B Patient Identification Domain C Interoperability Strategy Workshop

  14. PIX Integration Profile & MPIThe Equivalent IHE Model Master Patient Index Patient Identity Cross-reference Manager Patient Identification Domain A (Master Domain) Master (A) PatientIdentity Source Patient Identification Domain B Patient Identification Domain C Interoperability Strategy Workshop

  15. More information…. • IHE Web sites: www.ihe.net • Technical Frameworks, Supplements • ITI Technical Framework • Radiology Technical Framework • LAB Technical Framework • Cardiology Technical Framework • ITI Supplements for trial implementation • August 2005: Radiology, Cardiology, IT Infrastructure, PCC • Non-Technical Brochures : • Calls for Participation • IHE Fact Sheet and FAQ • IHE Integration Profiles: Guidelines for Buyers • IHE Connect-a-thon Results • Vendor Products Integration Statements Interoperability Strategy Workshop

More Related