Slashdot Mirror


RFID Tags Can Interfere With Medical Devices

An anonymous reader writes "A new study suggests RFID systems can cause 'potentially hazardous incidents in medical devices.' (Here is the JAMA study's abstract.) Among other things, electrical interference changed breathing machines' ventilation rates and caused syringe pumps to stop. Some hospitals have already begun using RFID tags to track a wide variety of medical devices, but the new finding suggests the systems may have unintended consequences."

2 of 120 comments (clear)

  1. Need in health care for asset tracking by steeljaw · · Score: 3, Interesting

    Interestingly enough, I've been approached 3 times now by people in the health care industry who have expressed a need for some time of asset tracking software and I've always given them my brother's card (his company specializes in RFID based asset tracking). Actually, one person specifically asked me if I was capable of integrating an RFID solution into their environment. I wonder how many companies are currently developing RFID based software geared towards the health care industry only to receive a backlash from the medical community when this type of information becomes common knowledge..

    --
    Procrastinators, Unite Tomorrow!!
  2. Re:Interference in medicine by bill_mcgonigle · · Score: 3, Interesting

    I can corroborate your basic point, and the sad part is that my data is 10 years old. Back then wireless ethernet (2Mbps pre-b stuff, even) was new and we were testing for interference. The very same kinds of machines had trouble as in TFS, and it was at sub-foot ranges.

    I suspect either this study tested old gear (I'm assuming our hospital used a popular vendor) or the same vendors are playing lazy. Back then, the biomedical engineering guys explained to me that the FCC granted exceptions to medical device manufacturers for emitted interference, and that an emitter is a receiver, but that most good medical products companies didn't need to bother with these exceptions, they did a fine job on principle.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)