Oral Surgery Office Network Design: Surgical Suites, Sedation-Monitor Stations and What Must Never Share a Network

It is build-out week for a two-suite oral surgery office. The low-voltage contractor wants to know where the drops go in each surgical suite, the monitor vendor asks which computer the sedation monitor plugs into, and someone asks how to connect a sedation monitor to WinOMS so vitals reach the anesthesia record.

Carestream's documents describe the module. Its installation guide for technicians makes the local technician responsible for the client's computer network, which in most offices means the practice's IT provider. If you are choosing who should own that work, our page on dental IT support for oral surgery practices explains how Legend works with practices. For the whole office beyond the network, start with the oral surgery practice IT guide.

In this guide
- Why an oral surgery network is different from a general dental office
- How the monitor connects to the anesthesia record, method by method
- An 11-line monitor-connection checklist
- The seven network segments an oral surgery office needs
- Ports and power, room by room
- What changes when you expand, remodel or add a satellite
- A 10-minute pre-surgery-day test
- Questions for your IT provider and your monitor vendor

Why is an oral surgery office network different from a general dental office?

An oral surgery office has rooms and devices a general office does not: surgical suites, a recovery area, a CBCT room and a vitals monitor that writes into the patient record during sedation through its workstation. The software vendor recommends wired connections, and a fault mid-case costs more, so the design has to be written down.

The rest of this page covers the oral surgery layer only. The general parts of an office network (drop counts, cable category, the closet build and a Wi-Fi plan) are in our guide to dental office network setup, and the full room list and technology map are in the practice IT guide linked above.

Next step: list every surgical suite and recovery bay where vitals are recorded. Each one is a monitor station.

How do you connect a sedation monitor to WinOMS's anesthesia record?

You cable the monitor to one Windows workstation and let that PC carry the readings into WinOMS. Carestream's 10.1.x requirements list a "DB9 serial port for Anesthesia Vitals Monitor" on the workstation, a null-modem cable for Criticare monitors, a USB-to-serial adapter for Mindray and Bluetooth adapters for some models. The workstation then needs a LAN or VPN connection.

The monitor talks to one PC, not to the network

This is the point most network plans miss. The monitor in the surgical suite is a medical device with a serial output. It sends readings down a short cable (or a Bluetooth link) to a single workstation. The Anesthesia Records module on that workstation writes the readings into the record, and the workstation is the device on your network.

So the network questions are really workstation questions. Which PC is the monitor station? Is it wired? Which segment is it on? Is it on battery backup? Who replaces it, and who re-tests the link when they do?

Which monitors can do this? Carestream's documents name them, and the names differ slightly from document to document:

• • The WinOMS 10.1.x System Requirements (page 2) list the Casmed PPM3 and Zoe Nightingale PPM3 "with DB9 to RJ45 adapter from manufacturer"; the CUSP-compatible Criticare 8100E nCompass or 8100E nGenuity; the Criticare 506 NT3 (not ECG compatible); and two discontinued but approved Criticare models, the Poet Plus 8100 and the 507EL Scholar. Its legacy page adds the Mortara Surveyor S12 or S19 and the "Criticare 8100H (nCompass)".
• • Carestream's Mindray integration guide covers the Mindray ePM 10A, "tested with WinOMS versions 9.7.1, 10.0.5 and 10.0.6 with Windows 11 (Workstation)".
• • Carestream's online help page for configuring the monitor prints its own list of Criticare, Zoe Medical and CAS Medical, Mortara and Mindray models, with spellings that do not always match the PDFs.

Read your monitor's model plate and match it against the current document, not against a list someone copied into an email.

The three ways to connect, and what goes wrong with each

For Mindray, Carestream's guide adds two workstation-side details. The first configuration step sets the PC's COM port, in Windows Device Manager, to "a baud rate of 19200 bits per second". The document also notes "ECG features are not supported with Mindray". It says the vendor supplies the monitor and the cable connection.

Carestream's guidance on compatibility is direct: "Contact manufacturer customer service to determine if your vitals monitor is CUSP compatible." That is the manufacturer's answer to give, not your IT provider's. Your monitor vendor or biomedical service confirms the monitor's own output settings against Carestream's monitor configuration page.

WinOMS Hosted or Sensei Cloud: where the Virtual Channel fits

If the practice runs WinOMS in a hosted or cloud setup, the monitor still plugs into a local PC, and that PC needs one more piece of software. Carestream's help says that "the monitor integration requires that the Virtual Channel with the Anesthesia Record module be installed on the client machine to which the monitor is attached". In the Mindray guide, installing the Virtual Channel client is step 2, and WinOMS is then launched through the user's Citrix account.

Sensei Cloud works differently. Its help article says vitals integration is "currently only available for Criticare Technologies, Inc. monitors". It runs a small piece of software as a Windows service on each monitor PC, and each PC is registered as a "Connected PC" for its practice location. If that PC is off or the service stops, the monitor shows as disconnected. Sensei's troubleshooting article for a Criticare monitor that will not connect sets that PC's COM port to 38400 bits per second, with a 9-pin null-modem cable, a serial-to-USB adapter and the IoT software running. That is a different speed from the 19200 in Carestream's Mindray guide for WinOMS, so note which product each monitor PC serves. For an IT provider, that means a service to monitor and a registration to redo when a PC is swapped.

Which deployment fits your office, and what it means for the server and the internet line, is covered in choosing a WinOMS server, Hosted or Sensei Cloud.

Not on WinOMS?

If your practice runs OMSVision, DSN or another oral surgery system, ask that vendor the same questions: which monitor models it lists, which cable or adapter it specifies, what the workstation needs, and whether a hosted version needs extra software on the monitor PC. Get the answers in writing and keep them with the network documents.

