Self-hosted laboratory platform

From sample to certificate. Every record, one platform.

CHERT LIMS follows every sample from reception through testing, quality control and review to a signed certificate, on one hash-chained record. Built for your own servers, in Arabic and English, and every capability on this page shows its verification status.

Lifecycle stages
8
Platform layers
4
Statements verified
37
Languages
2

The sample lifecycle

Every sample follows the same journey. CHERT LIMS keeps all of it on one record.

Eight stages, from the order to the retained certificate. Select a stage to see what happens, which parts of CHERT LIMS do the work, and what is available today.

Stage 01 / 08

Order & specify

Agree what will be tested

Clients, sample types and tests are controlled master data. Versioned methods and specifications carry the decision rules applied when a result is entered.

Runs on

Status today

  • Sites, departments, clients, sample types and tests kept as controlled master data with stable identifiers.Verified in testing
  • Versioned methods and specifications, test packages, and decision rules evaluated when a result is entered.Verified in testing

Stage 02 / 08

Receive

Register and label every sample

Each sample is registered with its condition on arrival and gets a Code 128 label you can find or scan later, from any screen.

Runs on

Status today

  • Code 128 sample labels, find by label, and camera scanning where the device supports it.Verified in testing
  • Bench and field capture on any screen size that queues while offline and replays safely; final approvals are never made offline.Verified in testing

Stage 03 / 08

Custody & storage

Know where every sample is

Storage locations, transfers, aliquots and disposal with a reason, each step on an append-only custody trail; reagent lots and expiry are tracked alongside.

Runs on

Status today

  • Registration, reception with condition, storage locations, transfers, aliquots and disposal with a reason, each step on an append-only custody trail.Verified in testing
  • Reagent and reference-material lots, expiry, preparations with their genealogy, and consumption per worksheet.Verified in testing

Stage 04 / 08

Test

Run the method as written

Work queues put urgent work first. Guided execution follows the exact effective procedure revision, and instrument files are captured with their hash.

Runs on

Status today

  • Work queues by test with urgent work first, and worksheets created from the queue.Verified in testing
  • Guided execution bound to the exact effective procedure revision, with equipment and lot checks, computed calculation steps and witnessed signatures.Verified in testing
  • Instrument files captured by upload or watch folder; original bytes kept with a hash, parser version and lineage, and values reviewed before they become results.Verified in testing
  • Analyser messaging over ASTM and HL7, built and tested in simulation only; awaiting a real analyser.Awaiting external qualification — not yet available

Stage 05 / 08

Quality control

Show the run is in control

Blanks, controls and duplicates are evaluated against limits. A failed control holds review, and an out-of-specification result opens an investigation.

Runs on

Status today

  • Blanks, controls and duplicates placed on worksheets, evaluated against limits, with control charts.Verified in testing
  • A failed control holds the worksheet's review until a reviewer records a disposition.Verified in testing
  • Automatic out-of-specification and out-of-trend investigations; the original result is preserved and retests need a justified, authorised count.Verified in testing

Stage 06 / 08

Review

A second person verifies

Results carry units, precision and validated calculations, and are verified by a second, authorised person. A withdrawal keeps the history.

Runs on

Status today

  • Result entry with units, precision and rounding, validated calculation versions, and verification by a second person; a withdrawal keeps the history.Verified in testing
  • Training records, acknowledgements and validity; task authorisation is enforced when results are entered and verified.Verified in testing

Stage 07 / 08

Certify

Issue the certificate, signed

Certificates are issued in Arabic and English from frozen, hashed snapshots and signed after signing in again, with the Hijri date beside the Gregorian.

Runs on

Status today

  • Certificates of analysis issued from frozen, hashed snapshots; issuance fails closed, amendments create new versions and the original is retained.Verified in testing
  • Electronic signatures require signing in again and are bound to the hash of exactly what was signed.Verified in testing
  • Bilingual Arabic and English certificates rendered on A4.Verified in testing
  • Umm al-Qura Hijri dates beside the authoritative Gregorian date on screens and certificates, checked from 2020 to 2029.Verified in testing

Stage 08 / 08

Amend & retain

Keep every version and its evidence

