What Is the Difference Between HITRUST e1, i1 and r2, and Which Does My Organization Need?
A plain-language comparison for healthcare, finance and government organizations.
HITRUST e1, i1 and r2 are three assurance levels of the same framework. The e1 covers 43 foundational requirements, the i1 covers 182 threat-adaptive requirements, and the r2 is a risk-based assessment tailored to your environment. Your customers, partners and payers usually decide which level you need.
How the three levels relate to each other
All three assessments draw on the HITRUST CSF, a single framework that brings together requirements from HIPAA, NIST and other standards. What changes from one level to the next is how many requirements are tested, how much of your environment is in scope, and how much assurance the result gives the people relying on it.
e1: foundational assurance
The e1 covers 43 requirements focused on essential cyber hygiene, such as access control, patching, backup and malware protection. It is valid for one year. Organizations use it as a first milestone, or when a customer needs more than a questionnaire but does not need a deep assessment.
i1: moderate, threat-adaptive assurance
The i1 covers 182 requirements chosen to address current threats, and it is also valid for one year. It gives customers stronger third-party assurance than the e1 without the full scope of the r2. Many organizations treat it as a stepping stone toward the r2.
r2: the highest level of assurance
The r2 is risk-based and tailored. Requirements are selected from your organization’s size, systems, data volume and regulatory factors, and assessors evaluate policy, procedure and implementation. It is valid for two years, with an interim assessment after the first year. This is the level most health systems, payers and large enterprise customers ask their vendors for.
Three common misunderstandings
- A higher level is not automatically better for you. The right level is the one your customers accept and your risk justifies. Paying for an r2 when an i1 satisfies every contract wastes budget.
- Certification covers a defined scope, not the whole company. The letter names the systems, facilities and services that were assessed, so customers read the scope as carefully as the level.
- The levels are not interchangeable in a customer’s eyes. Some contracts name a specific level, and an e1 will not satisfy a requirement written for an r2.
What drives the cost and effort
Three things move effort more than the level itself: the size of the scope, the number of gaps you need to fix before testing, and how well your evidence is organized. Assessor fees and your team’s time follow from those. Narrowing the scope and fixing known gaps early are the most reliable ways to control both.
Side by side, and how to decide
| e1 | i1 | r2 | |
|---|---|---|---|
| Assurance level | Foundational | Moderate, threat-adaptive | Highest, risk-based |
| Requirements | 43 | 182 | Tailored to your scope |
| Valid for | 1 year | 1 year | 2 years, with an interim assessment at year one |
| Best fit | Lower-risk environments, or a first assurance milestone | Stronger assurance without the full r2 scope | Sensitive data, regulated industries, enterprise customer contracts |
| Typical readiness effort (indicative) | 2 to 4 weeks | 4 to 6 weeks | 6 to 10 weeks |
Readiness times are indicative only and vary with scope and existing controls.
Four questions that settle most decisions
- What does your largest customer or payer require? Ask them directly which level they accept before you start. This answers the question more often than anything else.
- How sensitive is the data you handle? Electronic protected health information and financial account data push toward the i1 or r2.
- How many systems, facilities and third parties are in scope? A broader scope usually points to the r2.
- Do you need to satisfy more than one framework? The r2 lets one assessment support several requirements at once.
If you are unsure, starting at the e1 or i1 is a legitimate path. The work you complete is useful evidence if you move up to the r2 later.
What this means for healthcare, finance and government
Health systems and payers commonly require HITRUST r2 from vendors that touch protected health information. Because the HITRUST CSF incorporates HIPAA, one assessment can answer many HIPAA-related vendor questions.
Banks and insurers use third-party assurance like HITRUST to reduce the number of one-off security questionnaires they send and review each year.
Agencies and their contractors often ask for evidence mapped to NIST-based controls. The HITRUST CSF includes NIST requirements, which makes the mapping easier.
SmartBase Solutions has held HITRUST CSF r2 certification since 2017 and supports healthcare, finance and government organizations. Having been through the process ourselves, we know what assessors ask for and how long each stage tends to take.
Not sure which level fits your situation?
A short conversation can usually narrow it down. Tell us who your customers are and what they have asked for, and we will help you work out which level makes sense.
Get A Complimentary Evaluation
Our Location
9900 13th Avenue North, Suite 270,
Plymouth MN 55441
