Choosing an IT Company for an Orthodontic Practice (2026)
Records morning, first patient in the chair, and the ceph will not land in the chart. The IT company says it is a Dolphin problem; Dolphin says the capture station is IT's. You are the owner, on both calls at once.
If that scene is familiar, this guide is about choosing an IT company that never leaves you there again. It covers the provider side of running an orthodontic office: what an IT company has to cover, where Dolphin, OrthoTrac, Cloud 9, topsOrtho, Edge Cloud and your scanner makers stop and the IT company starts, what a well-supported clinic day looks like, the warning signs of a generalist, how to switch without losing scanner integrations, and what to ask and verify before you sign. The technology itself is covered in our orthodontic practice technology guide and the build-out list in the orthodontic office technology checklist; this page assumes you have read them or live them. Vendor documents checked 18 November 2026.
The right IT company for orthodontists keeps everything around your orthodontic software working: the open-bay workstations and Wi-Fi, scanner PCs and uploads, the imaging archive, the server or internet line your practice system needs, backups, staff accounts and the connections between your offices. The software vendor supports its application; the IT company owns the rest, including the handoff.
- The software vendor supports its application; the IT company owns the server or internet line, SQL, Windows, network, Wi-Fi, workstations, backups, accounts and the handoff between the two.
- An orthodontic support agreement should name ten things in writing: open-bay Wi-Fi surveys, scanner PC policy, the records imaging chain, archive restore tests, the practice-system platform, satellites, vendor coordination, patient-facing apps, account control and patch windows.
- Dolphin requires a domain when a server OS is used and caps one database at 25 locations; OrthoTrac recommends a dedicated server; iTero wants 1 Mbps upload per scanner; TRIOS Share runs on 5 GHz only.
- Switch IT companies with an inventory, not a handshake: every admin account in the practice's name, scanner and portal registrations recorded, the archive restored from backup, and cutover on a non-clinic day.
- A monthly report should show tickets by category, vendor-bounced faults, the dated restore test, patch windows, version dates, Wi-Fi at scanner chairs and account changes against the staff list.
In this guide
- What should an IT company for orthodontists cover that general dental IT does not?
- Where does the software vendor's support end and the IT company's begin?
- What does a good IT company do for an orthodontic office on a clinic day?
- How should an IT company serve several orthodontic offices on one practice system?
- What are the warning signs that your IT company does not understand orthodontics?
- How do you switch IT companies without losing scanner integrations and vendor access?
- What to ask your IT provider before you sign an orthodontic support agreement
- What to verify before you sign
- What should the monthly report from your IT company show an orthodontic owner?
- How Legend Networking works with orthodontic practices
- Frequently asked questions
- The bottom line
What should an IT company for orthodontists cover that general dental IT does not?
An orthodontic support agreement has to name ten things a general dental agreement leaves implicit: open-bay Wi-Fi as clinical equipment, scanner PCs and uploads, the records imaging chain, an archive that grows with each new patient and is restore-tested, the practice system's platform, satellite connections, vendor coordination, patient-facing apps, account control for a rotating team, and patch windows that respect clinic days.
The same server, the same brand of workstation and the same firewall can run a general practice or an orthodontic one. What changes is where the failures land. In a closed operatory a Wi-Fi gap is an annoyance; in an open bay with three scanners it stops the day. In a general office the imaging archive grows slowly; in an orthodontic office it grows with every records set, every progress series and every scan. The table turns those differences into a scope list. Use the last column when you read a proposal: if an item is not written down, it is not in the price.
| Scope item | Why it is orthodontic | Who owns it | What the agreement should say |
|---|---|---|---|
| Open-bay Wi-Fi surveyed at every scanner chair | Scanners upload over Wi-Fi from a single large room; the signal at the far chairs decides whether scans reach the cloud | IT company (design, survey, fixes); scanner maker publishes the spec | The survey is a named deliverable, repeated when chairs move |
| Scanner PCs and carts | iTero and TRIOS units run on computers with their own update rules and approved specs | IT company for the computer and network; the maker for the scanner software | Who approves Windows updates on scanner PCs, by name |
| The records imaging chain (pan, ceph, photos, CBCT) | One records appointment touches a capture station, a bridge into the chart and the archive | IT company for drivers, workstations, storage; the imaging vendor for its software | The bridge into the chart, named, with who tests it after changes |
| Imaging archive and its restore test | Years of records for patients who stay in treatment for years, many of them minors | IT company | A dated restore test, not a job log |
| The practice system's platform (server, SQL and domain, or the internet line for a cloud system) | Dolphin and OrthoTrac live on a Windows server with SQL Server; Cloud 9, Edge Cloud, topsOrtho and Greyfinch live on your internet connection | IT company | Version dates for a server system, or the line and failover for a cloud one |
| Satellite office connections | A part-time office must work on its clinic day with nobody on site | IT company | Each office listed, with its clinic days |
| Vendor coordination | A fault often sits between the vendor and IT; someone must own the ticket end to end | IT company | "We call the vendor with you" or "you call the vendor", in writing |
| Patient-facing apps (texting, financing, remote monitoring, aligner portals) | More vendors hold patient data; more logins to protect | The app vendor for the app; IT for the computers, accounts and sign-in security | Who manages the accounts and multi-factor sign-in |
| Accounts for a rotating team | Assistants, front desk and part-time staff change; shared logins creep in | IT company runs the process; the practice approves | The joiner and leaver steps |
| Patch and maintenance windows | A reboot during adjustments is a lost hour across the bay | IT company | Outside clinic hours and never on a records day |
Legend's own service is described on its page on IT support for orthodontic practices; the rest of this page is the buyer's side, written so you can hold any provider, including us, to it.
Where does the software vendor's support end and the IT company's begin?
The vendor supports its application: errors inside Dolphin, OrthoTrac, Cloud 9 or the scanner software, training, updates to its product. The IT company owns everything the application stands on: the server or internet line, SQL Server, Windows, the network and Wi-Fi, workstations, backups and user accounts. The handoff between the two is the IT company's job.
Most orthodontic IT frustration lives on that boundary, so it is worth being exact about it for each system you run. The table uses only what each vendor publishes in its own documents, read on 18 November 2026. Where a vendor's page could not be read, the row says so rather than guessing. The same who-supports-what map for a general dental office is in our guide to dental office technical support.
| System | How it runs | What the vendor supports | What your IT company must own | A line from the vendor's own documents |
|---|---|---|---|---|
| Dolphin Imaging and Dolphin Management | On a Windows server with SQL Server in the office; the requirements also list Dolphin Cloud | The Dolphin application; phone support in Pacific time, live chat on weekdays and closed at weekends | Server, SQL Server, Active Directory domain, capture stations, storage, backups | "When a Server operating system is used, a Domain is required." Dolphin also caps one database at 25 locations |
| OrthoTrac (a Sensei product) | On a dedicated Windows server with SQL Server | The OrthoTrac application | The server, SQL edition, workstation Windows and Office versions, backups | "Carestream Dental LLC recommends using a dedicated server to run OrthoTrac." Windows Server Essentials is not supported |
| Cloud 9 (Planet DDS) | Cloud-hosted by the vendor | The application and its hosting | The internet line and failover at every office, the firewall, workstations and sign-ins | Planet DDS calls Cloud 9 a "cloud-based solution"; its requirements page could not be read on 18 November 2026, so ask your IT company to read the current version with you |
| topsOrtho | Mac-based, cloud-powered | The application | Macs, Wi-Fi and internet, the imaging capture PCs that still run Windows, accounts | Tops describes "one reliable Mac-based system" that is "powered by the cloud" |
| Ortho2 Edge Cloud | Cloud, no local data server | The application | Internet line, workstations, local imaging, accounts | "Edge Cloud is a true cloud experience, meaning you don't need a server to store your data." |
| Greyfinch | Web-based, in the vendor's cloud | The application | Internet, workstations, accounts | Greyfinch describes itself as "100% web-based and cloud-based" |
| iTero (Align) | A scanner on Wi-Fi, uploading to Align's cloud | The scanner and its software, the MyiTero account | Wi-Fi signal at each chair, upload bandwidth, firewall ports, the Wi-Fi network the scanner joins | Upload "at least 1Mbps per scanner"; open ports 80 and 443 "in case of a firewall"; signal Good or Excellent |
| 3Shape TRIOS with TRIOS Share | A scanner on 5 GHz Wi-Fi talking to a scan PC | The scanner, the scan software, the 3Shape account | 5 GHz Wi-Fi design, signal at the chair, the ports and no captive portal between scanner and PC | "limited to work with 5GHz frequency band only"; "signal is stronger than -60 dBm at the scanner location" |
| Pan, ceph and CBCT units | Capture hardware on a workstation, images into the archive | The unit and its acquisition software | The capture workstation, drivers, storage for volumes, the bridge into the chart | Dolphin notes a local capture workstation is "sometimes necessary for non-TWAIN compliant X-ray machines or CBCT acquisition" |
Two things in that table decide whether a provider can serve you. First, hours: Dolphin publishes its support hours in Pacific time and closes live chat at weekends, so a problem before an early East Coast opening or on a weekend clinic day lands on the IT company until the vendor opens. Your agreement should say what the IT company does in that window: checks the server, the database service, the network and the capture station, and has the vendor ticket ready to open. Second, the bounce. A fault that sits between the vendor and IT, like a bridge that stops writing images into the chart after a Windows update, gets passed back and forth unless one side owns it. The right answer in a proposal is that the IT company opens the vendor ticket, stays on the call and reports back; "call Dolphin yourself" is the wrong answer.
The scanner rows matter more than their size suggests. Scanner PCs sit on the clinic Wi-Fi, run software the maker updates, and export cases to labs and aligner companies. Good support treats them as clinical devices: the maker's approved specs for the PC, Windows updates held until the maker has approved them, the Wi-Fi measured at the chairs where scans are taken, and the export path (STL to a lab, cases to the aligner portal) tested after any network change. Our guides to intraoral scanner IT requirements, CBCT computer and network requirements and dental imaging integration troubleshooting cover the technical side; for Dolphin specifically, see Dolphin Imaging IT support.
What does a good IT company do for an orthodontic office on a clinic day?
Good orthodontic IT support is mostly invisible on a clinic day because the work happened before the doors opened: the server and services were checked, scanner carts were online, the night's backup completed and verified, and nobody rebooted anything. During the day it is one number that answers, one owner for every ticket, and no update that interrupts the bay.
Here is the day as the office experiences it, next to what a well-run IT company has already done. Use it as a test: ask a provider to walk you through their version of this table for your office.
| Moment | What is happening in the office | What good support has already done | What you should notice |
|---|---|---|---|
| Before the doors open | Front desk signs in, bay workstations wake up, scanner carts come online | Monitoring checked the server or the cloud sign-in, the database service, the internet line and the backup result; a failed job was already being worked | Nothing. Everything simply opens |
| Records appointments | Pan, ceph, photos and a scan for a new start | The capture station was left alone by updates; the bridge into the chart was tested after the last change; the archive has headroom | Images land in the chart within the appointment |
| The adjustment bay | Short visits, chairs turning over, scans mid-treatment | Wi-Fi measured at the chairs where scans are taken; scanner uploads given room on the upload line; guest devices kept on their own network | Scans leave the queue; the schedule does not freeze |
| Consults and payments | Treatment plans, financing apps, texting, aligner portal | Multi-factor sign-in on every vendor portal; the people who left no longer have logins | Staff sign in once and work |
| A fault during clinic | One chair's computer slow, a scanner not uploading, the chart not opening | The helpdesk answers, takes the computer name and the exact message, decides whether it is IT or vendor, and owns the ticket either way | One call, one owner, a time by which someone calls back |
| End of day | Charts closed, offices locked | Backup jobs start with the practice database and the imaging archive both included; offsite copies follow | Nothing to do |
| One non-clinic day a month | The office is empty or on admin time | Windows and SQL patches applied, scanner PC updates applied only with the maker's approval, a restore test run and dated | A one-page report (see below) |
| Each quarter | New staff, maybe a new scanner, a new app | Accounts reconciled against the staff list; Wi-Fi re-surveyed if chairs or scanners moved; the vendor list reviewed | Questions from IT about what changed |
| Each year | Budget season | Version dates for Windows Server and SQL Server, hardware ages and storage growth reviewed with you before the vendor forces the decision | A roadmap, not a surprise |
Two dates show why the yearly line matters for orthodontic offices in particular. Microsoft's lifecycle pages give SQL Server 2016 an extended-support end of 14 July 2026 and Windows Server 2016 an end of 12 January 2027 (written as US dates; the pages show Pacific time the following morning). Both are the minimum platform in current Dolphin and OrthoTrac requirements, so an orthodontic office still on that minimum is already out of support on SQL Server and loses Windows Server support in January 2027. An IT company that knows orthodontics raised this with you a year ago; see Windows Server 2016 end of support for dental offices for the decision.
Patient-facing apps deserve one more line. Remote monitoring platforms, texting, financing and the aligner portals are the vendor's to support, but each one is a login that holds patient data and a browser that must work on your computers. Good support keeps a list of those vendors, turns on multi-factor sign-in where the vendor allows it, and removes departed staff from each one, not only from email. Our guide to dental patient communication software covers the texting side.
How should an IT company serve several orthodontic offices on one practice system?
Expect three things from an IT company that serves a multi-office orthodontic practice: one documented standard for every office, coverage on each satellite's clinic day without a technician on site, and a connection design written for your practice system rather than copied from the main office. The design differs completely between a server system and a cloud one.
For a server-based system the vendor's own rules shape the design. Dolphin requires an Active Directory domain when a server operating system is used and limits one database to 25 locations; OrthoTrac recommends a dedicated server. A satellite reaches that server over a secured connection or a hosted session, and the IT company has to prove the records workflow works from the far office before the first patient arrives there. For a cloud system the internet line at each office is the server cable, so the IT company's job becomes the line, its failover and the firewall at every address. The full plan, including the three multi-location patterns and the acquisition checklist, is in our orthodontic satellite office IT plan; the system-by-system requirements are compared in orthodontic practice management software, cloud vs server, and OrthoTrac across two offices has its own section in OrthoTrac support and migration.
Two practical tests separate providers here. Ask how a scanner moved between offices is reconnected (it needs the Wi-Fi details and the maker's account at both sites). Ask who is reachable on the satellite's clinic day if the main office is closed. A group with many offices and its own operations team is a different conversation, covered on our DSO IT support page.
What are the warning signs that your IT company does not understand orthodontics?
The clearest signs: an IT company that cannot say what your practice system needs, treats the bay's Wi-Fi as guest internet, has never measured the signal at a scanner chair, sends you to the vendor for anything inside the software, patches on clinic days, and has no dated restore test of your imaging archive. Each one costs clinic time.
| Warning sign | What it costs you | What to ask next |
|---|---|---|
| "We support everything" when you name Dolphin, OrthoTrac or Cloud 9 | A provider learning your system on your clock, during a fault | "What does our practice system need from the server or the internet line, specifically?" |
| The bay runs on one Wi-Fi network with the parents' phones | Scans stuck in the queue when the waiting room fills | "Which network do the scanners join, and when was the signal measured at the chairs?" |
| Updates arrive mid-morning | A reboot across the bay during adjustments | "Which day and hour are patches applied, and who approves updates on scanner PCs?" |
| "Call the vendor" for every error inside the software | You become the integration engineer between two support desks | "When a fault sits between the vendor and IT, who owns the ticket?" |
| "Nightly backups" offered as the whole answer, with no restore date | An archive you cannot prove you can get back | "Show me the last restore of our imaging archive: the date and the duration." |
| Server and SQL versions nobody can state | A forced upgrade when the vendor's requirements move | "Which Windows Server and SQL Server versions are we on, and when does each end support?" |
| The IT company holds your domain registrar, Microsoft 365 admin or firewall logins in its own name | A switch that takes months and a provider who can hold you | "Which admin accounts are in our name today?" |
| No idea what a records appointment is | Capture stations treated like front-desk PCs | "Walk me through what happens to a ceph from capture to the chart on our system." |
| A new scanner "just needs Wi-Fi" | A device that uploads at the front desk and fails at chair nine | "What do you check before a scanner is added?" |
One or two signs are a conversation with your current provider. Four or more is the reason this page exists. The general version of this list is in signs your dental office needs IT support.
How do you switch IT companies without losing scanner integrations and vendor access?
Switching IT companies is safe for an orthodontic office when the handoff is an inventory, not a handshake: every admin account in the practice's name, scanner and portal registrations recorded, the imaging archive opened from backup, static IPs and firewall rules written down, and cutover on a non-clinic day with a scan, a records capture and a claim tested first.
The dangerous moment is not the day the new company starts. It is the first records appointment after the switch, when a scanner that was registered under an old Wi-Fi network, a capture station whose bridge nobody documented, or a firewall rule that the departed company held in its head shows up as a fault. The inventory below is what the new IT company should collect, with the old one, before anything changes.
| What to hand over | Why it breaks in a switch | Who should hold it afterwards | How to check it |
|---|---|---|---|
| Domain registrar and DNS logins | Email and the website stop if the old company's account lapses | The practice (owner's name, practice email) | Sign in yourself and read the account holder |
| Microsoft 365 or Google Workspace global admin | Mail, sign-ins and multi-factor resets | The practice holds a break-glass admin; IT holds a named admin | Sign in with the break-glass account once |
| Firewall admin, static IP addresses, internet account numbers | Cloud systems that require a fixed address, site-to-site links, vendor remote access | The practice (documented); IT configures | Compare the documented IP with what the cloud vendor has on file |
| Wi-Fi networks and passwords for scanners | A scanner joined to a renamed network stops uploading | IT documents; the practice holds a copy | Scan a test case from the farthest chair after cutover |
| Scanner accounts (MyiTero, 3Shape Communicate) and the computers registered to them | Cases will not reach the lab or the aligner portal | The doctor's account, never an IT employee's | List the registered devices in each account |
| Aligner and lab portals, financing, texting, remote monitoring logins | Patient-facing work stops; departed staff keep access | The practice; IT manages sign-in security | Export the user list from each portal |
| Imaging bridge settings, TWAIN and capture drivers, archive path | New images stop writing into the chart | IT documents | Capture a test image into a test patient on the first non-clinic day |
| Server local admin, SQL service accounts, the practice-system service account | Nothing can be patched or restored without them | The practice holds a sealed copy; IT uses named accounts | Confirm the vendor's service runs under a documented account |
| Backup software login, offsite account and encryption keys | A backup you cannot open is not a backup | The practice holds the key; IT runs the jobs | Restore one patient's records set from the offsite copy |
| Vendor support contracts and customer numbers (Dolphin, Sensei, Align, 3Shape, imaging) | The new company cannot open a ticket on your behalf | The practice | Call one vendor and confirm the contact on file |
| Phone system admin and porting details | Numbers lost or calls misrouted at cutover | The practice | Read the porting authority from the carrier portal |
| Network map and the documentation of every closet | Cabling guesswork on the first fault | IT writes it; the practice keeps a copy | Ask for it before the old company's last day |
The sequence that works is four steps across about a month. Week one: the new company and the old one meet, and the inventory above is filled in with the practice present. Week two: the practice takes ownership of every account in its own name, and a verified backup of the practice database and the imaging archive is restored on a test machine. Week three: the new company shadows the helpdesk, takes over monitoring, and runs the first non-clinic-day patch window. Week four: cutover on a light clinic day, with a scan, a records capture and a claim tested first; the old company's handoff is in writing and their contact stays open until the first full clinic day has run. Two lines of the HIPAA Security Rule are worth reading beside this inventory: 45 CFR 164.312(a)(2)(i) reads "Assign a unique name and/or number for identifying and tracking user identity," and 164.308(a)(3)(ii)(C) asks for "procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends." How those standards apply to an outgoing IT company is your compliance adviser's reading; the inventory gives the adviser the facts to read them against.
The general steps for any dental office are in switching dental IT providers without downtime; the selection side is in our guide on how to choose a dental IT company.
What to ask your IT provider before you sign an orthodontic support agreement
These questions are written for a shortlist meeting, and they are different from the fifteen-point scorecard in the technology guide and the five questions on our orthodontic page: those test knowledge, these test how the company will actually work with you. Ask them of everyone, including us. A good answer is specific to your office; a bad one could be given to any business.
About your systems
- Walk me through a records appointment on our practice system, from capture to the chart. Where could it fail, and which failure would be yours?
- Our practice system is Dolphin / OrthoTrac / Cloud 9 / topsOrtho / Edge Cloud / Greyfinch]. What does it need from you that a general dental system does not?
- Which of our vendors will you open tickets with on our behalf, and which do you expect us to call?
- When the vendor's support desk is closed and ours is open, what do you do in that window?
About the clinic day
- Which day and hour do you patch, and what is your rule for a records day?
- When one chair's computer is slow at ten in the morning, what happens between our call and the fix?
- How do you decide whether a fault is yours or the vendor's, and who tells us?
- What do you monitor on our server or cloud sign-in before the doors open, and what did it catch last month for an office like ours?
About scanners and imaging
- What do you check before a new scanner is added to the bay, and what do you measure at the chairs?
- Who approves Windows updates on scanner PCs and capture stations?
- Describe the last time you restored an orthodontic imaging archive for a client: when, from where, and how long it ran.
- How do you keep guest and parent devices off the scanner network?
About accounts and the exit
- Which admin accounts will be in our name on day one, and which in yours?
- How do you add a new assistant and remove one who leaves, across email, the practice system and every portal?
- What is in the monthly report, and can we see one from an existing orthodontic client with the name removed?
- If we leave you, what do we receive, and how long does the handoff take?
For the contract itself, from term to exit to insurance, our 20-question pre-signing list for dental IT contracts covers the ground any dental office should check.
What to verify before you sign
Before you sign with any dental IT company, verify four things in writing rather than in conversation: orthodontic work you can see (project pages or references on your practice system), a scope that matches the ten-item table above, a pricing structure you can read without a calculator, and exit terms that return your accounts, data and documentation within a stated period.
- Orthodontic work you can see. Ask for project pages or references from offices on your practice system, not from dentistry in general. An orthodontic startup, a satellite added to an existing practice and a server-to-cloud move are three different proofs; ask which they have done.
- Scope in writing. Hold the proposal against the scope table in the first section. Wi-Fi surveys, scanner PC policy, restore tests, satellite coverage and vendor coordination should each appear as a line, not as "full support".
- Pricing structure. Understand what the monthly figure covers and what is quoted separately (hardware, cabling, licensing and projects usually are), whether it moves with workstations, offices or people, and whether a new scanner or a new satellite changes it. Our page on managed IT services for dental practices explains how a managed plan is built.
- Who answers. Ask whether first-level support is in-house or outsourced, where the engineers sit, and how onsite work is arranged for your addresses.
- Exit terms. The handoff inventory above should be a contractual deliverable at exit, with a period stated.
- Independent reading. Compare more than one company. Our list of the best dental IT companies is written to be checked against each company's own site, and the selection method is in the provider guide linked above.
A 2014 column in Orthodontic Products, relaying the view of a dental IT company's founder, put the case for specialist support plainly: the modern orthodontic practice "needs highly integrated systems. This is not a job for a one-, two-, or three-man team." A decade later the systems are more integrated, not less; the test is still whether the company in front of you can show you an orthodontic office it keeps running.
What should the monthly report from your IT company show an orthodontic owner?
A monthly report worth reading has one page for the owner: tickets by category with vendor-bounced faults counted separately, the date and duration of the last restore test of the practice database and imaging archive, patches applied and when, version dates, Wi-Fi survey results at scanner chairs, backup copy counts, account changes against the staff list, and open vendor tickets.
| Line on the report | Why an orthodontic owner needs it | What a good month looks like |
|---|---|---|
| Tickets by category (workstation, Wi-Fi, scanner, imaging, practice system, accounts) | Shows where clinic time is going and whether the same chair or scanner keeps appearing | Repeat faults named and closed, not re-opened |
| Faults that involved a vendor, and who owned them | Proves the bounce is handled | Each one lists the vendor ticket number and the outcome |
| Restore test: date, what was restored, how long it took | The only proof a backup works | Within the month, both the database and the imaging archive |
| Patches applied, with the window used | Shows updates stayed off clinic days | Non-clinic day, scanner PCs listed separately with the maker's approval noted |
| Windows Server and SQL Server versions with their end dates | The upgrade clock for Dolphin and OrthoTrac offices | Dates stated, with a plan if under twelve months |
| Wi-Fi survey at scanner chairs | Scanners are clinical devices | Signal per chair, re-measured after any change to the room |
| Backup copies and offsite status | Retention for long treatments | Copy count and the offsite job result |
| Accounts added and removed against the staff list | Departed staff with live logins are the commonest access failure | Zero unexplained accounts across email, practice system and portals |
| Internet failover test result (if you have a second line) | A cloud practice system is only as reliable as the line | Tested, with the switchover time |
The HIPAA Security Rule's information system activity review standard, 45 CFR 164.308(a)(1)(ii)(D), requires procedures "to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports." A monthly report that lists account changes and incidents is one practical way an IT company helps a practice meet that habit; what the rule requires of your practice is your compliance adviser's call. Backup lines on the report connect to the same rule's data backup plan standard, which asks for "retrievable exact copies of electronic protected health information". The restore-test method itself is in our backup and disaster recovery checklist for dental offices.
How Legend Networking works with orthodontic practices
Legend Networking works from Dallas, Texas, and has served over 3,500 practices since 2004: 22+ years in dental IT. Its engineers are in-house, with no outsourced first-level triage; the helpdesk is staffed 24/7 at 1-800-794-1588, alongside 24/7 monitoring. Onsite dispatch is by appointment across served dental markets, and support is remote-first nationwide. Its Google reviews stand at a 4.8 rating across 173 reviews.
On the orthodontic side, Legend supports the IT environment for Dolphin Imaging and for the imaging systems DEXIS, Vatech, Carestream and Planmeca/Romexis; practice systems such as Cloud 9, OrthoTrac, Edge Cloud, topsOrtho and Greyfinch are applications their vendors support, and the IT side around any of them is the computers, network, server or cloud access, backups and accounts described above. Three orthodontic projects on Legend's project pages show the range: a new orthodontic office on Potranco Road in San Antonio, set up for opening day, an orthodontic practice opening in Lewisville, Texas and an orthodontic startup launch in Jessup, Maryland. The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps.
If you want the general service picture first, start with dental IT support; if you want the picture for your own market, our note on specialty practice IT in Dallas shows how a city changes the detail, and the locations pages carry dental IT support near you.
Frequently asked questions
Does an orthodontic practice need a different IT company than a general dental office?
The equipment is similar; the failure points are not. An orthodontic office runs an open bay where Wi-Fi is clinical, scanners that upload to a vendor's cloud, a records imaging chain, an archive that grows with every new start, and often a satellite. Orthodontist IT support names each of those in the agreement and works around clinic days.
Should our IT company or the software vendor own a ticket that involves both?
The IT company should own it. The vendor supports its application and will not manage your server, network or capture station. A good agreement says the IT company opens the vendor ticket with you, stays on the call, and reports back. "Call Dolphin yourself" is the sign of a provider that has not worked in orthodontic offices.
Does an IT company need to know Cloud 9, Dolphin or OrthoTrac to support an orthodontic practice?
It needs to know what each system asks of the platform it runs on: a Windows server, SQL Server and a domain for Dolphin and OrthoTrac, a dependable internet line and firewall at every office for cloud systems such as Cloud 9, Edge Cloud or topsOrtho. The application itself stays with the vendor; the IT company must know the boundary.
Can an IT company support an orthodontic practice remotely?
Most of the work is remote: monitoring, patching, account changes, vendor tickets and helpdesk calls. Some is not: cabling, a Wi-Fi survey at the chairs, scanner and capture-station hardware, server replacement. Ask any provider how onsite work is arranged for your address and how a satellite office is covered on its clinic day.
What happens to our iTero or TRIOS scanner when we change IT companies?
Nothing, if the handoff records the Wi-Fi network the scanner joins, the maker's account the scanner is registered to, and the firewall ports it needs. Keep the scanner accounts in the doctor's name, not an IT employee's. After cutover, scan a test case from the farthest chair and confirm it reaches the lab or aligner portal.
How long does switching IT companies take for an orthodontic office?
About a month, run in four steps: a joint inventory with the outgoing company, the practice taking ownership of every admin account and a test restore of the database and imaging archive, the new company shadowing the helpdesk and running the first patch window, then cutover on a light clinic day with a scan, a records capture and a claim tested first.
Who should own our domain, Microsoft 365 and vendor portal logins?
The practice should. The domain registrar, a break-glass Microsoft 365 or Google Workspace admin, firewall and static IP details, scanner accounts, aligner and lab portals and backup encryption keys all belong in the practice's name, with the IT company working through named accounts. Confirm this in the first month of any agreement, not at the exit.
What should we ask an IT company about our satellite office?
Ask how the satellite reaches your practice system (a secured connection or hosted session for a server system, a dedicated line and firewall for a cloud one), who is reachable on its clinic day if the main office is closed, how a scanner moved between offices is reconnected, and whether the records workflow has been tested from the far office before the first patient.
How do we check an IT company's orthodontic experience before signing?
Ask for project pages or references from offices on your practice system and of your shape: a startup, a satellite added, or a server-to-cloud move. Then ask them to walk through a records appointment on your system from capture to the chart. A company with orthodontic experience answers in detail; a generalist answers in generalities.
Do we still need an IT company if our practice software is in the cloud?
Yes, the work moves rather than disappears. A cloud practice system puts the weight on the internet line, its failover and the firewall at every office, while scanners, capture stations, the imaging archive, workstations, accounts and backups of anything local stay in the building. The IT company owns all of that, plus the sign-in security on every vendor portal.
The bottom line
Take the scope table, the warning signs and the handoff inventory into your next shortlist meeting, including ours. If you would rather have your current setup looked at first, ask for a Free Dental IT Assessment: written findings and prioritized recommendations on your computers, software, network security, backups and performance. Bring the scope table; it tells you which findings matter most in an open bay. How Legend approaches IT support for orthodontic practices is on its own page, and the general service is described under dental IT support.