An amendment creates a new version and the original is kept. Evidence is verified by hash on every read, and the audit chain survives a restore.

Runs on

Status today

  • Every change is written to a hash-chained, append-only audit trail, and the chain is re-verified after a restore.Verified in testing
  • Evidence files are stored by content address and checked against their hash when read.Verified in testing
  • Every document revision is kept by the documents engine, and every file's hash is unchanged after a restore drill.Verified in testing

Interactive architecture

Every layer of the laboratory — and the CHERT component that runs it

Select any component to see what it does and its status, or play a journey and watch a sample move through the platform.

Select a component or play a journey.
01

Laboratory bench & instruments

Where samples are labelled, captured and measured.

02

Integration & edge

One guarded entrance, and events that carry every change.

03

Laboratory platform & records

The engines that hold samples, documents, evidence and the audit trail.

04

Quality, insight & customers

Where people review, report, search and share results.

S

Security & identity

One sign-in, authorised people only.

O

Operations & resilience

Installing, backing up and restoring on your own servers.

Component status

  • Verified in testing
  • In validation — not yet available
  • Awaiting external qualification — not yet available

Details appear in the panel above the diagram.

Why CHERT LIMS

Built to be relied on, record by record

One record, end to end

Every change lands on one hash-chained audit trail.

  • Every change is written to a hash-chained, append-only audit trail, and the chain is re-verified after a restore.Verified in testing

Evidence you can check

Files, certificates and signatures are bound to their hashes.

  • Evidence files are stored by content address and checked against their hash when read.Verified in testing
  • Electronic signatures require signing in again and are bound to the hash of exactly what was signed.Verified in testing

Your own servers

Built to install privately, including without internet access.

  • Installs on your own servers with one installer that installs, verifies, backs up, restores, upgrades and rolls back.In validation — not yet available
  • A signed offline bundle for installation without internet access.In validation — not yet available

Arabic and English, equally

Bilingual certificates and Hijri dates beside Gregorian.

  • Bilingual Arabic and English certificates rendered on A4.Verified in testing
  • Umm al-Qura Hijri dates beside the authoritative Gregorian date on screens and certificates, checked from 2020 to 2029.Verified in testing

Engines kept behind CHERT

No engine is reachable from the internet.

  • Engines are never exposed; only the edge publishes a port, and specialist screens sit behind a sign-in gate.Verified in testing

Open source, attributed

Pinned sources with every licence and notice kept.

  • Every engine is built from a pinned source snapshot kept in CHERT's repository, with its licence notices intact.Verified in testing
  • Every engine image is rebuilt from CHERT's own base-image mirror, with no public registry in the build.Verified in testing

Capabilities

Every function, at a glance

Each statement carries its status. Only what has passed verification is shown as verified; everything else says plainly that it is not yet available.

  • Verified in testingImplemented and verified by automated tests and end-to-end journeys on CHERT's build runners. Deployment at a laboratory and owner acceptance are separate steps that follow.
  • In validation — not yet availableBeing built or validated. Not yet available.
  • Awaiting external qualification — not yet availableBuilt as far as possible, then waiting for hardware, a vendor or an external service to qualify it. Not yet available.

Samples and laboratory operations

9 verified1 not yet available

Show the statements
  • Sites, departments, clients, sample types and tests kept as controlled master data with stable identifiers.Verified in testing
  • Registration, reception with condition, storage locations, transfers, aliquots and disposal with a reason, each step on an append-only custody trail.Verified in testing
  • Code 128 sample labels, find by label, and camera scanning where the device supports it.Verified in testing
  • Versioned methods and specifications, test packages, and decision rules evaluated when a result is entered.Verified in testing
  • Work queues by test with urgent work first, and worksheets created from the queue.Verified in testing
  • Result entry with units, precision and rounding, validated calculation versions, and verification by a second person; a withdrawal keeps the history.Verified in testing
  • Reagent and reference-material lots, expiry, preparations with their genealogy, and consumption per worksheet.Verified in testing
  • Bench and field capture on any screen size that queues while offline and replays safely; final approvals are never made offline.Verified in testing
  • Onboarding from spreadsheets with mapping, a dry run that lists row errors, source provenance and reconciliation counts.Verified in testing
  • Multi-site operation with authorised sample transfers and central reporting.In validation — not yet available

Quality control and out-of-specification results

4 verified

Show the statements
  • Blanks, controls and duplicates placed on worksheets, evaluated against limits, with control charts.Verified in testing
  • A failed control holds the worksheet's review until a reviewer records a disposition.Verified in testing
  • Automatic out-of-specification and out-of-trend investigations; the original result is preserved and retests need a justified, authorised count.Verified in testing
  • A confirmed adverse result is never retracted, and a confirmed out-of-specification result opens a nonconformity.Verified in testing

Guided execution, stability and monitoring

3 verified

Show the statements
  • Guided execution bound to the exact effective procedure revision, with equipment and lot checks, computed calculation steps and witnessed signatures.Verified in testing
  • Stability protocols, storage conditions and pull schedules with assigned tests and trends.Verified in testing
  • Environmental monitoring locations, schedules and limits; an excursion opens a deviation.Verified in testing

Research notebook and repository

3 not yet available

Show the statements
  • A research notebook linked to samples and methods; research evidence enters the LIMS only after review by someone else.In validation — not yet available
  • Curated research deposits with access policies; nothing is published automatically.In validation — not yet available
  • Persistent identifiers for publishing research datasets.Awaiting external qualification — not yet available

Controlled documents and quality management

3 verified1 not yet available

Show the statements
  • Controlled documents with stable codes, approval by someone other than the author, effective and obsolete revisions, and reading acknowledgements.Verified in testing
  • Every document revision is kept by the documents engine, and every file's hash is unchanged after a restore drill.Verified in testing
  • Arabic text recognition in scanned documents, being measured against agreed acceptance criteria.In validation — not yet available
  • Nonconformities, deviations, complaints and corrective actions with effectiveness review; failed quality control links in.Verified in testing

Competence, equipment and metrology

3 verified

Show the statements
  • Training records, acknowledgements and validity; task authorisation is enforced when results are entered and verified.Verified in testing
  • An equipment register with calibration and maintenance schedules; a failed calibration takes the equipment out of service.Verified in testing
  • Method validation gates, uncertainty budgets, uncertainty-based decision rules and proficiency-test scoring.Verified in testing

Instruments and automation

1 verified3 not yet available

Show the statements
  • Instrument files captured by upload or watch folder; original bytes kept with a hash, parser version and lineage, and values reviewed before they become results.Verified in testing
  • Analyser messaging over ASTM and HL7, built and tested in simulation only; awaiting a real analyser.Awaiting external qualification — not yet available
  • Connections to vendor instrument software and chromatography data systems.Awaiting external qualification — not yet available
  • Approved robot protocol runs with resource checks and operator reconciliation, in simulation only; hardware runs are refused until qualified.Awaiting external qualification — not yet available

Certificates, reporting and analytics

1 verified2 not yet available

Show the statements
  • Certificates of analysis issued from frozen, hashed snapshots; issuance fails closed, amendments create new versions and the original is retained.Verified in testing
  • chertBI dashboards for quality, turnaround and workload, with report schedules.In validation — not yet available
  • Reporting data rebuilt and reconciled from CHERT records, readable only for the sites you may see.In validation — not yet available

Client portal

1 not yet available

Show the statements
  • A client portal for own samples, issued certificates with hash-checked download, requests and messages; each client sees only their own records.In validation — not yet available

Integrations

7 not yet available

Show the statements
  • CHERT ERP billing with one billable line per verified analysis, never billed twice; tested against a simulated ERP, awaiting a live test environment.Awaiting external qualification — not yet available
  • SAP, Oracle and Odoo connector contracts, awaiting a named product version and a test environment.Awaiting external qualification — not yet available
  • Regulatory evidence exchange with CHERTREG.Awaiting external qualification — not yet available
  • Staff sign-in through your directory (AD/LDAP or Microsoft Entra).In validation — not yet available
  • Nafath sign-in for clients.Awaiting external qualification — not yet available
  • E-mail notifications through your own mail service.In validation — not yet available
  • Security log export to your monitoring system, kept apart from the laboratory audit trail.In validation — not yet available

Audit trail and electronic signatures

3 verified

Show the statements
  • Every change is written to a hash-chained, append-only audit trail, and the chain is re-verified after a restore.Verified in testing
  • Electronic signatures require signing in again and are bound to the hash of exactly what was signed.Verified in testing
  • Writes are idempotent, and events leave through a transactional outbox, so a retry never records an action twice.Verified in testing

Arabic, English and Hijri dates

2 verified2 not yet available

Show the statements
  • Umm al-Qura Hijri dates beside the authoritative Gregorian date on screens and certificates, checked from 2020 to 2029.Verified in testing
  • Bilingual Arabic and English certificates rendered on A4.Verified in testing
  • Every screen in Arabic and English from one codebase, mirrored for right-to-left reading.In validation — not yet available
  • Arabic laboratory terminology reviewed by a native-speaking specialist.In validation — not yet available

Private installation and offline operation

4 not yet available

Show the statements
  • Installs on your own servers with one installer that installs, verifies, backs up, restores, upgrades and rolls back.In validation — not yet available
  • A signed offline bundle for installation without internet access.In validation — not yet available
  • Coordinated backup and clean-environment restore of every store, with measured recovery times.In validation — not yet available
  • A cluster profile for high availability.In validation — not yet available

Security and supply chain

4 verified1 not yet available

Show the statements
  • Engines are never exposed; only the edge publishes a port, and specialist screens sit behind a sign-in gate.Verified in testing
  • Every engine is built from a pinned source snapshot kept in CHERT's repository, with its licence notices intact.Verified in testing
  • Every engine image is rebuilt from CHERT's own base-image mirror, with no public registry in the build.Verified in testing
  • Evidence files are stored by content address and checked against their hash when read.Verified in testing
  • Security and release maintenance with software bills of materials and vulnerability scans.In validation — not yet available

Engines

4 verified6 not yet available

Show the statements
  • Laboratory engine for samples, analyses, worksheets and quality control, reached only through CHERT.Verified in testing
  • Documents engine for every controlled-document revision, presented under the CHERT name.Verified in testing
  • Evidence store for original files, addressed and verified by hash.Verified in testing
  • Event bus carrying changes between modules from a transactional outbox.Verified in testing
  • Identity service for one sign-in across every CHERT screen.In validation — not yet available
  • Notebook engine for research records.In validation — not yet available
  • Repository engine for curated research datasets.In validation — not yet available
  • Analytics engine behind chertBI.In validation — not yet available
  • Search engine with Arabic and English analysis.In validation — not yet available
  • Robot runner for approved automation protocols, in simulation until hardware is qualified.Awaiting external qualification — not yet available
