Many independent practices use Epic through a hospital's Community Connect program. The host organization decides how the system is built, who can log in, and often how billing is done. A billing handoff starts with what your host allows.
The physician signs the encounter in Epic.
Codes are checked before claims go out.
Denials and balances get a named owner.
Community Connect setups differ by host. These are the points to map before anyone outside the practice touches a claim.
Hosts make different choices. Some give the practice's own billers Epic's professional billing application, Resolute. Some sell revenue cycle services. Others send charges out of Epic to a billing system the practice picks. Find out which one you signed up for.
When a provider closes an encounter, its charges move toward billing. Agree who reviews codes at that point. Taiga drafts ICD-10 and CPT codes from the note, and your physician approves them before anything is submitted.
Decide who releases claims, who reads rejections, and who works denials and appeals. Once the practice and the host agree on that split, Taiga's team works every denial, small balances included.
Settle where remittances post, who sends patient statements, and who answers billing calls from patients. Statements and follow-up can sit with Taiga when that work is in scope.
Clinicians keep charting in the hospital's Epic. The billing work gets a team that answers for it.
Community Connect gives your practice a patient record shared with the host. A billing handoff does not need to change that.
Codes arrive as drafts for review, so the provider still decides what is billed for each visit.
Low-dollar denials that sit in a work queue get appealed or closed out instead of aging.
Your Community Connect agreement and your host's IT team set the limits. Get these answers in writing.
Ask whether the host approves third-party billing users, what role they would get, and whether Epic's third-party access application applies to an outside company.
Confirm whether your practice uses Resolute in the shared Epic, a billing service the host provides, or a charge file sent to another system.
Ask which clearinghouse your claims leave through and who can see its rejection reports. On a hosted Epic, the host often manages that connection.
List unpaid claims by payer and age. Taiga can take over open A/R or run alongside your current team while new claims start.
This fits an independent group that sees patients in a hospital's Epic but owns its professional billing and wants an outside team to run it. If your host already bills for you under its own contract, start by reading that agreement.
Taiga has no Epic integration, API connection, or partnership. Any access would be a user account your host approves, under your host's rules. If your host does not allow outside billers, you will hear that on the first call.
Possibly. It depends on whether your host lets an outside billing company work in its Epic, or sends your charges to a system you control. Bring your Community Connect agreement to a call and you will get a direct answer.
No. Taiga has no Epic integration or partnership. Any work in a hosted Epic happens through access your host grants, the same way any approved biller would get it.
No. EpicCare Link is a portal that lets community users see a hospital's records for shared patients. Community Connect gives your practice its own use of the hospital's Epic, often with scheduling and billing. The EpicCare Link guide covers the portal case.
Partly. Epic also hosts larger independent groups directly, and then your own Epic administrators approve billing access instead of a hospital. The questions about codes, claims, and denials stay the same.
Share your host's name, your billing model, and a de-identified denial or two. Taiga will walk through what a handoff could look like on your setup.