Dental Software and Imaging Support for Chicago Practices: Which Layer Failed and Who Owns the Fix
At 9:40 on a Tuesday in a Naperville office, the intraoral sensor in operatory three reports "device not found." A patient is already reclined with a bitewing holder in hand. The front desk calls the imaging dealer, who says it sounds like a computer problem and to call IT. IT asks whether the software vendor pushed an update last night. If you want the commercial view of who covers this work across the city and suburbs, Legend's page on IT support for dental offices in Chicago sets it out; this guide stays on the operational side.
This guide is for the owner or office manager who has just lived that morning. It sorts symptoms into layers, shows how Chicago buildings shape software speed and imaging transfers, and lists what to write down so the next call is short. For the wider picture of buildings, weather and support across the metro, see our Chicago dental IT guide.
In this guide
- Why do dental software and imaging problems bounce between vendors in Chicago practices?
- Which layer is failing? A symptom table for front desks from the Loop to Orland Park
- What does IT look after in Dentrix, Eaglesoft, Open Dental and Archy, and what stays with the vendor?
- Where does imaging break in Evanston, Oak Park and Schaumburg offices: sensors, pans or CBCT?
- How do Chicago buildings affect software speed and imaging transfers?
- What should your practice keep in a software and imaging record?
- When should updates, upgrades and new workstations happen?
- What changes when a Chicago practice switches or adds software?
- What does Legend do for Chicago-area practices' software and imaging?
- What to ask your IT provider about software and imaging
- Sources
- Frequently asked questions
- The bottom line
Why do dental software and imaging problems bounce between vendors in Chicago practices?
They bounce because a single X-ray passes through four or five owners before it lands in a chart. The sensor maker, the imaging dealer, the practice-management vendor and the IT provider each own a slice, and each can truthfully say "our part looks fine." Nobody is lying; nobody holds the whole picture unless the practice asks someone to.
Think of a capture as a relay. The sensor hands an image to a driver on the operatory computer. The imaging program saves the file to a storage location, usually a share on a server or a network storage box in the closet. A bridge (the small piece of configuration that tells the imaging program which patient is open in the practice-management system) links that file to the right chart. The practice-management database records the visit. If the practice uses a cloud system, part of that relay runs over the internet circuit.
Each hand-off is a place to drop the baton. When Dentrix, Eaglesoft and Open Dental problems in Chicago-area offices get passed around, it is almost always because the symptom shows up in one layer while the cause lives in another. A sensor that "isn't found" may have a perfectly good sensor and a Windows update that replaced its driver. A chart that won't show today's pan may have a working pan and a storage path that changed when someone renamed a server.
The practical fix is not a better phone tree. It is knowing the layers well enough to name the likely one before the first call, and having a provider who will say which layer failed and who owns the fix rather than "try the vendor." That is also the thread running through our wider guide to dental IT in Chicago, which covers how practices across the city and suburbs choose and run their IT. For the national view of how practice-management and imaging systems are looked after, Legend's page on practice-management software and imaging support sets out the scope.
Which layer is failing? A symptom table for front desks from the Loop to Orland Park
Start with what the front desk sees, then match it to a layer. Most symptoms point to one of six places: the workstation, a network share, the imaging bridge or driver, the sensor and its USB path, the practice-management database, or a vendor's cloud service. The table below gives the usual owner and what to have ready.
"Usually" matters. Every practice is wired a little differently, and a symptom can have more than one cause. Use the table to make the first call to the right party, not to diagnose the problem yourself.
| What the front desk sees | Likely layer | Who usually owns the fix | Have this ready before you call |
|---|---|---|---|
| Sensor reports "device not found" in one operatory, works in others | Sensor or USB path, or the driver on that computer | IT first; imaging dealer if the sensor fails on a known-good computer | Operatory number, the exact message, whether anything was moved or updated, a photo of where the cable plugs in |
| Image captures, but never appears in the patient's chart | Imaging bridge | IT first; PMS or imaging vendor if the bridge settings check out | Patient name and time of capture, which program was updated last, whether other operatories attach normally |
| Pan or CBCT saves at the unit, but other rooms cannot open the study | Network share or storage path | IT | The study date, the room trying to open it, whether the server or storage box was restarted recently |
| Dentrix, Eaglesoft or Open Dental is slow on every computer at once | Server, database or network | IT; vendor if IT finds the database itself is the cause | Time of day it started, whether it is worse at peak check-in, any recent server change or new software |
| The PMS is slow on one front-desk computer only | Workstation | IT | Computer name, how long it takes to open a patient, whether the computer was recently replaced or updated |
| "Cannot connect to database" or "server not found" for everyone | Server, database service or network | IT | Whether the closet lost power, whether lights on the switch look normal, who last touched the closet |
| A cloud practice-management system logs everyone out or freezes | Internet circuit, firewall, or the vendor's cloud | IT to check the circuit; the vendor if their status page shows a problem | Whether other websites load, the vendor's status page, whether the office is on a backup connection |
| License or activation error on opening the program | Vendor license | The software vendor | License or customer number, which seat failed, the message text |
| A screen inside the program behaves wrongly (a report total, a ledger field) | Application | The software vendor | Steps to reproduce it, a screenshot, the program version |
| Everything broke the morning after an update | Whichever layer was updated | Whoever pushed the update; IT to roll back or check drivers | Which program updated, when, and on which computers |
Two habits make this table work. First, the last change is the first suspect: an update, a moved computer, a new device on a hub, a closet power-off. Second, the person calling should describe what they see in plain words and avoid guessing at the cause on the phone. "The image saved but isn't in the chart" sends the call to the bridge; "the X-ray system is broken" sends it nowhere in particular.
What does IT look after in Dentrix, Eaglesoft, Open Dental and Archy, and what stays with the vendor?
IT looks after the environment a practice-management system runs on: the server or cloud connection, Windows, the network, workstations, printers and scanners, antivirus settings, backups and the paths that link imaging to the chart. The vendor looks after its own code, licenses, features, data conversions and anything that only its tools can repair.
Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy. That wording is deliberate. The products are the ones your team uses all day; their makers write and fix the programs. An IT provider makes sure the computers, network and storage underneath them behave the way the programs expect.
In practice, the split looks like this for an office on Michigan Avenue or a group practice in Oak Brook:
- Dentrix. Slow loading across the office is often an environment question: server resources, network speed between front desk and server, or security software scanning files it should be told to leave alone. The national write-up on why Dentrix runs slowly walks through those checks, and the Dentrix IT support page describes the environment Legend looks after.
- Eaglesoft. The common "everyone is locked out" morning usually starts on the server, with a stopped service or a restart after an overnight update. The Eaglesoft IT support page covers that side.
- Open Dental. Open Dental's own requirements page warns that other services running on the same physical server "may use up resources that result in slower database service." If your Open Dental server also hosts imaging, file sharing and an old fax program, that sentence is worth reading twice. The guide to why Open Dental is slow takes it further.
- Archy. As a cloud system, Archy moves the database off-site, so the local questions become the internet circuit, the firewall, the browser and the imaging computers that still sit in the operatories.
None of this says anything about how good or bad a product is. It is a map of who to call, and it holds whichever system the practice has chosen.
Where does imaging break in Evanston, Oak Park and Schaumburg offices: sensors, pans or CBCT?
Imaging breaks at the joints: the USB path from sensor to computer, the driver that Windows updates can replace, the bridge to the chart, and the storage that 3D studies fill. Sensors fail most often at the cable and driver; pans and CBCT units fail most often at the network path and storage where their large files live.
Dental imaging and sensor problems in Naperville and Schaumburg sound the same as they do in Evanston or Oak Park, because the joints are the same. What differs from office to office is which joint is weakest. Legend supports the IT environment for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, and the questions below apply across all of them.
Intraoral sensors. A sensor draws power and data through one USB connection. Front-panel ports, extension cables run along a cabinet, and hubs shared with a keyboard or foot pedal are common reasons a sensor appears and disappears. After a Windows update, the driver the sensor relies on may have been replaced with a generic one. A useful first test is the sensor on another operatory computer: if it works there, the sensor is probably fine. The DEXIS IT support page describes how that environment is handled.
Panoramic units. A pan usually has its own acquisition computer. That computer writes each image to a shared location the rest of the office can read. When the shared location moves, fills up or loses its permissions, the pan keeps capturing while the chart stays empty. That is the classic case of who to call when the X-ray software stops talking to the PMS: the IT provider, to check the path and the bridge, before the dealer.
CBCT. A 3D study is many times larger than a 2D image, so CBCT is where storage space and network speed show up first. A study that opens at the scanner but crawls in the consult room points to the path between them. Planmeca publishes separate requirements for 2D and 3D work, and the Planmeca Romexis IT support page covers that environment. Ask your provider how much free space the imaging storage has and who checks it.
Bridges. The bridge is the most fragile joint because two vendors' updates touch it. After either program updates, test one capture end to end before patients arrive. Legend's national article on dental imaging integration troubleshooting goes through bridge faults step by step.
How do Chicago buildings affect software speed and imaging transfers?
The building decides where the closet sits, how long the cable runs are, whether the network is yours or the landlord's, and how many walls sit between the pan room and the server. Those facts turn into slow charts and late images. The table pairs common Chicago-area building types with the effect and the check to ask for.
None of this needs a measurement to be useful. It is a list of questions to put to whoever looks after your network, and the answers tell you whether a slow chart is a software problem or a building problem.
| Building type | What it can do to software and imaging | What to check |
|---|---|---|
| Loop or River North tower suite on a shared building network | Building-provided internet or wiring may pass through equipment the practice does not control; cloud PMS sessions and remote imaging reads depend on it | Whether the practice has its own circuit and firewall, who holds the keys to any building telecom room, and whether clinical computers are on a network separate from guests |
| Converted storefront on a Lincoln Park or Lakeview arterial with one closet | Server, switch, phone gear and storage often share a small closet that also holds supplies; heat and cramped cabling can cause slowdowns that look random | Ventilation in the closet, whether the server sits on the floor, whether network cables are labeled to rooms |
| Brick walk-up or older mixed-use building in Evanston or Oak Park | Operatories may sit on a different floor from the closet, with cabling fished through old walls; one room can run slower than the rest | Whether each operatory has a wired connection at full speed, whether any room relies on Wi-Fi or a small desk switch |
| Suburban strip-center office in Schaumburg or Orland Park | The pan or CBCT room is often at the far end of a long suite from the closet; long runs and added switches slow large file transfers | The path from the imaging room to storage, the number of devices in between, and where the acquisition computer saves |
| Medical office building in Naperville, Oak Brook or Arlington Heights | Landlord rules may govern ceiling access, new cable runs and rooftop or telecom-room space | What the lease allows for cabling, who approves work in shared spaces, and whether the practice has its own closet |
| New build-out or second-generation suite in Aurora or Joliet | A fresh start, or cabling left by a previous tenant that nobody has tested | Whether old cable was tested before reuse and whether the imaging room was planned with its own network drop |
Two of those rows deserve a note. In a tower, the practice may not own the network gear upstream of its suite, so a provider needs to know where the practice's equipment ends and the building's begins. In a strip center, the long run to the pan room is easy to forget until 3D arrives. Legend's network design page covers how practice networks are planned. If you are building out a new suite, our guide to dental startup IT in Chicago covers the questions to settle before the walls close.
What should your practice keep in a software and imaging record?
Keep one short document, owned by the practice, that says what you run, where it lives, who supports each piece and when changes are allowed. It turns a vague emergency call into a specific one, survives staff turnover, and makes a provider change or an office move far less painful.
A practice's IT provider can help assemble it, but the practice should hold the master copy. Here is what belongs in it:
- [ ] Practice-management system: product name, version number, whether it runs on a local server or in the cloud, and the date of the last major update.
- [ ] Imaging programs: each product in use (2D, pan, CBCT, intraoral camera), with version numbers and which computer acts as the acquisition station for each unit.
- [ ] License keys and customer numbers: who holds them (a named person at the practice, not only the vendor or a former manager) and where they are stored.
- [ ] Bridge settings: which bridge links imaging to the PMS, a screenshot of its settings page, and who set it up.
- [ ] Imaging storage path: where images are saved, what device holds them, and how much free space was left at the last check.
- [ ] Backup of images and database: what is backed up, where the copy goes, and the date of the last test restore. Backup design is a separate conversation, but the record should note the basics.
- [ ] Drivers: the sensor and camera driver versions that are known to work on your current Windows version.
- [ ] Vendor support contacts: phone numbers, portal logins held by the practice, and your account numbers for each software and imaging vendor.
- [ ] Update windows: the agreed time for updates outside patient hours, and who approves exceptions.
- [ ] Change log: one line per change (date, what changed, who did it).
If the practice has a records-retention question about stored images, write down the answer your compliance advisor gives you, alongside the storage path.
When should updates, upgrades and new workstations happen?
Updates belong outside patient hours, with one test capture and one chart lookup before the first patient. Upgrades of the PMS or imaging program should be scheduled, with a fallback plan. Workstation replacement becomes a question when a computer no longer meets the vendors' current requirements or runs an operating system the maker no longer supports.
Each of those deserves a short rule in the record:
- Routine updates. Windows and security updates run after hours, with the IT provider watching for anything that touches imaging drivers. The next morning, one person captures a test image and opens a patient before the day starts.
- Program upgrades. A version change to Dentrix, Eaglesoft, Open Dental or an imaging suite is scheduled for a quiet period, such as a Friday afternoon or a closed day, and both vendors involved in any bridge are asked whether their versions still work together.
- New workstations. Before buying, compare the computer against the current requirements from your software vendors. Legend's article on dental software system requirements collects them in one place.
- Operating systems. Microsoft ended support for Windows 10 Home and Pro on October 14, 2025, and Open Dental now lists Windows 10 among formerly supported systems. An operatory computer still on Windows 10 is a question to raise, starting with whether its sensor driver has a Windows 11 version.
Hardware refresh is a budgeting question as much as a technical one. Ask your provider which computers are oldest, which ones run imaging, and which would fail first. The workstations and servers page describes how Legend handles that side.
What changes when a Chicago practice switches or adds software?
Switching a practice-management system or adding an imaging unit changes every layer at once: new database, new bridge, new storage needs and new training. Plan the data conversion with the vendor, the environment with IT, and keep the old system readable until the new one is proven. A second location adds the question of how both sites reach one database.
Keep this part short in your planning, but do not skip it. The national dental software migration checklist lays out the sequence. For a Chicago practice, the local wrinkles tend to be about buildings and growth: a Lincoln Park office adding a Wheaton location, or a Naperville practice adding CBCT to a room that was never wired for it. In both cases, the record above makes the planning conversation shorter, because the provider can see what exists before proposing what comes next.
What does Legend do for Chicago-area practices' software and imaging?
Legend Networking looks after the IT environment for dental practices: computers, servers, networks, backups and the practice-management and imaging systems named below. It is headquartered in Dallas, works remote-first nationwide, and has served over 3,500 practices since 2004. The facts below are the same for a practice in the Loop as for one in Joliet.
The facts, in the form Legend states them:
- Experience: 22+ years in dental IT (since 2004). Served over 3,500 practices since 2004.
- Software and imaging: Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy, and for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging.
- People: In-house engineers; no outsourced first-level triage. A staffed 24/7 helpdesk at 1-800-794-1588, and 24/7 monitoring.
- Onsite: Onsite dispatch by appointment across served dental markets; remote-first nationwide.
- Price: Starting at $360 per month. Hardware procurement, major cabling projects and software licensing are quoted separately.
- Reviews: 4.8 rating · 173 Google reviews.
- Leadership: Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.
Two Illinois practices on Legend's project pages. Seven Bridges Dental Studio sits in Woodridge, in DuPage County; Legend marked its first anniversary in posts from August and September 2023, together with Dr. Fariha Querishi's Dental Town cover and her ADA Design Innovation Award. Little Roots Pediatric Dentistry is in Bartlett, northwest of the city; Dr. Marissa Dziepak's new practice was nearing opening while Legend's team worked on-site to install and configure its technology.
For scope, coverage and how a Chicago practice starts, see Legend's Chicago dental IT services page. If you are weighing a fully managed arrangement against calling someone when things break, our guide to managed IT for Chicago dental practices compares the two.
What to ask your IT provider about software and imaging
Whoever looks after your practice, these questions show whether they can work across the layers or only inside one. A provider should be able to tell you which layer failed and who owns the fix, and explain it in plain words.
- Which of our practice-management and imaging programs do you look after the environment for, by name?
- When a sensor stops working, what do you check before telling us to call the dealer?
- Who holds our license keys and vendor logins today, and how would we get them if we changed providers?
- Where are our images stored, how much space is left, and who checks it?
- Which bridge links our imaging to the chart, and do you have its settings written down?
- When do updates run, and what happens if an update breaks a driver overnight?
- Do you test one capture after updates before our first patient?
- Which of our computers no longer meet our software vendors' current requirements?
- Are any operatories or imaging rooms relying on Wi-Fi or a desk switch, and should they be?
- If we add CBCT or a second location in the suburbs, what would change in our network and storage?
- Will you help us build and keep the software and imaging record described above?
Sources
- Microsoft Learn, "Windows 10 Home and Pro" lifecycle page (end of support October 14, 2025): https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro (accessed 2026-10-23)
- Open Dental Software, "Computer Requirements": https://www.opendental.com/site/computerrequirements.html (accessed 2026-10-23)
Frequently asked questions
Who can fix a dental X-ray sensor that stopped working in an Evanston office?
Start with your IT provider, because most sensor faults sit in the USB port, cable or driver rather than the sensor itself. A quick test is plugging the sensor into another operatory computer. If it works there, the problem is the first computer. If it fails everywhere, the imaging dealer handles the sensor. Legend supports the IT environment for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging.
Is remote support enough for Dentrix problems in a Schaumburg practice?
For most Dentrix problems, yes, because slowness, database connection errors, Windows updates and security settings can be checked remotely. Physical faults such as a failed cable, a dead switch or a server that will not power on need hands in the office. Legend's model is onsite dispatch by appointment across served dental markets; remote-first nationwide. Ask any provider how it handles the physical cases.
Why is Open Dental slow at the front desk in our Oak Park office?
If every computer is slow, look at the server: Open Dental's own requirements note that other services on the same physical server can slow its database. If only the front desk is slow, check that computer's age, its network connection and whether it runs on Wi-Fi. Write down when the slowness started and what changed around that time.
Who should keep our imaging software license keys?
A named person at the practice, usually the owner or office manager, should hold license keys, customer numbers and vendor portal logins, with a copy in the practice's software and imaging record. Your IT provider and vendors may have copies too, but the practice should never depend on one outside party or one former employee to find them.
Can a Naperville practice update Eaglesoft without closing for a day?
Usually, yes, with planning. Schedule the update for a closed day or after the last patient, confirm the imaging vendor's version still works with the new Eaglesoft version, and have the IT provider check the server and workstations first. The next morning, capture one test image and open one chart before patients arrive. Keep a way back if the update misbehaves.
What should we tell IT when the pan won't send images to the chart?
Say which unit and room, the patient and time of the capture, and whether the image is visible on the pan's own computer. Mention any recent update, server restart or renamed folder. That tells IT whether the fault is the storage path, the network or the bridge, which is the right starting point before calling the imaging dealer.
Do Loop office buildings cause problems for dental imaging?
They can, mostly through the network. In some towers, internet service or wiring passes through building equipment the practice does not control, which matters for cloud systems and large imaging files. Ask whether your practice has its own circuit and firewall, where your equipment ends and the building's begins, and whether clinical computers are separated from guest Wi-Fi.
What does software and imaging support cost for an Oak Brook dental office?
Legend's IT plans are "Starting at $360 per month". Hardware procurement, major cabling projects and software licensing are quoted separately, and new practices still being built out receive a custom quote. Before comparing quotes, the Free Dental IT Assessment is one way to get a written picture of where your systems stand today.
The bottom line
If the sensor, the pan or the chart has cost your team a morning recently, it is worth looking at the whole chain rather than the last broken link. You are welcome to book a Free Dental IT Assessment for your office: it reviews your computers, software, network security, backups and performance, and you receive written findings with prioritized recommendations.