Salus Solvo Shift Control — Healthcare Staffing App

I built Shift Control to connect scheduling, professional assignments, required coverage and completed work in one operational application. The work grew directly from my role as COO at Salus Solvo.

My contribution: operational requirements, workflow design and hands-on implementation using AI-assisted development, without outside developers.

Coverage and booking are separate. A required position expresses demand; an assigned shift books a professional.

Responsibility shapes access. Operational roles and unit assignments have defined boundaries, with financial permissions handled separately.

Practice has its own space. An isolated Demo uses fictional records for training and handover.

Project stage: core release published; operational closeout and acceptance in progress.

Related workstreams include doctor-onboarding workflow design and an unpublished Italian Academy platform prototype.

Public case study: https://www.hesham.me/portfolio/salus-solvo/

How I evaluate the experience

A useful staffing screen must make the next operational decision clear: what coverage is required, what is booked and what still needs attention.

Worked example: coverage versus booking. If a required position and an assigned professional look interchangeable, a coordinator could mistake demand for confirmed cover. The design keeps those concepts separate. A focused validation scenario is to create a requirement in the fictional Demo, assign a professional, change the assignment and check that the remaining coverage is understandable at each step.

I would also check that status cues work without colour alone, keyboard focus follows the task order, and restricted roles cannot reach financial information through either the screen or a direct link. These are evaluation criteria and test scenarios, not a claim of accessibility certification or measured savings.