2014 Edition Test Scenarios January 2013. Contents Purpose of Test Scenarios3 Completed Work4 Current Work5 Using a Narrative Test Case Scenario to Develop.

Slides:



Advertisements
Similar presentations
Meaningful Use and Health Information Exchange
Advertisements

Dedicated to Hope, Healing and Recovery 0 Dec 2009 Interim/Proposed Rules Meaningful Use, Quality Reporting & Interoperability Standards January 10, 2010.
September, 2005What IHE Delivers 1 Presenters: Keith W. Boone, John Donnelly, Larry McKnight, Dan Russler IHE Patient Care Coordination.
Exit a Customer Chapter 8. Exit a Customer 8-2 Objectives Perform exit summary process consisting of the following steps: Review service records Close.
IWDS – Extensive Training for Case Managers
0 - 0.
ADDING INTEGERS 1. POS. + POS. = POS. 2. NEG. + NEG. = NEG. 3. POS. + NEG. OR NEG. + POS. SUBTRACT TAKE SIGN OF BIGGER ABSOLUTE VALUE.
MULT. INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
Addition Facts
National Learning Consortium
R OAD M AP TO M EANINGFUL U SE. What is Meaningful Use in the Hospital?
Past Tense Probe. Past Tense Probe Past Tense Probe – Practice 1.
ARRA Meaningful Use Update Mount Auburn Hospital Information Systems Update March 2011.
Addition 1’s to 20.
Test B, 100 Subtraction Facts
Week 1.
Meaningful Use Basics.  Demographics  Active Medication List  Active Allergy List  Vitals  Smoking Status  Problem List  Computerized Physician/Provider.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
2014 Edition Release 2 EHR Certification Criteria Final Rule.
Implementation Workgroup: Current Activities and Next Steps.
Electronic Prescribing in BC: The Past, The Present, and The Future February 19, 2015 Quality Forum 2015 Sorin Pop, BC Ministry of Health 1.
2014 Certification Criteria associated with MU Menu Stage 2: 2014 Certification Criteria associated with MU Core Stage 2: 2014 Certification Criteria associated.
HITSC: Health Information Technology “Summer Camp” Doug Fridsma
Meaningful Use Stage 2 JoAnne Hawkins OIT Meaningful Use Team Lead Barcode Medication Administration Awareness Resource Patient Management System.
Medication Reconciliation
Meeting Stage 1 Meaningful Use Criterion Carlos A. Leyva, Esq. Digital Business Law Group, P.A.
GOVERNMENT EHR FUNDING: MEANINGFUL USE STAGE 2 UPDATE October 25, 2012 Jonathan Krasner Healthcare IT Consultant BEI
Proposed Meaningful Use Criteria for Stage 2 and 3 John D. Halamka.
Series 1: Meaningful Use for Behavioral Health Providers From the CIHS Video Series “Ten Minutes at a Time” Module 2: The Role of the Certified Complete.
MEANINGFUL USE UPDATE 2014 Mark Huang, M.D. Chief Medical Information Officer Rehabilitation Institute of Chicago Associate Professor Department of PM.
Medicare & Medicaid EHR Incentive Programs HIT Policy Committee June 5, 2013.
Medicare & Medicaid EHR Incentive Programs
Preparing your data base for Medication Reconciliation.
Larry Wolf, chair Marc Probst, co-chair Certification / Adoption Workgroup February 14, 2014.
A First Look at Meaningful Use Stage 2 John D. Halamka MD.
Meaningful Use Personal Pace Education Module: Transitions of Care.
Meaningful Use Measures. Reporting Time Periods Reporting Period for 1 st year of MU (Stage 1) 90 consecutive days within the calendar year Reporting.
Series 1: Meaningful Use for Behavioral Health Providers From the CIHS Video Series “Ten Minutes at a Time” Module 2: The Role of the Certified Complete.
A First Look at Meaningful Use Stage 2 John D. Halamka MD.
Medicaid EHR Incentive Program For Eligible Professionals Overview of the Proposed 2015 Modification Rule Kim Davis-Allen Outreach Coordinator
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
Implementation days 10 Days Onsite Training Additional Hardware Automated Workflow Paperless Environment MD with PC Tablet / iPad Workflow Analysis.
Copyright © 2009 by The McGraw-Hill Companies, Inc. All Rights Reserved. McGraw-Hill Chapter 7 Introduction to Practice Partner Electronic Health Records.
Making better healthcare possible ® Meaningful Use Stage 2 The Changing Seasons of Healthcare Conference WV-HFMA/WV-HIMSS September 27, 2012.
Larry Wolf, chair Marc Probst, co-chair Certification / Adoption Workgroup February 21, 2014.
Medicare & Medicaid EHR Incentive Programs Jason McNamara Technical Director for Health IT.
HITPC – Meaningful Use Workgroup Care Coordination – Subgroup 3 Stage 3 Planning July 27, 2012.
Medicare & Medicaid EHR Incentive Programs Robert Anthony HIT Policy Committee March 7, 2012.
Provider Data Migration and Patient Portability NwHIN Power Team August 28, /28/141.
©2011 Falcon, LLC. All rights reserved. Proprietary. May not be copied or distributed without the express written permission of Falcon, LLC. Falcon EHR.
June 18, 2010 Marty Larson.  Health Information Exchange  Meaningful Use Objectives  Conclusion.
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
HIT Policy Committee Stage 2 Recommendations Presentation to HIT Standards Committee June 22, 2011.
Component 11/Unit 2a Meaningful Use of the Electronic Health Record (EHR)
Meaningful Use Made Easy Step by Step Approach to Stage 1 Compliance and 2013 Changes My Vision Express Practice Management and EMR Software Presented.
HL7 SDWG Topic October 29, 2015 David Tao.  HL7 Success! C-CDA 2.1 is cited, and Care Plan is in 2015 Edition Certification Final Rule  Common Clinical.
Meaningful Use: Stage 2 Changes An overall simplification of the program aligned to the overarching goals of sustainability as discussed in the Stage.
CMS Medicare and Medicaid Electronic Health Record (EHR) Incentive Programs Final Rule Overview 1 Robert Anthony.
Configuring axiUm for Meaningful Use
Procurement Sensitive Medicare’s 2009 ePrescribing Program Daniel Green, MD, FACOG Medical Officer, Quality Measurement Health Assessment Group Office.
2014 Edition Test Scenarios Development Overview Presenter: Scott Purnell-Saunders, ONC November 12, 2013 DRAFT.
 Proposed Rule by the Centers for Medicare & Medicaid Services on 11/03/2015Centers for Medicare & Medicaid Services11/03/2015  Revises the discharge.
 By phone: 1) Dial ) Enter conference ID: # Join the audio conference:  Via internet: 1) Click the phone icon 2) Click “Connect”
