Skip to content
HIPAA ComplianceConsulting

Nationwide Service Coverage

HIPAA Compliance Consulting Across the United States

How HIPAA works as a federal floor, where state law adds obligations, and how multi-state healthcare organizations decide which state requirements to map.

Reviewed Request a HIPAA Consultation

HIPAA sets one federal baseline for protected health information (PHI), but almost no healthcare organization operates under HIPAA alone. Every state has its own breach notification statute, many have medical confidentiality laws that go further than HIPAA, and state attorneys general can enforce HIPAA itself. If you see patients, process claims or host PHI for customers in more than one state, your compliance program has to account for that layering.

This page explains how we approach HIPAA compliance consulting for organizations with a national or multi-state footprint: how preemption works, where state law most often changes day-to-day obligations, and how to decide which state laws are worth mapping in detail.

Key points

  • HIPAA is a floor: under 45 CFR §160.203, contrary state privacy laws that are more stringent are not preempted.
  • All 50 states have breach notification laws, with different triggers, timelines and regulator notices.
  • HITECH lets state attorneys general bring HIPAA enforcement actions on behalf of residents.
  • Map state law based on where your patients, members or data subjects live — not only where you are incorporated.

How we deliver HIPAA consulting nationwide

Our engagements are built to run remotely: document review, stakeholder interviews over video, evidence collection through shared workspaces, and technical reviews of configuration exports or screen-shared walkthroughs. Where a physical safeguards review or facility walkthrough genuinely adds value, on-site visits can be arranged.

Because the work is remote by design, the same methodology applies whether your team sits in one building or across a dozen states. Typical starting points are a HIPAA risk assessment or a HIPAA gap analysis scoped to your footprint.

HIPAA as the federal floor: how preemption works

The general rule in 45 CFR §160.203 is that a provision of HIPAA preempts a contrary state law. The key exceptions matter more in practice than the rule itself. A state law is not preempted when it relates to the privacy of individually identifiable health information and is "more stringent" than HIPAA — for example, because it gives individuals greater access rights or restricts a use or disclosure that HIPAA would permit. Other exceptions cover state laws on public health reporting, health plan reporting and certain determinations by the HHS Secretary.

The practical consequence: where a state law is stricter, you usually comply with both, which means following the stricter requirement. Where a state law is less protective, HIPAA governs. Where the two simply address different things — such as a state data security statute covering non-health personal information — both apply on their own terms.

Common interaction patterns between HIPAA and state law
SituationTypical resultExample area
State law is more protective of health privacyNot preempted; follow the stricter ruleHeightened consent for mental health, HIV or genetic information
State law is contrary and less protectiveHIPAA preempts the contrary provisionA state rule that would permit a disclosure HIPAA prohibits
State law addresses something HIPAA does notBoth apply independentlyGeneral breach statutes, biometric laws, consumer privacy laws
State law exempts HIPAA-regulated dataExemption is usually partial — check what falls outsideComprehensive consumer privacy laws with PHI carve-outs

State breach notification: 50 states, many variations

Every state, plus the District of Columbia and several territories, has a breach notification law. HIPAA’s Breach Notification Rule (45 CFR §§164.400–414) requires notice to individuals without unreasonable delay and no later than 60 calendar days after discovery, media notice where 500 or more residents of a state or jurisdiction are affected, and notice to HHS. State laws can add obligations on top of that.

Many state statutes include a deemed-compliance provision for entities that notify under HIPAA, but those provisions are rarely a complete exemption. Some still require a copy of the notice to the state attorney general, some impose shorter deadlines, and some define "personal information" to include data elements — such as account credentials or biometric data — that may sit outside your PHI inventory.

  • Confirm whether each relevant state’s deemed-compliance language applies to your entity type (covered entity vs. business associate).
  • Check for state regulator notice thresholds and deadlines that are shorter than HIPAA’s outer limits.
  • Identify non-PHI personal information (employee data, payment data, login credentials) that triggers state law but not HIPAA.
  • Build state-specific templates into your incident response plan before you need them. Our breach notification requirements resource covers the federal side.

