SheeEttin
Sounds like a weak argument. They're not going to be inclined to operate a local ML system just for one or two people.
I would see if you can get a quote for locally-hosted transcription software you can run on your own, like Dragon Medical. Maybe reach out to your IT department to see if they already have a working relationship with Nuance for that software. If they're willing to get you started, you can probably just use that for dictation and nobody will notice or care.
What, exactly, are your privacy concerns about this?
I would expect any browser to properly render a page, regardless of platform. Are you sure the page is mobile-friendly? Why do you say it's "not great"?
That's not busy work. Busy work, as explained in the article, is work that doesn't really accomplish anything, like re-folding towels that have already been folded. Or as I've had to do before, sweep a perfectly spotless sidewalk. Data validation is valid work.
How confident do you need to be? I don't think I've seen any convincing evidence of any firmware spying in PC components.
Well, except the NSA's Clipper chip, but I don't think that really ever got implemented.
Long story short, I can’t use multiple monitor RDP because I have different resolution monitors and they are stacked 2x2 instead of all in a row.
Did you try setting them up as one big display across all four, instead of four little ones? I think that's something you can do.
Does the multi-mon RDP thing work from a Windows client too? I'd be surprised if it did, Windows' multi-monitor support is fairly lacking in my experience too.
This doesn't have anything to do with patient data and everything to do with pharmaceutical companies abusing care platforms.
Yes, and? They are not sending your PHI to Microsoft.
Or, if they use Microsoft cloud services like 365 or Azure, where they are sending PHI to Microsoft, Microsoft agrees to follow local healthcare information protection law. In the US, as a business associate, they are a covered entity under HIPAA and must maintain compliance to protect your information.
If it ain't broke, don't fix it.
Why not run sed and pipe to diff to preview changes?
You'd still have to manually copy out the command line to a notes file, but I don't think that that's too terrible. You could use a terminal-integrated snippets palette to make it a little smoother.
I'm not aware of any program that does exactly everything you want it to, so you might write your own or extend an existing one, as mentioned.
Mounting or unmounting a filesystem won't make a difference for drive longevity.
If you want to keep your backups secure, you want to keep them offline, so if you get ransomware it doesn't encrypt your backup too. (Or if you just mistype a command and target the wrong device, folder, etc.)
But drive motor starts and stops are when the most failures occur. So the ultimate question isn't how to make a drive last longer, it's how you plan to handle it when the failure inevitably occurs.