The first thing to do is to create an intuitive data interface ("dashboard"). We can all glance at the dashboard of our car and immediately recognize any system failures, our speed, and so forth. The medical data display should be at least as intuitive. I don't believe the end product will be a set of graphs. Perhaps it would be a human outline with a danger signal superimposed over the organ system that is failing. Or perhaps the organs would be "grayed out" when normal and "highlighted" when they were in an abnormal condition.
Hope to see many more such examples of sharing technological best practices across domains for good reasons.
So, is a doctor's job going to get easier with this tool as it is easier for a pilots to fly the plane equipped with the modern, sophisticated auto-pilot?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.