|
MEDITECH Recovery Procedures & Test Plan
With the advent of new and constantly improving technologies, MEDITECH organizations have an unprecedented opportunity to protect and retrieve their mission-critical data in the event of an operational disruption or even disaster in record time. But equally as important as the hardware, software, and networking required to facilitate robust Healthcare Operational Continuance strategies, are the documented procedures that detail the how of such solutions.
Indeed, in spite of all of the sophisticated technology and automation built into our data center environments, the fact remains that the majority of our processes still require human intervention and decision making. And this is particularly true in the event of an outage that disrupts normal operations and requires special response.
In times like these, step-by-step, current, and familiar procedural documentation frequently means the difference between successful recovery and staring at a pile of expensive equipment or an unfamiliar GUI not knowing where to begin.
JJWild has developed a suite of MEDITECH recovery procedure services designed to validate, document, test, and maintain an organization's HOC strategy. These processes--whether contracted with JJWild or developed independently--are of benefit for any MEDITECH hospital, regardless of the level of sophistication that a particular organization has achieved, however they are an absolute must for any facility that is operating and managing both a primary and a secondary data center environment.
MEDITECH Recovery Procedure - Development and Documentation
The more complex the HOC solution, the more critical the documentation to make it work.
During the MEDITECH Recovery Procedure (MRP) Development and Documentation project, JJWild provides technical and subject matter expertise, as well as project leadership, in the creation of a living MEDITECH Recovery Procedure document that is applicable to the hospital's MEDITECH IT environment.
During this engagement, JJWild first works with Hospital IT personnel to define the technology environment to be included in the recovery, and then documents (as applicable) server failover or recovery procedures, including re-naming and re-addressing changes, network failover procedures, processes to re-assign storage, and backup procedures.
With this baseline in place, a hospital is then free to maintain these documents going forward, ensuring that all new employees who should have familiarity with the procedures are trained and that change management procedures are in place.
MEDITECH Recovery Test Plan - Initial Development and Execution
The objective of the MEDITECH Recovery Test Plan (MRTP) Initial Development and Execution project is to develop and document a step-by-step procedure to test the MEDITECH Recovery Procedure (MRP), to conduct a test of these procedures, and to identify any updates or modifications required to the MRP that were uncovered during the test.
The MRTP and MRP are distinct in that the MRTP is intended to serve as a document that the Hospital can independently use to regularly test the MRP; whereas the MRP is a document that would generally only be invoked in the event that operational or disaster recovery were required due to some incident.
MEDITECH Recovery Procedure - Periodic Test and Update
No plan is complete without a plan to maintain the plan (or something like that).
The objective of the MEDITECH Recovery Procedure Periodic Test and Update is to test the pre-existing, step-by-step MEDITECH Recovery Test Plan (MRTP) and verify that it and the MEDITECH Recovery Procedure (MRP) are up-to-date and meet the Hospital's current recovery requirements. As part of this service, JJWild identifies and makes any updates or modifications required to the MRP or MTRP that are uncovered during the test.
The Periodic Test and Update service can be invoked by a hospital as frequently as desired. Most organizations opt to perform an audit annually and/or any time a material change is made to the production or recovery environment.
|
