Bed History Report Description
Permissions Required
You must have one of the following permissions to generate this report:
Run Any Reports, Including Those that Reveal Patient Information.
Run Only Reports That Do Not Reveal Patient Information.
Purpose
A single bed-related event can cause multiple transactions. For example, the event of creating a cleaning request can initiate:
A bed status change (from Clean to Dirty).
A notification prompting a bed cleaner to accept the cleaning job.
The Bed History Report displays transactions related to bed cleaning jobs, beds, notifications, or employees that were triggered by BedTracking®-related events. The report displays, in chronological order, transactions that have occurred during the selected time frame.
Note: All transactions (except notifications and alerts) related to bed cleaning activities appear on the report only after the associated bed cleaning jobs are completed or canceled.
The report includes:
Specific events and details about them. For example, the event might be blocking a bed. The details include the amount of time that the bed spent in Blocked status.
The statuses of environmental services (EVS) beds at the time that the events occurred.
EVS bed status changes that resulted from a specific event. For example, if the Status column shows that the bed was in CleanNext status at the time that the Change Cleaning Request Priority event occurred, then the Event Details column shows that the previous status of the bed was CleanNext. If a bed was occupied when a spill cleaning request was created, then the Status column shows Spill (Occupied).
Status transitions of completed or cancelled bed cleaning jobs and spill cleaning jobs (if the spill clean feature is enabled). For example, if a job's status is changed from CleanNext to Stat, then the prior status is noted as CleanNext in the Event Details column.
Bed size changes. (Changes to other bed settings are not included.)
Status changes of employees who are associated with bed or spill cleaning jobs in the units shown or whose memberships include the units shown. If an employee puts a job in progress and the employee's status changes to In Progress, then if the Type column shows User, the Status column shows In Progress.
Notifications and alerts related to transactions associated with events on the report. For example, if a cleaning request was created and there are no bed cleaners signed in who can respond to the cleaning request, then a No Coverage Alert is sent to the supervisor. The report includes both the notification sent about the available job and the No Coverage Alert sent to the supervisor.
Note: See About the Report Data for restrictions concerning locations that appear on the report.
Report Parameters
Criteria selected when the report was being generated appear under Report Parameters. An example is the name of the campus selected when the report was generated.
About the Report Data
Only locations that are associated with the BedTracking® application and that are within the membership of the user who generated the report are included.
For transactions related to bed cleaning jobs, only transactions associated with completed or cancelled jobs are included.
Only beds in units that are within the membership of the user who generated the report appear.
If the user who generated the report chose to include spill clean information, then statuses, events, and event details related to spill cleaning jobs appear on the report.
Only transactions that occurred within the selected date range and shift appear on the report. However, if a shift starts on the end date of the report date range and ends on the next day, data from the entire shift will be included on the report. For example, if the end date of the report is September 2, 2012 and a shift started at 11:00 PM on September 2 and ended at 7:00 AM on September 3, then data from the entire shift, including the part on September 3, will be on the report.
Bed History Report Column Descriptions
The following information appears in the columns on the Bed History Report.
This column. . . | Displays. . . |
Unit | This column appears only if the report output is an unformatted .xls file. It shows the unit where the bed is located. |
Bed ID | The IVR ID code of the bed. |
Bed Abbr | The abbreviation used to represent the bed name (for example, B122A for Bed 122A) |
Date/Time | The date and time that the transaction event occurred. If the Type column shows that the transaction type is Notification, then the column displays the date and time that the notification was sent. |
Status | Depending on the transaction type, this column could show the status of the bed at the time shown in the Time column, or the employee status at the time shown in the Time column, or it could be blank. If the Type column displays: User—The Status column displays the employee’s status at the time shown in the Time column (for example, Log In for the Day). Bed—The Status column displays the status of the bed at the time shown in the Time column. Job—There was a bed-cleaning job associated with the bed. The Status column displays the status of the bed-cleaning job at the time shown in the Time column. Notification— If a notification or alert was triggered by a bed-related or bed-cleaning-related event, then this column displays the status of the bed at the time shown in the Time column. If an alert or notification was not related to a bed or a bed cleaning job, then this column is blank. Examples are alerts about employee lunch periods or breaks or about employees in Available status. |
Type | View this column to learn whether the event is employee-related, bed-cleaning-job-related, bed-related, or notification and alert-related. The possible values are: User—If the transaction is related to employee status changes, but was not triggered by bed cleaning activity. Examples are Log In for the Day, Lunch, Break. Bed—If the transaction concerns an EVS bed, but is not related to a bed cleaning job. Examples are a bed size change or a bed status transition, such as “Occupy Location." Job—If the transaction concerns the status transition of a bed cleaning job. Notification—If the transaction concerns a notification or alert. |
User | The user responsible for the transaction. For example, the column might display the user who selected Set Location Clean. If Interface appears, then the transaction happened automatically and was not generated by a user. |
Event | The event that triggered the transaction. [See a list of events that could appear in the Event column] |
Event Detail | Additional information about the triggering event. [See a list of events that could appear in the Event column and examples of event details] |
Bed not Showing Information on Bed History Report
When running the Bed History report, there is no information showing for patients in a bed or cleaning jobs.
Solution
This can occur when EVS Service is not enabled in the location settings.
To enable this setting to have this information display in a Bed History Report, navigate to Admin Tool > Unit Managment > Unit > Location > Bed Settings > Enable "EVS Service"