Healthcare Asset Inventory: Protecting More Than EHR

For many small healthcare practices, the electronic health record is treated as the center of the technology environment, and understandably so. It holds critical patient information, supports clinical workflows, and is often the first system considered during a HIPAA discussion. Yet electronic protected health information can also be created, received, maintained, or transmitted by many other devices and services. Laptops, tablets, scanners, copiers, cloud portals, backup systems, phones, remote support tools, and network equipment may all be part of the risk picture. A security inventory that stops with the EHR is therefore likely to leave important questions unanswered.

That point has particular relevance after the HHS Office for Civil Rights issued its October 2026 cybersecurity newsletter. The agency again emphasized that regulated organizations should strengthen phishing defenses, authentication, patching, logging, encryption, incident response, and recovery planning in a manner appropriate to their environment. The guidance does not prescribe one standard technology stack for every practice. It does reinforce that the HIPAA Security Rule expects risks to electronic protected health information to be identified and managed, which begins with knowing where that information and the systems connected to it actually reside.

An inventory turns broad risk into practical decisions

An asset inventory should be designed to be useful in daily operations, not created only for a compliance folder. At a minimum, each entry should identify the device or service, its owner, its physical or cloud location, its primary user, whether it can access electronic protected health information, and how it is maintained. It should also identify systems that may not store patient data themselves but can reach systems that do, such as a network firewall, a remote administration platform, or an employee’s laptop. Those connections matter because an attacker does not need to begin inside the EHR if a less protected system can provide a path to it.

Small practices often discover overlooked assets during this process. A retired laptop may still be retained in a closet, a copier may retain scanned documents, a former employee may have access to a cloud application, or a vendor account may remain active after a project has ended. None of these examples automatically indicates a violation or an incident. They are simply the kinds of details that should be known before leadership can decide which safeguards are reasonable and appropriate. The HHS October 2026 newsletter provides a current, primary source reference for these foundational practices.

In our experience, the inventory works best when it is owned by both clinical and administrative leadership, with technical support available to document the details accurately. Staff understand which tools are actually used to communicate, scan, schedule, and serve patients. Technical teams can then connect those workflows to patching, account controls, encryption, backups, and monitoring. This approach produces a clearer result than asking either group to complete the review alone.

The inventory should be reviewed when the practice changes

An inventory is not a one time project. It should be updated when a practice adds a provider, changes an EHR module, brings on a billing company, replaces a copier, opens a new location, or adopts a new cloud service. Regular review makes it less likely that a change will quietly create an unmanaged account or an unsupported device. It also gives the practice a factual basis for the risk analysis discussed in our article on HIPAA risk analysis enforcement for small healthcare practices.

The inventory also supports recovery when something goes wrong. If ransomware, a failed workstation, or a service outage disrupts operations, the practice needs to know which systems are critical, who administers them, and whether a restoration can be tested. A list of assets becomes much more valuable when it is connected to tested backups and contingency procedures. Our guidance on disaster recovery testing explains why a backup should be verified before it is needed.

A complete inventory will not prevent every security problem, but it replaces uncertainty with an organized starting point. For a small healthcare practice, that clarity can make security investments more focused, incident response more manageable, and patient information better protected without imposing a large organization’s process on a small clinical team.