VAERS BadBatch, MatchYourBatch,ToxicLot?

The various apps to give you insight into VAERS lots#

From the main home page of the worlds best VAERS Interactive Dashboard VaersAware.com the public can now access three of the main VAERS lot# look-ups existing today. I wanted to honor my new friends at matchyourbatch.org because their work is excellent! A few of us have been collaborating with the creators of matchyourbatch about the possibility of getting some toggling or filter capabilities between untouched/unedited data from the CDC's WONDER System and “cleansed” data from custom built scripts or algorithms from the likes of Gary Hawkins aka “The Hawk” over at deepdots.substack.com, or from me or both! My opening image above shows a great example of raw unedited lot# counts versus truer lot# counts when typos and such have been corrected.

Sure the original accusation was technically correct when someone said, “100% of deaths are coming from 5% of the lot#’s…!”. But upon close inspection you can see how a lot# is written fifty different ways. Here is one example of lot EN6201:

There is much work philosophy/logic that goes into cleaning up lot#’s and it’s always a work in progress, but at least I try and give you all the truth and best visibility upfront for you. One other small big issue I have VAERS in general is the double, triple, and quadruple counting of adverse events per report. Meaning on one report a victim could be reported as landing in the ER, then being admitted into the hospital, with a life threatening event that ultimately left them permanently disabled. It’s good that all this info is documented in the report, but bad in these lot look-up sites and bad in the VAERS AE’s summary view seen here:

You can see at face value as many as ~1,739,390-1,558,671= 180,719 reports have at least a multiple AE designation, hence the percentage is 111.59%. This is somewhat deceptive because you need to remember the lowest level “None of above” (NOA) event level has ZERO AE boxes checked off. What’s more, there are very serious adverse events in the lowest level even deaths that are never counted, but that’s a whole other article. Now knowing this factoid the ratio of reports around ~548K reports from Office Visits up to Death carry those extra or multiple AE’s designations! So now let’s examine what Craig Paardekooper’s badbatch.com site looks like for the same lot EN6201 example I used above:

Right off the bat I included the drop down menu you will get searching for EN6201, what’s the odds all five of those options realistically are ALL batch EN6201? They all are! Let’s not beat around the bush or guild the lily! If I could put a note in Craig’s suggestion box, it would be to allow selection of multiple batches for scenarios like this that basically will happen for almost every single lot, if you do not clean-up the typos in the data modeling phase. However, this isn’t even the point I’m trying to make, the point I’m trying to make is the question about how many people landed in Life Threatening, Disabilities, and Other Events also died? Saying it a different way there are some of those 250 dead victims that are also counted in the other event levels, except NOA. What’s up with Hospitalizations and Birth Defects and why are they lumped into Other Events? Hospitalization and Birth Defects are considered SAE’s. You’ll never see the crazy amount of Hospitalizations recorded in Michigan compared to all other states but oh well, I’m sure Craig has his reasons for stashing away hospitalizations and birth defects…. probably to save space. Here is some of the answers I posed about double counts within batch EN6201:

As you can see there were 9 with Life Threats but died, 2 with Perm Disability but died, and 151 with hospitalizations but died. Kind of confusing isn’t it?

What if in a dashboard we assigned just the highest level adverse event per report, therefore eliminating the double counts and the need for disclaimers and explanations? 1.5M reports equals 1.5M adverse events. Well abracadabra and badda bing, here you go!

My dashboard will give you so much more… this is just the starter page. I need to call out my current small vulnerability, you can see it in the 196 deaths versus 250 deaths and this particular lot is one of the biggest lot discrepancies I have! I’m working on the fix now but it comes down to only capturing the first line item per report, and secondly how a lot is recorded like lot# EL9264/EN6201. Sometimes the submitter themselves comingle multiple doses on one line item. In the example of EL9264/EN6201 I arbitrarily select one or the other, and/or try to keep the most recent lot# if I can determine the expiration dates. The large discrepancy I’m having with this particular lot has more to do with me purging the multiple line items. It wasn’t a big issue early on, but as people have drank the kool-aid more than a few times, more and more reports came in with multiple line items (multiple vaxxes). It’s not a show stopper, and from my end it’s fixable. Sometimes the VAERSAWARE stats will show more deaths per lot than what’s shown on medalerts or bad batch, etc.. and that’s because the cleansing and correction of typos, hyphens and special characters has revealed more deaths for that particular lot. For all these reasons we should embrace multiple lot# look-up sites and say welcome to the new kids at matchyourbatch.org! The coolest VAERS word cloud site around…

Oh by the way, I haven’t even explained my Toxic Lot RVU but it’s the nuts!! Filter the dashboard properly and you can even see toxic lots coming on the horizon based on vax and lot expiration dates. If these evil clowns keep rolling out new elixirs for the baffled Kool-Aid drinking masses, we will be ready to expose every carnival trick the gargoyles have. God Bless