Regulatory — Glossary¶

← Back to glossary index

The regulatory frameworks, filings, and standards that govern clinical trials and drug development globally.

Terms covered:

IND / NDA / BLA / MAA
CTA (Clinical Trial Application)
FDA Type A / B / C meetings
Project Optimus
ICH-GCP
21 CFR Part 11
GxP (GCP, GLP, GMP, GVP)
Computer Systems Validation (CSV)
Pharmacovigilance / safety reporting
Major regulatory authorities

IND / NDA / BLA / MAA¶

Definition. The four foundational regulatory filings in drug development:

IND (Investigational New Drug, US FDA) — submitted before first human dosing; permission to conduct clinical trials
NDA (New Drug Application, US FDA) — submitted to seek approval to market a small molecule drug
BLA (Biologics License Application, US FDA) — submitted to seek approval to market a biologic (antibody, vaccine, cell therapy, gene therapy)
MAA (Marketing Authorisation Application, EU EMA) — the EU equivalent of NDA / BLA

In practice. A typical drug development timeline:

IND filed before Phase 1 begins (FDA has 30 days to object; if silent, the IND is "in effect")
CTA filed in other jurisdictions (EU, UK, AU, etc.) for parallel trial conduct
Phase 1, 2, 3 trials conducted under the IND / CTA framework
After successful pivotal Phase 3, NDA / BLA / MAA filed for marketing approval
Post-approval, ongoing obligations under the approved label and via Phase 4 commitments

For Adagene's muzastotug, the asset is currently under an active IND in Phase 2; a future BLA would seek approval for muzastotug as a biologic.

Why it matters. These filings are the gating regulatory events for drug development. Each is an enormous document submission (often tens of thousands of pages) that requires aggregation of clinical, preclinical, manufacturing, and quality data. Quality of submission significantly affects approval timeline.

Where Flusso fits. Indirect — Flusso supports submissions by providing audit-trail evidence and CDISC-aligned operational data, but the regulatory affairs / regulatory operations function owns the submission process itself.

CTA (Clinical Trial Application)¶

Definition. The application submitted to a regulatory authority outside the US to seek permission to conduct a clinical trial. Different jurisdictions use different names — CTA is the generic term — but the function is similar to a US IND.

In practice. Common equivalents:

CTA — used generically and in EU, UK, AU, NZ, Singapore
CTN / CTX (Clinical Trial Notification / Exemption) — Australia, sub-types of CTA
CTA-EU — EU CTA, harmonised under the Clinical Trials Regulation (CTR) 2014/536
NMPA submission — China, distinct process under the National Medical Products Administration
PMDA J-NDA — Japan, distinct process

