Head of Regulatory Affairs

Senior Regulatory Affairs Manager for HealthTech and MedTech companies.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/regulatory-affairs-head, including the files SKILL.md points to.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/ra-qm-team/skills/regulatory-affairs-head#main ~/.claude/skills/regulatory-affairs-head

For one project only, change the path to .claude/skills/regulatory-affairs-head. This skill also uses regulatory_tracker.py, fda-submission-guide.md, eu-mdr-submission-guide.md, global-regulatory-pathways.md, iso-regulatory-requirements.md — copying SKILL.md alone won't be enough. See the folder on GitHub.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Head of Regulatory Affairs

Show the full text482 lines
namedescriptiontriggers
regulatory-affairs-headSenior 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. - regulatory strategy - FDA submission - EU MDR - 510(k) - PMA approval - CE marking - regulatory pathway - market access - clinical evidence - regulatory intelligence - submission planning - notified body

Head of Regulatory Affairs

Regulatory strategy development, submission management, and global market access for medical device organizations.


Table of Contents


Regulatory Strategy Workflow

Develop regulatory strategy aligned with business objectives and product characteristics.

Workflow: New Product Regulatory Strategy
  1. Gather product information:
    • Intended use and indications
    • Device classification (risk level)
    • Technology platform
    • Target markets and timeline
  2. Identify applicable regulations per target market:
    • 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
  3. Determine optimal regulatory pathway:
    • Compare submission types (510(k) vs De Novo vs PMA)
    • Assess predicate device availability
    • Evaluate clinical evidence requirements
  4. Develop regulatory timeline with milestones
  5. Estimate resource requirements and budget
  6. Identify regulatory risks and mitigation strategies
  7. Obtain stakeholder alignment and approval
  8. Validation: Strategy document approved; timeline accepted; resources allocated
Regulatory Pathway Selection Matrix
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 Document Template
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]

FDA Submission Workflow

Prepare and submit FDA regulatory applications.

Workflow: 510(k) Submission
  1. Confirm 510(k) pathway suitability:
    • 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
  2. Schedule and conduct Pre-Submission (Q-Sub) meeting if needed (see Pre-Sub Decision)
  3. Compile submission package checklist:
    • 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
  4. Conduct internal review and quality check against FDA RTA checklist
  5. Prepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)
  6. Submit via FDA ESG portal with user fee payment
  7. Monitor MDUFA clock and respond to AI/RTA requests within deadlines
  8. Validation: Submission accepted; MDUFA date received; tracking system updated
Substantial Equivalence Comparison Example
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)
Workflow: PMA Submission
  1. Confirm PMA pathway:
    • Class III device or no suitable predicate
    • Clinical data strategy defined
  2. Complete IDE clinical study if required:
    • IDE approval
    • Clinical protocol execution
    • Study report completion
  3. Conduct Pre-Submission meeting
  4. Compile PMA submission checklist:
    • 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
  5. Submit original PMA application
  6. Address FDA questions and deficiencies
  7. Prepare for FDA facility inspection
  8. Validation: PMA approved; approval letter received; post-approval requirements documented
FDA Submission Timeline
Milestone 510(k) De Novo PMA
Pre-Sub Meeting Day -90 Day -90 Day -120
Submission Day 0 Day 0 Day 0
RTA Review Day 15 Day 15 Day 45
Substantive Review Days 15–90 Days 15–150 Days 45–180
Decision Day 90 Day 150 Day 180
Common FDA Deficiencies and Prevention
Category Common Issues Prevention
Substantial Equivalence Weak predicate comparison; no performance data Build SE table with data column; cite recognized standards
Performance Testing Incomplete protocols; missing worst-case rationale Follow FDA-recognized standards; document worst-case justification
Biocompatibility Missing endpoints; no ISO 10993-1 risk assessment Complete ISO 10993-1 matrix before testing
Software Inadequate hazard analysis; no cybersecurity bill of materials IEC 62304 compliance + FDA cybersecurity guidance checklist
Labeling Inconsistent claims vs. IFU; missing symbols standard Cross-check label against IFU; cite ISO 15223-1 for symbols

See: references/fda-submission-guide.md


