C1.ai to join Workday. Read the announcement →

Identity for HIPAA Compliance: How Identity Governance Protects PHI

Identity for HIPAA Compliance: How Identity Governance Protects PHI

Identity for HIPAA compliance means controlling, reviewing, and proving who and what can reach protected health information. The HIPAA Security Rule requires covered entities and business associates to grant access to ePHI only to authorized users, record activity in systems that hold it, and limit access to what each role needs. Identity governance turns those requirements into repeatable controls: role-based access, user access reviews, lifecycle automation, break-glass procedures, and audit evidence for humans and AI agents.

What is identity for HIPAA compliance?#

Identity for HIPAA compliance is the set of identity governance controls a healthcare organization uses to meet HIPAA's access requirements. It answers three questions for every user, service account, and AI agent: who has access to PHI, why they have it, and what evidence proves the access was authorized, reviewed, and removed on time.

HIPAA requirements mapped to identity controls#

Most HIPAA access obligations map directly to an identity governance control. The table below pairs each Security Rule and Privacy Rule requirement with the control that satisfies it and the evidence an auditor or OCR investigator will ask for. For a task-level list, see the HIPAA compliance checklist for IT and security teams. "R" means required and "A" means addressable. Addressable does not mean optional; HHS states that plainly in its Security Rule summary.

HIPAA requirementCitationIdentity controlEvidence to keep
Access control: access only for persons or software programs granted access rights45 CFR 164.312(a)(1)Centralized access policy across EHR, clinical, and business appsPolicy, entitlement inventory, grant records
Unique user identification (R)164.312(a)(2)(i)One identity per person and per agent; no shared loginsAccount-to-identity mapping, orphaned account reports
Emergency access procedure (R)164.312(a)(2)(ii)Break-glass access with time limits and post-event reviewBreak-glass log, justification, reviewer sign-off
Audit controls164.312(b)Logging of access grants, changes, and useAccess logs tied to identities
Person or entity authentication164.312(d)SSO and MFA enforced at the identity providerAuthentication policy and enforcement reports
Information system activity review (R)164.308(a)(1)(ii)(D)Scheduled review of access reports and activityReview records with dates and reviewers
Workforce security: authorization, clearance, termination (A)164.308(a)(3)Joiner-mover-leaver automation from the HR systemProvisioning and deprovisioning timestamps
Information access management: authorization, establishment, modification (A)164.308(a)(4)Access requests with approvals; role-based birthright accessRequest, approver, and justification records
Evaluation164.308(a)(8)Periodic user access reviews and control testingCampaign results and remediation proof
Business associate safeguards164.308(b), 164.314Governed vendor and contractor identities with end datesVendor access inventory and reviews
Minimum necessary164.502(b), 164.514(d)Least privilege by role; removal of unused accessRole definitions, access-to-role reports
Documentation retention164.316(b)(2)(i)Retained review and access recordsSix years of policies and records

What HIPAA requires for access to PHI#

HIPAA sets access rules in two places. The Security Rule governs electronic PHI through administrative and technical safeguards, and the Privacy Rule's minimum necessary standard governs how much PHI each workforce member uses. Together they require authorized access, recorded activity, and role-limited use. The rule names outcomes and leaves the method to each organization, which must document why its approach is reasonable.

Access control under the Security Rule#

The access control standard at 45 CFR 164.312(a)(1) requires technical policies that allow access to ePHI only to "persons or software programs" granted access rights. Two implementation specifications are required: unique user identification and an emergency access procedure. Automatic logoff and encryption are addressable. Access rights come from the information access management standard at 164.308(a)(4), which covers how access is authorized, established, and modified. A full plain-language overview lives in What is HIPAA?

Audit controls and activity review#

The audit controls standard at 164.312(b) requires mechanisms that "record and examine activity in information systems that contain or use [ePHI]." A separate required specification at 164.308(a)(1)(ii)(D) requires procedures to regularly review those records, including audit logs and access reports. OCR repeated both points in its October 2026 cybersecurity newsletter. Logs that nobody reviews do not satisfy the rule.

The minimum necessary standard#

The Privacy Rule requires covered entities to make reasonable efforts to limit use of PHI to the minimum necessary for the purpose. For internal use, HHS says covered entities must "limit access to protected health information to those in the workforce that need access based on their roles," per its minimum necessary FAQ. The Privacy Rule summary adds that policies must identify the classes of persons who need access and the categories of PHI they need. That is least privilege, written into federal law.

Proposed Security Rule changes#

HHS published a proposed Security Rule update on January 6, 2025. It would require MFA, end a departing workforce member's access "no later than one hour" after employment ends, and require notice to other regulated entities within 24 hours of an access change. As of this update, HHS has not issued a final rule. The HHS fact sheet summarizes the proposal. Build to it now; one-hour offboarding is not achievable with tickets and spreadsheets.

Where identity fits: who has access to PHI and why#

