For better or for worse, technology marches on, and it’s no different in the dental industry. We have seen a number of imaging software platforms announce they will no longer be supported, and many offices are looking at options. The challenge (and the opportunity) for an office is that, with a little bit of knowledge, they may be able to save quite a bit of money by avoiding a complete overhaul of all the hardware and software in the office.
One of the biggest challenges that dental offices face is knowing whether things will work together. For so many offices in this situation, they will hear high-priced imaging systems claim “nothing else will work”, while low-priced systems may claim “it will work with everything”.
The reality is usually somewhere in the middle depending not only on what systems are currently being used, but also what your needs and expectations are. More and more, we are hearing from dental professionals who want to understand the tradeoffs more clearly so they can determine the best price without sacrificing image quality or workflow efficiency.
With this goal in mind, we wanted to shed some light on some of the most common questions we hear from dental professionals so that an office can plan ahead and find the right solution for them.
Does my imaging software need to work with my practice management software? The communication linkage between the imaging software and the practice management software is typically referred to as “bridging”. Typically, the bridge offers two things:
1. The ability to open the imaging software directly from the Practice Management software, so that less clicks are required, and the patient being imaged will be automatically selected in the imaging software (i.e. no need to search for patient again in the imaging software after the patient was already looked up in the practice management system).
2. For new patients, the patient information that is entered into the Practice Management system is automatically updated into the imaging software thereby avoiding redundant data entry for new patients.
It’s worth mentioning that the imaging software can operate independently from the practice management system (i.e. without a bridge). However, if they do work together, there are some workflow advantages to this. The bridge will make the user feel like the practice management software and imaging software are one piece of software.
If I change my imaging software, what should I do with all the images that are stored in my current software? Typically, the imaging software is what stores and manages all your digital x-ray images. If you change your imaging software, new images will be stored and managed in the new imaging software. Assuming the new software is not able to simply connect directly with the existing database of images, typically, you have two main options for what to do with the images in your old software.
Option one, is to simply keep a copy of the older software that you already have and use it to access the older images. These images would also typically be archived and backed up as part of the normal IT best practices. With this approach, there is usually a short period where comparing images taken at different times for a patient would require referring to different software. However, after a short period, the need to refer to older images becomes less and less frequent.
Option two applies if both the old software platform and the new software platform are compatible. If they are, the images may be able to be “migrated” to the new software so that the old images would be available in the same place as the new images. Typically, if migrating is possible between the two software platforms, it would be a separate service that may have an additional charge.
Will my current sensors work with my new imaging software? Frequently, the answer to this question depends not only on the system you are using, but also on what’s important to you. Typically, plugging a sensor into a PC that uses another imaging software results in one of three common scenarios:
Scenario One: the imaging software cannot accept the image captured by the sensor. The sensor will not work with the software.
Scenario Two: the imaging software can capture the image, but the software will not offer any “capture automation” capabilities for that sensor. For example, during a multi-image study, the user may have to click to accept each image in the software before moving to the next position. Sometimes, the user may also have to manually rotate and place the images in the correct charting position.
Scenario Three: the software can capture an image and apply the same automation capabilities that its own sensor would have.
Some offices may see Scenario Two as unacceptable, while other offices may be ok with this if they are saving money. To further complicate matters, sometimes either the imaging software or the sensor (or both) may have the potential to work together to achieve Scenario Two or Three above, but they may require additional pieces of software to do so. In most cases, this additional software comes from the sensor provider, and is called a “driver”. A “driver” is a generic term for a small piece of software that is provided by the hardware manufacturer to “handshake” with a larger software application (e.g. a “TWAIN” driver is a very common one).
If you have any questions, or would like to better understand the tradeoffs of different options, please reach out to talk to one of our specialists.
Subscribe to Receive More Great Articles