This presentation prepared for Now is the time to initiate the one change that will have the most leverage across your business systems Patient Identity.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise
Advertisements

Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing for MPI (PIX) Profile Mike Henderson.
IHE IT Infrastructure Outreach to Patient Care Coordination Domain Michael Nusbaum IT Infrastructure Planning Committee December 13 th, 2010.
PRESENTATION TITLE Name of Presenter Company Affiliation IHE Affiliation.
June 28-29, 2005IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Cross-enterprise Document Sharing for Imaging (XDS-I) Rita Noumeir.
IHE Profile Proposal: Dynamic Configuration Management October, 2013.
Cross Community (XC) Profiles Karen Witting. Outline Vision – as described in 2006 IHE White Paper on Cross Community Exchange Existing – what has been.
Overview of IHE IT Infrastructure Integration Profiles IHE IT Infrastructure Technical Committee Charles Parisot, GE Medical Systems Information Technologies.
Cross-Jurisdictional Immunization Data Exchange Project Updated 4/29/14.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Integrating the Healthcare Enterprise IHE Technical Committee Status IHE ITI Plan Committee - February 2004.
January, Steve Moore Lynn Felhofer Connectathon Patient Identifiers.
Overview of IHE IT Infrastructure Integration Profiles Charles Parisot, GE Healthcare IT IHE IT Infrastructure Technical Committee co-chair.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
September, 2005What IHE Delivers IHE Eye Care Integration Profiles Andrew Casertano Department of Veterans Affairs.
Patient Identity Management
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin – Medicity/THSA.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Audit Trail and Node Authentication Robert Horn Agfa Healthcare.
Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.
Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
July 20, 2007 Healthcare Information Technology Standards Panel Principles for Proper Use of HITSP Interoperability Specifications And Proposal for Proper.
Charter: IHE Server Components project Requesting approval in principle.
Integrating the Healthcare Enterprise Enterprise User Authentication and Consistent Time Glen Marshall Co-Chair, IHE IT Infrastructure Planning Committee.
Patient Encounter Tracking Query (PEQ) Profile Proposal for IHE International IT Infrastructure Technical Committee Last update: 23/Apr/2012.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
Integration Profiles - Overview Integrating the Healthcare Enterprise G. Claeys Agfa Healthcare R&D, Technology Manager Vendor co-chair IHE Europe Courtesy.
September, 2005What IHE Delivers 1 Key Image Notes Evidence Documents Simple Image & Numeric Report Access to Radiology Information IHE Vendors Workshop.
1 Integrating the Healthcare Enterprise Patient Demographics Query IHE IT Technical and Planning Committee June 15 th – July 15 th Public Comment.
Elysium Next Generation Master Patient Index (MPI) Scott Parkey Research Engineer © Axolotl Corp
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
Sharing Value Sets (SVS Profile) Ana Estelrich GIP-DMP.
Review and update of IHE The Future & XDS–I. Overview - IHE Updates IHE Organisational Changes The Infrastructure Domain Radiology Update XDS-I.
IHE IT Infrastructure: The Value Proposition HIMSS 2003 Joining the IHE in its New Enterprise Initiatives.
Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.
Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Integrating the Healthcare Enterprise Personnel White Pages Profile Name of Presenter IHE affiliation.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
Cross-Enterprise User Authentication John F. Moehrke GE Healthcare IT Infrastructure Technical Committee.
Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Cross-Community Patient Identification (XCPI) Brief Profile Proposal for 2009 presented to the IT Infrastructure Technical Committee Karen Witting November.
IHE Workshop – June 2007What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.
IHE IT Infrastructure & Radiology Integration Profiles IHE Update to DICOM Committee Charles Parisot, GE Medical Systems Information Technologies.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Access to Radiology Information Cor Loef Co-chair IHE Radiology Technical.
IHE Update DICOM Committee Taipei, April IHE Global Update IHE Technical Framework for Year 5 V5.5 issued for public comment in February Trial.
Federation Karen Witting. Goals of “Federation” Show a vision for support of cross XDS Affinity Domain communication Show cooperation between IHE and.
IHE Workshop – June 2006What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.
XCPI - Cross-Community Patient Identification (likely to be renamed to something like XC Patient Location and Identification) Karen Witting.
IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Technical Committee co-chair.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Cross-Enterprise User Authentication Year 2 March 16, 2006 Cross-Enterprise User Authentication Year 2 March 16, 2006 John F. Moehrke GE Healthcare IT.
September, 2005What IHE Delivers 1 Patient Index and Demographic Implementation Strategies IHE Vendors Workshop 2006 IHE IT Infrastructure Education Rick.
Shaun Grannis, MD, MS, FAAFP FACMI Biomedical Informatics Scientist Regenstrief Institute / Indiana University The Impact of Interoperability / HIE to.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
XDS Security ITI Technical Committee May, XDS Security Use Cases Prevent Indiscriminate attacks (worms, DOS) Normal Patient that accepts XDS participation.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
Jonathan L. Elion MD, FACC Co-Chair, IHE Cardiology Planning Committee The Basics of IHE: Concepts and Process.
Case Study: HL7 Conformance in VA Imaging Mike Henderson Principal Consultant Eastern Informatics, Inc.
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin - Medicity.
Patient Demographics Query (PDQ) Didi Davis Director, Eclipsys Corporation Co-Chair, IT Infrastructure Planning Committee.
IT Infrastructure Plans
Healthcare Information Technology Standards Panel
Patient Identifier Cross-Referencing for MPI (PIX)
Connectathon Patient Identifiers
IHE Workshop: Displayable Reports (DRPT)
IHE: Integrating the Healthcare Enterprise
Presentation transcript:

This presentation prepared for Now is the time to initiate the one change that will have the most leverage across your business systems Patient Identity Cross Reference Manager (PIX) and Patient Demographic Query (PDQ) Lessons Learned Now is the time to initiate the one change that will have the most leverage across your IT systems IHE

2 Confidential and Proprietary to Initiate Systems, Inc. This presentation  Is about A technical review of lessons learned in the implementation of the PIX and PDQ profiles from one vendors prospective.  It is not A critique of IHE, the personnel, or the processes  Caveat This presentation is the reflections of its author and not necessarily those of Initiate Systems

3 Confidential and Proprietary to Initiate Systems, Inc. What’s the Pix profile say  The Patient Identifier Cross-referencing Integration Profile (PIX) is targeted at healthcare enterprises of a broad range of sizes (hospital, a clinic, a physician office, etc.). It supports the cross-referencing of patient identifiers from multiple Patient Identifier Domains via the following interactions: The transmission of patient identity information from an identity source to the Patient Identifier Cross-reference Manager. The ability to access the list(s) of cross-referenced patient identifiers either via a query/ response or via update notification.  By specifying the above transactions among specific actors, this integration profile does not define any specific enterprise policies or cross-referencing algorithms. By encapsulating these behaviors in a single actor, this integration profile provides the necessary interoperability while maintaining the flexibility to be used with any cross-referencing policy and algorithm as deemed adequate by the enterprise.

4 Confidential and Proprietary to Initiate Systems, Inc. Important note to the profile  The Patient Identifier Cross-reference Manager Actor is not responsible for improving the quality of identification information provided to it by the Identity Source Actors. It is assumed that the Identity Source actors are responsible for providing high quality data to the Patient Identifier Cross-reference Manager. For example, the Patient Identifier Cross-reference Manager Actor is NOT responsible to provide a single reference for patient demographics. The intent is to leave the responsibility for the quality and management of its patient demographics information and the integrity of the identifiers it uses within each Patient Identity Domain (Source actors). When receiving reports and displays from multiple PIX domains, it is inevitable that some of those reports and displays will have inconsistent names.

5 Confidential and Proprietary to Initiate Systems, Inc. Connectathon add/modify/merge test

6 Confidential and Proprietary to Initiate Systems, Inc. Connectathon query test

7 Confidential and Proprietary to Initiate Systems, Inc. General gotcha’s we found  PIX managers = Enterprise Master Patient Indexes (eMPI) The system had to be de-tuned for general use  Not enough demographic information ID’s are part of the demographics – what if someone typed the wrong ID at registration To properly link records more demographics are generally used This caused some records not to link because there wasn’t enough information  Same Demographic information for all patients This causes false linkages to occur therefore searching for a specific ID could yield wrong results Patients with different names from the same address could be household related or potentially fraud case  Queries The query assumes you know the domain If you Query the PIX manager and there is only one registered record then that record should be returned

8 Confidential and Proprietary to Initiate Systems, Inc. What’s the PDQ Profile say  Figure shows the actors directly involved in the Patient Demographics Query Integration Profile and the relevant transactions between them. Other actors that may be indirectly involved due to their participation in Patient ID Cross-referencing, etc. are not necessarily shown.

9 Confidential and Proprietary to Initiate Systems, Inc. Important note to the profile  Patient Demographics Supplier receives a Patient Demographics Query or Patient Demographics and Visit Query request from the Patient Demographics Consumer, and returns demographics (and, where appropriate, visit) information from the single domain that is associated with the application to which the query message is sent. Identifier information may be returned from multiple or single domains; see the “Using Patient Data Query (PDQ) in a Multi-Domain Environment” section (ITI TF-2: Appendix M) for a discussion of the architectural issues involved.

10 Confidential and Proprietary to Initiate Systems, Inc. PDQ Connectathon test

11 Confidential and Proprietary to Initiate Systems, Inc. General gotcha’s we found  PDQ Manager = Enterprise Master Patient Indexes eMPI Solution had to be tuned down to allow for the non- varying data  Not enough and Same demographics Same as previous PIX discussion  Queries Wildcard searches could return too many results in a RHIO or Enterprise environment Single attribute search could yield to many results (i.e. City = Chicago or Last name = Smith In Europe not many vendors supported PDQ query

12 Confidential and Proprietary to Initiate Systems, Inc. Some General Comments about our experience  This was our first year participating and we were confused  IHE personnel was very helpful educating and working through issues  We felt that the tests need to be clearer with a better understanding of the workflows  More time and effort needs to be given to the generation of useful data  Security and Audit test were delayed because of our focus on other issues  During the Europe Connectathon we encountered optional country codes in the HL7 messages

13 Confidential and Proprietary to Initiate Systems, Inc. Some General Comments about our experience  We are seeing increased interest in our support of IHE profiles from vendors and customers  We have a concern about the perceived conflict OMG has with IHE  We would like to see more participation by HL7 and OMG in IHE  We feel IHE has had a positive affect on our product  We will participate in future connectathons

14 Confidential and Proprietary to Initiate Systems, Inc. Questions?