Laboratory samples

lims is a small laboratory information system: samples come in, methods measure them against limits, and a result outside the limits opens a case before the sample can be released.

better-supabase add lims

import { createLims } from "better-supabase/blocks/lims";

The module requires memberships, permissions and subjects. With forms a method can name the form that captures its readings. With cases an out of specification result opens a nonconformity. With assets and qualifications an instrument is an asset that must hold a valid qualification on the test date. With numbering samples get the numbering block's format, outbox records the events and audit audits every change.

TablesCopy Anchor Link

A sample is a subject of type lims_sample.

Methods and samplesCopy Anchor Link

saveMethod creates a method, or updates the one you pass as the second argument. The key cannot change. A result below lowerLimit or above upperLimit is out of specification, and a method with no limit accepts every value on that side.

const lims = createLims({ transport, tenant: organizationId });

const ph = await lims
  .saveMethod({ key: "ph", name: "pH", lowerLimit: 6.5, upperLimit: 7.5 })
  .orThrow();

const sample = await lims
  .registerSample({ title: "Batch 12", lot: "L-12" })
  .orThrow();

A sample is registered, then in_testing once the first result arrives, completed when testing ends, and finally released or rejected.

ResultsCopy Anchor Link

recordResult checks the value against the method's limits and stores the outcome. The first result moves the sample into testing. A sample accepts results while it is registered or in testing.

const result = await lims
  .recordResult(sample.id, ph.id, { value: 8.2, instrumentId: balanceAssetId })
  .orThrow();
// result.outcome is "out_of_spec"; result.caseId is the nonconformity case

An out of specification result opens a case of the nonconformity kind (options.nonconformityKind renames it) with the sample, the method, the value and the limits in its description, and emits lims_result.flagged. The case uses the source lims when the cases block lists it in options.sources, and internal otherwise.

With options.instrumentQualification: "calibration" a result needs an instrumentId, the instrument must be an asset of the organization, and it must hold that qualification on the test date. instrumentStatus answers the same question before the work starts.

const status = await lims.instrumentStatus(balanceAssetId).orThrow();
// { instrumentId, required: true, qualified: true }

ReleaseCopy Anchor Link

completeSample ends testing. releaseSample needs lims.manage and refuses while the latest result of any method is out of specification. rejectSample takes a reason and works on a sample that is not released.

ErrorsCopy Anchor Link

EventsCopy Anchor Link

The hooks are before_lims_sample_register, after_lims_sample_register, before_lims_result_record and after_lims_result_record.

Without the clientCopy Anchor Link

save_lims_method(tenant, input, method_id), archive_lims_method(method_id), list_lims_methods(tenant, include_archived), register_sample(tenant, input), get_sample(sample_id), list_samples(tenant, filters), record_lims_result(sample_id, method_id, input), complete_sample(sample_id), release_sample(sample_id), reject_sample(sample_id, reason) and instrument_status(tenant, asset_id, on_date) are plain SQL functions. In custom mode you implement them over your own tables.