Crash With

Pickup Truck

Highest Injury Severity Alleged

Minor W/O Hospitalization

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear

SV Precrash Speed (MPH)

1

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

Phoenix Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 6:08 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was traveling northbound on [XXX] in the rightmost lane when it slowed for a queue of traffic at the intersection with [XXX]. As the Waymo AV was slowing, a pickup truck traveling northbound on [XXX], partially in the rightmost lane and partially in the second from the right lane, approached the Waymo AV from behind and the front right of the pickup truck made contact with the rear left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The passenger in the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Right

SV Precrash Speed (MPH)

28

CP Pre-Crash Movement

Changing Lanes

CP Contact Area

Front

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 2:20 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling southwestbound on [XXX] in the left lane. An SUV exited the parking lot at [XXX] onto the right lane of southwestbound [XXX] in front of and to the right of the Waymo AV and proceeded to cross the dashed white lane line and enter the Waymo AV's lane of travel. The Waymo AV began braking and maneuvered to the left, and the front left side of the SUV made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Other Fixed Object

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Bottom

SV Precrash Speed (MPH)

5

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Parking Lot

Weather

Clear

Investigating Agency

Redwood City Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 12:07 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Redwood City, California was in a collision involving a curb and later a speed bump in a parking lot at [XXX]. The Waymo AV was traveling northeastbound on [XXX] in the parking lot at [XXX] when it initiated a U-turn over a curb partitioning parking stalls. While proceeding over the dividing curb, the undercarriage of the Waymo AV made contact with the curb and the left side rail trim of the Waymo AV partially detached. After the Waymo AV completed the U-turn, the Waymo AV traveled southwestbound on [XXX], turned right onto northwestbound [XXX], and parked for a passenger pick-up. After remaining stopped for approximately five minutes, the passenger pick-up was cancelled and the Waymo AV traveled northwestbound on [XXX] for a short distance and then proceeded over a rubber speed bump. As the Waymo AV traveled over the rubber speed bump, the partially detached left side rail trim of the Waymo AV caught on the rubber speed bump. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV and the speed bump sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Other, see Narrative

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Making Left Turn

SV Contact Area

Front

SV Precrash Speed (MPH)

5

CP Pre-Crash Movement

Other, see Narrative

CP Contact Area

Unknown

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Parking Lot

Weather

Cloudy

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 2:56 PM PT a Waymo Autonomous Vehicle (Waymo AV') operating in Daly City, California was in a collision involving a movable traffic barrier in a parking lot at [XXX]. The Waymo AV was stopped facing west in a parking lotat [XXX] in a queue of traffic. As traffic ahead advanced, the Waymo AV proceeded to make a left turn to travel southbound within the parking lot and the front left side of the Waymo AV made contact with the movable traffic barrier that was blocking off a section of the parking lot. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Heavy Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Passing

SV Contact Area

Front Left

SV Precrash Speed (MPH)

1

CP Pre-Crash Movement

Parked

CP Contact Area

Rear

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 4:14 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a heavy truck with a flatbed trailer on [XXX] near [XXX]. The Waymo AV was traveling eastbound on [XXX] behind a heavy truck with an attached flatbed trailer when the heavy truck slowed to a stop and parked at the curb on the south side of [XXX] near a stop sign at the intersection with [XXX]. The Waymo AV slowed to a stop to yield to the parked heavy truck, which was partially in the Waymo AV's lane of travel. The Waymo AV proceeded to maneuver around the left side of the heavy truck and the front right side of the Waymo AV made contact with the rear left side of the flatbed of the heavy truck. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Pickup Truck

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Front Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 5:12 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing west in the third to the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a pickup truck traveling westbound on [XXX] approached the Waymo AV from behind and the front of the pickup truck made contact with the rear of the stationary Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

First Responder Vehicle

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Rear

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Proceeding Straight

CP Contact Area

Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 2:55 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an ambulance on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] with vehicles parked on both sides when it maneuvered towards a driveway opening and came to a stop to yield to an ambulance, which did not have lights or sirens activated, traveling southbound on [XXX]. As the ambulance passed the stationary Waymo AV, the left side of the ambulance made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

Passenger Car

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Stopped

SV Contact Area

Front Right

SV Precrash Speed (MPH)

0

CP Pre-Crash Movement

Backing

CP Contact Area

Rear Left

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

None

Make

TOYOTA

Model

Highlander

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

