When something breaks on a busy Tuesday, the support model matters more than the feature list. This page helps Fort Lee practices ask both vendors the right questions and decide who manages the relationship after go-live.
Support quality can’t be read from a brochure. Ask each vendor for written service levels, escalation steps, maintenance windows and contract remedies, then assign one person at your practice to manage the vendor relationship. A healthcare IT partner can add coordination when an issue spans more than one party.

Practices tend to judge support by the friendliness of the sales team. That’s understandable, but the sales team isn’t the one answering the phone at eight on a Monday morning. What you’ll actually live with is whatever the agreement says, and whatever your own staff do to use it.
This page compares the support question for athenahealth and eClinicalWorks without claiming that either one does it better. We found no independent source that ranks vendor support, and we won’t invent one. If you’re still deciding between the two, begin with our full comparison of both platforms, then return here to test the support terms.
Comparing athenahealth and eClinicalWorks?Walk us through your Fort Lee practice and we will help frame the decision.
athenahealth’s athenaOne page says that its dedicated implementation teams guide customers through onboarding. A vendor blog says athenaOne runs as one shared cloud instance with updates applied automatically. eClinicalWorks says its cloud is powered by Microsoft Azure and that each client database is replicated to a failover site in another region. All of those are vendor statements.
Notice that these describe onboarding and architecture. The pages we reviewed didn’t give support hours, response targets, escalation paths or a definition of what counts as an urgent issue. That isn’t a criticism; marketing pages rarely do. It simply means those terms must come from the contract or a written service description, and you shouldn’t assume them. Think of the written support contract as the real product description for this part of the purchase.
Security and privacy responsibilities belong in the same conversation, since a support team may touch protected data while fixing a problem. Our security questions for each vendor covers business associate agreements and the questions that go with them.
Federal guidance supports asking. The ONC Health IT Playbook notes that cloud-based EHRs bring shared data-security responsibility and advises practices to use contracts, service-level agreements and ongoing monitoring. It’s laid out in ONC’s Playbook guidance on cloud EHRs.
So ask each vendor for a written description that covers the following, and compare the answers line by line:
We did not find a hospital located in Fort Lee in any source we opened, and we won’t claim one. Englewood Hospital sits in neighboring Englewood, a municipality that borders Fort Lee, which tells us about adjacency and nothing about distance.
Why mention hospitals on a support page? Because a practice that sends results, referrals and records to organizations in other towns, and a support problem rarely stays inside one vendor’s system. If a referral document doesn’t arrive, the cause could sit with your EHR vendor, the receiving hospital or an interface in between. Ask each vendor how it handles a problem that crosses organizational lines, and who calls whom. HHS’s cloud computing guidance says a cloud service provider that maintains ePHI for a covered entity is a business associate, so how support staff reach your data belongs in the agreement your attorney reviews.
Here’s an illustration. A three-physician office near the bridge sends a referral note to a specialist in a neighboring borough, and the specialist never receives it. Before anyone can fix the problem, someone has to decide whose problem it is. A practice that has agreed in advance who opens the ticket, who contacts the receiving office and who tracks the outcome will resolve it faster than one that argues about ownership.
The most frustrating support calls are the ones where each party says the problem is elsewhere. A lab result doesn’t post, and the lab blames the interface, the interface vendor blames the EHR, and the EHR vendor asks for a ticket number you don’t have.
ONC’s contract guide says liability should sit with the party able to control and mitigate the risk, with carve-outs such as HIPAA breaches and willful misconduct. Use that idea when you review the agreement: for each type of failure, who is responsible for diagnosing it, and who is responsible for the fix? Read the guide through this ONC PDF and bring your counsel into the conversation.
ONC describes its Certified Health IT Product List as a public directory of health IT that has passed testing and certification, and says a user can find the certifying body for a product by searching the listing. That matters if a complaint about a certified module isn’t resolved with the developer. See ONC’s CHPL page.
This is a backstop, not a support channel. Certification isn’t an endorsement or a ranking, and it doesn’t speak to response times. Still, knowing the route exists is useful when a practice-wide problem lingers. Keep a dated record of each issue and each reply, because a clear paper trail is what lets anyone, including your counsel, act on it.
One more habit helps: before you sign, ask for the escalation path in the form of names or roles, not just a phone number. A number tells you where to start. A named escalation role tells you where a stuck issue goes next, and who inside the vendor is accountable for it.

