Epic Community Connect lets a health system extend its own Epic system to independent practices and other affiliated organizations. For a small practice, it can mean access to a full Epic record shared with the local hospital, at a fraction of the cost of buying Epic alone. It also means tying the practice's core system to another organization.
This guide explains what Community Connect is, how it differs from EpicCare Link, what practices typically get, the federal rules on EHR donation, how practice data is kept separate, what onboarding involves, how other systems connect, and what a practice should ask before signing.
What is Epic Community Connect?
Joining or hosting Community Connect?
Agnotic builds integrations for Epic hosts and affiliated practices, from lab and device interfaces to reporting extracts.
Epic Community Connect is a program through which a health system that runs Epic hosts the same Epic system for independent practices, hospitals and other affiliated organizations. The affiliate gets its own Epic build within the host's instance, typically including the clinical record, scheduling and billing, while sharing patient records with the host.
The host handles hardware, software licences, upgrades and support, and charges the affiliate for its share. Sutter Health, for example, describes Sutter Community Connect as offering independent practices Epic's EHR, billing and practice management tools.
For the host, the program extends a shared record across its referral community, which makes care coordination easier and reduces duplicate tests. For the practice, it offers an enterprise EHR without having to buy, build and run one. Both sides gain, but both also take on obligations that last for years.
How does Community Connect differ from EpicCare Link?
EpicCare Link is a web portal that gives outside clinicians limited access to a health system's Epic records, for tasks such as viewing results and placing referrals. Community Connect gives the affiliate a full Epic system to run its own practice.
- Scope: EpicCare Link offers a narrow window into the host's records; Community Connect is the practice's own EHR.
- Documentation: Link users document in their own EHR; Community Connect users document in Epic.
- Billing: Link has no practice billing; Community Connect usually includes it.
- Cost and commitment: Link is light and low-cost; Community Connect is a multi-year relationship with significant onboarding.
Many practices start with EpicCare Link to work with a hospital and move to Community Connect when they need to replace their own EHR.
A third option is to keep an independent EHR and connect it to the hospital through interfaces, Care Everywhere or other exchange networks. That keeps the practice's freedom of choice but leaves the shared record thinner. The right answer depends on how much of the practice's work involves the host's patients.
What do affiliated practices typically get?
Affiliated practices typically get Epic's ambulatory clinical record, scheduling, registration, billing, patient portal and record sharing, configured from the host's standard build. The exact list varies by host.
- Hartford HealthCare example: Its Community Connect page lists applications including Cadence for scheduling, Prelude for registration, Resolute for billing and Care Everywhere for record exchange.
- Shared record: Clinicians see the hospital's notes, results and imaging for shared patients without separate logins.
- Patient portal: Patients use one portal across the practice and the health system.
- Support and upgrades: The host's Epic team runs upgrades and provides help desk support.
- Reporting: Access to standard reports and dashboards, sometimes with limits on custom work.
Ask for the exact list in writing. Applications such as specialty modules, advanced analytics or third-party add-ons may cost extra or not be offered at all.
Specialty practices should look hardest at this list. A cardiology, ophthalmology or orthopedic group may rely on specialty content, imaging links or device interfaces that the host has not built for affiliates, and the cost of adding them can change the economics of joining.
Which federal rules govern EHR donation?
When a hospital helps fund an EHR for referring physicians, federal law on physician self-referral applies. The EHR exception at 42 CFR 411.357(w) sets conditions under which an EHR donation does not count as a prohibited financial relationship.
- Cost share: The physician must pay 15% of the donor's cost for the items and services.
- Interoperability: The software must be interoperable, and the rule treats certified software as meeting this condition.
- Referral volume: The donor must not decide eligibility or the amount of the donation in a way that takes into account the volume or value of referrals.
- Written agreement: The arrangement must be set out in writing, specifying the items and services and the physician's cost share.
Hosts and practices should both have counsel review the arrangement. The rules are detailed, and the anti-kickback statute has a parallel safe harbor with its own conditions. Keep the signed agreement, the cost calculation and proof of the practice's payment on file for the life of the arrangement.
How is practice data kept separate?
Practice data is kept separate through security and configuration in the shared Epic instance: the practice's financial data, schedules and internal reports are restricted to its own staff, while clinical records for shared patients are visible across organizations as allowed by policy and law.
- Financial data: Hartford HealthCare states that practice financial data is kept separate.
- Clinical sharing: Shared patients' records are visible to treating clinicians across the community.
- Access controls: Role-based security limits what each organization's staff can see and do.
- Audit: The host audits access, and the practice should be able to request reports for its own patients.
Read the data sections of the agreement carefully. They should cover ownership of the practice's data, the host's permitted uses, breach notification and the practice's right to a full extract.
What does onboarding look like?
Onboarding follows the host's standard implementation plan: workflow reviews, build of the practice's departments and providers, data conversion, training and go-live support. Practices usually adopt the host's build with limited changes.
- 1. Discovery: Review the practice's workflows, payers, interfaces and reports.
- 2. Build: Set up departments, providers, schedules, fee schedules and billing rules.
- 3. Conversion: Move demographics, appointments, problem lists, medications, allergies and balances from the old system.
- 4. Training: Role-based training for clinicians, front desk and billing staff.
- 5. Go-live: On-site or remote support for the first weeks, then hand-off to the help desk.
Plan for the old system too. Data not converted, such as old notes and scanned documents, needs to stay accessible for record requests and legal retention, often in an archive.
Expect lower productivity for the first weeks after go-live, and plan schedules for it. Practices that reduce patient volume briefly and keep super-users on hand usually recover faster than those that try to see a full schedule from day one.
How do affiliated practices connect other systems?
Affiliated practices connect labs, devices, clearinghouses and specialty systems through the host's interface team, using HL7 v2 interfaces and Epic APIs. Every new interface competes for the host's time, so practices should list their needs before signing.
- Reference labs: Orders and results with the practice's preferred labs.
- In-office devices: ECG, spirometry and other devices that send results into the chart.
- Clearinghouse: Claims and remittances, often through the host's existing connection.
- Specialty systems: Imaging, optical or other specialty software the practice keeps.
- Reporting: Extracts for quality programs, payer reporting and the practice's own analytics.
Ask how the host handles third-party developers. Some hosts allow approved vendors to build interfaces and apps for affiliates, following the host's standards and testing process, which can be faster than waiting in the host's own queue. Others build everything in-house.
Reporting deserves early attention. Practices in value-based contracts need data for quality measures and payer reports, and if standard reports do not cover them, the practice needs an agreed way to get extracts from the shared system.
What should a practice ask before joining?
A practice should ask about total cost, contract length, what is included, how much it can customize, how support works and what happens if it leaves.
- Cost: Upfront fees, monthly fees, the 15% donation share where it applies, and future increases.
- Term and exit: Contract length, termination rights and fees, and the data extract on exit.
- Customization: Which requests the host will build and how long they take.
- Support: Help desk hours, response times and on-site support.
- Independence: Any requirement, written or implied, about referrals or affiliation.
Talk to other practices on the same host. Their experience with support, change requests and upgrades is the best preview of what joining will be like. Ask them what surprised them in the first year, and what they would negotiate differently.
What happens if a practice leaves?
If a practice leaves, it must move its records to a new EHR and keep access to historical data. The agreement should say what data the host will extract, in what format, at what cost and how long the practice can keep read-only access.
- Clinical data: Problems, medications, allergies, results, notes and documents for the practice's patients.
- Financial data: Open balances, payment history and claim status, so collections can continue.
- Format: Standard formats such as C-CDA documents and FHIR resources, plus database extracts where agreed.
- Timing: Notice periods and the date access ends, with time to test the conversion.
Shared patients complicate exits. Records created jointly with the host stay in the host's system, so the practice needs clear rules on what it takes and how it will request older records later. Agree these rules at signing, when both sides are on good terms.
How Agnotic can help
Agnotic Technologies builds Epic integrations for Community Connect hosts and affiliated practices: lab and device interfaces, clearinghouse connections, reporting extracts and FHIR apps, working within the host's standards.
Agnotic also helps practices joining or leaving Community Connect with data conversion and archiving, so historical records stay available and the move does not disrupt care.
Connect your Epic community
Explore Agnotic's Epic integration services, or browse the EHR integration hub.
Related reading on Agnotic
Continue with EpicCare Link, Epic integration strategies, Epic modules, Epic implementation and EHR integration methods.
