Abstract 17543: The Chicken or the Eggs? Examining the Causal Relationship Between the Development of Atrioventricular Valve Regurgitation and Ventricular Dysfunction in Patients With Functionally Single-Ventricle Physiology
Bibliographic record
Abstract
Introduction: Development of atrioventricular valve regurgitation (AVVR) with or without ventricular dysfunction (VD) often occurs during the first 6 months of life and has a significant impact on outcomes for single-ventricle patients. Yet, it is not well known whether AVVR causes VD or vice versa. Thus, we sought to identify the timing and causal relationship between AVVR and VD. Methods: Among 156 consecutive single-ventricle patients who had staged palliation (2005- 2012), 28 who had AVV repair at the time of stage II (n=24, 86%) or inter-stage (n=4, 14%) were reviewed. Diagnosis included HLHS in 17 (61%) patients, tricuspid atresia in 2 (7%), and others in 9 (32%). Ventricular morphology was left-dominant in 6 (21%) patients and right-dominant in 22 (79%). AVV morphology included mitral in 6 (21%) patients, tricuspid in 18 (64%), and common in 4 (14%). Serial echocardiograms were reviewed to identify the timing of development of AVVR and/or VD. Results: After stage I palliation, ventricular end-diastolic dimension (VEDD) z-score significantly increased from 4.01 to 5.69 (p<0.01) AVVR (Figure). By the time of stage II palliation, VEDD further increased and subsequent AVV annular dilation occurred, resulting in 23 patients with significant AVVR. None of the patients, however, had significant VD before stage II palliation/AVV repair, but 9 patients developed significant VD after AVV repair. Conclusions: Ventricular dilation occurred immediately after stage I palliation and continued until stage II palliation. Secondary annular dilation occurred inter-stage and this further triggered the development of AVVR. Tangible ventricular dysfunction was not seen before AVV repair, however, important ventricular dysfunction was unmasked after volume unloading surgery. Heart failure management and early intervention to significant AVVR may reduce the incidence of ventricular dysfunction following AVV repair.
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.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.003 | 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".