Nova Guide
Menu

Deployment

Deployed like any managed browser extension.

Nova Guide reaches the applications staff already use through a browser extension that IT installs and configures centrally. For a web application your organisation runs itself, one script tag does the same job.

1

What it works with

Any web application your staff use in Edge or Chrome, with no change to the application.

1.1Browsers
Microsoft Edge and Google Chrome.
1.2Applications
Web applications used in those browsers: web-based EPRs, other clinical systems, and administrative systems such as e-learning, rostering and referral portals.
1.3Page structures
Single-page applications, frames and shadow DOM.
1.4Several applications
One organisation can run Nova Guide on any number of applications, each with its own content, settings and analytics. A guide can hand over to a guide in another of them.
1.5The application itself
Needs no integration and no change to its code or screens.
1.6Desktop applications
Outside Nova Guide’s scope. A desktop application has no web page for Nova Guide to draw on.

2

The extension, through Intune

Two policies do everything: one installs the extension, and one tells it which applications to work on.

The managed configuration, with illustrative values
api           https://your-service.example
applications  [{ "origin": "https://epr.trust.example",
                  "tenant": "your-trust",
                  "application": "epr" }]
attributes    { "ward": "7B", "site": "Main site" }
2.1Installing
The extension is force-installed by browser policy, from the identifier and update address Nexus Nova supplies. In Intune this is a setting in the settings catalog for Edge or Chrome, and Group Policy has the same setting.
2.2Configuring
A second policy names your Nova Guide service and enrols each application by its exact web address. Intune delivers it as a registry script, because its settings catalog has no native setting for an extension’s own policy.
2.3Workstation details
The same policy can state the ward and site a workstation serves, so content can be offered to them. These details are read in the browser and are not sent to Nova Guide.
2.4Updates
The browser checks the update address about every five hours, so machines move to a new version without further work from IT.
2.5For staff
Nothing to install. The extension shows as installed by your organisation, it cannot be removed, and its settings page reads “Managed by your organisation” with every field read-only.
2.6On other sites
On a site your policy does not enrol, the extension adds nothing to the page.
2.7Network
Workstations reach the Nova Guide service over HTTPS. The service makes no connections into your network, and nothing is installed on your servers.

Checking a machine

  1. The extension appears in the browser’s extensions page as installed by your organisation, with no remove button.
  2. Its identifier matches the one Nexus Nova supplied.
  3. The browser’s policy page lists both policies.
  4. The extension’s settings page reads “Managed by your organisation”, with the right values.
  5. On an enrolled application, the launcher appears in the bottom-right corner.
  6. On any other site, the extension has added nothing to the page.
  7. A content change published in the portal arrives without touching the machine.

Why the extension’s permission is broader than the sites it acts on is explained on the Security page.

3

Citrix and shared workstations

NHS estates mix local browsers, published browsers and shared ward logins. Each has a clear answer.

3.1A published browser
Where Edge or Chrome is published through Citrix, the extension is installed once, in the published image.
3.2A published desktop application
Outside Nova Guide’s scope, as it would be on a local machine.
3.3Shared sign-ins
Where a workstation’s sign-in does not identify a person, Nova Guide counts the workstation, keeps nobody’s progress, and shows an announcement once per browser session.
3.4Named people
Where the application or the page script identifies the person, that reference is pseudonymised as it arrives, and progress and Loyalty can be counted per person.

4

The page script

For an application your organisation runs, a single script tag adds Nova Guide without the extension.

The script tag, with illustrative values
<script src="address supplied by Nexus Nova"
        data-api="https://your-service.example"
        data-tenant="your-trust"
        data-application="rostering"
        data-user-ref="stable id for the signed-in person"
        data-user-attributes='{"staffGroup":"Nursing","ward":"7B"}'
        defer></script>
4.1When to use it
For web applications your organisation runs and can change. The extension remains the route for applications supplied by a vendor.
4.2Required
data-api, data-tenant and data-application: your Nova Guide service and the application, as set up in the portal.
4.3The person
data-user-ref, optional: a stable identifier for the signed-in person, which Nova Guide pseudonymises on arrival. Without it, Nova Guide treats the browser as a shared workstation.
4.4Audiences
data-user-attributes, optional: details such as staff group and ward, used to choose content. They stay in the browser.
4.5Placement
data-position, optional: the launcher in the bottom-right corner, or the bottom-left.
4.6Behaviour
The script starts only after the content’s signature has been verified, and every failure ends with it showing nothing.
4.7Same guidance
Both routes use the same guidance layer, content, approvals and analytics, and a shared link opens a guide by either route.

5

Getting started

From an agreement to the first guide on a ward screen, with each step owned by you or by Nexus Nova.

  1. Agreement

    Both

    The contract and the data protection paperwork. Nova Guide is set up for an organisation once an agreement is in place.

  2. Your organisation

    Nexus Nova

    You tell us your Microsoft Entra directory. We set up your organisation, its pseudonymisation key and your first admin.

  3. Approval tiers

    Both

    We agree your tiers from the clinical or standard template. Changes later are made by Nexus Nova on request, so a tier cannot be relaxed from a screen.

  4. Your team

    You

    Your admin invites authors, reviewers and moderators by email. Each invitation is linked to the person’s Microsoft account when they first sign in.

  5. Your applications

    You

    Each application is registered with its web address.

  6. Rollout

    You

    IT deploys the extension by policy, or adds the page script to an application you run.

  7. The first guide

    You

    An author records it, a reviewer approves it, and it goes live for the screens and staff it was written for.

What Nexus Nova provides

During rollout, Nexus Nova sets up your organisation and its approval tiers, and supplies the extension’s identifier and update address and the Nova Guide policy pack for Intune and Group Policy.

A full day’s training for your organisation covers every feature of Nova Guide.

Support is available Monday to Friday, 9am to 5pm, by email at info@nexusnova.co.uk.

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.

Book a demonstrationRead the specification
  1. RecordingA guide recorded in Nova Guide Studio, click by click.
  2. Review and publishingApproval by a named reviewer, then the guide going live.
  3. On the screenThe guide as staff see it, started from the launcher.
  4. Withdrawal and PULSEWithdrawing a guide, and the analytics behind it.
  5. Your organisationDeployment, data protection and the clinical safety material.