Trial Investigating an Immunostimulatory Oncolytic Adenovirus for Cancer: Complete Statistical Analysis

1. Trial at a Glance

This page covers the registry results for Trial Investigating an Immunostimulatory Oncolytic Adenovirus for Cancer (NCT03225989), a na phase 1, phase 2 study. The primary outcome is Safety: Toxicity Symptoms Graded According to CTCAE v4.03..

2. Clinical Question

3. Trial Design

This is a Phase I/II study of LOAd703 in people with pancreatic adenocarcinoma, ovarian cancer, biliary carcinoma or colorectal cancer. Its status is completed. The registry gives a start date of 2018-03-01 and a primary completion date of 2023-08-22. Enrollment is recorded as 47; the brief summary says that a maximum of 50 patients can be enrolled. These are distinct registry statements, and the record does not explain their relationship.

The study is described as sequential, with allocation recorded as not applicable and masking recorded as none. It is not a randomized comparison. The groups correspond to different LOAd703 dose levels, with treatment tailored to the cancer indication. LOAd703 was intended as an addition to standard-of-care chemotherapy, or with gemcitabine immune-conditioning when standard of care was no longer an option, such as after the last line. The virus was administered through intratumoral image-guided injections.

The primary outcome is toxicity symptoms graded according to CTCAE v4.03, assessed over up to 50 weeks. The registry also lists secondary outcomes concerning tumor-size response by dose and cancer diagnosis, overall survival, time to progression, progression-free survival, systemic and immune-cell activation, and the presence of LOAd703 virus in blood. The record includes nine outcome measures, but does not report analyses for these outcomes. Details of the sequence used to assign participants to dose groups, dose-escalation rules, decision criteria, or stopping rules are not reported in the registry record. The record also does not explain whether participants entered the groups at the same stage of care or had otherwise comparable baseline characteristics.

4. Participant Flow and Accounting

The registry reports how participants moved through each stage of the study. All counts below are exactly as posted; missing counts are not inferred from other stages.

Before assignment: Overall, a total of 47 subjects signed the informed consent, 5 out of 47 subjects were screening failures and 42 subjects were assigned to the study treatment (Group 1, 2 or 3). One subject was assigned to Group 3, but was not exposed to the study treatment.

Group 1: LOAd703 Dose Level 5x10e10VP

Reasons for not completing this period:

Group 2: LOAd703 Dose Level 1x10e11 VP

Reasons for not completing this period:

Group 3: LOAd703 Dose Level 5x10e11VP

Reasons for not completing this period:

Analysis population for the primary outcome, as defined in the registry: Overall, a total of 42 subjects were assigned to the study treatment, 1 out of 42 did not receive the study treatment and it was not included in the safety evaluation. The subject who did not receive the study treatment was assigned to group 3.

5. Baseline Characteristics

The table reproduces the baseline characteristics posted in the registry, which describe the participants analysed at baseline and help show whether the randomized groups were comparable.

6. Primary Endpoint

The registry lists the primary outcome as Safety: Toxicity Symptoms Graded According to CTCAE v4.03., measured over Up to 50 weeks.

The primary endpoint counts toxicity symptoms graded according to CTCAE v4.03. CTCAE is a standardized framework for describing and grading adverse events; in general, standard grading supports consistent recording of the type and severity of symptoms across participants. The endpoint is expressed as a number of events, rather than as a single measure of tumor response or survival. Its stated timeframe is up to 50 weeks.

A toxicity endpoint is used in early-phase research to characterize harms observed during treatment and to inform decisions about further study. The grade helps distinguish the recorded severity of events; the event count gives a way to describe how many were recorded. These measures answer different questions from whether an event occurred in a particular participant, whether it was serious, or whether it was caused by study treatment. The record’s primary outcome description does not give a detailed definition of the counting unit, rules for repeated events, or the planned summary method. Those details are not reported in the registry record.

The posted information describes the endpoint and gives adverse-event summaries by group, but does not provide a full numerical result for the primary outcome as a count of CTCAE-graded toxicity events by grade. Nor does it report an estimate with a confidence interval. The group-level safety counts can therefore be read as descriptive safety information, not as a complete inferential analysis of the stated primary endpoint.

7. Why No Re-analysis Is Shown

8. Statistical Interpretation

9. Statistical Methods Explained

