skills$openclaw/regulatory-affairs-head
alirezarezvani3.6k

by alirezarezvani

regulatory-affairs-head – OpenClaw Skill

regulatory-affairs-head is an OpenClaw Skills integration for writing workflows. Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Provides regulatory strategy development, submission management, pathway analysis, global compliance coordination, and cross-functional team leadership.

3.6k stars3.2k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026writing

Skill Snapshot

nameregulatory-affairs-head
descriptionSenior Regulatory Affairs Manager for HealthTech and MedTech companies. Provides regulatory strategy development, submission management, pathway analysis, global compliance coordination, and cross-functional team leadership. OpenClaw Skills integration.
owneralirezarezvani
repositoryalirezarezvani/regulatory-affairs-head
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @alirezarezvani/regulatory-affairs-head
last updatedFeb 7, 2026

Maintainer

alirezarezvani

alirezarezvani

Maintains regulatory-affairs-head in the OpenClaw Skills directory.

View GitHub profile
File Explorer
9 files
.
references
eu-mdr-submission-guide.md
3.2 KB
fda-submission-guide.md
3.8 KB
global-regulatory-pathways.md
9.6 KB
iso-regulatory-requirements.md
13.8 KB
scripts
regulatory_tracker.py
8.0 KB
_meta.json
309 B
SKILL.md
14.7 KB
SKILL.md

name: regulatory-affairs-head description: Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Provides regulatory strategy development, submission management, pathway analysis, global compliance coordination, and cross-functional team leadership. 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

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

Factor510(k)De NovoPMA
Predicate AvailableYesNoN/A
Risk LevelLow-ModerateLow-ModerateHigh
Clinical DataUsually not requiredMay be requiredRequired
Review Time90 days (MDUFA)150 days180 days
User Fee~$22K (2024)~$135K~$440K
Best ForMe-too devicesNovel low-riskHigh-risk, novel

Regulatory Strategy Document Template

REGULATORY STRATEGY

Product: [Name]
Version: [X.X]
Date: [Date]

1. PRODUCT OVERVIEW
   - Intended use: [Statement]
   - Device classification: [Class I/II/III]
   - Technology: [Description]

2. TARGET MARKETS
   | Market | Priority | Timeline |
   |--------|----------|----------|
   | USA    | 1        | Q1 20XX  |
   | EU     | 2        | Q2 20XX  |

3. REGULATORY PATHWAY
   - FDA: [510(k) / De Novo / PMA]
   - EU: [Class] via [Conformity route]
   - Rationale: [Justification]

4. CLINICAL EVIDENCE STRATEGY
   - Requirements: [Summary]
   - Approach: [Literature / Study / Both]

5. TIMELINE AND MILESTONES
   [Gantt or milestone table]

6. RISKS AND MITIGATION
   | Risk | Probability | Impact | Mitigation |
   |------|-------------|--------|------------|

7. RESOURCE REQUIREMENTS
   - Budget: $[Amount]
   - Personnel: [FTEs]
   - External support: [Consultants, CRO]

FDA Submission Workflow

Prepare and submit FDA regulatory applications.

Workflow: 510(k) Submission

  1. Confirm 510(k) pathway suitability:
    • Predicate device identified
    • Substantial equivalence supportable
    • No new intended use or technology concerns
  2. Schedule and conduct Pre-Submission (Q-Sub) meeting if needed
  3. Compile submission package:
    • Cover letter and administrative information
    • Device description and intended use
    • Substantial equivalence comparison
    • Performance testing data
    • Biocompatibility (if patient contact)
    • Software documentation (if applicable)
    • Labeling and IFU
  4. Conduct internal review and quality check
  5. Prepare eCopy per FDA format requirements
  6. Submit via FDA ESG portal with user fee payment
  7. Monitor MDUFA clock and respond to AI/RTA requests
  8. Validation: Submission accepted; MDUFA date received; tracking system updated

Workflow: PMA Submission

  1. Confirm PMA pathway:
    • Class III device or no 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:
    • Administrative and device information
    • Manufacturing information
    • Nonclinical studies
    • Clinical studies
    • Labeling
  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

Milestone510(k)De NovoPMA
Pre-Sub MeetingDay -90Day -90Day -120
SubmissionDay 0Day 0Day 0
RTA ReviewDay 15Day 15Day 45
Substantive ReviewDays 15-90Days 15-150Days 45-180
DecisionDay 90Day 150Day 180