Healthcare identity and access management decides who can reach PHI. Identity governance decides whether they should, and proves it. A hospital may run hundreds of applications that touch PHI, each with its own roles and local accounts. Without a single view of entitlements across all of them, nobody can answer the question auditors ask first: who can see patient data, and who approved it?

Map access to role and purpose#

Start with role definitions that reflect clinical reality. A charge nurse, a radiologist, a billing specialist, and a research coordinator need different PHI. HHS allows role-based policies that give treating providers access to full records for treatment, so the goal is access that matches the job. Where roles are too coarse, add attributes like department, location, and credential so access follows people as they move.

Find the access nobody approved#

Real risk sits in access that drifted. Clinicians float between units and keep old permissions. Former residents keep EHR accounts. Shared workstation logins break unique user identification. Privilege creep is the most common way a minimum necessary policy fails in practice. Toxic combinations, like the ability to both create and approve billing adjustments, belong under separation of duties rules.

User access reviews for HIPAA#

HIPAA does not use the phrase "user access review," and it does not set a review frequency. Reviews are still the most direct way to meet the information system activity review, evaluation, and access modification requirements. A user access review asks the person who owns a system or manages a team to confirm that each user's access is still needed, then removes what is not.

How often to review#

Most healthcare organizations review EHR and other high-risk PHI systems quarterly and lower-risk systems annually. Base the cadence on your risk analysis and document the rationale. The proposed Security Rule would require review and testing of access control procedures at least every 12 months, so an annual floor is the minimum defensible position. Tie event-driven reviews to role changes, leaves of absence, and vendor contract renewals.

What makes a review defensible#

OCR's 2022 breach report to Congress found "deficient or non-existent information system activity review processes" in its investigations. A review that holds up has five parts: a complete and accurate user list, the right reviewer, context on usage and risk, a recorded decision, and proof the revoke reached the target system. The user access review template covers the policy side, and user access review best practices covers the operating model.

Cut rubber-stamping#

Clinical managers will not review thousands of EHR entitlements line by line. Scope campaigns to high-risk access, pre-approve access that matches policy, and surface unused or anomalous access for human decisions. That is how teams automate user access reviews without lowering the bar. Comparing tools? Start with the user access review software guide.

Identity lifecycle for clinicians, contractors, and students#

The HIPAA workforce includes employees, volunteers, trainees, and others under the organization's direct control, as defined at 45 CFR 160.103. That covers residents, nursing students, locum tenens physicians, travel nurses, and agency staff. Each group joins, moves, and leaves on a different schedule, and each needs access granted at the start and removed at the end. Identity lifecycle management makes that consistent.

Clinicians and employees#

Use the HR system as the source of truth. A hire event should create accounts and assign birthright access by role. A transfer from the ED to oncology should add new access and remove the old. A termination should revoke access everywhere, including local EHR accounts the identity provider does not control. The joiner-mover-leaver process is where termination procedures under 164.308(a)(3) either work or fail, and automated provisioning and deprovisioning closes the gap.

Contractors, locums, and business associates#

Contractors often live outside the HR system, so their access has no natural end date. Assign a sponsor, set an expiration at grant time, and review vendor access on contract renewal. Business associate staff need the same treatment. See non-employee access management for an operating model that holds up.

Students, residents, and rotating trainees#

Academic medical centers onboard cohorts of students and residents who rotate through departments every few weeks. Rotation schedules should drive access: grant at rotation start, remove at rotation end, and expire everything at program completion. Students are workforce members under HIPAA, so their access is reviewed and logged like anyone else's.

Emergency (break-glass) access in healthcare#

The emergency access procedure at 164.312(a)(2)(ii) is a required specification. Healthcare leans on it more than most industries: a clinician treating a patient in crisis cannot wait for an approval chain. Break-glass access grants elevated access immediately, then makes the event visible and reviewable. Done well, it protects patients without becoming a standing back door.

How to govern break-glass access#

Five controls keep emergency access honest:

  • Pre-defined scope. Define which systems and records break-glass can open, and who is eligible.
  • Justification at the moment of use. Capture the reason, patient context, and requester.
  • Automatic expiration. Grant just-in-time access that ends on its own, measured in hours.
  • Mandatory after-action review. Route every event to a privacy or security reviewer within a set window.
  • Pattern detection. Flag users who break glass routinely. Repeated emergencies usually point to a role that needs permanent access or to misuse.

The proposed Security Rule would require both written and technical emergency access procedures. Most organizations already have the written half.

HIPAA audit evidence#

HIPAA audit readiness comes down to evidence. When OCR opens an investigation after a breach or complaint, it asks for policies, risk analyses, and proof the controls ran. HIPAA requires keeping required documentation for six years under 164.316(b)(2)(i). Identity governance produces most of the access evidence as a byproduct of doing the work.

Evidence auditors ask for#

  • Access control and minimum necessary policies, with role definitions.
  • An inventory of systems that hold ePHI and who owns them.
  • Access request and approval records with justifications.
  • User access review results: reviewer, decision, date, and remediation proof.
  • Provisioning and deprovisioning timestamps for joiners, movers, and leavers.
  • Break-glass logs with after-action reviews.
  • Activity review records showing logs were examined, not only collected.

