Role-based access
Permissions are granted by role for each practice and location. Screens and actions a role cannot use are not available to it.
Security
Patient information deserves care in the design, not a checkbox at the end. These are the controls built into IasoPulse.
Permissions are granted by role for each practice and location. Screens and actions a role cannot use are not available to it.
Access and changes to records are written to an audit log that is chained so tampering can be detected.
Every organization's data is separated, and each request is scoped to the user's practice and location.
All traffic to IasoPulse uses HTTPS with modern TLS.
System logs are designed to exclude patient identifiers, and sign-in tokens do not carry patient information.
Sign-in attempts are rate limited and sessions expire. Signed clinical notes are locked against silent edits.
HIPAA compliance is a shared responsibility between a software vendor and the practice. IasoPulse is built with the administrative and technical safeguards described on this page, and we discuss a business associate agreement with each customer before any patient data is loaded.
Yes. A BAA is part of onboarding before production use.
Yes. Roles and permissions are set per user, practice and location.
Call +1 (561) 915-0195 or use the contact form and mark the message as a security report.
A 30-minute walkthrough with someone who knows billing. No slides, just the product.