[FORGED] Re: Representing microseconds in DateTime

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

Hi Bert, I was saying ISO8601 do support this - it is openEHR that constrains to milliseconds.

In my case it is action potential measurement from myocytes



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

Just for the record, which medical requirement makes measuring micro-seconds necessary?

By the way, ISO allows one or more digits to represent a decimal fraction of a second.

I don't have the original standard at hand, but Wikipedia says:
There is no limit on the number of decimal places for the decimal fraction.


On 02-02-16 10:51, Koray Atalag wrote:

I have a requirement to capture timeseries data which happens at 250 microseconds - that is 0.000250 seconds.
While many programming languages, and the ISO8601 spec, supports this  openEHR RM<http://www.openehr.org/releases/RM/latest/docs/support/support.html#_iso8601_time_class> seems to be constrained to milliseconds:
hh:mm:ss[,sss][Z | ±hh[mm]]

Any particular reason we dump microseconds? If not can we add this capability - I think it won't break any existing code (I hope!)




openEHR-technical mailing list

openEHR-technical at lists.openehr.org<mailto:openEHR-technical at lists.openehr.org>


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

More information about the openEHR-technical mailing list