The Admitting System Crashes, Case Study Example

As the CIO, identify integral steps to carry out during the outage.

During an outage as presented in the given scenario, the first course of action is remaining  calm.  Next is trying to configure or distinguish the processes that are usually cmonitored by TechMed, and develop a hand mechanism execution device. At the same time  IT staff would be working to identify and fix the outage until the situation is resolved. The process of trying to get things done manually may be a tedious and timely task, so supplementary staffing maybe necessary. Unprocessed information would have to be recorded manually during t shut down. After experiencing a outage such as this, emergency planning would need to be completed to help facilitate future situations such as outages

Identify ways to reduce the likelihood of a recurrence of the problem.

As was previously mentioned, in order to prevent panic in situations such as a system crash there must be emergency planning for such occurrences. What this organization needs is a contingency plan. The formation of a contingency plan embodies five implementation specifications. As we studied in Chapter 11, these implementations include; Data backup plan, Disaster recovery plan, Emergency mode operation plan, Testing and revision procedures, and applications and data criticality analysis. The HIPAA security rule addresses contingency plans for ePHI. This plan should include the following: Refurbish IT operations at another location, recuperating IT operations using alternative equipment, and performing some or all of the business activities the old fashion way, by hand. A business impact analysis should be generated to identify critical IT resources, in identifying disruption impacts,  allowable outage times, and developing recovery priorities. Audit trails can be great for crisis supervising. This preparation makes a IT system quickly adjustable to sudden crashes.