Legacy Record Systems Kept for Lookup: Securing Read-Only Archives

Your facility switched charting systems two years ago, but the old one is still running on a dusty computer in the business office. Staff use it a few times a month to look up an old medication record or a resident who was discharged long ago. It is read-only now, so nobody worries about it. That is the problem: nobody worries about it.

An old system that holds years of resident information deserves more attention than a system you use daily, because it often has fewer protections and fewer people watching.

Why old systems are a quiet risk

Systems kept for reference are commonly left unpatched, because the vendor stopped supporting them or no one wants to risk breaking something that still works. They may run on an operating system that no longer receives security updates. The accounts are often old, with shared logins from the era when everyone used one password.

Because "read-only" sounds harmless, it is easy to overlook that people can still read a great deal of protected information.

Who can still sign in

Start here, because it is the easiest and most useful step.

Get a list of every account on the old system.

Compare it to your current staff list.

Disable accounts for anyone who has left or no longer needs lookup.

Remove or rename shared and default accounts, and change their passwords.

Limit access to the few roles that truly need it, such as medical records and the administrator.

Keep a simple log of who looks up what when practical, or turn on the system's audit trail if it has one.

If the system cannot be managed this way, consider restricting who can reach the computer or server physically and over your network.

Reduce the system's reach

If the old system must stay on, keep it away from the rest of your network as much as possible.

Place it on a separate network segment, or allow connections only from the records computers that need it.

Do not let it browse the internet or receive email.

Turn off remote access unless it is required, and if it is, use a secure method rather than an open connection.

Remove unneeded software and external drives.

Your IT provider can set up these limits without changing the application itself.

Back it up and test it

The old system may hold the only copy of some records. Make sure it is backed up, that the backup is stored away from the machine, and that someone has tried a restore. Confirm the backup is also protected, since a backup of an old system carries the same information.

Also write down how the system works: where it runs, who supports it, license or vendor contacts, and how the data is stored. That information tends to disappear when the person who knew it leaves.

Decide how long it needs to live

Ask why you are keeping it. Common answers are retention requirements, occasional lookups and fear of losing something. Retention periods depend on law and your own policies, so confirm what applies with counsel, your state association or your insurer.

Then consider the options with your vendor and IT provider:

Exporting records to a protected, searchable format.

Having the vendor or a conversion service move the data into your current system or an archive.

Keeping the system, but in a minimal, locked-down form.

Whatever you choose, document it, test that the data can be read afterward, and keep the old system until you have confirmed that. When the time comes to retire the hardware, have drives wiped or destroyed with a record of the process.

Questions to bring to your vendor

Before you decide anything, ask the old system's vendor a few direct questions. Is the software still supported, and for how long? Can you export the data in a standard format, and does the export include notes, attachments and audit information? What happens to your data if the vendor stops operating? Is there a read-only or archive edition meant for exactly your situation? Written answers help your counsel and your IT provider make a sound plan, and they give you something to show a surveyor or insurer who asks how you handle old records.

How we can help

UnityCare IT can inventory your legacy systems, review who can sign in, isolate them on the network and verify that they are backed up. We can also help you plan a move to a protected archive when you are ready, working with your previous vendor and your counsel on retention questions.

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