ISO 13485
Build a medical-device quality system around design, supplier control, production and post-market feedback.
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.
Organizations seeking HITRUST assurance for a defined system, frequently in healthcare and related services.
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.
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
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.
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.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Agree the assessment type and boundary | Compliance + customer owner | Before engaging the assessor | Set a start date | Scope memo; System inventory; Responsibility matrix | Open |
| Build the evidence set and close readiness gaps | Control owners + readiness team | Before validation | Set a start date | Control matrix; Evidence index; Remediation tracker | Open |
| Support independent validation and review | External assessor + compliance | During assessment and program review | Set a start date | Assessment evidence; Response log; Remediation plan | Open |
| Maintain the result and plan reassessment | Risk governance + compliance | Following issuance | Set a start date | Certification decision; Renewal calendar; Corrective actions | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Confirm e1, i1 or r2 and current program rules. Define systems, locations, providers, scope factors and responsibility for shared controls.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Map applicable requirements and test supporting records. Capture approvals, control dates and scoped assets, and assign gaps before the assessment period.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Provide complete evidence and resolve requests. Track scoring, corrective plans and submissions in the program’s current workflow.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Record certified scope, applicable interim or renewal milestones, control changes and follow-up actions.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.