A Zoox vehicle (Vehicle 1) in autonomous mode was traveling eastbound on [XXX] past [XXX] in San Francisco when it began to slow gradually for a nearly stopped passenger car (Vehicle 2) ahead in the same lane. The driver of Vehicle 2 then began reversing without using turn signals. The Zoox vehicle braked to a stop, and its operator disengaged autonomy, while vehicle 2 continued to reverse, steering left, seemingly attempting to pull into a parking spot in the curb lane adjacent to the stopped Zoox vehicle. During this maneuver, the right rear corner of Vehicle 2 swiped the left front corner of the Zoox vehicle. The Zoox vehicle sustained no damage, while Vehicle 2 incurred minor damage. No injuries were reported, and law enforcement was not notified.

Crash With

SUV

Highest Injury Severity Alleged

Minor W/O Hospitalization

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Front Left

SV Precrash Speed (MPH)

9

CP Pre-Crash Movement

Parked

CP Contact Area

Rear

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Cloudy

Investigating Agency

San Francisco Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 3:14 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling westbound on [XXX] in autonomous mode when it approached a portion of the roadway with vehicles parked at the curb on the north side. A van that was traveling eastbound on [XXX] began crossing into the path of the Waymo AV. The Waymo AV began slowing and maneuvering to the right as the van approached, and the test driver transitioned the Waymo AV to manual mode. The test driver then maneuvered the Waymo AV further to the right, and the front right side of the Waymo AV made contact with the rear left side of an SUV parked at the curb on the north side of [XXX]. At the time of the impact, the Waymo AV's Level 4 ADS was not engaged and a test driver was operating the Waymo AV in manual mode. Both vehicles sustained damage. The driver of the Waymo AV alleged a minor injury. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Crash With

SUV

Highest Injury Severity Alleged

Property Damage. No Injured Reported

SV Pre-Crash Movement

Proceeding Straight

SV Contact Area

Rear

SV Precrash Speed (MPH)

7

CP Pre-Crash Movement

Stopped

CP Contact Area

Right

Within ODD?

Yes

Automation System Engaged?

ADS

Roadway Type

Street

Weather

Clear

Investigating Agency

Tempe Police Department

Make

JAGUAR

Model

I-PACE

SV is the subject vehicle — the one whose operator filed the report. CP is the crash partner, the other party. Contact area is where each was struck. NHTSA requires a report for any crash involving the driving system regardless of fault.

