Why the study?
Does serum CK-MB-estimated infarct size correlate with morbidity and mortality in patients with acute myocardial infarction?
Does serum CK-MB-estimated infarct size correlate with morbidity and mortality in patients with acute myocardial infarction?
Infarct size estimated from serum CK-MB correlates significantly with the development of serious complications and mortality after acute myocardial infarction.
CK-MB-estimated infarct size was associated with mortality and complications in AMI; supports prognostic value but leaves open whether it alters management.
The relationship between acute myocardial infarct (AMI) size and morbidity and mortality was estimated in 317 patients followed for one year or until death. Infarct size was estimated from serum creatine kinase (CK)-MB levels measured thrice daily. The incidence of ventricular arrhythmias, congestive heart failure, cardiogenic shock, and the cardiac performance during exercise were studied during hospitalization. Hospital mortality and one-year mortality were registered. A positive correlation was found between serum CK-MB-estimated infarct size and the incidence of ventricular arrhythmias (p less than 0.05). Patients with congestive heart failure and patients with cardiogenic shock had significantly larger infarct size than patients without (p less than 0.05-0.01), although there was a substantial overlap. During exercise test the rise in systolic blood pressure correlated negatively and the rise in heart rate correlated positively to estimated infarct size (p less than 0.01). Both hospital mortality and one-year mortality were significantly related to estimated infarct size (p less than 0.01). Thus the infarct size, as estimated from serum CK-MB, seems to be of importance for development of the most common and serious complications after AMI.
No takes yet. Share an insight, caveat, or question.
Grande et al. (1984) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: