See Simplifying Patching for Capacity Management Suite®

Clients experienced continuous errors after switching to daylight savings time. The issue caused frequent system errors due to incorrect time conversions, leading to session management failures.

The time conversion logic was updated to properly handle daylight savings time changes. This fix prevents the system from generating errors due to invalid date values, ensuring stable session management.

Errors were occurring in ADT Messages, Mobile Transport Jobs, and Placements due to a missing Reason Code in the database. This caused foreign key constraint failures, preventing these functions from completing successfully.

A data correction adds the missing Reason Code for affected campuses.

The database was processing transactions very slowly. The issue was traced to an excessive number of duplicate physician entries, which caused the physician search function to perform poorly. This was found to be related to the way duplicate physicians are handled.

The fix matches duplicate physician records against the oldest entry, preventing further issues.

The application was experiencing slow performance and blocking issues due to triggers being reactivated.

Logic added to correct issue from occurring.

Some patient custom attributes, such as "Continuous Observation" and "Urinary Catheter Insertion," were not being removed when sent with empty double quotes in ADT messages. Other attributes using the same format, like "72 Hour Hold" and "Suicide Precautions," worked as expected. Investigation revealed that a 20-character limit on ADT Tag Names was preventing proper removal.

The character limit issue was identified as the root cause. The limit on characters has been increased to 50 characters.

An OR patients could not be discharged using the ADT Transaction or manual discharge process due to a Null reference in the database

The issue was caused by discharge logic. We updated the logic to handle this missing data and use an alternative location value as backup in this scenario.

A user without the correct permissions was able to change a cleaning job to a “Clean Next” status. This was not expected behavior, as their role did not allow prioritizing cleaning tasks.

The system was updated to prevent users without the right permissions from prioritizing cleaning jobs. The update ensures users can no longer change job priorities unless their role allows it.

When using Firefox version 134.0.0, the login box on Capacity Management Suite® page fails to load. However, the login page loads on version 133.0.3.

Web components are updated allowing the page to load. It is still recommended to use the latest browser version.

A previous hotfix applied to 2024.02 included an outdated version of a script, causing issues with last modified date tracking.

The script was updated to ensure the correct changes are applied. This adjustment ensures accurate last-modified date tracking, preventing further issues.

Emails were not being sent for Care Progression Threshold Alerts, preventing timely notifications.

Logic was improved in multiple areas to correct the issue with alerts.

In PatientTracking Portal, the "Close" button in the Orders Dialog box displayed as <%$ Resources:Resource, BedAttributesDialog_CloseButton %> instead of "Close." While the button functioned correctly, it caused confusion and included a delay before closing.

A fix was developed that corrects the button displaying improperly.

Whiteboards lost their chosen unit settings nightly after the app pool recycled. This caused the patient list to display "no data found" until the unit was manually reselected or the user logged out and back in.

The system was updated to resolve the issue of whiteboards losing unit settings after the app pool recycle. While the fix addresses unit settings, console changes still revert to default unless saved before an IIS reset.

The Daily Cleans Standard Report in Capacity Management Suite versions 22.11 to 23.10 experienced significant performance delays. The report completion times were suboptimal due to inefficiencies in logic

A hotfix was implemented and tested successfully, leading to improved report completion times.

In Capacity Management version 2023.02, the In-progress and Complete Times in the Daily Cleans Standard Report did not match the reported duration. Users could not reconcile average clean times with the aggregate clean times, leading to data inconsistencies.

The report's calculation logic for average clean times was reviewed and corrected to ensure alignment with the aggregate clean time values.

Both fixes are combined into one file change, ensuring optimal performance and data accuracy for the Daily Cleans report across all applicable versions.

Electronic BedBoard units disappeared after an IIS recycle, requiring users to log out and perform manual interventions to restore functionality. This issue disrupted workflows and delayed bed management processes.

The system was updated to prevent Electronic BedBoard units from disappearing after an IIS recycle. The fix ensures that bedboard functionality remains stable and accessible, even after IIS restarts, improving overall reliability for users.

