Find a safety record
Every incident, injury and recall on file, from the national registries that publish them. Search a maker, a model, a town or a reference number — or narrow by what happened. Each record is the registry's own text, reproduced without rewriting, with the reference that locates it at the source. Registries count different things, so a total is a count of FILINGS and never a measure of how dangerous something is. How the record was collected.
Or jump to a maker
1,090 records match
2007–20265 registriesClear
Narrow it down
What happened
Country
Year
Not graded by the source2023-12-04FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00032Monarch Platform
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 DURING A MONARCH BRONCHOSCOPY PROCEDURE AN E-STOP ERROR OCCURRED. THE PHYSICIAN WAS UNABLE TO CLEAR THE E-STOP ERROR AND ELECTED TO ABORT THE CASE. THERE WERE NO REPORTED ADVERSE EFFECTS TO THE PATIENT BECAUSE OF THE SYSTEM ISSUES.
cause not established3014447948-2023-00032Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-29FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00033Monarch Platform
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 DIAGNOSTIC PROCEDURE USING THE MONARCH BRONCHOSCOPY SYSTEM, THE PATIENT DEVELOPED A PNEUMOTHORAX AND LATER PASSED AWAY. THERE WAS NO REPORTED DEVICE MALFUNCTION ASSOCIATED WITH THE ADVERSE EVENT. PER THE ACCOUNT MANAGER, HOSPITAL ENDO MANAGEMENT DOES NOT ATTRIBUTE THE PNEUMOTHORAX OR THE SUBSEQUENT DEATH TO ANY DEFICIENCY OF THE MONARCH SYSTEM.
cause not established3014447948-2023-00033Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-29FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00534ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS INFORMED THAT ONE CASE OF L1-L4 MIS FIXATION WITH INTRAOP (O-ARM)WORKFLOW WAS BEING DONE AND THE PLANNING WAS DONE AFTER REGISTRATION. SURGEON HAD ALREADY PLACED L1 LEFT, L2 LEFT & L3 LEFT SCREWS. AFTER DRILLING IN L4 LEFT PEDICLE, SURGEON HAS CHECKED WITH BALL TIP PROBE AND OBSERVED THAT SOMETHING WAS WRONG, AND HE STOPPED THE PROCEDURE. AFTER CHECKING WITH C-ARM SHOT IT WAS FOUND THAT ALL THREE PLACED SCREWS ARE NOT AS PER THE PLAN AND ALL THE SCREWS WERE SHIFTED MEDIALLY AND CAUDALLY. AFTER THAT SURGEON HAS STOPPED USING ROBOT AND REPOSITIONED ALL THE SCREWS MANUALLY.
cause not established3004142400-2024-00534Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-29FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00251ExcelsiusGPS
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 WHILE USING THE EXCELSIUS GPS SYSTEM, THE CASE WAS ABORTED AND SCREWS WERE THEN PLACED BY HAND. THIS EVENT OCCURRED IN GERMANY.
cause not established3004142400-2024-00251Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-23FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00533ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THIS WAS AN INTRAOP ADOLESCENT SCOLI CASE T4-L5 WITH A SIEMENS CIOS SPIN. WE DIVIDED THE CASE INTO THREE SEGMENTS (L2-L5, T9-T11 AND T4-T6) AND REIMAGED THE PATIENT. APPARENTLY, THE TECHNICIAN CANNOT ISOLATE THE SINGLE SCAN, SO ALL SCANS WERE TRANSFERRED WITH THE LAST ONE. DURING THE NAVIGATION ON THE LAST SEGMENT, THE IMAGE OF THE SCAN WAS KIND OF TORN AND THE SAGITTAL AND AXIAL PLANE LOOKED ALIKE. RESET SOFTWARE, HARD DID NOT HELP, DID A HARD SHUTDOWN AND RESTART. THE ISSUE WITH THE SCAN WAS STILL THERE AND COULD NOT BE SOLVED. THE LAST THREE TRAJECTORIES WERE DRILLED WITH THE ROBOT, BUT SCREWS WERE INSERTED FREEHANDED.
cause not established3004142400-2024-00533Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-20FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00532ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: GPS UNIT IS HAVING HARD DRIVE ISSUES. IT WILL ONLY DISPLAY A BLACK SCREEN WHEN BOOTING UP STATING "REBOOT AND SELECT PROPER BOOT DEVICE OR INSERT BOOT MEDIA IN SELECTED BOOT DEVICE AND PRESS A KEY."
cause not established3004142400-2024-00532Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-17FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00223ExcelsiusGPS
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 INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2024-00223Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-15FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00528ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE CASE WAS AN L4-S1 ALIF 360 USING HEDRON IA AND CREO ONE HARDWARE. THERE WAS NO PRIOR HARDWARE IN THE PATIENT. THE EGPS WORKFLOW WAS INTRA-OP CT. THE EGPS IS RUNNING SOFTWARE VERSION 1_1R3. THE PATIENT WAS POSITIONED PRONE FOR THE POSTERIOR PORTION AND THE CAMERA WAS POSITIONED AT THE FOOT OF THE BED. AN O-ARM WAS USED FOR IMAGING AND REGISTRATION. DR. (B)(6) PLACED THE DRB AT RIGHT PSIS WITH THE LOW-PROFILE QUATTRO SPIKE AND SURVEILLANCE MARKER AT LEFT PSIS. SURVEILLANCE WAS REGISTERED PRIOR TO THE ICT BEING POSITIONED ON THE QUATTRO SPIKE. THE ICT WAS POSITIONED, THE BED WAS RAISED, AND THE SURGICAL SNAPSHOT WAS TAKEN. THE O-ARM SPIN WAS ACQUIRED AND TRANSFERRED SUCCESSFULLY TO EGPS VIA ETHERNET. ALL 7 FIDUCIALS WERE CAPTURED SUCCESSFULLY, AND THE REGISTRATION FIT WAS DOWN ON GREEN. DR. (B)(6) PERFORMED LANDMARK CHECKS ON THE ICT FIDUCIALS AS WELL AS DOWN THE LOW-PROFILE QUATTRO SPIKE. NAVIGATION APPEARED TO EVERYONE IN THE ROOM TO BE ACCEPTABLE AND OF HIGH QUALITY. FOLLOWING PERCUTANEOUS PLACEMENT OF ALL SCREWS THROUGH BILATERAL WILTSY INCISIONS, A POST-OP REGISTRATION O-ARM SPIN WAS ACQUIRED. DR. (B)(6) DECIDED TO DO THIS PRIOR TO LOCKING THE CONSTRUCT DOWN AS HE QUESTIONED
cause not established3004142400-2024-00528Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-14FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00531ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE SURGEONS COMPLAINT WAS THE FACT THAT WHILE ATTEMPTING TO MERGE THE L2 VERTEBRAL BODY, HE WAS UNABLE TO GET A BETTER MERGE BECAUSE OF THE LORDOTIC SHIFTING.
cause not established3004142400-2024-00531Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-14FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00527ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: WE WERE INSTRUMENTING PEDICLE SCREWS AT T12 & L2 , SKIPPING THE FRACTURE LEVEL. THE E3D SPIN WENT FINE, AND INITIAL NAV INTEGRITY CHECKS SEEMED FINE AS WELL. WE PLACED ALL 4 SCREWS AT T12 / L2. WE BATTLED A LITTLE BIT OF SAVING BUT NOTHING SIGNIFICANT. WE TOOK AP SHOT AFTER SCREWS WERE PLACED, AND ALL FOUR SCREWS WERE COMPLETELY OUT OF THE PEDICLE. THE LEFT SIDE WAS LATERAL, AND RIGHT SIDE WAS MEDIAL.
cause not established3004142400-2024-00527Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-13FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00526ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ALL OUR SCREWS WERE ON, WE USED PRE OP CT WORKFLOW WITH G-ARM. THEN WE TOOK AN X-RAY OF OUR LATERAL TRIAL, AND THE NAVIGATION WAS ON. WHEN PLACING THE IMPLANT, WE WERE 4/5MM OFF POSTERIOR. WE HAD TO GO BACK IN, OPEN THE PATIENT, RETRIEVE THE CAGE AND RE DO EVERYTHING, NAVIGATION APPEARED TO BE ON UP UNTIL THE CAGE.
cause not established3004142400-2024-00526Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-11FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00529ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: APOLOGIES, ORIGINAL REPORT DID NOT PROCESS. LOGS HAVE BEEN UPLOADED TO INR PORTAL. THERE WAS A SUSPECTED ISSUE WITH THE PREOP REGISTRATION/MERGE. T12 FRACTURE, SCREWS PLACED AT T10-11, L1-2. NAMELY, T11-L WAS PLACED LATERAL TO THE ORIGINAL PLACE. ADDITIONALLY, T10 SCREWS PLACED PROUD. AFTER DISCUSSION, SUSPECTED MISSTEP MAY HAVE BEEN PROPER PLACEMENT OF FLUORO FIXTURE BUT NO YET CAUSE DETERMINED. SCREWS WERE REPOSITIONED VIA TRADITIONAL MIS JAMSHID TECHNIQUE.
cause not established3004142400-2024-00529Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-10FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00030Monarch Platform
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 DURING A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN WAS ADJUSTING THE SCOPE TOWARDS TARGET OF NODULE AND THE PATIENTS HEART RATE (HR) BEGAN TO DECLINE AND THE PHYSICIAN ABORTED THE CASE. THE PATIENT THEN WENT INTO ASYSTOLE AND REQUIRED EMERGENT CONVERSION AND CHEST COMPRESSIONS. ONCE THE PATIENT REGAINED A PULSE THE WERE TRANSPORTED THE INTENSIVE CARE UNIT (ICU) WHERE THE PATIENT CODED AGAIN AND WAS BEING SENT TO THE CARDIAC CATH LAB. THE PHYSICIAN STATED THAT THE ADVERSE EVENTS ARE NOT ATTRIBUTED TO THE MONARCH SYSTEM.
cause not established3014447948-2023-00030Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-10FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00031Monarch Platform
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 DURING A MONARCH BRONCHOSCOPY PROCEDURE THE PHYSICIAN WAS ADJUSTING THE SCOPE TOWARDS TARGET OF NODULE AND THE PATIENTS HEART RATE (HR) BEGAN TO DECLINE AND THE PHYSICIAN ABORTED THE CASE. THE PATIENT THEN WENT INTO ASYSTOLE AND REQUIRED EMERGENT CONVERSION AND CHEST COMPRESSIONS. ONCE THE PATIENT REGAINED A PULSE THE WERE TRANSPORTED THE INTENSIVE CARE UNIT (ICU) WHERE THE PATIENT CODED AGAIN AND WAS BEING SENT TO THE CARDIAC CATH LAB. THE PHYSICIAN STATED THAT THE ADVERSE EVENTS ARE NOT ATTRIBUTED TO THE MONARCH SYSTEM.
cause not established3014447948-2023-00031Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-09FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00530ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE PLANNED SURGERY ON THE DORSAL CERVICAL SPINE INCLUDED A SCREW FIXATION C1/C3/C4. WHEN CHECKING THE SCREW POSITION IN THE 3D SCAN AFTER SCREW PLACEMENT, THE SURGEONS WERE NOT SATISFIED WITH THE SCREW POSITION OF A C1 SCREW. A NEW 3D SCAN WAS PERFORMED AND A NEW C1 SCREW WAS PLANNED INTRAOPERATIVELY. WHEN APPROACHING THE TRAJECTORY, THE ROBOTIC ARM STOPPED FAR AWAY FROM THE FINAL POSITION AND ONLY SHOWED A YELLOW FRAME. THE END EFFECTOR WAS SO FAR AWAY THAT THE INSTRUMENTS DID NOT REACH THE BONE. RESETTING THE SOFTWARE AND MOVING THE ROBOT ARM MANUALLY DID NOT CHANGE ANYTHING. BECAUSE THE ROBOT ARM WAS TOO FAR AWAY, THE C1 SCREW HAD TO BE INSERTED MANUALLY (WITH NAVIGATION OF THE ROBOT), BUT NOT BY THE END EFFECTOR.
cause not established3004142400-2024-00530Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-09FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00034Monarch Platform
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 REPEATED SYSTEM FAULTS OCCURRED DURING A MONARCH BRONCHOSCOPY. THE PHYSICIAN TRIED MULTIPLE BRONCHOSCOPES, BUT THE SYSTEM CONTINUED TO FAULT. THE PHYSICIAN ELECTED TO ABORT THE DIAGNOSTIC PROCEDURE. NO CLINICAL CONSEQUENCES TO THE PATIENT WERE REPORTED DUE TO THIS EVENT.
cause not established3014447948-2023-00034Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-08FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2023-00196ExcelsiusGPS
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 A SCREW USING THE EXCELSIUS GPS SYSTEM WAS MISPLACED INTRA-OPERATIVELY CAUSING A SCREW TO BREACH THE PATIENT'S SPINAL CANAL.
cause not established3004142400-2023-00196Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-07FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2023-00194ExcelsiusGPS
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 A REVISION SURGERY WAS NEEDED TO REMOVE AND REPLACE MISPLACED SCREWS THAT WERE PLACED USING THE EXCELSIUS GPS SYSTEM.
cause not established3004142400-2023-00194Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-03FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00521ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: CAMERA IS BROKEN FULL DESCRIPTION ENTIRE SYSTEM NEEDS TO BE RUN FOR BUGS CAMERA IS BROKEN STORAGE IS LOW AND COMPUTER IS SLOW NEED TO BE DONE ASAP.
cause not established3004142400-2024-00521Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-11-03FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00029Monarch Platform
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 PHYSICIAN OBSERVED EXCESS AMOUNT OF BLOOD IN THE AIR WAY AFTER SUCCESSFULLY COMPLETING THE MONARCH BRONCHOSCOPY PROCEDURE. THE PHYSICIAN ELECTED TO USE THEIR MANUAL BRONCHOSCOPE AND COLD SALINE TO CLEAR THE AIRWAY; HOWEVER, COMPLICATIONS OCCURRED DURING THE POST-MONARCH BRONCHOSCOPY PROCEDURE. THE PATIENTS BLOOD HAD CLOTTED AND BLOCKED THE ENDOTRACHEAL TUBE (ET TUBE). THE PATIENT THEN FELL INTO CARDIAC ARREST DUE TO LACK OF VENTILATION FROM THE FROM THE BLOOD CLOT BEING PRESENT IN THE ENDOTRACHEAL TUBE (ET TUBE). THE PHYSICIAN FOLLOWED CARDIAC ARREST PROTOCOL AND WAS ABLE TO RECOVER THE PATIENT. THE PATIENT WAS ADMITTED INTO INTENSIVE CARE UNIT (ICU) ON THE SAME DAY. AFTER THE PATIENT WAS SENT TO RECOVERY IN THE INTENSIVE CARE UNIT (ICU), THE PATIENT WAS GIVEN A CHEST X-RAY WHERE DOCTOR DISCOVERED THE PATIENT HAD EXPERIENCED A PNEUMOTHORAX. A CHEST TUBE WAS PLACED AND REMOVED THE FOLLOWING DAY. THE PHYSICIAN STATED THE PNEUMOTHORAX WAS DUE TO LONG BAG VENTILATION TIME, EXCESS SUCTION, AND OVER ALL STRESS ON THE LUNG THAT OCCURRED DURING BLEEDING MANAGEMENT POST-MONARCH PROCEDURE. THE PATIENT HAS BEEN RELEASED FROM THE HOSPITAL.
cause not established3014447948-2023-00029Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-11-02FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00028Monarch Platform
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 DURING A DIAGNOSTIC PROCEDURE USING THE MONARCH BRONCHOSCOPY SYSTEM, THE PHYSICIAN DECIDED TO ABORT THE DIAGNOSTIC PROCEDURE DUE TO NAVIGATIONAL DIFFICULTY AND POOR VISIBILITY. PATIENT MUCUS CONTRIBUTED SIGNIFICANTLY TO THE POOR VISIBILITY. THE PHYSICIAN DECIDED TO CONVERT THE DIAGNOSTIC PROCEDURE TO A MANUAL BRONCHOSCOPY PROCEDURE. IT WAS REPORTED THAT THE PATIENT DEVELOPED A PNEUMOTHORAX AND A CHEST TUBE WAS PLACED.
cause not established3014447948-2023-00028Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-10-30FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00519ExcelsiusGPS
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 INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2024-00519Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-30FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00518ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: TRYING TO START A CASE AND THE ROBOT WENT TO REBOOT AND SELECT PROPER BOOT DEVICE. NEED AN FSE FOR TOMORROW'S CASE WITH A NEW SURGEON.
cause not established3004142400-2024-00518Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-29FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00524ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING ROBOTIC REGISTRATION THE FLUORO SHOTS AND PRE-OP CT SCAN DID NOT ALIGN PROPERLY. WITH CLEAR FLUORO PHOTOS IT LOOKED AS IF THE ROBOT WAS PULLING AN OBLIQUE CT SLICE. WE HELD RESPIRATION, CENTERED EACH VERTEBRAE, SOFTWARE RESET, SWITCHED TO CRANIAL AND BACK WITH NO SUCCESS. I USED LIFE SAVER, BUT AT THAT POINT DR. (B)(6) CHOSE NOT TO CONTINUE WITH THE ROBOT.
cause not established3004142400-2024-00524Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-27FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00525ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS THE INTRA-OP SPINE CASE. UNFORTUNATELY, THE TEAM COULDN'T GET THE AUTOMATIC REGISTRATION. IT HAD BEEN DONE ANOTHER SCAN WITH THE SAME RESULT. AFTER THE REGISTRATION WAS DONE MANUALLY, THE SURGEON NOTICED SOME NAVIGATION SHIFTS. THE ROBOTIC CASE WAS ABORTED AND DONE TRADITIONALLY. NO ADVERSE EFFECTS FOR THE PATIENT.
cause not established3004142400-2024-00525Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-27FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00228ExcelsiusGPS
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 WHILE USING THE EXCELSIUS GPS SYSTEM, THE CASE WAS ABORTED DUE TO HARDWARE ERROR. THIS EVENT OCCURRED IN THE UNITED KINGDOM.
cause not established3004142400-2024-00228Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-26FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2023-00188ExcelsiusGPS
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 A SCREW USING THE EXCELSIUS GPS SYSTEM WAS MISPLACED INTRA-OPERATIVELY CAUSING A LARGE BLEED.
cause not established3004142400-2023-00188Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-25FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00520ExcelsiusGPS
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 INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED.
cause not established3004142400-2024-00520Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-24FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00227ExcelsiusGPS
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 WHILE USING THE EXCELSIUS GPS SYSTEM, THE CASE WAS ABORTED AND SCREWS WERE THEN PLACED BY HAND.
cause not established3004142400-2024-00227Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-23FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00517ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: ALL POWER LOST TO EGPS UNIT WHILE UNIT WAS PLUGGED INTO A VIABLE/TESTED POWER SOURCE. POWER SOURCE WAS USED IN TWO CASES DURING THE SAME DAY (B)(6) 2023. ALL FUNCTION AND AGENCY LOST TO THE EGPS UNIT DURING THIS TIME. BOTH THE BATTERY SYMBOL AND ON/OFF SYMBOL WERE NOT EMITTING ANY COLOR.
cause not established3004142400-2024-00517Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-23FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00523ExcelsiusGPS
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 INTRA-OPERATIVELY AND THEN REMOVED AND REPLACED. THIS EVENT OCCURRED IN AUSTRALIA.
cause not established3004142400-2024-00523Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-20FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00509ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: SCREWS L2-S1, ALL LEFT SCREWS MEDIAL AND ALL RIGHT SCREWS LATERAL. WHEN REMOVING SCREWS, INITIALLY OUR SPIN WAS CORRECT AND NAVIGATION INTEGRITY WAS SOLID; HOWEVER, AFTER REMOVING ONE OR TWO MORE SCREWS, WHEN THE CHICKEN FOOT WAS AGAIN PLACED DOWN THE SCREW TRAJECTORY TO CONFIRM NAVIGATION ACCURACY, THE SCREW APPEARED TO BE MEDIAL TO WHERE THE TOOL WAS PLACED.
cause not established3004142400-2024-00509Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-17FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00510ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: IT WAS NOT POSSIBLE TO UPLOAD THE PLANNED CASE FROM LAPTOP TO THE ROBOT WITH USB STICK. WE GOT THE MESSAGE ''GPS CLIENT IS NOT RESPONDING''. SOFTWARE RESET, HARD SHUTDOWN DIDN'T HELP. THE SCREEN WAS FROZEN WITH THE MESSAGE ''IMPORTING CASE FROM USB''. THE CASE WAS DONE IN TRADITIONAL WAY.
cause not established3004142400-2024-00510Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-16FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00027Monarch Platform
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 A SYSTEM FAULT OCCURRED DURING SETUP FOR A MONARCH BRONCHOSCOPY. THE PHYSICIAN ELECTED TO NOT START THE DIAGNOSTIC PROCEDURE. THE PATIENT HAD ALREADY BEEN ANESTHETIZED. NO CLINICAL CONSEQUENCES TO THE PATIENT WERE REPORTED DUE TO THIS EVENT. (B)(4). THIS REPORT IS BEING SUBMITTED PURSUANT TO THE PROVISIONS OF 21 CFR, PART 803. THIS REPORT MAY BE BASED ON INFORMATION WHICH HAS NOT BEEN INVESTIGATED OR VERIFIED PRIOR TO THE REQUIRED REPORTING DATE. THIS REPORT DOES NOT REFLECT A CONCLUSION BY ETHICON, AURIS HEALTH, OR ITS EMPLOYEES THAT THE REPORT CONSTITUTES AN ADMISSION THAT THE PRODUCT, ETHICON, OR ITS EMPLOYEES CAUSED OR CONTRIBUTED TO THE POTENTIAL EVENT DESCRIBED IN THIS REPORT. IF INFORMATION IS OBTAINED THAT WAS NOT AVAILABLE FOR THE INITIAL REPORT, A FOLLOW-UP REPORT WILL BE FILED AS APPROPRIATE.
cause not established3014447948-2023-00027Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-10-12FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2023-00181ExcelsiusGPS
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 A REVISION SURGERY WAS NEEDED TO REMOVE AND REPLACE MISPLACED SCREWS THAT WERE PLACED USING THE EXCELSIUS GPS SYSTEM.
cause not established3004142400-2023-00181Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-12FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00236ExcelsiusGPS
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 WHILE USING THE EXCELSIUS GPS SYSTEM, THE CASE WAS ABORTED AND SCREWS WERE THEN PLACED BY HAND.
cause not established3004142400-2024-00236Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-12FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2023-00184ExcelsiusGPS
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 A PATIENT EXPERIENCED ADVERSE EFFECTS FOLLOWING SURGERY WHERE SCREWS USING THE EXCELSIUS GPS SYSTEM WERE MISPLACED INTRA-OPERATIVELY.
cause not established3004142400-2023-00184Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-11FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00507ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING AN INTRA-OP DBS CASE AT (B)(6) MEDICAL CENTER, A 2ND O-ARM EVALUATION SPIN SHOWED THAT THE LEAD WAS ~2 MM SUPERFICIAL TO THE PLANNED DEPTH. THE PLANNED DEPTH WAS 2 MM PAST THE TARGET BASED ON THE BURNED IN BRAINLAB LEFT VIM TRAJECTORY. FROM THE FIRST EVALUATION SPIN, THE LEAD WAS 6.5 MM ABOVE THE PLANNED DEPTH AND 4.5 MM ABOVE THE BURNED IN TARGET. AFTER OBSERVING THE RESULTS FROM THIS FIRST SPIN, DR. (B)(6) STATED THAT HE MAY HAVE PULLED BACK ON THE LEAD WHEN REMOVING THE CANNULA. HE WENT BACK IN AND MANUALLY ADVANCED THE LEAD 6.5 MM FURTHER TO ACCOUNT FOR THE DEPTH DISCREPANCY WHILE HAVING HIS PA PERFORM LFPS ON THE PATIENT. AFTER HE ADVANCED THE LEAD TO HIS DESIRED DEPTH, A 2ND EVALUATION SPIN WAS PERFORMED. THE RESULT OF THIS SPIN SHOWED THAT THE LEAD WAS EXACTLY TO TARGET DEPTH, WHICH IS 2 MM SUPERFICIAL FROM HIS PLANNED DEPTH.
cause not established3004142400-2024-00507Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-11FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00508ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: FOR A SINGLE POSITION LATERAL CASE AT L4-5 DURING CASE SET UP THE END EFFECTOR LATCH WAS VERY STICKY AND HARD TO CLOSE. AFTER THE FIRST MERGE WITH PREOP CT WORK FLOW WE RECEIVED A HIGH SURVEILLANCE MESSAGE, SO WE REMERGED AND RESETTLED SURVEILLANCE. AFTER DRILLING THE FIRST PEDICLE L4 LEFT IT DID NOT FEEL OR LOOK RIGHT SO WE BROUGHT IN FLUORO. THE LATERAL WAS TO PLAN BUT THE AP WAS VERY MEDIAL. WE AGAIN REMERGED AND RESETTLED SURVEILLANCE. WE SWITCHED OUT THE END EFFECTOR AND, ON THE 3RD, TRY WE WERE ABLE TO ACCURATELY PLACE BILATERAL PEDICLE SCREWS. WE NEED TO REPLACE THE END EFFECTOR. I WILL UPLOAD CASE LOGS FOR THIS CASE TO THE ECL MODULES.
cause not established3004142400-2024-00508Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-10FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00506ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: WE PLACED QUATTRO SPIKE IN RIGHT PSIS AND SURVEILLANCE MARKER IS LEFT PSIS. WE TOOK X-RAYS FOR THE MERGE, AND ALL CONFIRMED L4 AND L5 VERTEBRAL BODIES. THE MERGE WAS SUCCESSFUL, AND X RAY CAME OUT. AT THIS POINT, THE REP HAD NOTICED THAT THE DRB ON THE LEFT WAS CLOSE TO PATIENT AND ASKED IF IT HAD BEEN LIKE THAT. I ASKED THE SURGEON IF THERE WAS A GAP, SURGEON CONFIRMED THAT THERE WAS. ROBOT WAS BROUGHT IN, AND STABILIZERS WERE PLACED. SURGEON MOVED FORWARD WITH PLACING LEFT L4, INSTRUMENTS DIDN'T LOOK RIGHT ON NAVIGATION, BUT SURGEON FELT FINE. WE DID L5 AND SAW SAME NAVIGATION ISSUE AFTER PLACING SCREW WE DECIDED TO TAKE A X RAY TO CONFIRM AND NOTICED WE WERE OFF. SURGEON THEN HAD ROBOT TAKEN OUT AND OPENED PATIENT UP. SCREWS REMOVED AND HE FINISHED THE PROCEDURE.
cause not established3004142400-2024-00506Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-06AU Product Safety2023/19875Aiper Elite Pro GS 100 cordless robotic vacuum pool cleaner
Aiper Elite Pro GS 100 cordless robotic vacuum pool cleaner — Charging cable can be plugged directly into the device without the adaptor, causing the battery to overheat and short circuit, risking serious injury and property damage via fire. One incident has occurred resulting in consumer injury. Sold online via Aiper's website and Amazon 5 Jan-18 Jul 2023, nationally. Consumers told to stop use immediately and return for a replacement.
cause not established2023/19875Read the record ↗Not graded by the source2023-10-06FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00505ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING A ROUTINE CASE, REGISTRATION WAS COMPLETED AND FIRST 2 SCREWS WERE PLACED SUCCESSFULLY. THIRD TRAJECTORY WAS ACTIVATED. SYSTEM GAVE ERROR "FOOTPEDAL ENABLED ERROR". USER THEN TRIED TO ACTIVATE SURGEON BRACELET AND THAT DID NOT WORK AT ALL. THAT IS WHEN THE USER DISCOVERED THE SYSTEM DID NOT HAVE ANY MOVEMENT AND THE FIRST SHUT DOWN WAS COMPLETED. THE USER LOGGED IN TOO QUICK WHEN MOTION WAS STILL BE CHECK SIGNIFIED BY BLUE INFORMATION RING. IT WAS ATTEMPTED TO CALIBRATE LOAD CELL WHICH DID NOT WORK. USER THEN PLACED REST OF SCREWS FREE HAND. SYSTEM WAS PULLED OUT OF THE FIELD AFTER THE PROCEDURE. FOOT PEDAL WAS RE-ENGAGED INTO THE PORT AND A LOAD CELL CALIBRATION WAS COMPLETED. THEY PULLED HTE SYSTEM OUT AND RESTARTED AGAIN AND MOTION WAS RESTORED.
cause not established3004142400-2024-00505Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-10-02FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00026Monarch Platform
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 DIAGNOSTIC PROCEDURE USING THE MONARCH BRONCHOSCOPY SYSTEM, A PNEUMOTHORAX WAS NOTED. A CHEST TUBE WAS PLACED, AND THE PATIENT WAS ADMITTED TO THE HOSPITAL. THERE WAS NO REPORTED DEVICE MALFUNCTION ASSOCIATED WITH THE ADVERSE EVENT.
cause not established3014447948-2023-00026Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-09-28FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00504ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: DURING AN EGPS WITH E3D SINGLE LEVEL L5-S1 PERC CASE, THE TWO L5 SCREWS WERE PLACED SUPERIOR TO THE PLAN. IT IS ASSUMED THAT THE DRB WAS MOVED DURING THE CASE AND DISCOVERED THAT THE SURVEILLANCE WAS NOT SET. DURING SCREW PLACEMENT, NOTHING LOOKED UNUSUAL - DOCKING THE HIGH-SPEED BUR ON THE BONE DIDN'T SHOW THE BUR HIGH OR INTO THE BONE AS ONE WOULD EXPECT WITH A DRB SHIFT. THE SCREWS ALL STIMULATED AT 20MA EXCEPT THE RIGHT S1 WHICH WAS 10MA WHICH PROMPTED A VERIFICATION SPIN WITH THE E3D. THE L5 SCREWS AND THE RIGHT L1 WERE REMOVED AND A SECOND E3D SPIN WAS DONE. THE SCREWS WERE THEN PLACED WITH NO FURTHER DIFFICULTY. THE CASE LOG WILL BE FORWARDED.
cause not established3004142400-2024-00504Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-09-27FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00503ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: THE CASE WAS AN L2-4 LLIF WITH POSTERIOR FIXATION USING CREO MIS AND PRE-OP CT WORKFLOW USING EGPS. THE CT SCAN APPEARED TO BE TO PROTOCOL BUT UPON MERGING THE AP AND LATERAL VIEWS APPEARED OBLIQUE AND A SUCCESSFUL MERGE COULD NOT BE OBTAINED EVEN WITH TRUE SHOTS. I AM ATTACHING CASE LOGS AS WELL AS A ZIPPED FOLDER OF THE CT SCAN SO INR APPLICATIONS MAY REVIEW THIS SCAN FOR DATA. IT CAME TO MY ATTENTION THAT THE KERNEL VALUE OF THE CT WAS B70 AND THIS IS NOT IDEAL FOR OUR PROTOCOL. THE SCANNER WAS A SIEMENS.
cause not established3004142400-2024-00503Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-09-25FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00502ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: L5-RT SCREW WE ACTUALLY HAD SPACE FOR A 5.5 SCREW RUNNING MEDIAL TO THE OLD SCREW AND TRIED THIS. THIS IS THE SCREW THAT ULTIMATELY LOOKED TO MEDIAL ON FLUORO AND WHEN WE DECOMPRESSED, WE COULD SEE 6 THREADS OF THE SCREW WERE MEDIAL TO THE PEDICLE WITH HALF THE SCREW EXPOSED.
cause not established3004142400-2024-00502Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-09-25FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00025Monarch Platform
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 A SYSTEM FAULT OCCURRED DURING SETUP FOR A MONARCH BRONCHOSCOPY. THE PHYSICIAN ELECTED TO NOT START THE DIAGNOSTIC PROCEDURE AND TO RESCHEDULE THE PROCEDURE FOR ANOTHER DAY. THE PATIENT HAD ALREADY BEEN ANESTHETIZED. NO CLINICAL CONSEQUENCES TO THE PATIENT WERE REPORTED DUE TO THIS EVENT.
cause not established3014447948-2023-00025Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-09-22FDA MAUDEAuris HealthMonarch Platform3014447948-2023-00024Monarch Platform
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 SYSTEM FAULTS OCCURRED DURING SETUP FOR A MONARCH BRONCHOSCOPY. THE PHYSICIAN ELECTED TO NOT START THE DIAGNOSTIC PROCEDURE. THE PATIENT HAD ALREADY BEEN ANESTHETIZED. NO CLINICAL CONSEQUENCES TO THE PATIENT WERE REPORTED DUE TO THIS EVENT.
cause not established3014447948-2023-00024Auris HealthMonarch PlatformRead the record ↗Not graded by the source2023-09-21FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00501ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: MERGED CT WITH FLAT PANEL. CENTROID PLACEMENT SEEMED EXTRA OFF IN LATERAL VIEW EVEN MORE THAN USUAL. PHYSICIAN STATED THAT SOMETHING FELT OFF FROM FIRST SCREW. THROUGH 7 SCREWS PLACED, SURGEON X-RAYED AND NOTICED MULTIPLE SCREWS WERE BREACHED. NO ALARMS FROM SURVEILLANCE UNTIL THE LAST SCREW WHICH IS WHY SURGEON DID X-RAY. DID O-ARM SPIN AND NEW CASE TO REPLACE SCREWS THAT WERE BREACHED AND FINAL SCREWS.
cause not established3004142400-2024-00501Globus MedicalExcelsiusGPSRead the record ↗Not graded by the source2023-09-18FDA MAUDEGlobus MedicalExcelsiusGPS3004142400-2024-00499ExcelsiusGPS
ExcelsiusGPS — Injury report filed with FDA (MAUDE). A MAUDE report does not establish that the device caused the outcome. Reported narrative: UPON SYSTEM BOOT UP, SYSTEM WOULD GET STUCK ON BLACK SCREEN WHERE NO BOOT MODE HAD BEEN SELECTED. THE SYSTEM WAS RESTARTED MULTIPLE TIMES AND STILL COULD NOT MAKE IT PAST THE BLACK BOOT MODE SELECT SCREEN. REQUESTING FSE SUPPORT TO ADDRESS COMPUTER/HARD DRIVES AND FIGURE OUT THE ROOT OF THIS PROBLEM.
cause not established3004142400-2024-00499Globus MedicalExcelsiusGPSRead the record ↗