Data security
Miraa handles sensitive clinical information, so security is built into how it works — and reinforced by the habits of everyone who uses it.
How Miraa protects data (high level)
- Access control. People see only what their role, access level, permissions, and clinic allow, and clinics are isolated from one another. See User roles & access.
- Encryption. Patient data is protected in transit and at rest, and sensitive credentials (such as integration secrets) are encrypted.
- Audit trail. Sensitive actions are logged. See Audit trail.
- Authentication. Sign-in is protected, and clinics can require multi-factor authentication.
These are high-level operational descriptions. For your clinic’s formal security and compliance documentation, contact Miraa directly — these docs don’t assert any specific certification or accreditation.
Your security habits matter
Most real-world security issues come down to everyday practice:
Protect your account
Use a strong, unique password and keep multi-factor authentication enabled.
Don’t share accounts
Each person uses their own account, so the audit trail stays meaningful.
Lock your screen
Don’t leave patient data visible on an unattended device.
Be careful with exports
Exported files leave the app’s protections — store and share them securely. See Documents & history.
Report concerns
If you suspect an account is compromised or data was exposed, tell your admin immediately.
Keep sensitive data where it belongs. Don’t paste patient-identifying information into unrelated tools, chats, or notes outside the clinical record.
Analytics and logs stay free of patient data
Miraa’s product analytics and operational logs are designed to exclude patient identifiers. If you ever see patient-identifying information somewhere it shouldn’t be, report it.
Common mistakes
- Reusing a weak password or turning off MFA.
- Sharing a login “just this once”.
- Emailing or storing exported clinical files insecurely.