A Floor, Not a Ceiling — And That Distinction Has Cost Organizations Millions
A hospital system in Texas once told me they were "fully HIPAA compliant" and didn't need to worry about state law. Six months later, they were facing enforcement action from the Texas Attorney General for violating HB 300 — a state law that imposes stricter requirements on medical records privacy than anything in federal regulation. They'd confused the floor with the ceiling.
Here's the concept that trips up more compliance officers than almost any other: HIPAA regulations establish a floor of patient rights, which means they set the minimum standard of privacy protection that every covered entity and business associate must meet. States are allowed — and many do — to go further. Federal law doesn't cap how much protection a patient can receive. It only guarantees a baseline.
If your organization operates under the assumption that meeting HIPAA requirements is enough, you may already be out of compliance with the laws that actually govern your patients.
What Does "Floor of Patient Rights" Actually Mean?
Think of it like building codes. The federal government sets minimum safety standards for construction. But your city or state can require thicker walls, stronger foundations, or better fire suppression systems. You can't build below the federal minimum, but you can absolutely build above it.
HIPAA's Privacy Rule, Security Rule, and Breach Notification Rule work the same way. The U.S. Department of Health and Human Services (HHS) established these rules under the Health Insurance Portability and Accountability Act to protect individually identifiable health information — what we call protected health information, or PHI. Every covered entity in the country must comply with them.
But Section 1178 of the Social Security Act, as codified at 42 U.S.C. § 1320d-7, contains the preemption provision. It says HIPAA preempts state law only when the state law is less protective of patient privacy. If the state law is more stringent — meaning it gives patients greater rights or imposes tougher requirements on entities — the state law wins.
That single provision is what makes HIPAA a floor and not a ceiling.
The Real-World Impact Most Organizations Miss
I've consulted with covered entities in over a dozen states, and the pattern is consistent. Compliance teams build their programs around the HIPAA Privacy Rule and call it done. They train their workforce on the federal minimums. They write policies that mirror 45 CFR Part 164. And then they're blindsided when a state regulator or attorney general comes knocking with a different set of expectations.
Here's what happens in practice. HIPAA gives patients the right to access their medical records within 30 days, with a possible 30-day extension. But some states require faster turnaround. HIPAA allows covered entities to charge reasonable, cost-based fees for copies. Some states cap those fees at specific dollar amounts or prohibit them entirely in certain circumstances.
HIPAA's breach notification rule requires notification to affected individuals within 60 days of discovering a breach of unsecured PHI. Several states have shortened that window significantly. If you're following only the federal timeline, you may be violating state law every time a breach occurs.
Texas: A Case Study in Why the Floor Matters
Texas offers one of the clearest examples. The Texas Medical Records Privacy Act, commonly known as HB 300, goes well beyond HIPAA in several critical areas. It requires covered entities to provide employee training that's specific to Texas law — not just federal requirements. It imposes its own breach notification obligations. It mandates a stricter standard for the use and disclosure of PHI for marketing purposes.
If you operate in Texas — or treat Texas patients — and your training program only covers HIPAA, you have a gap. That gap is enforceable, and penalties under Texas law can be substantial. I've seen organizations address this by adding dedicated Texas Medical Records Privacy Act (HB 300) training to their compliance programs. It's not optional if you're in that state.
Which Patient Rights Does HIPAA's Floor Guarantee?
To understand what states are building on top of, you need to know what the floor includes. HIPAA's Privacy Rule establishes several core patient rights that no state can weaken:
- Right to access PHI: Patients can request and receive copies of their medical records from covered entities and most business associates.
- Right to request amendments: Patients can ask that errors in their records be corrected.
- Right to an accounting of disclosures: Patients can request a list of certain disclosures of their PHI made by the covered entity.
- Right to request restrictions: Patients can ask that the use or disclosure of their PHI be limited, though the entity generally doesn't have to agree — with one important exception involving self-pay services.
- Right to confidential communications: Patients can request that the entity contact them through alternative means or at alternative locations.
- Right to receive a Notice of Privacy Practices: Every covered entity must provide this document explaining how PHI is used and what rights the patient has.
These rights are the baseline. Every patient in the United States has them. States can expand these rights — for example, by granting patients stronger rights around sensitive health information like mental health records, substance abuse treatment, or HIV status — but they can never shrink them.
The $4.3 Million Question: What Happens When You Only Meet the Floor
Even meeting the federal floor isn't something every organization manages to do. The HHS Office for Civil Rights (OCR) has levied significant penalties against entities that failed to uphold even the minimum patient rights under HIPAA.
In 2019, OCR settled with Cignet Health for $4.3 million after the entity refused to provide 41 patients with access to their medical records — a direct violation of the HIPAA access right. That case remains one of the largest penalties specifically tied to patient rights rather than a data breach. You can review OCR's enforcement actions on the HHS enforcement page.
Now imagine layering state penalties on top of that. An organization that fails to meet both the federal floor and stricter state requirements faces enforcement from multiple directions simultaneously — OCR at the federal level and the state attorney general or health department at the state level.
How to Build a Compliance Program That Goes Beyond the Floor
The answer isn't to memorize every state law. It's to build a compliance infrastructure that accounts for the floor-not-ceiling reality from the start. Here's how I advise organizations to approach it.
Step 1: Map Your State Obligations
Identify every state where you operate, treat patients, or store ePHI. For each state, determine whether its privacy laws impose requirements beyond HIPAA. Focus on access timelines, breach notification windows, consent requirements, fee limitations, and sensitive health information categories.
Step 2: Layer Your Workforce Training
Your workforce training should start with HIPAA as the foundation and then layer on state-specific requirements. A one-size-fits-all training program signals to regulators that you haven't done the work. Explore compliance training options that address both federal and state-specific obligations — especially if you have staff in states with heightened requirements.
Step 3: Audit Your Policies Against the Highest Standard
When you operate in multiple states, your policies should default to the most protective standard unless you have state-specific workflows. If one state requires breach notification in 30 days and HIPAA allows 60, your policy should reflect the shorter window for patients in that state.
Step 4: Document Everything
OCR and state regulators both look for evidence that you've analyzed the interplay between federal and state law. Document your preemption analysis. Keep records of how you determined which law applies in each scenario. This documentation is your best defense in an investigation.
So What Does "Floor of Patient Rights" Mean? The Quick Answer
When we say HIPAA regulations establish a floor of patient rights, we mean that HIPAA sets the minimum level of privacy protection that all covered entities and business associates must provide. No state can pass a law that gives patients fewer rights than HIPAA. But every state can — and many do — pass laws that give patients greater protections, impose stricter penalties, or require additional safeguards beyond what federal law demands. The federal standard is the starting point, never the finish line.
Stop Treating the Minimum Like the Maximum
The organizations I see get into trouble are almost always the ones that treated HIPAA as the entire universe of their compliance obligations. They met the floor and assumed the job was done.
Your patients deserve more than the minimum. Your regulators expect more than the minimum. And in most states, the law requires more than the minimum.
Build your compliance program from the floor up. Know what HIPAA guarantees, and then go find out what your state demands on top of it. That's how you protect your patients — and your organization.