Security Risk Assessment Checklist for Online Hearing Aid Fitting Companies
Online hearing aid fitting involves patient information, remote consultations, connected devices, and cloud-based records. A documented security risk assessment helps you identify where electronic protected health information (ePHI) could be exposed, altered, lost, or made unavailable—and decide how to reduce those risks.
First, determine whether your company is a HIPAA covered entity, a business associate, or neither. Providing online hearing aid fittings alone does not establish HIPAA status; HIPAA obligations depend on the organization’s role and the services it performs. HHS guidance on covered entities and business associates explains which organizations are subject to the HIPAA Rules.
How to identify and document risks to electronic protected health information
Start by defining the systems, people, and business activities included in the assessment. Identify where ePHI is created, received, maintained, or transmitted, including during appointment scheduling, remote consultations, hearing evaluations, device adjustments, payment workflows, and follow-up support.
- Inventory information: List patient records, audiograms, fitting notes, device settings, session recordings or transcripts, and identifiable messages or files. Include contact or billing details when they are linked to health information and handled as ePHI.
- Map data flows: Record how information moves between patients, clinicians or fitters, practice systems, mobile devices, telehealth platforms, cloud storage, and vendors.
- Identify threats and vulnerabilities: Consider stolen or lost devices, phishing, weak passwords, misdirected messages, unauthorized viewing during a fitting, software weaknesses, accidental deletion, and service outages.
- Assess likelihood and impact: Evaluate how likely each threat is and how it could affect the confidentiality, integrity, and availability of ePHI.
- Document decisions: Record the systems reviewed, risks found, safeguards already in place, remaining risks, corrective actions, owners, and completion dates.
The HIPAA Security Rule calls for an accurate and thorough analysis of potential risks and vulnerabilities to ePHI. HHS describes risk analysis as considering both the likelihood of harm and its potential effect, and notes that the analysis must be documented. See HHS guidance on conducting a Security Rule risk analysis and HHS’s explanation of risk analysis and risk management.
Which access controls and device safeguards should you verify?
Check whether safeguards limit access to people and systems that need ePHI for their work. Use unique user accounts, assign permissions by role, promptly remove access when staff leave or change roles, and review privileged accounts regularly. Shared accounts make it harder to determine who accessed a record and should be avoided where individual accounts are feasible.
- Authentication: Verify identities before granting access. Consider multifactor authentication for remote access, administrator accounts, and other higher-risk systems. HIPAA requires a way to verify a person or entity seeking access; it does not prescribe multifactor authentication for every system.
- Audit controls: Confirm systems record relevant access and activity, and that someone reviews logs for suspicious patterns, such as unusual downloads or repeated failed logins.
- Endpoint safeguards: Check laptops, phones, tablets, fitting equipment, and home-office workstations for screen locks, supported software, malware protection, and secure configurations. Assess whether endpoint encryption is appropriate for devices that store ePHI.
- Physical and media security: Set rules for unattended workstations, equipment storage, removable media, secure disposal, and device return when employment or a contract ends.
- Integrity and availability: Protect records from unauthorized changes and confirm there is a tested way to restore essential information after loss or disruption.
Encryption is an addressable Security Rule implementation specification, not a blanket requirement that every organization use one identical method. If your assessment determines that encryption is reasonable and appropriate, implement it; if not, document the decision and any reasonable alternative safeguards. See HHS guidance on encryption under the Security Rule. The Rule’s technical safeguards also address access controls, audit controls, integrity, authentication, and transmission security; see HHS’s Security Rule technical safeguards guidance.
How can you protect privacy during telehealth hearing aid fittings?
Review the full fitting workflow—not just the video platform. Consider whether the service creates, stores, or transmits ePHI through video, audio, chat, uploaded audiograms, remote-control features, device measurements, recordings, or transcripts. Include these technologies and their settings in your risk analysis.
- Use a private room for staff consultations, and help patients reduce the chance that others can overhear or view the appointment.
- Verify the patient’s identity and confirm who else is present or authorized to participate before discussing health information.
- Choose communication tools and settings appropriate to the risks. Review access restrictions, encryption options, recording controls, retention settings, and account security.
- Disable recording and transcription unless there is a defined need. If used, explain the practice to patients, obtain any consent required by applicable law and policy, and secure the resulting files.
- Avoid displaying unnecessary patient details on shared screens, and use secure channels to send fitting instructions, records, or links.
HHS advises providers to use private settings where feasible and reasonable safeguards when a private setting is not possible. Its telehealth guidance also identifies risks from intercepted transmissions, stored recordings or transcripts, and devices or apps that lack authentication or automatic locking. See HHS guidance on remote communication technologies for telehealth and HHS guidance on private settings for telehealth.
What security policies and staff training are required?
If the HIPAA Security Rule applies to your organization, maintain written policies and procedures that reflect how your actual systems and services operate. Assign responsibility for security, set rules for granting and reviewing access, and explain how staff should report suspected incidents. Revisit policies when technology, staffing, vendors, or fitting workflows change.
Train workforce members on the policies and procedures relevant to their duties, including safe handling of fitting records, secure remote work, phishing, identity verification, and incident reporting. Keep records of training and policy updates. HIPAA requires security awareness and training for workforce members; training should be specific to your organization’s systems and risks, rather than treated as a generic certificate that proves the company is compliant.
Include contingency procedures for emergencies, such as restoring records and maintaining essential operations during a system outage. HHS summarizes the Security Rule’s administrative, physical, and technical safeguards and emphasizes that organizations must document and maintain required policies and records. See HHS’s overview of the HIPAA Security Rule.
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 AssessmentHow should you manage vendors, patient records, and backups?
List each vendor that may create, receive, maintain, or transmit ePHI, including telehealth and cloud providers, record systems, messaging services, remote device-support tools, and IT contractors. Determine the vendor’s role before sharing information: a vendor that handles ePHI on behalf of a covered entity or business associate may be a business associate or subcontractor, while not every vendor relationship automatically creates that status.
When a business associate relationship exists, use a written business associate agreement (BAA) before permitting the vendor to handle ePHI. Review whether the agreement limits uses and disclosures, requires appropriate safeguards and incident reporting, addresses subcontractors, and covers return or destruction of records when the relationship ends. HHS explains these requirements in its business associate guidance.
For records and backups, verify that access is restricted, retention and deletion follow applicable requirements and documented policy, and records can be restored when needed. Protect backup copies from unauthorized access or alteration, and test restoration rather than assuming that successful backup jobs guarantee recovery. HHS notes that cloud services can be used to handle ePHI when applicable HIPAA requirements are met, including appropriate business associate arrangements and risk management; see HHS guidance on cloud computing and HIPAA.
What steps should an incident response plan include?
Give staff a clear way to report a suspected incident immediately, including a lost device, misdirected fitting record, compromised account, unexpected access, or service outage. The incident response plan should identify who leads the response and who is responsible for technical containment, privacy and legal review, communications, and recovery.
- Contain the incident: Secure affected accounts or devices, restrict access where appropriate, and prevent further disclosure without destroying useful evidence.
- Preserve and investigate: Retain relevant logs and records, establish what happened, and identify the systems, information, and people potentially affected.
- Assess the information: Determine whether ePHI was involved, whether it was unsecured, and whether the event constitutes a reportable breach under the applicable rules.
- Notify the right parties: Follow internal escalation steps and contractual reporting duties. Covered entities and business associates have different breach-notification responsibilities; apply the rules relevant to your role and any stricter contractual deadlines.
- Recover and improve: Restore affected systems or data safely, mitigate harm, document decisions, and update safeguards or training to address the cause.
For a lost device, promptly disable its accounts or remote access, use remote locking or wiping if available and appropriate, and determine what information it could access or store. Check whether ePHI was encrypted using a method that meets HHS guidance and whether the encryption key or credentials may also have been compromised. Do not assume the loss is non-reportable without documenting the assessment.
The HIPAA Breach Notification Rule covers breaches of unsecured PHI. When notification is required, the applicable deadlines and recipients depend on whether the organization is a covered entity or business associate; a business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery, while the covered entity has its own notification duties. See HHS’s Breach Notification Rule guidance.
How often should you review and update the assessment?
Keep risk analysis ongoing, and update it when meaningful changes could affect ePHI. Triggers include adopting a new telehealth or fitting platform, adding a device or data connection, changing a vendor, expanding remote work, experiencing an incident, changing ownership, or identifying a new vulnerability.
HIPAA does not set one universal schedule for completing a risk analysis. HHS says the frequency depends on the organization and its environment; some organizations conduct a comprehensive assessment annually or at another interval and revisit risks as needed. Also conduct periodic technical and non-technical evaluations of whether safeguards and policies remain effective, and document the results and corrective actions. See HHS guidance on periodic review and updates to risk assessments.
In short, an effective assessment connects your patient-data flows to practical safeguards, accountable staff, vendor obligations, and tested incident and recovery procedures. Keep the documentation current so it reflects how your online hearing aid fitting service actually works.
FAQs
How often should an online hearing aid fitting company conduct a security risk assessment?
HIPAA does not prescribe a single fixed interval. If the Security Rule applies, keep the analysis ongoing, perform periodic evaluations, and revisit the assessment when changes or new risks warrant it. HHS notes that organizations may use different schedules depending on their circumstances.
What patient data must be included in the assessment?
Include ePHI your organization creates, receives, maintains, or transmits within the activities being assessed. For an online fitting service, that may include identifiable audiograms, fitting notes, device settings, consultation communications, recordings or transcripts, and related records handled as ePHI. Inventory the systems and vendors that process those records.
Do vendors handling protected health information need a business associate agreement?
A BAA is generally required when a vendor is a business associate handling PHI on behalf of a covered entity or business associate. Determine the vendor’s role and the nature of its access rather than assuming every supplier qualifies. HHS describes business associate relationships and contract requirements in its business associate guidance.
What should the company do if a device containing patient data is lost?
Report and investigate the loss promptly, disable access, and remotely lock or wipe the device when appropriate. Determine what data was on or accessible through it, whether it was encrypted, and whether credentials or encryption keys were exposed. Document the breach assessment and follow applicable notification procedures if required.
Table of Contents
- How to identify and document risks to electronic protected health information
- Which access controls and device safeguards should you verify?
- How can you protect privacy during telehealth hearing aid fittings?
- What security policies and staff training are required?
- How should you manage vendors, patient records, and backups?
- What steps should an incident response plan include?
- How often should you review and update the assessment?
-
FAQs
- How often should an online hearing aid fitting company conduct a security risk assessment?
- What patient data must be included in the assessment?
- Do vendors handling protected health information need a business associate agreement?
- What should the company do if a device containing patient data is lost?
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