Cerner to Oracle Fusion Data Mapping Field by Field

Field-level cerner to oracle fusion data mapping is the documented, signed-off translation of every Cerner / Oracle Health source column to its Oracle Fusion target attribute, with PHI handling mode, transformation rule, validation logic, default behaviour for nulls and the audit-trail format declared per field. For a typical Cerner-rooted health system that means roughly 1,800–2,400 source fields across Millennium Oracle DB tables, BedRock REST payloads, FHIR R4 resources, HealtheIntent Redshift views and CareAware device records — mapped to Fusion Financials GL segments, Receivables customer attributes, SCM item and supplier attributes, Assets fixed-asset attributes and HCM Worker / Assignment / Position attributes. Each mapping carries its own PHI classification (Limited Data Set, Safe Harbor de-id, KMS pseudonymization, aggregate-only) and is countersigned by the privacy officer, CFO and CHRO before any cerner to oracle fusion data mapping ships to production.

Millennium Oracle DB: the encounter table (ENCNTR), charge transaction table (CHARGE), patient demographic table (PERSON), order metadata, result metadata, ADT event log, charge master (CHARGE_TYPE / CHARGE_CODE), department table (LOCATION + ORGANIZATION), provider table (PRSNL), and CCL views layered on top. BedRock REST: charge, encounter, provider, department and supply resource representations. FHIR R4: Patient, Encounter, Observation, MedicationRequest, Practitioner, AllergyIntolerance, Condition, Coverage, Account, ChargeItem. HealtheIntent: risk-stratified patient cohorts, quality-measure performance, HEDIS / CMS Stars metrics, VBC contract performance, social-determinants enrichment. CareAware: device asset register, biomed maintenance history, IoMT device telemetry summaries. Soarian legacy: GL transactions, AR aging, vendor master from sunsetting Soarian instances. Every table and every resource has a field-level row in the cerner to oracle fusion data mapping workbook.

Each field carries one of four explicit PHI handling modes, declared in the mapping workbook before extraction begins. Mode 1 — Direct: the field carries no PHI and flows through unchanged (charge code, item SKU, department code, fiscal-period identifier). Mode 2 — Limited Data Set: indirect identifiers retained for analytical value, direct identifiers stripped (encounter date kept, MRN replaced by pseudonym, ZIP truncated to first three digits). Mode 3 — Safe Harbor: full 18-identifier de-identification per 45 CFR 164.514(b)(2). Mode 4 — Pseudonymized: patient identifier replaced by a deterministic, KMS-encrypted token that lets Fusion link records without exposing source MRN. Every field's mode is reviewed and signed by the privacy officer; the cerner to oracle fusion data mapping workbook is a HIPAA audit artefact in its own right.

Cerner's PRSNL.position_cd (clinician position) is a free-form code with 2,000+ historical values, no enforced taxonomy and frequent duplicates ('RN', 'Reg Nurse', 'Registered Nurse', 'RN-BSN' all in production). Fusion HCM's PER_POSITIONS has a strict hierarchical position model. The cerner to oracle fusion data mapping resolves this through a governed crosswalk: a clustering algorithm proposes consolidations; clinical leadership and HR review and approve; a position-master file produced; Cerner PRSNL.position_cd flows through a lookup that maps each historical value to the new Fusion Position. Outliers (≤5 occurrences) routed to a 'review' position queue. The crosswalk is signed by CHRO and the Medical Staff Office. Every clinician's resulting Fusion Position is auditable back to the original Cerner record.

Cerner's charge master holds 8,000–25,000 active charge codes per IDN (the upper end for academic medical centres with specialty service lines). Fusion Financials uses a natural-account segment plus sub-account in the COA — typically 200–600 active natural accounts per ledger. The cerner to oracle fusion data mapping defines a many-to-one crosswalk: each Cerner charge code maps to one Fusion natural account, with optional sub-account derived from department, service-line or facility. The crosswalk is built collaboratively — finance proposes the chart, CDM analysts confirm clinical fidelity, internal audit confirms SOX traceability. Output is a CSV crosswalk loaded as a Fusion lookup; charge transactions extracted from Cerner pass through it before becoming Fusion FBDI Journal Import lines.

Cerner Millennium uses a hierarchical LOCATION + ORGANIZATION model — facility, building, unit, room — alongside a department code on transactions. Fusion uses a cost-centre segment in the COA, typically aligned to organizational reporting structure. Cerner department codes do not necessarily match the cost-centre granularity finance needs — emergency department might be one Cerner location but three Fusion cost centres (ED triage, ED treatment, ED observation), and academic departments often need separate cost centres per service line. The cerner to oracle fusion data mapping defines the department-to-cost-centre crosswalk through joint workshops with finance and clinical operations; the resulting mapping is loaded as a Fusion lookup and applied during charge-to-journal transformation. Effective-dated so reorganizations are auditable.

Yes. CareAware exposes a medical-device asset register — model, serial number, manufacturer, location, biomed responsibility, acquisition date, depreciation method, expected useful life, alarm telemetry summary. Fusion Assets needs asset category, asset key, location segment, depreciation account, expense account, units, original cost and asset description. The cerner to oracle fusion data mapping defines field-level translation: CareAware device model + manufacturer combine into Fusion Asset description; CareAware location maps via the same crosswalk as Cerner LOCATION; biomed maintenance history flows to Fusion Maintenance work orders; alarm telemetry routes to the analytical Parquet path for biomed dashboards. The result is a single asset register shared by biomed and finance — typically the first time these two functions agree on what equipment exists.

Delivered as a governed multi-tab Excel workbook plus a machine-readable YAML/JSON equivalent: one sheet per source system (Millennium, BedRock, FHIR R4, HealtheIntent, CareAware, Soarian), one tab per Fusion target object (GL, AR, SCM Item, SCM Supplier, Assets, HCM Worker, HCM Assignment, HCM Position), plus master sheets for charge master crosswalk, department crosswalk, provider crosswalk, asset-category crosswalk and PHI classification register. Each row carries source field, source data type, target field, target data type, transformation rule, PHI mode, validation logic, null-handling default, sign-off date and reviewer. Maintained as a versioned artefact in your Git of choice — every change has a pull request with reviewer comments, the cerner to oracle fusion data mapping is auditable end to end.