HITRUST certification
Choose an assessment that meets the requester’s needs and prepare evidence for independent validation.
ISO 13485:2016 quality management systems for medical devices
Build a medical-device quality system around design, supplier control, production and post-market feedback.
Organizations involved in relevant stages of the medical-device lifecycle and suppliers operating under the applicable quality requirements.
A documented quality management system and, when pursued and awarded, a certificate for its audited scope.
An ISO 13485 QMS can support market entry. Use each market’s legal requirements for clearance, licensing, inspection and post-market 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.
ISO 13485 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 Define the QMS scope and market requirements · Quality lead + regulatory affairs [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 device company outsources assembly but keeps design and complaints in-house. The quality lead puts those handoffs on the process map and tracks how supplier changes reach design, production and post-market teams.
Connect the QMS to U.S. classification, submissions and post-market obligations.
Check device-licence evidence and the MDSAP certificate route.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Define the QMS scope and market requirements | Quality lead + regulatory affairs | Before changing procedures | Set a start date | Scope statement; Obligations register | Open |
| Trace design, purchasing and production controls | Design assurance + supplier quality | Before routine production | Set a start date | Risk file; Control matrix; QMS records | Open |
| Run feedback and corrective action | Post-market lead + quality | Ongoing | Set a start date | Vigilance logs; CAPA log; Management review minutes | Open |
| Audit the system and resolve findings | Internal audit + certification body as applicable | Before an external audit and at follow-up | Set a start date | Internal audit report; Corrective-action register; Certification decision | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify devices, sites, roles and outsourced activities. Map applicable regulatory requirements and review any justified exclusion or non-applicability.
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.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Connect user needs, risk controls, verification and design changes. Assign supplier qualification and record validation of processes where required.
Fictional details. Use the same fields with evidence from your work.
Each control traces to a test or review and residual risk is resolved through the documented approval route.
Give the approved file to quality, product engineering and the submission or conformity lead.
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.
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.
Route complaints to investigation, vigilance and risk review where appropriate. Verify CAPA effectiveness and use trend data at management review.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
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.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Sample operating records, prepare independent internal audits and schedule assessments for the right site and product scope. Track corrective actions to closure.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for 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.
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.