BiospecimenChainOfCustodyChecker

Biospecimen Chain Of Custody

Liquid Biopsy жидкостная биопсия cfDNA ctDNA CTC exosomes NGS qPCR

Utility description: Biospecimen Chain Of Custody

Biospecimen Chain Of Custody Checker — Biospecimen Chain of Custody Verification

ℹ️ Utility performs audit of Chain of Custody (CoC) continuity according to ISO 15189, CLIA and 21 CFR Part 11 requirements:
• Signature Verification: Check for electronic or physical signature at each transfer event.
• Chronological Integrity: Guarantee of strict temporal sequence without inversions.
• Location Continuity: Automatic verification of previous "To" matching next "From".
• Time Gaps: Detection of unexplained pauses in sample movement.

⚠️ IMPORTANT:
• Chain of Custody is a legal document. Its breach questions all analysis results.
• For clinical trials, missing CoC may lead to data exclusion from regulatory submission.

Usage:
BiospecimenChainOfCustodyChecker.exe → demo mode (console output)
BiospecimenChainOfCustodyChecker.exe input.csv output.json → evaluate your data

Input format:
SampleID,EventID,EventType,EventTimestamp,FromLocation,ToLocation,HandlerID,AuthorizedBy,SignatureVerified,Comments

Example:
BS-001,EVT-001,Collection,2026-06-01 08:00,Clinic A,Clinic A,NURSE-01,,true,

📍 Scope of Application (Usage Where):
• Clinical Trials: Sample audit before data inclusion in CSR.
• Forensics and Toxicology: Confirmation of legal admissibility of evidence.
• Biobanking: Retrospective storage history verification.
• Regulatory Inspections: Demonstration of GCP/GLP compliance.

— WHY IS THIS NEEDED?
Biological samples pass through many hands and locations.
Without documented proof of each step, it is impossible to guarantee that analyzed sample truly belongs to stated subject and was not swapped or compromised.
Automated audit eliminates human factor when verifying hundreds of CoC records.

⚠️ CRITICAL:
• Signature: Missing signature at transfer = chain break.
• Chronology: Timestamp inversion indicates entry error or falsification.
• Location Link: Location mismatch means loss of traceability.
• Time Gaps: Long unexplained pauses require investigation.

Key features:
• Multi-level verification (Signature → Time → Location)
• Automatic detection of logical inconsistencies
• Chain status classification (Intact/Broken/Incomplete)
• Detailed audit report generation
• Compliance with 21 CFR Part 11 (Electronic Records)

Critical parameters:
• Signature Verified: True for all transfers
• Chronology: Strictly ascending
• Location Continuity: Prev.To == Curr.From
• Time Gap: < 72h or justified

💡 Usage tips:
1. Electronic Signatures: Use audited systems (LIMS/EDC) instead of paper forms.
2. Training: Personnel must understand legal significance of each record.
3. Comments: Require mandatory explanation for any non-standard situations.
4. Regular Audit: Conduct CoC checks not only during issues but also routinely.
5. Archiving: Retain CoC records as long as samples/data themselves.

⚠️ Note: This utility is a documentation audit tool. It does not replace physical sample integrity check but guarantees reliability of its documentary history.

input.csv

SampleID,EventID,EventType,EventTimestamp,FromLocation,ToLocation,HandlerID,AuthorizedBy,SignatureVerified,Comments
BS-2026-001,EVT-001,Collection,2026-06-01 08:00:00,Clinic A,Clinic A,NURSE-01,,true,
BS-2026-001,EVT-002,Transfer,2026-06-01 10:00:00,Clinic A,Courier X,COURIER-01,NURSE-01,true,
BS-2026-001,EVT-003,Receipt,2026-06-01 14:00:00,Courier X,Central Lab,LAB-TECH-01,,true,
BS-2026-002,EVT-004,Collection,2026-06-02 09:00:00,Clinic B,Clinic B,NURSE-02,,true,
BS-2026-002,EVT-005,Transfer,2026-06-02 11:00:00,Clinic B,Courier Y,COURIER-02,,false,Missing signature scan
BS-2026-002,EVT-006,Receipt,2026-06-02 15:00:00,Courier Y,Central Lab,LAB-TECH-02,,true,

URS & FS — User Requirements and Functional Specification

This document describes the controlled interface and behaviour of BiospecimenChainOfCustodyChecker for Biospecimen Chain Of Custody Checker.

Domain limits URS input.csv FS IQ/OQ/PQ

Domain limits and critical parameters

Key fragments from the source description are shown below. Before production use, limits must be verified against the approved specification, registration dossier and local SOPs.

