Choosing an IT Company for an Oral Surgery Practice (2026)
Friday's sedation block ran on paper: the suite 2 monitor station restarted for updates before the first case and came back without its serial adapter talking to the anesthesia record. Your IT company called the update window "standard"; the software vendor said the adapter is not its product.
This guide is for the surgeon or administrator of an oral and maxillofacial surgery (OMS) office who is choosing, replacing or re-reading the contract of an IT company. The equipment and rooms themselves are covered in our oral surgery practice technology guide. Its author is Ian Lynch: 22 years in dental IT, and today in charge of Legend's NOC, onsite dispatch and client technology roadmaps.
The right IT company for an oral surgery practice owns everything beneath the surgical software: the server or hosted connection, the monitor stations that write the anesthesia record, CBCT and referral imaging, the wired suite network, backups and surgeon remote access. It plans around your surgery schedule and takes vendor tickets off your hands.
- For a practice running sedation cases, managed IT is the model in which someone is paid to prevent a fault on a surgery day; vendor support alone leaves the network and backup unowned, in the vendor's own words.
- An oral surgery agreement must name twelve things: monitor stations and adapters, the anesthesia record's path, CBCT viewing in every suite, implant planning PCs, referral intake, hospital and remote access, the server or hosted line, backups with a restore test, suite-aware patch windows, phones, accounts and vendor coordination.
- WinOMS documents put the network and the backup on the local technician, say Remote Desktop Services is not supported, and require the anesthesia module over LAN or VPN, never Wi-Fi.
- Switch IT companies in four weeks around the surgery schedule: inventory, ownership of credentials and a tested restore, shadowing, then cutover on a non-surgery day with the monitor link tested first.
- The practice, not the IT company, should hold the server administrator password, the backup key, the domain registrar and every vendor account.
In this guide
- Which support model fits an oral surgery practice: vendor-only, break-fix, managed IT or co-managed?
- What must an IT agreement for an oral surgery practice cover?
- Where is the line between the software vendor and the IT company in an oral surgery office?
- What does a sedation day look like when the IT company is doing its job?
- How should your IT company handle hospital, ASC and remote-surgeon access?
- Which warning signs show that an IT company has never worked a sedation day?
- What does a safe switch of IT companies look like for an oral surgery practice?
- What to ask your IT provider about surgery days, suites and the exit
- What to verify before you sign
- What should your IT company report each month, and what should you test each quarter?
- How Legend Networking works with oral surgery practices
- Frequently asked questions
- The bottom line
Which support model fits an oral surgery practice: vendor-only, break-fix, managed IT or co-managed?
For a practice that runs sedation cases, a managed IT agreement is the only model in which someone is paid to prevent a fault on a surgery day rather than to fix it afterwards. Vendor support alone leaves the network and backup unowned, break-fix pays by the incident, and co-managed suits a practice inside a hospital system or group.
Most oral surgery offices arrive at this question after one of the other three models has failed them, so it is worth seeing the four side by side before reading any proposal. The rows are the things that go wrong in an OMS office specifically; a general dental comparison would score them differently.
| What you need | Vendor support only | Break-fix IT | Managed IT | Co-managed (your group's or hospital's IT plus a dental IT company) |
|---|---|---|---|---|
| Someone owns the server, Windows, network and backup | No: the WinOMS technician guide puts the network on "the local technician" | Only while a ticket is open | Yes, continuously, in writing | Split by a written matrix; the dental IT company usually holds the practice software platform |
| Monitor stations treated as clinical equipment (patch windows, wired ports, adapter checks) | No | No; patched when someone remembers | Yes, scheduled around surgery blocks | Yes, if the matrix says who owns the suite PCs |
| A tested restore of the practice database and imaging store | Vendor "does not train offices on configuring the backup system or restoring a database" | Rarely; restores are billed as incidents | Yes, on a schedule, with the date reported | Usually the dental IT company; confirm |
| Vendor tickets opened and followed on your behalf | You call; the vendor answers about its application | Sometimes, billed by the hour | Yes; the bounce between vendor and IT is the IT company's to resolve | Yes, within the matrix |
| Remote and hospital access controlled with named accounts and multi-factor sign-in | No one owns it | Set up once, rarely reviewed | Reviewed with the account list | The group or hospital often sets the standard; the dental IT company applies it |
| Cost structure | Licence and support fees only | Hourly, unpredictable in a bad month | A monthly figure that moves with devices, offices and users | Two agreements, one matrix |
| Best for | Nobody running sedation cases | A practice willing to carry the risk and the clinical consequences | Most oral surgery practices with one to a few offices | OMS practices owned by a group, a DSO or a health system |
Two of those columns deserve a sentence more. "Vendor support only" is not a real model for an OMS office, because the practice-software vendor has already told you in writing what it will not do. "Co-managed" is real and growing: a surgeon who operates inside a hospital system, or a practice bought by a group, often inherits a corporate IT department that will not touch WinOMS, the monitor stations or the imaging archive. The fix is a written matrix that says which company owns each line of the scope table below, and a dental IT company that has worked under one before. If you are the group, start with DSO IT support.
How a managed plan is put together, and what moves its monthly figure, is set out where we describe managed IT services for dental practices. Everything below is the OMS-specific layer on top of that plan: the lines a surgeon should expect to find in the agreement, whoever writes it.
What must an IT agreement for an oral surgery practice cover?
Twelve lines belong in an oral surgery practice's IT agreement that most dental ones omit: sedation-monitor stations and their adapters, the anesthesia record's path to the chart, CBCT viewing in every suite, implant planning workstations, referral intake, hospital and remote-surgeon access, the server or hosted connection, backups including the imaging store, suite-aware patch windows, phones, accounts and vendor coordination.
Nothing on the hardware list gives an oral surgery office away; a general practice buys the same server, firewall and workstations. The difference is what a fault costs. A frozen front-desk PC in a general office delays a hygiene visit; a frozen suite PC in an OMS office can interrupt the vitals record during a case. The table below converts that difference into contract language. Read any proposal against its last column, because an item that is not written into the agreement will be billed as a project or refused as out of scope.
| Line in the agreement | What makes it an OMS line | Normal owner | Written in, or not in the price |
|---|---|---|---|
| Sedation-monitor workstations: wired port, serial or USB adapter, the PC itself | The WinOMS requirements say the anesthesia module "must be locally installed through LAN or VPN connection" and that wireless "is not recommended for Anesthesia"; the monitor itself is a medical device | IT company for the PC, cable, adapter and port; the monitor maker for the device | Yes, each suite listed, with the adapter model recorded |
| The anesthesia record's path from monitor to chart | If the serial link drops, the record is written by hand and re-entered later | IT company first; the software vendor for its module | Yes: who is called first, and what the IT company checks before the vendor |
| CBCT acquisition PC and 3D viewing on every suite and consult PC | A volume captured in one room has to open in the suite where the surgeon stands | IT company for the acquisition PC, network path, storage and viewer installs; the imaging vendor for the unit and its software | Yes, with the viewer named per room |
| Implant planning workstations | Guided-surgery planning software runs on a graphics-heavy PC with its own requirements | IT company for the workstation; the planning-software vendor for the application | Yes, with the maker's published spec as the standard |
| The referral intake path: one intake PC, media handling, inbound links and portals | Discs, USB sticks and download links arrive from referring offices every day | IT company | Yes: the intake PC, scanning policy and where files land |
| Hospital, ASC and remote-surgeon access | Surgeons work in more than one building and need the practice record from each | IT company, inside the limits the software vendor publishes | Yes, per surgeon, with the method stated |
| The practice-software platform: dedicated server, SQL Server and domain, or the hosted or cloud connection | Carestream "strongly recommends running the WinOMS database on a dedicated server"; Hosted publishes bandwidth by user count | IT company | Yes, with version end dates for a server or line requirements for Hosted and cloud |
| Backups that include the database, imaging store, anesthesia records and scanned referrals, with a restore test | The vendor says "Live Back up of data is not recommended" and that the database "must be stopped to make a proper copy" | IT company | Yes: the method, the schedule and a dated restore test |
| Patch and maintenance windows that respect the surgery schedule | A monitor station that reboots during a case is a clinical event, not an IT one | IT company | Yes, with suite PCs excluded from automatic restarts on surgery days |
| Phones: the referring-doctor line, the post-op line and after-hours routing | Referral volume arrives by phone first | IT company for the phone system and network; the carrier for the line | Yes, with the referring-doctor line's routing agreed |
| Accounts for surgeons, anesthesia staff, rotating assistants and vendors | Suite PCs drift toward one shared login; vendor remote tools outlive the ticket they were installed for | IT company maintains; the practice signs off each change | Yes, including how a new hire is added, how a leaver is removed, and the list of vendors with remote access |
| Vendor coordination for WinOMS, Sensei, OMSVision, DSN, the CBCT maker and the monitor maker | A fault often sits between two vendors and the IT company | IT company | Yes: "we open the ticket with you and stay on the call" |
Legend's page on IT support for oral surgery practices carries a who-to-call table by symptom and five questions for any IT company before it touches a surgical suite. Those are not repeated here; this page is the buyer's reading of the agreement.
Where is the line between the software vendor and the IT company in an oral surgery office?
The software vendor's job ends at its application: an error inside WinOMS or Sensei Cloud, a licence, a report, an update. Beneath it is the IT company's layer: the server or hosted connection, SQL Server, Windows, the wired suite network, monitor PCs and adapters, backup and accounts. WinOMS itself calls the local technician "fully responsible" for the network.
Almost every bounced ticket in an OMS office sits on that line, so the table draws it for each system in the building. Only the WinOMS and Mindray documents are quoted; for the other systems, the vendor's current document is the thing to ask for.
| System in the office | Where it runs | The vendor's side of the line | The IT company's side of the line | The vendor's words |
|---|---|---|---|---|
| WinOMS on a server in the office | Microsoft SQL Server database on a Windows server, workstations on the wired LAN | The WinOMS application, its database conversion and updates | The server, Windows Server and its end dates, SQL Server, the domain, workstations, the network, the backup and its restore | "Carestream Dental LLC strongly recommends running the WinOMS database on a dedicated server." "Remote Desktop Services (formerly Terminal Services) is not a supported environment." |
| WinOMS Hosted | The application runs in the vendor's data centre; your PCs connect over the internet | The hosted application and its data centre | The internet line and failover, the firewall, the PCs, and everything that stays local: imaging capture, scanners, monitor stations | A hosted workstation "is not suitable for image acquisition"; "Network scanners are not supported"; bandwidth published per user count, "at least 2 Mbps for each simultaneous user at a single location" |
| Sensei Cloud | The vendor's cloud, reached from your workstations over the internet | The application, and the vendor's hosting of it | The internet line, the firewall, every workstation and sign-in, and the local PC that a connected vitals monitor plugs into | Not quoted here: ask the vendor for its current support article on which monitor brands the vitals integration accepts |
| OMSVision, DSN and other oral surgery practice systems | A server in the office or the vendor's cloud, by product | The application | The same platform layer as for WinOMS; the vendor's current requirements document is the standard to ask for | Not quoted here: ask each vendor for its current requirements document, which is the standard your IT company works to |
| Vitals monitors (Criticare, Mindray, Casmed and others) linked to the anesthesia record | A serial or USB link from the monitor to one suite PC | The monitor, as a medical device, and its cable | The suite PC, its port, the adapter and the wired network | WinOMS lists "Casmed PPM3, Zoe Nightingale PPM3 with DB9 to RJ45 adapter from manufacturer" and Criticare 8100E models with a "9-pin Male/Female Null-modem Serial cable no longer than 6 feet"; for Mindray, "The Vendor provides the Mindray Monitor and cable connection. A Serial to USB Adapter is required" |
| CBCT and panoramic units (Carestream, Planmeca, Vatech, DEXIS and others) | Acquisition software on a dedicated PC; volumes stored on a server or imaging store; viewers on suite PCs | The unit, its calibration and its acquisition software | The acquisition PC, the network path, storage, the viewer on every suite PC, and the backup of the volumes | WinOMS points imaging buyers to the "OMS Imaging System Requirements", which "will include 3D Viewing Workstation System Requirements" |
| Implant planning and guided-surgery software | A graphics-heavy workstation built to the maker's specification | The planning application | The workstation, its graphics drivers and update policy, and the path by which volumes reach it from the CBCT store | Not quoted here: ask the maker for its current specification; common requirements are collected in our implant planning software computer requirements guide |
| Referral portals, e-fax and the mail system | Cloud services with sign-ins | The portal or service | The intake PC, the accounts, multi-factor sign-in and the agreements you hold with each vendor | Not a vendor fact: the referral path is described in our oral surgery referral intake guide |
Read the table for three tests of any provider. The first is the backup. WinOMS states that its support "does not train offices on configuring the backup system or restoring a database" and that "Backups should be performed by a System Administrator." Your IT company is that administrator, so the agreement should say how the database is stopped for a proper copy, where the copy goes, and when a restore was last tested. The method is in WinOMS server vs Hosted vs Sensei Cloud and the general routine in our dental backup and disaster recovery checklist.
Second, the monitor station. The monitor maker will not touch the PC; the software vendor supports its anesthesia module but not the port, cable or Windows update that stopped it; the IT company has to own the whole chain from monitor plug to chart. Ask any provider to walk the chain for one suite with you, including the adapter model and the port it uses. The wiring and segment design are in oral surgery office network and sedation-monitor stations.
Third, remote access. WinOMS says Remote Desktop Services is not a supported environment and that the anesthesia module runs "through LAN or VPN connection". A provider who proposes a remote-desktop server for your surgeons has not read the document; one who proposes a VPN with named accounts and multi-factor sign-in has. For a general dental office, the five sources of support and the layer each one owns are mapped in our guide to dental office tech support; the table above is that map redrawn for a surgical practice.
What does a sedation day look like when the IT company is doing its job?
On a surgery day, a good IT company shows up as an absence of events: the server, last night's backup, the monitor stations and the internet line were checked before the first case, no update touched a suite PC, the helpdesk knows which rooms are running sedation, and a call from a suite is answered with "which suite?"
The difference between a dental IT company and an oral surgery one shows in the rhythm of a surgery day. The table describes what a well-run agreement does across one day and the week behind it; the monthly and quarterly cycle is in the report section further down. None of it needs clock times; it needs the surgery schedule, which your IT company should have.
| Point in the day | Work already done, or under way | What the team sees |
|---|---|---|
| Before the doors open | Monitoring has reported on the server, the database service, last night's backup result, the internet line and the suite PCs; anything red is handled before the first patient | Nothing; a short note if something was fixed |
| First case of the sedation block | No update, scan or reboot is scheduled on any suite PC; the monitor-to-chart link was confirmed during the morning check | The vitals appear in the record without anyone touching the PC |
| Between cases | A connection error in one suite is answered with "which suite, what is on the screen, did the monitor or the PC change"; the IT company checks the PC, port and adapter before calling the software vendor | One call, not two |
| Consult room, mid-morning | A CBCT volume from a referring office opens on the consult PC because the viewer, storage path and intake PC were set up and tested | The surgeon does not walk to the CBCT room to see a scan |
| Front desk, all day | Referral discs and links go to the intake PC; the referring-doctor line rings where it should; a new assistant's accounts were created the day before | No disc is opened on a random computer |
| Last case and close | The nightly backup is scheduled after the last entry, with the database stopped for the copy as the vendor requires; updates run on non-suite machines after close | A backup report in the morning, not a failed-job email at noon |
| Weekly | Update review for suite PCs against the monitor and imaging vendors' notes; account changes against the staff list; firewall and remote-access log review | A short weekly note or a line in the monthly report |
The downtime side of that day, including the paper fallback for a sedation case and the morning pre-flight, is in our surgery-day downtime plan. What this section adds is who does the work: a company that has to be told your surgery schedule is already behind.
How should your IT company handle hospital, ASC and remote-surgeon access?
Remote access for an oral surgeon should be a VPN or the vendor's hosted or cloud session, with a named account and multi-factor sign-in per surgeon, never a shared remote-desktop login or a consumer remote-control tool. Access from a hospital or ASC runs the other way too: hospital portals open from practice PCs that must stay off the clinical segment.
Oral surgeons work in more buildings than most dentists: the practice, a hospital where they hold privileges, an ambulatory surgery centre, a satellite office and home. Each place needs a slice of the practice record, and each is a door your IT company has to control. The table sets out the common cases and what the right answer looks like.
| Who needs access, from where | What they need | The right setup | What to rule out |
|---|---|---|---|
| A surgeon at a hospital or ASC | Today's schedule, a patient's chart, a CBCT volume before a case | A VPN into the practice with a named account and multi-factor sign-in, or the hosted or cloud session the vendor provides; a viewer that works over that link | A remote-desktop server for WinOMS (the vendor says Remote Desktop Services is not supported); a login shared by the surgeons |
| A surgeon at home, evenings and weekends | Charting, letters, reviewing scans | The same VPN or hosted session, on a practice-managed device | A personal laptop with the practice software installed and no device management |
| Anesthesia staff or an associate rotating between offices | The anesthesia record at whichever office they are in | WinOMS's anesthesia module "must be locally installed through LAN or VPN connection", so each office has its own installed station; accounts follow the person | Wireless monitor stations, which the vendor says are not recommended |
| Hospital or ASC systems opened from the practice | The hospital's portal, scheduling or results | Named accounts in the hospital's system, opened from a front-office or consult PC, not from a suite PC | Hospital portal sessions left open on the monitor station |
| Software vendors and the monitor maker | Remote support into a server or suite PC | Access that is turned on for a ticket and off afterwards, logged, and listed in the monthly report | A vendor's remote tool installed permanently on every PC and never reviewed |
| The IT company itself | Administration of everything above | Named engineer accounts, multi-factor sign-in, logged sessions, and the practice holding its own administrator credentials | One shared "admin" login used by the IT company, the vendors and the practice |
That table is the practical shape of two lines in the HIPAA Security Rule's technical safeguards. One requires a covered entity to "Assign a unique name and/or number for identifying and tracking user identity" (45 CFR 164.312(a)(2)(i)); the other to "Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information" (164.312(b)). How those words apply to your practice is for your compliance adviser to read. For your IT company they translate into one rule: no remote door without a name on it and a log behind it. Vendors that reach your data remotely also sit inside the business associate rule, 45 CFR 164.308(b)(1), which allows a business associate to handle protected information "only if the covered entity obtains satisfactory assurances" that it will safeguard it; our guide to business associate agreements for dental practices covers how to keep that list.
Which warning signs show that an IT company has never worked a sedation day?
The clearest warning signs are an update or restart that reaches a suite PC on a surgery day, a proposal that treats monitor stations as ordinary workstations, a remote-desktop server offered for WinOMS, a backup described without a restore date, and a provider who tells you to call the software vendor yourself when a fault sits between the two.
Every row pairs the sign with what it costs and one question to put across the table at a shortlist meeting. Ask the question of your current provider too; the answer is useful either way.
| What you see | The price on a surgery day | Ask this |
|---|---|---|
| Patches or restarts land on suite PCs during surgery blocks | A sedation case charted by hand; a vitals record re-entered later | "Which of our computers are excluded from automatic restarts on surgery days, and how do you know our surgery days?" |
| Monitor stations are listed as plain workstations in the proposal | The adapter, port and serial link have no owner until they fail | "Walk me through suite 1 from monitor plug to anesthesia record. Which parts are yours?" |
| A remote-desktop server is proposed for WinOMS | A setup the vendor documents as unsupported, and a support call that ends with "we cannot help on that platform" | "How do our surgeons reach the record from the hospital, and does the vendor's requirements document support that method?" |
| Backups are described as "nightly" with no restore test and no mention of stopping the database | A copy that cannot be restored, discovered on the day it is needed | "When did you last restore a WinOMS database and imaging store for a client, and how long did it take?" |
| Wi-Fi is proposed for suite workstations to save cabling | Dropped vitals links; the vendor recommends against wireless for anesthesia | "Which of our clinical PCs will be on Wi-Fi, and what does our software vendor say about that?" |
| Imaging is treated as a general dental sensor problem | A CBCT volume that opens in one room only; a referral disc opened wherever | "How does a referring dentist's CBCT get from a disc at the front desk to the surgeon's suite PC?" |
| "That one is the vendor's" ends the call when a fault sits between vendor and IT | Two tickets, a morning gone, and the same fault the following week | "Name the vendors you will open tickets with for us, and tell me who holds the line until it is closed." |
| No surgery schedule is requested during onboarding | Every other sign on this list follows from this one | "What do you need from us in the first week?" (If the surgery schedule is not on the list, stop.) |
| No oral surgery project pages or references | You are the first OMS office they learn on | "Show me an oral surgery office you set up or support, on our practice system." |
| Administrator passwords, backup keys and the domain registrar are in the IT company's name only | A hostage situation at exit; a scramble if the company folds | "Which administrator credentials will the practice hold on day one?" |
None of these is a sign of a bad company; several are signs of a general IT company that has not worked a sedation day. The difference matters because oral surgery faults are clinical before they are technical. A generalist learns that on your schedule.
What does a safe switch of IT companies look like for an oral surgery practice?
Plan the switch as four weeks fitted around surgery blocks: week one, a written inventory from the outgoing company; week two, the practice takes every administrator credential into its own name and watches a restore succeed; week three, the incoming company shadows the helpdesk; week four, cutover on a non-surgery day, proven by vitals, a CBCT and a claim.
Most of the risk in a switch sits in things that are not on any invoice: the serial adapter model in suite 3, the path where CBCT volumes are stored, the service account the backup runs under, the referral e-fax login. The handoff inventory below is what the outgoing company should produce and the incoming one should verify. Only the OMS-specific items appear in it; the notice, contract and timing steps shared by every dental practice are in switching dental IT providers without downtime.
| Handoff item | Why it matters in an oral surgery office | Who holds it after the switch |
|---|---|---|
| Server administrator and domain credentials; the SQL Server service and the WinOMS database location | The vendor supports the application, not the server; nobody else can restore it | The practice, in a sealed record, with the new IT company working through named accounts |
| Backup configuration: schedule, the step that stops the database, destination, encryption key, last restore test | WinOMS states that a live backup is not recommended; a copy made the wrong way may not restore | The practice holds the key; the IT company runs the job |
| Per-suite monitor station record: PC name, port, adapter model, cable, monitor model and firmware | Replacing an adapter with the wrong chipset breaks the vitals link | The practice's asset list, updated at every change |
| Imaging: CBCT acquisition PC, storage path, viewer versions per room, vendor accounts | A volume store moved without its path mapping is a room full of PCs that cannot open scans | The practice's asset list; vendor accounts in the practice's name |
| Referral intake: intake PC, e-fax and portal logins, download folder, scanning policy | Referrals keep arriving during the switch | The practice's accounts; the IT company applies the policy |
| Remote access: VPN configuration, surgeon accounts, hospital-portal PCs, vendor remote tools installed | The commonest leftover is a vendor or former technician's tool still running | Removed or re-issued in the first week under the new company |
| Network: firewall configuration and licence, static IPs, switch and VLAN map, which ports feed the suites | The monitor stations depend on specific wired ports | The practice holds the firewall admin; the IT company holds the map |
| Phones: the referring-doctor line's routing, after-hours rules, carrier account | Referral calls are revenue | The practice's carrier account |
| Access register: every person and vendor with a login to email, the practice software, imaging and portals, and what each can do | The most frequent access failure in a switch is a former employee or former technician whose login still works | The practice signs it off; the IT company keeps it current |
| Documentation and the monthly reports from the last year | Shows what was actually done | The practice |
The HIPAA Security Rule's administrative safeguards describe the account side of an exit as "Termination procedures (Addressable). Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends" (45 CFR 164.308(a)(3)(ii)(C)). An outgoing IT company's accounts are part of that arrangement. How the rule applies to your practice is for your compliance adviser; how it applies to the switch is simple: every account the old company used is listed, re-issued or removed, and the practice holds the proof.
The four-week sequence is designed for a surgery schedule:
- Week one: joint inventory. The outgoing company completes the table above in writing; the incoming company reads the server, backup job and firewall without changing anything. No surgery day is touched.
- Week two: ownership. The practice takes the administrator credentials, the backup key and the domain registrar into its own name. The incoming company restores last night's backup to a test machine and opens a CBCT volume and an anesthesia record from it. If the restore fails, the switch pauses here.
- Week three: shadowing. The incoming company answers the helpdesk alongside the outgoing one, runs the first patch window on non-suite PCs after close, and walks each suite from monitor plug to chart.
- Week four: cutover on a non-surgery day. Monitoring moves, remote-access tools change hands, the old company's accounts are removed. Before the next surgery block: a monitor records vitals into a test record in every suite, a referral disc opens on the intake PC, a scan opens in a consult room, a claim goes out and a backup completes.
Keep the platform decision out of the switch month. Whether to replace the server, move to WinOMS Hosted or move to Sensei Cloud is a separate choice, worked through in our WinOMS server vs Hosted vs Sensei Cloud checklist. Some practices face both at once because Windows Server 2016 reaches the end of extended support on 12 January 2027 (Microsoft Lifecycle, read 18 November 2026); the planning calendar for that is in Windows Server 2016 end of support for dental offices.
What to ask your IT provider about surgery days, suites and the exit
Bring these to the shortlist meeting. Our technology guide carries a fifteen-point scorecard and our oral surgery page five questions, and both test knowledge; the questions here test behaviour, meaning what the company will actually do on a Tuesday sedation block. Put them to every candidate, Legend included, alongside the one-line questions in the warning-sign table, and listen for your suite numbers, your software and your schedule in the answers. An answer that would fit a law firm is the wrong answer.
About surgery days
- How will you learn our surgery schedule, where does it live in your systems so a technician sees it before touching a suite PC, and who approves an exception to the no-restart rule?
- When a suite reports a fault during a sedation case, who answers, what do they ask first, and what can they do remotely before anyone drives?
- What did your monitoring catch last month for an oral surgery client before the first patient arrived?
About the monitor stations and the anesthesia record
- How do you record the adapter model, port and cable for each suite, and what happens when a PC is replaced?
About imaging and referrals
- Where are our CBCT volumes stored, how are they backed up, and when was a volume last restored from backup for a client?
- Before a Windows update reaches the CBCT acquisition PC or the guided-surgery planning PC, whose sign-off is needed and which vendor notes are read?
About the server, Hosted or cloud connection
- We run WinOMS on a server / WinOMS Hosted / Sensei Cloud / OMSVision / DSN]. Which of its published requirements fall to you, and which have you had to explain to a client before?
- How is the database stopped for the nightly copy, where does the copy go, and when was the last restore tested?
- For a server practice: tell us our Windows Server and SQL Server versions and their end-of-support dates after your first visit. For a Hosted or cloud practice: what internet line and failover will you insist on at each office?
About hospital and remote access
- Which vendors have remote access into our systems today, how is it turned on and off, and where is it logged?
- Which remote route will each surgeon use from the ASC and from home, on which device?
About accounts, reports and the exit
- A new anesthesia assistant starts Monday and one leaves Friday. List every system where their access changes and who makes each change.
- Show us a recent monthly report for an oral surgery client, name removed. Which lines on it would you expect us to question?
- Describe the day we leave you: what is handed over, in what form, and within how many days of notice?
Term, notice, insurance and liability belong to the contract conversation, which our 20 questions to ask before signing a dental IT contract covers, and the scoring method for a shortlist is in how to choose a dental IT company.
What to verify before you sign
Five claims in an IT proposal deserve written evidence before an oral surgery practice signs: that the company has supported OMS offices, that "full support" matches the twelve lines above, that the monthly figure can be recalculated for one more suite, that first-level helpdesk calls are answered by the company's own staff, and that exit terms hand back credentials, data and documentation within a stated number of days.
| What the proposal claims | The evidence to ask for | How you check it |
|---|---|---|
| "We support oral surgery practices" | Named project pages, or a reference, from an OMS office on your practice software and at your stage: a new build, an added suite, a move to Hosted | Phone the reference and ask what happened the last time a suite PC failed on a surgery day |
| "Full support" or "all-inclusive" | Each of the twelve lines from the agreement table, written out with its owner | Tick the proposal against the table; an unticked line is a future project invoice |
| "Nightly backups" | The method (database stopped for the copy), the destinations, the retention, and the date of the last restore test for a client | Ask to see a restore-test entry from a report, name removed |
| "Fast response" | How a suite reaches the helpdesk, when it is staffed, whether the people who answer are the company's own engineers, and where they are | Call the helpdesk during the evaluation with a made-up monitor-station fault and listen to the first three questions |
| "Secure remote access" | The method per surgeon, named accounts, multi-factor sign-in, session logging, and the vendor remote-access list | Ask for the list of every remote tool that would be installed on your PCs |
| A monthly figure | The variables behind it (suites, workstations, users, offices) and the items outside it, which in most agreements are hardware, cabling, software licences and projects | Have the company re-price the proposal for one added suite and one added office and compare the two figures |
| "We handle the vendors" | Which vendors, whether tickets are opened by the IT company, and whether someone stays on the call | Ask for an example from the last quarter, name removed |
| Exit terms | The handoff inventory above as a contractual deliverable, with a period | Read the termination clause before the pricing page |
| Onsite coverage | The arrangement for visits to your address, and the plan for a satellite on its own surgery day | Ask where the engineer who would replace a monitor-station adapter actually sits, and how long that visit takes to arrange |
Shortlist at least two. Our roundup of the best dental IT companies was built to be verified against each company's own site, and what can and cannot be fixed without a visit is set out in remote vs onsite dental IT support. A practice that wants the quote read by someone with no stake in it should look at what a dental IT consultant does.
What should your IT company report each month, and what should you test each quarter?
Each month the IT company should hand the surgeon one page: faults by suite and system, with vendor-involved faults on their own line; when the last restore ran and how long it took of the database and imaging store; what was patched and which suite PCs were excluded; server and SQL end dates; remote-access review; account changes; open vendor tickets.
| On the report | Why a surgeon cares | What a good month shows |
|---|---|---|
| Tickets by suite and by system (monitor station, imaging, practice software, network, accounts) | Shows whether one suite or one adapter keeps appearing | Repeat faults named, root cause stated, closed rather than re-opened |
| Faults that involved a vendor, with the vendor ticket number and who owned it | Proves the bounce is handled | Each has an outcome, not "referred to vendor" |
| Restore: date, scope (database, imaging store, anesthesia records) and duration | A backup is a claim; a restore is the evidence | One restore inside the month, from a copy taken with the database stopped as the vendor requires |
| Updates installed, by machine group, with the suite PCs held back | Proves no suite PC was updated in the middle of a block | Suite PCs on their own line, each update checked against the monitor and imaging makers' notes |
| Windows Server and SQL Server versions, each with its end-of-support date | The replacement clock for a server-based WinOMS practice | Both dates shown, and a written plan once either is inside twelve months |
| Internet line and failover test (Hosted and cloud practices) | The line is part of the clinical system | Tested, with the switchover time |
| Remote access: active surgeon accounts, vendor tools installed, sessions logged | Every remote door has a name and a log | Zero unexplained tools; vendor access off between tickets |
| Joiners and leavers reconciled to the staff list | A login that outlives its owner is the first thing an auditor or an attacker finds | Every account on every system matched to a current person or an active vendor ticket |
| Backup copies, where the offsite copy sits, and how far back retention reaches | Anesthesia records and CBCT volumes are kept for years, not months | The number of copies, the offsite job's result and the oldest restorable date |
| Open vendor tickets and what is waiting on whom | Keeps the vendor honest too | Each with a date and a next step |
Once a quarter, the surgeon should watch four things happen rather than read about them: a surgery-day drill from the downtime kit, one patient's complete record (chart, anesthesia record, scans) restored to a test machine, a walk of every suite from monitor plug to chart, and a review of every remote tool and login. Behind that habit sit the Security Rule's "procedures for periodic testing and revision of contingency plans" (45 CFR 164.308(a)(7)(ii)(D)) and its call for "retrievable exact copies of electronic protected health information" (164.308(a)(7)(ii)(A)); how they apply to your practice is your compliance adviser's reading.
How Legend Networking works with oral surgery practices
From its Dallas headquarters, Legend Networking has served over 3,500 practices since 2004, which is 22+ years in dental IT. Calls reach in-house engineers, with no outsourced first-level triage: the helpdesk is staffed 24/7 at 1-800-794-1588, and 24/7 monitoring watches the systems between calls. Visits are arranged as onsite dispatch by appointment across served dental markets; day-to-day support is remote-first nationwide. On Google the company carries a 4.8 rating across 173 Google reviews.
The imaging systems whose IT environment Legend supports include Carestream, Planmeca/Romexis, DEXIS, Vatech and Dolphin Imaging. Whatever oral surgery practice system an office runs stays with its vendor for the application; the layer beneath it is the IT company's, as the tables above set out. Two of Legend's project pages show that layer in oral surgery offices: a new oral surgery centre in Cleburne, Texas, built for day-one readiness and an oral surgery and implant centre expansion in Fate, Texas, covering workstations, networking and Wi-Fi, backups, phone integration and treatment-room technology.
The whole service, for every kind of practice, is described under dental IT support. To see how specialty offices are looked after in one market, read specialty practice IT in San Antonio; our locations pages cover the other cities.
Frequently asked questions
Which jobs does an IT company take on in an oral surgery office that a general dental office never needs?
It adds the sedation-monitor workstations and their serial or USB adapters, the anesthesia record's path into the chart, CBCT and 3D viewing in every suite, implant planning workstations, a referral intake path for discs and links, hospital and remote-surgeon access, and patch windows built around surgery blocks. The server, backup, network and accounts are the same work with higher stakes.
Who do we call when the vitals monitor stops writing to the anesthesia record?
Call your IT company first. The chain runs from the monitor through a cable and a serial or USB adapter into a suite PC, and most faults sit in the adapter, the port or a Windows update. The IT company checks those, then opens the software vendor's ticket if the module itself is at fault. The monitor is a medical device and stays with its manufacturer.
Should our IT company know WinOMS or Sensei Cloud before we hire them?
They do not need to operate the software, but they must know its published requirements: a dedicated Windows server with SQL Server and a stopped-database backup for WinOMS, a sized internet line with failover for WinOMS Hosted or Sensei Cloud, and locally installed anesthesia stations in every setup. Ask them to quote the vendor's requirements document from memory; a company that has read it can.
Can an oral surgeon use remote desktop to reach WinOMS from the hospital?
Not on a supported setup. The WinOMS 10.1.x requirements state that Remote Desktop Services is not a supported environment and that the anesthesia module must be installed through a LAN or VPN connection. The supported routes are a VPN with a named account and multi-factor sign-in, or the vendor's Hosted or Sensei Cloud session. Ask your IT company which one it proposes and why.
How much of an oral surgery practice's IT can be handled without a visit?
Largely, yes. Monitoring, patching outside surgery blocks, account changes, vendor tickets, backup checks and helpdesk calls are all remote work. Cabling a suite, replacing a monitor-station adapter or PC, swapping a server or rebuilding a CBCT acquisition PC need someone in the building. Before signing, find out who would make that visit to your address and how a satellite is covered on its own surgery day.
Can we change IT companies without cancelling a surgery block, and how long does it take?
Yes, if you allow four weeks placed around the surgery schedule. The outgoing company writes the inventory in week one; the practice takes the administrator credentials and backup key into its own name and watches a restore in week two; the incoming company shadows the helpdesk in week three; cutover happens on a non-surgery day in week four, proven by a monitor writing vitals, a CBCT opening and a claim leaving.
Who should hold the server administrator password and the backup encryption key?
The practice owns them and keeps them in its own sealed record; the IT company works through its own named accounts. Treat the domain registrar, the firewall administrator login, the imaging vendor accounts and the referral portal logins the same way. Settle this during the first month of a new agreement rather than discovering the answer on the day you give notice.
Our second oral surgery office opens two days a week: what do we ask the IT company about it?
Four things: how that office reaches the practice software (a VPN or the vendor's hosted session for a server system, its own sized line with failover for a cloud one); whether its monitor stations are installed locally as WinOMS requires rather than reached over Wi-Fi; who answers on its surgery day if the main office is dark; and whether a monitor-to-chart test was run there before the first case.
What proof shows an IT company has actually set up oral surgery offices?
Two tests. Ask to see published project pages, or to phone a surgeon, from an OMS office that runs your software and went through your kind of change: a new build, another suite, a move to Hosted. Then ask the company to narrate one of your suites from monitor plug to anesthesia record, and a referring dentist's CBCT from disc to surgeon's screen. Detail is the tell.
If we move WinOMS to Hosted or to Sensei Cloud, what is left for an IT company to do?
More than most practices expect. The server leaves the building, and each office's connection, its backup line and its firewall start behaving like clinical equipment, and the monitor stations, CBCT acquisition PC, scanners, suite workstations, accounts and the backup of anything local all stay. The vendor's own Hosted requirements say a hosted workstation is not suitable for image acquisition, so imaging stays local too.
The bottom line
Bring the agreement table, the warning-sign questions and the handoff inventory to each shortlist meeting, Legend's included, and score every company against the same three sheets. If you would rather know where your current setup stands first, ask for a Free Dental IT Assessment: a written review, with the fixes in priority order, of your suite workstations, monitor-station links, server or hosted connection, imaging store, backups and network security. For Legend's own approach, read its page on IT support for oral surgery practices; for practices of every kind, start with dental IT support.

