I built a handover board for the friend who was doing all the remembering

Description and use

A handover board was built to log medications and tasks with ownership, automatically detect errors, and generate a brief for the next caregiver.

Problem

Four caregivers each believed they knew the medication schedule, but no one could prove what had already been given, leading to confusion and potential errors.

Outcome

The board reduced medication record errors, surfaced duplicate therapies and timing conflicts, and provided an auditable, deterministic handover process.

Workflow

• Create a board for the patient
• Log doses, blood pressures, notes, and tasks, each tagged with an owner
• Drag a handover moment along the shift rail to transfer ownership
• Run the deterministic engine to identify potential errors
• Seal the handover and download the brief for the next caregiver

Evidence

Four people were helping, each of them believed they knew the schedule, and nobody could prove what had already been given.

Source

You open a board for one person. You log doses, blood pressures, the note the physio left, the blood test someone needs to book. Each entry carries who owns it.

Source

Then, before the care changes hands, you drag a handover moment along a shift rail. Every entry physically moves from the outgoing person to the next one, and a deterministic engine re‑runs for that exact instant.

Source

The readiness score is a weighted mean of six factors, each penalty traceable to a specific row on the board or a specific section of a public label.

Source

Live data comes from two keyless public APIs. NIH RxNorm resolves the concept id. openFDA supplies the label sections.

Source

Every create, update, decision and sealed handover appends one row: seal_n = SHA-384( UTF-8(prevSeal) || canonicalJson(event_n) )

Source