Project Fusion Epic XXXinsert Epic Module Name Update

  • Slides: 21
Download presentation
Project Fusion Epic XXX(insert Epic Module Name) Update By Department xxxx (insert name of

Project Fusion Epic XXX(insert Epic Module Name) Update By Department xxxx (insert name of specialty/department/group) Date: xxxxxx Presenter: xxxxx

TOH Readiness Owners • xxxxx (list of Readiness Owners)

TOH Readiness Owners • xxxxx (list of Readiness Owners)

xxxx (insert Epic Module name) Team (List Team Members with photos if available) •

xxxx (insert Epic Module name) Team (List Team Members with photos if available) • xxxxx

Agenda • Introductions • What is XXX(insert Epic Module Name) & Why Should I

Agenda • Introductions • What is XXX(insert Epic Module Name) & Why Should I Care? • General Timeline • Summary of Direction Meetings • What’s Staying the Same • What’s Changing • Other Changes • Where We’re Going to Need Your Help • Next steps

What is xxxx (insert Epic Module name) and Why Should I Care? Insert image

What is xxxx (insert Epic Module name) and Why Should I Care? Insert image of how module workflow works (below sample from Radiology) Describe Opportunities and Benefits to Users Electronic round trip Integrated software where all users have access to information documented by other users

What is xxxx (insert Epic Module name) and Why Should I Care? Engagement Helps

What is xxxx (insert Epic Module name) and Why Should I Care? Engagement Helps avoid the common Pitfalls Engagement is important to avoid common pitfalls because if we do it wrong: • Costs time and money to rework • Cost for errors born by xxxx (insert name of specialty/department/group) • Long-lasting effects on efficiency • Relearning workflows is difficult

Timeline Overview - Where We are Today

Timeline Overview - Where We are Today

Project Timeline – Detailing Project Activities & Milestones

Project Timeline – Detailing Project Activities & Milestones

xxxx (insert name of specialty/department/group) Team Involvement Up to Now (List of presentations made

xxxx (insert name of specialty/department/group) Team Involvement Up to Now (List of presentations made to team to date, including date presented) • xxxxx

What’s Staying the Same • xxxxx (list what will stay the same as it

What’s Staying the Same • xxxxx (list what will stay the same as it is today i. e. Overall workflow – protocoling, performing procedures etc. ) • xxxxx

What’s Changing • xxxxx (list what will change) Place detailed information supporting each point

What’s Changing • xxxxx (list what will change) Place detailed information supporting each point in the notes for this slide. • xxxxx

What’s Changing (cont. ) • xxxxx (list what will change) Place detailed information supporting

What’s Changing (cont. ) • xxxxx (list what will change) Place detailed information supporting each point in the notes for this slide. • xxxxx

Other Changes Add items specific to your department (samples are below) • All ordering

Other Changes Add items specific to your department (samples are below) • All ordering and scheduling will be in Epic • Most documentation will be in Epic • Patients will be able to see their results in My. Chart (list other confirmed features)

Where We’re Going to Need Your Help Outstanding Decisions: • Residents/Fellows workflows • Discrepancies

Where We’re Going to Need Your Help Outstanding Decisions: • Residents/Fellows workflows • Discrepancies • Critical results • Consults Build Phase Means Content Review: • Protocol development and forms • XXX(Enter Specialty or Discipline for your area)/reading physician tools • Engagement before its too late

Where We’re Going are Going to Need Your Help Testing • End-User Acceptance Testing

Where We’re Going are Going to Need Your Help Testing • End-User Acceptance Testing • Shadow Charting • Integrated Workstation Testing Training • Specialists Training Specialists • Pilot training • End-User training • Personalization Labs

All Hands on Deck Total Amount of Time Needed From xxx (department name or

All Hands on Deck Total Amount of Time Needed From xxx (department name or group) Time Spent To Date

Next Steps Phase Start Date Phase 2: Adoption and System Configuration January 2018 Adoption

Next Steps Phase Start Date Phase 2: Adoption and System Configuration January 2018 Adoption 1: Completed Adoption 2: Completed Adoption 3: May 8 -10, 2018 Adoption 4: June 5 -7, 2018 Phase 3: Testing July 10, 2018 Phase 4: Training, Deployment, and Go Live March, 2019 Go Live! June 1, 2019 Phase 5: Post-Live Support and Optimization July 2019 onward

Tools and Information on Project Fusion Website INFO: Fact Sheets on Epic Features •

Tools and Information on Project Fusion Website INFO: Fact Sheets on Epic Features • Clinical System Design • Your Guide to Pathways and Order Sets • Day 1 of Go-Live: What data will be available in Epic • Documentation Made Easy (Smart. Tools) INFO: Check out Project Fusion website Icon on your TOH desktop

Have you heard something about Epic and are not sure it is accurate? Stopping

Have you heard something about Epic and are not sure it is accurate? Stopping Myths and Misconceptions in their tracks • A place where anyone can ask any question about Project Fusion and the Epic delivery both by name or anonymously • answers will be provided by Project Fusion to provide greater clarity • A community area where questions can be posed answered online • A resource to gather relevant and current concerns as they occur and use as basis to develop key messaging, fact sheets, Q&As, and backgrounders • http: //www. ottawahospital. on. ca/en/project-fusion (password: fusion)

ENGAGE-Have Your Say! Help Project Fusion learn more ways to support you in our

ENGAGE-Have Your Say! Help Project Fusion learn more ways to support you in our journey together! http: //www. ottawahospital. on. ca/en/project-fusion

Questions? http: //www. ottawahospital. on. ca/en/project-fusion (password: fusion) projectfusion@toh. ca

Questions? http: //www. ottawahospital. on. ca/en/project-fusion (password: fusion) projectfusion@toh. ca