Design case study · Healthcare UX

Hospital management system

A user story case study. How I take a hospital from information stuck on paper to stories a team can build: who the people are, what has to be true for each task, and what a screen has to do about it.

Role
Product and UX designer
Coverage
12 roles, 17 areas of the hospital, 74 stories
Priority
40 Must, 29 Should, 5 Could
Deliverables
Role profiles, story map, prioritised stories with acceptance criteria, four wireframes, release plan, success measures
Industry
Healthcare
Status
A design framework for a new hospital engagement. Not a shipped hospital system.

Overview

A hospital runs on small handovers. A name passes from the front desk to a doctor, an order from the doctor to the lab, a result back again, a bill out to an insurer. Most of the delay and most of the risk sit in those handovers, not in the clinical work itself.

This case study follows how I turn that web into user stories a team can build and a hospital can check, and how I carry the riskiest ones into a designed screen.

What this is, and is not. It is a design framework for a new hospital engagement. It is not a record of a shipped hospital system. The healthcare I have delivered is the laboratory portal and related tools at Triquetra, in the project brief. The roles, stories and screens here are what I bring to a new hospital, to be rewritten with that hospital's own staff.

The problem

Most delays in a hospital are not clinical. They come from information stuck on paper or in separate systems.

  • Long queues at registration and billingThe same details are asked at every counter, and a returning patient can take longer to find than to treat.
  • Records scattered across departmentsThe doctor, the lab, the pharmacy and the ward each hold part of the picture, so someone has to carry it between them.
  • Billing delays and missed chargesCharges are collected from department slips at the end, so some are missed and the patient waits at discharge.
  • No live view for managementOccupancy, footfall and revenue are known at month end, when the decisions they should have informed are already made.

The approach

  1. Walk the floor

    Sit with the doctors, nurses, front desk, pharmacy, lab and billing teams and write down how work really moves. For a real hospital this always comes first. Here I have drawn the roles from how a typical Indian multi-specialty hospital runs. They are the first thing I would check with real staff.

    Produces: Current-state flows, observation notes

  2. Name the people

    Twelve roles, each with a day, what goes wrong today and what the system has to do for them.

    Produces: Role profiles

  3. Map the journey

    Follow one patient from booking to follow-up, and lay every story along that path, release by release.

    Produces: Story map

  4. Write the stories

    Who, in which moment, wants what, and why. Then what must be true for it to count as done, and the edge case that usually gets missed.

    Produces: 74 stories with acceptance criteria

  5. Prove it in a screen

    Draw the riskiest stories as wireframes and put them in front of the people who do the job.

    Produces: Wireframes, usability test plan

  6. Release in slices

    One department at a time, with training and support at each step, so the hospital keeps running while it changes.

    Produces: Release plan, definition of done

The people

Twelve roles. For each: what a day looks like, what goes wrong today, and what the system has to do. Every story belongs to one of them.

Front desk executive

A day. Registers fifty to a few hundred people before lunch, answers the phone with one hand, and tells patients where to go.

What goes wrong today. Hunts for the patient's file, retypes the same details at three counters, and creates a second record because the first one could not be found.

What the system has to do. One search that finds anyone fast, a short registration form, and a queue everybody can see.

Consultant (OPD doctor)

A day. Sees a patient every few minutes, reads a history, decides, writes it down, and moves on.

What goes wrong today. Loses minutes clicking through tabs, rewrites notes the system already holds, and finds out about a lab result a day late.

What the system has to do. The whole patient on one screen, quick documentation, and results that come to them.

Ward nurse

A day. Looks after a group of beds across a shift: vitals, medicines, dressings, handover, and every family question in between.

What goes wrong today. Writes on paper first and enters later, misses an order changed an hour ago, and loses detail at handover.

What the system has to do. Bedside entry that is quicker than paper, a clear list of what is due now, and a handover that cannot be skipped.

Emergency team

A day. Triage nurse and emergency doctor working against the clock, often with patients who cannot speak for themselves.

What goes wrong today. Registration paperwork delays treatment, and nobody can see who has been waiting longest.

What the system has to do. A record opened in seconds without an identity, and a board that shows the sickest and the longest waiting.

Lab technician

A day. Collects, receives, runs and verifies samples against a stack of orders, some of them urgent.

What goes wrong today. Retypes results from the analyser, chases wards about rejected samples, and phones doctors about critical values.

What the system has to do. A priority-ordered worklist, results that flow in from machines, and a critical value route that cannot be ignored.

Radiology technician and radiologist

A day. Schedules scans, runs them, and reports against a queue, with preparation rules for each study.

What goes wrong today. Patients arrive unprepared, orders lack clinical details, and reports reach the doctor late.

What the system has to do. Slots with preparation instructions, a clean worklist, and a report that lands in the doctor's view.

Pharmacist

A day. Dispenses outpatient prescriptions and ward requests while watching stock and expiry.

What goes wrong today. Deciphers handwriting, phones the doctor to confirm, and finds an expired batch on the shelf at the wrong moment.

What the system has to do. A clear digital prescription, the right batch suggested, and stock that updates as they dispense.

Billing and insurance executive

A day. Closes bills, raises pre-authorisations with insurers and TPAs, and follows claims for weeks.

What goes wrong today. Finds missed charges at discharge, rebuilds the bill from department slips, and loses claims to missing documents.

What the system has to do. Charges that post themselves, a bill the patient can follow, and a claim tracker that shows what is stuck and why.

Store and purchase officer

A day. Keeps the hospital supplied: indents, purchase orders, goods received, and expiry.

What goes wrong today. Stock-outs found by the ward, not the store, and purchase approvals stuck in a file.

What the system has to do. Reorder levels that warn early, approvals that travel, and receipts matched to orders.

Hospital administrator

A day. Decides on staff, beds and money, and answers to management, insurers and auditors.

What goes wrong today. Waits for month-end reports, cannot see occupancy right now, and cannot show who opened a record when an audit asks.

What the system has to do. A live view with its timestamp, reports in the format management already uses, and an audit trail.

Patient and family

A day. Anxious, short of time, often with a child or a parent in tow, and not sure where to go next.

What goes wrong today. Queues to book, calls to ask where a report is, and cannot read the bill.

What the system has to do. To book, see reports and pay from the phone, in a language they are comfortable with.

IT and compliance lead

A day. Keeps systems running, people's access correct, and the hospital ready for an audit.

What goes wrong today. Shared logins, leavers who still have access, and no record of who saw what.

What the system has to do. Roles that match jobs, quick access changes, and a trail they can show an auditor.

Story map

One patient's journey runs left to right. Each row is a release. Every box is an area of the hospital, with the number of stories in it. The areas link to their stories.

Book
Arrive
Consult
Tests and medicine
Stay
Pay and claim
Follow up
Run the hospital
Phase 1the front of the house and the money
Phase 2tests and medicines
Phase 3beds, wards and theatres
Phase 4apps and deeper integration
AlwaysAll phases
Platform 6 Sign-in, working offline, bringing old records in, training, connections and privacy

Online booking can start in Phase 1 as a simple web page. The patient and doctor apps come later because they are only as good as the data behind them.

Principles behind every story

  1. Enter it once. A patient is registered once. A doctor's order becomes the lab's worklist, the pharmacy's queue and a line on the bill. Every time a person has to type the same thing twice, the system is leaking time and adding a chance to be wrong.
  2. Make the safe path the fast path. A duplicate warning that takes ten seconds will be skipped. A duplicate warning that is the quickest way to open the right record will be used. When safety and speed pull apart, I redesign until they do not.
  3. Show the state. Never make people guess. Pending, collected, resulted, verified, corrected. A figure on a dashboard says when it was last updated. A department that is not connected yet says so, and does not show a zero.
  4. Every change leaves a trace. Results are corrected, not overwritten. Prescriptions are re-issued, not edited. The record can answer who saw this, who changed it, and what it said before.
  5. Design for the worst hour, not the demo. The queue at ten in the morning, the ward when the network drops, the emergency with an unknown patient. If it only works on a quiet day with good Wi-Fi, it does not work.
  6. Respect the doctor's five minutes. Take out steps. Do not take out information. When something must be seen, it is on the screen. When it is rarely needed, it is one tap away.
  7. Train inside the product. People learn a hospital system on shift, between patients. Guidance sits in the screens, each role gets a practice area with fake patients, and someone from the project is on the floor in the first week.

From story to screen

Four stories carried all the way to a wireframe: the ones where a wrong design costs the most. Each shows the story, what must be true, the decisions behind the screen, and how I would test it with the people who use it.

REG-3 Registration

