Occurrence of phrenic nerve stimulation in cardiac resynchronization therapy patients: the role of left ventricular lead type and placement site
Bibliographic record
Abstract
AIMS: Unwanted phrenic nerve stimulation (PNS) has been reported in ∼1 in 4 patients undergoing left ventricular (LV) pacing. The occurrence of PNS over mid-term follow-up and the significance of PNS are less certain. METHODS AND RESULTS: Data from 1307 patients enrolled in pre-market studies of LV leads manufactured by Medtronic (models 4193 and 4195 unipolar, 4194, 4196, 4296, and 4396 bipolar) were pooled. Left ventricular lead location was recorded at implant using a common classification scheme. Phrenic nerve stimulation symptoms were either spontaneously reported or identified at scheduled follow-up visits. A PNS-related complication was defined as PNS resulting in invasive intervention or the termination of LV pacing. Average follow-up was 14.9 months (range 0.0-46.6). Phrenic nerve stimulation symptoms occurred in 169 patients (12.9%). Phrenic nerve stimulation-related complications occurred in 21 of 1307 patients (1.6%); 16 of 738 (2.2%) in the unipolar lead studies, and 5 of 569 (0.9%) in the bipolar lead studies (P = 0.08). Phrenic nerve stimulation was more frequent at middle-lateral/posterior, and apical LV sites (139/1010) vs. basal-posterior/lateral/anterior, and middle-anterior sites (20/297; P= 0.01). As compared with an anterior LV lead position, a lateral LV pacing site was associated with over a four-fold higher risk of PNS (P= 0.005) and an apical LV pacing site was associated with over six-fold higher risk of PNS (P= 0.001). CONCLUSION: Phrenic nerve stimulation occurred in 13% of patients undergoing LV lead placement and was more common at mid-lateral/posterior, and LV apical sites. Most cases (123/139; 88%) of PNS were mitigated via electrical reprogramming, without the need for invasive intervention.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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".