The registry identifies a primary safety outcome and descriptive group-level adverse-event information. It does not report a statistical analysis plan, model, uncertainty estimates or hypothesis tests. The concepts below explain how such information is generally interpreted; they are not claims about analyses conducted in this study.

What does a count measure?

A count of adverse events and a count of participants affected are not interchangeable. One participant can experience more than one event, while a participant-level summary records whether a participant experienced at least one event in a category. A count of events may therefore be larger than a count of affected participants. The primary outcome is described as a number of events, while the adverse-event summaries separately give participants at risk and affected. The registry does not report detailed counting rules, including how repeated episodes or events spanning categories were handled.

In general, event counts can be summarized by type and severity, while participant counts can describe how many people experienced an event. Neither alone captures all relevant aspects of safety. Timing, duration, severity, seriousness, treatment interruption and attribution may also matter. The registry identifies CTCAE v4.03 as the grading framework for toxicity symptoms, but does not provide a full grade-by-grade result in the posted primary outcome information. A serious adverse event is a separate reporting category and should not be treated as synonymous with a high CTCAE grade.

Why does the comparison design matter?

A randomized design aims to make treatment groups comparable, on average, in both measured and unmeasured characteristics. That comparability supports interpreting between-group differences as evidence about the assigned treatments, subject to other assumptions. This study is recorded as sequential, with allocation not applicable and no masking. Its dose groups are not randomized control arms. In general, a difference between such groups could reflect differences in dose, patient mix, cancer diagnosis, prior care, or treatment context. A simple contrast would not isolate the effect of dose.

Sequential designs can be used to study escalating or changing treatment levels, but the exact sequence and decision rules matter for interpretation. Those protocol details are not reported in the registry record. It would therefore be inappropriate to assume a particular dose-escalation method, stopping boundary or statistical rule. The group counts can still describe what the registry records, but they do not supply a controlled comparison.

What would uncertainty estimates add?

In general, a confidence interval describes a range of values compatible with the observed data under a specified statistical model and repeated-sampling framework. Its width reflects the precision of an estimate, which depends in part on the number of observations and the variability of the data. A point estimate alone does not show how uncertain the estimate is. The registry record does not report confidence intervals for the safety counts or percentages, so the precision of those figures cannot be evaluated with an interval from the posted information.

A p-value, in general, describes how unusual data at least as extreme as those observed would be under a specified null hypothesis and model. It does not measure the probability that a treatment works, nor does it show the size or clinical importance of an effect. The record reports no p-values or inferential safety comparisons. Because there is no randomized comparator, adding a test to an unadjusted contrast would not resolve the underlying design limitations.

How should multiple outcomes be considered?

When a study examines multiple outcomes, groups, event categories or time points, the chance of at least one apparently unusual result can increase if each is tested independently without adjustment. This is the general multiplicity concern. A prespecified hierarchy, adjustment procedure or clearly exploratory framing can help readers understand the status of findings. The record lists multiple secondary outcomes and several adverse-event terms, but does not report a multiplicity strategy or a statistical plan. No conclusion about an adjustment method should be inferred.

Multiplicity is not only a matter of p-values. Selective reporting can also shape the impression created by a long list of measured outcomes. In general, a registry entry can help readers see which outcomes were named, while a complete analysis plan and report are needed to assess outcome definitions, timing, and all planned analyses. Details of prespecification and any changes to planned outcomes are not reported in the registry record.

What does the analysis population mean?

An analysis population defines which participants contribute to a particular result. In safety reporting, people who received at least one dose are often analyzed for adverse events, but the precise rule depends on the protocol and analysis plan. Here, the record says 42 subjects were assigned to study treatment and one who did not receive treatment was excluded from the safety evaluation. It does not state a complete set of analysis-population rules for all endpoints, or explain missing outcome data and follow-up. The reported safety groups should therefore be understood according to the registry’s stated counts, without assuming a broader population definition.

For time-to-event outcomes such as overall survival or progression-free survival, general methods account for differing follow-up and censoring. The record lists these as secondary outcomes but provides no analyses or details about event definitions, censoring, or model choice. No time-to-event result should be inferred from the listed outcome names alone.

10. Multiplicity, Missing Data and Analysis Populations

The registry lists nine outcome measures, including a primary safety outcome and secondary outcomes covering response, survival, progression, immune activation and viral presence in blood. Considering many outcomes can create multiplicity: when many statistical tests are performed, some may appear noteworthy by chance even if there is no underlying effect. This is a general statistical issue, not evidence that any particular reported result is spurious. The registry record does not report a multiplicity adjustment, a testing hierarchy, or which secondary outcomes were intended to be confirmatory versus exploratory.

The record lists no analyses for the outcome measures. It does not report p-values or confidence intervals for the safety results, and does not give enough information to assess whether all planned analyses or outcomes are represented. A statistical analysis plan, prespecified outcome definitions and a clear account of changes are not reported in the registry record. In their absence, the status of any outcome as prespecified, exploratory, or selectively reported cannot be determined from the registry entry.

Missing-data handling is also not described. The record notes that one assigned subject did not receive study treatment and was excluded from the safety evaluation, but this does not establish the missing-data rules for other endpoints or follow-up. The amount and pattern of missing data, participant withdrawal, and outcome-specific analysis populations are not reported in the registry record. For survival or progression outcomes, censoring methods and follow-up completeness are also not described. These omissions limit assessment of potential bias and precision. They do not establish that data were missing; they mean the registry record does not provide the information required to evaluate missingness and its handling.

11. Safety Results

The registry reports serious adverse events as affected participants divided by participants at risk.

Deaths

Other (non-serious) adverse events

Participants with at least one non-serious event at or above the registry's 0% reporting threshold.

Most frequent serious adverse event terms

Most frequent non-serious adverse event terms

Serious events with the highest arm-level rate: pyrexia (42.3%), fatigue (33.3%), general physical health deterioration (33.3%), abdominal pain (33.3%), back pain (33.3%).

The adverse-event entries report participants at risk and participants affected within each dose group. Group 1 lists 3 at risk and 3 affected for serious adverse events, and 3 at risk and 3 affected for other adverse events; the death count is 3. Group 2 lists 12 at risk and 12 affected for serious adverse events, 12 at risk and 11 affected for other adverse events, and 10 deaths. Group 3 lists 26 at risk and 20 affected for serious adverse events, 26 at risk and 26 affected for other adverse events, and 23 deaths.

These are counts, not randomized comparisons. They do not by themselves show that an event was caused by LOAd703, nor do they distinguish event timing, duration or severity. The record does not state whether deaths were attributed to treatment or to the underlying cancers or other causes. The listed percentages for serious-event terms are pyrexia at 42.3%, fatigue at 33.3%, general physical health deterioration at 33.3%, abdominal pain at 33.3%, back pain at 33.3%, and ascites at 16.7%. The denominators and event-specific attribution are not reported in the registry record. The percentages should therefore be read as registry-listed summaries, not as comparative risk estimates.

12. What the Result Does, and Does Not, Mean

The posted results provide a descriptive account of safety events recorded in a Phase I/II study of LOAd703. They identify the numbers of participants at risk and affected for serious and other adverse events in each dose group, list deaths, and name several frequent serious adverse-event terms with percentages. The primary endpoint is defined as toxicity symptoms graded according to CTCAE v4.03 over up to 50 weeks. These elements show the kinds of safety information the record captures.

They do not establish a causal effect of LOAd703 on any event. The study has no randomized control group, and the groups are not like-for-like comparisons. The record does not provide a statistical comparison adjusted for differences among participants or treatment contexts. Counts across the groups should not be interpreted as evidence that one dose level caused more or fewer events. Nor do the available figures alone establish the likelihood of an event for a broader population.

The record also does not provide a full numerical analysis of the stated primary endpoint by toxicity grade, uncertainty estimates, or a detailed account of how events were classified and attributed. The listed serious-event percentages have no reported denominators in the registry entry. The death counts are not accompanied by an attribution analysis. Thus, they should not be read as treatment-related death counts unless the registry explicitly says so, which it does not.

Overall, the registry entry can support a cautious description of the safety events it records, but not a definitive comparative safety conclusion. It does not report results for the listed secondary outcomes in the material described, so no efficacy or survival conclusion follows from the outcome names alone. The statistical interpretation is bounded by the study design and by the absence of analysis details, not just by the size of the recorded counts.

13. Why This Trial Matters Statistically

