Power Point Presentation

Leyanis
Chapter_020HIT4.pptx

Chapter 20

Health Information Systems: Downtime and Disaster Recovery

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Introduction

The primary objective for downtime and disaster planning is to protect the organization and the patients who are served by that organization by minimizing the disruption to the operations.

2

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Downtime Risk Assessment

Should occur from project inception through system maturity.

Downtimes can be classified by the root cause and the degree of impact.

Root cause must be determined.

Priority will be unique for each organization.

Information technology (IT) should work closely with the organization’s emergency preparedness and disaster planning groups.

3

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Sample Elements of Information Technology Infrastructure

4

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Box 18-1 from text

4

Examples of Information Technology Physical Structure

5

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Box 18-2 from text.

5

Downtime and Response Planning

Consider both planned and unplanned downtimes.

Develop the response and recovery plans.

Quick assessment of the significance of a downtime event will help determine a response.

6

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Downtime Determinator Model

7

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Figure 18-2 from text.

7

Clinical Impact and Planning

Clinical impact and planning: Acute care focus

Types of back-up systems

Downtime policies and procedures

8

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Redundant Systems

Are also known as back-up systems.

Provide the clinicians with the ability to access some, if not all, of the patient’s data during an electronic downtime.

Some systems cannot be updated during a downtime.

Shadow or mirror systems often have read and write capabilities.

Web-based systems are used for planned downtimes.

9

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Downtime Policies and Procedures

Guide the clinical team.

Should include specific instructions about required data entry back into the legal and permanent electronic health records (EHRs) systems at the conclusion of the downtime.

10

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Information Technology—Impact and Planning

Assessment risk

Is a service management program needed?

What is the service management life cycle?

Disaster plan

What are its contents?

Who needs to be involved?

Are the test plans up to date?

11

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Disaster Planning

Must be compliant with the Health Insurance Portability and Accountability Act (HIPAA) security rule of 1996, the Department of Health and Human Services, and The Joint Commission (TJC).

Organization needs to be prepared to rapidly test the clinical system to ensure that all aspects of the system are functioning as planned.

12

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Disaster Recovery

Determine and prioritize critical systems.

Plan to get the systems back on line.

13

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Business Continuity

Include the systems that run the business.

Formal process includes:

Impact analysis

Recovery strategies

Formal plan

Testing of the plan

14

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Communication

Communication plan

Who needs to know?

What details do they need?

Who will communicate the details to those who need to know?

What systems and workflows are affected?

15

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Responsibilities

Communicate the necessary information to the following:

Desk agents

Senior leadership

Public relations personnel

Other (e.g., university affiliations, community)

16

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

Conclusion and Future Directions

Downtime and disaster recovery is necessary to:

Minimize the economic loss.

Ensure organizational stability.

Protect the critical assets of the organization.

Ensure the safety of personnel.

Protect patients and other customers.

Reduce the variability in decision making during a disaster.

Minimize legal liability.

17

Copyright © 2014 by Mosby, an imprint of Elsevier Inc. All rights reserved.

image2.jpeg

image3.jpeg

image4.jpeg

image1.png