search

smart-on-fhir / smart-scheduling-links

Clinical Appointment Slot Discovery
28 stars 15 forks source link

Add timestamp offset advice #30

Closed jmandel closed 3 years ago

jmandel commented 3 years ago

Based on discussion at https://chat.fhir.org/#narrow/stream/281612-smart.2Fscheduling-links/topic/Time.20zones.20for.20slots.2C.20locations

jmandel commented 3 years ago

@GUI FYI

GUI commented 3 years ago

Thanks! Yeah, hopefully this will help clarify things for publishers.

Would a more concrete example maybe help clarify how the UTC zone should be used? I understand what this says, but given the fact that most of the sample data so far includes the Z specifier (so is therefore compliant), but perhaps isn't using it correctly, I'm just wondering if this could use more clarification to help publishers. Or maybe I shouldn't be reading as much into the sample data we have have so far, and maybe this could be addressed with the validator tool looking for suspicious times. But maybe including an explicit example like:

For example, to represent a start time of 10:45AM in America/New_York on 2021-04-21, this could be returned as either 2021-04-21T10:45:00.000-04:00 or 2021-04-21T14:45:00.000Z.

But I know I can also be overly-verbose, so it's also fine if you don't think the extra additions are needed. :) I think the changes you have will also help clarify the situation.

jmandel commented 3 years ago

I think verbose is good here; will incorporate an example, thanks for the suggestion!