Equipment ordering for hospital discharge

One shared record for ordering home medical equipment, from the therapist’s request to the Red Cross, the vendor and home health.

Project facts

Who it’s for
Hospital therapists, site coordinators, Canadian Red Cross staff, equipment vendors, home health teams and program managers.
Stage

Stage 2 of 5: Working prototype

Lloyd’s role
Sole designer and developer
Year
2026
Built with
React, TypeScript, Material UI, Node.js, Express, PostgreSQL, Playwright

In short

The problem
Home-equipment orders for discharge pass between therapists, coordinators, the Red Cross and vendors with no shared record, so nobody can see where an order is.
What changes
One record per order, routed automatically, with every change acknowledged and every view of client details logged.
Proof so far
A complete working prototype across seven roles, tested end to end on fictional clients. Not yet piloted.
MEPP 2.0 in 90 secondsThe problem, automatic routing to the Red Cross and vendors, flagged amendments and vendor quotes, cut from the full walkthrough.1:29 · Captions available

Evidence so far

  • 7Roles built end to endPrescriber to administrator, each with its own workspace
  • LoggedClient privacyEvery view of a client’s details is recorded; record numbers are blocked from vendors
  • In the databaseData separationEach health authority’s data is isolated by row-level security
  • AutomatedQuality checksUnit, accessibility and end-to-end tests run on every change

The problem

The Medical Equipment Provision Program lends short-term equipment so people can leave hospital, or stay at home, safely. Orders must go to the Canadian Red Cross first, then to other vendors for anything the Red Cross can’t supply.

The program’s own documents describe the friction: most orders are marked same-day or next-day, delays lead to avoidable rental extensions, and the electronic form had no database of previously submitted orders. Once a form was sent, nobody could see where it was.

Who it’s for

  • Prescriber

    Needs to
    Order equipment so a client can go home safely, then see who is filling each item and when it arrives.
    Today
    The electronic form keeps no record of past orders; unfilled items come back as a marked-up PDF to fax to a vendor.
  • Site coordinator

    Needs to
    Watch the site’s orders, work with the Red Cross and vendors, and accept quotes within budget.
    Today
    Requests are tracked in a hand-kept spreadsheet.
  • Red Cross staff

    Needs to
    Fill stocked items from a depot and arrange pickup or delivery.
    Today
    Anything they can’t fill goes back on paper to be re-faxed to a vendor.
  • Equipment vendor

    Needs to
    Quote a date and monthly rate, then deliver and collect.
    Today
    Most orders arrive marked same-day or next-day.
  • Program management

    Needs to
    Oversee spending, delays and overdue rentals, and decide later extensions.
    Today
    There is no program-wide view without phoning every coordinator.

How it works

  1. A therapist builds the order

    A four-step form (client, equipment, order details, review) that enforces program rules, such as a bed needing a mattress and lifts needing home-access answers.

  2. The system routes it

    Red Cross first. Vendor-only items go straight to the vendor, and anything the Red Cross can’t supply moves to a vendor automatically.

  3. The Red Cross answers each line

    In stock, partial or substitute, or not available, with pickup or delivery for every item.

  4. A vendor quotes

    A delivery date and a monthly rate. The coordinator can decline over-budget quotes with a reason and ask for a new one.

  5. Home health visits

    Delivery, installation and follow-up visits are recorded on the same order.

  6. Extensions, returns and escalations

    The first extension is automatic. Later ones go to management, and overdue rentals escalate.

Screens

Captured from the app with demo data. Select a screen to see it larger.

  • Prescriber home: what needs attention today
  • New order, step 2: equipment from the program formulary
  • New order, step 4: review before sending
  • Red Cross: answering each line of a requisition
  • Vendor: quoting a delivery date and monthly rate
  • Administrator: the patient-data access log

