“Ah, yeah… I’m okay, but my portable device just died.” “Your portable device, sir?” “Yeah, the portable medical device I use to monitor my vitals.” “Sir, let me connect you to a software developer who knows a thing or two about power management.”
There are portable devices and then there are portable medical devices. And while the malfunction or sluggishness of your smartphone might annoy you – its slow operation is not a detriment to your health.
Not so with portable medical devices. We live in an age where people are beginning to use portable and remote electronic devices to monitor and maintain their health at home – away from the hospital or doctor’s office. This equipment needs to transmit critical data to the health practitioner or facility, quickly and reliably.
In this newly created white paper by my colleague Andrew Caples, you’ll learn about the important role software development has in developing portable medical devices. Concepts such as mean time between failures (MTBF), failure in time (FIT), and acceleration factors, are discussed. Today, in order for a portable medical device to succeed, the software must be designed-in from project inception so it can effectively use and manage the power-saving features available in the hardware.
Mentor’s Nucleus RTOS offers an extensive Power Management Framework to provide efficient power management of portable medical devices. Andrew goes into great detail on how software developers might benefit from using this feature. Addressing SoC complexity is also discussed.
Device failure is not an option when it comes to portable medical devices. I hope you take a moment to read this paper.
Let’s do our part to make sure 911 calls are for humans, not machines.