What Really Matters
I keep coming back to a basic principle: monitoring, alerts, and reporting are important, but only when they allow you, our users, do things with that information. This is the perspective that drives our continuous improvement as we deploy OneVue.
Until now, we haven’t had a streamlined system to capture user comments on what actions were taken in response to an alarm. Records would show that there was an out-of-range temperature alert on a refrigerator containing medicine, for example, but not what was done about it.
Our new system of “alert resolutions” changes all of that.
Let’s say you’re responding to an alert regarding a temperature excursions for refrigerator containing vaccines. You might receive the email notification, walk to the refrigerator, and discover the door has been left open by accident.
When you resolve the alarm in OneVue, our revised “Alerts” screen will allow you to enter a “corrective action” (with “closed door” in this example), and OneVue will automatically note the duration of the temperature excursion.
Relevant: the CDC Vaccine Storage and Handling Toolkit lists the following recommendations for data capture after a temperature excursion: “General description of what happened.”
By capturing “what happened,” the new alert resolutions will help you stay in compliance, and more importantly, prove it with documentation.
Some Administration Required
While OneVue captures the temperature and time data by default, we need administrators’ help to add the alert resolution—which is the general description of what happened, as in the example above.
Some default options include:
- Sensor manually checked in and reset min/max
- Probe replaced
- Unit already empty
- Contents discarded
- Adjusted thermostat
- Closed door
But if you need to add more detail, you can add text to document, such as where the medications were moved, or what work order was created.
Need more options, or to add additional questions? Admins can visit our alert resolutions page to add, delete, or revise those responses. Admins then need to connect these revised Alert Resolutions to alert rules in order to be mandatory on the Alerts page. (It’s a very flexible design, which means that it can be a bit complicated—take a look at the help files or let me know if you have problems.)
Admins will see three new report types available, all aimed at understanding your account’s users.
- User report—detailed view of each user included. Device classes, account, location, and business unit roles, as well as alert rules which include that user.
- User Role report—view of many users which lists roles and entities (location or BU) and device classes.
- User Alert Rule report—view of multiple users specific to alert rules (includes teams, shifts, and escalations).
Confused? We were too at first, but found there were different problems we were trying to solve and adding too much flexibility was worse than creating three different report types.
You Are the Reason OneVue Exists, Improves
I also wanted to remind you that your feedback matters to me as I prioritize what we do next. If there’s a workflow that bothers you, or a new feature you think would improve your experience, please let me know.
I joined Primex in December, 2017, after spending years in academic research and product development in medical imaging. I’ve been honored to work with the teams here—from development to support to sales—but by far my greatest honor is supporting you, our user, in your mission and role. Keep in touch!