# Part 2 recipient, security and breach register

42 CFR Part 2 SUD patient-record confidentiality | Worked example with fictional data

Step: Secure vendors, connected systems and breach response
Owner: Security + Procurement + Privacy + vendor owner
When: Before granting access; rehearse at least annually and after material changes

## Gather first
- Record-flow map
- QSO and other contracts
- Access-control export
- Security incidents
- 42 CFR §2.16
- HHS breach reporting workflow

## How to prepare it
1. List each vendor or recipient, what records it can access, its purpose, user population, hosting location, subcontractors, agreement, incident contact and end-of-service return or destruction process.
2. Record who approved each account and role, the evidence used, the date granted, last review, revocation date and relevant audit-log location. Keep a separate privileged record for actual patient data and do not paste names, records or diagnosis into this tracker.
3. For an incident, log discovery time, affected systems, whether records are unsecured, estimated people and states, containment, investigation owner and the next review time. Keep unknowns open and use estimates when a timely HHS submission is required.
4. At 500 or more affected individuals, assign the HHS OCR report and the 60-calendar-day outside date. Below 500, assign the report due within 60 days after the end of the calendar year of discovery. Track individual notice without unreasonable delay and no later than 60 days; check the more-than-500-per-state media trigger and stricter state or contract duties.
5. Retain each submitted notice, portal transaction number, affected population calculation, addendum, individual notice version, media decision, vendor handoff and corrective action. Close only after counts and delivery evidence reconcile.

## Example

### Fictional incident
Training only. A vendor alert on 7 September 2026 reports a public export containing 512 fictional patient records. The incident lead preserves the vendor notice and starts parallel individual, OCR, state and media threshold checks.

### Threshold calculation
Fictional count: 512 people overall, 508 from State A and 4 from State B. OCR’s 500-person reporting threshold is reached. The State A count also prompts a separate media-notice review under the applicable HIPAA standard.

### OCR transaction
Leave blank until an actual report. The workflow stores the portal transaction number and authorized filer in the restricted incident record, then links later addenda to the original transaction.

### Vendor action
Owner: Privacy vendor manager. Evidence: signed QSO terms, current access list, incident statement, preservation request and a dated confirmation that the public export was removed.

## Review
The incident commander can see the correct thresholds and owners without handling patient-level data in the tracker, and a reviewer can reproduce the notice decisions.

## Handoff
Assign the report and notice owners at incident opening. Reconcile vendor facts against the program’s own affected-population query.

Official reference: HHS OCR Part 2 breach reporting instructions
https://www.hhs.gov/hipaa/for-professionals/breach-notification/breach-reporting/index.html

Use the current rules and any prescribed forms for your engagement.
