Allscripts / Veradigm EHR, Practice Management, Clinical History Migration — Three Domains, Three Patterns

Because EHR data, practice management data and clinical history are three distinct migration challenges with three distinct compliance frameworks, three distinct technical patterns and three distinct stakeholder groups. EHR data (clinical narratives, problem lists, medication orders, results, allergies) is PHI under tight HIPAA controls and stays in the source EHR or routes to the compliance archive — it doesn't cross to Fusion. Practice management data (scheduling, charges, claims, AR, payer mix) is the financial shadow of the clinical operation and crosses to Fusion as governed transactions. Clinical history (longitudinal patient record across years or decades) is the archive challenge with state-by-state retention obligations stretching to 30+ years. The allscripts / veradigm EHR, practice management, clinical history migration workstream treats each separately so each gets the right compliance framework, the right technical pattern and the right sign-off.

Through product-line-specific migration patterns. Sunrise (acute care, formerly Eclipsys, now under Altera Digital Health post-2022 sale): the EHR + practice management split is partly blurred because Sunrise Financial Manager overlays the clinical schema; the migration treats Sunrise charges as practice management data crossing to Fusion while Sunrise clinical narratives stay in Sunrise. TouchWorks (large physician group ambulatory): EHR and practice management are more cleanly separated; ambulatory PM data (scheduling, charges, claims) crosses to Fusion AR/GL while clinical encounter narratives stay in TouchWorks. Professional EHR (smaller practices): similar to TouchWorks pattern with simpler ambulatory PM. Practice Fusion (cloud ambulatory): cloud-API-driven PM data crosses to Fusion via REST APIs; clinical encounter detail stays in Practice Fusion. The migration workstream documents each product-line pattern explicitly.

An immutable cloud archive (S3 Object Lock or equivalent) holding clinical history per patient per encounter for the duration required by HIPAA (6-year floor), state medical-records laws (Texas 7 years post-encounter, Massachusetts 30 years, Illinois 10 years for ambulatory, New York 6 years or pediatric age 28, Florida 5 years, California 7+ years and longer for pediatrics), pediatric age-of-majority+ rules, Joint Commission audit retention (7 years financial+operational) and any contractual retention from research participation or specialty board certification. The archive is indexed for sub-15-second per-record retrieval, KMS-signed, RFC 3161 timestamped, with every read access logged to HIPAA accounting-of-disclosures. Clinical narratives, problem lists, medication orders, results metadata, encounter summaries and physician documentation all land in the archive in their source format (Sunrise SmartUI XML, TouchWorks Note objects, Professional EHR documents, Practice Fusion FHIR resources) for forensic-level reconstruction.

dbMotion is treated as a critical migration accelerator. dbMotion maintains a unified patient identity across Sunrise, TouchWorks, Professional EHR, Practice Fusion and external EHRs federated into the dbMotion master patient index. The allscripts / veradigm EHR, practice management, clinical history migration uses dbMotion's unified-identity views to reconcile cross-product patient identity at migration time — so a single patient who exists in Sunrise (Altera) acute, TouchWorks ambulatory and Practice Fusion (e.g., after seeing multiple practices in the IDN) lands in the archive as a single patient identity with cross-product encounter history. Without dbMotion, the migration would have to do patient-identity resolution manually across the five product schemas. dbMotion clinical encounter feeds also enrich the archived clinical history with cross-EHR encounter context where the patient saw external providers.

Practice management AR — the patient and payer accounts receivable — crosses to Fusion AR (Receivables) via FBDI Receipt and Customer Import. Payer mix data — which payers contribute what percentage of charges per facility per period — flows through as analytical dimensions on the Fusion side. Contractual adjustments (the difference between charged amount and contracted allowance per payer) cross as Fusion contra-revenue lines with per-payer routing. Self-pay and bad-debt write-offs route to the appropriate Fusion expense accounts. Practice Fusion's subscription-tier billing (the SaaS fee per provider per month) maps separately to a Fusion AP supplier entry rather than to AR. Payerpath claims clearinghouse data feeds into Fusion AR with payer-specific aging buckets. The migration produces a complete practice management financial reconstruction in Fusion that aligns to the cent with the historical Allscripts/Veradigm practice management close.

Yes, but with a specific pattern. FollowMyHealth (patient portal) holds patient-facing data: patient messages to clinicians, portal access logs, patient demographic edits, patient-reported outcomes. The migration extracts portal-engagement summaries (aggregate metrics on portal usage per practice per period for population-health analytics that lands in Fusion's analytical layer) but does NOT migrate patient-facing messages or PHI-rich portal data — that stays in FollowMyHealth or routes to the compliance archive under the same retention rules as clinical encounters. The portal continues operating uninterrupted through the migration; patients log in to the same portal, send messages to the same clinicians, view the same records. The migration's downstream impact on the portal is zero. Portal-engagement aggregate metrics in Fusion let the operations team report on patient engagement trends without touching individual patient portal data.

Veradigm Network and Veradigm Health Insights are de-identified clinical and claim datasets the customer has authorization to receive or contribute under data-use agreements. The migration treats these as a separate optional workstream signed off by the privacy officer and life-sciences research lead. If the customer wants to land Veradigm Network or Health Insights data into Fusion's analytical layer for executive reporting, the migration documents the Safe Harbor or Expert Determination de-identification mode applied per dataset, names the contractual retention window, encodes the authorized recipients, and routes the data to Fusion's analytical schema (not the transactional layer). Most customers don't migrate Veradigm Network data into Fusion's transactional ledger — it stays in the analytical layer for executive dashboards. Some customers route Veradigm Health Insights data to a separate research platform (Snowflake or Databricks) running alongside Fusion.

Practice management workstream (crossing to Fusion): aligns to the broader Fusion migration timeline — 14-18 weeks single-site, 22-32 weeks multi-facility IDN. EHR workstream (staying in EHR or routing to archive): runs in parallel as a no-EHR-impact activity — typically 8-12 weeks for archive setup, validation and steady-state ingestion. Clinical history workstream (archive deep-load): runs continuously across the migration window — typically 12-20 weeks for multi-decade clinical history depending on patient volume and state retention obligations. dbMotion identity reconciliation: runs upfront in weeks 1-3 to feed both the PM crossing and the archive deep-load. The three workstreams have different timelines but share the signed PHI classification, signed crosswalk register and signed retention matrix from the initial migration assessment.