Skip to content

ActivaPatch IontoGo 4.0 001-50Recalls & reported problems

Activatek Inc. · ActivaPatch IontoGo 4.0 carton with 6 pouches. 4 hour iontophoresis delivery. · Class 2

Data updated Oct 18, 2026 from official FDA records · Editorial policy

Adverse event reports
1
Deaths reported
0
Injuries reported
1
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 00859975005202), received between May 11, 2017 and May 11, 2017 — classified as 1 injury.

The most frequently reported specific device problem is “Insufficient Device Problem Information” (1 report).

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.

Most reported problems

Device problems

  • Insufficient Device Problem Information1

Patient problems

  • Partial thickness (Second Degree) Burn1
  • Wound Infection1

Recent adverse event reports

The 1 most recent of 1 reports, in the reporter's own words as published by the FDA.

  • InjuryMay 11, 2017Insufficient Device Problem Information; Insufficient Device Problem Information

    PER CUSTOMER, "UTILIZED IONTO PATCH COUPLED WITH DEXAMETHASONE AT THE END OF TREATMENT. SKIN CLEANED WITH ALCOHOL SWAB AND PATCH APPLIED WITHOUT ANY NEED FOR TAPING, ADHERED WELL. PT INSTRUCTED TO LEAVE PATCH ON 4 HRS. SHE NOTED BURNS AFTER REMOVAL." ALSO, PATIENT WAS "INSTRUCTED TO CLEAN BURNS (B)(6) 2017 AND APPLY NEOSPORIN. PATIENT FOLLOWED UP WITH PCP TUESDAY AND IS BEING TREATED FOR INFECTION WITH ANTIBIOTICS."

    Patient problems: Partial thickness (Second Degree) Burn; Wound Infection

    MAUDE report 6562011 ↗

Other Device, Iontophoresis, Other Uses devices

All Device, Iontophoresis, Other Uses devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page