Delivery of cardiac resynchronization therapy via the left inferior phrenic vein: a case report
Bibliographic record
Abstract
BACKGROUND: The successful implantation of cardiac resynchronization therapy (CRT) may be prevented by anatomical variations that preclude the delivery of clinically effective left ventricular (LV) pacing from within the coronary sinus (CS) or its tributaries. Failure of lead delivery, suboptimal LV capture thresholds, or intractable phrenic nerve capture with accompanying diaphragmatic twitch is often encountered. Commonly employed alternative approaches to LV lead delivery, including epicardial, trans-septal, or transapical pacing are associated with significant morbidity. CASE SUMMARY: A 74-year-old man with ischaemic heart disease, prior mitral valve repair, long-standing atrial fibrillation, and severe symptomatic LV systolic dysfunction, underwent single chamber pacemaker upgrade to a CRT defibrillator. It was found not to be possible to place a CS lead during the procedure. Biventricular pacing was accomplished by the delivery of a pacing lead through the left inferior phrenic vein (LIPV). Satisfactory LV capture thresholds were obtained with the avoidance of clinically significant diaphragmatic stimulation. Following implantation, a marked clinical response to treatment was observed with improvement in both heart failure symptoms and LV ejection fraction. DISCUSSION: The LIPV is known to drain into the inferior vena cava in around one-third of examined subjects. In these individuals, LV lead delivery through the LIPV may provide an alternate route for the delivery of resynchronization therapy. This approach to the implantation of CRT may be considered when pacing via the CS or its branches are not achievable.
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.005 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.004 | 0.003 |
| Scholarly communication | 0.003 | 0.004 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.009 | 0.006 |
| Insufficient payload (model declined to judge) | 0.003 | 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".