The Initiate EMPI Proposition

Transcription

1 Cemil Browne Principal Consultant 25th May 2010 The Initiate EMPI Proposition Information Management

2 Patient identification it s not easy Correctly identifying patients at the point of data entry is difficult Misidentification is a widespread problem Many causes Patient Registration staff Technology Workflow 2

3 Shared Information or Data Exchange Past Limited content Limited access Value in ownership Power in control Today Ubiquitous content Readily accessible Value in usage Power in coordination

4 Challenges to Achieving HIE Providers don t have access to complete Information.across continuum of care, impacts decision making Family History Exam Records Existing systems are not connected manually re-entering patient demographic and services information -- time consuming & error prone Costs continue to increase implementing new systems, but not achieving goals Limited information sharing across Boundaries cannot leverage patient or provider indexes Patient Symptoms Treatment Records Patient Healthcare Data Prescription History Ambulatory Admission History Ambulatory Data Providers are not recognised consistently cannot notify them in a timely & consistent manner or verify current credentials ensuring patient safety 4

5 The Fundamental Problem Data about patients and providers is spread across multiple systems in an inconsistent and fragmented way Interoperability is hard to achieve Data will always live in multiple distributed systems Poor availability, quality, and trust in a common key to find or retrieve all the records associated with an entity Data quality problems will exist throughout all systems 5

6 Linking records electronically is one of the greatest challenges facing healthcare Healthcare organisations currently don t do a stellar job of it within their own systems Duplicate Medical Record Rates in single facility MPI: 8-20% The larger the database, the higher the error rate, often as high as 30-40% Over 30% of all Master Person Index (MPI) records have an invalid or blank value in Name (first/last), Date of Birth or Gender Jumps to over 60% if middle name counted Over 80% of all confirmed duplicate records have a data discrepancy in one or more key patient identifying fields i.e., Name, Date of Birth, Medicare # or Gender Nearly 40% of all duplicate records have a discrepancy in the first or last name Valid Medicare Number captured 50% of the time, sometimes worse 6

7 How can Initiate help? Patient / Provider Data Sources Source 1 Source 2 Source 3 Name Local ID IHI DOB Sex Address 1 Postcode Home phone Mobile Dr Kath J. Jones 1:N /06/ Sussex St Dr Kate Lamb 2:2736 Female Mrs. K. Jones 3:S /06/1970 Level 1, 32 Sussex Rd Catherine Lamb n:97662 P /06/2006 Female Dr Kath J. Jones /06/1970 Female Level 1, 32 Sussex St Consuming Systems System 1 System 2 System 3 7

8 What Initiate does. Initiate s EMPI accurately Finds Links Indexes Maintains Provides secure access to patient and healthcare provider records within and across sources Provides the foundation for electronic health records Initiate enables quality of care and collaborative initiatives among local, regional and national healthcare organisations Without forcing you to do lots of programming, Initiate s EMPI moves large quantities of data, standardise database management systems or manages patient/provider identifiers Initiate provider a single solution for: Patient Healthcare Provider Service Location identification 8

9 NEHTA Health Identifiers & the Client Registry: Not Mutually Exclusive National Patient Identifier Requires launch by government agency or organisation Backporting to existing records expensive and perhaps impossible May heighten consumer privacy & confidentiality concerns One (of many) data elements for patient ID Not silver bullet-- will have data quality errors just like existing data Compatible with EMPI technology to manage evolving strategy Client Registry/Federated Views national identifier as just another piece of data to facilitate patient matching Manages current environment with no identifier as well as potential future identifier Data maintained within firewalls of source system Readily deployed in short timeframe with standards, retrospective or prospective Requires EMPI technology 9 National Patient Identifier and Client Registry/Federated approaches are Complimentary and help advance patient matching, interoperability and EHR initiatives...in a collaborative, timely manner

10 Challenges facing the HI Adoption Every existing record at the jurisdiction, GP, community health level will have to be linked to a validated HI number and checked for incomplete data fields before jurisdictions, et al will accept it to be uploaded into their clinical systems Many records will be rejected as duplicates, untraceable or invalid Hospitals admit to 8-15% duplication it usually be higher and some have as many as 17 unique identifiers in use today The average time to resolve a duplicate record is approx 1 hour Existing technology at jurisdictions is many years old and lacks the algorithms, applications and performance to solve this problem. Robust search capability at point of service can and must provide <1% error rate in creating of duplicate records Today Medicare maintains a central index of 20 million+ plus Medicare number records for Australia Downstream - the number of records increases continually due to births, unknowns, errors, inability to find existing records, etc. The demand for use of the HI numbers will increase significantly What is the expected adoption rate for HI numbers? To support a true interoperable national health record jurisdictions will need to achieve near complete HI number coverage across their systems Approx 95% is required before jurisdiction data can be migrated to the national data network as a safe foundation for a national shared EHR (sehr) 10

