Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathwa...
数据来源:ClawHub。 在 ClawSkills 查看
选择你使用的 Agent
方法一:命令行安装(推荐)
推荐(无需提前安装 clawhub)
npx clawhub@latest --dir ~/.claude/skills install regulatory-affairs-head或使用 clawhub CLI(需提前安装)
clawhub --dir ~/.claude/skills install regulatory-affairs-head⚠️ 需要 Node.js 18+,没有 Node?请使用下方方法二直接下载 ZIP。 安装 Node.js →
方法二:手动下载安装(无需 Node)
下载 ZIP,解压后将文件夹放到以下路径,重启 Agent 即可:
安装路径
~/.claude/skills/regulatory-affairs-head/💡解压后将文件夹放到上方路径,重启 Agent 即可生效
--- name: "regulatory-affairs-head" description: Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access. triggers: - regulatory strategy - FDA submission - EU MDR - 510(k) - PMA approval - CE marking - regulatory pathway - market access - clinical evidence - regulatory intelligence - submission planning - notified body ---
Regulatory strategy development, submission management, and global market access for medical device organizations.
---
---
Develop regulatory strategy aligned with business objectives and product characteristics.
- Intended use and indications - Device classification (risk level) - Technology platform - Target markets and timeline
- FDA (US): 21 CFR Part 820, 510(k)/PMA/De Novo - EU: MDR 2017/745, Notified Body requirements - Other markets: Health Canada, PMDA, NMPA, TGA
- Compare submission types (510(k) vs De Novo vs PMA) - Assess predicate device availability - Evaluate clinical evidence requirements
| Factor | 510(k) | De Novo | PMA | |--------|--------|---------|-----| | Predicate Available | Yes | No | N/A | | Risk Level | Low-Moderate | Low-Moderate | High | | Clinical Data | Usually not required | May be required | Required | | Review Time | 90 days (MDUFA) | 150 days | 180 days | | User Fee | ~$22K (2024) | ~$135K | ~$440K | | Best For | Me-too devices | Novel low-risk | High-risk, novel |
REGULATORY STRATEGY
Product: [Name] Version: [X.X] Date: [Date]
1. PRODUCT OVERVIEW
Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]
Device classification: [Class I / II / III]
Technology: [Brief description, e.g., "AI-powered wound-imaging software, SaMD"]
2. TARGET MARKETS & TIMELINE
| Market | Pathway | Priority | Target Date |
|--------|----------------|----------|-------------|
| USA | 510(k) / PMA | 1 | Q1 20XX |
| EU | Class [X] MDR | 2 | Q2 20XX |
3. REGULATORY PATHWAY RATIONALE
FDA: [510(k) / De Novo / PMA] — Predicate: [K-number or "none"]
EU: Class [X] via [Annex IX / X / XI] — NB: [Name or TBD]
Rationale: [2–3 sentences on key factors driving pathway choice]
4. CLINICAL EVIDENCE STRATEGY
Requirements: [Summarize what each market needs, e.g., "510(k): bench + usability; EU Class IIb: PMCF study"]
Approach: [Literature review / Prospective study / Combination]
5. RISKS AND MITIGATION
| Risk | Prob | Impact | Mitigation |
|------------------------------|------|--------|-----------------------------------|
| Predicate delisted by FDA | Low | High | Identify secondary predicate now |
| NB audit backlog | Med | Med | Engage NB 6 months before target |
6. RESOURCE REQUIREMENTS
Budget: $[Amount] Personnel: [FTEs] External: [Consultants / CRO]
---
Prepare and submit FDA regulatory applications.
- Predicate device identified (note K-number, e.g., K213456) - Substantial equivalence (SE) argument supportable on intended use and technological characteristics - No new intended use or technology concerns triggering De Novo
- [ ] Cover letter with device name, product code, and predicate K-number - [ ] Section 1: Administrative information (applicant, contact, 510(k) type) - [ ] Section 2: Device description — include photos, dimensions, materials list - [ ] Section 3: Intended use and indications for use - [ ] Section 4: Substantial equivalence comparison table (see example below) - [ ] Section 5: Performance testing — protocols, standards cited, pass/fail results - [ ] Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact) - [ ] Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable) - [ ] Section 8: Labeling — final draft IFU, device label - [ ] Section 9: Summary and conclusion
| Characteristic | Predicate (K213456) | Subject Device | Same? | Notes | |----------------|---------------------|----------------|-------|-------| | Intended use | Wound measurement | Wound measurement | ✓ | Identical | | Technology | 2D camera | 2D + AI analysis | ✗ | New TC; address below | | Energy type | Non-energized | Non-energized | ✓ | | | Patient contact | No | No | ✓ | | | SE conclusion | New TC does not raise new safety/effectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate) |
- Class III device or no suitable predicate - Clinical data strategy defined
- IDE approval - Clinical protocol execution - Study report completion
- [ ] Volume I: Administrative, device description, manufacturing - [ ] Volume II: Nonclinical studies (bench, animal, biocompatibility) - [ ] Volume III: Clinical studies (IDE protocol, data, statistical analysis) - [ ] Volume IV: Labeling - [ ] Volume V: Manufacturing information, sterilization
...
安装 Regulatory Affairs Head 后,可以对 AI 说这些话来触发它
Help me get started with Regulatory Affairs Head
Explains what Regulatory Affairs Head does, walks through the setup, and runs a quick demo based on your current project
Use Regulatory Affairs Head to senior Regulatory Affairs Manager for HealthTech and MedTech companies
Invokes Regulatory Affairs Head with the right parameters and returns the result directly in the conversation
What can I do with Regulatory Affairs Head in my marketing & growth workflow?
Lists the top use cases for Regulatory Affairs Head, with example commands for each scenario
将技能文件夹放到 ~/.claude/skills/regulatory-affairs-head/ 目录(个人级,所有项目可用),或 .claude/skills/regulatory-affairs-head/(项目级)。重启 AI 客户端后,用 /regulatory-affairs-head 主动调用,或让 AI 根据上下文自动发现并使用。
Regulatory Affairs Head 支持 Claude、Cursor、OpenClaw,可与这些 AI 平台无缝集成,扩展其能力。
Regulatory Affairs Head 可免费安装使用。请查阅仓库了解许可证信息。
Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathwa...
Regulatory Affairs Head 属于「Marketing & Growth」分类,该分类的技能帮助 AI 智能体在此领域执行专业任务。
Automate my marketing & growth tasks using Regulatory Affairs Head
Identifies repetitive steps in your workflow and sets up Regulatory Affairs Head to handle them automatically