What must a dispensing label legally contain?
A label on a dispensed medicine must identify the patient, the supplier, the date, the medicine and how to take it safely. The requirements for medicines dispensed against a prescription sit in Schedule 26 to the Human Medicines Regulations 2012, and in practice the standard set is: the patient's name, the name and address of the supplying pharmacy, the date of dispensing, the name of the medicine, with form and strength where the name alone does not identify them, the directions for use and any precautions, plus the warning to keep the medicine out of the reach and sight of children. Where the prescriber's directions are too long for a single label, the information must still reach the patient completely, which is where continuation labels come in.
"A label is a legal document applied at speed, dozens of times a day."
The reason this list opens a product wiki article is that it is the specification the software exists to meet. The design question for any dispensing system is how much of that specification is assembled automatically from data already in the record versus retyped by a tired human. In Dataforge PMR the answer is: all of it.
Where the label content comes from
Every field on a Dataforge PMR label is pulled directly from the private prescription that has been generated or entered in the system, so the label is a rendering of the record rather than a separate document someone types. There is no transcription step between the prescription and the label, which removes the classic label error mode: a correct prescription rendered incorrectly because the label was typed rather than generated.
| Label field | Source in Dataforge PMR |
|---|---|
| Patient's name | The verified patient record |
| Pharmacy name and address | The location the order is being dispensed at |
| Medicine, form, strength, quantity | The prescription itself |
| Directions for use | The dosing the prescriber set |
| Date of dispensing | The moment of dispensing |
| Cautionary and advisory warnings | BNF labels populated automatically at medicine selection |
This is the same one-record principle that runs through the whole platform, covered in our order screening article: the prescriber's approved prescription is the single source, and the label, like the audit trail, is produced from it. If something is wrong on a label, the correction happens on the record, and the label is reprinted from the corrected record, so the document trail never forks.
How BNF cautionary and advisory labels are handled
When the medicine is chosen, the applicable BNF cautionary and advisory labels populate on the label automatically. The British National Formulary's cautionary and advisory labelling framework assigns recommended warning labels to preparations, covering matters such as drowsiness, alcohol, timing with food and completing the course, and applying the right ones consistently is one of the fiddly, safety-critical, easily rushed steps of manual labelling. In Dataforge PMR the selection happens at the point the medicine is selected on the prescription, so the warnings arrive with the drug rather than depending on the dispenser's recall at the bench.
Auto-population sets the baseline; the pharmacist's judgement stays on top. The professional decision about additional advice, or about how warnings are explained at handover or in the delivery note for a distance supply, remains a clinical step, and the platform's job is to make the default complete rather than to make the pharmacist redundant, the same design boundary described in the order screening article.
Printers and label formats: what works
Dataforge PMR prints to all label printers, and supports all the standardised label sizes available in retail, which makes hardware setup deliberately unexciting. If your pharmacy already runs label printers for an existing PMR or dispensing operation, they will work; if you are buying for a new operation, choose any mainstream label printer and stock a standard retail label size, and the labels Dataforge PMR generates will fit it. There is no proprietary stationery, no locked-in hardware list and no special consumable to source, which matters operationally because label stock is something you buy under time pressure when it runs out.
- Connect the label printer as a normal printer on the machine or network you dispense from.
- Load your chosen label stock, any standardised retail size.
- Run a test print from a test order and check the rendering fits the stationery.
- Dispense normally, repeating the test print whenever you change label stock size.
Do the test print as part of go-live rather than on your first live order.
Split labels: multiple packs and long directions
Split labels in Dataforge PMR cover both situations that break a single label, and both print from the same screen as the main label. Where one supply spans multiple packs, each pack gets its own label, so every container leaving the pharmacy is individually labelled rather than one labelled box travelling with naked companions, which matters for any supply the patient will separate, store in different places or carry in part. And where directions run too long for one label, the content continues across continuation labels, so complex dosing reaches the patient in full instead of being abbreviated to fit, which is precisely the situation where compressed directions become misread directions.
The judgement about when to split remains the dispenser's, but the mechanics are one action in the workflow rather than a workaround, and the split is part of the same logged print event as the primary label.
Reprints, errors and the audit trail
Labels can be reprinted, and reprints are logged, which is the difference between a reprint facility and a governance gap. The legitimate reasons to reprint are routine: a printer jam, damaged stock, a smudged print, a label applied to the wrong pack and destroyed. The governance risk of reprinting is equally routine: labels that exist outside the record, printed twice with no trace of why. Dataforge PMR resolves this the same way it resolves everything else, by logging the action: every print and reprint sits on the order's audit trail with its timestamp, so the pharmacy can always account for how many labels exist for a supply and when each was produced.
Where a label is printed in error, because the prescription itself needed correcting, the discipline is: correct the record, reprint from the corrected record and destroy the erroneous label, with the trail showing both events. That is thirty seconds of workflow, and it is exactly the kind of small, boring evidence that makes an inspection sampling of your dispensing records uneventful, which is the goal.
Label printing inside the dispensing workflow
Label printing is not a separate module to visit; it happens inside the dispensing screen, between prescription generation and the dispensing queue. The flow runs: the prescriber approves, the prescription is generated, the medicine selection brings the BNF cautionary labels with it, the label and any split labels print without leaving the screen, and the order moves through the queue's verification and scanning states to completion, with despatch handled through the Royal Mail Click and Drop integration for distance supplies. Every step is logged as it happens, so the label events sit in sequence with the clinical and dispensing events on one patient journey, the end-to-end chain our private prescription workflow guide describes.
For the team, the practical effect is that labelling stops being a station and becomes a step: no re-keying into a labelling program, no second system to reconcile, and no way for the label to drift from the prescription it represents.
Key takeaways
- A dispensing label must carry the patient's name, the pharmacy's name and address, the date, the medicine with form and strength where needed, directions, precautions and the keep-out-of-reach-of-children warning, per the Human Medicines Regulations 2012.
- Dataforge PMR generates every label field directly from the private prescription record, removing the transcription step where label errors traditionally happen.
- BNF cautionary and advisory labels populate automatically when the medicine is chosen, with the pharmacist's judgement layered on top rather than replaced.
- All label printers and all standardised retail label sizes are supported, so there is no proprietary hardware or stationery to source.
- Split labels handle both multiple packs, each individually labelled, and long directions continued across labels, printed from the same screen.
- Labels can be reprinted and every print and reprint is logged, so the pharmacy can always account for every label that exists for a supply.
- Labelling is a step inside the dispensing workflow, not a separate system, so label events sit in sequence on the same audit trail as the clinical and dispensing record.
FAQs
Your busiest script, end to end.
The quickest way to judge a labelling workflow is to watch your own busiest prescription go through it. Book a 30-minute demo and we will run your real label stock, your printer setup and a complex split-label case end to end.
Book a demo