Stopping<i>versus</i>continuing long-term mepolizumab treatment in severe eosinophilic asthma (COMET study)
Bibliographic record
Abstract
Background The long-term efficacy and safety of mepolizumab for treatment of severe eosinophilic asthma are well established. Here, we examine the clinical impact of stopping mepolizumab after long-term use. Methods COMET ( NCT02555371 ) was a randomised, double-blind, placebo-controlled, parallel-group, multicentre study. Patients who had completed COLUMBA ( NCT01691859 ) or COSMEX ( NCT02135692 ) and received continuous mepolizumab treatment for ≥3 years were randomised 1:1 to stop (switch to placebo) or continue subcutaneous mepolizumab 100 mg every 4 weeks for 52 weeks. Primary end-point: time to first clinically significant exacerbation; secondary end-points: time to first exacerbation requiring hospitalisation/emergency department visit, time to decrease in asthma control (≥0.5-point increase in Asthma Control Questionnaire-5 score from COMET baseline) and blood eosinophil count ratio to COMET baseline. Safety was assessed. Results Patients stopping (n=151) versus continuing (n=144) mepolizumab had significantly shorter times to first clinically significant exacerbation (hazard ratio 1.61, 95% CI 1.17–2.22; p=0.004) and decrease in asthma control (hazard ratio 1.52, 95% CI 1.13–2.02; p=0.005), and higher blood eosinophil counts at week 52 (270 versus 40 cells·µL −1 ; ratio (stopping versus continuing) 6.19, 95% CI 4.89–7.83; p<0.001). Differences in efficacy outcomes between groups were observed when assessed from week 12 (16 weeks after last mepolizumab dose). Exacerbations requiring hospitalisation/emergency department visit were rare. Adverse events in patients continuing mepolizumab were consistent with previous studies. For patients who stopped mepolizumab, the safety profile was consistent with other eosinophilic asthma populations. Conclusion Patients who stopped mepolizumab had an increase in exacerbations and reduced asthma control versus those who continued.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.003 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".