Study guide

13.4 Entity Notification Mandates: HHS OCR Reporting (<500 vs. ≥500) and Media Notifications

AHIMA Certified in Healthcare Privacy and Security CHPS

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Healthcare Privacy & Security Legal Framework

1.1 HIPAA Statutory Architecture, HITECH Act, and Enforcement Evolution 1.2 Specialized Federal Privacy Laws: 42 CFR Part 2, GINA, FERPA, and Cures Act Information Blocking 1.3 State Law Preemption Analysis, Stringency Standards, and Multi-State Compliance

2 Chapter 2: Governance, Officer Responsibilities & Compliance Documentation

2.1 Privacy Officer vs. Security Officer: Roles, Governance, and Dual Accountability 2.2 Healthcare Accreditation Standards: Joint Commission, NCQA, and CARF Privacy Requirements 2.3 Documentation, Production, and Record Retention Mandates (State vs. Federal 6-Year Rule)

3 Chapter 3: Notice of Privacy Practices & Patient Rights

3.1 Notice of Privacy Practices (NPP): Content Requirements, Distribution, and Acknowledgment 3.2 Individual Right of Access: Timelines, Digital Formats, and Fee Limitations 3.3 Patient Rights: Amendments, Accounting of Disclosures, and Restriction Requests 3.4 Operational Workflows for Managing Patient Rights and Dispute Resolution

4 Chapter 4: Designated Record Sets, Special Protections & Release Protocols

4.1 Defining the HIPAA Designated Record Set (DRS) Across Clinical and Billing Systems 4.2 Special Privacy Protections: Mental Health, Psychotherapy Notes, SUD Records, and Reproductive Healthcare 4.3 Legal Demands for PHI: Subpoenas, Court Orders, Warrants, and Law Enforcement Inquiries 4.4 Verification Protocols for Requestor Identity, Legal Authority, and Release of Information (ROI)

5 Chapter 5: Minimum Necessary, De-Identification & Research Disclosures

5.1 Minimum Necessary Standard: Protocols, Role-Based Access, and Mandatory Exceptions 5.2 De-Identification Methodologies: Safe Harbor 18 Identifiers vs. Formal Expert Determination 5.3 PHI in Clinical Research: IRB Waivers, Preparatory to Research, Decedents, and Limited Data Sets (DUA)

6 Chapter 6: Business Associates, Contracts & Workforce Training

6.1 Business Associate Agreements (BAA): Mandatory Provisions, Subcontractor Flow-Down, and Liability 6.2 Vendor Risk Management and Service Level Agreements (SLAs) for Health Data 6.3 Workforce Privacy and Security Training: Curriculum Design, Delivery, and Retraining Triggers 6.4 Policy Management Lifecycle: Policy Formulation, Regular Review, and Organizational Communication

7 Chapter 7: Information Security Plan & Asset Risk Analysis

7.1 Developing and Maintaining an Organizational Information Security Plan (ISP) 7.2 Hardware, Software, and Sensitive Data Asset Inventories and Criticality Categorization 7.3 HIPAA Security Rule Risk Analysis: Threat Identification, Vulnerabilities, and NIST SP 800-30 Alignment

8 Chapter 8: Access Control Systems, Authentication & Emergency Operations

8.1 Access Authorization and Privilege Management: Role-Based (RBAC) and Attribute-Based Controls 8.2 Authentication Architectures: Multi-Factor Authentication (MFA), Passwords, and Identity Proofing 8.3 Emergency Access Protocols: "Break-Glass" Workflows, Documentation, and Post-Event Review 8.4 Information System Activity Review: Audit Logs, Access Tracking, and Anomaly Monitoring

9 Chapter 9: Technical Safeguards, Cryptography & Network Security

9.1 Data Encryption Standards: In Transit (TLS) vs. At Rest (AES-256) and FIPS Validation 9.2 Network Architecture Security: Firewalls, DMZ, Segmentation, and Wireless Protections 9.3 Secure External Data Transmission: Direct Messaging, SFTP, APIs, and FHIR Security 9.4 Event Triggering, Intrusion Detection/Prevention (IDS/IPS), and Security Information Event Management (SIEM)

10 Chapter 10: Physical Safeguards, Media Controls & Facility Security

10.1 Facility Access Controls: Visitor Policies, Physical Access Tracking, and Building Security 10.2 Workstation Use and Security: Screen Privacy, Physical Placement, and Clean Desk Standards 10.3 Media Control Lifecycle: Receipt, Movement, Re-Use, and Sanitization/Destruction (NIST SP 800-88)

11 Chapter 11: Business Continuity, Disaster Recovery & Contingency Planning

