IT support for practices on Epic Community Connect.
When a specialty practice joins a hospital system's Epic Community Connect program, the host system delivers and supports the Epic application. What it does not support is everything in your building: the network the connection rides, the workstations Hyperdrive runs on, the printers and scanners clinic workflow depends on, and the security of your own LAN. Galleon supports Community Connect practices across DFW and Houston on exactly that local layer, and coordinates with the host's IT team when an issue is on their side.
Galleon is an independent managed IT provider. We are not affiliated with or endorsed by Epic; we support practices that run it.
Community Connect gives you Epic. It does not give you IT.
Community Connect is a strong deal for many specialty practices: enterprise Epic, hospital-grade hosting, and integration with the systems that refer to you. But the agreement draws a hard line. The host supports the application and their data center. Your network, workstations, printers, wireless, phones, and security remain your problem, and the host's service desk will tell you so, politely and often.
The common failure mode is a practice that signed the agreement assuming 'the hospital handles IT now'. Then a printer mapping breaks during clinic, a workstation misses the host's required specifications after an upgrade, or the internet circuit that carries every chart has no backup, and there is no one to call who owns it.
Galleon is the party that owns it. We run the local environment to the host's published standards, keep workstation builds current with Hyperdrive requirements, give the connection to the host redundancy and priority, and work tickets with the host's IT team in their language instead of leaving your office manager to translate.
Six places we focus for every Community Connect practice.
Workstation and Hyperdrive standards.
Builds that meet the host's current specifications, patched on a schedule that does not break clinic mornings, with peripherals that survive updates.
Connectivity to the host.
Primary and backup internet, QoS so Epic traffic wins, and monitoring that catches degradation before clinicians feel it.
Printing, scanning, and labels.
The classic Community Connect ticket. We own print servers, drivers, and Epic print mapping end to end, coordinating with the host where their config starts.
Local security.
The host does not secure your LAN. We run EDR, MFA, segmentation, and HIPAA safeguards on everything inside your walls.
Downtime planning.
A documented plan for when the host's Epic instance or your connection to it goes down: read-only access, paper workflows, and a tested path back.
Host IT coordination.
We open, escalate, and track tickets with the host's service desk, and we sit in on the technical calls so nothing gets lost between sides.
Deep on the platforms Epic practices actually run.
On a different host setup? Ask.
The host's HIPAA program stops at their data center.
Joining Community Connect does not transfer your HIPAA obligations to the hospital. Your practice is still the covered entity for your own environment: access control on your devices, audit trails for your staff, encryption on your laptops, and a contingency plan for your site. Assessors and cyber insurers look at your local controls, not the host's.
Galleon documents the local environment, runs the annual security risk assessment, keeps EDR and MFA on every endpoint, and maintains the downtime plan, so the practice side of the arrangement holds up under the same scrutiny as the host's.
The questions practice managers actually ask us.
The application, yes. The host supports Epic itself and their hosting. Your network, internet, workstations, printers, wireless, phones, security, and backups of anything local remain yours, and that is the layer Galleon runs.
Yes, and we prefer it. We open and track tickets with their service desk, join their technical calls, and meet their published workstation and network standards so cutovers and upgrades go smoothly.
Yes. We review the technical requirements, what the host does and does not cover, what your local environment needs to meet their standards, and what it will cost, before you sign.
Yes. We manage the IT side of the transition: infrastructure the new EMR needs, data handoff logistics, workstation changes, and go-live support, alongside the new vendor's implementation team.
Yes. Engineers in Richardson and Houston, one helpdesk, on-site support in both markets.
Get the local IT layer your Community Connect agreement assumes you have.
Twenty minutes on the phone and you will know whether we are a fit. No pitch deck, no script.