After upgrading to version 2023.09, reason codes in dropdown boxes, such as Cancel Bed Request, were displayed in the order they were added to the dictionary rather than alphabetically. This deviated from the expected behavior in version 2021.09.

The issue was resolved by updating the dictionary query logic to enforce alphabetical ordering for dropdown items.

Users encountered an "unable to process request" error when attempting to log into the IVR system on Capacity Management Suite version 24.02, preventing successful access.

The issue was resolved through an updated configuration file.

An error occurred when assigning zones for Environmental Services (EVS) employees with variable memberships or device IDs in the BedTracking module. Users were redirected to an error page when trying to select or deselect sections and zones in the "Change Assignment" window.

The issue was resolved by updating the system to handle assignments for variable memberships correctly. The error message no longer appears, and the "Change Assignment" functionality now behaves as expected.

Conflicts were identified between hotfixes OP-9106 and OP-9129, both of which modified the same DLL (TeleTracking.Enterprise.ApplicationIntegrationController.Business.DLL). This caused issues with the Intra Unit Transfer Outbound Logic.

The workflow was reviewed, unnecessary files were removed, and the outbound message functionality was validated. Confirmation of merging these hotfixes was addressed, ensuring all relevant changes were included in this release.

Staff assignment requests and EVS notifications were failing due to a missing DLL. This issue disrupted key workflows for staff assignments and notifications.

The missing DLL was added to the system, restoring functionality for staff assignment requests and EVS notifications. The fix has been validated, and the issue is now resolved, ensuring stable operations for version 24.02.

The German translation of the “Requests by Hour of Day” report showed zeros for “Avg Transport Time” and “Avg Total Trip Time.” The issue was caused by a translation mismatch in a database table. This affected a German only environment.

The stored procedure was adjusted to account for mismatch, ensuring correct data display for the affected fields.

In version 2023.09, the "Delay/Dispatched" status appeared twice in the TransportTracking User Notifications settings. This issue was not present in version 2023.07 and likely began in version 2023.09, as confirmed by analysis of multiple systems.

The duplicate status entry was removed through a validated fix.

Users reported that the Telebot icon was missing on Capacity Management tabs after a hotfix was implemented. The issue persisted across multiple environments, with incorrect values being passed during navigation.

The issue was resolved by updating the system to use the correct TeleBot App ID for each environment. After cycling IIS, the Telebot icon now appears correctly on Capacity Management tabs, ensuring visibility across all supported regions.

Users were being logged out of the system unexpectedly, even when actively working. The session timeout settings were not being honored, causing active sessions to terminate incorrectly after the configured duration.

The issue was resolved by updating the system to ensure session timeouts only apply to idle users. Active sessions are now retained as expected, aligning with the group timeout settings. Validation confirmed the fix's effectiveness across multiple environments.

The client experienced 40+ second delays in their Test environment after upgrading to version 24.02. These delays occurred whenever an action was performed and were traced to requests made to LogRocket, despite the feature being disabled in the settings.

The LogRocket integration was fully removed from the system to eliminate the delays. This ensures faster page loads and consistent performance across all environments.

Automatic transport jobs were not cancelling as expected when a bed status was changed to "Dirty" or when a "Ready-to-Move" (RTM) status was removed. These actions either failed to cancel the transport job or generated an error message.

The system was updated to ensure transport jobs are cancelled automatically when bed statuses change or RTM designations are removed. Error handling was also improved to eliminate generic error messages, restoring expected functionality.

Variable users in the Transport and EVS mobile apps were not being prompted to select their sections and zones after their initial login. Once logged out, assignments became "stuck," and users bypassed the selection screen upon subsequent logins. This issue was observed only in German environments and was likely related to German translation settings.

Updates to how membership is provided for users was corrected.

The Instant Notify History Report displayed inconsistent timestamps across different notification methods. Notifications for handheld-a devices appeared in UTC time, while push, email, and screen alerts showed local server time.

The system was updated to ensure all notification timestamps in the Instant Notify History Report display in local server time, providing consistency across all devices and notification methods. This resolves the issue for handheld-a devices and aligns their timestamps with other notifications.

