Replies: 2 comments 5 replies
-
Big fan of UTC being used for everything in the database. There are no more headaches from those Daylight Saving Time changes, and no worrying about duplicated or missing times. And if we ever need to display it differently, converting from UTC is a breeze. I say we go for it! @clermontg |
Beta Was this translation helpful? Give feedback.
-
So, a workable solution would look like this. Sites first need to convert EHR datetimes to UTC. For sites that can upload limited data, this is all they need to do. For sites that do the time shifting themselves, the TS formula has to time an integral number of days, but within with standard time or DST eras. This is because the timing of events such as morning blood draws would not show a difference in local time but be one hour off one day to the next in a patient's data whose encounter bridges the ST/DST divide. This is a script that could be written centrally and deployed at site. |
Beta Was this translation helpful? Give feedback.
-
A argument could be made that all times in the database should be UTC to get rid of the time change issue where we go from UTC -5 to -4, and the local datetimes are duplicated in the dataset, while the opposite happens in the spring. What are folks position on this?
Beta Was this translation helpful? Give feedback.
All reactions