The monitor-connection checklist

Use this list before you buy a monitor or a PC, on install day and after any PC change. Each line is something IT can check without touching the medical device.

The USB-to-serial adapter and the null-modem cable are cheap parts, and both come in versions that look alike. Buy the one the document names, label it, and keep a tested spare in the closet.

If you want a second pair of eyes on your stations, a Free Dental IT Assessment gives you written findings and prioritized recommendations on your computers, software, network security, backups and performance.

Which network segments does an oral surgery office need?

A workable oral surgery office design uses about seven segments: clinical workstations with the practice-management server, imaging, the monitor stations, phones, cameras and door access, guest Wi-Fi with patient TVs, and vendor remote access. Each segment should reach only what it needs, and anything a patient or visitor can touch should reach the internet only.

A segment is a separate part of the network (usually a VLAN on the switches) with firewall rules that decide what can cross between parts. The general segment set for a dental office is in our dental office network setup guide. The table adds the oral surgery rows.

Segmentation is set up at the firewall and the switches, and our network design services and dental cybersecurity pages describe that side of the work. For the design method behind the table, see dental network design and implementation.

What "medical device segmentation" means at practice scale

Medical device segmentation means putting devices that cannot be updated on the same schedule as ordinary PCs (the PCs that host monitors, CBCT and pano acquisition PCs, cameras, phones and smart TVs) on separate segments with firewall rules between them. If one of them is compromised, it cannot reach the practice-management server. In a one-to-three-suite office it comes down to the seven rows above.

There is also a plain reliability reason. In 2015 a hospital's network dedicated to Mindray equipment had a cable looped from one wall jack to another. The Anesthesia Patient Safety Foundation reported that the resulting broadcast storm shut off six anesthesia machines and eight monitors while they were connected, and unplugging them restored them in 15–20 minutes. Mindray reported no patient injury and recommended switch settings that shut off ports flooding broadcast traffic. That was a hospital, not an oral surgery office or WinOMS. The lesson for any device segment still holds: ask your IT provider whether loop protection and storm control are switched on.

What the proposed rule's text says

The January 2025 HIPAA Security Rule proposal (Federal Register doc 2024-30983) was still a proposed rule as of 26 October 2026; no final rule had been published. Its text would add a network segmentation specification at proposed 45 CFR 164.308(a)(10)(ii)(E): "Establish and implement written policies and procedures that ensure that a covered entity's or business associate's relevant electronic information systems are segmented to limit access to electronic protected health information to authorized workstations."

This is the regulation's wording. How it applies to your practice is a question for your compliance adviser. Our summary of HIPAA Security Rule updates for dental practices tracks the proposal.

Room by room: ports and power for surgical suites, recovery and the CBCT room

Count every wired device in each room, add spares, and give every monitor station a UPS outlet. The table lists the devices that make an oral surgery office different. Use the drop worksheet in our network setup guide for the numbers, because port counts depend on your floor plan and equipment.

Which devices need a UPS?

Three groups. The server comes first, and Carestream recommends a UPS with shutdown software installed with it. Next is the network closet: the firewall and switches the monitor stations depend on. The third is each monitor station PC and the switch it plugs into, so a power blip does not drop the link mid-case. That last one is an IT recommendation, not a vendor requirement. Our server shutdown and UPS checklist covers sizing and safe shutdown.

Where Wi-Fi fits in an oral surgery office

Wi-Fi is fine for tablets and guests, and not for the anesthesia station. Carestream's requirements call for a "Wi-Fi Connected Tablet PC" for the Point-of-Care module. The same document says "Wireless networking is not recommended for Anesthesia" and, in general, "For best performance, use hard-wired connections." Put tablets on the clinical Wi-Fi, guests on their own network, and wire every PC that records vitals.

Planning a build-out? Ask for a Free Dental IT Assessment before the drops are pulled.

Expanding, remodelling or adding a satellite: what changes for the network?

Adding a surgical suite or a satellite office adds monitor stations, and each needs the same cable, port, power and segment decisions before the walls close. Book the monitor vendor early, agree where each station sits, and test every station before the first sedation case.

A monitor station at a satellite office connects to the practice software the same way: Carestream says the Anesthesia Module must be installed "through LAN or VPN connection". For the satellite, that means a VPN back to the main office or a hosted session, and the station is still wired. Group design for several offices is in the oral surgery practice IT guide. For a brand-new office, our pages on dental startup IT and IT setup for new dental practices cover the whole sequence.

The pre-surgery-day test

Run a 10-minute test before each sedation day, at least weekly, after any Windows update and after any PC swap. It checks that vitals reach the record, that every station is wired and powered, and that everyone knows who to call. It does not replace a downtime plan.

What if something fails during a case? That is a downtime plan, not a network test. See our surgery-day downtime plan.

Questions to ask your IT provider and your monitor vendor

Ask these before a build-out, before a PC refresh and whenever the monitor link has failed more than once. Written answers show who owns each part of the link.

For a wider list that covers contracts, response terms and the whole office, see the 20 questions to ask before signing a dental IT provider.

Oral surgery offices Legend has worked with

Recent project write-ups, oral surgery offices among them, are on our project pages. This guide comes from Ian Lynch, who has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps.

• • Practices: Served over 3,500 practices since 2004
• • Experience: 22+ years in dental IT (since 2004)
• • Engineering team: In-house engineers; no outsourced first-level triage
• • Monitoring: 24/7 monitoring
• • Onsite: Onsite dispatch by appointment across served dental markets; remote-first nationwide
• • Google reviews: 4.8 rating · 173 Google reviews