Discharge Disposition: A new Discharge Disposition field is available for clients using either the Capacity Management Suite® solution or the Bed Management Suite® solution. This read-only field is populated through the HL7 interface in the PV1.36 segment and can be added to the PreAdmitTracking® or PatientTracking Portal® consoles. A Discharge Disposition is an indication of what will happen to a patient after discharge. Examples of these values include Patient Going Home, Skilled Nursing, Rehab Facility, and Transfer. A Discharge Disposition helps caregivers doing discharge planning to act accordingly. Discharge Disposition can be used as an Advanced Filter condition.

Daily Clean Job Update: Daily Clean jobs for transferred patients now clear the job’s To Do status and update the reason code to System: Patient Transferred. The bed is then cleaned by the discharge bed cleaning workflow. Note: One or both of the Unit Information settings, Dirty Bed on Intra-unit Transfer or Dirty Bed on Intra-room Transfer, must be enabled for this enhancement to work for patients with the associated type of transfer.

Inbound HL7 Messages: Configurations are in place for customers who have the Capacity Management Suite® Shell to use with inbound messages. TeleTracking assistance is required for these settings. Note: These configurations are not for clients who currently have the BedTracking® standalone application, the Capacity Management Suite® solution, or the Bed Management Suite® solution.

App Refresh: The TeleTracking EVS™ mobile application now refreshes when it is brought to the foreground or unlocked.

Mobile Notification Sounds: In the Settings > Notification Sounds page, users of the TeleTracking EVS™, Transporter™, and Nurse™ mobile applications can now choose a different sound to replace the default tone that plays when receiving notifications.

Mobile Notification Sound: Users of the TeleTracking EVS™, Transporter™, and Nurse™ mobile applications can now change the sound played when receiving a notification. Users must navigate to Settings which will allow them to select a different sound for when push notifications are delivered to the device.

HL7 Outbound Messages Update: When a customer’s system is configured to send outbound A20 messages for Blocked bed statuses, if a reason code is associated with the block, the Capacity Management Suite® solution sends the reason code in the OBX5 segment of the A20 message to the Admissions Discharges Transfers (ADT) system. Administrators specify the bed statuses for which messages are sent in the Bed Status ADT Mapping section of the BedTracking® Global Settings page.

Reports

All of the Capacity Management Suite® Solution

Multi-Stage Bed Cleaning Available:

Mobile

All the Capacity Management Suite® Solution

Mobile

Tablet Navigation:

Deactivating Users:

TeleBot:

Admin Tool

AssetTracking® Application Integration

Mobile

Admin Tool

Notification Groups

Mobile

Daily Cleaning Jobs

TeleBot

Alerts Enhancement:

PatientTracking Portal:

BedTracking® Application and TeleTracking EVS™ Mobile Application:

Admin Tool:

TeleTracking IQ® Platform Integration:

PatientTracking Portal®:

PreAdmitTracking® and PatientTracking Portal® Applications:

Mobile:

All the Capacity Management Suite™ Solution:

Security:

Admin Tool:

TransferCenterIQ™ Application Integration:

Mobile:

Microsoft® .NET Framework:

Mobile:

OS Update: The TeleTracking EVS™, TeleTracking Transporter™, and TeleTracking Nurse™ mobile applications now support iOS version 15.

Reports:

TransportTracking™ Application:

All of the Capacity Management™ Suite:

Mobile:

Mobile:

Bed Status Timestamp: EVS employees using the TeleTracking EVS™ mobile app can now view the date and time that the bed’s current status was set. The timestamp appears in the My Jobs page in the bed card’s color-coded header along with the bed status.

Mobile:

Mobile:

Browsers:

Mobile:

PatientTracking Portal® Application:

IQ-Enabled Capacity Management Suite:

Mobile:

Multiple Instances of the Capacity Management Suite®:

TransportTracking™ Application:

Standard Reports:

TransportTracking™ Application:

Installation Program:

PreAdmitTracking® Application and PatientTracking Portal® Application:

Mobile Applications:

All of the Capacity Management Suite:

Mobile Apps:

All of the Capacity Management™ Suite:

PatientTracking Portal® Application, PreAdmitTracking® Application, and BedTracking® Application:

Mobile:

Mobile:

PatientTracking Portal® Application:

All of the Capacity Management™ Suite:

SQL Server® 2017 and 2019 Supported:

64-Bit Compatibility:

All of the Capacity Management™ Suite:

Integration with the Classic TransferCenter™ Application and the Clinical Workflow™ Suite:

Integration with the AssetTracking® Application:

Mobile Apps for Capacity Management:

PreAdmitTracking® Application:

PreAdmitTracking® Application and PatientTracking Portal® Application:

PatientTracking Portal® Application:

TransportTracking™ Application:

TeleTracking Real-Time Locating System™ Solutions Integration:

All of the Capacity Management™ Suite:

PreAdmitTracking® Application:

PatientTracking Portal® Application:

All of the Capacity Management™ Suite:

All of the Capacity Management™ Suite:

Administrators Can Deactivate Levels of Care:

Users Choose to Receive Patient Location Change and Patient Discharge Notifications on the My Notifications Tab:

Microsoft® Silverlight™ No Longer Required:

The Interactive Voice Response System (IVR) is Supported in Cloud-Hosted Capacity Management Suite:

Compatibility with TeleTracking Mobile Apps v2017.3.1:

PatientTracking Portal® Application:

PreAdmitTracking® Application and PatientTracking Portal® Application:

TransportTracking™ Application:

New Mobile Apps Available:

About the apps:

App requirements:

Additional Supported Versions of Microsoft® SQL Server® and Microsoft® Windows Server:

"Always On" Functionality Supported in Microsoft® SQL Server® 2014 and 2016: "Always On" mode validated for SQL Server 2014 (both ON and OFF) and for SQL Server 2016 (ON).

Mozilla® Firefox® Browser Supported:

Microsoft® .NET Framework 4.6.2 Supported:

Adobe Acrobat Reader DC Supported:

Apple® iOS 11.1 Validated:

Screen Alerts Button Updated:

Additional Unit or Ward Categories:

PreAdmitTracking® Application and PatientTracking Portal® Application:

TransportTracking™ Application:

TeleTracking IQ® Platform Admin Menu Reorganized for Easier Use:

PreAdmitTracking® Application:

PatientTracking Portal® Application:

All of the Capacity Management Suite®:

TransportTracking® Application:

Ready-to-Move:

Assigned Bed:

New Capacity Management Suite® Hosting Options and Options to be Enabled through the TeleTracking IQ™ Platform:

Integration with TeleTracking Real-Time Locating System™ Solutions:

TeleTracking Discharge Efficiency Report:

PatientTracking Portal® Application:

TransportTracking™ Application:

TeleTracking IQ™ Platform:

BedTracking® Application:

PreAdmitTracking® Application:

PatientTracking Portal® Application:

TransportTracking™ Application:

Navigation Update:

Mobile:

Show All Units/Wards View-Only Bedboard:

Electronic Bedboard Capacity Clarification:

TeleTracking Nurse™ App Clarification:

Campus Select Feature Clarification:

Clarification for SQL Always On Feature:

Release Note Correction:

WCTP Clarification:

Standard Reports:

TransportTracking Mobile Application:

Variable Membership (Floaters) Update:

Mobile for Capacity Management:

All of the Capacity Management Suite:

Mobile Apps for Capacity Management:

TLS 1.2 Support:

ADT (Admit, Discharge, Transfer System) Transactions

PatientTracking Portal® Application

Technical Requirements Guide Update:

Issue Resolution (OP-2608):

PreAdmitTracking® Application:

PreAdmitTracking® Application and PatientTracking Portal® Application:

TransportTracking™ Application:

All of the Capacity Management Suite:

PreAdmitTracking® Application:

TransportTracking™ Application:

PreAdmitTracking® Application and PatientTracking Portal® Application:

PreAdmitTracking® Application and PatientTracking Portal® Application:

TransportTracking™ Application:

All of the Capacity Management Suite®:

PatientTracking Portal® Application:

All of the Capacity Management Suite®:

[OP-8872] After a transporter had accepted a job changing it to a Dispatched status, an update from the Admissions Discharges Transfers (ADT) interface assigned the patient to a home location and cancelled the transport job. This has been fixed, and now ADT updates that place a patient in a home location do not automatically cancel the patient’s transport job.

[OP-8879] Employee/Supervisor History standard report did not display the employee’s section or zone. This has been fixed, and now the section or zone where the employee signed in is displayed in the report.

[OP-8942] The ADTBedRequestResult displayed incorrect values when it was returned to the Electronic Medical Records (EMR) system. The OrderControl and OrderContorlCodeReason values were reversed. This has been corrected, and now the ADTBedRequestResult has the correct values for OrderControl and OrderContorlCodeReason when it is sent to the EMR system.

[OP-8406] Some customers experienced degraded performance and responsiveness for a period of time. This has been fixed, and now the Capacity Management Suite® solution performs as expected.

[OP-8785] Some customers noticed slowed performance. This issue has been addressed by tuning the code in a stored procedure to not select from inactive users.

[OP-8217] A variable user’s base location campus appeared on the BedTracking > Employees tab. This has been corrected, and now the BedTracking > Employees tab displays the employee's selection during login as expected.

[OP-8748] The Bed History report did not generate in the time allowed. This has been fixed, and now the Bed History report successfully completes in the time allowed.

[OP-8726] The Average Response/Turn Time Report ran slowly for some customers. This problem has been fixed by a change to the code.

[OP-8477] Users who have the Capacity Management Suite® solution integrated with the TeleTracking IQ® platform could not view or access the links in the footer of the PatientTracking Portal® list view. Wallboard users could not access the secondary login option. This has been fixed, and now the footer appears on the PatientTracking Portal® list view, and wallboard users can access the secondary log in option.

[OP-8623] An error appeared when the Daily Cleans report ran and the report could not be generated. This has been fixed. The Daily Cleans report has been re-factored and indexes have been added. Now the report runs successfully without errors.

[OP-7059] Deactivated transporters were not included on any TransportTracking™ application reports. This problem has been fixed, and now all transporters, including deactivated ones, appear on the TransportTracking reports.

[OP-8637] In some situations, a patient’s alias was not created or updated. This issue has been fixed, and now an alias for a patient is created and updated according to the campus' configuration.

[OP-8127] A synchronization error sometimes occurred because bed requests that were sent from the TransferCenterIQ™ application to the Capacity Management Suite® solution could not be canceled. This issue has been fixed, and now bed requests made in the TransferCenterIQ™ application can be canceled and do not cause errors to appear in the Capacity Management Suite® solution.

[MOBA-742] Sometimes selecting Clear All in the Filter Patients By filter and the Bed Status filter of the TeleTracking Nurse™ mobile application only cleared the first option in the filter list. This has been fixed, and now Clear All clears all the previously selected options, as expected.

[MOBA-304] When transporters and EVS employees using Android devices were on break, the Sign out button appeared in the TeleTracking EVS™ and TeleTracking Transporter™ mobile applications, even though the users could not sign out. This has been fixed by adding text to the user interface that says, Unable to sign out while on break in the TeleTracking EVS™ and TeleTracking Transporter™ mobile applications.

