The HIPAA Security Rule, at 45 CFR Part 164 Subpart C, is the rule that specifies how electronic protected health information (ePHI) is stored and accessed in an EHR. It requires covered entities and their business associates to apply administrative, physical, and technical safeguards, and the technical safeguards in 45 CFR 164.312 are the ones that govern access controls, audit controls, integrity, authentication, and transmission security inside the EHR itself.

The Security Rule Is the Storage and Access Rule, Not the Privacy Rule

The Privacy Rule governs whether and why you may use or disclose health information. The Security Rule governs how you protect it electronically. If your question is specifically about storage and access in an EHR, the Security Rule is your operative regulation, and the Privacy Rule mainly sets limits on what the Security Rule is protecting.

The Security Rule applies to ePHI that a covered entity creates, receives, maintains, or transmits. "Covered entity" means a health plan, a health care clearinghouse, or a health care provider that transmits health information electronically in connection with a transaction the Department of Health and Human Services has adopted standards for. If you're a provider billing electronically, the Security Rule reaches your EHR.

One detail the top-ranking explainers often skip: the Security Rule isn't one document. It's broken into five subparts β€” general rules, administrative safeguards, physical safeguards, technical safeguards, and organizational requirements plus policies and procedures. Storage and access requirements sit mostly in the administrative and technical subparts, with physical safeguards covering the machines and rooms where EHR data lives.

The rules were issued in their current form in 2013 by the Omnibus Rule, which also extended direct compliance obligations to business associates. A 2025 HHS proposal to strengthen the Security Rule β€” cybersecurity risk analysis, asset inventory, and encryption β€” has been under review, so confirm the current text on the HHS website before you build a compliance program around any specific provision.

Required vs. Addressable: The Distinction That Decides Every Safeguard

Every Security Rule standard is required, but implementation specifications are either "required" or "addressable." That single distinction explains why two hospitals can both be HIPAA-compliant with visibly different EHR setups. Addressable does not mean optional; it means you assess whether the specification is reasonable and appropriate, implement it, or document why an equivalent alternative achieves the same protection.

Take encryption of ePHI at rest. It's an addressable implementation specification under the encryption and decryption standard at 45 CFR 164.312(a)(2)(iv). HHS has said in its guidance that encrypting ePHI is the single most effective way to reduce breach notification obligations, because properly encrypted data that's compromised is generally not "unsecured" under the breach notification rule. A small practice can reasonably rely on full-disk encryption; a hospital running a shared EHR database needs database-level controls too.

The practical consequence: your risk analysis drives your implementation choices. The risk analysis at 45 CFR 164.308(a)(1)(ii)(A) is required, and it's the first thing OCR investigators ask for. An EHR deployment with strong access controls but no documented risk analysis fails the audit before anyone opens a single log.

Failure case worth knowing: OCR's enforcement actions repeatedly cite missing risk analyses rather than missing technology. In 2024, OCR announced settlements with providers that had no risk analysis at all, including an HIV clinic that paid $120,000 after a breach affecting fewer than 2,000 people. Anti-discrimination protections for reproductive health care information under the 2024 HIPAA Privacy Rule change add a further layer when that data sits in the EHR.

Administrative Safeguards: 45 CFR 164.308 in Plain English

Administrative safeguards are the policies, workforce training, and governance that make the EHR's technical controls mean something. Nine standards live here: security management process, assigned security responsibility, workforce security, information access management, security awareness training, security incident procedures, contingency plan, evaluation, and business associate contracts. Every covered entity must designate a security official under 164.308(a)(2).

The information access management standard at 164.308(a)(4) is the one that most directly addresses who can access what in the EHR. It requires you to authorize access to ePHI and establish, document, and review procedures for granting access. In practice, that means a formal role-based access matrix: what a front-desk scheduler can see in the EHR versus a billing coder versus a treating physician.

The workforce security standard at 164.308(a)(3) requires authorization and supervision of workforce members who work with ePHI, and procedures for terminating access. Terminations are the classic failure point. A nurse who leaves on Friday and still has active EHR credentials on Monday is an access control finding, and it's a screenshot an auditor can produce in ten seconds.

Workforce clearance procedures β€” the other addressable specification under 164.308(a)(3)(ii)(B) β€” ask whether you screen people before granting EHR access. For most organizations, the reasonable approach is reference checks and a signed confidentiality agreement, not a criminal background check for every scheduler, but you must document that reasoning. The contingency plan standard at 164.308(a)(7) requires a data backup plan, a disaster recovery plan, and an emergency mode operations plan, each with testing and revision procedures.

Physical Safeguards: 45 CFR 164.310 and Where the Servers Actually Sit

Physical safeguards cover the facilities and equipment that house the EHR. The facility access controls standard at 164.310(a)(1) requires policies for limiting physical access to electronic information systems, including contingency operations, facility security plan, access control and validation procedures, and maintenance records. For a cloud-hosted EHR, most of this obligation moves to the hosting provider under a business associate agreement, but it doesn't vanish.

The workstation use standard at 164.310(b) requires documented policies on how workstations are used, including appropriate functions and physical attributes of the workstation location. The workstation security standard at 164.310(c) requires physical safeguards for workstations that access ePHI. That's the regulation behind the automatic screen lock you'd want on every nursing station desktop.

Device and media controls at 164.310(d)(1) govern disposal, media re-use, accountability, and data backup and storage. Disposal is the required specification: you must have procedures to dispose of ePHI and hardware or electronic media on which it is stored. A hospital that sends a decommissioned EHR server to recycling without sanitizing the drives has a disposal problem, and OCR treats it as one.

Real-world edge case: shared workstations in busy clinics often stay logged in because of workflow pressure. The Security Rule doesn't prohibit that, but it requires you to have a workstation use policy and to evaluate whether the configuration is reasonable. A better answer than a blanket rule is often a smart card tap-out with a 30-second lock timer; the regulation cares that you thought it through and documented it, not that you picked one exact timeout value.

Technical Safeguards: What 45 CFR 164.312 Requires Inside the EHR

The technical safeguards are the heart of the answer to your question. Five standards in 164.312 apply to every covered entity: access control, audit controls, integrity, person or entity authentication, and transmission security.

Regulation Standard Key required specs Common EHR implementation
164.312(a)(1) Access control Unique user identification (a)(2)(i); emergency access procedure (a)(2)(ii) Individual logins, break-glass emergency access
164.312(a)(2)(iv) Encryption/decryption Addressable Data at rest encryption, database encryption
164.312(b) Audit controls Required (no implementation specs listed) EHR audit log, log review schedule
164.312(c)(1) Integrity Mechanism to authenticate ePHI (c)(2) Checksums, version history, edit trails
164.312(d) Person/entity authentication Required (no specs listed) Passwords plus MFA
164.312(e)(1) Transmission security Integrity controls (e)(2)(i); encryption (e)(2)(ii), both addressable TLS/HTTPS for all data in transit

Access control at 164.312(a)(1) requires technical policies and procedures for electronic information systems that maintain ePHI to allow access only to persons or software programs granted access rights. The unique user identification specification is required: every person in the EHR needs their own credential. Shared logins are a compliance defect, full stop.

The emergency access procedure specification is required and underappreciated. If your EHR locks down during downtime and clinicians can't get to records during a mass-casualty event, you need a written break-glass process that grants necessary access and then gets reviewed afterward. Document who reviewed the break-glass events and when.

Audit controls at 164.312(b) require hardware, software, and procedural mechanisms that record and examine activity in systems that contain or use ePHI. The rule doesn't specify retention periods or review frequency; those come from your risk analysis and state law, and many state medical record retention laws run seven to ten years. A "we have audit logs" claim without evidence anyone has reviewed them is a weak response to an OCR inquiry.

Access Control and Authentication Are Separate Standards With Separate Evidence

It's easy to blur access control and authentication, but they cover different things and auditors look for different evidence. Access control limits what an authenticated user can do once inside the EHR. Authentication at 164.312(d) verifies that the user is who they claim to be. You need both, and neither substitutes for the other.

Authentication is a bare standard with no implementation specifications, which means the method is up to you, but the rule implies something stronger than a shared password. Multi-factor authentication (MFA) for remote EHR access is now the most common approach, and it's increasingly written into cyber insurance policies and business associate agreements whether or not the Security Rule names it. Confirm current MFA expectations with HHS guidance and your insurer's questionnaires before choosing a method.

A common misconception: that an EHR vendor's SOC 2 report removes the covered entity's compliance duty. It doesn't. The vendor is a business associate, and the covered entity still needs a signed business associate agreement, still needs to assess the vendor's safeguards, and still needs its own access control policies for the users the covered entity creates inside the EHR. The SOC 2 report is evidence, not a handoff of responsibility.

Authentication evidence auditors typically ask for: a password policy, an MFA enrollment report, a sample of disabled accounts after termination, and a record of the last access review. If you can produce those four items, you're ahead of most organizations. If you can't produce the account termination sample, that's usually where the conversation turns difficult.

How Required Versus Addressable Plays Out in a Small Clinic vs. a Hospital

The same regulation produces different-looking compliance in different organizations, and the difference is mostly a function of where ePHI lives and how many people touch it. Under 45 CFR 164.306, the Security Rule is designed to be scalable, and HHS states explicitly that a small practice can satisfy it with proportionately smaller measures.

Consideration Solo or small clinic (1–10 providers) Hospital system
Encryption approach Full-disk encryption on endpoints, vendor-managed encryption at rest Database-level encryption, key management program, encryption at rest and in transit
Audit log review Monthly review by the privacy officer Automated alerting plus quarterly compliance review
Emergency access Documented break-glass with owner review Break-glass tied to incident management, post-event review
Authentication MFA on all EHR access, including in-office MFA, plus single sign-on with role provisioning
Risk analysis Annual documented risk analysis, refreshed after change Continuous risk program with named owners

A clinic can honestly rely on the EHR vendor's encryption for data at rest and still have addressable encryption documented as satisfied; it just needs to record the reasoning, including what happens if the vendor's encryption isn't adequate for a particular data set. A hospital that hosts its own EHR database can't delegate that analysis to a vendor because it owns the servers.

The failure case differs too. For a small clinic, the most common audit finding is an outdated or missing risk analysis. For a hospital, it's often insufficient access governance across hundreds of roles or audit log review that exists on paper only. Both are addressable through documentation and process, not new technology.

Cost of getting this wrong isn't small. OCR civil money penalties are adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act, and the tier structure ranges from a corrective action plan at the low end to multi-million-dollar settlements at the top tier. Confirm the current penalty tiers on the HHS website because the figures are adjusted each year.

Storing EHR Data in the Cloud or With a Vendor: What Changes

Moving the EHR to a vendor-hosted or cloud platform doesn't move the legal obligation, it moves who executes parts of it. The business associate agreement required by 45 CFR 164.308(b)(1) is mandatory before any ePHI goes to the vendor, and it must require the vendor to implement reasonable safeguards and to report breaches.

The storage location matters for the physical safeguard analysis. If the vendor's data centers are outside your control, you still need to document your assessment of their facility access controls and device and media controls, typically through the vendor's audit reports, HITRUST certification, or SOC 2 Type II report. Ask for the report; don't accept the marketing page.

Backups are the most commonly missed piece in cloud EHR deployments. The contingency plan standard at 164.308(a)(7)(ii)(A) requires a retrievable exact copy of ePHI. That's a required specification and it applies to cloud deployments just as much as on-premise. If your vendor's backup is immutable and restorable, get that in writing in the BAA and test a restore at least annually.

One 2024 HHS development worth knowing: OCR issued guidance on online tracking technologies, clarifying that certain tracking tools on patient-facing pages can create impermissible disclosures of ePHI. If your patient portal or scheduling page runs third-party analytics, review the current guidance on HHS before publishing.

Access Reviews, Logging, and Incident Response: The Paper Trail That Survives an Audit

