Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

HITRUST vs HIPAA: 7 Essential Differences and When to Certify (2026)

HITRUST vs HIPAA compared: the federal law and the certifiable framework

HITRUST vs HIPAA is the comparison every healthcare vendor runs into sooner or later: a hospital security questionnaire asks for “HIPAA compliance,” and a few months later the same customer asks whether you are HITRUST certified. People search it both ways, HIPAA vs HITRUST, as if the two were alternatives, which they are not.

One is a federal law you must already be following if you touch protected health information (PHI). The other is a paid, private certification you might choose to pursue, and it is the only one of the two that produces a certificate a customer can check.

If you are still working through the underlying obligations, start with our complete HIPAA compliance guide. This page assumes you know roughly what HIPAA asks and need to decide what HITRUST would add, what it costs in effort, and whether your customers will actually reward it.

Free gap assessment

Could you evidence your HIPAA safeguards today?

Score every standard and implementation specification, free, including the addressable ones that still need a decision on file.

Run the free HIPAA gap assessment →  or  View premium report sample

HITRUST vs HIPAA: what this guide covers

HITRUST vs HIPAA at a glance

  HIPAA HITRUST CSF
What it is US federal law (with the HHS Privacy, Security and Breach Notification Rules) Private, certifiable control framework run by HITRUST
Who it applies to Covered entities and their business associates Anyone who chooses to be assessed; most often vendors to health systems
Obligation Mandatory if you create, receive, maintain or transmit PHI Voluntary, usually driven by customer contracts
Prescriptiveness Deliberately flexible; many specifications are “addressable” Specific requirement statements, tailored by risk factors and scored
Proof available No certification exists Validated assessment report and certification letter
Who checks HHS Office for Civil Rights (OCR), after a complaint, breach report or audit An authorized HITRUST External Assessor, then HITRUST quality assurance
Validity Continuous obligation e1 and i1: 1 year; r2: 2 years with an interim assessment
Consequence of failure Civil money penalties, corrective action plans, criminal liability in serious cases No certificate; lost or stalled deals

HITRUST vs HIPAA: 7 differences that matter in practice

The table gives the headline. These are the seven HITRUST and HIPAA differences that change how you plan the work.

1. Law versus framework

HIPAA is the Health Insurance Portability and Accountability Act of 1996 and the rules HHS has issued under it. You do not opt in. HITRUST is a company that publishes the HITRUST CSF and runs an assurance program on top of it. You opt in, pay for it and can walk away from it.

2. Who carries the obligation

HIPAA binds covered entities (health plans, clearinghouses and most providers) and the business associates that handle PHI for them, through a business associate agreement. HITRUST binds no one. It becomes an obligation only when a customer writes it into a contract or a vendor security policy.

3. Flexibility versus specificity

The HIPAA Security Rule tells you what to protect and leaves much of the how to you. The HITRUST CSF tells you exactly which requirement statements apply to your scope, based on factors such as organization size, system exposure and the regulations you are subject to.

4. Existence versus maturity

A HIPAA review asks whether a safeguard is in place and reasonable. An r2 assessment scores each requirement on maturity levels (policy, procedure, implemented, measured and managed), so a control that exists only on paper scores poorly. Our guide to HITRUST scoring walks through how those levels add up.

5. Self-assessment versus third-party validation

For HIPAA, you perform and document your own risk analysis. This is the HITRUST vs HIPAA difference buyers notice most. For a HITRUST validated assessment, an authorized external assessor tests your evidence and HITRUST reviews the assessor’s work before issuing a report.

6. Ongoing duty versus a dated certificate

HIPAA compliance has no expiry date and no finish line. HITRUST certification is dated: one year for e1 and i1, two years for r2, with an interim assessment due in the first year of an r2 cycle.

7. Regulator versus customer

The enforcer of HIPAA is OCR, plus state attorneys general. The enforcer of HITRUST is your customer’s procurement or third-party risk team. That is why, in any HITRUST vs HIPAA discussion, the decision to pursue HITRUST is commercial, while the decision to comply with HIPAA was made for you.

Why HIPAA leaves room for argument

The HIPAA Security Rule is written to apply to a sole practitioner and a national hospital network alike, so many of its implementation specifications are “addressable” rather than required. Addressable does not mean optional: you must assess whether the specification is reasonable and appropriate, implement it or an equivalent alternative, and document the reasoning either way. Our post on HIPAA safeguards covers how that documentation should look.

That flexibility is deliberate and sensible, but it creates a commercial problem: two vendors can both be genuinely HIPAA compliant with very different security postures. A buyer cannot tell them apart from a one-line claim.

