Insights
eClinicalWorks Outage Plan for FQHCs: What to Do When eCW Goes Down
The short answer
When eClinicalWorks goes down at a federally qualified health center, the first job is to find out where the failure is: eClinicalWorks itself, your internet or network, or one site's power or workstations. Most "eCW outages" at a single site are local. Then run a written downtime procedure: one person declares downtime, the front desk and clinical teams switch to prepared paper forms, the provider keeps seeing patients, and every visit is entered back into the record once the system returns. Centers that write this plan before the outage keep clinic open. Centers that improvise lose the day and spend the next week fixing charts and claims.
First 15 minutes: find out what is actually down
- Check more than one workstation and more than one site. If eCW works at the main site but not at a satellite, the problem is almost always that site's connection, network, or power.
- Check the internet connection. If other websites also fail, it is your carrier or your network, not the EHR.
- Check the application server if you host eCW yourself. A local server, storage, or power event looks like an eCW outage to staff.
- If everything local is healthy, check eClinicalWorks status and open a ticket. Look for any service notice eClinicalWorks has sent your center, then open a ticket with eClinicalWorks support. Include the time it started, which sites and users are affected, and the exact error message.
- Name one person who declares downtime. Staff should not each decide on their own when to stop waiting and switch to paper.
What a written eClinicalWorks downtime plan includes
- A trigger. How long the center waits before declaring downtime, and who makes the call.
- A call tree. Who notifies the medical director, the front desk leads, billing, the IT partner, and each satellite site.
- Paper forms ready at every site. Registration, vitals, progress note, orders, prescriptions, and a visit log, printed and stored where staff can find them at 7 a.m.
- A daily schedule that exists outside the EHR. Tomorrow's appointment list exported or printed at the end of each day, so the desk knows who is coming.
- Medication and allergy access. A defined way for providers to see current medications and allergies for scheduled patients when the chart will not open.
- Lab and e-prescribing fallback. How orders reach the lab and how prescriptions reach the pharmacy while the interface is down.
- Eligibility fallback. Which payer portals or phone lines the desk uses so coverage is still checked, and how the sliding fee is applied on paper.
- Back-entry rules. Who enters each paper visit into eCW, by when, and how it is marked so billing and UDS counts stay correct.
- Power and connectivity at each site. Which workstations, network equipment, and phones are on battery backup or generator, and whether there is a second internet connection.
Step by step: running downtime and recovering
- Declare downtime. The named owner announces it to every site through the call tree.
- Switch to paper. The desk registers from the printed schedule, clinical staff use the paper forms, and every visit goes on the visit log.
- Keep seeing patients. Providers document on paper. Urgent results and prescriptions go through the fallback written in the plan.
- Track the outage. Keep a timeline: start time, cause when known, ticket number, sites affected.
- Declare recovery. The same owner confirms eCW works at every site before staff go back to the system.
- Enter every paper visit back into eCW. Use the visit log as the checklist. Notes, vitals, orders, medications, and charges all go into the record before claims go out.
- Reconcile. Billing compares the visit log with encounters in eCW so no visit is lost or billed twice.
- Review the outage. Within a week, write down what failed, what worked, and what changes. Update the plan and the forms.
Puerto Rico and USVI: plan for power and connectivity first
In Puerto Rico and the USVI, power interruptions and storms are a planning fact, not an exception. Many eCW outages at island health centers start with the building, not the software. The plan should say which sites run on generator, how long battery backups last for network equipment, which sites have a second internet carrier, and what happens when one satellite is down while the main site is fine. Test it before hurricane season, not during it.
Where Millennial Networks fits
Millennial Networks has run healthcare IT for community health centers in Puerto Rico and the USVI since 2017. We work on both sides of an eClinicalWorks outage: the network, connectivity, power backup, and workstations that keep eCW reachable, and the downtime procedure, forms, and back-entry process that keep clinic open when it is not.
Managed IT for community health centers covers monitoring, connectivity, backup, and outage planning across sites. A virtual CIO for FQHCs owns the plan with leadership and keeps it tested. The downtime and incident procedure also belongs in your FQHC HIPAA security risk analysis and the file an HRSA reviewer opens for site visit cybersecurity.
After recovery, the repetitive work, such as checking eligibility for the visits seen on paper, is where automation helps. MediBOT, the healthcare automation platform built by Millennial Networks, supports eligibility verification, lab results processing, and workflow follow up inside eClinicalWorks today, with staff handling exceptions. Other workflows are scoped in an assessment.
Who this is for
- CEOs, COOs, and CIOs at FQHCs and community health centers that run eClinicalWorks.
- Medical directors and clinic managers who need clinic to stay open when the EHR does not.
- Billing leads who clean up after every outage.
Frequently asked questions
What should an FQHC do when eClinicalWorks goes down?
Confirm where the failure is first: eClinicalWorks, your internet or network, or one site's power or workstations. If the cause is not local, open a ticket with eClinicalWorks support. Then have one named person declare downtime and run the written procedure: paper forms, a printed schedule, fallback for labs and prescriptions, and back-entry of every visit after recovery.
How do we know if the outage is eClinicalWorks or our own network?
Test more than one workstation and more than one site, and check whether other websites load. If eCW works at the main site but not at a satellite, or nothing on the internet loads, the problem is local. If every site has a healthy connection and eCW still fails, contact eClinicalWorks support.
What belongs in an eClinicalWorks downtime plan?
A trigger and an owner, a call tree, paper forms at every site, a daily schedule kept outside the EHR, access to medications and allergies, fallbacks for labs, prescriptions, and eligibility, back-entry rules, and power and connectivity details for each site.
How do we enter paper visits back into eClinicalWorks?
Use the downtime visit log as a checklist. Assign who enters each visit and by when, enter notes, vitals, orders, medications, and charges before claims go out, and have billing reconcile the log against encounters so nothing is lost or billed twice.
How often should we test the downtime plan?
At least once a year and before hurricane season in Puerto Rico and the USVI, plus a short review after every real outage. Check that the forms are printed, the call tree is current, and backup power and the second connection actually work.
How do we start?
Book a discovery call. Bring your last outage: what happened, how long it lasted, and what it cost in visits and cleanup. We will help you write the plan and fix the weak points in the network and power behind eCW.
Talk to our team
Call 787-945-2260 or contact Millennial Networks to schedule a discovery call. Start with your last outage. We will help you make sure the next one does not close clinic.
