Impact of Luspatercept on Healthcare Resource Use (HCRU) Among Patients with Lower-Risk, Myelodysplastic Syndromes (LR-MDS): A Medical Record Review in Canada, Germany, and Spain
Notice bibliographique
Résumé
Background: In patients with lower-risk myelodysplastic syndrome (LR-MDS), luspatercept has demonstrated significant clinical benefit. However, luspatercept's impact on healthcare resource use (HCRU) is not well documented. This study aimed to describe MDS-related HCRU in patients with LR-MDS who initiated luspatercept therapy in Canada, Germany, and Spain. Methods: In this retrospective study, data for patients ≥ 18 years of age diagnosed with LR-MDS and treated with luspatercept after its approval in each country were obtained from patient medical records. Information on patient demographics, clinical characteristics, treatments, and MDS-related HCRU were abstracted by participating hematologists/hem-oncologists from October to November 2023. The date of luspatercept therapy initiation defined the study index date. The rate of inpatient (IP) admissions and emergency room (ER) visits were assessed per 100 patient-years (PYs) in the pre-index date period (i.e., between MDS diagnosis to initiation of luspatercept therapy) and in the post-index date period (i.e., during luspatercept therapy). A subgroup analysis was performed to assess HCRU patterns among patients who received luspatercept as first-line therapy. All analyses were descriptive in nature. Results: A total of 167 patients with LR-MDS and treated with luspatercept (median age 69 years; 61.1% male) were included from 3 countries: Canada (n = 59), Germany (n = 56), and Spain (n = 52). More than one-third of all patients (34.7%) initiated luspatercept therapy in the first line; 58.7% in the second line, and 6.6% in the third or later lines. Of all patients, 62.3% had been treated with erythropoiesis-stimulating agents prior to initiating luspatercept therapy. Median time from MDS diagnosis to luspatercept initiation was 9.3 months (first quartile [Q1] = 2.7, third quartile [Q3] = 22.7) and the median duration of luspatercept therapy was 9.0 months (Q1 = 7.4, Q3 = 13.3). In patients with non-missing HCRU data (n = 165), 17.6% had at least one HCRU encounter (an IP admission or an ER visit) during the pre-index period versus 7.3% in the post-index period. There were 18.9 IP admissions (95% confidence interval [CI] = 13.0-24.7) per 100 PYs in the pre-index period as compared to 8.2 (95% CI = 3.8-12.7) in the post-index period (most common reasons for IP admission: disease-related complications [9.1% vs. 4.3%, respectively] and treatment-related complications [2.4% vs. 1.2%, respectively]). Likewise, the rate of ER visits was 18.4 (95% CI = 12.6-24.2) per 100 PYs in the pre-index period versus 4.4 (95% CI = 1.2-7.7) in the post-index period (most common reasons for ER visit: disease-related complications [7.4% vs. 3.1%, respectively] and treatment-related complications [4.9% vs. 0.6%, respectively]). In the subgroup analysis of first-line luspatercept patients (n = 58), rates of HCRU in the pre-index versus post-index periods were as follows: IP admissions (25.0 vs. 5.5 per 100 PYs); and ER visits (10.7 vs. 3.7 per 100 PYs). Conclusions: In this retrospective study, a reduction in the rate of MDS-related IP admissions and ER visits was observed for patients with LR-MDS after initiating luspatercept, suggesting that the HCRU burden of LR-MDS may be lowered during luspatercept therapy. These findings were consistent for patients initiating luspatercept in the first line of therapy. Future research should examine potential heterogeneity in HCRU patterns that may exist across geographies.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,002 | 0,006 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,006 | 0,015 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,001 | 0,000 |
| Science ouverte | 0,001 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,001 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».