Perioperative oral eltrombopag versus intravenous immunoglobulin in patients with immune thrombocytopenia: a non-inferiority, multicentre, randomised trial
Notice bibliographique
Résumé
Background Patients with immune thrombocytopenia are at risk of bleeding during surgery, and intravenous immunoglobulin is commonly used to increase the platelet count. We aimed to establish whether perioperative eltrombopag was non-inferior to intravenous immunoglobulin. Methods We did a randomised, open-label trial in eight academic hospitals in Canada. Patients were aged at least 18 years, with primary or secondary immune thrombocytopenia and platelet counts less than 100 × 10 9 cells per L before major surgery or less than 50 × 10 9 cells per L before minor surgery. Previous intravenous immunoglobulin within 2 weeks or thrombopoietin receptor agonists within 4 weeks before randomisation were not permitted. Patients were randomly assigned to receive oral daily eltrombopag 50 mg from 21 days preoperatively to postoperative day 7 or intravenous immunoglobulin 1 g/kg or 2 g/kg 7 days before surgery. Eltrombopag dose adjustments were allowed weekly based on platelet counts. The randomisation sequence was generated by a computerised random number generator, concealed and stratified by centre and surgery type (major or minor). The central study statistician was masked to treatment allocation. The primary outcome was achievement of perioperative platelet count targets (90 × 10 9 cells per L before major surgery or 45 × 10 9 cells per L before minor surgery) without rescue treatment. We did intention-to-treat and per-protocol analyses using an absolute non-inferiority margin of –10%. This trial is registered with ClinicalTrials.gov, NCT01621204. Findings Between June 5, 2013, and March 7, 2019, 92 patients with immune thrombocytopenia were screened, of whom 74 (80%) were randomly assigned: 38 to eltrombopag and 36 to intravenous immunoglobulin. Median follow-up was 50 days (IQR 49–55). By intention-to-treat analysis, perioperative platelet targets were achieved for 30 (79%) of 38 patients assigned to eltrombopag and 22 (61%) of 36 patients assigned to intravenous immunoglobulin (absolute risk difference 17·8%, one-sided lower limit of the 95% CI 0·4%; p non-inferiority =0·005). In the per-protocol analysis, perioperative platelet targets were achieved for 29 (78%) of 37 patients in the eltrombopag group and 20 (63%) of 32 in the intravenous immunoglobulin group (absolute risk difference 15·9%, one-sided lower limit of the 95% CI –2·1%; p non-inferiority =0·009). Two serious adverse events occurred in the eltrombopag group: one treatment-related pulmonary embolism and one vertigo. Five serious adverse events occurred in the intravenous immunoglobulin group (atrial fibrillation, pancreatitis, vulvar pain, chest tube malfunction and conversion to open splenectomy); all were related to complications of surgery. No treatment-related deaths occurred. Interpretation Eltrombopag is an effective alternative to intravenous immunoglobulin for perioperative treatment of immune thrombocytopenia. However, treatment with eltrombopag might increase risk of thrombosis. The decision to choose one treatment over the other will depend on patient preference, resource limitations, cost, and individual risk profiles. Funding GlaxoSmithKline and Novartis.
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,003 | 0,004 |
| Méta-épidémiologie (sens strict) | 0,002 | 0,001 |
| Méta-épidémiologie (sens large) | 0,005 | 0,004 |
| Bibliométrie | 0,000 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,002 |
| Communication savante | 0,002 | 0,002 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,003 | 0,004 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,007 | 0,001 |
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 ».