Show Summary Details
Page of

Business continuity: Illustrated by hospital ward closures 

Business continuity: Illustrated by hospital ward closures

Chapter:
Business continuity: Illustrated by hospital ward closures
Author(s):

Alex G. Stewart

, Sam Ghebrehewet

, and David Baxter

DOI:
10.1093/med/9780198745471.003.0013
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2015. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy).

date: 26 June 2017

This chapter describes the strategies for business continuity when a significant challenging event affects a hospital or other healthcare provider: the scenario is a norovirus outbreak affecting several wards and staff. The strategy includes business impact analysis and a disaster recovery plan. The importance of developing a generic response plan, rather than a response for each type of incident, is emphasized. The early involvement of the infection control team, isolating or cohorting patients, and liaison with the community are essential components of the response. The chapter describes how a ‘less serious event’ (a few reported cases) may rapidly escalate into a major incident. The business continuity plan should be implemented early, and should identify which services can be stopped, and which must continue. Finally, the importance of holding a multi-agency and multi-professional debrief meeting as soon as the incident is declared over is emphasized, with revision of the plan accordingly.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.