Four-week structured MEDITECH migration assessment. MAGIC, C/S, 6.x and Expanse platform detection, NPR / M-AT / BCA inventory, HIPAA + Joint Commission + CMS RAC compliance posture, sized plan with binding timeline and budget.
The cost of a bad meditech migration assessment shows up six months later as scope creep, NPR report rebuild surprises and HIPAA control gaps surfaced under audit pressure. The Syntra ETL assessment exists specifically to make those surprises impossible.
MEDITECH is the EHR for over 23% of US hospitals — overwhelmingly community hospitals, critical access hospitals (CAHs), behavioral health facilities and small-to-mid IDNs that frequently grow by acquisition. Acquisitions inherit platform mix: one entity on MAGIC with NPR-heavy operations, another on Client/Server with the Data Repository licensed, a third already on Expanse with FHIR R4 endpoints. The meditech migration assessment has to map that mix per entity, because the extraction path is platform-specific and the cutover sequence depends on it.
A consultant-led assessment commonly spends the first 8–10 weeks just writing the discovery scripts and rebuilding HIPAA control documentation that should already be templated. Syntra ETL ships the discovery probe, the NPR catalog scanner, the BAA template, the HIPAA control checklist and the state-overlay retention matrix pre-built — so the assessment focuses on customer-specific decisions, not on rebuilding tooling.
The output is binding. Once the assessment is signed by finance, HR, the privacy officer, internal audit and the MEDITECH steward, it becomes the scope document for the migration project. No re-pricing, no re-discovery, no week-six surprise that the NPR report library is twice as large as estimated.
Patterns we see on virtually every MEDITECH hospital and IDN assessment, and the pre-built Syntra ETL response.
Acquisitions leave MAGIC, C/S and Expanse coexisting. Single Syntra ETL pipeline handles all three with platform-appropriate paths landing in one Fusion ledger.
800–3,000 active NPRs plus a long tail. Pre-built catalog scanner classifies retire / OTBI / BI Publisher / FAW / archive in week one.
Finance scope rarely needs PHI. Assessment draws the boundary explicitly, MRN hashing applied at extract, BAA scope locked before any data moves.
NY's 22-yr surgery rule, MA's 30-yr minor rule, 340B HRSA, CAH operational evidence — mapped to MEDITECH source and post-migration destination.
MAGIC's hierarchical Globals don't ODBC well. Pre-built NPR scheduled extract patterns clear 500K–2M rows per overnight window without touching bedside throughput.
Daily MEDITECH GL post to finance must survive cutover. Assessment specifies the FBDI Journal Import feed design before the project starts.
A structured four-week engagement that produces a binding scope, timeline and budget document.
Read-only platform-detection scan (MAGIC / C/S / 6.x / Expanse), HCIS Suite module inventory (MIS, NUR, PCM, OE, BMR, EMR, B/AR, Materials, GL, AP, Payroll/HR), DR licensing check, FHIR R4 reachability check, Cloverleaf / Rhapsody interface inventory.
Row counts per HCIS table, fund-accounting structure depth, cost-center hierarchy profile, NPR Report Writer catalog scan, M-AT script inventory, BCA cube inventory, custom report classification by business value.
Per-domain Fusion target mapping (MIS → Fusion GL/AP, HR/PR → Fusion HCM, Materials → Fusion SCM), HIPAA minimum-necessary boundary, BAA scope, de-identification policy, state-overlay retention matrix, CMS RAC / Joint Commission / 340B evidence map.
Timeline (typically 14–22 weeks), budget envelope, risk register, parallel-run strategy, reconciliation contract (what reconciles to what, to what tolerance), NPR rebuild backlog, sign-off pack circulated.
Signed by finance, HR, privacy officer, internal audit, MEDITECH steward. Becomes binding scope document for the migration project. No re-pricing, no re-discovery.
Assessment-team steward stays embedded with the project team through execution to ensure no scope drift from the signed plan.
Six binding deliverables that become the project foundation.
Per-entity MAGIC / C/S / 6.x / Expanse footprint with platform-specific extraction recommendation.
Row counts, complexity ratings and target Fusion module per HCIS Suite domain.
Every active report and script classified by business value with destination assignment.
BAA, minimum-necessary boundary, de-identification policy, state retention matrix.
Week-by-week timeline, budget, risk register, parallel-run strategy.
What reconciles to what, to what tolerance, signed by accountable parties.
A MEDITECH migration assessment is the structured discovery exercise that establishes scope, risk, timeline and budget for moving MEDITECH-resident finance, HCM and supply chain data into Oracle Fusion — while keeping the clinical EHR in place. It differs from a generic ERP assessment in four ways. First, it has to identify the platform mix: MAGIC (MUMPS-era), Client/Server (C/S), 6.x / READY, and Expanse are all in production across the installed base, often in the same IDN after acquisitions. Second, it has to inventory NPR Report Writer reports, M-AT (MEDITECH Automation Toolkit) scripts and the Data Repository (DR) SQL surface, because every report and integration is a potential cutover dependency. Third, it has to draw the HIPAA boundary: which data leaves MEDITECH at all, what minimum-necessary scope means for finance, and what the BAA covers. Fourth, it has to verify Joint Commission, CMS RAC and state hospital retention obligations on the source side before any extract.
The meditech migration assessment runs as a four-week structured engagement. Week one is the discovery probe: a read-only platform-detection scan against the MEDITECH environment identifies MAGIC vs C/S vs 6.x vs Expanse, inventories MIS / NUR / OE / PHA / B/AR / Payroll / HR / Materials Management module configuration, catalogs every active NPR report with run frequency and owner, and surfaces M-AT scripts and Cloverleaf or Rhapsody interface engine touchpoints. Week two is the data-volume and complexity profile: row counts per HCIS Suite table, fund-accounting and cost-center hierarchy depth, custom NPR vs DR usage split. Week three maps in-scope domains to Oracle Fusion targets and identifies HIPAA-relevant decisions. Week four delivers the sized plan with timeline, budget, risk register and reconciliation strategy. The output is signed by finance, HR, the privacy officer and the MEDITECH steward.
All four production platforms. MEDITECH MAGIC (the oldest, MUMPS programming language, hierarchical Globals / B-tree DB) — most legacy customers, hundreds of community hospitals, NPR Report Writer is the dominant extraction surface, Data Repository is sometimes licensed. Client/Server (C/S, the mid-generation platform) — adds direct SQL via DR and 6.x SQL extracts. 6.x / READY (the modern web-era release) — SQL-first, NPR coexists. Expanse (the current cloud / web-native, single-platform unified suite) — REST and FHIR R4 endpoints, BCA (Business and Clinical Analytics) cubes, Expanse Data Repository. The assessment auto-detects the platform mix, profiles each instance independently, and proposes the extraction path per environment: NPR scheduled extracts for MAGIC, DR SQL for 6.x, FHIR R4 for Expanse. Multi-entity IDNs running mixed platforms get one consolidated plan.
The standard Syntra ETL meditech migration assessment runs four weeks calendar time, costs a flat fee in the low five figures depending on scope, and delivers a signed plan with concrete timeline, budget and risk register. Consultant-led assessments commonly run 10–14 weeks and cost six figures before producing a comparable deliverable — primarily because they spend most of that time building bespoke NPR extract scripts and HIPAA control documentation from scratch. Syntra ETL ships those pre-built, so the assessment focuses on the customer-specific decisions: platform mix per entity, fund-accounting structure, cost-center hierarchy depth, NPR report classification, BAA scope, retention obligations and parallel-run strategy. The deliverable becomes the binding scope document for the migration project — no rework, no re-pricing once execution begins.
NPR Report Writer is MEDITECH's native reporting surface and the single largest hidden risk in any meditech migration assessment. Hospitals typically have 800–3,000 NPR reports in active rotation, plus another 5,000–15,000 in the catalog that may or may not still run. The assessment catalogs every NPR report — name, schedule, last run, owner, business purpose, source HCIS Suite tables — and classifies by destination: retire (40–60% are duplicates or low-value), rebuild in OTBI for ad-hoc analytics, rebuild in BI Publisher for pixel-perfect operational reports, rebuild in FAW (Fusion Analytics Warehouse) for executive dashboards, or preserve in a historical-reporting archive layer. The assessment surfaces the rebuild backlog before week three of the project, so OTBI work runs parallel with extract and the go-live includes the reporting layer.
Compliance assessment is a first-class part of the deliverable. The HIPAA review covers BAA scope, minimum-necessary boundary definition (finance-only typically excludes all clinical detail), de-identification methods at extract, encryption in transit (TLS 1.3) and at rest (AES-256), per-record access logging, and HHS OCR inquiry-readiness. The CMS RAC (Recovery Audit Contractor) review verifies that billing, charge and claims evidence for the audit window stays accessible — typically through a MEDITECH read-only archive plus a Fusion summary. The Joint Commission review confirms patient-care-relevant record integrity is preserved and the retention horizon (5–30+ years depending on state) is met. State-specific overlays — NY's 22-year surgical record retention, MA's 30-year minor record retention, 340B HRSA audit obligations, CAH-specific operational evidence — are mapped to the source MEDITECH module and the post-migration destination.
Yes. Every meditech migration assessment includes an interface engine inventory because Cloverleaf and Rhapsody are how MEDITECH talks to the rest of the hospital. The assessment lists every active HL7 v2 channel (ADT, ORM, ORU, DFT, MDM, SIU), every FHIR R4 endpoint exposed by Expanse, every flat-file interface to ancillary systems (LIS, RIS, PACS, pharmacy robots, EMAR, BCA cubes), and every batch extract to downstream finance and operational data warehouses. For each interface, the assessment identifies whether it survives the Fusion finance migration unchanged (most clinical interfaces do — Fusion is not in the clinical path), whether it needs to be rewired to a Fusion summary endpoint (the daily charge journal moves from MEDITECH GL post to Fusion FBDI Journal Import), or whether it can be retired (legacy point-to-point feeds replaced by the Fusion canonical model).
Six deliverables. (1) Platform-mix map per entity with MAGIC / C/S / 6.x / Expanse footprint, NPR vs DR vs FHIR extraction recommendation per environment, and concurrency / off-peak gating plan. (2) Data-domain scope document with row counts, complexity ratings and target Fusion module per HCIS Suite domain (MIS, HR/PR, Materials, B/AR summary). (3) NPR / M-AT / BCA inventory with rebuild backlog and OTBI / BI Publisher / FAW destination per report. (4) HIPAA + state-overlay compliance posture document covering BAA, minimum-necessary, de-identification, retention obligations and CMS RAC / Joint Commission / 340B / CAH evidence continuity. (5) Sized plan with week-by-week timeline, budget, risk register and parallel-run strategy. (6) Reconciliation contract — what reconciles to what, to what tolerance, signed by whom. The pack becomes the project bible.
Four weeks from kickoff to a signed scope document. We'll walk through your MEDITECH platform mix (MAGIC, C/S, 6.x, Expanse), NPR / M-AT / BCA library, HIPAA boundary and Fusion target — and deliver a binding timeline and budget.