Meaningful Use Update 2015: How Does It Impact Family Medicine? Ryan Mullins, MD, CPE, CPHQ, CPHIT.
Relevant and Pertinent Short Survey Results
HITSP Project Medications Management Use Case Presentation to CCHIT
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.3 Manage Medication List aka DC in EHR-S FM
Special Topics in Vendor-Specific Systems
Presentation transcript:

2014 Edition Test Scenarios January 2013

Contents Purpose of Test Scenarios3 Completed Work4 Current Work5 Using a Narrative Test Case Scenario to Develop Test Scenarios6–10 Test Scenario Development11–12 Test Scenario Diagram Overview13 Test Scenario Diagram – EHR Interoperability: Intake14–15 Test Scenario Diagram – Ordering and Medication Management16 Test Scenarios Development – Next Steps17 Proposed Test Scenario Development Workplan18 2

Purpose of Test Scenarios Make clinically relevant (i.e. align with plausible clinical scenarios) Ensure interoperability (using data across systems) Ensure intraoperability (using data within a system) 3 Interoperability Intraoperability

Completed Work 4 Developed 4 Narrative Test Case Scenarios (Inpatient, Ambulatory, Emergency Department, and Medication Management) Developed against the 2011 Edition Test Method Broad scope (e.g. encompasses full settings) Specific to setting and patient data Narrative (i.e. no procedure) Completed Work Current Work

5 Developing Test Scenarios (EHR Interoperability: Intake, Ordering and Medication Management) Developing against the 2014 Edition Test Method Focusing scope Generalizing scenarios o Setting specificity determined by unit tests o Scenario details determined by patient test data (e.g. pediatric vs. geriatric) Documents include o Unit Tests List o Scenario Procedure o Scenario Diagram o Scenario Test Data o Scenario Narrative Completed Work Current Work Developed 4 Narrative Test Case Scenarios (Inpatient, Ambulatory, Emergency Department, and Medication Management) Developed against the 2011 Edition Test Method Broad scope (e.g. encompasses full settings) Specific to setting and patient data Narrative (i.e. no procedure)

