The problem

The policy on the wall is two versions behind the one that was approved.

Procedures get updated, staff get trained on whichever copy they were handed, and consent forms are filed in whatever order the day allowed. Then an inspection is booked and a fortnight disappears into assembling evidence that should already exist.

What changes

Three things healthcare teams notice first

How it works

Three steps, start to finish.

What you get

Everything a practice needs, in one place

Policies, people and proof, without a filing cabinet holding the risk.

Policies and procedures with revisionsScheduled review dates and remindersConsent forms and checklistsTraining records per personConfidentiality set per documentIncident and complaint recordsAudit packs exported on demandTasks assigned to a named personAn audit trail nobody can edit

Every read and every change is recorded, so you can answer a privacy request with the record.

Questions

What people ask first

Confidentiality is set per document and per person, access is checked on every read rather than hidden in the interface, and each access is logged.

Yes. Acknowledgement is recorded per person against the version they read, which is the thing an inspector actually asks for.

The app and its database run in Johannesburg and files are stored in London. Enterprise customers can keep their files in any AWS region, Cape Town included. The database is backed up daily, and personal information is handled under POPIA.

Get started

Put your policy set on it this week.

Fourteen days free, five seats, every module. Load the policies you would be asked for first and see the pack build itself.

Get started

Everything your team runs on, in one workspace.

From the first client call to the final invoice, every part of the work sits in one place. Pick how you want to start.