IT Infrastructure for Dental Practices: The 9-Component Standard
The quote on your desk says "network refresh" and lists eleven items you cannot judge. Or the server made a noise last month, the sensor computer in operatory three reboots itself on Mondays, and the Wi-Fi drops around lunch. Either way the question is the same: what should the IT infrastructure of a dental practice look like, and how far is ours from it?
This guide is the standard, not the shopping list. It gives every component in plain words, says what "good" means for an office of one to three locations, puts a year count on replacement, shows what changes when a second office arrives, and ends with a self-audit you can run in half an hour. The deep dives on each component are linked where they belong; the owner-level view of the whole stack is in our guide to dentist office technology, layer by layer.
IT infrastructure for a dental practice is nine components: internet with a failover path, a firewall, switching and cabling, Wi-Fi, a server or cloud host, workstations, imaging and sensor computers, backup, and phones with power protection. Each has a standard a practice can check, a replacement cycle in years, and an owner. Score all nine before you sign anything.
- Dental practice IT infrastructure is nine components: internet with failover, firewall, switching and cabling, Wi-Fi, server or cloud host, workstations, imaging and sensor PCs, backup, and phones with power protection.
- Each component has a standard you can check without a technician: two internet paths tested, a supported and managed firewall, managed switches with a cable test report, clinical computers on cable, a dedicated supported server, one encrypted login per person, imaging PCs above the vendor's spec, a dated restore test, and a UPS with tested shutdown.
- Replace on a calendar, not on failure: workstations every five to six years staggered, the server at five years or its OS end-of-support date, switches at seven to eight years; Windows 11 24H2 support ended on 13 October 2026 and Windows Server 2016 ends on 12 January 2027.
- A second office changes identity, network, data, monitoring and the written build standard, not the component list.
- Score the nine rows from 0 to 2; any zero on backup, server or firewall comes first, whatever the total.
In this guide
- Which nine components make up the IT infrastructure of a dental office?
- Internet and failover: what standard should a dental office hold its connection to?
- Firewall: what should sit between the practice and the internet?
- Switching and cabling: what should the wired backbone look like?
- Wi-Fi: what belongs on wireless in a dental office, and what never should?
- Server or cloud host: what standard applies either way?
- Workstations: what standard should front-desk and operatory computers meet?
- Imaging and sensor PCs: why are they a separate component?
- Backup: what does a working backup mean for a dental practice?
- Phones and power: why do they belong on the infrastructure list?
- How often should each component be replaced? The replacement calendar
- What changes between a single office and a multi-site group?
- The 30-minute self-audit: score your infrastructure
- The IT side: who owns each component after the audit?
- What to ask your IT provider about your infrastructure
- What to verify before you sign an infrastructure quote
- How Legend Networking can help
- Frequently asked questions
- The bottom line
Which nine components make up the IT infrastructure of a dental office?
In a dental practice, IT infrastructure is everything the clinical and front-desk software runs on and through: the internet connection and its backup path, the firewall, switches and cabling, Wi-Fi, the server or cloud host, the computers at each chair and desk, the imaging and sensor computers, the backup system, and the phones and power protection.
Software is not on that list on purpose. Dentrix, Eaglesoft, Open Dental, Archy, DEXIS, Carestream and Planmeca Romexis are what the infrastructure carries; when any of them is slow or offline, one of the nine components below is usually the reason. The table is the whole standard on one screen. The sections after it say what each row means in an office.
| Component | What it includes | The standard to hold it to | Replace or review | Who usually owns it |
|---|---|---|---|---|
| 1. Internet and failover | Primary circuit, modem or ONT, a second path on a different carrier or medium | Two independent paths; automatic switchover tested on a quiet day; the practice knows what still works on the backup | Review the contract every 2 to 3 years; test failover twice a year | IT provider designs, ISP delivers |
| 2. Firewall | The business-class device between the modem and the network, with its security subscription | Current firmware, active subscription, remote access only through it, rules documented | 5 years, or at the maker's end-of-support date | IT provider |
| 3. Switching and cabling | Managed switches, PoE for phones and access points, the rack or cabinet, every cable run and jack | Managed and monitored switches; labeled, tested runs with a handover report; room to add drops | Switches 7 to 8 years; cabling lasts the tenancy if installed and documented properly | IT provider; low-voltage contractor for cabling |
| 4. Wi-Fi | Access points, controller or cloud management, separate networks for staff, patients and devices | Business access points, no consumer router; three separated networks; clinical computers on cable, not wireless | 5 to 6 years, or when the standard your devices need changes | IT provider |
| 5. Server or cloud host | The database server for the practice software and imaging, or the hosted service that replaces it, plus the local pieces a cloud setup still needs | Dedicated to its job, on a supported Windows Server version, on battery, monitored; or a hosted service with a written exit path | Server 5 years or at the OS end-of-support date, whichever comes first | IT provider |
| 6. Workstations | Front-desk, operatory, consult and private-office computers and their displays | Business-class, Windows 11 Pro, one account per person, encrypted drives, replaced on a schedule rather than when they die | 5 to 6 years, bought in a planned year, not all at once | IT provider; practice approves the schedule |
| 7. Imaging and sensor PCs | The computers that sensors, intraoral cameras, scanners, pans and CBCT units plug into, and the imaging server or share | Meet the imaging vendor's spec with headroom; updates held and tested; drivers documented; one owner for the sensor-to-software chain | Follow the imaging vendor's requirement, usually ahead of the office cycle | IT provider with the imaging vendor |
| 8. Backup | Copies of the practice database, imaging, documents and email, with the schedule, the off-site copy and the restore test | A restore tested on a date you can name; both the database and imaging covered; a written recovery time the owner has agreed to | Review quarterly; re-test the restore at least twice a year | IT provider; practice owns the restore-time decision |
| 9. Phones and power | The phone system and its internet dependency; UPS units on the server, network and sensor PCs; surge protection; what shuts down in an outage | Phones have a written outage path; the server and network ride the battery long enough to shut down cleanly; a list of what gets power first | UPS batteries on the maker's schedule; phone contract every 3 to 5 years | IT provider; phone carrier |
Two things to notice. First, half the rows are owned by the IT provider but decided by the practice: how long you can afford to be down, which year the computers are replaced, what the phones do in an outage. Second, nothing in the table is a brand. The standard is about behavior, which is why you can check it yourself.
Internet and failover: what standard should a dental office hold its connection to?
A dental office should hold its internet to a two-path standard: a primary circuit sized for the practice and a second connection on a different carrier or medium, with automatic switchover that has been tested on a quiet day. The practice should also know, in writing, which systems keep working on the backup path and which do not.
Open Dental's own requirements page puts the first half plainly: "For the best access to service and updates, you should be connected to a high speed internet connection. Consider this a requirement." If your practice software is cloud-hosted, the internet is no longer a convenience; it is the server room. Claims, eligibility checks, patient texting, phones and remote support all leave the building through the same pipe.
The standard, row by row:
- Two paths, not two cables. Two circuits from the same carrier on the same cable into the building are one path. Fiber plus cable, or cable plus a cellular router, are two.
- Automatic switchover. A firewall or router that moves traffic to the second path on its own. A phone hotspot someone finds in a drawer is not a failover plan.
- A tested result. Pull the primary on a quiet afternoon once or twice a year and watch what happens. Record the date.
- A written "what still works" list. Cloud software, phones and payment terminals usually do; a local server and sensors do not need the internet at all, which is worth knowing before anyone panics.
What to do in the first minutes of an outage, and how to judge the backup options, is covered in our guide to what to do when the dental office internet is down.
Firewall: what should sit between the practice and the internet?
A business-class firewall should sit between the modem and everything else, with current firmware, an active security subscription, rules that someone can print, and every remote connection into the office passing through it rather than around it. The practice should be able to name who manages it and when it was last updated.
The consumer router the internet company supplied is a modem with a Wi-Fi radio, not a firewall. The standard for the device that replaces it:
- Supported and subscribed. Firewalls have end-of-support dates like any other computer. A device the maker no longer updates fails the standard whatever it cost.
- One door for remote access. The software vendor, the imaging vendor, your IT provider and anyone working from home should come in through the firewall's remote-access method, with multi-factor sign-in. CISA's plain-language advice applies here: "Multifactor authentication (MFA) adds an extra layer of protection by requiring two or more ways to verify a user's identity." The agency adds that "Businesses should aim to use a phishing-resistant MFA method." Our guide to dental office remote access security covers the setups that pass.
- Written rules. Which ports are open and why, and which vendor asked for them. If nobody can answer, the audit score for this row is zero.
Firewall choice, segmentation and the rest of the perimeter are a topic of their own, covered in our guide to network security for dental practices. They belong with dental cybersecurity services rather than in an infrastructure standard, and this guide only asks whether the device exists, is supported, and is managed.
Switching and cabling: what should the wired backbone look like?
The wired backbone of a dental office should be managed switches that your IT provider can see into, with power over Ethernet for phones and access points, mounted in a rack or cabinet with the cabling labeled at both ends and tested at handover. Every operatory, the front desk, the pan room and the server should connect by cable.
Cabling is the component that outlives everything else, which is why it is worth doing to a standard once:
- Managed switches. An unmanaged switch cannot tell anyone which port is failing, which is why "the computer in op 4 drops out" takes three visits to fix. Managed switches report errors and let the provider separate phones, cameras and clinical traffic.
- PoE where the phones and access points are. It removes a power brick and an outlet from every ceiling and desk.
- Labels and a test report. Every run numbered at the jack and the patch panel, and a test report from the installer showing that every run passes. If you renovate or add operatories later, that report is what the next contractor works from.
- Headroom. Spare ports and spare runs to the operatories, because the next intraoral scanner, TV or camera will want one.
Drop counts per room, the cable category to specify, the closet build and the documents to collect at handover are the subject of our dental office network setup guide. For a build or renovation, that work is planned as network design and installation for dental offices before the drywall goes up.
Wi-Fi: what belongs on wireless in a dental office, and what never should?
Wi-Fi in a dental office should carry tablets, laptops, patient devices and the occasional scanner, on business-grade access points with at least three separated networks for staff, patients and devices. Chairside computers, the server, sensors and anything that writes to the practice database should be on cable, not wireless.
The standard is as much about what is kept off Wi-Fi as what is on it:
- No consumer router doing double duty. A business access point is managed, supports several networks, and is placed where the operatories are, not where the modem happened to land.
- Three networks minimum. Staff devices, patient guest access, and a devices network for TVs, cameras and anything that cannot run security software. A patient phone should never be able to see the server.
- Clinical computers on cable. A sensor capture that stalls because a microwave in the break room was running is not a story anyone wants to tell twice.
- Coverage mapped, not guessed. Operatories at the back and the sterilization area are where coverage usually fails.
If the Wi-Fi already drops and nobody can say why, our guide to why dental office Wi-Fi keeps dropping separates the Wi-Fi from the internet and the application before you call anyone.
Server or cloud host: what standard applies either way?
Whether the practice software runs on a server in the closet or in a vendor's cloud, the standard is the same: the system holding the database is dedicated to that job, runs on a supported operating system, sits on battery, is monitored, and has a written recovery plan and exit path. The cloud changes who does the work.
For a local server, Open Dental's requirements page says what every practice-software vendor says in some form: "We recommend having a dedicated server to protect data." Dedicated means the server is not also the front-desk computer, nobody browses on it, and the imaging share, the practice database and the backup agent are the only tenants. The same page adds that "An uninterruptible power supply (i.e., a backup battery) is optional but recommended. This can prevent loss of data on the server or workstation running MySQL/MariaDB."
The operating system is where the clock runs. Microsoft's lifecycle pages give the dates (shown there in Pacific time; written here as US dates):
| Server operating system | End of support | What it means for a dental server |
|---|---|---|
| Windows Server 2016 | 12 January 2027 (extended support ends; paid extended security updates listed after) | Replace or migrate before the date, not after |
| Windows Server 2019 | 9 January 2029 | Plan the replacement in 2027 or 2028 |
| Windows Server 2022 | Mainstream support ended 13 October 2026; extended support runs to 14 October 2031 | Still supported; buy with the 2031 date in mind |
Open Dental lists Windows Server 2016, 2019, 2022 and 2025 as supported today and records Windows 10 as suspended from 14 October 2025, which is a reminder that the vendor's list follows Microsoft's calendar.
A cloud-hosted practice does not escape the row; it changes it. The office still needs a local machine or share for imaging if the imaging stays local, still needs the internet standard above, and still needs a written answer to "how do we get our data out, in what format, and how long does it take." Whether to replace the box or move to the cloud is a decision in its own right, worked through in dental server replacement vs cloud migration, and if a server is already behaving badly, start with what to do when the dental server is down or see what dental server support covers day to day. The service side of dental servers and workstations is where the sizing and the install are handled.
Workstations: what standard should front-desk and operatory computers meet?
Every computer in a dental office should be a business-class machine on Windows 11 Pro, with a unique sign-in for each person, an encrypted drive, current updates, and a planned replacement year. The front desk, the operatory and the imaging room need different machines, but the standard of sign-in, encryption and replacement is the same for all.
Four points carry this row:
- Pro, not Home. Open Dental's requirements page notes that "Home editions of Windows are sometimes unacceptable because of connection and networking limits. The best editions are Pro, Business, or Ultimate." The reason is management: Pro machines can join a domain or a cloud identity, take encryption policy and accept remote administration.
- One person, one account. The HIPAA Security Rule's technical safeguards include "Unique user identification (Required). Assign a unique name and/or number for identifying and tracking user identity." A shared "FrontDesk" login is the opposite of a unique identifier, and it makes every audit log useless. Whether your current setup satisfies the rule is a question for your compliance adviser; this guide only quotes the safeguard.
- Encrypted drives. The rule lists "Encryption and decryption (Addressable)" as a technical safeguard; in practice, drive encryption on every laptop and desktop is the cheapest control there is, and it is the first thing a compliance adviser will ask about when a laptop goes missing.
- Replaced by plan. Windows 10 reached the end of support on 14 October 2025, and Windows 11 versions have their own end dates: version 24H2 ended on 13 October 2026, so a machine still on it is already out of support, and version 25H2 ends on 12 October 2027. A workstation standard includes who checks that the version is current.
Which machine suits which room, the specs that matter and the ones that are padding, and whether refurbished ever makes sense are all in which computers to buy for a dental office. What the practice-software vendors require of a workstation is in dental software system requirements.
Imaging and sensor PCs: why are they a separate component?
Imaging and sensor computers are a separate component because they obey the imaging vendor's calendar, not the office's: they must meet the sensor, camera, scanner or CBCT maker's specification with headroom, their updates and drivers are held and tested rather than applied automatically, and one party owns the chain from sensor to practice software.
What the standard asks:
- The vendor's spec, plus headroom. A sensor PC that just meets the requirement today will not meet it after the next imaging release. Buy above the line.
- A change rule. Windows updates, .NET updates and driver updates are the usual cause of "the sensor stopped working after the weekend." The standard is that updates on imaging machines are staged and tested, and that the practice knows the rollback path. Our guide to a dental sensor not working after a Windows update is the first-hour version of this row.
- Documented drivers and bridges. Which sensor, which driver version, which bridge to the practice software, on which machine. Written down, so the next technician is not starting from zero.
- One owner for the chain. Sensor maker, imaging software vendor, practice-software vendor and IT provider each own a link. The standard is that your IT provider owns the whole chain and calls the others.
- Storage for images. Two-dimensional images are small; CBCT volumes and intraoral scans are not. The imaging share needs a growth plan and a backup that covers it.
The sensor side, including what to check before buying one, is in our guide to dental X-ray sensors. A question owners ask often is what network and servers a fully digital imaging environment needs; the short answer is a wired network to every chair, an imaging share on a dedicated, supported server or host, and imaging workstations above the vendor's spec, all of which are the rows of this standard.
Backup: what does a working backup mean for a dental practice?
A working backup for a dental practice is one whose restore has been tested on a date the owner can name, that covers the practice database and the imaging files, keeps a copy off site, and comes with a written recovery time the owner agreed to. A nightly "success" report is not evidence until a restore has been run.
The federal rule is specific about the shape of the safeguard. Among the contingency-plan specifications in 45 CFR 164.308, the "Data backup plan (Required)" is to "Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information," and the "Disaster recovery plan (Required)" is to "Establish (and implement as needed) procedures to restore any loss of data." The rule also lists "Testing and revision procedures (Addressable). Implement procedures for periodic testing and revision of contingency plans." Those are the three questions of this row: are there copies, can they be restored, and when was that last tested.
The standard in practice:
- Both halves covered. The practice database is one file set; images, documents and email are others. A backup that covers the database but not the imaging share passes the vendor's checklist and fails the practice.
- Three copies, two media, one off site. The 3-2-1 pattern, which our dental data backup guide walks through, with what to back up and how to read the monthly report.
- A dated restore test. At least twice a year, a real file and a real database copy restored to a test location, with the time it took written down.
- A recovery-time decision the owner made. How many hours of closure the practice can carry decides how much the backup design costs. That is a business decision, and the standard is that someone asked. The written version of that decision is a dental disaster recovery plan.
Phones and power: why do they belong on the infrastructure list?
Phones and power belong on the infrastructure list because they fail on the same mornings the rest of it does, and nobody has planned for them. The standard is a phone system with a written outage path, battery units on the server, network core and sensor computers sized for a clean shutdown, and a list of what gets power first.
Phones. Where the phone system runs over the internet, as current dental phone systems do, the two-path internet standard above is also the phone standard. The written outage path says where calls go when the office is dark: to mobiles, to an answering service, to a recorded message that tells patients how to reach the on-call dentist. If the office still has copper lines for the alarm, the fax or the elevator, those are ending too; see replacing POTS lines in a dental office. Choosing the system itself is a separate decision, covered under dental phone systems.
Power. A battery unit is not there to keep working through an outage; it is there to keep the server, the firewall and the switches up long enough to shut down cleanly or ride through a flicker, and to keep the sensor computer from losing a capture mid-exposure. The standard:
- UPS on the server, the network core and every imaging computer; a smaller unit on the front desk if payments must finish.
- The server told to shut itself down when the battery reaches a set level, and that behavior tested.
- Batteries replaced on the manufacturer's schedule, with the replacement date on the maintenance calendar; most units report battery health, and the standard is that someone reads it.
- Surge protection between the wall and anything with a hard drive, including the pan and CBCT unit's computer.
- A written list of what gets power first if a generator or a limited circuit is all there is.
Which systems can simply be switched off in an outage, and in what order, is a conversation to have in daylight. Our guide to restarting versus power-cycling dental office equipment covers the morning after.
How often should each component be replaced? The replacement calendar
Replace dental practice infrastructure on a calendar rather than on failure: workstations every five to six years in a planned year, the server at five years or its operating system's end-of-support date, switches at seven to eight years, Wi-Fi and firewalls at five to six or the maker's end-of-support, UPS batteries on the maker's schedule. Documented cabling lasts the tenancy.
The years are a working standard for a practice that wants predictable spending; the end-of-support dates are not negotiable, because an unsupported system stops receiving security fixes. The dates that have just passed or force decisions in the next three years:
| Date (US) | What ends | Affects | Source |
|---|---|---|---|
| 14 October 2025 (passed) | Windows 10 Home and Pro support | Any workstation or sensor PC still on Windows 10 is already out of support | Microsoft Lifecycle; Open Dental requirements page |
| 13 October 2026 (passed) | Windows 11 version 24H2 (Home and Pro) | Workstations still on 24H2 are out of support; move them to 25H2 or newer | Microsoft Lifecycle |
| 13 October 2026 (passed) | Windows Server 2022 mainstream support (extended runs to 14 October 2031) | Servers bought 2021 to 2024; still in extended support, plan the next cycle | Microsoft Lifecycle |
| 12 January 2027 | Windows Server 2016 extended support | Servers bought 2016 to 2019; replace or migrate before this date | Microsoft Lifecycle |
| 12 October 2027 | Windows 11 version 25H2 | Workstations that stall on this version | Microsoft Lifecycle |
| 9 January 2029 | Windows Server 2019 extended support | Servers bought 2019 to 2021; plan replacement in 2027 or 2028 | Microsoft Lifecycle |
The two posts that work through the biggest of these are Windows Server 2016 end of support for a dental office and Windows 10 end of life for dental practices.
Three habits make the calendar work:
- Stagger the workstations. Replacing a third of the computers every two years spreads the cost and means the office never has a single year where everything is old at once.
- Buy the server in the right year. A server bought in the last year of an operating system's mainstream support carries the clock with it. Ask which version it ships with and what date that version ends.
- Keep an inventory with dates. Make, model, purchase date, operating system version, support end, replacement year, owner. One page. The self-audit below is easier with it and impossible without it.
What changes between a single office and a multi-site group?
A second location changes the infrastructure standard in five places: identity (one directory for every person across all offices), the network (the same design and firewall rules at each site, joined by a secure link), the data (per-office or shared databases, decided on purpose), remote support (one console for every site), and a written build template.
| Component | One office | Two or more offices |
|---|---|---|
| Identity and sign-in | Local accounts or a small domain on the server | One directory for all staff, with multi-factor sign-in, so a hygienist who covers both offices has one account and leaving staff are removed once |
| Internet and firewall | Two paths and one managed firewall | The same firewall model and rule set at every site, with a secure site-to-site link where the practice software or imaging must cross |
| Server or host | One server or one cloud tenant | A choice made in writing: one database per office, a regional database, or one shared database; and whether imaging stays local at each site |
| Workstations and imaging | A standard build | The same standard build, imaged from a template, so a new office opens on the group's standard rather than inheriting the seller's |
| Backup | One schedule and one restore test | One policy, one dashboard, a restore test per site on the calendar |
| Monitoring and support | The provider sees one office | The provider sees every office from one console, and the group gets one report |
| Phones | One system | One system with site-aware routing and a shared outage path |
The step from one to two is where most practices discover that their first office was never documented. The standard for a group is written before the second lease is signed, and every acquired office is measured against it rather than kept as it was. The IT part of taking over an existing office is worked through in dental practice acquisition IT due diligence and, after closing, in folding an acquired dental office into your IT standard; the service side for groups is DSO IT support. Searches for scalable infrastructure providers for dental groups usually mean this: a provider that can hold the same standard at office eight as at office one, and show it on one screen.
The 30-minute self-audit: score your infrastructure
Score each component from zero to two. Zero means the practice cannot answer or the standard is clearly not met; one means partly met or undocumented; two means met and written down. Nine rows, a maximum of eighteen. The low rows, more than the total, tell you where the next conversation with your IT provider starts.
| Component | Score 0 | Score 1 | Score 2 |
|---|---|---|---|
| 1. Internet and failover | One connection; no failover | A second connection exists but switchover is manual or untested | Two independent paths, automatic switchover tested in the last year, "what still works" list written |
| 2. Firewall | ISP router only, or nobody knows who manages it | Business firewall, but subscription or firmware status unknown | Supported, subscribed, rules documented, all remote access through it with multi-factor sign-in |
| 3. Switching and cabling | Unmanaged switches; unlabeled cables; no test report | Managed switches but no labels or report | Managed and monitored switches, labeled runs, handover report on file, spare ports |
| 4. Wi-Fi | Consumer router; one network for everyone; clinical PCs on Wi-Fi | Business access points but patients and staff share a network | Three or more separated networks, clinical computers on cable, coverage mapped |
| 5. Server or host | Server doubles as a workstation, or OS past end of support, or exit path from the cloud vendor unknown | Dedicated and supported, but no UPS or no monitoring | Dedicated, supported, on battery, monitored, recovery plan and exit path written |
| 6. Workstations | Shared logins; Windows Home or unsupported Windows; no replacement plan | Pro and supported but unencrypted or no replacement year | Business-class, Windows 11 Pro current version, one account per person, encrypted, replacement year set |
| 7. Imaging and sensor PCs | Below vendor spec or updates uncontrolled; nobody owns the chain | Meets spec; updates uncontrolled; drivers undocumented | Above spec, updates staged and tested, drivers and bridges documented, one owner for the chain |
| 8. Backup | No restore ever tested, or imaging not covered | Database and imaging covered but restore not tested in a year | Both covered, off-site copy, restore tested twice a year with dates, recovery time agreed by the owner |
| 9. Phones and power | No UPS on server or sensor PCs; no phone outage path | UPS present but batteries untested or shutdown not configured | UPS on server, network core and imaging PCs with tested shutdown, batteries on schedule, phone outage path written |
Reading the total:
- 15 to 18. The infrastructure meets the standard. The work is keeping the calendar and re-testing failover and restores.
- 10 to 14. Sound bones with gaps, usually in documentation, restore testing and power. Fix the zero rows first, in this order: backup, server, firewall.
- 6 to 9. The office is running on luck. Ask for a written plan that brings every zero row to at least one within ninety days, and put the server and backup rows first.
- Below 6. Treat the next quote as a rebuild, not a refresh, and insist on the inventory and the handover documents this guide describes.
Any row scored zero on backup, server or firewall outranks every other row, whatever the total.
The IT side: who owns each component after the audit?
After the audit, each component needs a named owner. In a practice of one to three locations that owner is almost always the IT provider, with the practice owning the decisions money depends on: recovery time, replacement year, what the phones do in an outage. Carriers, cabling contractors and software vendors own their own links only.
| Component | IT provider | Practice owner | Others |
|---|---|---|---|
| Internet and failover | Designs the two paths, configures switchover, tests it | Signs the circuit contracts; decides what must keep working | Carriers deliver and repair their circuit |
| Firewall | Owns, updates, documents, monitors | Approves who gets remote access | Vendors request access; they do not get their own door |
| Switching and cabling | Specifies, configures, monitors | Approves the build or renovation scope | Low-voltage contractor installs and tests the runs |
| Wi-Fi | Designs, places, manages | Decides whether patients get guest access | — |
| Server or host | Builds, patches, monitors, plans the replacement | Decides local versus cloud and the recovery time | Practice-software vendor supports the application, not the box |
| Workstations | Images, manages, replaces on the plan | Approves the replacement year and the budget | — |
| Imaging and sensor PCs | Owns the chain; stages updates; calls the vendors | Reports faults early; approves imaging purchases with IT in the room | Imaging vendors own their software and hardware |
| Backup | Runs it, tests restores, reports monthly | Agrees the recovery time; reads the report | Cloud vendors back up their platform, not your local files |
| Phones and power | Specifies UPS, configures shutdown, sets the phone failover | Decides the outage path and the power priority list | Phone carrier; electrician for circuits |
This is also where the buying decision sits. If the audit shows that nobody owns rows five, seven and eight, the practice does not need a quote for hardware; it needs a provider who will take ownership of the standard. That is what managed IT services for dental practices are for: the monitoring, patching, backup testing and replacement planning in the table above, done on a schedule rather than when something fails. What a dental-specific provider should take responsibility for is set out on our dental IT support page; if you are comparing providers, start with our review of the best dental IT companies and the questions below.
Two rows deserve a last word. Our legacy guide to dental IT network design and implementation covers what a secure dental IT infrastructure looks like at the design stage, before any equipment is bought. And the Security Rule's physical safeguards include "Disposal (Required)" and "Media re-use (Required)" for hardware that held patient data, so the replacement calendar needs a line for how old drives leave the building, which your IT provider should be able to describe.
What to ask your IT provider about your infrastructure
Take the audit to the meeting and ask these. The answers you want are documents and dates, not adjectives.
The inventory and the calendar
- Can we have a one-page inventory of every component with make, model, purchase date, operating system version, support end date and planned replacement year?
- Which of our systems hit an end-of-support date before the end of 2028, and what happens to each?
- Which workstations are still on Windows 10 or on a Windows 11 version that has ended, and when do they move?
Failover, power and restore evidence
- When did we last test internet failover, and what kept working?
- When was the last restore test, what was restored, and how long did it take?
- Which machines are on battery, and is the server configured to shut itself down when the battery runs low?
Ownership and access
- Who owns the sensor-to-software chain when an image will not capture, and who calls the imaging vendor?
- How many remote-access doors into our network exist today, and does each one use multi-factor sign-in?
- Does every staff member have their own login on every machine, and how are accounts removed when someone leaves?
The next office
- If we open or buy a second location, what is the written standard it will be built to?
- Could you show us every site from one console, and send one monthly report for the group?
What to verify before you sign an infrastructure quote
An infrastructure quote is a list of parts until you make it a list of outcomes. Before signing, verify these nine things, in writing:
- The quote maps to the components. Every line should belong to one of the nine rows above. A line you cannot place is a question, not a purchase.
- Support dates are stated. For the server and any firewall or switch, the operating system or firmware version and the date its support ends.
- Pro editions and encryption are included. For workstations: Windows 11 Pro, drive encryption, and a unique account per person, named in the scope.
- The imaging vendor's spec is referenced. For sensor and imaging computers, the quote should say which vendor requirement it meets and by how much.
- Cabling comes with a report. Labelling at both ends and a cable test report at handover are in the scope, not an extra.
- Failover is configured and tested. The second internet path, the switchover and a test date are in the deliverables.
- Backup includes a restore test. The first restore test, and the twice-yearly cadence after it, are in the plan, with the recovery time written down.
- Power is specified. Which machines get a UPS, and that shutdown behavior is configured and tested.
- Old equipment has an exit. How drives that held patient data are wiped or destroyed, and what record you receive.
Then ask for the two documents the quote should produce when the work is done: the inventory and the handover report. If the provider cannot say what those will contain, the quote is not finished.
How Legend Networking can help
Legend Networking is a Dallas-based dental IT company with 22+ years in dental IT. It has served over 3,500 practices since 2004 and supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, which is where most of the nine components meet the clinic. The work is done by in-house engineers; no outsourced first-level triage, with 24/7 monitoring of the systems the standard above describes, and onsite dispatch by appointment across served dental markets; remote-first nationwide.
The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For what a planned refresh of an established practice looks like in practice, see a technology upgrade covering computers, server infrastructure, networking, applications, software and security; for an office near you, find dental IT support in your city.
Frequently asked questions
What does the IT infrastructure of a dental practice consist of?
A dental practice needs nine infrastructure components: an internet connection with a tested failover path, a business-class firewall, managed switches with labeled cabling, business Wi-Fi with separated networks, a dedicated server or cloud host on a supported operating system, business-class workstations with individual logins, imaging computers that exceed the vendor's spec, tested backup, and phones with power protection on the server, network and sensor computers.
How much IT infrastructure does a small dental office really need?
A single-doctor office needs all nine components, just at smaller scale: one firewall, one or two managed switches, two or three access points, one server or a cloud host plus a local imaging share, a computer per operatory and desk, one or two imaging PCs, backup covering the database and images, and battery units on the server and sensor computers. Size changes the count, not the list.
If the practice software is cloud-hosted, does the office still need a server?
Often a smaller one, or a dedicated imaging computer, rather than none. Cloud practice software removes the database server, but sensors, cameras and CBCT units usually still write to a local machine or share, and that machine needs the same standard: dedicated, supported, on battery, backed up. The internet connection then becomes production infrastructure and needs the two-path failover standard.
What is a sensible replacement cycle for dental office IT equipment?
Hold a calendar rather than waiting for failure: workstations every five to six years in a staggered plan, the server at five years or at its operating system's end-of-support date, switches at seven to eight years, firewalls and Wi-Fi at five to six years or the maker's end-of-support, UPS batteries on the manufacturer's schedule. Cabling installed and documented to a standard lasts the tenancy.
Which Microsoft end-of-support dates matter for a dental practice in 2027 and 2028?
Windows 10 support ended on 14 October 2025 and Windows 11 version 24H2 on 13 October 2026; version 25H2 ends on 12 October 2027. Windows Server 2022 left mainstream support on 13 October 2026 but stays in extended support to 14 October 2031. Windows Server 2016 extended support ends on 12 January 2027, and Windows Server 2019 on 9 January 2029, per Microsoft's lifecycle pages.
Can a dental office run on Wi-Fi instead of network cabling?
Tablets, laptops and patient devices can; the computers that run the practice software, the server, the imaging computers and anything a sensor plugs into should be on cable. Wireless adds dropouts and interference that show up as stalled captures and frozen charts. The standard is business access points with at least three separated networks, and a wired drop at every chair and desk.
What is a secure dental IT infrastructure?
A secure dental IT infrastructure is one where all nine components are supported, managed and documented: a firewall that every remote connection passes through with multi-factor sign-in, separated networks so patient devices cannot reach the server, one account per person on encrypted workstations, staged updates on imaging computers, and a backup whose restore has been tested. Security is a property of the whole standard.
What should an IT infrastructure audit of a dental practice cover?
An audit should score all nine components against a written standard: whether internet failover exists and has been tested, the firewall is supported and managed, switches are managed and cabling documented, Wi-Fi is separated, the server is dedicated and supported, workstations have individual encrypted logins, imaging PCs exceed the vendor's spec, a restore has been tested, and power and phones have an outage plan.
What changes in IT infrastructure when a dental practice opens a second location?
Five things: one directory for every staff member across both offices with multi-factor sign-in; the same firewall model and rules at each site with a secure link between them; a written decision on per-office versus shared databases and where imaging lives; one backup policy with a restore test per site; and one monitoring console so the provider and the owner see both offices at once.
Who looks after each part of a dental office's IT infrastructure?
In a practice of one to three locations the IT provider owns the components day to day: firewall, switches, Wi-Fi, server, workstations, imaging computers, backup and power. The practice owns the decisions behind them: how long it can afford to be down, which year equipment is replaced, what the phones do in an outage. Carriers, cabling contractors and software vendors own their own link and nothing beyond it.
The bottom line
If three or more rows came back at zero, you do not need another parts list; you need someone to take ownership of the standard. Bring your nine scores to a conversation with our dental IT support team, or ask for a Free Dental IT Assessment: a review of your computers, software, network security, backups and performance, with written findings and prioritized recommendations, so the next quote you sign covers the gaps the audit found and nothing else.

