My understanding is that they don't review the code, but they do review all of the validation that goes into making sure the code does what it should.
[1]http://www.fda.gov/RegulatoryInformation/Guidances/ucm085281...
But I also know that the FDA is a massive organization, and there's no reason they couldn't hire for this specific purpose. But then the cynic says that government pay grades may not be up to snuff.
See the HCA rollout and subsequent rewrite.
Sorry, that was a long way of writing, "I don't know".
Think about that for a minute. There has been an official government review process for safety of computer controlled airplanes since the 70s, and a good decade for medical devices (likely earlier) 10 years earlier than the WWW existed.
I think it's kind of funny that you'd think that you were doing it better than production life critical systems THAT CAN ACTUALLY KILL PEOPLE that have been around at least ten if not 30 years longer than the tech you likely (sorry assumption) base your career around.
Your overall point is well taken, but maybe put a little more thought into the examples you pick to support it...
If they really wanted to, they could sidestep the pay issue as every other government agency does, by hiring contractors.
EDIT: Not sure what's up w/ the downvotes. There are well-established ways for regulatory agencies (whether FDA, FCC, etc) to obtain firmware for devices -- and it almost always involves a warrant under extraneous circumstances -vs- proactively receiving proprietary code.
Similarly, what about testing for drug quality? You could even extrapolate it out to the SEC's right to examine a private financial transaction in order to determine legality. Or the IRS's right to inspect one's taxes to determine compliance.
Point is (IMO) there is a need put on government by society to bypass some of our "Inalienable" rights. In most cases this societal decision is necessary and makes sense, and I'm arguing that code inspection of life-critical systems is a reasonable example of such a case.
In normal auditing, they will not inspect your source code - they may inspect everything around your source code (what you procedures for changes are, how you do your testing, etc etc).
However, I believe there's a general understanding that if you fuck up, your source code will be open to inspection - along with everything else. Cause you'll either voluntarily surrender it in hopes of getting on the FDA's good side, or cause they'll subpoena cause you killed someone.
Hold it right there, Karl Marx. We can't just be giving the proletariat access to the means of software production because of one little boo-boo. That could totally bankrupt a company and would be a theft of IP. Rest assured that the proper procedures will be followed and the flaws corrected, but under no circumstances can we take the lawful property of entrepreneurs and daring businessmen.
We never got that. For the most part, checking that we followed what we wrote down involved reading more documents that said that we did what we wrote down. The auditors weren't even allowed to walk around freely in our office, nor even be left alone without supervision, and we were all carefully coached on how to answer interviews with non-compromising responses. "I do what the SOP says. I cannot quite recall at the moment, but if you let me refresh my memory by reading the SOP, I will gladly clear it up for you."
It's just smoke and mirrors to pretend like important testing took place. Probably also to make sure whom to blame when things go bad. Some testing does frequently happen, between the document writing about the testing.
I guess that they function as regular police do - the actual experience is less than ideal and leaves a lot to be desired, but without any at all, the world would be horrible.
The FDA probably doesn't even know what source code is. They have vague regulations on how medical devices should be tested, which by tradition has been interpreted in a particular way to mean certain kinds of documents have to be prepared. There are auditors that check that those documents are written. Nobody checks that what the documents say about the software is in fact true because neither those writing the regulations nor those auditing the documents really know anything about computers.
Did the FDA actually check your software or just your documentation? Did the auditors very carefully grill you or just languidly ticked off boxes on a form? Did you find the process of writing documentation instrumental in ensuring that your software was carefully tested? Did you ensure that your tests were reproducible and comprehensive?
None of these things were done very carefully in our case. My superiors were very insistent on the documentation and were quite proud of the quality of our software but they mostly never had any interaction with it and had no real idea of what we did for software validation. They were more concerned with making sure signatures and dates were correct and that our documentation didn't make us look bad.
I think the audits must look more impressive when you're in charge, but as the one actually writing the software I was thinking... that's it? The FDA doesn't really give a damn about what I really worked on, do they?
Class III devices (pacemakers, deep brain stimulators, insulin pumps)
> Did the FDA actually check your software or just your documentation?
In a submission, occasionally. In an audit, it depended on the nature of an audit. I've been part of one audit that was due to persistent SW failure and yes, they checked code.
> Did you find the process of writing documentation instrumental in ensuring that your software was carefully tested?
No, but that's not really the point of documentation.
> Did you ensure that your tests were reproducible and comprehensive?
Yes, we could kill people if we screwed something up.
> They were more concerned with making sure signatures and dates were correct and that our documentation didn't make us look bad.
This practice is common, I grant. Doesn't mean it's universal or right.
> The FDA doesn't really give a damn about what I really worked on, do they?
FDA heavily triages activity based on risk. If your product is life-sustaining they will definitely be all up in your business.