Study guide
6.5 Disaster Recovery and Downtime Readiness
RHIA Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: RHIA Eligibility, Application, Fees, Format, Scoring, and Retakes
1.1 RHIA Purpose and Administrator-Level Scope 1.2 HIM-Only Eligibility Routes 1.3 MyAHIMA Application, Transcripts, and the 120-Day Scheduling Window 1.4 Fees, Format, and Appointment Time 1.5 Passing Score and Score Interpretation 1.6 Retakes, Certification Maintenance, and Current Statistics
2 2023 RHIA Outline, Exam Functionality, Pretest Items, and Study Strategy
2.1 Current 2023 Outline and Why It Controls Study 2.2 Domain Weights and Study-Time Allocation 2.3 Scored Items, Pretest Items, and Answer Discipline 2.4 Navigation, Flagging, Review, and Submit Workflow 2.5 Test Center Day and No-Resource Requirement 2.6 Official Task-Based Study Strategy
3 Data and Information Governance I: Documentation Integrity and Quality Reporting
3.1 Documentation Integrity as Governance 3.2 Complete, Accurate, and Timely Records 3.3 Documentation Standards and Clarification Workflows 3.4 Clinical Data Elements for Quality Reporting 3.5 Data Quality Validation for Reporting 3.6 Governance Committees, Metrics, and Remediation
4 Data and Information Governance II: Data Dictionaries, Retention, MPI, and Policy
4.1 Data Dictionary Standardization 4.2 Documentation and Data Standards 4.3 Data Analysis to Inform Management 4.4 Policies and Procedures for Information Governance 4.5 Retention and Destruction Policies 4.6 Master Patient Index Integrity
5 Compliance I: Access, Use, Disclosure, Patient Rights, ROI, and HIE
5.1 Domain 2 Compliance Decision Frame 5.2 Patient Access and Portal Governance 5.3 Advocacy for Patients and Families 5.4 ROI Intake, Validation, and Scope Control 5.5 Disclosure Documentation and Audit Trails 5.6 HIE and External Access Governance
6 Compliance II: Security, Breach Workflows, Cybersecurity, and Disaster Recovery
6.1 Request Workflow Controls and Escalation 6.2 Breach Protocols from Report to Resolution 6.3 Privacy and Security Initiatives 6.4 Cybersecurity Risks for HIM Leaders 6.5 Disaster Recovery and Downtime Readiness 6.6 Monitoring, Metrics, Tabletops, and Continuous Improvement
7 Data Analytics and Informatics I: EHR Support, Reporting, Databases, and Dashboards
7.1 EHR Support and HIM Administration 7.2 Reporting Lifecycle and Data Requests 7.3 Visualizations, Dashboards, and Executive Views 7.4 Database Management and Data Dictionaries 7.5 Data Mining and Analytics Workflows 7.6 Statistics Validation for Stakeholders
8 Data Analytics and Informatics II: CDI, Workflows, HIE, Integrations, and SDLC
8.1 Focused Documentation Audits for CDI, Quality, and Safety 8.2 CDI Workflows and Query Governance 8.3 Workflow Optimization Through Health Information Technology 8.4 HIE Governance and Exchange Controls 8.5 Software Integrations and Health Information Impact 8.6 Systems Development Life Cycle and HIM Participation
9 Revenue Cycle Management I: Reimbursement, Coding Validation, CDI, and Claims
9.1 Domain 4 Revenue Cycle Management Frame 9.2 Reimbursement Models and Provider Education 9.3 Coding Accuracy Validation Controls 9.4 HHS Documentation Requirements and CDI 9.5 Claims Workflow and Clean-Claim Controls 9.6 CDM, DNFB, and A/R Management
10 Revenue Cycle Management II: Revenue Integrity, Denials, Fraud, and Official Guidelines
10.1 Official Guidelines and Code Assignment 10.2 Groupings and Payment Data Validation 10.3 Revenue Integrity Program Design 10.4 Coding Audits, Monitoring, and Corrective Action 10.5 Denials Management and Appeals 10.6 Fraud Prevention and Compliance Escalation
11 Management and Leadership: Strategy, HR, Work Design, Training, Budgeting, and Projects
Strategy, Goals, and Change Management Contracting and Outsourcing Governance Human Resources, Staffing, and Performance Work Design and Process Improvement Training and Development Budgets, Accreditation, Compliance, and Projects
12 Final RHIA Review: Domain Integration, Exam Week, and Career Next Steps
Integrated Scenario Patterns Across Domains Final Week Domain-Weighted Review Test-Center Day, Functionality, and Pacing Results, Retakes, and RHIA Maintenance RHIA, RHIT, CHDA, CHPS, and CCS Career Map Readiness Checklist and Next-Step Plan
6.5 Disaster Recovery and Downtime Readiness
Key Takeaways Explain This Topic AI
The HIPAA Security Rule contingency plan is required and includes a data backup plan, a disaster recovery plan, and an emergency mode operation plan.
Recovery objectives are defined by Recovery Time Objective (RTO, how fast a system must be back) and Recovery Point Objective (RPO, how much data loss is tolerable).
Downtime procedures must preserve clinical documentation, patient identity, scanning and indexing, reconciliation, and release-workflow continuity so the legal health record stays trustworthy.
A backup that has never been restore-tested is an assumption, not a control; RHIA leaders validate recovered data and workflow dependencies.
Last updated: June 2026
Plan for Records During Disruption
Disaster recovery is not abstract technology for HIM — it is the ability to keep health information available, accurate, controlled, and recoverable when systems or facilities are disrupted by cyber incidents, power loss, network outage, severe weather, facility damage, interface failure, vendor outage, or planned EHR downtime. The HIPAA Security Rule makes a contingency plan a required administrative safeguard, and it has named components the exam tests: a data backup plan , a disaster recovery plan , an emergency mode operation plan , plus addressable testing/revision procedures and applications/data criticality analysis.
Two recovery metrics anchor planning. The Recovery Time Objective (RTO) is the maximum acceptable time a system can be down before unacceptable harm occurs — it answers “how fast must the EHR be back?” The Recovery Point Objective (RPO) is the maximum acceptable amount of data loss measured in time — it answers “how much recent documentation can we afford to lose?” If backups run nightly, the RPO is roughly 24 hours; if the EHR must be restored within 4 hours, the RTO is 4 hours. A business impact analysis sets these targets by ranking systems by criticality.
Recovery area HIM risk Readiness control
Clinical documentation Care occurs outside the EHR Approved downtime forms, chart packets, documentation standards
Patient identification Wrong-patient documentation enters the record Downtime registration controls and reconciliation checks
ROI and patient access Requests age or are released from incomplete records Status tracking, communication scripts, restart criteria
Scanning and indexing Paper from downtime is misplaced Batch control, indexing verification, backlog monitoring
- HIE and interfaces Data queues, duplicates, or fails Interface reconciliation and partner communication
- Coding and billing Incomplete records reach coding too early Hold rules, completion checks, coder alerts
- Reporting Dashboards show incomplete or stale data Data-quality notes and recovery validation
Recovery planning must identify critical systems and dependencies . The EHR may depend on identity management, network services, document imaging, dictation, lab and pharmacy interfaces, the patient portal, HIE connections, coding tools, claims systems, and reporting platforms. If one dependency fails, the workflow breaks even though the main application is running — a nuance the exam uses to discredit “the EHR is up, so we are fine” answers.
Backups are only useful if restoration works . HIM leaders should ask whether backups cover the right systems, whether restore tests are performed against the RTO and RPO, whether recovered data is validated, and whether downtime documentation merges into the legal record without gaps. A backup that has never been restore-tested is an assumption, not a control.
Downtime Readiness Checklist
Current downtime forms and job aids are stored where staff can reach them without the network.
Staff know when downtime begins, who announces it, and how updates flow.
Patient identity and encounter controls continue during downtime.
Paper is tracked from creation through scanning and reconciliation with batch control.
ROI, portal, HIE, coding, quality, and billing teams know hold and restart rules.
Backups, restoration, and data validation are tested against RTO/RPO targets.
An after-action review captures record gaps, delays, duplicate entries, and fixes.
Common trap: scenarios where staff document on scrap paper, scan without batch control, release records while downtime documents are missing, or resume coding before reconciliation. These are not mere inconveniences — they create patient-safety, compliance, revenue, and data-integrity problems. A strong RHIA answer protects the record across the full lifecycle: before the event define and train, during the event preserve documentation and communicate status, and after restoration reconcile, validate, scan, index, update queues, monitor backlogs, and document lessons learned.
Recovery is successful only when the organization can trust the restored legal health record.
Backup Strategy, Emergency Mode, and the Legal Health Record
A defensible backup strategy is often summarized as the 3-2-1 rule : keep 3 copies of data, on 2 different media types, with 1 copy stored off-site (and increasingly one copy offline or immutable to survive ransomware that targets connected backups). The off-site or air-gapped copy is what makes recovery possible after a site-wide event or an attack that encrypts production and network-attached backups together.
The emergency mode operation plan — a required Security Rule contingency component — governs how critical business processes continue while systems are down so PHI remains protected. For HIM this means downtime forms are authorized, registration assigns or verifies the correct medical record number to prevent duplicates and overlays, and a clear announcement protocol tells the organization when downtime starts and ends.
Reconciliation protects the legal health record (LHR) — the documentation an organization will produce on legal request. After restoration, every downtime document must be scanned, indexed to the correct patient and encounter, and verified so the LHR is complete; gaps, duplicates, and overlays must be corrected before the record is trusted for release, coding, or litigation. A late or mis-indexed downtime note can become a patient-safety event or a disclosure error months later.
- Recovery concept Definition Why it matters for HIM
- 3-2-1 backup 3 copies, 2 media, 1 off-site Survives site loss and ransomware on connected backups
Emergency mode operation plan Continue critical processes during downtime Keeps PHI protected and records controlled
Reconciliation Merge downtime docs into the EHR accurately Completes and validates the legal health record
Business impact analysis Ranks systems by criticality to set RTO/RPO Prioritizes which records-related systems recover first
The exam rewards candidates who connect these mechanics to outcomes: availability is meaningless if the restored record is incomplete, and a tested backup with sound reconciliation is the only way to prove the organization can both recover and trust its health information.