Postpacemaker Implant Pericarditis: Incidence and Outcomes with Active‐Fixation Leads
Bibliographic record
Abstract
Pericarditis has been noted as a potential complication of pacemaker implantation. This study evaluated the risk of developing pericarditis following pacemaker implantation with active-fixation atrial leads. Included were 1,021 consecutive patients (mean age 73.4+/-0.4 years, range 16-101 years; 45.2% women) undergoing new pacemaker system implantation between 1991 and 1999 who were reviewed for the complication of pericarditis. The incidence and outcomes of postimplantation pericarditis in patients receiving active-fixation atrial leads were compared to those not receiving these leads. Of 79 patients who received active-fixation atrial leads, 4 (5%) developed pericarditis postpacemaker implantation. Of 942 patients with passive-fixation atrial leads or no atrial lead (i.e., a ventricular lead only), none developed pericarditis postoperatively (P < 0.001). Of patients receiving active-fixation ventricular leads only (n = 97), none developed pericarditis. No complications were apparent at the time of implantation in patients who developed pericarditis. Pleuritic chest pain developed between 1 and 28 hours postoperatively. Three patients had pericardial rubs without clinical or echocardiographic evidence of tamponade. They were treated conservatively with acetylsalicylic acid or ibuprofen and their symptoms resolved without sequelae in 1-8 days. One patient (without pericardial rub) died due to cardiac tamponade on postoperative day 6. Postmortem examination revealed hemorrhagic pericarditis with no gross evidence of lead perforation. Pericarditis complicates pacemaker implantation in significantly more patients who receive active-fixation atrial leads. It may be precipitated byperforation of the atrial lead screw through the thin atrial wall. Patients developing postoperative pericarditis should befollowed closely due to the risk of cardiac tamponade.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| 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".