Well, I wonder why they even train physicians to read those scans then anyway - If a computer software program will do it.
Things are moving that direction faster than most people realize. In large part because the systems learn from the human physicians - every diagnosis the system missed, every false positive, becomes fodder for the database, a tweak to the AI.
The first gaming computers lost to chess grandmasters, and it took a long time and many evolutions, but then eventually the AI bested the humans. The same will happen with computer-interpreted diagnoses. I've already seen huge leaps in progress in my field since I was installing the first generation in the 90's.
This is a good thing, a wonderful thing.
And already a large percentage of the interpretations made by the human physicians are no longer being transcribed, but rather fed through a voice-recognition engine - which again took a while to evolve (believe me, I've had to
uninstall a few), but are now more accepted than not.
However, I do feel a lot more comfortable just being able to plan out my dives ahead of time, even if I might not stick exactly to my plan.
My computer already allows me to plan a dive, and "walk" through it. But I'll concede that function just isn't quite "there" yet. I think features like this will evolve to be even more flexible, useful, and powerful.
I am engineer, so yes I do understand the value that computers add to our everyday lives. But I also understand the need to know how and why the computer is giving me the results that it is.
Agreed, one should understand the limits of whatever technology one is using, whether it's a computer or a sextant. Or even a simple compass, a lesson I learned when failing my navigation checkout dives due to being too close to an old wreck that was skewing my readings.
Also agreed that
someone must understand how and why the digital system functions - but that throws the technological knowledge required back to the physical and physiological theories behind the tables, not the tables themselves, which are already just a crude compromise.
The hardware and software engineers always have to know the science and technology - and I've worked side-by-side with engineers my entire career and have great respect for them.
A GPS has to calculate position based on minute timing and phase differentials between satellite signals, for example. But
I don't want to do those calculations myself, I'll leave it to them - let them do what they're trained to do, and trust the device, also knowing its limitations. Likewise, I don't have to know how to calculate safe times using the modified Haldanean algorithms in my PDC, but I trust the technology and the engineers, and am also aware of the computer's limitations, what it can and can't do (like predict my future changes in depth).
But when it comes to performance in the field, I know my personal wetware CPU is affected by narcosis - even before I am aware of the effects. But the silicon CPU in my computer is not. So I also know which one I tend to trust more at depth.
>*< Fritz