scientific-regulatory-science

Consolidate FDA, EMA, PMDA, and IP regulatory data into unified profiles.

3|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/nahisaho/satori --skill scientific-regulatory-science
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scientific-regulatory-science
Source: https://github.com/nahisaho/satori/tree/main/src/.github/skills/scientific-regulatory-science
Command: npx skills add https://github.com/nahisaho/satori --skill scientific-regulatory-science

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates and cross-references regulatory data from FDA, EMA, PMDA databases and IP sources to deliver a unified regulatory profile for pharmaceuticals, medical devices, and related products. It enables comprehensive visibility into approvals, recalls, safety data, quality-management requirements, and patent landscapes across agencies.

Core Features & Use Cases

  • Cross-database queries across FDA Orange Book, EMA, and PMDA for approvals, classifications, safety signals, and recall histories.
  • ISO 13485 CAPA planning and quality-management alignment to support regulatory compliance and risk mitigation.
  • USPTO patent searches and competitive landscape analysis to identify freedom-to-operate and patent expiries.
  • Use Case: Regulatory teams rapidly assemble a regulatory profile for a new device, drug, or combination product, including timelines and key regulatory milestones.

Quick Start

Query regulatory databases for a product to retrieve approval histories, recalls, CAPA requirements, and patent information, and return a unified regulatory report.

Frequently Asked Questions about scientific-regulatory-science

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate FDA, EMA, and PMDA regulatory data into a single profile?

Cross-agency regulatory profiles consolidate FDA, EMA, and PMDA approval histories, safety signals, and classifications into structured JSON or CSV outputs with unified identifiers, dates, and statuses. This enables rapid assembly of comprehensive timelines and milestones for pharmaceuticals, medical devices, and combination products.

What is the best way to perform a cross-agency approval history check for a combination product?

Cross-agency approval history checks query FDA, EMA, and PMDA databases simultaneously to retrieve classifications, recalls, and milestones for combination products. This generates a unified regulatory report containing structured timelines, safety signals, and compliance summaries across multiple jurisdictions.

Can I use USPTO patent search and FDA Orange Book data for competitive intelligence?

USPTO patent searches and FDA Orange Book data can be cross-referenced for competitive intelligence and freedom-to-operate analysis. This identifies patent expiries and landscapes, returning structured outputs with patent identifiers, statuses, and dates to support strategic pharmaceutical planning.

How do I align ISO 13485 CAPA planning with regulatory compliance requirements?

ISO 13485 CAPA planning aligns with regulatory compliance by integrating quality-management requirements and risk mitigation into the regulatory profile. This consolidates safety data and recall histories to support corrective actions, producing structured outputs that map compliance milestones to quality standards.

Does cross-database regulatory querying support JSON and CSV exports?

Cross-database regulatory querying supports JSON and CSV exports by consolidating FDA, EMA, PMDA, and IP source data into structured outputs. These formats contain standardized identifiers, approval dates, statuses, and summaries, enabling direct integration into downstream regulatory reporting and analysis workflows.

What are the limitations of cross-agency regulatory data consolidation for medical devices?

Limitations of cross-agency regulatory data consolidation include reliance on available FDA, EMA, and PMDA dataset structures and IP source coverage. It does not replace official agency certifications, and structured outputs require manual validation for complex combination products where classification definitions differ across jurisdictions.