...
The table below provides a few illustrative examples.
Provided Value | Interpreted As |
2016 | 20160101000000.000 |
201602 | 20160201000000.000 |
20160203 | 20160203000000.000 |
20160203111213 | 20160203111213.000 |
20160203111213.987 | 20160203111213.987 |
20160203111213.9876 | 20160203111213.987 |
2016020311121 | ERROR |
Time zones and offsets
TS values are treated by PKB as communicating an absolute point in time. We interpret the value you provide as being a fixed point in time, and persist that fixed point in time to the database. As such, every TS value is interpreted within a time zone (or having an offset from UTC). The time zone we use is determined according to the following hierarchy:
...
Since PID-7 is a TS value, it is capable of representing an explicit point in time. This point in time is the patient's time of birth, but PKB does not store this value. There is no "time of birth" attribute on a[[Patient]].
However, PKB does capture a "date of birth". A patient's date of birth is the name of the date on which the patient was born according to the time zone in which they were born. Counter-intuitively, knowing the absolute point in time at which a patient is born is not sufficient to deduce their date of birth. By way of example, imagine you know a person is born right now, as you are reading this. You cannot know their birthday unless you also know where they were born (or more accurately, in which time zone they were born) since the name of the date is dependent upon their location relative to the international date line.
...
PKB customer sites:deploy |developer |information governance |procurement |manual
...