For a multi-jurisdictional trial (Adagene's typical APAC + US footprint), the sponsor must hold an active IND (US) AND CTAs (or equivalents) in every other country with active sites.

Why it matters. CTA timelines vary enormously by jurisdiction (4 weeks in some jurisdictions, 6+ months in others). CTA approval is a prerequisite for site activation in that jurisdiction. Multi-jurisdictional CTA management is a primary driver of trial start-up cycle time.

Where Flusso fits. CTA / IND status per jurisdiction is a tracked attribute in trial setup. Flusso surfaces regulatory approval status across the trial portfolio.

FDA Type A / B / C meetings¶

Definition. Categories of formal meetings between drug sponsors and the US FDA. The categories define the urgency, scope, and timing of the meeting:

Type A — urgent meetings (e.g., dispute resolution, clinical hold lifting); FDA target ~30 days to schedule
Type B — pre-submission and milestone meetings (pre-IND, end-of-Phase-1, end-of-Phase-2, pre-NDA/BLA); FDA target ~60 days
Type C — other meetings not fitting A or B; FDA target ~75 days

In practice. Type B meetings are particularly important — they're the "milestone meetings" where FDA provides feedback on the development program. The end-of-Phase-2 (EoP2) meeting determines whether the FDA agrees with the proposed Phase 3 design; the pre-NDA/BLA meeting confirms submission readiness.

For Adagene's muzastotug, FDA interactions on Project Optimus dose-optimisation likely happened via Type B meetings.

Why it matters. FDA meetings shape the development program — meeting outcomes can require protocol amendments, additional studies, or significant strategy changes. Preparation is intensive: a typical Type B meeting briefing book is 100-300 pages.

Where Flusso fits. Briefing book preparation requires the same kind of cross-system evidence aggregation as JSC packs and milestone evidence packets. Flusso's evidence packet infrastructure applies.

Related: Project Optimus · IND / NDA / BLA / MAA

Project Optimus¶

Definition. An FDA Oncology Center of Excellence initiative (launched 2021) to reform dose optimisation in oncology drug development. Replaces the historical "highest tolerated dose" approach with a requirement to evaluate multiple doses in registration-enabling studies and select the optimal dose based on benefit-risk, not just maximum tolerated dose.

In practice. Project Optimus typically requires:

Randomised dose-comparison studies (e.g., two or three dose levels) before pivotal Phase 3
Pharmacokinetic / pharmacodynamic data supporting dose selection
Exposure-response analyses
Long-term tolerability data at multiple doses
Justification documentation for the dose chosen for Phase 3 / for the label

For Adagene's muzastotug, the randomised Phase 2 study with two dose levels (10 mg/kg and 20 mg/kg) in the pembrolizumab combination is "designed in alignment with FDA Project Optimus" per their public disclosures.

Why it matters. Project Optimus has materially changed oncology development — it adds time and cost to the pre-Phase-3 phase but is intended to produce better-tolerated approved doses. Defending dose-selection decisions to the FDA requires extensive, well-documented analytical work.

Where Flusso fits. Statistical defensibility — versioned, auditable computation envelopes for sample-size, power, and dose-comparison analyses with regulator-ready PDF export — directly supports Project Optimus dose-defence at FDA Type B meetings.

ICH-GCP¶

Definition. The International Council for Harmonisation Good Clinical Practice guideline (ICH E6) — the international standard for the design, conduct, recording, and reporting of clinical trials. Adopted (with local modifications) by major regulatory authorities globally including FDA, EMA, PMDA, and others.

In practice. ICH-GCP defines:

Sponsor and investigator responsibilities
IRB / Ethics Committee responsibilities
Informed consent requirements
Protocol design requirements
Data quality and integrity requirements (including ALCOA-C principles)
Investigational product handling
Adverse event reporting

ICH E6 is currently in its R3 revision (released 2025), modernised for risk-based monitoring and decentralised trial models.

Why it matters. ICH-GCP is the universal compliance framework for clinical trials. Regulatory inspections assess GCP compliance; non-compliance can result in trial-data rejection or worse. Every clinical trial system, process, and SOP is built around GCP.

Where Flusso fits. Flusso operates within the GCP framework — read-only access to validated source systems preserves GCP compliance posture; audit-trail capture supports GCP documentation requirements.

Related: GxP · 21 CFR Part 11

21 CFR Part 11¶

Definition. US FDA regulation governing electronic records and electronic signatures in FDA-regulated activities. Defines the requirements for an electronic system to be considered an acceptable substitute for paper records and handwritten signatures.

In practice. Part 11 compliance requires:

Validated electronic systems (system testing documented)
Audit trails capturing who did what, when (and why, where applicable)
User access controls and authentication
Data integrity protections (no unauthorised modification, deletion)
Electronic signatures with identity verification and intent
Record retention through the regulatory retention period

EU GMP Annex 11 is the European equivalent (substantially aligned).

Why it matters. Any electronic system handling regulated clinical or manufacturing data needs Part 11 compliance. Validation effort to achieve Part 11 compliance is significant — months for a new CTMS or EDC. Replacing a Part 11-validated system means re-validation.

Where Flusso fits. Flusso does not write into Part 11-validated source systems by default — preserving the validation status of Oracle CTMS, Veeva Vault, Medidata Rave. For configurations where Flusso is the system of record (e.g., for derived analytics, JSC dashboards), Flusso operates as a Part 11-compliant system.

Related: Computer Systems Validation (CSV) · GxP · ICH-GCP

GxP (GCP, GLP, GMP, GVP)¶

Definition. A family of "Good Practice" quality frameworks governing different phases of drug development:

GCP (Good Clinical Practice) — clinical trial conduct
GLP (Good Laboratory Practice) — non-clinical (preclinical) safety studies
GMP (Good Manufacturing Practice) — drug manufacturing
GVP (Good Pharmacovigilance Practice) — post-approval safety monitoring
GDP (Good Distribution Practice) — drug distribution
GxP is the umbrella term

In practice. Each domain has its own regulatory framework, inspection regime, and compliance documentation. A drug going from discovery to market traverses GLP (preclinical safety), GMP (manufacturing for trials), GCP (clinical trials), and ultimately GMP (commercial manufacturing) and GVP (post-approval safety monitoring).

Why it matters. GxP compliance is non-negotiable. Inspection findings of GxP non-compliance can halt trials, withdraw approvals, or trigger consent decrees.

Where Flusso fits. Flusso operates in the GCP space (clinical trial operations) and adjacent spaces (regulatory operations, evidence chain). For systems supporting GMP or GLP environments, separate validation considerations apply.

Computer Systems Validation (CSV)¶

Definition. The process of establishing documented evidence that a computerised system consistently performs according to its intended use. Required for any system handling GxP-regulated data.

In practice. CSV typically follows the GAMP 5 framework (Good Automated Manufacturing Practice) and includes:

User Requirements Specification (URS) — what the system must do
Functional Specification (FS) — how the system does it
Risk Assessment — categorising risks to GxP integrity
Installation Qualification (IQ) — system installed correctly
Operational Qualification (OQ) — system operates per spec
Performance Qualification (PQ) — system performs reliably in production
Ongoing change control — every change re-validated

Validation effort scales with system criticality and complexity. A new EDC system can require 3-6+ months of validation work.

Why it matters. Validation is the operational gate for any new GxP system. Replacing a validated system is enormously expensive — which is why system replacement is a much higher bar than system addition. This is part of why Flusso's "additive, not replacement" positioning is so important.

Where Flusso fits. By integrating with validated source systems read-only, Flusso avoids triggering re-validation of those systems. Flusso's own components are validated to the extent they handle GxP-regulated data.

Related: 21 CFR Part 11 · GxP

Pharmacovigilance / safety reporting¶

Definition. The systematic monitoring, detection, assessment, and prevention of adverse effects from medicinal products. Encompasses safety reporting during clinical trials and post-marketing safety surveillance.

In practice. During clinical trials, sponsors must:

Capture adverse events (AEs) and serious adverse events (SAEs) per protocol
Report SUSARs (Suspected Unexpected Serious Adverse Reactions) to regulators within tight timelines (7 days for fatal/life-threatening, 15 days for others)
Submit periodic safety reports (DSURs — Development Safety Update Reports) annually
Maintain a safety database (typically a separate system from the EDC, often Oracle Argus or Veeva Vault Safety)
Convene safety review committees (SRC, DSMB) per protocol-defined cadence

Post-marketing, the equivalent function continues under GVP.

Why it matters. Safety reporting failures are among the most serious regulatory violations. SUSAR reporting timelines are non-negotiable. Pattern detection across trials of the same asset is a leading indicator of programmatic safety issues.

Where Flusso fits. Cross-trial safety signal aggregation — visible in the SRC dashboard — is one of the highest-value pharmacovigilance use cases for Flusso.

Related: SRC · DSMB · GVP

Major regulatory authorities¶

Definition. The national and supranational bodies that regulate drug development and approval. The major ones for global oncology development:

Authority	Jurisdiction	Notes
FDA	US	Food and Drug Administration; oncology decisions made by Oncology Center of Excellence (OCE)
EMA	EU	European Medicines Agency; centralised approval pathway
MHRA	UK	Medicines and Healthcare products Regulatory Agency; post-Brexit independent authority
NMPA	China	National Medical Products Administration; rapid reform over the past decade
PMDA	Japan	Pharmaceuticals and Medical Devices Agency
TGA	Australia	Therapeutic Goods Administration; recognises FDA / EMA approvals via comparable-overseas-regulator pathway
HSA	Singapore	Health Sciences Authority
MFDS	South Korea	Ministry of Food and Drug Safety
CDSCO	India	Central Drugs Standard Control Organisation
Health Canada	Canada
ANVISA	Brazil

Why it matters. Multi-jurisdictional trials must navigate each authority's distinct submission requirements, timelines, and post-approval obligations. Adagene's APAC + US footprint involves NMPA + HSA + FDA at minimum, with TGA, PMDA, MFDS commonly added for broader Phase 2/3 trials.

Where Flusso fits. Flusso supports the multi-jurisdictional regulatory affairs function by tracking submission and approval status per jurisdiction per trial, surfaced through the operational dashboard.

Related: IND / NDA / BLA / MAA · CTA

← Back to glossary index