Pryme Practice is a fully HIPAA-compliant chiropractic EHR with AES-256 encryption, Business Associate Agreement availability, comprehensive audit logging, and security controls aligned to the SOC 2 Type II framework. Also compliant with PIPEDA and Canadian provincial health information acts.
Security is built into every layer of the Pryme Practice platform — not bolted on as an afterthought.
All patient data encrypted at rest using AES-256 and in transit using TLS 1.2+. The same standard used by financial institutions.
Every access, edit, and export of patient records is logged with timestamp, user ID, and IP address. Immutable audit trail for compliance reviews.
Granular permissions for every staff role. Front desk, clinical, billing, and admin users each see only what they need.
BAA available to all customers. Documents the responsibilities of both parties for PHI handling as required under HIPAA.
Incident response procedures aligned with HIPAA Breach Notification Rule. 24/7 security team with documented response timelines.
Security controls aligned to the SOC 2 Type II framework. Regular third-party security assessments and penetration testing.
HIPAA (Health Insurance Portability and Accountability Act) compliance for a chiropractic EHR means the software meets the Privacy Rule, Security Rule, and Breach Notification Rule requirements for protecting Protected Health Information (PHI). This includes technical safeguards (encryption, access controls, audit logs), administrative safeguards (policies, training, risk assessments), and physical safeguards (data center security). A HIPAA-compliant EHR also provides a Business Associate Agreement (BAA) to customers.
Yes. Pryme Practice is fully HIPAA-compliant. All patient data is encrypted at rest using AES-256 and in transit using TLS 1.2+. The platform includes role-based access controls, comprehensive audit logging, automatic session timeouts, and Business Associate Agreement (BAA) availability for all customers. Pryme Practice is also SOC 2 Ready, with security controls aligned to the SOC 2 Type II framework.
Yes. A Business Associate Agreement (BAA) is available to all Pryme Practice customers. The BAA documents the responsibilities of both parties regarding the handling of Protected Health Information (PHI) and is required under HIPAA for any software vendor that processes, stores, or transmits PHI on behalf of a covered entity (your practice).
Yes. Pryme Practice supports compliance with PIPEDA (Personal Information Protection and Electronic Documents Act) at the federal level, as well as provincial health information acts including PHIPA (Ontario), HIA (Alberta), PIPA (BC), and Quebec Law 25. Canadian customers receive the same security infrastructure as US customers, with data residency options available.
Pryme Practice uses AES-256 encryption for all data at rest and TLS 1.2+ for all data in transit. Database backups are encrypted using the same standard. Encryption keys are managed using industry-standard key management practices with regular rotation.
In the event of a security incident, Pryme Practice follows the HIPAA Breach Notification Rule, which requires notification to affected individuals within 60 days of discovery, notification to the HHS Secretary, and (for breaches affecting 500+ individuals) notification to prominent media outlets. Our incident response team is available 24/7 and our BAA documents the specific notification procedures and timelines.
Pryme Practice includes role-based access controls (RBAC) that allow practice administrators to define exactly what each staff member can view, edit, and export. Roles can be customized for front desk, clinical staff, billing, and administrative users. All access events are logged in the audit trail with timestamps, user IDs, and IP addresses.
Book a free demo to see Pryme Practice's security features in action, or contact us to request a Business Associate Agreement.
Questions? Email [email protected]