eClinicalWorks Go-Live Checklist: EHR Implementation Steps for Practice Managers

Practice managers and billing leads: this eClinicalWorks go-live checklist covers the EHR implementation steps most plans skip, starting with the ones that cause claim denials after you switch.

Most EHR go-live checklists end the day you switch systems. That's not when practices get hurt.

The expensive problems usually show up a few weeks later. Claims that went out late or not at all. Remits that never posted. Lab results sitting unmatched. A provider inbox no one has cleared since Tuesday.

We work inside eClinicalWorks every day, on implementation and on billing for eCW practices. So this checklist covers both sides of an eClinicalWorks implementation: the clinical build and the revenue that depends on it. Copy it, cross off what's done, and send the rest to whoever owns it.

What should be finished 30 or more days before go-live?

Schedules and visit types

• Every provider and resource schedule is built. Templates, slot lengths, blocks, all of it.
• Visit types match how your front desk actually books, not a generic default list
• Reminders are on. Test them with a staff member's phone before a patient ever gets one.

Templates and documentation

• Progress note templates are built per specialty and per visit type
• Each provider charted a mock visit on their own templates and signed off. If they haven't, they'll rebuild them mid-clinic, and that's the week you can't afford it.
• Order sets and favorites (labs, imaging, common meds) are loaded, so nobody builds them on day one

Users and access

• Every user has a role-based account. No shared logins.
• Access follows minimum necessary: front desk doesn't need the same rights as a provider
• One named person owns adding and removing users after go-live.

Data migration

• A test load ran on a sample of real charts before the final load
• Someone compared those charts side by side with the old system: allergies, active meds, problem list, immunizations, last visit
• You know what isn't coming over. Staff know where to find it.
• Read-only access to the old system is arranged for after go-live

Which billing steps do go-live checklists usually skip?

This is the part that hits cash flow, and the part most implementation plans treat as "billing will handle it."

• Clearinghouse enrollment is done and test claims have gone through. Not "submitted." Accepted.
• ERA enrollment is filed with every major payer. Electronic remits are enrolled payer by payer, often through your clearinghouse, and some payers take weeks. Start early.
• EFT is confirmed. Many payers handle EFT separately from ERA. Medicare EFT runs through Form CMS-588 or PECOS, and CAQH offers a free tool for enrolling with many commercial plans at once.
• Fee schedules and the payer list are loaded and spot-checked. A wrong fee schedule doesn't throw an error. It just bills the wrong amount, every time, until someone notices.
• Charge capture has an owner. Who closes encounters? By when? Who chases the open ones?
• There is a plan for old A/R. Claims from before go-live still need to be worked in the old system. Decide who works them and until when.

Why do claims pass the eCW scrubber and still get denied after go-live?

When this happens, it's usually a setup problem, not a people problem. Your billing team isn't the issue. A claim scrubber checks the claim itself: codes, modifiers, required fields. It can't see most of what goes wrong during a switch.

• Enrollment didn't follow the change. If your billing NPI, tax ID, pay-to address or clearinghouse changed, payers may reject or deny until their records match.
• Provider mapping is off. Rendering and billing provider set up wrong in eCW sends a clean-looking claim under the wrong provider.
• Eligibility wasn't checked. New front desk workflows skip the eligibility check for a few weeks, and the denials show up a month later.
• Payer rules live outside the scrubber. Prior authorizations and payer-specific edits still need a person who knows that payer.

The fix for how to reduce claim denials after go-live is the same each time: group the first denials by reason, find the setup cause, fix it once.

How do you test lab, radiology and e-prescribing before go-live?

Interfaces fail quietly. We'd rather you find a broken lab route in testing than in a patient's chart, so test each one with real scenarios, not a single "it connected" message.

• Place a test order for each lab you use and confirm the result comes back to the right patient and the right provider
• Abnormal flags show up the way providers expect.
• Decide where unmatched or unsolicited results go, and who clears that queue daily
• Radiology orders and reports route the same way, with images or links where you need them
• E-prescribing works with your local pharmacies, including refill requests coming back in
• Prescribers who send controlled substances have finished EPCS setup. The DEA requires identity proofing and two-factor authentication for that, so build in time for it
• Texas practices that give vaccines: confirm your ImmTrac2 data exchange with DSHS, if you report electronically

How should you train staff for an eClinicalWorks go-live?

• Training is by role. Front desk, MAs, providers and billing each get their own sessions.
• Each role has a "super user" who knows the workflow well enough to help a coworker without opening a ticket
• Staff practice on their real daily tasks, not a demo walkthrough
• Provider schedules are lighter for the first days, so nobody is learning a new system with a full waiting room

What happens on go-live day?

• One person runs the day. They make the calls.
• There is a shared issue log: what broke, who owns it, when it's fixed
• Short huddles at the start and end of the day
• Everyone knows who to call for clinical questions, billing questions and IT

What should you watch in the first 30 days?

This is where most checklists stop, and where we'd tell you to look hardest. Check these daily for the first month:

• Open encounters. An unclosed visit is an unbilled visit.
• Days from visit to claim. If this number grows, something upstream is stuck.
• Clearinghouse rejections. Don't just fix the claim. Fix whatever in the setup caused it, or you'll fix the same claim forty more times.
• First denials, grouped by reason. A single setup error can repeat on every claim from that payer.
• Unmatched lab results. Each one is a result a provider hasn't seen.
• Provider inboxes. In eCW, the jellybean counts tell you fast who's falling behind.
• Posted payments versus deposits. If ERAs aren't posting, you'll see it here first.

Then keep going. Go-live is the start of optimization, not the end of the project. The first month shows you which templates slow people down and which workflows need a second pass.

Frequently asked questions

Sources: DEA EPCS requirements (21 CFR 1311, ecfr.gov), Texas DSHS Immunization Registry data exchange (dshs.texas.gov/immunizations), CMS and CAQH EFT/ERA enrollment guidance.