Skip to content

Sherlock 9770352YRecalls & reported problems

Bard Access Systems, Inc. · Remanufactured Sherlock 3CG Sensor · Class 2

All models of Sherlock (9)

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

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

Summary

The FDA's MAUDE database contains 3 adverse event reports that list this exact device (DI 00801741163074), received between Apr 3, 2025 and Aug 28, 2025 — classified as 1 injury, 2 malfunctions.

The most frequently reported specific device problem is “Data Problem” (2 reports).

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 16, 2026.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 1 reportsMay 2025: 0 reportsJun 2025: 1 reportsJul 2025: 0 reportsAug 2025: 1 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 0 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520261
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Data Problem2
  • Break1
  • Defective Component1

Patient problems

  • No Clinical Signs, Symptoms or Conditions2
  • Arrhythmia1

Recent adverse event reports

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

  • InjuryAug 28, 2025Defective Component; Data Problem; Defective Component; Data Problem

    IT WAS REPORTED THAT A PICC WAS PLACED IN THE RIGHT ARM WITH A 40 CM TRIM FOR TPN ON (B)(6), USING THE 3CG/SHERLOCK FOR CONFIRMATION SINCE THE PATIENT DIDN'T APPEAR TO HAVE A CARDIAC HISTORY THAT COULD INTERFERE WITH CONFIRMATION. IMPLANTING NURSE HAD WHAT SEEMED TO BE A GOOD ECG IMAGE BUT FOUND OUT ON CXR FROM SUBSEQUENT DAYS THAT THE PICC WAS IN FACT DEEP. ON 8/8 THE TEAM CONTACTED US TRYING TO FIND OUT IF THE PICC COULD BE PLAYING A ROLE IN PATIENTS NEW SVT. SINCE WE THOUGHT THIS WAS A LEGITIMATE POSSIBILITY, AND IN AN EFFORT TO REMOVE VARIABLES, A NEW PICC WAS PLACED IN THE LEFT ARM WITH A 44 CM TRIM. RECEIVED AN ECG RHYTHM WITH NEGATIVE DEFLECTION AT -1 (TAPER FULLY INSERTED TO SKIN) AND RETRACTED TO 1 CM OUT WITH THE DEFLECTION DISAPPEARING AND KEEPING LARGE P-WAVE PEAKS AS EXPECTED FOR A WELL POSITIONED LINE. TO FULLY ENSURE POSITION, AN CXR WAS PERFORMED AND THIS NEW LINE WAS ALSO FAR TOO DEEP. THE CONCLUSION WE DREW IS THAT THE PATIENT HAS ABNORMAL BRACHIOCEPHALIC VEIN ANATOMY WHICH WAS THROWING OFF OUR MEASUREMENTS AND CREATING SHORTENED PATHWAYS TO THE SVC. THE CONCERNING PART IS THAT THE 3CG VERIFIED BOTH LINES AS WELL POSITIONED, EVEN THOUGH THE OVER-WIRE EXCHANGE BASE

    Patient problems: Arrhythmia

    MAUDE report 22913757 ↗
  • MalfunctionJun 4, 2025Break; Break

    IT WAS REPORTED THAT WIRES ARE EXPOSED ON THE CORD. NO OTHER INFORMATION PROVIDED, AT THIS TIME.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 22143454 ↗
  • MalfunctionApr 3, 2025Data Problem; Data Problem

    IT WAS REPORTED THAT THE SENSOR IS NO LONGER DETECTING INTERNAL/EXTERNAL WAVE FORM. NO OTHER INFORMATION PROVIDED, AT THIS TIME.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 21767680 ↗

Other Catheter, intravascular, therapeutic, long-term greater than 30 days devices

All Catheter, intravascular, therapeutic, long-term greater than 30 days devices →

Sources and updates

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