Common FDA Deficiencies

CategoryCommon IssuesPrevention
Substantial EquivalenceWeak predicate comparisonStrong SE argument upfront
Performance TestingIncomplete test protocolsFollow recognized standards
BiocompatibilityMissing endpointsISO 10993 risk assessment
SoftwareInadequate documentationIEC 62304 compliance
LabelingInconsistent claimsEarly labeling review

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+)
  4. Compile Technical Documentation per Annex II:
    • Device description and specifications
    • Design and manufacturing information
    • General Safety and Performance Requirements (GSPR) checklist
    • Benefit-risk analysis and risk management
    • Clinical evaluation per Annex XIV
    • Post-market surveillance plan
  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

MDR Classification Decision Tree

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

Clinical Evidence Requirements by Class

ClassClinical RequirementDocumentation
IClinical evaluation (CE)CE report
IIaCE with literature focusCE report + PMCF plan
IIbCE with clinical dataCE report + PMCF + clinical study (some)
IIICE with clinical investigationCE report + PMCF + clinical investigation

Notified Body Selection Criteria

CriterionConsideration
ScopeDevice category expertise
CapacityAvailability and review timeline
ExperienceTrack record in your technology
GeographyProximity for audits
CostFee structure transparency
CommunicationResponsiveness and clarity

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

MarketSizeComplexityRecognitionPriority
USALargeHighN/A1
EULargeHighN/A1-2
CanadaMediumMediumMDSAP2
AustraliaMediumLowEU accepted2
JapanLargeHighLocal clinical3
ChinaLargeVery HighLocal testing3
BrazilMediumHighGMP inspection3-4

Documentation Efficiency Strategy

Document TypeSingle SourceLocalization Required
Technical file coreYesFormat adaptation
Risk managementYesNone
Clinical dataYesBridging assessment
QMS certificateYes (ISO 13485)Market-specific audit
LabelingMaster labelTranslation, local requirements
IFUMaster contentTranslation, 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

SourceTypeFrequency
FDA Federal RegisterRegulations, guidanceDaily
FDA Device Database510(k), PMA, recallsWeekly
EU Official JournalMDR/IVDR updatesWeekly
MDCG GuidanceEU implementationAs published
ISO/IECStandards updatesQuarterly
Notified BodyAudit findings, trendsPer 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 | Action Required | Timeline |
|---------|--------|-----------------|----------|
| [Name]  | [H/M/L]| [Description]   | [Date]   |

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

RESOURCE REQUIREMENTS
- Budget: $[Amount]
- Personnel: [Hours/FTEs]

APPROVAL
Regulatory: _________________ Date: _______
Management: _________________ Date: _______

Decision Frameworks

Pathway Selection Decision Tree

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

Pre-Submission Meeting Decision

FactorSchedule Pre-SubSkip Pre-Sub
Novel Technology
New Intended Use
Complex Testing
Uncertain Predicate
Clinical Data Needed
Well-established
Clear Predicate
Standard Testing

Regulatory Escalation Criteria

SituationEscalation LevelAction
Submission rejectionVP RegulatoryRoot cause analysis, strategy revision
Major deficiencyDirectorCross-functional response team
Timeline at riskManagementResource reallocation review
Regulatory changeVP RegulatoryPortfolio impact assessment
Safety signalExecutiveImmediate containment and reporting

Tools and References

Scripts

ToolPurposeUsage
regulatory_tracker.pyTrack submission status and timelinespython regulatory_tracker.py

Regulatory Tracker Features:

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

References

DocumentContent
fda-submission-guide.mdFDA pathways, requirements, review process
eu-mdr-submission-guide.mdMDR classification, technical documentation, clinical evidence
global-regulatory-pathways.mdCanada, Japan, China, Australia, Brazil requirements
iso-regulatory-requirements.mdISO 13485, 14971, 10993, IEC 62304, 62366 requirements

Key Performance Indicators

KPITargetCalculation
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

SkillIntegration Point
mdr-745-specialistDetailed EU MDR technical requirements
fda-consultant-specialistFDA submission deep expertise
quality-manager-qms-iso13485QMS for regulatory compliance
risk-management-specialistISO 14971 risk management
README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

| 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 |

FAQ

How do I install regulatory-affairs-head?

Run openclaw add @alirezarezvani/regulatory-affairs-head in your terminal. This installs regulatory-affairs-head into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/alirezarezvani/regulatory-affairs-head. Review commits and README documentation before installing.