Desktop clinical software · Real client delivery
DentalClinic
Delivered for a real dental-clinic client in 2021, DentalClinic brings patient management, patient files, medical records and day-to-day clinical workflows into a C# WinForms application on .NET Framework with SQL Server. Treatment planning links that record workflow to a 32-tooth chart with precise treatment-to-region mappings.
- C# / WinForms
- .NET Framework
- SQL Server
- Context
- Real client delivery
- Period
- 2021
- Platform
- Desktop clinic-management application
- Stack
- C# · WinForms · .NET Framework · SQL Server
Desktop software for a real clinic
DentalClinic is desktop software for running a dental clinic day to day, delivered to a real client in 2021. It is built with C# and WinForms on .NET Framework, with SQL Server for persistence.
The 32-tooth chart is its most distinctive screen, set inside a broader clinical and record-keeping workflow.
Organizing clinical work around the patient
Clinical work starts from the patient: who they are, what their file holds and what treatment is being planned. DentalClinic keeps those concerns in one desktop system instead of spreading them across unconnected screens.
Treatment planning adds a domain requirement: the software must record where on a tooth a treatment acts. A chart that only colours whole teeth would lose the difference between a filling, a root treatment and a crown.
The delivered product scope
The delivered application covers patient management, patient files, medical records, day-to-day clinic workflows, dental treatment planning and the 32-tooth chart.
Patient files and medical context
Each patient's file holds their information, and the medical records give clinicians the context for the care being planned. Treatment planning happens within that context, so a planned procedure belongs to a known patient rather than to a detached chart.
Mapping treatment to tooth region
Four mappings carry the clinical distinction: Filling → Middle; Endo → Root; Crown & Bridge → Crown; Exodontia → Whole tooth. Each treatment targets a defined region of the tooth rather than a generic mark.
Figure
| Treatment | Tooth region |
|---|---|
| Filling | Middle surface |
| Endo | Root |
| Crown & Bridge | Crown |
| Exodontia | Whole tooth |
From selected tooth to treatment plan
The chart presents all 32 teeth across the upper and lower arches. Selecting a tooth and a treatment previews the affected region before the treatment is applied.
The screens below contrast that preview with the applied result, where the chart, inspector, treatment plan and session record agree on the same change.
Figures
Before application: tooth 8 is selected and Crown & Bridge previews the crown region. 
After application: the chart, inspector, treatment plan and session record agree on Crown & Bridge applied to tooth 8. 
The same chart workflow in the interactive demo, reflowed for a narrow screen with tooth numbering still readable.
Desktop interaction and structured persistence
C# and WinForms provide the desktop interface on .NET Framework, and SQL Server provides structured persistence. Presentation, business logic and data access sit in separate PL, BL and DAL layers, so the interface, the clinical rules and the stored records each have a distinct responsibility.
Real delivery and private clinical records
The outcome is a desktop clinic-management system delivered to a real dental-clinic client in 2021.
Patient and client data stay private: the original clinic database is neither copied nor connected, and no real patient record appears in this portfolio.
Explore the planning workflow
The interactive demo recreates the chart and treatment-planning workflow with fictional data: one representative slice of the delivered clinic system.
The demo runs without the original clinic database and contains no real patient records.