Skip to main content

The medicines business | A question to investigate

Which supply exception deserves attention first?

A wholesaler can have many exceptions and only a limited number of people able to investigate them. A missing delivery confirmation, an uncertain replenishment date and a questionable customer record should not become the same red dot. The commercial problem is deciding what deserves attention now, what needs a different owner and what information would actually change the next action. That is a specific medicines-intelligence question worth testing.

Film credits

In the conversation.

NEUVIOR and our founder’s perspectives have appeared across science, business and technology publications.

University of Warwick IATL | AI Ethics NowpharmaphorumTechRadar ProET PharmaFinancial TimesPharmaceutical TechnologyPharmaTimesManufacturing ChemistDigital HealthDaily BusinessTheBusinessDesk.comStartups MagazineInsider MediaYorkshire PostYork PressBusinessCloud

Reporting, commentary, letters and podcast appearances | Read each feature for its format and source.

The cost of one undifferentiated queue

When every exception looks urgent, experienced people become the sorting system. Their reasoning may be excellent but difficult to share, audit or reproduce when workloads change. An apparently small account issue can block many orders; a large order can be operationally straightforward. Priority should therefore reflect the consequence and available response, with hard quality constraints recognised separately from commercial service preferences. The objective is a more intelligible queue, rather than simply a faster-moving one.

Distribution has an accountable framework

MHRA’s GDP guidance concerns suitable sourcing, storage, transport and handling (MHRA, 2014). Its licensing guidance distinguishes wholesale distribution authorisation from manufacturing permission (MHRA, n.d.). Neither source endorses a new prioritisation tool. They establish why an evaluation must respect existing responsibilities, approved procedures and licensed activities. A proposed analytical view should help the responsible team investigate an exception; it should never imply that a ranking can authorise an otherwise impermissible supply.

Different owners need different evidence

Customer services needs a dependable explanation it can communicate. Procurement needs to know whether replenishment information is credible. The responsible person and quality team need exceptions with potential quality consequences escalated appropriately. Finance may need to understand credit or contractual restrictions. Combining these perspectives begins with an ownership map: who can resolve each category, which facts they require, and which escalation cannot wait for a commercial convenience score.

A queue that explains itself

A useful first deliverable would be a reviewed exception taxonomy with routing rules, evidence requirements and unresolved categories. It could show where a repeated customer-service issue actually originates in product identification or replenishment data. The organisation would then have a specific improvement question to test, rather than a broad promise to optimise its entire operation.

A public decision brief | An illustrative example

Open the question.
Inspect the reasoning.

Choose a business question, then look beneath its claim. See what a public source supports, what depends on the local setting and what a useful next step could be.

A medicines or implementation team considering an AI-supported evidence review.

Would a quicker review make the decision better?

The interesting question is the complete piece of work: finding relevant material, checking it, correcting the draft and reaching an accountable decision.

A proposition to investigate

Less preparation. The same ability to challenge.

An evidence-review approach could be useful if it reduces avoidable preparation while preserving source access, relevant qualifications and professional checking. That is the proposed value to test. No time reduction, accuracy improvement or customer result is asserted in this example.

The proposition is constructed for this public brief. It is not a published finding about PHARMORIS.

What the next brief would contain

A decision someone
can commission.

The decision
Whether one defined review task merits an agreed evaluation.
The comparator
The team's existing complete review process, including checking and corrections.
The evidence
Representative cases, source records, reviewer decisions, complete-task effort and exceptions.
Stop or redesign
Stop or redesign if source checking weakens, errors are unacceptable or the complete task offers insufficient value.

Constructed public example | Not PHARMORIS-generated software output or a measured customer result.

Keep this example brief

An evaluation with a real comparator

NEUVIOR would propose a retrospective review of a bounded sample of resolved wholesale exceptions, followed only if justified by a supervised workflow study. Inputs could include pseudonymised order events, exception categories, timestamps, documented resolutions and existing escalation rules. The comparison would use the current queue and its actual handling practice, not an artificially simplified spreadsheet. Cases would be reviewed without allowing a proposed PHARMORIS output to change live dispatch decisions.

Measure the burden as well as the benefit

Candidate measures include correct escalation to the appropriate owner, time spent locating missing evidence, repeat handling of the same issue and agreement between reviewers about urgency. The evaluation should count false urgency and missed urgency separately. It should also record the new work needed to maintain categories or correct data. A view that appears efficient for central management may merely shift administration to warehouse or customer-service colleagues.

Where a sensible pilot stops

The pilot would stop if product identity cannot be reconciled reliably, if time fields have inconsistent meanings, or if historical outcomes conceal unrecorded manual interventions. It would also stop if users begin treating an experimental priority as release authority. No forecast of improved service or reduced costs should be published from a small retrospective exercise. A credible result may instead identify a narrower exception type, a data repair task or no useful case for further development.

A first discussion with operational value

A wholesale director does not need to arrive with a technology specification. Bring a recurring exception that is difficult to route, a view of its weekly workload and the people currently involved. We can discuss what a better decision would look like and whether the evidence exists to compare it fairly. The potential commercial value lies in resolving a recognisable operational friction with an accountable owner, a measurable baseline and an explicit boundary around supply authority.

Sources and scope

Another useful angle.

NEWSPerspectives & features