Periodontal Practice Technology Guide: The IT Checklist for CBCT, Implant Planning, Charting and Referrals
It is a surgical morning. The first implant case is at eight, and the planning PC in the consult room is still grinding through the CBCT study it was asked to open five minutes ago. A general dentist's office calls the front desk asking for "the scan" on a patient they referred last week, and someone starts looking for a USB stick. In operatory two, the hygienist's headset drops out halfway through a six-point perio exam. None of this is clinical. All of it is periodontal practice technology, and all of it lands on the owner or the office manager.
This guide is the IT side of running a perio office, written for the person who signs the invoices. It gives you a comparison with a general practice, a map of what you run and who to call, a network layout, a backup list with a restore test, an upgrade calendar, a 15-question scorecard for any IT provider, and a 24-row checklist you can fill in this week. If you are comparing providers, our page on dental IT support explains how Legend Networking works with dental offices. A 2025 survey of US board-certified periodontists in the Journal of Periodontology found "a majority utilizing cone beam computed tomography (CBCT) scanners and implant planning software", so the systems below are the normal stack, not the exception.
A periodontal practice needs everything a general dental office runs (practice software, imaging, network, backup, security, phones) plus five things a general office rarely has: CBCT studies that are far too large to email, an implant-planning workstation with a dedicated graphics card, voice or electronic perio charting, image exchange with referring dentists, and surgical-day uptime.
- A periodontal practice runs everything a general dental office does plus CBCT imaging, an implant-planning workstation with a dedicated graphics card, voice or electronic perio charting, image exchange with referring dentists and surgical days that cannot slip.
- Vendor minimums differ: Blue Sky Plan lists Windows only, 16 GB RAM and a dedicated card with at least 3 GB video RAM; coDiagnostiX lists OpenGL 3.3, 8 GB RAM and, for a network licence, a separate Windows dongle-server PC (both checked October 2026).
- Estimate CBCT growth with studies per week × MB per study × 52, and upload time with MB × 8 ÷ upload Mbps, using your own numbers.
- Backups often miss CBCT folders on the acquisition PC, planning projects, the photo folder and any separate charting database; restore one study, one plan and one chart each quarter.
- As of 26 October 2026, Windows 10 Home and Pro and SQL Server 2016 are past end of support, and Windows Server 2016 extended support ends January 12, 2027.
In this guide
- What technology does a periodontal practice need that a general dental office doesn't?
- What does a periodontal practice run? The technology map
- What does the implant-planning workstation need?
- How should a periodontal office's network be laid out?
- Which devices move data, and where does it go?
- How much does CBCT add to storage and the internet line? A worked example
- Imaging, surgical records and backup: what does your backup probably miss?
- Running more than one location
- Periodontal maintenance recall and patient texting: IT's part
- The upgrade calendar for a periodontal office
- Security for a periodontal practice
- Periodontal practices Legend has worked with
- What should a periodontal practice ask an IT provider? The 15-question scorecard
- What does IT cost for a periodontal practice?
- Frequently asked questions
- The bottom line
What technology does a periodontal practice need that a general dental office doesn't?
A periodontal practice runs the same base as a general office, then adds CBCT imaging, implant-planning software, six-point charting by voice or electronic probe, two-way image exchange with referring dentists and surgical blocks that cannot slip. Each addition changes what the PCs, network, backup and phone setup must do, as the table below shows row by row.
The comparison below is the place to start when you brief a new IT provider or check your current one. Read the right-hand column as a to-do list. For how Legend supports perio offices day to day, see our periodontal IT support page.
| Area | General practice | Periodontal practice | What IT has to do differently |
|---|---|---|---|
| Schedule | Hygiene-heavy days, short appointments | Surgical blocks plus periodontal maintenance | Plan maintenance windows away from surgical days; downtime on a surgical morning cancels the longest, highest-value appointments |
| Imaging | 2D sensors and a panoramic unit | CBCT on many implant cases, planning software, intraoral scans (STL files) | Storage that grows with every study, a graphics card on the planning PC, CBCT folders inside the backup |
| Charting | Tooth chart, typed notes | Six-point probing by voice or electronic probe | Headsets, USB drivers, quiet audio paths and a PC that does not lose the device after an update |
| Where patients come from | Mostly the practice's own patients | Referrals from general dentists | A secure way to receive and send images in both directions, with a record of what was sent |
| Documentation | Notes and X-rays | Surgical photos, implant and graft lot numbers, procedure notes | Templates in the practice software, a photo import folder, and both inside the backup |
| Recall | Six-month hygiene recall | Periodontal maintenance recall, often more frequent than a 6-month hygiene recall; the doctor sets the interval | More reminder traffic, a texting tool connected to the practice software, a signed agreement with the texting vendor |
One row is missing on purpose. Billing in a perio office often mixes dental and medical codes, which is a practice-software question more than an IT one; if you are weighing perio-specific software, start with our review of top-rated dental practice management software.
What the table means in practice: a general office can often run for years on one server, a handful of PCs and a consumer-grade backup. A periodontal office that tries the same thing usually finds the gaps on a surgical day, when the planning PC, the CBCT study and the referral all have to work at once.
What does a periodontal practice run? The technology map
The technology map lists each layer a periodontal office runs, the products you are likely to see, where each one lives, what IT is responsible for and who to call first when it fails. Fill in your own product names and you have the one-page document every new hire, vendor and IT provider should see.
A note on wording. Legend 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. Every other product named below is a system your practice may run: the vendor supports the application, and the computers, network, server, backups and accounts around it are IT's job.
| Layer | Products you may see | Where it usually lives | What IT has to do | Who to call first |
|---|---|---|---|---|
| Practice software | Dentrix, Eaglesoft, Open Dental, Archy; perio-specific systems you may run such as DSN Perio, PerioVision, CareStack or Denticon | Local server, or the vendor's cloud | Server health, database backup, user accounts, updates on an agreed schedule | Vendor for an error inside the software; IT for login, speed, server or network problems |
| 2D and CBCT imaging | DEXIS, Vatech, Carestream imaging (CS Imaging / CS 3D Imaging), Planmeca/Romexis | Acquisition PC by the unit, imaging server, viewer on each operatory PC | Storage growth, network speed between rooms, backup of the image store and the acquisition PC | Imaging vendor for the unit and its software; IT for the PCs, server, storage and network |
| Implant planning | Systems you may run such as Blue Sky Plan, coDiagnostiX, DTX Studio Implant or 3Shape Implant Studio | A dedicated workstation, sometimes a licence dongle or dongle server | Graphics card and RAM to the vendor's minimum, licence location, project files in the backup | Planning vendor for the software and licence; IT for the workstation, dongle-server PC and network |
| Perio charting | Built-in charting in your practice software; voice tools you may run such as Dentrix Voice or Denticon AI Voice Perio; Florida Probe | Operatory PCs, USB devices, sometimes a separate database | Device drivers, headset and microphone setup, Wi-Fi where devices move, database backup | Charting vendor for the application; IT for the PC, drivers and network |
| Intraoral scanners | Scanner software and its cloud | Scanner cart or laptop, vendor cloud | Wi-Fi or wired connection, Windows updates the vendor has approved, local cache in the backup | Scanner vendor first; IT for network and PC |
| Referral exchange | Portals, cloud shares, secure email | Vendor cloud or Microsoft 365 / Google Workspace | Accounts, sharing settings, a business associate agreement (BAA) on file, link expiry | IT, then the platform vendor |
| Phones and texting | Phone system, recall and texting tools | Cloud phone provider, texting vendor | Integration with the practice software, number ownership, network quality for calls | Phone or texting vendor; IT for the network |
| Backup and security | Backup software, firewall, endpoint protection, email security | On site and offsite | Monitoring, restore tests, patches, multi-factor sign-in | IT |
The last column matters more than it looks. When the CBCT export fails, the front desk needs to know whether to call the imaging vendor or IT without a debate. If the answer differs by system, write it on this table and tape it inside the server closet. For more on where the line falls, see dental software support versus IT support.
Want this map filled in for your office? That's where a Free Dental IT Assessment starts: written findings and prioritized recommendations on your computers, software, network security, backups and performance.
What does the implant-planning workstation need?
An implant-planning workstation needs a dedicated graphics card, more memory than a front-desk PC and a licence that keeps working when the network or internet blinks. The two planners below show how far apart vendor minimums are; the full side-by-side lives in our guide to implant planning software computer requirements.
Blue Sky Plan (Blue Sky Bio, checked October 2026) lists Windows 10 or 11 64-bit only, with macOS not supported; at least 16 GB of RAM; and a "dedicated NVidia or AMD card, at least 3 GB video RAM", on its download page. If a doctor plans on a Mac, that line decides the hardware conversation.
coDiagnostiX (checked October 2026) lists OpenGL 3.3 or higher, a minimum of 8 GB of RAM and at least 10 GB of free disk space before each start on its support page. Its network licence needs an "additional computer with a free USB slot running Microsoft Windows which acts as a dongle server", plus a permanent network connection to it while the software runs. The vendor also sells dongle-free subscription plans, which its plans page says are "Available in selected countries only"; those need a stable internet connection instead.
What to do with this: before you buy or replace a planning PC, put the vendor's current requirements page next to the quote from whoever builds it, and check three things: the graphics card's video memory, where the licence lives, and whether the planning projects folder is in the backup. Our workstation and server page describes the hardware side. Mac options and what a dongle server is in detail are covered in the spoke linked above.
How should a periodontal office's network be laid out?
A periodontal office's network should be split into zones so that clinical systems, the front desk, phones, building devices, guest Wi-Fi and vendor remote access cannot reach each other more than they need to. The CBCT acquisition PC, imaging server, planning workstation and any dongle server belong together in the clinical zone.
This is recommended practice, not a regulation. Most offices build it with VLANs (virtual networks on the same switches) and firewall rules between them. The zone table below is what to ask for.
| Zone | What sits in it | What it may reach | Notes for a perio office |
|---|---|---|---|
| Clinical | Practice software server, imaging server, CBCT acquisition PC, planning workstation, dongle server, operatory PCs | Its own devices; the internet only where a vendor needs it | Keep the planning PC and dongle server here; a licence that crosses zones breaks when rules change |
| Front desk | Check-in PCs, printers, card terminal | The practice software; the internet | Card terminals often need their own rules from the payment provider |
| Phones | Desk phones, phone adapters | The phone provider's servers | Separate so calls stay clear while large CBCT files move |
| Building and devices | Cameras, door entry, thermostats, TVs | Their own cloud services only | These are the devices that rarely get updates |
| Guest Wi-Fi | Patients' phones and laptops | The internet only | Never on the same network as the clinical zone |
| Vendor remote access | Imaging, planning and software vendors' support tools | Named PCs, for a set time | Switched on for a session, then off; logged |
Floor check, room by room
- Front desk: a wired drop for every PC and the card terminal; printers on the front-desk zone
- Operatories: a wired drop per chair for imaging; Wi-Fi coverage wherever headsets, tablets or scanners move
- CBCT room: the data drop and power the CBCT maker's site-preparation sheet asks for, agreed with the contractor before walls close
- Consult or planning room: a wired drop for the planning workstation, not Wi-Fi
- Surgical suite: nothing the surgeon needs mid-case depends on guest or shared Wi-Fi
- Server or network closet: battery backup (UPS), cooling and a door that locks
If you are building a new office, read our guide to dental IT network design and implementation and our guide to dental startup IT setup for new practices. For an existing office, our dental office network design page explains the work involved in re-zoning.
Which devices move data, and where does it go?
In a periodontal office, five kinds of device create files that have to travel: the CBCT unit, intraoral scanners, surgical cameras, electronic probes and voice-charting headsets. For each one, know the file it creates, where that file should land and who fixes it when it does not arrive.
| Device | What it creates | Where it should go | What usually breaks |
|---|---|---|---|
| CBCT unit | A DICOM study (often hundreds of files per scan) | Acquisition PC, then imaging server, then planning PC and, when needed, the referring dentist | Studies left only on the acquisition PC; slow copies across a busy network |
| Intraoral scanner | STL or similar scan files | Scanner software or its cloud, then the lab or planning software | Wi-Fi drops; Windows updates the scanner vendor has not approved |
| Surgical camera | Photos (JPEG or RAW) | An import folder, then the practice software's image module | Photos sitting on a memory card or a single PC, outside the backup |
| Electronic probe | Six-point readings | The charting software's database | Driver or COM-port conflicts after updates; two programs reaching for the same probe |
| Voice-charting headset | Spoken readings turned into chart entries | The practice software's perio chart | Microphone selection, Bluetooth range, room noise |
A note from a vendor document. An electronic probe connected over USB can appear to Windows as a virtual serial (COM) port, and one practice-software vendor's Florida Probe integration guide warns that when the probe is used as a device inside another program, no FP32 (Florida Probe) application may be open at the same time. If a probe "stops working" after someone opened two programs, that is usually why.
The detail for each device is in its own guide: voice perio charting setup for headsets and probes, how to send a CBCT scan to a referring dentist for studies going out, and intraoral scanner IT requirements for scanner upload and Wi-Fi.
How much does CBCT add to storage and the internet line? A worked example
CBCT adds storage every week and adds minutes to every study you send. You can estimate both with two formulas: studies per week × size per study × 52 for yearly storage, and size in megabytes × 8 ÷ upload speed in megabits per second for seconds per upload. Use your own numbers.
Start with the size of one study. Here is a calculated example, not a measurement: an 8 × 8 × 8 cm volume at a 0.2 mm voxel is 400 × 400 × 400 voxels, or 64 million voxels. At 2 bytes per voxel that is 128 million bytes, about 128 MB uncompressed. Real exports differ, because of field of view, voxel size, file format and whether a viewer is bundled. One CBCT maker's export size table (Vatech America, undated) lists its exports from 260 MB to 1,100 MB depending on field of view and whether the 3D viewer is included.
| Step | Formula | Example (hypothetical inputs) |
|---|---|---|
| Size per study | Your imaging software's export size, or the arithmetic above | 128 MB (calculated, uncompressed) |
| New storage per year | Studies per week × MB per study × 52 | 10 × 128 × 52 = 66,560 MB, about 67 GB |
| Backup copies | New storage × number of backup copies | 67 GB × 2 copies = about 134 GB more backup each year |
| Seconds to upload one study | MB × 8 ÷ upload Mbps | 128 × 8 ÷ 20 = about 51 seconds at a hypothetical 20 Mbps, at full line speed |
Two things to act on. First, run the yearly line with your real study count and your imaging vendor's real export size, then compare it with the free space on the imaging server and the backup target. Second, check the upload speed on your internet contract, not the download speed: a 20 Mbps upload is a hypothetical input here, and the same study takes longer when the phones, the cloud backup and everyone else are using the line. If one internet line is all you have, read what to do when the dental office internet goes down.
Where CBCT scans are saved and how to store them is covered in endodontic operatory imaging setup; file sizes by channel and the sending options are in the CBCT referral guide.
Imaging, surgical records and backup: what does your backup probably miss?
A periodontal office's backup usually covers the practice software database and the imaging server, then misses the files that live on single PCs: CBCT folders on the acquisition PC, planning projects and guide files, the photo import folder, a charting database and the dongle-server setup. Check each item below, then prove it with a restore test.
Is it in the backup?
- Practice software database
- Imaging server database and image store
- CBCT study folders on the acquisition PC (often stored locally first)
- Implant-planning projects and surgical guide files (STL) on the planning workstation
- Intraoral scanner software's local cache or export folder
- Surgical photo import folder
- Perio-charting database, if your charting tool keeps its own
- Dongle-server PC settings and licence details
- Implant and graft lot-number records (where your templates store them)
- Laser and procedure documentation saved outside the practice software
Why the charting line is there: Florida Probe's own FAQ page says FP32 Version 9 added "SQL database management", and it lists Windows Server 2016 or above with .NET Framework 3.5 for the server. A separate database is a separate backup item, and nobody notices it is missing until the PC fails.
How long to keep these records is set by your state; check with your dental board rather than a vendor's default retention setting.
A quarterly restore test that takes about one appointment slot
- Pick one CBCT study, one planning project and one perio chart from last month.
- Restore all three from the backup to a spare PC, not the original.
- Open each one in its own software: the study in the imaging viewer, the project in the planner, the chart in the practice software.
- Time it from "start restore" to "file open".
- Write the date, the time taken and anything that failed on one line, and keep the log.
If any of the three fails to open, you have learned it on a quiet afternoon instead of a surgical morning. For the full method, use the dental backup and disaster recovery checklist. Legend's backup and recovery service lists backup protection from $39.99 per month (storage-dependent), which is the backup add-on rather than a plan price.
Running more than one location
A second periodontal location raises four decisions: how both offices reach one practice-software database, how the office without a CBCT views studies, how the planning licence works across sites, and where referrals arrive. Decide each one on paper before the second lease is signed.
| Decision | Options to compare | Ask before you choose |
|---|---|---|
| Shared practice-software database | A server at one office with a site-to-site VPN, or a cloud edition of your software | What happens at the second office when the first office's internet is down? |
| CBCT at one site only | View studies over the network from the imaging server, or a cloud imaging tier | How long does one study take to open at the far site, measured, not estimated? |
| Planning licence across sites | A network licence with a dongle server, or a per-seat internet licence where the vendor offers it | Where is the dongle server, and does the far site depend on the VPN to plan? |
| Referral intake | One shared intake address and portal, or one per office | Who checks it at each site, and how are studies matched to the right chart? |
Groups with several offices have extra questions about standards, reporting and shared accounts; our page on DSO and multi-location IT support covers those.
Periodontal maintenance recall and patient texting: IT's part
Periodontal maintenance recall depends on reminders that reach the right patient at the right interval, and most offices now send them by text. IT's part is the plumbing: the link to your practice software, the agreement with the texting vendor before patient data flows, business-texting registration and keeping control of your number.
What does dental recall software need from IT?
Dental recall software needs four things from IT: a working connection to your practice software, a signed agreement with the vendor before any patient data is shared, a texting number registered for business messaging, and clear ownership of that number. Patient reactivation campaigns use the same plumbing, so set it up once.
Recall and texting setup in five steps
- 1Choose the connectionAsk whether the tool only reads appointments from your practice software or also writes confirmations back, and who installs and updates the connector.
- 2Sign the BAA firstPut a business associate agreement in place with the messaging vendor before patient data flows; ask your compliance adviser what your agreement must cover.
- 3Register for business textingAsk the vendor whether your texting number is registered for application-to-person messaging (A2P 10DLC) and who completed the registration.
- 4Keep reminder text genericDate, time, office name and a phone number; leave treatment details out of the message.
- 5Own your numberGet in writing who owns the texting number and how it moves if you change vendors.
On the registration step: one large messaging platform, Twilio, states in its A2P 10DLC documentation that "Anyone sending SMS/MMS messages over a 10DLC number from an application to the US must register for A2P 10DLC." Twilio's shutdown notice shows what happens without it: messages to US phone numbers from unregistered 10DLC numbers "will be fully blocked effective September 1st, 2023", blocked messages return error 30034, and "Twilio messaging rates will still apply to blocked messages." Your texting vendor may use a different platform, so ask them to show you their registration status rather than assume it.
The phone system is the other half of recall. Our pages on VoIP for dental offices and connecting the phone system to your practice software cover integration; if your fax or main lines still run on copper, see dental office phone systems and VoIP.
The upgrade calendar for a periodontal office
The upgrade calendar lists the dates that force hardware and software changes in a perio office. As of 26 October 2026, Windows 10 Home and Pro and SQL Server 2016 are past end of support, and Windows Server 2016 reaches its extended end date on January 12, 2027, per Microsoft's lifecycle pages.
| Item | Date (Microsoft Lifecycle, checked 26 October 2026) | What it means in a perio office |
|---|---|---|
| Windows 10 Home and Pro | Retired October 14, 2025 | Planning workstations, CBCT acquisition PCs and probe PCs still on Windows 10 need paid extended updates or replacement; check your imaging and planning vendor's Windows 11 support first |
| SQL Server 2016 | Extended support ended July 14, 2026; Microsoft now sells paid Extended Security Updates a year at a time | Imaging and practice-software databases, and charting databases, may sit on SQL Server 2016; ask each vendor which version they run and support |
| Windows Server 2016 | Extended support ends January 12, 2027 | Imaging and practice-software servers bought several years ago are the usual candidates |
| Implant-planning software major versions | Set by each vendor | Re-check graphics card and memory minimums before upgrading; see the planning workstation guide |
The sequence that causes the fewest surprises: ask the imaging and planning vendors which Windows and SQL Server versions they support, then replace or upgrade the PCs and server, then upgrade the applications. Doing it the other way round is how a CBCT acquisition PC ends up on a Windows version its software does not support. Our dental IT roadmap shows how to plan this over a year, and Windows 10 end of life for dental practices covers the PC side.
Security for a periodontal practice
A periodontal practice holds surgical photos, CBCT studies, referral letters from other offices and medical histories, so it needs the same HIPAA technical safeguards as any dental office plus attention to old servers, vendor remote access and the vendors who hold images. The checklist below is what a perio office should have in place.
Security checklist for a periodontal office
- Old servers kept "only for the backup" are treated as live: they still hold patient records
- Backups are encrypted, kept apart from the office network, with one copy offline or unchangeable
- Multi-factor sign-in on email, remote access and every cloud portal that holds images
- Vendor remote access to imaging and planning PCs is switched on per session and logged
- A written list of vendors that hold patient data (imaging cloud, planning cloud or licence service, referral portal, texting, email), each with its BAA status
- Agreed patch windows with the vendors who ask you not to update CBCT and planning PCs
- Separate user accounts per person; no shared logins on the planning workstation
- Guest Wi-Fi isolated from the clinical network
- Staff phishing training, repeated during the year
- A tested plan for a ransomware morning, written down and known to the office manager
The HIPAA Security Rule changes that HHS proposed were published in the Federal Register as a proposed rule on 6 January 2025 (RIN 0945-AA22). It is proposed; no final rule is listed as of 26 October 2026. How it would apply to your office is a question for your compliance adviser. Our overview of HIPAA Security Rule updates for dental practices tracks what changed.
For the worst case, read dental ransomware recovery. Our dental cybersecurity page and the page on email security for dental offices cover the two places most attacks start.
Periodontal practices Legend has worked with
These are periodontal practices whose projects appear on Legend's work pages. Each card states only what that public project page says.
Rolla Periodontics & Implant Center
A new practice opening in September 2026: office computers, imaging connectivity, networking and cybersecurity. See the Rolla project.
Anchor Periodontics
Technology infrastructure for a new practice, which Legend's September 2026 update described as wrapping up: network infrastructure, workstations, clinical technology and imaging connectivity. See the Anchor project.
Prosper Periodontics & Dental Implants
A new practice in October 2024, when Legend was in the final stages of building out its technology and security systems. See the Prosper project.
We have also worked with Gum Specialty Center in Allen, Texas, and Venice Periodontics & Implant Dentistry in Venice, Florida.
What should a periodontal practice ask an IT provider? The 15-question scorecard
Ask these 15 questions of any IT provider before you sign, and score each answer against the good answer and the red flag. A provider who answers most of them specifically, in writing, understands periodontal practice technology; one who answers in generalities does not.
These are the perio-specific questions. For contract, pricing and onboarding questions, use the 20 general questions to ask before signing a dental IT contract as well.
| No. | Question | What a good answer sounds like | Red flag |
|---|---|---|---|
| 1 | Which implant-planning software have you set up, and what graphics card did you specify? | Names the vendor's current minimum and adds headroom | "Any good PC will do" |
| 2 | Where will the planning licence live, and what happens if that PC or our internet is down? | Explains dongle, dongle server or internet licence for our planner | Has not heard of a dongle server |
| 3 | How do CBCT studies get from the acquisition PC to the imaging server and the backup? | A named path and a schedule | "The imaging company handles that" |
| 4 | How do we send a CBCT study to a referring dentist without email attachments? | A portal or share with a BAA, link expiry and a viewer | "Put it on a USB stick" |
| 5 | What do you need from the CBCT maker's site-preparation sheet before the room is built? | Asks for the sheet and the data drop specifications | Has never seen one |
| 6 | Which chairs need wired drops, and where will Wi-Fi carry headsets and scanners? | A room-by-room answer | "Wi-Fi covers everything" |
| 7 | How do you handle the electronic probe's driver and COM-port conflicts after Windows updates? | Knows the probe appears as a COM port and checks it after updates | Has not supported a probe |
| 8 | Which of our files are not in the backup today? | A list that includes planning projects, the photo folder and any charting database | "Everything is backed up" |
| 9 | When did you last restore a CBCT study, and how long did it take? | A date and a time | No restore test on record |
| 10 | How is our clinical network separated from guest Wi-Fi, cameras and phones? | Zones and firewall rules, written down | One flat network |
| 11 | Who has remote access to our imaging and planning PCs, and how is it switched off? | Named vendors, per-session access, a log | Always-on remote tools nobody tracks |
| 12 | Which of our vendors need a BAA, and do you keep the list? | Keeps an inventory and shows it | "That's your problem" |
| 13 | Which of our PCs and servers hit an end-of-support date in the next 18 months? | A dated list by device | No device inventory |
| 14 | If we add a location, how does the second office see CBCT and the practice software? | Compares VPN and cloud options with measured times | "We'll figure it out then" |
| 15 | What do you do on a surgical morning when the practice software server is down? | A written downtime plan; staffed 24/7 helpdesk; monitoring alerts before patients arrive | No plan, only a phone number |
Ask us all 15 in a Free Dental IT Assessment.
Periodontal practice IT checklist
Fill this in with your current provider or on your own. Every "No" or "Don't know" is a line for your next IT conversation. Our IT services for periodontists page covers how we work with perio offices.
| Area | Check | Yes | No | Don't know |
|---|---|---|---|---|
| Planning | The planning workstation meets the planner's current published minimum, including video memory | ☐ | ☐ | ☐ |
| Planning | We know where the planning licence lives and what happens if that PC is off | ☐ | ☐ | ☐ |
| Planning | Planning projects and guide files are in the backup | ☐ | ☐ | ☐ |
| Imaging | CBCT studies move off the acquisition PC to the imaging server on a schedule | ☐ | ☐ | ☐ |
| Imaging | We know the free space on the imaging server and when it runs out | ☐ | ☐ | ☐ |
| Imaging | Imaging PCs run a Windows version the imaging vendor supports | ☐ | ☐ | ☐ |
| Charting | Each operatory's headset or probe works after the last Windows update | ☐ | ☐ | ☐ |
| Charting | We know whether our charting tool keeps its own database | ☐ | ☐ | ☐ |
| Charting | Wi-Fi covers every room where headsets or tablets move | ☐ | ☐ | ☐ |
| Network | Clinical devices are on their own zone, apart from guest Wi-Fi | ☐ | ☐ | ☐ |
| Network | Phones and building devices are on separate zones | ☐ | ☐ | ☐ |
| Network | Vendor remote access is per session and logged | ☐ | ☐ | ☐ |
| Backup | The backup list covers every item in the "Is it in the backup?" list | ☐ | ☐ | ☐ |
| Backup | A CBCT study, a planning project and a perio chart were restored in the last quarter | ☐ | ☐ | ☐ |
| Backup | One backup copy is offline or unchangeable | ☐ | ☐ | ☐ |
| Security | Multi-factor sign-in is on for email and remote access | ☐ | ☐ | ☐ |
| Security | We have a vendor list with each vendor's BAA status | ☐ | ☐ | ☐ |
| Security | Staff had phishing training this year | ☐ | ☐ | ☐ |
| Phones and recall | The texting tool's BAA was signed before patient data flowed | ☐ | ☐ | ☐ |
| Phones and recall | Our texting number is registered for business messaging | ☐ | ☐ | ☐ |
| Phones and recall | We know who owns our texting number | ☐ | ☐ | ☐ |
| Lifecycle | No PC that handles patient data still runs Windows 10 without extended updates | ☐ | ☐ | ☐ |
| Lifecycle | We know which databases run on SQL Server 2016 | ☐ | ☐ | ☐ |
| Lifecycle | We have a plan for every Windows Server 2016 machine before January 12, 2027 | ☐ | ☐ | ☐ |
What does IT cost for a periodontal practice?
Legend's dental IT plans: starting at $360 per month. Hardware procurement, major cabling projects and software licensing are quoted separately, and new practices are custom quoted. The cost drivers for a perio office (planning workstations, CBCT storage, operatories with charting devices, locations) are explained on our dental IT support page.
Frequently asked questions
What technology does a periodontal practice need that a general dental office doesn't?
Beyond the practice software, imaging, network, backup, security and phones every dental office runs, a periodontal practice usually adds CBCT imaging, an implant-planning workstation with a dedicated graphics card, voice or electronic perio charting, two-way image exchange with referring dentists and surgical days that cannot afford downtime. Each one adds storage, network, backup or device work for IT.
What files does a periodontal office need to back up?
Back up the practice software database and the imaging server, then the files that often live on single PCs: CBCT folders on the acquisition PC, implant-planning projects and guide files, the scanner cache, the surgical photo folder, any separate charting database, dongle-server settings and lot-number records. Prove it each quarter by restoring one study, one plan and one chart.
Which of our PCs and servers hit end of support?
Per Microsoft's lifecycle pages, checked 26 October 2026, Windows 10 Home and Pro retired on October 14, 2025, SQL Server 2016 extended support ended on July 14, 2026, and Windows Server 2016 extended support ends on January 12, 2027. Check your imaging and planning vendors' Windows 11 and SQL Server support before you upgrade anything.
How do we separate the clinical network from patient Wi-Fi?
Put clinical devices (the practice software server, imaging server, CBCT acquisition PC, planning workstation, dongle server and operatory PCs) on their own network zone, usually a VLAN, and give patient Wi-Fi internet-only access with firewall rules blocking it from everything else. Phones, cameras and other building devices get their own zones, too, with access only to the services they need.
When planning software or the CBCT export fails, do we call the vendor or IT?
Call the software or imaging vendor first when the application shows an error, a licence message or a failed export inside the program. Call IT first when the PC is slow or will not start, the network or internet is down, a dongle server cannot be reached or storage is full. Write the answer for each system on your technology map.
What does dental recall software need from IT?
Dental recall software needs a working connection to your practice software, read-only or with write-back, set up and kept updated. Before patient data flows, sign a business associate agreement with the vendor. Confirm your texting number is registered for business messaging, keep reminder text generic, and get in writing who owns the texting number if you switch vendors.
The bottom line
A periodontal office runs a general office's technology plus CBCT, implant planning, perio charting and referral exchange, and each of those adds work for the PCs, network and backup. The checklist above is the first step: fill it in, and every "No" or "Don't know" becomes a line on your plan. Opening a new office instead? See our page on dental startup IT.
When you want a second opinion, ask for a Free Dental IT Assessment: written findings and prioritized recommendations on your computers, software, network security, backups and performance. Legend Networking has served over 3,500 practices since 2004. Support rests on 24/7 monitoring, in-house engineers with no outsourced first-level triage, and a staffed 24/7 helpdesk at 1-800-794-1588. This guide is published by Ian Lynch, who has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps.

