Designed for HIPAA. Built for CMS Auditors.

Buddee runs alongside your EHR in a shadow-mode architecture: AI surfaces suggestions, clinicians approve them, and every decision is designed to be appended to a SHA-256 hash-chained audit log. By design, nothing is submitted to a payer without an explicit human action — a clinician approval gate sits in front of every suggestion.

AES-256

At rest

TLS 1.3

In transit

SHA-256

Hash chain

Human-Gated

No auto-submit

Target architecture controls. Encryption at rest is provider-managed; hash-chain and verification tooling are described as design, not a completed certification.

Compliance Controls

The controls below describe Buddee's target production architecture and current posture. Independent attestation is planned, not yet complete; status notes are called out inline.

HIPAA

Administrative Safeguards
Physical Safeguards
Technical Safeguards
Workforce Training Program
Sanction Policy
Information Access Management

CMS

Hash-Chained Audit Design
Shadow-Mode Architecture
No Auto-Submit
Built to CMS-HCC v28 Coding Logic
Documented Evidence Linkage
Clinician Approval Gating

Operational

API Key Authentication
Rate Limiting
Tenant Isolation (by design)
Encrypted Backups (provider-managed)
Penetration Testing (planned)
Vendor Management (in progress)

HIPAA Architecture Overview (PDF)

A technical brief describing data flow, encryption layers, audit-chain mechanics, and control mapping is available during security review.

Download PDF

We Sign a Business Associate Agreement

Every Buddee deployment is governed by a Business Associate Agreement before any PHI may be processed. The BAA enumerates permitted uses, required safeguards, breach notification obligations, and termination rights consistent with 45 CFR 164.504(e).

Request BAA Template →

Compliance FAQ

The questions security teams ask most often during diligence.

Download Security Overview

Incident Response

The process below describes Buddee's designed incident-response workflow for production deployments. Timelines are targets defined per agreement.

Detect

Designed for continuous log aggregation, anomaly detection on the audit chain, and an on-call rotation. Mean time to detect target: under 15 minutes for chain integrity errors.

Contain

Tenant-scoped key revocation, write-path freeze on the affected tenant, and forensic snapshot of the hash chain prior to investigation.

Notify

Customer security contact notified within 24 hours of confirmation. HIPAA breach notification follows 45 CFR 164.404 timelines if applicable.

Security Contact

Reach the Buddee security team at security@trybuddeeai.com.

PGP key available on request for coordinated disclosure.

For coordinated disclosure see /.well-known/security.txt.