Pre-built epic systems to oracle fusion data mapping crosswalks for Resolute HB/PB → Fusion GL, CLARITY_EMP+CLARITY_SER → HDL Worker, Willow/OpTime/Beaker → Fusion Inventory + Materials. Column-level, sign-off-ready, 26x-current.
Mapping is the bridge between Clarity downstream tables and Fusion FBDI/HDL targets — the work that turns a migration architecture into loadable rows.
Most ERP migration projects under-scope mapping because the word sounds straightforward. In an Epic to Fusion context it isn't. Clarity has thousands of tables with tens of thousands of columns; Resolute HB/PB posts via configurable rules that aren't documented in a single place; CLARITY_EMP and CLARITY_SER overlap in non-trivial ways; Willow's 340B program adds a tier of contract pricing nuance; OpTime preference cards multiply the materials catalogue; Beaker reagent suppliers have instrument-linked tiering.
The epic systems to oracle fusion data mapping work bridges all of that into a small number of Fusion target templates: FBDI Journal Import (Resolute posting + legacy GL history), FBDI AP Invoice Import (supplier invoices), FBDI Supplier Import (vendor master), FBDI Fixed Assets Import, HDL Worker.dat (employee + provider), HDL Element Entry.dat (payroll), HDL Salary.dat, FBDI Item Import (Willow/OpTime/Beaker items), FBDI Inventory Transaction Import (consumption history). Each target has its own column schema for the current Fusion 26x release.
Syntra ETL ships pre-built crosswalk templates for every domain: column-level source-to-target maps, transformation rules (lookup, calculated, conditional, fixed value), validation rules and sign-off slots. Your engagement starts with the template pre-populated against the Epic patterns we've seen, your Resolute admin walks through the posting rules to confirm, your finance team signs off on the 7-segment COA, and the mapping is locked before the build engineers start writing the FBDI emission code. Compressed: 3–5 weeks vs 12–20 weeks consultant-led.
Patterns refined across multiple Epic-to-Fusion conversions. Configure to your instance instead of building from scratch.
Pre-built crosswalk patterns for the most common Resolute HB/PB posting rules: charge → revenue, contractual adjustment → contra-revenue, bad debt write-off, refund, transfer, payment posting. Configure to your instance.
Entity/Service Area/Department/Account/Cost Center/Patient Type/Future strawman matched to your prior reporting cuts. Validated against Resolute posting cardinality and Cogito reporting needs.
CLARITY_EMP × CLARITY_SER merge with NPI/SSN/employee-ID match logic. Provider attributes (specialty, NPI, DEA, board cert) preserved as Worker DFFs. No duplicate workers.
Pharmacy formulary mapping with 340B program flag, contract pricing tier and replenishment cost center context preserved from Willow into Fusion Inventory + Cost Accounting.
Preference card materials → Item master, case consumption → Inventory Transaction with implant tracking, lot, expiration. Cost center context preserved per surgical service line.
Lab reagent suppliers + instrument-linked materials mapped to Fusion Procurement with contract tier preserved. Common gotcha — Beaker has 5–10x more suppliers than legacy thought.
A compressed mapping cadence built on pre-built crosswalk templates. 3–4 weeks for regional health systems, 5–8 weeks for academic medical centres.
Crosswalk templates pre-populated for Resolute → FBDI Journal, CLARITY_EMP+SER → HDL Worker, Willow → FBDI Item+Inv, OpTime → FBDI Item+Inv, Beaker → FBDI Item+Procurement. Based on patterns from prior healthcare migrations.
Resolute admin walks through every active posting rule. Each rule matched to the pre-populated crosswalk library; exceptions documented. Cardinality (rule count × volume) confirmed.
7-segment healthcare COA strawman finalised with finance/controller. Validated against Resolute posting cardinality, Cogito reporting cuts, CMS cost report, 990 reporting needs. Account combinations rationalised (typical: 800–4,000 active).
CLARITY_EMP × CLARITY_SER merge logic finalised. Willow/OpTime/Beaker item master mapping reviewed with pharmacy/perioperative/lab leadership. 340B contract pricing flag confirmed. Cost center context per service line validated.
Crosswalks exercised against sample data extracts. Resolute posting replay reconciles to legacy trial balance. Worker merge produces no duplicates. Item master loads cleanly into Fusion sandbox. Errors surface before build engineers start emitter code.
Per-template owner sign-off: CFO/controller on Journal, HR director on Worker, pharmacy/perioperative/lab leads on Items. Mapping locked, hash-signed, handed to build engineering. Changes after lock require change-control.
Six concrete differences that compress the mapping phase from 12–20 weeks to 3–5 weeks.
Pre-built Resolute posting library covers 80%+ of typical patterns. Consultants reinvent each pattern over interviews — pattern-by-pattern, hour-by-hour.
7-segment healthcare COA strawmans drafted, validated and rationalised. Consultants run weeks of workshops to design from blank PowerPoint.
Per-template owner sign-off slots and audit trail built in. Consultants produce Excel that nobody owns and nobody re-runs in Phase 2.
Crosswalks exercised against sample data before lock. Consultants discover mapping errors during build phase when remediation costs 10x more.
Mapping templates tracked against Oracle Fusion 26x. Consultant mappings against an older release require re-mapping at the quarterly boundary.
3–5 weeks at fixed fee vs 12–20 weeks T&E at $300/hour. Mapping phase is the typical cost overrun line — pre-built crosswalks eliminate it.
Epic systems to oracle fusion data mapping is the field-level crosswalk design that translates Clarity downstream finance, HCM and SCM columns into Oracle Fusion FBDI/HDL templates. It covers Resolute HB/PB AR posting columns (ARPB_TRANSACTIONS, HSP_TRANSACTIONS) → Fusion GL Journal Import; legacy chart of accounts → 7-segment healthcare COA; CLARITY_EMP + CLARITY_SER worker master → HDL Worker.dat; Willow RX_MED + RX_FILL → Fusion Item + Inventory Transaction; OpTime OR_LOG + OR_CASE → Fusion Materials; Beaker ORDER_PROC + LAB_RSLT → Fusion Inventory + Procurement. Mapping is column-by-column, signed by finance/HCM/SCM owners. Chronicles MUMPS columns are never mapped directly — Clarity is the authorized source.
Three reasons. First, Clarity has thousands of tables and tens of thousands of columns — bespoke discovery takes weeks. Second, Resolute posting rules are configured per Epic instance and aren't documented in a single place — they have to be reverse-engineered from posting rule definitions in the Resolute admin tool. Third, the Fusion target COA (typically 7-segment healthcare) doesn't exist yet at mapping time — it has to be designed in parallel with the mapping. Consultant-led mapping commonly takes 12–20 weeks at $300/hour. Syntra ETL pre-built crosswalks compress this to 3–5 weeks: the column-level templates are pre-populated from prior healthcare migrations, leaving only the Epic-instance-specific posting rules and the COA finalisation.
A signed crosswalk artefact per Fusion target template. For FBDI Journal Import: source Clarity column → COA segment value with transformation rule (lookup table, calculated, fixed value) → target Fusion column → validation rule → sign-off owner. For HDL Worker.dat: source CLARITY_EMP/CLARITY_SER column → HCM attribute → conditional logic for employee-vs-provider role → target Fusion column → sign-off owner. Every crosswalk row is bound to a sample data extract so the mapping logic is exercised against real numbers before build kicks off. Stored as version-controlled Excel + JSON in your engagement repository, hash-signed at sign-off, referenced by the build engineers.
Resolute HB and PB posting rules are extracted from the Resolute admin tool (or its Clarity-published representations: HSP_REVENUE_LOC, ARPB_VISIT_GROUP, posting rule definitions) and converted into a transformation pattern library. Each rule says "when transaction type = X and revenue location = Y, post debit to GL account A, credit to GL account B with cost center C and patient type D". The epic systems to oracle fusion data mapping replays each rule against the new Fusion 7-segment COA: the same input produces a new posting line into Fusion GL Journal Import. Posting rules are signed off by the Resolute admin and the controller before the mapping is locked. Re-run reconciliation confirms the new posting matches the legacy posting at trial-balance level.
Standard healthcare 7-segment COA: Entity (legal entity per hospital), Service Area (clinical service line — Cardiology, Oncology, Surgery), Department (cost-center department), Account (5–6 digit natural account), Cost Center (often == Department in healthcare but kept separate for cross-cuts), Patient Type (Inpatient, Outpatient, Emergency, Observation), Future (for project accounting / 340B / grant overlay). The mapping work starts with the strawman drafted during the epic systems migration assessment, walks through every Resolute posting rule and every legacy ERP GL combination, validates that the new COA can carry every existing reporting cut, and is signed off by the CFO/controller before the build kicks off. Typical healthcare COA carries 800–4,000 active account combinations after rationalisation.
Two source tables, one target. CLARITY_EMP is the employee master (HR-owned), CLARITY_SER is the provider master (Epic clinical-owned). Many people exist in both — a hospitalist physician is both an employee AND a provider; a contracted radiologist may be only a provider; a non-clinical FP&A analyst is only an employee. The epic systems to oracle fusion data mapping merges the two with a person-record match (NPI, SSN-suffix, employee ID, name) and produces a single HDL Worker.dat row per person with role flags. Provider attributes (specialty, board cert, DEA, NPI) ride along as Worker descriptive flexfields. Employee attributes (payroll, benefits) ride as standard HCM attributes. Validation: every Resolute provider in Clarity must reconcile to a Fusion Worker with provider role set.
Yes. Willow mapping: RX_MED (formulary master) → Fusion Item Import, RX_FILL (dispensing) → Fusion Inventory Transaction Import, plus the 340B contract pricing tier where applicable. OpTime mapping: OR_LOG (case log) + OR_CASE (case details) → Fusion Materials Management, with preference card materials → Item master and consumption → Inventory Transaction. Beaker mapping: ORDER_PROC (lab orders) → Inventory consumption, plus reagent supplier master → Fusion Procurement Supplier. Each mapping carries cost center, lot tracking, expiration date and (for Willow) 340B program flag. For steady-state operation, these tables are also catalogued as OIC integration sources — same mapping serves both bulk migration and steady-state.
Oracle Fusion's quarterly release schedule (currently 26x) introduces schema changes in FBDI and HDL templates. Syntra ETL maintains the mapping crosswalk templates against Oracle's current GA release and pre-publishes delta notes for upcoming releases. Your engagement crosswalk picks up the current 26x release at signing; if the project crosses a quarterly boundary, the delta is applied automatically with no re-mapping work. For HDL specifically, the Worker.dat schema changes every 2–3 releases — the mapping template handles backwards-compat across the last 8 releases. This is the kind of maintenance that custom consulting projects punt to you as a Phase 2 cost.
Book a 30-minute mapping deep-dive. We'll walk through your Resolute posting rules, your worker/provider overlap, your Willow/OpTime/Beaker item catalogues, and show the pre-built crosswalks. Concrete mapping plan before the call ends.