In development. This page describes the intended architecture and planned workflows. Organization administration and policy authoring are implemented; managed client delivery and regulated workflows are not available end to end. See current availability.

Healthcare

AI that respects the chart

Healthcare Data Mode is in development for regulated workflows. In the planned design, when it is enabled under a qualifying contract, potential protected health information is evaluated on the device before anything is transmitted, and cloud destinations require explicit organizational approval backed by a BAA process.

Planned Healthcare Data Mode workflow

  1. Your organization contracts Enterprise Regulated and BAA eligibility is established.
  2. Onboarding and compliance review are completed with our team.
  3. Administrators approve specific destinations — provider, model, endpoint, region — with BAA status recorded per organization.
  4. Security admins publish a signed policy; enrolled devices enforce it.
  5. Unknown or unapproved cloud destinations are blocked by default.

What the product says — and doesn't say

  • The UI reports “Potential PHI detected” with safe, masked labels — it never claims automated de-identification.
  • Tokenization is pseudonymization/data minimization for the current flow. It is not HIPAA Safe Harbor de-identification and does not by itself make data non-PHI.
  • Detection is a layered heuristic ensemble. It reduces exposure; it is not a guarantee of complete PHI detection.
  • BAAs are tracked as records (state, dates, document, owner) for approved destinations. A recorded BAA reflects a signed agreement, not a legal opinion on your compliance program.

Availability

Healthcare Data Mode is not currently available end to end. Its planned activation requires an Enterprise Regulated contract with BAA eligibility plus a completed onboarding review. See Enterprise Regulated and contact sales to start the process.