Health

Did the Department of Defense falsify data to hide injuries?


This story is about what could become one of the biggest cases of medical data fraud. It is based on my conversation with Mathew Crawford, whom I had the pleasure of interviewing for my podcast.

Mathew’s background is in statistics, computational science, and mathematics. In the past, he worked on Wall Street, then focused on education, writing textbooks and helping build educational companies.

Mathew began looking for a large-scale dramatic event before the pandemic was announced. He became worried when, in the immediate aftermath of the repo market meltdown in the fall of 2019, the Federal Reserve lent $4.5 trillion to three banks. (The Fed “quietly disclosed the names of three banks” that received the loans on December 31, 2021.)

Thus, as soon as the irrational and economically exceptional “COVID response” was thrown at us, Mathew became suspicious of the “pandemic clown”.

DoD Convoluted Data Saga

This particular DoD data story began to be published in January 2022, when attorney Thomas Renz presented his whistleblower data at a five-hour hearing hosted by Senator Ron Johnson.

In his Substack post from February 2022, Mathew describes being “shocked to hear Renz in real time” and learns about “DoD accusers (Dr Samuel Sigoloff, Peter Chambers and Theresa Long) or the startling findings from the Defense Health Epidemiology Database (JOIN):

  • Deviation up to ~300%
  • Cancer rates up to ~300%
  • Neurological status up to ~1000%

Renz makes the database publicly downloadable here. “From there, things got complicated. And before we learn, let’s first identify the elephant in the room.

The Elephant in the Room: Summary

After Tom Renz made his earth-shattering announcement, the DoD came out and said that they had a server issue and as a result, the whistleblower’s data was not good.

And since the DoD was hiding behind the unsigned claim of a “server glitch,” Mathew Crawford went ahead and analyzed a set of public but little-known industry reports pulled from the same database of That DoD (DMED).

After reviewing the reports, he found that by the time brave whistleblowers queried the DMED data, the data could have been corrupted twice, using two different methods – potentially masking. vaccine wound in a very difficult way. (We need to look at the original data to know for sure what happened.)

Mathew believes it’s very likely that someone at the DoD noticed elevated levels of illness in the 2021 data – after all, that’s what the whistleblowers saw on the ground – and decided to cover it up it.

He suggested that the main coverup was done by retroactively changing the data in the DMED for previous years (2016 to 2020, done in mid-2021, sometime between May and July 2021, before Tom Renz announced), thus making previous years look worse than they are, in some ways.

But then in addition, the altered database was migrated to a new server, which could make it more difficult to investigate. Theoretically, it’s possible that during the move, there was an actual glitch – or there could have been an intentional glitch to create a lot of confusion and discredit any whistleblower. any in the future.

Mather’s main point is that even if there’s a glitch, that glitch could be on data that’s been forged – and that’s what he’s trying to scream from the rooftops.

And amazingly, if there was indeed a problem during the server migration (around August 2021), it went unnoticed for five months – in the military – despite the fact that the data was DoD used to assess military readiness and also internally by the CDC. No big deal, I guess.

No one looked, and no one noticed for at least five months that previous years’ data had undergone drastic changes! I say, believe in the DoD. They are trustworthy and will never lie to us. Here’s the original timeline, as a direct quote from Mathew:

In January, Renz testified on behalf of the accusers.

A few days later, still in January, the DoD held an offline DMED. The data has been significantly updated and the DoD confirms the glitch story there is no other explanation.

On Feb 14, I discovered the manipulation of DMED data in MSMR. DoD can never expect anyone to go through those old reports and check all past reports to fully summarize the history of DMED data. At this point, only Renz and I know this level of detail, although I’ve only superficially presented what I found to him at the time.

On February 15, the DoD filed an unsigned complaint about a server move that resulted in a glitch and was fined by a judge for not having an expert witness to back up their claim.

On March 11, Renz submitted a 193-page report to Congress that included my one-page affidavit about the possibility of manipulating the DMED. It’s likely that no one at the CDC or the DoD was reading that part at the time.

On March 22, I published my first paper on what I found. The DoD probably didn’t notice.

On April 6, I included MSMR operations in my summary of all the dirty data in my talk during the VRBPAC meeting. It was informed to me that right around that time the 2016 – 2020 data was suddenly offline (the rest of the database seemed to be available) in DMED!

