#DDOD Use Case: Consolidated reporting of medical device recalls

Metadata Updated: September 2, 2019

SUMMARY DDOD use case request for consolidated, consistent reporting of medical device recalls. WHAT IS A USE CASE? A “Use Case” is a request that was made by the user community because there were no available datasets that met their particular needs. If this use case is similar to your needs, we ask that you add your own requirements to the specifications section. The concept of a use case falls within the Demand-Driven Open Data (DDOD) program and gives you a formalized way to identify what data you need. It’s for anyone in industry, research, media, nonprofits or other government agencies. Each request becomes a DDOD use case, so that it can be prioritized and worked on. Use Cases also provide a wealth of insights about existing alternative datasets and tips for interpreting and manipulating data for specific purposes. PURPOSE This use case was requested with the goal of obtaining a "single source of truth" for medical device recalls, rather than trying to reconcile between the two data sources. It needs to:

Provide unique recall ID to link data from these two sources. Provide standardized, consistent product name or registered device key (such as PMA # or 510(k) #)

VALUE The value of the use case is to helps hospitals more effectively catch devices in their inventory that have been recalled and prevent them from buying potentially unsafe ones. It improves outcomes and patient safety by lowering probability of hospitals being unaware of devices have been recalled. USE CASE SPECIFICATIONS [HTML_REMOVED] SOLUTION Information about this use cases is maintained in a wiki: http://hhs.ddod.us/wiki/Use_Case_6:_Consolidated_reporting_of_medical_de... It serves as a knowledge base. USE CASE DISCUSSION FORUM All communications between Data Users, DDOD Administrators and Data Owners are logged as discussions within GitHub issues: https://github.com/demand-driven-open-data/ddod-intake/issues/6 It aims to provide complete transparency into the process and ensure the same message gets to all participants. CASE STATUS Closed via openFDA.gov API, which includes medical device recall information as of September 2015.

Access & Use Information

Public: This dataset is intended for public access and use. License: See this page for license information.

Downloads & Resources

References

http://www.healthdata.gov/dataset/recalls-medical-devices
http://www.healthdata.gov/dataset/radiation-emitting-product-corrective-actions-and-recalls-0

Dates

Metadata Created Date June 19, 2015
Metadata Updated Date September 2, 2019

Metadata Source

Harvested from Healthdata.gov

Additional Metadata

Resource Type Dataset
Metadata Created Date June 19, 2015
Metadata Updated Date September 2, 2019
Publisher U.S. Food and Drug Administration, Department of Health & Human Services
Unique Identifier bbc9fbb6-f473-4db9-9582-0364efd3a88c
Maintainer
David Portnoy
Maintainer Email
Public Access Level public
Bureau Code 009:10
Metadata Context https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld
Metadata Catalog ID https://healthdata.gov/data.json
Schema Version https://project-open-data.cio.gov/v1.1/schema
Catalog Describedby https://project-open-data.cio.gov/v1.1/schema/catalog.json
Data Dictionary https://github.com/demand-driven-open-data/ddod-intake/blob/master/_data/use-case-6-data-dictionary.json
Harvest Object Id 3d4e2d2e-6327-4054-9762-d6b393b8e1d7
Harvest Source Id 15c538b5-31a0-474e-8ba5-c85ee421cb4d
Harvest Source Title Healthdata.gov
License https://opendatacommons.org/licenses/odbl/1.0/
Data Last Modified 2018-11-16
Program Code 009:005
Related Documents http://www.healthdata.gov/dataset/recalls-medical-devices, http://www.healthdata.gov/dataset/radiation-emitting-product-corrective-actions-and-recalls-0
Source Datajson Identifier True
Source Hash 90cd881d55d172b4740788f06e87512a99903712
Source Schema Version 1.1

Didn't find what you're looking for? Suggest a dataset here.