State attorney general enforcement of HIPAA

The HITECH Act gave state attorneys general authority to bring civil actions in federal court on behalf of state residents for HIPAA violations. In practice, multi-state data breach investigations often involve coordinated AG offices alongside — or separately from — HHS Office for Civil Rights. AG actions frequently combine HIPAA claims with state consumer protection and data security statutes.

For a multi-state organization, this means a single incident can draw inquiries from several regulators with different priorities. The best preparation is ordinary HIPAA hygiene done well: a current risk analysis under §164.308(a)(1)(ii)(A), a documented risk management plan under §164.308(a)(1)(ii)(B), and policies kept for at least six years under §164.316.

Choosing which state laws to map

Mapping every state’s health privacy law in detail is expensive and rarely necessary. We help clients prioritize, then work with their counsel on the legal analysis for the states that matter most.

  1. 1

    Locate your data subjects

    List the states where your patients, members or end users reside, not just where you have facilities. Telehealth and SaaS platforms often have a much wider footprint than their office locations suggest.

  2. 2

    Identify high-sensitivity data categories

    Mental health, substance use, HIV/STI, reproductive, genetic and biometric data are where state laws most often exceed HIPAA.

  3. 3

    Rank states by exposure

    Weight by volume of residents, sensitivity of data and the presence of private rights of action or active AG enforcement.

  4. 4

    Map requirements to controls

    Translate each priority state’s requirements into specific policies, consent flows, training content and incident response steps.

  5. 5

    Assign ownership and review dates

    State laws change frequently. Assign a legal or compliance owner and a review cadence for each mapped state.

Federal rules that sit alongside HIPAA

Not every health data obligation is HIPAA or state law. The FTC Health Breach Notification Rule can apply to health apps and personal health record vendors that are not covered entities or business associates. 42 CFR Part 2 governs certain substance use disorder treatment records. Sector-specific frameworks, such as state insurance regulations, may apply to health plans.

Proposed changes also deserve tracking. HHS published a proposed update to the HIPAA Security Rule in the Federal Register on January 6, 2025. It is a proposal, not final law; verify its current status before planning around it. The 2024 reproductive health amendments to the Privacy Rule have been subject to litigation — verify their current status as well.

What a multi-state engagement typically includes

  • An enterprise-wide risk analysis covering all locations, systems and vendors that create, receive, maintain or transmit ePHI.
  • A state-law overlay for priority states, prepared with or reviewed by your legal counsel.
  • Unified HIPAA policies and procedures with state-specific addenda rather than separate policy sets per state.
  • Incident response playbooks that list state regulator notice requirements alongside HHS and individual notices.
  • Workforce training that covers both HIPAA and state-specific rules for staff in each region.
  • Ongoing review, because compliance is continuous — no assessment or consultant can promise a compliant end state.

Frequently asked questions

If we comply with HIPAA, are we compliant with state law?

Not necessarily. HIPAA is a floor. State laws that are more stringent on health privacy are not preempted, and state laws covering other topics — such as general breach notification or biometrics — apply independently. Confirm the details with qualified counsel.

Which state’s law applies to a patient who lives in one state and is treated via telehealth from another?

It can be both. Many state privacy and breach laws focus on the residence of the individual, while professional and facility rules may follow the location of the provider. This is a legal question we flag for your counsel rather than answer on our own.

Can state attorneys general enforce HIPAA?

Yes. HITECH authorized state attorneys general to bring civil actions in federal court for HIPAA violations affecting their residents. They often pair those claims with state consumer protection or data security laws.

Do you need to visit our locations?

Usually not. Most of the assessment work is done remotely. On-site visits can be arranged when a physical safeguards walkthrough or workshop is worth the travel.

Is there a national HIPAA certification we can obtain?

No. HHS does not offer or endorse any HIPAA certification for organizations or consultants. What you can obtain is documented evidence: a current risk analysis, risk management plan, policies, training records and BAAs.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.