• Set Yourself Up For Success Webinar

    October 6, 2021 at 2 PM Eastern/11 AM Pacific
    SDN and Osmosis are teaming up to help you get set up for success this school year! We'll be covering study tips, healthy habits, and meeting mentors.

    Register Now!

  • Funniest Story on the Job Contest Starts Now!

    Contest starts now and ends September 27th. Winner will receive a special user banner and $10 Amazon Gift card!

    JOIN NOW
  • Site Updates Coming Next Week

    Site updates are coming next week on Monday, Wednesday, and Friday. Click the button below to learn more!

    LEARN MORE

iDoctors !!! Medicine and Technology

moco89

Full Member
10+ Year Member
Jan 7, 2010
641
30
246
  1. Pre-Medical
Type 1 diabetic here, who uses an insulin pump and a CGM (continuous glucose monitor). I use an Omnipod insulin pump and a Dexcom G4 CGM.

I am also an electrical engineering major.

There is a lot of hype in the diabetes community about having a smartphone control devices such as a continuous glucose monitor and an insulin pump, using bluetooth 4.0 protocols, etc.

I have to say, it is rather insecure and unsafe.

While mobile healthcare is in our future, the only safe way for operating consumer healthcare devices (OTC and prescribed) is through some sort of mobile "healthcare operating system" and a specific device (which may look and feel like a "smartphone") to do only "healthcare operations"-that is approved by the FDA--NOT through a smartphone that can install various non-FDA approved apps, receives texts, phone calls, can send data through RF and various bluetooth protocols, and even send information via infrared .

There is also no efficient way of sorting through the data generated by the medical devices, such as mine, unless you carry a netbook with you at all times, carry the cords, and upload the devices all the time.

Also, you can forget about using the powerful information from the data generated from uploading (unless you can program in MatLab, C, Java, etc) from these devices unless they adopt the ISO/IEEE 11073 standard. I can say that dealing with the data exported from the proprietary diabetes-related programs is a nightmare to deal with. The programmers who code these programs all do a sub-par job, regardless of brand or manufacturer.

EDIT: I noticed the guy interviewed, Eric Topol, is a type 1 diabetic, using the Dexcom G5, which is under clinical trials. Basically that device uses the antenna in the transmitter (seen at 5:43) sending the data remotely via GSM (mobile/cellular network) to a server on the cloud. The Sony Ericsson phone can then access the server on the cloud, with the uploaded BG (blood glucose) data. The transmitter does not directly upload data to the phone (unlike what he said on the interview), bypassing a security flaw.
 
Last edited:

moco89

Full Member
10+ Year Member
Jan 7, 2010
641
30
246
  1. Pre-Medical
This article addresses the device interoperability problems that we all encounter as diabetics using technology.

Even if smartphones were available to control and upload our devices (diabetics) and the medical device industry was not greedy (by a miracle) and decided to use Bluetooth 4.0 (or any bluetooth protocol), instead of RF (analog)---and agreed on using a universal data storage format, the framework for basically all smartphone operating systems are unsuitable for real-time monitoring (such as for a CGM--continuous glucose monitor).

Smartphones are not suitable for people with chronic illnesses that require continuous monitoring--aside from the many, many, security issues involved.
 
Last edited:
About the Ads
This thread is more than 8 years old.

Your message may be considered spam for the following reasons:

  1. Your new thread title is very short, and likely is unhelpful.
  2. Your reply is very short and likely does not add anything to the thread.
  3. Your reply is very long and likely does not add anything to the thread.
  4. It is very likely that it does not need any further discussion and thus bumping it serves no purpose.
  5. Your message is mostly quotes or spoilers.
  6. Your reply has occurred very quickly after a previous reply and likely does not add anything to the thread.
  7. This thread is locked.