Timezones

Slot times are returned by the API in the clinic's timezone. The widget displays them as-is — a clinic in Delhi shows slots in IST, a clinic in London shows slots in BST/GMT.

Why not the patient's timezone?

For in-person consultations, "3:00 PM" always means 3:00 PM at the clinic. Converting to the patient's local time would be confusing (and wrong if they're traveling).

For online consultations, the patient still sees the clinic's local time. Their calendar invite (if enabled) includes the correct absolute time so their calendar app can render it in whatever zone they're actually in.

Timezone selector

The scheduling step exposes a timezone selector for online consultations — so patients booking a video call from another zone can see "what does 3 PM IST mean for me?" This is a display-only convenience; the booking is still stored in the clinic's timezone server-side.

Cross-timezone edge cases

• Daylight saving transitions — the API accounts for DST; times are correct across transitions.
• Half-hour and 45-minute offsets — the widget renders whatever the clinic's zone offset actually is (India, Nepal, etc.).
• Slot reservations — slot reservation lifecycles are managed server-side in UTC, so client clocks being off doesn't affect correctness.