What Should a Dental Practice Do When Its Practice Management Software Stops Working?
When Dentrix, Eaglesoft or Open Dental becomes unavailable, the practice should begin a structured response within the first 5 to 15 minutes. The immediate priorities are to determine the scope of the outage, protect patient data, contact the correct support teams and activate a temporary clinical workflow.
A software outage does not always mean the dental application itself has failed. The cause may be a workstation, server, database, network connection, storage problem, security tool, cloud service or third-party integration.
The fastest response follows a six-step framework: confirm the scope, preserve patient care, check the supporting technology, protect the data, coordinate vendors and document the cause. Practices that prepare these steps in advance can continue essential operations while technical teams restore normal access.
The Six-Step Dental Software Outage Response Framework
Use this process whenever the patient schedule, clinical charts, imaging links or other essential dental software functions become unavailable.
1. Confirm the Scope of the Outage
The first question is not, “Why is the software broken?” It is, “Who and what are affected?”
Determine whether the problem affects:
- One employee
- One workstation
- One operatory
- One department
- One location
- Every user and location
Ask employees to report exactly what they see. Useful information includes:
- The wording of any error message
- The time the problem started
- Whether the employee was already logged in
- Whether other applications still work
- Whether the computer can access the internet
- Whether images, schedules or charts are affected
- Whether anything changed immediately before the outage
A single-workstation problem may involve the local computer, user profile, permissions or network connection. An office-wide problem is more likely to involve a server, database, network, cloud platform or major application service.
Do not ask every employee to restart equipment simultaneously. Multiple uncontrolled changes can remove useful diagnostic information and make the cause harder to identify.
2. Activate the Practice’s Downtime Procedure
Patient care should not depend entirely on how quickly a technician can restore the software. The practice should have a written downtime procedure that employees can activate immediately.
The procedure should explain how to:
- Confirm the day’s patient schedule
- Check patients in manually
- Record essential clinical notes temporarily
- Identify allergies, medications and treatment concerns
- Capture treatment and billing information for later entry
- Communicate with patients about delays
- Handle prescriptions and referrals
- Contact the IT provider and dental software vendor
- Reconcile temporary records after recovery
The practice may maintain an approved emergency schedule containing the minimum information needed to contact patients and manage appointments. Any printed or exported information should be secured appropriately and destroyed according to the practice’s privacy procedures when it is no longer needed.
Employees should know who has authority to delay procedures, reschedule patients or close the office. These decisions should not be improvised during a stressful outage.
3. Check the Technology Supporting the Application
Dentrix, Eaglesoft and Open Dental depend on several layers of technology. The IT provider should evaluate each layer systematically.
The initial technical review may include:
- Workstation health
- Server availability
- Database services
- Available server storage
- Local network connectivity
- Internet service
- Connections between locations
- Cloud-service availability
- User permissions
- Recent software or security updates
- Endpoint-security alerts
- Imaging integrations
The technician should begin with the least disruptive checks and avoid making broad changes before understanding the problem.
For example, if one workstation cannot open Dentrix while every other computer works, restarting the entire server may interrupt the whole practice unnecessarily. If no user can connect to the database, the investigation should move quickly toward the server, database service, network or hosting environment.
4. Protect the Database and Patient Information
Before repairing, reinstalling, moving or restoring a dental application, the support team should confirm the condition of the practice’s data.
The response should establish:
- Whether the database is available
- Whether the database appears damaged
- When the most recent successful backup completed
- Whether images and documents are protected separately
- Whether the outage may involve ransomware or unauthorized access
- Whether logs and evidence should be preserved
Do not restore a backup simply because the application will not open. A premature restoration can overwrite newer information or complicate the investigation.
If ransomware, malware or unauthorized access is suspected, disconnecting affected systems may be necessary. The practice should follow its incident response plan and involve its cybersecurity, insurance, legal and compliance resources as appropriate.
Learn more about managed cybersecurity services and business continuity and disaster recovery.
5. Coordinate the IT Provider and Dental Software Vendor
The dental practice should not have to decide whether the problem belongs to the software company or the IT provider. Both teams may need to participate.
The IT provider generally handles:
- Computers
- Servers
- Networks
- Storage
- User accounts
- Permissions
- Security software
- Backups
- Internet connectivity
The dental software vendor generally handles:
- Application errors
- Application-specific database issues
- Supported software configuration
- Licensing
- Vendor-controlled updates
- Application-specific integrations
The managed IT provider should remain involved when the software vendor needs server access, database information, network testing or security changes. The practice manager should not spend the outage repeating technical messages between separate support desks.
The support case should include:
- Practice name and location
- Software name and version
- Number of affected users
- Exact error messages
- Time the outage began
- Recent changes
- Technical tests already completed
- Business impact
- Best contact for updates
6. Restore Service and Document the Root Cause
Restoring access is not the final step. The practice should receive an explanation of what happened and what will prevent the same problem from recurring.
The post-incident record should document:
- When the outage began
- When it was reported
- When technical work started
- Which systems were affected
- The root cause
- The corrective action
- When service was restored
- Whether any information was lost
- Which temporary records must be entered
- Which preventive improvements are required
A temporary restart may restore the application without resolving the underlying cause. Repeated outages involving server storage, aging hardware, database performance or unstable networking should result in a permanent remediation plan.
What Are the Most Common Causes of Dental Software Downtime?
Dental practice management systems can become unavailable for many reasons. The most common categories involve the workstation, server, network, database, storage, security controls or external services.
| Possible Cause | Common Warning Signs | Typical Response |
|---|---|---|
| Workstation problem | Only one employee is affected | Check the computer, user profile, permissions and network connection |
| Server failure | Most or all users lose access | Check server health, services, storage, hardware and virtual infrastructure |
| Database service stopped | The application opens but cannot reach patient data | Review database services, logs, storage and application status |
| Network failure | Multiple systems, printers or internet services are affected | Check switches, firewall, cabling, wireless equipment and internet connectivity |
| Storage is full | Slow performance, failed updates or database errors | Identify storage growth, free capacity safely and create a long-term plan |
| Failed update | The issue begins after a software or operating-system change | Review compatibility, logs and rollback options |
| Security software conflict | Files or services are blocked after a security change | Review alerts and use narrow, vendor-approved configuration changes |
| Ransomware or malware | Files are encrypted, systems behave unusually or security alerts appear | Contain affected systems and activate the incident response plan |
| Cloud or internet outage | Hosted software is unavailable while local computers continue working | Confirm provider status, internet availability and continuity options |
| Integration failure | Core software works, but imaging or another connected service does not | Identify the affected bridge, service, permissions or vendor connection |
What Should Employees Do During the First 15 Minutes?
A clear first-response checklist helps employees avoid making the outage worse.
- Notify the designated internal leader. The practice manager or assigned outage coordinator should take control of communication.
- Confirm who is affected. Determine whether the problem involves one computer or the whole practice.
- Record the error. Write down the message or take an approved screenshot without exposing patient information unnecessarily.
- Contact the IT help desk. Explain the clinical and business impact clearly.
- Activate downtime procedures. Use the approved temporary schedule and documentation process.
- Stop uncontrolled troubleshooting. Employees should not reinstall software, disconnect servers or repeatedly restart shared equipment.
- Prepare patient communication. Give employees a consistent explanation for delays.
The designated leader should provide updates to the team at set intervals, such as every 15 or 30 minutes during a significant outage. Regular communication reduces repeated questions and prevents employees from creating conflicting workarounds.
What Should Employees Avoid Doing?
Well-intentioned actions can create additional disruption or data risk. During an outage, employees should avoid:
- Restarting the server without technical direction
- Unplugging network equipment
- Installing unapproved remote-support software
- Sharing passwords with unknown callers
- Using personal email to send patient information
- Entering patient information into unapproved consumer applications
- Deleting files to create server space
- Restoring backups without authorization
- Making repeated changes without documenting them
- Assuming every unexpected support call is legitimate
Attackers may exploit a real or perceived outage by impersonating a software vendor or technician. Employees should use known support numbers and follow an established identity-verification process.
How Can a Dental Practice Continue Seeing Patients?
The ability to continue depends on which systems are unavailable, the procedures being performed and whether employees can access essential clinical information safely.
A downtime plan may allow the practice to continue limited operations through:
- A securely maintained emergency schedule
- Printed or approved offline forms
- Manual check-in procedures
- Temporary clinical notes
- Manual treatment and billing records
- Alternative communication methods
- Predefined criteria for delaying nonurgent procedures
The practice’s clinical leadership should decide which appointments can proceed. The IT provider should not make patient-care decisions.
Any information recorded during the outage should be entered into the primary system after service returns. Assign one person to manage reconciliation so records are not missed, duplicated or entered inconsistently.
What Should the Dental Downtime Kit Contain?
A downtime kit should be available even when computers and cloud services cannot be accessed. Store it securely and review it at least quarterly.
The kit may include:
- Written outage-response instructions
- IT help desk contact information
- Dentrix, Eaglesoft or Open Dental support information
- Internet and phone vendor contacts
- Dental imaging vendor contacts
- Cyber insurance contact information
- Approved downtime forms
- Patient communication scripts
- Emergency scheduling procedures
- Instructions for documenting temporary clinical information
- Instructions for reconciling records after recovery
- Named decision-makers and backups
Do not place administrative passwords in an unsecured binder. Privileged credentials should be stored in an approved password-management system with controlled emergency access.
How Long Does Dental Software Recovery Take?
Recovery time depends on the cause, infrastructure and preparation. A single workstation issue may be resolved within minutes. A failed server, damaged database or cybersecurity incident may require several hours or longer.
| Incident Type | Illustrative Planning Range | Variables |
|---|---|---|
| Single workstation issue | 15 to 60 minutes | Device condition, permissions, network and software configuration |
| Application service stopped | 30 minutes to 2 hours | Server health, database condition and vendor involvement |
| Network equipment failure | 1 to 4 hours | Replacement availability, onsite response and configuration backups |
| Server hardware failure | Several hours to more than one day | Redundancy, backup design, replacement hardware and recovery testing |
| Cloud or internet outage | Depends on the external provider | Internet redundancy, vendor recovery and available offline procedures |
| Ransomware or database corruption | Potentially one or more days | Containment, investigation, backup quality, legal requirements and recovery complexity |
These ranges are planning examples, not guarantees. The practice should establish its own recovery time objective: the longest acceptable period that each critical system can remain unavailable.
The practice should also establish a recovery point objective: the maximum amount of recent information it can afford to lose. These decisions determine the backup frequency, technology and recovery services required.
How Do Dentrix, Eaglesoft and Open Dental Outages Differ?
The initial response framework is similar for all three platforms, but the technical details vary according to the software version, deployment model, database, integrations and vendor requirements.
Dentrix Outages
A Dentrix issue may involve the application, server, database, workstation, network or a connected service. The support team should determine whether the problem affects the core practice-management system or only an integration such as imaging or patient communications.
Document the Dentrix version, server location, affected workstations, error messages and recent changes before contacting vendor support.
Eaglesoft Outages
Eaglesoft environments may involve practice-management functions, imaging systems, connected equipment and multiple vendor relationships. Troubleshooting should determine whether the issue affects the primary application, imaging, database or supporting infrastructure.
The IT provider should coordinate with the appropriate software and equipment vendors rather than making the office manager manage several cases independently.
Open Dental Outages
Open Dental environments can vary according to the database, hosting design, integrations and configuration choices. The support team should understand how the practice’s specific environment was implemented and who owns each component.
Custom integrations and undocumented changes can make diagnosis more difficult. Maintain current records of databases, servers, bridges, vendors and configuration decisions.
For a broader comparison, read Dentrix vs. Eaglesoft vs. Open Dental: IT support requirements compared.
What Happens When Dental Imaging Is Down but the Schedule Still Works?
An imaging outage should be treated separately from a full practice-management-system outage. The primary dental application may remain available while the imaging bridge, image database, acquisition computer, sensor, network connection or viewing software fails.
The support process should determine:
- Whether existing images can be viewed
- Whether new images can be captured
- Whether one room or every operatory is affected
- Whether the imaging database is available
- Whether the bridge from the practice-management software works
- Whether the acquisition device is detected
- Whether recent updates or configuration changes occurred
Clinical leadership should decide whether a procedure can continue without the unavailable imaging function. The technician should avoid changing sensor drivers, image storage or database settings without understanding the vendor requirements.
What Happens When the Internet Goes Down?
The effect of an internet outage depends on whether the dental applications are hosted locally or in the cloud.
A local practice-management system may continue working inside the office while cloud email, hosted phones, insurance portals and online communications become unavailable. A cloud-hosted dental platform may become inaccessible even though local computers and printers still function.
Practices that depend heavily on cloud services should evaluate:
- A secondary internet connection
- Automatic firewall failover
- Cellular backup
- Cloud-based phone continuity
- Secure remote access from an alternate location
- Offline clinical procedures
- Internet-provider escalation contacts
A backup connection should be tested before an emergency. Having a second service does not help if no one knows how it activates or if the firewall has not been configured to use it.
What Happens When the Server Fails?
If the dental database and application depend on an onsite server, a server failure may affect scheduling, charting, imaging and other shared systems simultaneously.
The IT provider should determine whether the incident involves:
- Power
- Storage
- Memory
- Operating system
- Virtualization
- Database services
- Network connectivity
- Cybersecurity
The recovery approach may involve repairing the existing server, moving services to alternate hardware, restoring a virtual machine or recovering data to a replacement environment.
The practice should not wait for failure to ask how recovery works. At least annually, leadership should ask the IT provider to explain:
- Which systems depend on the server
- What would happen if it failed today
- Where backups are stored
- When recovery was last tested
- How long restoration is expected to take
- What temporary clinical process would be used
How Do Backups Help During a Dental Software Outage?
Backups provide a recovery option when data is damaged, deleted, encrypted or stored on failed equipment. They do not prevent every outage, and they should not be the first response to a routine application problem.
A useful backup strategy should protect:
- Dental practice-management databases
- Images
- Patient documents
- Shared files
- Server configurations
- Cloud data
- Any separate integration databases required for recovery
The provider should monitor every backup job and investigate failures. The practice should also complete scheduled recovery tests.
A recovery test should answer:
- Can individual files be restored?
- Can the dental database be restored?
- Can the application open the recovered database?
- Can images and documents be connected correctly?
- How long does the process take?
- Who has authority to approve a full recovery?
Read how backup and disaster recovery work for healthcare and dental practices.
How Much Can One Hour of Dental Downtime Cost?
The cost varies according to the number of providers, scheduled procedures, employee count and length of the interruption. A practice should calculate its own downtime cost instead of relying on a generic average.
Use this framework:
- Lost or delayed production: Estimate the value of procedures that cannot continue.
- Employee time: Calculate the wages and overhead of employees who cannot perform normal work.
- Rescheduling: Account for staff time spent contacting and rebooking patients.
- Recovery labor: Include vendor, IT and after-hours costs.
- Record reconciliation: Add the time required to enter temporary notes and billing information.
- Patient experience: Consider delays, cancellations and lost confidence.
For example, assume a two-dentist practice normally produces $4,000 during an eight-hour clinical day. The direct production value is approximately $500 per hour before employee downtime, rescheduling and recovery costs are included.
This example is not a universal dental average. It shows why a practice should know its own hourly exposure and use that number when evaluating backup, redundancy and support options.
How Can Dental Practices Prevent Recurring Outages?
Not every outage can be prevented, but many recurring problems can be reduced through consistent maintenance and planning.
Maintain Supported Hardware and Software
Replace aging computers, servers, firewalls and operating systems before they become unsupported or unreliable.
Monitor Server Storage and Performance
Database and imaging growth should be reviewed before storage becomes critically low.
Schedule Controlled Updates
Coordinate dental software, operating-system and security updates. Confirm compatibility and maintain a rollback plan.
Standardize Workstations
Using approved hardware and configurations reduces troubleshooting complexity and inconsistent behavior.
Document Integrations
Maintain current information about imaging bridges, payment systems, patient communications, insurance services and vendor contacts.
Test Backups and Recovery
Verify that critical systems can be restored within the practice’s required timeframe.
Review Support Trends
Repeated tickets involving the same application, workstation or network segment should trigger a root-cause review.
Maintain a Technology Roadmap
Create a three-to-five-year plan for hardware replacement, software upgrades, cloud decisions and practice growth.
The dental technology standards guide explains how small recurring problems can become operational risk.
What Should a Dental Practice Ask Its IT Provider?
- Who answers when our dental software fails after hours?
- How do you prioritize an office-wide clinical outage?
- Will you coordinate directly with our software and imaging vendors?
- Where are our dental database and images stored?
- When were our backups last tested through an actual restore?
- How long would server recovery take?
- What happens if our internet connection fails?
- Do we have a written downtime procedure?
- Which computers or servers are approaching replacement?
- How will you determine the root cause after an outage?
- How are recurring problems tracked?
- What information will leadership receive after a major incident?
These questions should be reviewed at least quarterly. The goal is not to eliminate every possible technical problem. It is to ensure that the practice understands its risks and can respond predictably.
Review six questions dental practices should ask their IT provider every quarter.
A Realistic Dental Software Outage Scenario
Consider a 30-employee dental practice using Dentrix with digital imaging and an onsite server.
At 8:10 a.m., the front desk reports that Dentrix will not open. Within five minutes, the practice manager confirms that every workstation is affected but email and internet access still work.
The practice follows this response:
- The office manager calls the IT help desk and reports an office-wide clinical outage.
- Employees activate the approved downtime procedure and begin manual check-in.
- The technician confirms that the network is operating but the database service has stopped.
- The technician checks server health, storage and security alerts before restarting the affected service.
- Dentrix access is restored at 8:32 a.m.
- The IT provider investigates why the service stopped and identifies critically low server storage.
- The provider safely creates temporary capacity and schedules a permanent storage upgrade.
- The practice reconciles information recorded during the 22-minute interruption.
The restart restored access, but the storage remediation prevented the same issue from returning. That distinction separates reactive troubleshooting from managed IT.
Why Fast Response and Familiarity Matter
During a clinical outage, response speed matters. Familiarity with the practice matters just as much.
A technician who already understands the servers, software, imaging systems, network and vendors can begin focused troubleshooting immediately. A technician without current documentation may spend the first part of the outage discovering how the environment works.
“They are experienced and take time to know our setup. This allows them to resolve our issues fast.”
— Business owner and 911 IT client
Dental practices should expect their provider to maintain accurate documentation and remain involved until responsibility is clear and service is restored.
How 911 IT Supports Dental Software Outages
911 IT helps dental and healthcare organizations manage the technology surrounding Dentrix, Eaglesoft, Open Dental, imaging platforms and related clinical systems.
Support can include:
- 24/7 live help desk access
- Remote troubleshooting
- Local onsite assistance
- Server and workstation management
- Network monitoring
- Dental software vendor coordination
- Managed cybersecurity
- Backup monitoring and recovery testing
- Microsoft 365 administration
- HIPAA-focused technical safeguards
- Technology lifecycle planning
- Post-incident root-cause reviews
Explore managed IT services, healthcare IT support and business continuity services.
Frequently Asked Questions About Dental Software Downtime
Should employees restart every computer when Dentrix, Eaglesoft or Open Dental stops working?
No. First determine whether the outage affects one workstation or the entire practice. Restarting every device can create additional disruption and remove diagnostic information.
Should the dental practice call the software vendor or its IT provider first?
For most outages, contact the managed IT provider first so the team can check the workstation, server, network, database and security environment. The IT provider should involve the software vendor when application-specific assistance is required.
Can a practice keep seeing patients when its dental software is unavailable?
It may be possible to continue limited operations using an approved downtime procedure. Clinical leadership should decide which procedures can continue safely based on the information available.
Does a software outage mean patient information has been lost?
Not necessarily. The application may be temporarily unable to reach an intact database. The technical team should evaluate data integrity before restoring or modifying information.
How often should dental software backups run?
The schedule should reflect how much recent information the practice can afford to lose. Practices should define a recovery point objective and configure backups accordingly.
How often should a dental practice test recovery?
Recovery tests should follow a documented schedule based on the importance of each system. Critical databases, images and full server recovery should be tested rather than relying only on automated backup notifications.
Can internet backup keep a cloud dental platform running?
A properly configured secondary connection may restore access when the primary internet service fails. The firewall, backup connection and failover process should be tested in advance.
What if the dental software vendor blames the network?
The IT provider should test the network and provide relevant technical findings. Both support teams should coordinate until the affected component is identified.
What if the IT provider blames the dental software?
The IT provider should document the infrastructure checks and remain available while the software vendor investigates. The practice should not be left to translate between both companies.
Should every outage receive a written report?
Major or recurring outages should receive documentation showing the timeline, affected systems, cause, corrective action and prevention plan.
What is the best way to reduce dental software downtime?
Maintain supported equipment, monitor servers and networks, coordinate updates, document integrations, test backups, train employees and use an IT provider familiar with dental workflows.
Prepare Before Your Next Dental Software Outage
The middle of a busy clinical day is the wrong time to discover that no one knows where the backups are stored, who supports the server or how employees should continue working.
911 IT can review your Dentrix, Eaglesoft or Open Dental environment, document its dependencies, validate backups and create a practical downtime response plan.
To discuss dental IT support, contact 911 IT. You can also read how unresolved technology issues turn into clinical downtime.
