The MHRA Yellow Card scheme is the UK system for reporting suspected adverse drug reactions — and it applies to every UK telehealth operator dispensing licensed medicines. Under-reporting is a consistent MHRA enforcement theme, and the operators that get caught have almost always failed on workflow, not intent. This piece is the operator's guide to the Yellow Card workflow that actually works in production.
What the Yellow Card scheme actually is
The Yellow Card scheme is the MHRA system for collecting reports of suspected adverse drug reactions (ADRs) and problems with medicines. It is the UK's primary pharmacovigilance surveillance mechanism. Reports come from healthcare professionals, pharmacists, patients, and telehealth operators — and the collective data informs MHRA safety communications and regulatory action.
For UK telehealth operators, the scheme is not optional to engage with. Every operator dispensing licensed medicines participates by virtue of the activity. The question is how systematically. Under-reporting is a consistent enforcement theme because it looks like risk-avoidance behaviour — operators declining to surface issues that might attract scrutiny.
When to report — the threshold that trips operators up
The threshold for Yellow Card reporting is suspicion, not proof. Suspected adverse reactions to any medicine can be reported. Certain categories should be reported more actively: serious reactions to any medicine, any reaction to a black-triangle (newly authorised) medicine, reactions in children, reactions in elderly patients, and reactions where a causal relationship is at all plausible.
The operator error pattern: waiting for confirmation of causation before reporting. The scheme is designed to capture suspected reactions so MHRA can aggregate patterns across all reports. Individual operator confidence in causation is not required. Report on suspicion and let MHRA's aggregate analysis do its work.
The workflow that actually catches events
Five steps compose a working Yellow Card workflow. Step 1: support team trained to recognise reportable events from patient communication (side effects mentioned, tolerability concerns, complaints about how they feel on medication). Step 2: structured capture into the clinical record with defined fields (medicine, symptoms, timing, patient factors). Step 3: routing to the responsible clinician with defined SLA. Step 4: clinical assessment and Yellow Card submission where criteria are met. Step 5: documented audit trail and follow-up.
The single most common failure point is Step 1 — support-team recognition. Reportable events arrive as customer service tickets that don't look clinical on the surface. Training the support team to identify signals is the highest-leverage workflow investment operators can make.
SLA discipline — what timing looks like in practice
Serious suspected adverse drug reactions should be reported to MHRA as soon as possible. Non-serious reactions have a longer window but should not be indefinitely deferred. A workable internal SLA structure: capture within 4 hours of first contact, clinical assessment within 24-48 hours for non-serious events, immediate escalation and submission for serious events (chest pain, breathing difficulty, mental health crisis, anaphylaxis, hospitalisation).
The internal SLA matters because Yellow Card submission is often reactive to internal capture. Operators with clean capture-to-submission SLAs handle Yellow Card obligations cleanly. Operators without clean SLAs discover the gap during MHRA engagement — usually because a specific patient case gets scrutinised and the timing record shows delay.
Documentation and audit trail
Yellow Card workflow generates records that need retention. What the support team captured, what the clinician assessed, what was submitted to MHRA, what internal remediation followed. Retention should align with the broader clinical record retention framework — typically 8+ years for adult records.
The audit trail is what MHRA inspectors review during pharmacovigilance-focused engagement. Operators with clean audit trails demonstrate the workflow ran. Operators with gaps in the trail (support ticket found but no clinician assessment recorded; MHRA submission found but no internal record of the trigger) look like the workflow ran inconsistently — which is worse than not running it at all from an inspection perspective.
How PExpo handles Yellow Card workflow for brand and clinic customers
PExpo's dispensing operation includes structured pharmacovigilance capture and Yellow Card submission workflow as part of the regulated layer. Brand and clinic customers get the workflow infrastructure — patient support capture prompts, clinician assessment SLAs, MHRA submission process, audit trail retention — as part of the platform rather than building it from scratch.
The brand or clinic retains responsibility for its own operational discipline in engaging the workflow, but the framework itself is provided. See our [brand model page](../brands.html) for the operational scope or our [adverse event management guide](adverse-event-management-pharmacovigilance-uk.html) for broader pharmacovigilance context.
The threshold for Yellow Card reporting is suspicion, not proof. Operators waiting for confirmation of causation before reporting under-report systematically — and under-reporting is a consistent MHRA enforcement theme. Report on suspicion and let MHRA's aggregate analysis do its work.
The single most common Yellow Card workflow failure point is support-team recognition. Reportable events arrive as customer service tickets that don't look clinical on the surface. Train the recognition; capture at first contact.
Yellow Card reporting is not optional for UK telehealth operators dispensing licensed medicines — it is a foundational obligation, and under-reporting is a consistent enforcement theme. The fix is structural workflow rather than intent. Operators that build the five-step workflow (recognition, capture, routing, assessment, submission with audit trail) handle Yellow Card obligations cleanly. See our adverse event management guide for broader context, our brand model page for the PExpo operational scope, or our MHRA enforcement trends piece.
Frequently asked questions
When must UK telehealth operators submit a Yellow Card report?
Serious suspected adverse drug reactions should be reported as soon as possible. Non-serious reactions to black-triangle medicines and reactions in children, elderly patients, and specific vulnerable groups should also be reported. The threshold is suspicion, not proof of causation.
Who submits the Yellow Card report — the patient or the operator?
Either can. UK telehealth operators are expected to submit reports for events they identify through clinical assessment. Patients can submit reports directly. Operator submission and patient submission are complementary — both feed MHRA's aggregate surveillance.
Does PExpo handle Yellow Card submission for brand customers?
PExpo's dispensing operation includes the pharmacovigilance workflow and Yellow Card submission process. The brand retains responsibility for operational engagement with the workflow, but the framework and submission mechanism are provided. See our brand model page.
