PHARMORIS · A NEUVIOR PRODUCT

You already have the medicines evidence. Make it move.

The aim is to give every justified medicines opportunity a clear decision, owner and visible route through delivery. PHARMORIS by NEUVIOR is being built to help authorised medicines, pharmacy, finance and commissioning teams move from fragmented evidence and operational signals to source linked ActionCases, accountable human decisions, coordinated follow through and later value review.

It does not replace professional judgement or local governance.

Map your medicines workflow See how it works

CONTROLLED DEVELOPMENT · NON PRODUCTION · STAFF FACING · HUMAN DECISION REQUIREDREADINESS · EXACT VERSION EVIDENCE IN PREPARATION · NO INDEPENDENT TRL ASSIGNEDPublic page reviewed 27 August 2026

View dated product status

FROM SIGNAL TO OWNED WORK

Stop losing good opportunities between the signal and the next decision.

You can have a credible medicines signal and still watch it stall when the source, owner, decision route, blockers and follow through sit in different places. Medicines teams work across evidence, finance, providers, practices, community pharmacy and governance; PHARMORIS is designed to keep that thread connected through an ActionCase.

The better future is not another dashboard. It is a team that can see why the work exists, who owns the next decision, what is blocking delivery and what evidence will support the later review.

PHARMORIS remains in controlled, non production development. NEUVIOR is preparing the exact version evidence needed for an independent readiness review; no independent TRL has yet been assigned.

Target operating model

From attributable source to reviewable action

Target PHARMORIS lifecycle with provenance, stop states and human authority.

01Source definitionSource scope
02Rights and permissionUse constraint
03Receipt or approved snapshotProvenance receipt
04Validate or quarantineEvidence gate
05CandidateSignalRecord before operational work
06Human triageMandatory authority gate
07ActionCaseGoverned working record
08EvidencePack versionVersioned decision material
09Human gateAccountable decision
10PublicationScoped release or transfer
11AcknowledgementReceiver response
12ValueReviewLater evidence review

Missing, invalid or unauthorised → QuarantineNot established → UNKNOWNReject · retain source historyDefer · not active workRequest evidence · incompleteHold · decision not authorisedPublished ≠ acknowledgedObserved value not established

Accept. Authorised continuation.Authorised outcome

Target operating model derived from the approved PHARMORIS v5 architecture and Work 01 content controls. Human triage is required before an ActionCase. The figure does not establish a live source, implemented transition, NHS deployment, clinical authority or realised value. Sources checked 20 July 2026.

Record and authority distinctions

CandidateSignal is a prompt for authorised triage, not approved work.
Human triage is mandatory before an ActionCase exists.
EvidencePack version is versioned decision material, not the decision.
Publication and Acknowledgement remain separate records.
ValueReview is a later evidence review, not automatic proof of savings or outcomes.

PHARMORIS governed lifecycle sequence
Node	Display label	Record or control class	Human authority
01	Source definition	Source scope	Approves permitted purpose and owner
02	Rights and permission	Use constraint	Confirms that the material may support the intended work
03	Receipt or approved snapshot	Provenance receipt	Confirms attributable capture and date
04	Validate or quarantine	Evidence gate	Reviews failed, missing, stale or unauthorised material where required
05	CandidateSignal	Record before operational work	No authority is created by the signal
06	Human triage	Mandatory authority gate	Accept, reject, defer or request evidence
07	ActionCase	Governed working record	An authorised owner accepts bounded work
08	EvidencePack version	Versioned decision material	Relevant reviewers assess the defined version
09	Human gate	Accountable decision	Authorised people record an outcome within their remit
10	Publication	Scoped release or transfer	An authorised person controls version and scope
11	Acknowledgement	Receiver response	The receiver response remains separate from adoption
12	ValueReview	Later evidence review	An authorised reviewer assesses evidence without assuming savings

PHARMORIS lifecycle branch and terminal states
Branch origin	Outcome	Display text	Meaning
Rights or validation	Quarantine	Missing, invalid or unauthorised → Quarantine	Material cannot support work until resolved and reviewed
Any required evidence field	Unknown	Not established → UNKNOWN	Absence must not become PASS, zero or a positive claim
Human triage	Reject	Reject · retain source history	The signal does not progress; its basis and decision remain attributable
Human triage	Defer	Defer · not active work	The signal has not entered operational work and must not look in progress
Human triage	Request evidence	Request evidence · incomplete	Progress pauses until the missing basis is supplied and reviewed
Human gate	Hold	Hold · decision not authorised	Evidence material exists but no authorised outcome is recorded
Publication	Not acknowledged	Published ≠ acknowledged	A transfer does not prove receipt, adoption or implementation
ValueReview	Unknown	Observed value not established	Forecast, activity and outcome remain separate evidence classes

Software roles may structure the record. They do not create professional authority.

