When implementing new systems, the process can be broken down into 8 different phases. In the last few weeks we’ve discussed planning, process review and design and if you haven’t had a chance to read those posts, you can here. Today, we will be covering the “build” phase. This phase typically takes 3-4 months to complete and expands on what was completed during process review and design phases and prepares you for the upcoming test phase.
Here are 5 key components to consider:
- Standard Content: MEDITECH 6.1x is delivered with standard content which allows organizations to have consistencies across respective facilities and leverage best practices for various processes and regulatory reporting requirements. The standard content reduces build time so organizations can bring the system up in a timelier manner to ultimately reduce overall costs. Also, it allows the staff to allocate more time for adoption and processes.
- Localized Content: Localized content builds on top of the MEDITECH standard content that was initially delivered. Implementation requires additional content that is specific to each organization for example, patient rooms and surgical preference cards. Dictionaries that require localized content should be identified during the design phase when CMS settings are being determined.
- Interdependencies: When building dictionaries, there are various interdependencies that require some to be built before others. For example, supply chain items are dependent on supply chain packaging units, packaging strings, vendors, manufacturers and general ledger expense codes. These interdependencies need to be identified during the planning and design phases and incorporated into overall project tracking documents. Additionally, you should consider how the MEDITECH 6.1x Acute and Ambulatory applications interact with each other on the dictionary level. There are multiple dictionaries shared between Acute and Ambulatory that need to be factored into the build and overall project.
- Data Conversions: There are multiple data conversions that will take place when implementing MEDITECH 6.1x. As organizations rely more on MEDITECH delivered standard content, there will be multiple dictionaries that will need to be mapped between legacy and new values. There are multiple tools that can be utilized to map capabilities whether it’s within MEDITECH, a spreadsheet, database or within a conversion program. It is important to manage the mapping between your legacy and new system during implementation.
- Resource Allocation: You need to consider who will be handling the build tasks during implementation and how to best allocate local resources. There are multiple tools available to build dictionaries including MEDITECH provided utilities, scripting and manual. This could be an opportunity to leverage technology or lower your costs by using temporary resources while local resources focus on adoption and process.
If you are considering implementing a new system or upgrading your current MEDITECH environment, our team would be happy to provide specific insight depending on your needs and answer any questions you might have. Please contact us at email@example.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 McCollum 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.