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