MEDITECH 6.1x Implementation Phases Part 3: Design

Design phase of implementation

We’ve been discussing the multiple phases your organization needs to take into account when implementing MEDITECH 6.1x in acute and ambulatory environments. Throughout this series, we will go in-depth on each phase to help you and your organization prepare to take the next steps towards implementation. We have broken the process down into 8 different phases:

  1. Planning
  2. Process Review
  3. Design
  4. Build
  5. Test
  6. Train
  7. Go-Live
  8. Post-Live

So far, we have covered planning and process review in our previous posts and if you missed them, you can click here to catch up. Today, we will discuss the details of the “design” phase which typically takes 1-2 months to complete and builds on what was addressed during the process review. This is critical because the design of your system structure will prepare you for the upcoming build phase. Here are 3 key components to keep in mind:

  1. System structure: The design of the system structure is needed for MEDITECH to set-up and deliver the software. Key decisions include how many databases per application, database naming conventions, medical record number configuration, account number configuration and financial corporations. The system structure also requires you to determine how data and dictionaries will be shared. It’s important to understand that in some situations, these decisions cannot be changed once the build has started without significant impact to the project. The system structure decisions need to go through proper governance for review and approval.
  2. Parameter/Dictionary structure: The MEDITECH system is structured around multiple parameters and dictionaries designated for each application. The parameters determine how the system operates while the dictionaries, or master files, are tables of information utilized throughout the system. Recently, MEDITECH has adopted more standard content within its software delivery and it’s important to review and understand all the content during this phase. Additionally, MEDITECH relies on the Corporate Management System (CMS) application to manage multi-facility environments and you will need to review the CMS settings during this phase. This review needs to be completed across applications, parameters and dictionaries due to the integrated nature of the MEDITECH system. This integration includes applications that cross the acute and ambulatory environments.
  3. Style guide: There is a series of build and implementation related items that require standard naming conventions such as: dictionary mnemonic prefixes, dictionary description components and upper/lower case entries of information into MEDITECH system. The style guide needs to be created during the design phase in order to organize and document your naming conventions so there is consistency throughout the system. The style guide will also need to be reviewed and approved by the various implementation teams before the start of build phase.

Our team is READY certified and has extensive experience around the MEDITECH platform so we are sharing the knowledge we’ve gathered over the years to help you have a better idea of what to expect when implementing, optimizing, upgrading or supporting your MEDITECH environment.

If you are considering implementing a new system or upgrading your current system, our team would be happy to provide specific insight depending on your needs and answer any questions you might have. Please contact us at info@parallontechnology.com or call us at (855) 276-9112.  We encourage you to subscribe to our blog to catch more insight on the remaining phases in this series on implementation.

About The Author:

Craig McCraig McCollum- AVP of Implementation and Consulting ServicesCollum is AVP of Professional Services at Parallon Technology Solutions. In this role, he is responsible for implementation services and project delivery for PTS’ clients. Craig has more than 20 years of healthcare IT and finance experience, including practice leadership, business development, EHR project leadership, EHR implementation and financial management.

Craig is a member of Medical Users Software Exchange (MUSE) and Healthcare Information Management Systems Society (HIMSS). Craig is MEDITECH READY certified in project management, general financials, supply chain management and human resources planning. He earned a Bachelor of Science from Fresno State University.