Tuesday, March 20, 2018

FDA fixes another error with its MAUDE database

I feel like a broken record, but I am going to talk about another error in the MAUDE database.

For those playing along at home, the FDA tracks medical device malfunctions and adverse events using a database known as MAUDE. They are nice enough to make the entire database available for download. You can download the data files here. Last week, I noticed that one of the data files was missing reports from January 2018.

  • I emailed them informing them of the error.
  • They emailed me back explaining that everything was fine.
  • I emailed them back, explaining that it wasn't.
  • They emailed me back (see pic below) and fixed the issue.

I don't know how/why these errors keep cropping up, but it's the 3rd error I've found in MAUDE over the past year.

Labels: , , , , , ,

Friday, March 9, 2018

FDA Updates their MAUDE Production Database LIVE and on-the-fly

The FDA uses a data-base/search engine known as MAUDE to monitor the safety and malfunctions of FDA approved medical devices.

A few days ago, I downloaded the FDA's MAUDE "raw" data-set (located here). I do this a few times per month, and today I noticed that at least part of the data-set is corrupt. I won't go into the gory details, but some of the 2018 data seems to have been mistakenly vaporized from the current data-set.

While, I was trying to figure out what was corrupted, I ran a test search using the FDA's MAUDE search-engine (located here).

I searched for the word veritas and I got ZERO results.

Now, I KNOW there are reports in MAUDE involving the veritas collagen matrix because I've run the search before, so when I got ZERO results, I knew that not only were the "raw" data-files corrupt, but something was also corrupt with the FDA's live search-engine.

As I was writing my email to the FDA, I started to tell them that their error was NOT ONLY with the "raw" data-set, but their search-engine was corrupted, too!

Then I decided that I should take a screenshot of my search results just in case they thought I was crazy.

So, I re-ran the veritas search.

But this time, when I ran it, I got 62 RESULTS! See pic below. I started to think, "Maybe I am going crazy. Maybe I punched in the wrong search term, or maybe I selected an incorrect parameter."

But then, I ran the search again (2 minutes later), and I got 64 RESULTS!

Approximately 1 hour later, and we are up to 145 results.

So...just in case this is confusing....

  • The FDA is correcting errors on its production database.
  • In the middle of the day.
  • On a Friday.
  • And they're doing all of this while the search-engine is LIVE.
  • I can tell because I'm watching it happen in real time.

To the database and software-dev people out there, that is some cowboy stuff.

Labels: , , , , , , , ,

Thursday, September 21, 2017

FDA Repairs its MAUDE Database

I have posted several times this year about an error in the FDA MAUDE database (see here, here and here for previous posts).

To summarize, the FDA's MAUDE database captures reports of malfunctions and injuries associated with medical devices. The MAUDE database is supposed to capture patient outcome information like:

  • Did the patient die during/as a result of the device malfunction?
  • Was the patient hospitalized due to the malfunction?
  • Was the patient disabled?
  • etc.

About 2 years ago, the FDA's MAUDE database stopped reporting patient outcomes and replaced these outcomes with a cryptic code of "8.".

As you might imagine, this is a pretty serious omission. It seems kind of important to know what happened to the patients when a device malfunctions.

I contacted the FDA earlier this year and informed them of the error.

Today, I received an email indicating that the database has been fixed and the outcomes are back!

FDA was also kind enough to explain what "8." meant:

Labels: , , , , , , , , ,

Wednesday, August 30, 2017

Update # 2 on "8." MAUDE Database

I've previously written (here and here) about an error in the FDA medical device adverse events database known as MAUDE. The error prevents the database from reporting patient outcomes (death, hospitalization, etc.).

I received correspondence from someone at the FDA last week indicating that they may have found a fix (see screenshot of email).

However, so far, they have not implemented the fix. You can see this in two ways:

First, if you download the patient outcome file from the FDA website and open it up, you see a series of "8"s where the outcome data should be (see pic).

Second, you can query the MAUDE database using the OpenFDA platform and count the distribution of patient outcomes in the year:
As of this moment, if you click on this link, you will see the distribution of patient outcomes in the MAUDE database from the beginning of 2016 until yesterday. You can see from the pic below that there are no outcomes, only variations on "8."

Labels: , , , ,

Monday, August 7, 2017

Update on "8." and MAUDE Patient Outcomes

I have previously posted about the FDA's adverse events database for medical devices (known as MAUDE). In past years, the MAUDE database had captured patient outcome information (whether the patient died, was hospitalized, suffered some form of disability, etc.).

