Choosing an IT Company for a Periodontal Practice (2026)
Forty minutes before the first incision of a surgery block, the planning workstation says the licence cannot be found. The planning-software vendor's desk is not open yet and, when it is, says the dongle server belongs to the IT company. The IT company says nobody told it there was a dongle server. The patient has been fasting since midnight, the surgical guide is on the bench, and the only person who can see the whole problem is you.
This is the provider side of our periodontal series. The periodontal practice technology guide covers what to buy and how to lay it out; this page covers how to choose and work with the IT company that keeps it running: what it must own, where each vendor's support stops, how it should treat a surgery day, the warning signs, how to change providers without losing a licence or an archive, and what the first ninety days should deliver. Every vendor fact below was read in that vendor's published pages or PDFs on 18 November 2026.
The right IT company for a periodontal practice owns the computers, network, server, backups and sign-ins beneath your CBCT, implant-planning software, perio charting devices and referral exchange, including the licence or dongle server, and protects surgery days with maintenance windows, monitoring and a staffed helpdesk, while each software and imaging vendor answers only for its own product.
- An IT agreement for a periodontal practice should name the planning licence or dongle server, the CBCT archive, the charting database and the referral channels as line items, not imply them under "all workstations".
- Every vendor stops at the edge of its own application; the computer, Windows, drivers, free disk space, network, backup and accounts between systems belong to the IT company.
- Surgery days need written rules: no patches, reboots, network changes or vendor remote sessions inside a block, a pre-block check and a staffed helpdesk in the gap vendors do not cover.
- Switch by inventory, not by date: record and take ownership of every licence, account, archive path and number before notice, restore-test a CBCT study, and cut over on non-surgical days.
- The first ninety days should end with documents you can hold: an inventory, a backup scope list with a dated restore, a network map and a replacement calendar against Microsoft's end-of-support dates.
In this guide
- What must an IT company own in a periodontal office that a general office never asks for?
- Where does each vendor's support end in a periodontal office?
- How should an IT company protect a surgery day?
- What does an implant case ask of your IT, from CBCT to surgical guide?
- What should your IT company do about referring dentists, fax and portals?
- What are the signs that an IT company does not understand periodontics?
- How do you switch IT companies in a periodontal office without losing the planning licence, the CBCT archive or the referral line?
- What to ask your IT provider before you sign a periodontal support agreement
- What to verify before you sign
- What should the first 90 days with a new IT company deliver?
- How Legend Networking works with periodontal practices
- Frequently asked questions
- The bottom line
What must an IT company own in a periodontal office that a general office never asks for?
A periodontal practice needs its IT company to own five things most general offices never need: a planning workstation and its licence or dongle server, CBCT storage and its backup, perio charting devices and their drivers, image exchange in both directions with referring dentists, and a surgery-day protocol that keeps maintenance, updates and vendor remote access away from surgical blocks.
A general dental office can be supported well by a company that keeps the server up, the sensors capturing and the practice software fast. A periodontal office runs all of that and then adds systems whose failure modes are different: a licence that lives on one machine, a 3D study that is too big for email, a probe that disappears after a Windows update, a referring dentist who stops sending when a share link dies. Here, system by system, is what a periodontal support agreement should cover, and the column that matters most is the last one: whether the agreement says so in writing.
| System | Why a periodontal office is different | The vendor's part | The IT company's part | Should the agreement name it? |
|---|---|---|---|---|
| Practice software (Dentrix, Eaglesoft, Open Dental, Archy, or a perio-specific system such as DSN Perio) | Surgical templates, implant and graft lot documentation, mixed dental and medical billing | The application, its updates and its own support desk | Server or cloud sign-in health, database backup, user accounts, the bridges to charting and voice tools | Yes, including the bridges |
| CBCT and 3D imaging | Many implant cases carry a study; studies are large and must reach the planning PC and referring dentists | The unit, the acquisition software, the viewer | Acquisition PC, gigabit path to the server, storage growth, backup of the image store | Yes, with the archive location named |
| Implant-planning software and its licence | Dedicated graphics card; licence by USB dongle, dongle server or internet account | The planner, its updates, its licence account | The workstation spec, graphics drivers, free disk space, the dongle-server PC, project files in the backup | Yes, with the dongle or licence server named |
| Perio charting by electronic probe or voice | USB keys and receivers in every charting operatory; a separate charting database in some systems | The probe or headset, its software, its bridge file | USB ports, sound devices, drivers after updates, screen resolution, Wi-Fi where headsets move, the charting database in the backup | Yes |
| Intraoral scanner and surgical-guide path | STL files move to the planner and to a lab or in-house printer | The scanner, its software, its cloud | Wired or Wi-Fi connection, approved Windows updates, the export folder, the printer PC | Yes, if you print in-house |
| Referral exchange and fax | Images and reports go both ways every day | The portal or eFax application | Accounts in the practice's name, sharing settings, link expiry, the receiving folder, business associate agreements on file | Yes |
| Surgical photos and implant documentation | Photos, lot numbers and procedure notes belong to the surgical record | The camera, the practice software's templates | The import folder, where it lives, that it is in the backup | Yes, as a backup line |
| Lasers and surgical devices | Some lasers join Wi-Fi for vendor remote diagnostics; piezo units usually stand alone | The device and its firmware | A device zone on the network, a vendor remote-access policy, clean power protection | Yes, as a network zone |
| Phones, texting and periodontal maintenance recall | More reminder traffic; the recall interval is clinical, the integration is technical | The phone or texting application | The link to the practice software, who owns the number, call quality on the network | Yes, with number ownership stated |
| Backup and security | A surgical morning cannot wait for a slow restore | The backup software | Scope that names the CBCT archive, planning projects and charting database; quarterly restore tests; multi-factor sign-in; monitoring | Yes, with the restore test on a schedule |
The owner page, IT support for periodontal practices, says how Legend covers each of these rows. This guide is about judging any provider against them, including us. For the general shape of the support relationship, start with dental IT support.
Where does each vendor's support end in a periodontal office?
Every vendor in a periodontal office supports its own application and stops at its edge: Open Dental's desk helps you use Open Dental, Florida Probe's covers its probe and software, the planning vendor covers the planner and its licence. The computer, network, Windows, backup, accounts and the handoffs between systems belong to the IT company.
The gap between those edges is where surgery mornings are lost. The table below records what each vendor publishes about its own support or requirements, in its own words where a quote is useful, and what that leaves for the IT company to own. Every line was read on 18 November 2026; vendor pages change, so check the current page before you rely on one.
| System | What the vendor publishes (read 18 November 2026) | What that leaves for the IT company |
|---|---|---|
| Open Dental | Its support page says the team is "committed to helping you use Open Dental efficiently and effectively" and that "Up to two specific issues can be answered per call/email/chat." | The server, database backup, Windows, sign-ins, speed, the program links and bridge paths to probes and voice tools, and anything beyond the two issues per contact |
| Dentrix | Dentrix Connected Care Essentials gives "priority access to trained Dentrix specialists, automatic software updates, in-product chat support" | The server the updates land on, the workstations, the imaging and voice bridges, the backup |
| CBCT imaging software (CS 3D Imaging as the example) | The requirements sheet lists Windows 10 and 11 64-bit and Windows Server 2016, 2019 and 2022; asks for "1000 BaseT network bandwidth (1Gb/s)"; for its implant-planning module, a dedicated graphics card with 1 GB supporting OpenGL 3.2, and says "Keep your graphic cards' drivers up-to-date" | The acquisition PC, a gigabit path between rooms, graphics drivers, storage growth, the archive in the backup, the operating-system calendar |
| coDiagnostiX (Dental Wings, Straumann group) | Needs "Support for OpenGL version 3.3 or higher", "Minimum 8 GB RAM" and a "Minimum of 10 GB of free disk space prior to each start"; dongle-free subscription plans are "Available in selected countries only" | A workstation that clears the spec, a free-disk-space watch before surgery days, the dongle-server PC on cable where a dongle is used, project files in the backup |
| Blue Sky Plan | "BlueSkyPlan is no longer available for Mac. It can only be installed on Windows computers." | A Windows planning workstation; no Mac in the planning room |
| DTX Studio Implant | Windows 11 or 10 64-bit Pro or Enterprise, or current macOS; a "Dedicated add-in graphics card with optimal 3D support (OpenGL 3.3) and 2 GB memory or more", 4 GB for 4K displays | The graphics card and monitor pairing, driver updates, the licence account |
| Florida Probe and VoiceWorks | FP32 minimums: "MS Windows 10 or above (64 bit Recommended)", "RAM: 8 GB or above", two USB ports, "Network: 100 Mb/s (1 GB/s recommended)"; FP32 "can be installed on every computer in the office"; both systems "bridge to most practice management software" and link with "over 40" systems including Dentrix, DSN Software, Eaglesoft and Open Dental; VoiceWorks ships with a VoiceWorks USB Key and an FP32 Software Key per matched headset; technical support is reachable on weekdays in business hours, Eastern time | USB ports and keys in every charting operatory, the Windows sound device, drivers after updates, the FP32 database and where it lives, and the support window outside Eastern business hours |
| Bola AI (Dentrix Voice, Dentrix Ascend Voice) | "Bola is supported on Windows computers only"; Windows 11, with a note that Microsoft has ended Windows 10 support; "RAM: At least 8GB, 16 GB is recommended"; "Internet speed 10 Mbps"; "Display setting: 1600 x 900 or higher. Bola reads the perio chart from your screen, so a lower resolution can break tooth detection." Works with Dentrix, Dentrix Ascend, Eaglesoft, Open Dental, Curve and Fuse, and recommends a quality microphone. Bola describes its platform in HIPAA terms and offers a business associate agreement | Windows 11 on every charting PC, memory, display scaling and resolution, the microphone and sound device, the internet line |
| Open Dental voice perio charting | "Any microphone or headset recognized by Windows will work." and "Open Dental Cloud users are not able to utilize Voice Perio Charting." | The microphone as a Windows device, and the server-or-cloud decision this feature depends on |
| Waterlase iPlus (BIOLASE) | "WiFi connectivity enables remote diagnostics"; its BRASS system "archives your procedures"; it can "Email procedure and session notes directly from your Waterlase" | A device zone on the Wi-Fi, a written vendor remote-access policy, the email path; the laser itself stays with the vendor |
| Microsoft | Windows 10 Home and Pro reached end of support on 14 October 2025; Windows Server 2016 extended support ends 12 January 2027 | A replacement calendar for every PC and server near those dates, and a plan for the planning and charting software that only runs on a current Windows |
Two patterns stand out. First, several vendors publish their support window, and a surgery block does not keep those hours; your IT company's helpdesk is what answers in the gap, which is why its staffing belongs in the agreement. Second, almost every row ends with a Windows version, a driver or a free-disk-space figure. Those are not clinical decisions, and they are not the vendor's to manage. The implant planning software computer requirements guide collects the full workstation specs; the CBCT computer and network requirements guide does the same for imaging. For the general version of this boundary across every dental system, the batch companion on who supports what in a dental office walks through the support tiers.
How should an IT company protect a surgery day?
A surgery day is protected by rules written into the agreement: no patches, reboots, vendor remote sessions or network changes inside a surgical block; a pre-block check of the planning workstation, licence, CBCT path and backup; monitoring that alerts before the doors open; and a named way to reach a person during the block.
A periodontal office's week is not uniform. Hygiene and maintenance days tolerate a slow workstation or a reboot; a guided-surgery morning does not. A provider that understands the specialty asks for your surgical calendar in the first meeting and builds its maintenance around it. One that does not will patch on its own schedule and call it best practice. Ask to be shown each line of this protocol.
| When | What the IT company does | What you should see |
|---|---|---|
| The week before | Receives the surgical calendar; publishes a change freeze for each block; schedules patches and vendor updates on maintenance days only | A shared calendar or a monthly note that names the frozen blocks |
| The evening before | Confirms the backup completed and includes last week's CBCT studies and planning projects; confirms the dongle or licence server is on and reachable; checks free disk space on the planning workstation | A short written confirmation, or a monitoring dashboard you can open |
| Before the doors open | Monitoring has already run on the server, the acquisition PC, the planning workstation and the internet line; any alert was handled, or you were told | Silence that is explained, not assumed |
| During the block | No remote sessions on clinical machines; no vendor remote access without your say; a staffed helpdesk and a path to a person who can act | A number that is answered, and a rule for who may touch what |
| After the block | Releases held changes; confirms that the day's images, notes and photos landed where they should; every quarter, restores one CBCT study and one planning project as a test | A dated restore record you can read |
A note on who may connect. Imaging and planning vendors often ask for remote access to fix their own software. That is normal and useful, and it is also a session on a machine that holds patient images, so it should be per session, approved by someone in the practice and logged. The audit-controls standard in 45 CFR 164.312(b) asks for "mechanisms that record and examine activity in information systems that contain or use electronic protected health information"; a log of who connected to the planning workstation, and when, is the kind of record that standard describes.
Before every surgical block, your IT company should be able to tick each of these:
- The planning workstation opened the case project and the licence was found.
- The CBCT study for each case is on the imaging server, not only on the acquisition PC.
- The dongle or licence server is on, on cable, and reachable from the planning workstation.
- The last backup completed and the backup scope includes the imaging store and planning projects.
- No Windows update, firmware update or network change is pending for the block.
- No vendor remote session is scheduled; any emergency session needs your approval.
- The helpdesk knows this is a surgery day for your office.
What does an implant case ask of your IT, from CBCT to surgical guide?
An implant case crosses six systems: the CBCT and its acquisition computer, the imaging server, the planning workstation and its licence, the intraoral scanner, the guide path to a lab or printer, and the practice chart. Each handoff is a file moving between machines, and each one has an owner the IT company should be able to name in advance.
Vendors see their own step. The IT company is the one party whose view covers every step, which is why the case path, not the equipment list, is the right test of a provider. Ask a candidate to talk you through it; the table is what a good answer covers.
| Step | System and file | What usually breaks | Who fixes first |
|---|---|---|---|
| Capture | CBCT unit and acquisition PC produce the study | The acquisition PC's own disk fills; the unit's software is unsupported on a newer Windows | IT for the PC and disk; the imaging vendor for the unit |
| Store | The study moves to the imaging server and into the backup | The study stays on the acquisition PC; the archive folder is outside the backup scope | IT |
| Export | A DICOM export leaves the imaging software for the planner | The export fails inside the imaging software, or the export folder is not where the planner looks | The imaging vendor for the export; IT for the folder and path |
| Scan | The intraoral scanner produces an STL of the arch | The scanner cart cannot reach its cloud or the shared folder; an unapproved Windows update changed the scanner PC | IT for the connection; the scanner vendor for the software |
| Plan | The planning workstation opens the DICOM and STL, under its licence | Licence not found; graphics driver fails after an update; free disk space under the vendor's floor | IT for the licence server, driver and disk; the planning vendor for a fault inside the planner |
| Guide | The plan goes to a lab portal or an in-house printer | The upload fails on a slow or filtered connection; the printer PC is on guest Wi-Fi | IT |
| Chart | Implant and graft lot numbers, photos and notes land in the practice software | The photo import folder is on one PC and not in the backup; the template is missing | IT for the folder and backup; the practice-software vendor for the template |
When a step fails on the morning of surgery, the question is not whose fault it is but who touches it first. For the rows above, the answer is usually IT, because the fault sits between two products rather than inside one. Our guide to dental imaging integration troubleshooting covers the symptom-by-symptom version. If a candidate provider cannot describe this path, it will learn it on your surgery days.
What should your IT company do about referring dentists, fax and portals?
Referrals are a periodontal practice's supply line, so the IT company should own the technical side: the referral fax number or eFax account in the practice's name, the portal or secure share with a signed business associate agreement and link expiry, a folder where received scans land and get backed up, and a routine for adding a new referring office.
The clinical relationship with a referring dentist is yours. The technical relationship is a set of accounts and numbers that can quietly stop working, and the people most likely to notice are the referring office's front desk, who will not call your IT company. Here is what the IT company should hold for you:
- The referral fax number, whether it is a line or an eFax service, with the account in the practice's name and the IT company as an administrator, not the owner.
- The portal or secure-share accounts used to send and receive studies, with a business associate agreement on file for each vendor that handles patient images. 45 CFR 164.308(b)(1) lets a practice permit a vendor to create, receive, maintain or transmit electronic patient information for it "only if the covered entity obtains satisfactory assurances", and 45 CFR 164.314(a)(2)(i)(C) requires that contract to say the business associate will "Report to the covered entity any security incident of which it becomes aware".
- Link-expiry settings on every outgoing share, and a record of what was sent and when.
- The receiving folder for incoming studies, on the server and in the backup, with a naming rule the referral coordinator actually uses.
- A viewer path: what a referring dentist needs to open a CBCT you send, written once and reused.
- A new-referrer routine: when a general dentist starts sending, who sets up the share, confirms a test file both ways and records the office's preferred channel.
The file sizes, channels and the copyable referral form are in our guide to sending CBCT scans, X-rays and perio charts to referring dentists. The agreements themselves are covered in our guide to business associate agreements for dental practices. What belongs in the IT agreement is simpler: a line that says the referral channels are in scope, and a name for who maintains them.
What are the signs that an IT company does not understand periodontics?
The signs appear before you sign: no question about where the planning licence lives, a quote that specs every PC the same, a backup described as "everything", a patch schedule that ignores your surgical calendar, no idea what a dongle server or a DICOM export is, and no periodontal office it can point to.
Most generalist providers are competent at what they do. The problem is that what they do was designed for an office with a server, a few sensors and a hygiene schedule, and the gaps only show on a surgery morning. Each sign below comes with the question that exposes it in a meeting.
| Sign | What it costs you | The one question that exposes it |
|---|---|---|
| Every workstation in the quote is the same model | A planning PC that cannot render a study, or that fails the planner's graphics floor after the next update | Which machine in this quote is the planning workstation, and which vendor document did you spec it against? |
| Nobody asks where the licence lives | A dongle server that turns out to be the front-desk PC, and a block that waits for a reboot | If our planning software licence is a dongle, which machine holds it and what happens when that machine restarts? |
| "Everything is backed up" | A CBCT archive on the acquisition PC's own disk, outside the backup, discovered on the day you need it | Show me the backup scope list. Is the imaging archive folder on it by name? |
| Patching on the provider's schedule | A reboot or driver change inside a surgical block | Here is our surgical calendar. Which days will you never touch? |
| "The imaging company handles that" | Nobody owns the path from the acquisition PC to the server and the backup | Who moves a study from the acquisition PC to the server, and how often? |
| No experience with a probe or voice headset | A charting operatory that works until the first Windows update | After Windows updates, what do you check on a charting PC before the first patient? |
| Flat network | A laser, a guest tablet and the planning workstation on one segment | How many network zones will our office have, and which devices go in each? |
| No periodontal office to point to | A provider learning the specialty on your time | Which periodontal practices have you set up, and may we see the project pages? |
If more than two of these land, keep looking. Our guide to how to choose a dental IT company walks through the general shortlist process, and the best dental IT companies list is a place to see how providers describe themselves.
How do you switch IT companies in a periodontal office without losing the planning licence, the CBCT archive or the referral line?
Switch by inventory, not by date: list every account, licence, dongle, archive path, fax number and portal first, confirm the practice owns each, take a restore-tested backup that includes a CBCT study and a planning project, then cut over on non-surgical days with the old provider still reachable until the first full surgical block has run.
The owner page has the six steps of a switch in short form, and our guide to switching dental IT providers without downtime has the ten-phase version for any dental office. What follows is the part that is specific to a periodontal practice: the handoff inventory, which is the list of things that disappear with a departing provider if nobody writes them down.
| Item | Where it usually hides | Who should hold it | What to collect before notice |
|---|---|---|---|
| Planning-software licence | A USB dongle on one PC, a dongle-server PC, or a vendor account in the old provider's email | The practice | The dongle's location, the licence or account number, the vendor account email and its recovery method |
| Dongle-server PC | Under a desk, often an old workstation with a label nobody reads | The practice; the IT company administers it | Its name, address, which clients connect to it, what happens when it restarts |
| CBCT archive | The imaging server, or still the acquisition PC's own disk | The practice | The archive path, its size, its growth rate, and the date of the last successful restore |
| Imaging and planning vendor accounts | Vendor portals registered to the old provider | The practice | Each account, who is the administrator, and a transfer of the administrator role |
| Charting database (Florida Probe and similar) | A database on one PC or the server, separate from the practice software | The practice | Its location, its version, and whether the bridge path in the practice software points to it |
| Headset and probe keys | USB keys matched to headsets by sticker colour | The practice | A count per operatory, and the spares |
| Referral fax number or eFax account | A service in the old provider's name | The practice | The account, the porting authority if it is a line, the administrator credentials |
| Portal and secure-share accounts | Created by whoever set up the first referral | The practice | Each account, its business associate agreement, its administrator |
| Domain, email and sign-in administrator | The registrar and the Microsoft 365 or Google Workspace tenant | The practice | Global administrator access in a practice-owned account, with multi-factor sign-in |
| Firewall, Wi-Fi and switch administration | Devices configured by the old provider | The practice; the new IT company administers them | Current configuration exports and the administrator credentials |
| Internet and phone circuits | Carrier accounts, static addresses | The practice | Circuit IDs, static addresses, the carrier account contact |
| Texting and recall number | The texting vendor's account | The practice | Who owns the number and whether it can move |
Two specifications from the Security Rule belong on this list. The termination-procedures specification, 45 CFR 164.308(a)(3)(ii)(C), covers access that ends "when the employment of, or other arrangement with, a workforce member ends"; that specification is written about workforce members, and applying the same discipline to a departing IT company means every credential it held is closed or re-keyed at handoff. The unique-user-identification specification, 45 CFR 164.312(a)(2)(i), calls for "a unique name and/or number" per user, which is why a shared "admin" login left behind by the old provider should be replaced with named accounts.
Then the sequence, built around surgery blocks rather than calendar weeks:
- Inventory, before notice. Fill the table above with the current provider while the relationship is still cooperative. Anything you cannot find becomes a question in writing.
- Ownership, before notice. Move every account in the table into a practice-owned identity. Where an account cannot be moved, record it as a risk.
- Recovery gate, before any change. Take a backup, then restore one CBCT study, one planning project and the charting database to a machine other than the live system, and keep the record.
- Overlap, on maintenance days. The new provider installs its monitoring and management tools beside the old ones, on days with no surgical block, and removes the old tools only once it can see every machine.
- Cutover, on non-surgical days. Move the dongle server, the firewall administration and the backup job on days with no guided surgery. Confirm the planning workstation finds its licence afterwards.
- First surgical block, with both providers reachable. Keep the old provider's handoff contact open through the first full surgical block under the new agreement. Close the old accounts after it, not before.
- Thirty-day acceptance. Walk the inventory again with the new provider and confirm every item has a current owner and a current credential.
A switch handled this way takes about a month of elapsed time, most of it waiting for maintenance days. A switch handled by date takes a weekend and can cost the first surgery morning after it.
What to ask your IT provider before you sign a periodontal support agreement
None of these repeats the technology guide's scorecard or the owner page's five questions. They are the ones that only a provider who has run a periodontal office can answer in detail, and they are meant to be asked aloud, with notes taken.
About surgery days
- Who on your side receives our surgical calendar each month, and which actions are banned inside a block?
- What did your monitoring catch, before the doors opened, at an office like ours in the last quarter?
- If a planning workstation fails during a block, who comes, how do they get in, and what do they bring?
- Which of your people has set up a guided-surgery workflow, and may we speak to them?
About the planning workstation and licence
- Walk me through where our planning licence will live and what happens when that machine restarts or our internet drops.
- How do you watch free disk space on the planning PC, and what is your threshold?
- Who approves a graphics driver update on the planning workstation, and when is it applied?
- If we add a second planning seat, what changes on the network?
About imaging and charting devices
- By what route does a CBCT study leave the acquisition PC for the server and the backup, and how would we know if that stopped?
- What do you check on a charting PC after a Windows update, before the first patient?
- How many network zones will our office have, and where do the laser, the scanner cart and guest devices sit?
- When did your team last bring a 3D imaging archive back from backup, and how many hours did that take?
About referrals and vendors
- Which referral channels will be in scope, and who maintains the fax number, the portal accounts and the receiving folder?
- When a referring office changes how it sends, who sets up the new path and tests it both ways?
- For the planning, imaging and charting vendors, will you hold a ticket until it is closed, or hand it back to us once you have made the call?
- Our charting vendor's desk keeps Eastern business hours and our surgery blocks start early; who covers a charting fault in that gap?
About accounts, reporting and the exit
- Which administrator accounts will be in the practice's name on day one?
- How is vendor remote access approved and logged on our clinical machines?
- Show us the report a periodontal office receives from you each month, anonymised; which lines on it would tell us the archive had stopped growing?
- On the day we give notice, which documents and credentials come to us, in what format, and by when?
For the agreement's own terms, exit and insurance, pair these with our 20 questions for a dental IT contract.
What to verify before you sign
A spoken answer is only a promise. Before signing, turn the five or six that matter into evidence you can hold. None of this is unusual to ask for, and a provider that has done the work will have it ready.
- A reference from a periodontal or surgical specialty practice, and a conversation with it about a surgery morning that went wrong and how it was handled.
- Project pages or a written description of periodontal offices the provider has set up, naming the systems involved.
- The written scope, with the dongle or licence server, the CBCT archive, the charting database and the referral channels named as line items, not implied by "all workstations".
- The backup scope list as it would read for your office, with the restore-test schedule and the form of the restore record you will receive.
- The maintenance calendar policy in writing, with the surgical-calendar freeze stated.
- The vendor remote-access policy: per session, approved, logged.
- The exit clause: what is returned, in what form, in how many days, and what it costs.
- The business associate agreement the provider will sign with you, and its own list of subcontractors that will touch your data.
- The pricing structure: what is included monthly, what is a project, what is quoted separately, and how a second location or a new planning seat changes the number. A structure you can read beats a figure you cannot check.
- Proof of insurance, and the helpdesk staffing model in the provider's own words.
If you buy this as a monthly plan, what the plan should cover in general, before the periodontal additions above, is on our page about managed IT services for dental practices. If you run or plan a second location, read it with the DSO IT support page, because a second office changes how the archive, the licence and the referral line are shared.
What should the first 90 days with a new IT company deliver?
The first ninety days should produce documents you can hold: a system and account inventory, a backup scope list with a dated restore of a CBCT study and a planning project, a surgical-calendar maintenance schedule, a network map with the clinical, device and guest zones, and a replacement calendar for every machine near its end-of-support date.
Onboarding is where a provider's understanding of the specialty becomes visible. The table is a reasonable sequence; the point is that each period ends with something written.
| Period | What the IT company delivers | How you check it |
|---|---|---|
| Days 1 to 10 | The system and account inventory, filled; monitoring on every server, acquisition PC and planning workstation; the surgical calendar received and the first freeze published | Open the inventory and find the dongle server, the archive path and the fax account by name |
| Days 11 to 30 | The backup scope list naming the imaging archive, planning projects and charting database; the first restore test of a CBCT study and a planning project, dated; vendor remote-access policy written | Read the restore record; ask how long the study took to restore |
| Days 31 to 60 | The network map with clinical, device and guest zones; the laser, scanner cart and guest devices placed; multi-factor sign-in on email and remote access; the planning workstation checked against the planner's current requirements | Walk the office with the map; ask which zone each wall port belongs to |
| Days 61 to 90 | The replacement calendar: every PC and server against its Windows end-of-support date, and the planning and charting software against the Windows version each still supports; the first monthly report in the agreed form | Compare the calendar with the Microsoft dates in this guide; check that the report names your office's systems, not generic ones |
The replacement calendar is the item most often missing. Windows 10 Home and Pro reached end of support on 14 October 2025, and Bola's current requirement is Windows 11, so a charting PC still on Windows 10 is both unsupported and, for voice charting, out of spec. Microsoft lists 12 January 2027 as the last day of extended support for Windows Server 2016, so any imaging server still running it belongs on the calendar now. Our guides to what Windows 10's end of life means for dental practices and the Windows Server 2016 deadline for dental offices cover the options. Whether the fixes happen remotely or need a visit is covered in our guide to remote versus onsite dental IT support. The orthodontic version of this guide, written for offices with scanners and satellite locations, is our guide to choosing an IT company for an orthodontic practice.
How Legend Networking works with periodontal practices
Legend Networking is a dental IT company headquartered in Dallas, Texas, with 22+ years in dental IT. It has served over 3,500 practices since 2004 and has completed 1,500+ dental startup buildouts. 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. Planning software, charting devices and lasers are systems your practice runs; their vendors support the applications, while Legend looks after the workstations, graphics drivers, network, licence or dongle server, backups and sign-ins beneath them.
Support rests on 24/7 monitoring, in-house engineers with no outsourced first-level triage, and a helpdesk staffed 24/7 at 1-800-794-1588. Support is remote-first nationwide, with onsite dispatch by appointment across served dental markets. Legend holds a 4.8 rating from 173 Google reviews. The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps.
The periodontal work is on Legend's public project pages: a new periodontal and implant practice in Missouri, with office computers, imaging connectivity, networking and cybersecurity; a new periodontal practice in Maryland, with network infrastructure, workstations, clinical technology and imaging connectivity; a new periodontal and implant practice in Texas, with its technology and security systems; and a periodontal and implant practice in Florida that joined Legend in September 2026. Each page says only what the project recorded.
If you are opening rather than switching, the sequence from floor plan to first surgery is in our guide to starting a periodontal practice: the technology plan, and the device-level setup for hands-free charting is in our guide to voice perio charting setup. Specialty offices in North Texas have a local companion piece, specialty practice IT in Dallas; for other markets, start from dental IT support in your city.
Frequently asked questions
Does a periodontal office need a different kind of IT support from a general dental office?
Yes, in scope rather than in kind. A periodontal office adds a planning workstation with a licence or dongle server, large CBCT studies that must be stored and shared, charting devices with USB keys and drivers, two-way referral exchange and surgery blocks that cannot absorb a reboot. The IT company must own each of those, and the agreement should name them.
Who should hold the implant-planning licence and the dongle server, the practice or the IT company?
The practice should own the licence account and the dongle; the IT company should administer the machine that serves it. Record the dongle's location, the account email and its recovery method in the practice's name. If the only copy of that information sits in the IT company's mailbox, a change of provider puts your planning software at risk.
Should the IT company or the planning-software vendor take the first call on a surgery morning?
Call the IT company first unless the error is plainly inside the planner, such as a message about the plan itself. Licence not found, a missing export, a slow or blank display and a workstation that will not start are usually faults between products, and only the IT company's view covers every step. Agree this rule in writing before the first block.
Can a periodontal office be supported remotely, or does it need an IT company nearby?
Day to day, nearly all of it happens remotely: monitoring, patching on maintenance days, licence and account administration, backup checks and restore tests. Hands are needed for a failed workstation, a dongle move or new cabling, so ask how onsite visits are arranged and scheduled around surgery days. A provider that is remote-first with planned onsite dispatch fits most single-location periodontal offices.
What happens to our Florida Probe or VoiceWorks setup when we change IT companies?
Nothing should change if the handoff inventory records the FP32 database location, the bridge path in the practice software, and the USB keys matched to each headset. Florida Probe publishes its minimum computer requirements and says FP32 can be installed on every computer in the office, so the new provider can check each charting PC against them and confirm the bridge opens a chart.
Does cloud practice software remove the need for an IT company in a periodontal office?
No. Cloud practice software moves the database off your server, but the CBCT acquisition PC, the imaging archive, the planning workstation and its licence, the charting devices and the network stay in the building. Open Dental also notes that its Cloud users cannot use its voice perio charting, so the server-or-cloud decision should be made with the charting workflow in view.
How long should switching IT companies take for a periodontal office?
About a month of elapsed time, most of it waiting for maintenance days. Inventory and ownership transfers happen before notice, the recovery gate before any change, overlap and cutover on days without a surgical block, and the old provider stays reachable through the first full surgical block under the new agreement. A switch compressed into a weekend skips the steps that protect surgery mornings.
What should a periodontal IT agreement say about surgery days?
It should state that no patches, reboots, firmware updates, network changes or vendor remote sessions happen inside a surgical block; that the provider receives and honours the surgical calendar; what is checked before each block; how a person is reached during one; and that a CBCT study and a planning project are restored as a test on a schedule. Those lines make the protocol enforceable.
How do we check that a provider has actually worked with periodontal offices?
Ask for project pages or written descriptions of periodontal offices it has set up, with the systems named, and for a reference you can call. Then ask the provider to walk you through an implant case from CBCT to surgical guide and to say who fixes each step. Experience shows in that answer; a provider that has not done it will stay general.
Our laser connects to Wi-Fi: is that the IT company's problem or the laser vendor's?
Both, in different parts. The laser and its firmware belong to the vendor; the vendor's remote diagnostics depend on the Wi-Fi the IT company runs. The IT company should place the laser in a device zone apart from clinical computers and guest devices, and the vendor's remote access should follow the same approval and logging rule as any other connection to your office.
The bottom line
Bring the scope table, the handoff inventory and the shortlist questions to every provider you talk to, ours included. If the current setup is the first thing you want checked, ask for a Free Dental IT Assessment: written findings and prioritized recommendations on your computers, software, network security, backups and performance, with the planning licence, the CBCT archive and the referral channels looked at by name. How Legend covers each row of the scope table is on the page for IT support for periodontal practices, and the general version of the relationship is described under dental IT support.

