Reactivation of Hepatitis B Infection following Allogeneic Bone Marrow Transplantation in a Hepatitis B-Immune Patient: Case Report and Review of the Literature
Bibliographic record
Abstract
BACKGROUND: Reactivation of hepatitis B virus (HBV) infection following allogeneic bone marrow transplantation is a rare phenomenon. METHODS: Reverse seroconversion, defined as the clearance of antibody to hepatitis B surface antigen (HBsAb) and the appearance of hepatitis B surface antigen (HBsAg) in a patient with resolved HBV infection (i.e., a HBsAg-negative, HBsAb-positive, hepatitis B core antibody-positive patient) following receipt of a bone marrow transplant is described. A review of related cases in the literature was undertaken to identify clinical features associated with this phenomenon. RESULTS: We present a case of reactivation of HBV infection in a 47-year-old man after receipt of an allogeneic bone marrow transplant for acute myelogenous leukemia. Before undergoing bone marrow transplantation, the presence of HBsAb and hepatitis B core antibody and the absence of HBsAg indicated clearance of natural HBV infection. The donor was HBsAg and HBsAb negative. Twenty-nine months after bone marrow transplantation, the patient developed transaminitis and evidence of active HBV infection (the patient had test results positive for HBsAg, negative for HBsAb, and positive for HBV DNA). A total of 28 other cases of reverse seroconversion have been described in the literature, 11 of which provided adequate information to be summarized in detail together with the present case. Reactivation of HBV infection following bone marrow transplantation appears to occur almost exclusively in patients who have received marrow from an HBsAb-negative donor and have experienced graft-versus-host disease, the onset of which is associated with tapering of immunosuppressive therapy. CONCLUSIONS: Although HBV reverse seroconversion is an uncommon event, understanding the clinical features associated with the development of HBV reverse seroconversion may provide insight into how such a potentially fatal complication may be avoided.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.002 |
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".