MEDITECH 6.x Migration- Infrastructure and Planning

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search

Introduction

There is a lot to consider when migrating from MAGIC or Client/Server (C/S) 5.X to MEDITECH's 6.x. Infrastructure requirements are an important component of your migration journey. The following will hopefully assist in some of the decisions needed to ensure a successful migration to 6.x

Data Center Upgrade/Planning

  • Use strategic capacity planning to future-proof your data center's virtualization efficiency and make the most of server hardware. Review current servers, 6.x uses a new category of servers for journaling transactions. Best practice suggests building either a Tier 3 or Tier 4 level of physical and network redundancy. Reliable power supply ensured via grid sectors to avoid surges and ensuring basic principles and best practices of data center airflow management also will assist in a successful approach to migration.
  • WAN connections, increasing the bandwidth
  • Wireless Network, are you running 802.11 a/b/g/n? Higher speeds are always desirable.
  • Storage-As applications become more robust, storage needs will also grow. If you already don't have, you will need a SAN.
  • Back-Up -ISB (Integrated Serverless Backup) is used by 6.x for more efficient backup and recovery

Downtime Procedures/Business Continuity/Disaster Recovery

Have documented policies and procedures for both clinical and non-clinical departments. There are many tools that can be used for business continuity in the event of system downtime.

Implementation Time Line/Change Management

Plan for 1-3 years depending on the size of your organization. A 6.x migration is similar to a net new implementation and requires the same time and resources as a new installation. Cultural change process, need physician buy in and engagement. Prior to go-live set in place your EHR Steering Commitee and physician champions to assist with clinical decision making. Have a procedure in place.

Dictionary Management,Workflow, and Task Automation Technology

Dictionary clean-up very important, continue post go live, data migration and improved processes. Synchronizing and updating, reach out to vendors appropriately so no surprises at go live. There are more software updates with 6x compared to MAGIC, be prepared.

Interfaces

  • Custom Interfaces- If you have custom interfaces, what are their roles with 6.x?
  • Review all departments expectations with interfacing
  • Interface differentiators with 6.x (ADT 2.1 to 2.4)


Tips and Tricks

If you use a third party or add on vendor for for dispersing clinical reports, a few items to keep an eye on:

  • The MEDITECH C/S 6.x is a completely different HCIS and does process reports differently from MAGIC. Modifications will need to be made to ensure that reports are processed properly.
  • Windows printers need to be configured to receive reports for C/S 6.x. C/S 6.x does not have embedded printing routines.
  • Review your report distribution templates and make necessary changes so that C/S 6.x reports are properly processed.
  • Prior to processing reports generated by the C/S 6.x system, import a MIS provider dictionary from the C/S HCIS.
Retrieved from "https://wiki.galenhealthcare.com/index.php?title=MEDITECH_6.x_Migration-_Infrastructure_and_Planning&oldid=20156"