Start hereMap covered roles and ePHI
~91 days leftOpen step
Guide library
Regulation North America

HIPAA

U.S. HIPAA Privacy, Security and Breach Notification Rules

Identify covered health information and operate safeguards and breach response.

Who it applies to

Covered entities and business associates, with Security Rule safeguards applying to electronic protected health information.

What you’ll produce

Documented privacy and security controls, business associate agreements and breach decisions.

Confirm whether the organization is a covered entity, business associate or subcontractor. Check state rules and 42 CFR Part 2 where applicable.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which activities create covered responsibilities?
Have Privacy and Legal identify covered entity, business associate and subcontractor activities. Determine where state law, Part 2 requirements or insurer contracts create separate tasks.
Who owns the security risk analysis?
Assign a named Security Official and a privacy lead appropriate to the organization’s role. Fund discovery of ePHI and technical remediation across legacy and outsourced systems.
Who receives and acts on incidents?
Make sure vendor contracts and incident procedures give the incident lead a reachable contact and appropriate reporting deadlines. Agree who evaluates incidents and can authorize notices.

How to spend the first week

  1. Trace one patient record through intake, clinical software, messaging, claims, backups and vendors. Note ePHI on endpoints and in temporary exports.
  2. Match activities to the applicable HIPAA roles and BAA coverage. Verify with Procurement what each vendor actually handles.
  3. Review the first risk analysis entries with clinical and security owners. Schedule a backup restore and an incident exercise using test data.

What to review each week

Report high residual risks, stale access, unresolved vendor obligations, restoration tests awaiting verification and incidents with deadlines.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

HIPAA kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Map covered roles and ePHI · Privacy officer + security officer [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Trace one patient record through intake, clinical software, messaging, claims, backups and vendors. Note ePHI on endpoints and in temporary exports.
2. Match activities to the applicable HIPAA roles and BAA coverage. Verify with Procurement what each vendor actually handles.
3. Review the first risk analysis entries with clinical and security owners. Schedule a backup restore and an incident exercise using test data.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Who is the covered entity or business associate for the work?
  • Can you locate all electronic protected health information, including backups and service providers?

Worked scenario

A care provider’s billing vendor reports unusual access to a download link. Each party records the facts and timing, checks the agreement, and assigns responsibility for deciding and sending any required notices.

What to read next

FROM THE SOURCE

Cases and numbers

Enforcement settlements · 23 April 2026

$1.165MTotal payments across four settlements

Risk analysis was a common issue across four ransomware investigations

HHS OCR reported that the four breaches affected more than 427,000 individuals. The settlements included corrective action plans and two years of monitoring.

What to check Check that your risk analysis accounts for the actual systems holding electronic protected health information. Connect assessed risks to dated decisions and evidence that safeguards operate.

HHS OCR announcement and case details (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Within 60 calendar days

    Outer limit for individual notice

    For a reportable breach of unsecured PHI, notify affected individuals without unreasonable delay and within 60 days of discovery. Other notice rules can differ.

    Official reference (opens in a new tab)
Plan evidence for HIPAA and other programs
The whole journeyabout 91 days across 4 steps
  1. 01Map covered roles and ePHIPrivacy officer + security officer · ~14 days
  2. 02Analyze risks and apply safeguardsSecurity officer + IT · ~35 days
  3. 03Operate privacy and access workflowsPrivacy officer + care operations · ~28 days
  4. 04Assess and report breachesIncident response + privacy officer · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map covered roles and ePHIPrivacy officer + security officerAt initiationSet a start dateRole determination; ePHI inventory; BAA registerOpen
Analyze risks and apply safeguardsSecurity officer + ITBefore use and on material changesSet a start dateRisk analysis; Risk management plan; Safeguard recordsOpen
Operate privacy and access workflowsPrivacy officer + care operationsOngoingSet a start dateTraining evidence; Access workflows; Policy setOpen
Assess and report breachesIncident response + privacy officerUpon discovery and on the applicable scheduleSet a start dateIncident assessment; Notifications; Breach registerOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map covered roles and ePHI

    Who Privacy officer + security officer When At initiation

    Trace ePHI across storage, transmission and vendors. Identify entity roles and which relationship requires a business associate agreement.

    How to do this step

    Before you start

    Clinical and business workflows, data inventory, vendor contracts, service descriptions and backup locations.

    1. Identify ePHI that is created, received, maintained or transmitted. Trace representative records to exports, support, archives and vendors.
    2. Document the organization’s role by activity and identify where a BAA or subcontractor agreement is required. Compare signed terms with real services and access.
    3. Give each data flow a business and technical owner. Record uncertain scope and resolve it before sending ePHI to a new recipient.

    What a reviewer should see

    The ePHI inventory includes encrypted backups and export folders, with owners, systems and relevant vendor agreements.

    When to escalate

    Escalate undisclosed ePHI copies, a missing agreement or a third party that cannot explain its handling.

    What to produce

    Role determinationMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    ePHI inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    BAA registerMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.

    Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.

  2. 02

    Analyze risks and apply safeguards

    Who Security officer + IT When Before use and on material changes

    Evaluate threats to confidentiality, integrity and availability. Implement administrative, physical and technical safeguards and document implementation decisions.

    How to do this step

    Before you start

    ePHI inventory, threat and incident history, configuration evidence, vendor dependencies and existing safeguards.

    1. For each significant ePHI location, identify likely threats and vulnerabilities, present safeguards, likelihood, impact and the resulting risk level.
    2. Assign treatment dates and interim protections. For applicable addressable specifications, assess what is reasonable and appropriate and document alternatives or decisions as required.
    3. Test high-impact safeguards with authorized test data. Show who had access, what happened during a restore or alert and how deviations were handled.

    What a reviewer should see

    The ransomware scenario for a clinical platform maps to the backup design, a dated restore test, actual recovery result and approved treatment plan.

    When to escalate

    Raise risks to patient care or confidentiality that exceed approved tolerances, including inaccessible backups or unmanaged privileged access.

    What to produce

    Risk analysisSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.

    Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.

    Risk management planMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Safeguard recordsSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

  3. 03

    Operate privacy and access workflows

    Who Privacy officer + care operations When Ongoing

    Train staff, manage authorized uses and disclosures, handle individual rights and maintain policies and sanctions.

    How to do this step

    Before you start

    Current policy set, workforce roles and roster, request procedures and identity-management evidence.

    1. Walk through a new hire, transfer and termination. Check that access corresponds to the approved role and that disablement occurred when expected.
    2. Train teams on the incidents and requests they actually encounter. Track completion and demonstrate that Support, Privacy and IT route cases to the correct owner.
    3. Test a patient request or applicable business associate support request. Capture verification, location of records, response decision and timeliness.

    What a reviewer should see

    One test case shows workforce termination, revoked access in each in-scope system, reviewer sign-off and exceptions.

    When to escalate

    Escalate a workforce member with unexpected access or a request likely to miss an applicable deadline.

    What to produce

    Training evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Access workflowsMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

    Policy setMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

  4. 04

    Assess and report breaches

    Who Incident response + privacy officer When Upon discovery and on the applicable schedule

    Evaluate breach presumptions and exceptions. Document risk analysis and notify individuals, HHS, media or covered entities when their respective thresholds apply.

    How to do this step

    Before you start

    Incident timeline, affected records, disclosure facts, access logs, BAAs and current notification contacts.

    1. Capture discovery, mitigation and who potentially received or accessed the information. Notify the appropriate internal owner and covered entity or upstream partner as required.
    2. For an impermissible use or disclosure, document the applicable exception or the breach risk assessment where used. Record the nature of PHI, unauthorized recipient, actual acquisition or viewing, and mitigation.
    3. Keep notices, receipts and deadline calculations or the approved basis for non-notification. Check contractual and other applicable reporting routes in parallel.

    What a reviewer should see

    The case record links evidence to the reporting decision, responsible party, affected population and notice copies or documented rationale.

    When to escalate

    Escalate promptly if the facts involve unsecured PHI, patient harm or an approaching notification or contractual deadline.

    What to produce

    Incident assessmentSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.

    Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.

    NotificationsMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

    Breach registerSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.

    Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes