Hosting, access, backups, responsibilities
Discuss your practice's environment
What running locally means for your patient data — and what your practice remains responsible for.
Sienna is deployed on a server inside your practice. Patient records are stored on that server, and the system is reached through a browser on your practice network. Day-to-day use does not depend on an external cloud service.
Access to Sienna is controlled through user accounts with role-based permissions, so the people who can view or change patient information are limited to the roles your practice assigns. Accounts, roles, and permissions are configured during installation and maintained by your practice.
The network and access arrangements for your deployment are agreed during deployment planning. Transport encryption, encryption of stored data, and audit logging depend on the confirmed deployment for your practice, so they are stated in your written quotation rather than described generically here. If any of these applies to your setup, it will be written down before you rely on it.
Sienna includes backup and restore tooling, and backups stay inside your practice environment under your control. The backup schedule, storage location, retention period, and who is responsible for restoring are agreed as part of your deployment.
An optional cloud/off-site backup service is available as a priced add-on (see implementation details). No encrypted backup, retention period, or recovery guarantee is promised on this page.
Sienna is installed and configured on-site by our team, including the local environment required to run the platform inside your practice. What your practice needs for hardware, network, and power is assessed during deployment planning and set out in your written quotation. See implementation.
Because Sienna runs inside your practice, the following remain your practice's responsibility: physical security of the server, power and network availability, network security, management of user accounts and roles, and the storage and safekeeping of backups. We cover these during onboarding.
Rather than implying more than the current release supports, this is the boundary:
Read the privacy policy for how the details you submit on this site are handled, or see implementation for installation, support, and terms.
Choose the entry point that fits your stage: a quick sandbox, a guided demo, or a practice-fit discussion for your clinic.
Walk through consultation, records, scheduling, and billing with the team.
Explore the product with sample patient data and no sales call.