Ascom Telligence

The Ascom Telligence integrated system provides nurse call integration.

Setup

See the Data Servers page for information on configuring driver communication.

Compatibility

The Ascom Telligence integrated system has been verified against Telligence 6.8. By design, it is compatible with the below versions:
  • 4.X
  • 5.X
  • 6.X

Prerequisites

Software Minimum Version
IPFusion — Ascom Telligence 1.4
.NET Framework 4.7.2

When completing your setup, be sure to have the Ascom Telligence documentation available for reference.

Ports

These ports must be open in your network firewall for the integration to work.

Purpose Default Value Configurable
Station Assets 53249 Yes
Dataserver 9523 Yes
Debug Tools 9572 No

Communication Configuration

In the integrated system configuration panel, you will find the Communication Settings. The below information is required for the hardware sync functionality.

Server Address The address for the SQL server used for the Ascom system.
Username The username for the account used to connect to the Ascom database.
Password The password for the account used to connect to the Ascom database.
Database Name The name of the Ascom database.
Integrated Security Check this option if you want to use integrated security for the database connection.

Assets

Station Asset

This asset represents the state of a bedside module.

Required Property Grid Fields

Bed Id The identifier for the bed this station is associated with in Ascom Telligence.
Staff Console The console that holds the station's connection details. This is configured in the integrated system Communication Settings, then selected from the drop-down list.
Station Id The ID of the station within the Ascom Telligence system.

Optional Property Grid Fields

Tier 1 Escalation groups are used to determine where patient calls are sent. This property does not have any functionality on its own for the system, but can be used to configure sending alerts through Workflows. This is the first tier for an escalation group, which would typically be the group receiving an alert for the patient first.
Tier 2 Escalation groups are used to determine where patient calls are sent. This property does not have any functionality on its own for the system, but can be used to configure sending alerts through Workflows. This is the second tier for an escalation group, which would typically be the group receiving an alert for the patient second.
Tier 3 Escalation groups are used to determine where patient calls are sent. This property does not have any functionality on its own for the system, but can be used to configure sending alerts through Workflows. This is the third tier for an escalation group, which would typically be the group receiving an alert for the patient third.
Tier 4 Escalation groups are used to determine where patient calls are sent. This property does not have any functionality on its own for the system, but can be used to configure sending alerts through Workflows. This is the fourth tier for an escalation group, which would typically be the group receiving an alert for the patient last.

View all properties

Supported States

Note: The alarms and call request statuses in the following table are listed in order of highest to lowest priority when using the default configuration in the Ascom system. This priority overrides the one configured within the status table.
Normal The asset is online and in its default state.
Fault An issue has been detected in a connected asset.
Masked The asset has been masked over its true state.
Acknowledged An asset alarm has been acknowledged.
No Communication Communication has been lost with the driver or asset. This status can also occur if the communication configuration for the system or asset is invalid.
Note: This status is required in all status tables.
Room Alarm 1 A custom alarm for a room.
Room Alarm 2 A custom alarm for a room.
Code Blue A code blue call.
Code Pink A code pink call.
Staff Emergency 1 A custom alarm for a staff emergency.
Staff Emergency 2 A custom alarm for a staff emergency.
Lavatory Emergency An emergency call from a lavatory.
Urgent An urgent call.
Aux Emergency 1 A custom alarm from an auxiliary device.
Aux Emergency 2 A custom alarm from an auxiliary device.
Aux Emergency 3 A custom alarm from an auxiliary device.
Aux Emergency 4 A custom alarm from an auxiliary device.
Aux Emergency 5 A custom alarm from an auxiliary device.
Aux Emergency 6 A custom alarm from an auxiliary device.
Aux Emergency 7 A custom alarm from an auxiliary device.
Aux Emergency 8 A custom alarm from an auxiliary device.
Patient Priority 1 A custom alarm for a patient call.
Patient Priority 2 A custom alarm for a patient call.
Bed Exit An alarm for a patient exiting a bed.
Cord Pull 1 A custom alarm activated by a cord pull.
Cord Pull 2 A custom alarm activated by a cord pull.
Patient Normal A normal patient call.
Family A call for a patients family.
Staff Normal A normal staff call.
Housekeeping A call request for housekeeping.

See the Configure a Status Table page for more information on configuring status tables.

