Solutions
Compliance
Most hospitals are more compliant than they can prove. The work happens, then an inspection arrives and a team spends two weeks reconstructing from inboxes and paper what the organisation already did.
- Quality and compliance
- Biomedical engineering
- Executive and finance
What is equipment compliance evidence?
Definition
Compliance evidence
Compliance evidence is the durable, attributable record that a required activity happened: what was done, to which asset, by whom, when, against which procedure, with what result, and what followed from that result.
Every clause in that sentence is load-bearing. A record that something was done, without who or when or against what, is an assertion, and assertions fail inspections.
Evidence is a property of how the work was recorded while it was happening, not a document you produce. If the record was right at the time, the pack is a query; if not, no assembly afterwards fixes it.
Rydya does not certify anything
Rydya produces evidence and reports. It does not certify that equipment is safe or compliant, it does not interpret regulations for you, and it never files anything to a regulator on your behalf. Those judgements stay with the qualified people who own them. Any vendor telling you their software makes you compliant is selling you a liability.
Why proving it costs more than doing it
Because the evidence is created by one team in one moment and consumed by another team years later. Nothing bridges that gap except deliberate design.
The technician completing a safety test is thinking about the next job, not an audit in 2029. Asking them to also produce audit-ready documentation loses whenever the department is busy, which is always.
So the evidence has to be a by-product: the act that records the work has to produce the artefact. Provenance cannot be retro-fitted onto a history that never captured it, which is why "we will tidy the data later" is the most expensive sentence in this category.
The second cost is missing data. A register where a third of assets have no location or serial will produce a compliance report that is technically accurate and completely useless.
How Rydya turns work into evidence
By recording provenance at the moment of the work, then letting the pack be a query rather than a project.
- 1
Write the audit as part of the change
Every transition is permission checked and written to an append-only, hash-chained audit trail in the same transaction as the change. No update path, no delete path: the history cannot be improved later.
- 2
Keep the provenance attached
A result carries the asset, the procedure version, the instrument, the readings, the person and the timestamp. Nothing has to be reunited afterwards, because nothing was separated.
- 3
Surface missing data before an auditor does
Data-quality scans find incomplete and unverified records continuously and put them in front of someone who can fix them, while fixing is still cheap.
- 4
Assemble the pack from real data
Evidence packs pull the records for an inspection from live data, with the source of every figure visible. Exports run to CSV, XLSX, HTML and JSON, permission controlled and logged.
- 5
Send it on a schedule, and prove you sent it
Scheduled reporting delivers the monthly pack with delivery recorded and retried. "We sent it" becomes a record rather than a recollection.
What an inspector can actually be shown
Not a folder. A set of queries over records that were correct when they were written.
The audit report
Who did what, when, and to which record, as a readable view over the append-only trail. Hash-chaining means it could not have been edited.
Compliance by asset
Which equipment has overdue planned work, expired certificates or open restrictions, as a view rather than a reconciliation exercise.
Evidence packs
The records for a specific inspection or accreditation, assembled from live data with the provenance of every figure visible rather than asserted.
Data-quality exceptions
The honest list of what is incomplete. Knowing your gaps and working them is a stronger position than being shown them.
The exceptions, not just the successes
Failures, restrictions, quarantines and deferrals are records with owners and reasons. A history with no failures is not a good history; it is an incomplete one.
Where the evidence comes from
Compliance is not a bolt-on module. Every part of it is a by-product of a different team doing its normal job.
| Evidence | Produced by | At what moment |
|---|---|---|
| Service history | Fault reports and work orders | As the work is done |
| Test results and certificates | Calibration and safety testing | As readings are captured |
| Planned-work compliance | Preventive maintenance plans | As tasks complete or slip |
| Corrective actions | Incidents and CAPA | As the investigation proceeds |
| Who did what, when | The audit trail | In the same transaction as every change |
| Known gaps | Data-quality scans | Continuously, before anyone asks |
The activity that produces each kind of evidence
When to fix this
Before the inspection you already know about, in the ordinary period when nobody is asking.
Starting when an audit is announced is the worst moment: the fix changes how work is recorded, and the benefit only accrues to work recorded from that point on.
The tractable version is to start with the assets whose evidence you would be asked for first, and let the history accumulate. Evidence compounds: every month of correct recording is a month you never have to reconstruct.
Questions
Does Rydya make us compliant?
No, and be sceptical of anything that claims to. Rydya produces evidence and reports from the work your teams do. It does not certify that equipment is safe or compliant, does not interpret regulations, and never files anything to a regulator. Compliance decisions stay with the qualified people who own them.
Can the audit trail be edited?
No. Audit events are append-only and hash-chained, written in the same transaction as the change they record, with no update or delete path. Corrections are audited amendments rather than quiet edits, and closed financial records are never edited in place.
What if our asset data is incomplete?
Then your compliance reporting is unreliable, and Rydya will say so rather than produce a confident-looking report over gaps. Data-quality scans surface incomplete and unverified records continuously.
Can we prove a report was actually delivered?
Yes. Scheduled reporting records delivery and retries failures, so distribution is a record rather than a recollection. Exports run to CSV, XLSX, HTML and JSON, are permission controlled, and downloads are logged.
Does the evidence include patient information?
No. Rydya stores no patient clinical records at all. A fault report captures whether patient care or a clinical service was affected as a simple flag, and the forms explicitly ask reporters not to include clinical detail. The evidence is about equipment, not about people.
Keep reading
Calibration
Where certificates, readings and restrictions come from in the first place.
Preventive maintenance
Planned-work compliance, and why deferrals must be decisions rather than gaps.
Hospital equipment maintenance
The loop that produces the evidence as a by-product.
Glossary
The vocabulary this field uses loosely, defined so you can argue with it.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us