Fragmented and audit-triggered
- Separate evidence repositories
- Late discovery of gaps
- Flat, unprioritised task lists
- Manual pre-assessment collation
- Limited cross-site visibility
Continuous evidence assurance
Make every reported result traceable across systems.
Xaloreli rebuilds the evidence thread behind sampled laboratory results and checks whether the LIMS, QMS, QC, equipment, competency, reagent and EQA records agree at the moment the work was performed.
Vendor-neutralRead-only by designHuman-governedResult-level assurance
Quality command centreReadiness at a glance
Live modelReadiness84%↑ 6%
Priority gaps21 overdue
Current evidence148of 162
Evidence readiness by domain
Quality control94%
Equipment88%
Competency82%
CAPA76%
Priority actions
HighEQA outlier review
MedCompetency renewal
LowReagent evidence
One governed evidence modelCentral laboratory · multi-site services · POCT extension
Capture→Evaluate→Escalate→Resolve→Verify
The operating gap
Every system can look complete while the result-level evidence thread is broken.
The LIMS knows who released a result. The QMS knows whether that person was competent. QC, lot, equipment, SOP and EQA status may sit elsewhere. Xaloreli checks those independent records against one another through a continuous, risk-weighted vertical audit.
→
Continuous and cross-system
- Result-level evidence threads
- Contradictions found earlier
- Risk-weighted sampling
- Findings returned to the existing QMS
- Reproducible Thread Packs
Four connected layers
A verification layer above the systems laboratories already use.
Access layer
Views for quality managers, section leads, network governance and scoped, time-limited assessors.
Assurance engine
Evidence Thread Builder, cross-system rule library, risk-weighted sampler and requirement mapping.
Connector layer
Read-only file and API connectors for LIMS, QMS, QC, EQA, lots, equipment and rosters.
Data and security
UK hosting, tenant isolation, source fingerprints, immutable findings and least-privilege access.
Core product
Six modules that verify rather than replace.
Begin with one discipline and the highest-risk rule families, then extend across sites, systems and POCT sources.
Connector Hub
Read-only extracts and structured imports from systems that already hold laboratory evidence.
Evidence Thread Builder
Links each sampled result to its operator, authoriser, instrument, IQC, lots, SOP and EQA position.
Cross-System Rule Library
Tests whether time-bounded records from independent systems agree and explains every break.
Risk-Weighted Sampler
Increases coverage for new lots, post-maintenance runs, temporary staff and recent EQA concerns.
Break Manager and QMS Write-Back
Confirms, owns and returns findings to the laboratory's existing nonconformance process.
Thread Pack and Network Dashboard
Reconstructs selected samples and compares coverage, break rates and closure times across services.
Continuous vertical audit
From reported result to reproducible evidence thread.
Extract
Take scheduled, read-only exports from the LIMS, QMS, QC, EQA, lot and roster sources.
Resolve
Select a result by risk and resolve every person, instrument, lot, control and document state at that time.
Reconcile
Apply cross-system rules and show the two conflicting sources side by side.
Close the loop
Confirm genuine breaks, assign ownership and write findings back into the existing QMS.
Evidence
Create a clause-mapped Thread Pack with source references and reproducible snapshots.
Where Xaloreli fits
It checks between systems, not only within one.
Existing platforms remain the systems of record. Xaloreli adds the continuous cross-system check that is usually performed manually through a vertical audit.
Records quality activity
Documents, competency, equipment, audit and CAPA remain controlled in the laboratory's existing QMS.
Xaloreli reads and returns confirmed findings.Runs the result pathway
The LIMS remains responsible for accession, testing, authorisation and the clinical audit trail.
Xaloreli uses its activity as the thread anchor.Control their connected work
Specialist platforms continue to manage analyser, QC, device and operator workflows in their own scope.
Xaloreli includes their exports in the wider thread.Verifies the joins
It detects contradictions that only become visible when independently maintained records are tested together.
No replacement project. No parallel CAPA system.Practical result-level checks
Four evidence breaks the platform is designed to find.
Each example begins with a reported result and follows the evidence state that applied at that exact time.
Competency at authorisation
A LIMS account is active, but assay-specific competency expired four days earlier.
Lot acceptance after supply change
IQC passes, but the new reagent lot has no completed acceptance record.
Post-networking alignment
Two sites use different systems and show different evidence practices for the same rule.
Assessment-day vertical audit
Three selected samples are reconstructed with sources, rules and fingerprints.
Designed around real work
Different views. One source of assurance.
BENCH WORKFLOW
Capture evidence without interrupting laboratory work.
Confirm the instrument, lot, operator and outcome; receive immediate confirmation or a clear deviation prompt; attach evidence to an assigned action.
File first, API second
Keep the systems you have. Gain proof that they agree.
Xaloreli starts with scheduled structured exports laboratories already use for audit. APIs and supported vendor partnerships can follow. Clinical systems remain read-only, with approved write-back limited to findings in the existing QMS.
LIMSQMSQC
XaloreliThread reconciliation
EQALotsRoster
Trust and governance
Designed for evidence verification, not clinical decision-making.
The core workflow can operate on operational metadata without patient names, demographics or clinical values. Production deployment is intended to include UK data residency, DPIA support, DSPT alignment, tenant isolation, encryption and independent penetration testing.
Read-only clinical sourcesRole-based accessMulti-factor authenticationTenant isolationEncryptionSource fingerprintsBackup and recoveryIndependent testing
Questions and answers
Find answers for your laboratory service
Open any question to understand how Xaloreli fits around existing systems and day-to-day quality work.
A pilot starts with one discipline, three to five high-value rule families and file exports the laboratory already produces. The team agrees the scope, source mappings, confirmation process and measures for breaks found and audit time saved.
Yes. Blood sciences and a small set of rules, such as competency at task, lot acceptance and equipment status, provide a practical starting point before further disciplines and sites are added.
No. Its result-level evidence threads can support routine internal vertical audits, investigation, network governance and management review. ISO 15189 mapping is applied where it is relevant to the accredited service.
No. The LIMS remains the sample-to-result system and the QMS remains the home for controlled documents, nonconformances and CAPA. Xaloreli checks whether their records agree with other sources and returns confirmed findings to the QMS.
Xaloreli displays the two source states and the rule they failed. A quality manager confirms or dismisses the break before an approved finding is written into the existing QMS for investigation.
No. Findings are framed as evidence-consistency issues, not individual performance scores. Bench staff should have no extra data-entry burden and see only relevant feedback within the laboratory's governed process.
The initial scope covers LIMS activity, QMS competency, equipment and document records, IQC, EQA, reagent and calibrator lots, and roster exports. POCT middleware can be added as another source.
No. The integration strategy is file first. Scheduled CSV or report extracts can support a controlled pilot, while APIs are added where the vendor and trust IT team support them.
Access is designed around defined roles and service scope. Bench users, quality managers, governance leads and reviewers see only the functions and records appropriate to their responsibilities, with approvals and access activity logged.
POCT sites, operators, devices, IQC, EQA, connectivity and exceptions can use the same evidence, risk and CAPA model as the central laboratory. Coordinators gain a network view while local responsibilities remain clear.
A Thread Pack reconstructs one selected sample across operator, authoriser, competency, IQC, lots, equipment, SOP and EQA status. It includes source references, applicable requirement mapping and fingerprints of the snapshots used.
Implementation would include workflow mapping, configuration, user training, integration planning and agreed service support. Pilot outcomes and user feedback would be reviewed before extending the platform to further departments or sites.
12-week paid pilot
Prove the value with one discipline and real export constraints.
The proposed pilot uses file-based extracts and a small group of rule families, with success measured through evidence breaks found, time saved against manual vertical audit and quality-lead satisfaction.
- Map realistic source exports and identifiers
- Sandbox rules against historical data
- Confirm findings before QMS write-back
- Measure coverage, break rate and audit time saved