Telligence 6.0 Guideline Specification · Web viewGuideline Specification. Patient Response System, Telligence v6.1. Rev .04 8 March 2019. Foreword. If you have a standard IBM-compatible

Guideline SpecificationPatient Response System, Telligence v6.1

Rev .04 8 March 2019

ACDM-1683967683-291 Ascom (US) Inc. | 300 Perimeter Park Drive, Morrisville, NC 27560 USA | www.ascom.com/ws

Foreword

If you have a standard IBM-compatible computer with Microsoft® Word® installed, you can use an electronic copy of this file to develop a specification that outlines a standard of performance when soliciting a quotation. This file guides the Specifier (you) in selecting the system options required for a specific project. By saving the file under a new name and deleting the specifier notes and unwanted optional functions and features, you can create a custom specification for your project. It is assumed that you have a basic knowledge of the Telligence VoIP Based Nurse Call System manufactured by Ascom, and that you are familiar with Microsoft Word’s numbering and style features.

Proprietary Notice

The information contained within this file and any subsequent additions, revisions, updates, or corrections are and shall remain the property of Ascom. Any unauthorized reproduction, use, or disclosure of the information for purposes other than the development of Engineering Specifications for specific projects, or any part thereof, is prohibited. This material is meant solely for use by Authorized Ascom employees or partners.

Disclaimer

Every effort is taken to ensure the accuracy of the information contained in this file. However, this information is provided for development of specific project specifications based on customer requirements. Any additions and deletions to the file not authorized by Ascom or the SPECIFIER are without warranty of any kind, either expressed or implied, in respect to the contents of this file. Ascom reserves the right to make changes in the specifications at any time, without notice.


EDITING INSTRUCTIONS

To edit the electronic version of the Telligence Guideline Specifications:

1. SAVE a copy of the document under a new name BEFORE editing it for a specific product. Edit the copy, not the original file.

2. DELETE preceding pages (Title and Foreword) and these instructions before final printing. Start the specification with the next page. Enter the project name and location in the project name box.

3. Delete all the boxed SPECIFIER paragraphs as you edit the document by selecting the specifier text with your mouse and pressing the DELETE key.

4. The document uses Word’s automatic numbering feature. When deleting paragraphs for options that will not be included in the final specified system, the remaining paragraphs and sub-paragraphs should automatically renumber.

5. To add an unnumbered paragraph after a numbered paragraph, place the cursor at the end of the previous paragraph and press Shift Enter to insert a soft carriage return. If a space is required between paragraphs, press Shift Enter a second time.

6. To add a numbered paragraph after a numbered paragraph, place the cursor at the end of the previous paragraph and press Enter to insert a hard carriage return. You may need to assign the proper style to the new paragraph for it to indent and number properly. Place the cursor anywhere in the paragraph and select the appropriate style from the far-left pull down list in the formatting toolbar. You will only use styles Heading 2 through Heading 6.

7. Words or statements in brackets [ ] provide a choice or option that may or may not be required. Remove the [statements] not required and remove the brackets from valid statements. If the word is in [italics], enter the appropriate number or phrase to complete the sentence.

8. Words or statements in parenthesis ( ) clarify the previous word or statement. They are not removed.9. To insert a page break, place the cursor at the end of the last paragraph for that page, or at the

beginning of the first paragraph for the next page, and press Ctrl Enter.


GLOSSARY OF TERMS

ADT: Admission Discharge Transfer SystemAHJ: Authority Having JurisdictionAS: Australian Standards AWG: American Wire GaugeCAT 5/5e/6: Category ratings for twisted pair cable used for carrying signalsCCTV: Closed Circuit TelevisionDC: Direct CurrentEHR: Electronic Health RecordEMR: Electronic Medical RecordFDA: Food and Drug AdministrationGUI: Graphical User InterfaceHL7: Health Level 7 protocolIP: Internet ProtocolLAN: Local Area NetworkLCD: Liquid Crystal DisplayLED: Light Emitting DiodeNEC: National Electric CodePBX: Private Branch ExchangePC: Personal ComputerPDA: Personal Digital AssistantRTLS: Real Time Locate SystemSIP: Session Initiated ProtocolSQL: Structured Query Language (used to communicate with a database)T1: High speed data transmission lineUL: Underwriters LaboratoriesVoIP: Voice over Internet ProtocolWAN: Wide Area Network


<Project Name>IP Patient Response (Nurse Call) System

<Insert Date>


1 IP ARCHITECTURE

1.1 IP Network (Local Area Network)

A. The System shall be IP network-based and incorporate decentralized, distributed intelligence architecture. This intelligent architecture shall be built on an IP (Internet Protocol) network and support using the facilities local area network (LAN) for functions approved by local regulatory bodies.

B. The System shall allow both data and voice to be distributed over a common network infrastructure, which is consistent with the communication industry. Communication devices on the network will utilize standards-based protocols.

