Security and product readiness
Dental Software Security and Product Readiness
Review the private prototype’s current access model and the security work required before a clinical launch. No compliance certification is claimed.
At a glance
The current private dental prototype requires sign-in and keeps saved records separated by the signed-in user. It is for fictional data only. A full clinic access model and production security review remain outstanding.
The private prototype supports saved patient profiles, scheduling, visit statuses and recall tracking. Clinical, billing, insurance, messaging and website integrations described in our roadmap are not yet available for clinical use.
Review what is available →What the current build includes
The private site limits access to its owner. The application checks identity on data requests, scopes saved records to that identity and records successful patient and appointment changes. Local tests cover anonymous requests, cross-user access attempts, stale edits and booking conflicts.
What is not established yet
The prototype does not yet have shared clinic memberships, clinical staff roles, a completed recovery programme or a clinical launch review. Canadian data residency, regulatory compliance, completed vendor agreements and formal certifications are not being claimed.
Questions for any software evaluation
Request evidence for access controls, support access, logging, export capability, backup restoration, incident handling and responsibilities between vendors. Evaluate contractual and regulatory obligations with qualified advisers for your practice and location.
Official references
Use these sources to verify current requirements and product information for your own evaluation.