FDA permits marketing of AI-based device to detect diabetes-related eye problems
51–60 of 104 posts
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#52Ultimately, you will need a doctor somewhere along the diagnostic process so that someone is there to assume liability for incorrect diagnoses.
What's crazy is that if AI is better than doctors by some significant degree, what do we do when the doctor and AI disagree? Like if doctors are right 85% of the time, but the AI is 90%. I guess we treat it as another doctor? Like if we have 4 opinions that agree, we go with that one regardless of the source of those opinions (as long as they meet some minimum competence threshold).
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#53Ultimately, you will need a doctor somewhere along the diagnostic process so that someone is there to assume liability for incorrect diagnoses.
What's crazy is that if AI is better than doctors by some significant degree, what do we do when the doctor and AI disagree? Like if doctors are right 85% of the time, but the AI is 90%. I guess we treat it as another doctor? Like if we have 4 opinions that agree, we go with that one regardless of the source of those opinions (as long as they meet some minimum competence threshold).
Though even in those cases, you might be looking to show that your tool agrees with physicians at least as often as physicians agree with each other. Malpractice is usually about failing to offer the standard of care, and if you can show a reasonable level of concurrence with the standard of care in research and trials, you may be able to move forward and reach those higher levels of accuracy.
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#54Ultimately, you will need a doctor somewhere along the diagnostic process so that someone is there to assume liability for incorrect diagnoses.
What's crazy is that if AI is better than doctors by some significant degree, what do we do when the doctor and AI disagree? Like if doctors are right 85% of the time, but the AI is 90%. I guess we treat it as another doctor? Like if we have 4 opinions that agree, we go with that one regardless of the source of those opinions (as long as they meet some minimum competence threshold).
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#55Earlier quoted context omitted.
Generally, the FDA (or the government body responsible for certifying medical devices) does not conduct code reviews in the sense of looking at the code and trying to find bugs. The way it works is: the manufacturer of a medical device assesses the harm that can be caused by a software malfunction, and assigns it a safety classification (class A, B or C). Class A is used when no injury is possible, and class C is use…
> class C software it requires whitebox tests as well What does this mean?
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#56I wonder what factors made this decision possible? I love the idea of automated diagnosis but the performance rates are 87% true positive and 90% true negative in the article. Seems a bit low. Maybe people aren't getting diagnosed at very high rates? That would be a reasonable justification for deployment with somewhat less than perfect accuracy. Anyone have any insight?
The status quo is screening at the eye doctor. This enables screening at primary care visits. People mostly go to primary care more often than the eye doctor. The medical risk is that people will forgo other screening for 12 months when given a negative result. The cost of additional screening for false positives is the other big downside (this is all the machine does, recommend a specialist visit or to rescreen in a…
Really? Standard advice is 1/yr for both.
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#57Does the FDA conduct code reviews? And how do they guarantee that the code or the training data does not change over time without them knowing?
Generally, the FDA (or the government body responsible for certifying medical devices) does not conduct code reviews in the sense of looking at the code and trying to find bugs. The way it works is: the manufacturer of a medical device assesses the harm that can be caused by a software malfunction, and assigns it a safety classification (class A, B or C). Class A is used when no injury is possible, and class C is use…
More generally, the regulatory body will be looking for you to have a formal engineering process in place and be able to demonstrate its efficacy. Part of that will be looking for how you do hazard and risk analysis, how you handle CAPA (corrective and preventative actions in FDA-speak), how you do system trace, design history file generation, etc. etc. That you have a software development plan and can demonstrate how you follow it.
So they aren't really interested in code reviews per se, but they are very interested in how you view code reviews, how you perform them when you do, what gets documented, how you perform trace an V&V etc.
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#58Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#59Does the FDA conduct code reviews? And how do they guarantee that the code or the training data does not change over time without them knowing?
In general though approval to market for particular indications is for one fixed configuration of a product, so your model parameters won't change.
All of this is in the process of being hashed out, but I expect for a while at least if you are doing on-line learning it will be in non-clinical configurations only and you will end up releasing an update periodically. Depending on the changes this may need a new 510(k) or not, but would definitely need a formal release.
Re: FDA permits marketing of AI-based device to detect diabetes-related eye problems
#60I read that as .87 accuracy, .9 specificity (True Negative Rate). However, I can't find in the link provided in the article above the sensitivity (recall or True Positive Rate).
I'm guessing it goes a bit like this (assuming perfectly balanced classes which in reality they aren't):
Predicted + Predicted - Total
Actual + 378 72 450
Actual - 45 405 450
-------------------------------------
Total 423 477 900
Accuracy: 0.8700
Error: 0.1300
True Positive Rate: 0.8400
True Negative Rate: 0.9000
Precision: 0.8936
Recall (TPR): 0.8400
F-Score: 0.8660
I'm not sure how good or bad is 10% false positives and 16% false negatives are for that kind of diagnosis. The linked trial page says that 40% of diabetes patients have some degree of diabetic retinopathy (DR), that early treatment reduces vision loss "by as much as 52%" and that only some 50%-60% of people with diabetes have a yearly eye exam.Off the top of my head, it looks like automated screening will do some good and probably more good than harm, but without knowing how doctors judge good vs harm there's no way to know for sure how useful this device will really be.