Introducing Startup FDA: Demistifying FDA submissions through Open Source
themacro.com
themacro.com
The hardest part has been to clearly define what experiments we need to run on our product for the FDA to accept it. There is nothing inherently difficult about this, but the problem is the lack of available information and feedback cycles to get the information.
For example, the FDA has a feedback process called 'pre-submissions'. This is good, but the problem is the cycle to ask a question and get an answer is 3 months.
I'm happy that there is a growing group of entrepreneurs working within the regulatory system. Hoping to see more tools soon.
We're hoping this repo will grow as other contribute, and be a space where people can find references for various types of regulatory support.
If you'd like to contribute, we'd be happy to give you access.
Doing a 510k w.o that experience/perspective seems insane (especially for a startup(?)).
Also, I'm not sure which field you are in, but I've generally been able to access the applications from previous submissions in my field (Personal exoskeletons).
For our product category (sleep apnea diagnosis) the FDA has an unwritten rule that all devices must run a clinical study compared to existing tools.
The hard part has been extracting the exact details that would make an acceptable study in their eyes (testing environments, statistical methods...)
Also it seems like the testing standards have evolved over time and this isn't documented either. Only way we've been able to learn the standards is by giving the FDA a proposal and getting feedback on it.
We've gotten a few FOIA'ed 510ks of similar devices. Unfortunately they are 90% redacted and not very helpful.
Looking back on it, it may have been worth it to seek out a person who had gone through this exact experience before. That could have saved some time/effort.
What they did provide was a means to package our paperwork together in a way that is recognizable to FDA reviewers, and the resulting work is what you see in the StartupFDA repo.
We still had to produce all the work, and interpret the FDA guidelines on our own. It was a bit of a compromise on speed and cost, but worked for us.
Someone I know is working on a platform to help startups with FDA compliance (specifically the quality systems requirements), who I think would be complementary to this effort. Mind emailing me at brandon@cardiogr.am if you'd like to be put in touch?
It seems to me the big chunk of the problem is that my local hospital doesn't really have to compete with anyone and has rather free reign in setting prices.
Yes, there is definitely lack of competition at the provider level which has gotten worse post-ACA. But in this context I'm talking about lack of competition among technology manufacturers. Really easy to set high prices for things when competitors can't enter your market without going through several hoops. That's how you get guys like Martin Shkreli.
There are numerous costs that you can't avoid, such as lab testing, clinical trials, and fees for acquiring certifications, but being able to do more on your own as far as documentation is a big first step.
Here's an example of one for a powered laser surgical instrument (warning: 57MB PDF):
http://www.fda.gov/downloads/AboutFDA/CentersOffices/Officeo...
[1] http://www.accessdata.fda.gov/scripts/cdrh/devicesatfda/read...
Secondly, I want to let people know my company[1] works with many start-ups in the medical device space that are developing regulated products, both 510(k) and CE mark. We are engineers that understand the regulatory process not just regulatory consultants.
If anyone is interested feel free to contact me akehrer@in2being.com.