Systems engineering aims to systematically develop systems – in this context, medical devices – in the planned time and quality.
Content
This page helps manufacturers of medical devices and their service providers to gain an overview of systems engineering and to find further articles on the subject:
- Articles on processes and activities in the device life-cycle
- Articles on the IEC 60601-1 family and physical safety
- Articles on biocompatibility, sterility, and reprocessing
Definition of systems engineering
According to the ISO/IEC 15940 definition, systems engineering is …
… interdisciplinary approach governing the total technical and managerial effort required to transform a set of customer needs, expectations, and constraints into a solution and to support that solution throughout its life.
Wikipedia has also adopted this definition of systems engineering.
ISO/IEC/IEEE 21841 speaks of a process of planning, analysis, organization, development, and integration.
1. Articles on processes and activities
a) Processes
The V-model is a well-known model for the development process. It is suitable as a documentation model for the (agile) development of medical devices.
As part of this process, manufacturers carry out various activities for which further articles provide guidance. They can set up their development team for these activities and/or have activities carried out by third parties.
In the latter case, these articles are relevant:
- Outsourcing in medical technology
- Engineering service providers: successfully outsourcing development?
b) Formulate intended purpose and requirements
c) Designing systems
- Creating a system architecture for medical devices, ideally not a layered architecture
- Creating safety concepts to achieve functional safety
- Using modeling languages such as the Unified Modeling Language (UML)
- Creating designs using Computer-based Modeling & Simulation (CM&S)
- Performing threat modeling for systems that contain software for IT security
- Carrying out a design validation
- Developing software in compliance with the law
d) Verifying and validating systems
e) Further phases in the life-cycle
Notes and further information
Usability engineering and, thus, the verification and validation of usability are also part of systems engineering. You can find further information on systems engineering by clicking on this link.
Risk management is a special feature of systems engineering for medical devices. You will find an overview of articles on risk management by clicking on this link.
2. Articles on the IEC 60601-1 family and physical safety
a) Regulatory requirements
The regulatory requirements are based on EU regulations and directives:
The central standard is IEC 60601-1, which was extended by a 2nd amendment in 2019. IEC 61010-1 is relevant for IVDs.
The concepts of the standard(s) include:
- Basic safety, essential performance
- Functional safety
- MOPP, MOOP, MOP, and the IEC 60601 arithmetic
In addition to the basic standard, the particular standards are also relevant:
Many manufacturers rely on the CB Reports to provide evidence.
b) Implementation of requirements for specific systems and situations
- Systems, devices
- Components, parts
3. Articles on biocompatibility, sterility, and reprocessing
There are special standards for devices that are intended to come into contact with the human body:
ISO 17664 is relevant for the reprocessing of medical devices.
Please also refer to our article on substance-based medical devices.
Do you need support?
Do you still have questions about your medical device’s development, inspection, and approval? Then, please take advantage of our free micro-consulting service.
Would you like support in developing your medical devices in compliance with the law, testing, and authorizing their safety? The Johner Institute team will be happy to help! Contact us!
The term “medical device PC” is not clearly defined. However, most people understand a medical device PC to be Depending on the constellation, manufacturers must fulfill different regulatory requirements. These are presented in this article. 1. Case distinctions for medical device PCs Case A: Standalone software is delivered If you as a manufacturer only supply…
Details
The V-model is a development process model that was originally used for government projects (e.g., armaments). To this day, it is still anchored in many people’s minds and in standards for projects in regulated environments (e.g., medical technology, banks). This leads to disputes in teams that prefer agile development processes. This article helps to resolve…
Details
Laws and standards formulate requirements on how medical device manufacturers must define and document the development process. Notified bodies check these requirements during audits. This article on the development process provides tips on how to design the process and how to align it with other processes, such as the risk management process. 1. Development process:…
Details
In May 2016, the German version of IEC 60601-1-2:2014 (Edition 4) was published as DIN EN 60601-1-2:2016 with the title “Electromagnetic disturbances – Requirements and tests.” At the end of 2020, a new version of this “EMC standard” – modified by Amendment 1 and called Edition 4.1 – was published. 1. What is electromagnetic compatibility? a) Electromagnetic immunity Medical…
Details
Threat modeling is a “mandatory” topic for all manufacturers of medical devices that contain or are software. This is because threat modeling is a structured process for the systematic analysis of IT security risks that auditors consider to be the “state of the art.” 1. Why should you use threat modeling? Reason 1: To develop secure devices…
Details
Cytotoxicity testing can be used to test a sample to determine how much it can damage, or even cause the death of, human cells. Standards and legislation require manufacturers to demonstrate that their devices are not cytotoxic. With a good test setup, it is possible to detect whether a sample is 100% cytotoxic, i.e., highly cytotoxic, or…
Details
The Machinery Directive (2006/42/EC) is generally applicable to machines of all types. However, the directive can also be relevant for medical device manufacturers: both the MDR and the IVDR refer to it. If the Machinery Directive comes into play, requirements that go beyond those of the MDR and IVDR apply. Therefore, this article will give you an…
Details
Manufacturers of substance-based medical devices such as seawater nasal sprays, mucous membrane-soothing cough syrups, or osmotically active laxatives face several challenges once the Regulation (EU) 2017/745 (MDR) came into force: This article illustrates what can be done to overcome the regulatory hurdles and ensure the marketability of your substance-based medical devices beyond the transition…
Details
IVD medical device validation confirms the device’s medical purpose. IVD medical device verification, on the other hand, proves whether the IVD works as intended. In this article, we provide a five-step guide on how to carry out the verification and validation of your IVD medical devices in a targeted manner and without unnecessary effort. We…
Details
The same legal requirements apply to the clinical evaluation of software as to the clinical evaluation of all medical devices. This means that as a Medical Device Software (MDSW) manufacturer, you must prepare a clinical evaluation for your product just like any other manufacturer. A performance evaluation must be carried out for software that is an in vitro diagnostic…
Details