# Send Regulatory Affairs Head to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "regulatory-affairs-head", "name": "Regulatory Affairs Head", "source": "tencent", "type": "skill", "category": "金融交易", "sourceUrl": "https://clawhub.ai/alirezarezvani/regulatory-affairs-head", "canonicalUrl": "https://clawhub.ai/alirezarezvani/regulatory-affairs-head", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/regulatory-affairs-head", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=regulatory-affairs-head", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/eu-mdr-submission-guide.md", "references/fda-submission-guide.md", "references/global-regulatory-pathways.md", "references/iso-regulatory-requirements.md", "scripts/regulatory_tracker.py" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/regulatory-affairs-head" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/regulatory-affairs-head", "downloadUrl": "https://openagent3.xyz/downloads/regulatory-affairs-head", "agentUrl": "https://openagent3.xyz/skills/regulatory-affairs-head/agent", "manifestUrl": "https://openagent3.xyz/skills/regulatory-affairs-head/agent.json", "briefUrl": "https://openagent3.xyz/skills/regulatory-affairs-head/agent.md" } } ``` ## Documentation ### Head of Regulatory Affairs Regulatory strategy development, submission management, and global market access for medical device organizations. ### Table of Contents Regulatory Strategy Workflow FDA Submission Workflow EU MDR Submission Workflow Global Market Access Workflow Regulatory Intelligence Workflow Decision Frameworks Tools and References ### 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 Factor510(k)De NovoPMAPredicate AvailableYesNoN/ARisk LevelLow-ModerateLow-ModerateHighClinical DataUsually not requiredMay be requiredRequiredReview Time90 days (MDUFA)150 days180 daysUser Fee~$22K (2024)~$135K~$440KBest 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: [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 CharacteristicPredicate (K213456)Subject DeviceSame?NotesIntended useWound measurementWound measurement✓IdenticalTechnology2D camera2D + AI analysis✗New TC; address belowEnergy typeNon-energizedNon-energized✓Patient contactNoNo✓SE conclusionNew 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: 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 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 Milestone510(k)De NovoPMAPre-Sub MeetingDay -90Day -90Day -120SubmissionDay 0Day 0Day 0RTA ReviewDay 15Day 15Day 45Substantive ReviewDays 15–90Days 15–150Days 45–180DecisionDay 90Day 150Day 180 ### Common FDA Deficiencies and Prevention CategoryCommon IssuesPreventionSubstantial EquivalenceWeak predicate comparison; no performance dataBuild SE table with data column; cite recognized standardsPerformance TestingIncomplete protocols; missing worst-case rationaleFollow FDA-recognized standards; document worst-case justificationBiocompatibilityMissing endpoints; no ISO 10993-1 risk assessmentComplete ISO 10993-1 matrix before testingSoftwareInadequate hazard analysis; no cybersecurity bill of materialsIEC 62304 compliance + FDA cybersecurity guidance checklistLabelingInconsistent claims vs. IFU; missing symbols standardCross-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: 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 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 RefRequirementStandard / GuidanceEvidence DocumentStatusAnnex I §1Safe design and manufactureISO 14971:2019Risk Management File v2.1CompleteAnnex I §11.1Devices with measuring function ±accuracyEN ISO 15223-1Performance Test Report PT-003CompleteAnnex I §17CybersecurityMDCG 2019-16Cybersecurity Assessment CS-001In progress ### Clinical Evidence Requirements by Class ClassClinical RequirementDocumentationIClinical evaluation (CE)CE reportIIaCE with literature focusCE report + PMCF planIIbCE with clinical dataCE report + PMCF + clinical study (some)IIICE with clinical investigationCE 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 MarketSizeComplexityRecognitionPriorityUSALargeHighN/A1EULargeHighN/A1–2CanadaMediumMediumMDSAP2AustraliaMediumLowEU accepted2JapanLargeHighLocal clinical3ChinaLargeVery HighLocal testing3BrazilMediumHighGMP inspection3–4 ### Documentation Efficiency Strategy Document TypeSingle SourceLocalization RequiredTechnical file coreYesFormat adaptationRisk managementYesNoneClinical dataYesBridging assessmentQMS certificateYes (ISO 13485)Market-specific auditLabelingMaster labelTranslation, local requirementsIFUMaster 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 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 SourceTypeFrequencyFDA Federal RegisterRegulations, guidanceDailyFDA Device Database510(k), PMA, recallsWeeklyEU Official JournalMDR/IVDR updatesWeeklyMDCG GuidanceEU implementationAs publishedISO/IECStandards updatesQuarterlyNotified 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 (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 _______ ### 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 FactorSchedule Pre-SubSkip Pre-SubNovel Technology✓New Intended Use✓Complex Testing✓Uncertain Predicate✓Clinical Data Needed✓Well-established✓Clear Predicate✓Standard Testing✓ ### Regulatory Escalation Criteria SituationEscalation LevelActionSubmission rejectionVP RegulatoryRoot cause analysis, strategy revisionMajor deficiencyDirectorCross-functional response teamTimeline at riskManagementResource reallocation reviewRegulatory changeVP RegulatoryPortfolio impact assessmentSafety signalExecutiveImmediate containment and reporting ### Scripts ToolPurposeUsageregulatory_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 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 DocumentContentfda-submission-guide.mdFDA pathways, requirements, review processeu-mdr-submission-guide.mdMDR classification, technical documentation, clinical evidenceglobal-regulatory-pathways.mdCanada, Japan, China, Australia, Brazil requirementsiso-regulatory-requirements.mdISO 13485, 14971, 10993, IEC 62304, 62366 requirements ### Key Performance Indicators KPITargetCalculationFirst-time approval rate>85%(Approved without major deficiency / Total submitted) × 100On-time submission>90%(Submitted by target date / Total submissions) × 100Review cycle compliance>95%(Responses within deadline / Total requests) × 100Regulatory hold time<20%(Days on hold / Total review days) × 100 ### Related Skills SkillIntegration Pointmdr-745-specialistDetailed EU MDR technical requirementsfda-consultant-specialistFDA submission deep expertisequality-manager-qms-iso13485QMS for regulatory compliancerisk-management-specialistISO 14971 risk management ## Trust - Source: tencent - Verification: Indexed source record - Publisher: alirezarezvani - Version: 2.1.1 ## Source health - Status: healthy - Source download looks usable. - Yavira can redirect you to the upstream package for this source. - Health scope: source - Reason: direct_download_ok - Checked at: 2026-04-23T16:43:11.935Z - Expires at: 2026-04-30T16:43:11.935Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/regulatory-affairs-head) - [Send to Agent page](https://openagent3.xyz/skills/regulatory-affairs-head/agent) - [JSON manifest](https://openagent3.xyz/skills/regulatory-affairs-head/agent.json) - [Markdown brief](https://openagent3.xyz/skills/regulatory-affairs-head/agent.md) - [Download page](https://openagent3.xyz/downloads/regulatory-affairs-head)