A 3–4 week productised epic systems migration assessment that delivers a sized, costed, risk-rated plan for moving downstream finance, HCM and SCM off legacy ERPs onto Oracle Fusion. Clarity-driven discovery, Resolute feed inventory, HIPAA risk register, parallel-run strategy. Chronicles is never touched.
Every Epic deployment is different. The epic systems migration assessment turns those differences into a numbered, costed, risk-rated plan — before the build SOW is written.
An epic systems migration assessment is not a sales discovery and it is not a Big-Four-style multi-month diagnostic. It is a structured, productised, 3–4 week exercise that produces a numbered scope map of the downstream finance, HCM and SCM data flows that will move to Oracle Fusion, a Resolute HB/PB downstream feed inventory, an OpTime/Willow/Beaker interface inventory, a legacy ERP retirement plan, a HIPAA risk register and a parallel-run reconciliation strategy. The output is a fixed-fee, fixed-timeline build SOW — not a 'phase two' for another paid engagement.
The discovery happens against your Clarity environment using a read-only service account scoped to downstream finance/HCM/SCM tables. Chronicles is never queried. The Clarity inventory automation walks the relevant tables (ARPB_TRANSACTIONS, HSP_TRANSACTIONS, HSP_ACCOUNT, CLARITY_EMP, CLARITY_SER, RX_MED, RX_FILL, OR_LOG, OR_CASE, ORDER_PROC and the rest), captures row counts, partition shapes and ETL freshness watermarks, and produces a sized extraction plan. Your Epic technical team reviews the scope and signs off before any data movement.
On the legacy ERP side, the epic systems migration assessment inventories your Lawson, PeopleSoft, McKesson, EBS, ADP or other in-scope source systems — chart of accounts, supplier master volume, worker master, fixed assets register, GL history years, interface dependencies. A target Fusion COA strawman is drafted (typically 7-segment healthcare: Entity, Service Area, Department, Account, Cost Center, Patient Type, Future) and walked through with finance leadership. The build SOW that follows is sized off these numbers — not off assumptions.
Patterns refined across multiple healthcare ERP migrations — already costed, already risk-rated.
How many distinct downstream journal posting patterns Resolute generates is the single biggest cost driver. The assessment enumerates them automatically — 200 patterns vs 20,000 changes the COA design fundamentally.
Pharmacy locations, automated dispensing cabinets (Pyxis/Omnicell tied to Willow), 340B program scope. The assessment enumerates every inventory location feed that Fusion Inventory will need to consume.
Preference card count per service line is the cost driver for OpTime → Fusion Materials Management. The assessment enumerates the full catalogue and the consumption history per card.
Reagent suppliers and instrument-linked materials are usually the messiest data shape in any healthcare migration. The assessment maps every Beaker-tied supplier and tier of contract pricing.
How many CLARITY_EMP records also exist in CLARITY_SER (i.e. employee + provider role) determines the worker master crosswalk complexity. The assessment quantifies the overlap.
CMS cost report (typically May 31 federal, varies by hospital), state regulatory filings, 990 deadlines map to a no-go-live calendar. The assessment enumerates and overlays them on the proposed timeline.
A repeatable 3–4 week cadence for regional health systems (6–8 weeks for multi-IDN academic medical centres).
60–90 minute sessions with CFO/controller, CIO/VP IT, Epic technical director, Resolute admin, supply chain VP, HR director, internal audit, CMIO. Charter signed. Read-only Clarity service account scoped and provisioned by your Epic technical team.
Automated inventory runs against Clarity downstream finance/HCM/SCM tables: row counts, partition shapes, ETL freshness watermarks, Cogito reconciliation references. Legacy ERP inventory runs in parallel: Lawson/PeopleSoft/McKesson chart-of-accounts, supplier master, worker master, FA register.
Bridges/Cloverleaf/Rhapsody interface engine catalogue extracted. Every Willow/OpTime/Beaker downstream feed enumerated. HL7 v2 and FHIR R4 endpoints catalogued. Inbound and outbound flows mapped. Future steady-state OIC integration architecture drafted.
COA strawman drafted (typically 7-segment healthcare), reviewed with finance leadership, iterated. HIPAA risk register populated. 42 CFR Part 2 flags surfaced. Joint Commission retention plan documented. Parallel-run reconciliation strategy designed.
Full assessment document written. Numbered scope, sized timeline, fixed-fee build SOW drafted. Executive presentation to CFO, CIO, Epic technical director and internal audit. Sign-off captured. Service account scope broadens from discovery to extraction (if you proceed).
If you proceed, the build phase starts immediately with no re-discovery. Clarity service account in place, scope numbered, Resolute feed inventory catalogued, COA strawman ready for formalisation. If you don't proceed, the assessment is yours to take to any vendor.
Six concrete differences that cut cost by 70–80% and time-to-build-start by 3–4x.
Clarity inventory automation is pre-built. Big Four reinvents it per engagement at $300/hour for 4–8 weeks. The assessment runs the same automation in 3–5 days.
7-segment healthcare COA strawmans are pre-built from prior migrations. Big Four drafts from scratch with PowerPoint workshops over 4–6 weeks.
Resolute HB/PB posting patterns catalogued from prior Epic conversions. The assessment matches your patterns against the library in days. Big Four interviews-out the same patterns over weeks.
Assessment is fixed-fee and 100% credited against the build engagement. Big Four bills T&E and discovery becomes a permanent overhead cost line.
HIPAA risk register template and Joint Commission retention plan are pre-built. Big Four redesigns each from scratch with the privacy officer.
Assessment closes with a signed, sized, fixed-timeline build SOW ready to execute. Big Four exits and a new RFP starts. Save 6–12 weeks of procurement cycle.
An epic systems migration assessment is a 3–4 week structured discovery exercise that delivers a sized, costed, risk-rated migration plan for moving your downstream finance, HCM and SCM stack off legacy ERPs (Lawson, PeopleSoft, McKesson, on-prem EBS) onto Oracle Fusion — while leaving Epic clinical untouched. Deliverables: a Clarity table-by-table extraction scope map, Resolute HB/PB downstream feed inventory, OpTime/Willow/Beaker interface inventory, legacy ERP retirement plan, COA crosswalk strawman (typically 7-segment healthcare), HIPAA risk register, timeline sized to your year-end and CMS cost report deadlines, total budget envelope and a parallel-run reconciliation strategy. Outputs are signed by your CFO, CIO and Epic technical director.
Because every Epic deployment is different — and the difference shows up in cost. The same regional health system can have Resolute configured to post 200 downstream journals daily or 20,000; can have Willow integrated with 2 inventory locations or 47; can have OpTime preference cards numbering in the hundreds or the tens of thousands; can have its Clarity ETL refresh on a 2-hour cycle or a 12-hour cycle. Without an epic systems migration assessment, RFPs go out with placeholder assumptions and projects overrun 40–70%. With one, the actual interface inventory, data volumes, refresh cadence and reconciliation requirements are quantified before the contract is signed.
Three to four weeks for a regional health system (3–8 hospitals, 200–800 beds each). Week one: discovery interviews with Epic technical, Resolute admins, supply chain, HR, finance, internal audit. Week two: Clarity inventory automation runs against your environment, scoping every downstream finance/HCM/SCM table; legacy ERP inventory runs in parallel; interface engine (Bridges, Cloverleaf, Rhapsody) catalogue extracted. Week three: COA strawman, reconciliation strategy, parallel-run plan, HIPAA risk register, regulatory timeline mapping (CMS cost report, 990, state filings). Week four: write-up, exec presentation, signed scope. For multi-IDN academic medical centres (15+ hospitals) plan 6–8 weeks instead.
No. The epic systems migration assessment reads only from Clarity (the SQL Server relational mirror), Cogito (analytics layer), and your legacy ERP (Lawson, PeopleSoft, McKesson, etc.). Chronicles is never queried. The Epic technical team configures a read-only Clarity service account scoped to downstream finance/HCM/SCM tables — typically the same scope your reporting analysts use. The assessment introduces no risk to clinical operations, no Epic configuration changes, no Hyperspace builds, no Chronicles writes. Your Epic governance signs off on the service account scope before any discovery extract runs. HIPAA chain of custody is preserved from the first read.
A regional health system fixed-fee assessment is $75K–$150K depending on hospital count, legacy ERP complexity and Resolute downstream feed volume. Academic medical centres with multi-IDN consolidation run $200K–$400K. The assessment is credited 100% against the migration engagement if you proceed. Versus consultant-led discovery (where a Big Four firm will quote $400K–$1.2M for the same scope and take 12–16 weeks), the productised assessment is roughly 70–80% cheaper and 3–4x faster — because the Clarity inventory automation, COA strawman patterns and Resolute feed catalogue are pre-built from prior healthcare migrations, not redeveloped per engagement.
Six roles minimum from your side: CFO or controller (signs off on COA and reconciliation strategy), CIO or VP IT (signs off on integration architecture), Epic technical director (signs off on Clarity scope and interface inventory), Resolute admin (walks through HB/PB posting rules), supply chain VP (walks through Willow/OpTime/Beaker integration), and internal audit (signs off on HIPAA chain of custody and parallel-run evidence). Optional but recommended: HR director (worker master crosswalk), Cogito lead analyst (reconciliation reference), CMIO or clinical informatics director (signs off on "clinical stays untouched" guarantee). The epic systems migration assessment runs 60–90 minute sessions with each role across weeks 1–2.
Yes — these are mandatory deliverables, not optional. The HIPAA risk register catalogues every PHI touchpoint in the migration path, the safeguards applied at each, and the audit-log retention plan (6 years federal HIPAA minimum, up to 30+ years for some state and Joint Commission requirements). HITECH breach notification readiness is reviewed. 42 CFR Part 2 (substance use disorder) flags are surfaced where Resolute or Willow data may carry Part 2 patient identifiers. Joint Commission survey-readiness retention plan is documented. Where applicable, FDA 21 CFR Part 11 (clinical research at academic medical centres) and GDPR (international Epic deployments) coverage is added. Privacy officer and security officer sign off before any production extract.
Three things, in parallel. First, a fixed-fee, fixed-timeline Statement of Work for the migration build phase is issued — typically 16–24 weeks for a regional health system, 9–14 months for an academic medical centre. Second, the Clarity service account is broadened from discovery scope to extraction scope (still read-only, still no Chronicles access). Third, the Fusion target environment is provisioned and your COA crosswalk moves from strawman to formal design with finance team sign-off. The assessment artefacts feed directly into the build — no rework, no re-discovery, no re-budgeting. If you choose not to proceed, the assessment is yours to keep and run with a different vendor.
Book a 30-minute scoping call. We'll walk through your Epic deployment, your legacy finance/HCM/SCM stack, your Resolute configuration and your year-end deadlines — and quote the assessment in the call. Chronicles is never touched.