Skip to content
Discuss a project
RUEN

A tool for a clinical team / 2026

Who needs
the room?

Booking for operating
rooms 546 and 506.

The doctor books a time for a procedure.
The nurse knows what to prepare for.

See how it works
DR IVANOV / Daily planMobile daily plan with two rooms and scheduled procedures

Actual interface.
Demonstration bookings.

Workflows, design, development and launchWeb application / Desktop and mobile

01 / The task

One spreadsheet.
Different questions.

A doctor needs an hour for a procedure. The nurse needs to know who is coming and when the room will be free. They look at the same schedule with different questions.

The team originally used a shared Google spreadsheet. It could hold a booking, but early and late procedures needed approval. Preparation notes and staff access needed a place too.

I started with Room 546: a calendar for doctors and a daily plan for the nurse. Approval requests and schedule controls followed. By the time Room 506 was needed, the team already knew the service.

2rooms
in one service
3roles
for the team
15 mintime selection
increment

02 / The team

For doctors
and nurses.

01 / Doctor

Find a suitable time

Doctors can see available time in both rooms, choose a duration and procedure, and leave preparation notes. If plans change, they can move or cancel their upcoming booking.

02 / Nurse

Know what to prepare for

The nurse has the day in one list, without piecing it together from calendar entries. She can approve additional time and book a room for a doctor herself.

03 / Administrator

Keep the schedule in order

The administrator invites staff and sets room availability. Part of a day in 506 can be closed without affecting 546.

03 / Interface

Take a look
inside.

Explore the month view, booking form and nurse’s daily plan. Open any screenshot for a closer look.

Where is there a free hour?

The month view makes open days and busy stretches easy to spot. For a ninety-minute procedure, the panel on the right finds slots long enough to fit.

These screenshots show the actual interface with fictional names and bookings. The team’s live schedule remains private.

04 / Booking

Say you need
an hour.

  1. 01

    Room

    Choose 546 or 506. The calendar shows that room’s bookings.

  2. 02

    Time

    Select a 60-minute duration and choose an available slot.

  3. 03

    Details

    Add the procedure category and any preparation notes.

  4. 04

    Validation

    When saving, the service checks that nobody else has just booked the same time.

  5. 05

    Plan

    The booking appears in the schedule. If approval is needed, the nurse receives a request.

05 / Approvals

What about
an earlier start?

An empty room is not always ready to book. Early mornings, evenings and weekends need the nurse’s approval.

Those hours are marked in lilac. The doctor submits a request and the slot is held pending a decision. A nurse or administrator then approves or declines it.

Weekdays
08:00–09:00 / 19:00–20:00
Saturday and Sunday
Approval required all day
Exceptions
Restrictions for a specific date and room

Each room has its own rules. The hours currently match; 506 can be adjusted later to fit its nurse’s schedule.

06 / On mobile

Who is working.
When they finish.

The first version of the daily plan showed when a procedure started. In use, the nurse also needed the booking’s end time and the doctor’s name.

I put both in the card alongside the procedure and note. There is no need to open each booking to see who is coming next and how long they have reserved.

The phone has the same working view. The service can be added to the home screen and opened from its own icon, without hunting for a browser tab.

Combined plan for the nurse
Details of a booking

07 / Evolution

First 546.
Now 506 too.

After launch, a second room was added. The doctors and nurses were the same, so asking them to use another set of accounts made little sense.

Two buttons in the header, 546 and 506, switch the schedule. The daily plan and requests can show both rooms together, with a visible room label on each booking and a filter above the list.

Daily plan filtered to Room 506

SeparateAvailability and restrictions. Closing 506 does not block 546.

SharedStaff accounts, the combined daily plan and the approval queue.

The team’s rulesA doctor can hold overlapping bookings in different rooms. Conflicts within the same room are blocked.

08 / Refinements after launch

Why extractions
became blue.

Green was already taken

Extractions were originally green. So was free time, which made a booking blend into the background. I changed extractions to blue throughout the service, including the category selector. The calendar became easier to read.

Open at the right time

Selecting 15:00 in the month view used to open the day at eight in the morning. Now it opens near the selected time, saving that extra scroll.

Familiar from the first screen

When the main DR IVANOV website was ready, I brought its wordmark, dark green and warm off-white into the service. Removing the large header image also left more space for the schedule.

One less selection

The administrator books for one doctor most of the time. That doctor used to require a fresh selection on every booking. Now he is selected by default, while the others remain available in the list.

09 / Under the hood

What happens
when you book.

While a doctor fills in the form, a colleague might book that slot. The service checks the schedule again when saving. Two overlapping bookings in the same room cannot both be accepted, even if submitted almost simultaneously.

Each staff member has an account and permissions. Doctors manage their own bookings, nurses can book for colleagues, and the administrator controls access. The service records who created and approved a booking, and backs up the database before updates.

HTML / CSS / JavaScriptNode.js / SQLiteDocker / Caddy / HTTPS

The service handles rooms and schedules. Medical records are kept elsewhere.

10 / The result

From a spreadsheet
to everyday use.

Room 546 is already in use. Room 506 has been added and is being tested by the team.

Some decisions came only after launch. The nurse needed the doctor’s name in the plan; the administrator wanted to avoid selecting the same doctor on every booking. Those requests shaped the service shown here.

Next, the team will settle the hours for 506. It will be a schedule change in a familiar service, without having to learn a new way to book.

Your project

What would make
your work easier?

Let’s talk
Application interface