Identify the host organization
The practice first names the hospital or health system whose EpicCare Link portal it uses and the patients covered. Access to one organization's portal does not imply access to another organization's Epic records.
EpicCare Link is a window into records, not a billing connection.
For approved users, an organization's EpicCare Link portal may offer view-only clinical context for eligible patients. Any Taiga billing workflow must be assessed with that organization and the practice; the portal is not a claim-submission system or a native Taiga-to-Epic integration.
Book a demoSeparate record access from billing work
A portal can help an authorized team review context. It does not by itself create a claim workflow.
Request an approved role
The host organization reviews enrollment and individual user access. Ask whether a billing or non-clinical role is permitted and which patient records that role may view; rules vary by organization.
Use only the allowed view
Where approved and relevant, authorized staff may review available visit, result or demographic context for a billing question. The view is limited to the host's records and its local permissions.
Do the billing elsewhere
Confirm which separate practice-management system owns claim creation, submission, payment posting and denial follow-up. The portal itself must not be presented as the destination for those tasks.
What EpicCare Link does not establish
EpicCare Link is not the full Epic EHR or a general bridge to all Epic organizations. Access can be read-only and patient-scoped. This page does not claim Taiga API access, automated synchronization, write-back, claim submission through the portal or a vendor partnership.
Where portal access might help
These are review possibilities to validate against the host's permissions, not guaranteed Taiga capabilities.
Find permitted context
An approved view may help an authorized team locate relevant hospital encounter details without changing the source chart.
Clarify the boundary
Keep the hospital's record view separate from the independent practice's own claims and receivables workflow.
Avoid false integration assumptions
Ask for the actual portal and billing-system workflow before defining staff responsibilities or timelines.
Check the host's rules first
Enrollment, patient scope and access rights are set locally by the organization operating the portal.
Who operates your portal?
Name the host organization and its enrollment contact. Is the practice already enrolled, or does the organization require an agreement and approval?
Which user role applies?
Can an authorized billing or non-clinical user be granted access, and which patients and record types would that role see?
What work is permitted?
Confirm the host's policies for viewing information and any allowed downstream use. Do not assume exports, automated retrieval, API access or chart changes.
Where are claims worked?
Identify the practice's actual billing system and assign ownership of claim submission, payments, denials and follow-up outside the portal.
Who this is for
An independent practice that already has, or may qualify for, host-approved EpicCare Link access and wants to assess whether permitted record viewing can support a separate billing process.
Questions about EpicCare Link access
Is EpicCare Link a native Taiga integration with Epic?
No. This page describes a possible, host-approved portal view. It does not describe a native Taiga-to-Epic integration, an API connection or access to every Epic organization.
Can EpicCare Link submit claims or bill patients?
Do not rely on it for those tasks. A host organization's EpicCare Link product overview explicitly excludes claim processing, patient billing and access to that organization's billing system. Confirm your separate billing system.
Who approves access for a billing team?
The organization operating the portal controls enrollment and user roles. Some hosts describe non-clinical or billing roles, but the practice and Taiga must confirm eligibility and allowed use with their own host.
Can someone using one portal see every Epic patient record?
No. Portal access is tied to the operating organization, an approved user role and an eligible patient relationship. Scope and duration can vary by host.
Can Taiga change the chart or pull records automatically?
This page makes neither claim. Examples of EpicCare Link from host organizations describe view-only access to clinical records; any additional function would require separate verification and authorization.
Map your portal and billing boundaries
Bring the host organization's access rules and the name of your practice's billing system. We can assess whether a permitted record view has a useful role in your billing workflow.
An additional hospital portal FAQ describes enrollment roles and patient-scoped access. Each host sets its own rules.