Telepsychiatry Staffing Company Security Risk Assessment Checklist
Use this checklist to assess how your telepsychiatry staffing company protects electronic protected health information (ePHI) across clinical services, workforce access, remote work, and vendor relationships. First clarify the company’s role: a staffing company is not automatically a HIPAA covered entity or business associate simply because it places clinicians. Its obligations depend on the functions it performs, whose workforce the clinicians are, and whether the company creates, receives, maintains, or transmits protected health information on behalf of a covered entity or business associate.
The HIPAA Security Rule risk analysis must be accurate and thorough, address risks to ePHI confidentiality, integrity, and availability, and inform appropriate safeguards. HHS does not prescribe one risk-analysis method or a fixed assessment format. HHS Guidance on Risk Analysis
Which systems create, receive, maintain, or transmit ePHI?
Identify every system that handles ePHI, including systems used by clinicians, schedulers, credentialing teams, billing staff, supervisors, and IT administrators. Include systems that hold data temporarily, connect to other systems, or provide remote support—not only the electronic health record (EHR).
- Telehealth video, messaging, appointment, and patient-intake platforms.
- EHRs, e-prescribing tools, clinical documentation, and care-coordination systems.
- Staffing, scheduling, credentialing, payroll, billing, and claims systems if they contain or connect to ePHI.
- Email, file-sharing, cloud storage, help-desk, backup, identity-management, and remote-access services.
- Workstations, laptops, phones, tablets, removable media, network equipment, and backup devices that store, display, or transmit ePHI.
- Interfaces, APIs, integrations, and data exports that move information between systems.
Record each system’s owner, purpose, data handled, user groups, hosting location, integrations, and whether it is production, test, or backup infrastructure. HHS identifies system and application inventory as a possible part of risk analysis and says all ePHI created, received, maintained, or transmitted is within the Security Rule’s scope. HHS Risk Analysis and Risk Management FAQ
How should telepsychiatry data flows and assets be inventoried?
Map how information moves from collection through use, sharing, storage, backup, and deletion. For example, trace appointment requests to intake, the video visit, clinical documentation, prescriptions, billing, and any follow-up communication. Note where data crosses organizational or vendor boundaries and who can access it at each point.
- Document the ePHI involved at each step, such as identifiers, appointment details, clinical notes, diagnoses, prescriptions, and billing data.
- Identify the systems, devices, accounts, networks, and locations involved in creating, receiving, maintaining, or transmitting it.
- Record the source and destination of transfers, including integrations, downloads, email attachments, and support or maintenance access.
- Identify where data is stored, how backups are handled, and what happens to copies when a service or workforce relationship ends.
- Consider human, technical, environmental, and natural threats, including misdirected messages, lost devices, unauthorized access, service outages, and ransomware.
For each identified risk, assess the likelihood and potential impact on ePHI, note existing safeguards, and identify gaps. HHS says the Security Rule does not require a particular methodology, but the analysis must cover potential risks and vulnerabilities to ePHI confidentiality, integrity, and availability. HHS Guidance on Risk Analysis
What workforce access controls and training are required?
Review how clinicians and staff receive, use, change, and lose access. Access should reflect each person’s duties and the ePHI they need for those duties. Use role-based access control where it fits your environment, and review whether shared accounts or excessive permissions make it difficult to identify who accessed information.
- Document who approves access, which roles and systems are available, and how permissions are changed when duties change.
- Remove or disable accounts promptly when a clinician or staff member leaves or no longer needs access.
- Assess authentication for remote access, including whether stronger authentication, such as multifactor authentication, is appropriate to reduce risk.
- Review privileged accounts separately and limit, monitor, and protect administrative access.
- Provide security awareness and training relevant to workforce responsibilities, including company policies for accessing, discussing, storing, and transmitting ePHI.
- Keep evidence of training and policy acknowledgments, while treating a training completion certificate as evidence of an individual’s training—not proof that the organization is HIPAA compliant.
HHS describes workforce training as a Security Rule requirement and explains that access controls must limit ePHI access to appropriately authorized people. Training should reflect employer-specific policies and relevant risks; do not assume that an annual certificate renewal is a universal federal requirement. HHS OCR Cybersecurity Newsletter on Access Controls
How can remote devices and workspaces be secured?
Assess the actual conditions in which clinicians and staff access ePHI, including home offices and other approved remote locations. Remote access remains within the scope of the Security Rule; working away from a company office does not remove the need for appropriate safeguards.
- Identify whether devices are company-managed or personally owned, what ePHI they can access, and how devices are secured and updated.
- Assess screen locks, automatic logoff, device encryption, endpoint protection, patching, and the ability to remotely disable or wipe a lost device where appropriate.
- Review whether remote connections use approved, protected access methods and whether ePHI may be downloaded, printed, or stored locally.
- Set workspace expectations for private conversations, screen visibility, household access to devices, and secure handling of notes or printed material.
- Address secure disposal, device return, removable media, and reporting of lost devices or suspected exposure.
- Train remote workers on safe access and transmission practices, including restrictions on public computers and unsecured networks when applicable.
HHS says telecommuting staff with ePHI access must have appropriate safeguards. Automatic logoff is an addressable specification: assess whether it is reasonable and appropriate, and document the decision and any appropriate alternative measure. HHS FAQ on Telecommuting and Access Controls
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 AssessmentWhich technical safeguards and audit controls should be assessed?
Check whether technical safeguards are configured and used effectively across the systems in scope, not simply whether a product includes a security feature. Compare the safeguards in place with the risks identified in your HIPAA Security Rule risk analysis.
- Access and authentication: Review unique user identities, permission settings, remote authentication, session controls, and protections for administrator accounts.
- Audit controls: Confirm relevant systems record activity involving ePHI and that responsible personnel review logs for suspicious access, changes, or system activity.
- Integrity and availability: Assess protections against improper alteration or destruction, as well as backups, recovery procedures, and service continuity.
- Encryption at rest and in transit: Assess whether ePHI is protected when stored and transmitted. HIPAA treats encryption specifications as addressable, not as a blanket technical mandate in every circumstance; document the risk-based decision and any appropriate alternative safeguard.
- Security configuration: Review patching, supported software, endpoint protections, logging, and system settings against identified risks.
HHS identifies access controls, encryption, audit controls, and authentication as technical safeguards informed by risk analysis and risk management. HHS OCR Cybersecurity Newsletter on Security Baselines HHS also explains that an addressable specification is not simply optional: if it is not reasonable and appropriate, document that determination and implement an equivalent measure when reasonable and appropriate. HHS Guidance on Risk Analysis
How should vendors and business associates be evaluated?
List vendors and subcontractors that may create, receive, maintain, or transmit ePHI, or that provide services involving access to it. Determine each party’s role from the actual services and relationship; do not assume every technology vendor is a business associate, or that a vendor is exempt because data is encrypted.
- Consider telehealth platforms, EHR and cloud providers, data-hosting and backup services, IT support, billing services, transcription, and other vendors whose work involves ePHI.
- For each relationship, document what data the vendor handles, why it handles it, who can access it, and what subcontractors may be involved.
- Determine whether a business associate agreement is required before the vendor performs the relevant service or receives ePHI.
- Review contract provisions for permitted uses and disclosures, safeguards, security-incident reporting, breach notification, subcontractors, and return or deletion of information at termination.
- Assess vendor security information and service arrangements in light of your own risk analysis; a signed agreement does not replace the organization’s assessment of risks.
A business associate generally performs certain functions or services on behalf of a covered entity that involve protected health information; a business associate’s subcontractor may also need a written agreement. HHS lists cloud providers and IT contractors with relevant ePHI access among potential business associates. HHS Business Associates FAQ
How should risks, incidents, and remediation actions be documented?
Keep a written record of the assessment’s scope, information reviewed, systems and data included, identified threats and vulnerabilities, existing safeguards, risk determinations, and decisions about additional measures. The Security Rule does not prescribe a specific risk-analysis format, so use a structure that lets responsible staff understand the findings and track action.
- For each risk, record its affected system or data flow, potential impact, likelihood or rating method, existing controls, and planned response.
- Assign each remediation action an owner, priority, target date, and status; retain evidence when the action is completed or a decision is made to accept or otherwise address the risk.
- Document security incidents, investigation findings, affected systems and data, mitigation, recovery, notifications or escalations, and lessons learned.
- Maintain incident-response procedures that explain how workforce members report concerns and how the organization identifies, responds to, mitigates, and documents incidents.
- Revisit findings after relevant environmental or organizational changes, such as new technology, new threats, changed operations, or an incident.
HHS requires documentation of the risk analysis and says required Security Rule documentation must generally be retained for six years from its creation or the date it was last in effect, whichever is later. This retention rule applies to documentation required by the Security Rule, not automatically to every business record. HHS Summary of the HIPAA Security Rule Business associates must identify and respond to suspected or known security incidents, mitigate harmful effects to the extent practicable, and document incidents and outcomes. HHS FAQ on Business Associate Security-Incident Reporting
In summary, a useful telepsychiatry staffing company assessment maps ePHI and its data flows, checks workforce and remote-access safeguards, evaluates technical controls and business associate relationships, and documents risks through remediation. Keep the analysis current as your systems, services, and risks change.
FAQs
How often should a telepsychiatry staffing company update its security risk assessment?
HIPAA does not prescribe a fixed annual interval for a comprehensive risk analysis. HHS describes the process as ongoing and says entities should review and update documentation in response to environmental or organizational changes affecting ePHI. Set a review cadence appropriate to your operations and reassess when relevant systems, vendors, workflows, threats, or incidents change. HHS Guidance on Risk Analysis
What systems and devices should the assessment include?
Include all systems and devices that create, receive, maintain, or transmit ePHI, as well as connected services and data flows that affect its security. This can include telehealth platforms, EHRs, email and messaging, cloud storage, scheduling and billing tools, remote-access systems, workstations, laptops, phones, tablets, removable media, and backups.
Which vendors need a business associate agreement?
Assess whether each vendor performs a function or service on behalf of a covered entity or business associate that involves creating, receiving, maintaining, or transmitting PHI. Vendors such as cloud providers or IT support providers may qualify depending on their services and access. A vendor’s role depends on the actual relationship and activity, so determine whether a business associate agreement is required before disclosing ePHI for the service. HHS Business Associates FAQ
What records should be retained to document risk mitigation?
Retain the documented risk analysis, identified risks, decisions and rationale, remediation plans, responsible owners, progress and completion evidence, relevant policies, and incident records. HIPAA generally requires documentation that the Security Rule requires to be maintained for six years from its creation or the date it was last in effect, whichever is later. HHS Summary of the HIPAA Security Rule
Table of Contents
- Which systems create, receive, maintain, or transmit ePHI?
- How should telepsychiatry data flows and assets be inventoried?
- What workforce access controls and training are required?
- How can remote devices and workspaces be secured?
- Which technical safeguards and audit controls should be assessed?
- How should vendors and business associates be evaluated?
- How should risks, incidents, and remediation actions be documented?
- 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