Calendar integration
Personal calendar connection
Meetings, on-call shifts and private appointments on a physician's Google or Microsoft calendar narrow the clinic's availability automatically. Appointments in HekimBis are written to the external calendar only as Busy, without patient details. Between the two calendars, HekimBis is always the source of truth.
The calendar works in both directions, and HekimBis stays the source of truth
Inbound, only busy or free information is read from the external calendar. These blocks narrow the hours when the physician can be booked in HekimBis.
Outbound, a HekimBis appointment is written to the external calendar as a generic Busy entry. The entry holds only the time slot; the patient's name, the service and the diagnosis never leave HekimBis.
The connection is set up with the physician's own authorization. Access keys are stored encrypted on the server, and the physician can withdraw authorization at any time, after which reading and writing stop and a reconnect warning is shown.
Sync and reconciliation
Busy times on the external calendar narrow availability, appointments are booked against the HekimBis record, and the two sides are compared regularly.
Regular reconciliation
Both sides are compared and differences are shown.
- The process is complete here.
- If appointments conflict06a Conflict
All steps
- 01 Authorization (Physician) The physician connects their own calendar and chooses the direction.
- 02 Reading busy blocks (Sync) Only busy/free information is taken from the external calendar.
- 03 Availability narrows (HekimBis) HekimBis updates availability around these blocks.
- 04 Appointment booked (HekimBis) The final check uses HekimBis's own record.
- 05 Generic "Busy" entry (External calendar) Written to the external calendar with no patient details.
- 06 Regular reconciliation (Sync) Both sides are compared and differences are shown.
Alternative path from 06 Regular reconciliation; it returns to the main flow at 06 Regular reconciliation.
- 06a Conflict (Sync) A block on the external calendar overlaps an existing appointment.
- 06b Decision (Physician) The conflict is shown to the team; the physician or front desk resolves it, with no silent merge.
Alternative path from 02 Reading busy blocks; it returns to the main flow at 02 Reading busy blocks.
- 02a Authorization revoked (Sync) The connection dropped.
- 02b Re-authorization (Physician) A warning is shown and the physician renews the connection.
06 Regular reconciliation
No double bookings, and conflicts are shown to the team
- The final check happens in HekimBis
- When an appointment is booked, the final check runs against HekimBis's own record. A conflict that appears later on the external calendar is not resolved silently; it is shown to the team, and the physician or front desk decides.
- Patient details stay inside
- Only a generic Busy entry is written to the external calendar. It does not include the patient's name, the service or the diagnosis.
- The physician controls authorization
- When you withdraw authorization, the access keys become invalid and reading and writing stop. Each calendar is connected only with its owner's own authorization.
Setup takes five steps
- 1
The physician authorizes their calendar
The connection is made with the physician's own account, and access keys are stored encrypted on the server.
- 2
The direction is chosen
Inbound (busy blocks from the external calendar) and outbound (a generic Busy entry for HekimBis appointments) are set separately.
- 3
Busy blocks narrow availability
Busy times on the external calendar narrow the hours when that physician can be booked in HekimBis.
- 4
Appointments appear on the external calendar
HekimBis appointments are written to the external calendar as a generic entry without patient details.
- 5
Reconciliation runs
The two sides are compared regularly; a difference or conflict is shown to the team and never merged silently.
Frequently asked questions about the calendar connection
Does the patient's name appear on my external calendar?
No. HekimBis appointments are written to the external calendar only as a generic Busy entry.
Can HekimBis read the events on my external calendar?
Only busy or free information is read; event titles, attendees and details are not taken.
What happens if there is a conflict on the external calendar?
The conflict is shown as a warning, and the physician or front desk decides. Nothing is merged silently.
Can I remove the connection whenever I want?
Yes. When you withdraw authorization, the access keys become invalid and reading and writing stop.
Which calendar services are supported?
Google and Microsoft personal and organizational calendars. For other services, get in touch with us.
Who can set up the connection?
The physician or user who owns the calendar. Someone else's calendar cannot be connected without their authorization.
Do my working hours and leave come from the external calendar?
Busy blocks on the external calendar narrow availability; working hours and leave rules are defined separately in HekimBis, and HekimBis stays the source of truth.
Can several calendars used by one physician be connected?
Each calendar is connected with its owner's own authorization, and which calendars are in scope is decided when the connection is set up.
What shows up in the calendar app on my phone?
The generic Busy entries written to your external calendar account appear in every app that shows that account; the entries hold no patient details.
Keep reading
Related pages
Features
- Appointments and calendarPhysician, room, and device calendars with a waitlist and double-booking checks.
- Mobile appAgenda, quick check-in, voice notes, and critical result alerts for the care team.
- Front desk and check-inArrival logging, QR or kiosk check-in, waiting room status, and delay estimates.
- Patient communicationSMS, email, and WhatsApp reminders with consent, İYS, and quiet-hour checks.
Specialties
Integrations
Company and support