A medication fridge fails on a quiet night ward.
A failed pharmacy refrigerator isn’t just spoiled stock — it’s a patient-safety risk and a compliance event. The alarm fired. The pharmacist’s phone was in another room. my-iris makes sure the alert reaches a clinician, escalates until someone acts, and leaves an auditable record of who responded and when.
Illustrative industry scenario — not a specific client.
- Primary risk
- patient safety
- Regulatory exposure
- compliance violation + liability
- At risk
- medication · vaccine · tissue stock
- With my-iris
- reached · acknowledged · proven
Illustrative cost-of-failure categories
The problem
Three ways a ward alarm fails a patient-safety review
The fridge alarm worked. The alert didn’t reach a clinician who could act — and there was nothing to show the patient-safety review afterward.
Single channel
One text to the pharmacist on shift. On a quiet night ward, with the phone on a desk in another room, the fridge fault goes unnoticed for hours.
No escalation
No reply, no backup. Nothing reaches the duty pharmacist, the ward manager or the on-call lead while medication and vaccine stock warms toward waste.
No proof
A patient-safety review asks who was alerted and when. Without an auditable acknowledgement trail, “the system sent an SMS” doesn’t close the loop.
How my-iris maps
From fault to confirmed clinical response
The same stateful lifecycle behind pharma cold-chain monitoring — applied to your wards, your duty chain, your review.
Escalation up the duty chain
No answer in your window? my-iris goes from a push to a voice call to the next responder — up to 20 attempts by default — until a clinician or pharmacist acknowledges the alert.
Voice/IVR for the night shift
When a push is missed on a quiet ward, an automated call reaches the on-call phone. The keypress that acknowledges the alert is captured and timestamped.
Built for cold storage
Medication fridges, vaccine stores, biobank and tissue freezers at ultra-low temperatures — my-iris sits on top of whatever monitors them and turns a fault into action.
Two-way acknowledgement
Recipients acknowledge or skip in the my-iris app or on the call. The alert only resolves when a person has it — not when a gateway reports “delivered”.
Audit-ready event log
Every notification, escalation, reply and resolution is logged append-only and tamper-evident — the evidence a patient-safety or compliance review depends on.
7 languages on the call
Each receiver group has its own call language, so each team hears the voice call in the language it works in.
Fits your ward, not a software on-call rota
Escalation that follows the duty chain
A medication-fridge fault at 3 AM has to find a person, not a dashboard. my-iris maps an escalation policy onto whoever is actually on shift — and proves the loop closed for the review afterward.
- 01
Up the on-call chain
Duty nurse → on-call pharmacist → estates/facilities → site manager: each step escalates only if the previous person doesn’t acknowledge, so a phone left at the nurses’ station never ends the chain.
- 02
Every cold-store class
Medication and vaccine fridges, biobank and tissue freezers, blood and reagent stores — my-iris sits on top of whatever monitors each one and treats its alarm as an escalating, acknowledged event.
- 03
Feeds incident reporting
The acknowledgement trail is the “who was alerted, when, and did they act” record a patient-safety or clinical-governance review opens with — exportable and EU-resident.
Audit-ready by design
Evidence for your patient-safety review
my-iris produces the timestamped, EU-resident record a clinical-governance or patient-safety review asks for — every notification, escalation, acknowledgement and resolution. We give you the trail and the residency posture; your organisation owns its clinical and EU MDR-adjacent obligations. We don’t claim certifications we don’t hold.
- Patient-safety audit export
- EU data residency by architecture
- Configurable retention · up to 5 yr
- GDPR Art. 15 / 17 · DPA
- Two-way acknowledgement proof
- STOP/START opt-out · 7 languages
my-iris comes from MeshWorks Wireless Oy, which also runs Seemoto — pharmaceutical cold-chain monitoring across 5 EU countries.
Its predecessor, AMS v1, delivered 1,431+ alerts in Seemoto production — the temperature-critical, compliance-critical alerting healthcare depends on.
Read the Seemoto case studyHealthcare — frequently asked
Is my-iris suitable for hospital and pharmacy environments?
my-iris is the escalation-and-proof layer for the equipment alarms you already monitor — medication fridges, vaccine stores, biobank and tissue freezers. It is designed to be audit-ready for patient-safety and quality reviews, with a tamper-evident acknowledgement trail and EU-resident data. We provide the evidence and residency posture; your organisation maps it to its own clinical-governance and EU MDR-adjacent obligations. my-iris does not itself hold healthcare certifications.
Can it sit on top of our existing fridge and freezer monitoring?
Yes. my-iris does not replace your sensors or BMS — anything that can fire a webhook posts the fault to one REST endpoint, and my-iris takes over routing, escalation by push and voice call, acknowledgement and the audit trail.
How is patient and staff data protected?
Data lives on Cloudflare’s EU edge, with alert state in Durable Objects pinned to EU jurisdiction. GDPR Art. 15 export and Art. 17 erasure are supported, STOP/START opt-out is built in, retention is configurable, and a DPA is available.
Make sure a fridge fault reaches a clinician
Talk to us about a hospital or pharmacy rollout: your wards, your duty chain, your review.