Agreed on Kyocera. Once we moved to them for the majority of our clinic's printing, we had a measured 90% decrease in printer problems. It also is a good idea to find a local printer maintenance company that specializes in Kyocera printers as I have found that when there is a problem it is generally a worn out part that is causing it. Which speaks volumes about the quality of the printers as they wear out before they break something. I have never seen them fail to the point of disabling the printer without having printed well over 10000 pages first. Our current Kyocera with the record for the most pages printed is somewhere above 1 Million pages printed.

As someone that works in Healthcare IT, you nailed it. If the software has no effect on the actual treatment of the patient, then it doesn't have to have ANY certification. If your software effects the treatment of the patient but not actually controllling the treatment, like radiation treatment planning software, then the software must be certified and must run on FDA approved hardware with the trusted platform module chip present and in use. If the software actually controlls the treatment, then the software, hardware, interfaces, and attached/associated systems must be FDA approved.

Roman/Greek Gods and Goddesses... There's nothing like SSHing to Zeus or a quick telnet into Athena...

from a man armed with a piece of fresh fruit.

So from the start, the internet caused computers to crash... seems like a bad omen to me...

This has been going on there for YEARS! I mean really just look at what a simple search returns on this subject.