Medicines, devices, temperatures and training for two surgeries, instead of paper logs

Two surgeries in different buildings, each with its own medicines, devices and fridge. Temperatures, the UV lamp and cleaning were written onto paper sheets, medicine and supply expiry dates were checked at the shelf, and calibration and training dates sat in spreadsheets.

Paper records, but it does not warn. A temperature out of range looks the same on the sheet as a correct one, a skipped day goes unnoticed until the inspection, and an expired medicine turns up when someone needs to use it.

Medicines with packs, batches and expiry dates, medical and office supplies with minimums and a shopping list, daily logs for temperatures, the UV lamp and cleaning, devices with an inspection plan, IT and licences, training, attendance and leave. Almost every record belongs to one surgery, and the header switches between one of them and both.

The reminder engine collects deadlines from every module and sorts them into overdue, within 7 days and within 30 days. A reminder can be resolved or snoozed, the bell in the header announces new ones, and everyone can add the deadlines to their own Google or Apple calendar through a private link.

Two roles — doctor and nurse — with permissions enforced on the server, and a history on every change: who, when and what. The system deliberately stores nothing about patients: no names, no national ID numbers, no diagnoses, and no connection to the clinical system.

Monthly sheets for temperature, UV exposure and cleaning print straight from the logged values. A checklist of the practice's equipment and staffing requirements shows which are met and which are not.

Patients see opening hours, the price list and other documents on a public waiting-room page that the nurse updates directly from the system. Planned, not yet deployed: importing the original spreadsheets and a link to the Pohoda accounting software.