Stop a duplicate before it is created

The safest moment to stop a duplicate is before it exists, and the front desk is the only person who can.

As a front desk executive, when the details I type look like an existing patient, I want to see the likely match before I can save, so that nobody ends up with two files.

Wireframe. Sample data, no real patient. The numbers match the decisions on the right.

Done when

  • A warning appears when name, date of birth and mobile number closely match an existing record.
  • The match shows enough to decide: photo if held, age, last visit, address area.
  • 'Same person' opens the existing record straight away.
  • Creating a new record anyway needs a reason, and the reason is logged.
  • Duplicates that slip through can be found later and merged by an authorised person (REG-5).

Design decisions

  1. The warning sits inline, above the form. A modal would cover what the desk has typed, and that typing is exactly what they are trying to protect.
  2. The match shows last visit, age and area, not just a name. Two people called Rajesh Kumar look identical until the desk sees the last visit date.
  3. The safe action is the primary button and first in the tab order, so pressing Enter takes the careful path.
  4. Creating a new record anyway is allowed, because twins and namesakes exist, but it asks for a reason. The reason becomes part of the audit trail.

How I would test it

Give front desk staff ten registrations, three of them near-duplicates, with and without the warning. Count duplicates created and seconds per registration.

OPD-2 Outpatient consultation

Open the whole patient on one screen

A doctor spends the day on this one screen. The test of it is whether a safety-critical fact ever needs scrolling to find.

As a consultant with a patient in front of me, I want their history, allergies, current medicines, latest results and last note on one screen, so that I do not hunt through tabs while they wait.

Wireframe. Sample data, no real patient. The numbers match the decisions on the right.

Done when

  • Allergies and chronic conditions sit at the top and are always visible.
  • The last visit shows a short summary and what has changed since.
  • Latest lab and radiology results show with the previous values beside them.
  • Documents scanned from other hospitals are listed.
  • Every item carries its date and the person who recorded it.
  • Opening the record is logged.

Design decisions

  1. The allergy sits in the header and never scrolls away. If a doctor has to look for an allergy, the screen has failed.
  2. Long-term conditions sit beside it, so the doctor reads the person before the numbers.
  3. Each result comes with the previous value and its date. The doctor sees direction, not only a figure.
  4. Everything carries when it was recorded and by whom. Doctors trust what they can place in time. Today's vitals appear as soon as the nurse saves them, so nobody is asked twice.

How I would test it

Hand a doctor a patient with a hidden allergy in the record and time how long it takes to state it, on this layout and on a tabbed one.

LAB-4 Laboratory

Make a critical value impossible to miss

This is the one failure the system exists to prevent: a dangerous result that waits unread.

As a lab technician, when a result is critical, I want the responsible doctor or nurse to be alerted and to have to acknowledge it, so that a dangerous value is acted on in minutes.

Wireframe. Sample data, no real patient. The numbers match the decisions on the right.

Done when

  • The hospital sets which values are critical for each test.
  • The alert reaches the ordering doctor, and the nurse in charge for an inpatient.
  • It stays visible until someone acknowledges it.
  • If nobody acknowledges within the agreed time, it escalates.
  • The time the alert went out, who saw it and the action are recorded.

Design decisions

  1. The value, unit, reference range and previous result sit together, so the doctor can judge the alert without opening anything.
  2. The alert is marked with an icon and the word Critical, never colour alone. It reads in a bright ward and for colour-blind staff.
  3. It stays until someone acknowledges it. There is no dismiss, only acknowledge, and the person and time are recorded.
  4. The escalation path is shown, so everyone knows what happens if nobody answers. The times are set by the hospital, not by the designer.

How I would test it

Simulate a critical result at three times of day with the doctors and nurses on duty. Measure the time from alert to acknowledgement, and whether the right person responded.

NUR-2 Nursing

Give medicines against the order

Most medicine errors happen at the moment of giving. The screen slows down that one moment, and is fast everywhere else.

As a ward nurse at medicine time, I want a list of what is due now for each patient, with a check of patient, drug, dose, route and time, so that I give the right medicine and record it as I do it.

Wireframe. Sample data, no real patient. The numbers match the decisions on the right.

Done when

  • The list is sorted by due time, with overdue doses first.
  • I confirm the patient's identity, by scanning the wristband where the hospital has them, before I record.
  • Dose, route, time and my identity are recorded.
  • A missed or refused dose needs a reason, and the doctor is told.
  • High-alert drugs ask for a second nurse's confirmation.
  • If the doctor changes an order, I see it at once, marked as changed.

Design decisions

  1. Overdue doses come first, sorted by how late they are, so the nurse never has to look for what matters.
  2. Confirming the patient is part of giving the dose, by wristband scan where the hospital uses them. The moment that needs care is slowed down on purpose.
  3. A high-alert drug carries a clear tag and asks for a second nurse before the dose can be recorded.
  4. A changed order says so on its own line, with the time it changed. The nurse should never give against an order that has moved.

How I would test it

Run a mock medicine round on a quiet ward with real staff. Note taps per dose and any near miss of a wrong patient.

All 74 stories

17 areas of the hospital. Open an area to read its stories, and open a story for what must be true, why it matters and the edge case.

Must The release it belongs to cannot go live safely without it. Should Important and planned for the same release, but the department can start without it. Could Worth doing once the core is stable.

Registration and patient identity

5 stories · Phase 1
Goal
One person, one record, found in seconds. Everything else in the hospital hangs off this, so a wrong or duplicate record spoils every department after it.
Watch for
Duplicate records, the wrong patient opened, and a registration form so long that the queue grows.
Who
Front desk executive, patient, records administrator

REG-1Find a returning patientMust

As a front desk executive in the morning rush, I want one search box that finds a returning patient by name, mobile number or UHID, so that I can start the visit without asking them to repeat themselves.

Done when, why it matters, edge case

Done when

  • Partial names and partial mobile numbers both match, and the search forgives common spelling differences between English, Kannada and Hindi names.
  • Each result shows name, age, sex, last visit date and the last digits of the phone number, so I can tell two people with the same name apart without opening either record.
  • I can scan a barcode on the patient's card or printed slip instead of typing.
  • Results appear quickly on the hospital's own network. The target to agree is under two seconds.
  • If nothing matches, 'Register as new' is one click and carries over whatever I already typed.

Why it matters

Most of the time at a registration counter goes on finding the person, not typing their details. The result list is the screen that matters, more than the form.

Edge case

A patient registered years ago under a different spelling, or with a number they no longer use.

REG-2Register a new patient with the minimumMust

As a front desk executive registering a first-time patient, I want to capture only what is needed to start care and finish the rest later, so that the queue keeps moving.

Done when, why it matters, edge case

Done when

  • Required to save: name, age or date of birth, sex and a mobile number.
  • A UHID is issued immediately and given to the patient on a slip or by SMS.
  • Address, ID proof, emergency contact and insurance details can be added later. Records missing them carry an 'incomplete' marker the next person can see.
  • If the patient has an ABHA number, I can link it here.
  • Consent to hold their data is recorded with the time and my name.

Why it matters

Every field I make mandatory at the desk becomes a longer queue. Required fields should be the ones the clinic cannot safely work without, and nothing more.

Edge case

A family that shares one mobile number. Allow it, but show that the number belongs to more than one patient.

REG-3Stop a duplicate before it is createdMust

As a front desk executive, when the details I type look like an existing patient, I want to see the likely match before I can save, so that nobody ends up with two files.

Done when, why it matters, edge case

Done when

  • A warning appears when name, date of birth and mobile number closely match an existing record.
  • The match shows enough to decide: photo if held, age, last visit, address area.
  • 'Same person' opens the existing record straight away.
  • Creating a new record anyway needs a reason, and the reason is logged.
  • Duplicates that slip through can be found later and merged by an authorised person (REG-5).

Why it matters

Two records for one patient means a doctor misses an allergy or a result that is sitting in the other file. It is a clinical risk, so the safe path has to be the quickest one.

Edge case

Twins, or a father and son with the same name and the same phone.

REG-4Open a record for an unknown emergency patientMust

As an emergency desk executive, when an unconscious patient arrives with no ID and no relative, I want to open a temporary record in seconds, so that tests and treatment start now and the identity is added later.

Done when, why it matters, edge case

Done when

  • One action creates a temporary record with a generated identity, for example 'Unknown male, about 40 years, 14:32'.
  • Orders, notes and results can be added at once.
  • I can mark the case as medico-legal.
  • When the person is identified, details are added and the temporary record is merged with an audit entry.
  • The record is visible on the emergency board straight away.

