Medical imaging archive migration
Keep control of your medical imaging archive and your next move

Give the archive an exit plan
Give the archive an exit plan
A medical imaging archive can make a system change difficult long before the new platform is chosen. We assess migration into AWS HealthImaging and export into the receiving system, with reconciliation at both ends.
A medical imaging archive can make a system change difficult long before the new platform is chosen. We assess migration into AWS HealthImaging and export into the receiving system, with reconciliation at both ends.
Plan around the clinical record
Plan around the clinical record
We inventory the archive, review the required modalities and object types, and agree retention requirements with your clinical and information owners. The migration scope identifies source access, receiving-system requirements and acceptance measures.
We inventory the archive, review the required modalities and object types, and agree retention requirements with your clinical and information owners. The migration scope identifies source access, receiving-system requirements and acceptance measures.
Move and reconcile the archive
Move and reconcile the archive
Delivery covers the agreed DICOM objects, migration batches and reconciliation. Export produces DICOM Part 10 files with manifests, count and checksum checks, and a process for resuming after interruption.
Delivery covers the agreed DICOM objects, migration batches and reconciliation. Export produces DICOM Part 10 files with manifests, count and checksum checks, and a process for resuming after interruption.
Review retention with a provable process
Review retention with a provable process
Any retirement requires clinical and policy approval. The process records a ledger before deletion, completes a dry run with zero deletions, requires typed count-matching confirmation and tests restoration on real studies before removal. The audit trail contains no patient identifiers.
Any retirement requires clinical and policy approval. The process records a ledger before deletion, completes a dry run with zero deletions, requires typed count-matching confirmation and tests restoration on real studies before removal. The audit trail contains no patient identifiers.
Experience with large archives
Experience with large archives
We’ve delivered multiple archive migrations of 20 TB and above. A cardiology archive moved between two vendors’ systems included roughly 25,000 retained studies, more than 2,000 archive days and 131,492 reconciled files. Clinical retention review retired 58% of studies on a delivered archive. These are project results, not forecasts for your archive.
We’ve delivered multiple archive migrations of 20 TB and above. A cardiology archive moved between two vendors’ systems included roughly 25,000 retained studies, more than 2,000 archive days and 131,492 reconciled files. Clinical retention review retired 58% of studies on a delivered archive. These are project results, not forecasts for your archive.
Account for the full cost
Account for the full cost
The proposal sets out migration and optional operations costs. AWS HealthImaging, storage, retrieval and data transfer are billed separately by AWS. Incumbent vendor licensing remains your responsibility until the source is decommissioned.
The proposal sets out migration and optional operations costs. AWS HealthImaging, storage, retrieval and data transfer are billed separately by AWS. Incumbent vendor licensing remains your responsibility until the source is decommissioned.
Talk through your next step
Tell us what you need to achieve, the systems involved and the constraints your team needs to work within. We’ll discuss the fit and prepare a scoped proposal.
Pricing is agreed in a scoped proposal. AWS usage charges are separate from Easycoder’s engagement price.