Live pharmacy fridge temperature monitoring with HeartBeat
A live fridge, monitored in the open.
- Live demonstration
- Read-only
- No customer data
NoazRX HeartBeat is a continuous temperature-monitoring system for pharmacy refrigerators and other fixed cold storage. It records the temperature of each monitored fridge, the operating limits configured for it, every temperature excursion outside those limits, every gap in the record, the alerts raised, the sensors assigned to the equipment and the history those readings build up.
The fridge below is demonstration equipment operated by NoazRX. Its readings are requested from the live monitoring endpoint each time this page refreshes, so what you see is what the system recorded — including the moments when it recorded nothing.
NoazRX Demonstration Pharmacy Fridge
No reading— Reading unavailable
- Configured operating range
- —
- Last reading
- —
no reading recorded - Gateway
- —
- Sensor battery
- —
- Humidity
- —
- Door
- —
- Active alerts
- —
Live demonstration temporarily unavailable
The monitoring endpoint did not respond. No reading is shown, because an old value presented as a current one would be misleading.
Last 24 hours
Period shown: —. The line breaks wherever the record does — a continuous stroke across missing readings would claim data that was never recorded.
The 24-hour history has not loaded yet.
- Recorded temperature
- Configured operating range
- Outside the configured range
- No readings recorded
Recorded summary
Periods outside the configured range
Gaps in the record
Read the 24-hour readings as a table
| Recorded at | Temperature |
|---|
Audit-ready record
Print the same record layout a pharmacy exports for an inspection: report identification, monitored equipment, the temperature summary, every recorded excursion, every gap in the record and the full reading log for the period above.
The audit-ready record becomes available once the live readings and the 24-hour history have loaded.
Demonstration equipment operated by NoazRX. No patient, prescription or customer information is displayed. Status reflects configured operating limits and is not a regulatory compliance determination.
This page reads a real NoazRX demonstration pharmacy refrigerator. The temperature, the configured operating limits, the last 24 hours of readings, every period outside those limits and every gap in the record are shown exactly as the monitoring system recorded them — including when the record is incomplete.
What HeartBeat is monitoring here
The fridge above is a piece of equipment with a record. NoazRX HeartBeat links four things that are usually kept apart: the equipment itself, the sensors physically assigned to it, the operating limits configured for it, and every reading those sensors produced while they were assigned.
- Equipment, not a sensor. A fridge with a temperature probe and a door contact is one fridge, not two lines on a screen.
- Configured limits, recorded per fridge. A range is either configured or it is not. When it is not, this page says so instead of assuming a default.
- Continuous recording with a stated cadence. Readings are stored at a defined interval, and out-of-range movement is stored immediately rather than waiting for the next tick.
- Gaps are part of the record. A period where nothing was received is shown, not smoothed over. A clean chart with a silent sensor behind it is the failure this exists to prevent.
- Alerts with an owner. A reading outside the configured limits raises an alert that someone is notified about and has to act on.
Audit-ready reporting
The same records behind this page produce the report a pharmacy hands to an inspector. Because every figure is resolved once and reused, the number on a dashboard, the number in a PDF and the number in this demonstration cannot disagree.
- One period, one set of figures. Minimum, maximum, average, out-of-range readings, distinct excursions, longest excursion and record completeness are calculated once at the source.
- Distinct excursions, not just counted readings. Forty readings during one two-hour event is one excursion, and the report says so.
- Completeness is reported honestly. When the expected number of readings cannot be established, completeness is reported as unknown — never as 100%.
- Which sensor, and for how long. A sensor is included only for the period it was actually assigned to the equipment, so a mid-period swap never attributes one fridge's readings to another.
- Objective language. Readings are reported against configured limits. The system does not issue a determination about regulatory standing.
Recorded excursion workflow
This is a recorded example of how an excursion is handled. It is not the current state of the live fridge above, and none of the times or values below are read from it.
- Temperature crosses a configured limit. A reading arrives outside the range recorded for that fridge. It is stored immediately rather than at the next scheduled interval.
- An alert is created. The alert names the equipment, the reading, the configured limits and the time, and stays open until someone closes it.
- Notification and escalation. The configured contacts are notified. If the alert is not acknowledged, escalation continues to the next contact.
- Acknowledgement and action. A person acknowledges the alert and records what was done — door closed, stock moved, service called.
- Resolution retained in the audit history. The excursion, its duration, its extremes, the notifications sent and the action recorded all stay in the history for the reporting period.
Pharmacy fridge temperature monitoring: common questions
What is pharmacy fridge temperature monitoring?
Pharmacy fridge temperature monitoring is the continuous recording of the temperature inside a pharmacy refrigerator, measured against the operating limits configured for that specific piece of equipment, so that every reading, every period outside those limits and every interruption in the record is retained rather than reconstructed from memory.
How does continuous refrigerator monitoring work?
A temperature sensor is placed inside the refrigerator and linked to that fridge in the system. The sensor reports to a gateway, which forwards readings to NoazRX HeartBeat. Readings are stored at a defined interval, and a reading that falls outside the configured limits is stored immediately rather than waiting for the next scheduled one.
What does NoazRX HeartBeat monitor?
HeartBeat monitors the equipment, not just a sensor. For each fridge it records the temperature readings, the configured operating range, the sensors currently assigned to it and the period each was assigned, gateway connectivity, the alerts raised and acknowledged, and — where the hardware supports it — humidity, door state and sensor battery level. Anything the hardware does not measure is reported as not supported rather than as a zero.
How are temperature excursions detected and recorded?
A reading outside the range configured for that fridge is an out-of-range reading. Consecutive out-of-range readings are grouped into one excursion with a start, an end and its extremes, so forty readings during a single two-hour event are reported as one excursion rather than forty. Out-of-range readings and distinct excursions are reported as separate figures.
What happens when a fridge goes outside its configured range?
An alert is raised naming the equipment, the reading, the configured limits and the time. The contacts configured for that pharmacy are notified, and an unacknowledged alert is retried and escalated to the next contact. Once someone acknowledges it and records what was done, the alert, its notifications and its resolution stay in the history for the reporting period.
How are gaps in temperature data handled?
A period in which no reading was received is reported as a gap in the record. On the chart above the line breaks across it, in the summary it is listed with its start and end, and when the expected number of readings cannot be established, record completeness is reported as unknown instead of 100%. A missing reading is a fact about the record, not something to interpolate.
Can HeartBeat monitor more than one refrigerator?
Yes. A pharmacy can register any number of fridges and other monitored cold storage, each with its own configured operating range, its own assigned sensors and its own alert history, and each reported separately. An organisation that operates several pharmacies sees each site’s equipment under that site, and audit records are produced per fridge and period.
Does HeartBeat keep historical temperature records?
Yes. This page publishes the last 24 hours because that is what the public demonstration endpoint returns. In the pharmacy product the readings, excursions, alerts and sensor assignments are retained and an audit record can be produced for a chosen fridge and date range.
What is in the audit-ready temperature record?
Report identification, the monitored equipment and its configured range, the temperature summary (minimum, maximum, average, out-of-range readings, distinct excursions, longest excursion and record completeness), every recorded excursion, every gap, the alert history, the sensor assignment history and the reading log for the period. The record a pharmacy files is generated on the server and carries a report identifier; the export on this page mirrors that layout for demonstration and says on its own face that it is not an issued record.
How is a sensor associated with a refrigerator?
A sensor is explicitly linked to a fridge with a role — for example primary temperature or door — a placement and an optional calibration certificate reference. The system never infers which equipment a sensor sits in from its name. Every assignment and unassignment is kept, so a reporting period only ever includes a sensor for the time it was actually assigned to that fridge, and a mid-period swap cannot attribute one fridge’s readings to another.
How is this different from delivery temperature monitoring?
Fridge monitoring watches fixed equipment standing in a pharmacy: one record per fridge, continuous, open-ended. Delivery temperature monitoring watches a container in motion and is linked to a specific delivery, so its record starts and ends with that delivery. Both are HeartBeat, and they are reported separately because they answer different questions.
Can it be used for vaccine or medication refrigerators?
HeartBeat monitors any refrigerator whose operating limits are configured for it, which includes fridges used for vaccines and other refrigerated medication. Refrigerated storage is commonly specified as 2–8 °C, but the limits that matter are the ones configured for that fridge and the requirements of what is stored in it — not every medication is stored at 2–8 °C, and HeartBeat reports readings against the configured limits rather than making a regulatory determination.
See HeartBeat against your own equipment
A demonstration walks through fridge setup, sensor assignment, alert routing and the audit report, using your equipment list rather than ours.
Book a HeartBeat demonstration