Digital adoption for NHS clinical systems
Step-by-step guidance inside your clinical systems.
Help staff become confident on new and changing clinical systems sooner, with approved guidance at the moment they need it.
01Studio
Recorded in the application it describes.
Guides are created by carrying out the task in the application itself. Each action is captured as a step, worded from the control’s own label, and the application responds as normal throughout.
- Fill in “Medicine”
- Fill in “Dose”
- Choose “Route”
- Choose “Frequency”
- Click “Confirm prescription”
02Review
Approved by a named reviewer.
A named reviewer approves the exact version, and the approval is bound to a fingerprint of its content. Higher-risk guidance needs an approver other than its author.
Any later edit is a new version that goes back through review.
03Portal
Published item by item.
Each guide goes live on its own, for the wards, sites, screens and staff groups it was written for. Every change rebuilds a bundle signed with ECDSA P-256.
Unpublishing keeps the approval, so republishing needs no new review.
04Guide
On the screen staff are already using.
The browser checks the bundle’s signature before reading it. Each step then highlights the control to use next, explains it in plain words and is announced to screen readers. The application needs no integration and no change to its code or screens.
IT installs the extension through Intune or Group Policy, so staff have nothing to install.
05Certainty
It points only where it is certain.
Nova Guide identifies each control from several signals. When two controls match on every one of them, the step is shown as lost and the guide waits. The clinician can skip the step or leave the guide.
06PULSE
PULSE shows how guidance is used.
Every figure is printed beside the formula that produced it. Events record the guide, the step and the screen’s path, with no page text and no typed values, and staff identifiers are pseudonymised as they arrive.
When a step fails to find its control five times in eight hours, an alert opens, and the fix goes back through review as a new version.
07Withdrawal
Withdrawn in about a minute.
Anyone who works on content can withdraw a guide, with a reason recorded. Open screens stop showing it within about a minute, including a guide already in progress.
A workstation that cannot reach the withdrawal list for 15 minutes stops showing guidance, and staff carry on in the application as normal.
Where to start
Start with the question you need answered.
Chief Clinical Information Officers and programme leads
What Nova Guide does and how its guidance is governed.
Product for chief clinical information officers and programme leadsTraining and adoption leads
How guidance is recorded, reviewed, published and kept up to date.
Authoring in the studio for training and adoption leadsIT and security teams
Browser support, deployment through Intune, and how data is handled.
Deployment for it and security teamsClinical safety officers and IG leads
DCB0129, the controls behind each hazard, and what is recorded.
Clinical safety and governance for clinical safety officers and ig leadsProcurement
The specification, clause by clause, with what is standard and what is configurable.
Specification sheet for procurement
See a guide recorded, approved and published.
A demonstration records a guide, takes it through review and publishing, and shows it as staff see it. It also covers how Nova Guide would be deployed and assured in your organisation.
- RecordingA guide recorded in Nova Guide Studio, click by click.
- Review and publishingApproval by a named reviewer, then the guide going live.
- On the screenThe guide as staff see it, started from the launcher.
- Withdrawal and PULSEWithdrawing a guide, and the analytics behind it.
- Your organisationDeployment, data protection and the clinical safety material.