[OP-7185] Customers saw an error when they tried to navigate to the second page of the BedTracking Dashboard, and the page did not refresh. This has been corrected, and now customers can successfully navigate to multiple pages of the BedTracking Dashboard.

[OP-7312] In the Asset/Patient/Staff Interaction report, the name format appeared incorrectly as the first name followed by a comma and then the last name. This issue has been fixed, and now names appear in the Asset/Patient/Staff Interaction report as last names followed by a comma and then the first name, as expected.

[OP-8354] When users selected a number of columns to freeze in the Console Settings dialog box, the selected columns expanded to fill the entire screen width, and a scroll bar did not appear. This has been fixed, and now the frozen columns retain their original width while locking in place, and a scroll bar allows users to see the other columns to the right as expected.

[MOBA-718] When multiple patients in the same room have the same isolation type, the room's Daily Cleans job card listed the isolation type more than once. This has been fixed and now, the Daily Cleans job card lists the isolation type once if multiple patients in the room have the same isolation type.

[MOBA-316] The TeleTracking Nurse™ mobile app does not load when one or more patients in the current unit have a pending transfer within the same unit and when a bed is assigned without a Target Unit being specified. This has been corrected and now, patients with a pending transfer within the same unit appear as Intra Transfer on the user interface.

[OP-6119] If the Asset/Patient/Staff Interaction report was run over midnight, the report displayed some staff entries from days that occurred after the selected end time. This has been fixed, and now the report displays data from only the period between the start and end times selected in the report criteria.

[OP-7295] Staff members were automatically cleared from the Staff Assignment list even though they were still available to be assigned. The problem was that the PatientTracking Portal® application did not use the value in the Purge Staff from Staff List After (Days) setting in the Staff Assignment dialog box of the Admin Tool. This has been fixed, and now staff members remain on the Staff Assignment list for the entire time that is configured in the Purge Staff from Staff List After (Days) field.

[OP-6935] When a staff member’s name was updated, the update did not appear on the Staff Assignment list. This has been fixed, and now the Staff Assignment list displays updates to staff members' names.

[RTLS-2996] Running an Asset Search in the Capacity Management Suite® solution took a long time and caused a performance problem within the Microsoft SQL database. This has been fixed, and now the Asset Search results are returned in a timely manner.

[MOBA-331] When navigating to some TeleTracking mobile application screens, the application appeared to jump through several previous screens before reaching the one the user selected. This has been fixed, and now the screens do not jump through previous screens when navigating.

[MOBA-728] When a TeleTracking mobile application appeared in the foreground of a device, Instant Notify messages sent to the user did not display the expected banner, sound, and vibration. This has been fixed, and now users see Instant Notify banners when a TeleTracking mobile application appears in a device’s foreground.

[MOBA-714] When users opened the TeleTracking Nurse™ mobile application, they immediately saw a message asking about accepting notifications. If the users denied the notifications, they could not log into the mobile application. This has been fixed, and now the notification message appears after users log into the TeleTracking Nurse™ mobile application.

[MOBA-719] Users saw an error at login if they had the ability to log into two or more campus that each had different features enabled. This has been fixed, and now users who can chose which campus to log into do not get an error at log in.

[MOBA-745] Users had to enter the mobile URL each time that they signed in. This has been fixed, and now the Mobile Device Management program automatically saves the mobile URL. Consequently, users do not need to enter the mobile URL when they sign in.

[OP-6890] When viewed on Google Chrome™ (on Android) and Apple® Safari® browsers (on iPad), the standalone and IQ-Enabled versions of the PatientTracking Portal® application displayed column headers that did not align with their corresponding columns. This has been fixed, and now the headers align with their corresponding columns on Google Chrome™ and Apple® Safari® browsers.

[OP-5414] A security vulnerability with Active Reports was resolved by adopting Active Reports 15.

[OP-7946] In all Standard and Quick Reports, the last character of the report parameters was truncated. This has been fixed, and now the report parameters display complete text as expected.

[OP-8004] An error appeared and the Asset/Patient/Staff Interaction Report could not generate when users attempted to run it with one or more patients selected. This has been fixed, and now the report runs successfully without an error.

[OP-7999] On the Bed Dashboard, the numbers displayed in the Udef8 and Udef9 bed status columns were summed and displayed in the Delayed bed status column. This has been corrected, and now the number of beds in a Udef8 and Udef9 bed status are not added to the Delayed bed status on the Bed Dashboard.

[OP-8015] Some customers noticed the tooltips displayed on the bedboard had extra text that said, “DONOT Change the German value.” This text has been removed from the bedboard tooltips.

[OP-8034] Users could not change a bed’s status from Clean to Udef9. This has been fixed, and now users can change a bed’s status from Clean to Udef9.

[OP-8192] When users hovered over a spill location in the Spill column of the Discharge and Spill Clean multi-view listing, the pop-up message that appeared stated “no user notified” even though a user had been notified. This issue has been fixed, and now the pop-up message for a spill location on the Discharge and Spill Clean multi-view listing accurately displays the name of the last employee who was notified of the spill clean job.

[MOBL-127] The TeleTracking mobile applications automatically calculate the number of temporary groups that users can select based on any Floater Notification Groups the users may have inherited from their units or clusters. If users tried to select more than the allowed number of temporary groups on the Settings > Temporary Groups page, no groups were saved and no message appeared to explain why they could not select groups. This has been corrected, and now a message appears that informs the users how many temporary groups they can select if they try to select too many.

[MOBA-240] The Android operating system back button on the user interface did not work well. This has been fixed, and now although the Android OS back button might appear on the user interface (if enabled), users navigate back to the previous page by selecting the application back arrow.

[MOBA-252] Level of Care appeared on the push notification banner and when the notification was initially opened, but an in-app notification for Level of Care or Hospital Service was not generated and did not appear in the Notifications list. This has been fixed. Level of Care and Hospital Service changes generate in-app notifications and appear on the Notification list after the notification is opened.

[MOBA-255] The word “Verweildauer” appeared in the English versions of the TeleTracking Nurse™ mobile applications instead of “Length of Stay.” This has been fixed, and now the English phrase “Length of Stay" appears in the TeleTracking mobile applications for English speaking users.

[MOBA-296] When users signed into the TeleTracking Nurse™ mobile application and selected a cluster for their membership, nothing appeared on the Dashboard. This has been fixed, and now the Patient Overview chart appears on the Dashboard when users select a cluster upon signing in.

[MOBA-316] The mobile app does not load when one or more patients in the current unit have a pending transfer within the same unit and when the assigned bed does not have a Target Unit specified. This has been corrected and now, patients with a pending transfer within the same unit appear as Intra Transfer on the user interface.

[MOBL-564, MOBA-347] Users who employed gesture navigation on the TeleTracking mobile applications were directed to the wrong workflow. The Gestures Navigation option is not supported by the TeleTracking mobile applications on iOS and Android operating systems.

[MOBA-714] When users opened the TeleTracking EVS™ and TeleTracking Transporter™ mobile applications, they immediately saw a message asking about accepting notifications. If the users denied the notifications, they could not log into the mobile application. This has been fixed, and now the notification message appears after users log into the mobile application.

[OP-6220] Some customers noticed that there was a delay between the time that a transporter requested assistance and when the job was dispatched to the secondary transporter. This has been fixed, and now there is no delay when an assist job is dispatched to the secondary transporter.

[OP-8092] Users were able to set the default origin or destination priority to zero. This issue has been fixed, and now zero cannot be set as a default origin or destination priority. Users can only set the default origin or destination priority to numbers between one and nine. Existing records that have a default priority of zero will be automatically changed to a priority of one.

[OP-6996] Changes made on the Admin Tool > Patient Alias Configuration page did not appear on the PreAdmitTracking® and PatientTracking Portal® application list views, even though a confirmation message appeared. This has been fixed. This was previously a Known Issue in version 2022.11.

[OP-7180] The archive program did not purge some patient records because removal was based only on the Last Modified Date. This has been fixed by adding Expected Admit Date Time to the removal criteria.

[OP-1576] On large touchscreen displays, users saw an error when they tried to log out using the secondary Logout button. This has been fixed, and now users can log out with the secondary Logout button on touchscreen displays, as expected.

[OP-6166] In the PatientTracking Portal® application, when users searched for patients by entering the bed ID in the search field, the patients were not found. This has been fixed, and now patients appear in the search results when users search for them using their bed ID’s.

[OP-7676] On the User Management page, when administrators changed a user’s Membership type from Fixed to Variable, then in the Membership & Assignment section the Variable Membership Campus Map tab appeared as expected, but the Membership tab continued to display the previous fixed assignments. This has been corrected, and now when the user’s Membership type changes from Fixed to Variable, the Variable Membership Campus Map tab appears and displays the variable assignments while the previous fixed assignments clear from the Membership tab.

[RTLS-2755] Customers were unable to attach badges with a Battery Status of Medium to patients, assets, and staff. This issue has been resolved.

[OP-5967] The Transport Priority Change Report displayed times as UTC time rather than the local time. This issue has been fixed, and now local times appear in the Transport Priority Change Report.

[OP 7589] The Daily Cleans Report did not generate when Summary View was set to No in the report criteria page. This has been fixed, and now users can create a Daily Cleans Report with a Summary View.

[OP-6627] The Capacity Management Suite® solution did not integrate with the Rauland® Responder® Enterprise nurse call system. This has been fixed, and now the Rauland® Responder® Enterprise nurse call system and the Capacity Management Suite® solution integrate successfully.

[OP-6887] When using the PreAdmitTracking® or PatientTracking Portal® applications on an iPad operating system viewed on Google Chrome™ browser, users saw an error at each refresh. This has been fixed, and now when the PreAdmitTracking® or PatientTracking Portal® applications refresh on an iPad operating system using Google Chrome™ browser, an error does not appear.

[OP-7354] Users saw an error when they added the Nurse column to the Patient Search list view via View Options > Configure Columns. This has been fixed, and now users can successfully add the Nurse column to the Patient Search list view.

[OP 7358] Sometimes users saw an error when they selected a unit/ward in the Unit Filter of the Beds tab and then clicked Apply. This has been fixed, and now users do not see an error when they filter the Beds tab by unit/ward.

[OP-7420] When an EVS employee has an In Progress status for a Daily Cleaning job, that employee is not available for selection in the Employee list of the Notify New dialog box. This has been fixed, and now EVS employees can be selected for a notification of another cleaning job while they are performing a Daily Cleaning job.

[MOBL-452] When transporters and EVS employees using iOS devices were on break, the Sign out button appeared in the TeleTracking EVS™ and TeleTracking Transporter™ mobile applications, even though the users could not sign out. This has been fixed by adding text to the user interface that says, Unable to sign out while on break in the TeleTracking EVS™ and TeleTracking Transporter™ mobile applications. (Note: This update is temporarily only for users with iOS mobile devices)

[OP-7553] An error appeared sometimes when supervisors changed the transporter who was assigned to a transport job. This has been fixed, and now supervisors can successfully update the transporter assignment.

[OP-7560] The membership screen did not appear for variable users when they attempted to log in. This has been fixed, and now variable membership users can successfully select their membership when they log in.