The "Forgot Password" screen was not displaying correctly, preventing users from accessing the password reset feature. While the screen’s email functionality was unaffected, some users reported not receiving password reset emails.

The issue with the "Forgot Password" screen was resolved, ensuring it renders correctly for all users. Email sending functionality was not modified, but users experiencing issues were advised to verify their email configuration settings.

PreAdmit columns were not aligning correctly causing issues when scrolling through the console.

The misalignment was caused by discrepancies between the header and list content scrollbars. A fix was applied by adding a scrollbar to the header or a placeholder for alignment.

When filtering the Daily Clean Detail report by user, no data was displayed. The issue was The issue is related to the initial data insertion into the temporary table. Specifically, filtering by User ID resulted in the exclusion of job-created entries, resulting in a blank report.

The report logic was updated to ensure job-created entries remain visible when filtering by User ID.

The MessageBrokerMessageQueue was processing messages very slowly due to duplicate physician data, which disrupted backend operations. Additional latency was caused by the SQL server and application being hosted in different regions.

The system was updated to handle duplicate physician data more efficiently and streamline backend processes. Additionally, the SQL server and application were aligned to the same region, reducing latency and improving transaction speed.

The Automated Discharge Report was not displaying data despite discharge events appearing in the system. The issue was suspected to be related to the report expecting a confirmed discharge status, which in this case was not being used.

The report logic was updated to correctly display discharge events, even when only pending discharge statuses were used.

The "Last Seen" column was missing in Patient Tracking Portal. Instead, two "Gender" columns appeared, with one showing the correct "Last Seen" data.

The issue was caused by an incorrect translation which led to a mislabeled column.

Multi-Stage Clean jobs were unable to transition past the UDEF8 status in the XT UI and Mobile Application. Dropdown selections were not available, preventing manual and automated job transitions.

The issue is resolved by updating missing database values related to workflow transitions.

When a Walkout Alarm triggers, the alarm displays the patient’s previous location instead of their current location. This issue was confirmed in both in-house testing and at multiple sites, affecting accuracy in tracking patient movement.

The location tracking logic is now corrected, ensuring alarms now display the patient’s actual current location. Email alerts now confirm the correct location.

The "Stat Job" system reason code in BedTracking couldn’t be selected by users. This was because the reason code wasn’t connected to a group, which made it unusable in the system.

We fixed the issue by connecting the reason code to the right group. This ensures that system reason codes are accurately generated. Users will still be unable to select them if they are not authorized to do so.

The LastModDate field in the database was not being updated consistently, affecting the ability to pull accurate data through Minifi. Existing triggers were only applied after updates, missing changes when data was inserted.

We created new rules in the system so that whenever new data is added or updated, the LastModDate field will automatically be set to the current time. This makes sure the system always has the most up-to-date information when pulling data, even if someone had manually entered a different date before.

After signing into the Capacity IQ® EVS app, housekeepers were not appearing on the Employees tab in BedTracking. Despite the application of prior fixes and service restarts, the issue persisted, impacting system functionality.

The resolution ensures EVS employees will display correctly on the Employees tab after implementation.

In Capacity Management Suite version 2023.09, the LogDetail table recorded 230,000 error messages daily. This was caused by a configuration issue with the MPI Feature for Cross Campus. While the client was unaware, the large number of errors could slow down the system.

The configuration issue was fixed to stop the system from generating unnecessary errors. The solution is included in version 24.02, ensuring the LogDetail table now functions correctly.

When a external staff assignment system’s staff role is mapped in Capacity Management Suite®, the staff assignments work as expected. However, if a role that is not mapped in Capacity Management Suite is used, the staff assignments are not created, and they do not appear in the Patient Tracking Portal.

The system has been updated to ensure that staff assignments are processed correctly, even if the role is not mapped in Capacity Management Suite. Previously, the system would discard the entire message if it included an unmapped role. Now, unmapped roles will no longer prevent valid assignments from being processed and displayed in the Patient Tracking Portal.

When editing a user profile in Capacity Management Suite®, users were unable to search for other users in the "Copy to" section, even when entering the correct information. This issue was specific to version 2023.09.

