MRI read outs are 3d, so can't be printed for analysis. They are gigabytes in size, and the units are usually in a different part of the building. So you could sneakernet cds every time an MRI is done, then sneakernet the results back. Or you could batch it and then analysis is done slowly and all at once. OR you could connect it to a central server and results/analysis can be available instantly.
Smarter people than us have already thought through this and the cost-benefit analysis said "connect it to a server"
Oh my god, round and round on this topic. Leave it alone. Copilot is an amazing tool and demo of what AI can do. I will happily pay for good ML products, which a notoriously hard area to monetize.
Copilot may produce results from the training set, but if you're letting it do that, that says more about you than about copilot.
All of these claims use the example "Write me a function to foo the bar that takes baz as an argument". If you prompt it to write entire functions and classes for you, then it will lean on its training set.
But if you actually just write code, then it will complete small single lines in exactly the style you've previously written. With code that is unique to your program because it can synthesize new code.
In this role copilot is no different than a search engine. By prompting it lazily, copilot isn't the one stealing the code, you are.
Then go write your own opinionated article on your blog. For myself, I was already thinking about trying to develop a package and this gives me a nice starting point for doing so even if I don't use all the same tools to do it.