Supported Commands

Mask Mask the asset's true state.
Acknowledge Acknowledge an asset alarm.
Reset Resets the asset to its true hardware state.
Cancel Deselects all selected assets.
Acknowledge Call Acknowledges a call received on this station. This differs from the Acknowledge command as this one sends an acknowledgement to the Ascom system, rather than just acknowledging the alarm within Runtime.

See the Command Tables page for more information on configuring command tables.

Staff Console Asset

This asset represents the state of a staff console in the Ascom Telligence system. The Ascom driver uses ports 53000-53499 to connect to the Staff Consoles. If one of the ports is in use, the Ascom driver will automatically fail over to the next available port within this range. You must have at least one port per Staff Console asset available within this range, or you will experience connectivity issues with the Staff Console assets which cannot be assigned to an open port.

Required Property Grid Fields

Address The address used to connect to the Staff Console.
Duty Area The duty area number for this Staff Console.
Port The port used to connect to the Staff Console.

View all properties

Supported States

Normal The asset is online and in its default state.
Fault An issue has been detected in a connected asset.
Masked The asset has been masked over its true state.
Acknowledged An asset alarm has been acknowledged.
No Communication Communication has been lost with the driver or asset. This status can also occur if the communication configuration for the system or asset is invalid.
Note: This status is required in all status tables.

See the Configure a Status Table page for more information on configuring status tables.

Supported Commands

Mask Mask the asset's true state.
Acknowledge Acknowledge an asset alarm.
Reset Resets the asset to its true hardware state.
Cancel Deselects all selected assets.

See the Command Tables page for more information on configuring command tables.

Hardware Sync

The hardware sync functionality is used to sync the assets in your project with the Ascom system. This will import missing assets, update existing assets with information which does not match in Ascom, and delete assets which do not exist in the Ascom system.

Before using the hardware sync, you must first configure the Communication Settings in your project.

The hardware sync will match assets existing in your project to ones on the server to determine required changes. Staff Consoles will be matched based on either Duty Area or Address. The Station assets are matched based on Bed ID and Station ID.

To sync the assets in your project with the Ascom server:

  1. In Project Explorer, right-click the Ascom Telligence system and select Hardware Sync.
  2. For each asset type, check the actions you wish to complete:
    • Add missing assets.
    • Update assets which have outdated settings.
    • Remove assets which do not match with any hardware.
  3. Before syncing the hardware, you may Export a summary of all changes which will be made to the Ascom assets. The settings which are exported are:
    • Asset — The asset type.
    • Id — The ID of the asset within Designer.
    • Action — The action being completed for the asset (add, update, or remove).
    • CurrentCaption — The asset caption prior to the hardware sync being completed.
    • CurrentDutyArea — The duty area of a staff console prior to the hardware sync being completed.
    • CurrentAddress — The address of a staff console prior to the hardware sync being completed,
    • CurrentPort — The port of a staff console prior to the hardware sync being completed.
    • CurrentStationId — The ID of a station prior to the hardware sync being completed.
    • CurrentBedId — The assigned bed ID for a station prior to the hardware sync being completed.
    • UpdatedCaption — The asset caption after the hardware sync is completed.
    • UpdatedDutyArea — The duty area of a staff console after the hardware sync is completed.
    • UpdatedAddress — The address of a staff console after the hardware sync is completed.
    • UpdatedPort — The port of a staff console after the hardware sync is completed.
    • UpdatedStationId — The ID of a station after the hardware sync is completed.
    • UpdatedBedId — The assigned bed ID for a station asset after the hardware sync is completed.
    • Maps — The maps which this asset has been placed onto.
  4. Click Apply to make the changes to your project.

Troubleshooting

Staff Consoles Going Into No Communication Repeatedly

If you find there are Staff Consoles which are repeatedly going into no communication status for a moment, then back to their previous status, there may be an issue with the connection. To resolve this issue:

  1. Contact your network administrator to confirm the ports within the range of 53000-53499 are not being used by another process. There must be at least one port available within this range per Staff Console in your project.
  2. Restart the Ascom Telligence driver.

Logs from the driver and Runtime can be viewed in the Debug Tools client. These messages contain information which can provide further context for issues during initialization, or while actively running. This can help diagnose problems.