Due to a chicken-egg problem, most Dental EHR only work in MS Windows while a very few work on macOS and none work on Linux.
Clear.Dental works to fix this by being the first Linux native EHR system that does everything in Linux without having to use a translation layer like Wine or Proton.
Using a keyboard and mouse is not compatible with clinic care. A dental clinic is a wet and dirty environment that requires providers to wear gloves and to avoid cross-contamination wherever possible. One could put a cover over the keyboard or mouse but it makes them very difficult to use. You also can’t place a keyboard near the patient’s mouth for your charting. Doctors have to hire an extra assistant just to help in charting what is in the patient’s mouth.
Clear.Dental solves this issue by being made with touch in mind. Specifically, it was made with resistive touch screens in mind which allows anything (including the explorer) to be used as a stylus. That way, the doctor doesn’t have to stop what he/she is doing and now charting and treatment planning can be streamlined.
Many companies have created EHR system that are not only too complicated for an average doctor to understand, but too complicated for any outside software developer to understand either. Doctors used to enjoy being able to have direct access to their chart information and to make changes directly. The overly complex solution has discourged doctors from truly being paperless in their office.
Rather than use a relational database, Clear.Dental uses simple .ini and .json files that any doctor can read. Give any doctor 30 minutes, and they can learn how to read a .json file. Give them another 30 minutes and they will know how to edit them by hand. Although they do not need to edit the files directly, having the ablity to see the data directly not only gives doctors the freedom to make their own changes, it also gives them the confidence they need to go properly paperless.
There is a different company that makes the charting system, the intraoral radiograph software, the patient reminder software, CBCT software, etc.
Every module is open source and can work as one single suite. There is no need to build a "bridge" because everything works under the same system. This not only makes the different parts of the software easier to manage, but it allows the different parts to work as one single unit with the same look and feel without having to relearn everything.