Cisco HealthPresence 2.5 Release Notes

Transcription

1 Version 2.5 November 8, 2012, Contents This release notes address the following subjects: Overview Important Safety Information New Features System Requirements Compatible Video Components Interoperable Medical Devices Installing and Upgrading to a New Software Release Open Issues and Known Limitations Resolved Issues and Limitations in Previous Versions Service and Support Related Documentation Overview Cisco HealthPresence 2.5 is a software-defined platform 1 that facilitates collaboration among healthcare professionals in a telehealth environment. 1. Cisco HealthPresence Software is listed with the U.S. Food and Drug Administration as a Class I, 510k exempt medical device pursuant to the Medical Device Data System rule (see 21 CFR ) and as a medical device with other governmental agencies in other jurisdictions. Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA

2 Overview Cisco HealthPresence Software is comprised of the following: Cisco HealthPresence Connect Server software, which manages all of the connectivity among the video conferencing components and the telemetry sessions among Endpoint Computers and provides the user interface to the Providers and Attendants. Cisco HealthPresence Connect Endpoint software, which provides access to the Cisco HealthPresence portal and enables the device aggregation software to communicate with the Cisco HealthPresence Connect Server. "Medical Device Aggregation software (which ships as part of the Cisco HealthPresence Connect Endpoint software), which interfaces to the medical devices. Cisco HealthPresence Software provides the following features: Cisco HealthPresence 2.5 facilitates high definition video conferencing and collaboration. Cisco HealthPresence 2.5 also allows optional integration with compatible workflow and productivity tools, including Electronic Medical Records systems, directory services and medical practice applications that address items such as scheduling, billing and appointment reminders. Important Safety Information Cisco HealthPresence is intended to allow healthcare providers to evaluate patients remotely or patients and healthcare providers to collaborate with specialists remotely. Cisco HealthPresence is not intended for use in emergency situations. In the event of an emergency call 911 or your local emergency response system. Cisco HealthPresence is not for use in situations involving real-time patient monitoring or alarming. For further important information, refer to the Cisco HealthPresence 2.5 Instructions For Use, which can be found at: Related Definitions Cisco Appliance The PC sold by Cisco that is preinstalled with the Cisco HealthPresence Connect Software. Endpoint Computer The Laptop, PC, or Cisco Appliance running the Cisco HealthPresence Connect Endpoint Software. Interoperable Medical Devices The third-party medical devices that have been tested for technical compatibility with Cisco HealthPresence 2.5 by Cisco, as identified in the Interoperable Third Party Medical Device List which can be found at: 2

3 Architectual Overview Architectual Overview Behind the scenes, Cisco HealthPresence supports a number of video components and other Cisco HealthPresence components that pull the solution together. The architectural overview of Cisco HealthPresence Version 2.5 is illustrated in Figure 1. Figure 1 Architecture of Cisco HealthPresence Release 2.5 New Features Cisco HealthPresence Version 2.5 is an incremental version and builds on the features provided by Cisco HealthPresence Version 2.1. New features in Cisco HealthPresence Version 2.5 include the following: Cisco Health Presence as a software solution Cisco HealthPresence is a Clinical integration software platform that brings together workflow, device integrations, clinical applications and Cisco video collaboration to enable care at a distance, healthcare education, continuity of care and effective management of healthcare resources. Cisco HealthPresence is truly a software solution - resides on top of OS layer There are no specific direct hardware dependencies All interactions are through interfaces/standards Interface with external hardware 3

4 New Features Warning Third-party software applications must be tested and verified as compatible by Cisco before being used with Cisco HealthPresence. The Cisco HealthPresence software will interface with external components using standard interfaces, standards and protocols. Figure 2 Cisco HealthPresence Interface diagram. Cisco HealthPresence 2.5 receives information from compatible third party medical devices that are used with a patient and transmits it to a provider in a different physical location. Third party medical devices that are compatible with Cisco HealthPresence 2.5 include: Devices 1 using: Driverless USB with UVC S-video RCA Interoperable 3rd party medical devices as described in the Interoperable Third Party Medical Device List, awhich can be found at: ml. Cisco HealthPresence can work with any video endpoints as long it passes the test plan that outlines the interface that will be supported. The protocols supported include SIP and H323. The video endpoint capabilities will determine the level of integration with Cisco HealthPresence for One Click Join/Leave. Any video endpoints that do not support APIs will need to conduct call initiation and termination on a manual basis. Support for endpoint install on a generic laptop or desktop. Details include: To provide end users the option to use their preferred laptop/desktop devices, Cisco HealthPresence will support endpoint software on a laptop as well as a desktop. A software disk will be made available for install. The non-hardened model will be used to avoid any settings change in the customer's laptop. Endpoint installer improvements. These include: Endpoint installer changes to support dynamic IP address. The site installer will install a new scheduled task Cisco HealthPresence Sync IP that runs once every minute. This decision is based on the endpoint type. 1. Third Party medical devices using S-Video or RCA may have other hardware requirements, such as a Grabee(TM) dongle. 4

