There is a reason emc is organised around medicinal products rather than active ingredients, and it is the reason this article exists: the clinically material information frequently lives at product level, and any answer pitched at drug level, however accurate, can be silently unsafe for the actual product in the actual patient's hand. AI systems inherit the problem structurally, because training data and summaries skew toward drug-level generalisation, which makes "technically correct but product-blind" the characteristic AI medicines answer, and the prescriber's defence is a habit: the product identity check, run wherever the decision touches formulation, device, strength or population.
Where product-level differences bite
Six territories, each with the failure mode named. Release profiles: immediate-release and modified-release preparations of the same ingredient differ in dosing logic, interchangeability and consequences of substitution, and a drug-level answer that never states which it means has answered neither. Devices: inhalers delivering the same molecule through different devices are different products in technique, training and licensing, and switching the device is a clinical act, not a dispensing detail. Concentrations: liquids and injectables of the same drug at different strengths are the classic serious-error substrate, and any volume-based reasoning that has not fixed the concentration is arithmetic waiting to go wrong. Licensed populations: products containing the same ingredient can carry different age ranges and indications in their marketing authorisations, so "licensed for children" is a product claim, never an ingredient claim. Biologics and biosimilars: brand-level identity matters for prescribing, recording and pharmacovigilance in ways generic thinking actively obscures. And excipients: sodium content, alcohol, lactose and other constituents differ by product and matter for specific patients, information that lives only in the exact SmPC's pharmaceutical particulars, a place drug-level answers never visit.
The seven-point product identity check
Before any product-touching decision, confirm seven fields, most answerable in seconds from the SmPC the decision should end at anyway: brand, or the deliberate decision that generic prescribing is appropriate here; strength; formulation; route; device, where one exists; marketing-authorisation territory, the UK product, not a lookalike from elsewhere; and current SmPC date, because the document's version is part of its identity. An AI answer that lets you complete all seven has been product-specific; an answer that leaves fields blank has told you its level, and the blank fields are your remaining work, not its rounding error. This is also the honest description of how the iatroX medicines layer is built to help: pages organised around selected UK products with review dates and direct links to their current SmPCs, navigation to the product level, with the exact SmPC remaining authoritative, per the division of labour at /blog/iatrox-vs-emc-non-medical-prescribers.
Prompting and verifying at product level
Two behavioural conversions close the article. Ask product-shaped questions: name the brand, strength and formulation in the prompt where you know them, and where you do not, make "which products does this apply to?" the explicit follow-up, because a question pitched at ingredient level licenses an answer at ingredient level. And verify at the level the decision needs: pathway questions legitimately resolve at drug level, but anything touching administration, switching, devices, children, or excipient-sensitive patients resolves only at the exact SmPC, and the 90-second screen's product stage, /blog/verify-ai-prescribing-answer-90-seconds, exists to catch the mismatch before it ships. The one-sentence version for the ward: the active ingredient is what the medicine is, the product is what the patient gets, and prescribing safety lives in the second.
Frequently asked questions
When is drug-level thinking legitimately sufficient?
For pathway placement, class effects and most initial orientation: the level becomes unsafe exactly when the decision acquires a formulation, device, strength or special population, which is the promotion trigger to product level.
How should generic prescribing policy interact with this?
Comfortably: generic prescribing is a deliberate, guideline-supported default with named exceptions, and the exceptions, modified-release preparations, devices, biologics, narrow-therapeutic-index territory, are precisely this article's territories, usually specified in local policy.
Do patients need the product distinction explained?
Where it affects them, plainly: a changed device needs technique review, a changed appearance needs reassurance and confirmation, and a biologic brand switch needs a conversation, all of which the PIL for the exact product supports.
How do product shortages interact with the identity check?
They weaponise it: substitutions under shortage are exactly where release profiles, devices and concentrations swap silently, and the seven fields re-run on the replacement product is the shortage-safety behaviour local medicines teams keep asking for.
Are product-level errors more common with AI than before it?
The substrate predates AI, transcription and substitution errors fill incident archives; what AI changes is fluency, drug-level answers now arrive polished enough to skip the check, which is why the habit needs to be deliberate.