[Gnumed-devel] Default datetime precision

[Busser, Jim]

At the creation of an encounter, it is sane that GNUmed offers by default, and 
saves, either

        now()

or maybe even better

        date_trunc('minute', now())

and the only other kinds of entries that I can see value to capturing to the 
level of minutes, and maybe seconds, include

- date of birth, in those circumstances where the minutes matter (say, in the 
case of a multiple birth)

- measurements, especially when there would be multiple measurements for 
example blood pressures, or test specimens collected at at timed intervals 
following an injection.

Otherwise, for example with the inputting of a start_date for medication that a 
patient first began days to months ago, or which is intended to start at some 
undefined time later today even tomorrow, it might be better to truncate to the 
level of the date.

The same is true when it is desired to backdate the clin_when of an encounter 
that is being created today, to create a record of the phone call which I had 
with the patient two days ago when I answered their message request from a 
hospital phone while not connected to GNUmed, and of which I had made myself a 
paper note but not fully detailed with the hour and minute, which I would 
rather not be spuriously preserved in the backdated clin_when.

It would be nice if I changed the clin_when for this newly created entry to be

        2013-08-22

it would be recorded as

        2013-08-22 00:00:00

without my having to enter the

        00:00:00

Would it be difficult for GNUmed to NOT auto-offer, nor auto-append after 
exiting the field, a "time" portion when a user inputs a date only to the level 
of the date (and did not specify a time)?

-- Jim