The database no longer reports patient outcomes (it stopped doing so in late 2015). Instead, the database field that should contain outcome data contains the cryptic entry of "8." (the number 8 with a period). I recently contacted the FDA, asking why MAUDE no longer provided patient outcome data. I received the following responses (thus far). I've edited out identifying information (and superfluous text).

This is from an email dated 28 July 2017. It's moderately encouraging. In particular, it's encouraging to know that the patient outcome information  is _still_ captured, and it will probably be added back to the database once they determine what the error is.

I will post updates as they develop.

 Dear Dr. Danese,
Thank you for contacting the Division of Industry and Consumer Education (DICE) at FDA's Center for Devices and Radiological Health (CDRH) xxxxxxx@fda.hhs.gov e-mail account. As far as I am aware, patient outcome information is still collected on so adverse event reporting forms. So, at this time I am not clear on why this information is not included in the data sets for 2015 and beyond. I am in the process of researching the issue and contacting the medical device reporting staff. I apologize for the delay but hope to have an answer for you next week. .... Sincerely, xxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx Division of Industry and Consumer Education Office of Communication and Education Center for Devices and Radiological Health U.S. Food and Drug Administration
I then received a follow-up email on 4 August (Friday)
Dear Dr. Danese, 
Thank you for your patience while I looked into your inquiry. I have spoken with a member of the Information Analysis Branch and it seems some of the patient outcome information may have been inadvertently excluded from the downloadable zip files. xxxxxx has kindly agreed to look into this issue to figure out what happened and how the problem may be corrected. Please feel free to contact xxxx directly. xxxxx name is xxxxxxxxxxxxxx and xxxxx email address is xxxxxxxx@fda.hhs.gov. I hope you have a pleasant weekend. Sincerely, 
Division of Industry and Consumer Education Office of Communication and Education Center for Devices and Radiological Health U.S. Food and Drug Administration
And then this email from the Information Analysis Branch (dated 7 August)
Paul, I was notified of the issue by xxxxxx on Friday, and we are currently investigating. We will get back to you when we know more. Thank you. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Information Analysis Branch Division of Post Market Surveillance Office of Surveillance and Biometrics Center for Devices and Radiological HealthUS Food & Drug Administration 

Labels: , , , , , , ,

Tuesday, May 30, 2017

Clustering of Drugs by Side Effect Profile

Others (here, herehere + others) have clustered medications based on side effect profiles. Everyone has done it a little differently.

In this post, I perform a similar type of clustering using slightly different methods (details forthcoming). I'm not providing m̶u̶c̶h̶ any of the methodological details in this post, but I just wanted to show a pretty plot with nice clusters.

Drugs were clustered using t-SNE (here and here), which is a method that is remarkably good at taking high-dimensional data (in this case, thousands of different side effects) and clustering it into 2-dimensions while maintaining much of the "nearest neighbor" information that was present at high dimensions.

You can see the 2-D "cluster plot" (after t-SNE transformation) below.

  • Hover over the data points to see drug names.
  • I colored the data points by running k-means on the 2-D data (very quick and dirty and probably not the best approach).
  • Still, you can see pretty good functional clustering. For example: 
    • the dark green points on the left edge of the plot are almost all related to cholesterol and lipid pharmacotherapy. If you zoom in, you will also find daptomycin (an anti-bacterial), but it clusters there b/c it is associated with reports of myopathy and rhabdomyolysis (adverse events that are somewhat characteristic of the "statins").
    • red and blue points on the left edge are primarily involved w/ Type 2 diabetes.

Labels: , , , , , , , , ,

Friday, March 17, 2017

Trump submitting adverse event reports?

Found this "classic" adverse event report submitted to the FDA in 1994. 76 year old male patient taking Sinemet and Xanax with a report of the following issues:

  • asthenia
  • coordination abnormal
  • dysphagia
  • med error

The kicker is in the comments section: 'Pharmacist "jokingly" told patient to take the medication with Vaseline, [which] the patient did.'

  • First, I'm not sure why jokingly is in quotes. Was the reporter quoting the pharmacist, in which case the quotation marks emphasize a literal and sincere description of the communication between pharmacist and patient? Or are the quotation marks meant in the ironic-2017-Sean-Spicer-fake-news sense, in which case the pharmacist comes across as malevolent? Tough call.

  • Second, the report labels the Sinemet as the suspect medication! I'm going to go out on a limb and speculate that the Vaseline itself was causing the dysphagia, but don't quote me on that.

Labels: , , , , , , , , ,