Here’s the general timeline, according to what Mathew told me in the interview (I’ve published a version of this timeline here):

General timeline and diagrams

The Department of Defense maintains a medical database called the DMED. The database records various military medical events. It does not record mortality data.

In addition to keeping DMED private, they also publish a little-known industry journal called “Monthly Medical Supervision Report”. The numbers published in the MSMR are based on the same DoD, DMED databases. The reports are publicly available.

Every year, usually around May, as part of the MSMR, they publish the annual totals for the previous year and for the few years before that. The reports look at different categories of data, based on medical billing codes.

When in 2021 they publish their annual totals, the historical data for the previous years has been changed from before. (For example, 2016 issues published in 2021 suddenly differed from previously published 2016 numbers, etc.) Doing so changed the reference point for the 2021 numbers.

However, contrary to normal data analysis practice, no explanation for the change was offered. See Mathew’s chart below, generated on the MSMR database:

monthly medical supervision report

The 2021 data (which Mathew believes nobody bothers to falsify on a large scale while the data is still ongoing) shows a higher signal for different, disaggregated medical events. coordinate between a variety of medical billing codes.

Curiously, “Bell’s Palsy” is a category that doesn’t show an increase in 2021, which seems like an anomaly compared to data from other parts of the world.

Around August 2021, DoD migrated the DMED database to a new server. Mathew believes that in the process, the data was corrupted a second time, and it is not known whether the additional error layer was added by accident or if it was added to create confusion.

It appears that as a result of the server migration, the numbers from previous years have been downgraded again – but in a way that doesn’t make them identical or close to those previously reported through MSMR.

Meanwhile, unrelated to any of this, some military doctors bravely blew the whistle on the unusual levels of illness they observed among service members, likely due to COVID injection.

In an explosive statement, attorney Tom Renz revealed that he queried whistleblower data from DMED and the data showed a huge increase in health problems in 2021 (See more at the Association of Southeast Asian Nations). Senator Ron Johnson roundtable).

Mathew believes the accusers queried the data after two levels of database corruption had occurred – so the data was essentially garbage and the DoD may have set the trap on purpose – but on At the time, no one knew it – and the courageous whistleblowers thought they were accessing authentic data.

A few days later, the DoD issued a vague, unsigned statement through PolitiFact saying that there had been a server malfunction and therefore the whistleblower’s data was not good.

That statement sparked a heated response. Those who believe in “safe and effective vaccines” believe in the DoD, while those who are “hesitant” say that the DoD is lying about the problem.

But according to Mathew, the server crash argument is a trap because the real fraud most likely happened earlier, in 2021, before the server migrated. The server glitch just adds another layer of confusion.

One notable fact: the “glitch” happened around August 2021 – and for a few months, no one noticed. That, despite the fact that the data has been used to assess military readiness and has also been studied internally by the CDC.

Mathew believes this could be one of the biggest health data frauds of our time.

An added bonus: oddly enough, according to “post-malfunction” data, the US military has no health crisis in 2020:

what happened to the code r

What now?

Mathew hopes that some attorneys file FOIA requests and try to get hold of the original data. This is not an easy task by any imagination. Data can be classified – and according to Mathew, opening it to the public might even require an Act of Congress.

But on the other hand, if the DoD officials are honest – of course they are because they would never lie to us – and if they have published their data in an industry journal, and if the injection is safe, safe and effective, what do they have to hide?

Importantly, Mathew encourages interested parties to review the MSMR data independently and draw their own conclusions. The data is publicly available.

For my part, I feel we should try everything to determine the truth. Our legal system is a bit shaky at this point, but it’s still working – and I hope that more and more people are starting to think from the inside and ask questions. I also hope that qualified attorneys will file those FOIA requests and we’re starting to get somewhere. And yes, we may need a miracle but miracles follow love and courage. Now is the time for love and courage.

Information about the Authors

To find more work by Tessa Lena, be sure to check out her profile, Tessa Fights Robots.





Source link

news7g

News7g: Update the world's latest breaking news online of the day, breaking news, politics, society today, international mainstream news .Updated news 24/7: Entertainment, Sports...at the World everyday world. Hot news, images, video clips that are updated quickly and reliably

Related Articles

Back to top button