Why it matters

In an emergency the system must never ask for something the patient cannot give. A perfect record is not worth a delayed treatment.

Edge case

Several unknown patients arrive together after an accident.

REG-5Correct or merge records safelyShould

As a records administrator, I want to correct a wrong detail or merge two records of one person with a full trail, so that the patient's history ends up in one place and nothing is lost.

Done when, why it matters, edge case

Done when

  • A correction needs a reason, and the old value stays in the history.
  • A merge shows both records side by side and says what will happen to each department's data.
  • Only roles with that permission can merge. A second person confirms.
  • Every merge writes an audit entry.
  • A merge can be reversed within an agreed period.

Why it matters

Merging is the riskiest edit in the whole system. It gets a preview and a second pair of eyes.

Edge case

Both records have an open admission.

Appointments and online booking

5 stories · Phase 1
Goal
Fewer calls, fewer empty slots, shorter waits. The booking page, the desk and the doctor all look at the same calendar.
Watch for
Online slots the desk cannot honour, doctors who are late with no word to the waiting room, and no-shows.
Who
Patient, front desk executive, consultant

APT-1Book a doctor from my phoneShould

As a patient, I want to pick a doctor and a real available time from my phone, so that I do not have to call or stand in a queue just to fix a time.

Done when, why it matters, edge case

Done when

  • I can search by doctor or specialty.
  • The slots I see are the same ones the front desk sees. There is one calendar.
  • Booking takes no more than four steps, and the fee is shown before I confirm.
  • A new patient can book without registering first, and is pre-registered from what they enter.
  • I get a confirmation by SMS and in the app.
  • Everything is available in English and in at least one local language.

Why it matters

A slot shown online that the desk then refuses is worse than no online booking. One calendar is the whole design.

Edge case

Two people take the last slot at the same moment. The second sees the updated slots and is not charged.

APT-2Move or cancel without callingShould

As a patient whose plan has changed, I want to reschedule or cancel in the app, so that the slot goes to someone else and I am not charged by mistake.

Done when, why it matters, edge case

Done when

  • Rescheduling only offers valid slots.
  • Cancelling returns the slot to the calendar at once.
  • Any fee or refund rule is shown in plain words before I confirm.
  • The doctor's list and the desk's list update immediately.
  • Reminders for the old time stop.

Why it matters

People cancel when it is easy. The easier it is, the sooner the slot can go to another patient.

Edge case

Cancelling inside the no-refund window.

APT-3Set and change my availabilityMust

As a consultant, I want to set my clinic days, timings, slot lengths and blocked time, so that bookings match when I can really see patients.

Done when, why it matters, edge case

Done when

  • I can set a weekly pattern and make one-off changes.
  • A first visit and a follow-up can have different slot lengths.
  • Taking leave blocks the slots and offers affected patients a new time.
  • Changes appear on the booking page immediately.
  • The desk can request a change but cannot override mine without permission.

Why it matters

The calendar is only as honest as the doctor's schedule behind it. If changing it is a chore, it will be out of date by Wednesday.

Edge case

A surgery overruns. Waiting patients get a delay notice and a choice to rebook.

APT-4Give a walk-in patient a tokenMust

As a front desk executive, I want to give a walk-in patient a slot or queue token in one step, so that booked and unbooked patients wait in one visible queue.

Done when, why it matters, edge case

Done when

  • Booked and walk-in patients appear in one queue per doctor.
  • The patient gets a token number and an approximate wait.
  • I can move an urgent case up, and I must give a reason.
  • The waiting room screen shows token numbers only, never names.

Why it matters

A screen that calls out a name in a waiting room tells everyone why that person is there. Tokens protect privacy and are quicker to read.

Edge case

A patient with appointments with two doctors on the same morning.

APT-5Reminders that cut no-showsCould

As a clinic manager, I want automatic reminders and follow-up nudges, so that fewer slots go empty.

Done when, why it matters, edge case

Done when

  • A reminder before the visit lets the patient confirm, cancel or reschedule in one tap.
  • A follow-up reminder is sent when a doctor has asked for a review.
  • Messages carry no clinical detail.
  • Patients can opt out.
  • The no-show rate is reported by doctor and by department.

Why it matters

A message sent to a wrong or shared number can reach someone else, so a reminder says when and where, never why.

Edge case

The number on file now belongs to a stranger.

Outpatient consultation

6 stories · Phase 1
Goal
Give the doctor the whole patient on one screen and take the typing out of the consultation, so the time goes to the person in front of them.
Watch for
Tabs, scrolling to find an allergy, notes rewritten from scratch, and prescriptions that reach the pharmacy unclear.
Who
Consultant, triage nurse, patient

OPD-1See my queue and who is nextMust

As a consultant starting clinic, I want today's patients in order, with the reason for the visit and any flags, so that I know what the next ten minutes hold before I call the patient in.

Done when, why it matters, edge case

Done when

  • The list shows token, name, age, sex, reason for visit and whether it is a new or follow-up visit.
  • Allergies and critical alerts show in the list itself.
  • Vitals taken by the nurse appear as soon as they are saved.
  • Calling the next patient is one action, and the waiting room display updates.
  • A patient who steps out for a test can be put 'on hold' and keeps their place.

Why it matters

A queue the doctor can read at a glance sets the pace of the whole morning.

Edge case

A patient who arrived late for a booked slot while walk-ins have been waiting.

OPD-2Open the whole patient on one screenMust

As a consultant with a patient in front of me, I want their history, allergies, current medicines, latest results and last note on one screen, so that I do not hunt through tabs while they wait.

Done when, why it matters, edge case

Done when

  • Allergies and chronic conditions sit at the top and are always visible.
  • The last visit shows a short summary and what has changed since.
  • Latest lab and radiology results show with the previous values beside them.
  • Documents scanned from other hospitals are listed.
  • Every item carries its date and the person who recorded it.
  • Opening the record is logged.

Why it matters

This is the screen a doctor spends the day on. If an allergy needs scrolling to find, the screen has failed.

Edge case

A patient with twenty years of history. Show what is relevant first and keep the rest one tap away.

OPD-3Write the consultation note quicklyMust

As a consultant finishing a consultation, I want to start from the patient's last note and structured defaults, so that the record is complete in less time and with fewer typing mistakes.

Done when, why it matters, edge case

Done when

  • Content from the previous visit is pre-filled, with what changed highlighted.
  • Only clinically or legally required fields are mandatory.
  • The draft saves itself and survives an interruption.
  • Signing locks the note. Later changes are saved as new versions.
  • Choices are structured fields. Free text stays free for the things a form cannot hold.

Why it matters

Speed and accuracy pull in opposite directions in documentation. Pre-filled text nobody reads is a new kind of error, so what changed has to be impossible to miss.

Edge case

The doctor is called away to an emergency halfway through a note.

OPD-4Prescribe safelyMust

As a consultant, I want to write a prescription with dose, frequency and duration and see allergy and duplicate-drug warnings before I sign, so that the pharmacy receives something clear and safe.

Done when, why it matters, edge case

Done when

  • Drug search works on generic and brand names.
  • I can keep sets of my common prescriptions.
  • The system warns on a recorded allergy and on a repeated active ingredient.
  • Dose, route, frequency and duration are required.
  • The printed and digital copies are identical, and the pharmacy sees it without retyping.
  • Changing a signed prescription creates a new version.

Why it matters

Handwriting and phone calls to confirm a drug are two of the most avoidable delays between a consultation and a medicine in hand.

Edge case

A drug that is not in the hospital's list. It can be written as free text, but the pharmacist is asked to review it.

OPD-5Order tests and imagingMust

As a consultant, I want to order lab and radiology tests during the consultation and see where each one stands, so that results come back to me and the patient is not sent to a counter to explain it again.

Done when, why it matters, edge case

Done when

  • Common work-ups are available as order sets.
  • Each order has a priority: routine or urgent.
  • Preparation, such as fasting, appears on the order and on the patient's copy.
  • Status shows ordered, sample collected, resulted.
  • I am notified when results are ready, and billing is triggered automatically.
  • Ordering a test that was done in the last few days shows a warning.

Why it matters

An order that carries its own instructions saves the patient a second trip and the department a phone call.

Edge case

A patient who has already paid for a package that includes the test.

OPD-6Follow-up and referralShould

As a consultant, I want to set a follow-up date and refer a patient to another specialist inside the same system, so that continuity does not depend on the patient remembering.

Done when, why it matters, edge case

Done when

  • A follow-up date creates a reminder for the patient and a slot hint for the desk.
  • A referral carries the relevant history and my note.
  • The receiving doctor sees it in their list, and I can see whether it was accepted.
  • A referral outside the hospital produces a printable letter.

