0

I am trying to use the openfda API to get a view of the data in the front end.

This is an example of a front end search: https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfMAUDE/detail.cfm?mdrfoi__id=2094110&pc=OCE

mdr_report_key: 2094110

this is the API query I'm trying:

https://api.fda.gov/device/event.json?search=mdr_report_key:%222094110%22&limit=30

Examples of data that is missing from the API:

1) Frontend - Brand Name: EPICEL (CULTURED EPIDERMAL AUTOGRAFTS) GRAFT

2) Frontend - Device Sequence Number : 1

3) Frontend - 1 Device Was Involved in the Event

Essentially any device or report data (description of event, I believe normally under mdr_text:[]) is missing from the search does not seem to show up in the API query, even though its the same mdr_report_key.

It looks like the front end joins together "Followups" to the "Initial Report" data. I was wondering how this is being joined on and how I can combine the data to something that makes sense? Should I ignore all Report_type: "follow up" records?

Thanks in advance!

  • Hello, I'm Jack with the openFDA team. I'm reviewing this now and will get back to you with an answer shortly. Thank you! – Jack Finch Apr 16 at 15:28
  • Thanks Jack - if I understand correctly this means that the OpenFDA API and the accessdata front end search are served by different databases (or the API exposes data that is transformed in a different way)? I am wondering why the same mdr_report_key can yield different results from the API and from the accessdata front end. If you could confirm that for me it would be extremely helpful, thanks in advance – user2364697 Apr 20 at 17:01
0

I'm Jack with the openFDA team. The missing fields you're referencing are normally found within the device object in the openFDA API endpoint for Device Event data. The data source for this object is the downloadable files labeled foidev which can be found here. In this case, these source files do not have an entry for this mdr_report_key, which is why the device object is missing. Apologies for the inconvenience!

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.