[OP-5421; 7195] The Capacity Management Suite® solution removed staff members who had been inactive for seven days rather than for the number of days that were defined in the Purge Staff from Staff List After (Days) setting on the Unit PatientTracking Portal Settings page. This has been fixed, and now staff members are removed in the number of days that are set in Purge Staff from Staff List After (Days).

[OP-7132] Transporters and EVS employees who did not have jobs did not receive Job for You notifications. This has been fixed, and now transporters and EVS employees receive Job for You notifications as expected.

[MOBL-322] In the TeleTracking Nurse™ mobile application, when users selected Now for Ready to Move, the patient’s card did not update. This has been fixed, and now selecting Now in Ready to Move updates the patient’s card with the correct Ready to Move time.

[MOBL-243] In the TeleTracking Nurse™ mobile application, completed timers appeared in the same format as in-progress timers. This has been fixed, and now completed timers appear in a dark gray box to distinguish them from in-progress timers.

[OP-7170] The campus PreAdmitTracking Global Settings page did not display the correct description for the Create bed request for Outpatient when moved to Specialty Holding bed row. This has been fixed and now the Create bed request for Outpatient when moved to Specialty Holding bed description is correct on the campus PreAdmitTracking Global Settings page.

[OP-7215] Users had difficulty selecting an origin or destination in the Transport Request dialog box because locations cleared from the Recent tab of the Origin / Destination finder section. This issue has been fixed, and now the locations in the Recent tab of the Origin / Destination finder persist and are available for selection.

[OP 6742] Staff members could not be assigned to beds because the Save and Save & Close buttons did not appear on the Staff Assignment dialog box. This issue has been fixed, and now the Staff Assignment dialog box displays the Save and Save & Close buttons as expected.

[OP-7158] The Daily Cleans report did not use the Daily Clean Min/Max Time values in the campus’s Global Settings for the report's Exclude from Averages > Adjusted Min Clean and Adjusted Max Clean values. This has been fixed, and now the report’s average min and max times are supplied by the Global Settings values for Daily Clean Min/Max Time.

[OP-7159] The Search Employees dialog box in the Daily Cleans report did not find some employees who existed in the system. This has been fixed, and now the employee search for the Daily Cleans report returns all employees who exist in the system if they match the entered criteria.

[OP-7235] Customers saw an error when they tried to add values to the Reason Code dictionary. This has been fixed, and now users can add new values to the Reason Code dictionary.

[OP-6992] When users clicked the Help button, a blank window appeared. This has been fixed by implementing an updated look for the Capacity Management Suite® solution help. Users still see the same topics and navigation in a tri-pane format. However, some functions are in different places on the interface and some functions now appear as icons rather than text buttons. For example, the Contents and Glossary are now tabs in the top of the left navigation pane, and the Search bar is in the top right of the window. The Print topic, Go back to previous topic, and Remove Highlights functions appear as icons to the right of the Contents and Glossary tabs. The collapse navigation function is an arrow in the middle of the right side of the navigation pane. To search within the currently visible topic users can click Control-F and type the text in the search box that appears. These changes improve the performance of the Help while delivering the same content and functionality.

[OP-6465] An error appeared on any page that was not in the PreAdmitTracking® application or the PatientTracking Portal® application, when users selected an alert to open the Patient/Placement Details dialog box and then selected Observation or Hold Timer. This has been fixed, and now the Observation or Hold Timer details appear when users select them from the Patient/Placement Details dialog box.

[OP 6728] Users could not view the Floor Plan in the Capacity Management Suite® solution. This has been fixed, and now the Floor Plan view appears when users select the Floor Plan button on the BedTracking®, PreAdmitTracking®, PatientTracking Portal®, or the TransportTracking™ application pages.

[OP-6960] When supervisors selected a number in the In progress column of the BedTracking® application Employee Dashboard, no employee appeared who was performing a daily clean job. This issue has been fixed, and now the employees who are performing daily clean jobs appear when supervisors select the number in the In progress column of the Employee Dashboard.

[OP-6964] The daily clean In Progress status does not appear in the Status column on the Employee List or in the Current Status field on the Employee Details page. This has been fixed, and now In Progress status appears on the Employee List and the Employee Details page.

[OP-5990] The User Master List report displayed the Last Login Date in mm/dd/yyyy format even when the Enterprise-wide Settings had dd/mm/yyyy format selected. This has been fixed, and now the Last Login Date in the User Master List report displays in the same format that is selected in the Enterprise-wide Settings.

[OP-6666] On the User Master List report, the Last Login Date appeared in UTC time instead of the time in the campus server’s local time zone. This has been fixed, and now the Last Login Date is converted to the local time zone, as expected.

[OP-6803] When the Master Configuration > Language Configuration page was set to English (United States), the Daily Cleans report > Group by criteria selection list displayed “Ward” rather than “Unit.” This issue has been fixed, and now the Daily Cleans report > Group by criteria selection list displays “Unit” when the Master Configuration > Language Configuration page is set to English (United States).

[OP-6925] Users saw an error message when they selected the Report Selection link at the top of the Daily Cleans report criteria page to return to the Report Selection page. This issue is fixed, and now when users select the Report Selection link at the top of the Daily Cleans report criteria page, no error appears and the Report Selection page appears as expected.

[OP-6926] The BedTracking® application Employee Dashboard did not display employees who had started a daily clean job in the Available column. This has been fixed, and now the Employee Dashboard > Available column displays employees who are working on daily clean jobs as well as discharge clean jobs.

[OP-6942] The following issues appeared in the Daily Cleans report output: When Employee was selected in the Group by criteria, each employee’s work appeared grouped by unit. This has been fixed, and now each employee's work appears under their name regardless of the unit in which the work was performed. When Employee was selected in the Group by criteria, the Unit column heading was aligned flush left rather than centered. This has been fixed, and now the Unit column heading is centered above the Unit column. If a user ran the report for the current day, the jobs that no employee worked on did not appear in the report. This has been fixed and now all the To Do jobs that were created appear in the report even if no employee worked on them.

[OP-6961] The Employee Details page of the BedTracking® application > Employees tab did not display any discharge cleaning jobs in the Employee Statistics section. This issue has been fixed, and now both the daily clean jobs and the discharge clean jobs appear in the Employee Statistics section of the Employee Details page.

[OP-6402, OP-6403, OP-6404, OP-6405] The date format in the following reports did not display the correctly: Bed Assignment Priority History Report Census Analysis by Day of Week Report Census Analysis per 12 Week Period Report Weekly Discharges/Transfers Report This has been fixed, and now these reports display dates in the format that is configured in Admin Tool > Enterprise Wide Setting > General > Date Format.

[OP-6241] The following fields did not appear on the Patient Audit report: Patient Hold Type, Patient Hold Start Date, Patient Hold End Date. This was fixed in version 2022.05, and now all the appropriate fields appear on the Patient Audit report as expected.

[OP-5934, OP-6389] The archive process did not include some Admissions Discharges and Transfers (ADT) transactions. This has been fixed, and now the archive process includes all ADT transactions.

[OP-6530] Enabling Display milestone progress on Bed Board for any active patient status caused duplicates of the Transfer milestones and the Discharge milestones to appear. This has been fixed, and now duplicate milestones do not appear. When users hold their pointers over a bed’s milestones, a tooltip displays the Discharge and Transfer milestones grouped separately with the Transfers milestones group appearing first in the list.

[OP-5910] Sometimes TeleTracking Transporter™ mobile application users could not change the status of transport jobs to InProgress unless they entered the job ID. This has been fixed, and now users do not have to enter the job ID to accept jobs and put them in progress.

[OP 6251] Transporters did not receive notifications for new transport jobs or instant messages in the TeleTracking Transporter™ mobile application. This has been corrected, and now the TeleTracking Transporter™ mobile application receives notifications and instant messages as expected.

[OP 6379] New patient attributes included in a HL7 discharge message were not included in the patient’s record in Capacity Management Suite® solution. This has been fixed, and now patient attributes that are included in a HL7 discharge message are included in the patient’s record in CMS.

[OP 6340] Users saw an error message when they tried to run the Patient Audit detailed report. This has been fixed, and now users can successfully run the Patient Audit detailed report without an error.

[OP-6064] Users saw an error when they sorted the Patient Transports by Apt/Pend Time and then attempted to navigate to another page of the list. This has been fixed, and now users do not see an error if there is more than one page of Patient Transports list which is sorted by Apt/Pend Time, and users navigate to another page.

[OP 6238] The Automated Patient Discharges report did not display events where the patient's badge was dropped in the discharge location's drop box. Instead, the report only displayed the events that came from the Admissions Discharges and Transfers (ADT) system. This has been fixed, and now the report displays data from the patient’s badge in the discharge location’s drop box as well as the ADT system’s data.

[OP-5047, 5747] In health systems with IQ-Enabled Capacity Management Suite® solution, users could not run the same report more than once with different criteria selected because the Run Report button was disabled after running the first report. Users had to close the report dialog box and open it again to run additional reports inputting different values. This has been fixed, and now the Run Report button remains active after a report is generated. Users do not have to close the dialog box and re-open it to be able to run the same report multiple times with different values selected.

[OP-6306] Some parts of the Capacity Management Suite® solution code continued to reference functionality in Microsoft .Net Framework version 4.6.2 instead of version 4.8. This has been resolved, and now the code no longer references Microsoft .Net Framework version 4.6.2 functionality.

[MOBL-19] When users signed into the TeleTracking Nurse™ mobile application, they could see patients who were not in their membership and sometimes could not sign in the next day. This problem has been fixed, and now TeleTracking Nurse™ application users only see the patients that they have permission to see, and they can sign in as expected.

[MOBL-20] When a notification arrived while a user was viewing any screen in the TeleTracking EVS™, TeleTracking Transporter™, or TeleTracking Nurse™ mobile applications, a red dot did not appear on the bell icon to indicate that there was an unread notification. This has been fixed, and now the red dot appears on the bell icon as a notification arrives.

[MOBL-31] If TeleTracking Nurse™ mobile application users closed the application while in the membership screen and then signed in again immediately, then the correct membership selection screen did not appear. This has been fixed, and now the correct membership selection screen appears when users close the TeleTracking Nurse™ mobile application from the membership screen and sign in again.

[OP-5730] Beds that were hidden in View Options > Show/Hide Beds for a Personal console appeared when users changed and saved the console to a Group console. This has been fixed, and now the hidden beds remain hidden when a Personal console is saved as a Group console.

[OP-5943] Administrators could not find patients using the search on the Advanced tab of the Admin Tool > RTLS > Patient Badging page. The search omitted the first character of the search criteria. This has been fixed, and now the Advanced search includes the entire criteria as expected.

[OP-6151] A large number of PatientAudit Log entries caused some customers to experience slowness when the archive and reports ran. This has been fixed in this release.

[OP-6105] Patient records were incorrectly updated with information for other patients in different campuses who had the same Visit Numbers. This has been fixed, and now patients in different campuses with the same Visit Number are updated with their own information.

[OP-2596] The PatientTracking Portal® application Unit Patients report did not display the patient's gender because the reports were printed in black and white and the gender was displayed on the user interface as a color (pink for female, blue for male, white for unknown). This has been fixed, and now the patient's gender is displayed as text in the report.

