/openfda/device/events

POST /api/openfda/device/events

Price: 1 credit

Get an FDA MAUDE device adverse-event report by its report number

How to use it

Get an FDA MAUDE (Manufacturer and User Facility Device Experience) adverse-event report by its report number. Returns the event type and location, key dates, the devices involved (brand, generic and manufacturer names, model, product code, implant flag and openfda block), the patients (age, sex, outcomes) and the MDR narrative texts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — MAUDE device event report number (examples: "2243621-1992-00036", "10"; minLength: 1)

Response

• @type string (default: "OpenfdaDeviceEvent")
• report_number string required
• mdr_report_key string nullable
• event_type string nullable
• event_location string nullable
• date_of_event_at integer nullable
• date_received_at integer nullable
• date_report_at integer nullable
• date_added_at integer nullable
• date_changed_at integer nullable
• date_report_to_fda_at integer nullable
• product_problem_flag boolean nullable
• adverse_event_flag boolean nullable
• report_source_code string nullable
• source_type array (default: [])
• type_of_report array (default: [])
• reporter_occupation_code string nullable
• manufacturer_name string nullable
• pma_pmn_number string nullable
• single_use_flag boolean nullable
• number_devices_in_event string nullable
• number_patients_in_event string nullable
• product_problems array (default: [])
• remedial_action array (default: [])
• devices array (default: [])
  • @type string (default: "OpenfdaDeviceEventDevice")
  • brand_name string nullable
  • generic_name string nullable
  • manufacturer_name string nullable
  • model_number string nullable
  • catalog_number string nullable
  • lot_number string nullable
  • product_code string nullable
  • implant_flag boolean nullable
  • device_operator string nullable
  • device_availability string nullable
  • openfda object nullable
    • @type string (default: "OpenfdaBlock")
    • application_number array (default: [])
    • brand_name array (default: [])
    • generic_name array (default: [])
    • manufacturer_name array (default: [])
    • product_ndc array (default: [])
    • package_ndc array (default: [])
    • product_type array (default: [])
    • route array (default: [])
    • substance_name array (default: [])
    • rxcui array (default: [])
    • unii array (default: [])
    • spl_id array (default: [])
    • spl_set_id array (default: [])
    • nui array (default: [])
    • pharm_class_cs array (default: [])
    • pharm_class_epc array (default: [])
    • pharm_class_moa array (default: [])
    • pharm_class_pe array (default: [])
    • is_original_packager array (default: [])
    • device_class string nullable
    • device_name string nullable
    • medical_specialty_description string nullable
    • regulation_number string nullable
    • fei_number array (default: [])
    • registration_number array (default: [])
    • k_number array (default: [])
    • pma_number array (default: [])
• patients array (default: [])
  • @type string (default: "OpenfdaDeviceEventPatient")
  • sequence_number string nullable
  • age string nullable
  • sex string nullable
  • weight string nullable
  • outcomes array (default: [])
  • treatments array (default: [])
• mdr_texts array (default: [])
  • @type string (default: "OpenfdaDeviceEventText")
  • text_type_code string nullable
  • text string required
  • patient_sequence_number string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Device event not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.