Efficient Remediation of Terms Inactivated by Dictionary Updates

Slides:



Advertisements
Similar presentations
Design and Implementation of a Web-Based Patient Portal Linked to an Ambulatory Care Electronic Health Record: Patient Gateway for Diabetes Collaborative.
Advertisements

Dedicated to Hope, Healing and Recovery 0 Dec 2009 Interim/Proposed Rules Meaningful Use, Quality Reporting & Interoperability Standards January 10, 2010.
Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 1 Medical.
ICD-10 Diagnosis Coding In use by majority of developed nations for years Goes into effect in 12 months (Oct. 1, 2014) Will require considerable adjustment.
ELTSS Alignment to Nationwide Interoperability Roadmap DRAFT: For Stakeholder Consideration in response to public comment.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
Rules, page 1 CSI 4106, Winter 2005 Representing knowledge with rules Points Definitions Production systems Conflict resolution strategies Examples A financial.
Introduction ICD-10-CM Overview Presented By Erline Franks CCS-P.
Strategic Planning Review and Setup RXM Expunge PRIORITY EVENT 257/327.
The sustainable transformation of health care systems requires New level of quality in the cooperation of all players in the healthcare system Significant.
Amy Sheide Clinical Informaticist 3M Health Information Systems USA Achieving Data Standardization in Health Information Exchange and Quality Measurement.
Proposed Meaningful Use Criteria for Stage 2 and 3 John D. Halamka.
The Role of Information Technology For A Private Medical Practice Noel Chua Rosalinda Raymundo.
Health Information Professionals Week March 22nd-28th, 2015 This week is an opportunity to showcase the thousands of certified HIM® professionals who.
Lifelines2: Hypothesis Generation in Multiple EHRs Taowei David Wang Catherine Plaisant Ben Shneiderman Shawn Murphy Mark Smith Human-Computer Interaction.
Decision Support for Quality Improvement
ICD-10 Staff Awareness. WHAT IS THIS COURSE? This course is designed to provide a basic awareness and understanding of ICD-10 and why it is so critical.
Why Use MONAHRQ for Health Care Reporting? May 2014 Note: This is one of seven slide sets outlining MONAHRQ and its value, available at
© 2015 TriZetto Corporation ICD-10: Ready, Set, Go! August 27, 2015.
1 Visioning the 21 st Century Health System Kenneth I. Shine, MD National Health Information Infrastructure 2003: Developing a National Action Agenda for.
National Efforts for Clinical Decision Support (CDS) Erik Pupo Deloitte Consulting.
Preventive Ethics Beyond the Basics. Module 2 Prioritizing Among Ethics Issues.
Why Use MONAHRQ for Health Care Reporting? March 2015 Note: This is one of eight slide sets outlining MONAHRQ and its value, available at
Julie M. Green, MS, DVM Veterinary Medical Informatics VMRCVM – Virginia Tech Veterinary Medical Informatics – Va-Md Regional College of Veterinary Medicine.
Correlating Knowledge Using NLP: Relationships between the concepts of blood cancers, stem cell transplantation, and biomarkers Katy Zou and Weizhong Zhu.
Panel: Problems with Existing EHR Paradigms and How Ontology Can Solve Them Roberto A. Rocha, MD, PhD, FACMI Sr. Corporate Manager Clinical Knowledge Management.
CHAPTER 28 Translation of Evidence into Nursing Practice: Evidence, Clinical practice guidelines and Automated Implementation Tools.
On-Time Prevention Program for Long Term Care: Clinical Decision Support On-Time Prevention Program for Long Term Care: Clinical Decision Support William.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
School of Health Sciences Week 8! AHIMA Practice Briefs Healthcare Delivery & Information Management HI 125 Instructor: Alisa Hayes, MSA, RHIA, CCRC.
Query Health Concept-to-Codes (C2C) SWG Meeting #11 February 28,
BlueCross BlueShield of Western New York BlueShield of Northeastern New York ICD-10: Coding to the Highest Specificity November 17, 2015.
Evolving Competencies of Healthcare Professionals in Long Term Care Westminster Ingleside Dusanka Delovska-Trajkova, CIO 1.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
HIT Standards Committee Clinical Operations Workgroup Report on Gaps and Next Steps Jamie Ferguson Kaiser Permanente John Halamka Harvard Medical School.
Innovators Panel Designing solutions to support decision making across the spectrum of health Randall S. Moore, MD, MBA, CEO.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Public Health Reporting Initiative July 25, 2012.
ICD-10 Operational and Revenue Cycle Impacts Wendy Haas, MBA, RN Dell Services Healthcare Consulting.
Methods We employ the UMLS Metathesaurus to annotate ICD-9 codes to MedDRA preferred terms (PTs) using the three-step process below. The mapping was applied.
Uses of the NIH Collaboratory Distributed Research Network Jeffrey Brown, PhD for the DRN Team Harvard Pilgrim Health Care Institute and Harvard Medical.
Achieving automated health data linkages for learning healthcare systems: Lessons learned Allison Devlin, MS Program Director, Comparative Effectiveness.
Finding Answers Online Comprehensiveness and accuracy in online information about breast cancer Kim Walsh-Childers, PhD Heather M. Edwards, MA University.
All Recurring Key Themes The below list includes themes across many of the different presentations to date. The next 2 slides address how these may be.
Clinical Decision Support Implementation Victoria Ferguson, COO - Program Manager Christopher Taylor, CIO – Business Owner Monica Kaileh, CMIO – Steering.
ICD-10 Lessons Learned from Canada. Background of ICD-10 in Canada 1995 – Agreement reached between World Health Organization (WHO) and Canada to adopt.
3M Health Information Systems 1© 3M All Rights Reserved. 3M Health Information Systems Data Standardization Interoperability.
Burden of Disease Research Unit (BOD) Towards a National Procedure Coding Standard for South Africa Lyn Hanmer Health Informatics R&D Co-ordination (HIRD)
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
Clinical Terminology and One Touch Coding for EPIC or Other EHR
Fragmented Services: 7+ Average number of health related vendors employees need to interact with. Lack Engagement: 57% of large employers say that a lack.
Use of translationCode and Combination Code Proposal
Combination Codes Discussion.
NeurOn: Modeling Ontology for Neurosurgery
Sales Proposal for Prospect
1st International Online BioMedical Conference (IOBMC 2015)
CERNER MILLENNIUM Diagnoses and Problems
Federal Health IT Ontology Project (HITOP) Group
Unit 5 Systems Integration and Interoperability
HI 5354 – Cognitive Engineering
LOCAL EXPERIENCES Innovation practices and experiences related to FIC development and implementation Ariadna Rius Clinical Dictionary for iSalut.
Controlled Vocabularies for Capturing Clinical Encounters
The Role of Health Institute Kingdom of Bahrain
Electronic Health Record Update
Health Information Exchange Interoperability
Provider and Member Education in Managed Care Pharmacy
CERNER MILLENNIUM Diagnoses and Problems
Customized Medical Accounting software. Objectives Medical accounting software is used to make a record and process accounting transaction includes purchase,
Component 11 Unit 7: Building Order Sets
Presentation transcript:

Efficient Remediation of Terms Inactivated by Dictionary Updates AMIA Symposium – November 8, 2017 Benjamin J. Gross, MD, MMSc,1 David H. Dubois, MBA, PMP,2 Mark H. Twelves MSW, LICSW,2 Roberto A. Rocha, MD, PhD2,3,4 1InterSystems Corporation 2Clinical Informatics, Partners eCare, Partners Healthcare System 3Brigham and Women’s Hospital 4Harvard Medical School, Boston, MA

Abstract Ongoing maintenance of a diagnosis dictionary in an electronic health record includes replacing inactivated terms with clinically equivalent terms in configuration and data records Partners Healthcare has developed an efficient process that relies on Detailed reports to suggest active replacement terms Clinical review by subject matter experts Replacements which are made manually or with the help of system tools Learning Objectives: Recognize dependencies of terms inactivated by dictionary updates Formulate an approach towards remediation

Background Partners Healthcare System (PHS) 800,000+ clinical terms Commercial EHR Third party diagnosis dictionary 800,000+ clinical terms Mapped to ICD-10-CM codes, SNOMED CT concepts Hundreds of terms inactivated with each periodic update + PHS customization

Implications of inactivating terms Providers can usually find desired terms despite inactivations thanks to significant redundancy After >2 years, 7% of terms accounted for 99% of usage However, certain inactivated terms must be replaced with active terms: Terms with “configuration dependencies” – linked to other system elements Terms with “process dependencies” – appear in patients’ records and can be used downstream

Diagnosis terms with dependencies Configuration dependencies Examples: questions on a form, triggers for decision support Inactive terms cause runtime errors and functionality gaps Terms must be replaced in advance Process dependencies Examples: patient’s problems, future orders Inactive terms hinder workflows, especially billing Providers may make replacements themselves EHR system offers alternative terms when available Replacing terms in advance reduces workflow interruptions and saves providers time

Finding appropriate replacement terms Mapping requires clinical expertise and each replacement requires approval To improve efficiency, PHS developed reports to suggest multiple options for each inactivated term Number of suggested terms for each inactive term (recent update) Suggestions ranked by likelihood of semantic equivalence Terminology engineers select a single optimal replacement term Clinical subject matter experts review proposed replacements Report type Median Mean Configuration dependencies 17 36 Process dependencies 20 41

Suggestion reports Criteria for suggesting alternative terms Rank 1 Previously approved mapping 2 Suggested by the dictionary vendor 3 Textual match + SNOMED CT concepts + ICD-10-CM codes 4 Textual match + SNOMED CT concepts only 5 Textual match + ICD-10-CM codes only 6 Textual match only (similarity function) 7 Textual match only 8 Matching SNOMED CT concepts + ICD-10-CM codes only 9 Matching SNOMED CT concepts only 10 Matching ICD-10-CM codes only

Configuration dependency – Protocol Chemical conjunctivitis ICD-10-CM: Configuration dependency – Protocol Chemical conjunctivitis ICD-10-CM: H10.219 Acute toxic conjunctivitis, unspecified eye SNOMED CT: 415733008 Toxic conjunctivitis (disorder) Term name ICD-10-CM SNOMED CT Matching criteria ACUTE CHEMICAL CONJUNCTIVITIS H10.219 415733008 SNO + ICD ACUTE CHEMICAL CONJUNCTIVITIS, UNSPECIFIED LATERALITY CHEMICAL CONJUNCTIVITIS, BILATERAL H10.213 SNO CHEMICAL CONJUNCTIVITIS, RIGHT H10.211 CHEMICAL CONJUNCTIVITIS, LEFT H10.212 TOXIC CONJUNCTIVITIS, LEFT TOXIC CONJUNCTIVITIS, RIGHT TOXIC CONJUNCTIVITIS, BILATERAL DRUG-INDUCED TOXIC CONJUNCTIVITIS 415734002 ICD DRUG-INDUCED TOXIC CONJUNCTIVITIS, UNSPECIFIED LATERALITY

Configuration dependency – Preference list High myopia, bilateral ICD-10-CM: H52.13 Myopia, bilateral SNOMED CT: 34187009 Severe myopia (disorder) Term name ICD-10-CM SNOMED CT Matching criteria SEVERE MYOPIA OF BOTH EYES H52.13 s34187009 Suggested by vendor SEVERE MYOPIA, UNSPECIFIED LATERALITY H52.10 SNO HIGH MYOPIA SEVERE MYOPIA … [2 more] … MYOPIA OF BOTH EYES s57190000 ICD CONGENITAL AXIAL MYOPIA OF BOTH EYES s232134006 SIMPLE MYOPIA s232133000 MYOPIC RETINOPATHY OF BOTH EYES s29555009

