News for hackers. Stuff that matters.
Re:Medical devices A ticking time-bomb by HeyLaughingBoy on Wednesday May 23, 2012 @12:53PM (#4013927)
This is interesting because at least one of our medical instruments runs on Windows Embedded and as part of the OS customization process, we turn off the "sync to time server" feature. The time is set during installation, and unless a customer or a service engineer notices something wrong, never touched again.

Why do we do this? Well, because we run into the same problem everyone else who wants to sync to a time server in a lab or hospital does: the hospital's IT people don't want anything on their network that isn't absolutely required to be there.

Clinical IT is understandably suspicious of anything on their network, but it will take cooperation on all sides before anything changes in this arena.

Re:Medical devices A ticking time-bomb by warech on Wednesday May 23, 2012 @12:28PM (#4013801)
FDA requirements for electronic data transmission (21 CFR Part 11) are a hassle to implement even for devices starting from a blank slate. That being said the sooner NTP standards are universally required, the better. As the article mentions it will be very resource-intensive to retrofit devices for this standardization - an EMR consultant's dream project.
Re:Medical devices A ticking time-bomb by stcredzero on Wednesday May 23, 2012 @12:14PM (#4013742)
Once again, the complexities of coding using time-related concepts rears its ugly head. There should be standards for time synchronization and tracking. All medical data should be timestamped to a global uniform standard like GMT.