Stream: patient administration WG
Topic: Slot.start -- DateTime vs Instant
Josh Mandel (Apr 30 2021 at 15:46):
I wanted to call out a use case we bumped into a bit in COVID-19 schedule publication for #smart/scheduling-links -- it's perhaps bending the intended use of Slots, so feel free to say "out of scope"... but sometimes a Slot might be quite coarsed-grained, like for a day-long event -- and in these cases, pinning the slot to an Instant rather than a DateTime means we can't quite express the intended semantics of "This slot represents May 5th" (best we can do is "midnight in EST on May 5 to midnight EST on May 6" or similar)
Josh Mandel (Apr 30 2021 at 15:47):
What would folks think about using a DateTime instead of an Instant for Slot.start and Slot.end ?
Brian Postlethwaite (Apr 30 2021 at 21:43):
I think some have done that, but more often for the 9-5, or 8pm-9am kind of like shifts.
Dont see an issue with that.
Josh Mandel (Apr 30 2021 at 21:52):
Yeah, for something like 9a-5p, Instant-based bounds probably work.
Last updated: Apr 12 2022 at 19:14 UTC
