Glossary
Definitions and breakdowns of terms used throughout the Mirador system.
Jump to:
General Terms
ABHR | Alcohol Based Hand Rub, also referred to as hand sanitizer. |
API | Application Programming Interface. A software intermediary that allows two applications to talk to each other. |
BLE | Bluetooth Low Energy. BLE is designed for very low power operation. |
BLE User Tag | The tag assigned to each user that communicates with the dispenser. |
EAP | Extensible Authentication Protocol. An authentication framework that is used in local area networks (LANs) and dial-up connections. |
LED | Light-Emitting Diode. A light source that emits light when current flows through it. |
Liquid Type | Mirador provides various liquids to be dispensed for varying needs, including ABHR and soap. |
MAC Address | Media Access Control Address. A unique identifier assigned to a network interface controller (NIC) for use as an address for communicating within a network. |
Optical Sensor | A sensor that measures a physical quantity of light and translates it into a form that is readable by a measuring device. |
PCB | Printed Circuit Board. A medium used in electrical and electronic engineering to connect electronic components to one another in a controlled manner. |
PIR Sensor | Passive Infrared Sensor. An electronic device that measures and detects infrared radiation in its surrounding environment used in motion detection. |
RSSI | Received Signal Strength Identifier. The signal strength of a tag as perceived by a dispenser. |
SSID | Service Set Identifier. The name for a Wi-Fi network. |
WPA+ | Wi-Fi Protected Access. A set of Wi-Fi security protocols for a Wi-Fi device. |
Software
Active Dispensers | Dispensers that are not in Inactive status (Approval Pending, Approved). |
Offline Dispensers | Active dispensers that have not had any communication with the system in at least two hours. |
Inactive Dispensers | Dispensers that are in Inactive status, applicable to stock dispensers as well as previously active dispensers that were removed from the field. |
Dispensers Critical Battery | Dispensers with a current battery status of Critical. |
Dispensers Critical Liquid | Dispensers with a current liquid refill status of Critical. |
Dispensers Low Liquid | Dispensers with a current liquid refill status of Low. |
Dispensers Low Battery | Dispensers with a current battery status of Low. |
Active Tag | Tags that are in Active status. |
Inactive Tags | Tags that are in Inactive status, applicable to stock tags as well as previously active tags that were removed from the field. |
Expired Tags | Tags that are in Expired status, applicable to previously active tags that have surpassed their efficacy date. |
User | A user created in the Mirador application that may or may not be assigned a tag. |
Active User | A user that is not in Inactive status. |
Inactive User | A user that is in Inactive status, applicable to users who have not yet been enabled or that have been disabled by an Administrator. |
Registered User | An active user who has an active tag assigned to their user record. |
Unregistered User | A dispenser user who does not and should not have a tag (family, patients, etc.) OR an active tag without an active user assigned to it. |
Unresponsive User | Registered users that have shown no activity in the Insights application for the last 7 days or more. |
Dispense Count | The count of dispense events triggered by all active dispensers. |
Event | Activity captured by a dispenser or by compliance algorithms. |
Dispense Event | An individual activation, i.e., actual liquid dispensed from a unit, triggered by an active dispenser. |
Registered Event | A dispense event where at least one registered user has been captured within the hygiene threshold of the dispenser. |
Unregistered Event | A dispense event where an unregistered user has been captured within the hygiene threshold of the dispenser. |
Compliant Event | A room entry or exit with an associated registered event that occurs within the pre-defined hygiene threshold window for a given registered user. |
Missed Opportunity | A room entry or exit that is not compliant. |
Room Entry | Also known as a check-in, when a BLE tag is first detected in a scan by a dispenser in a given room, provided the tag’s RSSI is stronger than the check-in threshold for that dispenser's scan parameters. |
Room Exit | Also known as a check-out, when a previously checked-in BLE tag is presumed to be no longer in the vicinity of the room as the tag’s RSSI is weaker than the check-out threshold for that dispenser's scan parameters. |
Compliance Duration | The time window established by your organization which determines the acceptable duration, in seconds, between an entry/exit and a registered event to be considered compliant. The default Compliance Duration is 60 seconds. |
Compliance Average | The ratio of compliant event (C) to the sum of compliant events & missed opportunities (C+M) expressed as a percentage. |
Organization | A facility campus, which could include one or multiple buildings. |
Parent Organization | A top-level facility or entity within the organizational hierarchy. Access at a parent org level means that you have access to all child organizations as well. |
Child Organization | Facilities nested within a system OR other non-hospital configurations. Access at a child org level means that you have access to this organization, but not to the parent nor any other child orgs. |
Location | Refers to physical dispenser location/placement within an organization, for example: 7th Floor, 1st Floor. Decoupled but “assumed” subset of this is Dispenser Group (aka “Room”). |
Group | Dispensers are tethered into logical groups, most often patient rooms, which identify location-based events as well as Entry and Exit criteria (when those modules are enabled), for example: Rom 201, Second Floor Hallways, Soiled Utility Room. |
Department | Associated specialties or functional areas within an organization, for example: ER, Radiology, Pediatrics. Departments are classified separately from locations as they are not 1:1 with physical location, as an organization can have both ER and Radiology on the 1st floor. |
Role | A user’s title and/or job function within an organization, for example: Specialist, Radiologist. |
Permissions | The access level / permission set of a user within the application, for example: Org Admin, Staff User. |