Epic and Community Connect Billing Services

Most independent practices reading this did not buy Epic. They joined a hospital's Epic through Community Connect, and inherited a revenue cycle platform designed for an organization with several hundred billing staff.

Community Connect gives you the system, not the department

The arrangement is straightforward. A host health system extends its Epic instance to your practice. You get Hyperspace, you get Resolute professional billing, you bill under your own tax ID and you keep your own money. What you usually do not get is the host's business office. Their revenue cycle team works the host's claims. Yours land in work queues that are yours to staff.

That is a reasonable deal, and it is where the trouble starts. A four-provider practice now owns a professional billing module built for an enterprise, and typically has one person who was trained for a week during go-live. We are the department that arrangement assumes you already have.

Work queues that fill faster than one person can empty them

Epic does not lose claims. It routes them. Charges that fail review sit in a charge review work queue. Claims that trip an edit sit in a claim edit work queue. Unpaid claims move to follow-up work queues, credits to credit work queues, patient balances to self-pay. Every one of those is a real, visible list, and every one of them requires a trained human to open it and act.

When nobody has time, the queues do not alarm — they just grow. Charges sit unbilled. Edits sit uncorrected. Timely filing runs the whole time. We work Epic by queue on a daily cycle: charge review first because unbilled charges are not even in your A/R yet, then claim edits, then follow-up by age and dollar value. Claims go out within 24 hours of the charge, denials are worked within 48 hours, and insurance aging is worked at 25 to 30 days.

You cannot change the build, so the workflow has to absorb it

This is the constraint nobody warns a practice about. On Community Connect the host owns the build. If a claim edit is firing on every one of your claims because a rule was written for a hospital outpatient department, you cannot switch it off. You submit a request, it enters the host's governance queue, and it is prioritized against everything else the health system needs. Upgrades land on the host's schedule too.

So we do not plan around build changes. We work with the build you actually have, document the edits that fire repeatedly on your specialty, and fix the cause upstream — in registration, in coding, in how the charge is captured — where we can act without anyone's approval. Where a build change genuinely is the answer, we write the request with the claim examples and dollar impact attached, which is what gets it prioritized.

Professional billing is not hospital billing

Practices on a hospital's Epic often absorb hospital habits. Charges get routed to the wrong place, provider-based versus office place of service gets applied inconsistently, and the professional component of a service is billed as though the practice owned the facility side too. Each of those is a denial or a takeback, and takebacks arrive months later when the money is already spent.

We bill professional claims as professional claims: correct place of service, correct rendering and billing provider, correct modifiers, medical necessity linked to the payer's policy before submission. Coding is included at no extra charge, along with coding audits when the denial pattern points at documentation.

Reporting when you do not have an Epic report writer

Epic's reporting is excellent and largely inaccessible to a practice without a certified analyst. Most Community Connect practices know their bank balance and very little else — not their clean-claim rate, not days in A/R, not which payer is quietly underpaying them.

Every month you get a Practice Performance Report at no charge: clean-claim rate, days in A/R, aging by bucket, denial reasons ranked by dollars, payer mix and collections against charges. Plain numbers, in a format you can act on and check. See days in A/R explained and what a good clean-claim rate looks like.

Access, security and the host's rules

Third-party access to a Community Connect instance goes through the host, and it should. We work under a signed Business Associate Agreement, using named accounts your practice requests and the host provisions, restricted to the security class appropriate for professional billing. Every action is in Epic's audit trail. We have been HIPAA-compliant for twenty years and we have no interest in shortcuts around a health system's security review.

If your Community Connect agreement genuinely does include host billing services, we will tell you that and you should keep them. This page is for the far more common case where it does not.

Why practices on Epic choose Synergy

You keep Epic. You keep your logins, your templates, your schedule and your data. Nothing is migrated and nothing new is purchased — we work inside the system you already run. What changes is who works it: a 98% clean-claim rate, claims out within 24 hours, denials worked within 48 hours, insurance aging worked at 25–30 days, and free insurance verification, coding, credentialing and monthly Practice Performance Reports. Twenty years in business, a US and India team so your queues move overnight, HIPAA-compliant throughout, a 30-day free trial and a 90-day money-back guarantee. We're not your billing service — we're your Billing Department.

---