Specialty Dental Practice IT in the Bay Area: Ortho, Perio, Oral Surgery and Endo Across Several Offices
Your main office is in Walnut Creek, and two days a week the schedule moves to a smaller suite in Pleasanton. On Tuesday the satellite assistant opens a chart and the previous visit's progress photos will not load, while your referral coordinator learns that a San Mateo dentist's CBCT scan bounced because the email was too large.
Ongoing support for offices from the city to the East Bay and the Peninsula is described on our dental IT company in San Francisco page. Our dental IT in the Bay Area guide covers utilities, building stock and internet across the region. This article stays with the questions that belong to specialists: orthodontists, periodontists, oral surgeons and endodontists who run more than one location or who depend on a steady flow of referrals. We cover which files each specialty depends on, how records reach part-week offices, how referral images should travel, what a surgical suite's network needs, what CBCT means for the link between offices, what to standardize first and how to move a specialty office without losing a week of production.
Specialty dental practice IT in the Bay Area means doing four jobs well. Move large imaging files between your offices and your referring dentists safely. Keep one source of truth for charts and images. Put clinical devices on their own protected network. Make every office identical, so a satellite day starts without surprises.
- Specialty dental IT in the Bay Area is mostly about distance and file size: offices across counties, many referrers and large imaging files.
- Keep one record and one imaging design that every office reaches, and make satellites identical to the main office.
- Publish one secure way for referring dentists to send scans, check it at set times and confirm receipt.
- Put sedation and patient monitors on their own segment, on battery-backed power, following the device maker's requirements.
- Measure your own CBCT file sizes and transfer times before you design the network between offices.
- Book imaging vendor windows first when you relocate, and tell referrers before the move.
In this guide
- Why do Bay Area specialists face different IT problems than general practices?
- Which systems and files does each specialty depend on?
- How should an orthodontist share records between a main office and satellites?
- How should referral images move between general dentists and specialists?
- What network does a surgical suite with sedation monitors need?
- What do CBCT files mean for the network and internet between offices?
- Which differences between offices should a specialty group remove first?
- What should a specialist plan before relocating a Bay Area office?
- Which systems should a specialist ask a provider to list in writing?
- What has Legend published from the East Bay?
- What to ask your IT provider
- Key takeaways
- Sources
- Frequently asked questions
- The bottom line
Why do Bay Area specialists face different IT problems than general practices?
Specialists here spread their work across more places and handle larger files. A Bay Area orthodontist or periodontist often splits the week between offices in different counties, receives scans from many general dentists and runs imaging or surgical equipment a general office may never own. Each gap between those places is where a file, login or device can fail.
Geography does a lot of the damage. The region is a ring of cities around the water, joined by bridges and long freeway corridors. A practice with a main office in Oakland and a satellite in San Mateo crosses a bridge every time someone has to visit the second site. A group with offices in Palo Alto and Los Gatos sits in two different counties, often with two different internet providers, two landlords and, in Palo Alto's case, a city-run electric utility instead of PG&E. The more the practice is spread out, the more it depends on systems that work the same way everywhere without someone on hand to nudge them.
Referrals do the rest. In dense areas such as San Francisco, the Peninsula and the 680 corridor, a single periodontist or endodontist may receive scans, radiographs and notes from dozens of general practices. Each of those practices runs its own imaging software and its own habits. Some send a link, some attach a file to an email, some still mail a disc. Your systems have to accept all of it, keep it organized and send a report back without exposing patient data along the way.
Staff time makes every failure more expensive. In May 2025, dental hygienists in the San Francisco-Oakland-Fremont metro earned a mean annual wage of $180,520, against $98,990 nationally, according to the Bureau of Labor Statistics. When imaging will not load at a satellite, the clinical team is still on the clock while someone works out why.
The problems specialists describe tend to fall into a short list:
- Images that never reach the referrer, or arrive without the patient's name attached.
- Satellite days that start broken: a workstation that missed a month of updates, a sensor that lost its driver, a printer that no longer exists on the network.
- Different software versions in different offices, so a chart or a 3D volume opens in one place and fails in the other.
- Surgical and monitoring equipment on the same flat network as the front desk and the guest Wi-Fi.
- Relocations at lease end that take imaging offline for longer than anyone planned.
- Email used for scans that are too large, too sensitive or both.
Each section below takes one of these and turns it into something you can check this week.
Which systems and files does each specialty depend on?
Each specialty leans on a different mix of imaging, capture devices and software, and each sends different files to different people. Orthodontists move photos, scans and cephalometric images between offices. Periodontists and endodontists receive referral imaging. Oral surgeons protect a surgical suite. Knowing your mix tells you where the network and backup effort should go first.
Treat the table below as a planning sheet. Named imaging systems are those Legend lists among the systems it supports; anything else is described as a type of device you may run. Use it to mark which rows apply to you and where your current setup is weakest.
| Specialty | Imaging and capture you may run | Files that move, and between whom | When an outage hurts most | Network note |
|---|---|---|---|---|
| Orthodontics | Intraoral scanner, cephalometric and panoramic imaging, clinical photo stations, an imaging and treatment-planning system such as Dolphin Imaging | Photos, scans and ceph images from every chair to one record; scans out to aligner or appliance labs; records between the main office and satellites | A heavy records or consult day, when every new-patient workup needs photos, scans and a ceph image in the chart before the doctor sees the patient | Satellites need the same access to the record as the main office; sending scans to labs depends on each office's outbound speed |
| Periodontics | CBCT, intraoral sensors, implant-planning software, intraoral scanner | CBCT volumes and radiographs in from referring dentists; planning files and reports back out; guides or files to labs | Surgical consult days, when the referral image must be in the chart before the patient sits down | A single, well-known way for referrers to send large files; enough storage for 3D volumes; tested restores |
| Oral and maxillofacial surgery | CBCT, panoramic imaging, patient and sedation monitoring equipment, surgical-suite displays | Referral imaging in; operative notes and images back to the referring dentist; images to hospital or lab when needed | During a procedure, when monitors, displays and records must keep working regardless of what the front desk is doing | Clinical devices on their own segment; UPS on the monitoring path; wired connections where the device maker calls for them |
| Endodontics | Intraoral sensors, CBCT (limited field of view in many offices), operating microscope with camera | Pre-op radiographs and CBCT in from referrers; post-op images and reports back out, often the same day | Mid-procedure, when a sensor or the microscope camera drops and the case is open | Sensor and camera drivers matched to each workstation; reports that reach the referrer without a phone call |
Two patterns stand out when practices fill this in. Orthodontic groups are usually weakest on keeping satellites in step with the main office, and surgical specialties are usually weakest on separating clinical devices from everything else. Periodontists and endodontists, who live on referrals, are usually weakest on intake: there is no single, published way for a referring office to send a large scan.
For deeper national guides on each specialty, see our pages on IT for orthodontic practices, periodontal practices, oral surgery practices and endodontic practices.
How should an orthodontist share records between a main office and satellites?
Keep one record and let every office reach it. Store the practice management database and the imaging database in one place, either a well-protected server at the main office reached over a secure site-to-site connection, or a cloud-hosted system. Avoid separate copies at each office that someone tries to keep in sync by hand.
The choice between a central server and a cloud system depends on your software and on the internet at each site. A central server keeps large image files close to the main office and gives you control over backups, but the satellite is only as good as the connection between the two buildings. A cloud system removes the server from your closet, but each office then needs dependable internet for every chart it opens, and imaging may still need local processing. Neither is right for everyone. The decision rules below help:
- If most images are created and viewed at the main office, and satellites mainly need charts, photos and the schedule, a central server with a site-to-site connection usually works well. Test how long a typical photo set takes to open at the satellite during a busy hour before you commit.
- If every office captures heavy imaging every day, consider whether imaging should live where it is captured, with one viewing system that reads from each location. Ask your imaging vendor what it supports for multi-site use, in writing.
- If internet at a satellite is weak or shared with other tenants, do not make that satellite depend on a live connection for every chart. Fix the connection first, or keep a read-only fallback for the day.
- If you are considering a cloud practice management system, ask what happens at the satellite when the internet drops, and whether imaging works offline.
Part-week offices bring their own problem: equipment that sits idle. A satellite open on Tuesdays and Thursdays may miss updates scheduled on other days, then install them all on Tuesday morning while patients wait. A simple routine fixes most of it:
- Schedule updates for the satellite's open days, outside clinical hours, or wake the computers remotely the night before.
- Run a first-morning check: every workstation signs in, the chart opens, a test photo saves and the scanner connects.
- Keep a printed card in the satellite listing who to call and what to try first.
- Keep the satellite's computers, printers and scanners on the same models and settings as the main office, so a fix at one works at both.
Groups whose satellites are in the South Bay can read more about ongoing coverage on our page for San Jose dental IT services. Our national guide to IT for orthodontic satellite offices goes further into scheduling and remote access.
How should referral images move between general dentists and specialists?
Give referring offices one clear, secure way to send large files, publish it, and confirm receipt. A secure upload portal or the share feature inside your imaging system usually works best for CBCT volumes and full radiograph sets. Email works only for small files and only with encryption. Discs and USB drives are a last resort.
Practices that rely on referrals rarely choose how referrals arrive. They take whatever comes. The result is a referral coordinator checking three email addresses, a fax line, a shared folder and a stack of discs. A better approach is to choose one primary method and one fallback, then tell every referring office how to use them.
| Method | Good for | Watch-outs | What to ask your IT provider |
|---|---|---|---|
| Secure upload portal or link (a web page where a referring office uploads files, with a login or one-time link) | CBCT volumes, full-mouth series, large photo sets; referrers with any imaging system | Links that never expire; files left in the portal after import; nobody checking it on busy days | Who can see uploaded files? How long do they stay? Is there a log of who uploaded and who downloaded? Who is notified when a file arrives? |
| Share inside your imaging system (sending a study between offices that use compatible software) | Repeat referrers on compatible systems; between your own offices | Works well only when both sides run compatible versions; can tempt staff to share whole databases | Which versions are compatible? Can we share one study instead of opening our database? How do we revoke access? |
| Encrypted email | Small files, reports, single radiographs, letters back to the referrer | Attachment size limits; patients' names in subject lines; replies that drop encryption | Is encryption automatic or does staff have to remember? What is the size limit? What happens when a referrer cannot open an encrypted message? |
| Physical media (disc or USB drive) | A referrer with no other option; very large archives | Lost or unlabeled media; malware on USB drives; no record of who handled it | Who scans media before it is opened? Where is it stored, and when is it wiped or returned? |
Whichever method you choose, the safeguards are the same: limit who can open referral files, encrypt them in transit, keep a record of who accessed them and remove copies you no longer need. What the law requires of your practice in a given case is a question for your compliance adviser or attorney; your IT provider's job is to make the safeguards work and to show you that they do.
Three habits make referral intake reliable:
- Publish a short "how to send us images" page for referring offices, with the portal link, the file types you accept and a phone number for questions.
- Name one person who checks referral intake at set times each day, with a backup when that person is out.
- Confirm receipt to the referring office, so nobody resends a scan through a less safe channel because they were not sure it arrived.
Our national guide to sharing referral images in a periodontal practice works through the referrer's side of this in more detail.
What network does a surgical suite with sedation monitors need?
A surgical suite needs its clinical devices on their own network segment, wired where the device maker calls for it, on battery-backed power and kept away from guest Wi-Fi and general office traffic. Start with each device maker's network and power requirements, then design around them, and write the result down so nobody changes it casually.
Oral surgery offices, and periodontal offices that sedate, run equipment where an interruption matters more than a slow chart. Patient monitors, displays in the operatory, imaging stations and sometimes a central monitoring screen all share the building's network with the front desk, the phones and, too often, the guest Wi-Fi. A misbehaving laptop or an overloaded switch should never be able to affect a monitor in the middle of a procedure.
A sound surgical-suite design usually includes:
- Separation. Clinical devices on their own network segment (a VLAN or a separate physical network), with rules that allow only the traffic each device needs.
- Wired connections for anything the device maker says must be wired, and for imaging stations in general. Keep operatory Wi-Fi for convenience devices, and give clinical equipment that the maker expects on a cable its own wired port.
- Battery-backed power for the monitors, the switch they connect through and the network closet, sized so equipment can finish a procedure or shut down cleanly.
- Controlled change. No firmware updates, cable moves or new devices in the surgical segment without a plan, a time outside procedures and a test afterward.
- Documentation. A drawing that shows which port each clinical device uses, which segment it is on and who supports it: your IT provider, the device maker or both.
Two points need care. First, the device maker's instructions win. If a monitor's manufacturer specifies how it must be connected, your network is designed around those instructions. Second, responsibility needs to be clear. Your IT provider looks after the network and the computers; the device maker or its service company looks after the device. Write down who to call for which symptom before you need to.
Older buildings add their own limits, especially in San Francisco and Berkeley, where a converted Victorian or a mid-century mid-rise may not have a sensible path for new cable. Where closets and cable runs can realistically go in those buildings is the subject of our dental office network cabling in San Francisco guide. For the national view of surgical networks, see network design for oral surgery offices with sedation monitors.
What do CBCT files mean for the network and internet between offices?
CBCT volumes are much larger than standard radiographs, and their size depends on the machine, the field of view and the settings you use. Check your imaging vendor's specifications for a typical scan, then measure how long that scan takes to move inside your office and between offices. Then plan the network and internet from those measurements.
We do not quote file sizes or transfer times here, because they vary too much between machines and settings to be useful as a general number. What you can do is measure your own situation in an afternoon:
- Pick a typical scan. Ask the person who runs the CBCT to export or locate a scan with your most common field of view and settings, and note its size.
- Time it inside the office. Open that scan on a viewing workstation in an operatory during a normal clinical hour. If it takes long enough that the doctor waits, look at the cable run, the switch and the workstation before you look at anything else.
- Time it between offices. Open or copy the same scan from your other office, at a busy time of day. That number tells you whether satellites can work from a central image store.
- Check outbound speed at each site. Files you send to referrers, labs or a cloud backup travel on the line's sending side, which on many business connections is slower than the receiving side. Ask each carrier what sending speed the office actually has, then test it.
- Check where viewing happens. Some imaging systems send the whole volume to the viewing computer; others process it on a server and send images. Ask your vendor which yours does, because it changes what the network has to carry.
Storage and backup follow from the same numbers. A periodontal or surgical office that takes CBCT scans every day adds up a large archive quickly. Ask your IT provider how much space the imaging archive uses now, how fast it is growing, how long a full restore of the imaging database would take and when that restore was last tested.
Our national guide to CBCT computer and network requirements explains the workstation side, including what to check before buying a viewing computer.
Which differences between offices should a specialty group remove first?
Standardize the things that decide whether a chart and an image open the same way everywhere: software versions, the imaging database design, backups, user accounts and the workstation build. Then standardize the devices and the documentation. A group that does this can fix a problem once and know the fix works at every office.
Groups usually grow one office at a time, and each office arrives with its own history: a different firewall, a printer nobody else has, a computer that runs a slightly older imaging version because the sensor driver never got updated. Each difference is small. Together they make every satellite a special case. Work through this checklist in order, because the early items unblock the later ones.
| # | Standardize | Why it comes at this point | What "done" looks like |
|---|---|---|---|
| 1 | Practice management software version | Mismatched versions break charts, reports and integrations | Every office on the same version, updated on the same night |
| 2 | Imaging software version and database design | 3D volumes and photos must open the same way in every office | One documented design: one database or a defined set, with every workstation pointing to the right one |
| 3 | Backups and restores | A group is only as safe as its weakest office | One backup design for every site, with a tested restore of each office on record |
| 4 | User accounts and sign-in | Staff float between offices; shared logins hide who did what | One account per person, multi-factor sign-in on email and remote access, accounts removed the day someone leaves |
| 5 | Workstation build | A fix that works on one computer should work on all | The same Windows version, settings, drivers and software list on every clinical workstation |
| 6 | Naming | Nobody can support "the computer in the back" | Every computer, printer, shared folder and network named the same way at every office |
| 7 | Sensors, scanners and printers | Drivers and spare parts are easier when models match | One or two models per device type across the group, with spares stored centrally |
| 8 | Firewall and network design | A known design is easier to secure and to troubleshoot | The same firewall model and the same segment layout at each office, documented |
| 9 | Phones and call routing | Patients call one number and expect to reach the right office | One phone system, with call flows that follow the schedule of each office |
| 10 | Documentation | When someone new takes over, the group should not depend on memory | One documentation set covering every office, owned by the practice, updated after each change |
Two cautions apply. First, standardization takes time, so fit it around your clinical calendar. Plan version changes for evenings or days off, one office first, then the rest once the first is confirmed. Second, decide whose decision each item is. Software and imaging versions usually need the vendor's agreement; the network, accounts and backups are your IT provider's job; the choice of devices is often the doctor's.
Specialty groups that are growing toward a dental support organization model will find the governance side covered in our page on DSO IT support.
What should a specialist plan before relocating a Bay Area office?
Plan the imaging move first, because it takes the longest to bring back. Book the imaging vendor's removal, reinstall and calibration windows as soon as you have a move date, get the CBCT room's cabling and power into the build plan, order internet early, and tell referring offices before the move so referrals do not stall.
Bay Area specialists move for the usual reasons: a lease ends, rent goes up, a better suite opens nearer the referral base, or a group consolidates two offices into one. A specialty move differs from a general practice move in one main way: the imaging equipment. CBCT units, panoramic and cephalometric machines usually need the manufacturer or its service company to remove, reinstall and calibrate them, and those visits are booked in advance. If the imaging is not ready on the first day, the specialty schedule is not either.
A relocation plan for a specialty office should cover at least:
- Imaging vendor windows. Ask the vendor, in writing, for the removal date, the reinstall date and the calibration date, and who confirms the unit is ready for patients.
- The imaging room. The CBCT room's power, data drops and any construction the manufacturer requires belong in the contractor's drawings before the walls close. Your contractor handles permits; your IT provider makes sure the data drops and the closet are where the equipment needs them.
- The network closet and internet. Place the internet order the week the new address is final, find out which carriers already reach the building, and run both offices' service in parallel until the new line has been tested.
- The data move. Decide whether the server, the imaging database or both are moving physically or being copied, and keep a verified backup taken just before the move.
- Referral continuity. Update the "how to send us images" page, the referral forms, the address on reports, and the fax and phone routing. Tell your top referring offices directly.
- A first-day test. Before the first patient, a scan is taken, saved to the right chart, opened in an operatory and sent to a referrer as a test.
The general relocation and opening checklist, including what to inspect in a suite before signing, sits in the dental startup IT in the Bay Area guide.
Which systems should a specialist ask a provider to list in writing?
Ask every provider for its supported practice management and imaging systems in writing, with versions. Legend, for example, lists Dentrix, Eaglesoft, Open Dental and Archy among the practice management systems it supports, and DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging among the imaging systems. If your specialty runs on something else, ask how it would be supported.
Specialists tend to run a narrower and more demanding set of software than general offices, so it is fair to ask any provider for its list before anything else. For two systems that matter to many specialty offices, see our pages on Dolphin Imaging IT support and Planmeca Romexis IT support.
Here is how Legend Networking describes its own work. Legend has 22+ years in dental IT (since 2004), with 3,500+ practices supported, and is headquartered in Dallas. It uses in-house engineers; no outsourced first-level triage. Systems have 24/7 monitoring, and the helpdesk is staffed 24/7 at 1-800-794-1588. The delivery model is "Onsite dispatch by appointment across served dental markets; remote-first nationwide." Day-to-day software and support issues are handled remotely; cabling, installations, equipment moves and new-office build-outs are scheduled onsite by appointment. Ian Lynch's published role reads: "Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps."
On price, as of November 2026, Legend's ongoing support is "Starting at $360 per month." Hardware procurement, major cabling projects and software licensing are quoted separately, which matters for specialists, whose imaging workstations and storage are often the largest hardware line. Our page on IT support for dental offices in San Francisco covers what ongoing support looks like for practices across the city and the East Bay.
If you would like someone to look at your imaging, referral intake and multi-office setup before you change anything, ask for a Free Dental IT Assessment.
What has Legend published from the East Bay?
As of November 2026, Legend's published project in the area is an East Bay opening. Its Kanopi Kids Dental & Orthodontics page marks that Antioch practice's March 2025 grand opening, with photos and the original post. The page describes no installation work, so none is described here.
As of November 2026, Legend's Google reviews read 4.8 rating · 173 Google reviews. When you compare providers, ask each one for project pages and references from practices like yours, and read reviews for mentions of imaging and multi-office work in particular.
What to ask your IT provider
Use these questions in your next conversation with your current provider or with anyone quoting for your practice. The answers should be specific and written down.
- Which practice management and imaging systems do you list among those you support, and which versions are we running at each office?
- Where does our imaging database live, and what happens at a satellite when the connection to it drops?
- How do referring offices send us large scans today, and who can see those files once they arrive?
- When was each office's backup last restored as a test, and how long did the imaging restore take?
- Are our sedation and patient monitors on a separate network segment? Show me the drawing.
- What battery-backed power protects the monitors, the switch they use and the network closet?
- How do satellite workstations get updates if the office is open only part of the week?
- Does each staff member have their own sign-in, with multi-factor sign-in on email and remote access?
- Before we move or open an office, who books and coordinates with the imaging vendor, and who confirms the scanner works before the first patient?
- Do we own our documentation, admin passwords and licenses, and where are they kept?
Key takeaways
- Specialty dental IT in the Bay Area is mostly about distance and file size: offices across counties, many referrers and large imaging files.
- Keep one record and one imaging design that every office reaches, and make satellites identical to the main office.
- Publish one secure way for referring dentists to send scans, check it at set times and confirm receipt.
- Put sedation and patient monitors on their own segment, on battery-backed power, following the device maker's requirements.
- Measure your own CBCT file sizes and transfer times before you design the network between offices.
- Book imaging vendor windows first when you relocate, and tell referrers before the move.
Sources
- BLS OEWS, May 2025 estimates (retrieved from the BLS public data API on 2026-11-09): dental hygienists' mean annual wage was $180,520 in the San Francisco-Oakland-Fremont metro and $98,990 for the United States.
- Palo Alto city utility: About CPAU (opened by the cluster researcher on 2026-11-09).
- Legend Networking, Kanopi Kids Dental & Orthodontics project page, accessed 2026-11-09.
Frequently asked questions
How should a Bay Area orthodontist share records between a main office and satellites?
Keep one practice management record and one imaging design that every office reaches, either a central server with a secure site-to-site connection or a cloud system. Avoid separate copies kept in sync by hand. Test how long a typical photo set takes to open at the satellite during a busy hour, and give part-week offices a first-morning check.
What is the safest way for a Bay Area periodontist to receive CBCT scans from referring dentists?
Offer one secure upload portal or link, or use the share feature in your imaging system for referrers on compatible software. Limit who can open uploaded files, keep a log of access and remove copies after import. Publish a short page telling referrers how to send scans, check intake at set times and confirm receipt so nobody resends by email.
What network does an oral surgery suite with sedation monitors need?
Put clinical devices on their own network segment, separate from the front desk and guest Wi-Fi, and use wired connections wherever the device maker calls for them. Protect the monitors, their switch and the network closet with battery-backed power. Follow each manufacturer's requirements, control changes in the surgical segment and keep a drawing showing which port each device uses.
Should a multi-office endodontic practice in the Bay Area keep one imaging database or one per office?
It depends on where images are captured and how good the connections between offices are. One database is simpler to back up and lets every office see every image, but satellites then depend on the link. Separate databases suit offices that capture and view locally. Ask your imaging vendor what it supports for multiple sites, and measure before choosing.
What should a specialist check before moving a Bay Area practice to a new suite?
Book the imaging vendor's removal, reinstall and calibration dates first. Get the CBCT room's power and data drops into the contractor's drawings before walls close, order internet as soon as the address is settled and keep the old service until the new one is tested. Update referral forms and portal details, and test a scan end to end before the first patient.
Which systems should a Bay Area specialist ask an IT provider to list in writing?
Ask for the practice management and imaging systems the provider supports, with versions, and compare them with what each of your offices runs. As an example, Legend lists DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging among imaging systems and Dentrix, Eaglesoft, Open Dental and Archy among practice management systems. If one of yours is missing, ask how it would be supported.
How large are CBCT files, and what does that mean for internet between offices?
CBCT files are much larger than standard radiographs, and their size depends on the machine, the field of view and the settings, so check your imaging vendor's specifications. Then measure: time a typical scan opening in an operatory and copying between offices at a busy hour, and confirm each office's sending speed with its carrier. Design the connection from those measurements.
Why does a chart open at the main office but fail at a Bay Area satellite?
Usually because the offices have drifted apart: different practice management or imaging versions, workstations built differently, or a satellite pointed at the wrong imaging database. Fix it by matching software versions first, then the imaging database design, backups, one account per person and the workstation build. Change one office first, outside clinical hours, then roll the change out.
The bottom line
Whether your offices sit in Oakland and San Mateo or in Palo Alto and Los Gatos, the place to start is a clear picture of where your records live, how referrals arrive and what each satellite depends on. Ask for your Free Dental IT Assessment, and bring a list of your offices, imaging systems and the ways referring dentists send you scans today.

