eCW System Administration

Most practices do not have an eCW administrator. They have an office manager, a biller and a provider who each know part of the build. We take the seat: configuration, security, upgrades and interfaces, with everything written down.

Schedule a consultation →

A clinician entering patient information at a workstation keyboard

Scope of work

What the admin seat covers

Engage us fractionally by the month, or as a fixed scope project to clean up a specific area.

A clinician reviewing information on a tablet

User access and securityRole design from scratch instead of cloning departed employees. Provisioning and deprovisioning, module level permissions, fee schedule and refund authority, and an access list you can hand an auditor.
Item dictionary hygieneFinding and retiring duplicate structured items, consolidating problem and medication entries, and making sure templates pull the codes your quality measures depend on.
Templates and order setsProgress note templates, structured data capture, order sets and preference lists built around how each specialty actually documents, then tested before release.
Upgrade planning and regression testingVersion moves including V11 to V12: inventory of custom templates, interfaces and billing rules, a written test script, a staged validation pass, and a rollback plan.
Interface and error queue monitoringLab, radiology, immunization registry and HIE feeds. Somebody watching the error buckets before a provider notices a missing result.
Database and system oversightBackup verification, performance review, growth monitoring and coordination with your hosting or eCW cloud support on anything server side.

Deliverables

What you receive, in writing

Every engagement produces artifacts that stay useful after we leave.

01 · Build findings listA ranked inventory of configuration problems with the business impact and effort for each.

02 · Security role matrixEvery role, every permission, every user mapped. The document your compliance officer asks for.

03 · Configuration runbookPlain language documentation of what is configured how, and why.

04 · Upgrade test scriptThe templates, interfaces and billing paths that must be validated after every version change.

05 · Change logDated record of every production change we make, what it affected, and how to reverse it.

06 · Monthly summaryHours used, work completed, open items and what we recommend next.

Before you call

Common questions

Do you replace our eClinicalWorks support contract?

No. eCW support handles the application and the platform. We handle your build: how it is configured, who has access, whether your templates and reports match how you practice. The two are complementary.

How much access do you need?

Read access to start, so the assessment does not require trusting us with change authority. Configuration work needs administrator access to the modules in scope, and we document every change we make.

Can you work alongside our internal IT team?

Yes, and that is common. Internal IT usually owns hardware, network and identity. We own the eCW build. We document to their standards if they have them.

All frequently asked questions →

Related services

Often bought together

02Data Migration→ 03Training and Workflows→ 04Report Writing→

A clinician in scrubs with a headset taking notes on a patient chart

A nurse in scrubs and gloves preparing a syringe at a clinical supply trolley

A clinician scanning a patient wristband against a chart

A laboratory technician labelling specimen tubes

Get started

Let us make eClinicalWorks work better.

A 30 minute call, no charge. Bring the report that will not reconcile, the upgrade that stalled, or the migration nobody wants to own.

Schedule a consultation → (321) 550-2564