1 / 11

EMR Project Kickoff May 21, 2010

WELCOME!. EMR Project Kickoff May 21, 2010. Agenda. Reflection Welcome and Introductions Our Goals for the EMR and How We Selected Aria Interfaces Current Project Status / Project Timeline Estimated Clinical Resources Requirement (Hours) Project Roles and Responsibilities

totie
Download Presentation

EMR Project Kickoff May 21, 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WELCOME! EMR Project Kickoff May 21, 2010

  2. Agenda Reflection Welcome and Introductions Our Goals for the EMR and How We Selected Aria Interfaces Current Project Status / Project Timeline Estimated Clinical Resources Requirement (Hours) Project Roles and Responsibilities Next Steps and Q&A

  3. System Selection Process Key Requirements How we selected Varian Aria EMR • Held a good ol’ fashioned Bake-Off between four vendors • Developed detailed criteria for evaluations including clinical scenarios. • Sent our functional requirements to vendors, RFP process. • Conducted on–site system demonstrations for key clinical and management personnel. • Selected the vendor that had the best fit to the needs of the organization and physicians. Capture essential clinical, demographic, and financial information Link patient-specific information across inpatient/outpatient hospital settings and private office settings Records can be accessed on and offsite throughout SJO and authorized physician practices System includes warnings and alerts for patient safety Authorized data can be shared with caBIG

  4. Varian Aria Interfaces Center for Cancer Prevention and Treatment

  5. Current Status • Currently completing “pre-implementation” tasks: • Architecture – Single Database • Data Privacy Review • Interface Strategy (BizTalk) • We have ordered Hardware (BIG milestone) • Began database initialization pre-work (user list, dept list, database setup, etc.) • Detailed project workplan finalized.

  6. Project Timeline Go Live! Notes: • Clinical team resources will be needed during the Interface Development and Pre-Golive activities. Please see next slide for details. • Assumes no custom Aria development. • Biweekly project status will be sent to all team members.

  7. Roles & Responsibility Structure

  8. Core Team Roles • Security Application Mgmt • User/password setup • Setting up scheduling mgr • Clinical mgr/security setting • Label setting • Monitor interface logs • First Line Support • Provide primary Go-Live support • Provide ongoing first level support • Prime contact with Varian for support issues • Chemo/Infusion (Med Mgmt) • Regimen building • Favorite agent build • Agent formulary/billing • Agent security setting - dose limits • Prescription printing • Clinical Reports and Assessments • Questionnaire development • Toxicity default list • Maintain note templates • Maintain physician exam defaults • Lab • Monitor lab interface logs

  9. Estimated Hours per Team Member • Aug, Sep, Oct, and Nov: Regimen and Form Development • SuperUser Training: 3 ½ Days • Go Live with Cancer Center: Feb 15th 2011! Go Live!

  10. Conduct follow up meeting w/ Core Team (today at 2pm) • Send regular project communication to team members (biweekly or monthly) • Complete Database Initialization Workbook • Begin interface development process Next Steps 1 2 3 4 Communicate, communicate, communicate.

  11. Questions Questions?

More Related