11.1 Contingency Planning Frameworks: Business Impact Analysis (BIA) and Emergency Mode Operations 11.2 Data Backup Plans, Redundancy Architectures, and Off-Site Storage Strategies 11.3 Disaster Recovery and Testing: RTO, RPO, Downtime Procedures, and Restoration Validation

12 Chapter 12: Incident Response, Investigation Protocols & Mitigation

12.1 Security and Privacy Incident Intake, Triage, and Response Team (CSIRT/PIRT) Structure 12.2 Investigating Privacy and Security Complaints: Evidence Gathering and Root-Cause Analysis 12.3 Immediate Containment and Harm Mitigation Strategies for Breaches and Exposures 12.4 Disciplinary Guidelines and Sanctions Enforcement for Workforce Non-Compliance

13 Chapter 13: Federal Breach Notification Rule & Risk Assessment

13.1 Federal Breach Notification Rule Definition, Exceptions, and Safe Harbors 13.2 The Four-Factor Breach Risk Assessment Methodology and Documentation 13.3 Individual Notification Requirements: Content, Timelines (60-Day Clock), and Substitute Notice 13.4 Entity Notification Mandates: HHS OCR Reporting (<500 vs. ≥500) and Media Notifications

14 Chapter 14: Compliance Auditing, External Investigations & Enforcement Tiers

14.1 Ongoing Compliance Auditing, Risk Metrics, and Executive/Board Governance Reporting 14.2 Managing External Investigations: Responding to OCR Inquiries, Subpoenas, and State AGs 14.3 Enforcement Penalties: HIPAA Civil Monetary Penalty Tiers, Resolution Agreements, and Criminal Sanctions

13.4 Entity Notification Mandates: HHS OCR Reporting (<500 vs. ≥500) and Media Notifications

Key Takeaways Explain This Topic AI

Under 45 CFR § 164.406, breaches of unsecured PHI affecting more than 500 residents of a single State or jurisdiction mandate notification to prominent media outlets serving that jurisdiction without unreasonable delay and within sixty (60) calendar days of discovery.

Under 45 CFR § 164.408(b), breaches affecting 500 or more individuals must be reported electronically to the Secretary of HHS without unreasonable delay and in no case later than sixty (60) calendar days after discovery, triggering mandatory inclusion on the public HHS OCR Breach Portal ('Wall of Shame').

Under 45 CFR § 164.408(c), breaches affecting fewer than 500 individuals must be reported electronically to the Secretary of HHS no later than sixty (60) days following the end of the calendar year in which the breach was discovered (by March 1 or March 2 of the subsequent year).

Under 45 CFR § 164.410, a business associate that discovers a breach of unsecured PHI must notify the covered entity without unreasonable delay and in no case later than sixty (60) calendar days after discovery, identifying each affected individual and providing essential breach details.

While federal law provides a 60-day outer ceiling for business associate breach reporting, healthcare Business Associate Agreements (BAAs) routinely mandate expedited reporting within 24 to 72 hours, which contractually supersedes the regulatory ceiling without violating federal law.

Last updated: September 2026

Entity Notification Mandates: HHS OCR Reporting and Media Notifications

While notifying affected individuals under 45 CFR § 164.404 represents the individual-facing core of breach response, the HITECH Act established an aggressive public accountability and regulatory oversight infrastructure. Healthcare organizations that experience a breach of unsecured protected health information must navigate mandatory entity-level disclosures to prominent media outlets , the Secretary of the Department of Health and Human Services (HHS) , and between business associates and covered entities .

For the AHIMA CHPS candidate, mastering entity-level notifications requires an exact understanding of numerical thresholds, geographical qualifiers, distinct reporting calendars, and the operational liabilities associated with the HHS Office for Civil Rights (OCR) public breach registry. A failure in entity-level reporting carries severe consequences: it routinely triggers immediate federal compliance investigations, extensive subpoena requests, and crippling Civil Monetary Penalties.

Media Notification Mandates (45 CFR § 164.406)

Under 45 CFR § 164.406(a) , the requirement to notify public news media is governed by a precise statutory threshold:

"For a breach of unsecured protected health information affecting more than 500 residents of a State or jurisdiction, a covered entity shall notify prominent media outlets serving the State or jurisdiction."

Critical Statutory Elements for Exam Analysis

The Geographical Qualifier ("Residents of a State or Jurisdiction"):

The media notification threshold is NOT simply 500 total individuals nationwide. It is triggered only when a breach affects more than 500 residents of a single State or jurisdiction (e.g., a U.S. State, the District of Columbia, Puerto Rico, or a U.S. territory).

Mind the boundary wording. § 164.406(a) says "more than 500 residents," so the media trigger begins at 501 . By contrast, § 164.408(b) says "500 or more individuals," so immediate HHS reporting begins at 500 . A breach affecting exactly 500 residents of one state therefore requires contemporaneous notice to the Secretary but no media notice — a favorite boundary-value distractor.

