MétaCan
Menu
Retour à la cohorte
Enregistrement W2997561837 · doi:10.1681/asn.2019070676

Clinical Features and Outcomes of Immune Checkpoint Inhibitor–Associated AKI: A Multicenter Study

2020· article· en· W2997561837 sur OpenAlex

Pourquoi ce travail est dans la base

Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.

affAu moins un auteur déclare une institution canadienne dans l'instantané OpenAlex épinglé.

Notice bibliographique

RevueJournal of the American Society of Nephrology · 2020
Typearticle
Langueen
DomaineMedicine
ThématiqueRenal cell carcinoma treatment
Établissements canadiensUniversity of TorontoUniversity Health Network
Organismes subventionnairesNational Institute of Diabetes and Digestive and Kidney DiseasesNational Cancer InstituteNational Heart, Lung, and Blood InstituteAmerican Society of Nephrology
Mots-clésMedicineNivolumabAcute kidney injuryInternal medicineImmune checkpointOncologyImmunotherapyCancer

Résumé

récupéré en direct d'OpenAlex

Significance Statement Kidney toxicity from use of immune checkpoint inhibitors is being recognized as an increasingly frequent complication of treatment. However, existing data on immune checkpoint inhibitor–associated AKI have been limited to small, mostly single-center studies. In this multicenter study of 138 patients with immune checkpoint inhibitor–associated AKI and 276 controls, the authors characterize the clinical features of this complication and identify risk factors associated with its development, clinicopathologic features, and determinants of kidney recovery after an episode. Failure to achieve kidney recovery was associated with worse overall survival, and a minority (23%) of patients who were retreated with immune checkpoint inhibitors had a recurrence of AKI. The study provides insights into immune checkpoint inhibitor–associated AKI, although further study is needed to inform the care of affected patients. Background Despite increasing recognition of the importance of immune checkpoint inhibitor–associated AKI, data on this complication of immunotherapy are sparse. Methods We conducted a multicenter study of 138 patients with immune checkpoint inhibitor–associated AKI, defined as a ≥2-fold increase in serum creatinine or new dialysis requirement directly attributed to an immune checkpoint inhibitor. We also collected data on 276 control patients who received these drugs but did not develop AKI. Results Lower baseline eGFR, proton pump inhibitor use, and combination immune checkpoint inhibitor therapy were each independently associated with an increased risk of immune checkpoint inhibitor–associated AKI. Median (interquartile range) time from immune checkpoint inhibitor initiation to AKI was 14 (6–37) weeks. Most patients had subnephrotic proteinuria, and approximately half had pyuria. Extrarenal immune-related adverse events occurred in 43% of patients; 69% were concurrently receiving a potential tubulointerstitial nephritis–causing medication. Tubulointerstitial nephritis was the dominant lesion in 93% of the 60 patients biopsied. Most patients (86%) were treated with steroids. Complete, partial, or no kidney recovery occurred in 40%, 45%, and 15% of patients, respectively. Concomitant extrarenal immune-related adverse events were associated with worse renal prognosis, whereas concomitant tubulointerstitial nephritis–causing medications and treatment with steroids were each associated with improved renal prognosis. Failure to achieve kidney recovery after immune checkpoint inhibitor–associated AKI was independently associated with higher mortality. Immune checkpoint inhibitor rechallenge occurred in 22% of patients, of whom 23% developed recurrent associated AKI. Conclusions This multicenter study identifies insights into the risk factors, clinical features, histopathologic findings, and renal and overall outcomes in patients with immune checkpoint inhibitor–associated AKI.

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.

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,001
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Observationnel · Signal consensuel: Observationnel
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,054
Score d'incertitude au seuil0,362

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0010,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0010,001
Bibliométrie0,0000,000
Études des sciences et des technologies0,0000,001
Communication savante0,0000,000
Science ouverte0,0000,000
Intégrité de la recherche0,0000,001
Charge utile insuffisante (le modèle a refusé de juger)0,0000,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.

Tête enseignante Opus0,033
Tête enseignante GPT0,329
Écart entre enseignants0,296 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_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écoule