Make the evidence trustworthy#

Auditors test completeness and accuracy of the populations you hand them. A review built on an export from one system, edited in a spreadsheet, invites questions. Pull user lists directly from source systems, keep decisions attributable and timestamped, and confirm revocations in the target application. The same discipline applies to SOC 2 and other audits, so one evidence model can cover all of them.

AI agents touching PHI#

AI agents now summarize charts, draft prior authorization requests, and query claims data. Each one is an identity with access to PHI. HHS stated in its proposed rule that ePHI "in AI training data, prediction models, and algorithm data" maintained for covered functions is protected by the HIPAA Rules. It also said a risk analysis must consider the type and amount of ePHI an AI tool accesses and who receives its output.

Treat agents as governed identities#

The access control standard already covers "software programs," so agents need the same controls as people. Give every agent a unique AI agent identity with an accountable human owner. Scope its access to the minimum necessary for its task. Never let an agent inherit a clinician's full session. Non-human identity management covers the service accounts and API keys underneath.

Controls for agent access to PHI#

  • Inventory. Know which agents exist, what systems they connect to, and what data they can reach.
  • Least privilege by task. Grant narrow, time-bound access instead of standing permissions. Zero standing privileges applies to agents first.
  • Credential hygiene. Store agent secrets in a vault and rotate them on a schedule.
  • Logging. Record every tool call and data access so activity review covers agents.
  • Review. Include agents in user access reviews, reviewed by their owners.

Agentic identity governance explains the model in depth.

How C1.ai supports identity for HIPAA compliance#

Healthcare teams need one governance model for clinicians, contractors, students, and AI agents across every system that holds PHI. C1.ai is an identity governance platform that maps those access requirements to automated controls and keeps the evidence attached. Each capability below corresponds to a requirement covered earlier in this guide.

  • User access reviews. UAR automation scopes campaigns by risk, gives reviewers usage context, and tracks each revoke to the target system.
  • Lifecycle. C1 Lifecycle turns HR events into access changes and finds access that offboarding missed.
  • Break-glass and JIT access. Just-in-time access applies policy, scope, and expiration to routine, on-call, and emergency requests.
  • Audit evidence. Compliance and risk management keeps timestamped, attributable, exportable records and flags separation of duties conflicts.
  • AI agents and NHIs. AI agent security logs and enforces policy on agent actions, and NHI governance inventories service accounts and keys.

To see how C1.ai maps HIPAA access requirements to automated controls, book a demo.

Frequently asked questions#

What does HIPAA require for access control?#

The Security Rule requires technical policies that limit ePHI access to persons or software programs granted access rights (45 CFR 164.312(a)(1)). Unique user identification and an emergency access procedure are required. Automatic logoff and encryption are addressable. Organizations also need procedures to authorize, establish, and modify access under 164.308(a)(4), and must authenticate users before granting access.

Does HIPAA require user access reviews?#

HIPAA does not name user access reviews or set a frequency. It requires regular review of information system activity, periodic evaluation of safeguards, and procedures to modify access. User access reviews are the standard way to satisfy those requirements with evidence. Most healthcare organizations review high-risk systems like the EHR quarterly and others annually, based on their risk analysis.

How fast must access be removed when someone leaves?#

Current HIPAA rules require termination procedures but set no deadline. The January 2025 proposed Security Rule would require removal no later than one hour after employment or another arrangement ends. HHS has not finalized that rule. Automated deprovisioning from the HR system is the only practical way to meet a one-hour standard across every PHI system.

Is break-glass access allowed under HIPAA?#

Yes. HIPAA requires it. The emergency access procedure at 164.312(a)(2)(ii) is a required implementation specification. Organizations must have procedures to obtain necessary ePHI during an emergency. Govern break-glass with defined scope, a recorded justification, automatic expiration, and after-action review of every event.

Do HIPAA access rules apply to AI agents?#

Yes. The access control standard covers software programs as well as persons. HHS stated in its 2025 proposed rule that ePHI in AI training data, prediction models, and algorithm data is protected by the HIPAA Rules. Give each agent a unique identity, an accountable owner, minimum necessary access, logging, and inclusion in access reviews.

How long must HIPAA access records be kept?#

HIPAA requires covered entities and business associates to retain required documentation for six years from creation or the date it was last in effect, whichever is later (45 CFR 164.316(b)(2)). That includes policies, risk analyses, and records of actions the Security Rule requires. Keep access review results, approvals, and break-glass reviews on the same schedule.

What is the difference between identity governance and healthcare IAM?#

Healthcare IAM authenticates users and grants access to systems. Identity governance decides whether that access is appropriate, reviews it over time, and proves it to auditors. HIPAA needs both. See IGA vs IAM for the full comparison.

What is C1.ai?#

C1.ai (formerly ConductorOne) is an AI-native identity governance platform. It automates user access reviews, lifecycle management, just-in-time access, and audit evidence for human users, non-human identities, and AI agents across cloud and on-premises applications.

Sources#