Process dependency – Future order Dry eye syndrome, bilateral ICD-10-CM: H04.123 Dry eye syndrome of bilateral lacrimal glands SNOMED CT: 346221000119103 Tear film insufficiency of bilateral eyes (disorder) 46152009 Tear film insufficiency (disorder) Term name ICD-10-CM SNOMED CT Matching criteria INSUFFICIENCY OF TEAR FILM OF BOTH EYES H04.123 346221000119103 46152009 Suggested by vendor BILATERAL DRY EYES 162290004 Textual match + ICD DRY EYES ICD DRY EYE SYNDROME OF BILATERAL LACRIMAL GLANDS INSUFFICIENCY OF BOTH LACRIMAL SACS 231840003 CHRONIC DRYNESS OF BOTH EYES 302896008 DRYNESS OF BOTH EYES DUE TO DECREASED TEAR PRODUCTION 302896008 46152009

Textual match + SNO + ICD Process dependency – Future order Hepatic cirrhosis, unspecified hepatic cirrhosis type ICD-10-CM: K74.60 Unspecified cirrhosis of liver SNOMED CT: 19943007 Cirrhosis of liver (disorder) Term name ICD-10-CM SNOMED CT Matching criteria HEPATIC CIRRHOSIS K74.60 s19943007 Suggested by vendor CIRRHOSIS OF LIVER Textual match + SNO + ICD OTHER CIRRHOSIS OF LIVER K74.69 Textual match + SNO CIRRHOSIS SNO + ICD CIRRHOSIS OF LIVER WITHOUT ASCITES … [2 more] … CONGENITAL CIRRHOSIS P78.81 SNO NON-ALCOHOLIC CIRRHOSIS s266468003 ICD … [5 more]

Results of recent updates Jun 2017 Oct 2017 Inactive terms queued for replacement 847 778 Replacement terms identified 743 (88%) 658 (85%) Elements impacted by replacements: When replacements were not made Configuration dependencies 402 662 Configuration dependencies were otherwise changed or removed Process dependencies Future orders 163,279 107,903 Terms associated with < 50 orders were left to providers Problem lists 23,749 41,940 Terms associated with < 50 problems were left to providers Active treatment protocols 682 339 All inactive terms were replaced Total elements impacted 188,112 150,844

Effort required Initial report design and development 1 x Clinical Informatician (report design) 1 x Software Engineer (report development) Single dictionary update (x4/year): Approximately 75 hours 12-13 people with complementary roles and expertise 1 x Terminology Team Lead (project management) 1 x Clinical Informatician (project management) 1 x Software Engineer (report delivery) 2-3 x Terminology Engineers (selection of optimal replacement terms) 6 x Clinical Subject Matter Experts (review of proposed replacements) 1 x Application Coordinator (implementation)

Summary This is the PHS approach for replacing terms inactivated by periodic updates of the diagnosis dictionary Terms with “configuration dependencies” – to avoid runtime errors and functionality gaps Terms with “process dependencies” – to reduce workflow interruptions and save providers time

Conclusions Just one example of overall effort to maintain system configuration and data integrity Costs and expertise required may be the “Achilles heel” of complex EHR systems EHR vendor offers few tools for knowledge management Data integrity is only one consideration of content vendors. Others include term availability, term “friendliness”, matching multiple terminologies simultaneously Responsibilities split between EHR vendor (search) and content vendor (content), and available solutions are limited to single domains (diagnoses, meds, procedures) PHS has large quantities of configured content and patient data to consider PHS has dedicated resources for knowledge management and necessary expertise. Not available at every institution

Thank you Ben Gross, MD, MMSc grossdoc@gmail.com