IT Support for Specialty Dental Practices in San Antonio: Orthodontic, Endodontic, Oral Surgery, Pediatric and Perio Offices

The cone beam volume you captured ten minutes ago will not open in operatory three, the patient is a referral who waited a week for the slot, and the help desk has just told you to restart the computer, again.

This page goes specialty by specialty. It names what each kind of office in San Antonio typically runs, where the chain fails and why, what a cone beam unit asks of a server room in a city that logged sixty 100-degree days in a single year, which projects Legend Networking has documented for specialists in San Antonio and elsewhere in Texas, and the questions that separate a provider who knows your systems from one who will learn them on your patients.

Why does a San Antonio specialty office need different IT from a general practice?

A general practice's IT is mostly a practice management database, sensors and a printer. A specialty office adds systems that move large files between rooms, buildings and vendors: 3D volumes, scanner exports, photo sets, planning files and referral records. Those systems fail at their connections, and a provider who has never built those connections cannot see the failure coming.

The difference is not the number of computers. A six-chair orthodontic office and a six-chair general office can have the same count of workstations and still have nothing in common on the server. The orthodontic office stores a photo set for every patient at every timepoint, a cephalometric and a panoramic image, intraoral scans measured in hundreds of megabytes each, and an upload history to one or more aligner labs. The general office stores bitewings. The server, the switches, the internet circuit and the backup were all sized by someone, and if that someone was thinking about bitewings, the orthodontic office is running on the wrong assumptions from day one.

San Antonio adds its own layer. A specialist here draws referrals from the whole metro: general dentists in Stone Oak, Alamo Heights and the Medical Center area, in the suburbs along I-35 toward New Braunfels and Schertz, and in Boerne and the Hill Country edge. Every one of those offices sends images in whatever format its own software exports, and every one of them expects a report back. That is a transfer system, and a transfer system has to be designed, tested and owned by someone.

Then there is the building. Many medical suites, in San Antonio as anywhere, were cabled long before the imaging equipment now in them, and the software problems a specialist reports are often cabling and switch problems in disguise. The commercial page for San Antonio Dentrix and imaging support covers that side for every practice type in the city; this page stays with the specialist. Whatever the platform, the network, server and workstation side of it is set out nationally on Legend's practice management software and imaging IT support page.

What does each specialty run in San Antonio, and where does it break?

Every specialty pairs its own software and capture devices with traffic to outside offices, and each has a weak link that fails first. The table names the products a San Antonio specialist is likely to run, where the chain usually breaks, why, and the one question that tests whether a provider has fixed it before.

Read the rows with three cautions. A product is listed because a specialist in that chair is likely to be using it; the table says nothing about any vendor and nothing about who supports which product. The "what breaks" column describes configuration, sizing and sequencing, not the equipment: the fix is almost never a new unit. And the question in the last column has a checkable answer, which is the point; a provider who answers in generalities has told you what you needed to know.

Legend keeps a separate page for each of these platforms that explains where it sits inside a practice network. Orthodontic offices start with Dolphin Imaging and Management IT support; for cone beam and pan units there is Planmeca and Romexis IT support, Vatech and EzDent-i IT support and Carestream Dental software and imaging IT support; sensor-heavy offices will want DEXIS imaging and IT support; and on the practice software side, Dentrix IT support or Open Dental IT support. When the practice software and the imaging bridge have stopped talking to each other, the troubleshooting order is in dental imaging integration troubleshooting.

Orthodontic offices: what fails between the scanner, the imaging suite and the lab?

An orthodontic office is among the heaviest file-movers in dentistry. Every patient produces photo sets at each timepoint, a ceph and a pan, intraoral scans and the lab uploads that follow them, and the practice software often shares a database server with the imaging suite. The failures sit where those loads meet one workstation, one circuit or one satellite link.

Start with the vendor's own words, because they settle arguments. Dolphin's published system requirements state that "Dolphin Management is not supported running through a WAN directly," that a remote office "must be connected via Remote Desktop Services," and that "if you plan to capture images from the remote office, a local PC and a VPN is required." An orthodontic office with a second location in Schertz or on the far west side that opened its practice software straight across the internet from the main office is not running an unlucky configuration; it is running an unsupported one, and the slow screens and dropped sessions follow from that.

For storage, the figures come from an older Dolphin file, the Minimum Imaging Requirements marked Rev. 03/17, which gives typical sizes of "1MB to 2MB each" for 2D photos and "100MB to 200MB" for cone beam scans, and the note that "the disk space used for an imaging application is at least 100-times that of financial programs." Multiply the photo figure by a full set at every timepoint for every active patient and the server that was sized for the practice management database alone is full within a few years. Dolphin's current system requirements state that its software's performance "is highly influenced by Disk I/O speeds" and recommend SSD drives "for both Workstations and Servers"; the Rev. 03/17 imaging document recommends a "100/1000 network card (gigabit for Dolphin 3D)" with the reminder that "your network will run at the speed of the lowest component." One unmanaged switch under a desk sets the speed for the whole imaging suite.

