Complications of Bioglue postsurgery for aortic dissections and aortic valve replacement
Bibliographic record
Abstract
AIMS: Bioglue is an adhesive used during cardiovascular surgery to improve hemostasis perioperatively and to strengthen and reinforce vascular anastomoses. It has also been used to 'seal' the false lumen in patients presenting with acute aortic dissections. Herein, we examine the complications of Bioglue, which may lead to redo sternotomy in selected patients. METHODS: A review of pathology records at our institution from 2002 to 2010 found 4 cases of excised aortic tissue and/or aortic valves with previous Bioglue use at initial operation. Excised tissues and valves were examined, looking for the presence of Bioglue, inflammatory cells (acute, chronic, macrophage and giant cells) and micro-organisms. Patient demographics were also reviewed and recorded. RESULTS: We identified four cases of Bioglue use found at redo surgery, after the formation of pseudoaneurysm (n=3) and aortic stenosis (n=1). Mean interval to redo surgery was 2.28 + 0.32 years (range 2-2.6 years). Pseudoaneurysm formation was thought to be caused by an inflammatory reaction to the Bioglue itself in two cases, while one case found no such reaction. One patient with previous aortic valve replacement had large annular abscesses filled with necrotic debris surrounding the prosthesis and pannus found on the sewing cuff, comprised of Bioglue itself. CONCLUSIONS: The mechanisms leading to these complications include mechanical strain, inflammation and tissue necrosis. The judicious use of Bioglue when clinically indicated, and close follow-up of these patients with serial imaging, remain an integral part of avoiding future complications.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".