Julie M. Green, DVM, MS Veterinary Terminology Services Laboratory

Slides:



Advertisements
Similar presentations
Managing Users. Overview for School Admin Users Define Users Users Module Add Users Importing Users and Groups Manually adding users Search for Users.
Advertisements

Altman IM Ltd | | capture | index | organise | workflow Enterprise document & content management … for all types & size.
CareCentrix Direct Training.
Implementing a Clinical Terminology David Crook Subset Development Project Manager SNOMED in Structured electronic Records Programme NHS Connecting for.
Health Informatics Series
1.02 ANALYZE METHODS TO CORRECTLY MAINTAIN VETERINARY MEDICAL RECORDS VETERINARY MEDICAL RECORDS.
1 Definitions Value set: A list of specific values, which may – or may not – contain subsets of one or more standard vocabularies, that define or identify:
Managing SNOMED in your system. 2 nd AAHA Software Vendors Summit – April 21, 2009.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
Unit 18: Database Modelling
Veterinary Terminology Services Lab Va-Md Regional College of Veterinary Medicine The Animal Names Terminology Subset of SNOMED CT ® Suzanne L. Santamaria,
Karen Gibson.  Significant investment in eHealth is underway  Clinical records: ◦ Not only a record for the author ◦ Essential to inform the next person.
SNOMED for Clinical Records: Tools to facilitate implementation. Jeff R. Wilcke, DVM, MS, DACVCP AVMA Liaison to the SNOMED Editorial Board.
Electronic Serials Invoicing with Innovative Presenter: Kathy Peters Accounts Payable, Acquisitions University of Missouri.
Working Together to Advance Terminology Tooling Presentation to OHT Board, Birmingham Jennifer Zelmer & Karen Gibson.
SNOMED CT Afzal Chaudhry Renal Association Terminology Committee
Julie M. Green, MS, DVM Veterinary Medical Informatics VMRCVM – Virginia Tech Veterinary Medical Informatics – Va-Md Regional College of Veterinary Medicine.
Database What is a database? A database is a collection of information that is typically organized so that it can easily be storing, managing and retrieving.
Building Marketing Databases. In-House or Outside Bureau? Outside Bureau: Outside agency that specializes in designing and developing customized databases.
HIT Standards Committee Vocabulary Task Force Task Force Report and Recommendation Jamie Ferguson Kaiser Permanente Betsy Humphreys National Library of.
VTSL Enhancing the AAHA & AAEP Diagnostic Subsets 2013 Talbot Symposium Jeff R. Wilcke DVM, MS, DACVCP; Julie M. Green DVM, MS; Suzanne L. Santamaria DVM,
Flat Files Relational Databases
HITPC Meaningful Use Stage 3 RFC Comments July 22, 2013 Information Exchange Workgroup Micky Tripathi.
Veterinary Adaptation of SNOMED-CT ® We don’t have to eat the whole elephant!
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
Concepts & the Concept Dictionary Regional East African Centre for Health Informatics (REACH-INFORMATICS) Lauren Stanisic July 2012 REACH-INFORMATICS,
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Wildfire Costing (WFCST) for Recorders A component of Wildfire One Fire Season 2016.
Bartek Doruch, Managing Partner, Kamil Karbowiak, Managing Partner, Using Power BI in a Corporate.
VAdata Tools VAdata: Virginia’s Sexual and Domestic Violence Data Collection System.
Data quality & VALIDATION
Human Computer Interaction Lecture 21 User Support
SNOMED Core Structures RF2
Presented by: Ambulatory Education and Systems
Functional EHR Systems
Lesson 10 Databases.
Chapter 1 Introduction.
Electronic Medical and Dental Record Integration Options
Database Management.
Making your good ideas count!
Human Computer Interaction Lecture 21,22 User Support
NeurOn: Modeling Ontology for Neurosurgery
Clean Harbors Online Services – CS1045
Test Around the Clock Testing Revolutionized
Data Quality Webinar for General Practice
Holdings – vital to library success
22-INTEGRATION HUB
Parts.cat.com Client training 2016.
CERNER MILLENNIUM Diagnoses and Problems
6th Annual PHIN Conference August 25-28, 2008
ConnectingOntario ClinicalViewer
Efficient Remediation of Terms Inactivated by Dictionary Updates
Fast Action Links extension A love letter to CiviCRM
Records Management & ARIMS
Making your good ideas count!
Markle Site Map + Wireframes.
New Functionality in ARIN Online
Data Quality By Suparna Kansakar.
Functional EHR Systems
ARCH-1: Application Architecture made Simple
ONE® Mail Training Presentation
Two methods to observe tutorial
Unemployment Insurance Agency Michigan Web Account Manager
PubMed.
Data Warehousing Concepts
Ensuring the Quality and Best Use of Information
NextGen Payroll Demo Resource 2018
Discrepancy Management
Ready, Set, Goal! The Key to Practice Success
OBSERVER DATA MANAGEMENT PRINCIPLES AND BEST PRACTICE (Agenda Item 4)
Presentation transcript:

Julie M. Green, DVM, MS Veterinary Terminology Services Laboratory Your Master Problem List Working FOR you or AGAINST you? Julie M. Green, DVM, MS Veterinary Terminology Services Laboratory Look at structured recording of our Master Problem list….. How must of us are doing and How doing it well can facilitate benefits, not just for ourselves and our practices, but all of veterinary medicine. Look at common problems with the lists in medical record systems today, and why moving towards the use of an external standard such as the AAHA Prob and Diagnosis Terms is the right thing to do. August 28, 2016

“The Master Problem List” The Diagnosis List Differential Diagnosis List “Things that are Wrong with our Patients”

What are you goals? Capture Data Retrieve My Own Cases Share Records Pool Data

Pet Health Communication Productivity Entertainment Banking Travel Cell phones and electronic devices organize our lives…carry all important data with us… Clients are beginning to expect their pets’ data to be electronically portable… Reality: Vet EMRs are not capable of truly portable data Some services mine EMRs (Pattersons’ eHealth) and make patient data viewable online for owners, but this data is not transferrable to other clinics or systems. Education Shopping Our Health Pet Health

Truly Portable Data Messaging Standards Terminology Standards Shared Data Model Truly Portable Data requires: Means: My data “fits” into your EMR... If I’ve coded diagnoses for a transferred patient, it comes up in searches within YOUR EMR for that patient (can’t do this with a pdf of a case summary) Won’t go into the technical details, but Truly Portable Electronic data requires Share Data model, Terminology Standards and Messaging standards Emailing a pdf of a patient summary is NOT portable data. You can store and read the file, but you can’t import the individual pieces of data (diagnoses, lab values, weights, etc) into your own system.

Truly Portable Data Slightly less complex than data modeling Messaging Standards Terminology Standards Slightly less complex than data modeling Nice, logical first step Shared Data Model

A Place to Start…. The Master Problem List The Master Problem list serves as an important part of nearly all medical records giving a quick historical view of the patient’s medical history.

Standardization – The Local List Everyone uses the same list Any EMR will have this level of standardization Benefits (vs free text recording): Internal consistency Prevent common spelling errors Promotes consistent & reliable retrieval Problems: Incomplete Users will “change” the list, introducing inconsistency, misspellings, duplication PROS: Internal consistency – problems in the problem list….not owner notes, demo info, procedures performed Spelling…. How many ways can we spell diarrhea? Retrieval: with standardization this list of possibilities is already present…cardiac failure vs heart failure, kidney vs renal,.... To retrieval all in free text storage, you have to first think of all the possibilities….. CONS:

Standardization - The Local List User – introduced problem #1: Duplication Veterinarian with cardiologist interest diagnoses: Arrhythmogenic right ventricular cardiomyopathy Doesn’t find it in local list: Adds it manually Another veterinarian diagnoses: Boxer cardiomyopathy Doesn’t find it in the local list….(forgets the more technically correct term): Adds it manually Now we have 2 codes for the same disorder Search for 1 misses the cases recorded with the other – INCOMPLETE RETRIEVAL Veterinarians and technicians don’t have the time or training to be “in house terminologists”

Standardization - The Local List User – introduced problem #2: Ambiguity Overworked veterinarian sees a congested kitten Searches for “congestion” & doesn’t find it quickly in local list: manually adds “Congestion” Another busy veterinarian sees a dog with pulmonary congestion Searches for “congestion” & finds the one added above…records it in his record. Now we have 1 code used for two different disorders Search for “Congestion” returns a mixture of cases – LOSS OF DATA ACCURACY Veterinarians and technicians don’t have the time or training to be “in house terminologists” Other examples: locations like “Fundus” (stomach or eye), “knee” (horse carpus or dog stifle)

Standardization - The Local List User – introduced problem #3: Inconsistency Mixture of “types” of codes get added: Procedures performed (spay, pedicure, AG) Notes on animal disposition (caution, will bite) NOT “Master Problems” – belong elsewhere Veterinarians and technicians don’t have the time or training to be “in house terminologists” Other examples: locations like “Fundus” (stomach or eye), “knee” (horse carpus or dog stifle)

Standardization – The Controlled List Managed using good principles of terminologies Maintain consistency Prevent misspellings Avoid duplication & ambiguity Benefits: Internal consistency Prevent common spelling errors Promotes consistent & reliable retrieval Can’t be “dismantled” by users accidentally Problems: Requires trained personnel NOTE: Software must be “locked down” to prevent user changes

Standardization – The Controlled List LOCALLY Controlled Total control over wording No reliance on External entity Requires on-staff expertise Codes will NOT transfer to other systems VS EXTERNALLY Controlled Codes are TRULY PORTABLE Highly trained external terminology expertise Rely on External entity (submit requests!) System needs capability of updating (vendor dependent) Costs of maintenance

Truly Portable Data = External Standard Recommended Standard (in US) SNOMED CT International (VetSCT) Adopted by US Public Health U.S. Meaningful Use Guidelines Only terminology standard that will keep Vet Med compatible with Public Health (and human medicine) Additional benefits: Logical structure for advanced querying Broad network of terminology experts developing and maintaining – high quality terminology

