Vitalis Therapeutics Inc. — The NDA for VitaFlow (VTX-401) as submitted 2028-10-12 and accepted for filing 2028-12-11: what the five modules contain, why the integrated summaries are new analyses rather than compilations, what the sixty-day filing review actually decides, and how the program's character changes at acceptance.
~106,200
Pages filed
5
eCTD modules
60 days
Filing review
Standard
Review class
Contents
Forward-dated end-state sample. This artifact speaks from the submission and filing period,
October to December 2028 — two years beyond the 15 October 2026 status date of the
in-flight suite, and deliberately not reconciled against it.
1. What Was Filed
| Application | 505(b)(1) NDA — VitaFlow (VTX-401) |
| Submitted | 2028-10-12 |
| Format | eCTD v4.0 |
| Volume | ~106,200 pages, plus SDTM and ADaM, define.xml, reviewer's guides |
| Clinical study reports | 6 |
| Patient narratives | 214 |
| Filing accepted | 2028-12-11 |
| Review classification | Standard review |
| Action date | 2029-10-11 |
An NDA is not a document. It is a structured electronic submission — roughly a
hundred thousand pages, organized into five modules under an internationally agreed structure,
accompanied by analysis-ready datasets that let a reviewer re-run the sponsor's analyses
independently.
That last point is worth sitting with. The agency does not take the sponsor's word for the result. It receives the data in a standardized form and can reproduce the analysis. A submission whose datasets do not support reproduction generates questions until it does — and questions consume review time the program does not control.
That last point is worth sitting with. The agency does not take the sponsor's word for the result. It receives the data in a standardized form and can reproduce the analysis. A submission whose datasets do not support reproduction generates questions until it does — and questions consume review time the program does not control.
2. The Five Modules
| Module | Contents | What is in it | Pages |
|---|---|---|---|
| Module 1 | Administrative and prescribing information | Forms, proposed labeling, patent and exclusivity statements, the agreed iPSP, financial disclosure, REMS assessment. | ~1,400 |
| Module 2 | Common Technical Document summaries | Quality overall summary, nonclinical overview and summaries, clinical overview, Summary of Clinical Safety and Summary of Clinical Efficacy. | ~2,100 |
| Module 3 | Quality (CMC) | Drug substance and drug product, manufacture, control of materials, specifications, analytical procedures and validation, container closure, stability, device. | ~18,600 |
| Module 4 | Nonclinical study reports | Pharmacology, pharmacokinetics, toxicology — single-dose, repeat-dose, genotoxicity, carcinogenicity, reproductive toxicity. | ~9,800 |
| Module 5 | Clinical study reports | Every clinical study report with protocols, statistical analysis plans, case report forms, patient narratives and datasets. | ~74,300 |
Note the distribution. Module 5 — the clinical study reports — is roughly 70%
of the submission by volume. Module 3, the quality section, is the next largest at about 18%.
Between them they are nearly nine-tenths of what is filed.
The modules a program manager spends most time worrying about — Module 1's administrative content, Module 2's summaries — are the smallest. That inversion is worth remembering when resourcing an assembly effort: the pages are in clinical and CMC, and those are the two functions already fully committed to producing the underlying work.
The modules a program manager spends most time worrying about — Module 1's administrative content, Module 2's summaries — are the smallest. That inversion is worth remembering when resourcing an assembly effort: the pages are in clinical and CMC, and those are the two functions already fully committed to producing the underlying work.
Module 2 is small in volume and disproportionate in influence. It contains the Clinical Overview and the two integrated summaries, and it is where most reviewers actually begin. A reviewer forms an initial view from Module 2 and then goes to Modules 3 through 5 to test it.
3. The Integrated Summaries
| Document | What it does | Why it is under-estimated |
|---|---|---|
| Integrated Summary of Safety (ISS) | Pools safety data across all studies in the program — Phase 1, 2 and 3 — into one analysis population. | Not a compilation of existing tables. A new analysis, with its own statistical analysis plan, requiring every study's data to be mapped to a common structure. |
| Integrated Summary of Efficacy (ISE) | Pools efficacy across the pivotal program and analyzes consistency across subgroups. | Subgroup consistency is where a reviewer looks for effects that hold in the overall population but not in a demographic the label will cover. |
These are new analyses, not compilations. This is the single most common planning error in
a filing, and it is easy to make because the name sounds like assembly work.
The Integrated Summary of Safety pools every participant ever dosed — Phase 1 volunteers, Phase 2 participants, both pivotals and the sub-study — into one analysis population. Studies run years apart, under different protocols, with different data structures and different coding dictionary versions, have to be mapped to a common standard before a single table can be produced. That mapping is real statistical and data-management work with its own analysis plan.
A schedule that treats the ISS and ISE as a six-week write-up after database lock has under-provisioned the critical path of the filing.
The Integrated Summary of Safety pools every participant ever dosed — Phase 1 volunteers, Phase 2 participants, both pivotals and the sub-study — into one analysis population. Studies run years apart, under different protocols, with different data structures and different coding dictionary versions, have to be mapped to a common standard before a single table can be produced. That mapping is real statistical and data-management work with its own analysis plan.
A schedule that treats the ISS and ISE as a six-week write-up after database lock has under-provisioned the critical path of the filing.
The ISE carries a specific risk worth naming: subgroup consistency. An effect that holds in the overall population but disappears in a demographic the label will cover is exactly what a reviewer looks for, and finding it first is considerably better than having it found for you.
4. Filing Review — the Sixty Days Before the Clock Starts
| Step | When | What it means |
|---|---|---|
| Application submitted | 2028-10-12 | The clock has not started. |
| Filing review | 60 days | FDA determines whether the application is sufficiently complete to permit a substantive review. This is not a scientific judgment about the drug. |
| Filing decision | 2028-12-11 | Accepted. The review clock begins from the submission date, and the action date is set. |
| Day 74 letter | 2028-12-25 | FDA communicates the review classification, planned review timeline, and any identified review issues. The program's first substantive signal about how the review will go. |
| PDUFA action date | 2029-10-11 | Ten months from the filing date for a standard review of an NME — twelve months from submission. The clock runs from the filing date, not from receipt. |
Filing review is not scientific review. The agency is answering one question: is this
application sufficiently complete to permit a substantive review at all. Nobody is yet
assessing whether the drug works.
The outcome that matters is refuse-to-file. It is not a rejection of the drug and it is not a delay in the review — it means there is no review. The application is returned, the deficiency is fixed, and the program resubmits into whatever queue then exists, having spent its submission window for nothing.
This is why the Regulatory Strategy treats the agreed pediatric study plan as a filing-blocking obligation rather than administrative housekeeping.
The outcome that matters is refuse-to-file. It is not a rejection of the drug and it is not a delay in the review — it means there is no review. The application is returned, the deficiency is fixed, and the program resubmits into whatever queue then exists, having spent its submission window for nothing.
This is why the Regulatory Strategy treats the agreed pediatric study plan as a filing-blocking obligation rather than administrative housekeeping.
The Day 74 letter
Roughly two and a half months after submission, FDA communicates the review classification, the planned review timeline, and any review issues already identified.
This is the program's first substantive signal about how the review is going, and it
arrives before anyone has told the sponsor anything about the science. A letter listing several
identified issues is a different program position from one that lists none — and it arrives
early enough to change how launch preparation is resourced, which is the only reason the timing
matters commercially.
5. How It Was Assembled
| Workstream | When | Note |
|---|---|---|
| Pre-NDA meeting | 2028-08-10 | Content and format agreed, integrated summary approach confirmed, labeling strategy discussed. Held two months before submission — late enough to have the data, early enough to act on the answer. |
| Datasets and define.xml | Q2–Q3 2028 | Standardized datasets are a submission deliverable in their own right. A reviewer who cannot re-run an analysis will ask questions until they can. |
| Patient narratives | Q2–Q3 2028 | 214 narratives, one per serious adverse event. Authored, medically reviewed, and reconciled against the safety database. |
| Proposed labeling | Q3 2028 | Drafted by the sponsor. What the sponsor proposes and what the agency approves are different documents. |
| Publishing and validation | Q3–Q4 2028 | eCTD assembly, hyperlink validation, technical validation against FDA specifications. A technically invalid submission is rejected before anyone reads it. |
One of those ends careers, and it has nothing to do with science. An eCTD
submission is validated technically before it is read. Broken hyperlinks, non-conforming file
structure, datasets that fail specification checks — any of these can cause a submission to
be rejected on technical grounds by a system, before a human being has opened Module 2.
Publishing is contracted, and it is the one part of the regulatory workstream in the Regulatory Strategy §7 that sits outside the sponsor. It is also the part where a failure is most avoidable and most humiliating.
Publishing is contracted, and it is the one part of the regulatory workstream in the Regulatory Strategy §7 that sits outside the sponsor. It is also the part where a failure is most avoidable and most humiliating.
The pre-NDA meeting on 2028-08-10 was placed deliberately: two months before submission, late enough that the pivotal data existed and the integrated summary approach could be described concretely, early enough that the agency's answer could still change what was filed. A pre-NDA meeting held after the submission is assembled is a meeting about a document nobody can now alter.
6. What the Program Chose Not to Do
- No request for priority review. Not electable in any case; the program planned on ten months and treated anything faster as upside.
- No comparative tolerability claim in the proposed labeling. The decision recorded at Gate 5 §5, on regulatory advice, against the Market Access position.
- No rolling submission. Available under some expedited designations, none of which this program holds.
- No proposed REMS. The safety profile did not support the need for one, and proposing a risk-management program the data does not require invites a question about why the sponsor thinks it does.
The last item is a real judgment and reads as counter-intuitive. Volunteering a risk
evaluation and mitigation strategy looks cautious and cooperative. It is neither. A REMS is a
permanent operational burden on the product, restricts how it can be prescribed and dispensed, and
— most importantly — a sponsor proposing one is asserting that its own drug requires
restrictions to be used safely.
If the data supports that assertion, the agency will require it regardless. If it does not, the sponsor has volunteered a constraint and raised a question in the same sentence.
If the data supports that assertion, the agency will require it regardless. If it does not, the sponsor has volunteered a constraint and raised a question in the same sentence.
7. Position After Acceptance
| Question | Answer at 2028-12-11 |
|---|---|
| Is the application under substantive review? | Yes — accepted for filing, clock running. |
| What is the action date? | 2029-10-11 |
| What can the program still influence? | Response quality and speed on information requests; inspection readiness; launch preparation. |
| What can it no longer influence? | The content of the application. What was filed is what will be reviewed. |
| What remains authorized? | $15,800,000 under Stage 5, covering review support, pre-approval inspection and launch preparation to the action date. |
Somewhere in that sequence the program's character changes, and it is abrupt. For five and a
half years this program made decisions — about doses, endpoints, sites, suppliers, scope and
money. From the moment of acceptance it primarily responds. The agency sets the questions
and the timetable; the sponsor answers well and quickly or answers badly and slowly.
That is a genuinely different management problem, and it is why Stage 5 is the smallest tranche in the program at 7% of base. There is very little discretionary work left to fund. What remains is readiness — and readiness for a pre-approval inspection is the subject of its own artifact.
That is a genuinely different management problem, and it is why Stage 5 is the smallest tranche in the program at 7% of base. There is very little discretionary work left to fund. What remains is readiness — and readiness for a pre-approval inspection is the subject of its own artifact.