EU MDR Submission Workflow

Achieve CE marking under EU MDR 2017/745.

Workflow: MDR Technical Documentation
  1. Confirm device classification per MDR Annex VIII
  2. Select conformity assessment route based on class:
    • Class I: Self-declaration
    • Class IIa/IIb: Notified Body involvement
    • Class III: Full NB assessment
  3. Select and engage Notified Body (for Class IIa+) — see selection criteria below
  4. Compile Technical Documentation per Annex II checklist:
    • Annex II §1: Device description, intended purpose, UDI
    • Annex II §2: Design and manufacturing information (drawings, BoM, process flows)
    • Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)
    • Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)
    • Annex II §5: Product verification and validation (test reports)
    • Annex II §6: Post-market surveillance plan
    • Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification
  5. Establish and document QMS per ISO 13485
  6. Submit application to Notified Body
  7. Address NB questions and coordinate audit
  8. Validation: CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete
GSPR Checklist Row Example
GSPR Ref Requirement Standard / Guidance Evidence Document Status
Annex I §1 Safe design and manufacture ISO 14971:2019 Risk Management File v2.1 Complete
Annex I §11.1 Devices with measuring function ±accuracy EN ISO 15223-1 Performance Test Report PT-003 Complete
Annex I §17 Cybersecurity MDCG 2019-16 Cybersecurity Assessment CS-001 In progress
Clinical Evidence Requirements by Class
Class Clinical Requirement Documentation
I Clinical evaluation (CE) CE report
IIa CE with literature focus CE report + PMCF plan
IIb CE with clinical data CE report + PMCF + clinical study (some)
III CE with clinical investigation CE report + PMCF + clinical investigation
Notified Body Selection Criteria
  • Scope: Designated for your specific device category
  • Capacity: Confirmed availability within target timeline
  • Experience: Track record with your technology type
  • Geography: Proximity for on-site audits
  • Cost: Fee structure transparency
  • Communication: Responsiveness and query turnaround

See: references/eu-mdr-submission-guide.md


Global Market Access Workflow

Coordinate regulatory approvals across international markets.

Workflow: Multi-Market Submission Strategy
  1. Define target markets based on business priorities
  2. Sequence markets for efficient evidence leverage:
    • Phase 1: FDA + EU (reference markets)
    • Phase 2: Recognition markets (Canada, Australia)
    • Phase 3: Major markets (Japan, China)
    • Phase 4: Emerging markets
  3. Identify local requirements per market:
    • Clinical data acceptability
    • Local agent/representative needs
    • Language and labeling requirements
  4. Develop master technical file with localization plan
  5. Establish in-country regulatory support
  6. Execute parallel or sequential submissions
  7. Track approvals and coordinate launches
  8. Validation: All target market approvals obtained; registration database updated
Market Priority Matrix
Market Size Complexity Recognition Priority
USA Large High N/A 1
EU Large High N/A 1–2
Canada Medium Medium MDSAP 2
Australia Medium Low EU accepted 2
Japan Large High Local clinical 3
China Large Very High Local testing 3
Brazil Medium High GMP inspection 3–4
Documentation Efficiency Strategy
Document Type Single Source Localization Required
Technical file core Yes Format adaptation
Risk management Yes None
Clinical data Yes Bridging assessment
QMS certificate Yes (ISO 13485) Market-specific audit
Labeling Master label Translation, local requirements
IFU Master content Translation, local symbols

See: references/global-regulatory-pathways.md


Regulatory Intelligence Workflow

Monitor and respond to regulatory changes affecting product portfolio.

Workflow: Regulatory Change Management
  1. Monitor regulatory sources:
    • FDA Federal Register, guidance documents
    • EU Official Journal, MDCG guidance
    • Notified Body communications
    • Industry associations (AdvaMed, MedTech Europe)
  2. Assess relevance to product portfolio
  3. Evaluate impact:
    • Timeline to compliance
    • Resource requirements
    • Product changes needed
  4. Develop compliance action plan
  5. Communicate to affected stakeholders
  6. Implement required changes
  7. Document compliance status
  8. Validation: Compliance action plan approved; changes implemented on schedule
