Intraoperative dialysis during liver transplantation with citrate dialysate
Bibliographic record
Abstract
Liver transplantation for acutely ill patients with fulminant liver failure carries high intraoperative and immediate postoperative risks. These are increased with the presence of concomitant acute kidney injury (AKI) and intraoperative dialysis is sometimes required to allow the transplant to proceed. The derangements in the procoagulant and anticoagulant pathways during fulminant liver failure can lead to difficulties with anticoagulation during dialysis, especially when continued in the operating room. Systemic anticoagulation is unsafe and regional citrate anticoagulation in the absence of a functional liver carries the risk of citrate toxicity. Citrate dialysate, a new dialysate with citric acid can be used for anticoagulation in patients who cannot tolerate heparin or regional citrate. We report a case of a 40-year-old female with acetaminophen-induced fulminant liver failure with associated AKI who underwent intraoperative dialytic support during liver transplantation anticoagulated with citrate dialysate during the entire procedure. The patient tolerated the procedure well without any signs of citrate toxicity and maintained adequate anticoagulation for patency of the dialysis circuit. Citrate dialysate is a safe alternative for intradialytic support of liver transplantation in fulminant liver failure.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".