Industries
Laboratory networks
Laboratories already live by records. The problem is rarely that a laboratory does not care about calibration evidence; it is that the evidence lives in instrument printouts, a shared drive and one person's memory, and assembling it into something an inspector will accept is a fortnight of somebody's life, repeatedly.
- Quality and compliance
- Biomedical engineering
- Hospital operations
What is different about a laboratory?
The evidence is the product. An analyser that works but cannot demonstrate that it was calibrated has produced results the laboratory cannot fully stand behind.
In most segments, equipment records exist so the equipment gets maintained. In a laboratory, the record has a second job: it is part of what makes the result defensible. The instrument being fine is not sufficient if the demonstration that it was fine is a printout in a drawer.
That raises the cost of the ordinary failure mode. A missing maintenance record on a ward pump is an administrative gap. A missing calibration record on an analyser is a question about every result it produced in the interval, and the question arrives from someone with authority to ask it.
The second difference is volume and repetition. A laboratory does a lot of the same checks on the same instruments, which means the marginal cost of recording well is low and the compounding benefit is high. This is the segment where getting the record right pays back fastest.
How Rydya supports a laboratory
Holds the calibration machinery and the evidence trail, without ever telling you what your limits should be.
Your limits, your procedures, your intervals
Rydya ships none of these and never will. What a pass looks like on your analyser, how often it is checked and what the procedure contains are decisions for your qualified staff and the standards that apply to you. The platform holds them and enforces them once set.
Readings recorded against those limits
The value and the comparison, both retained. Not a tick. A record showing that a reading was taken and what it was is worth something years later; a record showing somebody ticked a box is not.
The instrument's own status counts
Test and calibration instruments carry their own calibration status, so a reading taken with a lapsed instrument is visible as such rather than silently trusted. A result is only as good as the thing that measured it, and this is the quiet failure that makes a complete-looking record meaningless.
Procedure versions travel with results
Improving a procedure is normal rather than dangerous, because the version used is stored with the result. Work done last year stays interpretable this year, and nothing retro-edits the past into false tidiness.
Certificates and restrictions are real records
Stored as bytes, permission-checked and audited on download, with expiry visible before it bites rather than after. A certificate that lives on a shared drive is a promise about somebody else's folder structure.
Why the fortnight before an inspection exists
Because the evidence was never assembled, only generated, and assembling it afterwards is a research project into your own organisation.
Every laboratory knows the rhythm. An inspection is scheduled. A quality lead spends two weeks finding printouts, chasing engineers for service reports, reconstructing which instrument was used for what, and building a folder. The laboratory passes. Nothing about the equipment changed; the fortnight bought presentation, not safety.
The fortnight exists because the record and the work were separate activities. The calibration happened, and then, later, somebody described that it had happened. Any gap between an event and its recording is filled by memory, and memory is exactly what an inspector is entitled to be unimpressed by.
The alternative is unglamorous: the record is a by-product of doing the check, written in the same transaction, append-only, with the procedure version attached. The evidence pack then becomes a query rather than an excavation, and the fortnight goes back to the person who was spending it.
Missing data never reads as compliant
This is the rule that matters most in this segment, and it is enforced rather than left to a report author. An instrument with no data is reported as an instrument with no data: not zero, not interpolated, not quietly excluded. The absence of a failed check is not a passed check. A compliance report that hides its own gaps is worse than no report, because it is confidently wrong in the direction you will not question.
Who should own this, and when to start
Quality, with the biomedical team, starting from the instruments whose records you would least like to be asked for.
The natural owner in a laboratory is quality rather than facilities, because quality is who bears the consequence of a gap. That is not true in most other segments, and it changes the rollout: the first configuration conversation is about evidence rather than about maintenance scheduling.
Start where the exposure is, not where the estate is easiest. The instruments whose calibration history you would least like to be asked for are exactly the ones to bring in first, because the point is not to have a tidy register, it is to stop the next fortnight from happening. Widen once the rhythm exists, and let the first inspection after that be the proof rather than the test.
Questions
Does Rydya tell us our calibration limits or how often to check an analyser?
No, and it never will. Limits, intervals and procedures are decisions for your qualified staff and the standards that apply to you. Rydya holds what you configure, compares readings to it, records both the value and the comparison, and refuses to bend them. Any software supplying a default here is making a claim about an instrument it has never seen.
Is Rydya a LIMS?
No. Rydya holds no samples, no results and no patient records. It manages the equipment: its calibration and maintenance history, the instruments used, the certificates, the downtime and the cost. It sits alongside a LIMS rather than replacing it, and the boundary is deliberate.
What happens if a check was done with an instrument that was out of calibration?
It is visible rather than silently trusted. Test and calibration instruments carry their own calibration status, because a reading is only as good as the thing that took it. This is precisely the quiet failure that leaves a laboratory with a complete-looking record that does not mean what it appears to mean.
Will this shorten the scramble before an inspection?
That is the main thing it is for in this segment. The fortnight exists because evidence was generated but never assembled, so assembling it afterwards becomes a research project. When the record is a by-product of doing the check, append-only and with the procedure version attached, the evidence pack becomes a query rather than an excavation.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us