Client
Private hospital foodservice operator
Hospital Meal Ordering and Kitchen Operations Platform
A web-based meal ordering and operations platform that turns patient preferences, room context, menu cycles, approvals, kitchen lists, chef tallies, labels, and display screens into one connected workflow.
Snapshot
Project snapshot.
The fast read on what the platform is, who it serves and what was delivered.
Country
Australia
Year
2024
Platform
Web ordering + staff operations
Users
Patients, foodservice staff, and display viewers
Scope
Meals, bed lists, approvals, labels
Scope markers
The brief
What needed to change.
Hospital meal ordering carries sensitive operational detail. Each order needs room context, menu timing, texture, fluid texture, allergies, dietaries, dislikes, comments, serving size, and approval state before it becomes useful for staff.
The platform had to make ordering clear for patients while giving foodservice teams practical screens for bed lists, production, chef tallies, labels, menus, support requests, and print-ready outputs.
The platform had to make ordering clear for patients while giving foodservice teams practical screens for bed lists, production, chef tallies, labels, menus, support requests, and print-ready outputs.
The challenge
What made it complex.
The challenge was connecting patient choice to kitchen execution without exposing private hospital or patient information in the public case-study story.
Orders carried sensitive operational context
Room details, texture, allergies, dietaries, dislikes, comments, serving size, and meal timing all needed to stay attached to the order.
Patient choice had to become kitchen work
Breakfast, lunch, dinner, alternatives, drinks, soups, desserts, vegetables, carbohydrates, and no-meal states needed staff-ready production views.
Late changes needed approval
Out-of-window orders needed review before they moved into production so staff could manage exceptions without losing patient context.
Public proof had strict boundaries
The case study needed to show operational depth while avoiding real patient data, site names, staff details, hospital identifiers, and credential exposure.
What we built
The operating system delivered.
Webits built a Django hospital foodservice platform with patient registration, meal ordering, room and dietary capture, bed list management, late-order approvals, meal production views, chef tallies, menu management, support enquiries, labels, PDFs, display screens, and spreadsheet-connected outputs.
Patient workflow
Patient registration and meal ordering
Patients can register or log in, review upcoming order dates, and place meals through a guided ordering flow.
Room, texture, allergy, and dietary capture
The ordering path captures room context, texture, fluid texture, allergies, dietaries, dislikes, comments, serving size, and preference notes.
Kitchen operations
Bed list and production views
Staff can manage bed records, missing orders, trolley grouping, breakfast, lunch, dinner, and date-specific production screens.
Chef tallies, approvals, and labels
The platform supports pending approval queues, chef tally aggregation, drink label output, and preparation-ready order context.
Operational outputs
Menu management and display screens
Menus, weekly cycles, historical menu records, daily displays, and weekly display screens support patient-safe foodservice communication.
PDFs and spreadsheet-connected outputs
Print-friendly order views, menu PDFs, drink labels, and spreadsheet-connected preparation data support daily catering operations.
Technical foundation
The technical foundation.
Built on a server-rendered Django foundation for patient ordering, staff operations, PDF outputs, spreadsheet sync, and display-ready menu surfaces.
Backend
- Python
- Django
- Django forms
- Celery
Frontend
- Django templates
- Server-rendered forms
- Print-friendly views
- Display-screen templates
Database
- PostgreSQL
- Django ORM
- Historical menu snapshots
- Role-aware data model
Document generation
- WeasyPrint
- PDF generation
- Print views
- Label outputs
Integrations
- Google API client
- Spreadsheet sync
- SMTP email
- Background tasks
Deployment
- Managed cloud hosting
- Gunicorn
- NGINX
- SSL/TLS
What changed
The result of the rebuild.
The platform turned a sensitive hospital foodservice workflow into one connected ordering and operations system, while keeping public claims deliberately general.
Patient ordering gained a clearer path
Patients can move through meal dates, preferences, and menu selections without staff collecting every request manually.
Room and dietary context stayed attached
Texture, allergies, dietaries, room status, dislikes, comments, and serving size travel with the order into staff workflows.
Kitchen teams gained practical views
Bed lists, production screens, breakfast, lunch, dinner, trolley grouping, and tallies turn patient selections into preparation context.
Late orders became reviewable
Pending approval states give staff a controlled way to handle out-of-window submissions before they affect production.
Outputs became part of the workflow
PDFs, labels, display menus, and spreadsheet-connected data are generated from the same records used for ordering and review.
The public story stayed safe
The case study can show the operational depth of the platform without exposing patient data, hospital identity, or sensitive implementation details.
System Views
Visual walkthrough across the system.
The clearest screens, system states, and support visuals behind the work.
Operations dashboard
Bed list operations
Breakfast production table
Lunch production table
Dinner production table
Chef tally
Pending approval queue
Support enquiry management
Menu item library
Menu item editor
Weekly menu editor
Weekly menu view
Daily menu view
Historical menu records
Drink labels
Bed-list logs
Patient dashboard
Patient profile
Patient information step
Breakfast order step
Lunch order step
Dinner order step
Order confirmation
My orders
Patient order detail
Daily display menu
Weekly display menu
Public entry screen
Next Step
Need software for a sensitive operational workflow?
Webits builds practical systems for complex operations where roles, approvals, records, outputs, and public-safe handling all need to be considered from the start.