Using a Narrative Test Case Scenario to Develop Test Scenarios 6 Narrative Test Case Scenario X Setting WHERE

Using a Narrative Test Case Scenario – Extract Test Scenarios 7 EHR Interoperability: Intake Patient Intake Patient Interaction Ordering & Med Mgmt. Patient Output WHAT (extract individual Test Scenarios) Narrative Test Case Scenario X Setting WHERE

Using a Narrative Test Case Scenario – Extract Test Case 8 EHR Interoperability: Intake Patient Intake Patient Interaction Ordering & Med Mgmt. Patient Output WHAT (extract individual Test Scenarios) Narrative Test Case Scenario X Setting WHERE Test Data (extract specific test case) HOW

Using a Narrative Test Case Scenario – Determine Unit Tests 9 EHR Interoperability: Intake Patient Intake Patient Interaction Ordering & Med Mgmt. Patient Output WHAT (extract individual Test Scenarios) Narrative Test Case Scenario X Setting WHERE Test Data (extract specific test case) HOW Med list Med allergy list Problem list TOC (in) Clinical info rec Med list Med allergy list Problem list TOC (in) Clinical info rec Demographics Med list Med allergy list Problem list Smoking status Vital signs Advance directives Demographics Med list Med allergy list Problem list Smoking status Vital signs Advance directives *Examples of possible unit tests per test scenario. Actual unit tests may vary CPOE eRx Drug-formulary D:D/D:A Med list Med allergy list Problem list Clinical info rec TOC (in) eMAR CPOE eRx Drug-formulary D:D/D:A Med list Med allergy list Problem list Clinical info rec TOC (in) eMAR TOC (out) Clinical summary TOC (out) Clinical summary Unit Tests* (determine specific unit tests)

Using a Narrative Test Case Scenario – Choosing Unit Tests and Test Scenarios 10 EHR Interoperability: Intake Patient Intake Patient Interaction Ordering & Med Mgmt. Patient Output WHAT (extract individual Test Scenarios) Narrative Test Case Scenario X Setting WHERE Test Data (extract specific test case) HOW Med list Med allergy list Problem list TOC (in) Clinical info rec Med list Med allergy list Problem list TOC (in) Clinical info rec Demographics Med list Med allergy list Problem list Smoking status Vital signs Advance directives Demographics Med list Med allergy list Problem list Smoking status Vital signs Advance directives *Examples of possible unit tests per test scenario. Actual unit tests may vary CPOE eRx Drug-formulary D:D/D:A Med list Med allergy list Problem list Clinical info rec TOC (in) eMAR CPOE eRx Drug-formulary D:D/D:A Med list Med allergy list Problem list Clinical info rec TOC (in) eMAR TOC (out) Clinical summary TOC (out) Clinical summary Determine /Choose Unit Tests and Test Scenarios Unit Tests: determined by Setting (popping tests) Test Scenarios: determined by Test Data Determine /Choose Unit Tests and Test Scenarios Unit Tests: determined by Setting (popping tests) Test Scenarios: determined by Test Data Unit Tests* (determine specific unit tests)

Test Scenario Development – Unit Based Testing 11 Minimum requirement Independent tests Individual test data and results Currently employed for 2011 Edition Test Procedures Unit Based Testing

Test Scenario Development – Scenario Based Testing 12 Alternative to unit based testing Dependent tests Dependent test data and results Can remove individual test from sequence Scenario Based Testing If test 1 is not applicable…

Test Scenario Diagram Overview 13 Scenarios represent a suggested sequence for testing criteria Unit Tests are poppable (i.e. can remove from scenario for various reasons) Scenario is made setting specific by adding/removing setting specific tests (e.g. choose between 4a or 4b) Test Scenario Diagram visually represents the linking of Unit Tests Both settings XX Inpatient setting XX Ambulatory setting XX Test procedure: Evaluates conformance to certification criterion Test use of EHR data: Evaluates ability to automatically use data already stored in the EHR Number of Tests: 2*(Number of Criteria) – a 56 7a 7b 4b 1, 2 and 5 1, 2, 3, 5 and 6 data 1, 2, 3, 4, 5, 6, and 7 Test Criterion data added by criterion

