Pre-built allscripts / veradigm data migration for Sunrise charges, TouchWorks ambulatory financials, Practice Fusion encounter data, dbMotion identity reconciliation, Veradigm Unity / Network feeds and clinician HCM context. BAA-signed, PHI-classified per domain, row-level reconciliation, FBDI/HDL emitters native to Fusion 26x.
The hard part is not pulling rows from Sunrise's Sybase database. It is governing PHI on every domain, reconciling Sunrise against TouchWorks against Practice Fusion against the Veradigm Network before anything reaches Fusion, and producing audit evidence the privacy officer can sign.
Allscripts / Veradigm is unusual among healthcare data sources in three ways. First, the data model is split across multiple product lines: Sunrise (acute care) on Sybase or SQL Server with a Sunrise Financial Manager overlay; TouchWorks and Professional EHR (ambulatory) on SQL Server with distinct schemas; Practice Fusion (cloud ambulatory) on AWS with a REST API surface; FollowMyHealth (patient portal) as a separate store; dbMotion as the cross-EHR interoperability layer; Veradigm Network and Veradigm Health Insights as payer/life-sciences analytical datasets. A real allscripts / veradigm data migration to Fusion has to reconcile across all of these before it loads anything. Second, the 2022 Allscripts/Veradigm split added complexity — Sunrise customers may now operate under Altera Digital Health with separate support and licensing, while ambulatory customers remain on the Veradigm contract. Third, retention rules are jurisdiction-specific and run from HIPAA's 6-year floor to 30+ years for adult records in some states and indefinite for pediatrics — with extended ambulatory-specific retention rules in Illinois, New York, Florida and elsewhere.
Syntra ETL solves this with a four-mode PHI handling framework reviewed once with your privacy officer per domain (Limited Data Set, Safe Harbor de-identification, pseudonymization, aggregate-only), pre-built extractors against every Allscripts/Veradigm data channel, and FBDI/HDL emitters that produce Fusion-native loads validated locally against the current 26x release schema before submission.
The same engine handles single-practice ambulatory scope, multi-facility health-system scope carrying both Sunrise and ambulatory, and the hybrid where some facilities have already moved off Allscripts (to Cerner or Epic) and only need their pre-cutoff history archived. Reconciliation produces a signed pack — Allscripts charge register vs Fusion GL trial balance to the cent per facility per period — that CFO, CHRO and privacy officer countersign before cutover. That signed pack is the deliverable the allscripts / veradigm data migration is judged on.
The transformations Syntra ETL ships pre-built. No bespoke Sybase SQL, no improvised REST clients, no manual Veradigm Unity development.
Limited Data Set, Safe Harbor de-id, KMS-pseudonymization, aggregate-only — chosen per data domain in a one-shot privacy-officer review and enforced uniformly through the allscripts / veradigm data migration.
Sunrise, TouchWorks, Professional EHR, Practice Fusion, dbMotion and Veradigm Network reconciled at the encounter, patient-pseudonym and asset levels before any Fusion load — catches drift that consultant projects only find post-go-live.
Pre-built FBDI Journal, Receipt, Supplier, Asset, Item emitters plus HDL Worker, Assignment, Position emitters. Validated locally against Fusion 26x schemas — errors caught in seconds.
Every read of PHI logged with patient pseudonym, user, timestamp, scope, purpose code, recipient — exports to SIEM, satisfies HIPAA's 6-year accounting-of-disclosures rule out of the box.
Sunrise watermarks, TouchWorks change tracking, Practice Fusion REST incremental endpoints, dbMotion daily refresh, Veradigm Unity change endpoints — captured into idempotent delta extracts supporting 1–2 cycle parallel-run.
Allscripts charge register vs Fusion GL trial balance to the cent per facility per period, supply consumption vs SCM, asset count vs Fusion Assets, headcount vs Fusion HCM — countersigned by CFO, CHRO, privacy officer.
Skip a step in this order and an FBDI Journal load fails on missing departments, or an HDL Worker load fails on missing positions.
Fusion enterprise structures, ledgers, business units, COA segments, natural-account hierarchy, departments, positions, item categories, asset categories configured via FSM. Nothing user-facing yet, but every downstream allscripts / veradigm data migration load depends on it.
Allscripts charge master → Fusion natural accounts. Allscripts departments → Fusion departments and cost centers. Provider tables → HDL Worker.dat and Assignment.dat for clinician headcount. Medical-device asset categories → Fusion Asset categories. Supply item master → Fusion Item Master via FBDI Item Import.
In-flight encounters and unposted charge transactions migrated via FBDI Journal Import. Open AR for patient and payer accounts via FBDI Receipt / Customer Import. Pending supply receipts via FBDI Receiving Import. Approval state preserved through AMX.
Closed financial periods loaded into Fusion if the active reporting window requires it; older history routed to the compliance archive. Either way queryable for audit during HIPAA/state retention windows.
Worker.dat, Assignment.dat, Position.dat loaded; clinician credentialing license-expiry dates carried; shift patterns mapped. Parallel-pay reconciliation with the legacy HRIS for one pay cycle.
Final delta replay across Sunrise, TouchWorks, Professional EHR, Practice Fusion, dbMotion, Veradigm Unity. Parallel financial-close cycle reconciled to the cent per facility. Signed-pack countersigned by CFO, CHRO, privacy officer. Legacy GL, HRIS, asset register frozen. Production cut to Fusion. Allscripts / Veradigm clinical unchanged.
The deliverables that land in your environment, not the slides.
Per-fiscal-period, per-facility journals derived from Allscripts charge transactions. Account-segment crosswalks applied. Locally validated against Fusion 26x schema.
Patient-account and payer-account receivables routed to Fusion AR via FBDI Receipt Import. Customer master reconciled across Allscripts patient-encounter shadow.
Clinician records (Sunrise + TouchWorks + Practice Fusion provider tables) loaded as Fusion HCM workers without clinical PHI. Credentialing license-expiry dates carried for compliance reporting.
Medical-device asset registry into Fusion Assets, with biomed maintenance history preserved in Fusion Maintenance.
Supply item master and consumption transactions to Fusion Inventory and Procurement, reconciled against Allscripts-fired charge codes.
Signed PDF + JSON: counts, sums, hashes per facility per period; HIPAA accounting-of-disclosures log; privacy-officer countersignature page; CFO and CHRO sign-off pages.
Allscripts / veradigm data migration is the engineered movement of patient-encounter financial data, charge transactions, supply consumption, medical-device asset records, clinician HCM context, and ambulatory practice-management summaries from Allscripts / Veradigm (Sunrise, TouchWorks, Professional EHR, Practice Fusion, dbMotion, Veradigm Network) into Oracle Fusion Financials, SCM and HCM. It is downstream consolidation — the Allscripts/Veradigm products remain the clinical and practice-management system of record, and PHI clinical detail (problem lists, medication orders, results, e-prescribing data) stays in those EHRs or routes to the compliance archive. What flows to Fusion is the financial and operational shadow plus the workforce data, all under HIPAA controls with BAA in place. Syntra ETL handles the full allscripts / veradigm data migration with pre-built extractors against every Allscripts/Veradigm product line and row-level reconciliation.
Patient demographic shadow (limited data set: encounter date, age band, geographic region — not name or DOB) for charge-to-customer mapping; encounters (admission, discharge, transfer events for Sunrise; visit events for TouchWorks/Professional EHR/Practice Fusion) for financial period assignment; charge transactions and contractual adjustments; supply consumption per encounter (item code, quantity, charge link); medical-device asset registry and biomed maintenance records; clinician provider tables (name, NPI, department, credentialing license-expiry dates) for Fusion HCM Worker creation; department and cost-center tables; charge master for natural-account crosswalk; Practice Fusion subscription-tier and billing data; FollowMyHealth portal-engagement summaries for population-health analytics; and Veradigm Network claim datasets where the customer has the appropriate data-use authorization. Clinical detail — orders, results, narratives, allergies, problems, e-prescribing — is not part of the allscripts / veradigm data migration to Fusion; it remains in the source EHRs.
PHI handling is governed per data domain by a HIPAA-aligned classification table reviewed and signed off by your privacy officer before extraction starts. Four handling modes: Limited Data Set (LDS) — direct identifiers stripped, indirect identifiers retained for analytical use, governed by a Data Use Agreement; Safe Harbor de-identification — full 18-identifier removal per 45 CFR 164.514(b)(2); pseudonymization — patient ID replaced with a deterministic KMS-encrypted token that lets Fusion link records without exposing the source MRN or Practice Fusion patient ID; aggregate-only — only counts and sums leave the source EHR. Every extraction is logged with user, timestamp, scope, purpose and recipient for the HIPAA accounting-of-disclosures audit. BAA covers every component of the allscripts / veradigm data migration pipeline.
Fusion-native load formats for every domain: FBDI Journal Import for charge-derived GL journals; FBDI AR Receipt/Customer Import for patient-account and payer-account receivables; FBDI Supplier Import for vendor consolidation; FBDI Fixed Asset Import for medical-device asset registry into Fusion Assets; HCM Data Loader (HDL) Worker.dat, Assignment.dat and Position.dat for clinician records; FBDI Item Import for supply chain consumables; and REST API payloads for incremental delta loads during parallel-run and post-cutover. Every payload validated against the current Fusion 26x release schema locally — validation errors surface in seconds, not after a 4-hour Fusion ESS job fails. Output staged as encrypted Parquet for the archival and analytical paths.
Every Allscripts-side record extracted is hashed at source (header hash + line hashes + PHI-handling hash). Every Fusion-side record loaded is re-hashed post-load. The reconciliation engine compares counts (encounters, charge transactions, supply consumption lines, worker records), sum totals (charges by department per fiscal period, supply spend by item category, workforce headcount by cost center), and hash signatures per facility per period. Any record that fails Fusion validation captured with field-level diagnostics ready for bulk fix. Output is a signed timestamped sign-off pack: Allscripts charge register vs Fusion GL trial balance to the cent per facility per period, supply consumption vs Fusion SCM, asset count vs Fusion Asset count, clinician headcount vs HCM Worker count. The allscripts / veradigm data migration audit pack is countersigned by CFO, CHRO and privacy officer.
Yes — and you should. After the initial bulk load, Syntra ETL captures Allscripts deltas via Sunrise's modified-since watermarks, TouchWorks and Professional EHR change tracking, Practice Fusion REST API incremental endpoints, dbMotion's daily refresh, and the Veradigm Unity API change endpoints. Deltas replay into Fusion through REST APIs. The standard pattern: 1–2 month-end financial close cycles run in parallel — Allscripts-derived close in the legacy GL versus Fusion close — reconciled per facility per period. Once CFO, CHRO and privacy officer sign off, the legacy GL freezes and Fusion becomes the system of record for financial close. Allscripts / Veradigm clinical and practice-management workflow is unchanged through the entire allscripts / veradigm data migration window.
HIPAA's accounting-of-disclosures rule requires covered entities to track when PHI is disclosed and to whom, for six years. Every allscripts / veradigm data migration read of PHI is logged with patient identifier (or the pseudonymized token), user identity, timestamp, scope, purpose code (operations / payment / research / law enforcement / etc.) and recipient system. Logs export to your SIEM via syslog or CloudTrail. When an Office for Civil Rights audit arrives, the accounting query runs against the immutable log store and produces the patient-by-patient disclosure report in minutes. Same store also serves Joint Commission record-retrieval audits and CMS Conditions of Participation audits — one log, three audit families. Practice Fusion and FollowMyHealth disclosures are logged through the same mechanism so the audit answer is consistent across ambulatory and acute footprints.
No. Syntra ETL consumes Allscripts / Veradigm data through Sunrise's read-only Sybase/SQL Server replica, TouchWorks and Professional EHR SQL Server replicas, Practice Fusion REST APIs, dbMotion interoperability views and the Veradigm Unity API surface as a parallel consumer — not as an interface engine or intermediary. Existing HL7 v2 feeds (ADT, ORM, ORU, DFT, SIU), FHIR R4 partner endpoints (payer queries, public-health reporting, ACO data sharing) and ePrescribe traffic keep running through your interface engine unchanged. The allscripts / veradigm data migration is invisible to clinical workflow and to external interface partners. Cutover affects only the downstream financial, SCM and HCM systems being consolidated to Fusion.
30-minute scoping call with your privacy officer, CFO and CHRO. We classify PHI per data domain, size Sunrise / TouchWorks / Practice Fusion / dbMotion / Veradigm Network extracts, and produce a concrete allscripts / veradigm data migration plan and budget before the call ends.