Security Risk Assessment Guide for Wheelchair Seating and Mobility Providers
What is a security risk assessment for a wheelchair seating and mobility provider?
A security risk assessment is a structured review of how your organization creates, receives, maintains, and transmits electronic protected health information (ePHI), and what could threaten its confidentiality, integrity, or availability. It helps you identify weaknesses, estimate the risks they create, and decide how to reduce them.
If your organization is a HIPAA-covered entity or business associate, the HIPAA Security Rule requires a risk analysis. A health care provider is generally a covered entity if it transmits health information electronically in connection with a transaction for which HHS has adopted a standard; an organization may also have HIPAA obligations if it performs certain services for a covered entity as a business associate. Supplying wheelchairs or other durable medical equipment alone does not establish whether a provider is covered. Check your organization’s actual transactions and contractual relationships using HHS guidance on covered entities and business associates.
The assessment should reflect how your business operates—not just list computers or cybersecurity products. For example, consider how clinicians and technicians access seating evaluations, prescriptions, fitting notes, and follow-up records in clinics, patients’ homes, vehicles, and workshops. HHS describes risk analysis as assessing risks and vulnerabilities to ePHI, their likelihood, and their potential impact; the Security Rule does not prescribe one assessment format. See HHS guidance on risk analysis and the current Security Rule at 45 CFR § 164.308.
Keep the distinction between law and proposals clear: HHS has published a proposed update to the HIPAA Security Rule, but says the current Security Rule remains in effect while rulemaking proceeds. See the HHS HIPAA Security Rule NPRM page.
Which patient, business, and technology assets should be assessed?
Start with an inventory of where ePHI and other sensitive information reside, how staff use it, and which vendors or systems can access it. Include information in digital and paper workflows, and document the connections among people, facilities, devices, applications, and service providers.
- Patient and clinical information: referrals, prescriptions, insurance and billing details, contact information, seating evaluations, measurements, photographs or videos, mobility and functional assessments, fitting records, repair histories, and communications with patients or caregivers.
- Business information and operations: employee and payroll records, supplier and payer contracts, purchasing and inventory data, accounts, appointment schedules, and operational records needed to provide or coordinate care and equipment.
- Devices and applications: electronic health record or practice-management systems, billing and claims tools, scheduling software, email, file-sharing services, mobile phones, tablets, laptops, workstations, printers, servers, and removable storage.
- Clinical and mobility-related technology: any connected equipment, configuration or programming tools, remote-support applications, or vendor portals used in your workflow. Include these only where your organization uses them or they connect to systems holding sensitive information.
- Facilities and service providers: clinics, workshops, storage areas, vehicles used to transport devices or records, cloud-hosted services, IT support, billing services, and other vendors that create, receive, maintain, or transmit ePHI.
For each asset, note its owner, purpose, data handled, users, location, dependencies, backup arrangements, and relevant vendor or business associate agreement. HHS recommends taking an inventory of systems and applications used to access or house ePHI and assessing the safeguards in place. See HHS risk analysis guidance.
How can providers identify and prioritize security threats?
Use a repeatable threat and vulnerability assessment: identify what could go wrong, find weaknesses that could make it possible, and consider the likely effect on patients and operations. Threats may include phishing, ransomware, stolen or lost devices, accidental disclosure, inappropriate staff access, weak passwords, software failures, power loss, fire, and vendor outages. Relevant vulnerabilities may include shared accounts, unpatched devices, excessive access, insecure remote connections, missing backups, or unclear procedures for handling records outside the clinic.
Assess each threat-and-vulnerability combination by considering both its likelihood and its impact. For a wheelchair seating and mobility provider, impacts may include exposure of patient information, loss or alteration of clinical records, delayed fittings or repairs, interrupted billing, or inability to retrieve the information needed to continue operations. Rank the resulting risks so you can address the most serious ones first, and record the rationale, planned safeguards, responsible owner, and target date.
HIPAA requires covered entities and business associates to conduct and document risk analysis, but it does not mandate a particular scoring formula or a single assessment template. HHS recommends assigning risk levels and documenting corrective actions. See HHS guidance on identifying and prioritizing risk and 45 CFR § 164.316 on Security Rule policies, procedures, and documentation.
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 safeguards protect patient information and clinical systems?
Select safeguards based on the risks you identified, your organization’s size and capabilities, and the systems and information involved. The HIPAA Security Rule calls for administrative, physical, and technical safeguards; it does not make one tool or product a complete compliance solution. Document why selected measures are appropriate and how you will check that they work.
- Access control: Give each workforce member an individual account and access suited to their job. Remove or adjust access promptly when responsibilities change or someone leaves. Avoid shared credentials, and use stronger authentication for remote or administrative access where appropriate.
- Audit controls: Enable and review available system logs to help identify unusual access, failed sign-ins, or changes to records. Define who reviews alerts, how concerns are escalated, and how long relevant logs are retained.
- Device and facility security: Protect laptops and mobile devices used during visits, fittings, repairs, or travel. Use screen locks, secure storage, and procedures for lost devices; restrict access to rooms or equipment that can expose records.
- Data protection: Use secure methods to transmit information, maintain safeguards against unauthorized changes, and evaluate encryption for devices and communications that contain ePHI. Address paper records as well as electronic files.
- Staff awareness and vendor oversight: Train staff on your organization’s security policies, phishing, safe device use, and incident reporting. Review vendor access and agreements; when a vendor is a business associate, HIPAA generally requires appropriate written assurances through a business associate agreement.
- Contingency planning: Maintain retrievable backups and procedures to restore information and continue essential operations during emergencies or system outages. Consider how staff will access necessary records and coordinate patient care if a primary system is unavailable.
The Security Rule includes standards for access control, audit controls, incident response, and contingency planning. Review the applicable requirements in 45 CFR § 164.308 and 45 CFR § 164.312. The rule’s implementation specifications distinguish required from addressable specifications; “addressable” does not mean ignore it—evaluate whether it is reasonable and appropriate for your organization and document your decision and any equivalent measure.
How should providers respond to a security incident?
Use a written response process that tells staff how to report a suspected incident immediately and identifies who will assess and coordinate the response. A security incident can involve an attempted or successful unauthorized access, use, disclosure, modification, or destruction of information, or interference with system operations.
- Report and assess: Record when and how the incident was discovered, the systems and information involved, and who may be affected. Notify the designated internal lead and follow the applicable vendor or business associate reporting process.
- Contain and preserve: Limit further exposure or disruption while preserving relevant records, logs, devices, and communications. Coordinate with IT support or other responders; avoid actions that could destroy evidence.
- Mitigate and restore: Address the cause, reduce harm where practicable, and restore systems or information using your contingency procedures. Document decisions, actions, outcomes, and any follow-up safeguards.
- Evaluate notification duties: A security incident is not automatically a reportable breach. If unsecured protected health information may have been involved, assess the facts under the Breach Notification Rule and promptly involve the people responsible for privacy and legal decisions. Covered entities must provide required notices without unreasonable delay and no later than 60 days after discovery of a breach; business associates must notify the covered entity under the applicable rule and agreement. See HHS breach notification guidance.
HIPAA requires regulated entities to identify and respond to suspected or known security incidents, mitigate harmful effects to the extent practicable, and document incidents and their outcomes. See 45 CFR § 164.308(a)(6). Keep the response plan practical: assign roles, maintain current contact details for key vendors, and make sure staff know how to report an issue even when usual systems are down.
How often should the assessment be reviewed and updated?
The HIPAA Security Rule does not set a universal annual schedule for risk analysis. HHS says frequency varies by organization and describes risk analysis as an ongoing process. Review the assessment when meaningful changes could affect ePHI—for example, after a security incident, a change in ownership or key staff, a new technology or vendor, a workflow change, or a move to a new facility. See HHS guidance on ongoing risk analysis.
Set a review cadence that fits your operations, then update it sooner when changes or incidents warrant. Track open risks, completed safeguards, owners, and deadlines so the assessment leads to action rather than becoming a static document. HIPAA requires documentation of Security Rule activities and periodic review and updates to documentation in response to relevant environmental or organizational changes; see 45 CFR § 164.316.
In short, identify the information and systems your wheelchair seating and mobility services depend on, assess realistic threats and weaknesses, implement and document suitable safeguards, and revise the assessment as your organization changes. A regular, risk-based process helps protect patient information while supporting continuity of clinical and business operations.
FAQs
Is a security risk assessment required for wheelchair seating and mobility providers?
It is required under the HIPAA Security Rule for covered entities and business associates. A health care provider is generally a covered entity if it conducts certain standard transactions electronically; a business associate may also have Security Rule obligations when it handles ePHI on behalf of a covered entity. Whether a particular wheelchair seating and mobility provider meets either definition depends on its activities and relationships, not simply the equipment it supplies. See HHS guidance on covered entities and 45 CFR § 164.308.
Which systems and records should the assessment cover?
Include all relevant systems and records that create, receive, maintain, or transmit ePHI, along with the people, devices, facilities, vendors, and workflows that can access them. For a mobility provider, that may include clinical evaluations, prescriptions, fitting and repair records, billing and scheduling systems, staff devices, email, cloud services, and any connected tools used in service delivery.
How often should providers update their security risk assessment?
HIPAA does not prescribe one universal annual interval. Review it on a schedule appropriate to your organization and update it when incidents, technology, vendors, staffing, ownership, facilities, or workflows create new risks. Keep the assessment and related documentation current and track corrective actions.
What should a provider do after discovering a security incident?
Report it promptly through your response process, assess what information and systems may be affected, contain the incident, preserve relevant evidence, mitigate harm, and document the outcome. Then determine whether the facts trigger breach notification duties. If a business associate is involved, follow the reporting terms in the applicable agreement and notify the covered entity as required. See HHS breach notification guidance.
Table of Contents
- What is a security risk assessment for a wheelchair seating and mobility provider?
- Which patient, business, and technology assets should be assessed?
- How can providers identify and prioritize security threats?
- What safeguards protect patient information and clinical systems?
- How should providers respond to a security incident?
- How often should the assessment be reviewed and updated?
- FAQs
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