VAERS reports by lot
Merck Varicella/Shingles lot 0300X: VAERS reports
29 VAERS reports list lot 0300X as a Merck Varicella/Shingles vaccine, received between 2008-06-17 and 2010-03-24. Data: VAERS public files through 31 December 2024 (site extract 2026-07-04).
Read this first. VAERS accepts reports from anyone, and a report does not establish that the vaccine caused the event. A lot's report count mostly reflects how many doses it contained, when it was used and who received it; no administered-dose counts are published for this lot, so counts are not rates and cannot rank lots against each other. Lot numbers in VAERS reports are typed by reporters and are sometimes wrong.
29
Reports
34%
Marked serious
0
With a death outcome
10
Months with reports
Symptom categories in these reports
A report can mention several categories, so the counts add up to more than the number of reports.
| Category | Count | % |
|---|---|---|
| Injection-site / Local reaction | 54 | 52% |
| Dermatological (non-injection-site) | 18 | 17% |
| General / Systemic (non-local) | 17 | 17% |
| Musculoskeletal | 6 | 6% |
| Cardiac / Cardiovascular | 5 | 5% |
| Neurological | 2 | 2% |
| Allergic / Anaphylactic | 1 | 1% |
Where reports came from
U.S. state of the reporter, where given (top 12).
| Illinois | 5 |
| Tennessee | 4 |
| Iowa | 3 |
| Pennsylvania | 2 |
| Colorado | 2 |
| Oregon | 1 |
| Indiana | 1 |
| Wisconsin | 1 |
| Mississippi | 1 |
| Minnesota | 1 |
| Florida | 1 |
| Vermont | 1 |
Reports by month received
| 2008-06 | 6 | |
| 2008-07 | 2 | |
| 2008-08 | 1 | |
| 2008-09 | 4 | |
| 2008-10 | 9 | |
| 2008-11 | 2 | |
| 2008-12 | 2 | |
| 2009-01 | 1 | |
| 2009-07 | 1 | |
| 2010-03 | 1 |
Products recorded with this lot
- Shingrix / varicella-zoster — Merck (29 reports)
Manufacturer and product as reported in VAERS. Reports listing the lot under more than one product are counted once.
Related
Source: VAERS public data (CDC/FDA), grouped by manufacturer and lot by the Open Source Medicine Foundation; extract 2026-07-04 16:35 UTC. Not medical advice. Report errors via contact.