Paragon Project Survivor’s Guide

This is your project, your system.

Take the majority of the projects you have completed over the last 8-10 years, roll them into a bundle and deliver them again, all at once, over one weekend. This approximates what your Paragon project entails. The good news is you and your staff delivered those projects in the past and support those systems today. You have tremendous insight into what has worked, and what has not. Insight you lose to every degree you cede control to either McKesson or companies like CHA. McKesson and CHA have a critical role to play in the project, but if you expect too much from either - the best case is you are disappointed, the worst case is a failed project.

This guide will help you to:

Depend on McKesson and consulting as little as possible
Accelerate your team knowledge to most effectively guide your build
Own the project, and adopt a new structure of support
Create a project structure that defines roles and responsibilities
Facilitate a high level of communication
Use your conversion to clean and reset your data
Close the gap between current workflow and building the future state
Utilize patient based testing to expose gaps
Reduce risk during the Go Live phase