Product
Product
What the platform does for dental clinics, and how requirements are tracked.
Owner: ProductLast reviewed:
The platform assists Canadian dental clinics across four connected areas:
- Clinical documentation — record a patient visit (with explicit consent), get a diarized transcript, and generate draft clinical notes with evidence links back to the transcript. Drafts land in a review workspace where a dentist edits, regenerates, or approves section by section.
- Treatment planning — procedure catalogs and fee guides, plan options and comparisons, consents, instructions, referrals, and prescriptions.
- Patient communication — patient-friendly summaries (English/French), a secure patient portal for document review, e-signatures, and treatment acceptance. Email is a notification with a secure expiring link, never a PHI attachment by default.
- Clinic management assistance — organizations, clinics, locations, rooms, staff and roles, patients, appointments, reporting, and integrations (starting with ABELDent).
Every AI-generated artifact is an unapproved draft until an authorized dental professional approves it; approvals are recorded as hash-chained audit events.
Pages in this section
- Requirements Traceability Matrix — the
canonical requirement-by-requirement status table (mirrored from
docs/product/requirements-matrix.mdin the repo), mapping each prompt requirement to where it is implemented.
Where product truth lives
| Question | Answer lives in |
|---|---|
| What must the system do? | Requirements matrix |
| Why is it built this way? | Architecture Decision Records |
| When does scope land? | Implementation plan |