ITIL 4 ITAM study materials
ITIL 4 ITAM study resources

MRI refresh and safe disposal at St. Alden's Hospital

ITIL 4 ITAM · Put your knowledge to work in context.

All case studies

MRI refresh and safe disposal at St. Alden's Hospital

St. Alden's Hospital plans to replace a 7-year-old MRI scanner and 220 associated imaging devices. The vendor offers a 5-year lease at £1.9 million including maintenance and a mid-term refresh, or outright purchase at £1.6 million plus £240,000 annual maintenance. The current MRI loses vendor support in 14 months. Patient data remains on device disks until decommissioning, and the trust must retain imaging records for eight years under health records policy. A disposal broker has offered £90,000 for the old units but cannot provide a data sanitization certificate, only a collection note. The capital budget is fully committed this year, while the operating budget has limited headroom. Clinical engineering wants no scanner downtime; finance wants the lowest five-year cost; information security wants documented data destruction. The trust has no standard retirement checklist and the asset register shows the MRI as 'in use' despite a failed detector.

1. Evaluate the lease versus purchase decision using lifecycle cost and risk, and state the conditions under which you would recommend each option.

Read the worked answer

Compare total cost of ownership over the clinical and support life, not just acquisition. Purchase is £1.6 million plus five years of maintenance at £240,000, about £2.8 million before migration, downtime, and disposal; support also ends in 14 months, creating clinical risk. Lease is £1.9 million including maintenance and refresh, with lower capital impact, but the team must check exit costs, end-of-term obligations, data sanitization at return, and whether the refresh meets clinical requirements. Five-year cash cost may favor lease, but the decision must include downtime cost, migration effort, residual value, and risk. Recommend lease only if maintenance scope is defined, refresh meets clinical needs, sanitization at end of term is contracted, and exit costs are capped. Otherwise purchase with a funded replacement reserve. The asset manager should model scenarios and record the assumptions used.

2. Define the retirement and disposal workflow for the old MRI and imaging devices, including the evidence required before the asset record changes.

Read the worked answer

The workflow should be: confirm clinical decommissioning and data-retention obligations; export required images to the records system; remove the device from operational service and update CI status; sanitize media to an agreed standard with a certificate listing serials and method; remove or wipe storage from devices; dispose through an approved vendor with chain of custody; capture residual value or recycling; and only then change asset status to retired or disposed. The broker's £90,000 offer is unacceptable without a sanitization certificate. A collection note is not evidence of data destruction. The asset record must not be closed merely because the equipment left the building; closure requires documented sanitization and disposal. The register already says 'in use' despite a failed detector, which shows status is not maintained, so reconcile status before disposal.

3. What acquisition and operational data should be captured for the new MRI to avoid repeating the failed-detector problem?

Read the worked answer

Capture a unique asset identifier, manufacturer serial number, model, location, asset owner, custodian, purchase and contract details, warranty, maintenance provider, support end date, data-bearing components, security classification, and service relationships. At operation, integrate clinical-engineering work orders and change records so detector failures, firmware changes, and maintenance events update the asset and CI status. The asset owner needs the support end date and risk status; clinical engineering needs maintenance history; security needs data-bearing component details. This data allows the organization to see lifecycle risk before support expires and prevents a failed component being hidden behind a stale 'in use' status.