C. The system shall support both DHCP and BootP protocols for IP address handling.

D. The System shall also provide a means of interoperability with 3rd party wired and wireless network devices within the facility, including PCs, PDA's, mobile phones, databases, pagers, etc.

E. The System shall be capable of Hill-Rom and/or Stryker bed side-rail communication compatibility including visual and audible annunciation of patient safety and fall prevention alarms generated by the bed and of disconnected bed.

F. It shall be possible to configure the System using a modular, flexible GUI application that provides the system administrator the ability to manage, (add, delete, modify) and diagnose information within the nurse call network. Systems not supporting administrative access remotely shall not be accepted.

G. The System shall not rely on any computer for primary operation. Systems requiring a PC to be connected for UL1069 operation shall not be accepted.

H. IP Devices shall accept switches or power supply devices (such as PoE+) approved by local authority having jurisdiction.

2 NETWORK

A. IP nurse call systems shall be capable of using the facility’s local area network where approved by AHJ (Authority Having Jurisdiction).

B. The IP nurse call system must support the following network standards:

1. 10/100 BaseT networks, supporting auto negotiation2. Power over Ethernet (802.3 af and 802.3 at3. Wi-Fi (802.11 bg)4. Support of UDP for performance with security aspects handled in the

application


3 SYSTEM

A. System shall be capable of incorporating legacy nurse call equipment, 3rd party nurse call equipment (24V), and 5.5V equipment.

B. System shall be able to integrate with Electronic Health Records (EHR Systems) or similar via standard HL7 protocol.

E. Migration of legacy system shall be supported using existing cabling.

H. Supplier shall include all control equipment needed to enable open voice communication for patients within the system.

I. System shall support serial data transmission from medical equipment to pass through to centralized server for documentation into EMR/EHR systems.

J. System shall support in-room touch screen station with supported HTML5 browsers

K. System shall support integrated automatic presence of staff via mobile device.

L. System shall support multi-touch buttons which allows additional functionality on room devices. Example a short press can be staff assist and a long press can be a staff emergency.

3.1 Redundancy/Safe Mode

A. During system communication failure with the nurse call network it shall be possible that the Patient Call is still signaled at the dome light.

B. Dome light shall provide a visual indication of the system in “Safe Mode” on the top lens of the light.

C. Dome light shall display a “Room Alert” on the bottom lens of the light to indicate that there is an active request in the room while in “safe mode”.

4 PATIENT DEVICES

4.1 Pillow Speaker/Handsets

A. Provide one (1) bedside Pillow Speaker/Handset for each patient location. The Pillow Speaker/Handset shall have a magnetic plug to minimize potential device damage.

B. The Pillow Speaker/Handset shall contain selected options that include the nurse call button, a speaker (optional), and controls for TV volume and channels in a molded, flame-retardant, ABS housing. The cord shall be <8'> in length and have an integrated sheet clip.

C. System shall support patient-initiated requests via specific events like Pain, Toilet,Water, or SunBlind buttons.


4.2 Call Cords & Specialty Devices

A. Provide call cords as required. The call cord shall have a heavy duty, molded magnetic connector, a flexible PVC jacketed cable, and a molded, flame retardant, ABS switch housing. The switch shall be the momentary contact type. The cord shall be <8'> in length, have an integrated sheet clip, and be suitable for ethylene oxide sterilization.

B. Call Cords shall be of a sealed design with a smooth shape and minimal crevices to allow for easy, comprehensive cleaning to assist in keeping infectious contaminants out of the pendant and reduce the potential for cross contamination.

C. Call cord shall provide a call assurance LED indicating the patient a call has been placed.

D. Provide <INSERT QUANTITY> Breathcall® call cords for use by patients who do not have adequate use of their hands to initiate a call. The Breathcall® cord shall have a heavy duty, molded, ¼ inch connector, a flexible PVC jacketed cable, and a momentary contact switch that is sensitive to air pressure. The cord shall be <9'> in length, feature an adjustable arm for clamping the call cord onto a headboard or bed frame, and be suitable for use in oxygen atmospheres. Each Breathcall® call cord shall be furnished with twelve (12) replacement straws

E. Provide <INSERT QUANTITY> air bulb call cords for use by patients who must remain distant from electrical fixtures. The air bulb call cord shall have a heavy duty, molded, combination ¼ inch connector/air pressure sensitive switch. The "cord" shall consist of <8'>of flexible tubing terminated with an air bulb, have an integrated sheet clip, be suitable for use in oxygen atmospheres, and be suitable for ethylene oxide sterilization.

F. Provide <INSERT QUANTITY> geriatric call cords for use by patients who have minimal use of their hands to initiate a call. The geriatric call cord shall have a heavy duty, molded, ¼” connector, a flexible <white> <beige> <gray> PVC jacketed cable with a sensitive, momentary contact reed switch that requires only a gentle squeeze or tap to activate. The cord shall be <8’> in length, have an integrated sheet clip, and be suitable for ethylene oxide sterilization.

5 ROOM DEVICES

5.1 Patient StationA. Patient Station shall be an expandable to from single bed to dual occupancy without

hardware change. As a dual patient station unique bed ID shall be annunciated with associated events.

B. Patient Station design shall allow for mounting on a 2 gang or 3 gang back box enabling system options without increased rough in/ back box change requirements.

C. Patient Station shall support Serial Input from Pillow Speakers enabling options on Pillow Speakers functions.

D. Patient Station shall support integration to Smart Beds (Hill-Rom, Stryker, etc) for nurse call, entertainment and room controls in addition to transmitted bed alarm(s).

E. Patient Station shall provide a input from equipped Stryker beds to enable bed alarms to be annunciated within the nurse call system. Bed alarms shall include bed exit, bed height, angle, wheel lock and status of rails.


F. Patient Station shall provide three (3) configurable buttons. Each button shall be capable of two call types via a short press or long/double press activation. At minimum Code Blue, Staff Assist and Staff Emergency buttons shall be provided at each patient station location.

G. Single Patient configurations must provide a minimum of four (4) inputs that can be used for Pillow Speaker(s), Call Cord(s), Bed Integration and analog inputs from medical equipment.

H. Shall support Full-Duplex audio for Pillow Speaker when event is generated from patient device. Intercom response to staff calls shall open two way duplex audio to the Patient Station.

I. To support infection control measures, station shall support Cleaning Mode to temporarily disable buttons and cord disconnects without generating nuisance alarms to allow the device to be properly be sanitized.

J. Patient Stations shall offer basic or advanced maintenance mode of operation. Basic (Easy) will utilize dipswitch setting enabling plug and play replacements, while advanced will use serial number programming.

K. System connections shall utilize RJ45 connectors for simplified service.

5.2 Peripheral Devices

A. Peripheral Devices are addressable initiating modules that provide patient room call-for-assistance indication to the system. When a Peripheral Device is activated, visual indication of the call displays on the device for assurance, at the dome light associated with the patient room, and an appropriate alert indication registers on the staff console, as well as on any installed and covering annunciators.

B. Each room shall be capable of supporting up to 16 devices. These stations shall be configurable to generate any level of call supported by the system configuration. Examples of Peripheral devices are: Lavatory, Shower, Lav-Audio, Staff Emergency, Remote Cancel, Housekeeping, Code Blue, Code Pink, Urgent, Family Call, Staff Normal, Manual Presence, Auxiliary Inputs, Bed-Connect etc.

C. Room devices shall offer basic or advanced maintenance mode of operation. Basic (Easy) will utilize dipswitch setting, while advanced will use serial numbers.

D. Pushbutton/Pull Cord Stations shall be field configurable for a minimum of three total alerts/events on the single device mounting to a one (1) gang back box.

E. Call type/priority for each pushbutton or pull cord shall be programmable to annunciate the facility-determined call type.

F. Devices shall allow customization with buttons and matching re-assurance lights in the field.

G. The physical device button label shall be field replaceable to match the specified call type/priority. Systems requiring the device to be replaced by a new device to match a new call type/label or require buttons to be purchased from the manufacturer shall not be accepted.


H. Peripheral device buttons shall be configurable for ‘Toggle On / Toggle Off”, supporting bed management, patient flow, workflow and other non-clinical type events, as defined by the facility.

I. Peripheral device buttons shall have multiple functions—short press, long press and double press—that can activate different alerts or room status.

J. Peripheral devices shall provide on-board lighting for visibility in dark rooms.

K. Peripheral devices shall support the reuse of existing category cabling (Cat5/5e/6)

L. Each Peripheral device button shall have a dedicated LED to indicate that the button has been pressed or is actively indicating a call.

M. LED assurance must match the color of the button for reassurance to staff the proper alert/event has been placed.

N. All Peripheral devices shall have the ability to be individually numbered to represent a separate and distinct location, even stations that are in the same daisy chain.

O. Peripheral devices shall be hot swappable and not require system shutdown or removal of power prior to replacement and no additional software programming.

P. Peripheral device pull cords shall be made of a non-contaminant material to reduce the spread of nosocomial infections. Pull cords made of cotton or other absorbent materials will not be accepted.

Q. Peripheral devices shall provide a cleaning mode to allow station surfaces to be cleaned without accidentally generating calls. Activating cleaning mode shall temporarily disable front panel buttons for a configurable period of time.

R. All Peripheral devices must be fully supervised.

S. The Pull Cord shall meet IP44 rating to be splash proof and suitable for use in wet areas such as bathrooms.

T. Pull Cord shall support up to 80 newtons of force before breakaway occurs.

5.3 Lavatory-Audio StationA. Lavatory Station with intercom capability shall provide duplex audio and mount to a

single gang back box.

B. Shall support a minimum of 3 unique alert/events on a single device (Assist, Emerg, Cancel, or Supplies for example)

C. Lavatory station shall have an IP44 rating to withstand environment.

D. Pull Cord shall support up to 80 newtons of force before breakaway occurs.

5.4 Bedside Module

A. Bedside module shall be field configurable to support a minimum of three (3) customizable buttons and receptacle for use of Pillow Speaker , Bed or Call Cord.


B. Bedside module shall have a magnetic connector with SafeConnect socket that can be used with all system Pillow Speaker/Handsets and call cords. Call assurance LED shall be supported on both Pillow Speaker and Call Cord.

C. Bedside module shall be able to activate any call event in system and system shall provide output for reassurance LED.

5.5 Customizable Module

A. Module is wall-mounted with a minimum of three (3) customizable buttons with matching color reassurance used to register staff presence in the room.

B. Module shall have option to add Speech Module for intercom functions.

C. Module shall support audible tones

5.6 Speech Module

A. System shall be capable of providing stand-alone speech modules connected to the active room bus that can be located at the headwall, in the ceiling, or in any area as needed.

B. Speech shall support duplex audio for two way speech between patients and staff.

C. System shall support multiple speech modules in the same room.

D. Speech module must contain a microphone and speaker.

E. Speech Module shall include LED indicating microphone and speaker activity. Speech module shall be able to produce dual tone audible notification.

5.7 Medical Device IntegrationA. Shall Support magnetic safe release plug from validated medical device. Staff shall be

able to disconnect devices without generating a cord out error. Unintentional disconnects must provide cord out alert.

B. Shall support the ability to receive and transmit medical device data via supervised, high-speed RS485 interface to a centralized medical device monitoring system.

C. Shall have RGB LED and indicate if the device if properly connected

D. Shall support connection of medical devices for automatic collection of vital signs and other relevant data to the EMR.

E. Shall support a minimum of 8 medical devices connected to a single bed/location.

F. Shall support visual display via touch screen in patient room indicating successful connection and provide status of connected equipment.

G. Shall support automatic identification of device type (Pump, Monitor, etc.) with association of the location/patient without the need for configuration by staff.


6 STAFF DEVICES

6.1 Staff Station

A. The Staff Station is an IP device with a color touch screen. Touch screen shall be a minimum of 7 inches and support 800 x 480 pixels.

B. The Staff Station shall accept PoE+ power via a UL1069 listed switch

C. The Staff Station shall have a highly durable scratch resistant screen (Gorilla glass or equal).

D. The Staff Station touch screen display shall support the ability to scroll, swipe and gesture for navigation and user interaction.

E. The Staff Station shall support a mico-SD card to store basic device configuration easy maintenance. Systems requiring programming for service replacements shall not be acceptable

F. The Staff Station shall support two-step credentialing. Credentialing must also be possible by pin code protection, third party RTLS location data. For EHR credentialing requirements, two (2) of the listed credentialing options can be deployed. Systems that cannot enforce proper credentials for EHR integrations shall not be acceptable.

G. The Staff Station shall support a minimum of ten (10) HTML5 web browser buttons per device. HTML5 web browser must provide access to supported tools to enable improved clinical workflow.

H. Staff Station must provide application to manage timing of routine tasks such as check skin, bathroom needs, nutrition, blood sugar, fluids, four P’s or other custom events. Notifications to remind responsible staff as to when tasks are to be completed and automated documentation of when completed must be included in the workflow solution.

I. Staff Station shall support speed dial capabilities to include room-to-room communication from a room/bed list, as well as ability to call any phone permitted by hospital PBX either by a dial pad or speed dial list. Speed dial list must provide a minimum of twenty-one (21) speed dial touchpoints.

J. Shall support Cleaning Mode to temporarily disable buttons to allow the device to be properly be sanitized without accidental activation of applications or alarms.

6.2 Staff Consoles

A. The Staff Console is a primary point of contact among users of the system. It operates as both a user interface and a communications device that sends and receives data and audio signals over the IP network.

B. As a user interface, the Staff Console alpha-numerically displays incoming calls from stations and connected healthcare equipment, and provides a means for the operator to prioritize and respond to selected events. As an audio device, it provides audible signaling functions and facilitates two-way full-duplex staff/patient and staff/staff communications.


C. The Staff Console shall provide visual identification of the calling station(s) including:

1. Room number 2. Bed identification3. Priority or event type4. Time of event5. Elapsed time (duration)6. Staff presence7. Pending service tasks associated with the room or bed

D. The Staff Console shall be IP-based, utilizing power over Ethernet (PoE) and Voice over IP technology.

E. The Staff Console shall support hot swappable replacement and shall not require reprogramming.

F. Staff Console audible annunciation shall indicate priority level. Incoming calls shall be displayed on the color display in the colors for their associated priority levels.

G. The Staff Console shall have a 7" capacitive touch backlit color LCD screen.

H. The Staff Console touch screen display shall support the ability to scroll, swipe and gesture for navigation and user interaction.

I. The touch screen shall utilize programmable soft keys as opposed to a mechanical dial/touchpad. Devices requiring hardened buttons to provide operation shall not be accepted.

J. Staff Console display shall provide an adjustable tilt mechanism for viewing clarity.

K. The Staff Console shall connect to the nurse call LAN/WAN utilizing CAT5/5e/6/7 cable and Power over Ethernet. No separate power supply or wiring shall be used.

L. The alert list screen on the Staff Console shall allow a minimum of five calls to be visible at a time and provide a simple scrolling function to view additional calls when more than five pending calls are present. Pending calls shall be displayed in priority order regardless of the order in which they are received.

M. The user shall have the ability to adjust the volume of the Staff Console incoming call tones.

N. The Staff Console shall support a “nighttime” mode which will automatically reduce the alert tone volumes when active.

O. The Staff Console shall support hands-free communication or the use of a handset to have better privacy for communication.

P. Facility shall be able to make available or remove selected functions/buttons from the Staff Console screens where selected functions are not to be used and to simplify operation. Functions/buttons that can be removed include Audio Page, Swing/Capture/Share and volume adjustments.

Q. Facility shall be able to make available or password protect selected functions/buttons from the Staff Console where functions are to be restricted to approved users. Functions/buttons that can be restricted include Audio Page, Swing/Capture/Share, Reminder Clear and volume adjustments.


R. The Staff Console shall support the ability to override full duplex mode to eliminate background noise at the nurse station while communicating with patient rooms.

S. The Staff Console shall be able to call any other audio device on the same nurse call network with two way duplex audio.

T. The Staff Console shall be programmable to receive and display selected call priorities from desired areas, or to delay selected calls for a programmable interval.

U. The Staff Console shall have the ability to adjust independent talk and listen volume levels via easy-to-use touchscreen controls. These settings shall be adjustable on a bed-by-bed basis. Systems using group or zone-wide audio adjustments shall not be accepted.

V. The Staff Console shall allow a user to create a service task identifying a patient’s specific request.

W. A service task shall allow a choice of up to three user-specified levels of staff which can be associated with the task.

X. The Staff Console shall provide for up to 21 user-specified service request soft keys.

Y. The Staff Console shall allow up to three simultaneous services to be selected for a single service task.

Z. A service task shall illuminate the dome light with the appropriate level of staff response required (e.g. Red=nurse, Amber=Nurse Assistant, Green=Aide) at the location where the service will be delivered.

AA. A service task shall be able to be created without requiring an audio connection to the location.

BB.The Staff Console shall display service tasks created from mobile devices.

CC.The Staff Console shall display service task status, identifying those that have been accepted by a mobile device.

DD. The staff console shall display a timeout when the user has exceeded a specified time and identify the task as overdue.

EE. The staff console shall display overdue tasks.

FF. The Staff Console shall interact with supplemental (PC) display.

6.3 IP Annunciator

A. IP Annunciator features shall be identical in operation to the Staff Console (Section 6.2) with the exception that it will be wall-mounted.

B. The IP Annunciator will have an optional Pillow Speaker/Handset to support private conversations between patients and staff.


7 CORRIDOR DEVICES

7.1 Dome Lights

A. Dome and zone lights provide bright, easy-to-see visual annunciation that speeds response time and increases caregiver efficiency. These devices are typically installed in corridors and outside patient rooms to provide staff with a visual indication as to the origin of a call placed on the system.

B. Dome lights operate in a similar fashion to annunciator panels or staff consoles: the light color and flash rate indicates the type and priority of the call.

C. Each Dome Light shall utilize Light Emitting Diodes (LED) for displaying colors. Dome Lights utilizing incandescent bulbs shall not be accepted.

D. Dome and Zone Lights shall be available in two, or four sections. E. Dome light shall have a status LED for maintenance purposes.F. Dome lights shall have two general purpose inputs. G. To maintain aesthetics, reduce obstruction, and limit risk of damage to devices, the

maximum size of each Dome Light shall not be greater than 5 inches in height, nor shall it protrude more than 3.5" from the mounted surface.

H. Each Dome Light section shall be capable of indicating in excess of eight facility-selected configurable colors. Dome Lights requiring more than four sections to provide these colors shall not be acceptable.

I. To allow for maximum flexibility, the Dome Light shall be configurable via programming to allow multiple sections of a single light to illuminate and/or flash the same color for higher priority calls.

J. Dome Lights shall be able to match existing Dome Light schemes via programming. Systems with dome light schemes that are not able to match existing systems will not be accepted.

K. Any dome lights requiring the replacement of filter caps or lenses to obtain facility-requested dome light colors for any priority shall not be accepted.

L. Dome Light shall be supervised and provide a diagnostic indication of room status to prevent maintenance personnel from disrupting patients.

M. Dome Light shall be capable of providing power to location infrared beacon for used for integrated automated staff presence.

8 CONTROL DEVICES

All control devices shall be IP-based, utilizing IP Switches and gateways for connection to room devices. These devices shall make up the Nurse Call LAN/WAN.

8.1 IP Gateway

A. IP Gateways shall be IP-based and provide power and data to room devices.

B. IP Gateways shall mount in a standard 19" rack to be shared with the facility's IT equipment or shall mount in an independent rack.

C. IP Gateways shall have internal power supplies to support all peripheral devices. Systems using a proprietary enclosure/card cage for central equipment and/or requiring power supplies apart from the control equipment shall not be accepted.

D. IP Gateways shall be solid state, fan-less design for high reliability.

E. IP Gateways shall provide up to two voice paths for voice communications.

F. IP Gateways shall support up to 80 dome lights and passive bus concentrator.


8.2 Passive Bus Concentrator (PBC)

A. The PBC is the interface between the network and the peripheral devices. It has eight individually addressed passive room buses.

B. PBC shall support up to eight rooms utilizing passive devices. C. PBC shall use low power (5.5v) for reduced operating cost.

9 INTEGRATION

9.1 Integration SoftwareA. The integration platform MUST be compatible with other Nurse Call Systems offered by

the selected vendor to allow migration options to other Systems. A Manufacturer whose interface platform cannot be shared with other Systems shall not be accepted.

B. The system shall support industry standard protocol output to interface to 3rd party middleware platforms.

C. The system shall support downloadable software for updates or new installations. Systems requiring hard media (e.g. CD, DVD, etc.) to be used shall not be accepted.

9.2 EMR/EHR Integration

A. The System shall allow automatic monitoring of the facility's HL7 Admit, Discharge & Transfer (ADT) transactions, and shall parse selected patient demographic fields into the Nurse Call System's database. This data shall be made available to assignments, messaging, mobile phones, and reporting applications.

B. Patient precautions from the ADT interface shall be displayed on supplemental PC displays

9.3 Automatic/Manual MessagingA. The System shall allow text messages to be sent to wireless devices from a messaging

browser. Login to the browser shall be password protected.

B. The messaging software shall allow the user to send a message to a staff wireless device by selecting either the staff name or device number.

C. The messaging software shall provide feedback to indicate that the wireless system has received the message. Systems that do not provide acknowledgment of sent messages shall not be accepted.

D. The messaging software shall be browser-based, allowing users to send messages from any networked PC with Internet Explorer 10.0 or newer. Systems that require a dedicated PC or special software loaded onto individual PCs to provide messaging access shall not be accepted

9.4 Staff Assignments

A. Staff assignment software to assign staff to wireless devices and staff to beds shall be accessible via PC-based software.

B. The staff assignment screens shall be password protected. The login password shall determine the staff, beds and wireless devices available to the operator.

C. Unoccupied beds shall be flagged or indicated informing user that assignments are not completed or required (with EHR integration).

D. Staff assignment software, with integration to the EHR, shall allow the user to optionally view the patient name, age and sex for each bed.


E. The staff assignment software shall allow for shifts to be created ahead of time and saved so that they can be reused.

F. The staff assignment software shall provide active help to guide the user through the process (without opening a separate help screen). Help screens shall also be available for more detail instructions.

G. The staff assignment software shall provide the ability to manage float staff. The user shall be able to reassign staff that work in various locations throughout the hospital from one unit to another without entering the staff names into multiple databases.

H. The staff assignment software must allow shift assignments to be completed from any networked computer in the facility. Systems requiring a dedicated PC for completion of staff assignments shall not be accepted.

I. Staff assignments shall allow assignment of multiple brand nurse call systems and other 3rd party medical devices such as monitors.

J. Staff assignment software shall allow unique assignments or call escalations based on event type or system generating the event.

K. Staff Assignments must be available in two formats, Event based by assigning Primary Secondary and tertiary levels of staff to each location or a Role based option where events are routed only to the apocopate staff type. For example, an event requiring a RN will be sent to a RN only. If escalation is required the event would escalate to another RN. Role based assignments must provide a minimum of two levels of escalation for a minimum of 6 levels of staff.

L. Staff assignment software shall allow assignments to be automatically or manually activated at a designated start time.

9.5 Wireless Telephone Integration

A. The Nurse Call System shall allow connection to any brand of in-house wireless telephone system including wireless IP systems. This integration shall allow calls from patients to automatically ring the wireless device of the assigned caregiver(s). The wireless device must show the caregiver the bed number of the call, the call type/priority, and optionally either the unit name or the patient name (with presence of ADT interface).

B. The wireless telephone integration shall allow no less than three levels of staff, plus a charge nurse and a "group," to be assigned to each patient/bed or call priority. These assignments shall be performed via the client-based assignments software. The rollover time from the primary staff member to the secondary, tertiary, and charge nurse shall be definable by the facility.

C. A call escalation manager shall manage automatic messaging to wireless devices. The call escalation manager shall also provide group page functions that allow any defined group of devices to receive any selected call type(s). When a call is sent to a group, the call escalation manager shall also provide the ability to transmit a "call cancel" in the event of a call being attended to; remaining staff not yet on-site can be notified that the situation has been attended to.

D. System shall be capable of integrating to <Ascom UNITE> <Polycom> <Spectralink> <Vocera> <Cisco> wireless devices without the need for additional third party software.

E. The wireless integration shall allow device failures in the Nurse Call System to generate an automatic call directly to a Biomed device.

F. The Wireless integration shall not require facility to disable functions of the wireless phones including voice mail.

G. The wireless integration shall allow service tasks to be created from mobile devices.


H. When integrated with Ascom Unite, the Nurse Call System shall support the ability to upgrade nurse call events and generate service task events with identification of patients need from wireless phones.

9.6 Reporting (Logging)

A. A server computer running Microsoft SQL Server and a reporting application shall reside on the hospital's network to monitor all nurse call activity and log events into the SQL database. Reporting applications that do not utilize Microsoft SQL Server shall not be acceptable. The nurse call events shall be retrievable in the form of user-defined reports. The reporting database must provide flexibility to generate reports for facility wide efficiency studies, unit performance statistics, incident report/details, and system performance/device failures.

B. Staff members shall be able to generate and view reports from any networked PC with Internet Explorer 10.0. Systems requiring staff members to go to a dedicated PC to generate or review reports, or requiring special software applications such as GoToMyPC to be loaded on PCs to provide report access, shall not be accepted.

C. The reporting database shall not limit the number of user logins or simultaneous users generating or viewing reports. Systems that only allow a limited number of users to generate or view reports at a time shall be considered unacceptable.

D. Staff shall gain access to the reporting package via a login name and password. Each staff member's password shall determine which areas within the facility the staff member can include in his or her reports.

E. The reporting system must be capable of automatically generating scheduled reports. When the report is generated, a hyperlink shall be emailed to predetermined recipients. The recipient may click on the hyperlink and log in to view the report. This is applicable to PC’s on the hospital intranet with appropriate access in order to secure the data.

F. Scheduled reports shall be user selectable to be sent in any of the following formats: Excel, CSV, PDF, HTML, Crystal Report File, RTF, .tab, .txt, MS Word, XML. Reports packages not supporting multiple formats shall not be accepted

G. The reporting system shall allow report templates to be defined and saved for access at a later date.

H. Reports shall be organized by the user to include and sort data by any or all the following categories:

1. Time and Date

2. Shift-Range 3. Room/Bed Number4. Area Name5. Call Priority6. Event7. Staff Level8. Patient Name

I. Dependent on the user's report selections, a generated report shall include a statistical summary of the maximum and average times for the following event pairs at each priority level:

1. Place/Answer-The interval between the time a call is placed to the Staff Console and the time the Staff Console answers the call.

2. Place/Clear-The interval between the time a call is placed to the Staff Console and the time a staff member makes the first response by answering from the Staff Console, pressing the presence set button at the originating station, or pressing the CANCEL button at the originating station.

3. Place/Cancel-The interval between the time a call is placed to the Staff Console and the time it takes for a staff member to disconnect the call at the Staff Console (unless


the reminder feature is activated), press the CANCEL button at the originating station, or press the presence clear button at the originating station.

4. Connect/Disconnect-The interval between the time a Staff Console either originates or answers a call and the time the Staff Console ends the call.

5. Reminder Set/Reminder Clear-The interval between the time the reminder feature is activated for a particular room/bed number and the time the reminder feature is canceled.

6. Presence Set/Presence Clear, the interval between the time the presence feature is activated at a station and the time the presence feature is canceled, with associated call/event.

7. The reporting system shall then take the Place/Answer, Place/Clear, Place/Cancel, and Reminder Set/Reminder Clear statistical summaries and display them in the report as a percentage in comparison to target rates determined by the administration. A percentage between 0 and 99 indicates that the staff's response time did not meet the standards set by the author of the report or the administrator of the system.

J. The reporting system shall allow each area of the facility to set target response times for each of the call priorities. Various types of exception reports shall be available to provide information about calls that were not handled within the department's target time. Systems with reporting packages that do not allow each area to set target times or to create exception reports shall not be accepted.

K. Reports shall be capable to show Tasks to illustrate trends on patient requests and delivery time of the requests. Data on what level of staff are assigned to patient requests shall also be provided.

L. Where RTLS is integrated or automated staff presence, reports shall illustrate time spent with patient, by staff member.

M. The reporting system shall record system failure signals, thereby allowing maintenance personnel to generate reports relating to system reliability and service response times.

N. Where supported, wireless phone integration (if present), shall provide the Nurse Call system an ‘acknowledgement’ of events sent to the wireless interface to be recorded in the reporting system providing historical data on the success of events being automatically routed to caregivers wireless devices.

9.7 List View Software

A. View Client Software shall be available to provide a view of each nursing unit via login to supplement the Staff Console. This client shall display the following information:

1. Pending calls2. Active Service Tasks3. Reminder reason 4. Staff Location (automated with presence of IR Locate)5. Patient record data (manually or automatically with presence of ADT Interface)6. Patient precautions (indicated by icon and text)

a. Fall risk

b. NPO (Food and fluid shall be withheld for various reasons, e.g. pre-op)c. IV (IV Pump assigned)d. I/O (Monitoring of fluid input/output required)e. Touch (Patient may be diabetic and uses a device for monitoring blood sugar or

glucose levels)f. Isolationg. NINP (No Info No Publication)h. Allergy

7. Activity history per patient/bed including:a. Calls


b. Audio connection to room

c. Service Tasks

d. Text messages (automatic and manual)

e. Staff Arrivals

B. In addition, the List View Client shall optionally display the following information when integrated with ADT. 1. Admitted location2. Patient ID3. Patient name 4. Date of birth (Age)5. Sex6. Doctor (attending doctor)7. Status (routine, priority, urgent)8. Patient precautions9. Free-text information

C. Staff presence icons shall be configurable to match staff level/type. Up to nine colors/levels shall be available.

D. The List View Client shall allow user to expand events to show additional information including: event history, patient demographics (with ADT/EHR integration) and room summary for the first call on the pending calls list.

E. The List View Clients shall be password protected. The login password shall determine the units visible and view preferences for each client.

F. Each List View login shall be capable of having a unique task reason and messaging list. Systems requiring all users to share the same remind and messaging list shall not be accepted.

G. List View Client's event notification colors shall be configurable to match Dome Light settings.

H. The List View Client shall be capable of messaging a caregiver (one of three levels assigned or any active staff member) from the List View screen.

I. List View Clients shall be capable of ‘filtering’ call activity based on call priority and/or what nursing unit the event was generated. Font size and color shall also be configurable. These features shall allow List View Clients to have the flexibility serve as system wide Supplemental Code Blue Display(s) and departmental status screens to allow LCD’s or Plasmas to be used as an option to marquee displays.

J. List view client shall interact with associated Staff Console to provide a view of events which reflect the same topology and coverage areas as presented on the associated Staff Console.

9.8 Mobile Applications

A. Mobile Applications for Smart Devices shall allow patient information and alerts to be delivered to a smart device utilizing robust, standards-based security and message encryption.

B. All message alerts shall be encrypted end-to-end so data remains secure. C. The application shall support failover via SMS/SMTP to the same device or another device in

the event carrier data network coverage is not available.


D. Software Requirements

1. Mobile Applications for Smart Devices shall supports iOS devices with OS versions 9.x/10.x

2. Mobile Applications for Smart Devices shall support Android devices with OS version 4.1 to 5.x.

9.9 RTLS

A. The Nurse Call System shall allow connection to a third party Real Time Locate System (RTLS). The Locating “network” shall be an optional infrastructure integrated to Nurse Call via a software connection.

B. Current Vendors are:

1. Ascom MYCO

2. AeroScout (Stanley Healthcare)3. Awarepoint4. Centrak5. Versus6. Sonitor

E. RTLS, when integrated to Nurse Call, shall be configurable to provide the following functionality when staff wearing a RTLS device enters a room:

1. A pending patient normal call shall be canceled and all associated LED’s and signals shall be extinguished, if a Staff Console or Wireless Phone has not previously answered the call.

2. A pending reminder shall be cancelled and all associated LED’s and signals shall be extinguished if the appropriate level of staff has entered the room for the given reminder level.

3. The matching colored section of the dome light, as assigned to the RTLS device of the staff member entering the room, shall steadily illuminate to indicate staff presence.

4. The Status LED on the Patient Stations shall steadily illuminate while staff is in the room.

5. While staff is registered in a patient room a double press of the call button on the bed rail, bedside Pillow Speaker/Handset or call cord shall generate a Staff Emergency call, providing staff and patients an additional level of safety.

6. View Clients shall indicate staff locations7. Events from RTLS system such as button press on RTLS badge shall have ability to

annunciate the event in the Nurse Call system via dome light at the room/location of the event and on Staff Consoles

F. The Management Reporting software (if present) shall record all events of staff entering and exiting patient rooms. This data shall be available to draw reports showing identification of staff entering patient rooms; time stamped and indicates duration with the patient when associated to a call.

G. The RTLS shall be capable of supporting Equipment Tracking. Equipment tags shall be configurable providing the nurse call system the option to display device locations on the dome lights.


Documents

Telligence 6.0 Guideline Specification · Web viewGuideline Specification. Patient Response System, Telligence v6.1. Rev .04 8 March 2019. Foreword. If you have a standard IBM-compatible