5 System Requirements Reduced installer footprint. In Cisco HealthPresence 2.1, the endpoint installer bundled some dependent software to handle offline installations for the Windows XP platform. The support for Windows XP has been removed for this release. As a result, the base installer no longer includes Microsoft DotNet Framework and Internet Explorer installers. AMD software upgrade. Cisco HealthPresence 2.5 release will support AMD 3.0 including support of the following specific features: Dynamic IP address support for video and audio streaming. To support dynamic IP address at the attendant/provider side, the GetDeviceInfo API exposed by AMD will now expect a new parameter called _ip holding the value of the endpoint's current IP address. This will be used by the AMD software to generate appropriate Audio and Video URLs. Once the IP address changes, the user has to start and stop the Audio/Video stream for the devices to work properly. AMD VLC audio parameters. Cisco HealthPresence 2.5 will support and send the following parameters that AMD VLC takes in to boost the audio signal. loudness-level - This is the loudness boost required. (0 = disabled, 1-20 indicate a boost). Cisco HealthPresence 2.5 sets the value of this parameter at 5, as recommended by AMD. loudness-type - This is the required loudness filter. Currently, AMD VLC expects a hard-coded value of limiter. 3M Littmann Stethoscope support. Cisco HealthPresence 2.5 supports the 3M Littmann model 3200 stethoscope as an interoperable medical device for general availability used with AMD. System Requirements Components Not Supported Note that the following are not supported for Cisco HealthPresence 2.5: Microsoft Windows XP Cisco Unified Video Conferencing Unit Cisco Unified IP Phone 7985G The Neurosynaptic ReMeDi Medical Data Acquisition Unit (MDAU) will not be supported in the Cisco HealthPresence ver Cisco HealthPresence Endpoint Computer The specification for the laptop/desktop used as an endpoint computer are as follows: Processor: Minimum 2.6 GHz dual core processor Graphics: Minimum 1 GB RAM with DVI/HDMI output and display of at least 1280 x1024 Memory: Minimum 4 GB RAM Hard Disk: Minimum 150 GB HDD Audio Card: Onboard HD Audio Codec with Line/Mic in Operating System: Windows 7 profession 64-bit (service pack 1) USB Ports: Sufficient number of USB ports for connecting medical devices NIC: Onboard Gigabit Ethernet 5

6 Supported Video Components Optical Drive: DVD ± R Cisco HealthPresence Connect Server Cisco HealthPresence Connect Server runs on the following platform: Enterprise Server Red Hat Enterprise Linux 5.7 compatible or later Processor: Two (2) multi-threaded four (4) core 2.4GHz CPUs with 12MB cache Minimum Hard Drive: 100GB SATA/SSD/SAS Minimum Memory: 16GB DDR3, 1333 MHz Network Interface Card: Quad Port 10/100/1Gb Optical Drive DVD±R RAID support optional Supported Video Components Video Conferencing Data Center Components Cisco HealthPresence has been validated with a variety of Unified Communication Servers and multipoint bridges that typically reside in a data center. Unified Communication Servers Multi-point Control Units Cisco HealthPresence V2.5 has been validated with the following Unified Communication servers: Cisco Unified Communication Manager (CUCM) Cisco TelePresence Video Communications Manager (VCS) (Both Control and Expressway) TelePresence Management Suite (may be required when using Cisco Jabber Video for TelePresence) Cisco HealthPresence V2.5 has been validated with additional multi-point control units (MCUs). These MCUs are used for multipoint calls or calls that require interoperability. They are configured as a meeting resource to Cisco HealthPresence. The the following multipoint control units 1 can now be used with Cisco HealthPresence: Cisco Unified Communication Manager (CUCM) Servers Cisco TelePresence Video Communication Server (VCS) Cisco TelePresence Multipoint Switch (CTMS) Solutions using Cisco TelePresence-only endpoints can use the CTMS. 1. Cisco HealthPresence V2.0 supported the Cisco Unified Video Conferencing Unit (CUVC). In V2.5, CUVC is no longer supported. 6