[MOBL-21] In the TeleTracking Nurse™ mobile application, the patient’s Observation Timer did not match the timer in the desktop version of the Capacity Management Suite® solution. One timer appeared to have crossed the first time threshold (yellow) while the other appeared to have crossed the second time threshold (red). This has been fixed, and now the Observation Timer in both applications displays the same threshold status.

[OP-6159] When using the desktop version of the BedTracking® or TransportTracking™ applications on a tablet, users who selected any tab saw an error message stating “Multiple tabs are open.” This has been fixed, and now the error does not appear when tablet users select tabs in the desktop version of the BedTracking® or TransportTracking™ applications on a tablet.

[OP-6074] During peak discharge hours, the popup when hovering over a bedboard entry took a long time to appear. This has been fixed in the code, and now when users hover their mouses over bedboard entries, the popup information appears in a timely manner.

[OP-6123] Users could not request patient transports because a search of the Patient List did not return any results. This has been fixed, and now the search on the TransportTracking™ application Patient List works as expected.

[OP-4990] Previously, the Clinical Workflow™ suite did not integrate with the Capacity Management Suite® solution’s Census Based Scheduling (CBS). This has been corrected. Now, if health systems use ES Optimizer™ to track nonBedTracking® application tasks for Environmental Services (EVS) employees, then the Clinical Workflow™ suite can access the Census Based Scheduling (CBS) feature via integration with the Capacity Management Suite® solution. Census Based Scheduling can help ensure that bed cleaners can complete their other work, such as routine daily room cleanings, and also complete bed cleaning jobs in a timely manner so that clean beds can be ready for new or transferred patients.

[OP-5414] A Static Application Security Testing (SAST) scan revealed two OS Command injection vulnerabilities. These issues have been corrected.

[OP-5944] When users manually activated a patient, and admitted the patient via the Admissions Discharges Transfers (ADT) system, then the patient’s Expected Admit Date reverted to a past date. This issue has been fixed.

[OP-6026] The success message for deleting a record was the same as the message for saving a record in the Dictionary Management > View Group page. Now the message for deleting a record is appropriate.

[MOB-2596] The Ready to Move functionality did not work for the TeleTracking Nurse™ mobile application when it was integrated with the IQ-enabled Capacity Management Suite® solution. This has been fixed, and now when the IQ-enabled Capacity Management Suite® solution is integrated with the TeleTracking Nurse™ mobile application, then TeleTracking Nurse™ users can set Ready to Move for patients.

[OP-5081] After patients with Pending Discharge/Assigned statuses were transferred to their new non-holding home locations, the bed request continued to display statuses of Pending Discharge/Assigned. This has been fixed, and now the Pending Discharge/Assigned statuses are closed when patients are transferred to their new non-holding home locations.

[OP-5564] The Employee/Supervisor History report timed out before completing. This has been fixed, and now the report completes without timing out.

[OP-5843] The observation timer in the Obs@ column appeared in a color that was not the color set in Master Configuration. This has been fixed, and now the observation time appears red, yellow, or green at the appropriate times as configured.

[OP-5892] Black boxes obscured assets appearing on floor plans that had a diagonal arrangement. This has been fixed, and now black boxes do not appear on top of assets on diagonal floor plans.

[OP-5911] Some users with variable memberships could not login because an error appeared when they selected their memberships. This has been fixed, and now the error does not appear when variable users select their memberships.

[OP-5733] The Capacity Management Suite® HL7 system sent a second Bed Request message with the ORU message when the assigned bed’s status changed. This has been fixed, and now duplicate Bed Request messages are not generated when there is a change to the assigned bed’s status.

[OP-3570] On the Projected Census view, some values, such as long campus or discipline names, were cut off even though sufficient space was available to display them. This issue has been fixed, and now long values fill the available space based on the standard supported screen resolution (15” 1024 x 768 for desktop displays).

[OP-5453] Sometimes Patient badges did not detach when the patients were discharged. This has been corrected, and now patient badges automatically detach from the patient records when the patient is discharged.

[OP-5694] Customers who had the Capacity Management Suite® integrated with the TeleTracking IQ® platform could no longer edit consoles to remove the toolbar row, tabs, or unit/shift row for a whiteboard display. This has been fixed, and now after integrating the Capacity Management Suite® with the TeleTracking IQ® platform, users can change console settings to remove the toolbar row, menu tabs, or unit/shift row for a whiteboard display.

[OP-5593] If users tried to sign into deactivated accounts on a standalone Capacity Management Suite® environment, they saw a message to request a temporary password by selecting Forgot your Password? This has been fixed, and now users who attempt to sign into deactivated accounts see the appropriate message stating, This user account is currently deactivated.

[OP-5136] Patient Search results in PatientTracking Portal® application did not display icons for active transport jobs in the Transport Status column. This has been fixed, and now the icons for active patient transport jobs appear in the Patient Search results as expected.

[OP-5424] Sometimes an error message appeared when entering Patient Audit report selection criteria, if the date was in a format different from mm/dd/yyyy and the users sorted the list of returned patients by Admit Date Time or Discharge Date. This has been fixed, and now when creating a Patient Audit report while using a date format different from mm/dd/yyyy, users can sort the list of patients in the Search Patients dialog box by Admit Date Time or Discharge Date without an error appearing.

[OP-5444] Some customers noticed that the Capacity Management Suite® solution was not processing updates from the Admissions Discharges Transfers (ADT) system for Payor information. Now, the Capacity Management Suite® solution Admissions Discharges Transfers (ADT) system successfully processes Payor information. This improvement to a previous fix was made in version 2021.07 but mistakenly not reported.

[OP-5549] Customers had performance issues caused by too many outbound Bed Requests and A20 records in the archive. This has been fixed with code that automatically removes older records from the archive. The new archive process will take longer the first time that it runs, however, subsequent archives will take the normal amount of time.

[OP-5560] Sometimes the Wireless Communications Transfer Protocol (WCTP) service crashed because it overwhelmed the system with duplicate notifications. This has been fixed with code that prevents and removes the duplicate notifications, and now the WCTP service does not crash.

[OP-5583] Users with Fixed memberships could see all unit/wards in the electronic bedboard’s View Options > Displayed Units/Wards field. This allowed users to see patient information that was outside of their membership. This has been fixed, and now users with Fixed memberships only see the units/wards on the electronic bedboard® view for which they have membership.

[OP-5629, MOB-2430] Newly created users in the TeleTracking EVS™ mobile app users could not sign in if they selected No sections and zones. This has been fixed, and now employees can successfully sign into the TeleTracking EVS™ mobile app when selecting the No section and zones option.

[OP-5527] TransportTracking™ application users, who had the User can access "Notify History" view permission and who had a membership other than All, did not see notifications sent to their membership. This has been fixed, and now users with the User can access "Notify History" view permission can see the notifications that are sent to their membership as expected.

[OP-5080] A patient’s isolation type was changed when the following occurred:

[OP-5493] The TransportTracking™ application did not cancel automatically-created transport jobs when users removed the patient’s Assigned Bed OR cancelled the patients Ready To Move (RTM) . This has been fixed, and now, as expected, the application cancels automatically-created transport jobs if the patient’s Assigned Bed OR Ready To Move is removed.
Note: the jobs will be cancelled only if the transport is in a status of Pending, Dispatched or Delay Dispatched. If the Transporter has transitioned the job to InProgress (or later) the job will remain as an active job.

[OP-5415] When a patient’s automatic transport job was rescheduled as an appointment, and a user opened, saved, and closed the patient’s Patient Placement Details, then a duplicate automatic transport job was created. This has been fixed, and now duplicate transport jobs are not created if users save and close the Patient Placement Details when the patient has a pending transport job that was previously rescheduled as an appointment.

[OP-5528] The BedTracking Employee List sometimes took a long time to load. This has been fixed, because the query has been rewritten to be more efficient. Now the BedTracking Employee List loads in an acceptable time.

[OP-4220] When viewed in the Google Chrome™ browser, the PatientTracking Portal® application list view columns were misaligned if the columns were frozen and the Large font size option was selected in the Console Settings. This has been fixed, and now frozen columns are not misaligned in a Chrome browser when Large font size is configured.

[OP-5547, 5455, 5499] Some customers noticed slowed performance. This has been fixed in the code, and now performance is improved.

[OP-5200] The Discharge Timer was still running when patients changed from Pending or Confirmed Discharge to In House status because the Physician Order discharge milestone was not automatically removed. This has been fixed, and now the Discharge Timer stops when patients go from Pending or Confirmed Discharge to any other status, as expected.

[OP-4989] When two enterprise Capacity Management Suite® systems sent the same VMI Client ID to the Vocera server, notifications were not delivered. This has been fixed with a new configuration option. Contact your TeleTracking representative to implement this update for your enterprise.

[OP-5618] The Capacity Management Suite® HL7 system sent a second Bed Request message with the ORU message when the patient was marked Ready to Move (RTM). This has been fixed, and now the Capacity Management Suite® sends only one outbound HL7 message when the bed request is made and does not send a second one when the patient is marked Ready to Move (RTM).

[OP-5486, OP-5498, OP-5499] Some customers experienced slow performance. This has been fixed with improvements to the PatientTracking Portal® application, electronic bedboard® view, and archiving process.

[MOB-2339] In the TeleTracking Transporter™ mobile app, the Filter Patients By page had a section incorrectly labeled Bed Status. This has been fixed, and now the Filter Patients By page displays a section titled Patient Status as expected.

[OP-5253] The archive process took longer than normal because in some situations deadlocks occurred. This has been fixed, and various improvements were made to the archive process. Archiving now takes the normal amount of time.

[OP-4937] Bed columns that were frozen did not retain their sizes after the screen refreshed. This issue has been fixed, and now a screen refresh does not change frozen bed column sizes

[OP-5271] Only When Multi-Instance Capacity Management™ Suite Is Enabled - Users saw a gray screen and could not perform any action on one instance of Capacity Management Suite® when they signed out of another instance of Capacity Management Suite®. This has been fixed, and now signing out of one Capacity Management Suite® instance does not cause another instance to lock.

[OP-4978] An error appeared when administrators sorted the records by the DOB column on the Advanced tab of the Admin Tool > RTLS > Patient Badging page. This problem has been fixed, and now sorting by the DOB column on the Patient Badging page does not result in an error.

[OP-5386] As of versions 2020.05 and later, the patient attributes remained in the database after the patients were discharged or the patient visits were cancelled. This made the Patient table extremely large and slowed performance. This problem has been fixed, and now the patient attributes clear from the Patient table in the database when patient’s are discharged or visits are cancelled.

[OP-5105] Sometimes the Load/Save Console dialog box did not display the selection options. This has been fixed, and now the Load/Save Console dialog box displays the selection options as expected.

[OP-4557] In Microsoft® Internet Explorer® browser, when a user selected Alerts on the Home page and then selected Reply All for an instant message from a notification group, an error appeared in the Screen Alerts dialog box. This has been fixed, and now no error appears.

[OP-4770] Users could run the Location Dwell Time Report when grouped by Location for a Date Time Range of up to a year. This resulted in decreased performance. This has been fixed in the code, and now the application prevents users from entering a Date Time Range of more than 30 days when the Location Dwell Time Report is grouped by Location.