Main features

  • A workspace per role

    Seven roles each see only their own part of the job, from prescriber to administrator.

  • Changes that can’t slip through

    Once an order is routed, any edit becomes a flagged amendment that the supplier must acknowledge.

  • Messages on the order

    Conversations stay attached to the request and are encrypted. The client’s medical record number is blocked from vendor threads.

  • Grouped notifications

    Alerts are grouped per order, so one large order doesn’t flood an inbox.

  • Oversight for managers

    Read-only views of every queue across sites, plus extension decisions and site budgets.

  • Privacy by design

    Each health authority’s data is separated in the database, and every view of a client’s details is logged.

Product decisions

  1. Allow changes after routing, as visible amendments

    Instead of the old rule that a submitted order can’t change, so you cancel and re-order.

    It cuts rework, and nothing is overwritten without the supplier seeing and acknowledging it.

  2. One alert per person, per order and type

    Instead of one alert for every line and every event.

    In a test run, one 15-item order sent the coordinator 15 unread alerts. Grouping brought it to 3.

  3. Keep each health authority’s data apart in the database

    Instead of relying on the application’s own filters.

    Even a bug or a missing filter can’t reach another authority’s clients. The database is the last line of defence.

Left out on purpose

  • Real patient data and a live launch. The blockers aren’t code: privacy and security assessments, sharing agreements and Canadian hosting come first.
  • A link to the provincial patient registry. Clients are entered by hand for now; the integration is planned, not built.
  • Administrators opening client records. A deliberate limit that keeps access management separate from patient work.

What changed along the way

  • “Accept all” for delivery offers, and grouped alerts. Two full 15-item test runs through every role found six problems. Accepting one order’s offers went from 26 clicks to 2.
  • Stair and access answers shown to delivery crews. The test run found crews couldn’t see the stair details needed for beds and lifts.
  • A shorter, clearer executive video. The first cut repeated its disclaimer and left out management and administration.

How it saves time

  • Every order has a single, searchable record instead of a sent form nobody can track.
  • Routing to the Red Cross and vendors happens automatically, so coordinators re-key less.
  • Late changes are acknowledged rather than missed.
  • Managers can see delays and extension costs as they build up, not after the fact.

These are intended outcomes. There is no pilot or time study yet, so no savings are claimed.

How success would be measured

MeasureTarget or resultStatus
Unread alerts per order for the coordinatorNot set. 15 down to 3 for one orderTest data only
Clicks to accept a whole order’s delivery offersNot set. 26 down to 2Test data only
Share of orders filled by the Red CrossNot set. Shown on the performance screenNot yet measured
Coordination time per orderNot set. Needs a time study firstNot yet measured

More video

Full walkthroughThe seven roles, and one fifteen-item order followed from prescription to delivery, extensions, oversight and administration. Fictional clients; all amounts are illustrative.18:27 · Captions available

How it’s built

Lloyd designed and built MEPP 2.0 end to end as its only developer: the workflow model, interface, API, database security and test suite. He drew on his years working in hospitals as a rehabilitation assistant, where equipment for discharge is part of the daily work.

Lloyd Dela Cruz, Founder, DYOL Digital Labs. About Lloyd

Interface
React, TypeScript, Material UI, React Query, form validation with zod
Server
Node.js, Express, strict TypeScript, two-step sign-in (TOTP)
Data
PostgreSQL with row-level security and hand-written migrations
Quality
Vitest, Testing Library with automated accessibility checks, Playwright end-to-end tests, CI on GitHub Actions

Where it is now

  1. Concept
  2. Working prototypeThis project
  3. Pilot-ready
  4. Public beta
  5. In use

A working prototype on test data with fictional clients. It is not deployed and has not been through a privacy impact assessment or security review, which a pilot would need first.

What’s next

  1. A pilot with synthetic or consented test clients at one site
  2. A time study to replace assumptions with measurements
  3. Review by the health authority’s privacy and security teams
  4. Conversations with the Red Cross and vendors about what they need to see

A free 20-minute conversation, then an honest assessment. You’ll know what it costs and how long it takes, in writing, at a fixed price.

Or email lloyd.delacruz@outlook.com. We reply within 24 hours.