Lane A: Source and provenance: Source definition
Permitted purpose and rights
Receipt or approved snapshot
Validation, freshness and limitations
Quarantine and UNKNOWN
Lane B: Product records: CandidateSignal
ActionCase
EvidencePack version
Publication record
Acknowledgement
ValueReview
Lane C: Human authority: Source owner or governance approval where required
Authorised triage
ActionCase owner
Professional, finance, procurement or governance review
Publication authority
Later value reviewer
Lane D: Evidence state: Attributable
Valid or quarantined
Incomplete or UNKNOWN
Accepted or rejected
Versioned
Decided or held
Published
Acknowledged or not acknowledged
Later value evidence reviewed or not established

PHARMORIS state separation ledger
Record	Exact distinction
CandidateSignal	Prompt for authorised triage; not approved work
ActionCase	Owned operating record; not automatic evidence quality or value
EvidencePack	Versioned material; not the decision
Publication	Scoped release or transfer; not adoption
Acknowledgement	Receiver response; not implementation or outcome
ValueReview	Later evidence review; not automatic proof of savings

Evidence boundary

This is a target operating model. It is not a live PHARMORIS interface, a complete implemented flow, a production or NHS workflow, an autonomous decision system, a prescribing system, support tailored to a patient, a live source claim, a release readiness receipt or proof of realised value.

Sources: PHARMORIS Architecture Map v5, audit baseline 17 July 2026; PHARMORIS active source and evidence register, dated 17 July 2026; PHARMORIS source readiness baseline, dated 17 July 2026; approved Work 01 product truth, claim library and website content brief. Checked 20 July 2026.

Product design

See the evidence path, not just the answer.

You should be able to inspect why a case exists, who owns the next decision, what supports it and what remains unknown.

PHARMORIS is being designed to preserve that context from source receipt through human review and the later decision record.

Source provenance

Keep the source, date, scope and confidence beside the work.

Visible unknowns

Record what is missing instead of filling the gap with certainty.

Human triage

Require an accountable person before a candidate becomes owned work.

Evidence packs

Carry assumptions and limitations into the material prepared for review.

Decision history

Record who decided, why the work moved and what still needs review.

Value boundary

Keep projected opportunity separate from evidence of realised value.

Source architecture

A registry of evidence. Not a claim of connected sources.

Source access, permission, licensing and technical connectivity must be validated separately. PHARMORIS is being designed to keep public, authorised, commercial and local evidence distinct.

Follow the full evidence lifecycle

01Medicine identity and referenceAccess must be validated
02Prescribing and utilisationAccess must be validated
03Reimbursement and pricingAccess must be validated
04Shortages and supplyAccess must be validated
05Safety and regulationAccess must be validated
06Health technology assessmentAccess must be validated
07Research and real world evidenceAccess must be validated
08Local implementation contextAccess must be validated

Source linked

Keep the evidence basis, date, scope and limitations visible.

Human gated

An authorised person decides whether a signal should progress and which gate applies.

Accountably followed through

Keep owner, blockers, hand off, receiver response and later value review distinct.

REPRESENTATIVE WORKFLOW

A best value medicines opportunity, carried through with its evidence.

A medicines team identifies a possible formulary or best value change. The case may involve cost avoided and incurred, workforce and time, supply stability, implementation effort and patient experience. PHARMORIS is designed to keep those effects reviewable without turning an estimate into a saving or a software state into an approval.

Each record remains distinct. Missing evidence stays unknown. The workflow does not prescribe, approve a medicine or replace the people who hold those responsibilities.

Representative workflow. No live case data.

The thread shows what a governed record must retain. It does not claim a working integration, current data flow, saving or outcome.

Source class: Approved public or authorised evidence required
Evidence date: UNKNOWN
Scope and limitation: Representative medicines value or formulary switch evaluation; no live case data
Authorised owner: Medicines or pharmacy role, subject to local governance
Decision gate: Human triage and separate human gate
Receiver acknowledgement: Separate response state; not implementation
Later review question: Observed value: UNKNOWN

01
Candidate identified
Source evidence + CandidateSignal
Medicines user checks relevance and source status
Unauthorised, stale, unmapped or missing source remains unavailable or UNKNOWN
02
Triage
TriageDecision
Accept, reject, defer or request evidence
No automatic ActionCase creation
03
Case framed
ActionCase + exact source links
Owner defines objective, scope, participants and due date
No projected figure shown as approved or realised
04
Evidence prepared
Versioned EvidencePack
Medicines, finance and provider contributors add evidence and limitations
Pack stays blocked if a required input is missing
05
Gate review
Approval or override events
Each named role decides within remit
No single role substitutes for finance, clinical, procurement or information governance authority
06
Transfer
Publication
Authorised publisher releases a defined version to named receivers
No publication before required gates
07
Receiver response
Acknowledgement
Receiver records a separate response
Acknowledgement does not equal implementation
08
Follow through
ActionCase activity and blockers
Owner coordinates implementation evidence and exceptions
Progress state does not prove completion
09
Value review
ValueReview + method, source and reviewer
Finance or value reviewer compares projected and observed evidence
Missing data remains UNKNOWN; no realised savings claim without method and verified result

