Clinical oversight

Pharmacists remain at the heart of every decision.

A connected workflow should make responsibility easier to understand. Hannah keeps collection, clinical assessment and the work that follows distinct.

Editorial illustration of two professionals considering information together.

The intended purpose

Organise the evidence. Support the review.

Hannah Health is designed to organise structured medication-review information, preserve its source and uncertainty, and support a pharmacist’s assessment, reviewed note and accountable follow-up.

The pharmacist remains responsible for the clinical review. Completing a question set does not complete a medication review, and the end of a conversation does not supply clinical sign-off.

Hannah does not diagnose, prescribe, change doses or renew medicines. The clinical service determines the required record context, reviewer competence, suitable pathway and appropriate next steps.

Built into the workflow

Clear boundaries at each stage.

Governed question sets

Questions are versioned, with approval and retirement history. Clinical owners must agree the wording, suitability and service scope before a patient pathway is used.

Evidence with its limits

Original evidence stays separate from the assessment. Missing, unknown and declined answers remain visible; silence or incomplete information is not treated as reassurance.

A human route when needed

New or changed communication needs hold collection for an owned human review. Unresolved concerns and follow-up need a responsible person and an explicit next action.

Separate completion steps

Collection, pharmacist sign-off, approved note export, filing acknowledgement and action closure are distinct. Each records a different part of the work.

Current product status

In development. Evaluated with synthetic records.

The current application is a working local product used for synthetic workflow evaluation. Separate, authorised staff voice tests are limited development exercises; they do not establish patient readiness.

No patient pilot approval is claimed. Patient-facing operation requires named clinical and information-governance decisions, production identity and security arrangements, provider acceptance, and agreed practice procedures.

The current practice-record route is reviewed note export with manual filing acknowledgement. Direct clinical-system writeback and production patient-call operation are not presented as available capabilities.

Before patient use

Evidence and responsibility belong together.

The responsible people need to agree the service purpose, eligibility, question wording, communication support and escalation arrangements. The operating team also needs a clear approach to access, data handling, record transfer and recovery.

Technical tests can demonstrate a defined software behaviour. They do not replace clinical acceptance, a service agreement or a decision that the product is suitable for a particular practice.

What this means for an enquiry

A product discussion can explore your workflow and the current application. It is an opportunity to understand fit and identify the approvals and practical arrangements a future service would require.

This website does not offer medical advice or a patient support channel. Please keep patient information out of general product enquiries.

Discuss Hannah Health

A conversation about your team

Make room for a better review.

Explore how Hannah could support your medication-review workflow.

The Plum Folio workspace

Current application interface · fictional demonstration data, not measured customer results.

Current Hannah Health overview with labelled demonstration records, completed reviews and owned follow-up.