Why it matters

Care often drops between visits. A referral that arrives with its history spares the next doctor from starting over.

Edge case

A referral that the other specialist declines.

Inpatient admission, beds and discharge

5 stories · Phase 3
Goal
From the doctor's advice to admit, to the patient walking out with a clear summary, without the family going back and forth between counters.
Watch for
Beds that are 'free' but not cleaned, transfers that lose medicines and tasks on the way, and discharge delays that start the day before.
Who
Admission desk, ward doctor, bed manager, nurse

IPD-1Admit a patient from the doctor's adviceMust

As an admission desk executive, I want to admit a patient from the doctor's advice, with deposit and insurance details in one flow, so that the family is not sent between counters.

Done when, why it matters, edge case

Done when

  • Admission starts from the advice and pre-fills from registration.
  • Choosing a room category shows the tariff and what is free.
  • Deposit and insurance details are entered in the same flow.
  • Consent forms are generated, signed on paper or on screen, and stored with the record.
  • The ward is told a patient is on the way.

Why it matters

Admission is stressful for the family. The fewer times they are asked for the same thing, the better the first impression of the whole stay.

Edge case

A patient admitted through emergency with no paperwork. It is completed afterwards.

IPD-2See which beds are freeMust

As a bed manager, I want a live board of beds by ward and status, so that I can place the next patient without phoning around.

Done when, why it matters, edge case

Done when

  • Status is one of occupied, reserved, being cleaned or blocked, and changes as patients are admitted, transferred or discharged.
  • Housekeeping marks a bed clean to release it.
  • A reservation has an expiry time.
  • Isolation and gender constraints are visible.
  • The board shows how long a bed has been waiting since discharge.

Why it matters

The delay between 'discharged' and 'ready for the next patient' is where beds are lost. The board shows that delay so someone can act on it.

Edge case

A bed held for a planned surgery that is postponed.

IPD-3Ward round with the data at the bedsideShould

As a ward doctor on rounds, I want the patient's trend, pending results and today's tasks on a tablet, so that I can decide and order at the bedside.

Done when, why it matters, edge case

Done when

  • The view shows the vitals trend, intake and output, and new results since yesterday.
  • Orders placed at the bedside reach the nurse and the pharmacy immediately.
  • My round note is tied to the patient and the time.
  • Items still pending for the day are listed.

Why it matters

A round where the doctor is walking back to a desk to look something up is a round that loses minutes with every patient.

Edge case

A ward with a weak network. The data needed for the round is available offline.

IPD-4Transfer between wards or bedsShould

As a ward nurse, I want to move a patient to another bed or ward with everything going along, so that nothing is lost on the way.

Done when, why it matters, edge case

Done when

  • A transfer request states the reason, and the receiving ward accepts it.
  • Charges change to the new room category from the time of transfer.
  • Pending medicines and tasks go with the patient.
  • The old bed moves to cleaning.

Why it matters

Transfers are a classic place for a dropped medicine or a wrong bill. They need to be one flow, not three phone calls.

Edge case

A transfer to intensive care in the middle of a medicine round.

IPD-5Discharge with a clear summaryMust

As a ward doctor, I want a discharge summary built from the stay's own data, so that I do not rewrite what the system already knows and the patient leaves with a document they can follow.

Done when, why it matters, edge case

Done when

  • The summary is pre-filled with diagnoses, procedures, key results, medicines and follow-up.
  • I edit and sign it.
  • A discharge checklist shows bills cleared, medicines dispensed and results pending, and is visible to every department involved.
  • A discharge against medical advice is recorded with the reason and consent.
  • Medicine instructions are written in plain language and can be given in the patient's own language.

Why it matters

Many discharge delays are decided the day before. A shared checklist makes each blocker visible while there is still time to clear it.

Edge case

A result that is still pending at the time of discharge.

Nursing care on the ward

5 stories · Phase 3
Goal
Make bedside entry quicker than paper, so nurses actually use it, and make the handover impossible to skip.
Watch for
Charting on paper first and typing later, medicines given against an order that was changed, and information lost at shift change.
Who
Ward nurse, nurse in charge, quality officer

NUR-1Record vitals at the bedsideMust

As a ward nurse, I want to record vitals on a phone or tablet at the bedside, so that the chart is correct the moment I take the reading.

Done when, why it matters, edge case

Done when

  • Entry takes fewer taps than writing it on paper.
  • An out-of-range value is flagged as I enter it, with an early warning score where the hospital uses one.
  • Every reading is time-stamped and carries my name.
  • Entries made without a network are kept and synced later, with a clear sign of what has not yet synced.

Why it matters

If entry is slower than paper, nurses will keep a paper copy as well, and the system becomes a second job.

Edge case

A reading entered against the wrong patient. It can be corrected, with a reason.

NUR-2Give medicines against the orderMust

As a ward nurse at medicine time, I want a list of what is due now for each patient, with a check of patient, drug, dose, route and time, so that I give the right medicine and record it as I do it.

Done when, why it matters, edge case

Done when

  • The list is sorted by due time, with overdue doses first.
  • I confirm the patient's identity, by scanning the wristband where the hospital has them, before I record.
  • Dose, route, time and my identity are recorded.
  • A missed or refused dose needs a reason, and the doctor is told.
  • High-alert drugs ask for a second nurse's confirmation.
  • If the doctor changes an order, I see it at once, marked as changed.

Why it matters

Most medicine errors happen at the point of giving. The screen's job is to slow that one moment down just enough, and to be fast everywhere else.

Edge case

An order changed a minute before I reach the bed.

NUR-3Hand over the shiftShould

As a ward nurse at shift change, I want one handover view per patient with vitals, pending medicines and tests, and alerts, so that nothing is lost between shifts.

Done when, why it matters, edge case

Done when

  • One screen per patient, with overdue medicines at the top.
  • The outgoing nurse adds a note, and the incoming nurse must acknowledge it.
  • My patient list opens on my own ward by default.
  • A patient with no acknowledgement is highlighted for the nurse in charge.

Why it matters

Handover is a known weak point in any ward. The design has to show that the next nurse actually saw it.

Edge case

A nurse who leaves in a hurry without finishing the handover.

NUR-4Care tasks and worsening alertsShould

As a nurse in charge, I want a list of care tasks and an alert when a patient's readings are getting worse, so that I can send help before it is an emergency.

Done when, why it matters, edge case

Done when

  • Recurring tasks such as dressings, turning and fluid balance appear on a schedule.
  • A worsening trend raises an alert with the readings behind it.
  • An alert that nobody acknowledges escalates to the nurse in charge and then to the doctor.
  • Alerts show who saw them and when.

Why it matters

A quiet drift in readings is easy to miss during a busy shift. An alert that cannot be ignored is the point.

Edge case

A sensor reading that is wrong, not the patient. The nurse can mark it so.

NUR-5Report an incident without blameCould

As a nurse, I want to report a near miss or an incident quickly, so that the hospital learns from it and nobody has to hide it.

Done when, why it matters, edge case

Done when

  • The form takes a minute and does not block my other work.
  • Reports go to the quality officer, and I can see that they were received.
  • Each report is tracked to closure.
  • Trends are reviewed by the quality team, and the hospital can use them for its accreditation records.

Why it matters

People report when it is easy and safe to. A long form, or one that feels like a charge sheet, guarantees silence.

Edge case

An incident where a patient has been harmed. It escalates to the duty manager straight away.

Emergency

3 stories · Phase 3
Goal
Treat first, complete the paperwork after. The sickest are seen first, and nobody is forgotten in a corridor.
Watch for
Forms that ask for what the patient cannot give, a board that shows names to the whole waiting room, and times that nobody records.
Who
Triage nurse, emergency doctor, emergency desk

ER-1Triage in under a minuteMust

As a triage nurse, I want to assign a triage level from the complaint and vitals and see a board of who is waiting, so that the sickest are seen first and nobody is forgotten.

Done when, why it matters, edge case

Done when

  • The category shows as a colour and also as text.
  • Vitals entry calculates the score where the hospital uses one.
  • Changing a category is allowed and is logged.
  • The board shows waiting time by category and highlights anyone past the agreed limit.
  • The board uses tokens or initials, never full names.

Why it matters

Triage is one decision made quickly and revisited often. The board is how the department stays honest about who has been waiting longest.

Edge case

A patient who looks stable at triage and gets worse in the waiting area.

ER-2Order in a crisisShould

As an emergency doctor, I want to place the common urgent orders in a couple of taps, so that I am treating the patient and not the software.

