Over the past month and a half, using the experience of David Chou (VP/CIO Children’s Mercy Hospital), Stephen Tokarz (HCI Senior VP, Training & Activation), and Bob Steele (HCI Executive VP, Clinical Services), this blog series has covered all of the aspects of an EHR Go-Live. From pre Go-Live planning and training, to post Go-Live adoption and transition to support mode, the Go-Live process is long, multidimensional, and requires much forethought and detailed planning. If you’re in the process of preparing for your own Go-Live, hopefully you’ve found the information contained within these posts to be helpful and relevant. Of course, if you’d like more information or have specific questions about your own project, we’d enjoy the opportunity to speak with you one-on-one—just look for the form at the bottom of this post!
Today, we’ll be publishing our last chapter of the series. Though less complicated planning-wise than the other topics we’ve covered, security and access issues can nonetheless cause major problems and project delays during Go-Live. It’s pretty straightforward—if your staff can’t get into the EHR system, they’re not going to be able to do their jobs!