Non-Emergency Medical Transportation Broker Security Risk Assessment Checklist
Use this checklist to identify where rider information is collected, accessed, shared, and stored—and where a security failure could disrupt transportation operations. First determine whether your organization is a HIPAA covered entity or business associate based on its role and handling of protected health information (PHI); being an NEMT broker does not, by itself, establish HIPAA status. HHS explains who qualifies as a covered entity or business associate.
If the HIPAA Security Rule applies, its risk analysis must address potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic PHI (ePHI). Treat this as an ongoing process, not a one-time compliance exercise. See HHS guidance on HIPAA Security Rule risk analysis.
How should brokers define the scope and map sensitive data flows?
Set boundaries before evaluating controls. Identify the business units, locations, systems, processes, and outside parties included in the review. Record what is excluded and why, and confirm the scope covers every place in which ePHI is created, received, maintained, or transmitted.
- Map how rider, trip, eligibility, authorization, payment, and service data enter the broker’s environment, move between systems, and leave it.
- Trace transfers among riders and caregivers, broker staff, healthcare plans or providers, transportation providers, call centers, payment processors, and technology vendors.
- Include mobile apps, web portals, email, text messaging, application programming interfaces, file transfers, printed manifests, call recordings, and spreadsheets where applicable.
- Mark where data is collected, viewed, changed, stored, backed up, archived, exported, or deleted—including vendor-hosted systems and staff devices.
- For each flow, identify the information involved, the sender and recipient, the transfer method, the business purpose, and the safeguards in place.
Use a data-flow diagram and system inventory together: the diagram shows movement, while the inventory identifies the applications and infrastructure involved. HHS notes that a thorough risk analysis accounts for ePHI throughout an organization’s environment, including information handled by vendors; see its risk analysis guidance.
Which patient and operational assets should the assessment cover?
Include assets that store, process, transmit, or provide access to sensitive information, as well as the operational services needed to arrange and deliver rides. Separate ePHI from other sensitive business information, but assess both where loss or compromise could affect privacy, rider safety, service availability, or contractual obligations.
- Rider information: names, contact details, member or plan identifiers, pickup and destination addresses, appointment or provider details, trip history, eligibility, authorizations, and relevant mobility or accommodation notes. Whether these details are PHI depends on their context, identifiability, and how the broker handles them.
- Operational records: trip assignments, dispatch instructions, driver and vehicle details, service complaints, payment or claims records, and emergency contact information.
- Systems and data stores: scheduling and dispatch platforms, customer relationship tools, databases, identity services, email, call-recording systems, backups, logs, reports, and integrations.
- Devices and facilities: laptops, phones, tablets, removable media, workstations, offices, dispatch centers, and paper files.
- People and access paths: employees, temporary staff, contractors, administrators, support personnel, transportation providers, and vendor personnel who may access information or systems.
Keep the inventory current and assign an owner to each important asset. HHS identifies inventories of systems and applications that access or house ePHI as useful inputs to a risk analysis in its guidance on risk analysis and risk management.
How can brokers identify and rate security threats and risks?
For each asset and data flow, identify plausible threats and vulnerabilities, then evaluate both the chance of an event and its potential impact. Consider confidentiality, integrity, and availability—for example, unauthorized disclosure of rider details, altered pickup instructions, or an outage that prevents dispatch.
- Consider phishing, stolen credentials, ransomware, misdirected messages, excessive access, insider misuse, lost devices, insecure integrations, vendor incidents, and unpatched software.
- Include operational hazards such as power loss, connectivity failures, physical access to dispatch systems, severe weather, and disruption at a critical service provider.
- Review existing safeguards and evidence that they work, such as access reviews, security logs, incident records, and vulnerability scanning results.
- Use a consistent rating method—for example, likelihood and impact scales—and record the rationale, affected assets, existing controls, and resulting risk level.
- Prioritize risks that could expose sensitive rider details, compromise trip accuracy, disrupt essential services, or affect many people or systems.
Vulnerability scanning can help identify technical weaknesses, but it does not replace reviewing configurations, access, vendor practices, physical safeguards, or business processes. HIPAA does not prescribe one risk-rating formula or one scanning schedule; document the method you select and use it consistently. HHS describes the expected risk analysis process in its official risk analysis guidance.
What access, encryption, and device controls should be verified?
Check whether controls limit access to authorized users and protect information in the systems and devices that handle it. A control checklist can guide the review, but it does not by itself establish HIPAA compliance; safeguards must be appropriate to the organization’s circumstances and documented where required.
- Role-based access control (RBAC): Confirm roles provide only the access needed for assigned duties, including dispatch, billing, customer support, vendor support, and system administration. Review permissions when roles change and promptly remove access when it is no longer needed.
- Authentication: Verify unique user accounts, secure password practices, and multifactor authentication (MFA), especially for remote access, administrative accounts, and systems containing ePHI. Treat MFA as a prudent risk-based safeguard rather than a universal requirement expressly named in the current Security Rule.
- Logs and monitoring: Confirm systems record and review relevant access and administrative activity, and that alerts or investigations have an assigned owner.
- Encryption: Check protections for ePHI stored on devices and servers and sent over networks, including how encryption keys are managed. Under the Security Rule, encryption is an addressable implementation specification: assess whether it is reasonable and appropriate, and document the decision and any applicable alternative. See HHS guidance on HIPAA encryption.
- Devices and physical security: Review device inventories, screen locks, secure configuration, remote access, loss reporting, disposal, media reuse, and controls for workstations and paper records.
- Updates and weaknesses: Review patching, secure configuration, vulnerability scanning, and remediation processes, with appropriate testing before changes affect dispatch or other critical services.
HHS summarizes the Security Rule’s technical safeguards—including access control, audit controls, authentication, and transmission security—in its HIPAA Security Rule overview.
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 vendors and business associate agreements be assessed?
Assess vendors according to the information they handle and the services they perform, not just their industry or contract label. A vendor may be a business associate when it performs certain functions or services on behalf of a covered entity that involve PHI; a subcontractor may also qualify when it handles PHI on behalf of a business associate. Determine the parties’ roles and obligations based on the actual arrangement.
- List vendors that can create, receive, maintain, or transmit PHI, such as dispatch-platform providers, cloud or hosting providers, call centers, billing services, and data-integration vendors, where relevant to their role.
- Confirm a written business associate agreement (BAA) is in place when required. Review permitted uses and disclosures, safeguards, incident and breach reporting, subcontractors, cooperation with individual rights, and return or destruction of PHI at the end of the arrangement.
- Check that relevant subcontractors are covered by appropriate written assurances and that the vendor can identify its downstream data handling.
- Review security evidence and practices, including access management, incident handling, continuity, vulnerability remediation, and data deletion or return.
- Document vendors that do not require a BAA because they do not meet the business associate definition, while still evaluating contractual, operational, and privacy risks where appropriate.
HHS explains the business associate definition and BAA obligations in its Business Associates FAQ and business associate contract guidance. A vendor’s general security assurances do not replace a required BAA.
How can brokers test incident response and continuity plans?
Check that written procedures identify who detects, reports, assesses, contains, and resolves a security incident. Test whether responders can preserve evidence, determine which systems and rider information may be affected, coordinate with vendors and transportation providers, and restore essential dispatch functions.
- Run a tabletop exercise for scenarios such as compromised staff credentials, ransomware, a lost device, a vendor outage, or an incorrectly shared trip file.
- Confirm staff know how to report suspected incidents and who can make containment and escalation decisions.
- Review breach notification procedures, including how the broker will promptly inform the appropriate covered entity or business associate under the applicable agreement and support required notifications.
- Verify that contingency arrangements cover data backup, disaster recovery, emergency-mode operations, and access to needed information during an outage.
- Test backups and recovery procedures, record the results, and track gaps through resolution. Review plans after exercises, incidents, or significant system and business changes.
The Security Rule includes contingency planning requirements, including data backup, disaster recovery, and emergency-mode operations; testing and revision is an addressable implementation specification. HHS describes these elements in its administrative safeguards guidance. The HHS Breach Notification Rule guidance explains notification duties for covered entities and business associates.
How should residual risks, owners, and corrective actions be tracked?
Maintain a risk register that connects each finding to a decision and an accountable person. A useful entry records the affected asset or data flow, threat and vulnerability, likelihood and impact, existing safeguards, residual risk, planned action, owner, target date, approval, and evidence of completion.
- Assign a named owner with authority to coordinate remediation, rather than leaving responsibility with a general team or vendor.
- Prioritize actions using risk severity, potential effect on riders and operations, dependencies, and available safeguards.
- For accepted or deferred risks, document the rationale, approver, any compensating controls, and a date or event that will trigger reconsideration.
- Track corrective actions to closure and verify that the change reduced risk; update the assessment if risk remains or conditions have changed.
- Retain assessment records and related decisions under applicable documentation policies, and make them available to the people responsible for implementing safeguards.
HIPAA does not require one particular risk-register format or set a universal reassessment interval. HHS says risk analysis should be ongoing and that reassessment frequency depends on the organization and its environment; reassess when meaningful operational or technology changes, incidents, or newly recognized risks warrant it. See HHS guidance on periodic review and updates.
A useful assessment connects rider data flows, assets, threats, controls, vendor obligations, and continuity plans to documented risk decisions and accountable corrective actions.
FAQs
What rider information should an NEMT broker include in a security risk assessment?
Include identifiable rider and trip information the broker handles, such as contact and member details, pickup and destination addresses, appointment or provider details, trip history, eligibility and authorization records, relevant mobility accommodations, and associated payment or claims information. Map where each type is collected, used, shared, stored, backed up, and deleted. Whether a detail is PHI depends on its context and the broker’s role.
How often should an NEMT broker reassess security risks?
HIPAA does not set one universal interval for a risk analysis. Reassess periodically and when changes—such as a new platform, vendor, data flow, incident, or operational process—could affect security. HHS describes risk analysis as an ongoing process, with frequency depending on the organization’s circumstances, in its risk analysis guidance.
Which vendors require a business associate agreement?
A BAA is generally required when a vendor meets the HIPAA business associate definition by performing covered functions or services involving PHI on behalf of a covered entity; a subcontractor handling PHI on behalf of a business associate may also require an agreement. Evaluate the actual service and data access rather than assuming every vendor does—or does not—need a BAA. See the HHS Business Associates FAQ.
How should brokers document and track residual security risks?
Record the risk, affected information or systems, likelihood and impact, safeguards, residual rating, chosen response, rationale, accountable owner, approval, and corrective-action due date. Review open risks and confirm completed actions are effective. Preserve the assessment and supporting decisions under the organization’s documentation and retention procedures.
Table of Contents
- How should brokers define the scope and map sensitive data flows?
- Which patient and operational assets should the assessment cover?
- How can brokers identify and rate security threats and risks?
- What access, encryption, and device controls should be verified?
- How should vendors and business associate agreements be assessed?
- How can brokers test incident response and continuity plans?
- How should residual risks, owners, and corrective actions be tracked?
- 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