What to do after a dispensing near miss in community pharmacy

When a pharmacy catches a dispensing mistake before supply, it needs to protect the current patient, record a useful account, distinguish the event from an error that reached a patient, identify system factors and verify that changes reduce recurrence. This guide uses an England NHS community pharmacy example, with GPhC professional standards relevant to registered pharmacies across Great Britain. NHS contract and incident recording requirements vary by nation and service.

Confirm that the error was caught before supply

A dispenser selects the wrong strength, and the final accuracy check catches it. A label prints the wrong patient name, but the bag is stopped before handover. Two similar packs sit next to each other, and a team member notices the selection error before any medicine leaves the pharmacy. These are near misses in the ordinary dispensing sense: an error was detected before it reached the patient. The immediate action is to make the specific supply safe. The learning task begins only after the patient facing risk has been contained.

If the medicine or label did reach the patient or their representative, do not classify the event as a near miss merely because the patient has not taken the medicine. The responsible pharmacist and local policy should determine the incident category and clinical response. NHS England’s community pharmacy incident reporting guidance distinguishes incidents from errors identified during the checking process. The former belong in the patient safety incident log; the latter should also be recorded for internal review and learning. Classification affects what must be followed up, but the label is less important than acting on the actual risk. NHS England: community pharmacy incident reporting system guidance.

For a caught error, recheck the prescription, patient identity, product, strength, form, quantity, directions and any clinical or supply concern using the pharmacy’s approved procedure. The person making the final accuracy check should not simply correct the pack and send it out without considering whether the same error appears in another item, another basket or another patient’s order. If the cause is a shelf mix up or software selection problem, other work in progress may be affected. The responsible pharmacist should decide the scope of immediate rechecking.

This page owns learning from a dispensing error that was stopped before supply. Broad registration and governance stay with the general GPhC pharmacy guide. A mismatch in a regulated stock register belongs with the controlled drug discrepancy guide, and manufacturer or MHRA notice action belongs with the medicines recall guide. These are related pharmacy safety tasks but have different starting events and evidence.

Record facts that explain how the near miss happened

Make the record soon enough for staff to remember the sequence. Capture the date, stage where the error arose, stage where it was detected, what was wrong, what was expected, the potential consequence, what was done to make the supply safe and who needs to review it. The record should distinguish an item selected incorrectly from a label generated incorrectly. A generic wrong drug count loses information about whether the risk came from shelf placement, e-prescription entry, dispensing software, pack appearance or a handover between people.

Record relevant conditions without turning the form into a blame exercise. How many prescriptions were being processed? Was the same person interrupted? Were two look alike packs adjacent? Did a change in packaging confuse the team? Was a new colleague working without the expected support? Was an automated dispensing aid or barcode check bypassed? These questions help the team find controllable factors. Do not conclude that staff were careless from a single entry. Ask what made that particular error more likely and what allowed the final check to catch it.

The GPhC standards for registered pharmacies require risks from pharmacy services to be identified and managed and safety and quality to be reviewed. A near miss log can provide evidence for those outcomes if it is actually analysed and acted on. A thick folder of entries without review does not show that the service became safer. Conversely, a month with no entries may indicate under reporting rather than perfect dispensing, especially if staff describe frequent informal corrections. GPhC: standards for registered pharmacies.

Keep patient information proportionate. Some near misses can be described without a patient identifier; others need a controlled link to the prescription to assess whether similar orders are affected. Follow the pharmacy’s information governance policy. Do not make a general compliance platform a duplicate patient record. Restrict identifiable prescription details to the dispensing or approved incident system. A governance log may hold the error type, context, action and coded reference while the clinical or prescription record retains patient specific details.

Decide whether the event needs another incident route

An error caught before supply is generally reviewed as a near miss, but additional facts can change the response. A patient may already have received another bag from the same batch of work. A device or software fault may have affected multiple labels. A product may have been incorrectly supplied to someone else. The responsible pharmacist should check the boundary rather than assuming that because this one item was caught, no other patient was affected. If a patient has been exposed, assess clinical safety and follow the appropriate patient safety incident process.

NHS England’s incident reporting system guidance says English pharmacy contractors must maintain a patient safety incident log for incidents and should keep a record of errors identified during checking for internal review. It also gives required fields for the incident log where information is known. Do not copy those patient incident fields mechanically into every near miss entry. Record enough for learning while keeping the distinction between an intercepted dispensing mistake and an incident that affected a person.

For NHS commissioned prescribing based services, a newer NHS England guidance page addresses recording prescribing related patient safety incidents and the Learn from Patient Safety Events service, known as LFPSE. That guidance is service specific. This article is about the wider community pharmacy dispensing process. The superintendent or NHS contract lead should check which national, local integrated care board and service specific reporting arrangements apply. Do not tell every near miss reporter that one LFPSE form is mandatory simply because another service uses it. NHS England: incident recording guidance for prescribing based community pharmacy services.

If a suspected defective medicine, falsified product or device issue contributed to the error, consider the separate MHRA route. If the near miss involves a controlled drug register mismatch, use the relevant controlled drug governance process. If a staff member identifies a repeated hazardous condition, the pharmacy may need immediate changes before the monthly review. Record those links, but avoid filing five disconnected records that no one reconciles.

Review trends without losing the individual story

Set a cadence for reviewing near misses and make it fit the pharmacy’s size and risk. One striking event may need review today, while a pattern across several weeks may emerge only from aggregated data. The review should look at error type, product or strength, time, stage of detection, workload, staffing, interruptions, packaging and location. A count alone does not explain causation. Ten label errors from one template problem require a different action from ten unrelated slips caught by normal controls.

