We validate our software to ensure the highest quality and security standards. Our validation process is risk-based, complies with regulatory requirements and is designed to minimize the effort for our customers.
Full initial validation:
Before the first release, our software was comprehensively validated according to the IQ/OQ/PQ model. All critical functions were identified, tested and documented.
Re-validation in the event of changes:
Every significant change (major version changes) triggers a so-called risk revalidation assessment. We check whether existing risks are affected or new risks arise. If necessary, tests are adapted and carried out again before an update goes live.
Automated and manual tests:
Our validation is based on two main types of tests:
Unit and end-to-end tests run automatically for every change before each deployment (pipe) - even for minor updates.
As a matter of principle, no change in our software goes live unless it has been covered and passed these tests.
Due to the high configurability of our solution, many different application scenarios arise. Not all of them can be technically mapped automatically. We therefore supplement our automated tests with manual tests in particularly complex or individual use cases.
Careful documentation:
Every validation is fully documented. This includes
Our documents are maintained in traditional Word and PDF formats and are available on request.
We know that validation requirements mean a lot of work for many customers. That's why we take a large part of the work off your hands with our pre-validation. Our documents are always up-to-date, complete and comprehensible so that you can easily use them for your own documentation or official requirements.
If you require additional specific information, we will be happy to provide you with individual support.