Headache during cryoballoon ablation for atrial fibrillation
Bibliographic record
Abstract
AIMS: Headache has been reported to occur during cryoballoon ablation for atrial fibrillation (AF). No study has systematically analysed this phenomenon. METHODS AND RESULTS: Twenty consecutive patients with symptomatic AF underwent cryoballoon ablation without sedation. Headache was evaluated before, during, and after the first cryoapplication in every pulmonary vein (PV) using a visual representation of a head for location of the headache, a numerical rating scale (NRS) for measuring pain intensity and the short-form McGill pain questionnaire (MPQ) for qualitative analysis of pain. The order in which the PVs were ablated was randomized. Sixteen (80%) patients perceived mainly frontal headache during cryoablation. The overall NRS scores were significantly higher during (5.1 ± 1.7), compared with before (2.7 ± 1.4), and after (3.5 ± 2.2) a cryoapplication (P < 0.05). The NRS score was significantly higher during ablation of the first PV. The intensity of the perceived headache was not related to the temperature reached 150 s after initiation of a cryoapplication (P = 0.81). Of the MPQ, three sensory adjectives and one affective adjective averaged between scores 1 and 2, representing mild-to-moderate severity of pain. CONCLUSION: The majority of patients treated by balloon cryoablation experienced headache during a cryoapplication. There was no correlation between the temperature reached during a cryoballoon freeze and the intensity of the headache. Cryoballoon ablation of the first PV was significantly more painful than the remaining PVs.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 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.000 | 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 teacher head, 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".