Each record remains distinct. Missing evidence stays UNKNOWN. The workflow does not prescribe, approve a medicine or replace the people who hold those responsibilities.

Best value / formulary

A representative path for reviewing a possible formulary or best value change across evidence, authority and follow through.

First workflow

Illustrative public pathway: DMS expected versus observed

An example for examining an expected pathway against later observed evidence. It is not a working integration and does not indicate NHS involvement or endorsement.

Public pathway example

Shortage / supply pressure

A representative scenario for keeping source limitations, supply effects, blockers and local decisions visible.

Representative scenario

THE WORKING RECORD

Keep source, owner, decisions and blockers together.

An ActionCase is the bounded record around one authorised piece of medicines work. Its target model retains the triggering/supporting evidence, accountable owner, current state, activity, blockers and audit root. It is not the same as an approval, publication, acknowledgement or outcome.

01CandidateSignal: A pre operational signal awaiting authorised human triage.
02ActionCase: The owned working record created after acceptance.
03EvidencePack: Versioned material prepared for review; not the decision itself.
04Publication: A controlled hand off of a defined version and scope.
05Acknowledgement: The receiver's separate response.
06ValueReview: A later review of value and evidence; not automatic proof of savings.

BUILT AROUND HUMAN AUTHORITY

Different roles make different decisions.

A role label in software does not create professional or organisational authority.

Human decision requiredProceed only inside an evidenced and governed scope.

Medicines and pharmacy

Check evidence, triage opportunities, own ActionCases and coordinate the review path.

Finance

Test baselines, assumptions, cost avoided and incurred, workforce/time effects and later observed evidence.

Commissioning and transformation

Sponsor the scope, convene organisations and decide the next evaluation stage.

Providers, practices and community pharmacy

Review scoped hand offs, record acknowledgements or blockers and retain local professional authority.

Assurance and governance

Review the exact intended use, data route, candidate and risks within their remit.

ONE CONFIGURABLE PRODUCT

Tenant configuration, personas and source adapters: not customer forks.

The target architecture is one staff facing product. An organisation may require different roles, settings, source permissions and workflow configuration. These requirements should remain within organisation specific configuration rather than separate customer codebases.

Tenant configuration

Keep organisation specific settings inside controlled configuration. Tenant boundaries must be verified for the exact candidate and scope.

Personas

Present the work relevant to a role without treating a label as authority.

Source adapters

Keep source specific handling separate from the shared operating model and prove each adapter independently.

A BETTER EVALUATION QUESTION

Examine the full effect of a medicines change.

A useful evaluation should define more than a headline opportunity. It should identify the baseline, costs avoided and incurred, time and workforce effects, implementation effort, supply constraints, patient experience question, data limitations and accountable reviewers.

Financial basis

Set out the baseline, costs avoided and costs incurred without converting an estimate into realised value.

Workforce and time

Examine the time, capacity and implementation work required across the affected roles.

Supply and delivery

Keep supply stability, dependencies, blockers and implementation constraints visible.

Patient experience question

Define the question, permitted evidence and limitations without claiming a patient outcome.

Classified public record

Inspect related publisher records

Contributed analysis·Pharmaphorum18 August 2026/Approval is not access: Pilots' real test is implementation Podcast appearance·AI Ethics Now / University of Warwick IATL23 August 2026/AI and Accountability: When Does a Suggestion Become a Decision?Founder commentary·ET Pharma4 August 2026/India’s pharma quality reset will be won after the inspector leaves NEUVIOR analysis·NEUVIOR Insights18 March 2026/From pilot theatre to financial grip: how NHS CFOs should evaluate AI in medicines optimisation NEUVIOR analysis·NEUVIOR Insights20 March 2026/NHS digital programmes do not fail on dashboards. They fail on deployment NEUVIOR analysis·NEUVIOR Insights19 March 2026/The NHS has not finished the generic job NEUVIOR analysis·NEUVIOR Insights19 March 2026/The quarterly medicines leakage report every ICB should want in 2026/27 NEUVIOR analysis·NEUVIOR Insights21 March 2026/Best value biological medicines are the clearest near term medicines productivity play in the NHS Expert commentary·Manufacturing Chemist4 June 2026/NICE approval is not enough: why the UK's next medicines challenge is operational delivery Founder commentary·PharmaTimes10 June 2026/How we roll

MEDICINES ANALYSIS + EXECUTION

You can identify the opportunity and still lose it in delivery.

Explore the financial, operational and governance questions that shaped PHARMORIS. Then check the product’s dated status before treating the model as implemented.

Explore every medicines analysis

NEUVIOR Insights and After Publication reflections are company or founder analysis. Publisher records evidence publication, not endorsement, adoption, product readiness, savings or clinical outcomes.

BRING ONE WORKFLOW QUESTION

See whether one stalled medicines workflow can become owned action.

Bring one evidence bottleneck, decision gap or implementation constraint. We will map it against a representative opportunity to ActionCase workflow and identify what would be needed for a bounded evaluation. Do not submit patient identifiable, confidential or security sensitive material.

Map your medicines workflow Review the assurance boundary