Skip to content
Apex Flow

Trust & security

Facts you can verify. Not badges.

Below is exactly what we have done to protect your data and what an independent party can confirm.

How your data is handled

The data rules, in plain language.

A BAA before any data moves

We sign a Business Associate Agreement, built on HHS OCR's own model language, before we handle any identifiable claim data. No signature, no data. Our client BAA is public: read it clause by clause.

De-identified by default

The only artifact meant to leave your environment is a de-identified aggregate: dollar ranges, payer families, denial codes. No patient name, date of service, claim number, or ZIP. A Safe Harbor gate blocks the file from being written if any identifier is detected.

Every vendor is under a BAA

Microsoft 365, Office Ally, and Amazon Web Services: every system that could touch claim data operates under a signed Business Associate Agreement. Certificates available on request.

Encrypted, logged, and human-accountable

Devices are BitLocker-encrypted. Access to protected data is written to a tamper-evident log (45 CFR 164.312(b)). The engine recommends; a human makes every final billing decision. Nothing auto-executes.

Where your data lives

Your building. Your server.

With a local KAIS installation, patient data lives on your machine, connections run on your own logins, and the license is checked on the machine. Synthetic data.

What you can verify today

Checkable facts, with the receipts.

✓ Verifiable

$2M insurance in force

$1M professional liability + $1M cyber, underwritten by a Berkshire Hathaway company. Certificate on request.

✓ Verifiable

HIPAA Security Risk Analysis

Completed and signed before any client data moved.

✓ Verifiable

Hardened transport & headers

HSTS-enforced TLS, strict security headers, content security policy. Grade it yourself: Mozilla Observatory or SSL Labs.

✓ Verifiable

More than 2,000 automated checks

Four internal suites (engine self-check, adversarial crucible, claim scrubber, denial-logic eval) run before a build ships, more than 2,000 checks across all 297 active CARC denial codes. Run on every build before it ships.

✓ Verifiable

Adversarial stress harness

A hostile integration test plants fake identifiers, corrupt files, and lock contention at the real engine and confirms it fails safe. We can run it live in a demo.

✓ Verifiable

AMA CPT® license executed

KAIS holds a CPT Data Files License Agreement with the American Medical Association, executed August 2026, covering the CPT content the product displays; every CPT descriptor in the product carries the AMA's copyright notice. CPT is a registered trademark of the American Medical Association.

Where the rules come from

Every rule carries the edition it came from.

A rule engine is only as current as the files behind it, whether it runs hosted or as the offline edition on the practice's own machine. So KAIS reads each shipped dataset's own provenance and computes whether it is the edition in force, rather than trusting a stamp. The answer is on a screen in the product, and it is on this site, generated from the same tables: CMS coding edits, fee schedules, code sets, coverage determinations, drug pricing and the payer rule library, each with the edition, the date it took effect and the publisher it came from.

See what KAIS is running right now

Diligence

Evaluating us for a partnership or license?

We keep a diligence pack ready: security posture, the engine's own test and stress-test output, our SRA attestation, and the full BAA list. Ask and we send it same day.