Tom Amlicke

The Robot Operating System (ROS) has changed how engineers entering our workforce learn robotics. These engineers had a shared toolbox to bootstrap their robot projects or research. They could start working on a robot and immediately solve real-world problems. ROS 2 addressed architectural problems that made it difficult to turn an R&D robot into a viable product. ROS 2 can scale up or scale down to meet the needs of the specific robot product. Safety is always a concern with robotics. In the past, robots were placed in work cells to operate safely away from humans. Industries with safety and risk concerns have created versions of ROS that allow systems to be more easily certified safe for use. Some examples are Apex.OS (automotive self-driving car safety standard 26262) and Space ROS (aerospace safety standards DO-178C and NPR7150.2D). ROS is not currently the de facto standard for surgical robotics and robotics in medical devices, but maybe it should be. In this presentation, we will explore the potential benefits from a version of ROS that is tailored to address the standards needed for the medical device industry, such as IEC 62304 and ISO 60601.This presentation will identify the possible features a medical ROS would support and compare potential benefits to actual benefits reported by users of Apex.OS and Space ROS. We will examine all possible paths that we as an industry can take to achieve a medical certifiable ROS, ensuring its success and sustainability to maximize industry-wide advantages.