Technology Transfer of prototypes based on CamiTK
FDA Guidelines / CE normalization for Off-the-Shelf software
(inspired by VTK and ITK guidelines)
CamiTK has to be considered as off-the-shelf (OTS) product for supporting a higher level medical application orproduct. The developer of such applications or products will be responsible for performing the validation process described in FDA published guidelines or CE normalization process for the development of software-related medical devices.
CamiTK is intended to be used as elements in medical applications, those medical applications are the ones that can be subject of an FDA approval / CE normalization. Whoever develop such applications has the responsibility of validating their application in order to demonstrate that it is appropriate for the advertised purpose.
For example, if you develop an application for radiation treatment planning based on CamiTK, it is your responsibility to validate that application. In the process you will have to validate that the use you make of CamiTK satisfies the requirements of your application. You will probably be using a limited set of CamiTK functionalities in such application, therefore what you have to demonstrate is that those specific CamiTK functionalities are behaving as expected in the context of your application.
Note that not only you need to validate the use of CamiTK, but also the use of any other off-the-shelf (OTS) software product used in the development of your application.
That will included things like:
- Your operating system
- Your compiler
- Your OpenGL library/drivers
- Any other library that your application is linking to
- Even your processor
Get Support
The CamiTK project team has a long experience in technological transfer of CAMI prototype. Do not hesitate to contact us for advice and support.
CamiTK Software Development and Good Practices
It is worth pointing out that the Software Development Process used to develop the CamiTK project are already following many of the FDA Guidelines / CE normalization for software developement.
In particular CamiTK uses:
- Configuration standardization: we use CMake and developed a lot of easy to use helper macros
- Version control: we use git
- Continuous Integration (CI) and testing: we use gitlab CI pipeline, see also the project CI dashboard
- Bugs and issues tracking: we use gitlab issue boards
How can CamiTK help you?
CamiTK offers a number of tools to simplify the transfert of your technology:
- definition of software units are at the base of the architecture: all software units are clearly identified within your extension (e.g. algorithms and process are encapsulated in actions, each action has a list of parameter that are named, described and well typed,…)
- automatic integration test generation: this is one of the most difficult tests to develop and CamiTK provides this automatically.
And much more!
General Guidelines
For details on the FDA Guidelines / CE normalization for development of software for medical devices you must look at the following documents:
- [PDF] The international standard IEC 62304
- ISO and IEC standards for software in medical devices in a nutshell
- Off-The-Shelf Software Use in Medical Devices
- [PDF] Guidance for the Submission Of Premarket Notifications for Medical Image Management Devices
- Guidance for FDA Reviewers and Industry Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices
- [PDF] Guide général pour la mise sur le marché de dispositifs médicaux sur mesure (in french)
See also
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.