Show Summary Details
Page of

Predicting the development of childhood asthma 

Predicting the development of childhood asthma
Chapter:
Predicting the development of childhood asthma
Author(s):

Dennis Ownby

DOI:
10.1093/med/9780199651559.003.0080
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2016. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 26 June 2019

Castro-Rodríguez et al. used longitudinal data from the Tucson Children’s Respiratory Study to develop two indices for the prediction of asthma. A ‘stringent’ index included frequent wheezing during the first 3 years of life and either one major risk factor (parental history of asthma or eczema) or two of three minor risk factors (eosinophilia, wheezing without colds, and allergic rhinitis). A ‘loose’ index was based on any wheezing during the first 3 years of life plus the same combination of risk factors as for the stringent index. The authors found that the stringent index had an acceptable positive predictive value and a high specificity, but low sensitivity. The loose index had a much higher sensitivity but lower specificity and positive predictive values. The negative predictive value at all ages was very high for both indices. The authors conclude that the indices provide a reasonably accurate method of predicting subsequent development of asthma in young children with wheeze, using data that can be easily collected in clinical practice.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.