Want the comparison pressure-tested?Share your shortlist and your biggest workflow worry.
Name one person at your practice as the vendor owner. That person keeps the contract, the renewal date, the support contacts and a log of tickets. Once a quarter, review the log: which issues repeat, which took longest and which were really training gaps.
That owner doesn’t need to be technical. They need to be organized and have the authority to escalate. If your team can’t spare the time, our vendor management page describes how an outside partner can take on part of that work, and our managed EHR administration service covers day-to-day system care for practices that want it.
Vendor support covers the product. It doesn’t replace a colleague who knows your templates and your habits. The super-user model, where a few staff members receive extra training and field first questions, shortens the path from problem to answer. It also reduces noise, because vendor tickets can be reserved for real defects.
Plan that internal layer deliberately. Give super-users time in their schedules, a shared place to record answers, and a direct line to the practice lead. Our ongoing training support can reinforce it. Refreshing training after an update can help prevent confusion.
A practical test is to ask what happens on the third bad day in a row. By then the first-line fixes have been tried, staff are frustrated and patients are waiting. Who steps in, and how do they hear about it? The answer reveals whether support is built around tickets or around people.
Qventive Healthcare lists athenahealth and eClinicalWorks among the platforms it supports. We help practices write support requirements, coordinate with vendors when an issue crosses systems, and keep documentation current. We don’t operate either vendor’s platform, and the vendor remains responsible for its own service.
For a practice near the bridge, that might mean one call to us when a referral feed misbehaves instead of three calls to three companies. We can’t promise response times, and we haven’t described any here. See how our Fort Lee EHR consulting page frames the work, or compare it with the rollout comparison for what happens before go-live.
Test the support terms before you sign
Tell us which platform your Fort Lee practice is weighing and what support you expect to need. We will help you write the requirements and review the answers from both vendors.
Call (201) 488-2750 or send us a message. Qventive Healthcare is at 200 Passaic Street, Hackensack, NJ 07601, and has served Northern New Jersey healthcare since 1994.
We can’t say, and we found no independent source that ranks athenahealth and eClinicalWorks on support. The public pages we reviewed describe onboarding and architecture, not support hours or response targets. The honest answer comes from your own contract, references you check yourself and a trial of the escalation path. Ask both vendors for the same written terms and compare them.
A service-level agreement is a written part of a contract that states what service a vendor will provide and how it is measured. For EHR support it might cover hours, response targets, availability commitments or maintenance windows, and what happens if a target is missed. Whether either vendor offers one, and on what terms, must be confirmed with that vendor. ONC’s Playbook advises practices to use contracts, service-level agreements and monitoring with cloud EHRs.
It depends on the contract and on where the failure sits. An interface involves your EHR vendor, the other system’s owner and sometimes a third-party connector. ONC’s guide says liability should sit with the party able to control and mitigate the risk. Ask each vendor to define ownership of interface issues in writing before you sign.
ONC says a user can find the certifying body for a certified product by searching the Certified Health IT Product List, which is relevant if a complaint isn’t resolved with the developer. That is a backstop and doesn’t replace contract remedies. Keep a dated record of every issue and reply. Your counsel can advise on the right route for a particular dispute.
Name one person with the authority to escalate and the time to keep records. They hold the contract, track renewal dates and review a ticket log regularly. This doesn’t need to be a technical role. If your team can’t spare the time, an outside partner can take on part of the work.
We help practices write support requirements, coordinate with vendors when a problem crosses systems and keep documentation current. Qventive Healthcare lists athenahealth and eClinicalWorks among the platforms it supports. We don’t operate either vendor’s platform, and we don’t promise response times. We agree the scope with you before work begins.
Call Qventive Healthcare at (201) 488-2750 or use the contact page. We will ask what you run today, what has gone wrong with support in the past and what you expect to need. Then we’ll set up a short working session. You’ll leave with a written list of support terms to request.
This page is general information for practice leaders. It is not legal or clinical advice. Clinical content decisions belong to your physicians, and compliance questions belong with your counsel.