openFDA Device Enforcement
Report-date coverage
June 20, 2012–July 08, 2026
Known gap: openFDA describes 2004-present coverage, but the current export has no report-date records in this interval.
openFDA Device Recall
event_date_initiated coverage
June 01, 1997–June 30, 2026
Enforcement coverage uses report dates; product initiation dates can precede those bounds. Device-enrichment coverage uses FDA event_date_initiated.
Product dates, classifications, firms, and source wording remain attached to their individual rows.
Opening this dossier never hides products that did not match a prior timeline filter.
In Online Entry (OEx) there are two scenarios where a Test result from one container may file to a Test on another container. In order for this to occur: 1) Site parameter SIT 1,2,1,26 (3,217) [Restrict resulting of tests to owner container (<Y>/N)]=Y. 2) The Tests are ordered on the same accession number and 3) The Test codes are defined to have the same upload code as either replicate or
These labels are deterministic app interpretations, not FDA categories.
In Online Entry (OEx) there are two scenarios where a Test result from one container may file to a Test on another container. In order for this to occur: 1) Site parameter SIT 1,2,1,26 (3,217) [Restrict resulting of tests to owner container (<Y>/N)]=Y. 2) The Tests are ordered on the same accession number and 3) The Test codes are defined to have the same upload code as either replicate or
