|
1 | 1 | { |
2 | 2 | "mapping_info": { |
3 | | - "haaisvs_version": "1.0", |
| 3 | + "haarf_version": "1.0", |
4 | 4 | "target_framework": "FDA Digital Health Guidance & Medical Device Regulations", |
5 | 5 | "target_version": "2024 Updates", |
6 | 6 | "mapping_date": "2025-01-10", |
|
10 | 10 | }, |
11 | 11 | "mappings": [ |
12 | 12 | { |
13 | | - "haaisvs_requirement": "1.1.1", |
14 | | - "haaisvs_description": "Three-factor risk assessment (clinical function, autonomy, data sensitivity)", |
| 13 | + "haarf_requirement": "1.1.1", |
| 14 | + "haarf_description": "Three-factor risk assessment (clinical function, autonomy, data sensitivity)", |
15 | 15 | "target_requirements": ["21 CFR 814.20(b)(1)", "Digital Health Guidance v1.0 Section 3.2"], |
16 | 16 | "alignment_type": "direct", |
17 | 17 | "notes": "FDA requires risk assessment for medical device classification - HAARF three-factor approach directly supports FDA Class determination", |
18 | 18 | "compliance_evidence": "Risk assessment documentation showing clinical function analysis, autonomy level classification, and data sensitivity evaluation" |
19 | 19 | }, |
20 | 20 | { |
21 | | - "haaisvs_requirement": "1.2.1", |
22 | | - "haaisvs_description": "FDA-style PCCP implementation for high-risk AI agents", |
| 21 | + "haarf_requirement": "1.2.1", |
| 22 | + "haarf_description": "FDA-style PCCP implementation for high-risk AI agents", |
23 | 23 | "target_requirements": ["FDA PCCP Guidance 2023", "21 CFR 814.39"], |
24 | 24 | "alignment_type": "direct", |
25 | 25 | "notes": "Direct implementation of FDA PCCP requirements for AI/ML medical devices", |
26 | 26 | "compliance_evidence": "PCCP documentation including modification types, validation protocols, performance criteria, and change control procedures" |
27 | 27 | }, |
28 | 28 | { |
29 | | - "haaisvs_requirement": "1.3.1", |
30 | | - "haaisvs_description": "Continuous clinical performance monitoring", |
| 29 | + "haarf_requirement": "1.3.1", |
| 30 | + "haarf_description": "Continuous clinical performance monitoring", |
31 | 31 | "target_requirements": ["FDA Real-World Performance Study Guidance", "21 CFR 814.82"], |
32 | 32 | "alignment_type": "direct", |
33 | 33 | "notes": "Supports FDA post-market surveillance and real-world performance monitoring requirements", |
34 | 34 | "compliance_evidence": "Clinical performance monitoring plan, statistical analysis protocols, and performance degradation alert systems" |
35 | 35 | }, |
36 | 36 | { |
37 | | - "haaisvs_requirement": "2.1.2", |
38 | | - "haaisvs_description": "Health Canada SGBA+ documentation and bias assessment", |
| 37 | + "haarf_requirement": "2.1.2", |
| 38 | + "haarf_description": "Health Canada SGBA+ documentation and bias assessment", |
39 | 39 | "target_requirements": ["FDA Diversity Action Plans", "FDA Medical Device Cybersecurity Guidance"], |
40 | 40 | "alignment_type": "partial", |
41 | 41 | "notes": "FDA diversity requirements less comprehensive than Health Canada SGBA+ but HAARF addresses both", |
42 | 42 | "compliance_evidence": "Demographic diversity analysis, bias assessment documentation, and mitigation strategies" |
43 | 43 | }, |
44 | 44 | { |
45 | | - "haaisvs_requirement": "2.3.1", |
46 | | - "haaisvs_description": "Explainable AI with clinically meaningful insights", |
| 45 | + "haarf_requirement": "2.3.1", |
| 46 | + "haarf_description": "Explainable AI with clinically meaningful insights", |
47 | 47 | "target_requirements": ["FDA Software Pre-Cert Guidance", "21 CFR 820.30"], |
48 | 48 | "alignment_type": "direct", |
49 | 49 | "notes": "FDA design controls require understanding of software function - XAI supports clinical validation requirements", |
50 | 50 | "compliance_evidence": "XAI implementation documentation, clinical validation of explanations, healthcare professional usability testing" |
51 | 51 | }, |
52 | 52 | { |
53 | | - "haaisvs_requirement": "3.1.1", |
54 | | - "haaisvs_description": "Healthcare-specific adversarial robustness testing", |
| 53 | + "haarf_requirement": "3.1.1", |
| 54 | + "haarf_description": "Healthcare-specific adversarial robustness testing", |
55 | 55 | "target_requirements": ["FDA Medical Device Cybersecurity Guidance", "21 CFR 820.30(g)"], |
56 | 56 | "alignment_type": "partial", |
57 | 57 | "notes": "FDA cybersecurity guidance covers general threats - HAARF adds AI-specific adversarial testing", |
58 | 58 | "compliance_evidence": "Adversarial testing protocols, robustness validation results, and threat model documentation" |
59 | 59 | }, |
60 | 60 | { |
61 | | - "haaisvs_requirement": "4.1.1", |
62 | | - "haaisvs_description": "Clinical accountability frameworks for healthcare professionals", |
| 61 | + "haarf_requirement": "4.1.1", |
| 62 | + "haarf_description": "Clinical accountability frameworks for healthcare professionals", |
63 | 63 | "target_requirements": ["FDA Human Factors Guidance", "21 CFR 820.30(h)"], |
64 | 64 | "alignment_type": "direct", |
65 | 65 | "notes": "FDA human factors requirements directly supported by HAARF clinical accountability frameworks", |
66 | 66 | "compliance_evidence": "Clinical oversight procedures, healthcare professional competency requirements, and accountability documentation" |
67 | 67 | }, |
68 | 68 | { |
69 | | - "haaisvs_requirement": "8.1.1", |
70 | | - "haaisvs_description": "Role-based tool access controls for healthcare AI agents", |
| 69 | + "haarf_requirement": "8.1.1", |
| 70 | + "haarf_description": "Role-based tool access controls for healthcare AI agents", |
71 | 71 | "target_requirements": ["FDA Medical Device Interoperability Guidance", "21 CFR 820.30"], |
72 | 72 | "alignment_type": "direct", |
73 | 73 | "notes": "Critical FDA priority - tool access controls essential for medical device integration safety", |
74 | 74 | "compliance_evidence": "Tool authorization matrix, clinical appropriateness validation, and access control audit trails" |
75 | 75 | }, |
76 | 76 | { |
77 | | - "haaisvs_requirement": "8.3.1", |
78 | | - "haaisvs_description": "FDA-regulated medical device integration maintaining classification integrity", |
| 77 | + "haarf_requirement": "8.3.1", |
| 78 | + "haarf_description": "FDA-regulated medical device integration maintaining classification integrity", |
79 | 79 | "target_requirements": ["FDA Medical Device Interoperability Guidance", "21 CFR 807"], |
80 | 80 | "alignment_type": "direct", |
81 | 81 | "notes": "Directly addresses FDA's highest priority concern - tool integration without altering device classification", |
82 | 82 | "compliance_evidence": "Device classification impact analysis, interoperability validation, safety function verification" |
83 | 83 | }, |
84 | 84 | { |
85 | | - "haaisvs_requirement": "8.7.1", |
86 | | - "haaisvs_description": "Regulatory classification analysis for tool combinations", |
| 85 | + "haarf_requirement": "8.7.1", |
| 86 | + "haarf_description": "Regulatory classification analysis for tool combinations", |
87 | 87 | "target_requirements": ["FDA Device Classification", "510(k) Guidance", "Combination Product Guidance"], |
88 | 88 | "alignment_type": "direct", |
89 | 89 | "notes": "Essential for determining correct FDA submission pathway for tool-enabled agents", |
|
113 | 113 | } |
114 | 114 | }, |
115 | 115 | "coverage_analysis": { |
116 | | - "total_haaisvs_requirements": 279, |
| 116 | + "total_haarf_requirements": 279, |
117 | 117 | "mapped_to_fda": 234, |
118 | 118 | "direct_alignment": 185, |
119 | 119 | "partial_alignment": 49, |
|
0 commit comments