Solutions
Calibration
Calibration is the only maintenance activity whose output is a claim: this device is performing within limits. Lose any link in the evidence chain and the claim is just a sticker.
- Biomedical engineering
- Clinical engineering
- Quality and compliance
What is calibration management?
Definition
Calibration management
Calibration management is scheduling calibration work, performing it against a defined procedure with a traceable instrument, recording the measured readings, comparing them to pass or fail criteria, and producing a durable record of the outcome.
Note what is not in that definition: any particular number. The interval, the procedure, the limits and the acceptable uncertainty belong to the device, its manufacturer, your standards and your qualified staff.
Storing a date and a tick is not calibration management. Without the readings, the instrument used and the procedure version, you have only a record that something happened.
Rydya holds your limits, it does not supply them
What a device must measure, what tolerance is acceptable, and how often it should be checked are decisions for your qualified staff, your manufacturers' instructions and the standards you work to. Rydya never invents a limit or an interval. It is where you configure them, and it is what refuses to let a failing device back into service.
Why calibration records fail an audit
Almost never because the work was not done. Usually because the record cannot prove which procedure was followed, which instrument was used, or what was measured.
The classic failure is the orphaned reading: two years on, nobody can say which instrument took the reading or whether it was itself in calibration at the time. That record has failed, however good the underlying work was.
The second is procedure drift. If the record does not capture which revision was followed, every historical result becomes ambiguous the moment the procedure changes.
The third is the silent pass. Failed, adjusted and passed is a different story from passed first time. A record that only holds the final state has destroyed the information that mattered.
How Rydya runs calibration
Procedure, instrument, readings, verdict, certificate, restriction. Each link is a field in the record rather than an assumption.
- 1
Define the procedure and its limits
A test template holds the steps, the readings to take, and the pass or fail criteria you have decided. Templates are versioned; every result records the revision it ran against.
- 2
Register the instruments that do the measuring
Test instruments are first-class records with their own identity and calibration status. Every reading is tied to the instrument that produced it.
- 3
Plan the work against assets
A test plan binds a template to assets on the recurrence you set. Due and overdue are evaluated continuously, so slippage is a state the system holds.
- 4
Capture readings, not just an outcome
Measured values are recorded against the limits, from a phone if the device is on a ward. The verdict follows from the readings; it is not typed in independently.
- 5
Issue the certificate, or the restriction
A pass produces a certificate tied to the asset, the readings, the instrument and the procedure version. A fail can restrict the device or quarantine it, and quarantine does not come off without the required tests and an authorised clearance.
What holds the claim together
The value of a calibration record is entirely in its traceability.
Reading to instrument
Every measurement is attributed to the instrument that produced it, and instruments carry their own calibration state.
Result to procedure version
Templates are versioned and the task records which version it ran. Revising a procedure does not retrospectively change what a past result meant.
Verdict to evidence
The pass or fail follows from recorded readings against configured limits, never a free-text outcome unattached to the numbers that produced it.
Failure to consequence
A failure can restrict the device or quarantine it; return to service requires the tests and an authorised clearance. The consequence is enforced rather than remembered.
Everything to the audit trail
Each transition is permission checked and written to an append-only, hash-chained audit trail in the same transaction. A calibration history cannot be tidied.
Calibration compared with the neighbouring work
Calibration, safety testing and preventive maintenance are scheduled the same way and evidenced very differently.
| Aspect | Calibration | Electrical safety testing | Preventive maintenance |
|---|---|---|---|
| Question it answers | Is this device measuring accurately? | Is this device electrically safe? | Is this device being looked after? |
| Produces | Readings against limits, a certificate | Readings against limits, a certificate | Completed steps and checks |
| Needs a traceable instrument | Yes, and its own calibration state matters | Yes | Usually not |
| A failure means | Adjust, restrict or quarantine | Quarantine until resolved | Raise corrective work |
| Who sets the limits | You, from the device and your standards | You, from your standards | You, from the manufacturer and your risk view |
What distinguishes calibration from the work it is usually filed alongside
Who owns calibration, and when it goes wrong
Biomedical or clinical engineering own the work; the risk concentrates between a failure and the ward that wants the device back.
The pressure point is predictable: a device fails, the ward needs it, and the person who can authorise a return to service is not in the building. What happens next usually involves a workaround.
Rydya removes the workaround rather than documenting it. Quarantine and return to service are server-authoritative gates: not a status somebody sets, and not something an offline device can decide. The alternative is a device in use that nobody has established is safe.
The second pressure point is the calibration of the calibrators. Letting it slide invalidates every reading taken with that instrument in the meantime, which is why instruments are assets with their own state.
Questions
Does Rydya tell us what the calibration limits should be?
No. Limits, tolerances, procedures and intervals come from the device, its manufacturer's instructions, your standards and your qualified staff. Rydya is where you configure them and what then enforces them, down to refusing to return a failing device to service.
Can we prove which instrument took a given reading?
Yes. Test instruments are first-class records with their own identity and calibration state, and every reading is attributed to its instrument. "Was the tester itself in calibration" becomes a lookup rather than an investigation.
What happens when a device fails calibration?
The failure is a recorded outcome with consequences. It can restrict the device or move it to quarantine, and coming back requires the required tests and an authorised clearance. That gate is server authoritative and cannot be bypassed for convenience.
What happens to old results when we revise a procedure?
Nothing, and that is deliberate. Templates are versioned and each task records the version it ran against, so a past result still means what it meant. Revising a procedure changes future work, not your history.
Can calibration work be done on a phone at the bedside?
Yes. Technicians capture readings from mobile, and approved field actions work offline with visible sync state. Quarantine and return to service stay online and server authoritative, because an offline device must not decide that equipment is safe again.
Keep reading
Preventive maintenance
The scheduled work that runs on the same rails and is evidenced differently.
Compliance
What the certificates and restrictions add up to when somebody asks.
Work orders
The return-to-service gate a failed calibration runs into.
Laboratory networks
Where calibration evidence is the product rather than the paperwork.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us