QuickSupply
Controlled-substance accountability · Available now

The medication story, reconstructed from events.

LockBox is an accountability ledger that calculates inventory—not a quantity field with an activity log attached. Receiving, custody, movement, administration, waste, counts, discrepancies, and final disposition become immutable linked events.

Inside LockBox

Ledger integrity and operational readiness stay visible together.

LockBox overview showing medication inventory, ledger events, discrepancy status, and operational readiness
Accountability overview. Medication lots, serialized containers, ledger events, a discrepancy, and loadout follow-up are visible at a glance in the synthetic demo.Open full-size view ↗
The accountability loop

Every action starts with location and ends with proof.

LockBox validates the current ledger state again at commitment, rejects stale or contradictory actions, and preserves the signed event that changed the record.

01 / ACQUIRE

Receive and serialize

Record the source, registration, destination, product version, lot, expiration, vial, and dual-signed batch.

02 / SECURE

Place and transfer custody

Keep physical location separate from human responsibility, with counts and signatures at handoff.

03 / ACCOUNT

Administer or waste

Link the patient-care event and require the complete vial balance to be explained before commit.

04 / VERIFY

Count and investigate

Compare physical findings to ledger expectations, open discrepancies, and retain the resolution trail.

Feature depth

Accountability is the architecture.

Critical controls live inside the transaction itself: identities, signatures, locations, expected state, timestamps, serialized medication, and the resulting ledger event.

01 / LEDGER

Inventory derived from immutable events

Every received package becomes a serialized container with a ledger-derived balance. Completed events are not edited or deleted.

  • SHA-256 chained medication events
  • Product-version, lot, and expiration grouping
  • Corrections create linked events
02 / SIGNATURES

Independent people sign the same action

Configured workflows require a different authenticated user and retain both identity snapshots, the signed payload hash, and separate signatures.

  • Actor cannot witness their own action
  • Witness access revalidated at commit
  • Signed confirmation visible from history
03 / RECEIVING

Atomic multi-lot acquisition

Receive up to 50 medication and lot lines and 250 vials in one batch while still serializing every vial and creating every ledger event.

  • Shipment-level details entered once
  • One invalid line rejects the full batch
  • Idempotency prevents duplicate receipt
04 / CUSTODY

Physical location and human custody stay distinct

A vault handoff includes a complete medication count, explicit verification of every expected vial, recipient reauthentication, and two signatures.

  • Person-to-person responsibility change
  • Signed storage-location movements
  • Required destination count after movement
05 / USE & WASTE

Account for the entire vial

Select eligible serialized items from one location and record separate administered and wasted amounts for the shared patient-care event.

  • Expired medication blocked from administration
  • Atomic stale-balance protection
  • Post-action full-location verification required
06 / COUNTS

Physical counts do not silently change inventory

Users enter medication totals before seeing serial prompts, verify every expected vial, review mismatches, and sign the exact snapshot.

  • Contradictory or incomplete counts rejected
  • Mismatch opens a discrepancy case
  • Resolution states its ledger effect before commit
07 / NARCOTIC BOXES

Expected loadouts without fictitious inventory

Version box loadouts, compare expected to actual serialized contents, replenish shortages from eligible stock, and retain placement and seal history.

  • Portable sealed or internal-storage mode
  • Two-person seal verification
  • Complete-box placement movement
08 / DISPOSITION

Quarantine through final disposition

Move serialized vials through quarantine, release, destruction holding, witnessed destruction, or reverse distribution in controlled batches.

  • Lifecycle-state validation at commit
  • Dual authentication and signatures
  • Certificate or manifest evidence with digest
Operational depth

Designed to reject an impossible story.

LockBox treats contradictions, stale balances, missing signatures, and unexplained medication as blocking conditions—not warnings someone can click past.

01
Conservation of quantityAdministered amount plus waste must account for the selected vial's complete ledger balance.
02
Server-generated operational timeCritical event timestamps are assigned at commit and are not supplied, backdated, or edited through the form.
03
Append-only investigationsDiscrepancies retain findings, reviews, resolution, reopening, and any explicit signed ledger disposition.
04
Actionable readiness queuesSurface expiring medication, registration deadlines, open discrepancies, destination counts, and post-action verifications.
Built for controlled access

Different responsibilities, one signed record.

Clinicians & custodians

Work from location-first medication views, complete guided counts, and sign the exact action being committed.

Supervisors

Review open discrepancies, custody state, required verifications, expiring medication, and signed transaction detail.

Compliance administrators

Manage registrations, medication products, secure locations, witness policies, lifecycle records, and audit exports.

See LockBox in context

Bring us a custody, count, or discrepancy workflow.

We will walk through the identities, signatures, state checks, and ledger events behind the operational action.

Call 833-511-5002