← Clinical Trials
PFO - Patent Foramen Ovale Phase not stated Binary Endpoint NCT04433520

Trevisio Post-Approval Study: Complete Statistical Analysis

The Trevisio Post-Approval Study was a completed, single-arm, non-randomized, multi-center study of a delivery system used with occluder devices. The registry record describes technical success and selected safety counts, but does not report the primary endpoint result.

Trial start: 2020-09-14  ·  Enrollment: 254  ·  Sponsor: Abbott Medical Devices
Scope of this record

This page provides an independent statistical analysis and educational interpretation of publicly reported results. ClinicalTrials.gov provides the official trial registry record. Numerical trial results on this page are restricted to the results posted in the ClinicalTrials.gov record; calculations added by Clinical Biostats are labelled as such.

1. Trial at a Glance

This page covers the registry results for Trevisio Post-Approval Study (NCT04433520), a registered phase not stated study. The primary outcome is Effectiveness Endpoint: Rate of Technical Success.

254
Enrollment
Phase not stated
n/a
Arms
In the primary outcome
n/a
Effect
No re-analysis shown
n/a
95% CI
See limitations
FeatureRegistry value
ClinicalTrials.gov identifierNCT04433520
PhasePhase not stated
ConditionPFO - Patent Foramen Ovale, ASD - Atrial Septal Defect, VSD - Muscular Ventricular Septal Defect
AllocationNot Stated
Design modelNot Stated
MaskingNot Stated
Enrollment254
Arms in the primary outcomen/a
Lead sponsorAbbott Medical Devices
Results postedYes

2. Clinical Question

Population

The study enrolled participants with conditions listed as patent foramen ovale (PFO), atrial septal defect (ASD), muscular ventricular septal defect (VSD), or post-infarct muscular ventricular septal defect (PIVSD). The registry describes an ASD/PFO cohort and a VSD cohort. The effectiveness endpoint analysis was performed in the Attempted Procedure population; further details defining that population are not reported in the registry record.

Intervention

The study assessed the Amplatzer Trevisio Intravascular Delivery System used to facilitate percutaneous, transcatheter implantation of Amplatzer occluder devices. The listed devices included PFO and ASD occluders for the ASD/PFO cohort, and muscular VSD or post-infarct muscular VSD occluders for the VSD cohort.

Comparator

There was no randomized comparator group. This was a single-arm, non-randomized study, and the two cohorts represent different clinical indications and occluder-device groups rather than like-for-like control groups. Any comparison between those cohorts would therefore not estimate a randomized treatment contrast.

Primary question

The primary endpoint asked whether technical success was achieved by pre-hospital discharge or 7 days after the procedure. Technical success was defined as successful deployment and release of at least one device. The registry record does not report the number of participants achieving this endpoint, so the rate and its statistical precision cannot be described from the reported information.

3. Trial Design

The Trevisio Post-Approval Study (NCT04433520) is listed as completed. It was a single-arm, non-randomized, multi-center clinical study sponsored by Abbott Medical Devices. Enrollment was 254. The study began on 2020-09-14, and primary completion was recorded on 2023-01-04. These dates describe the registry record; they do not by themselves explain how participants were recruited, followed, or analyzed.

The study evaluated the Amplatzer Trevisio Intravascular Delivery System when used to facilitate percutaneous, transcatheter implantation of Amplatzer occluder devices. The registry describes an ASD/PFO cohort and a VSD cohort. The first included participants indicated for ASD closure or PFO closure; the second included participants indicated for VSD closure with muscular or post-infarct muscular VSD occluders. The listed interventions reflect these different device uses.

Although the study has two named cohorts, it does not have a randomized control group. The cohorts differ in the conditions being treated and in the occluder devices used. They should not be read as interchangeable treatment arms, and the registry record does not describe allocation between them as a randomized process. The method by which participants entered either cohort is not reported in the registry record.

The primary endpoint was technical success, assessed at pre-hospital discharge or 7 days after the procedure. The endpoint analysis population was the Attempted Procedure population. A detailed analysis plan, including the handling of participants with an unsuccessful or unassessable procedure, is not reported in the registry record. The primary endpoint result is also not reported in the registry record, limiting interpretation of the study's effectiveness findings.

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.

Overall Study

StageASD/PFO CohortVSD Cohort
STARTED2513
COMPLETED2513
NOT COMPLETED00

Analysis population for the primary outcome, as defined in the registry: The endpoint analysis was performed on the Attempted Procedure (AP) population

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.

