Built for hospitals and health systems

The operational map of your information estate.

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.

Registry / Information / Duplicates Indexed 2h ago
Overview
Repositories
Patients
Policies
Flags
Audit
Duplicate copies1.24Macross 11 systems
Redundant storage418 TB10.7% of indexed
Patients affected186Kimaging and documents
Est. annual cost$1.9Meligible for review
ItemCopiesWhere it livesSize eachMatch basisStatus
Patient D•••, J. · MRN •••4821 · 3 duplicated items · 3.8 GB redundant
MRI brain without contrastImaging study · Mar 20223Radiology PACSVNAArchive A1.4 GBDICOM study UIDReview
MRI lumbar spineImaging study · Nov 20212Legacy PACSVNA960 MBDICOM study UIDRetention eligible
Discharge summaryPDF · Jan 20234EHR documentsDoc imagingFile shareArchive A2.1 MBContent hashReview
Patient R•••, M. · MRN •••0937 · 2 duplicated items · 1.8 GB redundant
CT chest with contrastImaging study · Jun 20192Legacy PACSArchive B1.8 GBDICOM study UIDLegal hold
Signed consent formScanned PDF · Jun 20193EHR documentsDoc imagingArchive B640 KBContent hashReview

Product preview. Illustrative data.

Read-onlyNever writes to production systems
Vendor-neutralAbove every EHR, archive, and cloud
ContinuousAlways current, not a one-time inventory
Healthcare onlyBuilt for hospitals and health systems
36%

Projected annual growth in healthcare data, faster than manufacturing, financial services, or media.

RBC Capital Markets
1,000+

Unique applications a large health system can run across on-premises and cloud environments.

Becker’s Hospital Review
$10.5M

Average annual IT spend per U.S. hospital, about 2.3% of operating expenses.

Definitive Healthcare
71%

Of health IT leaders see retiring legacy systems as a significant cost-savings opportunity, up from 58% two years earlier.

HIT Consultant
The problem

Every acquisition adds systems. No one sees across them.

Health 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.

Where is everything we hold on this patient?

Release of information and lookback requests mean searching by hand across live applications, multiple archive vendors, and backups.

Can we turn this system off?

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.

Who holds this data, and on what terms?

Archive locations, data-return terms, and renewal dates sit with individual owners. Portability risk surfaces only when an exit is already urgent.

Use cases

Where the map pays for itself.

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.

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.

OutcomeRetire systems on schedule and stop paying to keep legacy applications running.

Duplicate imaging and documents

Find every copy of the same MRI, CT, or PDF across PACS, archives, and file shares, grouped by patient.

OutcomeRecover storage spent on redundant copies, and keep it from growing back.

Retention and legal hold

Track when records become eligible for disposition and which are under hold, across every application and archive.

OutcomeDispose on time, respect every hold, and stop paying to keep what you no longer need.

Vendor exit and renewal

Know which archive vendor holds each system’s data, the data-return terms, and when each contract renews.

OutcomeNegotiate renewals with leverage and avoid surprise exit costs.

M&A consolidation

Catalog an acquired organization’s applications, archives, and storage alongside your own before migration planning begins.

OutcomeDecide what carries forward from a complete inventory, not from guesswork.

Release of information and lookback In development

Find everything held for one patient across live systems and archives in a single search.

OutcomeAnswer requests from one place instead of searching vendor by vendor.
Platform

One registry. Four layers of understanding.

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.

Layer 1

Discovery and registryFirst release

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.

  • applications
  • archives
  • file stores
  • cloud repositories
Layer 2

Application and storage intelligenceFirst release

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.

  • ownership
  • utilization
  • storage cost
  • return terms
  • renewals
Layer 3

Governance visibilityFirst release

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.

  • retention
  • legal hold
  • orphaned data
  • retirement candidates
Layer 4

Entity-level intelligenceIn development

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.

  • patient search
  • cross-archive
  • match confidence
Continuous, not one-time

An inventory is out of date the day it is finished.

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.

The estate keeps growing

New data every day, new applications every quarter, and new facilities with every acquisition. The registry updates as they arrive.

Retention runs on a clock

Records become eligible for disposition every day, and legal holds start and end. StrandFour tracks each one as it changes.

Requests never stop

Release of information and lookback requests arrive constantly. Patient-level search answers them in one place instead of across every archive.

Duplicates come back

Systems keep making new copies of studies and documents. Ongoing detection keeps a one-time cleanup from wearing off.

Contracts renew

Archive locations, data-return terms, and renewal dates change. The register stays current, so a vendor exit is never a surprise.

Acquisitions repeat

Every new facility is another consolidation project. The same registry catalogs it before migration begins.

Architecture

StrandFour indexes the estate. It does not become the estate.

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.

Your systems

  • EHRs, current and legacy
  • Imaging and PACS
  • Archive vendors
  • File stores
  • Cloud platforms
Remain authoritative and unchanged.

Approved connectors

  • Patient identifiers and file metadata
  • Scheduled and rate-limited
  • Monitored and resumable
Collected in the background, so searches never touch production.

StrandFour registry

  • Application profiles
  • Information catalog
  • Governance status
  • Patient-level index
Encrypted, access-controlled, and audited. Every search is logged.

PHI, handled as PHI

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.

No impact on care

Discovery is scheduled and rate-limited so clinical system performance is never affected.

You stay in control

No automated deletion and no actions on source systems. StrandFour identifies; your teams decide.

Why StrandFour exists

From systems of record to systems of operational understanding.

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

We are partnering with a small number of health systems.

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.

Ideal partner
Multi-hospital systems managing petabytes across many applications and archives, especially after acquisitions or EHR transitions
Starting point
Application registry across one region or facility
Access model
Read-only, approved by your security team
Outcome
A working map of your application and information estate