Server-side authorization
Sensitive app areas use authenticated access boundaries and organization-aware authorization checks.
Security / HIPAA
Built with healthcare privacy in mind
aiRVU is designed for HIPAA-aligned general surgery workflows, with role-based access, auditability, and clear boundaries around general surgeon review and EHR copy/paste.
Discuss Access
Important deployment note
Real PHI should be processed only after business associate agreements, hosting configuration, access controls, and legal review are complete.
Architecture
Privacy-minded controls for operative note workflows
The platform favors server-side services, structured validation, and auditable actions around sensitive clinical documentation.
Sensitive note handling
Operative notes are treated as sensitive healthcare data and kept out of normal application logs.
Audit-ready workflows
Note creation, CPT selection, aiRVU Note generation, and copy workflows are designed for audit events.
Server-only AI workflows
AI processing is handled through server-side services with structured output validation before save.
Trust Boundaries
Clear limits around automation
aiRVU supports general surgeon-reviewed documentation. It does not automatically submit to billing systems or the EHR.
HIPAA-minded architecture
Audit logs for sensitive workflows
Role-based access
No automatic EHR submission
General surgeon attestation before rewrite
Bring general surgeon review earlier in the note workflow
Request access for a focused general surgery pilot, or see the workflow before evaluating deployment requirements.