fda-consultant-specialist

Guide medical device manufacturers through FDA 510(k), PMA, and De Novo submissions.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nuwanda04/Ballen-Fisk --skill fda-consultant-specialist-nuwanda04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fda-consultant-specialist
Source: https://github.com/Nuwanda04/Ballen-Fisk/tree/main/.cursor/skills/fda-consultant-specialist
Command: npx skills add https://github.com/Nuwanda04/Ballen-Fisk --skill fda-consultant-specialist-nuwanda04

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the complex and time-consuming process of understanding and complying with FDA regulations for medical devices, helping companies bring their products to market faster and more efficiently.

Core Features & Use Cases

  • Pathway Guidance: Determines the correct FDA submission pathway (510(k), PMA, De Novo).
  • Regulatory Compliance: Provides detailed information on QSR (21 CFR 820), HIPAA, and device cybersecurity requirements.
  • Use Case: A startup developing a new diagnostic device needs to understand the regulatory requirements. They can use this Skill to identify the appropriate submission pathway, understand the necessary documentation, and ensure compliance with cybersecurity and HIPAA standards from the outset.

Quick Start

Use the fda-consultant-specialist skill to explain the difference between a 510(k) and a PMA submission.

Frequently Asked Questions about fda-consultant-specialist

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

FAQPage Schema
What is the difference between a 510(k) and a PMA submission for medical devices?

A 510(k) submission demonstrates substantial equivalence to a predicate device, while PMA requires comprehensive clinical data for high-risk devices. This Skill clarifies these FDA regulatory pathways to help manufacturers identify the correct submission route.

How do I ensure medical device cybersecurity compliance for FDA submissions?

Medical device cybersecurity compliance requires meeting specific FDA requirements for protecting device software and data. This Skill provides detailed guidance on integrating cybersecurity standards into your regulatory submission process.

When do I need a HIPAA assessment for my medical device?

A HIPAA assessment is needed when your medical device handles protected health information. This Skill offers detailed information on conducting HIPAA assessments to ensure your device meets regulatory compliance standards.

How to navigate Quality System Regulation 21 CFR 820 compliance?

Navigating 21 CFR 820 compliance involves establishing robust quality system requirements for medical device manufacturing. This Skill provides detailed information on meeting QSR standards to ensure your product complies with FDA regulations.

Does the De Novo pathway suit a new diagnostic device with no predicate?

The De Novo pathway suits novel low-to-moderate risk devices lacking a legally marketed predicate. This Skill helps determine if De Novo is the appropriate FDA submission pathway for your specific diagnostic device.

What are the limitations of using automated guidance for FDA regulatory pathways?

Automated guidance provides regulatory pathway information but cannot replace official FDA clearance or legal review. Use this Skill to understand requirements for 510(k), PMA, and De Novo submissions, but consult experts for final approval.