Oral Surgery Practice Technology: The IT Guide for OMS Offices
It is a Tuesday surgery block: three IV sedation cases before lunch, a referring dentist's CBCT on a disc at the front desk, a connection error on the suite 2 monitor station and a ringing post-op line. This guide is for owners and practice administrators of oral and maxillofacial surgery (OMS) offices. It covers one side of oral surgery practice technology, practice IT: computers, network and software. Clinical equipment and clinical decisions stay with the surgeon.
If you are choosing a provider rather than planning, our page on dental IT support for oral surgery practices is the place to start. This guide gives you a technology map of an OMS office with a who-to-call column, the responsibility split your software vendor already puts in writing, the rooms that change the IT plan, a restore list, a multi-site table, the upgrade dates that matter in 2026 and 2027, a security checklist, an opening timeline and a 15-question scorecard for any IT provider. It is written from the experience of Ian Lynch, who has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps at Legend Networking, which has 22+ years in dental IT (since 2004).
In this guide
- What makes IT in an oral surgery office different from a general dental office?
- What does an oral surgery practice run? The technology map
- Server, hosted or cloud: what does your oral surgery software need from IT?
- Which rooms change the IT plan in an oral surgery office?
- How do referrals and their images get into the chart?
- What has to be restorable in an oral surgery office?
- How should a multi-office oral surgery group connect its satellites?
- Which dates should be on an oral surgery practice's upgrade calendar?
- What does security look like for an oral surgery practice?
- Opening or expanding an oral surgery office: what's the IT sequence?
- Which oral surgery practices has Legend worked with?
- What should an oral surgery practice ask an IT provider? The 15-question scorecard
- What does IT cost for an oral surgery practice?
- The bottom line
- Frequently asked questions
- The bottom line
What makes IT in an oral surgery office different from a general dental office?
An oral surgery office runs the same IT foundations as a general dental office, under heavier conditions. Patients arrive by referral, images move in from and back out to other offices, sedated cases tie a vitals monitor to a workstation, the data includes medical history and anesthesia records, and a surgery day cannot simply be moved when a system fails.
None of these differences is clinical advice. Each one changes what your computers, network and backups have to do. The table compares the two kinds of office from the IT side only.
| Area | General dental office | Oral surgery office | What it means for IT |
|---|---|---|---|
| Patient flow | Recall-driven: hygiene and restorative visits booked months ahead | Referral-driven: consults and surgery booked from referring dentists' letters and images | Referral intake becomes a daily workflow with its own queue, computer and phone line |
| Imaging | Bitewings, periapicals, some panoramic images | Panoramic images, CBCT and clinical photos, coming in from referrers and going back out | A larger imaging store, a CBCT viewer on more machines and a safe way to open outside media |
| Devices | Sensors and intraoral cameras | Plus vitals monitors connected to workstations, signature pads, and ID and insurance-card scanners | More devices that depend on one specific computer, port or driver |
| Data | Dental chart, x-rays, insurance claims | Plus medical history, anesthesia records and medical billing details | More sensitive data per patient, so access control and restore testing matter more |
| Software | A wide choice of practice software | A small specialty market, often server-based or hosted | The vendor supports the application; the server, network and backup sit with you |
| Schedule | Most visits can be rebooked | Sedated surgery blocks with staff, patients and escorts committed | Outages cost more, so the downtime plan and spare equipment need more thought |
| Locations | Usually one office | Often a main office with satellites, and surgeons who rotate | Remote access, imaging across sites and the same setup in every suite |
The vendor of one widely used OMS system puts the stakes plainly. Its technician guide calls WinOMS "a critical systems application that must be running every day with as little down time as possible." That sentence is the reason the rest of this guide exists.
Next step: keep this table beside you while you fill in the technology map in the next section.
What does an oral surgery practice run? The technology map
An oral surgery practice runs practice software (on a server, hosted or cloud), OMS imaging and CBCT, sedation-monitor workstations, consent and ID scanning, referral intake, phones, payments, a network closet and backup. Each layer lives in a different place, needs different work from IT and has a different first call when it stops.
This is the reference version. It names systems an OMS office may run; yours will be a subset. Systems named here are products your practice runs, not products this page rates.
| Layer | Systems an OMS office may run | Where it lives | What IT must do | Who to call first |
|---|---|---|---|---|
| Practice software and chart | WinOMS (on a server or WinOMS Hosted), Sensei Cloud, OMSVision, DSN, CareStack, iDentalSoft, MaxilloSoft | A server in the office, a vendor's hosted session, or a vendor cloud | Server, Windows, database host, workstations, internet line, user accounts | The vendor for application errors; IT for server, network and computer problems |
| Imaging and CBCT | Carestream imaging, CS OMS Imaging, Invivo, Sidexis, Planmeca Romexis | An imaging server or share, capture stations and viewing workstations | Storage, capture drivers, graphics on viewing PCs, imaging backups | IT first; the imaging vendor for software faults |
| Anesthesia record and vitals monitors | The practice software's anesthesia module with Criticare, Mindray, Zoe/CASMED or Mortara monitors | A workstation in each surgical suite connected to the monitor | The workstation, its port or adapter, its network connection and its updates | IT for the workstation and network; the monitor's manufacturer or biomedical service for the monitor |
| Surgical planning | Planning software such as Blue Sky Plan or coDiagnostiX | A planning workstation, sometimes with a licence key | The workstation and its graphics, storage and licence | IT for the computer; the software vendor for the application |
| Consent and forms | Topaz signature pads, digital forms, PDF consents | Front desk and consult-room workstations | Drivers, USB ports, the forms software's version requirements | IT |
| Document and ID scanning | TWAIN scanners for insurance cards, IDs and referral letters | Attached to front-desk computers | Drivers and placement; the WinOMS documents state network scanners are not supported | IT |
| Referral intake | Online referral forms, e-fax, email, disc and USB | Vendor clouds plus one intake computer | A safe intake PC, the e-fax and email accounts, a viewer for outside images | IT for the PC and accounts; the form or fax vendor for their service |
| Phones and post-op line | VoIP or carrier phone service, after-hours routing, fax lines | A cloud phone service or an on-site system | The voice network and quality-of-service settings | The phone provider; IT for the network side |
| Payments | Card terminals and payment apps tied to the practice software | Front desk | A locally installed app or driver, network access | The payment vendor; IT for the computer |
| Network, server room and security devices | Firewall, switches, Wi-Fi, UPS units, cameras and door access | The network closet and every room | Design, separate networks, monitoring, updates | IT; the internet provider for a line outage |
| Backup | Local backup device plus an offsite copy | The closet and an offsite location or cloud | Backup jobs for the database and imaging, restore tests | IT |
Three notes for the map. Legend supports the IT environment for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. WinOMS, Sensei Cloud, OMSVision, DSN, CS OMS Imaging and the other systems named are software your practice runs: an IT provider keeps the computers, network, server, backups and accounts around them working, and the vendor supports the application. And the monitor row has a cloud wrinkle: Sensei's help center states its Sensei Cloud vitals integration "is currently only available for Criticare Technologies, Inc. monitors" (checked 26 October 2026).
For choosing practice software itself, see our practice management software comparison. For the planning row, check the planning software vendor's current workstation requirements before you buy the computer. For the phone row, see our dental phone solutions page.
Vitals monitors are medical devices. Change nothing on the monitor itself without the manufacturer or your biomedical service.
What those three jobs mean for a WinOMS server is in our guide to WinOMS server vs hosted vs cloud; what they mean for the suite network is covered in the rooms section below.
Now fill in your own map. One row per system is enough. The point is that every row has a name in the last two columns.
| Layer | Product and version | Where it lives | Vendor support page | Who calls the vendor | Last reviewed |
|---|---|---|---|---|---|
| Practice software | ____ | ____ | ____ | ____ | ____ |
| Imaging and CBCT | ____ | ____ | ____ | ____ | ____ |
| Monitor stations | ____ | ____ | ____ | ____ | ____ |
| Consent, forms, scanners | ____ | ____ | ____ | ____ | ____ |
| Referral intake | ____ | ____ | ____ | ____ | ____ |
| Phones and fax | ____ | ____ | ____ | ____ | ____ |
| Network and closet | ____ | ____ | ____ | ____ | ____ |
| Backup | ____ | ____ | ____ | ____ | ____ |
Who do you call when something stops working: the vendor or IT?
The software vendor owns the application and its licence; IT owns the server, Windows, network, Wi-Fi, backup and accounts; the monitor's manufacturer owns the device. WinOMS's own technician guide puts the network on the local technician. When you cannot tell which layer failed, call IT first and let IT bring in the vendor.
Before either call, write down four things: the time it started, the computer or room, the exact message on screen, and whether the internet and the other systems were working. That note shortens most support calls. It also helps stop the vendor and IT handing the problem back and forth, because the evidence of which layer failed is on paper.
| Symptom | Likely layer | Call first | Have ready |
|---|---|---|---|
| The practice software will not open on any computer | Server, database or hosted session | IT, then the vendor once the server checks out | When it started, the error text, whether imaging also fails |
| One suite's monitor station shows a connection error | That workstation, its port or adapter, or its network cable | IT; the monitor's manufacturer for the device | Suite number, the exact message, what changed since the last case |
| CBCT studies open slowly in the consult room | Imaging store, network or viewing PC | IT | Patient chart number, which rooms are affected |
| A referral disc will not open | The intake PC or the viewer | IT | Where the disc came from; do not try it on other computers |
| The hosted or cloud session freezes for everyone | Internet line or firewall | IT; the internet provider if the line is down | A speed test result and which offices are affected |
| Calls drop while images or backups upload | Network quality-of-service | IT, then the phone provider | Time of day and what was uploading |
| The signature pad or card scanner stopped working | Driver, USB port or a recent update | IT | Computer name and any recent update |
| Staff are locked out of email or a vendor portal | Accounts and multi-factor authentication | IT for email; the vendor for its own portal | Username and which phone holds the authenticator |
Want this map filled in for your office? A Free Dental IT Assessment gives you written findings and prioritized recommendations on your computers, software, network security, backups and performance.
Server, hosted or cloud: what does your oral surgery software need from IT?
Oral surgery software comes in three shapes: on a server in your office, in a hosted session run by the vendor, or in a browser cloud. Each shape moves some work from your server to your internet line, and none moves all of it. Imaging capture, monitor workstations, signature pads and document scanners stay in your office in every case.
With software on a server, your IT provider owns the server, its operating system, the database host, the backup and the network. WinOMS is the common example: Carestream "strongly recommends running the WinOMS database on a dedicated server," and its 10.1.x requirements state that Remote Desktop Services "is not a supported environment." With hosted software, the server moves to the vendor, but the WinOMS Hosted requirements say a hosted workstation "is not suitable for image acquisition," and network scanners are not supported, so imaging and scanning stay local. With browser-cloud software, device connectors still run on local computers. In both hosted and cloud setups the internet line becomes part of the clinical workflow, so plan a second circuit with automatic failover and read our guide to what to check when the office internet goes down.
The detail belongs elsewhere. Server specs, backup routines, hosted bandwidth and the WinOMS version 10 conversion are in our WinOMS server vs hosted vs Sensei Cloud guide. The general server-or-cloud decision is in dental server replacement vs cloud migration. OMSVision has a long history in the specialty: Discus Dental Software launched it in 2003, "created in partnership with the American Association of Oral and Maxillofacial Surgeons (AAOMS)," per the 2003 press release. For OMSVision, DSN and other systems, check the vendor's current requirements before you buy hardware: vendors update these documents, and the version on your desk may be out of date.
Next step: write the shape (server, hosted or cloud) and the version into the first row of your map.
Which rooms change the IT plan in an oral surgery office?
Seven rooms change the IT plan: the surgical suites, recovery, the CBCT and panoramic room, the consult room, sterilisation, the front desk and check-out, and the network closet. Lead each room's plan with its IT need: where the computer sits, which data drops it needs, what power and UPS it needs, and which devices connect to it.
Most office-design advice covers zones, medical gas and sterilisation flow and stops before the network. This list starts where that advice stops. Use it with your architect and low-voltage contractor while the drawings can still change, and use the room-by-room dental office technology plan for the rooms every dental office shares.
| Room | What the room adds to the IT plan | Ask before the drawings close |
|---|---|---|
| Surgical suite | A monitor-station workstation on a wired connection, placed where the monitor cable can reach it; a display for imaging; power on a UPS for the workstation | Where does the monitor sit, and how far is it from the workstation? |
| Recovery bay | A workstation or tablet for the anesthesia record if staff chart there; follow the camera placement in your practice's written policy | Will staff chart in recovery, and on which device? |
| CBCT and panoramic room | The acquisition PC, a wired connection to the imaging store, dedicated power as the device maker specifies, and space for the PC outside the exposure area | What does the imaging vendor specify for the acquisition PC and its network? |
| Consult room | A viewing workstation with the CBCT viewer and enough graphics, plus a large display for treatment discussion and a signature pad | Which viewer will run here, and what does it need? |
| Sterilisation | Usually a printer or tablet for logs; keep it on the clinical network only if it needs the practice software | Does anything in sterilisation need the server? |
| Front desk and check-out | Scanners for IDs, insurance cards and referral letters, signature pads, the card terminal, phones, and the referral intake computer | Which computer receives referral discs and e-faxes? |
| Network closet | Firewall, switches, the server or local backup device, UPS units with shutdown software, ventilation and a locked door | Is there space, power, cooling and a lock for the rack? |
Two rules apply across every room. Keep clinical devices off the guest Wi-Fi and the patient-TV network; the full segment plan is in our guide to connecting sedation monitors and segmenting the surgical network. And prefer wired connections for clinical computers: the WinOMS requirements state that "Wireless network connections are not recommended. For best performance, use hard-wired connections."
Before the low-voltage plan is signed
- Every surgical suite has a wired drop and UPS power for the monitor-station computer
- The CBCT acquisition PC has a wired drop and a place outside the exposure area
- Consult rooms have a viewing workstation that meets the imaging vendor's spec
- The front desk has a named referral intake computer and scanners for IDs and cards
- Guest Wi-Fi and patient TVs are on their own network, away from clinical devices
- The network closet has space, cooling, a lock and UPS units with shutdown software
- Camera placement follows the practice's written policy
If you are designing the network itself, our page on secure dental office network design and our guide to how a dental office network is set up cover the general plan.
How do referrals and their images get into the chart?
Referrals reach an oral surgery office by online form, fax, email, secure link, disc and USB, often all in the same week. Route every one into one intake queue, open outside media on one safe intake computer, and send images and letters back to the referring dentist through the channel they came in on, unless that channel is unsafe.
That is the whole IT side of referrals in three moves, and each needs an owner. Name the person who empties the intake queue each morning. Name the computer that opens discs and USB drives, keep it updated and keep it away from the server. And write down how each regular referring office prefers to receive reports and images, so the front desk does not invent a new method every time.
The step-by-step setup, from the referral form to the referring-doctor phone line, is in our guide to setting up oral surgery referral intake. When images arrive but do not appear in the chart, start with dental imaging integration troubleshooting. And if referral letters travel by email, read about email security for dental offices.
What has to be restorable in an oral surgery office?
Five things have to come back after a failure: the practice-software database, the imaging store (CBCT, panoramic images and photos), the anesthesia records, scanned referrals and letters, and the server's own configuration. A backup counts only when a restore of each has been tested, on a schedule, by someone you can name.
Each item has its own trap. Use this list to check your backup report line by line.
| What must be restorable | Why it is easy to miss | What to check |
|---|---|---|
| Practice-software database | Some databases cannot be copied while running; the WinOMS requirements state "Live Back up of data is not recommended" | The backup method your software vendor documents, and the date of the last test restore |
| Imaging store | It is large and often sits on a different share or server from the practice software | That imaging is in the backup at all, and how long a full restore takes |
| Anesthesia records | They may live in the practice-software database or in a separate module | Where your system stores them, and that a restored record opens |
| Scanned referrals and letters | They may sit in a document folder outside the database | That the document folder is included |
| The server's configuration | Accounts, shares, licences and settings take hours to rebuild by hand | A documented rebuild or an image-level backup of the server |
Keep one copy offsite and out of reach of the office network, and put the server and backup device on UPS units with shutdown software, which the WinOMS requirements also recommend. How long you keep records is set by your state; check your dental board.
The WinOMS backup routine is in the WinOMS server, hosted and cloud guide linked in the section above. A restore-testing routine for any dental office is in the dental backup and disaster recovery checklist, and our backup and recovery services page covers the service side. What to do when the server fails during a case is covered in our surgery-day downtime plan.
How should a multi-office oral surgery group connect its satellites?
Choose one connection method per system and write it down. With software on a server, satellites reach the main office over a site-to-site VPN. With hosted or cloud software, each office connects to the vendor over its own internet line. In every case imaging capture, monitor stations, scanners and signature pads stay local at each site.
The table shows what each method moves, what it leaves behind and how it fails. The last column is the question to ask the vendor before you open or connect a satellite.
| Method | What moves between sites | What stays local at each site | How it fails | What to ask the vendor |
|---|---|---|---|---|
| Practice software on a server at the main office | Satellite workstations reach the server over a site-to-site VPN | Imaging capture, monitor stations, scanners, pads, printers | If the main office's internet or the VPN drops, the satellites lose the software | Which remote-access methods are supported (WinOMS rules are in the spoke guide) |
| Hosted practice software | Every site opens sessions on the vendor's servers | Imaging capture, monitor stations, scanners, pads | Each site depends on its own internet line and latency | What bandwidth and latency each site needs at peak |
| Cloud practice software | Every site uses the browser and the vendor's cloud | Device connectors on local PCs, monitor stations, scanners | Each site depends on its own internet line | How monitor PCs are registered to each location |
| Imaging across sites | Studies move to a central store or stay per site | Capture PCs and local caches | Slow links make large studies slow to open at a satellite | How a CBCT study taken at one site opens at another |
For the cloud row, Sensei's help center describes monitor PCs registered as a "Connected PC" for each practice location, which is the kind of detail to confirm before a satellite opens.
Surgeons who rotate between offices
A surgeon who works in three offices should find the same thing in each: the same login, the same imaging access and the same monitor-station setup. Standardise the workstation model, the monitor connection and the viewer version across every suite, so a station that works in one office works in the next. Keep a one-page site sheet for each office with the internet provider, the circuit IDs, the closet location and the local contact.
Groups with ten or more offices have different needs again; see IT for multi-location dental groups and our DSO IT support services guide.
Which dates should be on an oral surgery practice's upgrade calendar?
Four Microsoft dates matter now: Windows 10 support ended on 14 October 2025, SQL Server 2016 extended support ended on 14 July 2026, Windows Server 2016 extended support ends on 12 January 2027, and SQL Server 2019 extended support ends on 8 January 2030. Plan server, database and workstation replacements around them.
Windows Server 2016 is the one to act on this quarter. Its extended support ends on 12 January 2027 (Microsoft Lifecycle). WinOMS 10.1.x still lists Server 2016 as supported, so the Microsoft date is the one that binds; plan the server replacement and any version 10 conversion together.
| Date | What ends | What it means in an OMS office | Action |
|---|---|---|---|
| 14 October 2025 | Windows 10 support (Home and Pro) | Front-desk, consult and monitor-station PCs still on Windows 10 no longer get security updates | Replace or upgrade them; check that the practice software supports the new version |
| 14 July 2026 | SQL Server 2016 extended support | Any system in the office still on a SQL Server 2016 database is out of support | Ask each vendor which database version its current release needs |
| 12 January 2027 | Windows Server 2016 extended support | A WinOMS or imaging server on Server 2016 loses security updates | Replace the server before the date; plan any software upgrade at the same time |
| 8 January 2030 | SQL Server 2019 extended support | WinOMS version 10 converts its database from Sybase to Microsoft SQL Server; the 10.1.x requirements list SQL Server 2019 | Note the date in the server plan now |
| With the server replacement | WinOMS 9.x (Sybase) to version 10 (SQL Server) | The conversion needs planning and downtime | Plan it with the server replacement; see the spoke guide |
| At every PC refresh | Monitor-station workstations | The WinOMS requirements list a DB9 serial port for the vitals monitor | Replace only with a machine that keeps a supported serial port or adapter; see the sedation-monitor guide |
As of 26 October 2026, these dates are checked against Microsoft's lifecycle pages and the WinOMS 10.1.x requirements. Vendors change their supported lists, so re-check before you buy.
For the Windows 10 side, see a Windows 10 exit plan for dental offices. For the day the old server is switched off, see server shutdown mistakes to avoid.
What does security look like for an oral surgery practice?
Security in an oral surgery practice protects a richer record than a general office holds: imaging, medical history, anesthesia records and medical billing details, spread across more vendors. In practice that means multi-factor authentication everywhere, protected workstations including monitor PCs, segmented networks, controlled vendor access and an offsite backup the office network cannot change.
Recent cases show where the exposure sits. Three oral surgery practices reported breaches in 2025 and 2026, according to HIPAA Journal, including exposed imaging files after a network attack and a vendor's phished email accounts; our surgery-day downtime plan walks through what each teaches.
The OMS data profile
An OMS patient record usually holds more than a dental chart: CBCT studies and clinical photos, a medical history and medication list, anesthesia records, ID and insurance details for medical as well as dental billing, and referral letters from other offices. Every one of those items lives somewhere: in the database, on the imaging store, in a document folder, in an email account or in a vendor's cloud. Knowing where each lives is the first security control.
Which vendors in an OMS office hold patient data?
List every outside company that stores, receives or can reach patient information. In an OMS office that usually includes:
- the practice-software vendor or host (for hosted and cloud systems)
- the imaging cloud or image-sharing service
- the online referral form host
- the answering service for the after-hours line
- the e-fax service
- the email provider
- the IT provider
Ask your compliance adviser which of these require a business associate agreement (BAA), and keep the signed copies with the list. Review the list when you add a vendor and at least once a year.
What an oral surgery practice should have in place
- Multi-factor authentication on email, remote access and every vendor portal
- Endpoint protection on every workstation, including monitor-station and acquisition PCs
- Operating-system updates installed as soon as they are released, as the WinOMS requirements state
- The server and imaging store on their own network segment, away from guest Wi-Fi
- Vendor remote access switched on only when needed, and logged
- An offsite backup copy the office network cannot change or delete
- Phishing training for the front desk and referral coordinators
- Practice-software roles that give each person only the access their job needs
- Logs kept and reviewed for the server, firewall and email
- A printed incident contact list: IT, the software vendor, the cyber insurer and your compliance adviser
Cyber insurers now ask for many of these controls; see what cyber insurers require of dental practices. The January 2025 HIPAA Security Rule proposal is still a proposed rule as of 26 October 2026 (Federal Register, RIN 0945-AA22); our article on HIPAA Security Rule updates for dental practices tracks it. For the service side, see dental cybersecurity services and HIPAA technical safeguards for dental practices. If the worst happens, start with dental ransomware recovery.
Opening or expanding an oral surgery office: what's the IT sequence?
Bring IT in at the floor plan, before the electrical and low-voltage drawings close. From there the sequence runs on a timeline: cabling and the closet about 90 days out, software vendors and two internet circuits at 60 days, hardware staged and backups tested at 30, and a full dry run two weeks before the first surgery day.
The dates below are a planning pattern, not a promise; long-lead items such as internet circuits set the real pace. Start the clock when the lease is signed.
IT sequence for a new or expanded oral surgery office
- 1Lease and designWalk the floor plan with IT; mark every suite, the CBCT room, consult rooms, the front desk and the closet from the room list above.
- 2About 90 days outCabling and the network closet are built; the monitor-station workstation spec is agreed with the monitor's manufacturer.
- 3About 60 days outKick off with the practice-software and imaging vendors; order two internet circuits from different providers.
- 4About 30 days outHardware is staged and configured; the first backup runs and a test restore is done.
- 5Two weeks outDry run: a test record written into the practice software from each monitor station, a CBCT opened in every suite, phones and fax tested, and an internet failover test.
- 6Opening dayIT on call for the first surgery block, with the site sheet and the vendor contacts printed.
Ecker Oral Surgery in Miami is a recent example of this kind of project: Legend's March 2026 project post gives a first look at its technology buildout, covering the network rack, computers, AV systems and security surveillance.
The network-specific steps for suites and monitor stations are in our sedation-monitor network guide. The general opening plan is in our dental startup IT setup guide, and the service page is dental startup IT. For rooms every dental office shares, use the dental office technology plan.
Which oral surgery practices has Legend worked with?
Legend's project posts include Ecker Oral Surgery in Miami (a first look at the technology buildout), East Austin Oral Surgery in Austin (the collaboration with Dr. Matthew Largent ahead of launch, and the grand opening) and AB Dental and Oral Surgery in San Antonio (welcomed to Legend in November 2025). Mystic Smiles in Carrollton is a multi-specialty practice with a general dentist, a pediatric dentist and an oral surgeon, followed from buildout to opening.
What should an oral surgery practice ask an IT provider? The 15-question scorecard
Ask questions an answer can be checked against: who owns the network and backup, when a restore was last tested, which servers face the January 2027 date, how monitor stations are set up, what the second internet circuit is and which vendors hold patient data. A good provider answers with names, dates and documents.
Start with these five:
- Which of our systems do you support, and who calls each vendor when something breaks?
- Who owns our network and our backup, given that our software vendor says it does not?
- How do you back up our practice-software database, and when did you last test a restore?
- How do you set up and test monitor-station computers, and what do you never touch on the monitor?
- What sits on its own network segment in our office, and why?
The full scorecard follows. Score each answer as good, partial or red flag.
| # | Question | What a good answer sounds like | Red flag |
|---|---|---|---|
| 1 | Which of our systems do you support, and who calls each vendor when something breaks? | A system-by-system answer that separates what they support from what the vendor supports, and names who makes the vendor call | "We support everything" with no list |
| 2 | Who owns our network and our backup, given that our software vendor says it does not? | "We do," with the backup jobs, the monitoring and the restore tests named | Pointing back at the software vendor |
| 3 | How do you back up our practice-software database, and when did you last test a restore? | The method the vendor documents, a schedule and the date of the last test restore | "The backup runs every night" with no restore date |
| 4 | How do you set up and test monitor-station computers, and what do you never touch on the monitor? | They own the workstation, port, adapter and network; the monitor stays with its manufacturer or biomedical service | Offering to change settings on the monitor |
| 5 | What sits on its own network segment in our office, and why? | A short list: server and imaging, clinical workstations, phones, cameras, guest Wi-Fi | One flat network for everything |
| 6 | Which of our machines run Windows Server 2016 or older, and what is the plan before 12 January 2027? | A list of machines and a dated replacement plan | Not knowing which servers you have |
| 7 | If we are on WinOMS 9.x, how will you plan the version 10 conversion? | A plan that ties the conversion to the server replacement, with the vendor's current requirements in hand | "We'll do it when the vendor makes us" |
| 8 | If our software is hosted, what bandwidth and latency do we have at peak, and what is our second circuit? | Measured figures for each site and a second circuit from a different provider | No measurement and no second circuit |
| 9 | How do referral discs, USB drives and links get opened safely? | One named intake computer, kept updated and kept away from the server | "Any computer at the front desk" |
| 10 | What happens in the first minutes if the server or internet fails during a sedation case? | A written downtime plan the clinical team has seen and practised | No plan, or a plan only IT has read |
| 11 | How do surgeons and satellites get remote access? | A method the software vendor supports, with multi-factor authentication | Remote desktop open to the internet |
| 12 | Which of our vendors hold patient data, and where are their agreements? | A current list, with the agreements kept by the practice | "That's not our area" |
| 13 | What security runs on every workstation and on email? | Endpoint protection, updates, multi-factor authentication and phishing training, with reports | Antivirus only |
| 14 | Who answers when we call, and how do you reach us onsite? | Named engineers in-house, staffed hours stated, and an onsite arrangement for your area | A ticket queue with no named people |
| 15 | What is in the monthly fee, and what is quoted separately? | A written scope with the exclusions listed | A single figure with no scope |
For reference, Legend's answer to question 14: in-house engineers, with no outsourced first-level triage; a helpdesk staffed 24/7 at 1-800-794-1588; and onsite dispatch by appointment across served dental markets, remote-first nationwide. For question 15: hardware procurement, major cabling projects and software licensing are quoted separately.
For the general version of this list, see the 20 questions to ask before signing a dental IT contract.
Score your current IT against these 15 questions, then book a Free Dental IT Assessment.
What does IT cost for an oral surgery practice?
Legend's published price: Starting at $360 per month. Hardware procurement, major cabling projects and software licensing are quoted separately, and startups are custom quoted. In an OMS office the cost drivers are the number of workstations (monitor-station and acquisition PCs included), server versus hosted licensing, CBCT storage, the number of sites and a second internet circuit.
For how to compare quotes, see our dental IT support cost guide.
The bottom line
An oral surgery office runs a general dental office's IT plus monitor stations, two-way imaging, a specialty software stack whose vendor leaves the network and backup to you, and surgery days that cannot move. Write the map, test the restores and put the January 2027 date on the calendar. Then hold your IT provider to the scorecard.
About Legend Networking:
- Served over 3,500 practices since 2004
- 22+ years in dental IT (since 2004)
- 24/7 monitoring
- Helpdesk staffed 24/7 at 1-800-794-1588
- 4.8 rating · 173 Google reviews
More on how we work with oral surgery offices is on our page about dental IT support.
Frequently asked questions
What technology does an oral surgery practice need?
Start with what any dental office runs: practice software, imaging, workstations, a network, phones, email and backup. An oral surgery practice adds four layers: sedation-monitor stations that write into the anesthesia record, CBCT and referral imaging in both directions, a specialty practice-software server or hosted session with the network and backup left to you, and surgery days that cannot be moved.
When something stops working, do we call the software vendor or our IT company?
Call the software vendor when one application shows the same error on every computer and the network is working. Call IT for the server, Windows, network, Wi-Fi, backup and accounts, or when you cannot tell. Call the monitor's manufacturer for the device itself. The WinOMS technician guide puts the client's computer network on the local technician, so network problems go to IT.
When should IT get involved in a new or expanding oral surgery office?
At the floor plan, before the electrical and low-voltage drawings close. That is when data drops, UPS power for monitor stations, cabling for the CBCT room and the network closet are still cheap to change. After that, IT follows a timeline: cabling about 90 days out, vendors and two internet circuits at 60, hardware staged at 30, and a dry run two weeks before opening.
Which technology dates matter for an oral surgery practice in 2026–2027?
Microsoft's extended support for SQL Server 2016 ended on 14 July 2026, and Windows Server 2016 extended support ends on 12 January 2027. WinOMS 10.1.x still lists Server 2016 as supported, so the Microsoft date is the one that binds. If the office is still on WinOMS 9.x, plan the move to version 10, which runs on SQL Server, together with the server replacement.
How should a multi-office oral surgery group connect satellites and surgeons who rotate between offices?
Pick one method per system and write it down: satellites reach an on-premises server over a site-to-site VPN, or every site connects to hosted or cloud software over its own internet line. Imaging capture, monitor stations, scanners and signature pads stay local at each site. Surgeons who rotate should find the same login, imaging access and monitor-station setup in every office.
What should an oral surgery practice ask an IT provider?
Start with five. Which of our systems do you support, and who calls each vendor? Who owns our network and backup, given that our software vendor does not? When did you last test a restore of our practice-software database? How do you set up and test monitor-station computers without touching the monitor? What sits on its own network segment, and why? The full scorecard has fifteen.
The bottom line
If your technology map has blank rows, your server runs Windows Server 2016, or nobody can say when the last restore was tested, you are welcome to ask for a Free Dental IT Assessment. You get written findings and prioritized recommendations on your computers, software, network security, backups and performance. Or call 1-800-794-1588.