The cerner migration checklist that runs a hospital downstream cutover from week-one stakeholder lockdown to week-twenty-two legacy decommission certificate. Sixty-plus items across nine phases, each with owner, timing, sign-off artifact and dependency.
A real cerner migration checklist is hospital-specific. It encodes PHI handling, charge-master discipline, Joint Commission walkthroughs, CareAware device handling and pediatric retention — items that do not appear on a generic ERP migration list.
The cerner migration checklist is the working artifact of a 16–22 week single-hospital cutover or a 28–40 week multi-hospital IDN cutover. It runs across nine phases, each with a defined entry condition, a defined exit condition, and a sign-off artifact that the next phase consumes. Phase 1 — stakeholder lockdown — finishes when the CFO, CMIO, CHRO, CIO, privacy officer, Medical Staff Office and biomed lead sign a scoped charter. Phase 9 — decommission — finishes when the legacy GL, HRIS and asset-register decommission certificates are signed by the CIO and privacy officer.
What distinguishes a real cerner migration checklist from a generic one is that it encodes the PHI-handling decisions per data domain, the Joint Commission audit walkthroughs, the CareAware device-feed handling, the HealtheIntent VBC contract metric integration, the pediatric retention partitioning rules, and the per-state retention policies for the immutable compliance archive. A generic ERP migration checklist would skip every one of those items. The cerner migration checklist is also explicit about the FBDI / HDL load sequence dependencies — load Position.dat before HCM Worker.dat tries to assign a position and the load fails; load FBDI Journal before the cost center exists and the journal posts to suspense.
The cerner migration checklist scales for multi-hospital IDN scope without adding new item categories. Most items are IDN-level one-time (BAA, PHI classification, compliance archive provisioning, audit calendar review); the per-facility items multiply (charge-master crosswalk per facility-charge-master, decommission certificate per facility, parallel-run reconciliation per facility per period). A 5-hospital IDN cerner migration checklist runs 80–110 items; a 12-hospital IDN runs 110–160 items — sub-linear scaling because the framework items do not multiply.
Skip any of these six and the cerner migration checklist leaves auditable gaps.
LDS / Safe Harbor / pseudonymized / aggregate-only per data domain, with privacy-officer signature. The cerner migration checklist captures the classification and the signed Data Use Agreements where LDS applies.
Cerner charge master to Fusion natural account, signed by CFO. Per-facility for IDNs with multiple charge masters. The cerner migration checklist scales this item per master, not per facility.
Cerner Provider table + HRIS + credentialing → single Fusion HCM Worker. The cerner migration checklist captures the resolution rule, the audit trail back to each source, and Medical Staff Office sign-off.
Device category crosswalk to Fusion Asset categories, biomed maintenance routing, IoMT telemetry policy. The cerner migration checklist treats CareAware as first-class scope, not back-of-list.
Per-state retention policies encoded in S3 Object Lock object metadata. The cerner migration checklist captures the 50-state rule lookup and the pediatric age-of-majority+ partitioning.
Joint Commission record retrieval, CMS RAC dry-run, HIPAA accounting-of-disclosures dry-run, SOX 404 evidence-pack. The cerner migration checklist sequences these during parallel run, not after go-live.
Each phase has an entry condition, an exit condition, and a sign-off artifact that the next phase consumes. Skip a sign-off and the cerner migration checklist exposes the project to a re-do.
CFO / CMIO / CHRO / CIO / privacy officer / Medical Staff Office / biomed lead identified. Project charter signed. Scope frozen. BAA signed between covered entity and Syntra ETL. Exit: signed charter.
Single privacy-officer review session. Every domain classified LDS / Safe Harbor / pseudonymized / aggregate. Data Use Agreements drafted. KMS key provisioned. Exit: signed PHI classification table.
Charge master freeze date agreed with revenue cycle. Fusion enterprise structures provisioned. SIEM endpoint registered. Exit: charge-master snapshot and Fusion foundation config baseline.
Millennium read-only replica access. HealtheIntent Redshift/Snowflake views. BedRock OAuth2 credentials. FHIR R4 bearer-token. CareAware device-feed access. Day-one accounting-of-disclosures logging. S3 Object Lock archive bucket. Exit: end-to-end extraction-to-archive smoke test.
Charges → natural accounts (CFO signed). Departments → cost centers (CFO signed). Providers → HCM Workers (CHRO + Medical Staff Office signed). Assets → Fusion Assets (biomed + finance signed). Items → Item Master (supply chain signed). HealtheIntent VBC → analytics. Exit: six signed crosswalk workbooks.
Local Fusion 26x schema validation. Sample-row payload generation. Error-pattern triage. Worker.dat / Assignment.dat / Position.dat dependency order tested. Exit: passing local validation across all emitters.
S3 Object Lock policies set per-state. Pediatric partitioning. Joint Commission retrieval rehearsal. CMS RAC dry-run. HIPAA accounting-of-disclosures dry-run. SOX 404 evidence-pack. Exit: archive countersigned by privacy officer + CIO.
Two full month-end close cycles in parallel. Per facility per period to the cent. HCM parallel-pay reconciliation. Sign-off pack assembled. CFO + CHRO + privacy officer + Medical Staff Office countersign. Exit: countersigned sign-off pack.
Production cut to Fusion. Legacy GL / HRIS / asset-register decommission certificates signed by CIO + privacy officer. Steady-state integration runtime engaged. Exit: decommission certificates archived.
The cerner migration checklist items that get dropped from consultant project plans — and the audit-time pain they reintroduce.
Often added post-cutover. Missing pre-cutover logs leave a 6-year HIPAA accounting gap that surfaces at the next OCR audit. Cerner migration checklist treats it as day-one provisioning.
Often defaulted to flat 7-year retention. Pediatric records need age-of-majority+5-to-10 in most states. Cerner migration checklist encodes per-state pediatric rules in object metadata.
Often replaced by server shutdown. Decommission certificates are the audit artifact that Joint Commission / CMS surveyors look for. Cerner migration checklist treats them as required.
Often deferred to post-go-live. Discovering archive issues during a real Joint Commission survey is much more painful. Cerner migration checklist rehearses during parallel run.
Often omitted, leaving crosswalks chasing a moving charge master. Cerner migration checklist captures the freeze date and the change-control process for in-flight changes.
Often defaulted to vendor-managed keys. Customer-controlled KMS keeps the re-identification key with the covered entity. Cerner migration checklist provisions in customer cloud.
A complete cerner migration checklist runs 60–80 items across nine phases: stakeholder lockdown, PHI classification, charge-master freeze, Millennium / HealtheIntent / CareAware extraction discovery, crosswalk design, FBDI/HDL emitter readiness, compliance archive provisioning, parallel-run reconciliation, and cutover-plus-decommission. Each item has an owner (CFO, CHRO, CMIO, CIO, privacy officer, Medical Staff Office, biomed lead), an expected timing (week N of the cutover), a sign-off artifact (workbook, certificate, audit-pack section) and a dependency note (what cannot start until this item closes). The cerner migration checklist is the working spine of a 16–22 week single-hospital cutover; it scales to 28–40 weeks for multi-hospital IDN scope without adding new item categories — just multiplying instances per facility.
Twelve pre-extraction cerner migration checklist items. (1) BAA signed between covered entity and Syntra ETL. (2) Privacy officer named as project sponsor. (3) Per-domain PHI classification table reviewed and signed. (4) Charge master freeze date agreed with revenue cycle. (5) Cerner Millennium read-only replica access provisioned. (6) HealtheIntent Redshift/Snowflake read-only views provisioned. (7) BedRock OAuth2 client credentials with scoped read-only access issued. (8) FHIR R4 client registered and bearer-token issuance tested. (9) CareAware device-feed read access provisioned. (10) S3 Object Lock (or equivalent) bucket provisioned for archive. (11) KMS key for PHI pseudonymization provisioned in customer cloud. (12) SIEM endpoint registered for HIPAA accounting-of-disclosures log forwarding. Skipping any of these leaves the cerner migration checklist exposed to a re-do.
Six cerner migration checklist items for Joint Commission readiness. (1) Joint Commission record-retrieval rehearsal during parallel run — random-sample retrieval against the archive, with retrieval time and chain-of-custody documented. (2) Archive object signing — every archived record signed and timestamped. (3) Sub-15-second per-record retrieval verified. (4) Patient-by-patient retrieval supported (not just facility-aggregate). (5) Date-range retrieval supported (the most common Joint Commission query). (6) Chain-of-custody documentation — extraction logged, transformation logged, archive object signed, retrieval logged. These six cerner migration checklist items leave a Joint Commission audit pack ready to hand to the surveyor without further preparation.
Six cerner migration checklist items for the CareAware → Fusion Assets pipeline. (1) CareAware device-feed read access provisioned and authenticated. (2) Device category crosswalk from CareAware to Fusion Asset categories signed by biomed lead. (3) Depreciation account assignment per category signed by finance. (4) Biomed maintenance history extracted and routed to Fusion or to the compliance archive per device-type policy. (5) IoMT device telemetry summary-level extraction agreed with the biomed lead and CISO. (6) Device-acquisition event subscription configured for real-time post-cutover steady state. The cerner migration checklist treats CareAware as a first-class scope, not a back-of-the-list afterthought.
Nine IDN-specific cerner migration checklist items beyond the single-hospital base. (1) IDN facility-list locked with go-live wave assignment. (2) IDN-level charge-master consolidation policy agreed (single master vs per-facility masters with crosswalk). (3) IDN HRIS-source inventory documented (typically 1–3 sources). (4) IDN HealtheIntent footprint mapped — single or multi-tenant. (5) IDN CareAware deployment inventory. (6) IDN Soarian footprint inventory with retirement scope per facility. (7) IDN compliance archive partitioning policy by state retention law. (8) IDN audit calendar (Joint Commission, CMS, SOX 404) reviewed for blackout windows. (9) IDN per-facility decommission certificate template approved by CIO and privacy officer. The cerner migration checklist scales sub-linearly with hospital count — most items are IDN-level one-time, not per-facility.
The Fusion-side load sequence is unforgiving — load FBDI Journal Import before the cost center exists and the load fails. Eight cerner migration checklist items for load sequencing. (1) Foundation: Fusion enterprise structures, ledgers, business units, COA segments configured. (2) Master data: charge master → natural accounts, departments → cost centers, providers → HCM Workers, assets → Asset categories, items → Item Master. (3) HCM Worker.dat and Assignment.dat loaded before Position.dat. (4) Position.dat loaded before any payroll-related load. (5) Item Master loaded before any supply-consumption FBDI. (6) Asset Master loaded before any CareAware asset event. (7) Open transactions loaded before closed history. (8) Closed history archived in immutable cloud — Fusion-load only if active reporting window requires it. The cerner migration checklist enforces this dependency order so loads do not fail on missing references.
Eight cerner migration checklist items that transition the cerner migration into a steady-state integration. (1) FHIR R4 webhook subscriptions for real-time clinical-impact events. (2) BedRock REST event subscriptions for real-time financial-impact events. (3) Millennium modified-since polling at 15-minute cadence for charge transactions. (4) HealtheIntent daily refresh for VBC contract metrics. (5) CareAware change-event subscription for asset events. (6) Monthly close reconciliation pack template installed. (7) Quarterly Cerner Millennium release compatibility test cadence agreed. (8) Annual SOX 404, biennial CMS RAC, triennial Joint Commission audit calendar populated. The cerner migration checklist closes with these eight items because the cerner migration is not a project; it is the start of an operating integration.
Five cerner migration checklist items for pediatric retention. (1) Pediatric record identification — patients <18 at last encounter — flagged in the archive partitioning. (2) Per-state pediatric retention rule encoded — typically age of majority (18 or 21 per state) + 5 to 10 years. (3) Per-state retention rule lookup table referenced for each pediatric record. (4) Retention-date computed and set on each archived object via S3 Object Lock. (5) Periodic retention-policy audit confirms no pediatric record is purged before its earliest legal disposal date. The cerner migration checklist treats pediatric retention as a partitioning-rule problem, not an exception-management problem.
30-minute scoping call — we walk through your Millennium domains, HealtheIntent footprint, CareAware register, Soarian inventory and audit calendar, then deliver a tailored 60-plus-item cerner migration checklist with owners and timing.