The GPhC inspection knowledge hub gives an example of a pharmacy using regular review of near miss records to change its dispensing process. It is an example of effective practice, not a prescribed universal review frequency. The team should decide what review period is long enough to show a pattern and short enough to act before the next avoidable harm. A monthly meeting cannot be the only control if a high risk near miss reveals a hazard now. GPhC: using near miss records and regular reviews.

Do not rank staff by the number of near misses they record. A person who reports more may be more observant or work on higher volume tasks. A culture that punishes reporting can drive the count down while risk stays the same. The review should consider denominators such as dispensing volume, service mix and changes in staffing, while recognising that these measures are imperfect. Compare similar processes over time, not simply one person against another. Discuss findings with the team and invite corrections to the account before deciding on an action.

Look for what worked. The final check caught the error. A barcode scan alerted the team. A second person challenged an unusual dose. Preserve effective barriers while fixing the upstream cause. If the team removes the final check to speed work because it rarely finds errors, the near miss log may show exactly why that check matters. The review should also ask whether any near misses are not being captured because the form is hard to access or staff do not get feedback. A reporting process has to be usable during real pharmacy work.

Choose corrective actions that change the system

An action should match the contributing factor. If look alike packs are adjacent, redesign shelf layout and test whether the separation remains after stock replenishment. If an electronic selection list puts two strengths next to each other, work with the system supplier and add a local check while the issue is investigated. If an interruption at the checking bench is the trigger, change the workflow or protected space. If a new service adds complex products, review training, staffing and supervision. A reminder to be careful may support awareness but does not remove the condition that produced the error.

Assign an owner and due date. Keep immediate containment separate from permanent repair. Moving two packs apart today may be a temporary control; a shelf redesign and stock location update may be the sustained fix. Review any unintended consequences. A new warning sticker can become visual noise. A change in pack storage can slow access to a medicine that is urgently needed. The responsible pharmacist and superintendent team should decide which controls suit the service and check that they work in practice.

Use the NHS Specialist Pharmacy Service guidance on medication incidents for a system based learning approach. It recommends a proportionate response focused on learning rather than blame. A near miss with no patient exposure can still deserve a careful review when the potential harm was high or the same failure is recurring. The scale of analysis should fit the risk. Not every intercepted wrong quantity requires a formal investigation, and not every repeated wrong strength selection should be dismissed as routine. NHS Specialist Pharmacy Service: responding to medication incidents.

Document the decision not to change a process when the team concludes existing controls are adequate. That may be reasonable for an isolated event caught by an effective check, but it should be an explicit conclusion with evidence. A record that simply says staff counselled gives little assurance that the pharmacy considered system factors. If an action involves a supplier, head office or IT provider, track their response and the local interim control. An email sent is not a resolved risk.

Verify improvement and keep staff informed

After a change, sample real work to see whether the risk reduced. Check the shelf arrangement after a delivery, the new software selection screen during a busy session, or the revised handover with a locum. Compare near miss patterns over an appropriate period. A lower count is not enough by itself; ask whether staff are still reporting and whether the same error type has moved to another stage. The GPhC standards support regular monitoring and review of safety and quality, not a one time policy rewrite.

Close the loop with the people who reported the event. Tell them what was found, what changed and what remains under review. Staff need to see that their reports lead to useful action. If a recurring hazard appears across multiple branches, the superintendent should consider a wider check rather than leaving each store to solve it alone. If one branch has a successful fix, share it with other sites after testing the fit. A local process may differ because layout, volume and service mix differ.

Keep the evidence organised for inspection or internal governance. A useful audit trail includes the original near miss record, trend review, meeting decision, action assignment, change evidence and follow up test. A chart alone cannot show that the team considered patient impact and acted. Equally, a detailed narrative in one record cannot prove a recurring risk was addressed across the service. The pharmacy should be able to explain both the immediate response and the learning cycle.

A worked example of similar packs on a busy bench

At 4:15 on a Friday, the final checker finds a lower strength pack in a basket for a higher strength prescription. The item has not reached the patient. The pharmacist stops the supply, checks the prescription and the other items in the basket, and confirms the correct product before release. The team records the near miss as a wrong strength selection caught at final check. The record notes that the two strengths have similar packaging and sit next to each other in a temporary stock area. The checking bench was also receiving repeated phone interruptions.

The pharmacist checks other work assembled from that temporary area and finds no further error. The packs are separated and clearly labelled as an immediate measure. At the weekly safety review, the team finds two earlier near misses involving the same strengths. The superintendent assigns a permanent shelf change and asks the IT lead whether the selection screen can make the strengths easier to distinguish. The responsible pharmacist briefs the team and tests the layout after the next delivery. A later review finds no further same product errors, but reporting volume remains stable, which supports the interpretation that the process improved rather than that staff stopped recording.

The example does not provide a universal rule for every look alike product. It shows how the record moves from one caught error to a wider pattern, then to a physical and digital control that can be checked. If the product had been handed to the patient, the first step would have been a clinical safety response and incident pathway, not merely a near miss trend review.

Sources

• NHS England: community pharmacy incident reporting system guidance
• GPhC: standards for registered pharmacies
• GPhC inspection knowledge hub: using near miss records
• NHS England: incident guidance for prescribing based community pharmacy services
• NHS Specialist Pharmacy Service: responding to medication incidents

Related: incident reporting software, and other compliance guides.