Exam Scenario: A nationwide cloud radiology provider suffers a breach compromising 800 individuals distributed across three states: 300 patients in New York, 300 patients in New Jersey, and 200 patients in Connecticut. Does the covered entity have to notify the media under 45 CFR § 164.406? NO. Although the breach affects 800 total individuals, it does not affect more than 500 residents in any single State or jurisdiction. Media notice is not mandated by federal law (though individual notices and HHS OCR reporting are mandatory).

Timeline: Notice to prominent media outlets must be provided without unreasonable delay and in no case later than sixty (60) calendar days after discovery of the breach.

Content Requirements: Under § 164.406(c), the media notification must include the exact same five mandatory elements required for individual notice under § 164.404(c) (incident description, types of PHI, individual mitigation advice, entity investigation/remediation steps, and a toll-free contact number).

Nature of Media Outlets: The covered entity must issue a formal press release to prominent media outlets (e.g., major metropolitan newspapers, leading television news stations, and prominent regional wire services) serving the affected jurisdiction. Media notice does NOT substitute for individual notice; it is a concurrent, independent statutory obligation.

Notification to the Secretary of HHS (45 CFR § 164.408)

Under 45 CFR § 164.408 , covered entities must notify the Secretary of HHS of all breaches of unsecured protected health information. However, the statute establishes a dramatic bifurcation in reporting timelines based on whether the breach affects 500 or more individuals versus fewer than 500 individuals : HHS OCR Breach Reporting Timelines (45 CFR § 164.408):

  • Breach of Unsecured PHI Confirmed
  • │
  • ┌────────────────────────┴────────────────────────┐
  • │ │
  • ▼ ▼
  • ┌───────────────────────────┐ ┌───────────────────────────┐
  • │ Major Breach: │ │ Minor Breach: │
  • │ 500 or More Individuals │ │ Fewer Than 500 Individuals│
  • │ (≥500 Patients) │ │ (<500 Patients) │
  • └─────────────┬─────────────┘ └─────────────┬─────────────┘
  • │ │
  • ▼ ▼
  • ┌───────────────────────────┐ ┌───────────────────────────┐
  • │ 60-DAY CLOCK: │ │ ANNUAL LOG REPORTING: │
  • │ • Report electronically │ │ • Report electronically │
  • │ WITHOUT UNREASONABLE │ │ no later than │
  • │ DELAY and ≤ 60 DAYS │ │ 60 CALENDAR DAYS │
  • │ from discovery date │ │ after calendar year end │
  • │ • Immediate listing on │ │ • Deadline: MARCH 1 │
  • │ public OCR Breach Portal│ │ (or March 2 leap year) │
  • │ • Triggers automatic OCR │ │ • Aggregated compliance │
  • │ formal investigation │ │ tracking │
  • └───────────────────────────┘ └───────────────────────────┘
  • 1. Major Breaches: 500 or More Individuals (45 CFR § 164.408(b))

Statutory Mandate: For breaches affecting 500 or more individuals (regardless of geographic distribution), the covered entity must notify the Secretary without unreasonable delay and in no case later than sixty (60) calendar days after discovery .

Electronic Submission: Reports must be submitted electronically through the official HHS OCR Breach Reporting web portal.

The OCR Breach Portal ("Wall of Shame"): Under Section 13402(e)(4) of the HITECH Act, the Secretary is legally mandated to publicly post a list of all covered entities and business associates that submit breach reports affecting 500 or more individuals. This public database—commonly referred to in industry and on exams as the "Wall of Shame"—displays the entity's name, state, number of affected individuals, breach date, and breach type (e.g., Hacking/IT Incident, Unauthorized Access/Disclosure, Theft, Loss).

Automatic Regulatory Investigation: Any breach report submitted to OCR involving 500 or more individuals automatically opens a formal compliance investigation by OCR regional investigators. Investigators immediately issue document requests demanding the entity's risk analysis, policies, workforce training records, and technical audit logs.

2. Minor Breaches: Fewer Than 500 Individuals (45 CFR § 164.408(c))

Statutory Mandate: For breaches of unsecured PHI affecting fewer than 500 individuals, the covered entity is not required to report to the Secretary within 60 days. Instead, the entity must maintain an internal log of all such breaches and report them to the Secretary electronically no later than sixty (60) days after the end of each calendar year .

Calculating the Annual Deadline:

The calendar year ends on December 31 .

Sixty (60) days following December 31 places the federal reporting deadline on March 1 of the subsequent year (or March 2 in a leap year).

Example: A breach affecting 45 individuals discovered on February 10, 2026, does not have to be reported to HHS OCR until March 1, 2027 . However, the individual breach notices must still be sent within 60 calendar days of discovery (by April 11, 2026)!

Business Associate Reporting Mandates (45 CFR § 164.410)

