“Built for the rigors of the fast-paced medical environment, Samsungâ€™s Chromebook 2 lineup offers a choice of processorsâ€”the Intel Celeron or the energy-efficient Exynos 5 Octaâ€”and up to 4GB of RAM for speed and performance. The devices can last a full hospital shift, with up to 9 hours of battery life, and every laptop in the series features a metal-reinforced chassis to withstand the wear and tear of daily use, as well as falls and drops.
Last summer, Chapters Health System, a provider of post-acute, palliative, and hospice care to patients in West Central Florida, began looking for a solution that would give its cadre of nurses and clinicians in the field more secure and affordable access to records and electronic charts as they make their rounds to hospitals, nursing homes, assisted living facilities, and private homes.
Chapters Health Systemâ€™s IT leaders began the process democratically, by polling 139 caregivers on their preferences for devices and applications. The results came back strongly in favor of Chromebooks for form factor, battery life, ease of use, speed, and performance of virtualized applications such as Microsoft Outlook and clinical applications, as well as Web-based apps.
Chromebooks beat out not only traditional laptops, but also Windows thin-client devices and the Apple iPad tablet. Ninety-two out of 139 caregivers who participated in the study voted the Chromebook as their favorite device for work.”
SeeChromebooks in Healthcare: Good for Patients and for Bottom LinesAs I’ve pointed out repeatedly thin clients work for almost anyone not generating huge quantities of multi-media stuff locally. Schools, banks, clerks, medical staff… They all have one thing in common. Most of their data is best kept on a server somewhere so why not their applications as well? Whether the applications are web applications or something GUI that could be provided by a desktop, it can also be provided by a rather thin client device, even a Raspberry Pi, it turns out.
Amazing. Just a few years ago I was called a nut-case or tyrant because I recommended thin clients and now the grand-daddy of thin clients on That Other OS is recommending thin clients on GNU/Linux, and schools, governments and health-care are adopting them too. We’ve gone from accepting gross inefficiency and duplication to admiring efficiency and minimalism. Further, That Other OS and Intel need not apply… Are we there yet?
Not quite. There are still a few hills to climb and bends in the road but eventually the huge installed base of the Wintel cash cow will be whittled down to size. */Linux now has lots of OEMs, developers, retailers and salesmen, enough to matter, a lot. Chuckle. I’m enjoying the reemergence of competition in the market for IT. It’s refreshing and much more efficient. I like that. I too will probably replace my ageing server, Beast, and my thin clients with ARMed small cheap computers that will consume a similar amount of power as a good hard drive and cost about the same.
On a side note, one of the issues with my system and the ARMed motherboards is that they are limited to 2-4gB RAM. Beast should have 8-16gB… Another issue is that FireFox has problems sharing the load amongst CPUs, so one process hogs the CPU on which FF is running and everything can grind to a halt. This is an ancient bug in FF. There is finally an effort to fix that. The Electrolysis project is ongoing. The “ShaderToy” site does not lock up other tabs on Chrome browsers… Perhaps I will have to go back to Chrome browser in order to use these ARMed clusters effectively or wait until they have more RAM, a lot more. I can also pin TLW’s FF process and mine to different CPUs using TaskSet. With a cluster, I could easily put the two processes on different motherboards but it would be better still to use all available cores rather than just one core on each motherboard.
I’m optimistic all these problems will be fixed in the coming year.