Regulatory Monitoring Sources
Source Type Frequency
FDA Federal Register Regulations, guidance Daily
FDA Device Database 510(k), PMA, recalls Weekly
EU Official Journal MDR/IVDR updates Weekly
MDCG Guidance EU implementation As published
ISO/IEC Standards updates Quarterly
Notified Body Audit findings, trends Per interaction
Impact Assessment Template
REGULATORY CHANGE IMPACT ASSESSMENT

Change: [Description]   Source: [Regulation/Guidance]
Effective Date: [Date]  Assessment Date: [Date]  Assessed By: [Name]

AFFECTED PRODUCTS
| Product | Impact (H/M/L) | Action Required        | Due Date |
|---------|----------------|------------------------|----------|
| [Name]  | [H/M/L]        | [Specific action]      | [Date]   |

COMPLIANCE ACTIONS
1. [Action] — Owner: [Name] — Due: [Date]
2. [Action] — Owner: [Name] — Due: [Date]

RESOURCE REQUIREMENTS: Budget $[X]  |  Personnel [X] hrs

APPROVAL: Regulatory _____________ Date _______ / Management _____________ Date _______

Decision Frameworks

Pathway Selection and Classification Reference

FDA Pathway Selection

Is predicate device available?
            │
        Yes─┴─No
         │     │
         ▼     ▼
    Is device   Is risk level
    substantially  Low-Moderate?
    equivalent?       │
         │        Yes─┴─No
     Yes─┴─No      │     │
      │     │      ▼     ▼
      ▼     ▼   De Novo  PMA
    510(k)  Consider      required
           De Novo
           or PMA

EU MDR Classification

Is the device active?
        │
    Yes─┴─No
     │     │
     ▼     ▼
Is it an   Does it contact
implant?   the body?
  │            │
Yes─┴─No   Yes─┴─No
 │    │     │     │
 ▼    ▼     ▼     ▼
III  IIb  Check   Class I
         contact  (measuring/
         type     sterile if
         and      applicable)
         duration
Pre-Submission Meeting Decision
Factor Schedule Pre-Sub Skip Pre-Sub
Novel Technology ✓
New Intended Use ✓
Complex Testing ✓
Uncertain Predicate ✓
Clinical Data Needed ✓
Well-established ✓
Clear Predicate ✓
Standard Testing ✓
Regulatory Escalation Criteria
Situation Escalation Level Action
Submission rejection VP Regulatory Root cause analysis, strategy revision
Major deficiency Director Cross-functional response team
Timeline at risk Management Resource reallocation review
Regulatory change VP Regulatory Portfolio impact assessment
Safety signal Executive Immediate containment and reporting

Tools and References

Scripts
Tool Purpose Usage
regulatory_tracker.py Track submission status and timelines python regulatory_tracker.py

Regulatory Tracker Features:

  • Track multiple submissions across markets
  • Monitor status and target dates
  • Identify overdue submissions
  • Generate status reports

Example usage:

$ python regulatory_tracker.py --report status
Submission Status Report — 2024-11-01
┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐
│ Product          │ Market   │ Type       │ Target Date │ Status   │
├──────────────────┼──────────┼────────────┼─────────────┼──────────┤
│ WoundScan Pro    │ USA      │ 510(k)     │ 2024-12-01  │ On Track │
│ WoundScan Pro    │ EU       │ MDR IIb    │ 2025-03-01  │ At Risk  │
│ CardioMonitor X1 │ Canada   │ Class II   │ 2025-01-15  │ On Track │
└──────────────────┴──────────┴────────────┴─────────────┴──────────┘
1 submission at risk: WoundScan Pro EU — NB engagement not confirmed.
References
Document Content
fda-submission-guide.md FDA pathways, requirements, review process
eu-mdr-submission-guide.md MDR classification, technical documentation, clinical evidence
global-regulatory-pathways.md Canada, Japan, China, Australia, Brazil requirements
iso-regulatory-requirements.md ISO 13485, 14971, 10993, IEC 62304, 62366 requirements
Key Performance Indicators
KPI Target Calculation
First-time approval rate >85% (Approved without major deficiency / Total submitted) × 100
On-time submission >90% (Submitted by target date / Total submissions) × 100
Review cycle compliance >95% (Responses within deadline / Total requests) × 100
Regulatory hold time <20% (Days on hold / Total review days) × 100