7 Interoperable Medical Devices Cisco TelePresence Media Services Engine (MSE) 8000, Cisco TelePresence Server MSE 8710 and the Cisco TelePresence MCU MSE combine to provide a high-capacity voice and video conferencing media services engine that supports conference bridging, interoperability, gateway, management and recording functions. Cisco TelePresence 4500 Series Multipoint Control Units (MCUs) solutions using only non-cts-500 video endpoints can use the 4500 Series MCUs. Video Endpoint Components The following video endpoints have been validated to work with Cisco HealthPresence: Cisco TelePresence Codec C20/C40 Cisco TelePresence System EX60/EX90 Cisco Jabber Video for TelePresence Legacy video endpoints are video endpoints that are validated but can no longer be purchased from Cisco. Legacy video endpoints can be used with Cisco HealthPresence if they are currently being used with a prior version of Cisco HealthPresence and the site is upgrading. Legacy video endpoints include the following: Cisco TelePresence System 500 (CTS 500) (with a 37 inch display) Cisco TelePresence Edge 95 MXP Cisco IP Communicator Note With the exception of Jabber Video, all validated video endpoints are fully integrated. That is, the telepresence video conference is started by clicking on the Join button and ended by clicking on the Leave button. With Jabber Video, Join starts the video conference, but the Attendant or Provider must use Jabber video controls to end the telepresence video conference. Interoperable Medical Devices Cisco has validated certain third party medical devices (the Interoperable Medical Devices ) as interoperable with Cisco HealthPresence. Interoperable Medical Devices should be used according to the instructions for use prepared by the manufacturers of those Interoperable Medical Devices. See the Interoperable Medical Devices List. This document can be found at: Note Interoperable Medical Devices are available only from the manufacturer of such devices or its authorized resellers and distributors. Cisco is not a reseller or distributor of such devices. Interoperable Medical Devices are not available in all countries. To find out if the Interoperable Medical Devices are available in your country, contact the manufacturer or the seller of the Interoperable Medical Device. 7

8 Installing and Upgrading to a New Software Version Installing and Upgrading to a New Software Version Refer to the Cisco HealthPresence 2.5 Connect Server Installation and Administration Guide for instructions on installing software for the Cisco HealthPresence Connect Server. It also provides instructions on updgrading existing 2.1 installations. Cisco HealthPresence 2.0 installations will first require an upgrade to Cisco HealthPresence 2.1. For instructions on installing software on Cisco HealthPresence Endpoints, refer to the Cisco HealthPresence 2.5 Endpoint Installation Guide. Both documents can be found at: Note The Cisco HealthPresence 2.5 software is available on CD. When copying the Endpoint software to the Connect Server for later use, verify that you have the correct install files, note that the Base Installer and Site Installer executables have the following MD5 checksums and version numbers: e4300e6480f82e37fb78d84787fce849 CHP_Connect_Endpoint_Base_Installer_ exe 04f943e113845f02dc73bbebd0b52fd5 CHP_Connect_Endpoint_Site_Installer_ exe Issues and Known Limitations Table 1 below explains the issues and known limitations of Cisco HealthPresence Version 2.5. Table 1 Open Issues and Workarounds Bug ID Headline Explanation / Workaround CSCua97857 Re-joining an ended call from Jabber video gives error. 1. Join a call from Jabber video from an appointment. 2. End the call manually from Jabber video window. 3. Click join again from Cisco HealthPresence. The Cisco Appliance displays a system error. This is because Cisco HealthPresence has no control over ending the conference and the only way to end the conference session in Cisco HealthPresence is to exit the appointment. Call can be re-joined after re-entering the appointment and clicking join. CSCub71438 Under certain high stress load conditions the total count of end user licenses used shows more than the number of end user licenses actually used. This issue is only observed under very heavy loads. This issue is resolved by restarting Cisco HealthPresence Services on the Connect Server. CSCua03605 Powering off the 3M stethoscope while it s streaming will cause it to disassociate the Bluetooth pairing and needs to re-paired before it can be used. For re-pairing instructions, see the Cisco HealthPresence 2.5 Instructions For Use at: ts_user_guide_list.html. 8

9 Resolved Issues and Limitations in Previous Versions Resolved Issues and Limitations in Previous Versions Table 2 lists resolved issues and limitations in previous versions of Cisco Healthpresence. Table 2 Resolved Issues Bug ID CSCtw65175 CSCty19434 CSCua05478 CSCtz91688 CSCty85802 CSCub05440 CSCtz91699 CSCtx89152 Headline Telemetry video streaming dropped frames. Exam camera low resolution not 512 Kbits of bandwidth. 3M Littmann Stethoscope Issue. Partner site instability can severely degrade the Cisco HealthPresence experience. Unable to access CHPCS via NAT'd IP. Telepresence Join fails if video endpoint access password is null. Using hostnames for portal servers causes IE to freeze when started. Multiple Vitals readings does not get updated on Oneplace Portal Update the Vitals to Onpleace Portal on first login. After an intitial successful update, the Portal does not show recent vitals after 2 or 3 updates. Service and Support For a complete description of the service and support offered for Cisco HealthPresence V2.5, refer to the Cisco HealthPresence Solution Design Guide. Related Documentation All related documentation can be found at 9

10 Related Documentation 10