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 A Study to Learn About the Benefit of Rimegepant Versus Triptans in Migraine Buddy App Users. (NCT06532357), a registered phase not stated study. The primary outcome is Number of Participants Classified as Per Responses for Satisfaction of Pain Intensity.
| Feature | Registry value |
|---|---|
| ClinicalTrials.gov identifier | NCT06532357 |
| Phase | Phase not stated |
| Condition | Migraine |
| Allocation | Not Stated |
| Design model | Not Stated |
| Masking | Not Stated |
| Enrollment | 1536 |
| Arms in the primary outcome | n/a |
| Lead sponsor | Pfizer |
| Results posted | Yes |
2. Clinical Question
Population
Eligible US Migraine Buddy app users who used Nurtec (rimegepant) and/or triptans as acute migraine treatment, with or without preventive treatment, and completed a survey. The registry reports enrollment of 1536, but does not report how many participants contributed data to the primary satisfaction outcome.
Intervention
Use of rimegepant, referred to as Nurtec in the study summary, as an acute treatment for migraine. Use was recorded in a real-life app setting rather than assigned by the study.
Comparator
Use of triptans as an acute migraine treatment. The registry does not state how treatment use was allocated, and the groups should not be treated as randomized or necessarily like-for-like.
Primary question
Among eligible survey respondents, how were satisfaction responses about pain intensity classified for rimegepant and triptans? The classification groups responses as satisfied, neutral, or dissatisfied. The registry record does not report the counts in these groups or a direct comparison estimate.
The study asks a descriptive, patient-reported question: how satisfied were app users with acute treatment for pain intensity? The summary describes a comparison of satisfaction with Nurtec and triptans, drawing on retrospective Migraine Buddy data. Because the study is observational, it records treatment use and participants’ reports rather than assigning a treatment. It can therefore describe the responses available in this setting, but by itself cannot establish that a difference in satisfaction was caused by the treatment.
The eligible users could have used Nurtec and/or triptans, and preventive treatment was permitted. The registry does not explain whether a respondent could contribute satisfaction information for both treatments, or how any such repeated responses were handled. That matters because responses from the same person would not necessarily be independent. The record also does not report the treatment-group counts for the primary outcome, so the question is clear but its answer cannot be quantified from the posted results.
3. Trial Design
This is a retrospective observational study using information from US users of the Migraine Buddy app. The study summary says the information was collected for users between 20 October 2023 and 20 May 2024. Eligible participants had used Nurtec and/or triptans as an acute migraine treatment, could also have been receiving preventive treatment, and had completed a survey. The record describes enrollment of 1536. It does not establish that every enrolled participant contributed to the primary endpoint.
The study compares satisfaction reports associated with rimegepant and triptans. Treatment was not assigned by the study; the allocation method is not stated. The record explicitly does not describe a randomized comparison, so treatment groups cannot be assumed to be comparable at baseline. Participants may differ in characteristics, treatment history, preventive medication use, or reasons for using a particular acute treatment. The registry does not report adjustment methods for such differences.
The primary outcome timeframe is described as up to 60 days after the last use of treatment, drawn from a retrospective data-collection period of 7 months. The outcome description also says that available retrospective data were evaluated in an observational study of a single day. The relationship among the treatment-use dates, survey timing, and endpoint assessment is not described in more detail.
The registry lists a study start date of 2024-06-09 and a primary completion date of 2024-06-10, with status COMPLETED. These dates do not change the retrospective nature of the data. The record lists six outcome measures and zero analysis entries. It does not report a protocol-level statistical plan, a sample-size justification, or details of interim analyses. The absence of registered analysis entries should not be interpreted as proof that no analysis was conducted; it means those analyses are not described in the registry record.
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: As pre-specified, only variables/data collected were the self-reported satisfaction of Migraine Buddy users via a questionnaire accessible from the home screen of the application. Users completed the satisfaction questions only once for each current acute migraine treatment. A total of 1536 participants were enrolled in this study who completed the survey. There were few participants who were not exclusive and completed survey for both rimegepant and triptans.
Period 1: Rimegepant User Survey
| Stage | Rimegepant | Triptans |
|---|---|---|
| STARTED | 708 | 0 |
| COMPLETED | 708 | 0 |
| NOT COMPLETED | 0 | 0 |
Period 2: Triptans User Survey
| Stage | Rimegepant | Triptans |
|---|---|---|
| STARTED | 0 | 845 |
| COMPLETED | 0 | 845 |
| NOT COMPLETED | 0 | 0 |
Analysis population for the primary outcome, as defined in the registry: Analysis population included all eligible participants whose data were retrieved and observed in the study.
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.
Population: For this retrospective study, as planned the only variables collected are the self-reported treatment satisfaction of Migraine Buddy users via a questionnaire accessible from the home screen of the application. Hence, Baseline data was not retrieved and not collected to be reported in the results.
| Characteristic | Unit | Rimegepant | Triptans | Total |
|---|---|---|---|---|
| Participants analysed | 0 | 0 | 0 | |
| Sex/Gender, Customized: Male | Participants | — | — | — |
| Sex/Gender, Customized: Female | Participants | — | — | — |
6. Primary Endpoint
The registry lists the primary outcome as Number of Participants Classified as Per Responses for Satisfaction of Pain Intensity, measured over Up to 60 days post last usage of treatment (from retrospective data collection period of 7 months); available retrospective data was evaluated in this observational study of a single day.
| Element | Registry entry |
|---|---|
| Result type | Count Of Participants |
| Measure of spread | not applicable |
| Unit | Participants |
| Endpoint classification | Binary Endpoint |
The primary endpoint counts participants according to their reported satisfaction with treatment for pain intensity. Survey responses ranged from extremely satisfied through extremely dissatisfied. The registry groups the three satisfaction responses at the positive end as satisfied, the neither-satisfied-nor-dissatisfied response as neutral, and the three dissatisfaction responses as dissatisfied. The endpoint is therefore a count-based summary of participant-reported experience, rather than a measure of pain intensity itself or a clinical measure of migraine frequency.
Grouping response levels can make the overall direction of reported satisfaction easier to describe. It also removes detail: people who chose different response levels within a grouped category are counted together. Neutral responses are kept distinct from both satisfaction and dissatisfaction, so the classification does not force every participant into a positive or negative judgment.
This endpoint is useful for addressing the study’s stated interest in satisfaction in a real-life app setting. It captures how respondents evaluated treatment, but it depends on survey completion and self-report. It should not be read as a direct measure of treatment efficacy, and satisfaction alone does not show why a participant selected a response.
The registry identifies the endpoint and its classification rules but does not report the observed category counts, treatment-specific denominators, or a comparative estimate. Consequently, the posted registry record does not show how satisfaction was distributed in either treatment group or how precise any difference might be.
7. Why No Re-analysis Is Shown
8. Statistical Interpretation
The primary endpoint is defined clearly enough to understand what is intended to be counted: participants are categorized as satisfied, neutral, or dissatisfied based on survey responses about treatment for pain intensity. However, the registry record does not report the number in any category for either rimegepant or triptans. It also does not report an effect estimate, confidence interval, or test result for the comparison. The record therefore describes the measurement question, but does not provide the numerical outcome needed to assess the direction, size, or precision of a difference.
The enrollment figure of 1536 is not a substitute for the endpoint denominators. Enrollment does not establish how many eligible respondents contributed usable satisfaction data, whether some participants reported on both treatments, or how missing survey responses were handled. Treatment-specific denominators and the analysis population for the primary endpoint are not reported in the registry record.
Even if category counts were available, interpretation would need to account for the observational design. Treatment was not assigned by randomization, and the allocation method is not stated. Differences in satisfaction could reflect differences among people who used each treatment, their treatment histories, their preventive therapies, or other factors, rather than treatment alone. The registry does not report an adjusted analysis that would address these possibilities. The data are retrospective and survey-based, so reporting and selection processes may also affect which experiences are represented.
General statistical interpretation: an estimate describes the observed contrast in the analyzed data, while a confidence interval conveys the range of values compatible with that estimate under the model and its assumptions. A narrow interval would indicate greater statistical precision than a wide interval, but neither interval width nor a small p-value resolves bias from nonrandom treatment selection or missing responses. No estimate, interval, or p-value for this endpoint is reported in the registry record, so none can be evaluated.
The registry lists six outcome measures but zero analysis entries. The other outcome definitions and any analysis specifications are not reported in the registry record. It is therefore not possible to determine whether the posted primary question was one of several tested comparisons, whether multiplicity was addressed, or whether the analysis followed a prespecified plan. Sample-size planning assumptions are described in the record, but no planning sample sizes or endpoint effect estimates are reported. Those assumptions cannot be used to infer observed power or the precision of the actual comparison.
The adverse-event fields list zero participants at risk and zero affected in both treatment groups for serious and other adverse events, with no serious-event terms listed. These recorded zeros do not establish that no adverse events occurred; the registry does not explain the data capture or reporting behind those fields. Overall, the record supports a description of the study question and design, but it does not support a numerical conclusion about satisfaction or safety.
9. Statistical Methods Explained
What does a participant count represent?
General explanation: a count is the number of participants assigned to a defined outcome category. Counts are easiest to interpret alongside their denominators, because the same count can have different meanings in groups of different sizes. This endpoint is described as a count of participants in satisfaction categories. The registry record does not report the category counts or the treatment-specific denominators, so the relative frequency of each response group cannot be assessed from the registry information.
The endpoint starts with an ordered set of survey responses, from extremely satisfied to extremely dissatisfied. It then combines the positive responses into a satisfied category, retains the neither-satisfied-nor-dissatisfied response as neutral, and combines the negative responses into a dissatisfied category. This recoding can simplify communication, but it discards distinctions among response levels within each combined category. It also treats the neutral category separately rather than assuming it is equivalent to either positive or negative satisfaction.
How should the treatment comparison be understood?
General explanation: a comparative analysis asks whether the observed outcome distribution differs between the treatment groups. The exact statistical method depends on the design, the data structure, and the analysis plan. The registry record does not name a test or model for the primary endpoint. It also does not report whether the comparison used counts, proportions, an ordinal model, or another approach. No particular method should therefore be attributed to the study.
The design raises an important data-structure question. Eligible people could use Nurtec and/or triptans. If some respondents contributed information for both treatments, their observations would be related. General statistical methods may need to account for such within-person dependence rather than treating every treatment response as independent. The registry record does not report whether participants contributed to one or both treatment categories or how repeated responses were handled.
What does nonrandom allocation mean statistically?
General explanation: random assignment helps balance measured and unmeasured participant characteristics across treatment groups on average. In an observational comparison, treatment choice arises outside a randomized allocation process, and groups can differ for reasons related to both treatment use and reported outcomes. Statistical adjustment can sometimes address measured differences, but it cannot guarantee removal of unmeasured confounding. The registry says this is not a randomized comparison and that allocation is not stated. It does not report covariates or adjustment methods for the satisfaction comparison.
As a result, even a statistically precise association would not alone establish a causal treatment effect. Precision concerns random uncertainty under a chosen model; bias concerns systematic departures from the comparison the analysis intends to make. More precise estimates do not automatically correct nonrandom selection, recall limitations, or differential survey response.
What would an interval or test contribute?
General explanation: a confidence interval describes uncertainty around an estimate under the statistical model and assumptions used. A hypothesis test evaluates how compatible observed data are with a specified null hypothesis under that model. Neither provides a complete assessment of study quality. Intervals and tests require appropriate data and a defined analysis; they cannot be reconstructed when the needed outcome counts and analysis details are absent. The registry record does not report a confidence interval or p-value for the primary endpoint.
The record describes planning assumptions for sample-size illustrations: a two-sided significance level of 0.05, equal allocation between the treatment groups, a normal approximation, and effects defined as stated fractions of the observed effect. For time-to-event outcomes, the description refers to total events; for other outcomes, it refers to participants per arm. These are planning assumptions, not an account of the study’s actual allocation or a report of observed power. The registry does not report the resulting sample-size illustrations, the observed effect used to define those illustrations, or the original sample-size justification. They therefore do not establish whether this study was adequately powered.
Why does over-dispersion matter in general?
General explanation: over-dispersion occurs when outcome variability is greater than a statistical model assumes. If a model understates variability, its standard errors may be too small and its intervals too narrow. This issue can arise in some count-data settings, but the primary endpoint is described as participant counts across satisfaction categories, and the registry does not report a model or evidence of over-dispersion. It would not be appropriate to claim that over-dispersion was present or that a correction was applied.
What can be concluded about the analysis?
The registry lists six outcome measures and zero analysis entries. The primary endpoint definition is available, but the other outcome details, analytic methods, handling of missing data, and multiplicity approach are not reported in the registry record. There is also no reported outcome estimate to recalculate from posted summary statistics. Thus, no independent unadjusted recalculation is available, and no sponsor analysis can be compared with a recalculated result. The posted record is insufficient to evaluate model choice, uncertainty estimates, or robustness checks.
10. Multiplicity, Missing Data and Analysis Populations
The registry lists six outcome measures, while the information available for the primary endpoint identifies satisfaction with pain intensity. The other outcome definitions, their status as primary or secondary, and any planned comparisons are not reported in the registry record. The record lists zero analysis entries. It does not state whether multiple outcomes or comparisons were tested, whether a hierarchy was prespecified, or whether any adjustment for multiplicity was used.
General explanation: when researchers test several hypotheses, the chance of at least one apparently unusual result can increase if each test is interpreted separately. A prespecified hierarchy or a multiplicity adjustment can help control the interpretation of a family of tests. Without the full set of planned tests and the analysis plan, it is not possible to assess whether such an approach was needed or used in this study.
The primary endpoint description does not report how missing surveys, incomplete responses, or unavailable treatment data were handled. It also does not state whether participants with missing endpoint data were excluded, retained in another analysis, or assigned any particular classification. The analysis population is described generally as eligible participants whose data were retrieved and observed, but the registry does not give its treatment-specific size or define the handling of missing data further.
General explanation: missingness can affect both the number of observations and the representativeness of the analyzed respondents. If the chance of completing a survey is related to treatment experience, the responses that remain may not reflect all eligible app users. Without response counts and a missing-data strategy, the extent and direction of any resulting bias cannot be assessed. The enrollment figure alone does not resolve these questions.
11. What the Result Does, and Does Not, Mean
The registry record identifies a real-life, retrospective question about app users’ satisfaction with rimegepant and triptans for migraine pain intensity. It defines how survey responses were grouped and reports the study’s enrollment. These details explain the intended measurement and general study population, but the record does not provide the actual satisfaction counts, treatment-specific denominators, or a comparative estimate. It therefore does not show which treatment group had more satisfied respondents or how large any observed difference was.
The study’s observational design also limits causal interpretation. Treatment was not randomly assigned, and the allocation method is not stated. People using different acute treatments may differ in ways that affect satisfaction. Even if a numerical association were reported, it could not be attributed to treatment alone without considering those differences and the limitations of any adjustments used. No adjusted analysis is reported in the registry record.
Satisfaction is a patient-reported outcome, not a direct measure of pain intensity or a complete assessment of treatment effects. The grouping of response options makes the categories easier to describe, while combining response levels loses detail. Survey completion and retrospective reporting can also shape which experiences are captured.
The record’s sample-size assumptions are planning illustrations, not observed power. No effect estimate or sample-size illustration values are reported, and the information does not establish the precision of an actual comparison. The adverse-event entries report zeros for both groups, but the registry does not explain those entries; they should not be interpreted as proof that no adverse events occurred. In short, the registry describes the study’s question and methods at a high level, but does not provide enough outcome or analysis information to quantify a result or draw a treatment-effect conclusion.
12. Why This Trial Matters Statistically
This study matters statistically because it illustrates the difference between a patient-centered research question and the evidence needed to answer it quantitatively. Satisfaction with acute migraine treatment is a meaningful experience to measure, and app-based retrospective data can describe treatment use in a real-life setting. Yet a defined endpoint is only the starting point for interpretation. Counts, denominators, a comparison estimate, and an account of uncertainty are needed to understand the observed pattern.
The study also highlights the challenge of comparing treatments without random assignment. App users chose or received treatments outside a randomized comparison, so differences between treatment groups may reflect participant characteristics and treatment histories as well as treatment-associated experience. The possibility that one respondent contributed information about both treatments is also relevant to the analysis structure, but the registry does not state how responses were linked or handled.
Transparent reporting is especially important for retrospective survey analyses. Clear response counts, missing-data rules, analysis populations, and prespecified methods would help readers judge who is represented and how the comparison was made. The registry record does not report these details for the primary outcome, nor does it provide its result. This limits assessment of both effect size and statistical precision.
The case is therefore a useful reminder that real-world relevance and statistical interpretability are related but distinct. A real-life setting can offer useful context, while still requiring careful attention to selection, measurement, dependence, and uncertainty. Without the numerical outcome and analytic details, the satisfaction comparison remains a stated research question rather than a quantifiable result in the registry record.
13. 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 principal limitation for interpreting this specific record is that the primary outcome results are not reported. The registry defines the satisfaction categories but gives no category counts, treatment-specific denominators, comparative estimate, confidence interval, or test result. The enrollment figure does not establish the size of the analyzed population, so the completeness of the primary endpoint data cannot be judged.
The study is retrospective and observational, and the treatment allocation method is not stated. The registry characterizes the comparison as nonrandomized. Consequently, the treatment groups may differ in characteristics that are associated with satisfaction. The record does not describe an adjustment strategy or give the participant characteristics needed to assess group comparability.
The eligibility description allows use of Nurtec and/or triptans and permits background preventive treatment. The record does not say whether individuals contributed data for both acute treatments, whether responses were repeated, or how dependence between any such observations was handled. It also does not explain the timing of each survey in relation to treatment use beyond the stated timeframe of up to 60 days after last use.
Because the endpoint is based on survey responses, its interpretation depends on who completed the survey and how responses were recorded. The registry does not report response rates, missing-data handling, or whether the observed respondents represent all eligible app users. The grouping of response levels also reduces detail within the satisfied and dissatisfied categories.
Finally, the record lists six outcome measures but zero analysis entries. The other outcomes, analysis plan, multiplicity handling, and any sample-size justification are not reported in the registry record. Adverse-event fields are recorded as zero for both groups, but the record does not explain the reporting basis. These limitations prevent a complete assessment of the analysis and its findings.
14. Related Tutorials
15. Related Statistical Calculators
16. Sources
- ClinicalTrials.gov: A Study to Learn About the Benefit of Rimegepant Versus Triptans in Migraine Buddy App Users. — NCT06532357.
- Registry record last updated 2025-08-22; status last verified 2025-08.
- Results first posted 2025-08-11.
- 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.
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.
17. Record Summary
The registry record describes NCT06532357, titled “A Study to Learn About the Benefit of Rimegepant Versus Triptans in Migraine Buddy App Users.” The official title is “Evaluation of Satisfaction With Rimegepant and Triptans Utilizing Migraine Buddy Retrospective Data.” Pfizer is listed as the sponsor, the condition is Migraine, enrollment is 1536, and the status is COMPLETED.
The study uses retrospective US Migraine Buddy app data for eligible users who used Nurtec and/or triptans for acute migraine treatment and completed a survey. The primary outcome classifies pain-intensity satisfaction responses as satisfied, neutral, or dissatisfied. The registry lists six outcome measures and zero analysis entries. It does not report the primary outcome counts or a comparison estimate, and it does not describe the analysis plan, missing-data handling, or multiplicity approach.
The study is observational and not a randomized comparison; allocation is not stated. The registry lists zero participants at risk and zero affected for serious and other adverse events in both treatment groups, without explaining those entries. The record supports understanding the research question and broad design, but does not provide the numerical satisfaction results needed to evaluate the comparison.