Response to Letter Regarding Article, “The sPLA <sub>2</sub> Inhibition to Decrease Enzyme Release After Percutaneous Coronary Intervention (SPIDER-PCI) Trial”
Bibliographic record
Abstract
Coronary Intervention (SPIDER-PCI) Trial"We thank Dr Krijnen and colleagues for their interest in our sPLA 2 Inhibition to Decrease Enzyme Release after Percutaneous Coronary Intervention (SPIDER-PCI) study, the results of which were not suggestive of any evidence of a protective benefit of varespladib, an inhibitor of secretory phospholipase A 2 (sPLA 2 ), in reducing myocardial injury sustained after elective percutaneous coronary intervention (PCI). 1 The hypothesis that varespladib might reduce myocardial injury associated with PCI arose from observations that nonemergent PCI is associated with a marked increase in blood sPLA 2 levels. 2Krijnen et al suggest that our patient cohort was unsuitable for the study of the hypothesis that sPLA 2 is involved in PCI-related cardiac inflammatory injury.We agree, and this was not our hypothesis.Rather, we set out to study whether or not sPLA 2 inhibition would reduce the myocardial injury frequently observed after PCI in a stable elective PCI population.The observational study of Liu et al 2 cited by Krijnen used a cohort that appears to have been similar to ours.Why the inflammatory response was so different from that observed in the SPIDER-PCI study is an interesting and puzzling question.An important clue may lie in the lipid levels of the 2 cohorts.The mean low-density lipoprotein cholesterol in the varespladib group of the SPIDER-PCI cohort was 65 mg/dL.In contrast, the mean low-density lipoprotein cholesterol of the PCI group in the Liu study was 134 mg/dL, and, although the medical therapy of patients in the study is not reported, it is quite likely that dyslipidemia in many of these patients was untreated.Statin therapy, which most our patients were receiving, may have suppressed the pathways that trigger the baseline and the periprocedural release of sPLA 2 and high-sensitivity C-reactive protein, as well.It is noteworthy that the baseline high-sensitivity C-reactive protein levels in our chronically statin-treated patients were closer to those in the Atorvastatin for Reduction of Myocardial Damage During Angioplasty (ARMYDA) patients after 1 week of therapy with atorvastatin 40 mg daily (2.6 mg/L). 3However, troponin I and creatine kinase-MB were still released at levels that were similar to prior observations in stable PCI cohorts.Thus, at least in this group of elective PCI patients on chronic statin therapy, it appears that there is indeed dissociation between the inflammatory axis, as measured by levels of highsensitivity C-reactive protein and sPLA 2 , and the myocardial injury arising from the intervention.Might the results be different if the effect of varespladib on myocardial injury after PCI were to be tested in patients with acute-phase levels of inflammatory markers such as those presenting with an acute coronary syndrome or acute myocardial infarction, as Krijnen et al suggest?The Fewer Recurrent Acute Coronary Events With Near-Term Cardiovascular Inflammation Suppression-ACS (FRANCIS) Trial randomly allocated 625 patients admitted with an acute coronary syndrome, that being a ST-elevation myocardial infarction in Ͼ40% to varespladib 500 mg daily or placebo in addition to atorvastatin 80 mg daily. 4Varespladib treatment resulted in 78.5% reduction in sPLA 2 levels at 16 weeks and a significant but modest reduction in the level of high-sensitivity C-reactive protein beyond that seen with atorvastatin treatment alone after 24 weeks of therapy.There was no signal of clinical event reduction with varespladib treatment, although the study was not powered to detect differences between groups in clinical events.Thus, whether or not varespladib would reduce myocardial injury when administered acutely to patients undergoing PCI in the setting an acute coronary syndrome is unclear, but, we agree, the question is worthy of further study.
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.003 | 0.022 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.028 | 0.019 |
| Insufficient payload (model declined to judge) | 0.019 | 0.017 |
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".