The system was updated to fix the search functionality in the "Copy to" section of the user profile. Users can now successfully search for and find other users when copying information, ensuring that the feature works as intended.

When running the Instant Notify History report, the system would display the full report, even if you tried to filter by a single sender or recipient. This made the report longer than necessary and harder to use.

The system has been updated to ensure that the report now correctly filters by the selected sender or recipient. This makes the report shorter and more focused, showing only the relevant results based on the filter applied.

Capacity Management Suite® was not processing the removal of StaffAssignment through Care Team Assignment (CTA) integration. When CTA sent messages to remove assignments, the microservices relayed the packets to CMS, but CMS failed to handle the removal, causing inconsistencies in staff assignment workflows.

The issue was resolved by updating Capacity Management to process StaffAssignment removal messages sent through CTA integration.

After an IIS cycle on the web servers, units on the Electronic BedBoard were missing. Users had to log out and back in to attempt to resolve the issue. The problem persisted until IIS was manually reset by client support.

The system has been updated to ensure that units on the Electronic BedBoard are properly loaded after an IIS cycle. This prevents the units from disappearing and eliminates the need for users to log out or manually reset IIS.

After upgrading to version 24.02, the Discharge Disposition database flag was incorrectly set to FALSE by default.

A hotfix was developed to enable the flag by default.

In Capacity Management Suite version 2023.09, the TransportTracking Employee Performance report failed to display the names of newly added employees. Instead, their performance totals were grouped together under a "NULL" entry in the database due to missing IVRID values. This impacted the accuracy of the employee performance report.

A function was developed to address the missing IVRID values, ensuring new users are properly recorded in the database. This solution ensures the Employee Performance report will display all user data accurately.

The Skip-Database flag in the Installer was not functioning, causing issues during installations and increasing downtime windows on affected servers.

The installer was updated to include a new GUI that correctly supports the Skip-Database flag. Additional changes were made to ensure compatibility by installing the required ODBC driver. The issue was resolved in the code, and testing confirmed the flag now works as expected.

The HIPAA Patient Audit Detail report experienced significant performance delays. When a nested procedure was executed, it returned no rows but took hours to complete, leading to operational inefficiencies.

Optimized the nested procedure, which improved execution time and enabled the procedure to return results promptly.

Supervisors were not receiving escalation alerts, even though the alert settings and user permissions were correct. The issue occurred when a supervisor had a fixed membership type for an entire campus, and the alerts were not being triggered as expected.

The system was updated to ensure that supervisors with a fixed membership type will receive escalation alerts correctly. This change addresses the issue where the system only triggered alerts for supervisors with a variable assignment. The updated alert logic now applies to both fixed and variable membership types, ensuring alerts reach all relevant supervisors.

When a bed transitioned from "in progress" to "clean" following Stage 1 of a multi-stage cleaning, transport jobs were automatically generated. Unfortunately, the bed was actually moving to a post-cleaning status (UDEF9), leading to confusion and the unnecessary creation of transport jobs.

The system was updated to ensure that beds undergoing multi-stage cleaning transition correctly from Stage 1 to Stage 2 without triggering transport jobs. This change ensures that transport jobs are only created when appropriate, improving the workflow for Environmental Services (EVS) and the transport team.

When changing a patient's bed assignment after an auto transport job was created, an error occurred, resulting in a log message stating: "Format String can be only 'D', 'd', 'N', 'n', 'P', 'p', 'B', 'b', 'X' or 'x'." This disrupted the auto transport job workflow and caused delays.

The system was updated to handle bed assignment changes correctly for auto transport jobs, resolving the format string error. Testing confirmed that bed assignment updates now proceed without issues, ensuring smooth operation.

Outbound bed request updates were sending patient Date of Birth (DoB) information that was off by one day. The issue was traced to a discrepancy between the Iguana database and the Capacity Management Suite® database, where the DoB had a timestamp from the previous day, depending on the campus's timezone.

The system was updated to ensure that the correct Date of Birth is sent in outbound bed request updates. The fix synchronizes the data between the Iguana database and Capacity Management Suite®, so that the patient’s correct DoB is displayed in both systems.

