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
Flor Dental is a private, sign-in-protected prototype for fictional data only. Clinic memberships and role-scoped staff workflows are implemented, but successful tester sign-in, device testing and clinical acceptance are still unverified. A deployed prototype is not a clinical release.
Private prototype for fictional data: practice workflows, role-scoped staff web tools and optional website previews. Implemented does not mean clinically accepted. Tester access, native apps, live integrations and clinical readiness remain unverified.
See implemented features and remaining release gates →What the current build includes
Site access is restricted to the owner and explicitly invited testers, not the public. Application requests separately check identity and clinic permissions; a site invitation alone does not grant a clinic role. The private build includes scoped staff schedules and tasks, actor-attributed audit records and a read-only access check that does not load patient records. Automated tests exercise anonymous and cross-clinic denial, role restrictions and stale or concurrent changes using fictional local fixtures.
Recovery tools are not operational acceptance
The private prototype includes owner-controlled export, backup and empty-target restore tools, plus patient-import preview and reconciliation checks. Local fictional-data tests are evidence about those implementations, not proof of a production migration, a hosted restore rehearsal or an agreed recovery service. Those operational checks remain required before any clinical launch.
What is not established yet
Actual invited-user sign-in, browser and physical-device acceptance, live activation, external integrations, operational recovery and a clinical launch review remain open. No real patient records should be entered. 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.