Epic Tapestry

What is Epic Tapestry?

Epic Tapestry is Epic's managed care and health plan administration application. Epic describes its health plan software as a way to track enrollment, manage benefits, authorize services, and pay claims and capitation on one platform, with utilization management tools that automatically assign statuses and track turnaround times.

Its users are health plans, including provider-sponsored plans, and its documented interfaces include files for Medicare Advantage, Marketplace coverage and a Texas Medicaid requirement. Texas Children's Health Plan, for example, launched the Epic Tapestry module on 1 August 2022.

Which plan operations run in Epic Tapestry?

Epic Tapestry covers the core administrative cycle of a plan, from enrollment to payment. Epic's health plan material and its documented interfaces show the main areas.

• Enrollment and eligibility: Taking member enrollment from employers, sponsors and Marketplace exchanges, and answering eligibility and benefit inquiries.
• Benefits and accumulators: Managing benefit plans, and taking benefit accumulation data from outside systems for cost calculations.
• Referrals and authorizations: Receiving referral requests for utilization review and tracking statuses and turnaround times.
• Claims: Receiving professional, institutional and dental claims, pricing them and paying them, with remittance back to providers.
• Premiums and payments: Premium billing and payment receipt, bank reconciliation and check files for processed claims.
• Government programs: Files exchanged with CMS for Medicare Advantage, and Marketplace enrollment and premium files.

Texas Children's Health Plan described the goal as end-to-end integrated operations support that unifies multiple data platforms in one system, to improve member and provider experience, revenue cycle and care coordination.

For a vendor, that breadth decides the integration. A tool that once received claims from a standalone claims system now receives them from Epic Tapestry, alongside enrollment, benefits and authorizations held in the same place, so its data contract changes with it.

How do X12 files move in and out of Epic Tapestry?

Most plan data still moves as HIPAA X12 transactions, and open.epic lists the managed care interfaces by transaction. These are the ones a vendor is most likely to meet.

• Claims in: Incoming Healthcare Claim, X12 837, receives professional, institutional or dental claims, processed in batch.
• Claim acknowledgments: X12 999 for file-level errors and X12 277CA for front-end claim status.
• Claim status: Incoming Claim Status Inquiry, X12 276/277, answers provider questions on paid and unpaid claims.
• Payment out: Outgoing Healthcare Claim Payment/Advice, X12 835, sends payment and remittance to providers.
• Eligibility: Incoming Eligibility Verification Query, X12 270/271, answers real-time member eligibility and benefit inquiries.
• Enrollment and premiums: Incoming Benefit Enrollment and Maintenance, X12 834, and Incoming Payment Order/Remittance Advice, X12 820, for premium billing.
• Authorizations: Incoming Referral Request for Review and authorization notifications, X12 278, plus an X12 278 endpoint over a JSON RESTful interface.

Repricing has its own paths. open.epic lists an incoming claim repricing request and an outgoing real-time repricing query, both on the 837, for plans that use an outside pricing engine.

Which HIPAA transaction rules apply to these files?

The HIPAA transaction standards in 45 CFR Part 162 apply. When a plan and a provider exchange these transactions electronically, both must use the adopted standard, which is why the X12 formats above are not optional.

• Claims: 45 CFR 162.1102 adopts the X12 837 for professional, institutional and dental claims.
• Eligibility: 45 CFR 162.1202 adopts the X12 270/271 for eligibility for a health plan.
• Authorizations: 45 CFR 162.1302 adopts the X12 278 for referral certification and authorization.
• Claim status: 45 CFR 162.1402 adopts the X12 276/277.
• Enrollment, payment and premiums: 45 CFR 162.1502, 162.1602 and 162.1702 adopt the X12 834, 835 and 820.

The standard fixes the format, not every detail. Each plan publishes a companion guide that sets its own identifiers, situational loops and business rules, and a vendor that ignores it will pass syntax checks and still fail adjudication.

Where FHIR fits for a plan on Epic

FHIR carries the newer payer exchanges, especially prior authorization and directory data. Epic on FHIR and open.epic list resources and operations that a plan's vendors can build against.

• Prior authorization: Claim $submit and $inquire for prior authorization, with Claim read.
• Claims and decisions: ExplanationOfBenefit read and search for claims and for prior authorizations.
• Coverage: Coverage read and search for patient insurance information.
• Prior authorization requests: ServiceRequest read, search and update for prior authorization.
• Provider directory: A Da Vinci Plan Net provider directory that gives public access to provider, plan and network data.

Epic's Payer Platform sits next to this. Epic describes it as automating the exchange of clinical insights, authorizations and event notifications between payers and providers, which is a different job from running the plan's own administration in Epic Tapestry.