Done when, why it matters, edge case

Done when

  • Order sets exist for common emergencies, such as chest pain, stroke and trauma, and can be edited by the hospital.
  • Stat orders reach the lab, radiology and pharmacy with a clear urgent mark.
  • Key times are recorded: arrival, first doctor contact, first order, results and decision.
  • The doctor can add detail after the first minutes without losing what was already entered.

Why it matters

In a crisis, a doctor will pick the fastest route. If the software is slower than a verbal order, the order will be verbal and the record will be late.

Edge case

A verbal order given in an emergency, entered a few minutes later by someone else, with the person who gave it named.

ER-3Hand over to a ward or dischargeShould

As an emergency doctor, I want to record what happens next and send the patient on, so that the ward is ready and the summary is already written.

Done when, why it matters, edge case

Done when

  • The outcome is admit, discharge, refer or left against advice.
  • Admitting sends a bed request to the bed board.
  • The summary is pre-filled from the emergency visit.
  • The time of the decision is recorded.

Why it matters

The gap between a decision to admit and a patient reaching a bed is where emergency departments back up. It has to be measured to be reduced.

Edge case

No bed is available. The patient stays in emergency with a visible 'waiting for bed' status.

Laboratory

5 stories · Phase 2
Goal
The right sample from the right patient, a verified result in the record the moment it is ready, and a critical value that is never missed.
Watch for
Samples labelled by hand, results retyped from an analyser, and a critical result that sits unread.
Who
Phlebotomist, lab technician, pathologist, ordering doctor

LAB-1Collect the right sample from the right patientMust

As a phlebotomist, I want a worklist of orders with the patient, test, priority and tube type, so that I collect the right sample from the right person the first time.

Done when, why it matters, edge case

Done when

  • The worklist is sorted by priority and location.
  • A barcode label is printed at the bedside or counter, at the time of collection.
  • I confirm identity with two details before collecting.
  • Fasting status is shown and recorded.
  • Home-collection orders show the address and the booked time window.

Why it matters

A wrongly labelled tube is one of the quietest and most serious errors in a hospital. Labelling at the point of collection is the single best defence.

Edge case

A child or an unconscious patient who cannot confirm their name.

LAB-2Know where every sample isShould

As a lab technician, I want every sample to have a visible status from collected to reported, so that delays and rejections are found and fixed early.

Done when, why it matters, edge case

Done when

  • Status moves through collected, received, in process and reported.
  • Samples taking longer than the expected time are flagged.
  • A rejected sample, for example haemolysed or insufficient, needs a reason.
  • A rejection notifies the ward or the doctor and asks for a recollection.

Why it matters

A recollection costs the patient time and sometimes another needle. The earlier it is raised, the smaller the cost.

Edge case

A precious sample, such as a CSF sample, that cannot be collected again.

LAB-3Enter or receive results and verify themMust

As a lab technician, I want results to come in from the analysers where possible, and to be checked for unit and range before I verify them, so that wrong values do not reach the record.

Done when, why it matters, edge case

Done when

  • Where the hospital has connected analysers, results flow in without retyping.
  • Manual entry checks the unit and the expected range.
  • Only authorised people can verify.
  • A verified result becomes read-only.
  • A correction creates a visible new version, and the doctor who saw the first one is told.

Why it matters

Every retyped value is a chance for an error. Taking the typing away is the safest improvement in this department.

Edge case

A result that is plausible but wrong because the sample was mixed up. The trail has to make that investigable.

LAB-4Make a critical value impossible to missMust

As a lab technician, when a result is critical, I want the responsible doctor or nurse to be alerted and to have to acknowledge it, so that a dangerous value is acted on in minutes.

Done when, why it matters, edge case

Done when

  • The hospital sets which values are critical for each test.
  • The alert reaches the ordering doctor, and the nurse in charge for an inpatient.
  • It stays visible until someone acknowledges it.
  • If nobody acknowledges within the agreed time, it escalates.
  • The time the alert went out, who saw it and the action are recorded.

Why it matters

A critical potassium that sits in an inbox overnight is exactly the kind of failure a system should be built to prevent.

Edge case

An alert to a doctor who has gone off duty. It goes to the doctor now covering.

LAB-5A report people can readShould

As a doctor or patient, I want a lab report that shows the result beside the previous values, the reference range and a clear flag, so that I can see at once whether something has changed.

Done when, why it matters, edge case

Done when

  • The report shows the value, unit, reference range and previous values with dates.
  • Abnormal results are flagged with text and an icon, not colour alone.
  • The printed and digital versions match.
  • Tests not yet reported show an expected time.
  • A patient sees a report only after the doctor has released it.

Why it matters

A report that shows the trend answers the doctor's real question, which is whether this is getting better or worse.

Edge case

A report with a very large number of values, such as a full panel. The abnormal ones come first.

Radiology

3 stories · Phase 2
Goal
Patients arrive prepared, studies are scheduled sensibly, and the report reaches the doctor with the images a click away.
Watch for
Patients who have not fasted or have not brought a creatinine, orders with no clinical question, and reports that reach the wrong place.
Who
Radiology technician, radiologist, ordering doctor, patient

RAD-1Schedule a scan with the preparation doneShould

As a radiology technician, I want an ordered study to be booked into a slot with its preparation and safety checks, so that the patient arrives ready and the scanner is not idle.

Done when, why it matters, edge case

Done when

  • Each study type carries its own preparation instructions, sent to the patient.
  • A safety checklist covers pregnancy, implants, allergies and contrast.
  • The order includes the clinical question.
  • A patient who does not arrive is flagged so the slot can be reused.

Why it matters

An unprepared patient means a wasted slot and a second visit. Most of that can be prevented at booking.

Edge case

An urgent scan that has to be fitted in without moving a booked patient.

RAD-2Capture and reportMust

As a radiologist, I want a worklist of completed studies and report templates, with a link to the images, so that I can report efficiently and send the finding to the right person.

Done when, why it matters, edge case

Done when

  • The worklist is sorted by priority.
  • Report templates exist for common studies and can be edited by the hospital.
  • The report links to the hospital's image archive instead of storing images separately.
  • A critical finding raises an alert to the ordering doctor in the same way as a critical lab value.
  • A report is verified before release and a correction creates a new version.

Why it matters

The radiologist's time is the bottleneck. The software should hold the template and get out of the way.

Edge case

A study done outside and brought in on a disc.

RAD-3See the report with the imageShould

As a consultant, I want to open a radiology report and the image from the patient's record, so that I read them together in the same visit.

Done when, why it matters, edge case

Done when

  • The report appears in the results panel with a link to the images.
  • I am notified when a report for my patient is ready.
  • Previous studies are listed with dates, for comparison.
  • Opening a study is logged.

Why it matters

A doctor who has to ask for the image will often decide without it. One link removes that excuse.

Edge case

A very large study on a slow connection.

Pharmacy

5 stories · Phase 2
Goal
A clear digital prescription goes in, the right batch comes out, and stock reflects the shelf without a monthly count to find the gap.
Watch for
Out-of-stock found at the counter, expired batches, and substitutions made without the doctor knowing.
Who
Pharmacist, ward nurse, prescribing doctor

PHM-1Dispense from a digital prescriptionMust

As a pharmacist, I want a prescription to arrive in my queue with allergy checks and the stock for each item, so that I dispense correctly without calling the doctor.

Done when, why it matters, edge case

Done when

  • The queue separates outpatient and inpatient prescriptions.
  • Stock and batch show against each drug.
  • Allergy and interaction warnings follow the rules the hospital has agreed.
  • A substitution needs the doctor's confirmation.
  • Dispensing reduces stock and adds the item to the bill.

Why it matters

A call to the ward to read out a drug name is a delay and an error waiting to happen. The prescription should be unambiguous when it arrives.

Edge case

A prescription for a drug the hospital does not stock.

PHM-2Dispense the nearest-expiry batch firstShould

As a pharmacist, I want the system to suggest the batch that expires soonest, so that stock is used before it is wasted.

Done when, why it matters, edge case

Done when

  • The nearest-expiry batch is suggested by default.
  • Alerts warn at agreed intervals before expiry.
  • An expired batch cannot be dispensed.
  • Near-expiry stock can be flagged for return to the supplier.

Why it matters

Expiry is a quiet cost. A default that follows the right rule saves money without asking anyone to remember.

Edge case

A short-expiry batch that is the only stock left for a critical drug.

PHM-3Ward requests and controlled drugsShould

As a pharmacist, I want ward requests and controlled-drug issues to be recorded against the patient and the nurse, so that stock and accountability both stay accurate.

