Dental Office Technology: The Stack a New Practice Needs and How Each Piece Connects
The practice-software rep wants a signature this week. The equipment dealer has quoted a sensor, a pan and an imaging licence as one bundle. Nobody has yet asked how it will all connect once the office is built.
Meanwhile the phone company wants a line count. This page maps the stack layer by layer, shows what each piece depends on, and gives you two tools no vendor quote includes: a list of integrations to test before opening and a register of the documents to collect from each vendor. When and in what order the whole build happens belongs to the full startup technology guide; this page stays on what the systems are and how they connect.
Dental office technology is the set of systems a practice runs on: practice software, imaging, computers, the network, email and logins, phones and patient messaging, payments, security and backup, and the room screens and cameras. For a new office, choose them as one connected stack: decide the practice software first, then check that every other purchase works with it.
In this guide
- What dental office technology does a new practice run on?
- Cloud or on-site practice software: what changes in the rest of the stack?
- How do imaging systems connect to practice software?
- Which computers and screens does each role need?
- Phones, patient messaging and payments: how do they plug into the practice software?
- Who should own the email, logins and accounts?
- How do security and backup cover the whole stack?
- How do the pieces depend on each other?
- Which integrations must be tested before opening?
- What should you collect from each vendor before buying hardware?
- How does the stack differ by specialty?
- What do new-office stacks look like in practice?
- After opening: how do you keep the stack current?
- What to ask your IT provider about the stack
- Frequently asked questions
- The bottom line
What dental office technology does a new practice run on?
A new dental office runs on about ten connected layers. Practice software sits at the centre; imaging, phones, messaging, payments and claims plug into it; the network, computers and logins carry it; security and backup protect it. Each layer has a dependency and a point in the build by which it should be decided.
Most quotes you receive cover one layer. The table puts them side by side so you can see which decision unlocks which. The "decide by" column uses the build milestones from the startup guide, not calendar dates, because timing varies by market, landlord and carrier.
Table A. The stack in layers
| Layer | What it does | Depends on | Decide by |
|---|---|---|---|
| Practice software | Schedule, chart, treatment plans, ledger, insurance claims | Hosting choice (on-site server or vendor cloud), internet, logins | Before the floor plan is final |
| Imaging | Captures and stores X-rays, intraoral photos, pan and CBCT scans | Practice software bridge, capture computers, storage location | Before the floor plan is final |
| Clinical devices | Sensors, intraoral cameras, scanners, CBCT, mills and printers | Imaging software, USB or network connection, room power and placement | Before low-voltage rough-in |
| Network and internet | Carries every other layer; the firewall guards the edge | Cabling, closet, carrier service at the address | At lease review for the carrier; before rough-in for cabling |
| Identity and email | Who can sign in to what; the practice's email domain | A tenant owned by the practice entity, MFA | Before staff are hired |
| Computers and screens | Front desk, operatory, imaging, doctor and back-office workstations | Vendor requirements of the software they run | After software is chosen, before equipment delivery |
| Phones and patient messaging | Calls, call routing, texts, reminders, online forms | Internet, the practice software integration, number porting | Once the address and the opening date are firm |
| Payments | Card terminals and online payments posting to the ledger | Practice software integration, network segment | With the phone and messaging choices |
| Security and backup | Protects data, watches for trouble, restores after loss | Every data store above, written ownership | Before the first patient record is created |
| AV and cameras | Operatory screens, waiting-room displays, door and security cameras | Cabling, power and mounting in the room plan | Before low-voltage rough-in |
Two things stand out once the layers sit together. First, almost everything depends on the practice software choice, so that decision cannot wait for the contractor. Second, three layers (the network, AV and cameras, and device placement) have physical work that is far cheaper while walls are still open; the technology decisions during dental office design guide covers where each item goes room by room.
Cloud or on-site practice software: what changes in the rest of the stack?
Cloud-hosted practice software moves the database and its server to the vendor, so the office leans harder on internet service, browser performance and logins. On-site software keeps a server in the closet, which then needs power protection, backup and patching. Imaging often stays local either way, so ask where images will live before deciding. Whichever model you choose, managed IT services for dental practices are meant to keep the server or cloud setup patched, backed up and monitored after opening.
The trade is not "cloud means no equipment." It is a shift in which equipment matters most.
What moves when the practice software is vendor-hosted
- The database and the server that runs it.
- Software updates to the core application, which the vendor schedules.
- Part of the backup duty for the chart and ledger (ask the vendor to state which data it backs up and how you would export it).
What stays in the office regardless
- Workstations at the front desk, in each operatory and wherever imaging is captured.
- The network, Wi-Fi and firewall, now carrying every click to the vendor.
- Imaging capture, and often imaging storage, unless the imaging product is also cloud-based.
- Printers, scanners, card terminals and the phone system.
What becomes more important with cloud
- A business-grade internet service, and a plan for what the front desk does when it drops.
- Strong logins: if the chart lives on the internet, a stolen password is a stolen chart.
Many new practices weigh Dentrix, Eaglesoft, Open Dental and Archy alongside cloud products such as Curve and Denticon, and some groups use CareStack. Legend supports the IT environment of Dentrix, Eaglesoft, Open Dental and Archy, with platform pages for Dentrix, Eaglesoft, Open Dental and Archy. This page does not rank products; which one fits your workflow is a choice between you and the vendors.
If you are weighing a server against hosting more broadly, the trade-offs are set out in cloud or on-site server. For a new office the useful question is narrower: which of your other systems (imaging, payments, messaging, the phone integration) does the vendor publish as supported for the hosting model you are choosing?
How do imaging systems connect to practice software?
Imaging connects to practice software through a bridge: a link that opens the imaging program with the right patient already selected, so images file to the correct chart. Sensors and cameras plug into a capture computer in the operatory, images are saved to a shared store, and every workstation that views them needs the viewer installed.
A new office usually ends up with more than one imaging product. An intraoral sensor and camera, a pan or CBCT unit, and sometimes an intraoral scanner can each arrive with their own software. For each one, four things need an answer before you buy:
- The bridge. Does the imaging product have a published bridge to the practice software you chose, and in which direction does the patient selection flow?
- The capture computer. Which computer in which room captures the images, and what connection does the device use (USB to the workstation, or a network connection to the unit)?
- The storage location. Where do the images live: on a local server or storage device, on the capture computer, or with a cloud service? Large 3D scans make this decision matter more than it does for a two-dimensional sensor.
- The viewers. Which rooms need to view each image type? CBCT volumes, for example, usually need their own viewing software on the doctor's and consult-room workstations, not only the room where the scan was taken.
Orthodontic practices add a records layer. Dolphin Imaging is common for cephalometric tracing, photos and treatment records, and it has its own bridge and storage questions next to the practice software.
Legend supports the IT environment of DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, with platform pages for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. How software and imaging are looked after once the office is open is set out under practice-software and imaging support.
Room power, unit placement and the electrical work an imaging unit may need are site preparation, covered in the new dental office IT setup guide. Ask the equipment vendor for its site-preparation document and file it with the others in Table D below.
Which computers and screens does each role need?
Each workstation should be specified by the most demanding software it runs, not by job title. Front desk machines run the practice software, scanning and card terminals; operatory machines add sensor capture and viewing; imaging and doctor stations carry the heaviest viewers. Collect each vendor's requirements document first, then size the computer to the strictest one.
The operating system choice is already made for you. Microsoft's lifecycle page states that Windows 10 "will reach end of support on October 14, 2025"; that date has passed, so a new office buys current Windows 11 machines. Use the professional edition: Open Dental's own requirements page notes that "Home editions of Windows are sometimes unacceptable because of connection and networking limits," and other vendors publish similar edition rules in their own documents.
Table B. Workstations by role
| Role or room | What drives the spec | Document to check |
|---|---|---|
| Front desk | Practice software, document scanner, card terminal, phone softphone if used, dual monitors for schedule and ledger | Practice software requirements; scanner and payment-terminal compatibility list |
| Operatory (hygiene) | Practice software, sensor capture, intraoral camera, patient-facing screen | Sensor and camera driver requirements; imaging software workstation requirements |
| Operatory (doctor) | Everything in hygiene plus 3D viewing if CBCT is in the plan | CBCT viewer requirements (graphics and memory) |
| Imaging or pan/CBCT room | Acquisition software for the unit; often the heaviest machine in the office | The unit's acquisition-workstation specification from the vendor |
| Doctor's office or consult room | Treatment planning, 3D viewing, case presentation on a large screen | CBCT viewer and treatment-planning software requirements |
| Sterilisation and lab | Barcode or tracking software, scanner or printer for the lab | That software's requirements; often light |
| Back office and manager | Practice software reports, payroll, email, file storage | Practice software requirements; office suite |
| Server or storage (if on-site) | Practice database, image store, backup target | Practice software server requirements; imaging storage guidance |
More detail on reading those vendor documents sits in software system requirements. Hardware itself is a separate line in any proposal: hardware procurement, major cabling projects and software licensing are quoted separately.
Phones, patient messaging and payments: how do they plug into the practice software?
Phones, patient messaging and payments are three separate products that each read from or write to the practice software. The phone system can show the caller's chart, messaging sends reminders from the schedule, and payments post to the ledger. Choose each one by the integration it offers with your practice software, then by features.
Phones. A cloud phone system runs over the same internet service and network as everything else, so the phone vendor and whoever designs the network need to agree on how voice traffic is handled. Caller identification that opens the patient record is the integration most front desks notice first. If you are keeping a number from another office or a previous practice, start the porting conversation early with the new provider. More on choosing a system is in phone systems for dental offices and on the VoIP page. The rule a new multi-line system must meet for 911 calls is covered in the startup guide; ask your phone vendor how its setup meets it at your address.
Patient messaging. Reminder, recall, two-way texting and online forms products (Weave is one many practices use) read the schedule and write back confirmations or forms. Ask which direction each piece of data flows, and whether forms land in the chart as structured data or as a scanned document.
Payments. Card terminals and online payment links should post to the correct patient ledger without being retyped. The terminal also sits on your network, so put it on the segment your network design sets aside for payment devices rather than on guest Wi-Fi.
A useful habit for all three: write down, before signing, which practice software version the integration supports and who fixes it if an update on either side breaks it.
Who should own the email, logins and accounts?
Identity is who can sign in to each system and who controls the accounts. A new practice should own its email domain and tenant in the practice entity's name, give every person a unique login, and turn on multifactor authentication from the first account. Accounts set up by a vendor or a relative are hard to reclaim later.
CISA describes multifactor authentication as "a layered approach to securing your online accounts and the data they contain." In a dental office the accounts that most need it are email, the practice software, the imaging cloud if used, the payment portal, the phone portal and the domain registrar.
Three habits set the identity layer up well from day one:
- One person, one login. Shared front-desk logins hide who did what in the chart and make offboarding guesswork.
- Admin rights stay with the practice. Vendors and IT partners get their own named admin accounts, never the owner's password.
- A written list of every account. The startup guide's account-ownership register is a ready template: account, owner of record, who holds admin access, and where the credentials are kept.
Email and file storage often live in Microsoft 365 or a similar suite. The tenant's default settings were not written for a healthcare office, so someone should review them before patient information starts moving through email. The pieces involved are listed on Legend's cloud services page.
How do security and backup cover the whole stack?
Security and backup are a layer that sits across every other one: each data store needs a copy kept somewhere else, a tested restore and someone watching for trouble. For a new office the practical start is a list of where data lives (database, images, email, forms, scans) and a backup and restore plan for each entry.
Use the stack table above as the checklist. For each layer that holds patient data, write down:
- Where the data lives (server, capture computer, vendor cloud, email tenant).
- What copies it, how often, and where the copy is kept.
- When a restore was last tested and how long it took.
- Who is alerted if the backup fails.
Imaging is the entry most often missed: the practice database is backed up, and the image store on a separate computer is not. Cloud services need the same scrutiny, because retention in an email suite or a vendor platform is not the same as a backup you control.
For practices Legend looks after, there is 24/7 monitoring and a staffed 24/7 helpdesk at 1-800-794-1588. What the security and backup layer costs to set up in a new office sits with the budgeting technology for a dental startup guide. How Legend approaches protection is described on the cybersecurity and backup and recovery pages. Technology choices support HIPAA compliance readiness through technical safeguards; the practice's own policies, training and risk analysis remain part of that picture.
How do the pieces depend on each other?
Every layer leans on another, so one failure can look like several. If the internet goes down, cloud software, phones and payments all stop together; if the imaging bridge breaks, the sensor works but images land nowhere. A dependency map tells the team what to check first and who owns the fix before anyone calls a vendor.
The map below re-keys the one this page has carried for established offices to a new office, adding a first check and an owner column. Fill the owner column with names before opening day.
The dependency map
| Component | If it fails | First check | Who owns it |
|---|---|---|---|
| Practice software | Schedule, chart and checkout stop; front desk reverts to paper | Is it every workstation or one? Is the server (or the vendor's status page) up? | Software vendor for the application; IT partner for the computers and network under it |
| Imaging software and bridge | Images capture but do not file, or the bridge opens the wrong patient | Does the imaging program open on its own? Is the bridge path set on this workstation? | Imaging vendor for the software; IT partner for drivers and the workstation |
| Sensors and cameras | One operatory cannot capture | Same device in another room; USB port and driver | Imaging vendor for hardware; IT partner for the workstation |
| Server or image store | Several rooms slow or images missing everywhere | Power, storage space, last reboot | IT partner |
| Wired network and switching | Widespread slowness or loss of access | Switch lights, recent changes in the closet | IT partner |
| Wi-Fi | Tablets, carts and patient devices drop | Which access point, and is it only one area? | IT partner |
| Internet service and firewall | Cloud software, phones, payments and remote help stop together | Carrier status, firewall lights, backup connection if any | Carrier for the line; IT partner for the firewall |
| Identity and email | Staff locked out, a departed employee still signed in | Account status and MFA prompts | Practice owner for decisions; IT partner for administration |
| Workstations | One room or the front desk down | Restart, then updates installed overnight | IT partner |
| Phones and messaging | Patients cannot reach the office; reminders stop | Internet status, phone portal, integration status | Phone or messaging vendor; IT partner for the network |
| Payments | Cards decline or post to the wrong ledger | Terminal network connection; integration log | Payment processor; IT partner for the network segment |
| Backup and recovery | Data lost after a failure or an attack | Last successful backup and last tested restore | IT partner, with the owner signing off on tests |
| Vendor accountability | Faults bounce between vendors while a room waits | Who was named to drive multi-vendor faults? | Named in each contract before opening |
That last row matters most in a new office, where five or six vendors meet for the first time. Decide who drives a fault that crosses two products, and say so in each contract or engagement letter.
Which integrations must be tested before opening?
Test every connection between two systems, not just each system alone. Before the first patient, run a real transaction across each link: a test patient scheduled, imaged, charged, reminded and billed, plus a restore from backup. Write down the result, who ran it, and who fixes any failure, so nothing first breaks in front of a patient.
Vendors test their own product at installation. The gaps sit between products, and nobody is assigned to them unless you assign someone. This matrix is the list to work through in the last stretch before opening, with a dummy patient record you delete afterwards.
Table C. Integration test matrix
| Integration | Test | Pass when | Who fixes a failure |
|---|---|---|---|
| Practice software ↔ imaging (each operatory) | Open the test patient, launch imaging from the chart, capture a sensor image and an intraoral photo | Image files under the test patient and is visible from the doctor's station | Imaging vendor for the bridge; IT partner for the workstation |
| Imaging ↔ CBCT or pan viewer | Take a test scan, open it at the consult room and the doctor's office | The volume opens in every room on the viewer list | Equipment vendor for acquisition; IT partner for viewer installs and storage |
| Practice software ↔ patient messaging | Book an appointment, send a reminder, confirm it by text, send an intake form | Confirmation and completed form appear in the chart | Messaging vendor |
| Practice software ↔ phones | Call the main number from a mobile phone listed on the test patient | The front-desk screen shows the test patient | Phone vendor; IT partner if traffic is blocked |
| Practice software ↔ payments | Run a small card charge and a refund on the terminal and an online link | Both post to the test patient's ledger without retyping | Payment processor |
| Practice software ↔ claims | Send a test claim or eligibility check to the clearinghouse | Accepted or returned with a readable response | Practice software or clearinghouse vendor |
| Backup ↔ every data store | Restore one file from the database backup, one image folder and one mailbox item | Each restored item opens, and the time taken is written down | IT partner |
| Email ↔ scanner and fax | Scan to email and send a fax to a known recipient | Both arrive at the right mailbox | IT partner; fax service vendor |
| Wi-Fi ↔ clinical tablets and guest network | Join each network from a tablet and a guest phone | Clinical devices reach the practice software; guest devices cannot | IT partner |
| Printers and label printers | Print a walkout, a prescription and a lab label from the practice software | Each prints from every workstation that needs it | IT partner |
Keep the completed matrix. It doubles as a baseline: when something breaks months later, you know it once worked and what changed since.
What should you collect from each vendor before buying hardware?
Before buying computers, servers or network equipment, collect each vendor's current requirements document: workstation specification, server or storage guidance, network needs, supported integrations and site preparation. Date each one, file it where your IT partner can see it, and buy hardware against the strictest requirement in the set.
The register pays off later: when a workstation is replaced or an upgrade lands, the technician starts from the filed document instead of from memory. Version matters too: requirements change with major releases, so note the version each document covers.
Table D. Vendor document register
| Vendor type | Document to collect | Checked on (date) | Filed where |
|---|---|---|---|
| Practice software | Server and workstation requirements for the version you will install; supported integrations list; data export method | ||
| Imaging software | Workstation and storage requirements; bridge setup for your practice software | ||
| Sensors and cameras | Driver compatibility with your Windows version; connection type | ||
| Pan or CBCT unit | Site preparation guide; acquisition-workstation specification; viewer requirements | ||
| Intraoral scanner | Computer requirements; how scans reach the practice or lab | ||
| Phone system | Internet and network requirements; practice software integration; number porting steps | ||
| Patient messaging | Practice software integration and the version it supports | ||
| Payments | Terminal network requirements; practice software integration | ||
| Internet carrier | Service order with the service type and the installation date offered for your address | ||
| Security and backup | What is backed up, where the copy sits, and how a restore is requested |
Leave the last two columns blank on purpose. They are for your office manager or IT partner to fill in, so you can see at a glance which documents are missing before the hardware order goes out.
How does the stack differ by specialty?
The layers stay the same across specialties; the weight on each one shifts. Orthodontic offices lean on records software and open-bay screens, pediatric offices on shared bays and patient entertainment, and surgical and periodontal offices on 3D imaging, viewing and storage. Size imaging, storage and screens to the specialty before buying.
- Orthodontics: records and ceph software (often Dolphin Imaging) beside the practice software, more photography, and screens in an open bay rather than closed rooms.
- Pediatric: open bays, ceiling or wall screens for patients, and more shared workstations per chair.
- Oral surgery and periodontics: CBCT viewing in consult and surgical rooms, planning software, and more storage for 3D data.
- Endodontics: microscope cameras and higher-resolution capture in each treatment room.
The startup guide's specialty matrix sets these out with a named Legend project for each one; see the full startup technology guide.
What do new-office stacks look like in practice?
Legend's /work pages record new offices as they are built, and their own wording names the same layers this page maps: computers, networking, Wi-Fi, practice software, imaging, AV and backups. Four projects show the range, from a studio on the Florida Gulf Coast to Texas practices north and east of Dallas.
- Pearl & Pine Dental Studio in Gulf Breeze, Florida: the /work update for Dr. Shane Mobley and Dr. Dixie Mobley's practice says the planned foundation includes "computers, networking, Wi-Fi, dental software, imaging integration".
- Young Horizon Dental in Mesquite, Texas, east of Dallas: the August 2026 update documents "computers, networking, dental software, imaging integrations, audio and video" for Dr. Tran's office.
- Gainesville Dental in Gainesville, Texas: Legend's on-site update documents "workstations, network connections, server-rack setup, imaging systems, backups and practice software" being prepared for the opening.
- Dental Plus Specialists in McKinney, Texas, north of Dallas: the July 2024 update marks Dr. Luisa F. Echeto's opening, with the team working on "technology integration and practice workflows".
Read together, the four pages describe the stack this article maps: the practice software and the imaging tied into it, the computers and network beneath them, and, at Young Horizon and Gainesville Dental, the AV and backup layers too. More openings are listed on Legend's /work page.
Legend Networking has served over 3,500 practices since 2004, counts 1,500+ dental startup buildouts, and holds a 4.8 rating · 173 Google reviews. Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.
After opening: how do you keep the stack current?
After opening, review the stack on a schedule and at every change. A short quarterly look at updates, accounts, backups and vendor versions, plus a full review once a year, keeps the layers working together. A new operatory, a new imaging unit, a software upgrade or a staff departure each trigger their own check.
The phased modernization plan this page used to carry was written for older offices. A new practice starts on the far side of it, so the job is to stay there. A simple cadence:
Every quarter
- Confirm updates installed on workstations, the server and the firewall, and that nothing important was deferred.
- Review the account list: remove leavers, check admin rights, confirm MFA on every account that holds patient data.
- Restore one item from backup and note the time.
Every year
- Re-run the integration test matrix (Table C) after the year's software upgrades.
- Refresh Table D for any vendor that released a major version.
- Check workstation ages against vendor requirements and plan replacements before they become urgent.
At every change
- A new chair or room: re-check the imaging bridge, capture computer and network drop for that room.
- A new imaging device or a software upgrade: run its rows of Table C again.
- A staff departure: close the accounts the same day.
Once the office is running, day-to-day support belongs with dental IT support for established practices. Two lines from Legend's own page describe how that support is delivered: in-house engineers; no outsourced first-level triage, and onsite dispatch by appointment across served dental markets; remote-first nationwide.
What to ask your IT provider about the stack
Use these questions with any IT partner bidding on a new office. Good answers are specific, written down and tied to your practice software.
- Which of our chosen practice software and imaging products do you support the IT environment of today?
- Who will check each vendor's requirements document before hardware is ordered, and where will those documents be kept?
- Where will our images be stored, how are they backed up, and how is a restore requested?
- Who will run the integration test matrix before opening, and do we get the completed copy?
- In whose name will the email tenant, domain and software admin accounts be registered?
- How will voice, payment and guest traffic be separated on our network?
- When a fault involves two vendors, who drives it to a fix, and how is that written into our agreement?
- What does the quarterly and annual review cover, and who sees the results?
Frequently asked questions
What belongs on a dental office technology list for a new practice?
A complete list covers practice software, imaging software and devices, workstations for each role, the network and Wi-Fi, internet service, email and logins, phones and patient messaging, card terminals, backup and security, and room screens and cameras. Group the list by layer and note which vendor document drives each item, so nothing is bought before its requirements are known.
Where are X-ray images stored when the practice software runs in the cloud?
It depends on the imaging product, not the practice software. Many imaging programs still store images on a local server or storage device even when the chart is vendor-hosted, while some imaging products are cloud-based too. Ask each imaging vendor where images live, how large 3D scans are handled, and how those images are backed up and restored.
How do imaging sensors connect to the practice software?
The sensor plugs into a capture computer in the operatory, usually by USB, and the imaging software saves each image to a shared store. A bridge links the imaging software to the practice software so the right patient opens automatically. Each operatory needs the driver, the imaging software and the bridge set up, then tested with a dummy patient.
Which documents should vendors provide before we buy computers?
Ask the practice software and imaging vendors for current workstation and server requirements for the versions you will install, the device vendors for driver compatibility, and any pan or CBCT vendor for its site preparation guide and acquisition-workstation specification. Date each document, note the version it covers, and buy hardware against the strictest requirement in the set.
What should be tested between systems before opening?
Test every link between two systems with a dummy patient: imaging launched from the chart, a reminder confirmed by text, a call that shows the patient record, a card payment posting to the ledger, a claim sent to the clearinghouse, and a restore from backup. Record who ran each test, the result, and who fixes any failure.
Who should own the email and software accounts?
The practice entity should own every account: the domain, the email tenant, the practice software licence, imaging licences, the phone platform, the payment processor and the internet service. Vendors and IT partners get their own named admin logins. Keep a written register of each account, its owner of record, who has admin access and where the credentials are stored.
How often should a new practice review its technology after opening?
A short review every quarter covers updates, accounts, backups and a test restore. A fuller review once a year re-runs the integration tests, refreshes vendor documents and plans computer replacements. Any change in between, such as a new operatory, a new imaging device, a software upgrade or a staff departure, should trigger its own check the same week.
Which practice software and imaging platforms does Legend support?
Legend supports the IT environment of Dentrix, Eaglesoft, Open Dental and Archy for practice software, and DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging for imaging. Each platform has its own support page. The software and imaging vendors remain responsible for their own applications, so ask any IT partner how it works alongside them for your products.
The bottom line
A new office that maps its stack first buys fewer things twice. If you are choosing vendors now, talk to Legend's startup technology team about how the pieces fit for your build; startup technology is custom quoted. If you would like a written look at your plans and choices first, you are welcome to request the Free Dental IT Assessment.

