Discover more from Rounding the Earth Newsletter
Defining Away Vaccine Safety Signals 8: DMED Story Simplified, Plus Updates
The Vaccine Wars Part XXXIII
"Simplicity is the ultimate sophistication." -Leonardo da Vinci
Friends have encouraged me to write up a simplified version of the story of what I found researching the Defense Medical Epidemiological Database (DMED) story. I believe this is because explaining the story in one breath makes it sound more complicated than it is. Since the goal is simplicity, I may rewrite some parts of this article (whereas I usually just fix up my typos).
The best way to understand the DMED saga is to forget what you've heard about it. Wipe your mind clean of the details and start over. The data results shared in January were likely incorrect, and the Department of Defense (DoD) comeback appears to be an ugly deception. This will be easier to understand after I explain what I believe did happen as clearly and as simply as possible.
The Simple Facts
The DoD is part of the CDC's vaccine safety work group. Yet, strangely, after the rollout of the experimental injectable products, we weren't reading data tables from the DoD's Defense Medical Surveillance System (DMSS) or the DMED database that draws from it.
Is that because there were safety signals that the CDC or DoD wanted to hide?
What I discovered while working on the project is the following:
At Health.mil there is an archive of Medical Surveillance Monthly Reports (MSMR).
Once a year in May, the MSMR includes summaries of ambulatory and hospitalization data from DMSS/DMED, organized by major classifications of medical billing codes. Each summary includes three prior (staggered) years of data. For instance, the primary data table in the May 2021 MSMR looks like this:
Going category by category, the 2016 and 2018 data in the table above is substantially higher than the reported data from the May 2019 MSMR.
The changes, which average 13.5% per category per year comparison, bring the 2016-2020 data (assuming these five years were all altered in the same way) much more in line with the numeracy of ambulatory illness and injury reports in 2021. There is no asterisk or explanation, which would never happen in an important database. I searched back over a decade and found no other large manipulations. The change in ambulatory reports was more than two orders of magnitude larger than small updates that are typical of the data due to simple issues like late records filed or re-dated. The most parsimonious explanation is that somebody with control over DMSS/DMED fraudulently manipulated the data in order to mask vaccine-associated harms.
So, what are the actual increases in rates of illness?
Unfortunately, we cannot know without an investigation of the DMSS/DMED data before and after the alterations that showed up in the 2021 MSMR. But there are still some alarming signals, and some of those, such as a jump in cases of myocarditis, should have been immediately apparent in January, 2021.
What the whistleblowers later discovered in their queries, and then reported via Renz, was likely an artifact of the manipulation process, which I will explain further. We should be thankful that they opened this can of worms for further examination. They sounded an alarm that drew attention to the DoD's behavior with respect to the data. But before we get into that, here is a visual of the data manipulations by category. Each pair of bars at the bottom was data as published in the May 2019 MSMR, and the pair of bars in the back are what was published in the May 2021 MSMR.
How the Data Manipulation Likely Evolved From Start to Finish
Maybe I'm wrong about this, though given the way the DoD has responded so far, I doubt it. This is how I think mass health data fraud took place with respect to DMSS/DMED…
The CDC and DoD were likely aware of vaccine safety signals all the way back in January, 2021. For the first few months of 2021, they just ignored it. When the CDC tells us they've been sitting on COVID data, I suspect that includes the DMSS/DMED data. If they have included any of it in any reports at all, which the DoD's inclusion in their VaST work group suggests, please post me the links. I haven't seen it (that's not to say they might not have used some of it, somewhere).
As the May 2021 MSMR publication data approached, I think that whoever was responsible for the database took the DMSS data, then partitioned the database sometime in April. They compared the 2016-2020 data to 2021 to generate scale factors for various ICD-10 codes, which were then applied to each partitioned piece of the 2016-2020 data. But the post-partition data (dates) were somehow not properly connected back to DMSS/DMED.
There was a server migration in August for DMED. As of mid-February, the DoD claims the glitch was introduced at that time. While this is possible, I prefer either my theory that the data was corrupted in April, or that the corruption was a combination of the April partitioning and August server migration. I also worry that the server migration was a way to wipe fingerprints of engineered data fraud.
It is noteworthy that the DoD did not mention this server migration to Politifact.
It is further noteworthy that their court statement was unsigned (below), meaning that nobody at all was willing to take responsibility for the statement.
And it is insane that the CDC either wasn't examining any of this data (since they didn't recognize a glitch present for many months), or willfully ignored it.
In January, Renz testified on behalf of the whistleblowers.
Several days later, still in January, the DoD took DMED offline. The data was updated dramatically, and the DoD claimed the glitch story with no other explanation.
On February 14, I spot the ahistorical DMED data manipulation in the MSMR. The DoD likely never expected anyone to look through those old reports and check all the past reports to full summarize the DMED data history. At this point, only Renz and I know this level of detail, though I had only superficially laid out what I found to him at that point.
On February 15, the DoD makes the unsigned claim of the server migration introducing the glitch, and gets admonished by a judge for not having an expert witness backing their claims.
March 11, Renz sends a 193-page report to Congress that includes my one-page affidavit about the likely DMED manipulation. It is likely that nobody at the CDC or DoD read that part at the time.
March 22, I published my first article about what I found. The DoD probably isn't paying attention.
On April 6, I included the MSMR manipulations in my summary of all the dirty data in my talk during the VRBPAC meeting. It has been reported to me that right around that time, the 2016-2020 data suddenly goes offline again (the rest of the database seems available) in DMED!
The problem with a story like the DMED saga is that partisans quickly arranged their version of the story. Many people are hard to budge once they've invested in a chosen reality. My version, which is backed by a more complete set of facts, challenges everyone's views at once, so there is more cognitive dissonance than usual. The vaccine pushers wanted the story to end with, "It was just a glitch you stupid anti-vaxxer," and those fighting the mandates were happy to be armed with 300% and 1000% increases (that don't often sway those in the middle, frankly, and certainly aren't necessary to suggest that there are serious issues with the vaccines).
That's where we are. I think it's FOIA time. Whether you think I've fully guessed at the remaining details, there was clearly a large data change that calls into question everyone managing the use of DMSS/DMED or responsible for using it as part of the CDC's VaST work group. That the DoD coasted on, "It's just a glitch," without anyone taking responsibility or laying out a complete set of information about the data during 2021 suggests a high likelihood that something very bad took place. That should be enough to stop the vaccine mandates until a full investigation is complete. At least, it would be in a sane world.