This trial is statistically notable because it combines multiple cancer diagnoses, different dose groups, and more than one treatment context within a sequential, non-randomized design. That structure may be useful for collecting early safety information across settings, but it makes simple comparisons difficult. A group’s event count can reflect not only dose but also who entered the group, the underlying diagnosis, prior treatment, and whether LOAd703 accompanied standard-of-care chemotherapy or gemcitabine immune-conditioning.

The record illustrates why the distinction between describing events and estimating treatment effects matters. Serious adverse-event counts and named event terms can help characterize what was observed. However, without a randomized control group, clear analysis populations, denominators for the listed percentages, and uncertainty estimates, those observations cannot establish comparative risks. A count is informative about the reported experience in the study, but it does not by itself identify what would have happened under another treatment strategy.

The entry also names outcomes across safety, tumor response, survival, progression, immune activation and viral presence. In general, a broad set of outcomes can support a fuller picture of a study, while increasing the importance of clear prespecification and transparent analysis. Those details are not reported in the registry record. The result is a useful case for reading early-phase registry findings with attention to endpoint definitions, the role of group assignment, the distinction between event and participant counts, and the information needed to judge precision. The appropriate statistical conclusion remains descriptive rather than causal or comparative.

14. Limitations

• The posted summary statistics are the only data these results rest on; patient-level data, full protocols and statistical analysis plans are not available.
• Recalculated results are simple, unadjusted calculations from posted summaries. They do not replace the sponsor's prespecified analysis.

The largest limitation for interpretation is the absence of randomization and a control group. Allocation is recorded as not applicable, and the design is sequential. The dose groups therefore cannot be treated as equivalent arms in a controlled comparison. Differences in recorded safety counts could reflect differences in participant characteristics, cancer diagnosis, clinical context, or other factors rather than dose. The registry does not provide enough baseline information to assess these possibilities.

The study includes pancreatic adenocarcinoma, ovarian cancer, biliary carcinoma and colorectal cancer, and allows more than one treatment context. This heterogeneity may limit how readily an overall safety summary applies to any one diagnosis or treatment setting. The registry record does not report subgroup-level primary endpoint results by diagnosis or treatment context. It also does not give details of the sequential assignment process or dose-escalation decisions.

The primary endpoint is described as a number of CTCAE v4.03-graded toxicity symptoms, but the posted information does not give a complete grade-specific result or the rules for counting repeated events. The adverse-event summaries include affected participants and deaths, but do not report the cause or treatment attribution of deaths. Denominators for the top serious-event percentages and uncertainty estimates are not reported in the registry record.

Finally, analysis-plan details are absent. The record does not report missing-data methods, outcome-specific analysis populations, multiplicity handling, or statistical models. It lists secondary outcomes but does not provide analyses for them. These limitations restrict conclusions to the descriptive information recorded and make it difficult to evaluate precision, completeness, or possible bias.

15. Related Tutorials

16. Related Statistical Calculators

17. Sources

• ClinicalTrials.gov: Trial Investigating an Immunostimulatory Oncolytic Adenovirus for Cancer — NCT03225989.
• Registry record last updated 2024-11-19; status last verified 2024-10.
• Results first posted 2024-11-19.
• Data retrieved from ClinicalTrials.gov on 2026-11-09.
• Group sizes, means, event counts and sponsor-reported p-values are reproduced as posted. Effect estimates, confidence intervals and p-values not attributed to the sponsor are independently calculated from the posted summary statistics.

18. Record Summary

NCT03225989 is a completed Phase I/II trial of LOAd703 for people with pancreatic adenocarcinoma, ovarian cancer, biliary carcinoma or colorectal cancer. The study is recorded as sequential, with allocation not applicable and no masking. LOAd703 was administered by intratumoral image-guided injections with standard-of-care chemotherapy, or with gemcitabine immune-conditioning when standard care was no longer an option. Enrollment is recorded as 47, while the brief summary states a maximum of 50 patients.

The primary outcome is the number of toxicity symptoms graded according to CTCAE v4.03 over up to 50 weeks. The registry reports adverse-event counts by dose group and lists serious-event terms and percentages, but does not report a controlled comparison, confidence intervals, p-values or a complete analysis of the primary endpoint. Because the groups are not randomized, the safety counts are descriptive and do not establish causal or comparative effects. Analysis-plan, missing-data and multiplicity details are not reported in the registry record.