When lives are at stake, people tend to be more amenable to changes like GMT and 24-hour clock. If the military can do it, a civilian organization with sufficient motivation (insurance terms, regulation, etc) should be able to make the same shift.
However, I was referring more toward the recording system than the staff. If the recording systems were all using unix time stamp with a GMT system clock synchronized over NTP, there would be no ambiguity as to when a record was added to the system. End user systems could be responsible for keeping track of what time zone the user is in, and could convert as necessary. The important thing is that the "One True Datum" have the appropriate stamp.
> End user systems could be responsible for keeping track of what time zone the user is in, and could convert as necessary.
That would require routine updates to the timezone database, which is a bit more complicated than NTP. (Yes, DST rules change all the time. The U.S. changed its rules just a few years ago.)
Hopefully, the rise of cheap and powerful ARM SoCs will make it impossible for device manufacturers to make excuses about not running a proper OS on their machines anymore. I would love to see more Linux and BSD on medical devices.
However, I was referring more toward the recording system than the staff. If the recording systems were all using unix time stamp with a GMT system clock synchronized over NTP, there would be no ambiguity as to when a record was added to the system. End user systems could be responsible for keeping track of what time zone the user is in, and could convert as necessary. The important thing is that the "One True Datum" have the appropriate stamp.