The LINCOR Patient Engagement System is a great idea, and well-implemented, aside from one unfortunate engineering decision:
1. Depending on wireless communications for TFTP/PXEBoot payload delivery for boot. (If the connection is wired then there's a hardware problem with the network adapter.)
My terminal is aparently on the edge of nearest wireless router, either that or there is a problem with this terminal's network adapter.
There are apparently no support services offerred to this hospital by LINCOR to troubleshoot and address system faults. They sent an electrician when I mentioned there was a problem with my Terminal.
The strengths of the system are mainly built on the reliability and efficiency of Debian Linux, without that, these systems would be exponentially more problematic.
TFTP/PXEBOOT is another stellar feature here making updates and feature implementation highly efficient. As well as troubleshooting nearly always coming down to networking or the network adapter.
Let's get this hospital a bit of help ironing out the networking issues that might be making staff feel that the problem is the system, instead of it actually being a few weak point in the general network stability.
If certain systems are having more problems than others, then check the networking to those systems either wired or wireless. Put a Status Module on the Application menu that lets savvy staff see if the network bandwidth and stability are sufficiently robust. Allow a tech-minded support staff to be able to patch in with a cable for systems that aren't remaining stable over wireless, at least for diagnostic purposes.
Let's show them that Linux is definitely the way to go.
"LINCOR Patient Engagement Terminal"
About: Busselton Health Campus Busselton Health Campus Busselton 6280
Posted by Splurben Bunyip (as ),
Do you have a similar story to tell?
Tell your story & make a difference ››
Responses
See more responses from Matthew Vomiero