difference? what difference?

Looking at LibreClinica you may wonder: 'what is this all about? it looks and feels like OpenClinica to me' and all we can say is: 'correct'. And the reason for this similarity is that we used the code-base of openclinica, version 3.14 in fact, as our starting point for LibreClinica. We spent about 18 months and the result has all the functionality and the design of OpenClinica.

and you spent 18 months on that?

It may sounds ridiculous to say that you have spent months of work to come up with something that already existed, but all the differences are under the hood.
An application like OpenClinica isn't built from scratch but uses extensive building-blocks or libraries. This makes the process of developing not only efficient, but also secure, because these libraries are regularly updated to fix bugs and security risks. In the course of years the number of libraries involved has grown to 100+ and some of these have been in the code from the start, so around 2003.

ok, so we're up-to-date; now what?

Getting all libraries up-to-date was a task, because a lot of code change was involved. But now that this is in place, what does it mean? First of all it means that you can use the latest version for your operating system of choice and have the latest versions java, tomcat and postgresql. Many people will be relieved to hear that. Well, maybe not 'many people' but definitely 'many system operators'.

so my it-team is happy; who else?

Not only the server-team will be pleased with LibreClinica, but also your programmer. We hope to give her an opportunity to contribute to the code, using the normal github-way-of-working. And we are convinced that there are many programmers willing and able to contribute, so the real change has just begun.
Equally important: your security officer could be happy with LibreClinica, because starting from version 1.2 it has the option to use two-factor-authentication.

this page was last reviewed January 2023