{ "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": { "downloadMode": "redirect", "downloadUrl": "/downloads/regulatory-affairs-head", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=regulatory-affairs-head", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "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" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "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." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/regulatory-affairs-head", "agentPageUrl": "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" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "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." ], "prompts": [ { "label": "New install", "body": "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." }, { "label": "Upgrade existing", "body": "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." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Head of Regulatory Affairs", "body": "Regulatory strategy development, submission management, and global market access for medical device organizations." }, { "title": "Table of Contents", "body": "Regulatory Strategy Workflow\nFDA Submission Workflow\nEU MDR Submission Workflow\nGlobal Market Access Workflow\nRegulatory Intelligence Workflow\nDecision Frameworks\nTools and References" }, { "title": "Regulatory Strategy Workflow", "body": "Develop regulatory strategy aligned with business objectives and product characteristics." }, { "title": "Workflow: New Product Regulatory Strategy", "body": "Gather product information:\n\nIntended use and indications\nDevice classification (risk level)\nTechnology platform\nTarget markets and timeline\n\n\nIdentify applicable regulations per target market:\n\nFDA (US): 21 CFR Part 820, 510(k)/PMA/De Novo\nEU: MDR 2017/745, Notified Body requirements\nOther markets: Health Canada, PMDA, NMPA, TGA\n\n\nDetermine optimal regulatory pathway:\n\nCompare submission types (510(k) vs De Novo vs PMA)\nAssess predicate device availability\nEvaluate clinical evidence requirements\n\n\nDevelop regulatory timeline with milestones\nEstimate resource requirements and budget\nIdentify regulatory risks and mitigation strategies\nObtain stakeholder alignment and approval\nValidation: Strategy document approved; timeline accepted; resources allocated" }, { "title": "Regulatory Pathway Selection Matrix", "body": "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" }, { "title": "Regulatory Strategy Document Template", "body": "REGULATORY STRATEGY\n\nProduct: [Name] Version: [X.X] Date: [Date]\n\n1. PRODUCT OVERVIEW\n Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]\n Device classification: [Class I / II / III]\n Technology: [Brief description, e.g., \"AI-powered wound-imaging software, SaMD\"]\n\n2. TARGET MARKETS & TIMELINE\n | Market | Pathway | Priority | Target Date |\n |--------|----------------|----------|-------------|\n | USA | 510(k) / PMA | 1 | Q1 20XX |\n | EU | Class [X] MDR | 2 | Q2 20XX |\n\n3. REGULATORY PATHWAY RATIONALE\n FDA: [510(k) / De Novo / PMA] — Predicate: [K-number or \"none\"]\n EU: Class [X] via [Annex IX / X / XI] — NB: [Name or TBD]\n Rationale: [2–3 sentences on key factors driving pathway choice]\n\n4. CLINICAL EVIDENCE STRATEGY\n Requirements: [Summarize what each market needs, e.g., \"510(k): bench + usability; EU Class IIb: PMCF study\"]\n Approach: [Literature review / Prospective study / Combination]\n\n5. RISKS AND MITIGATION\n | Risk | Prob | Impact | Mitigation |\n |------------------------------|------|--------|-----------------------------------|\n | Predicate delisted by FDA | Low | High | Identify secondary predicate now |\n | NB audit backlog | Med | Med | Engage NB 6 months before target |\n\n6. RESOURCE REQUIREMENTS\n Budget: $[Amount] Personnel: [FTEs] External: [Consultants / CRO]" }, { "title": "FDA Submission Workflow", "body": "Prepare and submit FDA regulatory applications." }, { "title": "Workflow: 510(k) Submission", "body": "Confirm 510(k) pathway suitability:\n\nPredicate device identified (note K-number, e.g., K213456)\nSubstantial equivalence (SE) argument supportable on intended use and technological characteristics\nNo new intended use or technology concerns triggering De Novo\n\n\nSchedule and conduct Pre-Submission (Q-Sub) meeting if needed (see Pre-Sub Decision)\nCompile submission package checklist:\n\n Cover letter with device name, product code, and predicate K-number\n Section 1: Administrative information (applicant, contact, 510(k) type)\n Section 2: Device description — include photos, dimensions, materials list\n Section 3: Intended use and indications for use\n Section 4: Substantial equivalence comparison table (see example below)\n Section 5: Performance testing — protocols, standards cited, pass/fail results\n Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact)\n Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable)\n Section 8: Labeling — final draft IFU, device label\n Section 9: Summary and conclusion\n\n\nConduct internal review and quality check against FDA RTA checklist\nPrepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)\nSubmit via FDA ESG portal with user fee payment\nMonitor MDUFA clock and respond to AI/RTA requests within deadlines\nValidation: Submission accepted; MDUFA date received; tracking system updated\n\nSubstantial Equivalence Comparison Example\n\nCharacteristicPredicate (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)" }, { "title": "Workflow: PMA Submission", "body": "Confirm PMA pathway:\n\nClass III device or no suitable predicate\nClinical data strategy defined\n\n\nComplete IDE clinical study if required:\n\nIDE approval\nClinical protocol execution\nStudy report completion\n\n\nConduct Pre-Submission meeting\nCompile PMA submission checklist:\n\n Volume I: Administrative, device description, manufacturing\n Volume II: Nonclinical studies (bench, animal, biocompatibility)\n Volume III: Clinical studies (IDE protocol, data, statistical analysis)\n Volume IV: Labeling\n Volume V: Manufacturing information, sterilization\n\n\nSubmit original PMA application\nAddress FDA questions and deficiencies\nPrepare for FDA facility inspection\nValidation: PMA approved; approval letter received; post-approval requirements documented" }, { "title": "FDA Submission Timeline", "body": "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" }, { "title": "Common FDA Deficiencies and Prevention", "body": "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\n\nSee: references/fda-submission-guide.md" }, { "title": "EU MDR Submission Workflow", "body": "Achieve CE marking under EU MDR 2017/745." }, { "title": "Workflow: MDR Technical Documentation", "body": "Confirm device classification per MDR Annex VIII\nSelect conformity assessment route based on class:\n\nClass I: Self-declaration\nClass IIa/IIb: Notified Body involvement\nClass III: Full NB assessment\n\n\nSelect and engage Notified Body (for Class IIa+) — see selection criteria below\nCompile Technical Documentation per Annex II checklist:\n\n Annex II §1: Device description, intended purpose, UDI\n Annex II §2: Design and manufacturing information (drawings, BoM, process flows)\n Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)\n Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)\n Annex II §5: Product verification and validation (test reports)\n Annex II §6: Post-market surveillance plan\n Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification\n\n\nEstablish and document QMS per ISO 13485\nSubmit application to Notified Body\nAddress NB questions and coordinate audit\nValidation: CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete\n\nGSPR Checklist Row Example\n\nGSPR 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" }, { "title": "Clinical Evidence Requirements by Class", "body": "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" }, { "title": "Notified Body Selection Criteria", "body": "Scope: Designated for your specific device category\nCapacity: Confirmed availability within target timeline\nExperience: Track record with your technology type\nGeography: Proximity for on-site audits\nCost: Fee structure transparency\nCommunication: Responsiveness and query turnaround\n\nSee: references/eu-mdr-submission-guide.md" }, { "title": "Global Market Access Workflow", "body": "Coordinate regulatory approvals across international markets." }, { "title": "Workflow: Multi-Market Submission Strategy", "body": "Define target markets based on business priorities\nSequence markets for efficient evidence leverage:\n\nPhase 1: FDA + EU (reference markets)\nPhase 2: Recognition markets (Canada, Australia)\nPhase 3: Major markets (Japan, China)\nPhase 4: Emerging markets\n\n\nIdentify local requirements per market:\n\nClinical data acceptability\nLocal agent/representative needs\nLanguage and labeling requirements\n\n\nDevelop master technical file with localization plan\nEstablish in-country regulatory support\nExecute parallel or sequential submissions\nTrack approvals and coordinate launches\nValidation: All target market approvals obtained; registration database updated" }, { "title": "Market Priority Matrix", "body": "MarketSizeComplexityRecognitionPriorityUSALargeHighN/A1EULargeHighN/A1–2CanadaMediumMediumMDSAP2AustraliaMediumLowEU accepted2JapanLargeHighLocal clinical3ChinaLargeVery HighLocal testing3BrazilMediumHighGMP inspection3–4" }, { "title": "Documentation Efficiency Strategy", "body": "Document TypeSingle SourceLocalization RequiredTechnical file coreYesFormat adaptationRisk managementYesNoneClinical dataYesBridging assessmentQMS certificateYes (ISO 13485)Market-specific auditLabelingMaster labelTranslation, local requirementsIFUMaster contentTranslation, local symbols\n\nSee: references/global-regulatory-pathways.md" }, { "title": "Regulatory Intelligence Workflow", "body": "Monitor and respond to regulatory changes affecting product portfolio." }, { "title": "Workflow: Regulatory Change Management", "body": "Monitor regulatory sources:\n\nFDA Federal Register, guidance documents\nEU Official Journal, MDCG guidance\nNotified Body communications\nIndustry associations (AdvaMed, MedTech Europe)\n\n\nAssess relevance to product portfolio\nEvaluate impact:\n\nTimeline to compliance\nResource requirements\nProduct changes needed\n\n\nDevelop compliance action plan\nCommunicate to affected stakeholders\nImplement required changes\nDocument compliance status\nValidation: Compliance action plan approved; changes implemented on schedule" }, { "title": "Regulatory Monitoring Sources", "body": "SourceTypeFrequencyFDA Federal RegisterRegulations, guidanceDailyFDA Device Database510(k), PMA, recallsWeeklyEU Official JournalMDR/IVDR updatesWeeklyMDCG GuidanceEU implementationAs publishedISO/IECStandards updatesQuarterlyNotified BodyAudit findings, trendsPer interaction" }, { "title": "Impact Assessment Template", "body": "REGULATORY CHANGE IMPACT ASSESSMENT\n\nChange: [Description] Source: [Regulation/Guidance]\nEffective Date: [Date] Assessment Date: [Date] Assessed By: [Name]\n\nAFFECTED PRODUCTS\n| Product | Impact (H/M/L) | Action Required | Due Date |\n|---------|----------------|------------------------|----------|\n| [Name] | [H/M/L] | [Specific action] | [Date] |\n\nCOMPLIANCE ACTIONS\n1. [Action] — Owner: [Name] — Due: [Date]\n2. [Action] — Owner: [Name] — Due: [Date]\n\nRESOURCE REQUIREMENTS: Budget $[X] | Personnel [X] hrs\n\nAPPROVAL: Regulatory _____________ Date _______ / Management _____________ Date _______" }, { "title": "Pathway Selection and Classification Reference", "body": "FDA Pathway Selection\n\nIs predicate device available?\n │\n Yes─┴─No\n │ │\n ▼ ▼\n Is device Is risk level\n substantially Low-Moderate?\n equivalent? │\n │ Yes─┴─No\n Yes─┴─No │ │\n │ │ ▼ ▼\n ▼ ▼ De Novo PMA\n 510(k) Consider required\n De Novo\n or PMA\n\nEU MDR Classification\n\nIs the device active?\n │\n Yes─┴─No\n │ │\n ▼ ▼\nIs it an Does it contact\nimplant? the body?\n │ │\nYes─┴─No Yes─┴─No\n │ │ │ │\n ▼ ▼ ▼ ▼\nIII IIb Check Class I\n contact (measuring/\n type sterile if\n and applicable)\n duration" }, { "title": "Pre-Submission Meeting Decision", "body": "FactorSchedule Pre-SubSkip Pre-SubNovel Technology✓New Intended Use✓Complex Testing✓Uncertain Predicate✓Clinical Data Needed✓Well-established✓Clear Predicate✓Standard Testing✓" }, { "title": "Regulatory Escalation Criteria", "body": "SituationEscalation LevelActionSubmission rejectionVP RegulatoryRoot cause analysis, strategy revisionMajor deficiencyDirectorCross-functional response teamTimeline at riskManagementResource reallocation reviewRegulatory changeVP RegulatoryPortfolio impact assessmentSafety signalExecutiveImmediate containment and reporting" }, { "title": "Scripts", "body": "ToolPurposeUsageregulatory_tracker.pyTrack submission status and timelinespython regulatory_tracker.py\n\nRegulatory Tracker Features:\n\nTrack multiple submissions across markets\nMonitor status and target dates\nIdentify overdue submissions\nGenerate status reports\n\nExample usage:\n\n$ python regulatory_tracker.py --report status\nSubmission Status Report — 2024-11-01\n┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐\n│ Product │ Market │ Type │ Target Date │ Status │\n├──────────────────┼──────────┼────────────┼─────────────┼──────────┤\n│ WoundScan Pro │ USA │ 510(k) │ 2024-12-01 │ On Track │\n│ WoundScan Pro │ EU │ MDR IIb │ 2025-03-01 │ At Risk │\n│ CardioMonitor X1 │ Canada │ Class II │ 2025-01-15 │ On Track │\n└──────────────────┴──────────┴────────────┴─────────────┴──────────┘\n1 submission at risk: WoundScan Pro EU — NB engagement not confirmed." }, { "title": "References", "body": "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" }, { "title": "Key Performance Indicators", "body": "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" }, { "title": "Related Skills", "body": "SkillIntegration Pointmdr-745-specialistDetailed EU MDR technical requirementsfda-consultant-specialistFDA submission deep expertisequality-manager-qms-iso13485QMS for regulatory compliancerisk-management-specialistISO 14971 risk management" } ], "body": "Head of Regulatory Affairs\n\nRegulatory strategy development, submission management, and global market access for medical device organizations.\n\nTable of Contents\nRegulatory Strategy Workflow\nFDA Submission Workflow\nEU MDR Submission Workflow\nGlobal Market Access Workflow\nRegulatory Intelligence Workflow\nDecision Frameworks\nTools and References\nRegulatory Strategy Workflow\n\nDevelop regulatory strategy aligned with business objectives and product characteristics.\n\nWorkflow: New Product Regulatory Strategy\nGather product information:\nIntended use and indications\nDevice classification (risk level)\nTechnology platform\nTarget markets and timeline\nIdentify applicable regulations per target market:\nFDA (US): 21 CFR Part 820, 510(k)/PMA/De Novo\nEU: MDR 2017/745, Notified Body requirements\nOther markets: Health Canada, PMDA, NMPA, TGA\nDetermine optimal regulatory pathway:\nCompare submission types (510(k) vs De Novo vs PMA)\nAssess predicate device availability\nEvaluate clinical evidence requirements\nDevelop regulatory timeline with milestones\nEstimate resource requirements and budget\nIdentify regulatory risks and mitigation strategies\nObtain stakeholder alignment and approval\nValidation: Strategy document approved; timeline accepted; resources allocated\nRegulatory Pathway Selection Matrix\nFactor\t510(k)\tDe Novo\tPMA\nPredicate Available\tYes\tNo\tN/A\nRisk Level\tLow-Moderate\tLow-Moderate\tHigh\nClinical Data\tUsually not required\tMay be required\tRequired\nReview Time\t90 days (MDUFA)\t150 days\t180 days\nUser Fee\t~$22K (2024)\t~$135K\t~$440K\nBest For\tMe-too devices\tNovel low-risk\tHigh-risk, novel\nRegulatory Strategy Document Template\nREGULATORY STRATEGY\n\nProduct: [Name] Version: [X.X] Date: [Date]\n\n1. PRODUCT OVERVIEW\n Intended use: [One-sentence statement of intended patient population, body site, and clinical purpose]\n Device classification: [Class I / II / III]\n Technology: [Brief description, e.g., \"AI-powered wound-imaging software, SaMD\"]\n\n2. TARGET MARKETS & TIMELINE\n | Market | Pathway | Priority | Target Date |\n |--------|----------------|----------|-------------|\n | USA | 510(k) / PMA | 1 | Q1 20XX |\n | EU | Class [X] MDR | 2 | Q2 20XX |\n\n3. REGULATORY PATHWAY RATIONALE\n FDA: [510(k) / De Novo / PMA] — Predicate: [K-number or \"none\"]\n EU: Class [X] via [Annex IX / X / XI] — NB: [Name or TBD]\n Rationale: [2–3 sentences on key factors driving pathway choice]\n\n4. CLINICAL EVIDENCE STRATEGY\n Requirements: [Summarize what each market needs, e.g., \"510(k): bench + usability; EU Class IIb: PMCF study\"]\n Approach: [Literature review / Prospective study / Combination]\n\n5. RISKS AND MITIGATION\n | Risk | Prob | Impact | Mitigation |\n |------------------------------|------|--------|-----------------------------------|\n | Predicate delisted by FDA | Low | High | Identify secondary predicate now |\n | NB audit backlog | Med | Med | Engage NB 6 months before target |\n\n6. RESOURCE REQUIREMENTS\n Budget: $[Amount] Personnel: [FTEs] External: [Consultants / CRO]\n\nFDA Submission Workflow\n\nPrepare and submit FDA regulatory applications.\n\nWorkflow: 510(k) Submission\nConfirm 510(k) pathway suitability:\nPredicate device identified (note K-number, e.g., K213456)\nSubstantial equivalence (SE) argument supportable on intended use and technological characteristics\nNo new intended use or technology concerns triggering De Novo\nSchedule and conduct Pre-Submission (Q-Sub) meeting if needed (see Pre-Sub Decision)\nCompile submission package checklist:\n Cover letter with device name, product code, and predicate K-number\n Section 1: Administrative information (applicant, contact, 510(k) type)\n Section 2: Device description — include photos, dimensions, materials list\n Section 3: Intended use and indications for use\n Section 4: Substantial equivalence comparison table (see example below)\n Section 5: Performance testing — protocols, standards cited, pass/fail results\n Section 6: Biocompatibility summary (ISO 10993-1 risk assessment, if patient contact)\n Section 7: Software documentation (IEC 62304 level, cybersecurity per FDA guidance, if applicable)\n Section 8: Labeling — final draft IFU, device label\n Section 9: Summary and conclusion\nConduct internal review and quality check against FDA RTA checklist\nPrepare eCopy per FDA format requirements (PDF bookmarked, eCopy cover page)\nSubmit via FDA ESG portal with user fee payment\nMonitor MDUFA clock and respond to AI/RTA requests within deadlines\nValidation: Submission accepted; MDUFA date received; tracking system updated\nSubstantial Equivalence Comparison Example\nCharacteristic\tPredicate (K213456)\tSubject Device\tSame?\tNotes\nIntended use\tWound measurement\tWound measurement\t✓\tIdentical\nTechnology\t2D camera\t2D + AI analysis\t✗\tNew TC; address below\nEnergy type\tNon-energized\tNon-energized\t✓\t\nPatient contact\tNo\tNo\t✓\t\nSE conclusion\tNew TC does not raise new safety/effectiveness questions; bench data demonstrates equivalent accuracy (±2mm vs ±3mm predicate)\t\t\t\nWorkflow: PMA Submission\nConfirm PMA pathway:\nClass III device or no suitable predicate\nClinical data strategy defined\nComplete IDE clinical study if required:\nIDE approval\nClinical protocol execution\nStudy report completion\nConduct Pre-Submission meeting\nCompile PMA submission checklist:\n Volume I: Administrative, device description, manufacturing\n Volume II: Nonclinical studies (bench, animal, biocompatibility)\n Volume III: Clinical studies (IDE protocol, data, statistical analysis)\n Volume IV: Labeling\n Volume V: Manufacturing information, sterilization\nSubmit original PMA application\nAddress FDA questions and deficiencies\nPrepare for FDA facility inspection\nValidation: PMA approved; approval letter received; post-approval requirements documented\nFDA Submission Timeline\nMilestone\t510(k)\tDe Novo\tPMA\nPre-Sub Meeting\tDay -90\tDay -90\tDay -120\nSubmission\tDay 0\tDay 0\tDay 0\nRTA Review\tDay 15\tDay 15\tDay 45\nSubstantive Review\tDays 15–90\tDays 15–150\tDays 45–180\nDecision\tDay 90\tDay 150\tDay 180\nCommon FDA Deficiencies and Prevention\nCategory\tCommon Issues\tPrevention\nSubstantial Equivalence\tWeak predicate comparison; no performance data\tBuild SE table with data column; cite recognized standards\nPerformance Testing\tIncomplete protocols; missing worst-case rationale\tFollow FDA-recognized standards; document worst-case justification\nBiocompatibility\tMissing endpoints; no ISO 10993-1 risk assessment\tComplete ISO 10993-1 matrix before testing\nSoftware\tInadequate hazard analysis; no cybersecurity bill of materials\tIEC 62304 compliance + FDA cybersecurity guidance checklist\nLabeling\tInconsistent claims vs. IFU; missing symbols standard\tCross-check label against IFU; cite ISO 15223-1 for symbols\n\nSee: references/fda-submission-guide.md\n\nEU MDR Submission Workflow\n\nAchieve CE marking under EU MDR 2017/745.\n\nWorkflow: MDR Technical Documentation\nConfirm device classification per MDR Annex VIII\nSelect conformity assessment route based on class:\nClass I: Self-declaration\nClass IIa/IIb: Notified Body involvement\nClass III: Full NB assessment\nSelect and engage Notified Body (for Class IIa+) — see selection criteria below\nCompile Technical Documentation per Annex II checklist:\n Annex II §1: Device description, intended purpose, UDI\n Annex II §2: Design and manufacturing information (drawings, BoM, process flows)\n Annex II §3: GSPR checklist — each requirement mapped to evidence (standard, test report, or justification)\n Annex II §4: Benefit-risk analysis and risk management file (ISO 14971)\n Annex II §5: Product verification and validation (test reports)\n Annex II §6: Post-market surveillance plan\n Annex XIV: Clinical evaluation report (CER) — literature, clinical data, equivalence justification\nEstablish and document QMS per ISO 13485\nSubmit application to Notified Body\nAddress NB questions and coordinate audit\nValidation: CE certificate issued; Declaration of Conformity signed; EUDAMED registration complete\nGSPR Checklist Row Example\nGSPR Ref\tRequirement\tStandard / Guidance\tEvidence Document\tStatus\nAnnex I §1\tSafe design and manufacture\tISO 14971:2019\tRisk Management File v2.1\tComplete\nAnnex I §11.1\tDevices with measuring function ±accuracy\tEN ISO 15223-1\tPerformance Test Report PT-003\tComplete\nAnnex I §17\tCybersecurity\tMDCG 2019-16\tCybersecurity Assessment CS-001\tIn progress\nClinical Evidence Requirements by Class\nClass\tClinical Requirement\tDocumentation\nI\tClinical evaluation (CE)\tCE report\nIIa\tCE with literature focus\tCE report + PMCF plan\nIIb\tCE with clinical data\tCE report + PMCF + clinical study (some)\nIII\tCE with clinical investigation\tCE report + PMCF + clinical investigation\nNotified Body Selection Criteria\nScope: Designated for your specific device category\nCapacity: Confirmed availability within target timeline\nExperience: Track record with your technology type\nGeography: Proximity for on-site audits\nCost: Fee structure transparency\nCommunication: Responsiveness and query turnaround\n\nSee: references/eu-mdr-submission-guide.md\n\nGlobal Market Access Workflow\n\nCoordinate regulatory approvals across international markets.\n\nWorkflow: Multi-Market Submission Strategy\nDefine target markets based on business priorities\nSequence markets for efficient evidence leverage:\nPhase 1: FDA + EU (reference markets)\nPhase 2: Recognition markets (Canada, Australia)\nPhase 3: Major markets (Japan, China)\nPhase 4: Emerging markets\nIdentify local requirements per market:\nClinical data acceptability\nLocal agent/representative needs\nLanguage and labeling requirements\nDevelop master technical file with localization plan\nEstablish in-country regulatory support\nExecute parallel or sequential submissions\nTrack approvals and coordinate launches\nValidation: All target market approvals obtained; registration database updated\nMarket Priority Matrix\nMarket\tSize\tComplexity\tRecognition\tPriority\nUSA\tLarge\tHigh\tN/A\t1\nEU\tLarge\tHigh\tN/A\t1–2\nCanada\tMedium\tMedium\tMDSAP\t2\nAustralia\tMedium\tLow\tEU accepted\t2\nJapan\tLarge\tHigh\tLocal clinical\t3\nChina\tLarge\tVery High\tLocal testing\t3\nBrazil\tMedium\tHigh\tGMP inspection\t3–4\nDocumentation Efficiency Strategy\nDocument Type\tSingle Source\tLocalization Required\nTechnical file core\tYes\tFormat adaptation\nRisk management\tYes\tNone\nClinical data\tYes\tBridging assessment\nQMS certificate\tYes (ISO 13485)\tMarket-specific audit\nLabeling\tMaster label\tTranslation, local requirements\nIFU\tMaster content\tTranslation, local symbols\n\nSee: references/global-regulatory-pathways.md\n\nRegulatory Intelligence Workflow\n\nMonitor and respond to regulatory changes affecting product portfolio.\n\nWorkflow: Regulatory Change Management\nMonitor regulatory sources:\nFDA Federal Register, guidance documents\nEU Official Journal, MDCG guidance\nNotified Body communications\nIndustry associations (AdvaMed, MedTech Europe)\nAssess relevance to product portfolio\nEvaluate impact:\nTimeline to compliance\nResource requirements\nProduct changes needed\nDevelop compliance action plan\nCommunicate to affected stakeholders\nImplement required changes\nDocument compliance status\nValidation: Compliance action plan approved; changes implemented on schedule\nRegulatory Monitoring Sources\nSource\tType\tFrequency\nFDA Federal Register\tRegulations, guidance\tDaily\nFDA Device Database\t510(k), PMA, recalls\tWeekly\nEU Official Journal\tMDR/IVDR updates\tWeekly\nMDCG Guidance\tEU implementation\tAs published\nISO/IEC\tStandards updates\tQuarterly\nNotified Body\tAudit findings, trends\tPer interaction\nImpact Assessment Template\nREGULATORY CHANGE IMPACT ASSESSMENT\n\nChange: [Description] Source: [Regulation/Guidance]\nEffective Date: [Date] Assessment Date: [Date] Assessed By: [Name]\n\nAFFECTED PRODUCTS\n| Product | Impact (H/M/L) | Action Required | Due Date |\n|---------|----------------|------------------------|----------|\n| [Name] | [H/M/L] | [Specific action] | [Date] |\n\nCOMPLIANCE ACTIONS\n1. [Action] — Owner: [Name] — Due: [Date]\n2. [Action] — Owner: [Name] — Due: [Date]\n\nRESOURCE REQUIREMENTS: Budget $[X] | Personnel [X] hrs\n\nAPPROVAL: Regulatory _____________ Date _______ / Management _____________ Date _______\n\nDecision Frameworks\nPathway Selection and Classification Reference\n\nFDA Pathway Selection\n\nIs predicate device available?\n │\n Yes─┴─No\n │ │\n ▼ ▼\n Is device Is risk level\n substantially Low-Moderate?\n equivalent? │\n │ Yes─┴─No\n Yes─┴─No │ │\n │ │ ▼ ▼\n ▼ ▼ De Novo PMA\n 510(k) Consider required\n De Novo\n or PMA\n\n\nEU MDR Classification\n\nIs the device active?\n │\n Yes─┴─No\n │ │\n ▼ ▼\nIs it an Does it contact\nimplant? the body?\n │ │\nYes─┴─No Yes─┴─No\n │ │ │ │\n ▼ ▼ ▼ ▼\nIII IIb Check Class I\n contact (measuring/\n type sterile if\n and applicable)\n duration\n\nPre-Submission Meeting Decision\nFactor\tSchedule Pre-Sub\tSkip Pre-Sub\nNovel Technology\t✓\t\nNew Intended Use\t✓\t\nComplex Testing\t✓\t\nUncertain Predicate\t✓\t\nClinical Data Needed\t✓\t\nWell-established\t\t✓\nClear Predicate\t\t✓\nStandard Testing\t\t✓\nRegulatory Escalation Criteria\nSituation\tEscalation Level\tAction\nSubmission rejection\tVP Regulatory\tRoot cause analysis, strategy revision\nMajor deficiency\tDirector\tCross-functional response team\nTimeline at risk\tManagement\tResource reallocation review\nRegulatory change\tVP Regulatory\tPortfolio impact assessment\nSafety signal\tExecutive\tImmediate containment and reporting\nTools and References\nScripts\nTool\tPurpose\tUsage\nregulatory_tracker.py\tTrack submission status and timelines\tpython regulatory_tracker.py\n\nRegulatory Tracker Features:\n\nTrack multiple submissions across markets\nMonitor status and target dates\nIdentify overdue submissions\nGenerate status reports\n\nExample usage:\n\n$ python regulatory_tracker.py --report status\nSubmission Status Report — 2024-11-01\n┌──────────────────┬──────────┬────────────┬─────────────┬──────────┐\n│ Product │ Market │ Type │ Target Date │ Status │\n├──────────────────┼──────────┼────────────┼─────────────┼──────────┤\n│ WoundScan Pro │ USA │ 510(k) │ 2024-12-01 │ On Track │\n│ WoundScan Pro │ EU │ MDR IIb │ 2025-03-01 │ At Risk │\n│ CardioMonitor X1 │ Canada │ Class II │ 2025-01-15 │ On Track │\n└──────────────────┴──────────┴────────────┴─────────────┴──────────┘\n1 submission at risk: WoundScan Pro EU — NB engagement not confirmed.\n\nReferences\nDocument\tContent\nfda-submission-guide.md\tFDA pathways, requirements, review process\neu-mdr-submission-guide.md\tMDR classification, technical documentation, clinical evidence\nglobal-regulatory-pathways.md\tCanada, Japan, China, Australia, Brazil requirements\niso-regulatory-requirements.md\tISO 13485, 14971, 10993, IEC 62304, 62366 requirements\nKey Performance Indicators\nKPI\tTarget\tCalculation\nFirst-time approval rate\t>85%\t(Approved without major deficiency / Total submitted) × 100\nOn-time submission\t>90%\t(Submitted by target date / Total submissions) × 100\nReview cycle compliance\t>95%\t(Responses within deadline / Total requests) × 100\nRegulatory hold time\t<20%\t(Days on hold / Total review days) × 100\nRelated Skills\nSkill\tIntegration Point\nmdr-745-specialist\tDetailed EU MDR technical requirements\nfda-consultant-specialist\tFDA submission deep expertise\nquality-manager-qms-iso13485\tQMS for regulatory compliance\nrisk-management-specialist\tISO 14971 risk management" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/alirezarezvani/regulatory-affairs-head", "publisherUrl": "https://clawhub.ai/alirezarezvani/regulatory-affairs-head", "owner": "alirezarezvani", "version": "2.1.1", "license": null, "verificationStatus": "Indexed source record" }, "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" } }