Paediatric Prescribing Safety Controls in the Record

Every weight-based control depends on the weight being present, current and correct, which makes it the first thing to enforce. A recorded weight with a date and the method of measurement should be a precondition for paediatric prescribing rather than a field that can be left empty, and the system should treat a weight older than a defined interval as absent rather than as usable.

The interval has to differ by age, because a weight from three weeks ago means something very different for a neonate than for a ten-year-old. Set it according to your protocols and enforce it in the system rather than relying on clinicians to notice the date. A stale weight used in a calculation is one of the more insidious errors precisely because everything about the process looks correct.

Distinguish a measured weight from an estimated one and carry that distinction visibly. Estimation is legitimate and necessary in emergencies, and a dose calculated from an estimate should be identifiable as such so that it is revisited once the child is weighed. Recording an estimate in the same field, the same way, as a measured weight erases exactly the information that would prompt someone to check.

Dose range checking against weight is the central control, and its value depends on how it is configured. Checking only against an absolute maximum catches the extreme cases and misses most real errors, which sit within plausible absolute ranges but are wrong for that child. Checking the calculated dose per kilogram against a range appropriate to the drug, the indication and the age band is what catches a decimal error before it reaches a patient.

Check the total daily dose as well as the individual dose, because a per-dose amount that is reasonable becomes unsafe at the wrong frequency, and frequency errors are common. Both checks are needed and neither substitutes for the other.

Configure the strength of the response to match the certainty. A dose outside a hard limit should be a hard stop requiring a defined override with a reason. A dose outside a soft range should warn and require acknowledgement. Making everything a hard stop produces obstruction and drives workarounds; making everything a soft warning produces alert fatigue and the warnings stop being read. The proportion between the two is a clinical governance decision, not a technical default, and it should be reviewed against the override data it generates.

A substantial share of serious paediatric medication errors are not dose calculation errors at all but formulation and concentration errors: the right dose prepared from the wrong strength, a product available in multiple concentrations with the wrong one selected, or an order expressed in millilitres where the concentration was ambiguous.

The system control is to express orders in mass or units rather than volume, and to carry the intended concentration and formulation explicitly through prescribing, dispensing and administration so that nobody has to infer it. Where a preparation requires dilution or manipulation, the record should carry the final concentration and the volume to be given rather than leaving that calculation to be repeated at the bedside by someone working from the original order.

Reduce the number of concentrations available wherever the formulary allows it. Standardising to a single strength for a given paediatric use removes an entire class of error at source, and it is a formulary decision rather than a software one. Where multiple strengths must be stocked, the system should make the selected strength unmissable at every step and the pharmacy should segregate them physically.

Independent verification before administration of defined high-risk paediatric medicines is standard practice and its value depends entirely on whether it is genuinely independent. A second person who is shown the calculation and asked to confirm it will confirm it; a second person who performs the calculation separately and then compares will sometimes disagree, which is the entire point of the exercise.

The system's role is to require and record it: which medicines require verification, that it occurred before administration rather than being back-filled, and who performed it. Recording the verifier by name matters, because a check recorded against an unidentified second person is not auditable and is not, in practice, always performed.

Design the workflow so verification is possible in the circumstances where it is required, which frequently means at night with two staff on a ward. A requirement that cannot be met at three in the morning will be documented as met and not performed, which is worse than not requiring it, because it creates a false record alongside the original risk. If the staffing does not support it, that is a staffing decision to be made explicitly rather than a policy to be quietly breached.

The controls above generate data that most hospitals never look at, and it is among the most useful safety data available. Override patterns tell you which alerts are firing so often that they have stopped being read, and which are genuinely catching errors. A drug whose range check is overridden almost every time is misconfigured, not routinely misprescribed, and fixing the configuration restores the alert's meaning.

Review overrides and near misses together, monthly, with paediatrics, pharmacy and nursing in the room. The purpose is configuration and workflow improvement rather than individual accountability, and it has to be visibly so or the reporting that feeds it will dry up. Errors reaching a patient warrant the hospital's full incident and review process; the value of this review is in the far larger number that did not.

Keep the resulting record — configuration decisions, override analysis, verification compliance and incident findings — in the same operational system as the rest of the hospital's quality data, as a platform such as HealUDoc allows. Paediatric medication safety fails when it is treated as a departmental concern reviewed after an event, and improves when it is a standing item reviewed against data that was already being collected.

Every control described here adds friction, and friction in a paediatric or neonatal unit has its own risks. A system so obstructive that clinicians route around it through verbal orders or paper has reduced safety while appearing to increase it, and that outcome is common enough to be the default result of an over-enthusiastic implementation.

Introduce controls in order of the harm they prevent rather than all at once. Mandatory current weight and per-kilogram range checking on high-risk medicines deliver most of the benefit and are readily accepted. Extending hard stops across the whole formulary usually delivers little additional safety and a great deal of resistance.

Then measure whether the controls are being used as intended rather than assuming. Rising override rates, verbal orders, retrospective documentation and off-system workarounds are all signals that the configuration has exceeded what the clinical reality can carry. Treat those signals as design feedback, which is what they are, rather than as a compliance problem to be addressed by instruction.