Scattered follow-up
Patient evolution was spread across separate files and records.
CLINICAL OPERATIONS PLATFORM
Pilot project · Concept validation in a clinical settingFrom scattered records to a prototype for clinical follow-up.
A volunteer concept-validation pilot exploring how to organise follow-up, trends and shift handoffs in a clinical setting.
Product Discovery
Clinical Workflows
Information Architecture
UX Validation
Multi-device Prototyping
01 · STARTING POINT
It was not about “building an app.” It was about understanding where the workflow broke down.
Part of the follow-up relied on distributed records, without a central view of the unit.
Shift handoffs with distributed information
Reconstructing what had changed over 24 hours required checking different values and notes.
Different profiles, shared information
The prototype needed to test different reading and editing needs.
Trends were hard to see
Laboratory, ventilation and weaning data need to be read as evolution, not isolated values.
02 · THE PRODUCT
See the unit. Drill into detail. Understand what changed.
These interfaces are anonymous recreations using fictional data. No screenshots or real clinical information are shown.
PUBLIC RECREATIONThe logic comes from the prototype; the data and interface shown on this page are recreated.
Beds10occupancy view
IMV4invasive mechanical ventilation
Isolated2operational context
Bed 01Patient A · follow-up day 4
Reason for admission · fictional demo data
SupportIMVRASS−2PBW63 kgHeight172 cm
Bed 02Patient B · follow-up day 7
Reason for admission · fictional demo data
SupportNIVRASS0PBW71 kgHeight178 cm
Bed 03Patient C · follow-up day 2
Reason for admission · fictional demo data
SupportIMVRASS−1PBW58 kgHeight165 cm
Bed 01Patient A · fictional data
Height 172 cmPBW 63 kgsex + height
Simulated trendevolution, not just the latest value
LaboratoryVentilationTimeline
Bed 01 · Patient AWhat changed since the previous shift
RELEVANT CHANGES
PEEP 8 → 6FiO₂ 50 → 40RASS −2 → −1
LATEST PROGRESS NOTE
Favorable response. Evaluation continues.
PLAN / PENDING
Review tolerance and trend on the next shift.
Prototype boundaryIt does not replace the medical record or aim to function as a medico-legal record. At this stage it is used to validate structure, workflow and information readability.
03 · DESIGNING WITH USERS
The product changed when feedback began to reorder priorities.
The test was not to make a polished screen. It was to use the prototype in a shift-handoff scenario and see what needed to change.
DECISION01
Height + predicted body weight move up the hierarchy
FeedbackThey are key variables for guiding ventilatory parameters.
→ChangeThe unit view gives them high visual priority and calculates PBW from sex + height.
DECISION02
Fever stops dominating the dashboard
Initial assumptionMake it a primary KPI.
→ChangeIt remains where it adds context, while the unit view shifts its focus to beds, mechanical ventilation and isolation.
DECISION03
“What changed in 24 h” becomes a central element
NeedMake shift handoff review faster.
→ChangeShift handoff with changes, progress note, plan and pending items per patient.
PRODUCT PRINCIPLEDo not design for the user from a distance. Design with the user while the workflow can still change.
WEANING PANEL · PROTOTYPE FOR VALIDATION
Read variables without automating a clinical decision.
The current build brings together six visible variables and a manual assessment. The final judgement remains with the professional, and the configuration is still open to user feedback.
System designOrganizing information ≠ deciding for the professional.
SBT / WEANINGQuick assessment
PrototypeSupportPSV
P/F ratio238
PEEP6
Norepinephrine0
VasopressinNo
RASS−1
PROFESSIONAL ASSESSMENTHas the cause that required mechanical ventilation resolved?Manual · not automated
04 · INFORMATION ARCHITECTURE
Two reading scales: the unit and the patient.
The public page does not need to become clinical documentation. The architecture is explained through relationships, hierarchy and flow.
UNIT
UNITOperational view
overall status · priorities · access to detail
shared context
Bedsoverall status
Patientpersistent context
Ventilationentry and review
Laboratorytrends
Timelinechanges over time
Shift handofflast 24 h
MULTI-DEVICE
The prototype needed to adapt across different devices.
iPhone, Android and desktop were considered from the early stages. Prototype testing surfaced specific navigation and readability fixes on Android/Chrome and Surface/Edge.
05 · CURRENT STATUS
First validate the concept. Then consider a possible technical evolution.
The project is still in development. It is not presented as a hospital deployment or as a measured clinical or operational outcome.
NOWProduct validationcurrent phase
- Information structure
- Visual hierarchy
- Metrics and variables
- Data-entry and review flows
- Shift handoff
- Responsive design and navigation
- User feedback
NEXTPossible technical evolutionlater phase
- Final data model
- Backend and persistence
- Authentication
- Real access control
- Security and deployment
- Further validation in context
Do not build permanent infrastructure around a workflow that is still changing.
WHAT THIS PROJECT DEMONSTRATES