Medication Reconciliation University of Minnesota N5115 Spring 2009 Group 2 Jolene Dickerman, Denise Frederick, Tom Lewison, Chris Pensinger, Sue Strohschein, Andrea Szkarlat University of Minnesota NURS 5115 April 17 th, 2009

Questions Addressed  Questions 1 & 3 Denise Frederick  Question 2 Susan Strohschein  Questions 4 & 10 Andrea Szkarlat  Questions 5 & 11 Jolene Dickerman  Questions 6 & 7 Chris Pensinger  Questions 8 & 9 Thomas Lewison University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

1. Minnesota eHealth Initiative and 2015 Mandates University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation  “ By January 1, 2015, all hospitals and health care providers must have in place an interoperable electronic health records system within their hospital system or clinical practice setting. “  Synchronizing patient data  E-prescribing  Lab result management  Timely clinical decision support

2. Medication Reconciliation: an Identified Gap in Care Start Dschg Ordered HUC Prints Med List Printed from EHR Charge RN Reviews Pharmacy Processes Floor RN Patient Preferred Pharmacy End University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

Medication Reconciliation Reality Start Dschg Ordered HUC Prints Med List Printed from EHR Charge RN Reviews Pharmacy Processes Floor RN Patient Preferred Pharmacy End Charge RN Writes the Final Med List onto the Discharge Note University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

3. Proposed Use Case and Objectives  The use case we chose is Medication Reconciliation at the point of discharge from an inpatient facility to self-care at home.  Current process involves many steps and people  Due to number of steps, increased chance of error  Time consuming, which equals more resources and this means more cost  Medication list is a paper copy, no electronic version available University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

Use Case Objectives cont.  Promote accurate medication reconciliation at time of discharge through an EHR  Improve patient safety  Increase patient knowledge and understanding of prescribed medications  Create interoperability  Maintain focus on the needs of the patient regarding medication reconciliation

4. Relationship of Use Case to eHealth Initiative  Improve patient safety Reduction of medication errors  Increase quality and efficiency Fewer paper copies “Flags” to notify providers  Interoperability Continuity of care “Smart card” proposal  Potential to aid in transition to e-prescribing University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

5. Benefits of Use Case to Specific Stakeholders  Patient and Family  Providers (Hospital and Primary Care)  Nursing  Pharmacy  Community Care Agencies  Clinics/Hospitals  Insurance Companies  State and National Regulatory Agencies University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation  Decrease in lost paper records  Reduction in errors  Improved efficiency  Expedites the discharge process  Clinical decision support assistance  Increased productivity  Electronic medication list for patients 6. Expected improvements in medication reconciliation workflow :

University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation NursingPhysiciansPharmacy Information Technology Patients Ancillary services Outpatient clinics 7. Necessary communication links:

8. Functional Requirements Needed  Administration (demographics and financial)  Clinical Documentation  Data Export  Data Import  ePrescribing  Orders Management  Privacy Protection and Security University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

9. Relevant Data, Vocabulary, and Technical Standards  SNOMED-CT has 311,000 active concepts  SNOMED-CT is a registered standard with HL7  Most comprehensive clinical vocabulary available.  Can cross-map to other international standards  Already used in more than fifty countries  See following vocabulary example: University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation Demographic Data Elements Local Term From Use Case Definition ContentVocabulary TermCodeStandardized Vocabulary Unique Patient IdentifierCode specific to patient identification Medical Record Number SNOMED-CT Last NameLegal NamePatient Identification SNOMED-CT First NameLegal NamePatient Identification SNOMED-CT Middle InitialLegal NamePatient Identification SNOMED-CT Street AddressPhysical AddressEnvironment SNOMED-CT CityCity which patient residesEnvironment SNOMED-CT StateState which patient resides Environment SNOMED-CT Zip codeZip code of patient’s residence EnvironmentSNOMED-CT 10 Digit Phone NumberContact numberPhone number SNOMED-CT Date of birthMM-DD-YYYYBirth date SNOMED-CT Primary Care ProviderHealth Care ProfessionalMedical Practitioner SNOMED-CT Preferred PharmacyPharmacy of ChoicePharmacy Facility SNOMED-CT Primary ClinicClinic of health careHealth Care Related Organization SNOMED-CT

University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation Medication Data Elements Local Term From Use Case Definition ContentVocabulary TermCodeStandardized Vocabulary Unique Patient IdentifierCode specific to patient identification Medical Record Number SNOMED-CT AllergiesPatient’s drug allergiesHypersensitivity SNOMED-CT Medication NamePrescribed medication on discharge Pharmaceutical Preparations SNOMED-CT Medication DoseAmount of medicationQuantitative Concept SNOMED-CT Medication RoutePO, SQ, IV, IM, topicalDrug Administration Routes SNOMED-CT Medication FrequencyTimes to take medications Frequencies (time pattern) SNOMED-CT Start DateWhen to begin medication Date SNOMED-CT End DateWhen to stop medicationDate SNOMED-CT Final Discharge Medication List Therapeutic or Preventive Procedure Medication Reconciliation C SNOMED-CT

University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation Discharge Data Elements Local Term From Use Case Definition ContentVocabulary TermCodeStandardized Vocabulary Final discharge medication list List generated from final reconciliation process Discharge Planning (procedure) A /SNOMED Clinical Terms/FN/ SNOMED CT

10. Proposed System Life Cycle  Initiation/Concept Development  Identified a need for improving medication reconciliation  Design  Using EHR exclusively to manage discharge meds  Smart card  Development  Research vendors to support needs (ie. Eclipsys)  Implementation  Maintenance Maryland Department of Information Technology (2008) University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

11. Proposal’s Desirability, Usability, and Feasibility  Desirability  Increased Provider efficiency and Patient safety  Usability  Patient and Provider friendly system  Feasibility  Collaboration between multiple health systems  Timeframe to achieve interoperability  Financial and Regulatory requirements University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation

References A Prescription for Meeting Minnesota’s 2015 Interoperable Electronic Health Record Mandate. A Statewide Implementation Plan. (June 2008) Retrieved April 10, 2009 from: Barnsteiner J. Chapter 38: Medication reconciliation in Hughes RG (ed.) Patient safety and quality: An evidence-based handbook for nurses. Volume 2 (Prepared with support from the Robert Wood Johnson Foundation.) AHRQ Publication No Rockville, MD: Agency for Healthcare Research and Quality; April 2008; p International Health Terminology Standards Development Organization. (2009). About SNOMED- CT. Retrieved April 12, 2009 from: Maryland Department of Information Technology: System Development Life Cycle (SDLC), Volume 1. (2008). Retrieved April 14, 2009 from: NYEHealth Collaborative. (2008). The Statewide Collaboration Project. EHR Functional Requirements. Retrieved April 12, 2009 from: University of Minnesota NURS 5115 April 17 th, 2009 Group Two Use Case: Medication Reconciliation