Application decommissioning
See exactly what a system holds, which rules govern it, and whether each part should be archived, retained, or destroyed before you turn it off.
Health systems run hundreds of applications across multiple archive vendors, and no one can see across them. StrandFour continuously maps what exists, where it lives, who owns it, what it costs, and where it sits in its lifecycle. Read-only. Vendor-neutral. Your systems of record stay the source of truth.
| Item | Copies | Where it lives | Size each | Match basis | Status |
|---|---|---|---|---|---|
| Patient D•••, J. · MRN •••4821 · 3 duplicated items · 3.8 GB redundant | |||||
| MRI brain without contrastImaging study · Mar 2022 | 3 | Radiology PACSVNAArchive A | 1.4 GB | DICOM study UID | Review |
| MRI lumbar spineImaging study · Nov 2021 | 2 | Legacy PACSVNA | 960 MB | DICOM study UID | Retention eligible |
| Discharge summaryPDF · Jan 2023 | 4 | EHR documentsDoc imagingFile shareArchive A | 2.1 MB | Content hash | Review |
| Patient R•••, M. · MRN •••0937 · 2 duplicated items · 1.8 GB redundant | |||||
| CT chest with contrastImaging study · Jun 2019 | 2 | Legacy PACSArchive B | 1.8 GB | DICOM study UID | Legal hold |
| Signed consent formScanned PDF · Jun 2019 | 3 | EHR documentsDoc imagingArchive B | 640 KB | Content hash | Review |
| Application | Owner | Hosting | Storage | Annual cost | Utilization | Status |
|---|---|---|---|---|---|---|
| Enterprise EHR | Clinical Applications | On-premises | 1.42 PB | $18.6M | 94% | Active |
| Legacy EHR, North Region | IT Department | Vendor-hosted | 38 TB | $1.2M | 6% | Retirement candidate |
| Radiology imaging | Imaging Services | Hybrid | 1.96 PB | $4.1M | 81% | Active |
| Cardiology imaging | Heart & Vascular | On-premises | 212 TB | $640K | 38% | Migrating |
| Departmental file shares | Unassigned | On-premises | 96 TB | $210K | 12% | Missing owner |
| Document imaging (retired) | HIM | Archive vendor | 54 TB | $180K | 2% | Archived |
Product preview. Illustrative data.
Projected annual growth in healthcare data, faster than manufacturing, financial services, or media.
RBC Capital MarketsUnique applications a large health system can run across on-premises and cloud environments.
Becker’s Hospital ReviewAverage annual IT spend per U.S. hospital, about 2.3% of operating expenses.
Definitive HealthcareOf health IT leaders see retiring legacy systems as a significant cost-savings opportunity, up from 58% two years earlier.
HIT ConsultantHealth systems accumulate hundreds of applications through growth, mergers, and EHR transitions. What data exists and where it lives is known only through the application that owns it. So retention decisions get made when a system is retired, the moment there is the least time to make them well.
Release of information and lookback requests mean searching by hand across live applications, multiple archive vendors, and backups.
Decommissioning stalls when no one can show what an old system holds, which rules govern it, or whether it should be archived, retained, or destroyed.
Archive locations, data-return terms, and renewal dates sit with individual owners. Portability risk surfaces only when an exit is already urgent.
Every one of these starts with the same question: what do we have, and where is it? StrandFour answers it once and keeps answering it.
See exactly what a system holds, which rules govern it, and whether each part should be archived, retained, or destroyed before you turn it off.
Find every copy of the same MRI, CT, or PDF across PACS, archives, and file shares, grouped by patient.
Track when records become eligible for disposition and which are under hold, across every application and archive.
Know which archive vendor holds each system’s data, the data-return terms, and when each contract renews.
Catalog an acquired organization’s applications, archives, and storage alongside your own before migration planning begins.
Find everything held for one patient across live systems and archives in a single search.
Each layer builds on the one before it. StrandFour starts with the applications you already run and grows into a complete, continuously maintained map of your information estate.
Connects read-only to approved systems and continuously catalogs the information estate down to the individual study and document: type, size, source application, location, and timestamps. The underlying information stays where it already lives.
An operational profile for every application and repository: owners, users, utilization, storage, cost, growth, hosting, and lifecycle status. Track where each system’s data is archived, its data-return terms, and when its contract renews.
Associates information with retention requirements, lifecycle stages, legal holds, and exceptions, and flags what needs review. StrandFour observes and surfaces. It does not enforce, delete, or act on source systems.
Correlates information for one patient across disconnected applications and archives, showing where it lives, when it was last accessed, and how large it is. See every duplicate MRI or PDF for that patient in one place. Relationships that cannot be established deterministically carry a confidence score.
A health system’s information estate changes every day. StrandFour keeps the map current, so lifecycle decisions happen throughout an application’s life, not only when it is retired.
New data every day, new applications every quarter, and new facilities with every acquisition. The registry updates as they arrive.
Records become eligible for disposition every day, and legal holds start and end. StrandFour tracks each one as it changes.
Release of information and lookback requests arrive constantly. Patient-level search answers them in one place instead of across every archive.
Systems keep making new copies of studies and documents. Ongoing detection keeps a one-time cleanup from wearing off.
Archive locations, data-return terms, and renewal dates change. The register stays current, so a vendor exit is never a surprise.
Every new facility is another consolidation project. The same registry catalogs it before migration begins.
It is not another EHR, archive, or system of record. Your existing systems remain authoritative. The first release is about understanding your information, not moving it.
Mapping information to patients means holding identifiers like name and MRN. StrandFour keeps only what the map needs, never copies the documents or images themselves, and protects it under a business associate agreement.
Discovery is scheduled and rate-limited so clinical system performance is never affected.
No automated deletion and no actions on source systems. StrandFour identifies; your teams decide.
Health systems have invested billions in systems of record. Each one knows its own data. No independent system understands the information across all of them.
Hospitals already monitor their applications, infrastructure, and networks continuously. We believe the information inside them deserves the same.
StrandFour adds that layer: one view of what exists, where it lives, and what governs it, no matter where it is stored or how the technology underneath changes.
AI can reason over the map. StrandFour builds and maintains the map.
Design partners shape the platform around their real environment and work directly with the founding team. Engagements are read-only and scoped together with your IT and security leadership.