[OP-4877] When the Location Dwell Time Report was grouped by Location and displayed details, the time stamp used for the Departure column and the Duration calculation was incorrect. This has been fixed, and now the correct timestamp, which is the transport job’s InProgress time, is used in the report.

[OP-4828] Administrators could not select the correct campus when creating a dispatch set. As a result, users could not be configured. This has been corrected, and now administrators can select campus to successfully create dispatch sets.

[OP-4840] The Floor Plan view displayed the unit/ward that was previously selected in the console even after the user’s session ended. This has been corrected, and now when users sign in, the unit/ward that appears on the Floor Plan view depends on one of the following conditions:

[OP-4854] Customers had rendering issues and errors that appeared when viewing the PreAdmitTracking® application in Split View in Microsoft® Internet Explorer® and Mozilla® Firefox® browsers. These issues have been fixed, and now customers can successfully view the PreAdmitTracking® application in Split View in Microsoft® Internet Explorer® and Mozilla® Firefox® browsers.

[OP-4083] When administrators created users with Fixed memberships, the Campus checkboxes did not appear and could not be selected. Administrators had to save the user with an All membership, change the membership to Fixed, and then save the user again. This has been fixed, and now when administrators create users with Fixed memberships, the campus selection boxes appear as expected.

[MOB-2133] Previously customers could see Protected Health Information (PHI) on their phone’s app switcher screen. This problem has been fixed, and now customers do not see PHI when viewing their phone’s app switcher. However, customers may find that this security enhancement prevents screen shots and accessing by phone remotely (for troubleshooting).

[MOB-2192] The My Jobs screen of the TeleTracking EVS™ mobile application displayed bed cleaning jobs with the most recent job at the top of the list. This has been fixed and now the oldest bed cleaning job appears at the top of the list so that the employees will clean it first.

[OP-3991] Some customers reported that their EVS employees waited for 10-20 minutes to receive dirty bed notifications after they signed into their mobile application. This has been fixed, and now EVS employees receive notifications of dirty beds immediately after signing in for the day as expected.

[OP-4669] Some customers had trouble integrating Mobile Heartbeat™ notifications service with the Capacity Management Suite® after upgrading to the Capacity Management Suite® 2019.12 or later. This has been fixed and now when the Capacity Management Suite® is integrated with Mobile Heartbeat™, notifications are received as expected.

[OP-4724] If no isolation end time was assigned to a patient at discharge, then the patient continued to appear on the Patient Isolation History Report. This issue has been fixed, and now the patient’s Isolation End Time is automatically added when the patient is discharged, and the patient does not continue to appear on the Patient Isolation History Report.

[OP-4784] The Location Dwell Time Report grouped by Patient did not display a count of exceptions when users selected the Include Exceptions parameter. This has been fixed, and now patients who have an arrival or departure that is outside of the selected date time range, appear in the report’s Exception column.

[OP-4727, OP-4798] On the list view, white text in several columns (Occupied Timer, Discharge Timer, or Patient Status) was difficult to see because it did not have enough contrast against the background color. This has been fixed, and now the color of the text in the list view columns contrasts with the background color making it more readable.

[OP-4740] When users changed their PatientTracking Portal® application console while the bedboard was minimized, then they could not make any changes to the bedboard and no message appeared stating the console had changed. This has been fixed, and now the message that the console has changed appears as expected and prompts users to refresh the bedboard.

[OP-3300] The Observation Timer on the Console counted down even though the Master Configuration setting was set to count upward. This has been fixed, and now the Observation Timer on the Console counts in the direction of the Master Configuration setting.

[OP-4474] When the PatientTracking Portal® application list view was sorted by the Bed column, the Admit, Holding bed information was displayed on two rows instead of one. This has been fixed, and now when sorted by Bed, the list view displays one row for each Admit, Holding bed.

[OP-3356] Users could not change the employee’s assignment in the Change Assignment dialog box of the Supervisor Login/Logout screen if the device section said Variable. This problem has been fixed, and now users can change the assignment of a variable employee in the Supervisor Login/Logout > Change Assignment dialog box.

[OP-4741] Customers noticed an unwanted duplicate tab appeared on the PreAdmitTracking® application console. This problem has been fixed, and now unwanted duplicate tabs do not appear on the PreAdmitTracking® application console.

[OP-4552] When the search pane was expanded in the floor plan, sometimes it was blank. This happened in both the regular and full-screen views. This problem has been fixed, and now when it is expanded, the search pane always displays the floor plan’s assets.

[OP-3927] The number of cancel reasons codes in the Cancel Reason section of the Compound Metrics report did not match the number of cancel reason codes listed in the Event Details column of the Bed History report. This issue has been fixed, and now the number of cancel reasons codes in the Compound Metrics report matches the number of cancel reason codes in the Bed History report.

[OP-3377] Users could not remove users with long names from the Selected Users and Groups list of the Instant Notify dialog box because the delete button was not visible. This has been fixed, and now the delete button is always visible in the Instant Notify dialog box.

[OP-4448] When users selected any Print button option on the list views, they saw a message, “An error has occurred. Please contact your system administrator.” This has been fixed, and now selecting any Print button option prints the list view as expected.

[OP-4686] Customers who use SQL databases with Always On availability groups noticed that some PreAdmitTracking® list view columns did not automatically update. A fix was developed for this problem by configuring a secondary replica with read-only access to the Always On availability groups. Contact your TeleTracking representative to implement this fix for your health system.

[OP-4582] Sometimes multiple transporters using the TeleTracking mobileXT™ application to access a job received an error stating, “Your changes cannot be saved, another user has changed this data.” This has been fixed, and now when the first user puts a job into Pending status, the second user no longer receives the job unless the first user decides to reject it.

[OP-3903] If there are no other jobs available, when a transporter is removed from an assist job (either by self or by others), then the job is rejected. This has been fixed, and now when a transporter is removed from an assist job and there are no other jobs available, the original job is not rejected.

[OP-4352] When Google Chrome™ browser users select an alert in the Screen Alerts window to navigate to the associated Patient/Placement Details view, the Screen Alerts window expands to display white space on the right. This has been fixed, and now navigating to the Patient/Placement Details view from Screen Alerts does not expand the Screen Alerts window with extra white space.

[OP-4420] Transporters did not get credit for automatic transport jobs when the ADT system completed the jobs before the transporters did. The information in various reports did not match. This problem has been fixed, and now automatic transport jobs cannot be canceled by the ADT system.

[OP-3807] When viewed in Microsoft® Internet Explorer® browser, the fields on the login screen for the standalone version did not display any hint text. This has been fixed for Internet Explorer®, Google Chrome™, and Mozilla® Firefox®, and now the User Login ID field displays the text “User Name” and the Password field display the text “Enter Password.” IQ Enabled Capacity Management Suite® continues to display the hint text “someone@example.com” and “password.”

[OP-4492] After administrators reset users' passwords, the users received a message that they could not sign in because the password was expired, even though it had just been reset. This has been fixed, and now users can successfully sign in after administrators reset their passwords.

[OP-4523] When users hold their mouses over locations that have assets but are not home locations, then the locations' pop-up information boxes do not appear. This has been fixed, and now the informational pop-up boxes appear when users hold their mouses over non-home locations that have assets.

[OP-4559] When some users added staff members to a unit on the Staff Assignment window and clicked Save, then all staff members were cleared from the window. No error message appeared. This has been fixed, and now users can successfully add staff members to a unit on the Staff Assignment window.

[OP-4430] Users could not run the same report more than once with different criteria selected because the Run Report button was disabled after running the first report. Users had to close the report dialog box and open it again to run additional reports inputting different values. This has been fixed, and now the Run Report button remains active after a report is generated. Users do not have to close the dialog box and re-open to be able to run the same report multiple times with different values selected.

[OP-4387] When users entered the patient’s date of birth in the Patient/Placement Details dialog box, the patient’s age failed to automatically calculate and appear in the Age field. This problem has been fixed, and now the patient’s age is automatically calculated and appears in the Age field if the patient’s date of birth is entered.

[OP-4495] Patients on the floor plan who were attached to missing badges did not appear grayed as they should have. This issue has been fixed, and now patients with missing badges appear grayed on the Floor Plan view.

[OP-4496] Assets on the floor plan did not display a color-coded border indicating their status. This problem has been fixed, and now a color border appears around assets to indicate their status.

[OP-4512] If users selected a floor plan that was not available, the previously viewed floor plan appeared. This has been fixed, and now if a selected floor plan is not available, the users see the default floor plan as expected.

[OP-4462] When some customers tried to assign a bed to a patient, the Assigned Bed list did not display any options. Then, when users tried to save the Patient/Placement Details, an error message appeared stating the placement could not be saved because it had an active assignment. This has been fixed, and now the Assigned Bed field displays the list of options and the Patient/Placement Details can be saved as expected.

[OP-4473] When users selected Reply All to a notification that was sent to their notification group, the sender of the original notification did not receive a reply. This has been fixed, and now the user who sent the original notification receives a reply along with the other users in the notification group.

[OP-3902, MOB-2015, MOB-1825] If a job was presented to a transporter before they went on break, sometimes when they returned from break, the job was logged as a rejection. This has been fixed, and now transporters who return from a break never log a rejection for jobs that are presented to them before they go on break.

[OP-4524] TeleTracking Transporter™ and TeleTracking EVS™ mobile apps on Android™ phones did not successfully send and receive notifications. This issue was fixed by increasing the maximum characters allowed in the push notification token. TeleTracking Transporter™ and TeleTracking EVS™ mobile apps on Android™ phones now successfully send and receive notifications.

[OP-4528] Patient attributes were occasionally cleared by the archiving process. This problem has been fixed, and now when patient records are archived, the patient’s attributes remain.

[OP-3904] A transport job rejection occurred any time a transporter took more than two minutes to implement an action. Consequently, transport job rejections were created inconsistently. This problem has been addressed in the code, and now transport job rejections occur when no action has happened before the Interval to keep a dispatchable job locked during assignment value in the master configuration has passed. For additional accuracy, the Master Configuration for job locking period for the transporter to initiate an action was changed from minutes to seconds.

[OP-4257] When users selected a Delay Reason in a Care Progression group for a patient who was Assigned and then later Admitted, a “Please Contact the System Administrator” error appeared. The workaround is to remove the delay reason, admit the patient, then add the Delay Reason again.

[OP-4241] When the Transporter Delay Analysis report output is unformatted Microsoft® Excel®, the values in the Delay End Time column and the Delay Start Time column were the same. This has been fixed, and now the columns display the correct values.

[OP-4258] When users ran the Processing Time Analysis Report in PDF format, some fields were blank. However, when running the same report in Microsoft® Excel® format, the fields that were blank in the PDF displayed values of "0.00." This was a problem when users tried to use the data for calculating averages. This problem has been fixed, and now the Processing Time Analysis Report displays a blank (Null) in both the Excel and PDF output. In addition, values in this field are now displayed in h:mm format.

[OP-4447] Users experienced unresponsive pages when they viewed the Capacity Management Suite® in the Google Chrome™ browser. This problem has been fixed, and users' workflow is no longer interrupted by unresponsive pages when viewing the Capacity Management Suite® in Chrome™.

