Healthcare AI with the gates stated up front

Honesty first: how Bee gates healthcare

Healthcare is a Tier-3 restricted domain on Bee. Healthcare workflows require explicit acknowledgement, may carry jurisdictional gates, and operate under your regulatory regime - Bee is a tool, and the platform says so in its Acceptable Use Policy rather than burying it.

That design is deliberate: organisations that answer to regulators need a vendor whose defaults are conservative and whose claims are checkable.

Where the platform does the heavy lifting

• →Document intelligence over policy manuals, research literature, and administrative documentation, with cited answers.
• →1M-token long-context on Comb and Buzz for reasoning across large document sets in one request.
• →Vision input on Comb, Buzz, and Hive for scanned forms and document images in administrative workflows.
• →JSON mode for schema-valid extraction into downstream systems.
• →Team workspace with pooled tokens, so departments share one governed deployment instead of shadow AI accounts.

Deployment and compliance posture

Protected-health-information workloads require a separately scoped engagement. Enclave designs start from $15,000/mo; identity, audit, key, residency, and HIPAA-related controls must be fixed contractually. Bee does not imply unheld SOC 2 or ISO 27001 certification.

Data handling follows the published DPA: TLS 1.3 in transit, AES-256-GCM at rest under per-tenant keys, breach notification within 72 hours, and sub-processors disclosed in Schedule A.

Data protection across jurisdictions

HEOSSI (Pte.) Ltd. is incorporated in Singapore and processes under the PDPA; the DPA extends coverage to GDPR and UK GDPR with EU Standard Contractual Clauses for transfers. Hive-plan and above customers can request region-pinned processing.

Tenant-scoped controls, encrypted transport, and governed release gates protect production workloads across Bee's hosted and private deployment paths.