As the Feb. 2 soft go-live of the utmbconnect system approaches, project teams have been very busy preparing for the “cutover”, a term used to describe the event that takes place when switching over from the old system to the new system (or new functionality in an existing system). In the case of utmbconnect, the old system refers to the legacy revenue cycle (Siemens Invision), and the new system, utmbconnect, is the integrated revenue cycle/clinical documentation system (Epic)

Actual system downtime might last a few minutes or a few hours but the cutover process can begin days ahead of time. The preparation for cutover starts months ahead of time.

There are many variables to consider when planning a cutover; stakes are high in terms of possibility for errors. Every step is precise and must be performed at the proper time – going out of order could potentially create major chaos during cutover or once live. But have no fear! The utmbconnect teams have been preparing since Novmeber and are ready for a success!

The cutover will actually be three distinct cutover events. The first will coincide with the Charging and Coding soft go-live in February. The second cutover will support the Pre-registration and Scheduling Appointment Conversions in March. The final cutover will end with the fully connected go-live in April.

Cutover for the entire process must be reviewed to ensure at the end of the three cutovers that all required data is live and functioning and that proper support is in place for the future. Analysis and planning for the March and April cutovers is underway even as teams are practicing for February.