4.1.1-1 | Stating the medical purposes | 0 |
4.1.1-2 | Stating the intended disease or condition | 0 |
4.1.1-3 | Stating the intended patient populations | 0 |
4.1.1-4 | Stating the intended users | 0 |
4.1.1-5 | Stating the intended use environment | 0 |
4.1.1-6 | Stating contraindications | 0 |
4.1.1-7 | Describing function, inputs, outputs and workflow | 0 |
4.2.1-Intended-Disease-or-Condition | Target disease or condition and its state | 0 |
4.2.1-Intended-Patient-Population | Intended patient population boundary | 0 |
4.2.1-Medical-Purpose | Medical purpose the software serves | 0 |
4.2.2-Intended-Use-Environment | Intended use environment and how remote it is | 0 |
4.2.2-Intended-User | Intended user of the software | 0 |
4.2.2-Role-of-Software-and-Output-Within-the-Healthcare-Task-Intervention | Part played by the software output in the care task | 0 |
4.2.2-Timing-Within-Healthcare-Task-Intervention | When the output falls within the care task | 0 |
4.2.3-Degree-of-Autonomy | How far the software acts without user control | 0 |
4.2.3-Destination-Target-of-Output | Destination or target of the output | 0 |
4.2.3-Explainability-of-Software-and-Output | How far the software logic and output can be explained | 0 |
4.2.3-Input-Source | Where the software inputs come from | 0 |
4.2.3-Output-Type | Kind of output the software produces | 0 |
4.2.4-Degree-of-Learning-Change-Management-Autonomy | Autonomy of learning and change management | 0 |
4.2.4-Domain-of-Learning-Change-Implementation | Domain or scope of learning and change | 0 |
4.2.4-Installation-Update-and-Error-Correction-Infrastructure | Infrastructure for installation, updates and error correction | 0 |
5-Key-Point-1 | Consider direct and indirect harms | 0 |
5-Key-Point-2 | Hazards arising from information and loss of effectiveness | 0 |
5-Key-Point-3 | Harms depend on intended use | 0 |
5.1 | Understand the software before assessing risk | 0 |
5.1-a | Ask why each characteristic matters | 0 |
5.1-b | Account for interdependencies between characteristics | 0 |
5.1-c | Use the characterization questions to find hazards | 0 |
5.1-d | Show whether software changes device risk | 0 |
5.2 | Estimate risk from likelihood and severity | 0 |
5.2-a | Assess severity of direct and indirect harm | 0 |
5.2-b | Set software failure likelihood to one | 0 |
5.2-c | Contextualize severity with the guiding questions | 0 |
5.2-d | Check for single-point software failure | 0 |
5.3 | Categorize early and before controls | 0 |
5.3-a | Allow interdependence and unequal weighting | 0 |
APP-A | Sample intended use statement | 0 |
APP-B | Summary table of characterization features | 0 |
APP-C | Questions for finding software hazards | 0 |
APP-D | Worked examples linking features to risk | 0 |
APP-E | Paired examples comparing risk considerations | 0 |
CL1 | Introduction and background to the guidance | 0 |
CL2.1 | Aim of the document | 0 |
CL2.2 | Scope of the document | 0 |
CL4 | Why medical device characterization matters | 0 |
CL4.1 | Purpose of the intended use statement | 0 |
CL4.2 | Medical device software description and characterization categories | 0 |
CL5 | Software risk characterization overview | 0 |
CL5.3-b | Recognize jurisdictional differences | 0 |
CL6 | Implementation considerations for jurisdictions | 0 |