CharacteristicUnitASD/PFO CohortVSD CohortTotal
Participants analysed2513254
Age, Customizedyears45 (0 to 77)77 (63 to 80)61 (0 to 80)
Sex: Female, Male: FemaleParticipants1291130
Sex: Female, Male: MaleParticipants1222124
Race and Ethnicity Not CollectedParticipants——0
MigraineParticipants41041
HypertensionParticipantsNA2NA

6. Primary Endpoint

The registry lists the primary outcome as Effectiveness Endpoint: Rate of Technical Success, measured over at pre-hospital discharge or 7 days after the procedure.

ElementRegistry entry
Result typeCount Of Participants
Measure of spreadnot applicable
UnitParticipants
Endpoint classificationBinary Endpoint

The primary endpoint was the rate of technical success, with the unit described as participants. Technical success meant successful deployment and release of at least one device. The assessment time was pre-hospital discharge or 7 days after the procedure. The analysis population was the Attempted Procedure population.

This endpoint focuses on whether the delivery procedure reached a defined technical milestone. In general, a clearly defined procedural endpoint can describe whether the device-delivery process achieved a specified immediate objective. It is distinct from a longer-term clinical outcome: successful deployment and release alone does not establish what happened to participants after the stated assessment period.

The registry record does not report the number of participants who met the definition, the denominator used for the endpoint result, or an uncertainty interval. Consequently, an endpoint rate cannot be stated, and its precision cannot be evaluated. The enrollment figure does not substitute for the endpoint denominator, because the record identifies the Attempted Procedure population for the analysis but does not report its size.

The registry record lists two outcome measures and two analyses, but details beyond the described primary endpoint are not reported in the registry record. No additional endpoint findings should be inferred from the title or definition of technical success.

7. Why No Re-analysis Is Shown

Reported as posted, not recalculated. Not a randomized comparison (allocation: not stated); arms are not a like-for-like control comparison. A result is recalculated only when the posted data support a clean two-arm comparison, so no result is shown beyond what the sponsor posted.

8. Statistical Interpretation

Clinical Biostats interpretation

The available registry information establishes the study design, the endpoint definition, its assessment time, and selected safety counts. It does not include the primary endpoint result. There is therefore no reported technical-success numerator or rate to interpret, and no confidence interval or other measure of uncertainty for that endpoint is reported in the registry record. Without those values, the posted information cannot show how often technical success was achieved or how precisely that frequency was estimated.

The study was single-arm and non-randomized. The two named cohorts involve different indications and device uses, rather than a randomized intervention and control. The design can describe observations in the enrolled participants, but it does not provide a randomized comparison against another delivery system or another treatment strategy. A difference between the cohorts, if one were reported, would not by itself isolate an effect of the delivery system because the groups are not described as comparable control groups.

The safety information reports serious adverse events for the ASD/PFO cohort as 1 event among 251 at risk, and for the VSD cohort as 0 among 3 at risk. Other adverse events are reported as 7 among 251 at risk in the ASD/PFO cohort and 1 among 3 at risk in the VSD cohort. Deaths are recorded as 0 in each cohort. These are counts with their reported at-risk denominators, not randomized comparisons. The record identifies device embolization at 0.4% among the top serious terms, but the event-specific count is not reported in the registry information available for interpretation.

The different sizes of the reported at-risk groups matter for how stable the cohort summaries may be. In general, estimates based on fewer observations tend to be less precise, and zero recorded events do not establish that the underlying event risk is zero. No confidence intervals or other precision estimates for the adverse-event counts are reported in the registry record. The safety counts should therefore be read as descriptive observations, not as proof of equivalence or as estimates that can be directly compared across cohorts.

Overall, the registry record allows a limited descriptive account of study conduct and selected adverse-event observations. The central effectiveness question remains unresolved in the reported results because the technical-success result is not reported in the registry record. It is not possible to draw a statistical conclusion about the endpoint's frequency or precision from its definition alone.

9. Statistical Methods Explained

The endpoint is binary at the participant level: a participant either meets the stated definition of technical success or does not. In general, binary outcomes are summarized by counts in each category and, when the denominator is known, by a proportion or rate. For this study, the definition is successful deployment and release of at least one device, assessed by pre-hospital discharge or 7 days after the procedure. The registry record does not report the success count or the endpoint denominator, so a rate cannot be interpreted.

What does a confidence interval add?

In general, a confidence interval expresses the statistical uncertainty around an estimate. A point estimate alone does not show how much the observed result might vary across repeated samples under the assumptions of the method. A narrower interval indicates greater precision, while a wider interval indicates less precision. The registry record does not report a confidence interval for technical success or for the listed safety counts, so precision cannot be assessed from the posted results. No interval should be reconstructed without the relevant result and analysis details.

