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.
10 sites have the affected software that is configured with the specific conditions listed in Code Information
App-derived interpretation
Unknownreason.no_named_rule · v1.0.0
When RadSuite is used with IPID (Issuer of Patient ID) as a part of the "Patient Identifier," it is possible in some circumstances that the demographics of one patient will be applied to a study or studies for another patient.
These labels are deterministic app interpretations, not FDA categories.
When RadSuite is used with IPID (Issuer of Patient ID) as a part of the "Patient Identifier," it is possible in some circumstances that the demographics of one patient will be applied to a study or studies for another patient.
Code information
RadSuite Versions: 5.30.8, 5.35.3, 5.35.4, 5.35.5, 8.30.7.3, 8.30.7.4, 8.30.7.5, 8.30.7.7 are affected, BUT ONLY if they are configured with all of the following conditions: (1) Must have IPID enabled; (2) Must use IPID morphers (3) Must Define a Defaultvalue in the IPID Morpher; (4) Must use the Aggregating Morpher; (5) Must not set OverwritelfPresent=false; and (6) Must be on an internal store (this is data that is already present on EA being stored to Radsuite, this excludes direct DICOM stores to the EA).
Distribution pattern
Distribution was made to medical facilities in AL, MI, MO, PA, TN, and TX.
