New: Orthotics and Prosthetics intake is live. See the O&P solution
Trust and security

Auditable by design, not by promise.

Darby is built for a regulated buyer. Decisions trace to a source, reference data carries its provenance, patient data stays inside our trusted boundary, and the compliance work can be verified by an outsider. Here is exactly how.

The trust commitments
1

Every decision traces to a source

Routine decisions are deterministic rules citing a regulation or a federal dataset, not a model's opinion.

2

No fabricated data, anywhere

Every reference value traces to a published source with a recorded date. We do not invent numbers, in the product or on this site.

3

Your patient data stays inside the boundary

Protected health information stays within our trusted infrastructure. We do not route it through third-party services to get the work done.

4

Isolated by tenant at the database

Each organization's data is isolated in the database itself, not only in application code.

5

Reproducible compliance

Audit sampling is seeded so an external auditor can re-derive the same sample. Compliance you can check, not take on faith.

6

A record for every order

The Verification Record gives an auditor the source, the checks, and the steps behind every result, signed and tamper-evident.

For your IT reviewer

The documents a security team asks for, in one place.

HIPAA postureDocumented
Business Associate AgreementAvailable on request
Where data livesInside the boundary
Subprocessor listPublished
Tenant isolationDatabase level
Request the security overview

Subprocessors

The named services that touch data are listed for your vendor review, each with its role. Enterprise buyers expect this inventory, so it is public.

The reason to trust the rest of the platform is that none of it asks you to trust a black box.