Protecting Scanned Record Archives From Silent File Corruption

A former resident's family asks for a scanned discharge summary from several years ago. The records clerk finds the folder, double-clicks the file, and gets an error. The file is there, it has the right name and the right size on the screen, but it will not open. The paper original was shredded after scanning.

This is silent file corruption, and it is the quiet cousin of a dramatic failure. Nothing crashed and nothing alerted anyone. Over time, a file simply became unreadable, and nobody looked until the day it mattered.

How scanned archives degrade unnoticed

A scanned archive is a very large number of files that mostly sit untouched. That is exactly the condition under which problems hide. Common causes include:

Storage aging. Drives develop bad areas over time, and a file stored on one can be altered or lost without any visible error.

Interrupted copies and moves. A migration to a new server or a network drop in the middle of a transfer can leave truncated files.

Accidental moves and deletions. A folder dragged into another folder, or a cleanup of what looked like duplicates.

Backups that faithfully copy damage. If a file is corrupted and the backup runs nightly, the bad version eventually replaces the good one in the backup too.

Format drift. Files in an unusual or proprietary format may stop opening when software is updated or retired.

The central lesson is that "the file exists" is not the same as "the file works."

Two kinds of checks

Existence checks confirm that the number of files and folders matches what is expected. Compare counts against your scan batch logs or the previous month's total. A sudden drop is a sign that something was moved or deleted.

Integrity checks confirm that files are unchanged. Many storage systems and backup tools can compute a fingerprint for each file, often called a checksum or hash, and compare it later. If the fingerprint changes without anyone editing the file, something is wrong. Ask your IT provider whether your storage does this automatically.

Both matter. Counting catches missing files, and fingerprinting catches damaged ones.

A periodic routine

Pick a schedule and assign an owner, usually the medical records lead working with IT.

Monthly: compare the file count for the archive against last month, and investigate any unexplained change.

Quarterly: open a random sample of files, perhaps a few from each year, and confirm they are readable and complete. Vary the sample each time.

Each year: run a fuller integrity scan, or have IT report on file fingerprints across the archive.

After any move or migration: verify counts and open a sample before retiring the old location.

Log everything with dates and initials so you can show the process.

When a bad file turns up, restore it from an older backup copy, then ask why it happened so the cause can be fixed.

Keep more than one copy, in more than one place

A single copy on a single server is a risk no matter how well it is checked. A sound arrangement has:

The working archive on managed, backed-up storage.

A separate backup copy kept offsite or in the cloud.

Backups retained long enough that a problem discovered months later can still be reversed. Because corruption can be found late, short retention can leave you with only bad copies.

Ideally, a copy that cannot be altered for a set period, so one mistake cannot spread.

Ask whether your backups are tested by actually restoring scanned files, not just by the software reporting success.

Use sensible file formats

Standard, widely supported formats are easier to keep readable for years than unusual ones. Ask your IT provider and records lead what formats your scans use, whether text search is included, and what the plan is if your document software is replaced. Keeping an export of the archive in a common format is cheap insurance.

Keep the archive protected

Limit who can move or delete files in the archive, since most "corruption" incidents are really human ones. Read-only access for most staff, with changes restricted to a few people and logged, prevents many accidents. Remember that these files hold protected health information, so access controls and encryption apply as they do for any record system.

How we can help

UnityCare IT sets up managed storage and backups for scanned archives, runs periodic file-count and sample-open checks, and helps you keep separate copies that can be restored from before a problem started. We document the routine so your records lead can show it, and we respond when a file turns up damaged.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support