Slashdot Mirror


Integrating A GUI Into An Existing Medical Device

Roland Piquepaille writes "As I'm not quite familiar with medical devices, I was fascinated by this long article from Medical Electronics Manufacturing. It tells us that "new technology makes graphical user interfaces (GUIs) a fast and cost-effective way to add features and improve on existing designs" of these medical devices. And it really looks simple to use. You just need a standard PC and an HTML authoring tool to develop your GUI. It is then compiled in micro-HTML and embedded in silicon, leading to a graphical OS chip which doesn't need to be powerful or have tons of memory. "The GUI shipped with the Amulet Technologies starter kit, for example, contains almost half a megabit of information in HTML. When all of the gifs, widgets, and other files are imported and compiled into micro-HTML, the file size is reduced to a mere 66 Kb of memory." This overview contains more details and a photograph of such a GUI at work."

27 of 129 comments (clear)

  1. Micro HTML eh? by nizcolas · · Score: 4, Funny

    How long before we get the first micro pop up ad?

    --
    If you get an error, type "OVERRIDE" or "SECURITY OVERRIDE" and then try the optimize command again.
  2. Re:Code blue (screeen of death) by Scott+Hale · · Score: 5, Funny
    the file size is reduced to a mere 66 Kb of memory

    I doubt that's Windows

  3. Who wrote this? by JoshuaDFranklin · · Score: 3, Insightful
    Jim Todd is director of sales and marketing for Amulet Technologies

    Makes you wonder if any of it is true.

    1. Re:Who wrote this? by Anonymous Coward · · Score: 3, Informative

      It pretty much is. He's a nice guy too.

      I'm working on a commercial product using Amulet Technologies' chip (really!), and it's very nice. The compiler could be a bit more verbose, and you could have a bit finer grained control over the functionality of the GUI module, but the rapid development and ease of coding are really quite good. You can whip together a GUI very, very quickly, using HTML and standard graphics files. There is a dizzying array of functionality available - wiping graphics such as the shown thermometer, line plots, numerical displays, all kinds of great stuff - all through a serial port and a simple protocol.

      I know it's uncool to say good things about non-GPL'ed commercial companies jere (aside from Apple for some strange reason), but this is a very cool product for rapid development.

    2. Re:Who wrote this? by westendgirl · · Score: 5, Informative
      I'm a marketing freelancer & consultant who frequently ghostwrites articles and success stories for companies. It's unlikely that the director of marketing wrote the article. More likely, a coordinator or specialist wrote it -- or they outsourced to a freelancer. So you're not even getting the goods from a senior manager. :)
      In fact, even when you see an article with a byline that credits an engineer or other techie, there's a huge chance that someone in marketing wrote it. This doesn't mean that the article is garbage. It just means that they interviewed the techs and wrote it up. The tech people still have to sign off on it. When something that isn't true goes through, I find it's often because the techies weren't willing to take the time to read it through before signing off on it. Of course, I admit that sometimes the marketers go off on a Dilbert-style tangent. But that's often because no one takes the time to read their stuff before okaying it!
      Still, I have to admit that Amulet took a bizarre step in crediting its marketing director. Usually, you could find *someone* in R&D to take the credit. ;)

      --

      -- SYS 64738 --

  4. Slight problem with the compression by heironymouscoward · · Score: 3, Insightful

    From "almost half a megabit" to 66kb?

    500,000 bits is 62,500 bytes.

    I hope they meant 0.5 megabytes.

    --
    Ceci n'est pas une signature
  5. Cannot avoid thinking of Therac by EggSausageBaconAndSp · · Score: 4, Insightful

    I cannot read such an article without thinking of the Therac-25 catastrophe (several people being killed or severely injured because of a poorly designed X-ray device).

    My 2 cents: When developing a medical device, don't focus on a nice'n'cool UI, but on safety.

    1. Re:Cannot avoid thinking of Therac by nickd · · Score: 3, Insightful

      Safety does also include making it easy and intuitive for people to use it so that they can operate it safely..

    2. Re:Cannot avoid thinking of Therac by more · · Score: 2, Interesting

      Safety and ease-of-use are interconnected. I participated in a project where we did replace an old text-based menu system (designed in the 1980's) using a tcl/tk on top of a largish medical Fortran-based simulation and planning system. I am pretty sure that the gui actually made it safer to use. The selection of tcl was done at a time when python was still at 1.3, and leaked memory like hell. Today, I would choose Python for the gui-building tool, if I would have to add a GUI to a system like that. However, even the tcl/tk conversion was a success story. The company got millions by selling the system, the gui giving a significant boost to declining sales, and the project was ready earlier! than was anticipated.

      --

      -- Imperial units must die --

    3. Re:Cannot avoid thinking of Therac by mongbot · · Score: 2, Insightful

      I was just at a lecture about the Therac disaster. The fact that it had a bad, uninformative UI was a factor in the disaster. In no way was it "nice'n'cool".

      It was text-based, and you basically pressed particular keys to get it to do things (for example 'e' put it in electron mode, 'p' performed a pulse, I think.) The problem happened when the technician kept pressing a key, thinking that an error had occurred and that nothing was happening. Meanwhile the patient was getting painfully zapped by the Therac. (Incidentally the video and audio link to the patient was broken.)

      A GUI would have been able to show the internal state of the device and the concurrency problems would have been more obvious.

      I KNOW this is slashdot, and I KNOW that most people here probably think a UNIX command line is better than a proper GUI, but for non-programmers, such as medical technicians, a GUI is far better way to interact with complex devices. I'd much sooner that my doctors were using devices with GUIs rather than cryptic key sequences or commands.

  6. Actually, many do run MS OS's by eericson · · Score: 4, Informative

    You'd actually be suprised how many systems run Winnt or 98 as their OS. A good example are the Siemens Allegra series ultrasound systems (mid range, specializes in General Imaging, not cardio). They run WINNT as a backend with a custom app handling HW interaction. (Which is causing an interesting political battle with their Semi-Recent aquisition, and my old employer, Acuson. All of our systems ran a custom build of Linx OS as the OS with UI in X11.

    Most of the MRI, CT, and PACS systems are built on industrial grade Unix OSs, but you'll still see a ton of MS around on the lower end devices.

    --
    The evil monkey commands you to dance.
  7. I worry... by littlerubberfeet · · Score: 3, Interesting

    How robust is this? I hope they are using QNX or VxWorks. I do think that a GUI could eliminate some errors and make training easier.

    an application:Centrifuge. One company evaluating a GUI has a significant stake in the centrifuge market. Its design teams' core competencies are motors and speed control.

    As the centrifuge spins too fast and destroys the samples. Maybe destrying DNA evidence and getting a death row inmate killed.

    Newly available technology enables medical device manufacturers to avoid additional costs and design complexity without sacrificing time to market

    Are they more worried about medical safety or time-to market?

    --
    Sig (appended to the end of comments you post, 120 chars)
  8. Think of the Children! by tsanth · · Score: 4, Interesting

    I could see how something like this could be useful, particularly when building devices which will be used primarily by children: acute asthma sufferers, for example, are told to take daily spirometer readings. The problem with this is that many children will either forget or refuse to take the readings.

    Much of the time, children will visit their asthma doctor having "forgotten" to take their daily readings. To make up for it, they take a dozen or so readings right before the appointment: the data is flawed and as a result, treatment suffers. With cutesy GUIs like this integrated into the spirometer, children can look at their daily readings as more of a game than a chore.

  9. from the finger-painting-dept. by Merik · · Score: 3, Funny

    A graphical OS chip eliminates the need for a marketing manager to possess a certification in C++ or other programming languages to develop the GUI. Rather, all that is needed is a PC, a commonplace text editor, and perhaps even the most basic and widely available graphics programs, such as Microsoft Paint.

    WoW! no longer will bad design be limited to the web. Now i can enjoy poor quality MSfingerpaint on my critical life support devices

    --

    --

    What is the sound of this sentence?

  10. standardised medical embedded gui by joshwa · · Score: 3, Insightful

    ok, why is this special? it's a standardised embedded gui for medical systems. you know, like the ones offered by half a dozen other companies (symbian, qnx, etc)

    I guess it's because you get to code in html instead of C. Great, so now you can hire a TOTAL idiot html jockey to design your life-and-death medical interface instead of a (slightly-) better-trained C programmer?

    Whoop tee doo.

  11. Re:Fantasic size reduction by dekashizl · · Score: 2, Insightful

    Well they claimed to compress it down to 66Kb, which would seem to be 500000 -> 66000. That's 500:66 ration = 7.6:1, which isn't so bad.

  12. Damn, a real breakthrough! by aiken_d · · Score: 3, Funny

    Imagine being able to take a half a megabit and reduce it to only 66K. Why, compressed, that data is only 2K larger than the uncompressed version. Eureka!

    (1024 * 512) = 524288 bits, or 65536 bytes, or 64K.

    Cheers
    -b

    --
    If I wanted a sig I would have filled in that stupid box.
    1. Re:Damn, a real breakthrough! by Stormie · · Score: 2, Informative

      The article said 66Kb, not 66K. Half a megabit (512 kilobits) reduced to 66 kilobits.

  13. Re:Code blue (screeen of death) by niko9 · · Score: 4, Insightful

    This could give a whole new meaning to the blue screen of death. I sure hope they're not using Winbloze on a critical piece of life support.

    I don't think the OS is the major issue. Poor GUI designs in all types of devices are rampant.

    From my experience, the Lifepak 12 Defibrillator leaves alot to be desired as far as the user interface is concerned. It's nice to have fancy GUI (oohh shiny things!), but if it's clunky in it's excecution and you have to spend 30 seconds to do simple things like synchronized cardioversion then....

    I would love to see and Apple desgined defibrillator. It would probably only have 4 buttons and you could work any function in less than 5 seconds.

    Medics can dream, can't they?

    --

  14. Without a GUI, this would happen by HungWeiLo · · Score: 3, Funny

    dr_pepr_> ls
    dr_pepr_> . .. hmo_files
    dr_pepr_> cd hmo_files
    dr_pepr_> ls
    dr_pepr_> . .. new_drug_test_subjects
    dr_pepr_> rm -rf new*
    dr_pepr_> uname
    dr_pepr_> unknown i586 gentoo 2.4.17custom
    dr_pepr_> uptime
    dr_pepr_> 8:08 am up 3 days load average: 0.0, 0.0, 0.0
    dr_pepr_> lynx www.slashdot.org
    Connection timed out
    dr_pepr_> lynx www.slashdot.org
    Connection timed out
    dr_pepr_> ipconfig

    --
    There are a huge number of yeast infections in this county. Probably because we're downriver from the bread factory.
  15. Re:Code blue (screeen of death) by EngMedic · · Score: 2, Interesting

    Keep in mind that in many outfits, Lifepak doubles as an EMT's AED; thus, the standard "on, analyze, shock" buttons are there. It's kind of serving double duty, but all really important functions are pretty easy to get to fast, with only a little bit of practice.

    and yeah, there are actually 2 button defibrillators -- on, and analyze/shock. However, they're definetly not as powerful as Lifepak, and are designed for use by your average civilian, not an EMT or a medic.

    at least you're using LP12 -- on half our fleet we have LP10, which is more than a little outdated.

    --
    filter: +3. Hey, look! all the trolls went away!
  16. "Authoring Tool" by sbszine · · Score: 4, Funny

    You just need a standard PC and an HTML authoring tool to develop your GUI.

    I hope they mean a text editor. I would hate to entrust my life to a piece of machinery with a GUI 'authored' in FrontPage : )

    --

    Vino, gyno, and techno -Bruce Sterling

  17. Re:Code blue (screeen of death) by nathanh · · Score: 2, Insightful

    This is why I like Slashdot. Not just one, but two medics are posting comments on this thread. I also regularly read comments from lawyers, doctors, engineers, accountants, physicists, chemists, professors, firefighters, etc. Communities are more valuable when there is strong representation by many groups. Slashdot seems to be dominated by computer-jockeys, but it's great that it's not just computer-jockeys.

  18. My new profession by itsari · · Score: 2, Funny

    I think I found a new profession:
    <html>
    <head>
    <title>Life Support System</title>
    </head>
    <body>
    <input type="button" value="Live" onclick="live();" />
    <input type="button" value="Die" onclick="die();" />
    </body>
    </html>

  19. There'll likely be regulation to contend with... by Empiric · · Score: 2, Insightful

    Back in the day, I worked for a software company working on a project called "iVision" with Eli Lilly. This was in the pre-widespread-web days, and so the idea was to make the status of medical devices viewable via a LAN, presenting to the medical staff at the "nursing station" a consolidated graphical view of all the devices on a given hospital floor.

    One thing that I would expect developers to still have to contend with when using embedded web servers, is the very extensive approval process for medical devices. At some point of integration, functionality added to a medical device via software becomes considered part of the medical device, and as such subject to a very long regulatory approval process. This required us to make fairly counter-intuitive limitations to our prototype system, including the notion that though we could show information about the device (alarms, infusion time remaining, etc.), we could not change what the device was doing via our software (e.g. turn off an alarm on an infusion pump in another room once it was acknowledged).

    It's been several years, so I'm not sure how the regulations may have changed, but I'd suggest if you're using embedded HTTP on medical devices don't assume you can just upgrade/tweak/patch on the fly like it was a public web server--you probably can't.

    --
    ~ Whence do you come, slayer of men, or where are you going, conqueror of space?
  20. MS based ventilatators already out there! by jubalj · · Score: 2, Interesting

    During my medical training when I was doing time at the neonatology unit at one of the hospitals. I was suprised/shocked to see that one of the ventilators was running a version of windows. Ok, I figured must be a specially designed cut down, more stable version, but then I looked carefully.. and beside the start button was the quick launch tool bar with an icon for internet explorer and media player - that is just plain scarry! would you trust MS with your neonates life?

    Thankfully, for the few weeks i was there I never came across anyone complaining bout it. I cant seem to find it on the web, I might have to go back and see what the model and brand was...

  21. html is for gui design only by bigmo · · Score: 2, Informative

    I have one of the units. The developers kit comes with a touch sensitive lcd screen. The "html" you write just makes buttons and things on the lcd for you to interact with.

    When you "click" a button on the touch screen, a string of several bytes representing one of up to 255 commands is sent to whatever device you connect the amulet unit to. All the amulet does is convert a touch on the lcd screen to a number and send it out serially.

    While it's certainly a nifty thing, and I actually have a use for it (custom control of some A/V gear), I think the whole thing is a little over hyped, not that we aren't used to that ...

    ps - it's not just for medical devices. You can control your garbage disposal with it if you're so inclined.