Done when, why it matters, edge case

Done when

  • Wards raise requests, and the pharmacy issues against them.
  • Each ward has stock levels and top-up levels.
  • Controlled drugs follow a register with a double signature.
  • Discrepancies are flagged at the end of the shift.

Why it matters

Controlled drugs are the one place where a register has to be exact. The system makes it the easy default.

Edge case

A partly used ampoule that has to be wasted and witnessed.

PHM-4Returns and wastageCould

As a pharmacist, I want returns and wastage recorded with a reason, so that stock is correct and the bill is fair.

Done when, why it matters, edge case

Done when

  • A return from a ward or patient requires a reason and creates a credit on the bill.
  • Wastage is logged against a reason such as breakage or expiry.
  • Returned stock goes back on the shelf only if it meets the hospital's rules.
  • Totals by reason appear in a report.

Why it matters

Without a reason, wastage is invisible. With one, it points at what to fix.

Edge case

A patient who returns an unopened strip after discharge.

PHM-5Handle an out-of-stock drugShould

As a pharmacist, when a prescribed drug is out of stock, I want to tell the doctor and suggest alternatives in one step, so that the patient is not sent away empty-handed.

Done when, why it matters, edge case

Done when

  • I can message the prescriber from the prescription.
  • Approved alternatives are listed.
  • The unmet demand is recorded for the purchase team.
  • The patient is told when the drug will be back, where known.

Why it matters

The same shortage shows up again next week unless the demand is recorded. A single click gives the purchase team its evidence.

Edge case

An out-of-stock drug for an inpatient due a dose in the next hour.

Billing and insurance

6 stories · Phase 1
Goal
Charges are captured where care happens, a bill the patient can follow, and cashless claims that are not stuck at discharge or lost for missing paper.
Watch for
Missed charges, disputes over a bill nobody can explain, pre-authorisations that run out, and rejected claims.
Who
Billing executive, insurance desk, patient, accounts

BIL-1Charges post themselvesMust

As a billing executive, I want charges to post automatically when a service is ordered or done, so that nothing is missed and I am not chasing departments.

Done when, why it matters, edge case

Done when

  • Each order or service adds a charge at the tariff for the patient's category: cash, insurance or corporate.
  • The running bill is visible at any time.
  • A charge cannot be changed without permission and a reason.
  • A charge posted after discharge is flagged.

Why it matters

Missed charges are revenue leakage, and they are also a source of corrections that the patient notices. Automation fixes both.

Edge case

A service delivered by a visiting doctor who is paid under a separate arrangement.

BIL-2Estimate and depositShould

As an admission desk executive, I want to give the family an estimate and track the deposit, so that nobody is surprised by the bill.

Done when, why it matters, edge case

Done when

  • An estimate for a planned admission uses the package or the expected charges.
  • The deposit is tracked against the running bill.
  • An alert appears when the deposit is nearly used.
  • The patient receives the estimate in writing.

Why it matters

The most heated moments in a hospital are often about money. A clear estimate early is the cheapest way to avoid them.

Edge case

An emergency admission with no time for an estimate.

BIL-3An itemised bill the patient can followMust

As a patient, I want an itemised bill grouped by department with dates, quantities and rates, so that I can see what I am paying for.

Done when, why it matters, edge case

Done when

  • Items are grouped by department with date, quantity and rate.
  • Package items and non-package items are clearly separate.
  • Tax is shown where it applies.
  • A discount needs approval from an authorised role, with a reason.
  • The printed and digital bills match.

Why it matters

A bill that can be read is a bill that is disputed less. Clarity here protects the hospital as much as the patient.

Edge case

A bill with hundreds of lines after a long stay. Summary first, detail on request.

BIL-4Raise a pre-authorisation and follow the claimMust

As an insurance desk executive, I want to raise a pre-authorisation, track its status and enhance it, and later submit the claim with the right documents, so that cashless patients are not stuck at discharge and claims are not rejected for missing paper.

Done when, why it matters, edge case

Done when

  • The request is pre-filled from the admission.
  • Status is tracked: requested, approved with an amount, queried or rejected.
  • An enhancement can be raised when the cost passes the approved amount.
  • A checklist shows the documents each insurer or TPA requires.
  • A claim tracker shows each claim's status and age.
  • Rejection reasons are recorded and can be reported on.

Why it matters

This desk lives in follow-ups. A tracker that shows what is stuck and why replaces a notebook and a lot of phone calls.

Edge case

An approval that arrives after the patient has already been discharged.

BIL-5Refunds and cancellationsShould

As a billing executive, I want refunds and cancellations to go through an approval linked to the original bill, so that money moves only with a reason and a name.

Done when, why it matters, edge case

Done when

  • A refund request refers to the original payment.
  • An authorised person approves it.
  • The refund is made by the same mode wherever possible.
  • Every step is in the audit trail.

Why it matters

Refunds are a place where mistakes and misuse both happen. A visible trail protects the honest majority.

Edge case

A refund for a payment made by a relative, not the patient.

BIL-6End-of-day settlementShould

As a cashier, I want to close my counter at the end of the day with the system's total by payment mode, so that cash, cards and digital payments reconcile without a long recount.

Done when, why it matters, edge case

Done when

  • The day's collections show by mode: cash, card, UPI, cheque.
  • I enter the cash I counted and the difference is shown.
  • A difference needs a note before I can close.
  • Accounts receives the settlement report.

Why it matters

Reconciliation is dull work that grows into a long evening if the figures are not ready. The system should have them ready.

Edge case

A shift that changes cashier in the middle of the day.

Operation theatre

3 stories · Phase 3
Goal
Theatre time used well, and a safety checklist that is a real stop, not a tick box filled in afterwards.
Watch for
Double-booked theatres, missing consent or tests on the day, and counts of swabs and instruments left to memory.
Who
Surgeon, anaesthetist, theatre nurse, theatre coordinator

OT-1Schedule a surgeryMust

As a theatre coordinator, I want to book a surgery with the surgeon, theatre, anaesthetist, team and equipment, so that nothing clashes and everything needed is ready.

Done when, why it matters, edge case

Done when

  • The booking shows conflicts for the theatre, the surgeon and the team.
  • Implants and special equipment are listed on the booking.
  • A pre-operative checklist covers consent, fasting and required tests.
  • Items not yet complete are visible to the whole team the day before.

Why it matters

A surgery postponed on the morning for a missing test costs the patient, the family and the theatre. Most of it is visible a day earlier.

Edge case

An emergency case that takes a slot that was booked.

OT-2Run the safety checklist as a real stopMust

As a theatre nurse, I want the safety checklist to be recorded at the three points before, during and after the operation, so that it is carried out and not filled in later.

Done when, why it matters, edge case

Done when

  • The sign-in, time-out and sign-out are recorded with the time and the names of the people present.
  • The next stage cannot be started without confirming the one before.
  • Any step skipped needs a reason.
  • The completed checklist is part of the patient's record.

Why it matters

A checklist is only useful if it interrupts the work for a moment. A form completed after the fact protects no one.

Edge case

An emergency where the time-out is shortened. It is still recorded.

OT-3Record the operation and what was usedShould

As a surgeon, I want an operation note template, and implants and consumables recorded with their batch details, so that the record is complete and the bill is correct.

Done when, why it matters, edge case

Done when

  • The note uses a template for the procedure and can be edited.
  • Implants are recorded with batch and serial numbers.
  • Consumables used are added to the bill automatically.
  • Instrument and swab counts are recorded and any difference is flagged before closing.

Why it matters

An implant that cannot be traced to a patient is a safety problem the day a recall notice arrives.

Edge case

A procedure that changes mid-way. The note records what was actually done.

Stores and purchase

3 stories · Phase 2
Goal
The ward never discovers a stock-out before the store does. Orders go through the right approvals and arrive matched to what was ordered.
Watch for
Approvals stuck in a file, goods received without a purchase order, and expiring stock found late.
Who
Store officer, purchase officer, department heads, accounts

STO-1Raise an indent and get stockMust

As a department in-charge, I want to request supplies from the store and see when they will arrive, so that I am not guessing whether the order was seen.

Done when, why it matters, edge case

Done when

  • An indent is raised from a list of items the department normally uses.
  • The store sees it, issues against it and the stock reduces.
  • Consumption by department is available as a report.
  • A partly met indent shows what is still pending.

Why it matters

The ward only knows its own needs. A visible indent saves the phone call that begins with 'did you get my request?'

Edge case

An urgent request outside store hours.

STO-2Purchase orders and goods receivedMust

