Skip to main content

Laboratory data

Laboratory data in Erde covers the analytical record from receipt to validation: the Lab Report the laboratory issues, the Lab Analyses that group its runs, the individual Lab Results those runs produce, and the validator's later review of each result. This section is for the staff who load laboratory deliverables and the Data Stewards who validate them.

Most laboratory data arrives through Import, not hand entry — a parsed deliverable creates the report, its samples, analyses, and results in one pass. The pages here describe what that data looks like once it lands and how you review it.

In this section

  • Lab reports — the report header: its Code (unique per Project), assigned laboratory, dates, and the five-value status lifecycle (Draft, Preliminary, Approved, Rejected, Validated).
  • Lab analyses and results — how a report groups analyses by Method, Matrix, and fraction, and the result fields: value or text, qualifiers, detection limits, and non-detect handling.
  • Manage lab data — create, edit, and delete reports, their analyses, and results; change report status; and the dependency rules that block a delete.
  • Validate lab results — the field-sample validation workflow: applying a validated qualifier, overriding values, and gating validation behind Approved report status.
  • Manage lab report samples — record the report's field and laboratory quality-control samples that analyses anchor to.
  • Manage lab batches — record the report's preparation, leach, and analysis batches and assign each analysis its typed batches for quality-control traceability.
  • Record QC and radiochemistry results — add spike, recovery, and control-limit detail, and radiochemistry measurements, to a result.
  • Lab data reference — the field-by-field tables for lab reports, analyses, and results, with the status, run type, fraction, basis, and result type values listed inline, plus the detection-limit, quality-control, and radiochemistry field details. The full validation-level and quality-control-type code tables live in Enumerations and codes.
  • Qualifiers — the application-wide reference data that defines what each lab-result qualifier code (J, U, R, UJ, and the like) means and how it propagates when results combine.

How laboratory data is structured

A report sits under its Project, groups its analyses, and each analysis carries its own results. Validation attaches to a result as a separate record.

Figure: A Lab Report groups analyses; each analysis carries results; a validation record attaches to a result at most once.

info

Validation applies to field-sample results only. Laboratory quality-control results (method blanks, spikes, and duplicates) are recorded and reviewed but are never validated.