Aligned with the Arkansas State Dental Association — supporting every Arkansas dental clinic.
Layer · DatabaseWhere every layer eventually lives.
Where every layer eventually lives.
Each category — family / pediatric / cosmetic / orthodontic — has different gravity at this layer. Below, four deep reads on what good looks like for each.
Family / General→
What makes a good family-practice database
Tenant isolation at the database (FORCE RLS + per-transaction GUC), AES-256-GCM PHI columns, audit log keyed off the same encryption.
PediatricComing soon
What makes a good pediatric database
Parent_or_guardian as a distinct encrypted column, child_age as a plain integer (Safe Harbor), age-routed intake submissions.
CosmeticComing soon
What makes a good cosmetic database
Consent_records lattice with revocation cascade, transformation_gallery with one-consent-per-pair invariant, package modeling that supports both pricing philosophies.
OrthodonticComing soon
What makes a good orthodontic database
Virtual_consults with encrypted multi-photo storage, age-aware patient/requestor split, status lifecycle that audit-emits every transition.