fda-consultant-specialist

Guide medical device teams through FDA submission pathways and compliance planning.

Updated Dec 23, 2024
One-click install
npx skills add https://github.com/salamientark/dotfiles --skill fda-consultant-specialist-salamientark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fda-consultant-specialist
Source: https://github.com/salamientark/dotfiles/tree/main/claude/skills/ra-qm-team/fda-consultant-specialist
Command: npx skills add https://github.com/salamientark/dotfiles --skill fda-consultant-specialist-salamientark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

FDA regulatory navigation and pathway decision-making for medical device teams, guiding them to select the appropriate submission routes (510(k), De Novo, PMA) and align with FDA expectations, while also addressing QSR (820) compliance, HIPAA assessments, and cybersecurity considerations across the product lifecycle.

Core Features & Use Cases

  • Guidance on 510(k)/PMA/De Novo submission pathways and predicate device evaluation.
  • QSR (21 CFR 820) compliance planning, HIPAA assessments, and device cybersecurity considerations.
  • Use cases include regulatory strategy development, risk assessment planning, and documentation readiness for submissions.

Quick Start

Describe your device, intended use, and target FDA submission path to generate a regulatory plan.

Frequently Asked Questions about fda-consultant-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine the right FDA submission pathway for a new medical device?

FDA submission pathway selection depends on your medical device classification and intended use, guiding the choice between 510(k), De Novo, or PMA. Evaluating predicate devices and analyzing risk assessments help align your product with the correct regulatory route.

What is the difference between 510(k), De Novo, and PMA submissions?

The difference between 510(k), De Novo, and PMA submissions lies in risk level and predicate availability. 510(k) requires a predicate device, De Novo is for novel low-to-moderate risk devices without a predicate, and PMA applies to high-risk devices requiring clinical data validation.

How do I plan QSR compliance under 21 CFR 820 for a medical device?

Planning QSR compliance under 21 CFR 820 involves establishing quality system requirements across the medical device lifecycle. You generate documentation artifacts, conduct risk assessments, and integrate cybersecurity and HIPAA considerations to meet FDA expectations for manufacturing and post-market surveillance.

When do I need a De Novo classification instead of a 510(k) for my medical device?

You need a De Novo classification instead of a 510(k) when your medical device is low-to-moderate risk but lacks a legally marketed predicate device. The De Novo pathway establishes a new regulatory classification, whereas 510(k) requires demonstrating substantial equivalence to an existing device.

Does my medical device submission need to include cybersecurity and HIPAA considerations?

Medical device submissions increasingly require cybersecurity and HIPAA considerations if the device handles patient data or connects to networks. Integrating these assessments into your risk management and documentation artifacts ensures compliance with FDA expectations across the product lifecycle.

What documentation artifacts are required for a 510(k) or PMA submission?

Required documentation artifacts for 510(k) or PMA submissions include device descriptions, intended use statements, and comprehensive risk assessments. You must compile these artifacts to demonstrate substantial equivalence or safety and effectiveness, satisfying FDA submission requirements and QSR compliance planning.