Member apps are the third FHIR audience. The Patient Access API, first required under CMS-9115-F, lets members send their claims and clinical data to an app they choose, so a plan's member app competes with any app a member authorizes.

What does CMS-0057-F ask of a plan's systems?

CMS-0057-F, the Interoperability and Prior Authorization final rule, sets decision timeframes now and API requirements next. Plans on any system, Epic Tapestry included, have to meet it.

• Who it covers: Impacted payers are Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities and QHP issuers on the federally facilitated Exchanges.
• Decision timeframes: From 1 January 2026, impacted payers other than Exchange QHP issuers must decide prior authorization requests within 72 hours for expedited requests and 7 calendar days for standard requests, and impacted payers post prior authorization metrics publicly.
• Drugs excluded: The rule's prior authorization policies do not apply to drugs.
• APIs: From 1 January 2027, impacted payers implement a Prior Authorization API, Provider Access API and Payer-to-Payer API, and enhance the Patient Access API first required under CMS-9115-F.
• Implementation guides: The Da Vinci CRD, DTR and PAS guides are recommended, not required.
• Scope limit: The rule does not govern X12 270/271 eligibility transactions, which remain under the HIPAA transaction standards.

The practical effect is two parallel tracks. X12 keeps running claims, eligibility and enrollment, while FHIR APIs take on prior authorization and data sharing, and both have to agree on the same authorization and member records.

Plan the API work from the data already in Epic Tapestry. Members, claims and authorization decisions exist there first, so each API is a new view of records the plan already keeps, and its accuracy depends on those records being complete.

What should a vendor confirm before connecting to a plan on Epic Tapestry?

• Transactions in scope: Which X12 transactions and FHIR APIs the integration touches, by name and version.
• Batch or real time: Claims arrive in batch by default, so confirm timing before promising real-time claim decisions.
• Companion guides: The plan's own companion guide for each X12 transaction, including identifiers and loop usage.
• Member and provider identifiers: Which IDs the plan uses for members, providers and networks, and how they map to yours.
• Authorization source: Whether utilization management runs in Epic Tapestry or in an outside system that sends completed authorizations.
• Business associate terms: A signed BAA, because a health plan is a HIPAA covered entity and a vendor handling its PHI is a business associate.
• Test data: A test environment with realistic members, benefits and claims, and the plan's test calendar.
• Replay and duplicates: How files are held and resent during an outage, and how duplicates are detected on each side.
• Monitoring owner: Who watches acknowledgments and rejected files after go-live, at the plan and at the vendor.

Settle these in writing with the plan's Epic Tapestry analysts and its EDI team. They own different halves of the same integration, and each needs to sign off.

Where plan integrations break

Plan integrations break at reconciliation points, where two systems must agree on a member, a claim or an authorization. The failure points below are the ones to test hardest.

• Authorization mismatch: The utilization management system approves a service, but the claim pays or denies against a different authorization number.
• Accumulator drift: Deductible and out-of-pocket totals from an outside system arrive late, so members see the wrong cost share.
• Silent rejections: X12 999 or 277CA errors are not monitored, and claims never enter adjudication.
• Enrollment timing: An 834 file posts after claims for the new member arrive, and they deny as ineligible.
• Two sources of truth: A FHIR prior authorization decision and an X12 278 decision for the same request disagree.
• Directory staleness: Provider directory data served through FHIR lags network changes made in the plan's system.
• Pricing loops: An outside repricing engine returns a price after the claim has moved on, and payment uses the wrong amount.

Build reconciliation reports for each of these from day one. A daily count of files received, accepted, rejected and paid shows a break in hours rather than at month-end.

How Agnotic can help

Health plans on Epic still depend on outside systems for pricing, review, member engagement and data exchange. Agnotic Technologies builds those connections: X12 pipelines for the 834, 837, 835, 270/271, 276/277 and 278 with acknowledgment monitoring, FHIR payer APIs for CMS-0057-F, and reconciliation reporting that catches mismatched members, claims and authorizations.

Agnotic works with the plan's Epic Tapestry analysts and EDI team, follows each companion guide, and builds to HIPAA Security Rule safeguards for plan data.

Sources

• Epic: Health plan software and Payer Platform
• open.epic: Managed care interfaces, including X12 837, 835, 834, 820, 270/271, 276/277 and 278
• open.epic: FHIR interfaces, including Claim, ExplanationOfBenefit and Coverage
• Texas Children's: Health Plan launches the Epic Tapestry module
• CMS: Fact sheet, Interoperability and Prior Authorization final rule (CMS-0057-F)
• 45 CFR Part 162: HIPAA administrative requirements and transaction standards
• 45 CFR 164.502: Uses and disclosures, including business associates