Background: Secondary care studies showed that a recorded allergy to beta-lactams could not be confirmed by valid allergy testing in >85% of cases. In daily practice, recorded beta-lactam allergies probably cause prescription of secondary choice antibiotics. This overrating of beta-lactam allergy hampers appropriate use of narrow spectrum antibiotic and generates unnecessary cost and bacterial resistance.
Objective: To assess registration and over diagnosis of allergies against beta-lactams in Dutch primary care.
Methods: A retrospective cohort study in 8288 primary care subjects was performed. Patients with recorded allergy were identified through International Classification for Primary Care coding. Signs and symptoms of the recorded allergic reaction and patient's characteristics were extracted from patient's files and patients were sent a questionnaire. The probability of allergy was based on a composite reference standard that was scored by two authors independently.
Results: One hundred sixty-three subjects had a recorded allergy (2.0%). In 51.5% of cases, no characteristics of the recorded allergic reaction were reported in patients' medical files. Based on our composite reference standard, allergy was excluded in 19 subjects (11.7%). Risk factors for allergy registration were female gender, age <4 years, and the comorbidities-asthma, allergies and skin disorders.
Conclusions: The prevalence of recorded allergy against beta-lactam antibiotics in a large Dutch primary care centre was 2%. Due to lack of registration of accompanying signs and symptoms of the recorded allergy, this diagnosis is uncertain in most patients. Better documentation and classification by a screening algorithm of future possible allergic reactions to beta-lactams are needed in primary care.
Keywords: Beta-lactams; The Netherlands.; hypersensitivity; prevalence; primary health care; probability; risk factors.
© The Author 2015. Published by Oxford University Press. All rights reserved. For permissions, please e-mail: firstname.lastname@example.org.