@Scaevolus so very true. I use to work in this field. I was the IT director for a small pharmaceutical company that produced prescription creams and ointments and worked with a nearby university to work on new drugs.
My role was to develop the custom software that ran on laptops we gave to hospitals involved in the clinical trial. In the drug manufacturing world, anytime computer software is used in a clinical trial or in the tracking of drug production, you have to have the software validated.
Software validation is basically a process by which you hire an outside company to go over what your software does. Similar to an ISO certification. The folks & companies you hire are very clueless... They know enough buzz words to ask good questions but they often over look things.
Anyway, long story short, the whole process of just collecting data is riddled with security problems. None of this, as far as I know, is exposed to the public either. So if buggy software is, somehow, corrupting test results, there is not feedback loop to correct or discard the data. Companies like the one I worked for at the time, would throw out the data as a policy and start over. Hence, very expensive situation and very crucial to make sure your systems do the right thing the first time.
This was in the late 90s and in one situation I was in charge of some software that we were developing that was expected run past Y2K. Back then there was a lot of hoopla about the Y2K century roll over and what it would do to computer systems.
The company we hired validated our software for Y2K use cases but they often over looked basic things like data encryption, plain text storage of user passwords, etc...
I imagine the validation companies have gotten better over the years but in the end I learned that software validation is nothing more than a big CYA tactic. It's a paper trail to try and claim we did our due diligence if the shit were to hit the fan.