The scanner is the third load. An intraoral scanner captures locally and then uploads to the lab portal, and uploads use the half of the internet circuit nobody looked at when it was bought. Most business circuits are quoted on their download speed; an orthodontic office's working day is upload. If scans sit in the queue until after close, the fix is usually the circuit's upload figure or a firewall rule, not the scanner. The same scanner is often attached to the workstation that also captures the ceph or runs the photo station, and nobody specified that machine for both. One question from the table applies here: which workstation in your office captures for more than one system?

The one San Antonio orthodontic project on Legend's work pages, Ray Orthodontics on Potranco Road, is described in the proof section below, in the words the work page uses and no others.

Endodontic and periodontal offices: what does CBCT demand of the network and the server room?

A cone beam unit asks three things of an office that bitewings never did: storage that grows by the volume, a wired path fast enough to open those volumes in a room other than the one where they were taken, and a workstation specified by the imaging vendor rather than by whoever bought the last batch of PCs.

Take the storage figure from a vendor rather than from a sales conversation. Planmeca's published Romexis requirements estimate disk use at "between 50 MB to 1 GB per 3D image depending on the volume size and resolution." Arithmetic on the upper end of that range is sobering: ten scans a week at a gigabyte each is roughly half a terabyte a year before any 2D images, photos or the database are counted. Planmeca's page also lists server storage advice of two 1 TB drives in RAID1 mirroring and 16 GB of server RAM as a minimum, and sets workstation RAM by unit, from 8 GB for its smaller ProMax 3D models to 32 GB for its larger Viso models, with a 120 GB hard disk on the client. Your unit may be from a different vendor; the point is that the figure exists, it is published, and your provider should have checked your workstations against it.

The network path is the second demand. The acquisition workstation opens a volume quickly because the data is local. Operatory two opens it across the network, and if there is an unmanaged switch, a Wi-Fi hop or a cable run from a previous tenant in that path, operatory two is where the complaint comes from. For a sense of how much bandwidth these files want, look at what Planmeca writes about its hosted Romexis Image Cloud: for 2D images, "a minimum upload and download speed of 10 Mbps is necessary, while a 100 Mbps or better connection is recommended for 3D images." Inside the office the standard is a managed gigabit switch and a wired drop at every viewing workstation, with imaging on its own segment. How big the circuit should be, which switches to buy and how to split the segments in a San Antonio building is left to a sister piece, dental office network support in San Antonio. For the server itself, Legend's dental office server setup services page covers specification and placement.

