Telemedicine, mobile healthcare, and smart healthcare all rely on feature-rich software. Whether it is a health software/app that collects users' blood pressure, blood sugar and other data, or remote control of medical equipment for diagnosis and treatment, as well as the hospital's electronic medical record system/information management system, they are included in the scope of health software. Software as a Medical Device (SaMD) is a health software that is not intended to run on a dedicated hardware device.
Whether it is SaMD or health software, the development process and safety requirements need to be defined "in advance" by appropriate standards. For manufacturers, the entire life cycle of software needs to be considered, including product design, development, installation, verification, validation, maintenance, and processing, etc. The level of impact on patient or public health must be considered during the life cycle of the product and whether software as a medical device is treating/diagnosing or informing on clinical decision.
In fact, there are significant differences between SaMD and health software under the framework of regulatory requirements, including whether the actual software manufacturer is a medical device manufacturer in the strict sense or a general software manufacturer, as well as the intended use, intended environment, and usage scenarios.