In the bulk sync process, the Unit ID was missing from the bed location data, causing issues on the IQ platform. This led to problems such as bed assignments being lost during bed request synchronization.

The system was updated to ensure that the Unit ID is included in the bulk sync for bed locations. This fix helps prevent issues with bed assignments and ensures that the IQ platform has the correct unit information during the sync process.

Users who do not have RAC request rights were unable to log into the interactive (touchscreen) wall displays using their IVR ID. When attempting to log in, they received an "An Error Has Occurred" message. This issue was tied to user permissions for requesting RAC in their assigned roles.

The system has been updated to ensure that users without RAC request rights can still log into the interactive Portal display using their IVR ID. This fix allows users to access the portal without needing additional permissions, resolving the login issue.

German translations for several items required updates and review mid year 2024.

The translation updates have been reviewed and merged into the system.

The Patient Purge feature was not functioning correctly in version 24.02 because the version number had not been updated with the new release.

The issue was resolved by updating the version number to ensure that the Patient Purge feature works as expected. The fix has been confirmed to work and has been successfully applied to the system.

Users, particularly those in transport roles, were getting stuck in a Logged In state on the mobile app and were unable to log out to change their access. This caused frustration as they could not reset their sessions without technical support.

The issue has been resolved by updating the system to prevent users from being stuck in a Logged In status on mobile. This allows users to log out and change access without requiring technical intervention.

Users needed a way to create eSaf role assignment templates through the Admin Tool, with options to set specific assignment types for EVS and Transport. This required updates to both the user interface and backend to support the new configuration options.

The system was updated to add EVS Assignment and Transport Assignment dropdowns to the Custom User Provisioning Configuration screen under User Management in the Admin Tool. These fields are optional and allow users to select from predefined assignment types, improving flexibility in role management. German translations for the labels are included.

eSaf requests were not correctly handling EVS Assignment Type and Transport Assignment Type. Hard-coded logic caused assignment types to be updated only during user creation, and manual changes in CMS were not conforming to the role’s configuration. Additionally, updates were being applied even when users were logged in.

The system now uses Role Config values to set EVS Assignment Type and Transport

Assignment Type during both Create and Update user requests.

In environments with both Auto Transport Jobs and the Multi-Stage Cleaning feature enabled, an issue was identified where auto transport jobs were being incorrectly created and then immediately cancelled. This occurred after the first stage of cleaning, even though a new transport job should only be created after the second stage of cleaning is completed.

The system has been updated to ensure that auto transport jobs are only triggered once all stages of cleaning are complete. This prevents jobs from being prematurely created and cancelled, ensuring that the correct workflow is followed for multi-stage cleaning.

In environments with both Auto Transport Jobs and the Multi-Stage Cleaning feature enabled, transport jobs were being created and then immediately cancelled after the first stage of cleaning. This was unexpected, as a new transport job should only be created after the second stage of cleaning is completed.

The system has been updated to ensure that transport jobs are only triggered after the second stage of cleaning is completed. This fix prevents premature job creation and cancellation, ensuring that auto transport jobs follow the correct workflow.

The compatibility of the EVS, TT, and Nurse apps needed to be verified with the upcoming iOS 18 to ensure smooth operation for users.

The apps were tested on iOS 18 and confirmed to work without any issues. This ensures that the apps are fully compatible with the upcoming iOS version.

In BedTracking, when changing a bed status to "Blocked," the dropdown for selecting a reason code displayed options in a random order, making it difficult for users to locate specific reasons efficiently.

The system was updated to ensure that blocked bed reason codes are displayed in alphabetical order in the dropdown. The fix also included adjustments to handle case sensitivity, ensuring consistent sorting. Testing confirmed the updated sorting functionality works as expected.

The XTMessageBrokerQueueService.exe experienced a System.NullReferenceException, causing it to terminate unexpectedly. Slow database operations further delayed message processing, and intermittent blocking issues required monitoring to ensure consistent performance.

The issue was resolved by fixing the error and improving the logic for handling backend operations. Database performance was enhanced by refining processing methods and adding optimizations. Testing confirmed improved performance, resolving the immediate issue and stabilizing message processing.