Skill Integration Point
mdr-745-specialist Detailed EU MDR technical requirements
fda-consultant-specialist FDA submission deep expertise
quality-manager-qms-iso13485 QMS for regulatory compliance
risk-management-specialist ISO 14971 risk management
1---
2name: "regulatory-affairs-head"
3description: 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.
4triggers:
5 - regulatory strategy
6 - FDA submission
7 - EU MDR
8 - 510(k)
9 - PMA approval
10 - CE marking
11 - regulatory pathway
12 - market access
13 - clinical evidence
14 - regulatory intelligence
15 - submission planning
16 - notified body
17---
18 
19# Head of Regulatory Affairs
20 
21Regulatory strategy development, submission management, and global market access for medical device organizations.
22 
23---
24 
25## Table of Contents
26 
27- [Regulatory Strategy Workflow](#regulatory-strategy-workflow)
28- [FDA Submission Workflow](#fda-submission-workflow)
29- [EU MDR Submission Workflow](#eu-mdr-submission-workflow)
30- [Global Market Access Workflow](#global-market-access-workflow)
31- [Regulatory Intelligence Workflow](#regulatory-intelligence-workflow)
32- [Decision Frameworks](#decision-frameworks)
33- [Tools and References](#tools-and-references)
34 
35---
36 
37## Regulatory Strategy Workflow
38 
39Develop regulatory strategy aligned with business objectives and product characteristics.
40 
41### Workflow: New Product Regulatory Strategy
42 
431. Gather product information:
44 - Intended use and indications
45 - Device classification (risk level)
46 - Technology platform
47 - Target markets and timeline
482. Identify applicable regulations per target market:
49 - FDA (US): 21 CFR Part 820, 510(k)/PMA/De Novo
50 - EU: MDR 2017/745, Notified Body requirements
51 - Other markets: Health Canada, PMDA, NMPA, TGA
523. Determine optimal regulatory pathway:
53 - Compare submission types (510(k) vs De Novo vs PMA)
54 - Assess predicate device availability
55 - Evaluate clinical evidence requirements
564. Develop regulatory timeline with milestones
575. Estimate resource requirements and budget
586. Identify regulatory risks and mitigation strategies
597. Obtain stakeholder alignment and approval
608. **Validation:** Strategy document approved; timeline accepted; resources allocated
61 
62### Regulatory Pathway Selection Matrix
63 
64| Factor | 510(k) | De Novo | PMA |
65|--------|--------|---------|-----|
66| Predicate Available | Yes | No | N/A |
67| Risk Level | Low-Moderate | Low-Moderate | High |
68| Clinical Data | Usually not required | May be required | Required |
69| Review Time | 90 days (MDUFA) | 150 days | 180 days |
70| User Fee | ~$22K (2024) | ~$135K | ~$440K |
71| Best For | Me-too devices | Novel low-risk | High-risk, novel |
72 
73### Regulatory Strategy Document Template
74 
75```
76REGULATORY STRATEGY
77 
78Product: [Name] Version: [X.X] Date: [Date]
79 
801. PRODUCT OVERVIEW
81 Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]
82 Device classification: [Class I / II / III]
83 Technology: [Brief description, e.g., "AI-powered wound-imaging software, SaMD"]
84 
852. TARGET MARKETS & TIMELINE
86 | Market | Pathway | Priority | Target Date |
87 |--------|----------------|----------|-------------|
88 | USA | 510(k) / PMA | 1 | Q1 20XX |
89 | EU | Class [X] MDR | 2 | Q2 20XX |
90 
913. REGULATORY PATHWAY RATIONALE
92 FDA: [510(k) / De Novo / PMA] — Predicate: [K-number or "none"]
93 EU: Class [X] via [Annex IX / X / XI] — NB: [Name or TBD]
94 Rationale: [2–3 sentences on key factors driving pathway choice]
95 
964. CLINICAL EVIDENCE STRATEGY
97 Requirements: [Summarize what each market needs, e.g., "510(k): bench + usability; EU Class IIb: PMCF study"]
98 Approach: [Literature review / Prospective study / Combination]
99 
1005. RISKS AND MITIGATION
101 | Risk | Prob | Impact | Mitigation |
102 |------------------------------|------|--------|-----------------------------------|
103 | Predicate delisted by FDA | Low | High | Identify secondary predicate now |
104 | NB audit backlog | Med | Med | Engage NB 6 months before target |
105 
1066. RESOURCE REQUIREMENTS
107 Budget: $[Amount] Personnel: [FTEs] External: [Consultants / CRO]
108```
109 
110---
111 
112## FDA Submission Workflow
113 
114Prepare and submit FDA regulatory applications.
115 
116### Workflow: 510(k) Submission
117 
1181. Confirm 510(k) pathway suitability:
119 - Predicate device identified (note K-number, e.g., K213456)
120 - Substantial equivalence (SE) argument supportable on intended use and technological characteristics
121 - No new intended use or technology concerns triggering De Novo
1222. Schedule and conduct Pre-Submission (Q-Sub) meeting if needed (see [Pre-Sub Decision](#pre-submission-meeting-decision))
1233. Compile submission package checklist:
124 - [ ] Cover letter with device name, product code, and predicate K-number
125 - [ ] Section 1: Administrative information (applicant, contact, 510(k) type)
126 - [ ] Section 2: Device description — include photos, dimensions, materials list
127 - [ ] Section 3: Intended use and indications for use
128 - [ ] Section 4: Substantial equivalence comparison table (see example below)
129 - [ ] Section 5: Performance testing — protocols, standards cited, pass/fail results
130 - [ ] Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact)
131 - [ ] Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable)
132 - [ ] Section 8: Labeling — final draft IFU, device label
133 - [ ] Section 9: Summary and conclusion
1344. Conduct internal review and quality check against FDA RTA checklist
1355. Prepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)
1366. Submit via FDA ESG portal with user fee payment
1377. Monitor MDUFA clock and respond to AI/RTA requests within deadlines
1388. **Validation:** Submission accepted; MDUFA date received; tracking system updated
139 
140#### Substantial Equivalence Comparison Example
141 
142| Characteristic | Predicate (K213456) | Subject Device | Same? | Notes |
143|----------------|---------------------|----------------|-------|-------|
144| Intended use | Wound measurement | Wound measurement | ✓ | Identical |
145| Technology | 2D camera | 2D + AI analysis | ✗ | New TC; address below |
146| Energy type | Non-energized | Non-energized | ✓ | |
147| Patient contact | No | No | ✓ | |
148| SE conclusion | New TC does not raise new safety/effectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate) |
149 
150### Workflow: PMA Submission
151 
1521. Confirm PMA pathway:
153 - Class III device or no suitable predicate
154 - Clinical data strategy defined
1552. Complete IDE clinical study if required:
156 - IDE approval
157 - Clinical protocol execution
158 - Study report completion
1593. Conduct Pre-Submission meeting
1604. Compile PMA submission checklist:
161 - [ ] Volume I: Administrative, device description, manufacturing
162 - [ ] Volume II: Nonclinical studies (bench, animal, biocompatibility)
163 - [ ] Volume III: Clinical studies (IDE protocol, data, statistical analysis)
164 - [ ] Volume IV: Labeling
165 - [ ] Volume V: Manufacturing information, sterilization
1665. Submit original PMA application
1676. Address FDA questions and deficiencies
1687. Prepare for FDA facility inspection
1698. **Validation:** PMA approved; approval letter received; post-approval requirements documented
170 
171### FDA Submission Timeline
172 
173| Milestone | 510(k) | De Novo | PMA |
174|-----------|--------|---------|-----|
175| Pre-Sub Meeting | Day -90 | Day -90 | Day -120 |
176| Submission | Day 0 | Day 0 | Day 0 |
177| RTA Review | Day 15 | Day 15 | Day 45 |
178| Substantive Review | Days 15–90 | Days 15–150 | Days 45–180 |
179| Decision | Day 90 | Day 150 | Day 180 |
180 
181### Common FDA Deficiencies and Prevention
182 
183| Category | Common Issues | Prevention |
184|----------|---------------|------------|
185| Substantial Equivalence | Weak predicate comparison; no performance data | Build SE table with data column; cite recognized standards |
186| Performance Testing | Incomplete protocols; missing worst-case rationale | Follow FDA-recognized standards; document worst-case justification |
187| Biocompatibility | Missing endpoints; no ISO 10993-1 risk assessment | Complete ISO 10993-1 matrix before testing |
188| Software | Inadequate hazard analysis; no cybersecurity bill of materials | IEC 62304 compliance + FDA cybersecurity guidance checklist |
189| Labeling | Inconsistent claims vs. IFU; missing symbols standard | Cross-check label against IFU; cite ISO 15223-1 for symbols |
190 
191See: [references/fda-submission-guide.md](references/fda-submission-guide.md)
192 
193---
194 
195## EU MDR Submission Workflow
196 
197Achieve CE marking under EU MDR 2017/745.
198 
199### Workflow: MDR Technical Documentation
200 
2011. Confirm device classification per MDR Annex VIII
2022. Select conformity assessment route based on class:
203 - Class I: Self-declaration
204 - Class IIa/IIb: Notified Body involvement
205 - Class III: Full NB assessment
2063. Select and engage Notified Body (for Class IIa+) — see selection criteria below
2074. Compile Technical Documentation per Annex II checklist:
208 - [ ] Annex II §1: Device description, intended purpose, UDI
209 - [ ] Annex II §2: Design and manufacturing information (drawings, BoM, process flows)
210 - [ ] Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)
211 - [ ] Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)
212 - [ ] Annex II §5: Product verification and validation (test reports)
213 - [ ] Annex II §6: Post-market surveillance plan
214 - [ ] Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification
2155. Establish and document QMS per ISO 13485
2166. Submit application to Notified Body
2177. Address NB questions and coordinate audit
2188. **Validation:** CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete
219 
220#### GSPR Checklist Row Example
221 
222| GSPR Ref | Requirement | Standard / Guidance | Evidence Document | Status |
223|----------|-------------|---------------------|-------------------|--------|
224| Annex I §1 | Safe design and manufacture | ISO 14971:2019 | Risk Management File v2.1 | Complete |
225| Annex I §11.1 | Devices with measuring function ±accuracy | EN ISO 15223-1 | Performance Test Report PT-003 | Complete |
226| Annex I §17 | Cybersecurity | MDCG 2019-16 | Cybersecurity Assessment CS-001 | In progress |
227 
228### Clinical Evidence Requirements by Class
229 
230| Class | Clinical Requirement | Documentation |
231|-------|---------------------|---------------|
232| I | Clinical evaluation (CE) | CE report |
233| IIa | CE with literature focus | CE report + PMCF plan |
234| IIb | CE with clinical data | CE report + PMCF + clinical study (some) |
235| III | CE with clinical investigation | CE report + PMCF + clinical investigation |
236 
237### Notified Body Selection Criteria
238 
239- **Scope:** Designated for your specific device category
240- **Capacity:** Confirmed availability within target timeline
241- **Experience:** Track record with your technology type
242- **Geography:** Proximity for on-site audits
243- **Cost:** Fee structure transparency
244- **Communication:** Responsiveness and query turnaround
245 
246See: [references/eu-mdr-submission-guide.md](references/eu-mdr-submission-guide.md)
247 
248---
249 
250## Global Market Access Workflow
251 
252Coordinate regulatory approvals across international markets.
253 
254### Workflow: Multi-Market Submission Strategy
255 
2561. Define target markets based on business priorities
2572. Sequence markets for efficient evidence leverage:
258 - Phase 1: FDA + EU (reference markets)
259 - Phase 2: Recognition markets (Canada, Australia)
260 - Phase 3: Major markets (Japan, China)
261 - Phase 4: Emerging markets
2623. Identify local requirements per market:
263 - Clinical data acceptability
264 - Local agent/representative needs
265 - Language and labeling requirements
2664. Develop master technical file with localization plan
2675. Establish in-country regulatory support
2686. Execute parallel or sequential submissions
2697. Track approvals and coordinate launches
2708. **Validation:** All target market approvals obtained; registration database updated
271 
272### Market Priority Matrix
273 
274| Market | Size | Complexity | Recognition | Priority |
275|--------|------|------------|-------------|----------|
276| USA | Large | High | N/A | 1 |
277| EU | Large | High | N/A | 1–2 |
278| Canada | Medium | Medium | MDSAP | 2 |
279| Australia | Medium | Low | EU accepted | 2 |
280| Japan | Large | High | Local clinical | 3 |
281| China | Large | Very High | Local testing | 3 |
282| Brazil | Medium | High | GMP inspection | 3–4 |
283 
284### Documentation Efficiency Strategy
285 
286| Document Type | Single Source | Localization Required |
287|---------------|---------------|----------------------|
288| Technical file core | Yes | Format adaptation |
289| Risk management | Yes | None |
290| Clinical data | Yes | Bridging assessment |
291| QMS certificate | Yes (ISO 13485) | Market-specific audit |
292| Labeling | Master label | Translation, local requirements |
293| IFU | Master content | Translation, local symbols |
294 
295See: [references/global-regulatory-pathways.md](references/global-regulatory-pathways.md)
296 
297---
298 
299## Regulatory Intelligence Workflow
300 
301Monitor and respond to regulatory changes affecting product portfolio.
302 
303### Workflow: Regulatory Change Management
304 
3051. Monitor regulatory sources:
306 - FDA Federal Register, guidance documents
307 - EU Official Journal, MDCG guidance
308 - Notified Body communications
309 - Industry associations (AdvaMed, MedTech Europe)
3102. Assess relevance to product portfolio
3113. Evaluate impact:
312 - Timeline to compliance
313 - Resource requirements
314 - Product changes needed
3154. Develop compliance action plan
3165. Communicate to affected stakeholders
3176. Implement required changes
3187. Document compliance status
3198. **Validation:** Compliance action plan approved; changes implemented on schedule
320 
321### Regulatory Monitoring Sources
322 
323| Source | Type | Frequency |
324|--------|------|-----------|
325| FDA Federal Register | Regulations, guidance | Daily |
326| FDA Device Database | 510(k), PMA, recalls | Weekly |
327| EU Official Journal | MDR/IVDR updates | Weekly |
328| MDCG Guidance | EU implementation | As published |
329| ISO/IEC | Standards updates | Quarterly |
330| Notified Body | Audit findings, trends | Per interaction |
331 
332### Impact Assessment Template
333 
334```
335REGULATORY CHANGE IMPACT ASSESSMENT
336 
337Change: [Description] Source: [Regulation/Guidance]
338Effective Date: [Date] Assessment Date: [Date] Assessed By: [Name]
339 
340AFFECTED PRODUCTS
341| Product | Impact (H/M/L) | Action Required | Due Date |
342|---------|----------------|------------------------|----------|
343| [Name] | [H/M/L] | [Specific action] | [Date] |
344 
345COMPLIANCE ACTIONS
3461. [Action] — Owner: [Name] — Due: [Date]
3472. [Action] — Owner: [Name] — Due: [Date]
348 
349RESOURCE REQUIREMENTS: Budget $[X] | Personnel [X] hrs
350 
351APPROVAL: Regulatory _____________ Date _______ / Management _____________ Date _______
352```
353 
354---
355 
356## Decision Frameworks
357 
358### Pathway Selection and Classification Reference
359 
360**FDA Pathway Selection**
361 
362```
363Is predicate device available?
364 │
365 Yes─┴─No
366 │ │
367 ▼ ▼
368 Is device Is risk level
369 substantially Low-Moderate?
370 equivalent? │
371 │ Yes─┴─No
372 Yes─┴─No │ │
373 │ │ ▼ ▼
374 ▼ ▼ De Novo PMA
375 510(k) Consider required
376 De Novo
377 or PMA
378```
379 
380**EU MDR Classification**
381 
382```
383Is the device active?
384 │
385 Yes─┴─No
386 │ │
387 ▼ ▼
388Is it an Does it contact
389implant? the body?
390 │ │
391Yes─┴─No Yes─┴─No
392 │ │ │ │
393 ▼ ▼ ▼ ▼
394III IIb Check Class I
395 contact (measuring/
396 type sterile if
397 and applicable)
398 duration
399```
400 
401### Pre-Submission Meeting Decision
402 
403| Factor | Schedule Pre-Sub | Skip Pre-Sub |
404|--------|------------------|--------------|
405| Novel Technology | ✓ | |
406| New Intended Use | ✓ | |
407| Complex Testing | ✓ | |
408| Uncertain Predicate | ✓ | |
409| Clinical Data Needed | ✓ | |
410| Well-established | | ✓ |
411| Clear Predicate | | ✓ |
412| Standard Testing | | ✓ |
413 
414### Regulatory Escalation Criteria
415 
416| Situation | Escalation Level | Action |
417|-----------|------------------|--------|
418| Submission rejection | VP Regulatory | Root cause analysis, strategy revision |
419| Major deficiency | Director | Cross-functional response team |
420| Timeline at risk | Management | Resource reallocation review |
421| Regulatory change | VP Regulatory | Portfolio impact assessment |
422| Safety signal | Executive | Immediate containment and reporting |
423 
424---
425 
426## Tools and References
427 
428### Scripts
429 
430| Tool | Purpose | Usage |
431|------|---------|-------|
432| [regulatory_tracker.py](scripts/regulatory_tracker.py) | Track submission status and timelines | `python regulatory_tracker.py` |
433 
434**Regulatory Tracker Features:**
435- Track multiple submissions across markets
436- Monitor status and target dates
437- Identify overdue submissions
438- Generate status reports
439 
440**Example usage:**
441```bash
442$ python regulatory_tracker.py --report status
443Submission Status Report — 2024-11-01
444┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐
445│ Product │ Market │ Type │ Target Date │ Status │
446├──────────────────┼──────────┼────────────┼─────────────┼──────────┤
447│ WoundScan Pro │ USA │ 510(k) │ 2024-12-01 │ On Track │
448│ WoundScan Pro │ EU │ MDR IIb │ 2025-03-01 │ At Risk │
449│ CardioMonitor X1 │ Canada │ Class II │ 2025-01-15 │ On Track │
450└──────────────────┴──────────┴────────────┴─────────────┴──────────┘
4511 submission at risk: WoundScan Pro EU — NB engagement not confirmed.
452```
453 
454### References
455 
456| Document | Content |
457|----------|---------|
458| [fda-submission-guide.md](references/fda-submission-guide.md) | FDA pathways, requirements, review process |
459| [eu-mdr-submission-guide.md](references/eu-mdr-submission-guide.md) | MDR classification, technical documentation, clinical evidence |
460| [global-regulatory-pathways.md](references/global-regulatory-pathways.md) | Canada, Japan, China, Australia, Brazil requirements |
461| [iso-regulatory-requirements.md](references/iso-regulatory-requirements.md) | ISO 13485, 14971, 10993, IEC 62304, 62366 requirements |
462 
463### Key Performance Indicators
464 
465| KPI | Target | Calculation |
466|-----|--------|-------------|
467| First-time approval rate | >85% | (Approved without major deficiency / Total submitted) × 100 |
468| On-time submission | >90% | (Submitted by target date / Total submissions) × 100 |
469| Review cycle compliance | >95% | (Responses within deadline / Total requests) × 100 |
470| Regulatory hold time | <20% | (Days on hold / Total review days) × 100 |
471 
472---
473 
474## Related Skills
475 
476| Skill | Integration Point |
477|-------|-------------------|
478| [mdr-745-specialist](../mdr-745-specialist/) | Detailed EU MDR technical requirements |
479| [fda-consultant-specialist](../fda-consultant-specialist/) | FDA submission deep expertise |
480| [quality-manager-qms-iso13485](../quality-manager-qms-iso13485/) | QMS for regulatory compliance |
481| [risk-management-specialist](../risk-management-specialist/) | ISO 14971 risk management |
482 

Discussion

Alternatives

Also in Developer docsSee all 533 in Development →