Study guide

6.2 Breach Protocols from Report to Resolution

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.2 Breach Protocols from Report to Resolution

Key Takeaways Explain This Topic AI

Under the HIPAA Breach Notification Rule, individuals must be notified without unreasonable delay and no later than 60 calendar days after discovery of a breach.

Breaches affecting 500 or more individuals require notice to HHS OCR and to prominent media within 60 days; breaches under 500 are logged and reported to HHS within 60 days after the calendar year ends.

The 2013 Omnibus Rule presumes any impermissible use or disclosure is a reportable breach unless a four-factor risk assessment shows a low probability that PHI was compromised.

RHIA leaders contribute by reporting immediately, containing exposure, preserving evidence, supplying factual record details, and driving root-cause corrective action.

Last updated: June 2026

Treat Suspected Breaches as Managed Events

A breach under HIPAA is the acquisition, access, use, or disclosure of unsecured protected health information (PHI) in a manner not permitted by the Privacy Rule that compromises its security or privacy. The Breach Notification Rule sets hard deadlines the RHIA exam loves to test: affected individuals must be notified without unreasonable delay and no later than 60 calendar days after discovery . If a breach affects 500 or more individuals , the covered entity must also notify the HHS Office for Civil Rights (OCR) within 60 days and notify prominent media serving the state or jurisdiction within 60 days.

Breaches affecting fewer than 500 individuals are logged and reported to HHS within 60 days after the end of the calendar year .

The 2013 Omnibus Rule changed the analysis: an impermissible use or disclosure is presumed to be a reportable breach unless the entity documents a four-factor risk assessment showing a low probability that PHI was compromised. The four factors are (1) the nature and extent of the PHI, including identifiers and likelihood of re-identification; (2) the unauthorized person who used or received it; (3) whether the PHI was actually acquired or viewed; and (4) the extent to which risk has been mitigated.

Three exceptions can avoid breach status entirely: good-faith unintentional access by workforce, inadvertent disclosure between authorized workforce members, and disclosure to a recipient who could not reasonably have retained the information.

The first operational rule is that a suspected breach is reported through policy , never quietly fixed. A staff member who misdirects a fax, opens the wrong record, loses a paper packet, or spots unusual access in an audit log must not clean it up and move on — informal cleanup destroys evidence and can blow the 60-day clock.

  • Breach response phase Purpose RHIA contribution
  • Report Bring a suspected event into the official path Ensure staff know how and what facts to capture
  • Contain Stop additional exposure or access Suspend release, disable access, retrieve records, correct routing

Preserve evidence Keep logs, documents, and system details intact Identify request records, disclosure logs, audit trails, patient lists

Investigate Determine what happened and what PHI was involved Validate identity, record scope, document set, workflow history

Assess risk Apply the four-factor test with facts Provide recipient, viewing, mitigation, and sensitivity details

Notify Meet 60-day and 500-individual obligations Supply affected-individual counts and addresses for the notice list

Remediate Correct the process that allowed the event Update workflow, training, configuration, vendor or monitoring controls

  • Document Preserve decisions and actions Maintain defensible notes, approvals, and closure evidence
  • Breach Protocol Do and Do Not List

Do report suspected incidents immediately through the official path so the 60-day clock is managed.

Do preserve audit logs, request records, release packages, emails, envelopes, and transmission receipts.

Do contain further exposure before routine processing resumes.

Do document the four-factor risk assessment, even when the conclusion is “no notification required.”

Do not rely on hallway opinions or memory as the only evidence.

Do not alter records, logs, or correspondence to make the event look cleaner.

Do not promise patients an outcome before the designated team finishes review.

Worked scenario: an unencrypted laptop holding 1,200 patients' records is stolen. Encryption would have made the PHI “secured” and exempt; because it was unencrypted, this is presumptively a breach. Because it exceeds 500 individuals, the entity must notify each individual, OCR, and prominent media within 60 days. The exam answer that says “wait to see if anyone complains” is wrong on its face.

When a question asks for the first action , choose report-contain-preserve. When it asks for the management action after repeated incidents , choose root-cause correction — retraining, workflow redesign, stronger verification, system configuration, encryption, vendor review, or audit monitoring — because repeated misdirected faxes prove a system weakness, not a string of unrelated accidents.

Content of the Notice, Business-Associate Duties, and Civil Penalties

The individual notice itself has required content that the exam may test: a brief description of what happened and the date of the breach and discovery; the types of information involved; steps individuals should take to protect themselves; what the entity is doing to investigate, mitigate, and prevent recurrence; and contact procedures. Notice goes by first-class mail (or email if the patient agreed), and if contact information is insufficient for 10 or more individuals, the entity must post a substitute notice on its website for 90 days or use major media.

Business associates add a layer. When a vendor that creates, receives, maintains, or transmits PHI suffers a breach, it must notify the covered entity, generally within 60 days of discovery, and the business associate agreement (BAA) should specify the timeline and the facts the vendor must supply. The covered entity, not the vendor, usually issues notices to individuals, so HIM and privacy must obtain the affected-patient list quickly to protect the 60-day clock.

The stakes are concrete. HIPAA civil monetary penalties run on a tiered structure based on culpability — from “did not know” at the lowest tier up to “willful neglect, not corrected” at the highest — with substantial per-violation amounts and large annual caps. OCR also publishes large breaches on its public “wall of shame.” These consequences are why the exam rewards disciplined evidence and timely notification over informal cleanup.

  • Notice deadline / trigger Recipient Timing
  • Any breach of unsecured PHI Affected individuals Without unreasonable delay, ≤ 60 days from discovery
  • Breach ≥ 500 individuals HHS OCR ≤ 60 days from discovery
  • Breach ≥ 500 in a state/jurisdiction Prominent media ≤ 60 days from discovery
  • Breach < 500 individuals HHS OCR (annual log) ≤ 60 days after calendar year-end
  • Business associate breach Covered entity Generally ≤ 60 days from discovery

Knowing these rows cold lets you eliminate distractor answers quickly, because most wrong options either omit a required recipient or invent a deadline that does not exist.