Post-migration epic systems reporting after migration strategy: Layer 1 Epic-side reporting unchanged (Clarity, Cogito, Reporting Workbench, Slicer Dicer, Caboodle). Layer 2 Fusion-side back-office reporting (OTBI, Financial Reporting Center). Layer 3 cross-system FP&A + cost-report + service-line.
Healthcare reporting after an Epic-to-Fusion migration isn't a replacement — it's an addition. Epic-side reporting continues. Fusion-side reporting takes over back-office. Cross-system reporting bridges the two.
Pre-migration, a typical regional health system runs reporting in three messy zones: Clarity SQL Server for operational reporting against Epic, Cogito + Reporting Workbench for analytics, plus Slicer Dicer for ad-hoc cuts; legacy ERP reporting tooling (Lawson Smart Notes, PeopleSoft Query, McKesson canned reports) for back-office GL/AP/HR; and a fragile cross-system reporting layer (typically Excel-based or a home-grown SQL Server warehouse) that nobody fully trusts. CFOs reconcile Resolute AR against legacy GL once a month with manual workpapers.
Post-migration, the three layers become clean. Layer 1: Epic-side reporting continues unchanged. Clarity, Cogito, Reporting Workbench, Slicer Dicer, Caboodle (where adopted) all keep working. Resolute admin reports continue. Bridges interface monitoring continues. Clinical reporting, operational reporting, revenue-cycle reporting — unchanged. Layer 2: Fusion-side reporting takes over for back-office. OTBI dashboards replace legacy ERP canned reports. Fusion Financial Reporting Center handles GL/AP/FA close. Fusion HCM analytics handles workforce. Fusion SCM analytics handles supply chain.
Layer 3 is the new clean cross-system layer. Service-line P&L pulls Resolute revenue (Cogito) + Fusion cost. Physician productivity pulls Cogito work-RVU + Fusion HCM compensation. Cost-report pulls Cogito clinical detail + Fusion GL/HCM. FP&A consumes both layers through Power BI / Tableau (or Fusion OTBI + Cogito cross-system links). The CFO reconciles Resolute AR aging against Fusion GL AR balance per service area to the cent automatically. The fragile Excel-based cross-system reporting layer retires.
Each domain has clear ownership between Layer 1 (Epic-side) and Layer 2 (Fusion-side). Cross-system reports live in Layer 3.
Layer 1: Resolute + Cogito hold patient-billing detail. Layer 2: Fusion GL shows consolidated AR per service area. Drill: Fusion → Resolute → Cogito clinical context.
Layer 2: Fusion Financial Reporting Center. Reconciles to Layer 1 Resolute AR for the revenue side. CFO month-end close pack assembled in Fusion.
Layer 1: Cogito work-RVU + provider workflow. Layer 2: Fusion HCM compensation + headcount. Layer 3: physician productivity dashboards combining both.
Layer 1: Willow/OpTime/Beaker operational reporting in Cogito. Layer 2: Fusion Inventory + SCM analytics. Layer 3: 340B utilization reports combining Willow detail + Fusion Inventory.
Layer 3 cross-system. Revenue from Resolute via Cogito, cost from Fusion GL + supply chain + HCM. Service-line directors see one consolidated P&L per service area.
Layer 3 cross-system. Encounter / payer mix from Epic, GL + HCM + supply detail from Fusion. Cost-report pack assembled per fiscal year for reimbursement consultant retrieval.
A phased reporting build aligned to the migration timeline. Reports rebuilt in parallel with the migration; cross-system layer goes live at cutover.
Inventory every existing report consuming legacy ERP data. Categorize: replaceable in Fusion OTBI, requires cross-system rebuild, or retire. Identify critical reports (CFO close pack, service-line P&L, cost report). Sized rebuild plan.
Critical back-office reports rebuilt as Fusion OTBI dashboards. Financial Reporting Center for GL close. HCM analytics for workforce. SCM analytics for supply chain. Mapping to legacy report parameter sets preserved.
Service-line P&L, physician productivity, cost-report, FP&A. Built as Power BI / Tableau models consuming Fusion OTBI + Cogito. SSO + scope-limited HIPAA access. Cross-system drill chains tested.
Reports run in parallel with legacy versions. Numbers reconciled to the cent. Service-line directors and FP&A staff validate the rebuilt reports against the legacy versions. Sign-off captured per report.
At cutover, Fusion-side reports activate with first day-of-Fusion data. Legacy ERP reports cut to read-only archive (year-1 hot archive). Cross-system reports switch to Fusion as the source. Legacy report links redirect to archive.
Three-layer reporting in steady-state. Quarterly Fusion 26x release adopt-cycle handles Fusion-side schema changes. Epic quarterly upgrades handled per Layer 1 maintenance. Cross-system layer maintained continuously.
Six concrete improvements that show up in Month 1 post-cutover and compound over the next 5 years.
Clinical/revenue-cycle reporting owned by Cogito team. Back-office reporting owned by Fusion BI team. Cross-system reporting owned by FP&A. Clear lines, no orphaned reports.
Fusion GL → Resolute AR detail → Cogito clinical context. Drill works end-to-end. HIPAA actor-logged at every cross-system hop.
Resolute AR aging = Fusion GL AR balance per service area, period-end, to the cent — automatically. No more Excel reconciliation workpapers.
Cross-system reports consume both layers automatically. Close cycle compresses 3–5 business days. CFO close pack assembled in hours not weeks.
Finance users see consolidated data without patient identifiers. Clinical users see full clinical with their existing Cogito access. Cross-system access reviewed by privacy officer.
Layer 1 ready to absorb Caboodle cloud-scale analytics in Year 3 of the modernization roadmap. No reporting redesign at Caboodle adoption.
Three reporting layers. Layer 1 — Epic-side reporting continues unchanged: Clarity for operational SQL Server reporting, Cogito for analytical models, Reporting Workbench for clinician self-service, Slicer Dicer for cross-domain analytics, Caboodle for cloud-scale BI. Resolute admin reports continue. Bridges interface monitoring continues. Layer 2 — Fusion-side reporting takes over for back-office: OTBI dashboards rebuilt from legacy reports, Fusion Financial Reporting Center for GL/AP/FA close, Fusion HCM analytics for workforce, Fusion SCM analytics for supply chain. Layer 3 — cross-system reporting bridges Epic + Fusion: cost-allocation reports linking Epic encounter data to Fusion GL, contract pricing analytics linking Willow 340B data to Fusion Inventory, FP&A reports consuming both Cogito and Fusion BI.
Cogito continues unchanged for clinical, operational and revenue-cycle reporting. Cogito reads from Chronicles via Epic-published patterns — that integration is untouched. Existing Cogito models, Reporting Workbench reports and Slicer Dicer cubes continue to work. What changes is the destination of some downstream-derived reports: legacy GL reports that used to draw from Lawson/PeopleSoft/McKesson now draw from Fusion GL instead. Those cross-system reports are rebuilt during the migration as part of the OTBI dashboard work. Pure Epic-side reporting (clinical, patient, revenue cycle) is unaffected. The post-migration reporting team has fewer system boundaries to manage, not more.
No — they complement Cogito. OTBI (Oracle Transactional Business Intelligence) and Fusion Financial Reporting Center serve back-office reporting (GL, AP, AR, FA, Procurement, Inventory, HCM, Payroll). Cogito serves Epic-side clinical, operational and revenue-cycle reporting. The two are complementary, not competing. Where they touch: Fusion OTBI shows the consolidated AR balance per service area from the Resolute downstream feed; Cogito shows patient-level Resolute AR aging detail. Drill from one to the other is supported via cross-system links. For FP&A and executive reporting, both data layers feed dashboards (typically in Power BI or Tableau) consuming OTBI + Cogito + Caboodle.
Resolute AR reports continue running in Resolute and Cogito — patient-billing system of record stays in Resolute. CFO and controller see the same Resolute AR aging report they always saw. What changes is the GL-side view: Fusion GL receives the consolidated AR balance per service area as a journal-posting feed, so Fusion-side GL trial balance reports show the consolidated AR. Reconciliation: Resolute AR aging total = Fusion GL AR balance per service area, period-end, to the cent. Drill from Fusion GL AR line through to Resolute patient-billing detail via Cogito link, with HIPAA actor logging. No reporting is lost; the boundary between billing detail and GL consolidation is now clearer.
CMS Form 2552-10 cost reporting consumes data from both layers. From Epic side: encounter mix, payer mix per service area, supply consumption per service line, lab and pharmacy utilization. From Fusion side: GL trial balance per legal entity, payroll FTE workforce data, depreciation per asset class, AP supplier-paid data. The post-migration cost-report workflow consumes both layers automatically through pre-built reports. Cost-report supporting evidence is retained in the WORM archive (per the data-retention design) for CMS audit defense. Reimbursement consultants retrieve a single cost-report pack per fiscal year combining Epic + Fusion sources. This actually improves cost-report preparation versus legacy ERP scattered reporting.
Two of the highest-stakes cross-system reports. Service-line P&L pulls revenue from Resolute (patient-billing detail) and cost from Fusion (GL + supply chain consumption + payroll allocation). Physician productivity pulls work-RVU from Cogito (provider workflow data) and compensation from Fusion HCM (payroll detail). Both reports are built during the migration as part of the cross-system reporting layer — typically rebuilt from the legacy versions but with cleaner data lineage thanks to Fusion + Cogito integration. Drill from service-line P&L to the underlying GL/AR/supply detail is supported through Cogito + OTBI cross-system links. Same applies to grant accounting and 340B reporting.
Layered access control. Epic-side reporting access stays under Epic's existing security model (typically Epic security points + Cogito roles administered by Epic security team). Fusion-side reporting access uses Oracle Fusion role-based security (data security policies, role hierarchies, data access sets). Cross-system reporting consumers — typically FP&A analysts, controllers, service-line directors — get scope-limited Cogito read access plus Fusion OTBI access. HIPAA scope-limiting applied: clinical access requires clinical role assignment; finance-only users see consolidated data without patient identifiers. Single sign-on (SSO) covers both layers via Okta/Azure AD typically. Privacy officer reviews cross-system access scoping during migration cutover.
Increasingly yes. Caboodle is Epic's cloud-scale data lake — SQL warehouse + Spark + R/Python notebook environment. For health systems adopting Caboodle (typical Year 3 of the modernization roadmap), Caboodle becomes the cloud-scale analytical layer reading from Chronicles via Epic-published patterns. Post-migration cross-system reporting can include Caboodle + Fusion BI / OTBI combinations: large-scale Epic clinical analytics from Caboodle joined to Fusion GL/HCM data via Power BI or Tableau. Clarity continues for operational SQL Server reporting; Caboodle handles cloud-scale analytics; Fusion OTBI handles back-office reporting. Three layers, complementary, with clear ownership boundaries.
Book a 30-minute reporting workshop. We'll walk through your critical-report inventory, your Fusion OTBI rebuild plan, your cross-system Layer 3 design (service-line P&L, physician productivity, cost report) and the Cogito ↔ Fusion integration. Concrete reporting plan before the call ends.