Nearshore and offshore are often discussed as two price points for the same thing. For Epic support they are better understood as two kinds of coverage: one that works while your own analysts work, and one that works while they sleep. Most health systems that outsource part of their Epic operation end up using both, so the useful question is which work belongs in each.
What is the practical difference between nearshore and offshore Epic support?
Nearshore support comes from a delivery center whose working day overlaps with yours. For a U.S. health system that usually means Latin America. Colombia keeps UTC-5 all year, which lines up with U.S. Eastern time in winter and Central time in summer, so an analyst in Medellín and an analyst in Ohio are never more than an hour apart.
Offshore support comes from a center whose working day falls in your night. India is nine and a half to ten and a half hours ahead of U.S. Eastern time depending on the season. That is the point of the model: build, test and batch work handed off at the end of a U.S. day is finished when the U.S. team logs back in, and three rotating shifts turn that into round-the-clock coverage.
How much does time-zone overlap matter for Epic work?
It depends on the type of work. Some Epic tasks are interactive: a Resolute analyst walking a revenue-cycle manager through a claim edit, an Ambulatory analyst in a clinic optimization huddle, a command-center seat during a go-live. Each loses most of its value when every question waits a day for an answer.
Other tasks are asynchronous by nature: running the regression pack for a quarterly upgrade, monitoring interfaces and batch jobs, validating converted data against source counts, working down a report backlog, staffing a Tier 1 desk at 3 AM. For this work an overnight hand-off is an acceleration, not a compromise, because results are waiting at 8 AM.
Rule of thumb: if a task needs someone from your team in the room more than once a day, keep it in the overlap window. If it can be described in a runbook and checked in the morning, it is a candidate for offshore.
Does language change the decision?
Both models deliver in English for analyst and clinician-facing work. Spanish matters when the work is patient-facing. MyChart activation calls and patient access questions arrive in whatever language the patient speaks, and a bilingual nearshore team covers Spanish volume directly rather than through a translation line. Whether a nearshore or offshore analyst may take a call involving protected health information at all is decided by contract and policy, not language.
How do health systems get real 24x7 coverage from the two models?
By chaining them. A follow-the-sun arrangement typically runs U.S. onshore staff during business hours, a nearshore team across the same window overlapping the full U.S. business day, and an offshore center overnight. InterScripts runs this with U.S. leadership in Chantilly, Virginia, a nearshore Epic team in Medellín, Colombia on U.S. hours and a 24x7 three-shift operation in Hyderabad, India.
What makes it work is hand-off discipline rather than geography:
- One queue. Every hub works the same ticket system under the same priority definitions.
- Written runbooks for overnight work. If the overnight team has to guess, the work waits for morning anyway.
- A named owner per shift and an escalation path back to the U.S. lead that does not depend on the hour.
- A shared change calendar so an overnight test cycle, an Epic quarterly upgrade and a payroll close do not collide.
What changes for data protection and the Business Associate Agreement?
HIPAA does not prohibit a business associate from using staff outside the United States, but every entity touching protected health information must be bound by the agreement. A vendor with analysts in several countries usually employs them through separate legal entities, so ask which entity employs the people on your account and whether each one is under the BAA, directly or through a written subcontractor agreement.
Then ask where PHI is processed. The lowest-risk pattern is that it never leaves your environment: analysts work inside your Epic instance through virtual desktops or a managed remote-access path, with no local storage, printing or file transfer. Ask for that design in writing, and ask how it is audited.
Certifications such as HITRUST, SOC 2 Type II and ISO 27001 are only useful if the certified scope includes the nearshore and offshore sites that will serve you, so ask for the scope statement rather than the badge. InterScripts, for example, holds ISO 27001:2022 certification, signs a BAA before any PHI access, and keeps every person who handles PHI on its MyChart patient service desk U.S.-based.
Finally, check your own obligations. Some state Medicaid contracts, payer agreements and federal programs restrict offshore access to member or beneficiary data regardless of what HIPAA permits. Where that restriction exists, it settles the question for the affected work before any other factor is weighed.
How long does each model take to ramp?
Ramp time is driven more by the role than by the location. Three things govern it: whether the analyst already holds the Epic credential for the module, how quickly your organization can provision access, and how much tribal knowledge the role requires.
Geography does shape the curve. Interactive roles ramp faster nearshore because shadowing happens live with your team; runbook-driven roles ramp well offshore because the knowledge transfer is mostly documentation and test cases. Across its healthcare IT roles, InterScripts quotes a ramp inside two weeks for most positions and four to six weeks for complex Epic Bridges, Beaker, Beacon and Stork roles. Schedule the start around your Epic release calendar, not the week of a quarterly upgrade.
When does nearshore fit, and when does offshore fit?
Nearshore tends to fit:
- Embedded application analyst pods that attend your stand-ups and optimization meetings.
- Same-day break/fix where the requester expects a conversation, not a status update.
- Patient access and MyChart support where bilingual coverage is needed and PHI rules permit it.
- Extra hands during go-live, upgrade and conversion weeks.
Offshore tends to fit:
- Quarterly upgrade regression testing and test-script maintenance.
- Interface, batch and infrastructure monitoring overnight.
- Data conversion, validation and reconciliation runs.
- Report backlogs that can be specified and reviewed asynchronously.
- After-hours Tier 1 coverage where contracts allow it.
Some work stays onshore in nearly every program: leadership and governance, roles that need a badge in your facility, and any queue where your contracts require U.S.-based staff.
How do health systems blend the two without creating a third problem?
The pattern that holds up is a single accountable lead per module or service line, a nearshore pod working the overlap window, offshore capacity for test and batch work, and one contract with one set of service levels that apply regardless of which hub closed the ticket. Blending is also where the economics come from: a hybrid onshore, nearshore and offshore mix lowers total cost of ownership by roughly 30% on average, because you pay for coverage hours rather than inherited headcount.
Measure it the way you would measure an internal team: response and resolution times by priority with no exemption for the overnight shift, ticket reopen rates, hand-off defects between shifts, and analyst retention on your account.
If you are weighing the two models now, decide in this order: work type first, hours second, PHI and contract rules third, price last. The nearshore Epic support page describes how the Medellín bench is structured, the Epic staff augmentation page covers roles, vetting and engagement terms across all three hubs, and the Epic and Workday services page shows how both platforms are supported from one bench under one governance model.
