Need tenant-specific help? Prepare a safe support request.Do not submit sample, client, patient, credential, report, or other regulated data
On this page

Setup object reference

Sample and Collection Setup Objects

How samples are described, collected, preserved, stored, and disposed.

Availability varies. The descriptions below explain common operational meaning. Fields, labels, permissions, and availability depend on your Clearline implementation.

Sample Matrices#

Defines the broad material or medium being tested, such as water, soil, air, or sludge.

Example

Create “Water” as the broad matrix used by drinking water, wastewater, groundwater, and surface-water Sample Types.

Core pieces
  • Name
  • Description
Connects to
Sample Types and sample classification.
Configuration guidance
Matrix is broader than Sample Type. Keep matrices stable and use Sample Types for operational distinctions.

Sample Types#

Defines an operational sample classification and the defaults applied when that kind of sample is registered.

Example

Create “Finished Drinking Water” under the Water matrix with its minimum volume, retention period, label format, and default collection rules.

Core pieces
  • Name, description, and sample-type prefix
  • Sample matrix relationship
  • Minimum volume
  • Hazard and hazard-category settings
  • Retention period and behavior where configured
  • Default container/preservation behavior through related setup
  • Allowed and default sticker/label formats
Connects to
Sample Matrices, Sample Containers, Preservations, Sample Points, Profiles, Specifications, Templates, and Samples.
Configuration guidance
Use Sample Types for operational rules, not merely for reporting labels. Changes can affect intake defaults, identifiers, container requirements, retention, and specifications.

Container Types#

Defines a broad category of container, such as Bottle, Tube, Jar, or Bag.

Example

Create “Bottle” as a broad type used by several specific glass and plastic Sample Container records.

Core pieces
  • Name
  • Description
Connects to
Sample Containers.
Configuration guidance
A Container Type is the category; a Sample Container is the specific selectable configuration. Neither necessarily tracks each physical container as inventory.

Sample Containers#

Defines a specific reusable container option used during collection and intake.

Example

Define a 250 mL sterile plastic bottle, pre-preserved with sodium thiosulfate, with an expected intact security seal.

Core pieces
  • Name and description
  • Container type
  • Capacity/volume
  • Pre-preserved status and preservation
  • Security-seal expectation
Connects to
Container Types, Sample Preservations, Sample Types, Analysis Services, and sample registration.
Configuration guidance
Include enough detail to distinguish operationally different containers. Do not imply stock-on-hand tracking unless inventory functionality is separately implemented.

Sample Preservations#

Defines preservation treatments or conditions applied to collected samples.

Example

Create “Nitric acid to pH < 2” as the preservation used for designated dissolved-metals samples.

Core pieces
  • Name
  • Description
  • Category
Connects to
Sample Containers, Sample Types, Analysis Services, partitions/aliquots, and intake requirements.
Configuration guidance
Use precise laboratory language and align preservation choices with method and container requirements.

Sample Conditions#

Defines selectable condition observations recorded when samples are received or evaluated.

Example

Create “Received above required temperature” as an observable condition recorded during sample receipt.

Core pieces
  • Name
  • Description
Connects to
Sample reception, acceptance decisions, deviations, and chain-of-custody context.
Configuration guidance
Define observable conditions, not conclusions. Pair material conditions with a documented acceptance/rejection procedure.

Sampling Deviations#

Defines standard reasons why collection did not follow the expected plan or procedure.

Example

Create “Sample collected outside scheduled window” as a standard deviation reason with occurrence-specific notes captured on the sample.

Core pieces
  • Name
  • Description
Connects to
Sample collection records, chain of custody, review, and reporting where configured.
Configuration guidance
Use clear, non-overlapping deviation reasons and preserve free-text context for the specific occurrence.

Sample Points#

Defines repeatable collection locations associated with a client or program.

Example

Create “North Plant Effluent — Outfall 001” with coordinates, permitted Sample Types, and a monthly sampling frequency.

Core pieces
  • Name and description
  • Client/location context
  • Latitude, longitude, and elevation
  • Sampling frequency
  • Allowed Sample Types
  • Composite-sample indicator
  • Reference attachment or location file
Connects to
Clients, Sample Types, sampling schedules, sample registration, maps/exports, and historical trend reporting.
Configuration guidance
Use stable identifiers and coordinates. Inactivate retired points rather than reusing a point for a different physical location.

Sample Templates#

Provides a reusable intake pattern for recurring sample configurations.

Example

Create a “Monthly Outfall” template that adds the usual services and partitions for a recurring compliance collection.

Core pieces
  • Name and description
  • Composite and laboratory-collected indicators
  • Partitions/aliquots
  • Automatic partitioning on reception
  • Included analysis services
  • Per-service hidden/override settings where enabled
Connects to
Sample registration, Analysis Services, containers/preservations, and partitions.
Configuration guidance
Templates reduce entry effort but can also replicate mistakes at scale. Validate every default against a representative intake scenario.

Storage Locations#

Defines hierarchical physical locations used to place retained samples, references, or other stored materials.

Example

Define Site “Main Lab,” Location “Cold Room 1,” and Shelf “B-03” so retained samples can be found consistently.

Core pieces
  • Site title/code/description
  • Location title/code/type/description
  • Shelf title/code/description
  • Address
Connects to
Samples, reference materials, retention, retrieval, and disposal workflows where enabled.
Configuration guidance
Use unambiguous codes that match physical labels. Moving or renaming a location should preserve historical traceability.

Next step

Return to the object map, continue through the setup journey, or contact Clearline Support for tenant-specific guidance.