80 likes | 179 Views
Detailed overview of the Billing & Electronic Health Record (BEHR) Project, including benefits, major deliverables, system usage, and lessons learned. Presented by Robert Mayer, CIO & Dr. Maggi Gallaher, PHD Medical Director. Certification closeout on August 27, 2008. The project aimed to improve billing and claims functions, comply with HIPAA requirements, and enhance tracking of health care services. Major deliverables included practice management & electronic health record deployment, business process redesign, and extensive user training. Key lessons learned highlight the importance of project sponsorship, effective scope management, and workflow-based training strategies.
E N D
Public Health Division (PHD)Billing & Electronic Health Record (BEHR) Project – presented by Robert Mayer, CIO & Dr. Maggi Gallaher, PHD Medical Director DoIT Project Certification Closeout August 27, 2008
BEHR Project - Certification Request • $ Requested this phase: $0 • Project Phase cert request: Closeout • Project Start Date: 11/1/06 • Projected End Date: 6/30/08 • Total Project Value ‘and’ expended to date: $1,378,202
BEHR Project - Benefits • Improve billing and claims functions • Comply with HIPAA requirements • Improve tracking & monitoring of health care services and clients • Support management of its local public offices
BEHR Project – Major Deliverables • Designed, Configured, Tested, and Successfully Deployed Practice Management (PM) & Electronic Health Record (EHR) • Completed Business Process Redesign • Trained over 300 users • Implemented at 50 local public health offices in one year
BEHR Project – System Usage • Clients: 21,062 • Procedures: 129,756 • Users: 345
BEHR Project - Lessons Learned • Strong project sponsorship valuable to success • Scope Management allowed baseline product implementation to offices within year • Limited scope created future list • Workflow-based training more effective than content style training
BEHR Project – Lesson Learned continued • Training the week prior to go-live; followed by on-site go-live support • Impact of change to the “before” workflow model and to the culture • Varying degrees of user acceptance of the new workflow model and system