Endodontic offices have one more dependency: the referral loop. Your production depends on a general dentist in Helotes or Universal City sending a periapical or a limited-field volume before the patient arrives, and on your report going back. Decide which file formats you will take, how they travel (through a referral portal, by secure upload link, or as the referrer's own export), which folder on your network receives them and whose job it is to watch that folder. Then prove it with one referring office before you announce it to the rest. A report that goes back to the referrer as an ordinary unencrypted email with the radiograph attached is a safeguard question first and a convenience question second; your provider should be able to tell you which method they configured and show it working.

Periodontal and implant offices add the planning stack. Implant planning software has its own workstation requirements, usually above the practice management workstation's, and the exports to a surgical guide vendor have size limits that an export preset handles and a default setting does not. The right order is: check the planning workstation against the vendor requirement, set the export preset once, and put the guide-vendor upload on the list of paths your provider monitors.

Oral surgery offices: what belongs on the clinical network, and what must never share it?

An oral surgery office runs some of the largest imaging volumes in dentistry and the most devices that are not computers: anesthesia and patient monitors, surgical units, implant planning stations, and a hospital VPN client. The IT task is an inventory with a network segment for each class of device and a documented route for every record that leaves.

Begin with the inventory, because the surprises are always there. Walk each surgical suite and write down everything with a network cable or a wireless radio: the monitor, the sedation pump if it reports, the planning workstation, the pan, the CBCT acquisition PC, the camera, the phone. Then ask which of them can reach the practice management server and which of them can be reached from the guest Wi-Fi. In an office that grew one device at a time, the honest answer is usually "all of them" and "all of them." Segmentation puts monitors and surgical devices on a segment that can reach only what they need, puts imaging on its own, and keeps the front desk and guest traffic away from both. Knowing which systems carry patient information and controlling what can reach them is also groundwork your compliance adviser will want to see when your HIPAA risk analysis is reviewed. Legend's HIPAA safeguards support for dental practices page describes the readiness work, and the dental cybersecurity services page covers the protective layers around it.

The operating system on the acquisition workstation is the second check. Imaging and practice software vendors publish the operating systems they support and the dates support ends. Open Dental's requirements page, for example, lists Windows 11 and Windows Server 2016 through 2025 as supported and moves Windows 10 to its formerly supported list, with support suspended on October 14, 2025. A capture PC left on an operating system its maker has dropped is exposed on the security side, and it turns into a compatibility dead end the day the imaging company releases an update that refuses to install. Get a list from your provider: each imaging workstation, the operating system on it now, and the date it moves to a supported one.

The third item is the record that leaves. Hospital credentialing portals, hospital remote-access clients, anesthesia records, sedation logs and implant planning exports each need a route, a format and a named owner. A hospital VPN client installed on the same workstation that captures CBCT volumes is a common shortcut and a poor one; it ties a clinical machine's security posture to a third party's. Where the hospital's client must run, put it on a workstation that does nothing else.

Legend's work pages document two Texas oral surgery projects, Cleburne Oral Surgery and Trinity Valley Oral Surgery & Dental Implant Center in Fate; both are described in the proof section, as Texas projects and not as San Antonio ones.

Pediatric offices: what should never share the clinical network?

A pediatric office carries more non-clinical devices than any other practice: ceiling screens, tablets at check-in, a parent Wi-Fi that is busy from seven to five, and sedation monitoring. The clinical network should be a separate segment that none of those devices can reach, and the sensors should never ride on Wi-Fi.

The common mistake is a single wireless network with one password that parents, staff tablets, the ceiling streaming boxes and a wireless sensor adaptor all share. Streaming to eight ceiling screens through a busy afternoon is a sustained load, and when a sensor capture stalls behind it, the complaint reads as "the x-ray software is slow." The design answer is three segments: clinical (workstations, sensors, server, imaging), entertainment and guest (screens, parent Wi-Fi, check-in tablets, with no route to patient data), and monitoring devices (with only the access they need). Parent Wi-Fi gets its own SSID, its own bandwidth cap and no path to anything clinical. Legend's pediatric dental IT support page carries this design for offices anywhere in the country, and IT network services covers the segmenting itself for every kind of practice.

Two pediatric specifics belong in writing. A pediatric sensor is carried from room to room far more than an adult sensor, and its cable is the first thing to go; budget for a sensor in each operatory, and until then write down who carries it, how, and where it rests between patients. And the front desk of a pediatric office carries more logins than any other: school forms, Medicaid and insurance portals, consent and reminder platforms. Every one of them is a login somebody owns; keep them in a managed password tool with an account per person and multi-factor authentication wherever the portal offers it, so a team member who leaves does not walk out with portal access.

What breaks when it is 100 °F outside and the power blinks?

Heat and power are San Antonio's local failure modes for an imaging room. In 2023 the city logged its 60th 100-degree day, a record; in February 2021 roughly 251,606 CPS Energy customers were without power for more than 24 hours. A cone beam unit, its acquisition PC and the server need cooling, a UPS and a power-return routine.

The sources are local and plain. Texas Public Radio reported on 27 August 2023 that "San Antonio recorded its 60th 100-degree day of the year Sunday, breaking its record for total days at or above the century mark set in 2009," after "a total of 23 days in a row" above 100, itself a record. KSAT reported in April 2021 that, after Winter Storm Uri, "roughly 251,606 customers are eligible to receive the credit" CPS Energy offered to those without power for longer than 24 hours. Neither is a reason for alarm; both are reasons to put two questions to your provider that a general IT plan never asks.

The first is heat. The acquisition PC usually sits in the CBCT room because the cable has to reach the unit, and the server usually sits in a closet that was a closet before it was a server room. On a 100-degree afternoon with the building's cooling working hard, a closet without return air can run well above the room it opens onto, and the first symptom is not a crash but a slowdown and a fan noise nobody connects to the imaging complaints. Ask where the server and the acquisition PC sit, what the temperature in that space is on a summer afternoon, and whether anything measures it.

The second is power. A UPS on the acquisition workstation should carry it through a capture in progress and a clean shutdown; a UPS on the server should carry the server and the switch long enough for a clean shutdown, and should be connected to the server so the shutdown happens without a person. The runtime you need depends on your equipment, so take it from the UPS vendor's sizing tool for your actual load rather than from a rule of thumb. The CBCT unit itself has its own electrical requirements in its installation document and a dedicated circuit is the normal expectation; confirm it from the document for your model. And back up before you need to: Dolphin's requirements document puts the responsibility plainly ("you are responsible for making proper backups of your Dolphin data") and recommends "a proper backup protocol including offsite data backups," which is the same advice for every imaging platform. For the backups themselves, see Legend's dental backup and disaster recovery services page; the shutdown and restart sequence for the entire office belongs to our San Antonio dental IT guide, and the version for the imaging room follows here.

Keep the table on the wall of the server closet. A provider who already has one is a provider who has been through a San Antonio summer and a February with a practice.

Which San Antonio specialty practices has Legend worked with?

Legend Networking's work pages record one orthodontic project in San Antonio and two oral surgery projects elsewhere in Texas; the company's published figures are 3,500+ practices supported, 22+ years in dental IT (since 2004), a 4.8 rating · 173 Google reviews, and in-house engineers; no outsourced first-level triage.

Ray Orthodontics, San Antonio. The work page states that Legend Networking supported the technology setup for Dr. Andrew Ray's new orthodontic office on Potranco Road in San Antonio, coordinating the systems needed for opening day. It is recorded as an orthodontic startup with a project update dated 16 June 2026 and nine photographs. The page does not list the imaging or scanning systems the office runs, so this article does not either.

Cleburne Oral Surgery, Cleburne, Texas. The work page records a brand-new oral surgery center launch in Cleburne, Texas, with Legend Networking delivering the technology foundation behind the practice: secure infrastructure, reliable connectivity, and day-one readiness. Project update 25 February 2026, four photographs. Cleburne is south of Fort Worth; it is named here as a Texas oral surgery project, not a San Antonio one.

Trinity Valley Oral Surgery & Dental Implant Center, Fate, Texas. The work page records a practice expansion in which Legend's team installed the IT infrastructure for Trinity Valley's Fate location, with a published scope that includes workstations, networking and Wi-Fi, backups and phone integration. Project update 19 June 2025, five photographs. Fate is east of Dallas; again, a Texas project.

The operating model behind all three is what a specialist should ask any provider to put in writing. Two things are published separately: 24/7 monitoring of the systems, and the staffed hours, which are Help desk Mon–Fri 7 AM–7 PM CT, Saturday 8 AM–2 PM CT; 24/7 critical/emergency line. San Antonio is on Central Time, so those hours read exactly as written; no conversion is needed. For visits, Legend's published position is onsite dispatch by appointment across served dental markets; remote-first nationwide. Before signing, have Legend spell out in writing what that means for your San Antonio address. Legend Networking's headquarters are in Dallas, Texas. Ian Lynch brings 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps.

On cost, the published figures are flat monthly plans of $399.99–$1,200 per practice per month, with hardware procurement, major cabling projects and software licensing quoted separately. That last clause matters more to a specialist than to anyone: wiring the cone beam unit's circuit, running cable to the second operatory and buying the imaging software licence are separate project lines rather than part of the monthly fee, and a quote that mixes them deserves a second look.

Every San Antonio practice, specialist or not, can begin at IT support for San Antonio dental practices; our San Antonio dental IT guide pulls the metro's managed IT, startup, network and continuity topics together in one overview.

What should a San Antonio specialist ask an IT provider?

Ask questions whose answers can be checked against a document, a screen or a named office. The twelve below are written for a specialist who has already paid one provider to learn dentistry on the job; each has a specific answer, and a general answer is itself the information you needed.

• • [ ] Which vendor requirement documents do you keep on file for my imaging units and software, and when did you last check my acquisition workstation against them? The documents exist (Dolphin, Planmeca and Open Dental all publish theirs); a provider who has never opened them has never specified a workstation for you.
• • [ ] Show me the storage graph for my imaging share. How much is free today, how fast is it filling, and on what date do you expect it to be full?
• • [ ] Which workstation in my office captures for more than one system, and was it specified for both? The scanner-plus-ceph machine in an orthodontic office is the usual answer.
• • [ ] How is my second location connected, and does that match the vendor's remote-office requirement? For an orthodontic office running Dolphin, the vendor's own document answers this; ask the provider to show you where.
• • [ ] List every device on my network that is not a computer, the segment each one sits on, and who put it there. Monitors, screens, scanners, cameras, phones, streaming boxes.
• • [ ] What is the route for an inbound referral image, where does it land, and who tested it with the last new referring office? If the answer is "email," ask what happens to the attachment.
• • [ ] When an aligner or guide upload fails at four in the afternoon, who finds out first: the lab, my treatment coordinator, or your monitoring?
• • [ ] What does the UPS on my acquisition workstation carry, for how long, and when was its battery last tested? The same question for the server and the switch.
• • [ ] After a CPS Energy outage, what do you check before I take the first image, and is it written down? Compare the answer to the table above.
• • [ ] Which antivirus exceptions and update windows are set for my imaging software, and who tests a capture the morning after a patch? Imaging vendors publish exception lists; an update that applies at 2 AM with no test capture at 7 AM is how a full Tuesday starts without a sensor.
• • [ ] Which of my operating systems is past its vendor's support date, and what is the replacement date for each machine?
• • [ ] Name the specialty office nearest to mine that you support and what you did there in the last year. A named practice on a public page beats a logo wall.

Write the answers down. Three months in, those notes are the yardstick for the provider you chose; if it falls short, they become the starting brief for whoever replaces it.