Hospital RTLS Asset Tracking Vendor Security Risk Assessment Guide
Real-time location systems (RTLS) help hospitals locate equipment, but their tags, readers, network connections, software, and vendor services can introduce security risks. Use this guide to assess how an RTLS vendor handles data, protects connected devices, and responds to incidents before deployment.
What security risks should hospitals assess in RTLS vendors?
Start by mapping the system’s components and the information they handle. A typical deployment may include asset tags, readers or anchors, gateways, management software, cloud services, mobile applications, and interfaces with hospital systems. Identify who operates each component, where data is processed, and which subcontractors can access it.
Assess risks to confidentiality, integrity, and availability. Examples include unauthorized access to the management console, exposed credentials, altered location records, device tampering, ransomware affecting the vendor’s service, and outages that prevent staff from finding critical equipment. Consider whether the system connects to clinical or enterprise networks and whether a compromise could enable access to other systems.
Determine whether RTLS data is or could become protected health information (PHI). An asset identifier and location may not, by themselves, identify a patient. However, data that links equipment or location to an identifiable patient, treatment, or care episode may involve PHI. If the vendor creates, receives, maintains, or transmits PHI on the hospital’s behalf, assess whether it is a business associate and whether a HIPAA business associate agreement (BAA) is required. HHS describes the Security Rule’s risk analysis as an assessment of risks and vulnerabilities to ePHI; include the RTLS components and relevant data flows in the hospital’s assessment. HHS risk analysis guidance HHS business associate guidance
How does RTLS collect, transmit, and store asset data?
Ask the vendor to diagram the full data lifecycle: what each tag broadcasts, what readers capture, what gateways forward, how the application processes events, and where records and backups are stored. Confirm whether the system collects only asset identifiers and location or also includes user accounts, patient identifiers, room assignments, timestamps, equipment status, or integration data.
Trace data across each connection, including wireless links, internal networks, application programming interfaces (APIs), remote support sessions, cloud hosting, analytics, and subcontractor services. Ask which party controls each stage, which geographic regions are used for processing and backup, how long data is retained, and how it is securely deleted when no longer needed or when the contract ends.
Request documentation of the device’s expected network behavior, such as required destinations, protocols, ports, and communications initiated by the vendor. Compare that information with observed traffic during testing. NIST notes that understanding and documenting IoT device network behavior is important to cybersecurity; use the vendor’s data-flow and network diagrams to support this review. NIST guidance on IoT device network behavior
Which access controls and authentication safeguards should vendors provide?
Check whether the platform supports unique user accounts, least-privilege permissions, and role-based access control (RBAC) that lets the hospital limit access by job function, location, or administrative responsibility. Ask how privileged accounts are controlled, reviewed, and removed when an employee or vendor technician no longer needs access.
Ask whether the system supports multifactor authentication (MFA), especially for administrators, remote access, and vendor support. MFA is a prudent safeguard to evaluate, but do not present it as a specific, universally stated HIPAA Security Rule requirement. Also review password and session controls, single sign-on options, emergency access, and whether service accounts and device identities can be individually identified and managed.
Request a demonstration of audit logs showing who accessed the system, what actions they took, and when. Find out whether logs capture changes to permissions, configuration, asset records, and integrations; how long logs are retained; and whether the hospital can export them to its security monitoring tools. The HIPAA Security Rule includes access control, audit controls, and person or entity authentication standards for systems containing ePHI. 45 CFR § 164.312, Technical safeguards
How should hospitals assess encryption, network security, and device security?
Ask how the vendor protects data in transit between tags, readers, gateways, applications, and cloud services, and how it protects stored data in databases, backups, logs, and portable media. Request details about encryption coverage, key management, key access, and how keys are rotated or revoked. Verify the protections for vendor support and administrative connections, not only the main application.
HIPAA’s technical safeguards require transmission security and include addressable encryption specifications for ePHI at rest and in transit. “Addressable” does not simply mean optional: the regulated entity must determine whether the specification is reasonable and appropriate, implement it or an appropriate alternative, and document its decision. Hospitals should therefore evaluate encryption against their risk analysis and not treat a vendor’s general claim of “HIPAA compliant” as proof of specific safeguards. 45 CFR § 164.312 HHS explanation of addressable specifications
For network security, determine whether RTLS traffic can be restricted to approved destinations and isolated from unrelated clinical systems. Ask about secure configuration, exposed services, remote-access protections, and whether the hospital can segment the system into a dedicated network zone. Test integrations and firewall rules before production use.
For connected devices, ask how they are authenticated, physically secured, inventoried, updated, and retired. Review the vendor’s vulnerability management process, including how it receives vulnerability reports, evaluates severity, issues patches, communicates known risks, and supports devices that cannot be patched promptly. NIST’s IoT device guidance recommends defining device cybersecurity requirements for the organization’s intended use; hospitals can use that approach to assess whether RTLS devices are securable in their environment. NIST SP 800-213
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk AssessmentWhat evidence should hospitals request during vendor due diligence?
As part of vendor due diligence, request evidence that addresses the system and deployment being evaluated, not just general marketing materials. Useful items include a current architecture and data-flow diagram, security policies, a summary of the latest risk assessment, penetration-test results or an executive summary, vulnerability management and patching procedures, access-control details, and incident response documentation.
Where available, ask for independent assessment reports, such as a SOC 2 report, along with its review period, scope, exceptions, and any complementary customer controls the hospital must implement. These documents can inform due diligence, but they do not by themselves establish HIPAA compliance or guarantee that the hospital’s specific deployment is secure.
For a vendor acting as a business associate, review the BAA and identify its permitted uses of PHI, safeguard commitments, subcontractor obligations, incident reporting terms, and requirements for returning or destroying PHI at contract end. HHS identifies these as core areas for business associate contracts. HIPAA does not expressly require a cloud service provider to give customers its security documentation or permit customer audits, so negotiate access to appropriate evidence and audit rights where they are important to the hospital’s risk management. HHS sample BAA provisions HHS cloud computing guidance
How should hospitals review incident response and breach notification practices?
Ask the vendor to explain how it detects, investigates, contains, and recovers from security incidents. Review how it preserves relevant logs, identifies affected systems and data, coordinates with subcontractors, and supports the hospital’s investigation. Confirm that the vendor has tested its response plan and can provide a designated contact available for urgent incidents.
Set clear contract terms for notifying the hospital of suspected or confirmed incidents, including the reporting channel, required initial details, follow-up updates, and cooperation with investigations. Distinguish a general security incident from a breach of unsecured PHI: the BAA should address security incidents, while breach notification duties apply under the Breach Notification Rule when the relevant legal conditions are met.
HIPAA requires a business associate to notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery. That is an outside federal deadline, not necessarily an appropriate operational target for a hospital. Negotiate a shorter contractual notification period so the hospital has time to assess impact and meet its own obligations. HHS Breach Notification Rule guidance HHS sample BAA provisions
What security limitations should hospitals consider before deployment?
Identify limitations that could weaken safeguards or disrupt operations: devices with limited logging or update support, wireless coverage gaps, dependence on a single cloud service, restricted access to vendor security evidence, unsupported integrations, or reliance on shared accounts. Confirm what happens when a tag, reader, network link, or vendor service is unavailable, and whether staff have a safe fallback process for locating critical equipment.
Document which risks the vendor cannot mitigate and what compensating controls the hospital will use, such as network segmentation, additional monitoring, restricted remote access, or reduced data collection. Pilot the system in a controlled environment, validate expected network traffic, and include RTLS components in ongoing asset inventory, vulnerability management, and security reviews.
Summary: A sound RTLS vendor assessment follows the data, verifies access and device safeguards, reviews evidence and incident terms, and records deployment-specific risks. Confirm whether PHI is involved, use a BAA when required, and plan hospital controls for any vendor limitations.
FAQs
Does an RTLS asset tracking system handle protected health information?
Not necessarily. A system that tracks equipment without identifying patients may not handle PHI. If its records link equipment or location to an identifiable patient or care episode, or the vendor otherwise handles PHI on the hospital’s behalf, assess the data and vendor relationship under HIPAA and determine whether a BAA is required.
What security documents should a hospital request from an RTLS vendor?
Request a system architecture and data-flow diagram, security and vulnerability management policies, available independent assessment reports, penetration-test summaries, incident response procedures, access-control and encryption details, and subcontractor information. Review the BAA if the vendor is a business associate. HIPAA does not automatically require a vendor to provide every security document or allow customer audits, so agree on appropriate evidence and access in the contract.
How should hospitals assess RTLS devices connected to clinical networks?
Inventory the devices and map their expected network communications. Confirm how devices authenticate, receive updates, report logs, and handle vulnerabilities; test actual traffic against vendor documentation; and restrict communications to what the system needs. Consider network segmentation and monitor the devices within the hospital’s security program.
What should an RTLS vendor’s breach notification process include?
It should specify whom the vendor contacts, how and when it reports an incident, what initial facts it provides, how it sends updates, and how it preserves evidence and assists the hospital. If the vendor is a business associate and a breach of unsecured PHI occurs, HIPAA requires notice without unreasonable delay and no later than 60 calendar days after discovery; hospitals can negotiate a shorter contractual deadline.
Sources
- What is the difference between Risk Analysis and Risk Management in the Security Rule? | HHS.gov
- Business Associates Frequently Asked Questions (FAQs) | HHS.gov
- IoT Device Network Behavior: NIST IR 8349 | CSRC
- What is the difference between addressable and required implementation specifications in the Security Rule? | HHS.gov
- SP 800-213, IoT Device Cybersecurity Guidance for the Federal Government: Establishing IoT Device Cybersecurity Requirements | CSRC
- Business Associate Contracts | HHS.gov
- Guidance on HIPAA & Cloud Computing | HHS.gov
- Breach Notification Rule | HHS.gov
Table of Contents
- What security risks should hospitals assess in RTLS vendors?
- How does RTLS collect, transmit, and store asset data?
- Which access controls and authentication safeguards should vendors provide?
- How should hospitals assess encryption, network security, and device security?
- What evidence should hospitals request during vendor due diligence?
- How should hospitals review incident response and breach notification practices?
- What security limitations should hospitals consider before deployment?
- FAQs
- Sources
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk Assessment