Real-world outcomes of mepolizumab for the treatment of severe eosinophilic asthma in Canada: an observational study
Bibliographic record
Abstract
BACKGROUND: Mepolizumab, the first widely available anti-interleukin 5 biologic, targets eosinophilic inflammation and has been shown in clinical trials to reduce exacerbations, oral corticosteroid dependence, and healthcare utilization in patients with severe asthma. The impact of mepolizumab in a real-world, publicly funded healthcare setting is unknown. The objective of this study was to describe the demographics and clinical characteristics of real-world patients receiving mepolizumab, and to compare asthma-related outcomes and associated asthma-related costs before and during mepolizumab use. METHODS: This retrospective, observational study in Ontario, Canada, included patients initiating mepolizumab between February 2016 and March 2019. Patients were identified using the mepolizumab patient support program and linked to the Institute for Clinical Evaluative Sciences database of publicly accessed healthcare. Patient outcomes were obtained for 12 months pre- and post-mepolizumab initiation and compared. RESULTS: A total of 275 patients were enrolled in the overall patient support program cohort (mean [standard deviation] age 57.6 [13.5] years, mean [standard deviation] of the median per-patient eosinophil count 540.4 [491.9] cells/μL). Mepolizumab was associated with reductions in asthma exacerbations (46.1%, P < 0.001) and in the number of asthma-related visits to general practitioners (40.2%, P < 0.001), specialists (27.2%, P < 0.001), and emergency departments (52.1%, P < 0.001). Associated costs were significantly lower post- versus pre-mepolizumab for asthma-related general practitioner and specialist visits, and for all-cause emergency department visits and hospital admissions. CONCLUSIONS: In a real-world population of Canadian patients with severe asthma with an eosinophilic phenotype, the use of mepolizumab within a patient support program reduced asthma exacerbations and decreased asthma-related healthcare resource utilization and associated costs.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.004 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".