← ClaudeAtlas

ce-to-510klisted

Port CE Mark / UKCA medical device technical documentation into an FDA 510(k) submission package for AI/ML SaMD (Software as a Medical Device). Use when a user (typically a non-US medical device manufacturer with existing MDR / IVDR / UKCA technical files) wants to (1) plan a 510(k) submission, (2) identify and analyse a predicate device using FDA databases, (3) draft a Q-Submission (pre-sub) request, (4) map CE Mark documents to the FDA eCopy section structure, or (5) anticipate the AI/ML-specific deficiency questions FDA will ask. Built from real 510(k) clearance experience for an AI/ML imaging device, including the Additional Information / Interactive Feedback cycle. Triggers on "510k", "510(k)", "FDA submission", "pre-sub", "Q-sub", "predicate device", "substantial equivalence", "CE to FDA", "MDR to FDA", "AI/ML 510k".
smorrel1/claude-code-skills · ★ 2 · Data & Documents · score 65
Install: claude install-skill smorrel1/claude-code-skills
# CE Mark → FDA 510(k) Conversion for AI/ML Medical Devices ## Purpose Help a non-US manufacturer take an existing CE Mark / UKCA / MDR technical file for an AI/ML SaMD and produce: (1) a planning document, (2) a predicate device research and analysis, (3) a pre-submission (Q-Sub) request when appropriate, (4) a mapped 510(k) eCopy package structure with content gap list, (5) a strategic recommendation on whether to pursue a Pre-Sub. This skill encodes lessons from a recent (2023) AI/ML SaMD 510(k) clearance, including the full Additional Information Request and Interactive Feedback cycle. Patterns generalise across imaging, signal-processing, clinical-decision-support and other AI/ML SaMD; domain-specific examples are flagged inline. ## When to use Trigger when the user mentions any of: 510(k), FDA submission, Q-Sub / pre-sub, predicate search, substantial equivalence, converting MDR/CE/UKCA technical file to FDA, AI/ML 510(k), engaging an FDA regulatory consultant. Do **not** use for: De Novo, PMA, IVD CLIA, EUA, IDE, drug applications, CE/MDR-only work without FDA intent. ## Inputs the user must supply Before starting, get these from the user. If any are missing, ask before proceeding. 1. **Path** to their CE Mark / UKCA technical file root 2. **Device name** and version 3. **Intended use** statement (verbatim from current CE labelling) 4. **Candidate predicate K-numbers** if already suspected 5. **Trade-off context**: willing to revise the Indications for Use to