Skip to main content

Security Overview

Secure by Design​

CareLaunch's product is built using a secure development process that includes:

  • Open Source Security Code Scanning: Automated analysis of code to detect vulnerabilities.
  • Automated Code Deployment and Infrastructure Provisioning: Ensures consistent and secure application updates.
  • Continuous Monitoring: Tracks environment changes and versions to identify potential risks.

CareLaunch leverages industry-leading tools to ensure HIPAA/GDPR compliance and implements robust controls to reduce risk and protect sensitive data.

PHI Overview​

Protected Health Information (PHI) is securely stored using a HIPAA-compliant cloud healthcare data store, which offers:

  • Comprehensive security controls, monitoring, and review.
  • Segregation from other resources using:
    • Identity and access management.
    • Network-level filtering.
    • Certificate-based authentication.

Cloud Providers​

CareLaunch runs on Google Cloud Platform and Amazon Web Services. Clinical records are stored in Google Cloud's Cloud Healthcare API (FHIR). Sign-in (Amazon Cognito), video visits (Amazon Chime), email (Amazon SES), and application hosting (Amazon ECS) run on AWS. Both providers offer HIPAA Business Associate Agreements.

Compliance Certifications​

Both cloud providers undergo regular independent third-party audits. The certifications and links below are Google Cloud's, which covers the data store where clinical records are kept. AWS publishes its own certifications on AWS Compliance Programs. Key Google Cloud certifications include:

Access Control​

Authentication​

  • Strong Passwords: Required for all user accounts.
  • Multi-Factor Authentication (MFA): Optional but recommended for additional security. Supports authenticator apps (TOTP) and SMS. See Setting Up MFA for setup instructions.
  • Login Protections:
    • Failed attempts logged.
    • Temporary lockout after repeated failed attempts (managed by the identity provider).
  • Session Management:
    • Sessions expire after a configurable period of inactivity (default 30 minutes). Admins can set 5 to 480 minutes with Session Idle Timeout (minutes) under Settings > Organization.
  • Advanced Security: Risk-based adaptive authentication and compromised credential detection.

User Provisioning​

  • Administrators can:
    • Provision and revoke access.
    • Revoke patient access and delete patient data.
  • Principle of Least Privilege: Access granted based on role-specific needs.
  • Role-Based Access Control: Includes roles with varying permissions (e.g., read-only, update restrictions).

Endpoint Security​

  • Web Application Firewalls (WAFs):
    • Filter malicious requests.
    • Block known bad actor IPs.
  • Country Restrictions:
    • Administrators can block patient sign-up from selected countries under Settings > Countries. The check uses the country the patient selects when registering.
  • Internal System Protections:
    • Accessible only within a secure internal network.
    • Route access restricted to approved application instances.
  • Multi-Layer Security:
    • Limited permissions and separation of responsibilities.
    • Private virtual network with restricted access.
  • Infrastructure Updates:
    • Monitored and automatically updated.
    • Changes require approval and generate alerts.

Monitoring, Logging, and Alerting​

  • Monitoring:
    • Infiltration attempts, system errors, and performance issues are actively monitored.
  • Alerting:
    • Alerts sent for configuration changes, failed logins, and system degradations.
  • Logs:
  • Backups:
    • Regularly scheduled.
    • Redundant copies for data loss prevention.

Encryption​

Encryption is implemented at multiple levels to secure data.

  • Data at Rest:
    • Stored using AES-256 encryption in our HIPAA-compliant cloud data store.
    • Data is encrypted with unique encryption keys for additional security.
  • Data in Transit:
    • Encrypted using TLS 1.2 or higher, ensuring secure user-to-platform and system-to-system communication.

Data Retention and Disposal​

  • Data Retention:
    • Data is retained until designated for deletion by the customer.
    • Access logs are not deleted on a schedule, and they are kept when the records they describe are deleted. A deleted record's access log entries stay in place and still identify the record by its ID.
  • Deletion Process:
    • Upon request, customer data other than access logs is deleted, including:
      • Demographics.
      • User information.
      • Attachments/file uploads.
      • Messaging/conversations.

Conclusion​

CareLaunch prioritizes security through:

  • Secure development practices.
  • Active vulnerability scanning.
  • Encryption for data in transit and at rest.
  • Endpoint protections and proactive monitoring.

These measures ensure sensitive data remains secure while enabling a reliable and compliant platform.