Patient Compass Suite
One line, from the first appointment to the last check-up.
Three products that follow a patient through a surgical pathway, built on the same infrastructure and the same rules. Each appears at the moment it is needed, then steps back.
Before surgery
Polaris
Pathway information a patient can hold on to: every phase and step of the procedure they are preparing for, in a standard track and an easy-read track, written from the clinical team's own approved documents.
- Two tracks on every step
- Standard and easy-read, side by side, chosen by the reader.
- Source
- The team's current approved document, reflected exactly, with its version recorded on every item.
- Reader identity
- None. No account, no login, no email.
- Accessibility
- WCAG 2.2 AA, reduced motion respected, content warnings before anatomical detail.
Through recovery
The Compass
A paced recovery companion that the surgical team gives to their patients: what to expect day by day, what is normal and what is not, so nothing depends on memory or chance.
- Pacing
- Editorially chosen post-operative days, not a feed.
- Delivery
- Handed over by the team as a guide with a link and a code; the content it points to is a named, immutable release.
For the clinical team
The Helm
Shared visibility across a pathway for the people running it: what has been published, against which source version, signed off by whom, and what a patient was given.
- Identity
- Clinicians and staff only. Patients are never users of The Helm.
- Handover
- Guide letters reviewed by a staff member before they leave the building.
Beneath the line
Some things the patient-facing surfaces will never do. They are rules of the infrastructure, not settings.
- No patient accounts, logins or email capture.
- No identity-graph or advertising trackers.
- No clinical decision logic: the content informs, the clinician decides.
- No large-language-model calls from the patient app.
- No frozen snapshots: the current approved document is the only source of truth.
- No invented figures: surgeon-discussed parameters stay with the surgeon.
Written down, versioned, signed, kept.
Clinical content is defensible only if its history is. The suite records provenance at the level of the individual item and publishes in releases that cannot change after the fact.
- Provenance on every item
- Each piece of content carries its source document type, the source version it reflects and the date it was last synchronised against that source.
- Reissue propagation
- When a source document is reissued, everything that reflected the previous version is flagged for review automatically. The interval until it is back in sync is tracked, not assumed.
- Audit trail
- Every edit is retained with its author and timestamp.
- Sign-off attests fidelity
- Publication requires a warrant from a registered healthcare professional, signed in their own name, attesting that what is published faithfully reflects an identified approved source. Clinical approval is cited, never performed inside the tool.
- Immutable releases
- Each sign-off produces a named release: a canonical form of the whole pathway with a SHA-256 digest. The live pointer can move; the release cannot.
- Delivery bound to a release
- A link handed to a patient is bound to exact release hashes, so what was given can be shown, later, to be exactly what was published.
Licensed per clinical team.
- Co-branded to the practice, with its own name and lettering.
- Fully white-labelled for corporate partners.
- No operational dependency on GGO Systems: hosting and content can migrate.