MEDITECH Patient Records, Clinical, Billing & MPI Migration — Domain Deep Dive

This domain deep-dive is the part of a MEDITECH project that touches patient-related data — and the reality is that for most Oracle Fusion finance migrations, the answer is 'as little as humanly possible'. Oracle Fusion is a finance / HCM / SCM platform, not an EHR. The dominant pattern: patient demographic records (MPI — Master Patient Index), clinical records (encounter detail, diagnosis, procedure, lab, rad, pharmacy, nursing documentation), patient billing detail (charge-level posting, payer claim, remit detail, denial workflow) stay in MEDITECH. Only aggregated summary data — daily charge summary at cost-center-day-payer grain — crosses to Fusion GL. This page deep-dives the rare scenarios where patient records / clinical / billing data must move (full MEDITECH-to-Expanse modernization, IDN clinical consolidation onto a different EHR, retirement of MEDITECH MAGIC with archive of historical patient billing), and the HIPAA-rigorous discipline required.

Four scenarios. (1) MEDITECH MAGIC to Expanse modernization within MEDITECH — patient records, clinical detail and MPI migrate from MAGIC to Expanse on MEDITECH's native platform with MEDITECH professional services involvement. Syntra ETL is not typically the primary tool here. (2) MEDITECH retirement in favor of Epic, Cerner / Oracle Health, or another EHR — patient records / clinical / MPI exit MEDITECH and load into the new EHR via FHIR R4 import or vendor-specific tooling. (3) MEDITECH MAGIC retirement with patient billing / clinical history archived to a long-term retention system (S3-based archive accessible for CMS RAC, HIPAA, state retention) — Syntra ETL handles the archive extraction with HIPAA-rigorous controls. (4) IDN clinical consolidation onto a single EHR following acquisition — multiple MEDITECH instances consolidate or retire onto a chosen platform. Pattern (3) — archive-on-retirement — is the most common Syntra ETL scope.

MPI is the most sensitive table in any healthcare migration — it carries patient demographic detail (name, DOB, SSN where present, address, phone, payer identifiers) and the cross-system patient identifier (MRN). The Syntra ETL meditech patient records, clinical, billing, MPI migration follows a strict HIPAA discipline. (1) BAA executed covering MPI movement. (2) Minimum-necessary scope — only MPI fields the destination actually requires. (3) Patient consent posture verified per state law where applicable. (4) Encryption in transit (TLS 1.3) and at rest (AES-256). (5) Per-record access logging with operator identity. (6) Chain-of-custody from MEDITECH MPI extract to destination MPI load, hash-signed at each step. (7) Reconciliation: source MPI count = destination MPI count, source MRN set = destination MRN set, source-MRN-to-destination-MRN mapping table preserved with the same retention horizon as the records themselves.

Clinical records (encounter, diagnosis, procedure, lab, rad, pharmacy, nursing documentation) move through the healthcare interface engine ecosystem rather than as a bulk database extract. The pattern. (1) MEDITECH HCIS Suite or Expanse FHIR R4 endpoints emit clinical resources (Encounter, Condition, Procedure, Observation, MedicationRequest, MedicationAdministration). (2) Cloverleaf or Rhapsody routes and transforms to destination-specific formats. (3) Destination EHR ingests via its FHIR R4 import endpoint or native bulk-load tooling. (4) Reconciliation at the resource-count and resource-hash level by encounter, by patient, by date range. (5) Clinical reviewer sign-off on a sampled set of patient records — a registered nurse, a physician informaticist or a clinical lead verifies that representative patient charts in the destination match source. (6) HIPAA audit-signed manifest per migration wave covering BAA, encryption, access logging.

Patient billing detail (charge-level posting, payer claim, remit detail, denial workflow, adjustment history) is the volume-heaviest part of a patient records migration. Typical hospital systems carry 5-15 years of billing history with 10-100 million billing records per entity. The Syntra ETL approach. (1) Define retention horizon — typically the longer of CMS RAC look-back (3 years extendable for fraud), HIPAA (6 years), state hospital association retention (varies, NY 22yr surgical, MA 30yr minor) and 340B HRSA compliance horizon. (2) Hot tier — recent 2-3 years accessible online for active denials and appeals. (3) Warm tier — 3-7 years accessible within hours for audit response. (4) Cold tier — 7-30 years accessible within days for state retention compliance. (5) HIPAA Object Lock retention enforces the per-record horizon. (6) Aggregated GL summary continues to flow daily to Fusion GL via FBDI.

MPI migration carries the maximum HIPAA control burden because it moves identified PHI by definition. Additional controls beyond finance scope. (1) Per-record consent verification where state law requires explicit patient consent for record transfer. (2) HHS OCR notification posture pre-defined — even when no breach occurs, large-volume MPI movement frequently triggers HHS OCR awareness obligations. (3) Identity matching governance — destination system MPI may have different matching rules than MEDITECH (probabilistic vs deterministic, score thresholds, manual review queue); merge-or-split decisions must be governed. (4) Patient access rights preserved — patient amendment requests, access requests and accounting-of-disclosures requests must work across the migration boundary. (5) Breach contingency plan — if PHI leaks during migration, breach notification clock starts; the migration plan includes the breach response playbook upfront.

Yes, with additional discipline. Behavioral health records (mental health, substance use disorder), 42 CFR Part 2 substance-use treatment records, HIV / AIDS records under state-specific rules, minor reproductive health records under state-specific rules, and genetic information under GINA all carry additional protection beyond standard HIPAA. The migration plan inventories special-protection data at scope definition, applies the additional consent / access / disclosure controls, segments these records in the destination with destination-system access controls matching source restrictions, and produces additional audit evidence per special-protection category. Behavioral-health-specialized hospital scopes (psych hospitals, substance-use facilities, community mental health centers) carry materially higher control burden — and the migration plan reflects it.

Six artifact categories per migration wave. (1) HIPAA control evidence — BAA in effect, minimum-necessary scope per data domain, encryption proof, access logging, breach contingency plan, HHS OCR notification posture. (2) MPI reconciliation — source MPI count = destination MPI count, MRN set match, source-to-destination MRN mapping table. (3) Clinical reconciliation — resource counts by Encounter / Condition / Procedure / Observation / MedicationRequest / MedicationAdministration, hash match per resource. (4) Billing reconciliation — claim count, payment count, denial count, balance match per service date. (5) Clinical reviewer sign-off — RN / physician informaticist / clinical lead reviewed sampled patient charts vs destination. (6) Special-protection evidence — behavioral health, 42 CFR Part 2, GINA controls applied per record category. Signed by privacy officer, CMIO, controller, compliance officer.