|
Department Downtime Procedures
It's up to individual organizations to determine how robust their Healthcare Operational Continuance solution needs to and will be. An easy way to measure the aggressiveness of the plan? Take a look at the Recovery Point Objective (RPO). Is it 24 hours (i.e., it's okay if the point in time to which the hospital's IT environment will recover is up to 24 hours in the past)? Or, is it two hours? Clearly, one means a lot less lost data than the other--a critical measure, particularly for those organizations who have implemented Advanced Clinical Systems (ACS).
But, hard as we may look, it's difficult to find a healthcare organization that has successfully implemented a true "zero-downtime" solution.
That means that every organization needs to carefully document the Departmental Downtime Procedures that employees should follow during a downtime, whether that downtime may be brief or extended.
Most hospitals have created these documents at one time or another. But whether these are actually up-to-date and whether current employees have been trained on their use is frequently a different matter altogether.
JJWild has created a service to assist MEDITECH organizations in ensuring their departmental staffs know where to go and what to do--particularly as it relates to continuing to treat patients--during a downtime. During this engagement, our consultants direct and coordinate development and/or remediation of a hospital's standardized departmental downtime procedures. The goal of any such project--whether undertaken in partnership with JJWild or independently--is to achieve consistency, inter-departmental integration, and usability of these procedures so that a downtime--whether 30 minutes or 30 hours--has the least negative consequences possible.
|
