StorEasy WORM Appliance Enterprise Medical Datasheet
WORM appliance edition oriented to medical imaging retention. Compliance depends on configuration and applicable regulation.
- Vendor:
- StorEasy (INCOM)
- Date:
- Jun 2026
- Format:
- Size:
- 3.9 MB
Clinical imaging infrastructure
Aban Smart designs imaging archive tiers around what your scanners actually generate, so cache, capacity and retention are sized from modality data rather than a single average.
Study sizes vary enormously between installations. Every figure on this page is illustrative. We size from an export of your own PACS statistics.
Ask two hospitals how big an average study is and you will get two answers a factor of ten apart, because the answer depends entirely on the mix of scanners on site. A site with a busy CT and a digital pathology programme has a completely different capacity curve from an ultrasound-heavy maternity unit, even at identical study counts. So imaging archive design starts with the modality worksheet, not with a terabyte number, and everything downstream (cache size, tier boundaries, media choice, migration duration) follows from it.
Retention is long. Prior-study recall is measured in minutes.
The chain in most hospitals runs: modality, PACS, vendor-neutral archive, archive tier, then a write-once copy. Each hop has a distinct job and a distinct failure mode.
The common design error is collapsing the middle. Sites that archive directly from PACS to bulk storage end up with an archive whose catalogue lives inside the PACS database, which makes the next PACS replacement a data migration rather than an application swap.
Study size is driven by matrix size, slice count, bit depth and whether the modality produces cine or whole-slide data. The ranges below are illustrative planning figures, not measurements from any specific installation, and real sites vary widely.
| Modality (illustrative) | Typical study size | Objects per study | Character |
|---|---|---|---|
| Computed radiography / DX | 20 to 40 MB | 2 to 6 | High count, low volume |
| Ultrasound | 60 to 120 MB | tens to hundreds | Cine loops dominate |
| MR | 150 to 400 MB | hundreds | Many series per study |
| CT | 250 to 800 MB | hundreds to thousands | Thin slices multiply objects |
| Digital pathology (whole slide) | 1 to 4 GB | few, very large | Breaks size assumptions |
Now the worked example. Assume, purely as an illustration, a hospital running 120,000 imaging studies a year with this mix, and take a single planning size per modality from the middle of each range.
Annual total: 1.8 + 2.25 + 3.75 + 4.0 + 9.0 = 20.8 TB per year. Over ten years at flat volume that is 208 TB, and with a second protected copy, 416 TB of media.
Two things fall out of it. DX accounts for half the study count and under nine per cent of the volume, so any sizing model built on average study size badly misestimates both ends. And digital pathology, at 1.7 per cent of studies, contributes nearly a fifth of the annual footprint. A pathology programme that scales from 2,000 to 10,000 slides a year adds 16 TB annually on its own, which is close to doubling the whole archive's growth rate. That is a capacity decision that gets made in a clinical department, not in IT.
Retention is measured in years. Recall is measured in seconds. A radiologist reading a follow-up scan wants the comparison study on screen while the current one loads, and a retrieval that takes four minutes changes clinical behaviour: people stop asking for priors.
That tension is resolved with cache policy, not with a faster archive. Three patterns are common:
Prefetch is what makes an optical or tape archive tier clinically viable. Without it, deep-tier retrieval latency lands on the radiologist. With it, most of the day's priors are already on disk before anyone sits down. Oncology and orthopaedic follow-up pathways are the strongest candidates for it, because that recall pattern is genuinely predictable.
The reason to run a vendor-neutral archive is not storage efficiency. It is that PACS contracts end. A VNA holds studies in standard DICOM with its own index, so replacing the reading application does not require moving petabytes or renegotiating access to your own history.
It also handles the untidy reality of multi-site estates: differing accession number formats, duplicated patient identifiers between a hospital and a clinic it acquired, and modality worklists that were configured by different people years apart. Tag morphing at the VNA is where that gets normalised. Doing it at the archive tier instead means rewriting objects that should be immutable.
DICOM's value over decades is that it is documented, widely implemented and self-describing: the pixel data carries its own acquisition parameters. An archive holding DICOM objects with intact headers can be read by software that does not exist yet. An archive holding a proprietary compressed derivative usually cannot.
Underneath, the durable copy needs to resist alteration. INCOM StorEasy WORM appliances present as NAS over NFS or SMB while writing to optical WORM media in the background, with MD5 checksums maintained at file level and offline copies held separately from the online cache. Optical media in this class is ISO/UDF, which matters for the same reason DICOM matters: a platter readable by any conforming drive is not dependent on the appliance that wrote it. Vendor documentation differs on capacity ceilings between publications, so we size from a configuration quotation rather than from a brochure figure. The mechanisms are covered on immutable and WORM storage and WORM storage appliances.
For study handover to patients, Rimage RX400 MedX systems integrate as a DICOM destination and write to write-protected USB media rather than discs, with published retention figures of up to ten years for the higher-grade stick and up to three for the base one. Those are manufacturer figures for the media, not a statement about your archive.
Retention periods themselves are a legal question. A multi-year clinical imaging obligation, and paediatric records that may run considerably longer, must be set by your own advisers. We build the enforcement, not the policy.
Comparable long-retention estates are discussed under government records and research and AI workloads. Start at the industries overview, or request an assessment with a modality breakdown from your PACS.

Manufacturer documentation relevant to this page. Availability, specifications, and configurations are subject to verification.
WORM appliance edition oriented to medical imaging retention. Compliance depends on configuration and applicable regulation.
Optical media publishing system flyer for medical imaging distribution.
German-language brochure on medical archive media. Provided for reference; English confirmation recommended.
You can, and plenty of sites do. The cost appears at PACS replacement, when the archive index is inside the outgoing vendor's database and the migration becomes a data project with its own budget and risk. If a VNA is not affordable now, at least insist the archive keeps a catalogue that can be exported in full, independently of the PACS.
Share the workload, capacity, retention, access, and resilience requirements. Aban Smart will identify the next discovery inputs and the appropriate engagement path.