Skip to main content

Governed workflow

Accountable coordination, with human decisions at every gate

PHARMORIS is intended to support repeatable medicines workflows while keeping triage, approval, professional judgement and local governance with authorised people.

Workflow | Configurable, not customer forkedAuthority | Server derived and human gatedAutomation boundary | No autonomous approval or prescribing

ActionCase sequence

Keep the source, decision and activity in one reviewable thread.

The intended workflow begins with approved evidence and ends with evidenced closure or a recorded stop decision.

01

Source and signal

Identify the source, rights, provenance and candidate issue.

01
02

Authorised triage

A responsible person decides whether the signal should become an ActionCase.

02
03

Evidence Pack

Assemble decision context, limitations and required review material.

03
04

Governance gate

The authorised body records a decision and accountable owner.

04
05

Activity and review

Track blockers, value review, closure and the controlled record.

05

One configurable product

Variation belongs in configuration, personas and source adapters.

PHARMORIS should not become a collection of customer specific code forks. Bounded configuration must preserve one product and one assurance path.

01

Personas

Present the information and actions appropriate to an authorised role.

02

Workflow configuration

Represent local gates without changing the core product identity.

03

Source adapters

Keep source specific ingestion separate from the governed operating model.

Automation boundary

Automation may support the record. It must not inherit human authority.

No automated step should be presented as approval, prescribing or clinical judgement. Failed source calls must not appear as successful activity.

Human decision requiredProceed only inside an evidenced and governed scope.
01

Assist

Support structured capture, routing and completeness checks where verified.

Permitted intent
02

Escalate

Route uncertainty, missing evidence and low confidence states to authorised people.

Required
03

Stop

Block progression when authority, evidence, tenant context or source status is uncertain.

No go

Classified public record

Make the next step useful

Bring the problem that needs a clearer decision.

Tell us what is stuck, what decision you need to make and what a better outcome would change. We will connect you to the most relevant NEUVIOR, PHARMORIS, media or investor route.

QUESTIONS · ANSWERED DIRECTLY

The useful answers, in one place.

Browse every question
01What problem does PHARMORIS address?

Medicines teams can identify an opportunity yet still lack a consistent way to connect the evidence to a decision, accountable owner, delivery tasks, blockers and a reviewed result. PHARMORIS is being built for that operational gap.

02Who is PHARMORIS intended for?

PHARMORIS is intended for authorised medicines, pharmacy, finance, procurement and operational teams working inside responsible healthcare institutions. Scope and deployment requirements must be agreed for each organisation.

03Does PHARMORIS replace professional judgement?

No. PHARMORIS is designed to structure evidence and accountable work while keeping professional and institutional decisions with authorised people.

04What is an ActionCase?

An ActionCase is the governed unit of work at the centre of PHARMORIS. It can hold the evidence basis, scope, owner, decisions, tasks, blockers and review record for a medicine opportunity.

05Is PHARMORIS ready for production or deployed?

PHARMORIS is under controlled development and should not be interpreted as a live, adopted or clinically approved product unless a current, specific deployment record says otherwise.

06Does the public demonstration use patient data?

No. Public and representative demonstrations are designed without live data that identifies patients. Any future institutional data scope would require separate governance, security and contractual controls.