On October [XXX], 2025 at 11:57 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Tempe, Arizona was in a collision involving a SUV on [XXX] at [XXX]. The Waymo AV was stopped facing east in the fourth to the right lane on [XXX] in a queue of traffic for a red light at the intersection with [XXX]. An SUV was stopped facing east in the adjacent designated left turn lane to the left of the Waymo AV. As the light turned green and the Waymo AV began to proceed forward, a passenger in the SUV opened the front right side door, and the open front right side door of the SUV made contact with the rear left side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A SINGLE POSITION LATERAL USING EGPS AND AIRO. L3-S1 FIXATION WITH L3-4 L4-5 LATERAL FUSION. THERE WERE HIGH SKIVE WARNINGS ON R L4 SCREW INSERTION. THE SCREW PLACED SLIGHTLY SUPERIOR AND LATERAL TO PLAN. THE SURGEON ATTEMPTED TO PLACE SCREW MULTIPLE TIMES AND EACH ATTEMPT GAVE HIGH SKIVE WARNINGS DESPITE HS DRILL AND SIDE CUTTING DRILL FOLLOWING TRAJECTORY. IT WAS NOT TAPPED. THERE WERE NO SURVEILLANCE WARNINGS. IT WAS THEIR FIRST CASE WITH EGPS 6.1 SOFTWARE USING RELINE SCREWS. THE R L5 SCREW HAD SIMILAR ISSUE AND WAS FINALLY PLACED OVER K-WIRE. (AWL - K-WIRE - NON-NAVIGATED DRIVER) ON AIRO SCAN REVIEW THE R L4 SCREW WAS PLACED SLIGHTLY SUPERIOR AND LATERAL TO PLAN. SCREW WAS REMOVED AND NOT REPLACED. THE PATIENT SHOWED NO ADVERSE EFFECTS FROM MISPLACED SCREW.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED PANCREATODUODENECTOMY PROCEDURE, IT WAS OBSERVED THAT THE RUBBER COATING AT THE TIP OF THE SYNCHROSEAL INSTRUMENT HAD PEELED OFF AFTER THE TISSUE WAS CLAMPED. CONSEQUENTLY, A FRAGMENT FELL INSIDE THE PATIENT BUT WAS IMMEDIATELY RETRIEVED DURING THE SAME PROCEDURE. THE SYNCHROSEAL INSTRUMENT WAS REPLACED WITH A BACKUP, AND THE PROCEDURE WAS SUCCESSFULLY COMPLETED ROBOTICALLY, WITHOUT FURTHER COMPLICATIONS.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED HIATAL HERNIA-PARAESOPHAGEAL PROCEDURE, THE TIP OF THE HARMONIC ACE INSTRUMENT BROKE OFF, RESULTING IN A FRAGMENT FALLING INSIDE THE PATIENT. THE INSTRUMENT WAS INSPECTED BEFORE USE AND NO UNUSUAL OBSERVATIONS WERE NOTED. THE INSTRUMENT WAS USED FOR HIATAL DISSECTION WHEN THE ISSUE OCCURRED; THERE WAS NO INSTRUMENT COLLISION. THE FRAGMENT WAS SUCCESSFULLY RETRIEVED WITHIN THE SAME PROCEDURE UNDER DIRECT VISUALIZATION, AND CONFIRMATION OF REMOVAL WAS MADE. THE PROCEDURE WAS COMPLETED AS PLANNED WITHOUT ANY ADDITIONAL ADVERSE IMPACT ON THE PATIENT. NO X-RAY WAS PERFORMED. THE CAUSE OF THE BREAKAGE REMAINS UNKNOWN.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED DISTAL GASTRECTOMY SURGICAL PROCEDURE, WHEN CHANGING FORCEPS ON ARM, THE BLACK VALVE PART OF THE UNIVERSAL SEAL BROKE AND FELL INTO THE BODY. THE FALLEN PART WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE ACCESSORY WAS INSPECTED PRIOR TO USE, AND NO DAMAGE WAS NOTED. WHILE PERFORMING TISSUE MOBILIZATION, BLACK FRAGMENTS WERE FOUND. THE BLACK FRAGMENTS OBSERVED WERE FRAGMENTS THAT FELL OF THE VALVE FROM UNIVERSAL SEAL. IT IS UNKNOWN WHAT THE SURGEON BELIEVED WAS THE CAUSE OF THE FRAGMENTS FALLING INTO THE PATIENT. THE ACCESSORY WAS USED FOR ABOUT TWO HOURS. IT IS UNKNOWN IF THE FRAGMENTS FELL INSIDE THE PATIENT DURING AN INSTRUMENT TIP, OR ACCESSORY COLLISION. THE FRAGMENTS WERE RETRIEVED WITH RAPALO FORCEPS. IT WAS CONFIRMED THAT ALL FRAGMENTS WERE RETRIEVED AND MATCHED WITH THE DAMAGED AREA. NO ADDITIONAL SURGICAL PROCEDURE WAS REQUIRED TO REMOVE THE FRAGMENTS. NO POST OPERATIVE TESTS LIKE AN X-RAY ULTRASOUND WERE PERFORMED TO CHECK FOR REMAINING FRAGMENTS. PROCEDURE WAS COMPLETED ROBOTICA

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY BECAME LOOSE AND FELL INTO THE PATIENT'S BODY. THE ACCESSORY WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: PRIOR TO USE, BOTH THE INSTRUMENT AND THE MCS TIP COVER ACCESSORY WERE INSPECTED AND FOUND TO BE IN NORMAL CONDITION WITH NO DAMAGE OBSERVED. DURING THE PROCEDURE, THE MCS TIP COVER ACCESSORY FELL INSIDE THE PATIENT WHILE THE SURGICAL TASK OF INSTRUMENT EXCHANGE¿SPECIFICALLY SWITCHING TO A LARGE NEEDLE DRIVER¿WAS BEING PERFORMED. THE ACCESSORY WAS SUBSEQUENTLY RETRIEVED USING THE ASSISTANT PORT (12MM). THE SURGEON BELIEVES THAT THE ACCESSORY SLIPPED OFF OR BROKE DUE TO A DEFECTIVE PRODUCT. THE MONOPOLAR CURVED SCISSORS (MCS) INSTRUMENT HAD BEEN IN USE FOR OVER 60 MINUTES AT THE TIME OF THE EVENT. NO ISSUES WITH THE FUNCTIONALITY OF THE MCS INSTRUMENT WERE NOTICED DURING THE PROCEDURE, NOR WAS THERE ANY COLLISION WITH OTHER INSTRUMENTS. THE MCS TIP COVER ACCESSORY APPEARED TO BE PROPERLY INSTALLED DURING SURGERY, W

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: CITATION: SEIF, HASSAN, ET AL. ¿A RETROSPECTIVE COHORT STUDY COMPARING ROBOT-ASSISTED AND CONVENTIONAL FLUOROSCOPY-GUIDED PEDICLE SCREW PLACEMENT.¿ JOURNAL OF CLINICAL MEDICINE, VOL. 14, NO. 19, 26 SEPT. 2025, PP. 1¿14, HTTPS://DOI.ORG/10.3390/JCM14196831. BACKGROUND/OBJECTIVES: PEDICLE SCREW PLACEMENT IS CRUCIAL FOR RESTORING STABILITY. EMERGING ROBOT-ASSISTED TECHNOLOGIES MAY OFFER ENHANCED PRECISION AND REDUCED RADIATION EXPOSURE. THIS STUDY AIMED TO COMPARE THE ACCURACY AND CLINICAL OUTCOMES OF ROBOT-ASSISTED VERSUS CONVENTIONAL FLUOROSCOPY-GUIDED PEDICLE SCREW PLACEMENTS. METHODS: THIS RETROSPECTIVE COHORT STUDY INCLUDED 218 PATIENTS UNDERGOING PEDICLE SCREW PLACEMENT AT A SINGLE SPINE CENTER BETWEEN 2019 AND 2023. OF THESE, 105 PATIENTS UNDERWENT ROBOT-ASSISTED SURGERY USING THE MAZOR X¿ STEALTH EDITION (MEDTRONIC, MINNEAPOLIS, MN, USA), AND 113 UNDERWENT CONVENTIONAL FLUOROSCOPY-GUIDED SURGERY. THE PRIMARY OUTCOME WAS SCREW PLACEMENT ACCURACY (GRADE 0 = OPTIMAL, GRADES 1¿3 = SUBOPTIMAL, ACCORDING TO THE GERTZBEIN¿ROBBINS CLASSIFICATION). SECONDARY OUTCOMES INCLUDED ESTIMATED BLOOD LOSS (EBL), RADIATION EXPOSURE, LENGTH OF HOSPITAL STAY (LOS), CLINICAL OUTCOME ACCORDING TO TH

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE BLADE WAS FOUND BROKEN ON THE HARMONIC ACE INSTRUMENT. A FRAGMENT FELL INTO A PATIENT AND WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DR. (B)(6) USED THE EXCELSIUS ROBOT (INTRA-OP WORKFLOW) FOR A T11-L1 POSTERIOR LATERAL FUSION. IT IS TO BE NOTED HE ONLY PLACED PEDICLE SCREWS AT T11AND L1 SKIPPING T12 DUE TO A TUMOR SURROUNDING THE T12 VERTEBRAL BODY. DR. (B)(6) DECIDED TO PERFORM HIS DECOMPRESSION THROUGH A POSTERIOR MIDLINE INCISION PRIOR TO PLACING PEDICLE SCREWS BECAUSE HE WANTED TO KNOW HOW FAR THE TUMOR HAD SPREAD. DR. (B)(6) WANTED TO USE THE DRB AND SURVEILLANCE MARKER AND PLACED THEM IN THE PSIS AFTER DECOMPRESSION. AFTER SCREWS WERE PLACED AND ANOTHER CT SCAN WAS PERFORMED VIA E3D THE PEDICLE SCREWS ON THE PATIENT'S RIGHT SIDE WERE MEDIAL OF THE PLANNED TRAJECTORY. LEFT PEDICLE SCREWS WERE IN THE PROPER TRAJECTORY. SURVEILLANCE SHOWED THAT THE DRB HAD NOT MOVED DURING THE CASE. DR. HAMILTON REMOVED THE RIGHT SCREWS AND IMPLANTED THEM FREEHAND. HE ADVISED HE DID NOT SEE ANY DURAL LEAKS AND LATER TOLD US THE PATIENT WAS DOING WELL.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING THE REGISTRATION PROCESS, HD INTRAOPERATIVE 3D SPIN WAS USED FOR REGISTRATION. AFTER THE SPIN WAS COMPLETED, AN XRAY GENERATOR FAILURE POP UP WAS OBSERVED. THE SCAN ACQUIRED WAS UNUSABLE, WHITED OUT AND GRAINY. THE SURGEON ABANDONED E3D AND ROBOT FOR THE DURATION OF THE CASE. ADDITIONALLY, AUTO REGISTRATION FAILED AND SCAN DID NOT PUSH OVER TO ROBOT AUTOMATICALLY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN UNSPECIFIED DA VINCI-ASSISTED SURGICAL PROCEDURE, A SMALL PIECE OF BLACK RUBBER WAS INCIDENTALLY FOUND INSIDE THE PATIENT. THE CUSTOMER REMOVED THE PIECE DURING THE SAME SURGICAL PROCEDURE AND DETERMINED THAT THE FRAGMENT WAS PART OF A UNIVERSAL SEAL. THE PATIENT'S ABDOMINAL CAVITY WAS SEARCHED PRIOR TO CLOSURE. THE PROCEDURE WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) HAS ATTEMPTED TO GATHER ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING AN UNSPECIFIED DA VINCI-ASSISTED SURGICAL PROCEDURE, THE SINGLE PORT (SP) MONOPOLAR SCISSORS TIP ACCESSORY FELL OFF INTO THE PATIENT AND HAD TO BE REMOVED. IT IS UNKNOWN IF THE FRAGMENT WAS FULLY RECOVERED OR WHAT INTERVENTION, RESOLUTION, AND EFFECT THIS HAD ON THE PATIENT.

ROSA Robotic Surgery — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT FOLLOWING DEEP ELECTRODE IMPLANTATION, POSTOPERATIVE CT DEMONSTRATED A SUBARACHNOID HEMORRHAGE. THE SURGERY WAS COMPLETED USING THE UNIT. PREOPERATIVE PLANNING REPORTEDLY SHOWED NO OBVIOUS VASCULAR INTERFERENCE, AND THE CAUSE WAS UNKNOWN. THE SURGEON COMMENTED THAT THE HEMORRHAGE MAY HAVE BEEN RELATED TO PLACEMENT OF AN ELECTRODE TOWARD THE LEFT AMYGDALA AND POSSIBLE TRACTION ON THE SYLVIAN FISSURE DURING TRACT CREATION. THE PATIENT HAD NO DECREASE IN CONSCIOUSNESS AND WAS MANAGED WITH BLOOD PRESSURE CONTROL AND OBSERVATION WITHOUT DRUG ADMINISTRATION. A REPEAT CT PERFORMED APPROXIMATELY 4 HOURS POSTOPERATIVELY DEMONSTRATED NO HEMORRHAGE EXPANSION, AND A SUBSEQUENT PROGRESS CHECK APPROXIMATELY 2 DAYS LATER AGAIN NOTED NO EXPANSION WITH THE PATIENT IN GOOD HEALTH. AN ANGIOGRAM WAS PERFORMED APPROXIMATELY 3 DAYS POSTOPERATIVELY, AND THE PLAN WAS TO REMOVE THE ELECTRODE IF NO ANEURYSM WAS IDENTIFIED. THE PATIENT REMAINED IN GOOD HEALTH WITH NO DECREASE IN CONSCIOUSNESS, AND NO HEMORRHAGE EXPANSION WAS OBSERVED ON SERIAL CT EVALUATIONS. ATTEMPTS HAVE BEEN MADE AND NO FURTHER INFORMATION HAS BEEN PROVIDED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT THE CANNULA WAS INSERTED INTO THE CENTER TRAJECTORY, MER TESTING WAS PERFORMED. THE CANNULA WAS THEN MOVED TO THE MEDIAL TRAJECTORY. HOWEVER, RESULTS WERE NOT AS DESIRED AND THE TARGET WAS MOVED 3MM MEDIAL FROM THE ORIGINAL CENTER TRAJECTORY. THE LEAD WAS PLACED. DURING TESTING, IT WAS DECIDED TO MOVE THE CANNULA/LEAD TO THE POSTERIOR TRAJECTORY. AT THIS POINT, THE PATIENT APPEARED TO HAVE A STROKE AND THE PATIENT WAS CLOSED AND TAKEN TO THE ER. FOLLOW UP WITH THE SURGEON REVEALED THAT THERE WERE TWO BLEEDS UNILATERALLY ON THE RIGHT AT THE INTERNAL CAPSULE. THE SURGEON STATED THAT EVERY TRACK PLACED IS A 1% RISK OF THIS OCCURRING (4 TOTAL TRACKS ON RIGHT SIDE). THE LAST INFORMATION RECEIVED WAS THAT THEY WERE WAKING THE PATIENT UP, BUT IT IS UNKNOWN IF ANY DEFICITS ARE TEMPORARY AT THIS TIME.