ℹ️ Utility performs audit of Chain of Custody (CoC) continuity according to ISO 15189, CLIA and 21 CFR Part 11 requirements:
⚠️ CRITICAL:
Critical parameters:
• Time Gap: < 72h or justified
2. Training: Personnel must understand legal significance of each record.

URS — User Requirements Specification

ID	Requirement	Criticality	Acceptance criterion
URS-001	The utility shall accept an input.csv file for Biospecimen Chain Of Custody Checker with headers defined in the data contract.	High	The file is processed without manual header editing.
URS-002	The utility shall perform deterministic QC evaluation without machine learning and without probabilistic conformance decisions.	High	Identical input data, rule version and configuration produce reproducible results.
URS-003	The utility shall validate mandatory fields, data types, ranges, units and domain plausibility.	High	Schema, conversion and range errors are explicitly reported.
URS-004	The utility shall apply domain limits and rules from the description, approved specification, registration dossier and local SOPs.	High	Each check has PASS/WARNING/FAIL and a clear message.
URS-005	The utility shall generate output.json with machine-readable results, source values, warnings, failures and critical findings.	High	JSON is suitable for LIMS/ELN/MES integration and QA/QC review.
URS-006	The utility shall preserve traceability between batch/sample, input file, applied rules and final status.	High	Output contains identifiers, checked parameters and audit metadata.
URS-007	The documentation shall support IQ/OQ/PQ, CSV/CSA and review by internal QA or inspectors.	Medium	URS, FS, input/output contract and test scenarios are supplied with the utility.
URS-008	The utility shall be used as a QC decision-support tool and not as a substitute for approved specifications and QA/QP release decision.	Medium	Documentation states change control and limit-verification expectations.

input.csv contract

#	Field	Type	Sample	Purpose
1	`SampleID`	string / controlled vocabulary	`BS-2026-001`	Sample or laboratory specimen identifier.
2	`EventID`	string / controlled vocabulary	`EVT-001`	Controlled input parameter for deterministic QC rules.
3	`EventType`	string / controlled vocabulary	`Collection`	Controlled input parameter for deterministic QC rules.
4	`EventTimestamp`	string / controlled vocabulary	`2026-06-01 08:00:00`	Time parameter for process, incubation, storage or analytical workflow.
5	`FromLocation`	string / controlled vocabulary	`Clinic A`	Controlled input parameter for deterministic QC rules.
6	`ToLocation`	string / controlled vocabulary	`Clinic A`	Controlled input parameter for deterministic QC rules.
7	`HandlerID`	string / controlled vocabulary	`NURSE-01`	Controlled input parameter for deterministic QC rules.
8	`AuthorizedBy`	string / controlled vocabulary		Controlled input parameter for deterministic QC rules.
9	`SignatureVerified`	string / controlled vocabulary	`true`	Controlled input parameter for deterministic QC rules.
10	`Comments`	string / controlled vocabulary		Controlled input parameter for deterministic QC rules.

SampleID,EventID,EventType,EventTimestamp,FromLocation,ToLocation,HandlerID,AuthorizedBy,SignatureVerified,Comments
BS-2026-001,EVT-001,Collection,2026-06-01 08:00:00,Clinic A,Clinic A,NURSE-01,,true,
BS-2026-001,EVT-002,Transfer,2026-06-01 10:00:00,Clinic A,Courier X,COURIER-01,NURSE-01,true,
BS-2026-001,EVT-003,Receipt,2026-06-01 14:00:00,Courier X,Central Lab,LAB-TECH-01,,true,

Input validation rules

ID	Field	Rule	Criticality
VR-001	`SampleID`	The field shall match an approved dictionary or accepted string representation.	High
VR-002	`EventID`	The field shall match an approved dictionary or accepted string representation.	High
VR-003	`EventType`	The field shall match an approved dictionary or accepted string representation.	High
VR-004	`EventTimestamp`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-005	`FromLocation`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-006	`ToLocation`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-007	`HandlerID`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-008	`AuthorizedBy`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-009	`SignatureVerified`	The field shall match an approved dictionary or accepted string representation.	Medium
VR-010	`Comments`	The field shall match an approved dictionary or accepted string representation.	Medium

FS — Functional Specification

