Security
Built for sensitive workflows. Designed for controlled visibility.
PatientLIENQ supports HIPAA-compliant workflows involving sensitive medical, legal, financial, lien-related, and account information.
The platform is built around HIPAA-eligible AWS services, Business Associate Agreements, encryption in transit and at rest, role-based access, tenant-level data separation, documented HIPAA security policies, and SOC 2-aligned safeguards.
Trust requires separation.
Being part of the PatientLIENQ ecosystem does not give one participant visibility into another participant's patient volume, lien portfolio, account activity, or business information.
Coordination requires shared information.
Trust requires controlled access.
PatientLIENQ is designed for both.
Controlled visibility
Controlled visibility across the ecosystem.
PatientLIENQ is built to support coordination without creating open visibility across customers, markets, organizations, or ecosystem participants.
Providers, Law Firms, Funding Institutions, and other authorized users only see information they are permitted to access based on organization, role, workflow responsibility, and configured relationships.
Foundations
Security and compliance foundations
HIPAA-eligible AWS infrastructure
PatientLIENQ uses HIPAA-eligible AWS services to support workflows involving protected health information and other sensitive data.
Business Associate Agreements
PatientLIENQ uses Business Associate Agreements with customers where appropriate for workflows involving PHI.
Encryption in transit and at rest
PatientLIENQ encrypts sensitive data in transit and at rest.
Role-based access and workflow permissions
Access is structured around user role, organization, workflow responsibility, market relationships, and authorized account access.
Tenant-level data separation
Customer data is separated by tenancy controls designed to prevent unauthorized visibility between organizations and participants.
SOC 2-aligned safeguards
PatientLIENQ is aligning its security controls and operational safeguards with SOC 2 Trust Services Criteria and is working toward SOC 2 certification.
Support
PHI-aware support and implementation.
PatientLIENQ support and implementation processes are designed to account for sensitive medical, legal, financial, and lien-related information.
Support and implementation may include user verification, issue classification, appropriate routing, PHI-aware communication, workflow permissions, account configuration, and controlled activation.
Stewardship
Responsible data stewardship.
Better information creates better decisions, but only when that information is handled responsibly.
PatientLIENQ's role is to support operational coordination across the personal injury ecosystem while maintaining disciplined access controls, clear account ownership, tenant-level separation, and responsible support practices.
Important compliance note.
Security and compliance obligations may vary by organization, market, role, and workflow.
PatientLIENQ customers remain responsible for their own legal, privacy, compliance, professional, and contractual obligations.
PatientLIENQ works with customers, counsel, and appropriate advisors to confirm required security, privacy, and compliance expectations for their use of the platform.
Questions about security or compliance?
For security, privacy, compliance, or implementation questions, contact PatientLIENQ.