Role-based access
Dispatchers, drivers, billing staff, and administrators see the data their role requires—drivers see their manifests, not your whole operation.
Security & data protection
NEMT software holds sensitive information: rider details, trip histories, and your business records. Here is how we approach protecting it—and the questions we think you should ask every vendor, including us.
Dispatchers, drivers, billing staff, and administrators see the data their role requires—drivers see their manifests, not your whole operation.
Every user works from an individual authenticated account, so activity is attributable and departing staff can be removed immediately.
Data moving between the driver app, dispatch, and our servers is encrypted in transit using TLS.
Trip records carry the rider details needed to deliver and document service—we encourage teams to store only what the workflow requires.
Axen runs on managed cloud infrastructure with backups, rather than servers in an office closet.
Security questionnaires and specific technical questions are welcome—ask during your evaluation and we will answer directly.
Many software websites stamp “HIPAA compliant” on a page as a marketing badge. In practice, HIPAA obligations depend on how your organization handles protected health information, your agreements with payers and brokers, and the safeguards both you and your vendors maintain—including whether a Business Associate Agreement is in place. Rather than make blanket claims, we encourage you to raise your specific regulatory requirements during evaluation so we can address them concretely, and to involve your compliance advisor where appropriate.
These belong on your demo checklist alongside features and pricing—see our full list of questions to ask during an NEMT software demo.
We'd rather answer hard questions before you buy than after.
Contact our team