Safety-Critical Medical Device Firmware Code Review
Review medical device firmware for safety, compliance, and critical defects
What You Can Do
This skill performs rigorous code review of safety-critical medical device firmware, identifying compliance gaps, security vulnerabilities, and design defects that could impact patient safety. You submit firmware code snippets or full modules, and Claude analyzes them against FDA guidance, IEC 62304 standards, and embedded systems best practices. The skill flags issues before they reach certification or production, categorizes risk levels, and provides specific remediation guidance.
Features
buffer overflows, use-after-free, race conditions
cryptographic misuse, unvalidated inputs, hardcoded secrets
Example Output
Code Review Summary
File: patient_monitor_v2.1.c
Risk Level: CRITICAL (2 issues found)
Issue #1: Buffer Overflow in Sensor Handler (CRITICAL)
Location: Line 127, memcpy(buffer, sensor_data, length);
Problem: No bounds checking on incoming sensor data
Risk: Stack overflow → arbitrary code execution → device compromise
FDA Guideline: 21 CFR Part 11.10(e) — software validation
Remediation: Add bounds check: if (length > BUFFER_MAX) return ERROR_OVERFLOW;
Issue #2: Unprotected Shared State (MAJOR)
Location: Lines 45-63, waveform_data race condition
Problem: Interrupt handler and main loop access waveform_data without synchronization
Risk: Torn writes → corrupted vital sign displays → clinical misdiagnosis
IEC 62304 Clause: 7.3.4 (FMEA mitigation)
Remediation: Wrap access with mutex_lock/unlock
Compliance Scorecard
- ✅ Input validation: 3/5 functions compliant
- ⚠️ Memory safety: 1 critical defect found
- ❌ Real-time determinism: No WCET analysis
- ✅ Approved cryptography: AES-256 (compliant)
- ⚠️ Error handling: Missing recovery paths in 2 places
What's Included
- SKILL.md: Complete firmware review methodology with decision trees and checklists
- FDA 21 CFR Part 11 Compliance Checklist: Automated validation against software requirements
- IEC 62304:2015 Traceability Worksheet: Map code to design and verification documents
- Common Medical Device Code Defects Library: Pattern reference for buffer overflows, race conditions, crypto misuse
- Risk Assessment Template: Quantify patient safety impact for each finding
- Remediation Response Tracker: Document fixes and evidence of resolution
Who It's For
- Firmware engineers preparing code for FDA 510(k) or PMA submissions
- Medical device QA/compliance specialists reviewing design changes and vendor code
- Embedded systems architects designing patient-facing or life-critical modules
- Regulatory affairs teams preparing for pre-submission meetings with FDA
- Clinical engineering teams validating third-party or legacy device firmware
Best For
- Pre-certification code review (identify defects before FDA inspection)
- Security vulnerability assessment in connected medical devices
- Compliance gap analysis — verify firmware meets IEC 62304 and FDA requirements
- Post-incident forensics — root cause analysis after adverse events
- Vendor firmware vetting — evaluate firmware from acquired or partnered companies
You might also like
You can accelerate your entire antenna design workflow—from initial concept to optimized specifications—by leveraging Claude's knowledge of electromagnetic theory, antenna types, and design trade-offs. Claude helps you parameterize designs, identify optimal configurations for your frequency band and application, and prepare detailed briefs for simulation and manufacturing. You'll generate design reviews, impedance-matching solutions, and validation checklists without context-switching to multiple tools.
Rapidly analyze production incidents by correlating observability signals—logs, metrics, traces, and events—to identify the true root cause instead of symptoms. You'll reconstruct incident timelines, quantify impact scope, and generate both immediate remediation steps and long-term prevention measures.
This skill guides you through designing Kalman filters for your specific state estimation and sensor fusion problems. You'll learn to diagnose filter divergence, tune covariance matrices (Q and R), and validate observability—turning mathematical theory into production-ready filters. The skill provides step-by-step workflows, diagnostic tools, and practical templates for common applications like GPS/IMU fusion, SLAM, and aircraft navigation.
Claude analyzes your code diffs and generates standardized commit messages that follow the Conventional Commits specification. The skill automatically determines the correct commit type, scope, and description based on the changes you've made, ensuring your messages are parseable by automation tools while remaining human-readable for code reviewers.
You'll transform high-level feature requirements into a complete development plan covering API design, frontend implementation, testing strategy, and documentation. The skill helps you identify dependencies, parallelize work across frontend and backend teams, and establish quality gates that ensure features ship bug-free with proper error handling and logging.
Transform schema and data changes into production-ready migration packages that protect data integrity and minimize downtime. You can handle column additions, renames, type conversions, and backfills using proven patterns like expand-contract and shadow tables. The skill generates explicit rollback scripts, validation checklists, and phased execution plans that keep applications stable throughout the migration.
You can design end-to-end NGS pipelines tailored to your experiment type (WGS, WES, RNA-seq, targeted), troubleshoot pipeline failures by analyzing QC metrics and logs, and optimize performance by fine-tuning parameters and identifying bottlenecks. This skill handles the full workflow from raw sequencing data quality assessment through variant interpretation and annotation.
You can rapidly design, optimize, and validate chromatographic and LC-MS/MS methods for analyzing drugs and metabolites in biological matrices. This skill guides you through analytical method development workflows—including parameter selection, sensitivity optimization, and regulatory strategy—while ensuring ICH Q2(R2) and FDA compliance throughout the development process.