HITRUST certification has become a common requirement for organizations that handle sensitive healthcare data — and increasingly for vendors in other industries too. But "get HITRUST certified" now means choosing among three different assessments. Picking the right one can save months of effort.
Why HITRUST?
The HITRUST CSF harmonizes requirements from many authoritative sources — including HIPAA, NIST, ISO, PCI DSS and others — into a single, certifiable framework. Two features set HITRUST apart from many other assessments:
- Centralized quality assurance. Every validated assessment is reviewed by HITRUST before certification is issued.
- Inheritance. Organizations can inherit control results from participating cloud and service providers, reducing duplicate work.
The three validated assessments
e1: Essentials, one-year
The e1 assessment focuses on 44 foundational cybersecurity requirements — the essential practices every organization should have in place. It's designed for lower-risk relationships, smaller organizations and companies just beginning their HITRUST journey. An e1 provides moderate assurance and requires less effort than the other options.
i1: Implemented, one-year
The i1 assessment covers 182 requirements representing leading security practices. It's a significant step up from the e1 in breadth and rigor, and it evaluates whether requirements are implemented. Many organizations use the i1 to demonstrate a solid program to customers that don't require the full r2.
r2: Risk-based, two-year
The r2 assessment is the most comprehensive. Its scope is tailored based on your organization's risk factors, systems and regulatory requirements, so the number of requirements varies — often several hundred. The r2 evaluates maturity more deeply, including policy, procedure and implementation. r2 certifications are valid for two years with an interim assessment at the one-year mark.
| e1 | i1 | r2 | |
|---|---|---|---|
| Requirements | 44 | 182 | Tailored (varies) |
| Assurance level | Moderate | Moderate-high | High |
| Certification period | 1 year | 1 year | 2 years (with interim) |
| Typical use | Startups, lower-risk vendors | Established programs, many vendor relationships | Higher-risk relationships, large enterprises |
How to choose
1. Start with your customers. The most important question is which assessments your customers and partners accept. Some health systems require an r2 for any vendor with access to PHI; others accept an i1 or even an e1 depending on the relationship.
2. Consider your risk profile. If you handle large volumes of sensitive data, operate critical systems or face regulatory scrutiny, an r2 may be appropriate regardless of customer requirements.
3. Be realistic about maturity and timing. If your program is still developing, an e1 or i1 can deliver a certification sooner while you build toward an r2.
4. Think about the path, not just the first step. Organizations often progress from e1 to i1 to r2 as their programs and customer base mature. Work done at each level carries forward.
Preparing for a successful assessment
- Scope carefully. Include the systems and facilities that matter to your customers — no more, no less.
- Use inheritance from your cloud providers where available.
- Align policies with practice. Assessors test that what's written matches what's done.
- Perform a readiness assessment to identify gaps before the validated assessment begins.
- Plan for HITRUST's QA review in your overall timeline.
The bottom line
HITRUST's tiered model lets you match assurance to risk. Ask what your customers accept, be honest about your program's maturity and choose the assessment that gets you credible assurance on a realistic timeline — with a path to grow.