This vulnerability affects multiple Unitree robot models including Go2, G1, H1 and B2 series robots up to the latest firmware from today [20. September 2025].

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED AND REVISED INTRA-OPERATIVELY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE BLADE WAS FOUND BROKEN ON THE HARMONIC ACE INSTRUMENT. A FRAGMENT FELL INTO THE PATIENT AND WAS RETRIEVED IN A DIFFERENT PROCEDURE. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED HYSTERECTOMY SURGERY, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY DEVELOPED A HOLE, WHICH LED TO THERMAL INJURY OF THE SMALL INTESTINE. THE INCIDENT OCCURRED WHILE THE SURGEON WAS DISSECTING THE UTERUS ON THE LEFT SIDE. AS THE TIP OF THE MCS INSTRUMENT WAS POSITIONED AGAINST THE UTERUS, A PORTION OF THE SMALL INTESTINE CAME INTO CONTACT WITH THE INSTRUMENT'S SHAFT, WHICH IS NORMALLY INSULATED BY THE MCS TIP COVER ACCESSORY. DUE TO THE HOLE NEAR THE ORANGE MARKER ON THE MCS TIP COVER ACCESSORY, A BURN APPROXIMATELY 1 CM IN DIAMETER OCCURRED ON THE INTESTINE. THE SURGEON PROMPTLY SUTURED THE AFFECTED AREA TO PREVENT RUPTURE, AND A GASTROINTESTINAL SURGEON WAS CONSULTED TO EVALUATE THE INJURY. THE ASSESSMENT CONFIRMED THAT THE INTERVENTION WAS SUFFICIENT. THE AFFECTED MCS INSTRUMENT WAS REMOVED AND THE MCS TIP COVER ACCESSORY WAS REPLACED. NO ELECTRICAL ARCING WAS OBSERVED AT THE TIME OF THE EVENT, AND THE PROCEDURE WAS COMPLETED ROBOTICALLY. THE SURGEON ASSESSED THE IMPACT ON THE PATIENT'S OUTCOME AS MINIMAL, AND NO POST-OPERATIVE COMPLICATIONS WERE REPORTED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED PANCREATODUODENECTOMY SURGICAL PROCEDURE, THE METAL TIP ON HARMONIC ACE INSTRUMENT BROKE OFF AND FELL INSIDE THE PATIENT. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED.

ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED AND REVISED INTRA-OPERATIVELY.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED MALIGNANT HYSTERECTOMY PROCEDURE, THE MONOPOLAR CURVED SCISSORS (MCS) TIP COVER ACCESSORY SLIPPED OFF THE MCS INSTRUMENT INSIDE THE PATIENT, AND WAS SUBSEQUENTLY DISCOVERED IN THE PELVIC AREA. THE MCS TIP COVER ACCESSORY WAS RETRIEVED DURING THE SAME PROCEDURE, USING A THIRD-PARTY LAPAROSCOPIC GRASPER INSTRUMENT. THE PROCEDURE WAS SUCCESSFULLY COMPLETED ROBOTICALLY. ADDITIONAL INFORMATION HAS BEEN REQUESTED; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM BEING USED DURING A SPINAL PROCEDURE. IT WAS REPORTED THAT DURING AN L2-L3 FUSION PROCEDURE USING COMPUTED TOMOGRAPHY-FLUORO REGISTRATION, NAVIGATION WITH THE GUIDANCE SYSTEM APPEARED TO BE INACCURATE BY 2 MILLIMETERS (MM), DEEP ON THE RIGHT SIDE OF L2 WHEN USING THE DILATOR OR THE PASSIVE PLANAR PROBE. THIS RESULTED IN A NERVE INJURY TO THE PATIENT. ANOTHER SNAPSHOT WAS PERFORMED AS A TROUBLESHOOTING STEP, WHICH DID NOT RESOLVE THE ISSUE. THE SYSTEM WAS THEN RE-REGISTERED, WHICH RESOLVED THE NAVIGATION INACCURACY. SURGICAL DELAY WAS LESS THAN ONE-HOUR. ADDITIONAL INFORMATION WAS RECEIVED. IT WAS REPORTED THAT THE PATIENT HAD SOME NUMBNESS/TINGLING. THEY HAD NOT MOBILIZED MUCH AS THEY WERE STILL RECOVERING, SO IT WAS UNKNOWN WHETHER IT WOULD MATERIALIZE TO ANY SORT OF DEFICIT.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MEDTRONIC RECEIVED INFORMATION REGARDING A GUIDANCE SYSTEM BEING USED DURING A SPINAL PROCEDURE, A T1-T12 SPINAL FUSION. IT WAS REPORTED THAT AN ALLEGED INACCURACY OCCURRED. INITIALLY, THE FIRST SURFACE SCAN WAS DELETED WITHOUT USER ACTION, AND THE SECOND SURFACE SCAN WAS UNUSABLE DUE TO A SHOULDER SHIFT. A THIRD SURFACE SCAN WAS SUCCESSFULLY PERFORMED. MEDTRONIC IMAGING WAS CONDUCTED FOR SCREW PLACEMENT PLANNING AND VERIFICATION. THE FIRST SCREW WAS PLACED, BUT WHEN THE ROBOT ARM WAS MOVED TO THE SECOND SCREW LOCATION, THE SURGEON OBSERVED THAT THE LOCATION APPEARED INACCURATE. THE ROBOT ARM USE WAS HALTED, AND CHICKENFOOT WAS USED TO CONFIRM THE LOCATION OF THE FIRST SCREW PLAN, REVEALING THAT THE PLAN WAS APPROXIMATELY 1 CENTIMETER (CM) LATERAL TO THE ACTUAL FIRST SCREW PLACEMENT. THE GUIDANCE SYSTEM USE WAS ABORTED. THE SURGICAL TEAM SWITCHED TO MEDTRONIC IMAGING AND NAVIGATION SYSTEM FOR PLACEMENT OF THE REMAINING SCREWS. MEDTRONIC IMAGING SHOWED THAT THE FIRST SCREW APPEARED TO BE 1 CM MEDIAL OF THE ORIGINALLY PLANNED LOCATION, AND IT WAS REPORTED THAT THE SCREW PENETRATED THE CANAL AT P1. A CEREBROSPINAL FLUID (CSF) LEAK WAS IDENTIFIED AND WAS REPORTEDLY BEING ADDRESSED DURI

