Cerner Migration Reconciliation the Board Will Sign

Related but distinct. Cerner data validation answers "did each load land correctly" at the record and field level. Cerner migration reconciliation answers the broader question — "does the new system, viewed as a whole, equal the old system on the financial, operational and workforce dimensions that matter to the CFO, CHRO and the board?" Reconciliation operates at the financial-close level (Cerner-derived legacy GL trial balance vs Fusion trial balance per fiscal period per facility), the encounter-parity level (total encounters in Cerner Millennium vs encounters represented in Fusion-side analytics), the workforce-parity level (Cerner provider tables active headcount vs Fusion HCM active workers), and the asset-parity level (CareAware device count vs Fusion Asset count). Validation feeds reconciliation; reconciliation is the artefact the board signs.

Five reconciliation pillars: (1) Financial-close reconciliation — Cerner-derived charge fact rolled into legacy GL trial balance per fiscal period per facility vs Fusion trial balance per cost centre per period, with closing journal mappings and accrual rules documented; (2) Encounter parity — Cerner Millennium ADT-confirmed encounters per period per facility, with patient-pseudonym hash totals to confirm no encounter has been lost or duplicated; (3) Workforce parity — Cerner PRSNL active providers vs Fusion HCM active Workers per cost centre per pay cycle, with FTE totals; (4) Asset parity — CareAware device asset register per category per facility vs Fusion Assets, with original cost and accumulated depreciation reconciliation; (5) VBC and quality-measure parity — HealtheIntent value-based-care contract metrics vs Fusion-side analytics. Each pillar emits a per-period reconciliation grid signed by the relevant business owner.

Encounter parity is the parity check most consultant-led projects miss until parallel-run weekend. The cerner migration reconciliation engine extracts the full encounter table from Millennium (ADT events with admit, transfer and discharge timestamps) per facility per period; computes a pseudonym-hashed total of encounter IDs; and reconciles against Fusion-side records (where Fusion-side encounters appear via the charge-link or via the patient-account AR record). Discrepancies — typically (a) encounters that didn't generate a charge in the period (observation cases, pending charges, denied claims), (b) encounters split across fiscal-period boundaries, (c) encounters retroactively cancelled — are categorized and counted per facility per period. The reconciliation grid shows total encounters expected, total represented in Fusion, and the categorized variance — signed by the revenue-cycle leader.

Cerner posts charges in near-real-time as encounters progress; legacy GLs typically book daily or weekly; Fusion closes on the corporate fiscal calendar with formal period-close events. The cerner migration reconciliation framework defines an explicit close-alignment rule per service line — when does a Cerner charge become a Fusion journal? — captured in the data-mapping workbook and applied consistently. Late-arriving charges (a charge posted in Cerner after Fusion period close) are accrued or back-posted per the rule, and the cerner migration reconciliation engine surfaces them in a dedicated late-arriving log so the next-period reconciliation accounts for them transparently. Without this rule, the reconciliation drifts every month; with it, the reconciliation is to the cent every period.

Yes. The signed cerner migration reconciliation pack carries the chain-of-custody from Cerner source extract through transformation through Fusion load through reconciliation. Every Cerner extract is signed (SHA-256 manifest); every transformation step is logged (which crosswalk, which mapping rule, which PHI handling mode); every Fusion-side record is traceable back to the source extract via the chain-of-custody manifest; the reconciliation grid is signed by the CFO (financial), CHRO (workforce), biomed lead (assets), privacy officer (PHI handling) and internal audit (controls). SOX 404 walkthroughs use the manifest plus reconciliation pack as evidence that the financial close is supportable. CMS Conditions of Participation audits use the encounter-parity log to demonstrate revenue cycle integrity. Joint Commission audits use the chain-of-custody to demonstrate record retention.

Yes. The same cerner migration reconciliation framework applies to Soarian-derived financial history that was archived as part of the migration. Soarian source extracts (made once during the decommissioning project) are reconciled against the compliance archive — counts, sums and hashes per fiscal period per facility — so the archive is provably equivalent to the retired Soarian instance for the retention window. When a Joint Commission auditor or a CMS RAC auditor requests records from a Soarian-era period, the cerner migration reconciliation pack documents that the archived records are the equivalent of the retired source. The framework handles Soarian, CommunityWorks legacy, PowerChart-for-closed-facilities the same way.

Initial migration sign-off: privacy officer, CFO, CHRO, biomed lead, internal audit, and (for multi-hospital IDNs) hospital-level CFOs per facility. Sign-off pages are integrated into the cerner migration reconciliation pack PDF with reviewer name, role, reviewed-period and digital signature. Post-cutover steady-state: monthly cerner migration reconciliation pack issued the day after Fusion period close, countersigned by CFO and CHRO each month; quarterly pack countersigned by internal audit; annual pack countersigned by external auditors as part of SOX 404 walkthrough. Joint Commission and CMS audit cycles draw from the steady-state pack archive directly — no special-request generation needed.

Most multi-hospital IDNs have facilities that joined Cerner Millennium at different times — sometimes a decade apart — with different chart-of-account starting points, different department codings, and in some cases parallel Soarian or legacy systems still resident on certain campuses. The cerner migration reconciliation framework treats each facility as an independent reconciliation unit with its own crosswalk versions, its own fiscal-calendar alignment and its own retention boundaries. The IDN-level pack rolls facility-level reconciliations into a consolidated view with explicit per-facility provenance so the board sees both the consolidated number and the per-facility composition. Acquisition events, divestiture events and facility closures are handled by adding or retiring facility units in the reconciliation register without disrupting the historical pack archive.