In modern healthcare, vast quantities of protected health information are processed, stored, and managed by third-party vendors acting as Business Associates (BAs) under 45 CFR § 160.103. Under the HITECH Act and 45 CFR § 164.410 , business associates are directly subject to federal breach notification obligations:

1. Statutory Reporting Timeline

Under 45 CFR § 164.410(b) , a business associate that discovers a breach of unsecured PHI must notify the covered entity without unreasonable delay and in no case later than sixty (60) calendar days after discovery of the breach.

2. Mandatory Information Furnished by the Business Associate

Under § 164.410(c), the business associate's notification to the covered entity must include:

The identification of each individual whose unsecured PHI has been, or is reasonably believed by the business associate to have been, accessed, acquired, used, or disclosed;

A description of the incident, dates of breach and discovery, types of PHI involved, and immediate mitigation actions taken;

Any other available information that the covered entity is required to include in the individual notice under § 164.404(c).

3. Agency Law and the Imputation of Discovery Date

A crucial legal concept on the CHPS exam is the interaction between federal agency law and breach discovery under 45 CFR § 164.404(a)(2) :

Independent Contractor vs. Legal Agent: If the business associate is determined to be a legal agent of the covered entity under federal common law of agency (i.e., the covered entity exercises operational control over the day-to-day manner and means of the BA's performance), knowledge of the breach by the business associate is legally imputed to the covered entity on that exact same day .

The Operational Peril: If a business associate acting as an agent discovers a breach on Day 0, but waits until Day 58 to notify the covered entity, the covered entity's 60-day clock has already been ticking for 58 days! The covered entity would be left with only 48 hours to notify individuals and HHS, creating an impossible operational deadline.

Contractual Shortening of Reporting Windows: Because of this extreme regulatory risk, covered entities almost never rely on the statutory 60-day ceiling in their contracts. Standard healthcare Business Associate Agreements (BAAs) legally bind business associates to report suspected or confirmed breaches within 24 hours, 48 hours, 72 hours, or 5 business days . Contracting parties are fully permitted under federal law to establish more stringent reporting covenants than HIPAA's statutory minimums.

Master Entity Notification Comparison Matrix

Recipient Statutory Threshold Federal Statutory Deadline Statutory Basis Public Disclosure Impact

Affected Individuals 1 or more individuals Without unreasonable delay; ≤ 60 calendar days from discovery 45 CFR § 164.404 Private written letter; potential public website notice if ≥10 addresses missing

Prominent Media Outlets > 500 residents (501+) of a single State or jurisdiction Without unreasonable delay; ≤ 60 calendar days from discovery 45 CFR § 164.406 Public press release to regional broadcast/print news media

Secretary of HHS (Major) ≥ 500 individuals total across all jurisdictions Without unreasonable delay; ≤ 60 calendar days from discovery 45 CFR § 164.408(b) Listed immediately on public HHS OCR Breach Portal ("Wall of Shame"); triggers OCR audit

Secretary of HHS (Minor) < 500 individuals total No later than 60 calendar days after calendar year end (March 1) 45 CFR § 164.408(c) Archived in internal annual log; aggregated into annual OCR statistical enforcement report

Business Associate to CE Any breach of unsecured PHI Without unreasonable delay; ≤ 60 calendar days (often 24–72 hrs by BAA) 45 CFR § 164.410 Internal business notification; triggers covered entity's downstream external notice clocks

CHPS Exam Tips and Common Candidate Traps

Tip

Exam Tip: March 1 Is the Minor Breach Reporting Date Always remember the annual HHS reporting deadline calculation for minor breaches (<500 individuals). The statute states "no later than 60 days after the end of the calendar year" (45 CFR § 164.408(c)). December 31 plus 60 days equals March 1 (or March 2 in a leap year). Watch for distractors claiming December 31, January 31, or 60 days from incident date.

Warning

Candidate Trap: Total Count vs. Single State Media Threshold An exam scenario will often state that a breach affected 650 patients nationwide, but only 250 reside in California, 200 in Nevada, and 200 in Arizona. The question asks whether media notification is mandatory. The answer is NO under 45 CFR § 164.406 because the breach did not affect more than 500 residents of any single State. However, notice to the Secretary of HHS is mandatory within 60 days under § 164.408(b) because the total nationwide count exceeds 500!

Caution

Candidate Trap: Contractual BAA Windows vs. Statutory Ceilings When a question asks for the statutory federal maximum time a business associate has to report a breach to a covered entity, the answer is 60 calendar days under 45 CFR § 164.410(b). If the question asks what standard practice or a specific BAA requires, it is typically 24–72 hours. Do not confuse the federal statutory ceiling with institutional contract provisions.

Loading diagram... Comprehensive Healthcare Entity Breach Escalation and Notification Architecture