Socioeconomic differences in the pathways to diagnosis of coronary heart disease: a qualitative study

Abstract

Background

Socioeconomic inequalities in coronary heart disease (CHD)-related morbidity and mortality are well explored. However, less is known about the causes of inequalities in CHD treatment. In this qualitative study, we explored socioeconomic differences in the pathways to diagnosis of CHD.

Methods

The data originated from 38 semi-structured interviews with older CHD patients, aged 59–80 years, conducted at the university hospital in Halle, Germany, between November 2014 and April 2015. We analysed the narratives related to the time before CHD was confirmed by coronary angiography electively or urgently. Transcripts were analysed following inductive qualitative content analysis and we identified socioeconomic differences by comparing and contrasting patients' narratives.

Results

The patients interpreted their symptoms based on expectations, normalization, relief and obtaining help from third parties. For those experiencing chronic CHD symptoms, only patients with low socioeconomic status (SES) waited to seek healthcare until they suffered myocardial infarction. Mainly low-SES patients procrastinated in undergoing diagnostic procedures. We found no socioeconomic differences in the urgent pathway. However, along the elective pathway, only low-SES patients reported receiving assistance from a general practitioner in accessing a cardiologist.

Conclusions

Socioeconomic differences in CHD diagnosis were mainly apparent before patients sought healthcare. These differences were more pronounced when CHD was electively diagnosed due to chronic symptoms rather than urgently diagnosed due to acute symptoms. To address socioeconomic differences, general practitioners should focus on any indication of symptoms and interpretation mentioned by low-SES patients, and coordinate these patients' pathways to diagnosis while emphasizing the seriousness of CHD.

from Health via xlomafota13 on Inoreader http://ift.tt/2hO4fhy
via IFTTT