Regulation · Healthcare · US law
HIPAA compliance: Security Rule safeguards, Privacy Rule and breach notification
HIPAA is the US Health Insurance Portability and Accountability Act of 1996. Its rules, in 45 CFR Parts 160 and 164, require covered entities and business associates to protect health information: the Privacy Rule limits use and disclosure, the Security Rule sets safeguards for electronic PHI, and the Breach Notification Rule sets reporting deadlines.
What you need to know about HIPAA
Who must comply with HIPAA?
HIPAA is law; whether it applies depends on your role with health information.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does HIPAA require?
HIPAA requires you to limit how PHI is used and disclosed, protect electronic PHI with administrative, physical and technical safeguards, sign business associate agreements, and report breaches on time.
Privacy Rule
Uses and disclosures, minimum necessary, patient rights, notices.
In QULDEX: Disclosure and request logsAdministrative safeguards
Risk analysis, workforce, training, incidents, contingency, BAAs.
In QULDEX: Risk analysis in the risk registerPhysical safeguards
Facilities, workstations, devices and media.
In QULDEX: Disposal and access evidenceTechnical safeguards
Access, audit controls, integrity, authentication, transmission.
In QULDEX: Log and access reviews scheduledOrganisational and documentation
BAA terms, policies, six-year retention.
In QULDEX: Retention enforced in the vaultBreach Notification Rule
Individuals, media, HHS and business associate notices.
In QULDEX: 60-day clock per breachEnforcement Rule
OCR investigations and tiered civil penalties.
In QULDEX: Audit trail ready for OCRWhat are the HIPAA Security Rule safeguards?
The Security Rule has standards in four groups of safeguards plus documentation, and the Breach Notification Rule adds four notice requirements. Select any standard to see what it asks for, typical evidence and the matching NIST CSF and ISO 27001 controls.
Showing up to 6 per group. Search, filter, or open a group to see all 25.
Administrative safeguards 9
164.308(a)(1)Security management processRun a risk analysis and risk management, apply a sanction policy and review system activity.
In QULDEXThe risk analysis lives in the risk register and is refreshed on schedule.
- Typical evidence
- Risk analysis, risk management plan
- Maps to
- NIST ID.RAISO 27001 6.1.2
164.308(a)(2)Assigned security responsibilityName a security official responsible for the Security Rule.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Security official appointment
- Maps to
- ISO 27001 A.5.2
164.308(a)(3)Workforce securityMake sure workforce members have appropriate access to ePHI and remove it when they leave.
In QULDEXJoiner and leaver tickets attach as evidence.
- Typical evidence
- Access provisioning records
- Maps to
- ISO 27001 A.5.18SOC 2 CC6.2
164.308(a)(4)Information access managementAuthorise access to ePHI based on role and need.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Access authorisation records
- Maps to
- ISO 27001 A.5.15
164.308(a)(5)Security awareness and trainingTrain the workforce, including on malware, log-in monitoring and passwords.
In QULDEXTraining completion is imported and checked against headcount.
- Typical evidence
- Training records
- Maps to
- ISO 27001 A.6.3NIST PR.AT
164.308(a)(6)Security incident proceduresIdentify, respond to, mitigate and document security incidents.
In QULDEXIncidents are logged with response steps and evidence.
- Typical evidence
- Incident log
- Maps to
- ISO 27001 A.5.24–A.5.26NIST RS.MA
164.308(a)(7)Contingency planKeep data backup, disaster recovery and emergency mode plans, and test them.
In QULDEXBackup and recovery tests are scheduled with results attached.
- Typical evidence
- Contingency plan, test results
- Maps to
- ISO 27001 A.5.29A.8.13NIST RC.RP
164.308(a)(8)EvaluationEvaluate security periodically and after operational or environmental changes.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Evaluation reports
164.308(b)(1)Business associate contractsGet satisfactory assurances from business associates through a written contract.
In QULDEXEach business associate record links its BAA.
- Typical evidence
- BAAs
- Maps to
- ISO 27001 A.5.20NIST GV.SC
Physical safeguards 4
164.310(a)(1)Facility access controlsLimit physical access to systems and facilities holding ePHI.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Badge logs, facility security plan
- Maps to
- ISO 27001 A.7.2
164.310(b)Workstation useSpecify how workstations that access ePHI should be used.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Workstation policy
164.310(c)Workstation securityPhysically safeguard workstations that access ePHI.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
164.310(d)(1)Device and media controlsControl receipt, movement, disposal and re-use of devices and media with ePHI.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Disposal certificates, media log
- Maps to
- ISO 27001 A.7.10A.7.14
Technical safeguards 5
164.312(a)(1)Access controlAllow access to ePHI only to authorised people and software, with unique IDs and emergency access.
In QULDEXAccess reviews run as recurring tasks; revocations become tracked actions.
- Typical evidence
- Access reviews, unique ID policy
- Maps to
- ISO 27001 A.5.15A.8.5NIST PR.AA
164.312(b)Audit controlsRecord and examine activity in systems that contain ePHI.
In QULDEXLog review evidence is collected on schedule.
- Typical evidence
- Audit log reviews
- Maps to
- ISO 27001 A.8.15SOC 2 CC7.2
164.312(c)(1)IntegrityProtect ePHI from improper alteration or destruction.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Integrity controls
164.312(d)Person or entity authenticationVerify that anyone seeking access to ePHI is who they claim to be.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- MFA settings
- Maps to
- ISO 27001 A.8.5
164.312(e)(1)Transmission securityGuard ePHI sent over networks against unauthorised access.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Encryption in transit
- Maps to
- ISO 27001 A.8.24SOC 2 CC6.7
Organisational and documentation 3
164.314(a)Business associate contract requirementsBusiness associate contracts must include required terms, such as safeguarding ePHI and reporting incidents.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- BAA template review
164.316(a)Policies and proceduresImplement reasonable policies and procedures to comply with the Security Rule.
In QULDEXPolicies are versioned with approvals and linked to standards.
- Typical evidence
- Policy set
164.316(b)(1)Documentation and retentionDocument actions and assessments and keep them for six years.
In QULDEXRetention is enforced on documents in the vault.
- Typical evidence
- Document register
Breach notification 4
164.404Notice to individualsNotify affected individuals without unreasonable delay, and no later than 60 days after discovering a breach of unsecured PHI.
In QULDEXBreaches are logged with a running 60-day clock.
- Typical evidence
- Notification letters
164.406Notice to the mediaNotify prominent media when a breach affects more than 500 residents of a state or jurisdiction.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
164.408Notice to the Secretary (HHS)Notify HHS within 60 days for breaches of 500 or more; log smaller breaches and report them annually.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- HHS breach portal submissions
164.410Notification by a business associateBusiness associates notify the covered entity of breaches without unreasonable delay, within 60 days.
In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.
Nothing matches that search.
Citations follow 45 CFR Part 164. Summaries are QULDEX paraphrases, not legal advice; the eCFR text is the authority. HHS has proposed Security Rule changes; check their status before go-live.
How do you become HIPAA compliant?
There is no HIPAA certification. You confirm your role, run a risk analysis, put safeguards and policies in place, sign BAAs and keep six years of evidence. A first programme usually takes 3 to 9 months.
Confirm your role and map PHI
Decide whether you are a covered entity, business associate or both, and map where PHI and ePHI live.
Run the security risk analysis
Assess risks to the confidentiality, integrity and availability of all ePHI, as 164.308(a)(1) requires.
Put safeguards in place
Implement administrative, physical and technical safeguards, and document decisions on addressable specifications.
Policies, training and BAAs
Write policies, train the workforce and sign business associate agreements.
Test contingency and incident response
Test backups, disaster recovery and incident procedures, and fix what fails.
Independent assessment (optional)
A third party assesses your programme, or you pursue a framework certification such as HITRUST.
Keep it current
On changeUpdate the risk analysisYearlyTraining and evaluation6 yearsKeep documentation
Durations are typical planning ranges from QULDEX delivery, not legal requirements.
Which documents does HIPAA require?
OCR asks for these first in an investigation. The risk analysis is the most common gap in enforcement actions.
| Document or record | Citation | Where it lives in QULDEX |
|---|---|---|
| Security risk analysis | 164.308(a)(1) | Risk register |
| Risk management plan | 164.308(a)(1) | Risk register |
| Security official designation | 164.308(a)(2) | Program setup |
| Training records | 164.308(a)(5) | Evidence vault |
| Incident log and responses | 164.308(a)(6) | CAPA automation |
| Contingency plan and test results | 164.308(a)(7) | Evidence vault |
| Business associate agreements | 164.308(b), 164.314 | Vendor register |
| Policies and procedures | 164.316 | Evidence vault · policy library |
| Breach notifications and HHS submissions | 164.404–164.410 | CAPA automation |
| Notice of privacy practices | 164.520 | Evidence vault |
Keep documentation for six years from creation or last effective date (164.316(b)(2)).
How long does HIPAA compliance take and what drives the effort?
A first programme usually takes 3 to 9 months, then runs continuously. Effort depends on how many systems hold ePHI, how many business associates you have and your incident history.
Where the time goes
Bars show the upper end of each range on one scale (5 months = full width).
What changes the effort
- Systems with ePHI: each needs safeguards and evidence
- Business associates: every one needs a BAA and oversight
- Workforce size: training and access management scale with headcount
- Existing SOC 2 or ISO 27001: reused controls cover much of the Security Rule
- Incident history: past breaches bring OCR scrutiny
How ready are you for a HIPAA review?
OCR and healthcare customers check these eight things first. Nothing you enter leaves this page.
How HIPAA maps to NIST CSF 2.0, ISO 27001 and SOC 2
HHS has published a crosswalk between the HIPAA Security Rule and the NIST Cybersecurity Framework, and most safeguards have ISO 27001 and SOC 2 counterparts. One tested control can support all of them.
HIPAA Privacy Rule vs Security Rule
| Privacy Rule | Security Rule | |
|---|---|---|
| Covers | All PHI, in any form | Electronic PHI (ePHI) only |
| Focus | Who can use and disclose PHI, and patients' rights | Safeguards that protect ePHI |
| Key duties | Minimum necessary, notices, access requests, authorisations | Risk analysis, administrative, physical and technical safeguards |
| Applies to | Covered entities; business associates by contract | Covered entities and business associates directly |
| Citation | 45 CFR 164 Subpart E | 45 CFR 164 Subpart C |
| In QULDEX | QULDEX tracks Privacy Rule requests and Security Rule safeguards in one programme with shared evidence. | |
Safeguard crosswalk
| HIPAA Security Rule | NIST CSF 2.0 | ISO 27001:2022 | SOC 2 | Shared evidence |
|---|---|---|---|---|
| 164.308(a)(1) Risk analysis | ID.RA | 6.1.2 | CC3.2 | Risk analysis |
| 164.308(a)(3) Workforce security | PR.AA | A.5.18 | CC6.2 | Access provisioning |
| 164.308(a)(5) Training | PR.AT | A.6.3 | CC1.4 | Training records |
| 164.308(a)(6) Incidents | RS.MA | A.5.24–A.5.26 | CC7.3–CC7.5 | Incident log |
| 164.308(a)(7) Contingency | RC.RP | A.5.29 · A.8.13 | A1.2–A1.3 | Recovery tests |
| 164.308(b) BAAs | GV.SC | A.5.20 | CC9.2 | BAAs |
| 164.310(d) Device and media | PR.DS | A.7.10 · A.7.14 | CC6.5 | Disposal records |
| 164.312(a) Access control | PR.AA | A.5.15 · A.8.5 | CC6.1 | Access reviews |
| 164.312(b) Audit controls | DE.CM | A.8.15 | CC7.2 | Log reviews |
| 164.312(e) Transmission | PR.DS | A.8.24 | CC6.7 | Encryption settings |
Indicative mapping aligned to HHS's HIPAA-to-NIST crosswalk approach. The full crosswalk is in the QULDEX control library.
How QULDEX runs HIPAA compliance from risk analysis to audit
QULDEX is HIPAA compliance and audit management software built from EGV Group's audit delivery, used by covered entities, business associates and the assessors who test them. Pick your role to see who does what.
For healthcare organisations and their vendors.
- Role and PHIMap PHIPHI inventory linked to systems and vendors
- Risk analysisAssess risksRisk analysis refreshed on schedule
- SafeguardsRun the safeguardsStandards with owners and evidence requests
- BAAsSign agreementsVendor register with BAAs
- BreachesNotify on timeBreach log with a 60-day clock
- AuditProve complianceControlled, logged evidence for OCR and customers
For HIPAA privacy and security officers and consultants.
- Role and PHIRun the gap assessmentA reusable HIPAA gap template
- Risk analysisFacilitate the analysisRisk analysis templates
- SafeguardsReview evidenceReview and approval states
- BAAsReview contractsBAA status per vendor
- BreachesDecide on notificationDecision records per breach
- AuditReport to leadershipReports from live data
For third parties assessing HIPAA programmes.
- PlanningAgree scopeScope and PHI inventory in a standard format
- FieldworkReview evidenceView-only evidence access with download control and an access log
- TestingSample safeguardsSampling per standard
- FindingsRecord gapsFindings per citation
- ReportIssue the assessmentTraceable workpapers
- Follow-upTrack fixesFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →HIPAA questions people ask
Who needs to comply with HIPAA?
Covered entities (healthcare providers that bill electronically, health plans and clearinghouses) and their business associates and subcontractors that handle PHI.
Is there an official HIPAA certification?
No. HHS does not certify organisations or recognise any HIPAA certification. You can get an independent assessment or a framework certification such as HITRUST.
What are the three HIPAA safeguards?
Administrative, physical and technical safeguards under the Security Rule, plus organisational and documentation requirements.
What is the HIPAA breach notification deadline?
Notify affected individuals without unreasonable delay and no later than 60 days after discovery. Breaches of 500 or more also go to HHS and, by state, to the media.
What is a business associate agreement?
A contract a covered entity signs with a vendor that handles PHI on its behalf, setting how the vendor must protect PHI and report incidents.
What is the difference between required and addressable specifications?
Required specifications must be implemented. Addressable ones must be implemented if reasonable and appropriate, or you document why not and what you do instead. HHS has proposed changes to this; check the current rule.
Can QULDEX run HIPAA alongside SOC 2 and ISO 27001?
Yes. Safeguards are mapped once to NIST CSF, ISO 27001 and SOC 2, so one evidence set supports each.
References
- 45 CFR Part 160 and Part 164 (Privacy, Security and Breach Notification Rules). ecfr.gov
- HHS OCR, Guidance on Risk Analysis Requirements under the HIPAA Security Rule. hhs.gov
- HHS, HIPAA Security Rule Crosswalk to the NIST Cybersecurity Framework. hhs.gov
- NIST SP 800-66 Rev. 2, Implementing the HIPAA Security Rule. nist.gov
- HHS, Breach Notification Rule guidance. hhs.gov
Reviewed by
Page history
- : Rebuilt with standards explorer, breach notification rules, compliance path and readiness check
- : Page first published
Find your HIPAA gaps in 15 minutes
Answer a short readiness check and get a gap summary by standard. No sales call needed to see the result.