Start hereAgree the assessment type and boundary
~122 days leftOpen step
Guide library
Certification Global

HITRUST certification

HITRUST Essentials (e1), Implemented (i1) and Risk-based (r2) validated assessments

Choose an assessment that meets the requester’s needs and prepare evidence for independent validation.

Who it applies to

Organizations seeking HITRUST assurance for a defined system, frequently in healthcare and related services.

What you’ll produce

A validated assessment and certification decision if the selected program’s criteria are met.

Confirm the required assessment and scope with the requesting organization. Passing a framework assessment does not settle separate legal duties.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What do we need the certification to cover?
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

HITRUST certification kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Agree the assessment type and boundary · Compliance + customer owner [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What assessment, system and reporting outcome did the customer specify?
  • Can owners show that each control actually operates across the environment you plan to include?

Worked scenario

A health software vendor receives an i1 request from a customer. It confirms which hosting and support components must be in scope, tests evidence from the actual product and keeps a record of shared or inherited controls.

What to read next

  • HIPAA

    Assess statutory health-data obligations independently.

  • SOC 2

    Compare the CPA report customers may ask for in addition to HITRUST.

The whole journeyabout 122 days across 4 steps
  1. 01Agree the assessment type and boundaryCompliance + customer owner · ~21 days
  2. 02Build the evidence set and close readiness gapsControl owners + readiness team · ~45 days
  3. 03Support independent validation and reviewExternal assessor + compliance · ~42 days
  4. 04Maintain the result and plan reassessmentRisk governance + compliance · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Agree the assessment type and boundaryCompliance + customer ownerBefore engaging the assessorSet a start dateScope memo; System inventory; Responsibility matrixOpen
Build the evidence set and close readiness gapsControl owners + readiness teamBefore validationSet a start dateControl matrix; Evidence index; Remediation trackerOpen
Support independent validation and reviewExternal assessor + complianceDuring assessment and program reviewSet a start dateAssessment evidence; Response log; Remediation planOpen
Maintain the result and plan reassessmentRisk governance + complianceFollowing issuanceSet a start dateCertification decision; Renewal calendar; Corrective actionsOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Agree the assessment type and boundary

    Who Compliance + customer owner When Before engaging the assessor

    Confirm e1, i1 or r2 and current program rules. Define systems, locations, providers, scope factors and responsibility for shared controls.

    What to produce

    Scope memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    System inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    Responsibility matrixMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

  2. 02

    Build the evidence set and close readiness gaps

    Who Control owners + readiness team When Before validation

    Map applicable requirements and test supporting records. Capture approvals, control dates and scoped assets, and assign gaps before the assessment period.

    What to produce

    Control matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Evidence indexSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Remediation trackerSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  3. 03

    Support independent validation and review

    Who External assessor + compliance When During assessment and program review

    Provide complete evidence and resolve requests. Track scoring, corrective plans and submissions in the program’s current workflow.

    What to produce

    Assessment evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Response logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Remediation planSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  4. 04

    Maintain the result and plan reassessment

    Who Risk governance + compliance When Following issuance

    Record certified scope, applicable interim or renewal milestones, control changes and follow-up actions.

    What to produce

    Certification decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Renewal calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

    Corrective actionsSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes