Introduction
The Capacity Management Suite® solution is a fully integrated suite of patient flow solutions that includes the BedTracking® application, the PreAdmitTracking® application with the electronic bedboard® view, the TransportTracking™ application, the PatientTracking Portal® application, and the Custom Reporting Solution™ application.
Third Party Hardware Requirements
System Performance
System performance will vary based on data volume, network, and server capacity.
Server Hardware Requirements
The Capacity Management Suite® solution supports the following server models:
Server Requirements per Hospital Size
The minimum requirements listed below are dependent on the size of the hospital that is deploying the Capacity Management Suite® solution.
These requirements are for the current Capacity Management Suite® solution release. Any existing client who is considering an upgrade to the current version would need to consider how these requirements affect their hardware setup.
Application, IVR and Web Servers
Hospitals with a Combined Bed Count of | RAM (Win 2016 - 2019) | CPU Cores (Win 2016 - 2019 |
0 to 149 | 16 GB | 4 @ 3.1 GHz |
150 to 799 | 16 GB | 4 @ 3.1 GHz |
800+ | 16 GB | 8 @ 3.1 GHz |
Web Server
For larger clients, a separate web server is required to handle the load generated by the system. Please see the table below for guidelines:
Hospitals with a Combined Bed Count of | RAM (Win 2016 - 2019) | CPU Cores (Win 2016 - 2019) | Number of Web Servers |
1,200-2,000 | 16 GB | 4 @ 3.1 GHz | 1 |
2,001-4,000 | 16 GB | 4 @ 3.1 GHz | 2 |
4,001-6,000 | 16 GB | 4 @ 3.1 GHz | 3 |
6,001-8,000 | 16 GB | 8 @ 3.1 GHz | 4 |
9,001-10,000** | 16 GB | 8 @ 3.1 GHz | 5 |
Hospitals with additional bed sizes or who plan to enable Command and Query Responsibility Segregation (CQRS) should contact TeleTracking for more information about hardware requirements.
**Example Configuration of Hospital with a Combined Bed Count of 8,001-10,000 Beds
App Server: 8 CPU Core with 3.1 GHZ and 16 GB RAM
Web Servers: 5 web server each with 8 Core of 3.1 GHZ and 16 GB RAM, balanced through a Load Balancer
Database Server: 48 Core @ 2GHZ and 128 GB RAM
Hospital Capacity Indicators: Number of licensed beds: 8000-10000 Number of active users at any point of time: 2000-2500 Number of active patients present in the system: 0.1 to 0.2 Million Number of ADT messages in peak hour: 8000 to 10000
Application Server Requirements
Dedicated Servers Required | 1 |
Architecture | Intel® 64-bit or Equivalent AMD processor is supported. |
Server Operating System | Windows Server® 2016 Windows Server® 2019 The Capacity Management Suite® solution installed on Windows Server 2019 cannot reliably be integrated with the Rauland staff assignment System. Integrations with other staff assignment systems, such as Hill-Rom® and Kronos®, may also be affected. |
CPU | Intel® Xeon® processor, 2.0GHz, 133MHz FSB, or equivalent AMD CPU. |
RAM | For details on Socket and Core Requirements, see Server Requirements per Hospital Size |
Disk Architecture | RAID 5 |
Free Internal Disk Space | 80 GB for the application partition and a separate 80 GB operating system partition |
Fault Tolerance | RAID |
High Availability | Yes. Active/Passive. TeleTracking allows failover clustering within Microsoft Clustering Services, but will not set up and support this environment for our clients. This is the responsibility of the client's server administrator (or equivalent role). |
Backup Device/Method | Customer provided. Backup must have open file capability. File locking must be disabled. |
Proprietary Hardware | Not required. |
Application is CPU Intensive | No. |
Paging File Size | Use recommended Microsoft® Windows setting. |
Microsoft® Windows PowerShell™ | Minimum Version 5.1. Execution Policy cannot be set to Restricted, AllSigned, or RemoteSigned. |
Load Balancing | Supported on web tier only. Only supported with Microsoft® Network Load Balancing. However, TeleTracking will not set up and support this environment for our clients. This is the responsibility of the client's server administrator (or equivalent role). We recommend using Source IP persistence with a persistence time of the average shift length (8 hours). |
Web Server and Third Party Software Components | Microsoft® Internet Information Services (IIS) is a built-in component of your Windows OS and Server. Versions are as follows:
The following are required and installed by the TeleTracking installation program:
|
Third-Party Software |
|
Virtualized Servers | The server can be a virtualized server as long as the virtual machine meets all requirements that are specified in this document for each server and for resources dedicated to the virtual machine, and as long as the virtualized server only supports a network-based configuration. In particular, comply with all requirements for network paging. TeleTracking will not set up and support this environment for our clients. Support for this environment is the responsibility to our client’s server administrator or equivalent role. Performance can vary greatly based on hardware, configuration, and utilization. All systems should conform to Microsoft’s Best Practices. VM environments may increase RAM and CPU requirements. |
Microsoft® Active Directory | Secure Socket Layer SSL=Yes - Optional but strongly recommended for the Capacity Management Suite® solution versions 2022.02 and earlier. Required for the Capacity Management Suite® solution v2022.03 and later. Clients must supply a valid SSL certificate. Trusted self-signed or third-party provided (Verisign) certificates are valid. Test certificates are not considered valid. Premise Active Directory is supported for Capacity Management Suite® solution in the following deployment options:
|
Website Encryption | Secure Socket Layer is optional but strongly recommended for the Capacity Management Suite® solution versions 2022.02 and earlier. Secure Socket Layer is required for the Capacity Management Suite® solution v2022.03 and later. |
Workstation Requirements
Workstation Operating Systems | Windows® 8, Windows® 10, Windows® 11 |
Paging File Size | Use recommended Microsoft® Windows® setting. |
CPU/RAM | Intel® Pentium® or equivalent AMD CPU. Less robust processors, such as Intel® Atom™ or AMD Fusion processors, are not equivalent to the processor that is specified above and may cause performance issues. Workstations with Intel® Atom™ or AMD Fusion processors may be used for wall-mounted public displays, but not for interactive features. |
Disk Space | 20MB+ |
Network Interface | Ethernet 100/1000 Mbps. |
Monitor Requirements | 15” 1024x768 32-bit color depth For public views and/or department view-only displays, TeleTracking recommends a display of 50” or above at a resolution of 1280 x 1024. |
Browser Required |
Third Party Software Components
Microsoft® Excel® or Excel® Viewer installed on workstation for displaying reports
Supported Paging Methods
Standard
SNPP (Simple Network Paging Protocol) — This protocol is Network based, Numeric and/or Alphanumeric. It can be configured for SSL if valid certificates are provided and the feature is available from the paging/provider system. Clients must supply a valid SSL certificate. Trusted self-signed or third-party provided (Verisign) certificates are valid. Test certificates are not considered valid. l
SMTP (Simple Mail Transfer Protocol) — This protocol is Network-based, Numeric and/or Alphanumeric. It can be configured for SSL or StartTLS.
WCTP (Wireless Communication Transfer Protocol)
Vocera® 4.1 or higher
TAP paging is not supported.
Deployment Specific
Only SMTP, SNPP, and WCTP are supported when the Capacity Management Suite® solution is in the following deployment options:
Cloud-Hosted, TeleTracking IQ Enabled
When the Capacity Management Suite® solution is in On-premise deployment, WCTP requires the Gateway notification service on the TeleTracking IQ™ Platform connector server.
Vocera Specific
The Vocera® Messaging Interface (VMI) must reside on your hospital’s system. It is not available from TeleTracking.
The Vocera® devices tested by TeleTracking for the Capacity Management Suite® solution are the Vocera® smartphone and the B1000A and B2000 communications badges.
Network
Network Protocols | TCP/IP |
Requires Name Resolution | Yes |
DHCP Supported | No |
Shared Folders Required | Shared folders are required only for integration to the Census Based Scheduling (CBS) component of the Smart Facility™ (formerly Environmental Services Computer Tools (ESCt)) software. CBS and ESCt are not available when the Capacity Management Suite® solution is deployed in a Cloud-Hosted model. |
Mapped Drives Required | No |
Network Security Model | 2000 |
Internet Access | Yes. Needed for iNTERFACEWARE Iguana™ registration and Apple® Notifications Service messages.The registration process may be initiated from a client or server with Internet access. |
Managing Ports
General Port Openings
The following ports openings are applicable to most CMS implementations. The TeleTracking project team will indicate if any of these routes can be omitted:
Name | Port | Source | Destination | Direction |
User Access | TCP 80,443 | Workstations | CMS Application Server | Outbound |
Mobile User Access | TCP 443 | Mobile Devices | CMS Gateway Server | Outbound |
XT Reporting Service Communication | TCP 8523 | SQL Server | CMS Application Server | Outbound |
SQL Communication | TCP 1433 | CMS Application Server, CMS Gateway Server | SQL Server | Bidirectional |
Interface Ports | TCP 225XX* | Interface System or Integration Engine | CMS Application Server | Inbound or Outbound Depending on Port |
Mobile Notification Relay | TCP 443 | CMS Application Server | CMS Gateway Server | Outbound |
Mobile Notification Relay | TCP 5671 | CMS Gateway Server | 20.36.244.76, 20.242.51.105, 20.7.175.62 (TeleTracking Cloud Services) | Outbound |
Real-Time Transport Protocol (VoIP/SIP) | TCP or UDP 5060 | PBX | CMS Application Server | Bidirectional |
Real-Time Transport Protocol (VoIP/SIP | TCP or UDP 49151-49501** | PBX | CMS Application Server | Bidirectional |
Notification Sender Service | 10060 | CMS Application Server, CMS Web Server | CMS Application Server, CMS Web Server | Bidirectional |
*Interface ports will be customized per client. Ports will need to be opened in the direction that corresponds to the interface direction. Your TeleTracking project team can provide a specific port listing upon request.
**The ports listed here will be defined by the client telecom team, based on configuration of the SIP connection. The number of ports that need to be opened will reflect the maximum concurrent call volume.
Optional Port Openings
The following ports are required to be open systems for specific interfaces and are not applicable to all clients. The TeleTracking project team will advise if any of the following ports may need to be opened:
Name | Port | Source | Destination | Direction |
SMTP Notification | TCP 25 | CMS Application Server | SMTP Relay / Mail Server (Client Provided) | Outbound |
SNPP Notifications | TCP 444 | CMS Application Server | Paging Vendor (Client Provided) | Outbound |
RTLS Host Port | 6016 | TeleTracking RTLS Application Server | CMS Application Server | Bidirectional |
Staff Integration Utilities Service Host Port | 13373 | Staffing System | CMS Application Server | Outbound |
Rauland Service Host Port | 13374 | Rauland | CMS Application Server | Outbound |
External Integration Service Host Port | 13375 | External System | CMS Application Server | Outbound |
Census Based Scheduling | 13376 | External CBS System | CMS Application Server | Bidirectional |
Mobile Heartbeat | 8443 | 20.36.244.76. 20.242.51.105, 20.7.175.62 (TeleTracking Cloud Services | Mobile Heartbeat Endpoint (MH Cure Server | Bidirectional |
Software Details
Details and Design
The Capacity Management Suite® solution utilizes C#, Ajax, HTML, and Javascript. The application is an n-tier and web/browser-based architecture.
Server Side Software
Microsoft® .NET Framework 4.8 or later must be manually installed prior to updating to the Capacity Management Suite® solution v2021.12 or later.
iNTERFACEWARE Iguana™ (version 6.1.2) HL7 Interface Engine and iNTERFACEWARE Chameleon™ HL7 Messaging Toolkit.
The Capacity Management Suite® solution version 2021.12 and later requires iNTERFACEWARE Iguana™ version 6. Previous versions of the Capacity Management Suite® solution are compatible with Iguana™ versions 4 and 5.
Microsoft® ODBC Driver 17 for SQL Server
Microsoft® OLE DB Driver for SQL Server
Microsoft® Web Service Extension
Microsoft® Visual C++ 2015 - 2017 Redistributable program (x64), see https://www.visualstudio.com/vs/older-downloads/
Remote Access
System remote access is required to provide ongoing client support and services. TeleTracking’s preferred methods of remote access are included in the table below. If none of these methods are appropriate for your site, ensure that your implementation team is aware so that they can properly plan for the alternative.
Preferred Remote Access Types
Type | Description |
Bomgar™ (TeleTracking provided) | Fully audited and recorded remote access solution; HIPPA compliant; US and UK hosted systems available. |
SecureLink (TeleTrackingprovided) | Fully audited and recorded remote access solution – Existing SecureLink clients may setup a Nexus connection with TeleTracking’s SecureLink system. |
IPSEC Client to Gateway (client provided) | VPN Client connection configuration file must be included separately for each client – Cisco®, or Check Point® Clients Only. VPN client must support NAT Traversal |
Citrix Remote Access (client provided) | Access provided through client-controlled portal |
Tokens and Two-Factor Authentication for Remote Access
TeleTracking’s goal is to provide support for you in the fastest and most secure way. If two-factor authentication is required and a hardware token is used, the client must hold the hardware token. In this scenario, TeleTracking will work with you to develop processes for requesting access to your site. TeleTracking will not possess client-owned hardware tokens for remote access. Software tokens are generally not supported unless the authentication information can be shared securely via email.
Application Authentication
Proprietary | Yes |
Active Directory | Yes |
Single Sign-On | Supported for the Capacity Management Suite® solution version 2.3 and later. Single Sign-On is a configurable option. |
Compatible Tablets, Mobile Devices, and Smart Phones
Reference Mobile Software Versions - Info
iOS Version | Apple® - Latest Two Versions |
| ❗If you use iOS version 11.x, ensure that the Notifications setting Show as Banners is ON and set to Persistent (not Temporary) for your device, so that notifications will remain visible until they are acknowledged. |
| ❗iPad OS 15 or later supports the TeleTracking EVS™ mobile application. |
Android | Android® - Latest Two Versions |
| ❗Zebra models TC-25 & TC-52 have been tested |
Browser | Apple Safari® browser for iPad® and Google Chrome™ browser for Android™ tablets support the Capacity Management Suite® solution. |
Additional Requirements for Clinical Workflow® Suite Integrations
The Bed Management Suite® system may be configured with the Clinical Workflow® Suite (formerly Orchestrate™ application) to enable bed requests to be made directly from the Clinical Workflow® Suite to the Bed Management Suite® system.
Software Version 7.2 or later and Bed Management Suite® System Platform Version 2.1.30.4 or later
For additional Clinical Workflow® Suite requirements information, please refer to the Clinical Workflow™ Suite Technical Information Reference Guide.
Corporate Information
Reference Corporate Information