Skip to main content
Quick summary
  • Publishing puts a bundle of approved versions, one per product, on your Trust Centre under its own link.
  • A new published hazard log starts as “Private - requires access request”.
  • Update notifications need a privacy notice URL on your Trust Centre.

​
Publish a hazard log

A published hazard log is a bundle of approved versions of individual product hazard logs, usually the latest of each, with its own public link.
1

Open the published hazard logs

On the Hazard Log page, click Publish to open the Published Hazard Logs sheet.
The Published Hazard Logs sheet with a card for each published hazard log, its product badges and public URL

The Published Hazard Logs sheet, searched for one hazard log. Each card shows the products in the bundle and its public link.

2

Pick the versions

Click Publish New, then choose the products. Each product shows its 2 latest versions, and Show all lists the rest.Click Select Most Recent to tick the latest version of every product, then untick any you want to leave out. Click Next once at least one version is selected.
The Publish new hazard log dialog with the Clinic Triage Assistant version table and its latest version ticked

Choose a version for each product. Select Most Recent ticks the latest of each.

3

Create a new hazard log or update an existing one

  • To create a new bundle, fill in Hazard Log Title and Hazard Log Description under Publish a new hazard log. Assuric suggests both from the product names. Don’t use special characters in the title.
  • To update a bundle you’ve already published, choose it under Or update an existing published hazard log. The button changes to Update and the title and description fill in for you.
Update replaces the versions with the ones you ticked, so tick a version for every product it should still include, not only the one that changed.Then click Publish New or Update.
The second step of Publish new hazard log with the selected versions, Hazard Log Title and Hazard Log Description, and the update an existing published hazard log section

Name the new hazard log, or choose an existing one to update.

4

Set who can see it

A new published hazard log starts as “Private - requires access request”. To let anyone view it, open the resource in your Trust Centre and set Public? to “Public - anyone can view”.You can also place it in a folder with Folder (Optional). See Access requests and who can see what.

​
Manage a published hazard log

On a card in Published Hazard Logs, Edit Details in the ”…” menu opens Edit Published Hazard Log Details, which changes only the Title and Description.

​
What customers see

The link opens a bundle page with Download All (Download for a one-product bundle) and a card with a View button for each product version.
A published hazard log page with its title, description and Download button, and a card for the product version showing counts, summary of changes and approval date

The bundle page. Each card is one approved product version.

View opens the product page, with a Download button and 2 tabs:
  • Hazard Log lists each hazard with its causes, initial risk, controls, residual risk and status.
  • Transferred Controls lists the controls that are the deploying organisation’s responsibility.
A control’s evidence count opens Evidence for control, which lists each item with its link.
A published product hazard log with the Hazard Log tab open and the first hazard expanded to show its cause and controls

A product page, with a hazard expanded to show its causes and controls.

Published hazard logs that aren’t in a folder appear under Hazard Logs on your public Trust Centre.

​
Keep it current

1

Approve the new version and republish

Approve the product’s new version with Update published hazard logs for this product ticked.
2

Notify stakeholders

Open the card’s ”…” menu and click Send Notification, which opens the Send trust page update notifications flow in your Trust Centre.
You can’t send notifications until your Trust Centre has a privacy notice URL. Set it before you need it.

Approve and version your hazard log

Save a version and update the logs where it’s published.

Notify stakeholders of updates

Tell the people who hold a published resource that it changed.