An OCR investigation usually begins with a breach report and then asks for the documentation that shows safeguards were in place before the breach. The paper trail is what you need to build ahead of time, and it's the difference between a corrective action plan and a fine.

Start with an access review cadence. Every role in the EHR should be reviewed at least annually, and every terminated user's access should be removed within your documented timeframe. Common practice is same-day or within 24 hours for involuntary terminations; document whichever you choose and can actually meet.

Audit log review is next. Log what your EHR captures, who reviews it, how often, and what happens when the review finds something. A quarterly review of high-risk access events β€” views of VIP records, bulk exports, after-hours access β€” is a reasonable standard for a mid-size organization; set the frequency in policy and keep evidence of every review.

Incident response is administrative safeguard territory, and it connects directly to the breach notification rule at 45 CFR Part 164 Subpart D. You need a documented process for identifying, containing, and reporting a security incident, and you need to apply the four-factor risk assessment HHS describes when deciding whether an incident is a reportable breach. That assessment includes the extent and nature of the ePHI involved, the unauthorized person who accessed it, whether it was actually acquired or viewed, and the extent to which the risk was mitigated; write down each factor's answer.

A difficult edge case: insider snooping. A clinician looks at a celebrity's or a neighbor's record out of curiosity. The access control and audit controls provisions are there for exactly this scenario, and if your audit review catches it and your incident response documents the mitigation, the breach analysis may come out differently than if you found out six months later in a newspaper. Review the current HHS breach notification guidance before finalizing any decision on a suspected insider access incident.

FAQ

Do HIPAA requirements specify how EHR data must be stored?

Yes, but they specify the protections, not the technology. The Security Rule at 45 CFR 164.312(a) requires access controls and addressable encryption at rest, and 164.310 requires physical safeguards for the media and facilities where data sits. It doesn't tell you which database, cloud provider, or encryption algorithm to use; you document that choice in your risk analysis.

What's the difference between required and addressable HIPAA specifications?

Required specifications must be implemented. Addressable specifications must be assessed, and you either implement them or document why an equivalent alternative achieves the same protection. Addressable does not mean optional. Most small organizations implement addressable encryption and document why full-disk encryption is proportionate.

Is a shared EHR login ever acceptable?

No. Unique user identification at 45 CFR 164.312(a)(2)(i) is a required specification, and a shared login defeats audit controls because the log can't identify who accessed the record. The cost of fixing it is nearly nothing compared with the audit finding, and the fix also makes the access review meaningful.

Does using a cloud EHR vendor shift HIPAA responsibility to the vendor?

Not entirely; it splits responsibility. The vendor becomes a business associate and must sign a business associate agreement, safeguard the data, and report breaches. The covered entity remains responsible for risk analysis, access policies for its own users, and contingency planning, and it must verify the vendor's safeguards through audit reports.

How long must EHR audit logs be kept?

HIPAA doesn't set a specific retention period. Your risk analysis, state medical record retention laws, and payer contract requirements usually drive the answer, and many states require seven to ten years for medical records generally. Document the retention period you chose and why, and confirm the current HHS records retention guidance at the time you set policy.

What is the emergency access procedure HIPAA requires?

It's a required specification at 45 CFR 164.312(a)(2)(ii) that lets authorized users obtain necessary ePHI during an emergency. The rule requires a documented procedure, and good practice adds a review step after a break-glass event. If clinicians can access the EHR freely during downtime with no post-event review, the procedure exists on paper but not in practice.

Which HIPAA rule governs storage and access rather than privacy?

The Security Rule, at 45 CFR Part 164 Subpart C, governs the technical and physical safeguards for storing and accessing ePHI. The Privacy Rule sets limits on use and disclosure. Both apply to EHR data, but a question about how storage and access work is answered primarily by the Security Rule.

This article is general educational information and not legal advice or a compliance certification. HIPAA obligations vary by entity type, business associate relationship, state law, and current HHS guidance, so verify regulatory text and consult a qualified health care privacy attorney or compliance professional for your organization. If a breach has occurred, follow your incident response plan and the current HHS breach notification requirements immediately.