Notice bibliographique
Résumé
RhD antigens are highly antigenic and anti-D antibodies are known to cause haemolytic disease of the foetus and newborn and acute haemolytic transfusion reactions. However, the importance of the D antigen in haematopoietic progenitor cell (HPC) transplantation has been less well defined. In this issue of Blood Transfusion Cid et al.1 report a review of outcomes following RhD mismatched and incompatible HPC transplantation that provides greater insight regarding clinical outcomes and possible implications for transfusion practices. They conclude that D antigen-incompatible HPC transplantation is not likely to result in serious clinical consequences although the persistence of anti-D antibodies may be associated with worse outcomes in some settings. More information is needed to understand how transplant centres adapt their transfusion practices in RhD incompatible and mismatched transplants. Importantly, there may be certain settings in which RhD mismatches warrant special consideration in the context of allogeneic HPC transplantation. Prior to the introduction of Rh immunoglobulin as effective prevention, haemolytic disease of the foetus and newborn was an important cause of neonatal mortality and morbidity. Typically women are allo-immunised through pregnancy or transfusion. The work of Cid et al.1 suggests that HPC transplantation may be another means of immunisation with up to 10% of RhD-mismatched transplants resulting in development of anti-D. In a woman requiring HPC transplant whose fertility is likely to be preserved following the transplant or when implantation of frozen embryos following transplantation is likely to lead to a viable pregnancy2, RhD mismatching may be a relevant consideration affecting donor selection, in the fortunate context in which more than one HLA-matched donor is available. It is unlikely that RhD mismatching would have a negative affect on ability of transfusion services to supply safe products for transfusion. Although highly allo-immunised patients can pose a significant challenge to transfusion services for patients undergoing transplantation, approximately 10% of blood donors are RhD-negative and providing antigen-negative packed red blood cell units for transfusion to a patient who is D-immunised should not be a problem for most transfusion services unless patients return to remote locations where access to blood products is more limited. Consequently the presence of anti-D prior to transplantation or its development in the post-transplant period should not be a key consideration in planning transplants. The ongoing presence of anti-D or the re-emergence of anti-D antibodies in a patient immunised prior to transfusion may, however, be a harbinger of other adverse events unrelated to transfusion issues but that are related to persistent host immunity. Cid et al.1 (see Table III) cite four cases in which a transplant recipient mounted a response to the donor’s RhD-positive red cells. This finding indicates mixed chimerism which can be associated with late graft failure and/or relapse. Given the difficulty of finding compatible donors for patients requiring HPC transplantation, it is unlikely that RhD antigen differences between donor and recipient will be a major consideration in donor selection3. However, improved understanding of post-transplant immunisation and what it tells us about host immunity may enable important improvements in our ability to offer safer and more effective options for HPC transplantation and for transfusions to such patients.
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,001 | 0,004 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,000 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,000 | 0,001 |
| Communication savante | 0,002 | 0,001 |
| Science ouverte | 0,001 | 0,001 |
| Intégrité de la recherche | 0,003 | 0,003 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,045 | 0,019 |
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 ».