What can a single-arm design estimate?

In general, a single-arm study can describe outcomes observed in the enrolled group. Without a concurrent randomized comparator, it does not isolate the difference attributable to one intervention compared with another. Participants in the ASD/PFO and VSD cohorts have different clinical indications and device uses. The cohorts therefore do not create a like-for-like comparison, and their counts should not be treated as if they arose from randomized treatment allocation. The registry record does not identify a comparative hypothesis or a control group.

How should the sample-size illustration be read?

The registry's planning illustration is described as using the observed effect, a two-sided significance level of 0.05, equal allocation between two arms, and a normal approximation. It considers effects expressed as fractions of the observed effect. These are planning assumptions, not evidence that the trial itself used that design: the study is described as single-arm and non-randomized. The actual illustration values are not reported in the registry information available for interpretation, and the endpoint effect itself is not reported. Thus, no required sample size can be stated from these registry entries.

In general, a planning calculation asks how many participants a hypothetical study might need under specified assumptions. It is not a measure of the probability that the completed study produced a statistically significant result. A calculation anchored to an observed effect also depends on the effect estimate chosen. If that estimate is unavailable, the planning result cannot be checked or translated into a new design recommendation. Such planning figures must not be described as observed power.

Why does the outcome scale matter?

For a binary endpoint, the key information includes the number meeting the definition, the number not meeting it, and the denominator analyzed. Those counts allow an estimate of the event frequency and are needed for many standard uncertainty calculations. The Attempted Procedure population is identified for the primary analysis, but its size and the technical-success counts are not reported in the registry record. The overall enrollment figure cannot be assumed to be the endpoint denominator.

In general, statistical methods also depend on how observations are distributed and how participants are sampled. Over-dispersion is a concern for some count-data models when variability exceeds the model's assumptions; it is not a substitute for defining a binary participant endpoint. The registry entries describe the primary endpoint as a participant count and provide no model specification, dispersion estimate, or rationale for a particular statistical model. Those details are not reported in the registry record.

Likewise, the registry information does not state whether an adjusted analysis, a formal hypothesis test, or an interval method was used for technical success. Statistical significance, if it were reported, would not by itself convey the magnitude or precision of an effect. In this record, the primary result is absent, so neither statistical significance nor the size of the endpoint estimate can be evaluated. The supported interpretation is limited to the stated outcome definition and design, together with the safety counts that are reported.

10. Exact Estimates for Each Arm

No two-arm comparison is shown for this trial, but each arm's result can still be summarized with exact interval estimates computed from the posted counts. The Clopper-Pearson interval is exact and conservative; the Wilson interval is a common closer-to-nominal alternative; the Bayesian credible interval uses a uniform Beta(1, 1) prior. For small groups the three can differ noticeably.

ArmParticipantsEventsObserved %Clopper-Pearson 95% CIWilson 95% CIBayesian 95% credible interval
ASD/PFO Cohort25124798.4%96.0% to 99.6%96.0% to 99.4%96.0% to 99.4%
VSD Cohort33100.0%29.2% to 100.0%43.9% to 100.0%39.8% to 99.4%

R code and output

arm    <- c("ASD/PFO Cohort", "VSD Cohort")
n      <- c(251, 3)
events <- c(247, 3)
for (i in seq_along(n)) {
  ci <- binom.test(events[i], n[i])$conf.int          # Clopper-Pearson exact interval
  cr <- qbeta(c(0.025, 0.975), 1 + events[i], 1 + n[i] - events[i])   # Bayesian, uniform Beta(1,1) prior
  wi <- (function(x, n) { p <- x / n; z <- qnorm(0.975); d <- 1 + z^2 / n
    c((p + z^2 / (2 * n) - z * sqrt(p * (1 - p) / n + z^2 / (4 * n^2))) / d, (p + z^2 / (2 * n) + z * sqrt(p * (1 - p) / n + z^2 / (4 * n^2))) / d) })(events[i], n[i])
  cat(sprintf("ARM|%s|%d|%d|%.1f|%.1f|%.1f|%.1f|%.1f|%.1f|%.1f\n", arm[i], n[i], events[i], 100 * events[i] / n[i],
              100 * ci[1], 100 * ci[2], 100 * wi[1], 100 * wi[2], 100 * cr[1], 100 * cr[2]))
}
ARM  ASD/PFO Cohort  251  247  98.4  96.0  99.6  96.0  99.4  96.0  99.4
ARM  VSD Cohort  3  3  100.0  29.2  100.0  43.9  100.0  39.8  99.4

11. Multiplicity, Missing Data and Analysis Populations

The registry record lists two outcome measures and two analyses, but does not describe the full set of analyses, identify all planned hypotheses, or state whether any multiplicity adjustment was used. When a study evaluates multiple outcomes or makes multiple statistical comparisons, the chance of at least one false-positive result can increase. In general, a prespecified strategy for handling multiple tests helps readers interpret inferential results. No such strategy is reported in the registry record, and the reported information does not establish that a multiplicity adjustment was necessary or performed.

The primary endpoint is assigned to the Attempted Procedure population. The record does not report the number of participants in that analysis population, how it was defined in operational terms, or whether participants were excluded from it. The number with an observed technical-success outcome and the number with missing endpoint data are not reported in the registry record.

Missing-data methods can affect an estimate when outcomes are unavailable. In general, readers need to know how much outcome information is missing, why it is missing, and how the analysis handled those observations. The registry record does not report the amount of missing primary endpoint data, any imputation approach, or a sensitivity analysis. It is therefore not possible to assess whether missing outcomes could have changed the endpoint interpretation.

The registry also does not report details of interim analyses, stopping rules, or a complete statistical analysis plan. These items are not assumed to have been absent; they are not reported in the registry record. The lack of a reported endpoint result further limits assessment of both multiplicity and analysis-population choices.

12. Safety Results

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

ArmParticipants with serious adverse eventsParticipants at riskPercentage
ASD/PFO Cohort12510.4%
VSD Cohort030.0%
Participants with at least one serious adverse event
Serious adverse events by armASD/PFO Cohort0.4%VSD Cohort0.0%% of participants with at least one serious adverse event

Deaths

ArmDeaths (participants affected of at risk)
ASD/PFO Cohort0 of 251
VSD Cohort0 of 3

Other (non-serious) adverse events

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

ArmParticipants affected of at risk
ASD/PFO Cohort7 of 251
VSD Cohort1 of 3

Most frequent serious adverse event terms

Event termOrgan systemASD/PFO CohortVSD Cohort
Device embolizationVascular disorders1 of 2510 of 3

Most frequent non-serious adverse event terms

Event termOrgan systemASD/PFO CohortVSD Cohort
Chest PainGeneral disorders3 of 2510 of 3
TachycardiaCardiac disorders1 of 2510 of 3
Pain In The Punctured GroinGeneral disorders1 of 2510 of 3
Vasc BleedingGeneral disorders1 of 2510 of 3
Other Skin ChangesInjury, poisoning and procedural complications1 of 2510 of 3
Oxygen Saturation DecreaseInvestigations1 of 2510 of 3
St Segment ChangesInvestigations1 of 2510 of 3
HeadacheNervous system disorders1 of 2510 of 3
Sore ThroatRespiratory, thoracic and mediastinal disorders1 of 2510 of 3
HematomaVascular disorders1 of 2510 of 3

Serious events with the highest arm-level rate: device embolization (0.4%).

Do not overextend the safety comparison. Serious-adverse-event counts are safety observations, not efficacy outcomes, and should not be combined with the primary result into a single benefit-risk number.

The registry reports serious adverse-event counts separately for the ASD/PFO and VSD cohorts. The ASD/PFO cohort has 1 serious adverse event among 251 participants at risk; the VSD cohort has 0 among 3 at risk. For other adverse events, the reported counts are 7 among 251 at risk in the ASD/PFO cohort and 1 among 3 at risk in the VSD cohort. Deaths are recorded as 0 in both cohorts.

These figures are descriptive counts, not evidence from a randomized safety comparison. The cohorts differ in clinical indication and device use, and the VSD at-risk group is small. In general, a zero count means that no event was recorded in that observed group; it does not prove that the event cannot occur. Counts from groups of different sizes also have different levels of precision. The registry record does not report confidence intervals for these adverse-event results.

Device embolization is listed among the top serious terms at 0.4%. The corresponding term-specific count and further details are not reported in the registry record. These safety observations should be read as recorded events during the study, not as a complete characterization of risk beyond the recorded participants and reporting period.

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

The study's primary question concerns whether the Trevisio delivery system facilitated technical success, defined as successful deployment and release of at least one device by pre-hospital discharge or 7 days after the procedure. The registry record gives that definition and identifies the Attempted Procedure population, but does not report the number of participants with technical success or the endpoint rate. The primary effectiveness result therefore cannot be quantified from the reported information.

The safety information gives counts for serious and other adverse events, as well as deaths, in the ASD/PFO and VSD cohorts. Those counts describe events recorded among participants at risk. They do not establish that the cohorts have equal safety, nor do they provide a controlled comparison with another delivery system. The cohorts are not randomized control groups and differ by indication and device use.

