Primoro MVP — UI / UX Impact Summary

Ordered by most UI / UX change → least

1️⃣ Task Manager (v2.1 → v2.2) — BIGGEST UI/UX CHANGE

Why it’s first

Task Manager has evolved from a simple task list into a planner‑grade operational work system. This has major layout, interaction, and mental‑model implications.

What changed

Introduction of Kanban / board views alongside list and queue views

Checklists with evidence capture (attachments, confirmations)

Work Packages (bundled tasks / operational playbooks)

Templates and recurrence

Concept of task as calendar‑backed work remains core

UI/UX impact

Requires multiple view modes (List / Board / Calendar‑linked)

Cards must visually represent:

Status

Ownership (role vs person)

Due window / SLA

Evidence state

Needs clear separation between:

Individual tasks

Checklists

Work Packages

Heavy interaction surface → drag/drop, expand/collapse, quick‑complete

Designer notes

This is not a to‑do list UI

Think: Trello + calendar + governance overlays

Needs careful visual hierarchy to avoid overwhelm

%20v1.0.docx&action=default&mobileredirect=true&DefaultItemOpen=1)

2️⃣ Communication Hub (formerly UCH)

Why it’s high impact

This is no longer “messaging” — it’s the front door to work creation.

What changed

Messages must convert to owned work (tasks, callbacks, appointments)

Single thread per context (patient / lead / internal)

Explicit removal of inbox / WhatsApp mental models

UI/UX impact

Conversation UI must:

Visually surface ownership and follow‑ups

Show linked tasks / callbacks inline

Requires strong action affordances inside threads

Needs to feel calm, not chatty or consumer‑messenger‑like

Designer notes

This is a work orchestration UI

Messages ≠ end state; actions are

3️⃣ Appointment Manager

Why it’s high impact

This becomes a governed scheduling engine, not just a diary.

What changed

Explicit separation from:

Rota (coverage)

Communication (messaging)

Booking rules, policies, deposits enforced by the system

Full auditability of booking actions

UI/UX impact

Booking UI must:

Explain why slots are/aren’t available

Surface policy constraints cleanly (without modal overload)

Strong need for progressive disclosure (rules without clutter)

Clear states for:

At‑risk appointments

Policy‑bound actions

Designer notes

Avoid “open diary” metaphors

UI should feel protective, not permissive

/MVP/Task%20Manager%20%E2%80%93%20Technical%20Specification%20v2.2.docx)

4️⃣ Surgery & Decon Day View (Tablets)

Why it’s high impact

Completely consolidates multiple legacy tablet experiences into one nurse‑first view.

What changed

Single authoritative day view for:

Surgery flow

Decontamination readiness

Mandatory tooth‑level context

Shared‑device security constraints

UI/UX impact

Must work on wall‑mounted & in‑surgery tablets

Needs:

Large touch targets

Glanceable status indicators

No deep navigation or scrolling

Strong visual distinction between:

Awareness vs action

Designer notes

Treat as a real‑time operational dashboard

Zero tolerance for clutter

%20v1.0.docx&action=default&mobileredirect=true&DefaultItemOpen=1)

5️⃣ Staff App Mode (Mobile Staff Experience)

Why it’s important This replaces WhatsApp and informal comms for staff.

What changed

Dedicated staff‑only mobile surface

Rota‑aware quiet hours

Auditable, revocable communication

UI/UX impact

Needs to feel:

Fast

Respectful of work/life boundaries

Strong emphasis on:

Notifications

Quick actions

Must not feel like a patient app “with extras”

Designer notes

Calm, utility‑first mobile UX

Avoid social/chat app styling

%20v1.0.docx&action=default&mobileredirect=true&DefaultItemOpen=1)

6️⃣ Digital Forms

Why it’s moderate impact Functionally similar, but mentally repositioned.

What changed

Explicitly the system of record

Anti‑PDF / anti‑portal positioning

Embedded into appointments and journeys

UI/UX impact

Forms UI must:

Feel native, not document‑like

Clearly show completion / compliance state

Better in‑flow form surfacing (not buried in menus)

Designer notes

Think guided workflows, not uploads

7️⃣ Aftercare Manager

Why it matters Aftercare becomes ongoing care support, not a download.

What changed

Structured, treatment‑linked aftercare

Patient questions flow through AI first, then escalate

Clear audit trail

UI/UX impact

Patient UI needs:

Easy re‑access

Clear, readable formatting

Staff UI needs:

Signals for issues / escalations

Designer notes

Reassuring tone

Very readable on mobile

/MVP/Surgery%20%26%20Decon%20Day%20View%20%E2%80%93%20Technical%20Specification%20v2.0.docx)

8️⃣ Smart Dashboards

Why it’s lower risk Conceptually clearer than older dashboards.

What changed

Explicitly not reporting tools

Focused on:

Today / this week

Exceptions and risks

UI/UX impact

Glanceable, role‑based summaries

Strong linking from insight → action

Designer notes

Minimal charts

Prioritisation > aesthetics

%20v1.0.docx&action=default&mobileredirect=true&DefaultItemOpen=1)

9️⃣ Document Hub

Why it’s lower impact Logical evolution rather than functional shift.

What changed

Single governed document source

No uncontrolled copies

UI/UX impact

Requires clear:

Document provenance

Visibility / acknowledgement states

Designer notes

Trust and clarity over visual novelty

🔟 Family Profiles

Why it’s stable Enhancement, not redesign.

What changed

Stronger consent and delegation clarity

UI/UX impact

Slight increase in relationship indicators

Clear “acting on behalf of” states

Designer notes

Subtle but explicit context cues

1️⃣1️⃣ Access Manager & Security (Foundational)

Why lowest UI impact Primarily invisible UX, by design.

What changed

Platform‑wide identity and security baseline

UI/UX impact

Login, device switching, permissions states

Error and denial states must be human‑readable

Designer notes

Security should feel calm and silent

/MVP/Staff%20App%20Mode%20%E2%80%93%20Technical%20Specification%20v2.0.docx)%20v1.0.docx&action=default&mobileredirect=true&DefaultItemOpen=1)

✅ Designer takeaway (high‑level)

Greatest design effort should go into:

Task Manager

Communication Hub

Appointment Manager

Surgery & Decon Day View

These define Primoro’s identity as an operating system, not just an app.

If you want, next I can:

Turn this into a one‑page visual brief / slide for handover

Produce “UI danger areas” callouts per module

Map Web vs Tablet vs Mobile surfaces module‑by‑module

Just tell me which format your designer would prefer.