VELYS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: POPLITEAL ARTERIA INJURY WHILE USING VELYS DURING A KNEE ARTHROPLASTY. THE SURGEON EXPLAINED THAT THEY DID NOT USE RETRACTORS AS USUAL FOR A RECUT AND FACED A POPLITEAL ARTERIA INJURY. THEY MADE A SUTURE DIRECTLY ON THE ARTERIA TO STOP THE BLEEDING AND THE PATIENT HAD NO MAJOR HEMORAGIA, AND NO OTHER VASCULAR SURGERY NEEDED. ARTHERIOGRAPHY WAS DONE. PROCEDURE WAS COMPLETED SUCCESSFULLY WITH A FIFTEEN MINUTE DELAY. PATIENT RECEIVED SURVEILLANCE IN THE ICU FOR A NIGHT AND A PLATELET-INHIBITING AGENT.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE SYNCHROSEAL INSTRUMENT'S BLADE BROKE AND DETACHED FROM THE INSTRUMENT. A FRAGMENT FELL INSIDE THE PATIENT BUT WAS RETRIEVED DURING THIS PROCEDURE. THE PROCEDURE WAS COMPLETED AS PLANNED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, THE BLADE WAS FOUND TO BE BROKEN ON THE HARMONIC ACE INSTRUMENT. A FRAGMENT FELL INSIDE A PATIENT AND WAS RETRIEVED DURING THE SAME PROCEDURE WHICH WAS COMPLETED ROBOTICALLY. INTUITIVE SURGICAL, INC. (ISI) HAS ATTEMPTED TO GATHER ADDITIONAL INFORMATION REGARDING THE REPORTED EVENT; HOWEVER, NO RESPONSE HAS BEEN RECEIVED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ON (B)(6) 2025, INTUITIVE SURGICAL, INC. (ISI) RECEIVED AN FDA MEDWATCH REPORT (MDR) WITH MDR REPORT #MW5176084 STATING: "WHILE USING HARMONIC ACE DURING ROBOTIC TLH, TIP OF HARMONIC BROKE OFF IN PATIENT. SURGEON CHOSE TO LEAVE THE TIP; THOUGHT IT WOULD CAUSE MORE HARM IF RETRIEVAL OCCURRED." ISI MADE MULTIPLE FOLLOW-UP ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION; HOWEVER, NO FURTHER DETAILS HAVE BEEN RECEIVED AS OF THE DATE OF THIS REPORT.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED DISTAL PANCREATECTOMY SURGICAL PROCEDURE, THE BLADE HEAD BROKE ON THE HARMONIC ACE INSTRUMENT. THE PROCEDURE WAS COMPLETED. INTUITIVE SURGICAL, INC. (ISI) FOLLOWED UP WITH THE INITIAL REPORTER AND OBTAINED THE FOLLOWING ADDITIONAL INFORMATION: THE CUTTER HEAD GASKET FELL OFF COMPLETELY INSIDE THE PATIENT, AND THE DROPPED FRAGMENTS WERE REMOVED FROM THE PATIENT'S BODY. THE INSTRUMENT WAS INTACT BEFORE USE. THE BREAKAGE OCCURRED DURING TISSUE DISSECTION, AND NO CONTACT WITH HARD OBJECTS WAS MADE. THE INSTRUMENT HAD BEEN IN USE FOR APPROXIMATELY 15 MINUTES WHEN THE BREAKAGE HAPPENED.

