Security Risk Assessment Guide for a Per Diem Clinician Staffing Marketplace App
How to scope the risk assessment and map sensitive data flows
Start by identifying what the app does for each healthcare organization and what information it creates, receives, maintains, or transmits. HIPAA obligations depend on the organization’s role and its handling of protected health information—not simply on whether clinicians use the app. If the platform handles electronic protected health information (ePHI) on behalf of a covered entity or business associate, it may be a business associate; if it only handles clinician profiles, credentials, availability, and staffing logistics without handling PHI, HIPAA may not apply to those activities. Confirm the actual data and service relationship with counsel and each customer. See HHS guidance on business associates.
Map the information from collection through deletion. Include the mobile app, web portal, APIs, identity provider, databases, backups, customer systems, support tools, analytics, crash reporting, messaging, and cloud services. For each flow, record the data involved, who can access it, where it is stored, how it moves, why it is needed, and how long it is kept.
- Clinician and workforce information: profiles, contact details, credentials, availability, shift requests, location, and employment or payment records. Treat this as sensitive even when it is not ePHI.
- Potential ePHI: patient names or identifiers, clinical details, patient-linked assignments, or messages that reveal an individual’s care. Check free-text fields, attachments, notifications, and support tickets, not only fields labeled “medical.”
- System and vendor data: authentication records, audit events, backups, telemetry, support access, and information processed by hosting, messaging, analytics, and identity vendors.
Use the map to define the assessment boundary, identify data owners, and note trust boundaries between the marketplace, staffing agency, healthcare customer, clinician, and vendors. HHS says risk analysis should cover all ePHI an organization creates, receives, maintains, or transmits, regardless of its electronic medium or location. See HHS Guidance on Risk Analysis.
Which mobile app security controls should be assessed?
Assess controls across the app, its backend, and the devices used to access it. The HIPAA Security Rule is technology-neutral: it requires safeguards appropriate to the organization and its risks rather than prescribing one mobile security product or design. Check whether the controls work in practice and whether they protect confidentiality, integrity, and availability.
- Authentication and access: unique accounts, strong authentication, secure account recovery, session expiration, and prompt removal or adjustment of access when a clinician, employee, or administrator changes roles or leaves.
- Authorization: role-based access control (RBAC) and least privilege, with separation between staffing customers and restrictions on administrative access. Test whether users can access another organization’s records by changing an identifier or calling an API directly.
- Mobile application data encryption: assess encryption in transit and at rest, secure key management, and whether sensitive data is unnecessarily cached, copied, or included in notifications. HHS treats encryption as an addressable specification: assess whether it is reasonable and appropriate for the risk, and document the decision and any appropriate alternative safeguards. See HHS guidance on encryption under the Security Rule.
- Auditability and integrity: record and examine relevant activity in systems containing or using ePHI, including access and administrative changes. Protect logs from unauthorized alteration and limit who can view them.
- App and API security: review secure development, code and dependency updates, vulnerability testing, API authorization, input validation, secrets management, and controls that prevent sensitive data from reaching analytics or crash-reporting services.
- Availability and recovery: assess backups, restoration tests, outage procedures, and protections against data loss or service disruption.
Set audit log retention in a documented policy that considers investigation needs, contractual terms, and other applicable requirements. The Security Rule requires specified compliance documentation to be retained for six years from its creation or the date it was last in effect, whichever is later; that rule concerns required documentation and should not be treated as a universal retention period for every application log. See HHS Security Rule documentation guidance and the HHS Security Rule summary.
How to evaluate ePHI risks and vulnerabilities under HIPAA
For a regulated entity, the HIPAA Security Rule risk analysis must assess potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. It is not simply a checklist of safeguards or a scan for technical flaws. Consider threats to people, processes, devices, applications, infrastructure, and vendors, then assess likelihood and potential impact. See HHS risk analysis guidance.
For each data flow, ask what could go wrong and how. Examples include a lost personal phone with an active session, excessive access by a staffing coordinator, a misdirected message, an exposed API, a compromised vendor account, ransomware, an unavailable cloud service, or ePHI appearing in a notification or diagnostic log. Consider vulnerabilities in policies and procedures as well as technical weaknesses.
Document the assessment method, scope, identified threats and vulnerabilities, existing safeguards, likelihood and impact judgments, resulting risk levels, and corrective actions. Assign an owner and target date to each action, track open findings, and record the rationale for any risk decision. HHS explains that the Security Rule does not prescribe a single risk-analysis method; the organization must use a method suited to its size, complexity, and environment.
How to review workforce access and personal devices
Review access by job function, including clinicians, schedulers, credentialing teams, customer administrators, support staff, and system operators. Use unique user identities so activity can be attributed to an individual, and test that each role can reach only the records and functions needed for its work. Review access when duties change and revoke it promptly when it is no longer needed. HHS describes unique user identification and role-appropriate access in its Technical Safeguards guidance.
If users may access the app on personal devices, assess the risks created by lost or shared phones, outdated operating systems, local downloads, screenshots, backups, and notifications visible on a locked screen. Decide whether to permit personal devices and define safeguards such as device encryption and screen locks, supported operating-system versions, secure sessions, restricted local storage, remote revocation or wiping where feasible, and a clear process for reporting a lost device. HHS guidance calls for considering mobile and remote access to ePHI within the organization’s risk analysis; see HHS guidance on remote use of and access to ePHI.
Provide workforce members with training and instructions that match their access and responsibilities, including how to handle sensitive data and report a suspected incident. Do not treat completion of a general training course or certificate as proof that the organization is HIPAA compliant; staff must also follow the applicable employer, customer, and platform policies.
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 to assess business associates and subcontractors
Determine whether the marketplace performs a function or service for a covered entity or business associate that involves creating, receiving, maintaining, or transmitting PHI. A platform’s role depends on the services and data flows: supporting staffing alone does not automatically make it a business associate, but handling PHI on a customer’s behalf can. HHS provides examples and explains the business associate relationship in its Business Associates guidance.
Where required, put a business associate agreement (BAA) in place before the service handles PHI. Confirm that the agreement describes permitted uses and disclosures, requires appropriate safeguards, addresses incident and breach reporting, and sets out what happens to PHI when the arrangement ends. A BAA supports the relationship; it does not replace the parties’ risk analysis or implementation of safeguards. See HHS sample business associate agreement provisions.
Inventory subcontractors that may access or process ePHI, including cloud hosting, communications, support, and analytics providers. Assess their services, access, safeguards, incident procedures, and deletion or return practices. When a business associate uses a subcontractor to handle ePHI on its behalf, the business associate must obtain written assurances requiring the subcontractor to apply the required safeguards. See HHS guidance on HIPAA and cloud computing. Record who owns each vendor risk, how subcontractor security safeguards are checked, and how material service or control changes will be communicated.
How to document incident response and remediation responsibilities
Write down who detects, triages, contains, investigates, and resolves an incident involving the app or its data. Identify contacts and escalation routes for the marketplace, healthcare customer, staffing agency, hosting provider, and other relevant vendors. Include procedures to preserve evidence, assess possible ePHI exposure, restore operations, address the underlying vulnerability, and record lessons learned.
Define incident reporting expectations in contracts and operational procedures, including how quickly each party must notify the others and what information the initial notice should contain. HIPAA requires business associates to address, mitigate, and document security incidents; a BAA must require reporting of security incidents to the covered entity or business associate customer. Breach notification duties are separate and may apply when an incident meets the definition of a breach. See HHS guidance on reporting cloud-service security incidents.
Maintain a remediation register that links each finding to its risk level, owner, due date, corrective action, and verification evidence. Document any accepted residual risk and the person authorized to approve it. Keep the required risk-analysis and other Security Rule documentation in a retrievable form under the applicable retention requirements.
When should the security risk assessment be updated?
Keep the assessment current rather than treating it as a one-time launch task. Revisit it when the app adds a new feature or data type, changes an integration or hosting arrangement, adopts a new device or authentication method, changes who can access ePHI, or experiences an incident or newly identified vulnerability. Reassess when business operations, workforce roles, or customer requirements materially change as well.
HIPAA does not set a single universal interval for conducting a comprehensive risk analysis. HHS describes risk analysis as ongoing and says update frequency depends on the organization and its circumstances. Set a review cadence that fits the platform’s risk and operating environment, and trigger an earlier review when significant changes or incidents occur. See HHS guidance on ongoing risk analysis.
In short, define the app’s HIPAA role from its actual data flows, assess technical and operational risks to ePHI, verify access and vendor safeguards, and document owners, remediation, and review triggers. Keep that assessment connected to product changes and incident response so it remains useful as the marketplace evolves.
FAQs
Does a clinician staffing marketplace app need a HIPAA risk analysis?
If the marketplace is a covered entity or business associate handling ePHI, the HIPAA Security Rule requires an accurate and thorough risk analysis. An app that only handles clinician staffing information and does not handle PHI on behalf of a covered entity or business associate may not be subject to that requirement for those activities, though other privacy, security, contractual, or state-law obligations may apply. Determine the platform’s role from its actual services and data flows.
When is a staffing platform considered a business associate?
A staffing platform may be a business associate when it performs a function or service for a covered entity or another business associate that involves creating, receiving, maintaining, or transmitting PHI. The label “staffing marketplace” does not decide the issue; what matters is what the platform does and what data it handles on whose behalf. If it is a business associate, a BAA and appropriate safeguards may be required.
What security controls should protect ePHI in a mobile staffing app?
Assess unique user accounts, role-based access control, appropriate authentication, secure sessions, encryption decisions, audit controls, integrity protections, secure APIs, restricted local storage, device safeguards, backups, and incident response. Select safeguards based on the risk analysis, and document decisions where an addressable specification such as encryption is not implemented as specified.
How often should the app’s security risk assessment be updated?
HIPAA does not prescribe one universal annual schedule. Treat the analysis as ongoing, establish a review cadence appropriate to the platform’s risk, and update it after significant changes, new threats, or incidents. An annual review can be an organization’s chosen practice, but it is not a universal federal annual-renewal requirement.
Table of Contents
- How to scope the risk assessment and map sensitive data flows
- Which mobile app security controls should be assessed?
- How to evaluate ePHI risks and vulnerabilities under HIPAA
- How to review workforce access and personal devices
- How to assess business associates and subcontractors
- How to document incident response and remediation responsibilities
- When should the security risk assessment be 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