[FORGED] Re: [FORGED] Re: Representing microseconds in DateTime

Koray Atalag k.atalag at auckland.ac.nz
Tue Feb 2 05:27:54 EST 2016

Hi Bert, yes it is an extreme case - most clinical measurements will not go in this range.

Python's DateTime library <https://docs.python.org/2/library/datetime.html>  (which I'm using at the moment) supports 6 digits after decimal point which gives resolution of 1 microseconds.



From: openEHR-technical [mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Bert Verhees
Sent: Tuesday, 2 February 2016 11:18 p.m.
To: For openEHR technical discussions
Subject: [FORGED] Re: [FORGED] Re: Representing microseconds in DateTime

On 02-02-16 11:07, Koray Atalag wrote:
Hi Bert, I was saying ISO8601 do support this - it is openEHR that constrains to milliseconds.

You are right, you do say that. I don't know if your code supports this, because the ISO-time-string will be converted to a Time-class and must have the same value when converted back.

The Java 8 LocalTime class supports until 9 decimals.

In my case it is action potential measurement from myocytes

Sounds interesting, I asked because it is rare to measure microseconds in medical applications.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20160202/36a8fb28/attachment-0002.html>

More information about the openEHR-technical mailing list