Administrator guide

Administrator responsibilities

This page describes operating principles rather than guaranteeing a specific security feature. Verify the exact software build and your local security assessment before clinical use.

Accounts and access

The visible application includes user management and approval, account settings and secretary users. Restrict account privileges to job roles, disable unused access and review permissions regularly.

Surgeon profile and output

The Surgeon Profile section includes a title, contact details, address, footnote and optional logo used in printed reports.

Appointment setup

Configure time ranges and slot intervals within Account settings. Establish a local process for recording cancellations, blocked times and changes.

Security checklist

• Use a private network or a correctly configured VPN; enforce HTTPS/TLS for web access.
• Keep operating system, browser, Docker, dependencies and application up to date.
• Back up database and clinical media; verify restoring from backups regularly.
• Ensure only authorized roles access patient records or data exports.
• Set retention, consent, incident response and breach reporting policies with your institution.
• Keep PostgreSQL and internal services off public interfaces.
• Document your legal basis, organizational responsibilities and any processor relationships.

Release validation

After installation confirm authentication, create a synthetic patient, test each clinical module, reporting, backup and restore, and inspect security and server logs before authorizing real patient data.