As a purchase officer, I want orders to go through approvals by value and goods to be received against the order, so that what we pay for is what arrived.

Done when, why it matters, edge case

Done when

  • Orders go to approved suppliers.
  • Approval levels depend on the value of the order.
  • Goods received are matched to the order with batch and expiry details.
  • A mismatch in quantity or price is flagged before payment.

Why it matters

Matching what was ordered to what arrived is the control that matters most in purchasing. The system should do the comparing.

Edge case

A supplier delivers part of an order and substitutes an item.

STO-3Reorder before the stock-outShould

As a store officer, I want warnings when stock is nearing its minimum and a view of slow-moving items, so that I reorder in time and do not hold stock that never moves.

Done when, why it matters, edge case

Done when

  • Minimum levels are set per item.
  • A warning appears before the level is reached, with the usual lead time taken into account.
  • Slow-moving and near-expiry items are listed.
  • Alerts can be sent to the purchase officer.

Why it matters

A reorder level that only warns once the shelf is empty is a record of the problem and not a prevention of it.

Edge case

A seasonal item whose normal level changes through the year.

Blood bank

3 stories · Phase 3
Goal
Know exactly what is in stock, and trace every unit from donor to patient.
Watch for
Mislabelled units, expired components and requests that cannot be matched to a patient.
Who
Blood bank technician, requesting doctor, ward nurse

BB-1Know what is in stockMust

As a blood bank technician, I want to see units by group, component and expiry, with their testing status, so that I issue only what is safe and available.

Done when, why it matters, edge case

Done when

  • Stock is shown by blood group and component.
  • Units that are untested, in quarantine or close to expiry are clearly separate.
  • Expired or quarantined units cannot be issued.
  • Alerts warn when a group is running low.

Why it matters

Blood is a stock that expires quickly. Seeing it at a glance prevents both shortage and waste.

Edge case

A unit returned from a ward after being out of the cold chain.

BB-2Request, cross-match and issueMust

As a doctor or nurse, I want to request blood for a patient and see its progress, and as a technician I want to cross-match and issue it with the checks recorded, so that the right unit reaches the right patient.

Done when, why it matters, edge case

Done when

  • A request names the patient, the component and the reason.
  • Cross-match results are recorded before issue.
  • Issue records the unit number, the patient, the person collecting and the time.
  • Every unit is traceable from donor to patient.
  • A returned or unused unit is recorded with the reason.

Why it matters

A transfusion error is among the most serious in a hospital. Every step has a named person and a time.

Edge case

An emergency request for uncrossmatched blood, with the approving doctor recorded.

BB-3Donors and campsCould

As a blood bank technician, I want donor records and camp details in the system, so that donations are tracked and donors can be called back when they are eligible.

Done when, why it matters, edge case

Done when

  • A donor record holds screening results and the date of the last donation.
  • A donor who is not yet eligible cannot be bled.
  • Camp collections are recorded in a batch.
  • A donor can be reminded when they are due again.

Why it matters

A reliable donor list takes years to build and is quickly lost if kept in a notebook.

Edge case

A donor with a positive screening result. The result is handled privately and sensitively.

Management, reports and audit

4 stories · Phase 1
Goal
Decisions made on what is happening now, and an answer ready when an auditor asks who saw or changed a record.
Watch for
Figures with no timestamp, a department shown as zero because it is not connected, and access that outlives a person's job.
Who
Hospital administrator, department heads, IT and compliance lead

MGT-1See the hospital as it is nowShould

As a hospital administrator, I want live occupancy, footfall and revenue by department, so that I can decide on staffing and beds today, not at month end.

Done when, why it matters, edge case

Done when

  • Figures update as work is recorded and show an 'as of' time.
  • I can open a department and see the list behind a number.
  • A department that is not yet connected shows 'not connected', never zero.
  • Comparisons use the same period last week or last month.

Why it matters

A dashboard that people do not trust is ignored. Showing when the data was last updated is what earns the trust.

Edge case

A sudden spike in one department that is really a data entry backlog being cleared.

MGT-2Reports in the format we already useShould

As a department head, I want the reports management already uses, in that format, by department and by doctor, so that the system fits the meeting and not the other way round.

Done when, why it matters, edge case

Done when

  • Reports can be shaped to the hospital's existing formats.
  • They can be filtered by department, doctor and period.
  • They export to the formats the hospital uses.
  • Regular reports can be scheduled and sent.

Why it matters

A new system that forces everyone to learn a new report is asking for resistance. Match the old one first and improve it later.

Edge case

A report that needs data from a department that has not yet gone live.

MGT-3A trail of who saw and changed whatMust

As an IT and compliance lead, I want a searchable record of who opened or changed a patient's record, and when, so that I can answer an audit question or investigate a concern.

Done when, why it matters, edge case

Done when

  • The log records the person, the patient, the action and the time.
  • I can filter by user, patient, date and type of action.
  • Opening a record outside the person's usual patients needs a reason, and is reviewed.
  • Entries cannot be edited or deleted.
  • The log can be exported for an auditor.

Why it matters

A hospital holds some of the most private information about a person. The ability to show who looked at it is part of earning the right to keep it.

Edge case

A senior doctor who needs to open a record urgently outside their usual patients.

MGT-4Roles that match jobsMust

As an IT and compliance lead, I want access defined by role and changed quickly when a person joins, moves or leaves, so that nobody can see more than their job needs.

Done when, why it matters, edge case

Done when

  • Each role sees only what it needs.
  • A person can be given temporary access, which ends on its own.
  • Changes to access are approved and logged.
  • A leaver's access ends the same day, and a monthly review shows anyone who has not signed in for a long time.

Why it matters

Shared logins and forgotten accounts are how most privacy problems start. Making the right access easy to give removes the reason for shortcuts.

Edge case

A locum who covers for three days.

Patient app

4 stories · Phase 4
Goal
Book, see reports and bills, and pay from the phone, in a language the person is comfortable with, without having to call anyone.
Watch for
A sign-in that locks out older users, reports shown before a doctor has seen them, and a family member's data shown to the wrong person.
Who
Patient, parent or caregiver

PAT-1Sign in and find my recordsMust

As a patient, I want to sign in with my mobile number and see my own records, so that I do not need a password I will forget.

Done when, why it matters, edge case

Done when

  • Sign-in uses a one-time code to my mobile number.
  • I see only my own appointments, reports, prescriptions and bills.
  • I can add a child or a parent to my account, and each has their own record.
  • The app is available in English and in at least one local language, and text can be made larger.

Why it matters

The people who most need a hospital app are often the least comfortable with apps. A sign-in that works for them works for everybody.

Edge case

A patient who has changed their phone number.

PAT-2Reports, prescriptions and billsMust

As a patient, I want to see my reports, prescriptions and bills in one place, so that I can find them when I need them and share them with another doctor.

Done when, why it matters, edge case

Done when

  • A report appears once the doctor has released it, not before.
  • A new result sends a notification with no clinical detail in it.
  • Prescriptions are available to show a pharmacy.
  • Bills are itemised and can be downloaded.

Why it matters

Being told a result by an app before a doctor has had the chance to explain it is a cruelty the design can avoid.

Edge case

A sensitive result that the doctor wants to discuss in person first.

PAT-3Control who can see my recordShould

As a patient, I want to see who has accessed my record and to say who else may see it, so that I stay in control of my information.

Done when, why it matters, edge case

Done when

  • I can see a plain-language list of who has opened my record.
  • I can give consent to share with another provider, and withdraw it.
  • I can link my ABHA number where the hospital has switched that on.
  • I can ask for a correction or a copy of my data.

Why it matters

The DPDP Act gives patients rights over their data. Making those rights simple to use is better than describing them in a policy.

Edge case

A caregiver who manages a parent's records and needs their consent recorded.

PAT-4Pay and follow upShould

As a patient, I want to pay a bill, get a receipt and book my follow-up from the app, so that I do not have to wait at a counter for small things.

Done when, why it matters, edge case

Done when

  • I can pay online and download a receipt.
  • A follow-up the doctor advised is offered for booking.
  • Reminders arrive before an appointment.
  • I can ask the hospital a non-urgent question, with a clear message that it is not for emergencies.

Why it matters

A queue at a billing counter to collect a receipt is the kind of small friction that people remember longer than the treatment.

Edge case

A payment that fails after money has left the account.

Doctor app

3 stories · Phase 4
Goal
The day's patients and the results that matter, in a pocket, with the same safety rules as the desk.
Watch for
Patient data left on a personal phone, alerts that train people to ignore them, and orders placed too easily from a small screen.
Who
Consultant, visiting doctor, doctor on call

