Regulations/AI MedTech / SaMD/Evidence Readiness
Evidence Readiness · AI MedTech / SaMD

Evidence Readiness for AI MedTech / SaMD.

This page converts regulatory reading into evidence-readiness. It defines the records, owners, review questions, and trace fields that make a future checklist or readiness review defensible.

Source basis: AI/ML-enabled device software, SaMD, and change-control guidanceUse: evidence-readinessBoundary: not legal advice
AI MedTech / SaM TRACE FDA AI/ML SAMD HUBFDA PCCP GUIDANCFDA LIFECYCLE-MAFDA AI-ENABLED D
/ Evidence objects

Readiness becomes visible through records.

AI MedTech / SaMD
Evidence 01

Intended-use and clinical workflow map

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 02

Software function description

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 03

Training/validation data summary

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 04

Performance evaluation report

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 05

Human factors/oversight rationale

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 06

PCCP description

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 07

Modification protocol

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 08

Transparency/user information file

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 09

Post-market monitoring plan

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

Evidence 10

Real-world performance review log

Keep this as a named evidence object for AI MedTech / SaMD: source basis, owner, status, review question, and update trigger should be visible before reuse.

/ Readiness questions

Each object needs review before reuse.

question bank
Question 01

Intended-use and clinical workflow map

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 02

Software function description

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 03

Training/validation data summary

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 04

Performance evaluation report

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 05

Human factors/oversight rationale

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 06

PCCP description

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 07

Modification protocol

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?

Question 08

Transparency/user information file

Ask: who owns it, what source does it trace to, what evidence exists, what is missing, and what should not be claimed?