All work

Workflow systems · Client portalsDemo system

Autom8 Diagnostics Lab

Clinical and contract testing laboratories

Sample intake, testing, a three-stage result release, reporting, and a portal where customers collect their own results.

The bottleneck

A diagnostic result that reaches a patient early cannot be recalled. The damage is done the moment it is read. Most laboratory software treats the release step as a status field, which means any import, any batch job, or any administrator with the right permission can move a result to released without a person having looked at it.

  • Autom8 Diagnostics Lab: Home

    Home

  • Autom8 Diagnostics Lab: Services

    Services

  • Autom8 Diagnostics Lab: Staff sign-in

    Staff sign-in

What we built

  • Sample intake, testing and reporting for both clinical and contract work
  • A three-stage release: entered_by, then verified_by, then signed_by, always in that order
  • A single code path permitted to write results.status, in lib/pipeline/advance.ts
  • The rule enforced in five independent layers, so no one layer is the only thing holding
  • A customer portal where clients collect their own released results

What changed

  • There is no cron, import, batch job or admin override that can advance a result
  • Three distinct people have signed anything a customer can read
  • The constraint is in the schema, not in a policy document nobody reads
Built with
Next.js 16
Built with
TypeScript strict
Built with
PostgreSQL 17
Built with
Tailwind 4

Have a process like this one?

The consultation is free. If software is not the right fix, we will say so.

Free consultation