DOC-1Today at a glanceMust

As a consultant, I want my schedule, queue and flagged patients on my phone, so that I know what the day holds before I reach the hospital.

Done when, why it matters, edge case

Done when

  • Today's schedule and queue are shown.
  • Patients with a critical result or an urgent task are marked.
  • I can open a patient's summary.
  • The app locks after a short time and needs my sign-in again.

Why it matters

A doctor looking at the day's list on the way in is a doctor who starts clinic already oriented.

Edge case

A visiting doctor who works across two hospitals.

DOC-2Review results and respondShould

As a consultant, I want to be told when a result for my patient is ready and to acknowledge it, so that nothing important waits until I am back at my desk.

Done when, why it matters, edge case

Done when

  • Notifications carry no patient detail on the lock screen.
  • I open the result in the app and acknowledge it.
  • I can add a short instruction to the nurse.
  • Placing orders from the phone is limited to a safe set, with the rest left to the desktop.

Why it matters

The more urgent the result, the more it matters that the doctor acknowledges it. An alert that anyone can ignore is not an alert.

Edge case

A result that arrives while I am in the operating theatre.

DOC-3Cover patients when I am on callCould

As a doctor on call at night, I want to see a patient's history and the latest results from my phone, so that I can advise the ward without driving in for every call.

Done when, why it matters, edge case

Done when

  • I can see the summary, medicines and recent results of patients under my cover.
  • I can give a verbal or written advice that is recorded in the chart.
  • Access is only to the patients I am covering for that duty.
  • No patient data is stored on my phone after I sign out.

Why it matters

Being on call is where a good view of the patient matters most and a safe boundary on access matters just as much.

Edge case

A call about a patient who is not on my list.

Platform: security, resilience and rollout

6 stories · Across all phases
Goal
The unglamorous things that decide whether a hospital system survives its first year: sign-in, downtime, old data, training, connections and privacy.
Watch for
A sign-in that slows the ward, a network failure with no plan, old records that do not tie out, and training that stops the day the project team leaves.
Who
IT and compliance lead, every user, the project team

PLT-1Sign in securely without slowing the wardMust

As a nurse on a shared workstation, I want to sign in and out in a couple of seconds, so that I do not leave a session open just to save time.

Done when, why it matters, edge case

Done when

  • A badge tap or a short PIN signs me in at a shared workstation.
  • A screen locks automatically after a set time and when I walk away.
  • Administrators sign in with a second factor.
  • Each action carries the real person's name, never a shared account.

Why it matters

People leave sessions open because signing in is slow. The right fix is to make signing in quick and not to nag.

Edge case

A nurse who has to leave the screen in a hurry during an emergency.

PLT-2Keep working when the network dropsMust

As a ward nurse or an emergency doctor, I want the critical tasks to keep working without a network, so that patient care does not stop when the connection does.

Done when, why it matters, edge case

Done when

  • Registering an emergency patient, recording vitals and giving medicines keep working offline.
  • Offline entries are clearly marked as not yet synced.
  • Entries sync automatically when the connection returns, with a way to resolve conflicts.
  • Printed downtime forms exist for the rest, and are entered afterwards with the time they were actually written.

Why it matters

Every hospital has network failures. The question is whether the ward is working or waiting when one happens.

Edge case

Two people edit the same record while offline.

PLT-3Bring the old records inMust

As the project team, we want to move the hospital's old records into the new system with counts that tie out, so that staff trust it from the first day.

Done when, why it matters, edge case

Done when

  • Each old register is mapped to its place in the new system.
  • Trial migrations are run and reconciled by count and by sample.
  • Each department signs off its own data.
  • Old records remain available read-only for an agreed period.
  • Duplicates found during migration are handled through the merge process.

Why it matters

If the first record a doctor looks up is wrong or missing, the system is blamed from then on, whatever else it gets right.

Edge case

Years of records that exist only on paper.

PLT-4Train people inside the productShould

As a new user, I want practice with fake patients and short guidance inside the screens, so that I learn on my own time without risking a real record.

Done when, why it matters, edge case

Done when

  • Each role has a practice area with fake patients.
  • Short guidance appears on first use of a screen and can be switched off.
  • A one-page quick reference exists for each role.
  • People from the project team are on the floor during the first week of each department's go-live.

Why it matters

Nobody reads a manual on a ward. Learning has to happen in the screens and with a colleague nearby.

Edge case

A night-shift team that missed the daytime training.

PLT-5Talk to the other systemsShould

As an IT lead, I want connections to analysers, the image archive, insurers and the payment gateway to be monitored, so that a broken connection is noticed before the ward notices.

Done when, why it matters, edge case

Done when

  • Each connection has a visible status.
  • A failure raises an alert to IT, and shows the affected departments a plain notice.
  • Messages that failed are queued and retried, and I can see them.
  • Standards such as HL7 and FHIR are used where the other system supports them.

Why it matters

An interface fails quietly. Without monitoring, the first sign is a result that never arrived.

Edge case

An analyser that sends a result twice.

PLT-6Privacy by defaultMust

As the hospital, we want the system to show people only what they need and to keep a record of consent, so that we meet our duty to the people whose information we hold.

Done when, why it matters, edge case

Done when

  • Each role sees the minimum needed for its job.
  • Consent to hold and to share data is recorded with the time and purpose.
  • Retention periods are set and applied.
  • There is a process for a data breach and for a patient's request to see or correct their data.
  • The standards that apply to this hospital, such as the DPDP Act, ABDM and NABH documentation, are confirmed with the hospital in discovery.

Why it matters

Privacy built in at the start costs a fraction of privacy added after a complaint.

Edge case

A request from a patient to delete data the hospital is legally required to keep.

Release plan

Departments go live one at a time. This is the order I would propose, to be agreed with each hospital's own priorities.

  1. Phase 1: the front of the house and the money

    Registration, appointments, outpatient consultation, billing and insurance, management basics

    These touch every patient and show value soonest. Booking and billing also fix the most visible complaints.

  2. Phase 2: tests and medicines

    Laboratory, radiology, pharmacy, stores and purchase

    Orders from Phase 1 start flowing to departments. This is where retyping disappears.

  3. Phase 3: beds, wards and theatres

    Inpatient, nursing, emergency, operation theatre, blood bank

    The most complex flows, and the ones with the highest clinical risk, built on a record that is already trusted.

  4. Phase 4: apps and deeper integration

    Patient app, doctor app, analyser and insurer connections

    Apps are only as good as the data behind them. Online booking can start in Phase 1 as a simple web page.

Priority is judged inside each release

The patient app has its own Musts, and they are not the same as the emergency department's. Keeping Must to about half of the stories is deliberate: if everything is a Must, nothing was prioritised.

Definition of done

Applies to every story, on top of its own criteria.

  • Reviewed with the people who actually do the job, on the screens they will use.
  • Tested on the hospital's own devices and network, including a slow connection.
  • Roles, permissions and audit entries are in place.
  • Empty, loading and error states are designed, not left to the default.
  • Usable by keyboard and at small sizes, with text and colour that stay readable under hospital lighting, and available in the languages the staff and patients use.
  • Training material for the role is updated, and the story's edge case has been walked through at least once.

Measuring success

A design is finished when the hospital can see it working. These are the measures I would agree with the hospital before the first release.

AreaWhat I would measureWhy it matters
RegistrationTime from arrival to token. Share of new records that turn out to be duplicates.Shows whether the desk got faster without creating a safety problem.
OutpatientDocumentation time per consultation. Time to find the latest result.The two things a doctor feels most in a clinic day.
LaboratoryTime from a verified critical value to acknowledgement. Sample rejection rate.Measures the one failure the system exists to prevent.
PharmacyPrescriptions that needed a call back. Stock written off as expired.Tests whether a clear prescription removed the phone call.
Billing and insuranceCharges posted after discharge. Claim rejection rate and age of open claims.Shows leakage and where claims get stuck.
WardsOverdue medicines at handover. Bed turnaround time.Tracks safety and flow on the ward.
Privacy and accessRecord opens outside a person's usual patients, and how many were reviewed.Shows whether the audit trail is used, not just kept.
AdoptionShare of tasks done in the system rather than on paper, by department.If people keep a paper copy, the design has not earned their trust yet.

Baselines are measured with the hospital before any target is set. A number agreed without a baseline is a guess.

Designing a hospital system?

The first step is not software. It is a few weeks with the people in these roles, watching how work really moves, and rewriting these stories until each one is true for that hospital. Then clickable prototypes of their own screens, reviewed and signed off before any build.