Truly Portable Data = External Standard For Small Animal General Practice Problem & Diagnosis Terms (PDT Subset) Sponsored by AAHA Subset of concepts & descriptions from SNOMED & VetSCT Designed for recording problems or diagnoses Scope does NOT cover: Specialty practice Species other than cats & dogs Feedback so far is positive on coverage, though we expect expansion as more practices use it.

Truly Portable Data = External Standard For Equine General Practice Problem & Diagnosis Terms (PDT Subset) Initially Sponsored by AAEP Subset of concepts & descriptions from SNOMED & VetSCT Designed for recording problems or diagnoses Scope does NOT cover: Specialty practice Species other than horses Being used at EMC (VaMdCVM)

AAHA Prob & Diag Terms First Step …. Get the Terms in your system Remove/inactivate current list Add Prob & Diag Terms If you’re lucky this is a simple request to your vendor (Cornerstone, Agile/cloud based systems, others??) PIMS Problem List Prob & Diag Terms

AAHA Prob & Diag Terms Use Limited by what Current Systems can do Limitation #1: store only 1 term per identifier PDT Subset provides multiple terms for each concept Current systems force a single visible term Most use the “Preferred” term chosen by the PDT Editorial Board (specified in the files) We all have our own preferences…. (Boxer Cardiomyopathy v Arrhymogenic …) Example: Concept ID: 281170005 Preferred Term: Boxer cardiomyopathy Acceptable Term(s): Arrhythmogenic right ventricular cardiomyopathy

AAHA Prob & Diag Terms Use Limited by what Current Systems can do Limitation #2: size of identifier is limited SNOMED Identifiers are 64-bit integers Ex: Cornerstone altered the identifiers to fit their field Example: Concept ID: 334421000009101 Preferred Term: Feline leukemia virus infection Cornerstone ID: 33442-101

AAHA Prob & Diag Terms Use Limited by what Current Systems can do Limitation #3: update capability remains to be seen PDT Subsets are updated twice a year PIMS systems updated ???

AAHA Prob & Diag Terms First Step …. Get the Terms in your system No Batch import options (that I’m aware of) Vendors may offer to load via support (Cornerstone) Manual entry is most common (one code at a time) Prob & Diag Terms

AAHA Prob & Diag Terms First Step …. Get the Terms in your system Actual First Step …. Consider Legacy Data

AAHA Prob & Diag Terms Legacy Data Data already stored in your system using your current EMR’s list.

AAHA Prob & Diag Terms Legacy Data Never recorded diagnosis/problems before? Whoo Hoo! You have no legacy data! Inactive existing codes….add PDT terms/codes…and you’re ready to go! Already been recording diagnosis/problems? Sorry…You have more work to do…

AAHA Prob & Diag Terms Legacy Data – the simple way Just inactivate old code & add new ones Cornerstone “migration” does this No connection between old and new

AAHA Prob & Diag Terms Legacy Data – the simple way

Compare Existing with PDT concepts AAHA Prob & Diag Terms Legacy Data – the better way Create a “mapping” Compares existing terminology to AAHA (or AAEP) PDT Best done by terminologist or someone trained Compare Existing with PDT concepts Match Found? Add to Mapping File yes no Inactivate Needed? no yes Submit Request

AAHA Prob & Diag Terms Legacy Data – the better way Create a “mapping” Compares existing terminology to AAHA (or AAEP) DT Best done by terminologist or someone trained Kidney Failure – Acute (18917) Match Found? Add to Mapping File yes Example Mapping File PIMS PDT Exact? 18917 (Kidney Failure – Acute) 14669001 (Acute Renal Failure) YES Inactivate

AAHA Prob & Diag Terms Legacy Data – the better way Create a “mapping” Compares existing terminology to AAHA (or AAEP) DT Best done by terminologist or someone trained Acute Renal Failure (1718) Match Found? Add to Mapping File yes Example Mapping File PIMS PDT Exact? 18917 (Kidney Failure – Acute) 14669001 (Acute Renal Failure) YES 1718 Inactivate

AAHA Prob & Diag Terms Legacy Data – the better way Create a “mapping” Add AAHA (or AAEP) PDT concepts Manual process Results will be combination of AAHA PDT and a few remaining existing terms, but no duplication

AAHA Prob & Diag Terms Legacy Data – the better way Create a “mapping” Add AAHA (or AAEP) DT concepts Review old cases for updating Labor intensive, but only way to ensure old cases are retrievable/encoded Use the mapping file If case is coded with a term that has a match, consider updating diagnosis/problem coding with new PDT concept

AAHA Prob & Diag Terms Biannual Updates April and October of each year Updates include New concepts to add to interface lists New synonyms for existing concepts Consider changing term in interface list if preferred Some concepts will be retired (replaced by new concepts) Inactivate in interface & consider reviewing records for update Vendor automated? Maybe? Hopefully????

Out-of-box…no work for me… Standardized data True data portability Out-of-box…no work for me… The perfect PIMS

Thank you! Contact Info: Julie M. Green, DVM, MS jmgreen@vt.edu http://vtsl.vetmed.vt.edu Questions?