Modernizing the systems behind ABELDent.
Production clinical application modernization spanning a large SQL database, SQL Server 2022, Windows Server and the workstations that depend on them.
IVAN FERLAND / Independent dental practices
Technology that supports your practice’s working day.
For practice owners and managers considering a website, an application change or an infrastructure project. Your team’s workflow often crosses practice software, imaging, claims connectivity, workstations and a server. Bring those dependencies into focus before changing them.
← HomeWhat needs to work better
- Your website needs clearer practice information or a permitted link to an existing booking service.
- An application or imaging problem crosses the workstation, server, database and vendor boundaries.
- A server or database upgrade needs an application compatibility plan, a rollback path and validation at the workstation.
Concrete deliverables
- A practice website or redesign with usable mobile navigation and agreed enquiry or booking links.
- A dependency review and evidence-based investigation with clear vendor responsibilities.
- A scoped modernization plan, compatibility checks and implementation or cutover support.
POSSIBLE ENGAGEMENT
Modernize the database without losing the workflow
The ABELDent modernization case describes work across application, SQL Server and Windows Server dependencies, vendor coordination and clinic readiness. A similar commission starts with the actual version, supported upgrade path and acceptance checks for your practice.
- 01
Identify application versions, database dependencies and ownership.
- 02
Agree the vendor-supported change and the recovery boundary.
- 03
Validate the application and relevant workstation workflows after the change.
An approach that fits your team
My operational background includes ABELDent, Dentrix, ClearDent, Dentitek and Progitek environments, along with imaging and ITRANS claims-connectivity dependencies. The Stack explains individual technology contexts. Each new practice still requires its own discovery; familiar product names do not establish compatibility.
Experience with these systems is not vendor partnership or certification. Integrations depend on permitted interfaces and access; unrestricted writes to a practice-management database are not an assumed service.
Start with your situation.
Discuss your practice’s projectEnglish or French. Directly with Ivan.