There is also no such thing as HIPAA certification. HHS does not endorse or recognize any private HIPAA certification. Any vendor claiming to be “HIPAA certified” is describing a training course or a consultant’s opinion, not an official status. What exists is a risk analysis, documented policies and evidence you have acted on them, which is what our HIPAA risk assessment guide walks through.

Free ISO 27001 risk assessment

Which of your risks sit above your appetite line?

Set your own risk criteria, pick from 61 information security risk scenarios, rate likelihood and impact, and decide how to treat each one. You get a heat map, a process score and the findings an auditor would raise, free.

Run the free risk assessment →  or  View premium report sample

What HITRUST adds

The HITRUST CSF takes the ambiguity out. It harmonizes HIPAA with ISO 27001, NIST and dozens of other authoritative sources into one control set, then tailors the requirements to your organization’s size, systems and risk factors. Version 11 also made the framework “threat-adaptive”: HITRUST reviews threat intelligence and adjusts the e1 and i1 requirement sets as attack patterns change.

Crucially, r2 controls are scored on maturity, not merely on whether something exists. That scoring is why HITRUST is demanding and why customers value it. A validated assessment performed by an authorized external assessor produces something a HIPAA attestation letter cannot: a third-party-verified result, quality-checked by HITRUST, that a buyer can rely on.

The cost is real. You pay HITRUST for the MyCSF platform and assessment fees, you pay an external assessor for testing, and you pay internally for the evidence work and remediation. Our HITRUST certification cost breakdown sets out each line.

The three assessment types: e1, i1 and r2

HITRUST CSF v11 offers a graduated path rather than one all-or-nothing exam. The requirement sets are nested: everything in e1 is in i1, and everything in i1 is in r2, so work done for a smaller assessment carries forward.

Assessment Size of the requirement set Assurance level Certification validity Typical buyer signal
e1 (essentials, 1-year) Fixed set of roughly 44 foundational requirements Entry level 1 year Smaller vendors, low-risk data flows
i1 (implemented, 1-year) Fixed set of roughly 180 requirements Moderate 1 year Mid-sized vendors, “leading practice” assurance
r2 (risk-based, 2-year) Tailored; usually several hundred requirements depending on scope High 2 years, interim assessment in year 1 Vendors with large PHI volumes or deep system access

Counts are shown as approximate because HITRUST adjusts the e1 and i1 sets between CSF releases. Check the current release in MyCSF before you scope. Our guide to HITRUST assessments covers the choice in more depth.

Most vendors asked for “HITRUST” by a large health system are being asked for r2, but e1 and i1 make a credible starting point when the timeline is short. Ask the customer which one they will accept before you pay for anything.

HIPAA, HITECH and HITRUST: how they connect

The search “HIPAA vs HITECH vs HITRUST” comes up often because the names sound alike. They are three different things:

  • HIPAA is the 1996 law and the Privacy, Security and Breach Notification Rules issued under it.
  • HITECH is the Health Information Technology for Economic and Clinical Health Act of 2009. It extended HIPAA obligations directly to business associates, created the breach notification requirements and raised penalties.
  • HITRUST is the private organization behind the HITRUST CSF. It is not a law and not part of HHS.

There is one place where HITRUST and HIPAA formally meet. Public Law 116-321, signed on January 5, 2021, added section 13412 to HITECH. It requires HHS to take into account whether a covered entity or business associate had “recognized security practices” in place for the previous 12 months when deciding fines, audit outcomes and other remedies.

The law points to practices developed under the NIST Act and the section 405(d) approaches (the Health Industry Cybersecurity Practices).

HITRUST is not named in the statute, but because the HITRUST CSF maps to NIST and is evidenced by dated, assessor-tested reports, a current certification is strong evidence that you can show the 12 months of practice the law asks about.

That is a mitigation, not a safe harbor. A HITRUST certificate does not prevent an OCR investigation or a penalty if PHI is mishandled.

What changes for HIPAA in 2026 and 2027

OCR published a proposed overhaul of the HIPAA Security Rule in the Federal Register on January 6, 2025. Among other things, it would remove the distinction between required and addressable specifications and make measures such as encryption and multi-factor authentication mandatory, with limited exceptions. The comment period closed on March 7, 2025.

As of November 2026 the rule is not final. HHS had targeted May 2026, then moved the final rule to a July 2027 target in its regulatory agenda, and timetables like that are not binding. The current Security Rule stays fully in force until a final rule replaces it.

For the HITRUST vs HIPAA decision, the proposal matters in one way: if it is finalized close to its proposed form, the HIPAA baseline moves closer to what HITRUST already tests. Organizations that have implemented HITRUST-level controls would have less to change, which narrows the practical gap between HITRUST and HIPAA. Our HIPAA Security Rule update post tracks the details.

HITRUST vs ISO 27001, NIST and SCF

A lot of people comparing HITRUST vs HIPAA are really choosing between assurance options. Here is how HITRUST sits next to the other common choices.

Option Certifiable? Healthcare recognition Best fit
HITRUST CSF (e1, i1, r2) Yes, by HITRUST via authorized assessors High with US health systems and payers Vendors selling into US healthcare
ISO/IEC 27001:2022 Yes, by accredited certification bodies Moderate in US healthcare; high internationally Vendors with international or mixed-sector customers
SOC 2 No; it is a CPA attestation report Moderate; often accepted alongside a HIPAA mapping SaaS vendors whose customers already ask for SOC 2
NIST CSF 2.0 No certification exists Widely used as a reference; named in recognized security practices Building or benchmarking a program
Secure Controls Framework (SCF) Primarily a free control metaframework, not a buyer-recognized certificate Low as a buyer requirement Mapping many frameworks into one internal control set

If ISO 27001 is the realistic alternative for you, read our HITRUST vs ISO 27001 comparison. Many vendors end up with both, using HITRUST’s mappings to reuse evidence across the two.

When certification is worth it

The honest HIPAA vs HITRUST test is commercial, not technical. HITRUST is worth pursuing when:

  • customers are asking for it by name in questionnaires, RFPs or contracts;
  • you are losing or stalling deals without it;
  • you serve health systems or payers whose vendor policies require it; or
  • you are answering dozens of long security questionnaires a year, and one report would replace most of them.

It is not worth pursuing simply to feel more secure. A rigorous HIPAA program, built on a real risk analysis and a recognized framework such as NIST CSF, achieves that at lower cost. And if your customers are outside healthcare, ISO 27001 or SOC 2 will usually do more for you.

A useful HIPAA vs HITRUST rule of thumb: if one or two named customers want HITRUST, ask whether an e1 or i1 would satisfy them before committing to r2. If the requirement shows up across your whole pipeline, plan for r2.

A practical roadmap from HIPAA to HITRUST

  1. Confirm the ask. Get the customer to state which assessment (e1, i1 or r2) they accept and by when.
  2. Refresh the HIPAA risk analysis. It is the legal baseline and the best input for HITRUST scoping.
  3. Define scope. Decide which systems, locations and data flows are in. A tight scope is the biggest single lever on effort and cost.
  4. Write the documentation. Policies and procedures are the first two maturity levels in r2 scoring, and they are where most first-time gaps sit.
  5. Run a readiness assessment. Self-score in MyCSF before an assessor does. See our HITRUST readiness assessment guide.
  6. Remediate. Fix gaps and let controls operate long enough to produce evidence.
  7. Validate. Engage an authorized external assessor, submit to HITRUST QA and plan the interim assessment if you go for r2.

Timelines vary widely. As a typical range, e1 and i1 projects often run three to six months when policies already exist, while a first r2 commonly takes nine to eighteen months including remediation.

If the answer is yes, the documentation is the long pole. Our HITRUST CSF v11 Toolkit provides 45 Microsoft Office templates aligned to the framework, covering the information protection program, access control, audit logging, incident management, third-party assurance, risk management and the other domains assessors test. It gives you the policy and procedure layer the maturity scoring depends on, so your team can spend its time on implementation evidence.

For the legal side of HIPAA, the primary source is the HHS HIPAA site; for the HITRUST side, it is HITRUST itself.

Frequently asked questions about HITRUST vs HIPAA

Does HITRUST certification make you HIPAA compliant?

Not by itself. In HITRUST vs HIPAA terms, it demonstrates strong alignment, because the CSF incorporates HIPAA requirements, but the legal obligation remains yours. HITRUST is evidence of a well-run program and can count as recognized security practices, not a legal safe harbor.

Do I need HITRUST certification to be HIPAA compliant?

No. HIPAA does not require HITRUST or any other certification. You need a documented risk analysis, the required safeguards, business associate agreements and evidence that you follow your own policies. HITRUST is something customers may require on top.

Can you be HIPAA certified?

No. HIPAA has no certification scheme and HHS does not recognize private ones. Vendors advertising HIPAA certification are referring to training or a consultancy assessment, neither of which carries official standing.

How long does HITRUST certification take?

For an r2 validated assessment, most organizations should plan on nine to eighteen months including remediation. The e1 and i1 assessments are considerably faster and are often used as staging points. Remember that an r2 also needs an interim assessment in its first year.

Is HITRUST better than HIPAA, or HIPAA vs HITRUST a real choice?

That is the wrong question in HITRUST vs HIPAA terms: you cannot choose HITRUST instead of HIPAA. If you handle PHI, HIPAA applies. HITRUST is one way to prove to customers how well you meet it.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.