Test Scenario Diagram – EHR Interoperability: Intake 14 Med list (EHR) Med allergy list (EHR) Problem list (EHR) Problem list (reconciled) (a)(6) Med list 1)Med list 1 (a)(7) Med allergy list 1)Med allergy list 2 (a)(5) Problem list 1)Problem list 3 (b)(1) TOC – receive, display, incorporate 1)C-CDA 4 (b)(4) Clinical Info Reconciliation 1)Med list (C-CDA) 2)Med allergy list (C-CDA) 3)Problem list (C-CDA) 5 Med allergy list (reconciled) Med list (reconciled) Med list (C-CDA) Med allergy list (C-CDA) Problem list (C-CDA)

Test Scenario Diagram – EHR Interoperability: Intake (a)(1) CPOE 1)Med Orders 2)Lab Orders 3)Rad/Img Orders (b)(3) eRx 1)Prescriptions including medication, prescriber, pharmacy, and patient info (a)(10) Drug- formulary checks* 1)Drug-formulary or preferred drug list *Can be moved within the scenario (a)(2) D:D/D:A checks (a)(6) Med list 1)Med list (a)(7) Med allergy list 1)Med allergy list (b)(4) Clinical Info Reconciliation 1)Med list (C-CDA) 2)Med allergy list (C- CDA) 3)Problem list (b)(1) TOC – receive, display, incorporate 1)C-CDA (a)(16) eMAR 1)Patient 2)Medication 3)Dose 4)Route 5)Time 6)Document (EHR specific) Blue – both settings Green – inpatient (a)(5) Problem list 1)Problem list Med allergy list (reconciled, if applicable) Med list (reconciled, if applicable) Med from prescription (to update med list) Med allergy list (reconciled) Med allergy list (EHR) Med list (reconciled) Med list (EHR) Problem list (EHR) Problem list (reconciled) Patient, med, dose, route, time Prescriptions after drug- formulary check Med Orders Prescriptions Remove if ambulatory setting Prescriptions after drug-formulary, drug- drug, drug-allergy interaction check Med list (C-CDA) Med allergy list (C-CDA) Problem list (C-CDA)

Test Scenario Diagram – Ordering and Medication Management (a)(1) CPOE 1)Med Orders 2)Lab Orders 3)Rad/Img Orders (b)(3) eRx 1)Prescriptions including medication, prescriber, pharmacy, and patient info (a)(10) Drug- formulary checks* 1)Drug-formulary or preferred drug list *Can be moved within the scenario (a)(2) D:D/D:A checks (a)(6) Med list 1)Med list (a)(7) Med allergy list 1)Med allergy list (b)(4) Clinical Info Reconciliation 1)Med list (C-CDA) 2)Med allergy list (C- CDA) 3)Problem list (b)(1) TOC – receive, display, incorporate 1)C-CDA (a)(16) eMAR 1)Patient 2)Medication 3)Dose 4)Route 5)Time 6)Document (EHR specific) Blue – both settings Green – inpatient (a)(5) Problem list 1)Problem list Med allergy list (reconciled, if applicable) Med list (reconciled, if applicable) Med from prescription (to update med list) Med allergy list (reconciled) Med allergy list (EHR) Med list (reconciled) Med list (EHR) Problem list (EHR) Problem list (reconciled) Patient, med, dose, route, time Prescriptions after drug- formulary check Med Orders Prescriptions Remove if patient is not a transition/referral Remove if clinical info reconciliation is not applicable (e.g. a new patient) Remove if ambulatory setting Prescriptions after drug-formulary, drug- drug, drug-allergy interaction check Med list (C-CDA) Med allergy list (C-CDA) Problem list (C-CDA)

Test Scenarios Development – Next Steps 17 Goal: Post the Draft EHR Interoperability: Intake Test Scenario for public comment on January 31, 2013 and post the Final version on February 28, 2013 EHR Interoperability: Intake document development –Test Scenario Procedure –Test Scenario Data IWG Meetings to discuss EHR Interoperability: Intake Test Scenario ATL and ACB focus group to discuss Test Scenarios –Assess competency of ATL and ACB Pilot EHR Interoperability: Intake Test Scenario –Identify vendors to participate in the piloting

Proposed Test Scenario Development Workplan 18