Monarch Platform — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT AFTER A SUCCESSFUL ROBOTIC BRONCHOSCOPY PROCEDURE, THE PATIENT DEVELOPED A PNEUMOTHORAX. PATIENT WAS HOSPITALIZED AND CHEST TUBE WAS PLACED. NO DEVICE ISSUES WERE REPORTED.

Mazor X — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IAO, C., GUO, X., QIU, W., QI, Q., GUO, Z., SUN, C., ZHONG, W., & LI, W. (2025). RETROSPECTIVE ANALYSIS OF CLINICAL MANAGEMENT STRATEGIES FOR CAGE RETROPULSION FOLLOWING POSTERIOR LUMBAR INTERBODY FUSION. ORTHOPAEDIC SURGERY, 17(11), 3133¿3141. HTTPS://DOI.ORG/10.1111/OS.70174 SUMMARY OBJECTIVES: CAGE RETROPULSION (CR) IS A COMMON COMPLICATION FOLLOWING POSTERIOR LUMBAR INTERBODY FUSION (PLIF). SYMPTOMATIC PATIENTS WITH CR OFTEN REQUIRE REVISION SURGERY. HOWEVER, THERE IS A LACK OF LITERATURE SUPPORTING THE EFFECTIVENESS OF CONSERVATIVE TREATMENT FOR CR. THIS STUDY COMPARES CLINICAL AND RADIOGRAPHIC OUTCOMES BETWEEN CONSERVATIVE TREATMENT AND REVISION SURGERY IN PATIENTS WITH CR AFTER PLIF. METHODS: A TOTAL OF 55 PATIENTS WITH CR AFTER PLIF TREATED AT OUR INSTITUTION BETWEEN 2016 AND 2023 WERE RETROSPECTIVELY REVIEWED; P OSTOPERATIVE RADIOGRAPHIC DATA OF FOLLOW-UP WERE USED TO DIAGNOSE CR. CLINICAL OUTCOMES WERE ASSESSED BEFORE THERAPY AND AT THE FINAL FOLLOW-UP USING THE VISUAL ANALOG SCALE (VAS) FOR LOWER BACK PAIN AND LEG PAIN, OSWESTRY DISABILITY INDEX (ODI) SCORES, AND JAPANESE ORTHOPEDIC ASSOCIATION 29 (JOA-29) SCORES. THE TREATMENT EFFECTIVENESS WAS EVALUATED BASED ON WHETHE

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING DA VINCI-ASSISTED TRANSABDOMINAL PREPERITONEAL UMBILICAL HERNIA REPAIR PROCEDURE, A FRAGMENT FROM THE BLACK PART OF THE UNIVERSAL SEAL BROKE OFF INSIDE THE PATIENT. THE SURGEON SUCCESSFULLY RETRIEVED THE PIECE, AND THE PROCEDURE CONTINUED AS PLANNED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: REFER TO H11 FOR FOLLOW-UP INFORMATION.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: A PATIENT IN A STUDY UNDERWENT A DA VINCI-ASSISTED BILATERAL NIPPLE SPARING MASTECTOMY (NSM) PROCEDURE. DURING THE PROCEDURE, THE PATIENT EXPERIENCED A SKIN BURN/BLISTERING ON THE RIGHT BREAST. THE COMPLICATION WAS TREATED WITH BACITRACIN ON THE WOUND AND NITRO PASTE AROUND THE WOUND. AS A RESULT, NO TISSUE EXPANDER WAS PLACED INTRA-OPERATIVELY, ONLY ACELLULAR DERMAL MATRIX. AS A RESULT, NO TISSUE EXPANDER WAS PLACED INTRA-OPERATIVELY, ONLY ACELLULAR DERMAL MATRIX. POST-OPERATIVELY, THE BILATERAL SKIN FLAPS WERE VIABLE AT THE END OF THE PROCEDURE AND A BILATERAL TWO-STAGE RECONSTRUCTION WAS PERFORMED. TISSUE EXPANDER WAS PLACED TO THE LEFT BREAST ONLY. THE STUDY INVESTIGATOR REPORTED THE EVENT AS NOT A SERIOUS ADVERSE EVENT (SAE), POSSIBLY RELATED TO DA VINCI DEVICE, POSSIBLY RELATED TO THE NSM PROCEDURE, BUT NOT RELATED TO THE RECONSTRUCTION PROCEDURE, NOT RELATED TO OTHER PROCEDURES OR EVENTS, AND NOT RELATED TO THE PATIENT'S PRE-EXISTING CONDITION. A DEVICE MALFUNCTION DID NOT RESULT IN THE ADVERSE EVENT.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED BENIGN HYSTERECTOMY SURGICAL PROCEDURE, THE HARMONIC ACE CURVED SHEERS JAWS BROKE IN 2 PIECES. THE FRAGMENT WAS RETRIEVED DURING THE SAME PROCEDURE. THE PROCEDURE WAS COMPLETED.

da Vinci Surgical System — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS REPORTED THAT DURING A DA VINCI-ASSISTED SURGICAL PROCEDURE, A BLACK FOREIGN OBJECT THAT HAD FALLEN INTO THE PATIENT APPEARED ON THE MONITOR DURING THE PROCEDURE, AND IT WAS RETRIEVED. THE PROCEDURE WAS COMPLETED.