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.
There is an issue that could cause the Telligence System Gateway II, NGGTWY2 H, to stop communicating to the hallway devices connected to it. When this occurs, the dome lights connected to the Gateway II Ports A and B will start flashing, indicating that they are no longer communicating to the Gateway II. If this occurs, device failures that WOULD otherwise be annunciated WILL NOT be indicated at staff consoles that are configured to display failures.
These labels are deterministic app interpretations, not FDA categories.
There is an issue that could cause the Telligence System Gateway II, NGGTWY2 H, to stop communicating to the hallway devices connected to it. When this occurs, the dome lights connected to the Gateway II Ports A and B will start flashing, indicating that they are no longer communicating to the Gateway II. If this occurs, device failures that WOULD otherwise be annunciated WILL NOT be indicated at staff consoles that are configured to display failures.
Code information
Version 5.0 (Build 5.0.4)
Distribution pattern
AL, CA, CO, GA, IN, KY, LA, ME, MI, MO, MN, MS, NE, NV, OH, PA, RI, TX UT, VA, WI
