Separation by design.
Responsibility by default.
A transparent view of the proposed multi-tenant architecture and the controls that need to be validated before production. These are design requirements, not certification claims.
A boundary around
each practice.
The SaaS concept uses a database-per-tenant approach: a shared application layer with a separate proposed data store for each practice tenant.
This is a target architecture for the SaaS product. Existing local module work has its own implementation boundaries and does not prove multi-tenant production isolation.
No security certification, independent penetration test, uptime commitment or production hosting assurance is claimed.
Controls that deserve
evidence.
Production readiness requires implementation, testing and operational ownership of each control.
| Design requirement | Intended approach | Evidence still required |
|---|---|---|
| Access control | Tenant-scoped roles, module permissions and server-side authorisation. | Cross-tenant isolation tests and role-based access review. |
| Data protection | Minimise fields, define retention and restrict data access. | Data inventory, retention policy, contracts and hosting decisions. |
| Integration credentials | Keep credentials outside browser code; separate access by tenant. | Secret storage, key rotation and revocation procedures. |
| Audit & recovery | Trace significant actions and define backup and recovery responsibilities. | Logging review, backup restore tests and incident procedures. |
| AI oversight | Bounded knowledge, staff review and clear reception handoff. | Model behaviour testing, data handling review and escalation validation. |
Questions, answered plainly.
Is the platform production-ready?
No. The platform is in development. Local module validation and this website do not establish production security, deployment or operational readiness.
Does this website collect patient information?
There are no patient accounts, clinical records or live integrations here. All workflow examples are fictional. Please do not enter patient or sensitive information into the enquiry form.
Is the database-per-tenant model already deployed?
No. It is the proposed SaaS architecture. Provisioning, migrations, recovery and cross-tenant controls need implementation and validation for that model.
What is the status of compliance claims?
No accreditation, regulatory approval or compliance certification is asserted. Applicable obligations and supporting evidence must be reviewed before any operational launch.
Show us the work
you want to make easier.
Choose your priorities. We’ll discuss the supported workflows, setup and the right next step for your team.