Show every statement with its tracker rows
Every statement on this page, its status and the tracker rows it cites
AreaStatementStatusTracker rows
Samples and laboratory operationsSites, departments, clients, sample types and tests kept as controlled master data with stable identifiers.Verified in testingCAP-01
Samples and laboratory operationsRegistration, reception with condition, storage locations, transfers, aliquots and disposal with a reason, each step on an append-only custody trail.Verified in testingCAP-02
Samples and laboratory operationsCode 128 sample labels, find by label, and camera scanning where the device supports it.Verified in testingCAP-02
Samples and laboratory operationsVersioned methods and specifications, test packages, and decision rules evaluated when a result is entered.Verified in testingCAP-03
Samples and laboratory operationsWork queues by test with urgent work first, and worksheets created from the queue.Verified in testingCAP-04
Samples and laboratory operationsResult entry with units, precision and rounding, validated calculation versions, and verification by a second person; a withdrawal keeps the history.Verified in testingCAP-05
Samples and laboratory operationsReagent and reference-material lots, expiry, preparations with their genealogy, and consumption per worksheet.Verified in testingCAP-08
Samples and laboratory operationsBench and field capture on any screen size that queues while offline and replays safely; final approvals are never made offline.Verified in testingCAP-28, MOD-33
Samples and laboratory operationsOnboarding from spreadsheets with mapping, a dry run that lists row errors, source provenance and reconciliation counts.Verified in testingCAP-30
Samples and laboratory operationsMulti-site operation with authorised sample transfers and central reporting.In validation — not yet availableCAP-29
Quality control and out-of-specification resultsBlanks, controls and duplicates placed on worksheets, evaluated against limits, with control charts.Verified in testingCAP-06
Quality control and out-of-specification resultsA failed control holds the worksheet's review until a reviewer records a disposition.Verified in testingCAP-06
Quality control and out-of-specification resultsAutomatic out-of-specification and out-of-trend investigations; the original result is preserved and retests need a justified, authorised count.Verified in testingCAP-17, MOD-17
Quality control and out-of-specification resultsA confirmed adverse result is never retracted, and a confirmed out-of-specification result opens a nonconformity.Verified in testingMOD-17
Guided execution, stability and monitoringGuided execution bound to the exact effective procedure revision, with equipment and lot checks, computed calculation steps and witnessed signatures.Verified in testingCAP-10, MOD-13
Guided execution, stability and monitoringStability protocols, storage conditions and pull schedules with assigned tests and trends.Verified in testingCAP-18
Guided execution, stability and monitoringEnvironmental monitoring locations, schedules and limits; an excursion opens a deviation.Verified in testingCAP-19
Research notebook and repositoryA research notebook linked to samples and methods; research evidence enters the LIMS only after review by someone else.In validation — not yet availableCAP-13, MOD-07
Research notebook and repositoryCurated research deposits with access policies; nothing is published automatically.In validation — not yet availableCAP-14
Research notebook and repositoryPersistent identifiers for publishing research datasets.Awaiting external qualification — not yet availableINT-13
Controlled documents and quality managementControlled documents with stable codes, approval by someone other than the author, effective and obsolete revisions, and reading acknowledgements.Verified in testingCAP-12, MOD-14
Controlled documents and quality managementEvery document revision is kept by the documents engine, and every file's hash is unchanged after a restore drill.Verified in testingSYS-03
Controlled documents and quality managementArabic text recognition in scanned documents, being measured against agreed acceptance criteria.In validation — not yet availableDEP-07
Controlled documents and quality managementNonconformities, deviations, complaints and corrective actions with effectiveness review; failed quality control links in.Verified in testingCAP-15
Competence, equipment and metrologyTraining records, acknowledgements and validity; task authorisation is enforced when results are entered and verified.Verified in testingCAP-16
Competence, equipment and metrologyAn equipment register with calibration and maintenance schedules; a failed calibration takes the equipment out of service.Verified in testingCAP-07
Competence, equipment and metrologyMethod validation gates, uncertainty budgets, uncertainty-based decision rules and proficiency-test scoring.Verified in testingCAP-09
Instruments and automationInstrument files captured by upload or watch folder; original bytes kept with a hash, parser version and lineage, and values reviewed before they become results.Verified in testingCAP-11, MOD-21
Instruments and automationAnalyser messaging over ASTM and HL7, built and tested in simulation only; awaiting a real analyser.Awaiting external qualification — not yet availableINT-10, CAP-24
Instruments and automationConnections to vendor instrument software and chromatography data systems.Awaiting external qualification — not yet availableINT-09
Instruments and automationApproved robot protocol runs with resource checks and operator reconciliation, in simulation only; hardware runs are refused until qualified.Awaiting external qualification — not yet availableCAP-25, QUAL-07
SearchArabic and English search across samples, clients and documents, limited to the sites you may see.In validation — not yet availableCAP-23, MOD-24
Certificates, reporting and analyticsCertificates of analysis issued from frozen, hashed snapshots; issuance fails closed, amendments create new versions and the original is retained.Verified in testingCAP-21, MOD-20
Certificates, reporting and analyticschertBI dashboards for quality, turnaround and workload, with report schedules.In validation — not yet availableCAP-22, SYS-14
Certificates, reporting and analyticsReporting data rebuilt and reconciled from CHERT records, readable only for the sites you may see.In validation — not yet availableMOD-23
Client portalA client portal for own samples, issued certificates with hash-checked download, requests and messages; each client sees only their own records.In validation — not yet availableCAP-26, MOD-25
IntegrationsCHERT ERP billing with one billable line per verified analysis, never billed twice; tested against a simulated ERP, awaiting a live test environment.Awaiting external qualification — not yet availableINT-01, MOD-26
IntegrationsSAP, Oracle and Odoo connector contracts, awaiting a named product version and a test environment.Awaiting external qualification — not yet availableINT-02, INT-03, INT-04
IntegrationsRegulatory evidence exchange with CHERTREG.Awaiting external qualification — not yet availableINT-05
IntegrationsStaff sign-in through your directory (AD/LDAP or Microsoft Entra).In validation — not yet availableMOD-28, INT-06, INT-07
IntegrationsNafath sign-in for clients.Awaiting external qualification — not yet availableINT-08
IntegrationsE-mail notifications through your own mail service.In validation — not yet availableINT-11
IntegrationsSecurity log export to your monitoring system, kept apart from the laboratory audit trail.In validation — not yet availableINT-12
Audit trail and electronic signaturesEvery change is written to a hash-chained, append-only audit trail, and the chain is re-verified after a restore.Verified in testingMOD-04, MOD-03
Audit trail and electronic signaturesElectronic signatures require signing in again and are bound to the hash of exactly what was signed.Verified in testingCAP-20
Audit trail and electronic signaturesWrites are idempotent, and events leave through a transactional outbox, so a retry never records an action twice.Verified in testingMOD-04, MOD-03
Arabic, English and Hijri datesUmm al-Qura Hijri dates beside the authoritative Gregorian date on screens and certificates, checked from 2020 to 2029.Verified in testingGOV-06
Arabic, English and Hijri datesBilingual Arabic and English certificates rendered on A4.Verified in testingMOD-20
Arabic, English and Hijri datesEvery screen in Arabic and English from one codebase, mirrored for right-to-left reading.In validation — not yet availableMOD-01
Arabic, English and Hijri datesArabic laboratory terminology reviewed by a native-speaking specialist.In validation — not yet availableGOV-10
Private installation and offline operationInstalls on your own servers with one installer that installs, verifies, backs up, restores, upgrades and rolls back.In validation — not yet availablePROF-02, MOD-29
Private installation and offline operationA signed offline bundle for installation without internet access.In validation — not yet availablePROF-04
Private installation and offline operationCoordinated backup and clean-environment restore of every store, with measured recovery times.In validation — not yet availablePROF-05
Private installation and offline operationA cluster profile for high availability.In validation — not yet availablePROF-03
Security and supply chainEngines are never exposed; only the edge publishes a port, and specialist screens sit behind a sign-in gate.Verified in testingSYS-01
Security and supply chainEvery engine is built from a pinned source snapshot kept in CHERT's repository, with its licence notices intact.Verified in testingREPO-02, REPO-03
Security and supply chainEvery engine image is rebuilt from CHERT's own base-image mirror, with no public registry in the build.Verified in testingTL-08
Security and supply chainEvidence files are stored by content address and checked against their hash when read.Verified in testingMOD-09
Security and supply chainSecurity and release maintenance with software bills of materials and vulnerability scans.In validation — not yet availablePROF-06
EnginesLaboratory engine for samples, analyses, worksheets and quality control, reached only through CHERT.Verified in testingSYS-01
EnginesDocuments engine for every controlled-document revision, presented under the CHERT name.Verified in testingSYS-03
EnginesEvidence store for original files, addressed and verified by hash.Verified in testingMOD-09
EnginesEvent bus carrying changes between modules from a transactional outbox.Verified in testingMOD-04
EnginesIdentity service for one sign-in across every CHERT screen.In validation — not yet availableSYS-07, MOD-02
EnginesNotebook engine for research records.In validation — not yet availableSYS-02
EnginesRepository engine for curated research datasets.In validation — not yet availableSYS-04
EnginesAnalytics engine behind chertBI.In validation — not yet availableSYS-14
EnginesSearch engine with Arabic and English analysis.In validation — not yet availableSYS-15
EnginesRobot runner for approved automation protocols, in simulation until hardware is qualified.Awaiting external qualification — not yet availableSYS-05

From sample to certificate, on one record.

Sign in if your laboratory already has an account, or read how CHERT LIMS respects the open-source projects it is built on.