Display Settings:

Format

Send to:

Choose Destination
See comment in PubMed Commons below
J Infect Dis. 2009 Jul 1;200(1):99-106. doi: 10.1086/599364.

Epidemiological evidence for serotype-independent acquired immunity to pneumococcal carriage.

Author information

  • 1National Public Health Institute, Department of Vaccines, Helsinki, Finland. simo.granat@helsinki.fi

Abstract

BACKGROUND:

Asymptomatic nasopharyngeal carriage is the main reservoir for transmission of Streptococcus pneumoniae. The rate of both carriage and pneumococcal disease decreases with age. To what extent these changes are the result of developing natural immunity is currently a subject of debate.

OBJECTIVE:

To study the hypothesis that previous carriage induces serotype-independent protective immunity to new colonization.

METHODS:

We compared the rates of pneumococcal acquisition for children with different previous carriage histories. We identified 435 episodes of carriage during the first year of life in follow-up data for 99 Bangladeshi children. Cox regression analysis was adjusted for serotype-specific exposure within the family and other confounding factors.

RESULTS:

Previous pneumococcal carriage was associated with serotype-independent protection from subsequent acquisition (hazard ratio, 0.60 [95% confidence interval, 0.39-0.90]), whereas recent serotype-specific exposure within the family was associated with an 8-fold increase in the rate of acquisition for that serotype.

CONCLUSION:

Our findings are consistent with the hypothesis that serotype-independent protective immunity is stimulated in young children by previous pneumococcal carriage and reduces the rate of new colonization. This immunity has the potential to modulate the development of carriage, irrespective of the colonizing serotype, and to do so starting early in infancy.

PMID:
19469705
[PubMed - indexed for MEDLINE]
Free full text
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Icon for HighWire
    Loading ...
    Write to the Help Desk