ID	Function	Implementation
FS-001	CLI execution	Support execution modes: demo mode without arguments and production mode input.csv output.json.
FS-002	CSV import	Read input.csv in UTF-8/CSV-compatible format and validate header and expected columns.
FS-003	Schema validation	Check mandatory fields, column count, unknown key fields and empty mandatory values.
FS-004	Type conversion	Convert numeric, flag and text values; invalid format is recorded as a row-level error.
FS-005	Domain rule engine	Apply rules for Biospecimen Chain Of Custody Checker, including critical limits from the description and approved specification.
FS-006	Status aggregation	Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance.
FS-007	JSON export	Write output.json with detailed checks, source values, warnings, failures and critical findings.
FS-008	Audit support	Keep result structure suitable for review, deviation investigation and calculation reproduction.
FS-009	Integration contract	Support the scenario LIMS/ELN/MES → input.csv → utility → output.json → portal/admin review.
FS-010	Error handling	Return explicit messages for missing file, empty CSV, invalid schema, output write failure and invalid format.

Example output.json

{
  "utilityId": "biospecimenchainofcustodychecker",
  "utilityFolder": "BiospecimenChainOfCustodyChecker",
  "package": "LiquidBiopsy",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "processedAtUtc": "2026-06-10T00:00:00Z",
  "checks": [
    {
      "parameter": "SampleID",
      "value": "BS-2026-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-001"
    },
    {
      "parameter": "EventID",
      "value": "EVT-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-002"
    },
    {
      "parameter": "EventType",
      "value": "Collection",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-003"
    },
    {
      "parameter": "EventTimestamp",
      "value": "2026-06-01 08:00:00",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-004"
    },
    {
      "parameter": "FromLocation",
      "value": "Clinic A",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-005"
    },
    {
      "parameter": "ToLocation",
      "value": "Clinic A",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-006"
    },
    {
      "parameter": "HandlerID",
      "value": "NURSE-01",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-007"
    },
    {
      "parameter": "AuthorizedBy",
      "value": "",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-008"
    },
    {
      "parameter": "SignatureVerified",
      "value": "true",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-009"
    },
    {
      "parameter": "Comments",
      "value": "",
      "status": "PASS|WARNING|FAIL",
      "message": "Deterministic rule-based check result",
      "ruleReference": "FS-RULE-010"
    }
  ],
  "criticalFindings": [],
  "warnings": [],
  "audit": {
    "inputHash": "sha256:<calculated at runtime>",
    "rulesVersion": "<utility executable version>",
    "documentation": "BiospecimenChainOfCustodyChecker.documentation.html"
  }
}

Traceability matrix

URS	FS	Test	Evidence
URS-001	FS-001, FS-002	OQ-001	Verify execution and import of valid input.csv.
URS-002	FS-005, FS-006	OQ-004	Repeat the same dataset and compare output.json.
URS-003	FS-003, FS-004, FS-010	OQ-002, OQ-003	Verify missing columns and invalid types.
URS-004	FS-005, FS-006	OQ-004, PQ-001	Verify critical deviations on real/boundary data.
URS-005	FS-007, FS-009	OQ-005	Verify JSON schema and downstream-system suitability.
URS-006	FS-008	OQ-006	Verify identifiers and audit metadata.
URS-007	FS-008, FS-010	IQ-001, OQ-007	Verify documentation completeness and control evidence.
URS-008	FS-005, FS-008	PQ-002	Verify review workflow and no replacement of QA decision.

IQ/OQ/PQ test scenarios

ID	Scenario	Expected result
IQ-001	Verify executable, input.csv, documentation and checksum availability.	Delivery set is complete; version is recorded.
OQ-001	Valid sample row from input.csv.	PASS or acceptable WARNING according to rules.
OQ-002	Remove a mandatory CSV column.	Schema error or FAIL with missing-column reference.
OQ-003	Place a non-numeric value into a numeric field.	Type-conversion error with row/field reference.
OQ-004	Set a critical parameter outside the limit.	FAIL and critical finding.
OQ-005	Verify output.json structure.	All mandatory sections are present and JSON is valid.
OQ-006	Verify batch/sample traceability.	Input and result identifiers match.
PQ-001	Verify 3–5 real user batches/samples.	Result is confirmed by QC/QA review.
PQ-002	Verify deviation workflow and manual QA decision.	Utility supports review but does not replace approved decision.

QA/QC and change control

Do not rename columns without updating validator, documentation and test set.
Retain input.csv, output.json, executable version and checksum.
Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
Critical limits shall be verified against the approved specification, registration dossier and local SOPs.
The utility provides structured QC decision support; final release decision remains with QA/QP and approved procedures.

Included in packages

Liquid Biopsy QC Suite

QC and pre-analytical control package for liquid biopsy workflows: cfDNA/ctDNA, CTC, EV/exosomes, methylation, NGS/qPCR/ddPCR, sample quality, contamination, sensitivity and reporting checks.

Open