3 ms·
So our implant planning software coDiagnostiX actually used DICOM data coming from a CT-scan. You need the full bone/jaw information to make sure that the impla
by splittingTimes 5y ago
So our implant planning software coDiagnostiX actually used DICOM data coming from a CT-scan. You need the full bone/jaw information to make sure that the implant goes into a place where the bone is wide enough, had the right density and that you do not hit a nerve. Those are the clinical requirements. On top of that, the placement must allow for a proper aesthetic restoration design by the lab technician, too.
For the latter you then also need the intra-oral scan. The output of the IO scanner is a simple (but massive) 3D point cloud. The software then is meshing those points on the fly. Using the color information from the IO scanners camera, shaders are added to generate the right texture for teeth, gingiva, etc.
We have a module in the CAD Software that allows to Integrate the surgical and prosthetic workflows through real-time case data sharing between coDiagnostiX and DWOS CAD. The Real-time (or asynchronous) connectivity between lab technicians and implant-placing dentists enables better prosthetically-driven implant planning and immediate provisional design.
On a personal note, don't be afraid of the procedure. With those drill guides and today's planning solutions we made leaps in implantology. In the beginning the surgeons did it by hand and feeling. I shudder at the thought.
- PaulDavisThe1st 5y agoThanks for the explanation. IIUC, the "wand" object that was used to generate data inside my mouth is not using any absolute location data, it's just scanning whatever it can and then the point meshing Just Works (TM) ? It seems quite remarkable - the wand is essentially being waved around completely freely, and I was amazed that you could build a model from the data generated in that way.