FHIR Chat · DateTime representation · implementers

Stream: implementers

Topic: DateTime representation


view this post on Zulip Brian Postlethwaite (Nov 13 2016 at 04:50):

2014-10-07T14:45:00+00:00 or 2014-10-07T14:45:00Z
http://hl7.org/fhir/datatypes.html#datetime indicates that +24:00 is not acceptable, but nothing on Z vs 00:00 (defined same way in current build too)

view this post on Zulip Brian Postlethwaite (Nov 13 2016 at 04:51):

@Richard Ettema Some of my tests are failing for this reason. The .net client outputs dates with a +00:00 and not Z so the tests fail.

view this post on Zulip Grahame Grieve (Nov 13 2016 at 10:58):

Z and +00:00 and -00:00 are all equivalent in meaning

view this post on Zulip Brian Postlethwaite (Nov 13 2016 at 21:32):

Thanks Grahame, @Richard Ettema can you have a look at the touchstone tests for this?

view this post on Zulip Richard Ettema (Nov 14 2016 at 13:40):

@Brian Postlethwaite Thanks for the review. Those particular tests with the datetime values are using the minimumId assert which checks the returned resource against a known representative fixture of that resource. Since this check is done against the XML or JSON sytax, I can see why that would fail. I'm reviewing those tests now. -Thanks

view this post on Zulip Richard Ettema (Nov 14 2016 at 18:42):

@Brian Postlethwaite I have updated the DeviceComponent TestScripts and fixtures and deployed them to Touchstone. You can re-execute those tests at your convenience.

view this post on Zulip Brian Postlethwaite (Nov 14 2016 at 22:55):

Yes, that works for that one. Assume this is not a generic fix and needs to be applied to all the items individually.

view this post on Zulip Richard Ettema (Nov 15 2016 at 02:41):

Yes. I will be reviewing all the TestScript fixtures for datetime values and apply the same fix.


Last updated: Apr 12 2022 at 19:14 UTC