ALLSCRIPTS / VERADIGM DECOMMISSIONING

    Allscripts / Veradigm Decommissioning — License Savings Without Retention Risk

    Engineered allscripts / veradigm decommissioning for Sunrise (and Altera Sunrise), TouchWorks, Professional EHR, Practice Fusion and related instances. Archive deployment, successor-EHR integration, license retirement, NIST 800-88 media sanitization, knowledge transfer — five workstreams coordinated for HIPAA-clean retirement.

    $1M–$5M+
    Annual license savings per instance
    70–85%
    TCO reduction on retention
    16–22 wk
    Per-instance retirement timeline
    NIST 800-88
    Media sanitization built in

    What allscripts / veradigm decommissioning is — five workstreams, one coordinated runbook

    Decommissioning is more than turning off a server. It is the synchronized retirement of clinical access, financial reporting, retention storage, license contracts, infrastructure and institutional knowledge.

    When a health system has moved active clinical workflow off Sunrise (whether the original Allscripts version or post-2022 Altera Digital Health), retired TouchWorks ambulatory practices, sunset Professional EHR or closed Practice Fusion subscriptions, the natural next step is allscripts / veradigm decommissioning — turning off the source systems entirely and capturing the license, infrastructure and operational savings. Done well, the system goes off-line invisibly: clinicians retrieve historical context through their new EHR's viewer; finance retrieves prior-year analytics through OTBI / BI Publisher views on the archive; HIM responds to subpoenas and HIPAA right-of-access requests through the archive's retrieval portal; auditors see a stronger retention story than they had before. Done poorly, the system goes off-line with retention gaps, clinician complaints, audit findings and emergency restore projects.

    The allscripts / veradigm decommissioning runbook coordinates five workstreams so the system goes off-line cleanly. Workstream 1: full archive deployment (covered separately by the data archival and cloud archive runbooks). Workstream 2: successor-EHR integration so historical clinical context retrieves through the new EHR — Epic Care Everywhere, Cerner / Oracle Health BedRock and FHIR, Altera Sunrise back-integration, athenahealth and other ambulatory successors via FHIR R4. Workstream 3: license retirement — Allscripts/Veradigm or Altera support contract cancellation per the contract's notice period (typically 90–180 days), Sybase or SQL Server license termination, third-party integration license cancellation, DR replication contract retirement. Workstream 4: infrastructure retirement — server, storage, network and DR retirement with NIST 800-88 media sanitization for HIPAA Security Rule compliance. Workstream 5: knowledge transfer — capturing IT, clinician and HIM institutional knowledge before the system is gone.

    Coordination matters because the workstreams have dependencies. License cancellation cannot complete until the archive is verified and successor-EHR integration is live. Infrastructure cannot be retired until license contracts release the hardware. Knowledge transfer has to happen while the system is still running because nobody can demo a decommissioned system. The allscripts / veradigm decommissioning runbook sequences these so each workstream finishes in the right order and the CFO captures license savings as soon as legally possible.

    What allscripts / veradigm decommissioning eliminates

    1
    Annual license fees
    Allscripts/Veradigm or Altera support, Sybase or SQL Server licensing, third-party integration licensing — typically $500K–$3M per instance per year.
    2
    Infrastructure cost
    Server, storage, network, DR replication and data-center floor space — typically $200K–$1M per instance per year.
    3
    Application support staff
    Dedicated DBA, application admin and integration engineer FTEs — typically $300K–$1M per instance per year.
    4
    Security and compliance burden
    Patch management, vulnerability scanning, penetration testing, HIPAA Security Rule audit prep — eliminated alongside the source system.

    The five workstreams inside an allscripts / veradigm decommissioning

    Each runs in parallel with explicit dependencies and sign-off gates between them.

    🗄️

    Archive deployment

    Full source-system extract to the long-term cloud archive. Per-state retention enforced. Sub-15-second retrieval verified. Sign-off prerequisite for source shutdown.

    🏥

    Successor-EHR integration

    Historical clinical context retrieves through the new EHR's viewer — Epic Care Everywhere, Cerner BedRock/FHIR, Altera Sunrise, athenahealth FHIR. Clinicians see one continuous timeline.

    📜

    License retirement

    Allscripts/Veradigm/Altera support contract cancellation per notice period. Sybase/SQL Server license termination. Third-party integration license cancellation. DR replication contract retirement.

    🔧

    Infrastructure retirement

    Server, storage, network and DR retirement with NIST 800-88 media sanitization. IT asset disposal vendor coordination. Per-device disposal log with serial, sanitization method, verification.

    🧠

    Knowledge transfer

    IT, clinician and HIM institutional knowledge captured before the system is gone. Documented retrieval workflows. Trained backup contacts on archive retrieval portal.

    ⚖️

    Legal hold + audit handoff

    Active subpoenas, legal holds and open audits carried through the archive. Privacy officer and legal counsel sign-off on the hold inventory before source decommission proceeds.

    The allscripts / veradigm decommissioning runbook — eight stages

    A repeatable per-instance retirement workflow. Typical timeline: 16–22 weeks per Allscripts/Veradigm instance.

    1

    Decision + Notice — Weeks 1–2

    CFO, CIO, CMIO, privacy officer and legal counsel decision to decommission. Contractual notice period started with Allscripts/Veradigm or Altera (typically 90–180 days). Communication to clinicians, finance and HIM about timeline.

    2

    Archive Deployment — Weeks 2–10

    Full allscripts / veradigm data archival deployment (see separate runbook). Source extract complete. Archive load, indexing, per-state retention policy applied. Sub-15-second SLA verified. PHI handling per-domain configured.

    3

    Successor-EHR Integration — Weeks 6–14

    Historical clinical context integration with the successor EHR. Epic Care Everywhere, Cerner BedRock/FHIR, Altera Sunrise back-integration, athenahealth FHIR — whichever applies. Tested with clinician focus groups.

    4

    Finance Reporting Cutover — Weeks 10–16

    Allscripts / veradigm historical reporting layer in production. Finance VPs trained on OTBI/BI Publisher views. HIM trained on retrieval portal. Source-system reporting workload retired.

    5

    License Cancellation Coordination — Weeks 12–18

    Allscripts/Veradigm/Altera contract cancellation finalized per notice period. Sybase/SQL Server license termination scheduled. Third-party integration licenses retired. DR replication contracts ended. CFO sign-off on savings projection.

    6

    Knowledge Transfer + Legal Hold Sign-off — Weeks 14–18

    IT, clinician and HIM knowledge documented. Backup contacts trained on archive retrieval. Privacy officer and legal counsel sign off on active legal-hold inventory carried through to the archive.

    7

    Source Decommission — Weeks 18–20

    Source Allscripts/Veradigm/Altera instance frozen, then powered down. Database connections terminated. Application servers shut down. Network access revoked.

    8

    Infrastructure Sanitization + Sign-off — Weeks 20–22

    NIST 800-88 media sanitization per IT asset disposal policy. Per-device disposal log. Final allscripts / veradigm decommissioning sign-off pack issued: archive verification, license cancellation confirmation, sanitization log, savings realization.

    What gets retired in an allscripts / veradigm decommissioning — the asset inventory

    Six categories of cost that come off the books when the system goes dark.

    💰

    Vendor support contracts

    Allscripts/Veradigm or Altera Digital Health support and maintenance — typically $500K–$2M per instance per year for acute Sunrise; $100K–$500K per ambulatory practice for TouchWorks/Professional EHR.

    🗄️

    Database licensing

    Sybase or SQL Server licensing — typically $100K–$500K per instance per year depending on cores and edition. Retired with the application.

    🖥️

    Infrastructure

    Server hardware (or VMware/cloud-VM capacity), storage arrays (or cloud block storage), network capacity, DR replication targets — typically $200K–$1M per instance per year.

    👷

    Application support staff

    Dedicated Allscripts/Veradigm DBA, application admin, integration engineer FTEs — typically $300K–$1M per instance per year, often re-deployable to successor-EHR work.

    🔗

    Third-party integrations

    Interface engine connections (Rhapsody, Mirth, Cloverleaf), reporting tools (Cognos, etc.), specialty modules, ePrescribe and patient-portal third parties — retired with the source.

    🛡️

    Security and compliance overhead

    Patch management, vulnerability scanning, penetration testing, HIPAA Security Rule audit prep, SOC 2 controls — all eliminated alongside the source system.

    Frequently asked questions

    What does allscripts / veradigm decommissioning actually involve?+

    Allscripts / veradigm decommissioning is the engineered retirement of a Sunrise, TouchWorks, Professional EHR, Practice Fusion or related Allscripts/Veradigm instance after its active workflow has moved to a successor system. It involves five workstreams: (1) full source-system extract to the long-term archive — every clinical, financial and operational record preserved under HIPAA, state retention and Joint Commission requirements; (2) successor-system integration so historical context retrieves through the new EHR's clinical viewer; (3) license avoidance — terminating Allscripts/Veradigm or Altera support contracts, Sybase/SQL Server licenses, third-party integration licenses, DR replication contracts and application-support staffing; (4) infrastructure retirement — server, storage, network and DR retirement per IT asset disposal policies with NIST 800-88 media sanitization; (5) knowledge transfer — capturing institutional knowledge from clinicians, IT staff and HIM personnel before the system goes dark. The allscripts / veradigm decommissioning runbook coordinates all five so the system goes off-line without gaps in retention, retrieval or audit-readiness.

    Why are health systems doing allscripts / veradigm decommissioning now in 2026?+

    Three converging drivers. First, the 2022 Allscripts/Veradigm split created uncertainty — Sunrise moved to Constellation Software's N. Harris Group (now Altera Digital Health), Veradigm carries the ambulatory / payer / life-sciences book with public-listing trouble (delisting drama, restated financials, SEC investigation). Many health systems have chosen to reduce dependency. Second, successor EHRs (Epic, Cerner / Oracle Health, Altera Sunrise for customers who stayed) are now in production at most large IDNs, so the historical Allscripts/Veradigm instances are no longer needed for active workflow — only for retention. Third, license-maintenance fees and infrastructure costs for zombie systems running purely for retention range $1M–$5M+ per year per instance, with cloud archive alternatives 70–85% cheaper. The CFO wants the savings; the CIO wants the security-patching burden off the team; the CMIO wants no clinician forced to log into a deprecated system for historical context. Allscripts / veradigm decommissioning satisfies all three.

    How does allscripts / veradigm decommissioning preserve HIPAA, state and Joint Commission retention obligations?+

    Through the long-term archive deployed before the source system is decommissioned. Every required record — Sunrise clinical and financial, TouchWorks ambulatory, Professional EHR, Practice Fusion, FollowMyHealth, dbMotion identity reconciliation, Veradigm Network claims (with appropriate Data Use Agreements) — extracted in full to the cloud archive. Per-state retention engine carries Texas 7yr, Massachusetts 30yr, California 7+ (longer pediatric), Illinois 10yr ambulatory, New York 6yr post-encounter or pediatric age 28, Florida 5yr — computes maximum applicable retention per record. S3 Object Lock enforces immutability. HIPAA accounting-of-disclosures logging on every retrieval. Joint Commission and CMS Conditions of Participation audit retrieval served from the archive with sub-15-second SLA. Auditors see a stronger retention story after decommissioning than before — one consolidated log instead of multiple instance-specific logs.

    What happens to clinician access to historical patient context after allscripts / veradigm decommissioning?+

    Historical patient context retrieves through the successor EHR's clinical viewer via the archive's integration. For Epic customers, the archive registers as a Care Everywhere or Health Information Exchange partner — pediatric history, longitudinal medication, problem-list timeline and historical encounters surface in Hyperspace alongside current Epic data. For Cerner / Oracle Health customers, the archive integrates via BedRock or FHIR R4 endpoints into PowerChart. For Altera Sunrise customers (post-2022), the archive integrates back through Sunrise's own data layer for retrospective queries. For ambulatory practices that moved to athenahealth, NextGen or eClinicalWorks, the archive integrates via FHIR R4. The clinician sees one continuous patient timeline — they do not log into a deprecated Allscripts/Veradigm system. The allscripts / veradigm decommissioning is invisible from the clinical workflow side once the integration is live.

    How long does an allscripts / veradigm decommissioning take?+

    For a single Allscripts/Veradigm instance — typical Sunrise instance at a single hospital or TouchWorks across one ambulatory group — 16–22 weeks end-to-end including archive deployment, successor-EHR integration, license cancellation coordination, infrastructure retirement and final sign-off. For a multi-instance health system — e.g., a large IDN retiring acute Sunrise plus 15 TouchWorks ambulatory practices plus 5 Practice Fusion subscriptions — 8–14 months with instances retired in waves. The pacing is set by archive deployment (12–18 weeks per instance, often parallelized), successor-EHR integration testing, license-cancellation notice periods (Allscripts/Veradigm contracts typically require 90 to 180 days notice), and CFO sign-off cycles. The allscripts / veradigm decommissioning runbook sequences these so license cost savings start accruing as soon as legally possible.

    Does allscripts / veradigm decommissioning include the 2022-era Altera Digital Health Sunrise instances?+

    Yes — and that is a frequent scenario. After the 2022 Constellation Software / N. Harris Group acquisition of Sunrise (rebranded Altera Digital Health), many health systems chose not to renew Altera contracts and migrated active clinical workflow to Epic or Cerner / Oracle Health. The historical Sunrise instance — whether technically Allscripts pre-2022 or Altera Digital Health post-2022 — becomes the allscripts / veradigm decommissioning candidate. The data model is unchanged across the corporate boundary; the archive ingests from the Altera-managed Sunrise instance using the same channel-1 interfaces it would have used before the split. Sunrise license retirement saves the Altera support fee; the underlying Sybase or SQL Server license retires the same way; the rest of the runbook proceeds identically.

    What about NIST 800-88 media sanitization for the Allscripts/Veradigm infrastructure?+

    Required for HIPAA Security Rule compliance. Allscripts / veradigm decommissioning includes a media-sanitization workstream coordinated with your IT asset disposal vendor: NIST 800-88 Clear for systems being repurposed within the organization (cryptographic erase plus single-pass overwrite); Purge for systems leaving the organization (multi-pass overwrite, degaussing for magnetic media, or cryptographic erase with verified key destruction); Destroy for end-of-life media (shredding, incineration). Every disposed device is logged with serial number, sanitization method, verification result, operator identity and disposal vendor — generating the HIPAA-compliant audit trail OCR will want if a breach narrative ever references the decommissioned infrastructure. The runbook ties media disposal to the archive sign-off — no media leaves the data center until the archive is verified complete and signed.

    How does allscripts / veradigm decommissioning handle in-flight subpoenas, legal holds and open audits?+

    All carried through the archive. Subpoenas active at the time of allscripts / veradigm decommissioning get logged as legal holds in the archive — affected records' retention windows extend indefinitely until the matter resolves. HIPAA right-of-access requests in flight are completed before source decommission so the requester sees no service interruption. Open OCR investigations, Joint Commission audits and SOX audits get a memo from the privacy officer and legal counsel noting the archive replacement and providing the new retrieval contact — auditors typically welcome the upgrade because archive retrieval is faster and the chain-of-custody documentation is stronger than source-system retrieval. The legal team signs off on the legal-hold inventory before source decommission proceeds.

    Plan your allscripts / veradigm decommissioning

    30-minute scoping call with your CFO, CIO, CMIO and privacy officer. We inventory the instances ready for retirement, model license-savings ROI, sequence archive deployment and successor-EHR integration, and produce a concrete allscripts / veradigm decommissioning runbook and timeline.