[OP-4388] Variable membership users saw an "Contact your system administrator" error message when they logged in and attempted to select their units/clusters. This problem has been corrected, and now users with variable memberships do not see an error. They can successfully log in and select their units/clusters.

[OP-4170] The TransportTracking™ application took a long time to complete a Staff Search for a common name, such as “Smith.” This problem has been corrected by creating an index for the database.

[OP-4209] A stored procedure (ttEnterpriseTimerAlertEventUserGet) was timing out after one minute and constantly running every two minutes. This procedure could affect the patient, enterprise user, and milestone details. This issue has been fixed and the stored procedure no longer runs every two minutes and times out after one minute.

[OP-4237] Some TeleTracking IQ-enabled customers, who used the Google Chrome™ browser, could not remain logged in. They were automatically logged out when they clicked any tab in the TeleTracking IQ-enabled Bed Management Suite® and Capacity Management Suite® solution solutions version 2019.12 and later. This issue resulted from security changes implemented by Google™ in Chrome™, version 80 regarding the handling of SameSite cookies. This issue is fixed in version 2020.04, and users are no longer automatically logged out when they select any tab.

[OP-4259] Some customers experienced sporadic slowness across the entire Capacity Management Suite® solution solution lasting up to 30 minutes. The problem has been fixed, and users no longer experience slowness across the entire Capacity Management Suite® solution solution.

[OP-4284, OP-4280, OP-4271] On a maximized electronic bedboard® view displaying a horizontal scroll bar, a screen refresh hid the scroll bar behind the task bar. Users could display the scroll bar by minimizing and then maximizing or by scrolling down. However, the next screen refresh hid the scroll bar again. In addition, when users scrolled right and down, the application automatically re-positioned back to the top left when the screen refreshed. These problems, which were caused by unused memory not being released, have been fixed, and no longer occur.

[OP-4056] The electronic bedboard® view crashed because memory is not being released when the application was refreshed. This has been fixed, and now the electronic bedboard no longer crashes.

[OP-4249] The Location Master List Report displayed the full location name in the Location Abbreviation column rather than the abbreviation. This has been fixed, and now the location abbreviation appears in the Location Abbreviation column as expected.

Electronic Bedboard

All Applications

PatientTracking Portal® Application

TransportTracking™ Application

Mobile

[OP-3979] The Capacity Management Suite® now prevents administrators from creating new milestones names and new milestone delay names with commas in the Milestone Setup pages. If your existing milestone items contain commas, contact TeleTracking to have the commas removed.

[OP-3861] When Google Chrome™ users applied Freeze Columns to a tab in Console Settings, the columns in the list view became misaligned. This has been fixed, and now, PatientTracking Portal® list view columns do not become misaligned when the Freeze Columns setting is applied.

[OP-3868] PreAdmitTracking® patients were not matching and merging with patients who had bed requests made in the TransferCenterIQ™ application. This created new visit records. This problem has been fixed, and now, patients with bed requests in the TransferCenterIQ™ application are correctly matched and merged with patients the PreAdmitTracking® application.

[OP-3914] Customers who had workstations with a horizontal resolution of less than 1200 pixels found that the Search, Clear, Print, Adv. Filters, and View Options buttons on the list view were misaligned. This problem has been corrected, and now the list view appears as expected with horizontal screen resolutions under 1200 pixels.

[OP-3761] - In the list views, sub-menus that were expanded remained visible even after users had selected elsewhere in the view. This has been corrected, and now, the expanded sub-menus close when users select somewhere else on the page.

[OP-3364] - The Blocked Beds report was taking about 55 minutes to run when it processed six months of data. This has been fixed and now the report takes less time to run.

[OP-3730] Previously, the Security Modifications Audit report required that one campus be selected. As a result, when a user changed campuses, the report did not display the user in the new campus. This has been fixed, and now, when the Campus criteria field is left displaying Select, all campuses that the selected user had access to appear in the report. This allows the report to track the user’s modifications as the user moves from campus to campus.

[OP-3733] An expired timer alert sometimes caused the database archive to fail. A fix to a foreign key constraint for the ExpiredTimerAlert table has corrected this problem.

[OP-3824, 3825, & 3848] During peak usage hours, customers noticed slow response times. The database has been optimized to improve performance.

[OP-3697] In each campus' Global Settings for the Patient Notification/Alert Message Content and Discharge Timer Alert Message Content, it is no longer required that one of the following be enabled: the patient’s Full Name, MRN (Medical Record Number), or Visit Number. Now, administrators can enable any or none of these fields. This complies with the Protected Health Information (PHI) policies for some health systems.

[OP-3659] When users held their mouse over badge names in the RTLS Badge column on the Patient Tracking Portal list view, the tooltip displayed Unknown for the badge location information. This has been fixed, and now the badge location information updates after the badge has moved.

[OP-3855] When users selected Manage Temp Staff in the Staff Assignment dialog box and entered the staff member’s information, selecting Done did not add the staff member. This has been fixed and now when users can successfully add temp staff members.

[OP-3752] The Transport Tracking Requests by hour report displayed inaccurate times because it was calculating the average time from when the job was put into Pending status until it is set to Complete. This problem has been fixed, and now the average time is calculated from the start of Pending status to the start of In Progress status.

[OP-3685] TransportTracking™ application users who belonged to a user group that had the User can filter data in view setting disabled received an error when they performed a TransportTracking™ application patient search. This has been fixed and now the error does not appear.

[OP-3776] Transport jobs with a Possible status did not get archived even after the number of days in the Cut Off Days setting were met. This has been fixed, and now when the Cut Off Days are met, the transport job with a Possible status is archived, and removed from the Production database.

[OP-3441, OP-3410] An error appeared when users selected a patient from the electronic bedboard® view search results while in a split screen view. This has been corrected and now when a patient is selected from the electronic bedboard® view search results while in a split screen view, the Patient/Placement Details dialogue box appears as expected.

[OP-3530] In the Milestones Notification page, the text of the notification did not appear in the Notification History section if the Include Patient Information check box was cleared before sending the message.

[OP-3671] Customers were randomly getting the error message, “NavigationMenu_OnClientItemClickingHandler.” Users were able to close the message and continue working. This has been fixed, and now this error message does not appear.

[OP-3700] The PatientTracking Portal® application and PreAdmitTracking® application performed slowly because archived milestone detail entries that were past the number of days in the Cut Off Days setting were not deleted. This has been fixed in the code.

[OP-3526] When patients were transferred multiple times and then discharged, the Milestones Delay report displayed the patient's previous location rather than the most recent home location. This has been fixed, and now the report displays the patient's most recent home location.

[OP-2939] Some customers found that the Capacity Management Suite® locked up for an extended time. This issue has been fixed with a change to the web.config file timeout setting.

[OP-2657] The PatientTracking Portal® application list view rows became misaligned after users applied a font size in the Console Settings > Settings tab > Bed/Patient Row Text Size field and froze columns. This has been fixed, and now changing the font size and then freezing columns does not cause misalignment of the list view columns.

[OP-2800] Previously, the View Options drop-down menu extended beyond the edge of the PatientTracking Portal® application window, which truncated the option labels. This issue has been fixed, and now the menu’s position allows the option labels to appear in full.

[OP-2832] The PatientTracking Portal® application list view rows became misaligned after users selected a number of columns to freeze in the Console Settings > Settings tab > Freeze Columns field.

[OP-2936] The PatientTracking Portal® application list view rows and columns became misaligned after users changed the font size to Medium or Large, or created a console with 10 or more icons next to each other.

[OP-3471] Translations from the date / time format, configured in Enterprise-wide settings, was causing erroneous staff assignments. When set to dd/MM/yyyy hh:mm:ss, the day (dd) was being interpreted as the month (MM) This resulted on occasion in assigning a staff member to a bed for up to a year instead of the day intended. The year-long assignment had to be completed (or a data correction entry entered in the database) before the staff member could be assigned to the bed again. This problem has been corrected.

[OP-3729] Some customers noticed that the Patient Audit Details report returned the wrong patient’s data. This has been fixed and now data for the specified patient is returned when the report runs.

[OP-3346] In version 2018.4 and later, the Patient Search in the TransportTracking™ application timed out when there were a large number of returns, such as when searching for a common last name (Smith). This has been corrected and now large numbers of returns do not cause the Patient Search to time out.

[OP-3174] Some customers noticed that the XTTranstport tracking timer service periodically stopped and restarted. This issue has been fixed.

[OP-3639] In versions 2018.2 and later, when users scrolled the list of Patient Custom Attributes in the Patient/Placement Details dialog box, the checkboxes and the attribute names became misaligned. This issue has been fixed, and now the checkboxes remain next to their associated attribute name when users scroll the list.

[OP-3414] Customers could not enter dictionary item names of more than 29 characters. This has been fixed, and now the names of dictionary items can be up to 100 characters.

[OP-3586] In version 2018.4 and later, users who were configured with Microsoft Active Directory noticed that their sessions did not automatically close after the Time Out period if they also had the electronic bed board open. This issue has been fixed and the Time Out occurs when Microsoft Active Directory users also have the electronic bed board open.

[OP-3431] When a Clinical Workflow™ suite user assigned a procedure to a patient, the patient's current location was removed, which prevented an auto transport job. This has been fixed, and now assigning a procedure to a patient retains the patient's current location, and an auto transport job moves the patient as expected.

[OP-3483] An error appeared when a staffed bed was assigned to a patient, because all subscribed staff assignment systems were invoked even if it was not appropriate to do so. A code modification has fixed this problem, and the error no longer appears.

[OP-2943] Clients, who had single sign-on enabled, found that single sign-on was no longer enabled after upgrading from version 3.3 or 3.4 to versions 2017.3 or 2018.2. This has been fixed. Now the single sign-on feature remains enabled after upgrading.

[OP-3433] Users who had variable memberships and had Require RAC code enabled had to enter their RAC code each time they toggled the dark theme mode on and off, rather than only when they changed units. This has been fixed and now users do not need to enter a RAC code when toggling the dark theme mode on and off.

[OP-3409] Outbound HL7 messages (such as Bed Status) that the Capacity Management Suite® sent to the health system's ADT application did not process. This has been fixed, and now outbound messages to ADT process as expected.

[OP-3439] Sometimes the cursor would disappear when customers clicked in the Search Users and Groups field of the Instant Notify dialog box. This issue has been fixed, and now the cursor remains visible so that users can perform a search.

[OP-3026] Some reason codes appeared that were for TeleTracking internal use only. This has been fixed, and internal reason codes no longer appear.

[OP-3360] IQ enabled customers using Internet Explorer could not copy the text in the Screen Alerts dialog box. This has been corrected.

[OP-2632] Customers could not run the Patient Audit Report with the patient details enabled. This has been fixed, and now the Patient Audit Report successfully runs with the patient details.

[OP-3206] Customers experienced times when the Admission Discharge Transfer (ADT) system could not update patient records because the archiving process was locking the records. An update to the archiving process has fixed this problem.

[OP-3234] A GetStatisticsData error was noticed in the logs that affected the Real Time Key Indicators (RTKI). This has been fixed in the code.

