Clear Aligner Teledentistry Company Security Risk Assessment Guide

Kevin Henry

Risk Management

Published Updated

10 minutes read
Share this article
Clear Aligner Teledentistry Company Security Risk Assessment Guide

A security risk assessment helps a clear aligner teledentistry company identify where patient information is handled, what could go wrong, and which safeguards are appropriate. If your organization is subject to the HIPAA Security Rule as a covered entity or business associate, it must conduct and document an accurate and thorough HIPAA Security Rule risk analysis of the electronic protected health information (ePHI) it creates, receives, maintains, or transmits. See HHS guidance on risk analysis.

Which ePHI and information systems must the assessment cover?

Start by defining the assessment’s scope. Include all ePHI your organization creates, receives, maintains, or transmits—not just information in the electronic health record. HIPAA’s security analysis covers the information and the systems, devices, and media used to handle it, wherever they are located. HHS risk analysis guidance explains that the scope includes ePHI in all electronic forms and on all relevant media.

For a clear aligner service, inventory patient information such as names and contact details linked to care, dental and medical histories, treatment plans, digital scans, X-rays, intraoral and facial photos, progress videos, clinician notes, prescriptions or recommendations, appointment and billing records, and patient messages. Include information used to assess eligibility, plan tooth movement, monitor treatment, or make clinical decisions. Identifiable health or treatment information may be protected health information; assess photos and other files in context rather than assuming they are anonymous.

Map the systems that touch this information: patient portals and mobile apps, telehealth and messaging platforms, imaging and treatment-planning software, scheduling and billing tools, email, cloud storage, backups, staff workstations and mobile devices, and any interfaces between these systems. Include paper records and physical access in the broader security program, even though the Security Rule’s risk analysis focuses on ePHI. The Rule requires appropriate administrative, physical, and technical safeguards; see HHS’s summary of the Security Rule.

How should you map patient data flows and vendors?

Trace each kind of patient information from collection through use, sharing, storage, retention, and deletion. For example, document how a patient submits dental photos, how staff review them, where a clinician’s treatment notes are saved, whether images pass to an aligner-planning platform, and how the final plan returns to the patient or treating provider. Record the systems involved, who can access the information, where it is stored, and how it moves between them.

List vendors and subcontractors that may create, receive, maintain, or transmit ePHI on your organization’s behalf. Depending on the service and relationship, they may be business associates or subcontractors. Review each vendor’s role, access, security practices, incident-notification process, data retention and deletion terms, and relevant contract terms. A business associate agreement (BAA) is generally required when a vendor performs covered functions or services involving PHI on behalf of a covered entity or business associate. HHS guidance on cloud services and ePHI explains the BAA requirement and the customer’s continuing responsibility to assess risk.

Do not assume a service is outside the assessment simply because data is encrypted or the vendor cannot read it. HHS explains that a cloud provider maintaining ePHI may be a business associate even if it cannot decrypt the information. Check the actual service, access arrangements, and contractual relationship; see HHS guidance on HIPAA and cloud computing.

Which threats and vulnerabilities should you evaluate?

Identify reasonably anticipated threats and vulnerabilities for each relevant system and data flow. Consider unauthorized account access, phishing, stolen or lost devices, misdirected messages, insecure file sharing, excessive staff permissions, exposed backups, software flaws, vendor incidents, ransomware, service outages, and accidental deletion or alteration. Include risks from poor configuration, weak authentication, unpatched systems, and unclear procedures for handling patient images or recordings.

Assess how each threat could affect the confidentiality, integrity and availability (CIA) of ePHI. Confidentiality concerns unauthorized viewing or disclosure; integrity concerns improper alteration or destruction; availability concerns whether authorized users can access information when needed. The Security Rule’s risk analysis guidance calls for identifying and documenting threats and vulnerabilities, evaluating current security measures, and considering potential effects on all three CIA objectives. See HHS’s risk analysis elements.

Make the threat review specific to the service. For example, assess whether a staff member could send a photo to the wrong patient, whether a patient portal exposes treatment details after an account takeover, whether a compromised planning platform could alter a treatment plan, and how clinicians would access necessary records during a platform outage.

How do you assess likelihood, impact, and risk levels?

For each threat-and-vulnerability pair, estimate how likely it is to occur and how serious its consequences could be. Use a consistent qualitative scale, such as low, moderate, and high, or a documented quantitative method. Consider existing safeguards, the volume and sensitivity of information, the number of people or systems exposed, the ease of exploitation, and potential effects on patient care and business operations.

Combine likelihood and impact into a risk level, then document the reasoning. A simple matrix can help prioritize risks, but the method itself is not a substitute for a thorough analysis. HHS does not prescribe one risk-scoring method or format; its guidance recommends documenting risk levels and corrective actions and considering both probability and potential impact. See HHS guidance on likelihood, impact, and risk levels.

For each risk, record existing controls, remaining risk, the planned response, the person responsible, and a target date. Prioritize issues that could expose many patients, disrupt clinical access, or undermine treatment records. Reassess after safeguards are in place to determine whether they reduced the risk as intended.

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

What administrative, technical, and device safeguards should you implement?