11 Where does Initiate sit? Initiate s accuracy delivers superior matching, enabling higher auto-merge of records and reducing manual intervention Saves money Saves time (NHS clerical review estimated saving of up to 250 man years) Act as a staging platform for data to be transmitted to / or from the HI registry HI data stewards would thus deal only with the most difficult matches making best use of their specialist skills Initiate s accuracy would speed up migration of local data within the jurisdiction, and to / from the national HI service and Jurisdictional HI registries Update and verify patient demographics PMS Find HIs Exchange Information NEHTA Accurately matching records will result in: Higher levels of confidence amongst the public and clinicians, and the use in the Electronic Health Record / ICT projects 11

12 Interoperability that protects investment The design for the HI service must take into consideration the need to protect the investment in existing and new services This is NOT about replacing the existing Medicare Repositories Jurisdictions need to consider supplementing the HI Service with core EMPI functionality with a proven track record in healthcare The HI functionality must provide better match, search and index capability, together with a framework for managing issues such as data quality 12

13 CASE STUDY PROVINCE OF ONTARIO 13

14 Canada s Health Exchanges Province of BC Capital Health Authority Calgary Health Region Province of Alberta Province of Saskatchewan Province of Manitoba NORRad Province of New Brunswick Province of Newfoundland EHealth Ontario Province of Nova Scotia LEGEND: Health Exchanges 14

15 Case Study: Province of Ontario Hospitals: 100+ Physicians: 20K Records: 49M 62 data sources 250K Transactions/day Moving to SOA, web services, and HL7 integration Reducing wait times for key diagnoses and procedures key driver to EMPI initiative Accurate patient ID and linking of data required in order to support defining available medical personnel for key clinical conditions and procedures Within months benefits were being seen 81 hospitals, and over 1,700 surgeons are using the WTIS daily to help over 250,000 patients Clinician and clinic managers no longer working in the dark.. Fourteen months ago we had no idea about how long patients were waiting for cancer surgery in the province Multi-phased, quick deployment Phase One: Six (6) sources in 2 months, March 2006 Phase Two: 49 sources in 6 months, October 2006 Phase Three: 17 sources, June 2007

16 CASE STUDY ACT HEALTH 16

17 ACT Health Early Adopter Project: Some of the challenges Consent Issues Patient Registration Staff issues Record consent in Index Verified HI Could contain duplicates Unverified HI When a match is not found but sufficient demographics are available Potential to generate duplicates if search is not exhaustive...or too specific (address) Provisional HI May need to be resolved/linked to verified ID at a later stage

18 Use as a Primary or Supplementary Identifier? Diagram source: NEHTA As a Primary Identifier Means full adoption of the IHI across the environment Has system impacts for all systems As a Supplementary Identifier Reduces the impact on existing systems Would be implemented as a cross reference within the PMI Registry

19 Identification problem in perspective for NEHTA HI Medicare CDMS currently has 26 million records 20M active (6 million deceased/inactive) Largest State: NSW - Population million Records in NSW Public Hospital PMIs: ~ 22 million Average number of applications per Public Hospital with PMI data: 8 + EG. patient administration, pharmacy, radiology, pathology, emergency, operating theatres, diet management, UPI Total health records: > 176 million Australia s population million Extrapolation 526+ million public health records in Australia What is the transition strategy for linking existing healthcare records with NEHTA s new HI and HPI? How long will it take to adopt the HI? Can we wait 10+years? What are the rip and replace and/or modification costs 19

20 Something to think about.. On a business trip, you wake up with strange, painful symptoms in the middle of the night. You take a taxi to the hospital emergency room where doctors try to help you. They need to know your medical history. And you don t know, or can t remember, or never knew the details. Although your airline ticket confirmation number, your rental car record, and even your mobile phone bills and calling history are available 24/7 on-line, your medical records are locked away in filing cabinets somewhere, partially hand-written and partially typed, stored in paper folders, and stacked alphabetically. At four in the morning, that person with the key to your medical information is fast asleep and, in this case, a thousand miles away. How would you reach him or her? Would you call your doctor s answering service and hope someone will go down to the office? Perhaps it can wait until morning but wouldn t it be better for the doctor treating you to have that information now? Meanwhile, that emergency room doctor is asking you to remember as much of your history as you can while your stomach is in a knot or your head pounds or the pain in your chest begins to creep into your jaw and down your arm.

21 Final Thoughts NEHTA is one piece of a larger health identification puzzle NEHTA HI s should be one component in identifying patients within current systems National Initiatives require local or regional support Improving local data quality will greatly assist national information sharing Replacing local or regional systems wholesale is unnecessary, risky and may not improve quality by itself Data quality initiatives must take into account front-end staff in order to achieve the best possible outcome Anything that makes data entry at the front-line more difficult must be carefully considered 21