[OP-2818] If customers set the Toolbar View, Tabbed View, Logout Row, and Unit/Shift Row to Disabled in Console Settings, they could no longer access Console Settings in order to make changes. Now users always have a way to open Console Settings while still allowing more room for additional patient rows to be displayed.

[OP-3283] When customers enabled the Require authentication to edit information or the Freeze columns options for the Console settings in standalone mode, the column headers did not align with the list view columns when viewed in Google Chrome™ or Firefox® browsers.

[OP-2746] A high number of busy signals prevented access to the IVR system. This has been corrected by implementing new Host Media Processing (HMP) elements for Dialogic® PowerMedia™. A TeleTracking representative can assist your organization in implementing this fix.

[OP-3109] Notifications that were received on the mobile device did not appear on the Messages tab in the mobile app or in the Notification History in the TransportTracking™ application.

[OP-3189] In the TeleTracking mobileXT™ app, job notifications were appearing as JOB FOR YOU, CALL <number> (as they would appear for Interactive Voice Response [IVR] users who need to call for more information). The notifications in the TeleTracking mobileXT app now correctly show JOB FOR YOU.

[OP-2797] When there was a horizontal scroll bar on the PreAdmitTracking list view, the list view shifted.

[OP-3183] Although the PatientTracking Portal staff assignment feature was in use, and nurses were associated with the patients' current home location and assigned new home location, the Origin Nurse and Assigned Nurse boxes on the Patient/Placement Details form did not show the patients' nurses.

[OP-3197] If the "Use Master Patient Index" Master Configuration setting was disabled, the Patient/Placement Details form did not expand properly.

[OP-3090] In list views, the gender color indicator (pink or blue) did not appear in the Age column if the Age column was included in a group of frozen columns and the Bed/Patient Row Text Size setting in Consoles Settings was set to Smaller.

[OP-3154] When the "Require Reason Code When Job Destination is Home Location Type" Master Configuration setting was enabled, and users tried to create transport jobs requests where the destinations were occupied locations, the application stopped functioning. Users had to refresh the page to continue.

[OP-2911] Some ADT A04, A05, and A08 transactions were not being processed.

[OP-2882] After the Dark Mode and Light Mode feature was introduced in version 2018.2.5.3, the way timestamps were displayed in the RTM@ column changed inadvertently. In version 2018.4, this has been corrected. If the RTM@ column displays a future time, the timestamp appears in normal font. If the column displays the current time or a past time, the timestamp appears in bold font.

[OP-2976] In PatientTracking Portal staff assignments, if a staff member's user-defined shift started before midnight and ended after midnight, and then a user associated that staff member with a bed, the association of the staff member with the bed was not saved. Staff members with user-defined shifts that start before but end after midnight can be associated with beds successfully now.

[OP-3072] On the Listview Column Selection dialog box (accessed via View Options), when a user changed the size of one column and then saved, all other columns on the list view became larger. Each time the size of one column was changed, the sizes of other columns increased.

[OP-2989] If one user was using multiple monitors, it was not possible to move the Patient Placement Details form from one monitor to the other.

[OP-2849] The Automated Patient Discharge report could not be generated successfully if the Archive database was selected.

[OP-2794] In TeleTracking IQ-enabled Capacity Management suite, users with variable membership (or "floaters") saw consoles other than the ones that were associated with the units or wards they selected when signing in. Floaters now see the consoles that are associated with the units or wards they select when they sign in.

[OP-2240] In Dictionary Management, the search results for physicians or consultants did not display more than 25,000 records. For example, if you searched for a physician or consultant who was record number 25,100 in the database, that physician or consultant did not appear in search results, even though the record was in the database.

[OP-2553] When users attempted to generate a Patient Audit standard report with data from the archive database for a date range of longer than one week, an error message appeared and the report could not be generated.

[OP-2616] The following error message appeared when administrators attempted to add reason codes. The reason codes could not be added: “An error has occurred. Please contact your system administrator.” A configuration file has been modified so that between 1700 and 2000 total reason codes for BedTracking and TransportTracking combined can be accommodated now.

[OP-2698] Although the Capacity Management suite was not integrated with the TeleTracking IQ platform, TeleTracking IQ users were created through the Gateway service.

[OP-2455] Discipline names were truncated on the Projected Census when the census was grouped by Campus.

[OP-2606] In View Options > Configure Columns, if more than 20 columns have been added to Selected Columns and you scroll all the way to the right, and then you remove a column from the second row, you cannot add another column to that location to replace it..

[OP-1523] If you freeze some columns in a list view, the columns that are not frozen sometimes appear misaligned under the frozen column.

[OP-1934] If the Capacity Management Suite was integrated with the Rauland staffing system, no more than 500 entities at a time from Rauland integration points were available. To resolve this issue, entities are now processed in multiple batches of 500 entities each.

[OP-2567 and OP-2211] When you start to create a patient transport or item transport request (for example, you select the Patient Trans or Item Trans icon), the Transport Request dialog box appears. When you select the magnifying glass icon near the Origin or Destination box, the Find a Location dialog box appears. The search works as expected the first time that you enter text into the Search Text box on the Find a Location dialog box, and then select units or wards, and then search for and select a location, and close the dialog box. However, in Microsoft® Internet Explorer® versions 11.0.27 through 11.0.33 and 11.0.65 through 11.0.75, if you want to make a change and you select the magnifying glass icon again to open the Find a Location dialog box, you cannot enter text in the Search Text box. This issue occurs in versions 2017.3 and 2018.1 also. If you are using one of the affected Internet Explorer browsers, make sure the Find a Location dialog box and the Transport Request dialog box are closed, and then manually refresh the browser. Then, return to the transport request and search for the location. As an alternative, use a supported version of the Mozilla® Firefox® browser noted in the Technical Information Reference Guide for your version of the Capacity Management suite. Although this issue has been fixed, when you access the Find a Location dialog box the second time, you must double-click in the Search Text box before you can type text in it.

[OP-1216] When the application server is set to a different time zone from the workstations, the times for staffed bed assignments are incorrect by a few hours.

[OP-2226] The background colors that administrators selected in Dictionary Management to represent each isolation type are not appearing in list views.

[OP-2357] In TeleTracking IQ-enabled Capacity Management suite, when the Toolbar view is disabled in Console Settings, you cannot load and save consoles.

[OP-2141] Unable to edit users' membership types using the bulk edit feature. If you select more than one user record on the User Management page, and then select Edit Selected Records and try to change the membership type, the page becomes unresponsive.

[OP-2179] Total Bed Hours Gained value is calculated incorrectly on the Discharge Efficiency report.

[OP-2224] When users are uploaded in bulk through data import, orphaned SectionAssignment entries are created. This results in the Assignment section in user profiles displaying sections that the users should not be associated with.

[OP-2225] "Dead letter" ADT transactions are not removed during archiving. A "dead letter" transaction is a message from the Admit Discharge Transfer (ADT) system that either was sent to a non-existent queue or exceeded the queue length limit. During archiving, these transactions should be deleted from the database instead of being archived.

[OP-2227] Users cannot select units or wards. For example, PatientTracking Portal application console users and users who are creating transport requests cannot select units or wards.

[OP-2354] The Patient Audit report shows no transactions during a date range when there were transactions.

[OP-2303] If the PreAdmitTracking application global setting called "Maintain bed assignment on Pending / Confirmed Discharge status" is enabled, then when a Confirmed Discharge order is sent via the Admit/Discharge/Transfer (ADT) system, the bed request is cancelled. This does not happen if the a patient's status is set to Confirmed Discharge through the user interface.

[OP-1753]/[OP-1821] The Capacity Management suite might attempt to sign you out automatically due to inactivity when you are using a modal dialog box on a wall display (for example, the Patient Placement Details window, the electronic bedboard® view, the Console Settings dialog box, or the Message Board), even when you have been active and you have not exceeded the Secondary Login Inactivity Timeout (Seconds) setting. You might see a message prompting you to Leave Page or Stay on Page. Select Stay on Page to continue working.

[OP-1830] If an Active Directory user selects End Session in the PatientTracking Portal application, and then signs in again, multiple sessions of Capacity Management suite are open. However, the multiple active sessions do not affect the users, performance, or security.

[OP-1898] When users updated staff assignments from wall displays, they were signed out automatically when they should not have been.

[OP-1901] In TeleTracking IQ-enabled Capacity Management suite, if one user signs in to a wall display, and then another user signs in to the TeleTracking IQ platform using Active Directory credentials, and then navigates to the Capacity Management suite, and then signs in to a secondary session on the wall display using an IVR ID and PIN, and then that user signs out of the Capacity Management suite on the computer, both the second user and the first user are signed out on the wall display. The Capacity Management suite needs to be restarted or the first user needs to sign in to the wall display again. However, the Application Access Audit report incorrectly shows that the first user is still signed in, but that the second user's computer and wall display sessions have ended.

[OP-2221] If you are using a touch screen, you cannot use Slide to Acknowledge to acknowledge a Staff Assistance, Patient Isolation, or Walkout alarm.

[OP-2222] When you hover over a discharge milestone in a list view, a tool tip with information appears near the milestone (as expected), but also in the footer.

[OP-2355] Rows on the Staff Assignment window appear misaligned when the horizontal scroll bar is present in the Microsoft® Internet Explorer® browser.

[OP-1969] On the Listview Column Selection dialog box (accessed via View Options), in the SELECTED COLUMNS section, the display of the selected columns would break across multiple rows. This display issue has been corrected. In the same Listview Column Selection dialog box, in the AVAILABLE COLUMNS section, when text entered in the Filter box (shown below) was cleared, all available columns would not display. With this release, when the Filter box is cleared, the available columns appropriately display.

[OP-2097] A BedTracking or TransportTracking user with variable membership can select a PatientTracking Portal or PreAdmitTracking unit or ward that floaters are allowed to select when they sign in. After the users sign in, they will see the icons and/or menus for the PatientTracking Portal and PreAdmitTracking applications. However, if they try to access the applications, they will see an error message: “An error has occurred. Please retry your action. If the error continues, contact your system administrator.”

[OP-2146] In the Listview Column Selection dialog box (accessed via View Options), in the SELECTED COLUMNS section, previously added columns shrank after lengthier new columns were added causing misalignment on the list view.

[OP-2338] Users cannot access View Options to update custom console views.

[OP-2348] When users try to load a console list view, the following message appears: "List View Cannot be NULL."

[OP-2356] If you select the Alerts button and the list of alerts is more than one page long, then when you attempt to access additional pages, the following error message appears: "Please contact your system administrator."

[OP-2239] After upgrading to version 2017.3 or later, when administrators accessed TransportTracking global settings for a campus, they could not see dispatch sets that had been created previously.

[OP-850] Patient purge cannot be completed in version 2017.3.

[OP-1808] An error message appears if you open the Patient Placement Details form from an alert within the BedTracking® application or TransportTracking™ application or the Standard Reports component, and then select Search Patient Demographics.

[OP-1831] If an administrator accesses the Location Information page from the Unit Information page and then changes and saves a bed's location type on the Location Information page (for example, changes Home to Specialty Bed), the change is saved but it does not appear on the Unit Information page.

[OP-1834] If an administrator uploads and saves a logo through Enterprise Management, the logo does not appear in the upper-left corner as it should.