Choose safeguards that address the risks you identified and fit your organization’s environment. The Security Rule requires administrative, physical, and technical safeguards; its standards are flexible, but decisions about reasonable and appropriate measures should be grounded in your risk analysis. HHS’s Security Rule overview describes these safeguard categories.

  • Administrative safeguards: Assign security responsibilities; maintain written policies; train workforce members on your organization’s procedures; limit access according to job responsibilities; review user access; and establish vendor oversight, contingency planning, and security incident response procedures.
  • Technical safeguards: Use unique user accounts, appropriate authentication, role-based access, audit logs, and secure transmission methods. Consider encryption, multifactor authentication, session timeouts, and alerts based on the risks identified. The technical standards include access control, audit controls, integrity, person or entity authentication, and transmission security; see 45 CFR § 164.312.
  • Device and physical safeguards: Protect workstations and mobile devices with screen locks, supported software, device encryption where appropriate, and procedures for lost or stolen equipment. Control physical access to work areas and secure removable media. Set rules for local downloads of patient photos, videos, scans, and records, including approved storage locations and secure deletion.

Encryption and other implementation specifications must be assessed under the applicable Security Rule requirements; do not treat a checklist as a substitute for deciding what is reasonable and appropriate for your environment. Document your decisions and any alternative measures. For systems that contain ePHI, build in backups and recovery procedures so authorized staff can regain access if data is lost or a system is unavailable.

Maintain a written security incident response process. It should explain how staff report suspected incidents, who investigates and contains them, how harm is mitigated, what records are kept, and how the organization coordinates with vendors. The Security Rule requires regulated entities to identify and respond to suspected or known security incidents, mitigate harmful effects where practicable, and document incidents and outcomes. See HHS guidance on security incident procedures and business associates.

How can you protect privacy during telehealth sessions?

Use a telehealth workflow that limits access to intended participants and protects information while it is being shared. Verify the patient and clinician as appropriate, use individual accounts and access controls, and avoid public-facing tools for individualized consultations. Select platforms and configurations based on your risk analysis, privacy obligations, and vendor relationship; do not assume that a product’s marketing label alone establishes compliance.

Set clear rules for screen sharing, recording, screenshots, and session links. Restrict recordings to an approved purpose, limit who can access them, and define where they are stored and when they are deleted. If staff review photos or scans during a session, prevent unrelated people from viewing the screen and avoid saving files to unmanaged devices or consumer accounts.

Give patients practical privacy guidance, such as choosing a private place, using headphones when needed, avoiding public networks where possible, and keeping their device software updated. HHS also recommends steps such as using strong passwords, screen locks, and available multifactor authentication. See HHS telehealth privacy and security tips.

When should you document and update the assessment?

Document the assessment as you conduct it. Keep the scope, ePHI inventory, system and data-flow maps, vendor list, identified threats and vulnerabilities, current safeguards, likelihood and impact ratings, risk decisions, and remediation plan. The Security Rule requires documentation but does not prescribe a specific format. Required documentation must generally be retained for six years from its creation or the date it was last in effect, whichever is later. See 45 CFR § 164.316.

Keep the analysis ongoing rather than treating it as a one-time exercise. Review it when you introduce a new app, vendor, device, data-sharing route, or clinical service; after a security incident; when system access or workflows change; and when you identify a new threat or weakness. HHS says organizations should conduct continuous risk analysis to identify when updates to safeguards are needed, rather than relying on a universal fixed schedule. See HHS guidance on periodic review and updates.

A documented, current assessment connects your patient-data inventory to practical safeguards, vendor oversight, and incident response. Use it to prioritize improvements and revisit decisions as your clear aligner teledentistry workflows change.

FAQs

Does a clear aligner teledentistry company need a documented ePHI risk analysis?

If the company is a HIPAA covered entity or business associate, yes: the Security Rule requires a documented risk analysis of the ePHI it creates, receives, maintains, or transmits. A company’s legal role depends on its activities and relationships; for example, a provider may be a covered entity if it meets HIPAA’s definition, while a service provider handling ePHI on behalf of a covered entity may be a business associate. See HHS risk analysis guidance and HHS guidance on business associates.

Which patient photos, videos, messages, and records should be included?

Include all electronic information that identifies a patient, or could reasonably identify them, and relates to their health, care, or payment when handled by a covered entity or business associate. For clear aligner care, that can include facial and intraoral photos, progress videos, dental scans, treatment plans, clinician notes, messages, appointment details, and billing records. Include the systems and devices used to collect, view, transmit, store, back up, or delete them. HHS’s risk analysis guidance applies to all ePHI, regardless of its source or location.

How often should a teledentistry security risk assessment be updated?

HIPAA does not set one universal annual schedule for updating the risk analysis. Keep the process ongoing and review the assessment when changes, incidents, or newly recognized risks may affect ePHI or its safeguards. Document updates and the reasons for your decisions. See HHS guidance on ongoing risk analysis.

What safeguards help protect ePHI during remote consultations?

Use access controls and individual accounts, verify participants, limit recording and screen sharing, secure transmissions, and protect the devices and accounts used by staff. Select and configure telehealth tools based on your risk analysis and vendor obligations, including BAAs where required. Give patients practical privacy guidance, such as choosing a private location and using a screen lock and strong password. See HHS telehealth privacy and security tips.

Share this article

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

Related Articles