The study's single-arm, non-randomized design also limits causal interpretation. In general, observations in a single group cannot separate the contribution of the intervention from other influences on outcomes. The reported design does not support a randomized estimate of what would have happened under an alternative device or procedure. The registry record does not report a comparator or a comparative effect estimate.

The posted information does not establish longer-term outcomes, because the stated primary endpoint is assessed by pre-hospital discharge or 7 days after the procedure. It also does not report a confidence interval for technical success or the listed adverse events, the amount of missing outcome data, or the statistical plan. These absences limit assessment of precision and robustness. The appropriate reading is descriptive: the record specifies the technical endpoint and provides selected safety counts, while leaving the primary endpoint result and several analysis details not reported in the registry record.

14. Why This Trial Matters Statistically

This study is statistically notable because it combines a clearly stated procedural endpoint with a design that is descriptive rather than comparative. Technical success is defined as successful deployment and release of at least one device, which identifies a specific procedural milestone. The endpoint is assessed within a defined short-term timeframe. Those features clarify what the outcome is intended to capture, but they do not supply the observed endpoint result.

The two cohorts also illustrate why grouping labels should not be mistaken for treatment arms in a controlled trial. ASD/PFO and VSD participants have different indications and use different occluder-device groups. A comparison between their outcomes would mix differences in the clinical conditions and device use with any differences in observed events. The registry identifies the study as single-arm and non-randomized, so there is no basis for treating cohort comparisons as randomized evidence.

For biostatistical interpretation, the missing primary endpoint count is consequential. A definition alone cannot yield an estimated rate, and without a denominator or uncertainty measure, readers cannot evaluate either the magnitude or precision of the result. This is a useful reminder that a named outcome and an analysis population are not substitutes for a posted estimate.

The safety record similarly highlights the importance of denominators and cohort size. The reported counts are informative as descriptions of recorded events, but the cohorts have different at-risk counts, and the registry record provides no precision intervals. The smaller VSD cohort makes cautious interpretation especially important; a zero recorded count should not be read as proof of no underlying risk.

Finally, the planning assumptions described in the record should be distinguished from the study's actual design. A hypothetical two-arm planning illustration is not evidence that the completed study had random allocation or a comparator. Keeping design, estimation, uncertainty, and planning separate is central to interpreting post-approval registry results responsibly.

15. Limitations

The primary limitation for statistical interpretation is that the registry record does not report the technical-success result. The endpoint definition, assessment time, and analysis population are stated, but the success count, denominator, rate, and confidence interval are not reported in the registry record. The main effectiveness question therefore cannot be answered from the posted results.

The design is single-arm and non-randomized, with cohorts based on different indications and device uses. There is no like-for-like randomized control group, so the study information does not support a causal comparison with another treatment or delivery system. Any comparison between the ASD/PFO and VSD cohorts would be descriptive rather than a randomized contrast.

The reported safety counts have different at-risk denominators across cohorts, and no confidence intervals are reported. The VSD cohort includes 3 participants at risk, so its event counts have limited scope for characterizing uncommon outcomes. The record does not provide event-level detail for the device embolization term beyond its reported 0.4% value.

Further limitations arise from missing reporting details. The registry record does not report the primary endpoint's missing-data amount or handling, a full statistical analysis plan, multiplicity methods, or details of interim analyses. The specific method used to calculate uncertainty for the outcome measures is also not reported in the registry record. These gaps prevent assessment of the robustness of the endpoint estimate even apart from the absent result.

16. Related Tutorials

17. Related Statistical Calculators

18. Sources

Continue through the Clinical Biostats statistical pathway

Use this trial's endpoint as a starting point for deeper study of effect measures, confidence intervals, and sample-size planning.

19. Record Summary

NCT04433520, the Trevisio Post-Approval Study, is listed as completed and sponsored by Abbott Medical Devices. It enrolled 254 participants and is described as a single-arm, non-randomized, multi-center study of the Amplatzer Trevisio Intravascular Delivery System used with occluder devices. The registry lists ASD/PFO and VSD cohorts.

The primary endpoint was technical success, defined as successful deployment and release of at least one device by pre-hospital discharge or 7 days after the procedure. The analysis population was the Attempted Procedure population. The endpoint result is not reported in the registry record.

Reported safety counts include serious adverse events of 1 among 251 at risk in the ASD/PFO cohort and 0 among 3 at risk in the VSD cohort. Other adverse events are 7 among 251 and 1 among 3, respectively; deaths are 0 in each cohort. Device embolization is listed at 0.4% among the top serious terms.

Clinical Biostats