[OP-2007] The upgrade installation process used a large amount of transaction log space, causing upgrade installations to fail.

[OP-1815] After you assign a target bed to a patient on the Patient Placement Details window and save, and then remove the target bed assignment and save again, if you select the X in the corner to close the window, the window might not close.

[OP-1818] After you select a row on a list view and then select a second row, a blue border appears around both rows and the rows appear to separate from each other.

[OP-1626] In Microsoft Internet Explorer 11.x, long text is truncated in the columns in the list views. There are no ellipses before the truncated text, so it is not apparent that the text is missing.

[OP-1706] In the Firefox browser, columns are misaligned on the wall display when the Require Authentication to Edit Information setting is enabled.

[OP-1827] If your browser font size is set to Larger and there are more than 10 columns in a list view, then only partial text might be displayed in the Origin Unit / Origin Ward and Current Location columns. There are no ellipses in the columns to indicate that some of the text is not visible, so it is not apparent that you cannot see the all of the text.

[OP-1941] When a user with variable membership signed in, selected a unit or ward that an administrator had associated with a PatientTracking Portal console, and then accessed the PatientTracking Portal application, the console that the administrator associated with the selected unit or ward automatically became the default PatientTracking Portal console in the variable user's user profile.

[OP-1996] When two patients in the same unit or ward have the same last name, the background behind the names is red in the Name column on a list view to alert staff members about the similar names and prevent confusion. Because of the font color, the last names were difficult to read on red backgrounds.

[XT-3748] The Hand Hygiene audit report now includes logic for when the Treat Semi Private Rooms with One Patient as a Single Room and the Use Separate Hand Hygiene Settings for Isolation Patients Master Configuration settings are enabled. A TeleTracking representative can generate the audit report for you.

[OP-1538] On an item transport job request, if you are required to associate a patient with the item, but you do not, then when you save the job request, an error message appears and the selected origin and destination locations are deleted from the request.

[OP-1942] When users attempted to run the Employee/Supervisor History report from the archive database, the following error message appeared: "An error has occurred. Please contact your administrator."

[OP-570] The archiving process does not archive attending physicians for all patients, resulting in the attending physicians being excluded from reports in the Custom Reporting Solution™ application.

[OP-637] In TeleTracking IQ-enabled Capacity Management suite, in some cases, the user name fields in user accounts for new transporters and bed cleaners (housekeepers) were blank. Therefore, their user names were not appearing on the user interface. If the user name field in a user account is blank, the user's name now appears on the user interface in the following format: <last name>, <first name>.

[OP-666] Users whose names included apostrophes (for example, O'Hara) could not log in.

[OP-676] Operational validations of Capacity Management Suite® and TeleTracking Real-Time Locating System™ solutions databases with Microsoft® SQL Server® 2012 "Always On" functionality as well as Microsoft® .NET FrameWork version 4.6.2 in application server environments were unsuccessful. TeleTracking does not recommend using SQL Server® 2012 in an "Always On" environment or .NET FrameWork version 4.6.2 at this time.

[OP-826] Latency in page loading in User Management and with reports.

[OP-850] Patient purge fails.

[OP-885] If the Capacity Management suite is TeleTracking IQ-enabled, then only the users who have the default Capacity Management suite administrator role can click the Platform Version and Terms of Use links at the bottom of the Capacity Management landing page. For other users, these links are not clickable.

[OP-968] A repair installation of the Capacity Management suite version 3.4 fails when the Capacity Management suite is integrated with Performance Reporting on the TeleTracking IQ® platform.

[OP-970] Unable to edit existing users with email addresses.

[OP-1016] As of version 2017.3, there is no dependence on Microsoft® Internet Explorer® version 7 compatibility components.

[OP-1020] In the Asset Patient Staff Interaction report, the Lost Badge report, the Patient Staff Interaction report, and the Patient Staff Location report, the time stamps are not in local time. Instead of conversion to local time, UTC time conversion is used. Therefore, time stamps on reports are incorrect by one hour, except during Daylight Savings Time.

[OP-1026] On the User Master List report, the incorrect positions are displayed for employees.

[OP-1049] In the TeleTracking mobileXT™ app, the title bar overlapped the Done button and there was a drain on the phone battery.

[OP-1078] In the Admin Tool or Admin > Settings > Capacity Management, there is an unspecified error in patient search.

[OP-1152] TAP paging fails after a period of time because of inability to access the Comm Port. This leads to issues such as inability to create a transfer request.

[OP-1183] When a 404 error message page appeared in a browser because an incorrect page name extension was in the browser address bar (for example, the page extension was entered as .aspc instead of .aspx), a directory structure appeared in the message. The directory structure no longer appears, which minimizes security risks.

[OP-1186] Multiple duplicate A08 transactions were logged, causing the transaction log to grow excessively.

[OP-1580] If you attempted to generate the Discharge Efficiency Report when the Capacity Management suite was not integrated with TeleTracking RTLS™ solutions , the following message appeared: "An error has occurred. Please contact your system administrator."

[OP-1843] Excessive deadlocks affect database-side performance.

[OP-969] Consoles are not updating automatically.

[OP-1076] Unspecified error in patient search.

[OP-1149] Patients who have been discharged still appear on the floor plan.

[OP-561] If a patient badge for real-time locating has an alphanumeric code, staff members do not receive alerts and notifications about the patient who is associated with the badge (for example, a notification when the patient is marked Ready-to-Move).

[OP-578] On a wall display, users cannot use the touch controls for scrolling up and down and left and right unless they are also logged in to secondary accounts.

[OP-787] In patient search results, if you sort a column that has no values in it, the following error message appears: Error retrieving data.

[OP-1101] In patient search results, the Staff Type column is always blank.

[OP-1150] If two patients are associated with a bed, you cannot show or hide the bed on a console.

[OP-1159] In the Bed column on list views, the background color for beds in Clean status should be light green. Beds in Suspended status should have dark green backgrounds. Beds in Clean and in Suspended status both had dark green backgrounds.

[OP-1798] Interactive wall display users who were configured to not timeout are timing out.

[OP-371] Rauland external location identification codes not displayed in the locations section of the Admin Tool or Admin > Settings > Capacity Management.

[OP-542] Staff Assignment truncates long location names.

[OP-620] If the TransferCenterIQ™ application used the Capacity Management suite as the source for its physician records, the physicians were not automatically synchronized with the TeleTracking IQ® platform.

[OP-634] There were duplicate patients in PatientTracking Portal and optimization issues, as well as increased Microsoft SQL Server CPU usage.

[OP-791] On the Patient/Placement Details form, if the Admit Diagnosis box contains the special characters < or >, then users who receive alerts about the patient cannot delete the alerts or mark them as "read."

[OP-759] Transport jobs that occurred after the selected end date in the date range filter still appeared on reports.

[OP-815/OP-1237] If a transporter was offered a transport job and then took an unscheduled break, the job was noted as rejected.

[OP-1038/OP-1126] For possible and appointment transport jobs, the patient's current location should become the job's origin location automatically when the job's status changes from Possible or Appointment to Pending, so that the transporter can report to the correct location to start the job.

[OP-1147] When two different sections in two different campuses had the same section identification number, transporters with variable membership saw errors when they signed in to the TeleTracking mobileXT app and selected those sections.

[OP-1153] The Employee Audit report displays data from outside the selected date range.

[OP-1370] On the Transporters tab, if you select a job number for a job that is in Dispatched, Assist, or Dispatched/Delayed status, the transport request opens. When you close the transport request, the page shifts to the left and the status icons disappear. When the page is refreshed, the status icons reappear.

[OP-682] and [OP-754] In the Discharge Efficiency report and the Automated Patient Discharge report, the time stamps are not in local time. Instead of conversion to local time, UTC time conversion is used. Therefore, time stamps on reports are incorrect by one hour, except during Daylight Savings Time.

[OP-683] In the Discharge Efficiency report, if the same patient visit number has multiple ADT discharge messages, total counts and calculations include all of those discharge messages. Only the discharge message that was received first for a given visit number should be included in calculations. The counts should not show that the patient was discharged multiple times.

[OP-779] An exception error occurs in the Master Patient Index (MPI) search (Search Patient Demographics) when the user specifies a Middle Initial and at least one of the following in search criteria: a Suffix, an Age/Date of Birth, or a Gender.

[OP-785] The upgrade to the Capacity Management Suite® versions 5.0.1 through 2017.1 from version 3.4.0, with the version 3.4 patch applied, fails.

[OP-309] BedTracking supervisor does not appear on the BedTracking® application Employee Zone Coverage Quick Report.

[OP-719] Compliance Report does not include all data indicated in help. The reference to Source > BT has been removed from the Standard Reports online help.

[OP-475] Bed requests coming from the integrated TransferCenterIQ™ application are timing out. The timeout setting has been changed to address this.

[OP-512] Bed request orders from the Admit Discharge Transfer (ADT) system with a target unit in specified in ZB1.4 are not processed successfully.

[OP-540] Console-based notifications are not sent to subscribing users when 1) the HHI column is included in the console and 2) the Show Unit Hand Hygiene Index (HHI) on PatientTracking Portal setting is enabled for the selected unit or ward on the console.

[OP-662] Patient search does not allow sorting by column.

[OP-536] When a transporter accepts an assistance job, the following Apple® iOS error message appears: "Your changes cannot be saved. Another user has changed this data."

[OP-792] The following error message appears when users attempt to view patient details or transport job details: "An exception occurred while processing your request. Additionally another exception occurred while executing the custom error page for the first exception. The request has been terminated."

[OP-257] If SSL is enabled before an upgrade to version 3.2, it's disabled after the upgrade.

[OP-258] Incorrect indication of required field in Configure User Template.

[OP-296] Excessive IIS log growth.

[OP-417] Notifications not sent to Apple devices.

[XT-2390] Significant performance enhancements in various areas affecting database stored procedures, PatientTracking Portal® application, etc.

[XT-2540] Slow generation of Patient Audit report.

[XT-2560] Issue with updating user list when navigating pages.

[XT-2702] Archive failure.

[XT-2772] XT User Session Monitor service failure.

[XT-2306] Error message for users selecting a different menu option on subsequent logins.

[XT-2545] Timeout issue with Bed History report.

[XT-2666] Error with By the Hours Weekly and Employee Transaction Analysis reports from Archive database.

[OP-161] User interface issue in split view.

[XT-2387] Clean-to-Occupied Target setting ignored on Processing Time Analysis report.

[XT-2541] Slow generation of Milestone Delay report.

[XT-2542] Error generating Notification History report from Archive database.

[OP-89] Cosmetic UI issues.

[OP-253] Issue with Kronos OptiLink® integration.

[OP-306] Latency issue with milestones in list view.

[XT-2407] Unable to edit patient information in a custom column.

[XT-2408] HTML encoded value displayed in custom column.

[XT-2559] Unhandled exception error in Staff Assignment.

[XT-2270] Incorrect base unit logic.

[XT-2446] Transport supervisors receiving job rejection alerts from unauthorized campuses.

[XT-2763] Transport dispatch logic malfunction.

[XT-2865] Job rejection not recorded when transporter selects Break option on IVR.