Key result
In a 10-year study of 31 patients, asymmetric apical hypertrophy occurred predominantly in men over 40 years of age and was associated with infrequent complications and a generally good prognosis.
Observational (n=31)
Asymmetric apical hypertrophy is a distinct morphological variant of hypertrophic cardiomyopathy with specific electrocardiographic and echocardiographic features and a generally benign prognosis.
Answers are grounded in this paper and cite their sources.
Supports benign prognosis in asymmetric apical hypertrophy; leaves open confirmation in larger prospective cohorts.
This paper reports 10 years experience of 31 patients with asymmetric apical hypertrophy, in whom left ventricular hypertrophy involved the apex exclusively and giant T wave inversion in the left precordial leads was the characteristic finding. This type of hypertrophic cardiomyopathy was observed predominantly in men over 40 years of age. Family history was negative and patients usually had no complaints. Left ventricular hypertrophy was evident by physical examination as in other forms of hypertrophic cardiomyopathy, but a systolic murmur was faint or absent and the second heart sound was frequently split. Electrocardiographic signs may fluctuate, and occasionally progression or regression occurs. Echocardiography including the two-dimensional method was essential for the diagnosis and left ventriculography was helpful for confirmation. To date complications have been infrequent and the prognosis seems good. The relation of asymmetric apical hypertrophy to other forms of hypertrophic cardiomyopathy is under investigation.
No takes yet. Share an insight, caveat, or question.
Sakamoto et al. (1986) conducted an observational in Asymmetric apical hypertrophy (n=31). In a 10-year study of 31 patients, asymmetric apical hypertrophy occurred predominantly in men over 40 years of age and was associated with infrequent complications and a generally good prognosis.
Synapse has enriched 10 related papers. Consider them for comparative context: