Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
HeartStart MRx Service Library Implementation Guide Data Transmission HeartStart M Rx to HeartStart Telemedicine and Data Messenger Notice About This Edition: Manufacturer: Edition 3 Printed in the USA. Publication number 453564058751 The information in this document applies to the product versions indicated below. This information is subject to change without notice. Philips shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Philips Medical Systems 3000 Minuteman Road Andover, MA USA 01810-1099 (978) 687-1501 Edition History: Pub. Number Philips Medizin Systeme Böblingen GmbH Hewlett Packard Str. 2 71034 Böblingen, Germany Canada EMC: ICES-001 Ed. HeartStart Product Name MRx Version and Version 1 B2/B.04 2 B1/B.05 3 B1/B.05 4 B1/B.05 1 453564058751 2 3 T.0 M3536-90900 Authorized EU representative: Print Date U.S. FCC and Industry Canada Radio Compliance: Contains FCC ID: PQC-WMTS-MODULE 2.2 Feb., 2005 2.2 Oct., 2005 FCC ID: PI4TDKB2IPC 2.5 Dec., 2005 NCC ID: CCAI12LP1010T6 2.8 Apr., 2007 9.0 3.0 Feb., 2008 F.0 HeartStart 4.0 Telemedicine 4.2 System Jan., 2010 Operation of this equipment requires the prior coordination with a frequency coordinator designated by the FCC for the Wireless Medical Telemetry Service. This device complies with Part 15 of the FCC rules and RSS-210 of Industry Canada. Operation is subject to the following conditions: 12-Lead Transfer Station Mar., 2013 Copyright: Copyright © 2013 Koninklijke Philips Electronics N.V. All rights are reserved. Permission is granted to copy and distribute this document for your organization’s internal educational use. Reproduction and/or distribution outside your organization in whole or in part is prohibited without the prior written consent of the copyright holder. Use of supplies or accessories other than those recommended by Philips may compromise product performance. Trademarks: HeartStart MRx contains an Ezurio PC Card with Bluetooth® wireless technology. The Bluetooth wordmark and logos are owned by the Bluetooth SIG, Inc. and any use of such marks by Ezurio is under license. HeartStart MRx Monitor/Defibrillator, HeartStart Telemedicine System, and the HeartStart logo are either registered trademarks or trademarks of Koninklijke Philips Electronics N.V. DatamedFT® is a registered trademark of Engineering Solutions, Inc. ESO Solutions™ is a trademark of ESO Solutions, Inc. Microsoft®, Windows®, .NET Framework®, Outlook®, and Internet Explorer® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. onBoard™ Mobile Gateway is a trademark of In Motion Technology. PDF® is a registered trademark of Adobe Systems, Inc. Rosetta-Lt™ is a trademark of General Devices. Wireshark® is a registered trademarks of the Wireshark Foundation. Other trademarks and trade names are those of their respective owners. Medical Device Directive: The HeartStart MRx complies with the requirements of the Medical Device Directive 93/42/EEC and carries the 0123 mark accordingly. • This device may not cause harmful interference. • This device must accept any interference received, including interference that may cause undesired operation. Any changes or modifications to this equipment not expressly approved by Philips Medical Systems may cause harmful radio frequency interference and void your authority to operate this equipment. Declaration of Conformity: For the Declaration of Conformity Statement, please see the Philips Healthcare web site at http://incenter.medical.philips.com/PMSPublic. Scroll over the Quality and Regulatory tab located in the upper left corner of the window. Click to see the Regulatory by Business. Then click to select Defibrillators and select the entry for Declaration of Conformity (DoC). Chemical Content: REACH requires Philips Healthcare to provide chemical content information for Substances of Very High Concern (SVHC) if they are present above 0.1% of the product weight. Components of/within electric and electronic equipment may contain phthalates above the threshold (e.g. bis(2-ethyl(hexyl)phthalate), CAS nr.: 117-81-7). The REACH SVHC list is updated on a regular basis. Therefore, please refer to the following Philips REACH website for the most up-to-date information on products containing SVHC above the threshold: http://www.philips.com/about/sustainability/reach.page Warning: Radio frequency (RF) interference coming from devices other than the HeartStart MRx may degrade the performance of the HeartStart MRx. Electromagnetic compatibility with surrounding devices should be assessed prior to using the monitor/defibrillator. Use of supplies or accessories other than those recommended by Philips may compromise product performance. i Conventions Used in This Manual This guide contains the following conventions: WARNING: Warning statements describe conditions or actions that can result in personal injury or loss of life. CAUTION: Caution statements describe conditions or actions that can result in damage to the equipment or loss of data. NOTE: Notes contain additional information on usage. TIP: Tips provide hands-on insight into using and servicing this product. The “bull’s eye” icon indicates a process or a procedure (a set of steps to achieve a certain goal) Message and GUI Text represents messages that appear on the HeartStart MRx screen and soft key labels that appear on the screen above or below the button to which they correspond, or messages that appear on the computer screen and GUI actions to navigate the computer software. On-line Viewing Only: Hypertext represents hypertext links, which will display as blue; click on the blue link to go to that destination. The “mouse” icon indicates a hypertext link. Ignore in printed copies. Abbreviations Full Name Abbreviation HeartStart 12-Lead Transfer Station 3rd Generation Cellular Data Transmission Access Point Name Batch LAN Data Transfer Bluetooth® wireless technology, cell phone, modem, or receiving Telemedicine Server PC Datamed Format Translators Domain Name Server Dial Up Networking electronic Patient Care Record HeartStart Telemedicine System HeartStart MRx Monitor/Defibrillator device Internet Information Services Microsoft Windows® operating system Periodic Clinical Data Transmission Subscriber Information Module (card) Service Set Identifier TraceMasterVue Wireless Encryption Protocol 802.11 Wireless Fidelity (Wireless Networking) Wireless Link 802.11 WiFi Protected Access – Pre Shared Key 802.11 WiFi Protected Access 2 – Pre Shared Key 12-Lead Transfer Station 3G APN BLDT Bluetooth device DatamedFT DNS DUN ePCR HeartStart Telemedicine HeartStart MRx, device IIS MS Windows, the Windows PCDT SIM, SIM card SSID TraceMaster WEP WiFi WL WPA-PSK WPA2-PSK ii Contents Chapter 1 Overview . . Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 2 3 Understanding the Transmission Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 5 6 6 . . . . . . . . . . . . . . . . 7 Using HeartStart MRx with Data Messenger . . . . . . . . . . . . . . . . 7 Audience . . . . Tasks and Skill Levels . Data Transmission Stages . . . . . . . . . . . . 1 Understanding the Wireless Link . . . Understanding 12-Lead Transmission Process Understanding the PCDT Process . . . Understanding HeartStart Telemedicine . Chapter 2 Overview . . Planning Your Solution High Level Planning . . Questions for Consideration Prerequisites . . . . . . . . . . . . Data Transmission Solutions . . . . . . 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 10 11 . . . . Bluetooth Transmission Setup Overview. Other Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 11 15 15 16 . Wireless Link Transmission Setup . Wireless Link Data Flow Scenarios . 12-Lead Transmission Scenarios . Chapter 3 Overview . . Setup and Configuration . . . . . . . . . 17 . Introduction to the HeartStart Telemedicine System . The HeartStart Telemedicine Web Services . . . Parts of HeartStart Telemedicine . . . . . Installing HeartStart Telemedicine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 18 18 19 . . . . . . . . . . . . . 20 iii Table of Content Before You Begin . . . . . . . . . . HeartStart Telemedicine System Installation Requirements . Downloading the Application . . . . . . . . HeartStart Telemedicine Installation . . . . . . HeartStart Telemedicine as a Service . . . . . . Configuring HeartStart Telemedicine . . . . Specifying General Settings . . . . . . Setting Up the HeartStart Telemedicine Web Services Configuring Microsoft Fax Console . . . . Understanding Auto Send Lists . . . . . Specifying Application Destinations . . . . Specifying Fax Destinations . . . . . . Specifying Printer Destinations . . . . . Specifying Email Destinations. . . . . . Specifying Auto Send Lists . . . . . . Configuring the HeartStart MRx . Accessing the Configuration Menu Modifying Settings . . . . Configuring the Hub . . . . Configuring Sites . . . . . Configuring the Wireless Link . . . Chapter 4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 20 24 25 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 26 27 28 28 29 30 30 31 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 34 34 35 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 37 38 38 39 40 45 46 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 53 . . . . . . . . . . . . . . 56 Testing and Troubleshooting . . Troubleshooting the Wireless Link . . . Testing Data Transmission . . Transmission Activity Logs and Tables . . . . . . . . . . Wireless Link Indicators . . . . Testing Wireless Link Data Transmission . . . . . . . . . . . . . . . . 57 . . . . . . . . . . . . . 57 . . . Wireless Link Troubleshooting Flowcharts and Tables . Wireless Link Computerized Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 58 59 61 65 . . . . . . . . . . . . . 68 . . . . . . . . . . . . . . . . . . . . . . . . . . 73 73 . . Viewing the HeartStart MRx Logs iv . . . . . . . . . . Setting Up the Cell Phone for Bluetooth Device Configuring Data Messenger . . . . . . . . . . . . . . . . Configuring the HeartStart MRx for the Wireless Link . Wireless Link System Prerequisites . . . . . Before You Begin . . . . . . . . . . Welcome Screen . . . . . . . . . . Bridge/Router Mode . . . . . . . . . Wireless Link in the Access Point Mode . . . . Advanced Settings . . . . . . . . . Connecting Wireless Link . . . . . . . Configuring a Bluetooth Device . . . . . . Table of Content Viewing the HeartStart Telemedicine System Log HeartStart Telemedicine Troubleshooting Table . Testing and Troubleshooting Bluetooth Devices . Troubleshooting the Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 75 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 83 83 83 Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 83 84 84 Printer . Fax . Modem . . . Supported Help How Our Support Technicians Provide Help Customer Support Centers . . . . . Appendix A Overview . . Implementation Tools . . . . . . . . . . . . . . . . . . . . 85 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . 85 Checklists . . . . . . . . . . . . . . . . . . . Bluetooth Device Profile Settings . Cell Phone, Modem, Service Plan, and Dial-Up Account Checklists . ISP Checklist . . . . . . . . . . . . . . HeartStart Telemedicine Machine Checklist . . . . . . . HeartStart Telemedicine Applications . . . . . . . . Wireless Link Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 87 88 88 89 89 89 Sample Implementation Plan for Bluetooth . . . . . . . . . . . . . . . 90 . Appendix B Index . . . . . 85 . . Glossary . 91 97 v Table of Content vi 1 Getting Started Overview This guide describes the different data management solutions offered by the HeartStart MRx, and provides details on how to successfully implement these solutions within your organization. HeartStart MRx can transmit three different types of data: • 12-Lead reports, • Periodic Clinical Data (PCDT), and • Event Summaries. HeartStart MRx can transmit these data using the following transmission methods: • Wireless Link using WiFi or cellular connection, • Bluetooth® wireless technology, and • Rosetta-Lt (available in the USA only). The following Philips software can process data wirelessly transmitted from the HeartStart MRx: • HeartStart Telemedicine System, • Data Messenger, • Event Review Pro, and • ePCR. This guide provides detailed information on how to set up these components of the HeartStart MRx Data Management solutions. An electronic copy of this Implementation Guide can be found at www.philips.com/wirelesslink. Click these links to access the selected topics in this chapter: Overview . . . . . . . . . . . . . . . . . . p. 1 . . . . . . . . . . . . . . . . . . p. 2 Tasks and Skill Levels . . . . . . . . . . . . . . . . p. 2 Data Transmission Stages . . . . . . . . . . . . . . . p. 3 Understanding the Transmission Options . . . . . . . . . . . . p. 5 Understanding the Wireless Link . . . . . . . . . . . . p. 5 . . . . . . . . . . p. 6 Audience . . Understanding 12-Lead Transmission Process Understanding the PCDT Process . Understanding HeartStart Telemedicine Using HeartStart MRx with Data Messenger . . . . . . . . . . . . p. 6 . . . . . . . . . . . . p. 7 . . . . . . . . . . . p. 7 1 1: Getting Started Overview Audience The audience for this guide are EMS management and hospital IT professionals who have purchased or are considering purchasing or upgrading their HeartStart MRx with one or more of the Data Transmission options: • 12-Lead transmission (M3801A / 861326) • PCDT (861443) • BLDT (861447) • Wireless Link (860376-860378 or 860383-860385) In order to successfully implement your HeartStart MRx data transmission solution, depending on your installed equipment, you may need to access: • The HeartStart MRx with one or more Data Transmission options and associated Philips Data Management software installed. • HeartStart MRx Instructions for Use and effective addenda. • HeartStart MRx Service Manual • HeartStart Telemedicine System User Guide • HeartStart Data Messenger User Guide • HeartStart Data Management Solutions Implementation Guide Tasks and Skill Levels Table 1 outlines the tasks and skill levels required for the Data Transmission component setup: Table 1 Tasks and Skill Levels Task Configuring HeartStart MRx Setting up the cell phone or Bluetooth device Setting up the Wireless Link Skill Level • Knowledge of HeartStart MRx • Ability to determine cell phone or modem settings Ability to determine cell phone or modem settings Installing and configuring the HeartStart Telemedicine application on the HeartStart Telemedicine Server and the HeartStart Telemedicine Viewer machines If you will be installing and configuring the hub and integrating it into an existing network, you should have the following skills: • Experience installing the Microsoft operating system that you will be using • Experience setting up an IIS server • Experience addressing security issues, such as firewalls, anti-virus software, authentication, and encryption • Experience installing and configuring a fax modem on a server • Experience setting up networks • Basic understanding of the WiFi network technology • Basic understanding of the HeartStart Telemedicine System • Basic understanding of the HeartStart Data Messenger Setting up the hub (machine If you do not have an Information Technology (IT) professional (or someone with the running HeartStart skills listed below) to install and configure the hub, it is recommended that you purchase Telemedicine Server) a server with the Microsoft operating system pre-installed. 2 Overview Table 1 1: Getting Started Tasks and Skill Levels (Continued) Task Testing and troubleshooting Skill Level • Knowledge of the HeartStart MRx • Knowledge of the HeartStart Telemedicine System • Knowledge of the HeartStart Data Messenger • Experience installing the Microsoft operating system that you will be using • Experience setting up an IIS server • Experience addressing security issues, such as firewalls, anti-virus software, authentication, and encryption • Experience installing and configuring a fax modem on a server • Experience setting up networks If you need additional help with the HeartStart MRx or HeartStart Telemedicine installations, configuration, and maintenance, please contact Philips customer support. See “Customer Support” on page 83. Philips’ data management professionals are available to help you customize your data flow according to your institution’s needs. Philips customer support cannot help you with cell phones, Internet service, and non-Philips hardware and software questions. See “What Our Support Technicians Do Not Support” on page 84 for details. Data Transmission Stages The HeartStart MRx data management can be divided into two separate stages: • Management of data transmitted during patient care for directing care or obtaining clinical oversight, and • Management of data transmitted after patient hand off for documentation, archiving or retrospective review. Data Transmitted During Patient Care During patient care, the HeartStart MRx can transmit 12-Lead reports and Periodic Clinical Data (PCDT) to the HeartStart Telemedicine System. In general, this solution enables EMS agencies to send clinical data to hospitals or remote care centers that can provide clinical oversight. The transmission solution can link rural hospitals with metropolitan hospitals, or patient care centers with surrounding hospitals. The HeartStart Telemedicine can also aggregate 12-Lead reports and forward them to the cardiology department or ECG database inside a hospital or to other destinations. The HeartStart MRx can send data to the HeartStart Telemedicine using these mechanisms: • Using the Wireless Link (WL) option, the HeartStart MRx can send data using WiFi or cellular connection to the HeartStart Telemedicine System. • Using the Bluetooth® wireless technology, the HeartStart MRx can send data to a Bluetooth-equipped cellular phone to transmit data to the HeartStart Telemedicine System. • Using the Bluetooth technology, the HeartStart MRx can send data to a PC running HeartStart Data Messenger software. The Data Messenger can then forward data to the Telemedicine. • Using the Rosetta-Lt™ option, the HeartStart MRx can send data to the General Devices Carepoint Station. This option is available in the USA only. 3 1: Getting Started Overview Figure 1 illustrates some ways to transmit data between the HeartStart MRx and Telemedicine System: Figure 1 HeartStart MRx Data Transmission Pathways Data Messenger Cellular transmission Bluetooth Wireless Link Telemedicine Server 12-Lead / PCDT WiFi transmission Firewall Internet Mobile Gateway / hotspot The HeartStart Telemedicine System acts as a central point (hub) of communication to automatically or manually send 12-Lead reports to the following destinations: • Philips 12-Lead Transfer Station application • Philips TraceMaster ECG Management System (TraceMasterVue) application • Datamed Format Translators (DatamedFT) software that supports ECG hosts, such as GE MUSE • HeartStart Telemedicine System (HeartStart Telemedicine) application • Fax machine, Printer, or Email address. The HeartStart Telemedicine System also acts as the end destination for receiving Periodic Clinical Data Transmission (PCDT) from the HeartStart MRx. You can further distribute patient waveforms and vital trends acquired by PCDT to another HeartStart Telemedicine application. Figure 2 shows all possible destinations for the HeartStart Telemedicine. Figure 2 HeartStart Telemedicine Destinations Printer Printer Fax Fax 12-lead / PCDT 12-lead report / PCDT Patient Patient report E-mail E-mail address address Internet Internet 12-lead / PCDT 12-lead / PCDT Firewall Telemedicine Firewall Telemedicine Server Server 4 Telemedicine Telemedicine Server Server 12-lead 12-lead ` 12-lead 12-lead ` ` TraceMasterVue TraceMasterV ` Datamed FT Datamed GE MUSE FT GE MUSE Understanding the Transmission Options 1: Getting Started Data Transmission After Patient Hand Off Event summaries stored on the HeartStart MRx can be transferred to Event Review Pro, HeartStart Data Messenger, or ePCR software for archiving, retrospective review, or for documentation. This transfer can be accomplished using: • A data card: transfer patient cases from the HeartStart MRx to a PC. • Bluetooth technology: transfer patient cases from the HeartStart MRx to a PC. • Batch LAN Data Transfer (BLDT): connect the HeartStart MRx to a network and send event summaries to the Data Messenger for further routing. The Data Messenger can forward this information to other applications (e.g. Event Review Pro or an ePCR software) or store it for future use. • Wireless Link (includes wireless BLDT): transfer event summaries to the Data Messenger software using WiFi. Figure 3 shows a typical configuration for sending event summaries via WL: Figure 3 Batch LAN Transfer with the Wireless Link 'DWD 0HVVHQJHU (PDLO H3&5 VRIWZDUH %/'7 (YHQW 5HYLHZ 3UR 3ULQWHU C Understanding the Transmission Options To make right choices for your Data Management solution, you need to understand how different processes work. Understanding the Wireless Link The Wireless Link (WL) is a portable wireless communication accessory for the HeartStart MRx, providing patient data transmission to the Philips HeartStart Telemedicine System using WiFi or Cellular networks. WL can also use WiFi to locally transfer event summaries to a PC running Data Messenger. The WL fits inside the side or back pouch of the standard HeartStart MRx carrying case. From the end user’s point of view, the WL operation is controlled by the HeartStart MRx, however you can communicate with the WL using a PC for the configuration and troubleshooting purposes. The WL can connect to a number of pre-configured WiFi access points. If more than one authorized access point is available in the area, the WL will select the first available access point based on the configured priority. The WL can communicate to an access point with an invisible SSID. Alternatively, the WL itself may be configured as an Access Point with a visible or invisible SSID. The WL supports the 3G GSM and CDMA cellular technologies. 5 1: Getting Started Understanding the Transmission Options Understanding 12-Lead Transmission Process The following steps describe 12-Lead report transmission process at a high level: 1 The HeartStart MRx acquires a 12-lead ECG. 2 The HeartStart MRx uses Wireless Link (WL) to communicate through the cellular or WiFi technology (a gateway device: MiFi, In Motion Technology, etc.); or Bluetooth® wireless technology to communicate through a cellphone or In Motion gateway device to reach the Internet. 3 The HeartStart MRx sends the 12-Lead report and the designating information through the Internet to HeartStart Telemedicine. HeartStart Telemedicine receives, decrypts, and saves the 12-Lead report to the database. 4 According to the instructions from the HeartStart MRx, HeartStart Telemedicine emails or sends the 12-Lead report to faxes, printers, or other destinations. If the HeartStart Telemedicine user configured an Auto Send List, then HeartStart Telemedicine sends the 12-Lead report simultaneously to all of the destinations on that Auto Send List. 5 The HeartStart Telemedicine user can also do the following manually: – View and analyze the 12-Lead report – Forward the selected 12-Lead report to another destination – Export, print a report, or email the selected 12-Lead report Understanding the PCDT Process 6 The following steps describe the patient periodic clinical data transmission (PCDT) process at a high level: 1 The HeartStart MRx user initiates a transmission session. 2 The HeartStart MRx acquires patient’s periodic clinical data, which can include a 12-Lead report, event waveforms, and vital trends. 3 The HeartStart MRx uses Wireless Link (WL) to communicate through the cellular or WiFi technology (a gateway device: MiFi, In Motion, etc.); or Bluetooth® wireless technology to communicate through a cellphone or In Motion gateway device to reach the Internet and communicate with the HeartStart Telemedicine computer. 4 The HeartStart MRx sends the patient PCDT to HeartStart Telemedicine. HeartStart Telemedicine receives, decrypts, and saves the patient data to the database. HeartStart Telemedicine lists the patient transmission details on the Patients pane. 5 The HeartStart Telemedicine user can do the following: – View and analyze the patient transmission details on the Patients workspaces – Forward the selected 12-Lead report to destinations in an Auto Send List – Forward the selected 12-Lead report to another destination manually – Forward the selected patient, event, or vital trend transmission to another HeartStart Telemedicine application manually – Export, print a report, or email the selected patient or periodic clinical data transmission manually. Understanding HeartStart Telemedicine 1: Getting Started Understanding HeartStart Telemedicine HeartStart Telemedicine System (HeartStart Telemedicine) is part of an end-to-end telemedicine solution for communicating patient data from HeartStart MRx to a viewing and forwarding workflow station. HeartStart Telemedicine consists of software (provided by Philips) and hardware and accessories provided by you, the customer. HeartStart Telemedicine comes in two editions. The Classic 12-Lead ECG Edition supports receiving, displaying, and printing of 12-Lead ECG reports. The Critical Care Edition supports 12-Lead ECGs, but can also receive, store, and display periodic clinical data that consist of a Vital Signs trending table, updated as often as every minute, and waveform data including ECG, CO2, and SpO2. HeartStart Telemedicine consists of a server component that runs typically in the Information Technology (IT) server room and a viewer component that typically runs in the clinical environment. The server component, HeartStart Telemedicine Server, consists of the application software, the database, Internet access, and the system administration user interface. The viewer component, HeartStart Telemedicine Viewer, allows clinicians to interact with the patient clinical data found in HeartStart Telemedicine Server remotely and perform limited tasks such as forwarding events. Figure 4 illustrates a typical hospital implementation. Figure 4 Typical HeartStart Telemedicine System Hospital Implementation IT Dept. Telemedicine Server Internet Emergency Dept. Clinical Viewer 1 (e.g. Charge Nurse) Clinical Viewer 2 (e.g. MD Station) System Administrator HeartStart Telemedicine Viewer connects to the HeartStart Telemedicine database through a local area network (LAN). When you start HeartStart Telemedicine Server, you can configure and manage the HeartStart Telemedicine System. When you start HeartStart Telemedicine Viewer, you can edit patient data, view data, and manually forward data to configured destinations. You cannot change system configurations. Using HeartStart MRx with Data Messenger Philips HeartStart Data Messenger streamlines the process of transferring patient data from Philips defibrillators. You can use Data Messenger to view, print, email, and save patient data. Data Messenger can also forward the data for retrospective quality review and to make care decisions before the patient arrives to the hospital. NOTE: Data Messenger is required for some event summary transmission features on HeartStart MRx. To transmit these cases, Data Messenger must be running on the same subnet as the HeartStart MRx. HeartStart MRx can forward event-summary data and periodic clinical data to Data Messenger using a Wireless Link or Bluetooth. Data Messenger can forward the data to many destinations, including the following: • Send the data to a printer. 7 1: Getting Started • Save the data to a folder. • Email the data as a file in the .hic, .mic, or .pdf format. • Forward the data to Event Review Pro. Using HeartStart MRx with Data Messenger NOTE: Do not run Data Messenger software on two PCs on the same wireless station because it is not possible to determine which data messenger responds, and where the transmission goes. 8 2 Planning Your Solution Overview In order to plan your solution, you need to understand which HeartStart MRx data transmission options your need to install, and how the solutions should fit your organization infrastructure. Click these links to access the selected topics in this chapter: Questions for Consideration . . . . . . . . . . . . . . p. 10 Prerequisites . . . . . . . . . . . . . . . . . . p. 11 Data Transmission Solutions . . . . . . . . . . . . . . . p. 11 . . . . . . . . . . . . . p. 11 Wireless Link Data Flow Scenarios . . . . . . . . . . . . . p. 11 12-Lead Transmission Scenarios . . . . . . . . . . . . p. 15 Bluetooth Transmission Setup Overview . . . . . . . . . . . . p. 15 Other Solutions . . . . . . . . . . . . p. 16 Wireless Link Transmission Setup . . . . . . High Level Planning First, you need to determine the high level structure and choose an appropriate data transmission option on your HeartStart MRx and transmission device: • Do you plan to send 12-Lead reports ahead of patient arrival? • Do you plan to send PCDT to a remote viewer during patient transport? • Do you plan to send clinical data to your electronic patient care record (ePCR)? • Do you plan to collect HeartStart MRx events from your devices for quality control? If you plan to perform 12-Lead transmission, then you need: A transmission device (unless you are using the WL with a cellular data plan). Configuration data to set up different destinations for 12-Lead (hub, site, auto-send lists, fax, email, printers, etc.). The HeartStart Telemedicine System (Classic edition) software installed on appropriate server hardware (see “HeartStart Telemedicine System Installation Requirements” on page 20). If you plan to perform PCDT, then you need: A transmission device (unless you are using the WL with a cellular data plan). The HeartStart Telemedicine System (Critical Care edition) software installed on appropriate server hardware (see “HeartStart Telemedicine System Installation Requirements” on page 20) for each site. 9 2: Planning Your Solution If you plan to send clinical data to your ePCR, then you need: Overview The HeartStart Data Messenger software (required for the WL option) Site-wide licenses for the HeartStart Data Messenger (depending on the number of PCs) Integrate the ePCR a with Philips. The ePCRs can develop this integration using Philips’ Software Developer's Kit (SDK). If you plan to collect clinical data from your HeartStart MRx for quality control, then you need: The HeartStart Event Review Pro for reviewing clinical data Optionally, site-wide licenses for the HeartStart Data Messenger (depending on the number of PCs). Questions for Consideration To successfully plan your Data Transmission solution, obtain answers to the following questions. The answers will help you make better choices and will provide your Philips data management support specialist with the insight to offer you the best options. Your organization’s equipment and workflow determine the choices that you will make for your implementation solution. Consider these questions in your planning process: Do you want a very basic implementation that simply allows you to download data and print or email it? See “Simple Data Transfer Implementations” in the HeartStart Data Management Solutions Implementation Guide. What is your preferred method of downloading data from your HeartStart MRx? See “Understanding the Transmission Options” on page 5. When and where will data be downloaded from your HeartStart MRx? Will all the data be downloaded at the end of a work shift? Will the data be transferred after each event? Will the data be transferred while the patient is still attached? Will the data be transferred to a destination within the same location, such as a PC in the same office? Will the data be forwarded to a computer in another location? Will the data be transferred from a mobile unit, such as an ambulance? The answers will influence your connection configuration. Do you have a high volume of cases that makes manual case transfer impractical? See “Processing Cases Automatically” in the HeartStart Data Messenger User Guide. Do you plan to set up network connections to transfer data within or outside of your organization? Does your organization have security requirements such as password protection or data encryption? Does your organization use, or plan to use, a patient care reporting (ePCR) system? See the “Integrating Data Messenger with an ePCR Application” section in the HeartStart Data Management Solutions Implementation Guide. Workflow Optimization Answering these questions will help you to determine optimum workflow: 10 Are you planning to send 12-Leads during patient transport? If so: Who will host the HeartStart Telemedicine System? Do you plan to use auto send lists to distribute 12-Leads? Which destinations do you plan to send to (fax, email, printer, etc.)? Data Transmission Solutions 2: Planning Your Solution What transmission method do you plan to use for 12-Leads? What hardware will be involved? Do the ambulances have WiFi connectivity? If so: What type of hardware do you use? What type of WiFi encryption do you use (WPA, WPA2-PSK, etc.)? Are you using 802.11b or 802.11g network? Does the WiFi hardware provide any specific type of filtering? Is your WiFi implementation customized? Can smart phones connect to your WiFi access points without pre-configuration (other than a password)? Would you want a data plan on the WL, or you would rather rely only on the ambulance Internet connection? Do you use an ePCR? If so: Would you like to integrate the HeartStart MRx data into the ePCR? What type of hardware do you use to run your ePCR (toughbook, tablet)? How does the ePCR connect to the Internet and synchronize with the server? Do you transmit PCDT now? Do you use HeartStart Event Review PRo software? Do your ambulances have Internet connectivity? If so: What device do you use to access the Internet? Who is the Internet Service Provider? Do you have signal boosters outside the ambulances? Do you have a quality control team that reviews events on a regular basis? If so, how do they perform their analysis? Prerequisites Do you have the necessary infrastructure for the solution you plan to implement? Consider the HeartStart Telemedicine “HeartStart Telemedicine System Installation Requirements” on page 20 and “Wireless Link System Prerequisites” on page 38 as applicable. Refer to the HeartStart Data Messenger User Guide for the Data Messenger prerequisites. Data Transmission Solutions There are several avenues to transfer data from your HeartStart MRx to various recipients. Wireless Link Transmission Setup The WL option allows the HeartStart MRx to wirelessly transmit data to Philips’ Telemedicine System, Data Messenger, ER Pro, or to a third-party electronic patient care record (ePCR) software. Using the WL, you can send 12-Leads or periodic clinical data to the Telemedicine System via a cellular broadband connection or a gateway via WiFi. Some of the typical dataflows with WL are presented in “Wireless Link Data Flow Scenarios” below. Wireless Link Data Flow Scenarios Depending on your answers to the “Questions for Consideration” on page 10, you may consider the following sample data flow scenarios. 11 2: Planning Your Solution Data Transmission Solutions Simple 12-Lead or Periodic Data Transmission Figure 5 shows the HeartStart MRx sending clinical data to the Telemedicine System during patient care or transport by connecting to the WiFi network in the ambulance. The WiFi network could be provided by a gateway (e.g., InMotion), cellular phone with a mobile hotspot, or a MiFi device. Figure 5 Simple 12-Lead / PCDT via WiFi - MiFi - phone with Mobile Hotspot - Mobile Gateway Telemedicine Server 12-lead / PCDT Patient report You can also add a data plan directly to the WL and set cellular connectivity up as the primary or back up transmission mechanism. see Figure 6. Figure 6 Simple 12-Lead / PCDT via 3G or WiFi with a 3G Backup 3G Connection Plan from your cellular provider 3G 12-lead / PCDT Patient report Telemedicine Server Telemedicine Server 12-lead / PCDT Patient report 3G used when WiFi is not available To Implement a Simple 12-Lead / PCDT, You Have to: 12 • Set up the Hub for the HeartStart Telemedicine System that will be receiving and relaying your 12-Lead reports in the HeartStart MRx configuration, see “Configuring the HeartStart MRx” on page 34 for details. • Set up Sites in the HeartStart MRx configuration for your auto send lists and end-sites for 12-Lead reports. • Set up additional Sites of the Telemedicine type for the HeartStart Telemedicine System that will receive PCDT data. • Set up the HeartStart Telemedicine System with auto send lists and other end-sites. Data Transmission Solutions • 2: Planning Your Solution Configure the WiFi access points and cellular profile, as applicable and if not pre-configured, on the WL, see “Configuring the HeartStart MRx for the Wireless Link” on page 37. Cellular service can be activated on the WL to send clinical data to the HeartStart Telemedicine System over the Internet, then the WL automatically switches between the pre-configured WiFi and cellular connections if the existing connection is lost. TIP: Make sure you set your cellular connection to the lowest priority if you plan to use it as a backup. Data Transmission from a Moving Ambulance Figure 7 shows a HeartStart MRx with the WL in an ambulance transmitting 12-Lead reports and PCDT in WiFi or Cellular mode to a HeartStart Telemedicine System. After patient hand off, the HeartStart MRx can transmit Event Summaries directly to a PC using the WL in the Access Point (AP) mode (see “Access Point Settings” on page 46). Figure 7 Data Transmission from an Ambulance PC running: - Data Msgr (for BLDT) - ePCR - ER Pro 3G 12-lead / PCDT Patient report Telemedicine Server To Implement a Data Transmission from an Ambulance, You Have to: • Set up the Hub for the HeartStart Telemedicine System that will be receiving and relaying your 12-Lead reports in the HeartStart MRx configuration, see “Configuring the HeartStart MRx” on page 34 for details. • Set up Sites in the HeartStart MRx configuration for your auto send lists and end-sites for 12-Lead reports. • Set up additional Sites of the Telemedicine type for the HeartStart Telemedicine System that will receive PCDT data. • Set up the HeartStart Telemedicine System with auto send lists and other end-sites. • If using 3G connection as a backup,1 configure the cellular connection at the lowest priority, see “Creating Connections” on page 40 and “Connection Management” on page 43. • For the Event Summary transmission after patient hand off, configure the HeartStart MRx Wireless Link option for the AP mode on HeartStart MRx configuration. • Configure the WiFi access points and cellular profile, as applicable, and if not pre-configured on the WL, see “Configuring the HeartStart MRx for the Wireless Link” on page 37. 1. A cellular connection cannot transmit event summaries. Use a WiFi connection to transmit event summaries. 13 2: Planning Your Solution Data Transmission Solutions Configuration Recommendations • Set Access Point to Yes in the HeartStart MRx Wireless Link section of the Data Transmission configuration. • WL AP mode is pre-configured with an SSID “Wireless Link <Serial Number>” that can be found on the back of the WL device. See the “Wireless Link in the Access Point Mode” on page 45 to change this setting. • When the HeartStart MRx enters the Data Management mode, the WL shortly starts broadcasting an SSID. Connect to this SSID on your PC that is running Data Messenger • After you have connected your PC to the WL WiFi connection, wait for the “connecting” message to disappear, and the Send menu to appear. Data Transfer at Hospital Bay or EMS Station When the ambulance arrives at the hospital bay and within the WiFi network vicinity, the operator switches the HeartStart MRx to the Data Management mode to enable the WL to switch from the ambulance to the station WiFi access point, to enable event summaries transfer to the hospital or EMS station. Figure 8 illustrates the HeartStart MRx WL connecting to the WiFi network after arrival at the station or hospital to download event summaries. Figure 8 Data Transfer from a Hospital Bay or EMS Station PC running: - Data Msgr (for BLDT) - ER Pro Hospital or EMS station To Implement a Data Transfer from a Hospital Bay or EMS Station, You Have to: • Configure the WiFi access points and cellular profile, as applicable and if not pre-configured, on the WL, see “Configuring the HeartStart MRx for the Wireless Link” on page 37. • Set Hospital/EMS Station WiFi as highest priority on WL configuration • If using 3G connection as a backup,1 configure the cellular connection at the lowest priority, see “Creating Connections” on page 40 and “Connection Management” on page 43. • Set Access Point to No in the HeartStart MRx Wireless Link section of the Data Transmission configuration. • Wait for the “connecting” message to disappear, and the Send menu to appear. TIP: Enter the Data Management mode when your HeartStart MRx is in the vicinity of the WiFi network that you would like to connect to. 1. A cellular connection cannot transmit event summaries. Use a WiFi connection to transmit event summaries. 14 Data Transmission Solutions 2: Planning Your Solution 12-Lead Transmission Scenarios This topic illustrates a sample use of HeartStart Telemedicine. A company has a number of HeartStart MRx monitor/defibrillators. The HeartStart Telemedicine can receive data from any of the HeartStart MRx’s or from another HeartStart Telemedicine. The HeartStart Telemedicine acts as a central point of communication to send the 12-Lead reports manually or automatically to the following possible destinations: • 12-Lead Transfer Station application • TraceMaster ECG Management System (TraceMasterVue) • DatamedFT software that supports ECG hosts, such as GE MUSE • HeartStart Telemedicine application • Email address, Fax machine, and/or Printer When the destination is a central HeartStart Telemedicine, it can further distribute 12-Lead reports automatically or manually to additional destinations. The user can also further distribute patient waveforms and vital trends to another HeartStart Telemedicine application. Bluetooth Transmission Setup Overview Figure 9 illustrates all the Data Transmission scenarios that use the Bluetooth technology: Figure 9 Telemedicine Pathways with Bluetooth Printer 12-lead / PCDT 12-lead / PCDT Patient report Cell Phone / PDA Pocket PC Fax 12-lead / PCDT Mobile Gateway E-mail address 12-lead / PCDT Internet LandLine / BT Modem 12-lead / PCDT Firewall 12-lead / PCDT Telemedicine Server Telemedicine Server 12-lead ` Laptop / Tablet Data Messenger S/W TraceMasterVue 12-lead / PCDT 12-lead ` Datamed FT GE MUSE Sample 12-Lead Transmission Implementation Using Bluetooth Setting up a Bluetooth device for transmission involves the following steps: • Gathering Prerequisites: – HeartStart MRx – cellular transmission device with an Internet data plan and Bluetooth DUN capability – HeartStart Telemedicine Server (formerly 12-Lead Transfer Station) – Server station set up with a static IP address – 12-Lead Transfer Station or HeartStart Telemedicine System software. 15 2: Planning Your Solution Data Transmission Solutions • Configuring the HeartStart MRx – You create profiles for the Bluetooth device and configure hub and site settings through the HeartStart MRx Configuration menus. A profile is a list of specifications that define how wireless transmission should work between different Bluetooth devices. You can use the same profile for similar devices. • Installation – Install the HeartStart Telemedicine Server or 12-Lead Transfer Station software. • Discovery – HeartStart MRx searches for any Bluetooth device in the vicinity. The list of discoverable Bluetooth devices is displayed on HeartStart MRx for you to select. The discovery can be done in the HeartStart MRx Monitoring or Manual mode from the 12-Lead or Data Management menu by selecting Bluetooth, then Add Device. • Pairing a Bluetooth Device with HeartStart MRx (called bonding on some Bluetooth devices) – Once you select the discovered Bluetooth device from the list, you pair it with HeartStart MRx. Pairing requires you to enter a pass key on the HeartStart MRx and the Bluetooth devices, but it does not require switching to Configuration Mode and can be done at any moment. You need to discover and pair only when you add a new Bluetooth device. You can have up to 20 Bluetooth devices paired to a HeartStart MRx at any moment (if you add a 21-st device, it replaces the least recently used or added). The HeartStart MRx is not discoverable by other Bluetooth devices and must initiate pairing. NOTE: • Selecting a Bluetooth Profile – Once you have discovered and paired with the Bluetooth device, you select the profile (Dial-Up or File Transfer). • Pairing HeartStart MRx’s Bluetooth device to the HeartStart Telemedicine server PC's Bluetooth device – This step is applicable only if you have selected the FTP profile in the previous step. • Testing and Troubleshooting – Once a profile is selected, HeartStart MRx tests the profile to determine if the Bluetooth device can communicate with HeartStart Telemedicine. If testing is successful, the message Transmission Test Passed is displayed and you are ready to transmit. If testing fails, the message Transmission Test Failed is displayed along with additional information on where the failure occurred. Use Table 26 “Bluetooth Transmission Messages” on page 79 to resolve the problem. • Sending/Deployment – Once the profile has been successfully tested, you can transmit the data from the HeartStart MRx to HeartStart Telemedicine System and 12-Lead Transfer Station. Other Solutions The HeartStart MRx can also send 12-Lead reports over a 2-way radio using Rosetta-Lt™. This Guide does not discuss this technology in depth. Contact General Devices for details if you have this option. Electronic Patient Care Report (ePCR) solutions are available from a number of software providers. A Philips-SDK-integrated ePCR software can run on a laptop, tablet, or Windows Mobile device that runs HeartStart MRx Data SDK. 16 3 Setup and Configuration Overview This chapter describes how to configure the HeartStart MRx, set up a Wireless Link (WL), cellular phone, or a Bluetooth device, and install HeartStart Telemedicine. See HeartStart Telemedicine System User Guide for HeartStart Telemedicine configuration instructions. Click these links to access the selected topics in this chapter: The HeartStart Telemedicine Web Services . . . . . . . . . . . p. 18 Parts of HeartStart Telemedicine . . . . . . . . . . . . . p. 19 Installing HeartStart Telemedicine . . . . . . . . . . . . . . p. 20 HeartStart Telemedicine System Installation Requirements . . . . . . . . p. 20 Downloading the Application . . . . . . . . . . . . . . p. 24 HeartStart Telemedicine Installation . . . . . . . . . . . . p. 25 HeartStart Telemedicine as a Service . . . . . . . . . . . . p. 26 Configuring HeartStart Telemedicine . . . . . . . . . . . . . p. 26 Specifying General Settings . . . . . . . . . . . . . p. 26 Configuring Microsoft Fax Console . . . . . . . . . . . . . p. 28 Understanding Auto Send Lists . . . . . . . . . . . . . . p. 28 Specifying Application Destinations . . . . . . . . . . . . . p. 29 . . . . . . . . . . . . . p. 34 Accessing the Configuration Menu . . . . . . . . . . . . . p. 34 Configuring the Hub . . . . . . . . . . . . . . . . p. 35 Configuring Sites . . . . . . . . . . . . . . . . p. 35 . . . . . . . . . . . . . . p. 37 Wireless Link System Prerequisites . . . . . . . . . . . . . p. 38 Bridge/Router Mode . . . . . . . . . . . . . p. 40 Wireless Link in the Access Point Mode . . . . . . . . . . . . p. 45 Advanced Settings . Configuring the HeartStart MRx . Configuring the Wireless Link . . . . . . . . . . . . . . . . . . . . p. 46 Connecting Wireless Link . . . . . . . . . . . . . . . p. 50 Configuring a Bluetooth Device . . . . . . . . . . . . . . p. 51 Setting Up the Cell Phone for Bluetooth Device . . . . . . . . . . p. 53 . . . . . . . . . p. 56 Configuring Data Messenger . . . . . . 17 3: Setup and Configuration Overview Introduction to the HeartStart Telemedicine System HeartStart Telemedicine System (HeartStart Telemedicine) is part of an end-to-end telemedicine solution for communicating patient data from HeartStart MRx Monitor/Defibrillators (HeartStart MRx) to a viewing and forwarding workflow station. Most commonly, HeartStart Telemedicine serves EMS agencies sending clinical data from the ambulance to the hospital. HeartStart Telemedicine can also link rural hospitals with metropolitan ones and primary care centers with hospitals. The HeartStart Telemedicine can also aggregate 12-Leads and forward them to the cardiology department or ECG database inside a hospital. The Data Transmission solution consists of software (HeartStart Telemedicine System, Data Messenger, etc.) and hardware (HeartStart MRx, Wireless Link, etc., provided by Philips) and hardware and accessories (PC, network, Ethernet cables, etc.) provided by you, the customer. On the sending side, HeartStart MRx can be configured to transmit 12-Lead ECG reports (12-Lead reports) and periodic clinical data such as patient’s vitals and waveform data when trigger events occur. A trigger event is an HeartStart MRx event that initiates the transmission. The HeartStart MRx uses WiFi/cellular (provided through the Wireless Link option) or Bluetooth® wireless technology to send clinical data over the Internet. There are two software options of HeartStart Telemedicine. In HeartStart Telemedicine Classic 12-Lead Edition, HeartStart Telemedicine stores, displays, and forwards only 12-Lead reports. In HeartStart Telemedicine Critical Care Edition, HeartStart Telemedicine can store, display, and forward periodic clinical data transmission in addition to 12-Lead data. HeartStart Telemedicine consists of a server component that runs typically in the Information Technology (IT) server room and a viewer component that typically runs in the clinical environment. The server component, HeartStart Telemedicine Server, consists of the application software, the database, Internet access, and the system administration user interface. The viewer component, HeartStart Telemedicine Viewer, allows clinicians to interact with the patient clinical data found in HeartStart Telemedicine Server remotely and perform limited tasks such as forwarding events. HeartStart Telemedicine Server requires a static public IP address or a domain name that is connected to the Internet and to Internet Information Services (IIS). For more information, see the “Enabling Internet Information Services (IIS)” topic in the HeartStart Telemedicine System User Guide. The connection to the Internet must be on at all times. If you use HeartStart Telemedicine Server to receive connections over the Internet, confirm that IIS is installed, is running, and has an “always on” Internet connection before you install HeartStart Telemedicine. Configure the HeartStart Telemedicine system as an Application Server. By default, the HeartStart Telemedicine components communicate on TCP/IP Port 80. The HeartStart Telemedicine Web Services HeartStart MRx communicates with HeartStart Telemedicine through the Internet. To receive 12-lead reports, ECG waveforms, and vital trends from HeartStart MRx, you need to have a web server. The HeartStart Telemedicine Server machine requires the following services: 18 • Internet Service Provider (ISP): The ISP provides a connection to the Internet. The ISP must supply a static or permanent IP address to support your domain name. • Domain Name Service (DNS): The DNS provides a domain name for the IP address. Many ISPs can obtain and register a domain name for you, or you can do it yourself. For more information, see the Accredited Registrar Directory at the InterNIC Web site (http://www.internic.net). • Internet Information Services (IIS): The IIS sends and receives information from the Internet. Although IIS ships with the Windows application, Windows does not automatically install IIS when you install the operating system. You must install IIS separately. The Microsoft Web site at http://www.microsoft.com/iis has additional information. For more information, see the “Installing the Operating System” topic in HeartStart Telemedicine System User Guide. Overview 3: Setup and Configuration • Simple Mail Transfer Protocol (SMTP): The SMTP service delivers outgoing email messages. You can use it to create Auto Send Lists, so that a group of destinations is notified via email when information is received by the server. If you want to send patient reports, 12-Lead reports, ECG waveform, and vital trends through the Email feature, Philips Healthcare recommends that you name an SMTP address on the General Configuration workspace when you configure the HeartStart Telemedicine system. In most cases, you can use the SMTP address supplied by your ISP or network. If you install SMTP, you must install SMTP separately from the Windows Control Panel. The SMTP installation creates a default SMTP configuration. You can use IIS Manager to customize the SMTP configuration. For more information, see the “Configuring the System” topic in HeartStart Telemedicine System User Guide. TIP: Microsoft provides an SMTP service. For more information on how to deploy and configure the SMTP service, search for “smtp” on the Microsoft Developer Network (MSDN) Web site at http://msdn2.microsoft.com/en-us/worldwide/default.aspx. Parts of HeartStart Telemedicine HeartStart Telemedicine Server consists of the following parts: • HeartStart Telemedicine application – Displays HeartStart MRx patient data and system log information, which shows all HeartStart Telemedicine activity. The application provides the ability to configure HeartStart Telemedicine to send 12-Lead reports automatically and HeartStart MRx patient data manually. HeartStart MRx patient data includes 12-Lead reports, trigger events and waveforms, and periodic vital trends. • PCDT – The HeartStart MRx option to transmit clinical data from the point of care for a critical care patient to the receiving hospital to facilitate the next level of care. The PCDT option uses the Wireless Link or Bluetooth wireless technology to automatically transmit periodic vitals and 12-Lead reports and waveform data upon a set of trigger events from a clinical mode to HeartStart Telemedicine. • HTTP service – IIS hands over the received data from the HeartStart MRx or another HeartStart Telemedicine to the HTTP service. The HTTP service saves the data in the appropriate inbox. • Inbox Watcher service – Monitors the HeartStart Telemedicine inboxes. Inbox Watcher Service parses the data into separate files and moves the data from the inbox into the database and Backup folder. • SQL Server database – to store the 12-Lead report and configuration information, installed automatically with the HeartStart Telemedicine Server software. • Bluetooth Monitor Service – Enables the Bluetooth Monitor to automatically watch for patient periodic clinical data transmissions that are received from HeartStart MRx. The Bluetooth Monitor stores the data in the specified Bluetooth Exchange Folder location and imports the data into the database. Typically used in emergency departments where HeartStart MRx’s are sending 12-Lead ECGs locally. The “Glossary” on page 91 defines the terms used in this guide. The “HeartStart Telemedicine System Installation Requirements” on page 20 defines the installation prerequisites. The “Configuring HeartStart Telemedicine” topic on page 26 provides worksheets to help you set up HeartStart MRx for use with HeartStart Telemedicine. 19 3: Setup and Configuration Installing HeartStart Telemedicine The Implementation Tools appendix provides additional information to help you set up the transmission options. Philips Healthcare suggests that you refer to the sample implementation plan and fill out the worksheets before beginning the installation. Installing HeartStart Telemedicine This topic describes how to install, configure, and register HeartStart Telemedicine. CAUTION: You may install another application, such as a web application, on the same machine that runs the HeartStart Telemedicine. Philips Healthcare does not prohibit installing other applications, however, you are responsible for performing and validating any integration testing to ensure that additional applications do not affect the operation of HeartStart Telemedicine. Depending on your organization’s purchase, you will install the HeartStart Telemedicine Server application. You might also install one or more HeartStart Telemedicine Viewer applications. Your Proof of Purchase identifies the software URL, serial number, and license for each application. Philips recommends that a professional network technician installs and configures HeartStart Telemedicine. HeartStart Telemedicine is a web service. The application requires a static IP address that is connected to the Internet. The connection must be on at all time. For installation details, refer to the “Installing HeartStart Telemedicine” and “Setting Up the HeartStart Telemedicine Monitoring Service” chapters in HeartStart Telemedicine System User Guide. Before You Begin Before you install HeartStart Telemedicine, confirm that the following components are set up: • Confirm that a static IP address is assigned to the HeartStart Telemedicine Server machine and connected to the Internet. • Confirm that the Internet connection is on all the time. • Confirm that each HeartStart Telemedicine Viewer machine connects to the network. • Confirm that the HeartStart Telemedicine Server and the HeartStart Telemedicine Viewer machines are set up according to the instructions in HeartStart Telemedicine System User Guide. • Confirm that IIS is installed and running on the HeartStart Telemedicine Server machine. • If you plan to use the email function, then: • – confirm that the Simple Mail Transfer Protocol (SMTP) service is set up on the HeartStart Telemedicine Server machine according to the instructions. – confirm that the MAPI-compliant email client is set up on each HeartStart Telemedicine Viewer machine according to the instructions. Confirm that your internal firewall allows inbound communication on TCP port 80 on the HeartStart Telemedicine Server machine. HeartStart Telemedicine System Installation Requirements The HeartStart Telemedicine System requirements may depend on whether you have installed the 12-Lead Transmission and PCDT options installed on your HeartStart MRx. 20 Installing HeartStart Telemedicine 3: Setup and Configuration HeartStart Telemedicine Prerequisites You will need the following items before you begin: • Materials and documents listed in the “Audience” section on page 2. • The Bluetooth option requires HeartStart MRx Hardware Version B1 and Software Version B.05 or greater. The Wireless Link option requires HeartStart MRx Hardware Version B1 and Software Version T.00 or greater. – Device’s Hardware Version. Check the Hardware Version label on battery compartment B to see the device’s Hardware Version. – • • • Device’s Software Version. See “Printing the Device Info” in the HeartStart MRx Service Manual for information on determining the devices’s Software version. The Service Manual and other documentation can be found on the Philips website at: www.philips.com/productdocumentation. The HeartStart Telemedicine Server machine running Windows Server 2008 R2 operating system. The HeartStart Telemedicine Viewer machines running Windows 7 operating system. The HeartStart Telemedicine 4.2 applications and HeartStart Telemedicine System User Guide. 1 The Setup and Configuration chapter lists additional prerequisites for different options. System Requirements This section describes the software, hardware, and accessories required for HeartStart Telemedicine installation. Confirm that your facility supports the following minimum system requirements. Table 2 “System Requirements” has the following sections: • “SOFTWARE REQUIREMENTS” on page 21 • “HARDWARE REQUIREMENTS” on page 22 • “ACCESSORIES” on page 23 Table 2 System Requirements Component Requirements SOFTWARE REQUIREMENTS Operating system For HeartStart Telemedicine Server Required: Microsoft® Windows Server 2008 R2 or Windows 7 that run with the corresponding Microsoft Internet Information Service (IIS) Recommended: 64-bit Microsoft Windows 7 For HeartStart Telemedicine Viewer Required: 32- or 64-bit Microsoft Windows 7 Server software For HeartStart Telemedicine Server, to configure the HeartStart Telemedicine system, database, and web service Required: • Microsoft SQL Server 2008 R2 Express Edition, 10 GB of data capacity • IIS Server for Windows Server 2008 R2 • IIS Server for Windows 7 SMTP Server For HeartStart Telemedicine Server to forward emails, such as in an Auto Sent List. Bluetooth Required: Version 1.1 or higher 1. The HeartStart Telemedicine 4.0 may still be available for the customers running the 32-bit Microsoft® Windows Server 2003 (SP 2 or later) and Windows XP (SP 3 or later). 21 3: Setup and Configuration Table 2 Installing HeartStart Telemedicine System Requirements (Continued) Component Requirements HARDWARE REQUIREMENTS Processor speed For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer Minimum: 1 GHZ or higher Display For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer Minimum: 1024 x 768 Recommended: 1280 x 1024 or higher Memory For HeartStart Telemedicine Server Minimum: 2 GB For HeartStart Telemedicine Viewer Minimum: 1 GB Disk storage space For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer: Required: 20 GB of available disk space for database storage Hard disk space requirements vary depending on usage. Variables affecting disk space requirements include the number of HeartStart MRx patient cases archived and the number of years to store data. Philips Healthcare recommends to back up your data and store the data at an off-site location. See the “Storage Requirements” topic in HeartStart Telemedicine System User Guide for more information. CD-ROM drive For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer Required Internet connection For HeartStart Telemedicine Server: • To activate the application software • To forward patient transmissions to destinations • To receive software updates and send email • To connect with HeartStart MRx and to HeartStart Telemedicine Server on the local area network (LAN) For HeartStart Telemedicine Viewer: • To activate the application software • To forward patient transmissions to destinations • To receive software updates and send email • To send email • To connect to the HeartStart Telemedicine Server machines Telephone line 22 For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer, to fax patient data to destinations and dial in to the Internet Required: 1 analogue telephone line for each machine Installing HeartStart Telemedicine Table 2 3: Setup and Configuration System Requirements (Continued) Component Requirements ACCESSORIES PDF Reader For HeartStart Telemedicine Server and HeartStart Telemedicine Viewer, to view the documentation. Recommended: Adobe Reader latest version, available from www.adobe.com Back up and restore tool For the HeartStart Telemedicine Server, to prevent data loss. Follow your organization’s back-up policies. Email application For HeartStart Telemedicine Server, to send email through an Auto Send List Recommended: Microsoft® Outlook or Microsoft® Outlook Express. To activate the software or to send patient data using email, configure an email client: Required: MAPI-compliance For HeartStart Telemedicine Viewer, to activate the software or to send patient data using email, configure an email client: Required: MAPI-compliance Fax modem To fax patient data to destinations: Recommended Printer To print 12-Lead and periodic vitals reports Required Bluetooth adapter To transfer HeartStart MRx patient data using Bluetooth wireless transfer Required a Bluetooth stack For HeartStart Telemedicine Server: To transfer patient data from HeartStart MRx to your HeartStart Telemedicine Server machine Required a To transfer HeartStart MRx patient periodic clinical data Required: • Bluetooth Version: 1.1 or higher • Windows 7 • Recommended: Widcomm Bluetooth stack. You can use any Bluetooth stack supported for the HeartStart MRx, see HeartStart MRx Instructions for Use. Typically deployed in close proximity to HeartStart MRx devices, (e.g. emergency-departments-only environment). Bluetooth Class 1 maximum transmission range: 100 meters, approximately 300 feet. The transmission range depends upon the transmission range of the lowest class Bluetooth device. Most Bluetooth devices are Class II with a maximum transmissions range of up to 10 meters, approximately 30 feet. a. Required only if you do not use the Internet and transfer 12-Leads locally using Bluetooth wireless technology. This use case is more common in hospital emergency departments, where the HeartStart MRx is used as a bedside or hallway monitor. Philips recommends that you store backup information at a separate location on an installed tape or other backup device. You should have a plan for recovering information in the case of a software or hardware failure. Storage Requirements Storage requirements depend on the volume and frequency of patient transmissions, and on the type of data you send to HeartStart Telemedicine. 23 3: Setup and Configuration Installing HeartStart Telemedicine The SQL Server database should have a capacity of at least 10 GB to store the demographic patient information, 12-Lead reports, events, periodic vital trends, and configuration information. NOTE: Philips Healthcare recommends that you adjust the number of days that HeartStart Telemedicine stores data on the General Configuration workspace based on your network traffic. • HeartStart Telemedicine Classic 12-Lead Edition – Storage requirements depend on the volume of 12-Lead reports you send to HeartStart Telemedicine. If you assume that an average 12-Lead report is approximately 60 KB, the SQL Server Express 2008 R2 database can store approximately 150,000 12-Lead reports (10 GB/60 KB =150,000, approximately). • HeartStart Telemedicine Critical Care Edition – Storage requirements depend on the frequency of patient transmissions and the type of data you send to HeartStart Telemedicine. Table 3 provides an estimate of the storage required for one month and one year per HeartStart MRx Monitor•Defibrillator. Multiple the estimated storage required for the transmission data type and interval by the number of HeartStart MRx units used. Table 3 Storage Requirements Data to Transmit Periodic vital trends Data Transmission in KB Interval for One HeartStart MRx Approximate Storage Required per Year per Month 5 KB 1-minute interval 2.63 GB .22 GB 1 KB 5-minute intervals .53 GB .04 GB Events and periodic vital trends 15 KB 1-minute interval 7.9 GB .66 GB 3 KB 1.58 GB .13 GB 12-Lead reports, events, and periodic vital trends 45 KB 1-minute interval 23.65 GB 2 GB 9 KB 4.73 GB .4 GB 5-minute intervals 5-minute intervals Downloading the Application You can download the application that you purchase or receive from your sales representative. Use the instructions that you receive to download the application from the Internet. Save the application file to your computer. When you download HeartStart Telemedicine, save the application on the HeartStart Telemedicine machine. You can also save the application on a CD, DVD, or other media such as a USB memory stick or secure digital (SD) data card. 24 To download the application: 1 Close all currently running programs, including virus checkers. 2 Start Windows. 3 Start Internet Explorer. 4 Navigate to the URL provided in your Proof of Purchase or by your sales representative. 5 On the left pane, select the product. 6 On the right pane, press the link in Software Download. 7 Navigate to the download link. 8 Save the installation file to your machine. You can also save the file to a CD, DVD, or other media such as a USB memory stick or secure digital (SD) data card. Installing HeartStart Telemedicine 3: Setup and Configuration HeartStart Telemedicine Installation HeartStart Telemedicine saves Auto Send Lists from 12-Lead Transfer Station 3.0. The default Auto Send List also remains as the default Auto Send List in HeartStart Telemedicine System 4.2. Typically, you install the HeartStart Telemedicine software from URL provided in your Proof of Purchase or by your sales representative. To install HeartStart Telemedicine from a storage medium: 1 Navigate to the directory where you saved the downloaded installation file. 2 Double-click the installation file. 3 Read the on-screen messages. Follow the on-screen instructions. By default, HeartStart Telemedicine Service Manager starts after HeartStart Telemedicine Server starts. HeartStart Telemedicine Service Manager can also run as a window service. For more information, see the “Running HeartStart Telemedicine Service Manager as a Service” topic in HeartStart Telemedicine System User Guide. For information on how to activate, register, and configure HeartStart Telemedicine, see HeartStart Telemedicine System User Guide. Verifying the Installation To ensure that the HeartStart MRx can connect to HeartStart Telemedicine from outside of the firewall, run this test on a machine outside the firewall that protects the HeartStart Telemedicine. To verify the installation: 1 Type the following URL in the browser: – For a test from the Internet: http://<IP_addr_or_Domain_name>/ems/MRxtest.mrx?SourceName=test – For a test from within the firewall: http://<IP_addr_or_Domain_name>/ems/MRxtest.mrx?SourceName=test or http://<Telemed_machine_name>/ems/MRxtest.mrx?SourceName=test If you see a similar window as shown in Figure 10, the operating system, IIS, and the HeartStart Telemedicine are installed correctly. Figure 10 HeartStart Telemedicine Window Telemedicine Server x.x.xxx.xxx If this window does not appear, make sure that IIS is running. If not, restart IIS or check the IIS log to make sure it is configured properly. 25 3: Setup and Configuration 2 Configuring HeartStart Telemedicine Make sure that the HeartStart Telemedicine Server application is running on the machine. The automatic services provided by HeartStart Telemedicine are only active while the application is running and do not restart automatically. Thus, if there is a power outage, then you must restart the HeartStart Telemedicine application on the server. For information on how to configure Transfer Station Service Manager, see HeartStart Telemedicine System User Guide. HeartStart Telemedicine as a Service If you need to receive 12-Lead reports or other clinical data on a 24 hour/7 days schedule regardless if a user is logged on, you must set up HeartStart Telemedicine Service Manager to start up automatically. You can configure the service from Windows. When the HeartStart Telemedicine Server machine restarts, Windows starts HeartStart Telemedicine Service Manager automatically. For more information, see the “Running HeartStart Telemedicine Service Manager as a Service” topic in HeartStart Telemedicine System User Guide. Configuring HeartStart Telemedicine You can configure HeartStart Telemedicine to serve one EMS dispatch center, or one or more hospitals, or an entire regional STEMI or Critical Care Transport Network involving several agencies and hospitals. Configuration of HeartStart Telemedicine is performed on the HeartStart Telemedicine Server machine. The primary function of HeartStart Telemedicine is to send 12-Lead transmissions (12-lead ECG reports) and from the HeartStart MRx to one or more external destinations. Auto Send Lists allow you to build distribution lists on the HeartStart Telemedicine Server to send 12-Lead ECG reports to multiple destinations at once. On the HeartStart MRx side, you can have up to 20 different hospitals or receiving Sites. When a site is configured as a hub, and the spelling matches an Auto Send List on HeartStart Telemedicine, sending to this site will result in sending to all the destinations on that Auto Send List at once. Use the worksheets in the “Configuring a Bluetooth Device” section when you configure how the HeartStart MRx sends 12-Lead reports to HeartStart Telemedicine. In HeartStart Telemedicine, use the worksheets when you complete the features that are available on the Administration navigation pane. For information on how to configure HeartStart Telemedicine, see the “Configuring HeartStart Telemedicine System” and “Managing Patient Data and Destinations” chapters in HeartStart Telemedicine System User Guide. Specifying General Settings Before you can process, store, and send 12-Lead reports, you must specify how to store, fax, print, and email 12-Lead reports. The installation process automatically installs the database server on the HeartStart Telemedicine Server machine for you. By default, HeartStart Telemedicine formats 12-Lead reports with grids and in the time-sequential format, and saves 12-Lead reports in the database for 30 days. You can change these settings. You can also specify how to email 12-Lead reports. 26 Configuring HeartStart Telemedicine 3: Setup and Configuration General HeartStart Telemedicine Settings In HeartStart Telemedicine, the general settings listed in Table 4 appear on the General Configuration workspace: Table 4 General Settings Field Label Description HeartStart Telemedicine Server Name Name of the database for HeartStart Telemedicine Server machine that manages the database. Print with grid How HeartStart Telemedicine prints 12-Lead reports. Select the check box to print reports with grid lines. Clear the check box to print reports without grid lines. 12-Lead layout How the HeartStart Telemedicine faxes or prints 12-Lead reports. Select the format from the drop-down list. Previous history The number of days HeartStart Telemedicine saves reports in the database. The default is 30. The minimum is 1. SMTP server name The IP address or name of the email server. Reply email address Email address that receives an email when an email destination sends a reply. Used when emailing 12-Lead reports through an Auto Send List. Password protect attachment Select the check box to password protect a 12-Lead report attachment. Used when emailing 12-Lead reports from the File menu. Bluetooth Exchange Folder (for in-hospital use only) Specify the location of the Bluetooth Exchange Folder to watch for patient periodic clinical data transmissions automatically. The default Bluetooth Exchange Folder location is C:\Users\<user name>\. Settings Select the box Simultaneous Select the box Clear the box Time sequential Clear the box For more information on the Bluetooth Monitor feature, see the “Using the Bluetooth Monitor Feature” topic in HeartStart Telemedicine System User Guide. Setting Up the HeartStart Telemedicine Web Services HeartStart Telemedicine uses Internet Information Services (IIS) to send and receive information from the Internet. Although IIS ships with the Windows application, Windows does not automatically install IIS when you install the operating system. In order for the HeartStart Telemedicine to receive data from a HeartStart MRx in the field, the HeartStart Telemedicine Server machine must have a public Internet address. The HeartStart Telemedicine Server machine must be able to act as a web server and respond to incoming requests. Refer to the “Setting up Internet Information Services (IIS)” and “Providing the HeartStart Telemedicine Web Service” topics in HeartStart Telemedicine System User Guide. 27 3: Setup and Configuration Configuring HeartStart Telemedicine Configuring Microsoft Fax Console Fax users should configure the Microsoft Fax Console for landscape printing. Configure Microsoft Fax Console for the same account that runs the HeartStart Telemedicine service. • If you run HeartStart Telemedicine as a service, this “account” must configure the Fax Console. • If you run HeartStart Telemedicine as a console application, the user who is logged on must configure the fax printer. For more information, see HeartStart Telemedicine System User Guide. Configure Microsoft Fax Console for each HeartStart Telemedicine Server and HeartStart Telemedicine Viewer machine. You might need the operating system installation CD. The Microsoft Fax Console configuration process depends on your Windows version, therefore research Microsoft Help (http://support.microsoft.com/find-solutions/windows/) for instructions on how to configure Fax Console. If the fax printer clips portions of the 12-Lead report, consult your fax machine user’s manual for the subject “Reducing Faxes to Fit,” “Image Resizing,” or “Scaling.” This item is most often located in the menu under Fax options, Incoming faxes. Understanding Auto Send Lists You can configure up to 50 Auto Send Lists per HeartStart Telemedicine System, and each Auto Send List can have up to 20 destinations. A destination may be included in multiple Auto Send Lists. You configure a destination individually and then assign it to an Auto Send List. During the Auto Send List configuration process, you can select one list to be the default Auto Send List. HeartStart Telemedicine sends the 12-Lead report to the default Auto Send List when the site name for the HeartStart MRx hub does not match the name of a configured Auto Send List. For more information, see the “Sending a 12-Lead Report Automatically” topic in HeartStart Telemedicine System User Guide. Sending a 12-Lead Report Automatically An Auto Send List can automatically send a 12-Lead report to any combination of the following types of destinations: • 12-Lead Transfer Station application • TraceMasterVue application • DatamedFT software • HeartStart Telemedicine application • Fax machine, Printer, Email address NOTE: You can process and store 12-Lead reports from 12-Lead Transfer Station 3.0 or the current version of HeartStart Telemedicine. However, you can only send encrypted 12-Lead reports to the current version of HeartStart Telemedicine. If you do not configure a default Auto Send List, and the HeartStart MRx hub does not match the configured Auto Send List, HeartStart Telemedicine adds the 12-Lead report to the database. You can then send the 12-Lead report manually. Sending a 12-Lead Report Manually You can also manually send a selected 12-Lead report simultaneously to any combination of the following types of destinations: • Auto Send List • Any destination listed in “Sending a 12-Lead Report Automatically” above 28 Configuring HeartStart Telemedicine 3: Setup and Configuration Use the Forward Selected 12-Lead menu option on the File menu to send a selected 12-Lead report to one of the configured Auto Send Lists or destinations. Use the Fax 12-Lead, Print Report, and Email PDF options on the File menu to send a selected 12-Lead report to a fax machine, printer, or email address that is not configured as a destination HeartStart Telemedicine. You can also use the Print Report option on the File menu or toolbar button to print a report of the selected patient transmission, or a single selected transmission to the same printers set up for the HeartStart Telemedicine Server machine. Specifying Application Destinations In HeartStart Telemedicine, you can send patient 12-Lead reports from HeartStart MRx to one or more application destinations automatically through an Auto Send List or manually from the Forward Selected 12-Lead option on the File menu. You configure a destination from the Application Destinations workspace on the Administration navigation pane. Application Settings HeartStart Telemedicine uses the following fields to specify application destinations: Table 5 Application Destination Settings Field Label Description Name A name that you provide for the application. Description (Optional) A brief description that describes the use of the application. Location type The type of application: 12-Lead Transfer Station, TraceMasterVue, DatamedFT, or HeartStart Telemedicine. URL or Location The URL or path identifying where the application is installed. DatamedFT requires the location of the DatamedFT Inbox, for example C:\DatamedFT\Inbox Application Destination Worksheet Copy the following worksheet for each application destination used in HeartStart Telemedicine: Table 6 Application Destination Worksheet Application Destination Setting Name Description (Optional) Location type for the application, select one: 12-Lead Transfer Station TraceMasterVue DatamedFT HeartStart Telemedicine URL or Location (For DatamedFT only: specify the location of the DatamedFT Inbox) 29 3: Setup and Configuration Configuring HeartStart Telemedicine Specifying Fax Destinations In HeartStart Telemedicine, you can fax 12-Lead reports from HeartStart MRx to one or more of the fax destinations automatically through an Auto Send List or manually from the Forward Selected 12-Lead option on the File menu. You configure a fax destination from the Fax Destinations workspace on the Administration navigation pane. HeartStart Telemedicine also sends a 12-Lead report to any fax number specified in HeartStart MRx. Fax Requirements To use the Fax feature in HeartStart Telemedicine, complete the following tasks: • Connect HeartStart Telemedicine to a fax modem. • Install Microsoft Fax Service on the HeartStart Telemedicine machine. • Configure the retry settings in the Microsoft Fax Console window. • Complete the fax settings using the Fax Destinations workspace. For information on configuring the Microsoft Fax Console, see the “Setting up Fax Destinations” topic in HeartStart Telemedicine System User Guide. Fax Settings HeartStart Telemedicine uses the following fields to specify fax destinations: Table 7 Fax Destination Settings Field Label Description Name A name that you provide for the fax number. Description (Optional) A brief description that describes the use of the fax. Fax number The numeric telephone number of the fax device. Include the required numbers for the dialing plan. Fax Destination Worksheet Copy the following worksheet for each fax destination used in HeartStart Telemedicine. In the worksheet, you do not have to add any fax number that is specified in the HeartStart MRx. Table 8 Fax Destination Worksheet Fax Destination Setting Name Description (Optional) Fax number Specifying Printer Destinations In HeartStart Telemedicine, you can print 12-Lead reports from the HeartStart MRx to one or more of the printer destinations automatically through an Auto Send List, and manually from the Forward Selected 12-Lead and Print Report options on the File menu. You select a printer destination from the Auto Send Lists workspace while you configure an Auto Send List. You can also print reports for selected patient records, waveforms, and vital trends manually. You set up the default printer in Windows. 30 Configuring HeartStart Telemedicine 3: Setup and Configuration Printer Option Requirements All printers must be on the same network as the HeartStart Telemedicine Server machine. You must define each printer in Windows. For each HeartStart Telemedicine Viewer machine, you must set up the same printers as for the HeartStart Telemedicine Server machine. Printer Destination Worksheet Copy the following worksheet and enter the printer name and location for each printer used in HeartStart Telemedicine. When you press Quick Print on the Reports toolbar, HeartStart Telemedicine sends the report to the default printer. Table 9 Printer Destination Worksheet Printer Name HeartStart Telemedicine Location Default Printer (select one for each installation) Specifying Email Destinations In HeartStart Telemedicine, you can email 12-Lead reports from HeartStart MRx to one or more email destinations automatically through an Auto Send List or manually from the Forward Selected 12-Lead option. Configure an email destination from the Email Destinations workspace on the Administration navigation pane. You can also email a selected patient record, 12-Lead report, waveform, or periodic vital trending from the Email PDF option on the File menu. Email Requirements To use the Email feature in HeartStart Telemedicine, complete the following tasks: • Install the email application on the HeartStart Telemedicine Server machine. HeartStart Telemedicine uses the email client application to email the 12-Lead report when you select Email PDF from the File menu. For more information, see the instructions for your email application. • Install the SMTP server for use with IIS, if you want to email 12-Lead reports through an Auto Send List. For more information, see the “Setting Up Email Address Destinations” topic in HeartStart Telemedicine System User Guide. • Configure the email settings in HeartStart Telemedicine. For more information, see the “Setting Up Email Destinations” topic in HeartStart Telemedicine System User Guide. 31 3: Setup and Configuration Configuring HeartStart Telemedicine Email Settings HeartStart Telemedicine uses the email destination settings to specify email destinations for use with Auto Send Lists and the Forward Selected 12-Lead and Email PDF options on the File menu: Table 10 Email Destination Settings Field Label Description Name A name that you provide for the email address. Description (optional) A brief description that describes the use of the email address. Add an email address The alphanumeric email address for the recipient. Password for attachment Select to password-protect the email attachment. The password (optional) that the recipient will enter to open the 12-Lead report attachment. Email Destination Worksheet Copy the following worksheet for each email address destination used in HeartStart Telemedicine. Table 11 Email Destination Worksheet Fax Destination Setting Name Description (optional) Password for attachment (optional) Select the box; Password: __________________________ Clear the box Specifying Auto Send Lists In HeartStart Telemedicine, you can configure an Auto Send List to send 12-Lead report to as many as 20 destinations on the Auto Send Lists workspace on the Administration navigation pane. You can also configure as many as 50 auto send lists on one HeartStart Telemedicine. For example: One auto send list can consist of only one destination. And, the same destination can also appear on the 19 other auto send lists. You configure destinations individually. During the auto send list configuration process, you select the destinations for the auto send list that are listed in Destinations on the Auto Send List workspace. You can also select one list to be the default Auto Send List. Auto Send List Settings HeartStart Telemedicine uses the fields in Table 12 to specify auto send lists. TIP: Use the individual destination worksheets to specify settings for the applications, faxes, printers, and email address that you add to an Auto Send List. 32 Configuring HeartStart Telemedicine Table 12 3: Setup and Configuration Auto Send List Destination Settings Field Label Description Name A name that you provide for the Auto Send List. Description (Optional) A brief description that describes the use of the Auto Send List. Set as the Identifies the Auto Send List as the Auto Send List used to send 12-Lead reports when default Auto the site name for the HeartStart MRx hub does not match the name of a configured Send List Auto Send List. Destinations The destinations for the applications, faxes, printers, and email addresses that will automatically receive the 12-Lead report transmitted by the HeartStart MRx. Auto Send List Destination Worksheet Copy the following worksheet for each Auto Send List used in HeartStart Telemedicine. The maximum number is 50. Table 13 Auto Send List Destination Worksheet Auto Send List Setting Name Description (optional) Set as the default Auto Send List a Select the box Clear the box Destination names (20 maximum): Application 12-Lead Transfer Station TraceMasterVue DatamedFT HeartStart Telemedicine Fax number Printer name Email address a. The default Auto Send List applies to all incoming transmissions except those intended to another (designated) Auto Send List. Designated Auto Send Lists override the default Auto Send List. If you do not set the default Auto Send List, the HeartStart Telemedicine will have no default Auto Send List. 33 3: Setup and Configuration Configuring the HeartStart MRx Configuring the HeartStart MRx You can customize your HeartStart MRx Data Transmission settings through the Configuration menus. Save configuration settings to a data card for backup purposes and replication on other devices. Accessing the Configuration Menu WARNING: The HeartStart MRx should never be connected to a patient while performing configuration activities. To access the Configuration Main menu: 1 Turn the Therapy Knob to Monitor. 2 Press the Menu Select 3 Using the Navigation buttons, select Other and press the Menu Select button. 4 Using the Navigation buttons, select Configuration and press the Menu Select button. 5 Press the Menu Select button again to acknowledge leaving normal operating mode. 6 The Configuration Main menu is displayed, listing sub-menus for each category of configurable parameters. You may use this menu to view or print your device’s configuration, as well as to modify the date and time settings. To modify any other settings, see “Modifying Settings” below. 7 To return to normal operating mode, press the Exit Config soft key. button. Modifying Settings When modifying configuration settings, the device should be connected to external power and have a battery with at least 20% capacity installed. To modify configuration settings, from the Configuration Main menu: 1 Press the Change Config soft key. 2 When prompted, enter the configuration password. 3 Press the Menu Select button. Use the Navigation buttons to select the sub-menu for the category of parameters to be changed. Then press the Menu Select button. 4 Use the Prev Item and Next Item soft keys to select a parameter. 5 Use the Navigation buttons to highlight the desired choices. Press the Menu Select button to select the highlighted choice. 6 Repeat steps 3, 4, and 5 to select another sub-menu and modify additional settings. 7 Once the desired setting changes have been made, from the Configuration Main screen, press the Save Changes soft key, or press the Cancel Changes soft key to leave the settings unchanged. 8 Press the Exit Config soft key to return to normal operating mode. If you press Exit Config before saving the changes, you are prompted with the message Configuration Not Saved - Exit Anyway? Select No and press the Menu Select button. Then press the Save Changes soft key. The Tables 17, 14, and 15 on pp. 52 - 36 list configurable parameters for the Data Transmission submenus on the Configuration Main menu. A description of each parameter is provided along with the possible choices for settings. Default settings are in bold type. 34 Configuring the HeartStart MRx 3: Setup and Configuration Configuring the Hub Configure the hub for the 12-Lead Transmission only. PCDT does not require the hub1. A hub is a hardware device that provides the interconnection between networked devices. For Data Transmission, the hub is the machine running the HeartStart Telemedicine Server application. When you select Hub from the menu, the Hub screen is displayed, allowing you to configure the HeartStart Telemedicine Server machine URL in Table 14. Work with your ISP to ensure that these HeartStart MRx settings match the settings for the HeartStart Telemedicine Server computer. Table 14 Hub Settings Parameter Description Setting Choices Server URL Hub (HeartStart Telemedicine Server machine) address. up to 40 characters, blank Available from your ISP. For example, you could enter a domain name, such as www.example.com, or a static IP address, such as 192.168.111.1. HeartStart MRx adds the prefix http:\\ to the address, but it does not appear on the screen. User Name HTTP user name. up to 20 characters, blank Password HTTP password. up to 40 characters, blank NOTE: HeartStart Telemedicine does not require a user name and password because Data Transmission uses an anonymous (as opposed to authenticated) access. Configuring Sites A site is the final destination of a 12-Lead report. You can configure up to 20 sites on HeartStart MRx. When you select Sites from the menu, the Sites screen is displayed, allowing you to configure the parameters listed in Table 15. NOTE: In HeartStart Telemedicine, a “site” is called a “destination.” 1. Some HeartStart MRx documentation and this Data Transmission Implementation Guide refer to HeartStart Telemedicine as a hub. The term “hub”, as used in the documentation, refers to HeartStart Telemedicine as the central point of communication. 35 3: Setup and Configuration Table 15 Configuring the HeartStart MRx Site Settings Parameter Description Setting Choices Site Name This name appears in the Send To menu when initiating a transmission. The name should be easy to recognize. 12-20 characters, blank Site Type Indicates the end destination receiving the 12-Lead report. Fax, Printer, NOTE: All 12-Lead reports are sent through the hub, regardless of the site type you TraceMaster, 12LTS, Hub, HeartStart select. From the hub, 12-Lead reports can be forwarded to fax machines, printers, Telemedicine, TraceMaster systems, or other HeartStart Telemedicine applications. • Select Fax and enter the phone number, if you want to send the 12-Lead report to a single fax machine. If you want to send the 12-Lead report to multiple fax machines, you must also configure Auto Send Lists in HeartStart Telemedicine. See “Specifying Fax Destinations” on page 30. • Select Printer, if you want to send the 12-Lead report to a printer or multiple printers. The printer must be set up in the Windows operating system for the HeartStart Telemedicine Server machine. See “Specifying Printer Destinations” on page 30. • Select 12LTS and enter the URL, if you want to send the 12-Lead report to another 12-Lead Transfer Station. If you want to send the 12-Lead report to multiple 12-Lead Transfer Station applications, you must also configure Auto Send Lists in HeartStart Telemedicine. See “Specifying Application Destinations” on page 29. • Select Hub, if you want to send the 12-Lead report to the destinations on Auto Send Lists in HeartStart Telemedicine. If you use the Hub feature, then coordinate the Auto Send Lists content with the HeartStart Telemedicine system administrator. • Select Telemedicine and enter the URL, if you want to send the PCDT (12-Lead report, ECG, waveform, or vital trend) to another HeartStart Telemedicine. You can manually forward data from your HeartStart Telemedicine to another HeartStart Telemedicine. If you want to send the 12-Lead report to multiple HeartStart Telemedicine applications, you must also configure Auto Send Lists in HeartStart Telemedicine. See “Specifying Application Destinations” on page 29. Phone Number Phone number for fax site type, otherwise blank. URL URL for TraceMasterVue or another HeartStart Telemedicine. HeartStart MRx adds up to 30 characters, blank the prefix http:\\ to the address, but it does not appear on the screen. Use Hub’s Routing Reserved for future use. NOTE: Check the dialing rules for HeartStart Telemedicine. For example, does HeartStart Telemedicine need to dial a 9 for an outside line or an area code in addition to the number? If it does, the destination number must include these digits. Default Site If Yes, this will be the highlighted site when the Send To menu is displayed. When set to Yes, this field will automatically be set to No for all other sites. up to 20 characters, blank Yes, No Yes, No Adding and Deleting a Site To add a site: 1 36 From the Data Transmission Configuration menu, select Sites. A list of con1figured sites is displayed. If no sites are configured, then the Sites screen is displayed; proceed to Step 3. If fewer than 20 sites are configured, Add Sites appears on the menu. Configuring the Wireless Link 3: Setup and Configuration 2 Select Add Site. The Sites screen is displayed. 3 Enter the site information. See Table 15 “Site Settings” for more information. To delete a site: 1 From the Data Transmission Configuration menu, select Sites. A list of configured sites is displayed. 2 Select the site you want to delete. The site name menu is displayed with Delete Site near the top. 3 Select Delete Site and press the Menu Select button. The prompt Delete Site <>? is displayed. 4 Select Yes to delete the site. The selected site is deleted from the configuration. Configuring the Wireless Link Use the WL configuration utility described in this section to configure your WL for your specific connections. The WL configuration utility is pre-installed and is a part of the WL firmware. To configure the WL you need a Windows-operated PC. The configuration of the WL and its network connections requires the Windows Internet Explorer interface. Once your WL has been configured, your HeartStart MRx is ready to communicate with the HeartStart Telemedicine System. Configuring the HeartStart MRx for the Wireless Link To enable your HeartStart MRx to communicate through the WL, configure the following values: Data Transmission — Transmit Devices Bluetooth: Off (may remain On if you have Bluetooth installed and intend to use it in the Data Management mode) Wireless Link: On If both on in clinical mode use: Wireless Link Data Transmission — Wireless Link Access Point: Yes or No. This parameter determines whether the WL will operate in the Access Point Mode when your HeartStart MRx is in the Data Management mode. See “Wireless Link in the Access Point Mode” settings on page 45 to configure the WL AP settings. See “Data Transmission from a Moving Ambulance” on page 13 to determine when to use this setting. http Proxy Address: IP address, up to 15 characters http Proxy Port: IP address, up to 15 characters Wireless Link Address: 192.168.171.2 This address must match the WL static IP address as described in “Static IP” on page 48. If the WL static IP address is changed, then this address must change accordingly. 37 3: Setup and Configuration Configuring the Wireless Link Wireless Link System Prerequisites The WL system prerequisites and equipment required for the setup are listed in Table 16: Table 16 Wireless Link System Prerequisites Component Requirement HeartStart MRx Software Release HeartStart MRx Option (D01, D02, or D03) Internet Explorer browser a MS Windows® operating system b T.00 Wireless Link upgrade (860376-860378 or 860383-860385) installed XP, Vista, Windows 7 (32 and 64 bit), Windows 8 (32 and 64 bit) c Provided in the upgrade kit Provided by the customer Ethernet coupler Ethernet cable a. Browsers other than Internet Explorer or its older versions are not supported. b. Non-Windows and MS Windows 95, 98, ME, NT, and 2000 are not supported. c. Windows 8 may be incompatible with certain versions of other components, such as the HeartStart Data Messenger or HeartStart Telemedicine System. See also the WL Specifications in the HeartStart MRx Instructions for Use and effective addenda. Before You Begin Before you begin, ensure that: You have all the connection parameters for your WiFi and cellular connections handy. If you are not sure of these settings, contact your network administrator. Your computer runs MS Windows Vista, XP, 7, or 8 operating system. Your HeartStart MRx is turned to the Monitor mode and connected to your WL via the RS-232 cable. The WL can be powered by HeartStart MRx only. Your computer runs Windows Internet Explorer version 7 or above. Your WL is connected to your computer via the Ethernet cable. Use the coupler from your WL kit and your own Ethernet cable; do not strain the WL’s own Ethernet connector which is too short for a comfortable PC connection. Preparing Your Equipment Your HeartStart MRx supplies the operational power for your WL, and there are no other means to properly power the WL. Make sure the HeartStart MRx battery is fully charged or being charged. The WL does not work when your HeartStart MRx has a low battery because when the battery is low, only vital functionality directly related to patient care is available. Perform these steps prior to the implementation: 38 To prepare your equipment: 1 Start your computer system. 2 Turn your computer’s connection switch to the wired mode. Configuring the Wireless Link 3: Setup and Configuration 3 Set the computer’s LAN connection to a static IP address on the same subnet as the Wireless Link. (NOTE: If your computer is connected to a network, this step breaks the connection). a Navigate Start > Settings > Control Panel > Network Connections. b Right-click Wireless Network Connection and press Disable. c Right-click Local Area Connection and press Properties. d Under the General tab, select Internet Protocol (TCP/IP) and press Properties. e Check the Use the following IP address: radiobutton and enter 192.168.171.1 f Press Tab on the keyboard once. The Subnet mask gets filled: 255.255.255.0. g Leave the other fields blank and press OK. h Close the Local Area Connection Properties dialog box. 4 Use your Ethernet cable and coupler to extend the WL’s Ethernet Cable. 5 Connect the WL to your computer’s Ethernet port. 6 Connect the WL’s RS-232 cable to your HeartStart MRx. 7 Turn your HeartStart MRx to the Monitor mode. Wireless Link Initialization Perform the WL initialization by launching the WL for the first time. To Connect to the Wireless Link: 1 Open Internet Explorer. 2 Enter 192.168.171.2 in the URL field. The WL opens, and you are offered to login to the WL. If this IP address is reserved by another application, see “Static IP” on page 48 for using an alternative IP address. NOTE: If needed, you may change the first three octets of the IP address, see “Static IP” on page 48. 3 Enter your username admin and the password, also admin, and press OK to login to your Philips Wireless Link. See “Change Login Credentials” on page 50 if you wish to change your credentials later. 4 Press OK to enter the Welcome screen. Welcome Screen The Welcome screen has five selectable tabs on the left: Welcome (activated), Bridge/Router, Access Point, Advanced Settings, and Apply Changes, as shown in Figure 11. Here you can find the electronic Serial Number of the unit, the version of the Configurator utility, and the version of the Philips Wireless Link firmware. You may need this information if you call technical support in future. Figure 11 Welcome Screen 39 3: Setup and Configuration Configuring the Wireless Link Bridge/Router Mode This section describes how to set up regular WiFi and Cellular connections, where the HeartStart MRx with WL act as a WiFi or Cellular client. To access the Bridge/Router settings options, select the Bridge/Router tab on the left side of the Configurator. These settings determine the WiFi access points and cellular profiles that the WL will connect to. You can enter, edit, and test these settings of your WL, see Figure 12. Figure 12 Bridge/Router Settings CELL Creating Connections If you do not have any connections defined, then you must create a new connection; otherwise you may copy and edit an existing connection, see “Connection Management” on page 43. Import of existing configuration files is discussed in “Import/Export Settings” on page 46. TIP: Do not create more connections than necessary because this could affect connection time in clinical mode. The WL allows you to create up to 255 WiFi connections. However, in the start-up process the WL polls every configured connection until it finds a visible one, and each search for an unavailable or invisible connection delays the WL activation for several seconds. To create a new connection: Press the New WiFi button to create a WiFi connection (Bridge mode), see “New WiFi Connection” below. Press the New Cellular button to create a Cellular connection (Router mode), see “New Cellular Connection” on page 42. New WiFi Connection The New WiFi Connection dialog appears, see Figure 13. Enter the data and selections: • 40 Press the View Available Wireless Networks button to display a list of wireless networks in your vicinity. Use this list to configure your WL for an access to a wireless network within your range. Select a wireless network you wish to join from the displayed list of wireless networks. When you make your selection, the SSID Name reflects the name of your selected wireless network, and the authentication type is automatically selected. Configuring the Wireless Link 3: Setup and Configuration Figure 13 New WiFi Connection Settings • Connection Name field is up to 48 characters in length (no spaces or [;=‘%\”] characters allowed) and uniquely identifies and describes your connection. Give the connection a descriptive name that reflects its location and function. Avoid using the full allowed length of 48 characters when creating connections because, if the name of the new connection already exists, the configuration routine appends a digit in parentheses to the connection name to make it unique. For example, if you create three connections and specify the name EMS-A for each, the connections would be named EMS-A, EMS-A(1), and EMS-A(2). Other functions, like Copying Connections, also append characters to the Connection Name. • SSID Name is up to 48 characters in length (no spaces or [;=‘%\”] characters allowed) and identifies your Service Set Identifier (SSID). SSID is broadcasted from visible APs and automatically populated when you View Available Wireless Networks (see below). Alternatively, you can obtain SSID from the IT department managing APs at your institution. • SSID Visible option is typically selected because most 802.11 access points are visible. Deselect this option if the access point(s) you wish to connect to belong to a network that may use invisible SSIDs. • Authentication Type pull down list allows you to select the authentication method used by the access point you try to connect with. The available options are: WEP, WPA-PSK, and WPA2-PSK (default). If you conduct the setup in a WiFi access point vicinity, then the WL senses the WiFi presence and automatically populates the Authentication Type in the profile. Contact your IT department if you do not know which authentication type your institution uses. • Key field is required by the associated access point. – WEP-64 bit keys can be either exactly 5 arbitrary keyboard characters, or exactly 10 hexadecimal characters (0-9, a-f ). – WEP-128 bit keys can be either exactly 13 arbitrary keyboard characters, or exactly 26 hexadecimal characters (0-9, a-f ). – WPA-PSK or WPA2-PSK keys can be either 8-63 arbitrary keyboard characters, or exactly 64 hexadecimal characters (0-9, a-f ). After you have completed configuring your new WiFi connection, press the Save button, and then Apply Changes to save your work. Your configuration efforts may be lost if you do not apply changes. 41 3: Setup and Configuration Configuring the Wireless Link New Cellular Connection Before you create a Cellular Connection, you must obtain and activate a SIM card from your cellular service provider. If your WL has a pre-configured provider, then contact the provider to activate your WL. NOTE: You may configure only one cellular connection on your WL at any moment. To activate cellular service for your WL, you must provide the IMEI or MEID strings to your cellular service provider and, possibly, the SIM card ID if it is pre-loaded in the WL (the AT&T option). These strings are located on the label on the cardboard WL packaging. If you have more than a few WLs to activate, then you may peel off the labels from the cardboard box, stick them on paper, and fax to your cellular service provider. If the cardboard box cannot be located, the IMEI and MEID strings are repeated on the bottom of the WL box. See the WL Cable replacement instructions in the Repair chapter of the HeartStart MRx Service Manual for the instructions on opening the plastic housing. If you select a New Cellular Connection (see Figure 12 “Bridge/Router Settings” on page 40) then the New <Provider Code> Cellular Connection dialog appears, as shown in Figure 14. Figure 14 New Cellular Connection Enter the data and selections: 42 • The Select Cellular Provider pull-down box contains a list of some popular cellular service providers. Selection in this box loads the appropriate cellular profile for your cellular provider. If your cellular service provider is not listed: – select Verizon for Verizon. – select AT&T for AT&T. – for all other providers, select Rogers. Then verify and correct your credentials. (NOTE: In the CDMA environment, MEID identifies you to the network, and credentials are not necessary.) • Connection Name field is up to 48 characters in length (no spaces or [;=‘%\”] characters allowed) and uniquely identifies and describes your connection. Give the connection a descriptive name that reflects its location and function. If the name of the new connection already exists, the configuration routine appends a digit to the connection name to make it unique. • The Login Username string allows you to specify your login username if required in order to make a connection to your cellular network. The field length is limited to 64 arbitrary keyboard characters. Configuring the Wireless Link 3: Setup and Configuration • The Login Password string allows you to specify your login password if required in order to make a connection to your cellular network. The field length is limited to 64 arbitrary keyboard characters. • The APN String allows you to specify your cellular service provider’s Access Point Name if required in order to make a connection to your cellular network. Obtain this string from your service provider if it does not get populated automatically. After you have completed configuring your Cellular connection, press the Save button, and then Apply Changes to save your work. Your configuration efforts may be lost if you do not apply changes. After you have created one or more connections, perform a live connection test to determine whether your connections are functional, as described in “Connectivity Test” on page 65. Connection Management When you have created Wireless connections, you may need to manage these connections. You may prioritize, edit, delete, or copy your existing connections, or create new connections using the buttons shown in Figure 15. Figure 15 Connection Management CELL Prioritizing Connections Prioritizing your connections permits you to define the order in which you select wireless networks for joining. This feature is useful if you have multiple access points available within the same vicinity, however you only wish to join with a select network. Prioritizing your connections allows you customize the preference order in which you join the available wireless networks. TIP: Philips recommends that you assign the lowest priority to the cellular connection (if applicable). To prioritize your connections: 1 Select the Bridge/Router tab on the left side of the Configurator. 2 Select a connection for which you wish to change priority. 3 Press the Higher button to increase the priority, or press Lower button to decrease the priority. 4 Press the Save button. 5 If you have finished your connection management session, then press the Apply Changes button. 43 3: Setup and Configuration Configuring the Wireless Link Editing Connections When you edit an existing connection, you may alter any parameter, except the Connection Type. That is, you cannot change a WiFi connection to a Cellular one or back. To edit a connection: 1 Select the Bridge/Router tab on the left side of the Configurator. 2 Select the connection you wish to edit. 3 Press the Edit button. If you have selected a WiFi connection, then the Edit WiFi Connection screen appears, as in Figure 16. Figure 16 Editing WiFi Connection If you have selected a Cellular connection, then the Edit <Provider Code> Cellular Connection screen appears, as in Figure 17. You cannot change the cellular service provider by editing; if necessary, delete the connection and re-create it, selecting a new connection type or cellular service provider. Figure 17 Editing Cellular Connection 4 Edit any of the user-alterable parameters. 5 Press the Save button. If you have finished your connection management session, then press Save, and then Apply Changes buttons. 44 Configuring the Wireless Link 3: Setup and Configuration Copying Connections Only the WiFi connections may be copied, since your WL configuration may have no more than one cellular connection. To copy a connection: 1 Select a connection you wish to copy. 2 Press the Copy button. The Configurator copies your selected connection and appends “_Copy” to the end of the new connection name. NOTE: The Connection Name field is limited to 48 characters in length, therefore the original name must be no longer than 43 characters to allow for the five additional characters. If the resulting name exceeds 48 characters, then the message Sorry, but that connection could not be copied is displayed. 3 Press the Save button. If you have finished your connection management session, then press the Apply Changes button. Wireless Link in the Access Point Mode Depending on your communications requirements, the WL can operate as a WiFi client (Bridge), Cellular (Router), or an Access Point (AP). The AP mode allows you to send event summaries from your HeartStart MRx directly to your computer locally using your WL. Activate the AP mode through the HeartStart MRx Data Transmission — Wireless Link configuration parameter, see “Configuring the HeartStart MRx for the Wireless Link” on page 37. The WL in AP mode can transfer data only if the PC is running HeartStart Data Messenger. NOTE: Up to eight WiFi clients can connect to the WL at one time. If a client makes an attempt to connect when eight other clients are already connected, it would be rejected. To access the AP settings options, select the Access Point tab on the left side of the Configurator, as shown in Figure 18: Figure 18 Access Point Settings Options 45 3: Setup and Configuration Configuring the Wireless Link Access Point Settings The wireless client setup must be predefined and cannot be a result of a wireless network scan. To enter the Access Point Settings options: 1 Enter the Access Point Settings options, a SSID Name is up to 32 characters in length (no spaces or [;=‘%\”] characters allowed) and is broadcasted for others during a WiFi scan. Your default SSID is Wireless Link WHxxxxxxxx, where WHxxxxxxxx is the WL’s serial number listed on the WL cardboard package and on the back label of the WL metal box. b SSID Visible box is checked by default to enable SSID visibility, therefore your WL AP is detectable by a WiFi scan. Uncheck this box if you wish to make the access point invisible to external WiFi scans, and to prevent the WL from broadcasting its SSID. c Authentication Type pull down list allows you to select the authentication method for the AP. The selections are WEP, WPA-PSK, and WPA2-PSK. The default selection is WPA2-PSK. Contact your IT department for instructions on your institution requirements. d Key: By default, your AP’s key is accessmrx. If necessary, change the key according to your institution requirements. – WEP-64 bit passkeys can be either exactly any 5 keyboard characters, or exactly 10 hexadecimal characters. – WEP-128bit passkeys can be either exactly any 13 keyboard characters, or exactly 26 hexadecimal characters. – WPA-PSK or WPA2-PSK passkeys can be 8-63 keyboard characters. e Cipher type defines the encryption being used. The selections are TKIP, AES, and TKIP+AES. Leave this option at the default value (AES) unless instructed otherwise. f Wireless Channel allows you to select the Wireless Channel for the AP use. The values range from 1 to 11, with 6 as the default. 2 If you have finished your connection management session, then press Apply Changes. NOTE: If you or your IT team plans to change default SSID Name or Key, please convey this information to the end user. Advanced Settings To access the Advanced Settings options: On the left side of the Configurator, press the Advanced Settings tab. There are six sub-options of the Advanced Settings: • Import/Export Settings, • Restore Factory Settings, • Static IP, • Debug Log, • Power-Up Mode, and • Other. Import/Export Settings The Import/Export functionality allows you to save WL configurations to your hard drive to simplify configuration of a group of WLs and to restore your saved configurations back to your WL. 46 Configuring the Wireless Link To import a previously saved WL configuration file: 1 Press the Import/Export Settings button under the Advanced Settings tab. 2 Press the Browse button as shown in Figure 19. 3 Navigate to the configuration file you wish to import and press the Open button. 4 Press the Import button. Figure 19 5 3: Setup and Configuration Import/Export Dialog Press Apply Changes to apply the imported configuration. To export your WL configuration file to your PC: 1 Press the Export button as shown in Figure 19. 2 Navigate to the desired location on your PC and press the Save button. Restore Factory Settings You may restore the factory settings to start your configuration fresh. Adhere to the on-screen cautions. You will have to import a saved configuration or create a new one manually. To restore your WL configuration factory settings: 1 Press the Restore Factory Settings button under the Advanced Settings tab. 2 Confirm or cancel your action when prompted. 3 Press Apply Changes to apply the restored configuration. This method works only if you are logged into the WL Configurator. There is also a possibility to reset the factory settings if you forget or lose your WL password and cannot login. To reset your WL configuration factory settings without login: 1 Connect the WL’s Ethernet Cable to your computer’s Ethernet port. 2 Open Internet Explorer. 3 Enter 192.168.171.2/reset in the URL field. This URL opens to a dialog box. 4 Press OK to confirm your intention to reset the WL. The Configurator opens, and you are offered to login to the Configurator. 47 3: Setup and Configuration Configuring the Wireless Link 5 Enter the username reset and the password, also reset, and press OK. 6 Observe the Reset Complete screen. Static IP You may view and enter an alternate IP Address and Subnet Mask for your WL network interface. By default, your WL static IP address is 192.168.171.2. In the rare instance of the 192.168.171.x subnet being used in your network, you may change it here, for example, to 192.168.100.2, as shown in Figure 20. Figure 20 Static IP Dialog To view or change your Static IP: 1 Press the Static IP button under the Advanced Settings tab. 2 View or alter the IP Address and / or Subnet Mask settings. Make sure the static IP defined on your Windows system is on the same subnet as the WL, otherwise you will not be able to log back in. 3 Press the Apply button to apply the altered static IP. 4 Press OK to confirm the change. The WL reboots. 5 Change the Wireless Link Address HeartStart MRx configuration parameter accordingly, see “Configuring the HeartStart MRx for the Wireless Link” on page 37. 6 Login to the WL again. NOTE: If you forget the static IP that you had redefined, the WL broadcasts its configured Static IP at each cold boot. 1 Debug Log See the “Debug Log” section on pg. 66 of the “Testing and Troubleshooting” chapter. Power-Up Mode The WL can operate as a WiFi (Bridge) / Cellular (Router) (see “Bridge/Router Mode” on page 40) or as an Access Point (see “Wireless Link in the Access Point Mode” on page 45), depending on your communications requirements. Using the Power-Up Mode dialog, you may select the mode of operation at power up. By default, the WL powers up to the Bridge / Router mode. 1. Your IT department may be able to help you detect these broadcasts by connecting your WL to a PC that is running an Ethernet protocol analyzing and filtering software on the MAC address of your WL. During its initialization, the WL transmits three “Gratuitous ARP” messages that contain the device’s current static IP address. 48 Configuring the Wireless Link 3: Setup and Configuration To set the Power-Up Mode: 1 Select Power-Up Mode under the Advanced Settings tab. Figure 21 Power-Up Mode 2 Enable the desired mode at power up. 3 Press Apply Changes to activate and save the configuration. Other Advanced Settings The Other functionality offers the options to perform your WL firmware upgrade or change your login credentials. Figure 22 Other Advanced Settings Firmware Upgrade Upgrade your WL firmware when advised by your Philips support or sales representative. To perform a firmware upgrade: 1 Export the configuration data that you wish to save. The upgrade process erases the configuration data on your WL. CAUTION: 2 Download the firmware upgrade package file to your computer. 3 Initialize the router as directed in “Wireless Link Initialization” on page 39. 4 Navigate to Advanced Settings > Other. 5 Press the Perform Firmware Upgrade button. 49 3: Setup and Configuration 6 Configuring the Wireless Link Adhere to the CAUTION messages on the screen, see Figure 23. Note that for some time you will not be able to use your HeartStart MRx, WL, or Internet. Press the link at the bottom of the screen to return if you are not sure you are ready to proceed. Figure 23 Other Advanced Settings 7 Use the Browse dialog to locate the firmware upgrade package file. 8 Press the OK button to proceed. Do not disconnect the WL from either HeartStart MRx or the computer, or close or refresh the Internet Explorer Window during the upgrade process. A progress bar is displayed during the upgrade. Once the upgrade has completed, you must reconfigure your WL for further use, because all configuration information was erased. You may use the link at the bottom of the screen to return to the configuration screen. Change Login Credentials Change your login credentials from the factory defaults to enhance security according to your health care institution security protocols. To change your login credentials: 1 Enter the new Username. Use any keyboard characters for your Username and Password, except [='] and space. 2 Enter the new Password for your new Username. 3 Re-enter your Password. 4 Press Update to apply your new Username and Password. Use your new username and password the next time you login to the WL or access the Status Page (see “Status Page” on page 66). Connecting Wireless Link After you have finished the configuration and testing activities, connect your WL to your HeartStart MRx as described in the “Connecting Wireless Link” section of your HeartStart MRx Instructions for Use or its Wireless Link Addendum. NOTE: Reboot your HeartStart MRx after you switch to another or reconfigured WL. 50 Configuring a Bluetooth Device 3: Setup and Configuration Configuring a Bluetooth Device This topic provides instructions for configuring profiles for Bluetooth devices. Phone/Modem Profiles let you set the characteristics for the Bluetooth device you are using. The first time you select Phone/Modem Profiles, the Add Profile menu is displayed. Once you have configured Bluetooth devices, a list of up to ten configured Bluetooth profile names is displayed. When you select Data Transmission from the Main Configuration menu, the menu shown in Figure 24 is displayed if you purchased the Bluetooth option. NOTE: Add and pair Bluetooth devices and change profiles from the 12-Lead menu. See “Setting Up the Cell Phone for Bluetooth Device” on page 53 for more information. Figure 24 Bluetooth and Modem Data Transmission Configuration Menu Data Transmission Adding a Bluetooth Profile To add a Bluetooth profile: 1 From the Configuration menu, press the Menu Select button. 2 Use the Navigation buttons to select Data Transmission. 3 From the Data Transmission menu, select Phone/Modem Profiles. 4 From the Phone/Modem Profiles menu, select Add Profile. PP The first time you select Phone/Modem Profiles, the Add Profile menu is displayed automatically. 5 Enter the appropriate information, referring to Table 17. Remember to select Done from the menu after you have entered each parameter before moving on to the next one. 51 3: Setup and Configuration Table 17 Configuring a Bluetooth Device Phone and Modem Profile Settings Parameter Description Profile Name Name of the profile. Associate the profile name with the Auto Send List up to 20 characters, blank name (see “Understanding Auto Send Lists” on page 28). Configuration String Available from your cell phone service provider. up to 45 characters, blank Landline Set to “Yes” if you are using a modem. Yes, No Dial Prefix Only configurable if Landline is set to “Yes”. The dial prefix is the up to 10 characters, blank number or numbers you dial before the phone number. For example, you may need to dial a 9 for an outside line or an area code in addition to the number. Dial String Available from your cell phone service provider. Wait for Dial Tone User Name / Password Config Setting Choices up to 40 characters, blank Yes, No Available from your cell phone service provider. Per Profile – use to associate a user name and password with this profile. Per Profile, Per Device Per Device – use to associate a different user name and password for every device that uses this profile. PPP User Name Typically not needed, but may be required by some cell phone service providers. PPP Password Static IP Address up to 20 characters, blank up to 40 characters, blank 15 characters (nnn.nnn.nnn.nnn), blank Primary DNS Secondary DNS http Proxy Address 15 characters, blank http Proxy Port Figure 25 on page 53 shows a typical setting of Phone/Modem profile configuration. Deleting a Bluetooth Profile 52 To delete a Bluetooth profile: 1 From the Phone/Modem Profiles menu, select the profile you want to delete. 2 Select Delete Profile and acknowledge the confirmation prompt. Configuring a Bluetooth Device Figure 25 3: Setup and Configuration Phone/Modem Profile Configuration Menu Setting Up the Cell Phone for Bluetooth Device There is a number of ways in which the HeartStart MRx can transmit data to the Internet via Bluetooth and an intermediary device (see Figure 1 on page 4). Each of the methods have different configuration requirements (see below), but all of them must: Support the Bluetooth wireless technology version 1.1 or greater standard. Cellular Handset or Ambulance Broadband Gateway with an Air Card To send data through a simple cellular phone or ambulance broadband gateway with an air card, your device must: Have a data plan that supports tethered data (i.e., use the phone as a modem for a PC, contact your cellular service provider for details). Support Bluetooth Dial Up Networking (DUN) profile. PC or Windows Mobile-based Smartphone for Forwarding to Internet PC must have an air card or Smartphone must have an Internet data plan. Must support Bluetooth FTP Server (HeartStart MRx initiates file push to the receiving device). Bluetooth-to-Landline Modem This method allows HeartStart MRx to send data through an analog phone line or a business fax line. Must have a dial-up Internet service plan 53 3: Setup and Configuration Configuring a Bluetooth Device Bluetooth Device Transmission Range The class of a Bluetooth device is a definition of the maximum range of transmission. HeartStart MRx is a Bluetooth Class I device. This means that it is possible for the HeartStart MRx to communicate with a Bluetooth device within a maximum distance of 100 meters (300 feet). However, the maximum communication distance between two Bluetooth devices depends upon the device with the lowest class. See the your Bluetooth device’s documentation for more information on Bluetooth classes. Additional Bluetooth Device Information Keep the following points in mind when working with Bluetooth devices: • Many Bluetooth devices are not discoverable by default. Check your device’s documentation to see if you need to enable discovery. • As a general security practice, you should not leave your Bluetooth device in discovery mode. • Some devices require that you turn on the Bluetooth functionality. • Some devices may prompt you to authorize each time. Check your device’s documentation to see if you can configure it to always communicate with HeartStart MRx. • Give your Bluetooth device an easily recognizable name as this is the name that appears on HeartStart MRx menus. The name should be no more than 15 characters in order to display properly on HeartStart MRx. • Bluetooth modems and fax machines use analog lines to transmit data. If you are transmitting using a Bluetooth modem, plug it into the analog line used by the fax machine. Adding Bluetooth Devices to the HeartStart MRx Up to 20 Bluetooth devices can be configured for use. Adding a twenty-first device replaces the device used least recently. You cannot add or modify Bluetooth devices during 12-Lead transmission. Similarly, you cannot transmit a 12-Lead report during Bluetooth device configuration. To add a Bluetooth device to HeartStart MRx: 1 Press the 12-Lead soft key to enter the 12-Lead Mode, as shown in Figure 26: Figure 26 Entering 12-Lead Mode 2 From the 12-Lead Main Menu, select Bluetooth Devices. 3 Select Add Device and press the Menu Select button. 4 The message Searching for Bluetooth devices is displayed. If the message No Bluetooth Profiles Configured is displayed, then see “Configuring a Bluetooth Device” on page 51. 5 From the Add Device menu, select the desired device. 6 Pair the device with the HeartStart MRx, as described in the next topic. NOTE: Bluetooth devices within the specified range are discovered by HeartStart MRx and are displayed on the Add Device menu, even if you have already paired with the device. If the device you are searching for does not appear on the Add Device list, select Search Again. 54 Configuring a Bluetooth Device 3: Setup and Configuration Pairing a Bluetooth Device with HeartStart MRx After you have added a Bluetooth device to the HeartStart MRx, you are prompted to enter a passkey to pair (also called bonding on some devices) the Bluetooth device with the HeartStart MRx. The passkey is a user-defined character sequence, such as 000, or 1234, etc. You must ensure that you enter the same passkey on both the Bluetooth device and HeartStart MRx. If you are pairing with a Bluetooth modem, refer to the device’s documentation to determine the passkey you should enter. TIP: Some Bluetooth devices only allow pairing for 30 seconds, so be ready to enter the passkey. To pair a Bluetooth device with the HeartStart MRx: 1 Use the Navigation buttons to enter the passkey on the HeartStart MRx and select Done. The Bluetooth device prompts you for a passkey. 2 Enter the same passkey on your Bluetooth device. See the documentation that came with your Bluetooth device for instructions. Once the Bluetooth device has been paired with the HeartStart MRx, you are prompted to select a profile. See “Bluetooth Profile” below. Bluetooth Profile After you have paired the Bluetooth device with the HeartStart MRx, a list of configured profiles is displayed. Select the profile you want to use with that Bluetooth device to transmit the 12-Lead report. To select a Bluetooth profile: 1 Use the Navigation buttons to select the profile from the list of configured profiles. The HeartStart MRx tests the profile to determine if the Bluetooth device can communicate with HeartStart Telemedicine. 2 If your HeartStart MRx is enabled for both Dial-up Network (DUN) and File Transfer profiles (FTP), make an appropriate selection when prompted. 3 Progress messages, such as: Transmission Test, Connecting to Device, Dialing..., Connecting to Network, and Connecting to Server are displayed during the testing. If the test passes, the message Transmission Test Passed is displayed. If the test fails, the message Transmission Test Failed is displayed along with additional information on where the failure occurred. Refer to Table 26 on page 79 to troubleshoot. No files are transferred during the test. NOTE: To change a Bluetooth profile: 1 From the 12-Lead menu, select Bluetooth Devices. A list of paired Bluetooth devices is displayed. 2 Use the Menu Select button to select a device. 3 Select Change Profile. A list of configured profiles is displayed, with the currently associated profile highlighted. 4 Select the profile you want to use with that Bluetooth device to transmit 12-Lead report. The HeartStart MRx tests the profile to determine if the Bluetooth device can communicate with HeartStart Telemedicine. 55 3: Setup and Configuration 5 NOTE: Configuring Data Messenger Progress messages, such as: Transmission Test, Connecting to Device, Dialing..., Connecting to Network, and Connecting to Server are displayed during the testing. If the test passes, the message Transmission Test Passed is displayed. If the test fails, the message Transmission Test Failed is displayed along with additional information on where the failure occurred. Refer to Table 26 on page 79 to troubleshoot. No files are transferred during the test. Configuring Data Messenger For the Data Messenger installation and configuration instructions, refer to the HeartStart Data Messenger User Guide. For the Data Messenger installation and configuration instructions for the Wireless Link, refer to the “Batch LAN data transfer for MRx patient data” section of the HeartStart Data Management Solutions Implementation Guide. 56 4 Testing and Troubleshooting Overview This chapter provides information on testing and troubleshooting the Data Transmission option. This chapter covers the following topics: Troubleshooting the Wireless Link . . . . . . . . . . . . . . p. 57 . . . . . . . . . . . p. 59 Wireless Link Troubleshooting Flowcharts and Tables . . . . . . . . . p. 61 Wireless Link Computerized Diagnostics Testing Wireless Link Data Transmission Testing Data Transmission . . . . . . . . . . . . . p. 65 . . . . . . . . . . . . . p. 68 . . . . . . . . . . . . . p. 73 Viewing the HeartStart MRx Logs . . . . . . . . . . . . . p. 73 Viewing the HeartStart Telemedicine System Log . . . . . . . . . . p. 74 HeartStart Telemedicine Troubleshooting Table . . . . . . . . . . p. 75 Testing and Troubleshooting Bluetooth Devices . . . . . . . . . . p. 79 Transmission Activity Logs and Tables Troubleshooting the Accessories Customer Support . . . . . . . . . . . . . . . . . p. 82 . . . . . . . . . . . . . . p. 83 Troubleshooting the Wireless Link Philips recommends the following sequential approach to isolate and resolve the problems with your WL functioning and performance: 1 Check the WL lights and icons as described in the “Wireless Link Indicators” on page 58. 2 Make sure the WL is positioned in its pouch as described in the “Connecting Wireless Link” section of your HeartStart MRx Instructions for Use or its Wireless Link Addendum. 3 Perform the Op. Check. If the WL section of the Op. Check report indicates Fail/Check Cables and Module, then check for the WL connections with the HeartStart MRx’ Ethernet and RS-232 ports. 4 If the problem is not resolved, start troubleshooting as suggested in the “Wireless Link Troubleshooting Flowcharts and Tables” on page 61. 5 Check the HeartStart MRx Network Status Log entries. See “Wireless Link Network Status Log Entries” on page 74. 6 As applicable, consult the “PCDT Troubleshooting” section of the “Networking and Data Transfer” chapter of the HeartStart MRx Service Manual for possible PCDT problems. 7 As applicable, consult the “Device Status Log Messages” section of the “Troubleshooting” chapter of the HeartStart MRx Service Manual for possible 12-Lead transmission problems. 57 4: Testing and Troubleshooting Troubleshooting the Wireless Link 8 If the problem is not resolved, then disconnect the WL Ethernet cable from the HeartStart MRx, connect it to a computer, and: a Perform the Connectivity Test as described in “Connectivity Test” on page 65. b Examine the WL status as described in “Status Page” on page 66. c Examine the Debug Log as described in “Debug Log” on page 66. 9 Have the HeartStart MRx Network Log, WL Status Page, and Debug Log handy before contacting Philips customer support, see “Customer Support” on page 83. Wireless Link Indicators WL indicators consist of the connectivity icons located on the HeartStart MRx screen and lights located on the face of the WL router. Wireless Link Lights WL lights shown in Figure 27 and described in Table 18 indicate the momentary state of the WL router: Figure 27 Table 18 Icon Wireless Link Lights Wireless Link Lights Interpretation Letters a Description Light Status CEL WF Cellular status WiFi signal strength HeartStart MRx WL Status Steady light Connection actively ready for data transmission Long flashes No service or not authenticated / registered Short flashes Searching for subscribed network No light Cellular connection absent or inactive. Steady light WiFi signal is strong Long flashes WiFi signal is weak Short flashes WiFi signal is acceptable No light No WiFi connection or WiFi not active RUN Run indicator Steady light The WL is in the B/R mode Flashing The WL is in the AP mode PWR Power Indicator Steady light Power is on No light Power is off Flashing Data transfer in process ETH Ethernet Indicator No light • Ethernet cable disconnected • Transition in progress b a. The icons are painted on the WL door. If the WL door is removed, then the letters become visible on the internal WL front wall. b. The Ethernet Indicator goes off for a few seconds when the WL makes an network transition. 58 Troubleshooting the Wireless Link 4: Testing and Troubleshooting Wireless Link Connectivity Icons During PCDT, WL connectivity icons indicate whether the WL is transmitting data. Table 19 Icon Wireless Link Connectivity Icons Description HeartStart MRx WL Status No icon A transmission has not been initiated. White icon A transmission has been initiated. Green icon The WL is currently transmitting data. Crossed icon • A transmission has been initiated, but the WL is not ready yet. • The WL started a transmission, but the connection failed. Wireless Link Inop Messages Inop messages appear on the cyan background in the upper left corner of the HeartStart MRx screen, as shown in Figure 28: Figure 28 HeartStart MRx Inop Location 31 Dec Mark Event Inop location Table 20 Inop Wireless Link Unplugged Adult HeartStart MRx Wireless-Link-Related Inops Possible Cause Suggested Solution Wireless Link The WL has detected a • Turn your HeartStart MRx off for 10 seconds and restart. Disabled: DoS “denial of service” data • Contact your IT professional. attack and turned off. WL is not connected to the HeartStart MRx Wireless Link A failure in the WL Unplugged device or its cable • Check that RS-232 and Ethernet connections are secure. • Turn your HeartStart MRx off for 10 sec. and restart. Wait until the WL completes its startup process to be recognized by the HeartStart MRx, and for the Inop to disappear. • Check that RS-232 and Ethernet connections are secure. • If the WL power light is off, or the cable looks damaged, then replace the cable assembly. • If the WL power light is on, and the cable looks intact, then replace the WL. Testing Wireless Link Data Transmission Once all of the pieces of the Data Transmission option are installed and configured, you can test it by manually send data from the HeartStart MRx to HeartStart Telemedicine using a WL. It tests the following components: – HeartStart MRx and the WL are configured correctly. – HeartStart Telemedicine can receive HeartStart MRx data. 59 4: Testing and Troubleshooting 60 Troubleshooting the Wireless Link To send 12-Lead data from the clinical mode during an event: 1 Confirm the HeartStart MRx is in the 12-Lead mode for 12-Lead transfer. 2 Use a simulator to acquire a 12-Lead report or acquire a blank 12-Lead report if no simulator is available. See HeartStart MRx Instructions for Use for instructions on acquiring 12-Lead reports. 3 Press the Menu Select button. 4 Using the Navigation buttons, select Send 12-Lead and press the Menu Select button. 5 Using the Navigation buttons, select the Telemedicine destination (Site Name) for the data. Press the Menu Select button. 6 Watch the messages on the HeartStart MRx screen. 7 Confirm that the data were sent to the designated HeartStart Telemedicine Server. If not, begin troubleshooting as directed in “Wireless Link Troubleshooting Flowcharts and Tables” on page 61. To send PCDT from the clinical mode during an event: 1 Confirm the HeartStart MRx is in Clinical mode for PCDT. 2 Use a simulator to acquire a 12-Lead report or acquire a blank 12-Lead report if no simulator is available. See HeartStart MRx Instructions for Use for instructions on acquiring 12-Lead reports. 3 Press the Menu Select button. 4 Using the Navigation buttons, select Start Data Transmit and press the Menu Select button. 5 From the Send To menu, select a destination and press the Menu Select button. 6 From the Transmission Devices menu, select the transmission device and press the Menu Select button. The PCDT icon appears on the display and transmission begins. 7 Confirm that the data were sent to the designated HeartStart Telemedicine Server. If not, begin troubleshooting as directed in “Wireless Link Troubleshooting Flowcharts and Tables” on page 61. Troubleshooting the Wireless Link 4: Testing and Troubleshooting Wireless Link Troubleshooting Flowcharts and Tables Wireless Link Troubleshooting Flowcharts for BLDT Use the troubleshooting flowcharts in conjunction with the Tables 21-20 and other tools described below. Figure 29 WL BLDT in Bridge / Router Mode Troubleshooting Flowchart Turn off the MRx Check the cables Check WL positioning Check MRx battery charged to 40% + Reboot the MRx Enter Data Mgmt mode No WL Power LED on? Yes Wait 90 sec. MRx shows BLDT menu? No Not Steady Make sure: - PC runs Data Msgr. - FTP server accessible - PC and MRx on the same subnet - No firewall or antivirus SW blocks transmission Move closer to the transmitter Yes WL Run LED steady? Steady Steady WL WiFi LED steady? Not Steady No Are you within the WiFi network? Yes Resolve config mismatch Ensure WiFi priority higher than Cell No WL config correct? Yes No Did you reboot more than twice? Yes Have the MRx Network Log, WL Status Page, and Debug Log ready. Call Philips Service center. No Config test passed? Yes Run Op.Check Place device in service 61 4: Testing and Troubleshooting Figure 30 Troubleshooting the Wireless Link WL BLDT in Access Point Mode Troubleshooting Flowchart Turn off the MRx Check the cables Check WL positioning Check MRx battery charged to 40% + Reboot the MRx Enter DM mode No WL Power LED on? Yes Wait 90 sec. MRx shows BLDT menu? No Off Yes WL Run LED state? Blinks Solid Set AP mode to Yes No Run Op.Check Place device in service MRx AP mode configured to Yes? Yes Make sure: - PC runs DM - FTP server runs - No more than 8 WiFi clients Verify DM FTP connection as directed in Setting up batch LAN data transfer for the MRx in the HeartStart Data Messenger User Guide No Resolve config. mismatch Passed? Yes Configure to the same subnet Resolve authentication problems Did you reboot more than No twice? 62 Yes No MRx and PC on the same subnet? Yes PC connected to WL AP? No No Success? Yes Have the MRx Network Log, WL Status Page, and Debug Log ready. Call Philips Service center. Connect to AP Yes Troubleshooting the Wireless Link 4: Testing and Troubleshooting Wireless Link Transmission Problems Table 21 discusses general problems that can occur during data transmission with WL: Table 21 Wireless Link General Transmission Problems Symptom Possible Causes Suggested Solution WL is not connected • Check that RS-232 and Ethernet connections are secure. to the MRx • Turn your MRx off for 10 seconds and restart. Wait until the WL completes its startup process to be recognized by the MRx. The Power light The battery charge • Connect the MRx to the DC or AC power source. is below 40% • Replace the battery with a fully charged one. is off A failure in the WL • Check that RS-232 and Ethernet connections are secure. device or its cable • Replace the cable assembly. • Replace the WL. WL is not connected • Verify the WL Ethernet cable is connected to the PC’s to the PC Ethernet port using extension cord and a coupler. Unable to access WL from PC • Verify the PC runs a supported browser listed in Table 16 “Wireless Link System Prerequisites” on page 38. Wrong IP settings • Verify the PC runs a Static IP address on the same subnet as the WL, see “Static IP” on page 48. • Capture the ARP broadcast of the WL during its boot process. WL is not connected • Verify the WL Ethernet cable is connected to the MRx to MRx Ethernet port. • Observe the HeartStart MRx WL-related Inops, see Table 20 on page 59. Unable to access WL from MRx Wrong static IP settings The Ethernet light is off Verify the MRx settings for the WL match the assigned static IP. WL is not connected • If the Power light is off, then troubleshoot the Power light, see to MRx above. • Verify the Ethernet cable is connected to the MRx Ethernet port securely, and the locking tab is engaged. Cellular transmission stops Cellular LED flashes fast SIM card is dislodged • Reset the SIM card. • Make sure the SIM card door is snug. • Advise the paramedics to monitor the SIM card position when the device is subjected to strong vibration. 63 4: Testing and Troubleshooting Troubleshooting the Wireless Link Table 22 discusses problems that can occur during data transmission in the WiFi mode: Table 22 Wireless Link WiFi Transmission Problems Possible Causes Suggested Solution • Verify AP is within the range of the WL. Unable to associate • Verify WiFi connection settings match (SSID, Authentication, Passkey, etc.) with the AP. • Rule out Signal / Channel congestion. • Perform connectivity test, see “Connectivity Test” on page 65. Unable to find Verify AP is within the range of the WL during the WiFi scan. appropriate APs NOTE: The WL displays only the APs that are visible and employ WEP, during a WiFi scan WPA-PSK, or WPA2-PSK encryption. MRx is unable to transmit • Verify WiFi light indicates a WiFi connection has been established, and the WiFi signal is strong or acceptable. • Verify MRx configuration is set to the correct WL IP address and destination Telemedicine Server IP address. Table 23 discusses problems that can occur during data transmission in the cellular mode: Table 23 Symptom Wireless Link Cellular Transmission Problems Possible Causes Cellular • Unable to status light connect to the flashes fast cellular service provider Cellular transmissio • SIM card is dislodged n stops Suggested Solution • Verify a proper cellular connection for your service provider has been created and data service activated. • Rule out technical difficulties or network congestion on the cellular service provider’s side. • As applicable, verify the SIM card is inserted properly and SIM card door is closed snugly. If dislodged, advise the operators to monitor the SIM card position when subjected to strong vibration. • Observe the Cellular light to verify the signal strength is sufficient. Cellular Verify the MRx configuration is set to the correct WL IP address and HeartStart MRx is status light destination Telemedicine Server IP address. unable to transmit flashes slow Table 24 discusses problems that can occur during data transmission in the AP mode: Table 24 Wireless Link Access Point Transmission Problems Possible Causes Suggested Solution Wireless clients cannot • Check the WL AP settings. See “Access Point Settings” on page 46. see the WL AP during • Verify the WL AP is set to visible (the SSID Visible option is enabled). a WiFi scan • Verify client is within range of the WL AP. • Verify AP connection settings match (SSID, Authentication, Passkey, etc.) Wireless clients cannot • Verify SSID was not altered on the WL. associate with the WL • Verify there are no multiple WL APs with the same SSID. AP NOTE: The WL can have no more than eight simultaneously connected wireless clients. 64 Troubleshooting the Wireless Link 4: Testing and Troubleshooting Wireless Link Computerized Diagnostics The following tests require that you disconnect your WL’s Ethernet cable from the HeartStart MRx and connect it to your computer. Connectivity Test After you have created one or more connections as described in “Creating Connections” on page 40, test the connections function. To test a single connection: 1 Select the connection you wish to test, see Figure 31. 2 Click the Perform a Connection Test button. Figure 31 Connectivity Test To test multiple connections: 1 Do not select any connection to test. 2 Press the Perform a Connection Test button. The WL tests through the connections list starting with the first connection until it finds a functional connection or gets to the bottom of the list. The test stops as soon as a functional connection is found. As the connections are tested, an intermediate progress summary shows the results of the various test stages, as shown in Figure 32. 3 If the test takes longer than expected, press the Abort button to terminate the connection test and start troubleshooting, see “Troubleshooting the Wireless Link” on page 57. Figure 32 Connectivity Test in Progress 65 4: Testing and Troubleshooting Troubleshooting the Wireless Link Debug Log The Debug Log is used for WL troubleshooting. You can review, delete, or export the debug log. Access the Debug Log through the “Advanced Settings” menu. See Figure 33 for a Debug Log dialog sample: Figure 33 Debug Log Dialog If you call Philips Customer Support, they may ask you for the content of your Debug Log, therefore it is a good practice to export the Debug Log before deletion. Do not delete the Debug Log until you have resolved all configuration issues. The Debug Log size is 100 Kilobytes, or about 1500 log entries. Once this limit is reached, the WL overwrites the oldest entries. Status Page The WL Status Page provides diagnostic and statistical data on the WL operations. The data displayed depend on the current connection mode: WiFi, Cellular, or Access Point. Access the WL Status Page if asked by a Philips representative while troubleshooting. To access the WL Status Page: 1 Launch your Internet Explorer. 2 Follow the http://192.168.171.2/status URL to access the status page. 3 If required, enter your username and the password and click OK to login to your WL. If you already have logged into the WL configuration utility in another instance of your web browser, then login is not required. The WL Status Page is displayed. The Refresh Rate defines how often the Status Page information is updated. You can adjust the refresh rate: the default rate is 30 seconds, and you can change it to 10, 20, or 60 seconds, see Figure 34. Depending on your access mode, your WL Status Page may contain different sections: Ethernet, WiFi, Cellular, and Access Point. Status Page Ethernet Section Figure 34 presents an example of the Ethernet section; this section presents on every Status Page, regardless of the access mode. Some of the Status Page parameters are explained below. MAC Address is the electronic hardware address of the Ethernet interface. This address is in hexadecimal format, and is unique to each WL. The MAC address can also be found on the WL router body when the plastic housing is removed. Statistics data lists the received and transmitted packet details and the number of bytes transferred: 66 • The RX string include the number of packets received, the number of errors, the number of overruns, and the frame. • The TX string include the number of packets transmitted, the number of errors, the number of overruns, the carrier, the number of packet collisions, and the size of the transmit queue length. Troubleshooting the Wireless Link 4: Testing and Troubleshooting These statistics are accumulated while the WL remains powered on. During a power cycle, the statistics reset to zero. Figure 34 Ethernet Status Page Section Status Page WiFi Section The WiFi section of the Status Page (see Figure 35) is visible only if an active WiFi connection is present and lists additional parameters: Signal Strength values are always negative. The values of -90 and below indicate poor signal strength, the values -70 and above are considered good, and the values in between are fair. Figure 35 WiFi Status Page Section Status Page Cellular Section The Cellular section of the Status Page (see Figure 36) is visible only if an active cellular connection is present and lists the following additional parameters: IMEI stands for the International Mobile Station Equipment Identity. This number is unique and is used by GSM and UMTS cellular providers to identify the cellular radio. The IMEI identifies the device and has no relation to the subscriber. MEID is the Mobile Equipment Identifier. This number is unique and identifies CDMA radios. Registration State indicates the registration with the service provided to the device. The possible values are: Not Registered, Registered, Searching, Denied, and Unknown. Provider Name identifies the cellular service provider you have connected to. This field may be empty if the WL is roaming and not on its home cellular network. RAN stands the Radio Access Network and indicates the radio-access technology for the cellular network you are connecting to. The possible values are: cdma2000, UMTS, or Unknown. Radio Interface indicates the base radio interface being used. The possible values are: CDMA 1xRTT, CDMA 1xEV-DO, GSM, and UMTS. 67 4: Testing and Troubleshooting Testing Data Transmission Data Bearer indicates the cellular technology used for this connection. This value depends on the Radio Interface and on the cellular tower characteristics in the current coverage area. The possible values are: CDMA 1xRTT, CDMA 1xEV-DO, EDGE, GPRS, ‘HSDPA DL, HSUPA UL’, ‘HSDPA DL, WCDMA UL’, WCDMA, ‘WCDMA DL, HSUPA UL’, or Unknown. Signal Strength values are always negative: –90 and below — poor signal strength, –89 - –71 — fair signal strength, –70 and above — good signal strength. Figure 36 Cellular Status Page Section Testing Data Transmission Once all of the pieces of the Data Transmission option are installed and configured, you can test the entire Data Transmission option using the follow scenarios. • Scenario 1 — From a HeartStart MRx, manually send a 12-Lead report to HeartStart Telemedicine using a WL or cell phone. This tests the following components: – HeartStart MRx and the WL or cell phone are configured correctly – HeartStart Telemedicine can receive HeartStart MRx data Use WL or Bluetooth wireless technology instead of cell phones for in-hospital deployments in proximity to the HeartStart MRx devices. NOTE: • Scenario 2 — From HeartStart Telemedicine manually forward a 12-Lead report to a fax machine. This tests that HeartStart Telemedicine and the Windows fax component are installed and configured correctly. • Scenario 3 — From a HeartStart MRx, send a 12-Lead report from HeartStart MRx to a HeartStart MRx-designated fax machine. This tests the following components: – – – 68 HeartStart Telemedicine and the Windows fax component are installed and configured correctly HeartStart MRx and the WL or cell phone are configured correctly HeartStart MRx can communicate with HeartStart Telemedicine Testing Data Transmission 4: Testing and Troubleshooting • Scenario 4 — From a HeartStart MRx, send a 12-Lead report to multiple destinations all at once. This tests the following components: – HeartStart Telemedicine and the Windows fax component are installed and configured correctly – HeartStart Telemedicine default Auto Send List is configured correctly • Scenario 5 — From a HeartStart MRx, send patient periodic clinical data to HeartStart Telemedicine. This tests the following components: – HeartStart MRx PCDT option – HeartStart Telemedicine Critical Care Edition Scenario 1 – Manually send a 12-Lead report from HeartStart MRx to HeartStart Telemedicine using a WL or cell phone 1 From the HeartStart MRx, send a 12-Lead report to HeartStart Telemedicine Server. Use a simulator to acquire a 12-Lead report. See HeartStart MRx Instructions for Use for information on acquiring 12-Lead reports. a Upon acquisition of the 12-Lead ECG, HeartStart MRx displays the 12-Lead report view. b Press the Menu Select button. c Select Send from 12-Lead Main Menu and press the Menu Select button. d Select Site Name from the list of configured sites. e Press the Menu Select button to complete the selection. f Select the device from the Transmission Devices menu. g Monitor the messages on the HeartStart MRx screen. 2 Confirm that the 12-Lead report was sent to the designated HeartStart Telemedicine Server. If not, begin troubleshooting. Troubleshooting when HeartStart MRx fails to send a 12-Lead report or a PCDT to a designated HeartStart Telemedicine 1 Check the HeartStart MRx screen and status log for error messages. If an error message appears, use Table 25 on page 75 and, for WL, Tables 21 – 24 on pages 63 – 64 for WL to understand and correct the problem. 2 Did you enter the HeartStart Telemedicine Server machine URL correctly from the HeartStart MRx? Confirm that the URL was entered correctly on the HeartStart MRx. 3 Did HeartStart Telemedicine receive the file? To confirm that HeartStart Telemedicine received the file: a Click the Patients navigation button. b On the Patients navigation pane, click View All Patients or View Latest Patient. For more information, see the “View All Patients” and “Viewing Patient Detail” topics in HeartStart Telemedicine System User Guide. c Depending on your choice in Step b: – On the View All Patients workspace, double-click the 12-Lead Report, or Trigger Events, or Vital Trends, or specific PCDT, or – On the View Latest Patient workspace, click the 12-Lead Report, or Trigger Events, or Vital Trends, or specific PCDT. d Verify that a corresponding report is displayed on the respective pane. For more information, see the “Viewing Patient Detail” topic in HeartStart Telemedicine System User Guide. e Click the Administration navigation button. f On the Administration navigation pane, click System Log to use the system log. The log should display an information message indicating that the 12-Lead transmission was saved. g If the 12-Lead report was received, check to see if there are error messages for the transmission. See HeartStart Telemedicine System User Guide to understand and correct the problem. 69 4: Testing and Troubleshooting Testing Data Transmission 4 Confirm that HeartStart Telemedicine Server machine is installed at the HeartStart MRx receiving end. Type in the following URL in the browser: http://<IP address or domain name>/ems/MRxtest.mrx?SourceName=test If you see the “HeartStart Telemedicine” window shown in Figure 10 on page 25, the operating system, IIS, and HeartStart Telemedicine are installed correctly. If this window does not appear, make sure that IIS is running. If not, restart IIS or check the IIS log to make sure it is configured properly. 5 Confirm that HeartStart Telemedicine is running: a From the Windows Start menu, click All Programs. b Then click Philips HeartStart Telemedicine System 4.2. c Next, click Telemedicine. For more information, see HeartStart Telemedicine System User Guide. Scenario 2 – Manually send a 12-Lead report from HeartStart Telemedicine to a fax machine 1 Start HeartStart Telemedicine. 2 Click the Patients navigation button. 3 Use one of the following methods to select a 12-Lead report: – Display the View All Patients workspace. For more information, see the “Viewing All Patients” topic in HeartStart Telemedicine System User Guide. – Display the View Patient workspace. For more information, see the topic “Viewing Patient Transmission Details” topic in HeartStart Telemedicine System User Guide. 4 If you are using the View All Patients workspace, select a patient record and click the Expand button to the left of the row. 5 Select a 12-Lead transmission. 6 On the File menu, click Fax 12-Lead. HeartStart Telemedicine might display the Send Fax Wizard window. Follow the on-screen instructions. Troubleshooting when a 12-Lead report fails to fax: 1 Is the fax set up in Windows Fax Console and ready to receive? – Confirm that the fax is set up in Windows Fax Console. – Confirm that the fax number of retries and amount of time between retries is a low number, such as 2 and 0. – Confirm that paper orientation of the fax service is set to Landscape orientation. – Confirm with the receiving site that the fax is ready to receive. – Confirm that the fax is plugged in and has paper. 2 Follow Microsoft Windows Fax troubleshooting procedures for additional information. Scenario 3 – Sending a 12-Lead report to a HeartStart MRx-designated fax machine 1 70 From the HeartStart MRx, send a 12-Lead report to the designated fax. Use a simulator to acquire a 12-Lead report. See HeartStart MRx Instructions for Use for guidance on acquiring 12-Lead reports. a Upon acquisition of the 12-Lead ECG, the 12-Lead report View is displayed. b Press the Menu Select button. c Select Send from 12-Lead Main Menu and press the Menu Select button. d Select Fax as the Site Type. e Enter the fax number. f Press the Menu Select button to complete the selection. g If you are transmitting using a Bluetooth phone or modem, select the device from the Transmission Devices menu. Testing Data Transmission 2 4: Testing and Troubleshooting Confirm that the 12-Lead report was sent to the designated fax machine. If not, begin troubleshooting. Troubleshooting when a 12-Lead report fails to fax to a HeartStart MRx-designated fax 1 Check the HeartStart MRx screen and status log for error messages. If an error message appears, use Table 26 “Bluetooth Transmission Messages” on page 79 for Bluetooth and, for WL, Tables 21 – 24 on pages 63 – 64 to understand and correct the problem. 2 Did you enter the fax number correctly from the HeartStart MRx? Confirm that the fax number was entered correctly on HeartStart MRx, using the dialing rules for HeartStart Telemedicine. For example, you may need to dial a 9 for an outside line or an area code in addition to the number. 3 Did HeartStart Telemedicine receive the file? To confirm that HeartStart Telemedicine received the file: a Click the Patients navigation button. b On the Patients navigation pane, click View All Patients or View Latest Patient. For more information, see the “View All Patients” and “Viewing Patient Detail” topic in HeartStart Telemedicine System User Guide. c Depending on your choice in Step b, perform one of the following steps: – On the View All Patients workspace, double-click the 12-Lead report, – On the View Latest Patient workspace, click the 12-Lead report d Verify that a 12-Lead report displays on the 12-Lead pane. For more information, see the “Viewing Patient Detail” topic in HeartStart Telemedicine System User Guide. e Click the Administration navigation button. f On the Administration navigation pane, click System Log to use the system log. The log should display an information message indicating that the 12-Lead transmission was saved. g If the 12-Lead report was received, check to see if there are error message for the transmission. See HeartStart Telemedicine System User Guide to understand and correct the problem. 4 Confirm the HeartStart Telemedicine installation. Type in the following URL in the browser: http://<IP address or domain name>/ems/MRxtest.mrx?SourceName=test If you see the “HeartStart Telemedicine” window shown in Figure 10 on page 25, the operating system, IIS, and HeartStart Telemedicine are installed correctly. If this window does not appear, make sure that IIS is running. If not, restart IIS or check the IIS log to make sure it is configured properly. 5 Make sure that the HeartStart Telemedicine software is running. The automatic services provided by HeartStart Telemedicine might be active while the application is running and did not restart automatically. If the HeartStart Telemedicine Server machine restarts, you must restart the HeartStart Telemedicine application. a From the Windows Start menu, click All Programs. b Click Philips HeartStart Telemedicine System 4.2. c Click Telemedicine. For more information, see HeartStart Telemedicine System User Guide. 6 Is the fax set up in the Windows Fax Console and ready to receive? – Confirm that the fax is set up in Windows Fax Console. – Confirm that the fax number of retries and time between retries is a low number, such as 2 and 0. – Confirm that paper orientation of the fax service is set to Landscape orientation. 71 4: Testing and Troubleshooting – – Testing Data Transmission Confirm with the receiving site that the fax is ready to receive. Confirm that the fax is plugged in and has paper. Scenario 4 – Sending a 12-Lead report to multiple fax machines 1 On the Administration navigation pane, click Fax Destinations. 2 Configure fax destinations. For more information, see the “Setting Up Fax Destinations” topic in HeartStart Telemedicine System User Guide. 3 Assign fax destinations to an Auto Send List in HeartStart Telemedicine. a On the HeartStart Telemedicine navigation pane, click Administration. b On the Administration navigation pane, click Auto Send Lists. c In Destinations, select the name for the fax machine. For more information, see the “Sending 12-Lead reports to Fax Machines” topic in HeartStart Telemedicine System User Guide. 4 Send a 12-Lead report from the HeartStart MRx to the designated fax through an Auto Send List. Use a simulator to acquire a 12-Lead report. See HeartStart MRx Instructions for Use for information on acquiring 12-Lead reports. Upon acquisition of the 12-lead ECG, the 12-Lead report View is displayed. a Press the Menu Select button. b Select Send from the 12-Lead Main Menu and press the Menu Select button. c Select Fax as the Site Type. d Enter the fax number. e Press the Menu Select button to complete the selection. f If you are transmitting using a Bluetooth device, select the device from the Transmission Devices menu. 5 Confirm that the 12-Lead report was sent to the designated fax machine and the fax machines on the Auto Send List. If not, begin troubleshooting. Troubleshooting when a 12-Lead report fails to fax to multiple fax machines 1 Check the HeartStart MRx screen for error messages. If an error message appears, use Table 26 “Bluetooth Transmission Messages” on page 79 to understand and correct the problem. 2 Are there any fax destinations in the Auto Send List? a On the HeartStart Telemedicine navigation pane, click Administration. b On the Administration navigation pane, click Auto Send Lists. c In Destinations, is the fax machine listed? If not, create a fax destination using the fax number. For more information, see the “Setting Up Fax Destinations” topic in HeartStart Telemedicine System User Guide. d In Destinations, is there a check mark next to the fax machine? For more information, see the “Creating an Auto Send List” topic in HeartStart Telemedicine System User Guide. 3 Follow the steps of “Troubleshooting when a 12-Lead report fails to fax to a HeartStart MRx-designated fax” on page 71 to complete the troubleshooting. Scenario 5 – Sending Patient PCDT to HeartStart Telemedicine (if the HeartStart MRx is enabled with PCDT, and the HeartStart Telemedicine uses the Critical Care edition) 72 Transmission Activity Logs and Tables 4: Testing and Troubleshooting Introduction of PCDT and the Critical Care Edition of HeartStart Telemedicine make possible to send more data more often for more types of critical care patients. It also introduces a new use model, where clinical users may monitor inbound patients on a display screen rather than view printer or fax output. This live monitored use model means that the viewer client software runs on a nurses workstation rather than in the IT server room. 1 From theHeartStart MRx, configure a HeartStart Telemedicine application as a site. For more information, see the “Setting Up Application Destinations” topic in HeartStart Telemedicine System User Guide. 2 Send a patient transmission that includes one or more PCDT to HeartStart Telemedicine. 3 Confirm that the stream of data transmissions was sent to the designated HeartStart Telemedicine application. If not, begin troubleshooting. The data can include 12-Lead reports, event waveforms, or vital trends. Troubleshooting when a PCDT fails to be sent to a HeartStart Telemedicine 1 Follow the steps in “Troubleshooting when HeartStart MRx fails to send a 12-Lead report or a PCDT to a designated HeartStart Telemedicine” on page 69. 2 Follow the “Periodic Clinical Data Transmission” recommendations of the HeartStart MRx Service Manual to complete the troubleshooting. Transmission Activity Logs and Tables HeartStart MRx, Wireless Link, and Telemedicine maintain logs that register transmission and other activities. These logs may help you and Philips Customer Support to troubleshoot your transmissions. Viewing the HeartStart MRx Logs WARNING: The HeartStart MRx should never be connected to a patient while performing any activities in Service Mode. NOTE: Make sure that you insert a battery charged to at least 20% into the device or connect external power when you are performing functions in Service Mode. To view the HeartStart MRx Status Logs: 1 Access Service Mode: a Turn the Therapy Knob to Monitor. b Press the Menu Select button to display the Main menu. c Select Other. d From the Other menu select Service. The message Leaving Normal Operating Mode. Patient Monitoring Is Off. To Return To Normal Operating Mode, Press The Exit Softkey. appears. e Press the Menu Select button to acknowledge the message. You are prompted to enter a password. f Enter the password (27689) by scrolling through the list until the desired number is highlighted. 2 From the Service Mode Main menu, select Status Log and press the Menu Select button. 73 4: Testing and Troubleshooting Transmission Activity Logs and Tables 3 To view the device status log, select Device Status Log from the Status Log menu, and press the Menu Select button. Press the Print Log soft key to print the log. 4 To view the PCDT status log, select Network Log from the Status Log menu, and press the Menu Select button. Wireless Link Network Status Log Entries The WL writes messages to the Network Status Log. See the “PCDT Connectivity Problems” section of the “Networking and Data Transfer” chapter of the HeartStart MRx Service Manual. Troubleshooting Tables The tables in this topic provide information on messages and common troubleshooting issues for HeartStart MRx. For information on how to use the system log, see HeartStart Telemedicine System User Guide. Table 26 provides information on the Bluetooth messages that are displayed on HeartStart MRx and in the Status log. These messages can occur during the Bluetooth device testing phase as well as during transmission of 12-Lead reports. Errors that occur during the testing phase include the word “Test” in the message. For example, Transmission Test Failed. Cannot Reach Server is displayed when the HeartStart MRx is testing the connection. The possible causes and solutions are the same for both testing and normal operation. Table 25 provides information on the messages that are displayed on HeartStart Telemedicine system log. These messages can occur while using the HeartStart Telemedicine software. Viewing the HeartStart Telemedicine System Log To view the HeartStart Telemedicine system log: 1 On the navigation pane, click the Administration navigation button. 2 On the Administration navigation pane, click System Log. HeartStart Telemedicine displays the system log. A screen similar to the one shown on Figure 37 appears. For information on how to use the system log, see the “Working with the System Log” topic in HeartStart Telemedicine System User Guide. Figure 37 74 HeartStart Telemedicine System Log Screen Transmission Activity Logs and Tables 4: Testing and Troubleshooting HeartStart Telemedicine Troubleshooting Table HeartStart Telemedicine displays messages on the system log. Table 25 lists the messages that you might see while using the HeartStart Telemedicine software. The possible issues and solutions are the same for both testing and normal operations. Table 25 HeartStart Telemedicine Messages Log Type Action Description Possible Issues and Solutions Info Delete patient record Delete patient record Deleted patient record for Patient ID: {Incident ID} Failed to delete patient record for Patient ID: {Incident ID} All received data for the patient was successfully deleted. Delete request failed. Possible reasons: • Database connection failure • Another user might have already deleted the patient record Info Email 12-Lead Error Email 12-Lead Emailed 12-Lead report for Patient ID: {Incident ID} with recorded time: {date and time} to email address: {email address}, file name: {file name} Failed to email 12-Lead for Patient ID: {Incident ID} with recorded time: {date and time} to email address: {email address}, file name: {file name} Info Email trigger event report Error Email trigger event report Info Email patient record Error Email patient record Email vital trends report Error Info Error Email vital trends report Info Export trigger event report Click Refresh. The 12-Lead report was successfully sent to the email queue. Check the queue for the email client or the SMTP server for blocked transmissions. Invalid 12-Lead report. Possible reasons: • SMTP is not set up • Invalid 12-Lead data • Missing Incident ID • Missing acquired date and time Emailed trigger event report for Patient ID: The trigger event report was successfully sent to {Incident ID}, transmission ID: {Transmission the email queue. Check the queue for the email ID}, file name: {file name} client or the SMTP server for blocked transmissions. Failed to email trigger event report for The email client or SMTP server is not set up. Patient ID: {Incident ID}, transmission ID: {Transmission ID}, file name: {file name} Emailed patient report for Patient ID: The patient report was successfully sent to the {Incident ID}, file name: {file name} email queue. Check the queue for the email client or SMTP server for blocked transmissions. Failed to email patient report for Patient ID: The email client or SMTP server is not set up. {Incident ID}, file name: {file name} Emailed vital trends report for Patient ID: The patient vital trends report was successfully {Incident ID}, transmission ID: {Transmission sent to the email queue. Check the queue for ID}, file name: {file name} the email client or the SMTP server for blocked transmissions. Failed to email Vital trends report for Patient The email client or SMTP server is not set up. ID: {Incident ID}, transmission ID: {Transmission ID}, file name: {file name} Exported trigger event report. Patient ID: The trigger event report successfully saved in {Incident ID} transmission ID: {transmission PDF format. ID}, file name: {file name} 75 4: Testing and Troubleshooting Transmission Activity Logs and Tables Table 25 HeartStart Telemedicine Messages (Continued) Log Type Action Error Export Failed to export patient report for Patient ID: Possible reasons for failure might be: patient report {Incident ID}, file name: c • Patient report failed to save. • The disk is full. • The path is no longer available. • The path does not have write permission. Export trigger Exported trigger event report for Patient ID: The trigger event report was successfully saved event report {Incident ID} transmission ID: {transmission in PDF format. ID}, file name: {file name} Export trigger Failed to export trigger event report for Possible reasons for failure might be: event report Patient ID: {Incident ID}, transmission ID: • The trigger event report failed to save. {transmission ID}, file name: {file name} • The disk is full. • The path is no longer available. • The path does not have write permission. Export vital Exported vital trends report for Patient ID: Successfully saved the patient vital trends report trends report {Incident ID}, transmission ID: {Transmission in PDF format. ID}, file name: {file name} Export vital Failed to export vital trends report for Patient Possible reasons for failure might be: trends report ID: {Incident ID}, transmission ID: • The disk is full. {Transmission ID}, file name: {file name} • The path is no longer available. • The path does not have write permission. Fax 12-Lead Faxed 12-Lead for Patient ID: {Incident ID} The 12-Lead report was successfully sent to the with recorded time: {date and time} to fax FAX queue. Check the queue in FAX Console number: {Fax number} for blocked transmissions. Fax 12-Lead Failed to fax for Patient ID: {Incident ID} Invalid 12-Lead data. Possible reasons for with recorded time: {date and time} to fax failure might be: number: {Fax number} • Missing Incident ID • Missing acquired date and time Print 12-Lead Printed 12-Lead for Patient ID: {Incident ID} The 12-Lead report was successfully sent to the with recorded time: {date and time} to printer printer queue. Check the queue for blocked name: {printer name} printer jobs. Print 12-Lead Failed to print 12-Lead for Patient ID: Invalid 12-Lead data. Possible reasons for {Incident ID} with recorded time: {date and failure might be: time} to printer name: {printer name} • Missing Incident ID • Missing acquired date and time Print patient Printed patient report for Patient ID: The patient report was successfully sent to the report {Incident ID} to printer name: {printer name} printer queue. Check the queue for blocked printer jobs. Print patient Failed to print patient report for Patient ID: Possible reasons for failure might be: report {Incident ID} to printer name: {printer name} • Invalid patient data • Missing Incident ID Print trigger Printed trigger event report for Patient ID: The trigger event report was successfully sent to event report {Incident ID}, transmission ID: {Transmission the printer queue. Check the queue for blocked ID} to printer name: {printer name} printer jobs. Info Error Info Error Info Error Info Error Info Error Info 76 Description Possible Issues and Solutions Transmission Activity Logs and Tables Table 25 HeartStart Telemedicine Messages (Continued) Log Type Action Error Print trigger event report Info Error Info Error Error Error Info Error Error Info Error Description Failed to print trigger event report for Patient ID: {Incident ID}, transmission ID: {Transmission ID} to printer name: {printer name} Print vitals Printed vitals trend report for Patient ID: trend report {Incident ID}, transmission ID: {Transmission ID} to printer name: {printer name} Print vitals Failed to print vitals trend report for Patient trend report ID: {Incident ID}, transmission ID: {Transmission ID} to printer name: {printer name} Save 12-Lead Saved 12-Lead for Patient ID: {Incident ID} with recorded time: {Date and time} imported from {Source} file name: {File name} 4: Testing and Troubleshooting Possible Issues and Solutions Possible reasons for failure might be: • Invalid patient data • Missing Incident ID The patient vital trends report was successfully sent to the printer queue. Check the queue for blocked printer jobs. Possible reasons for failure might be: • Invalid patient vitals data • Missing Incident ID The 12-Lead report was successfully saved to database. NOTE: HS TM uses Incident ID, Patient ID and acquired date / time to identify a duplicate ECG. If the 12-Lead reports are duplicates, the newly arrived report overwrites the older report. Save 12-Lead Failed to save 12-Lead. Missing Patient ID: Possible reasons for failure might be: {Incident ID}, imported from file name: {File • The 12-Lead report is invalid. name} • The report is missing an Incident ID. NOTE: All MRx 12-Lead reports contain a valid Incident ID, but the reports from other devices might not. Incident ID is required field for use in HeartStart Telemedicine. Save 12-Lead Failed to save 12-Lead. Missing recorded Possible reasons for failure might be: time: {Data and time} imported from file • The 12-Lead report is invalid. name: {File name} • The 12-Lead or missing the date and time that 12-Lead report was acquired. Save patient Failed to save the periodic clinical data HeartStart Telemedicine Classic 12-Lead data transmission. Edition does not support PCDT. Save trigger Saved trigger event for Patient ID: {Incident The trigger event and associated ECG were event ID}, transmission ID: {Transmission ID} successfully saved to database. Save trigger Failed to save trigger event for Patient ID: Possible reasons for failure might be: event {Incident ID}, transmission ID: {Transmission • The trigger event might be corrupted. ID} • The trigger event is missing the Incident ID or Transmission ID. Save trigger Failed to save trigger event, unsupported The trigger event might be generated from event MRx version: {version number} imported HeartStart MRx version that is not supported from file name: {File name} by HeartStart Telemedicine System. Save vital Saved vital for Patient ID: {Incident ID}, The patient vitals were successfully saved to the transmission ID: {Transmission ID} database. Save vital Failed to save vital for Incident ID: {Incident Possible reasons for failure might be: ID}, transmission ID: {Transmission ID} • The patient vitals might be corrupted. • The patient record might be missing the Incident ID or Transmission ID. 77 4: Testing and Troubleshooting Table 25 HeartStart Telemedicine Messages (Continued) Log Type Action Info Send 12-Lead Sent 12-Lead for Patient ID: {Incident ID} with recorded time: {Date and Time} to application name: {folder name} Send 12-Lead Failed to send 12-Lead for Patient ID: {Incident ID} with recorded time: {Date and Time} to application name: {folder name} Error Info Error Description Send 12-Lead Sent 12-Lead for Patient ID: {Incident ID} with recorded time: {Date and Time} to application name: {URL} Send 12-Lead Failed to connect to application name: {URL} for Patient ID: {Incident ID} with recorded time: {Date and Time} Transmission Activity Logs and Tables Possible Issues and Solutions The 12-Lead report was successfully saved to the destination folder. Possible reasons for failure might be: • The disk is full. • The target folder is not accessible or does not have write permission. The 12-Lead report was sent successfully to the destination URL. Possible reasons for failure might be: • The sender cannot access the internet. • The dest. URL is not ready to receive data. • If dest. is either HS 12-Lead Transfer Station or HS Telemedicine, check the test page: http://<DN>/ems/MRxPost.mrx?SourceName=test Error Info Error where <DN> is the destination URL. If the image shows, the destination is ready. Send 12-Lead Rejected by application name: {URL} for Possible reasons for failure might be: Patient ID: {Incident ID} with recorded time: • TraceMasterVue rejected the 12-Lead report {Date and Time} because the schema validation failed. • Updated TraceMasterVue software might be required to support newer report schema. Send patient Sent patient data for Patient ID: Successfully sent patient data to another Event data {Incident ID} to application name: {URL} Review 3.5 Send patient Failed to send patient data for Patient ID: Possible reasons for failure might be: data {Incident ID} to application name: {URL} • The sender cannot access the internet. • The destination is not ready to receive data. • Check the test page: http://<DN>/ems/MRxPost.mrx?SourceName=test Info Info Info Info 78 Start Event Review BT Monitor Stop Event Review BT Monitor Start Event Review Service Mgr. Stop Event Review Service Mgr. Started Event Review Bluetooth Monitor where <DN> is the destination URL. If image shows, the destination is ready. Event Review successfully started Event Review Bluetooth Monitor. Stopped Event Review Bluetooth Monitor Event Review successfully stopped Event Review Bluetooth Monitor. Started Event Review Service Manager Windows successfully started Event Review Service Manager. Stopped Event Review Service Manager Windows successfully stopped Event Review Service Manager. Transmission Activity Logs and Tables 4: Testing and Troubleshooting Table 25 HeartStart Telemedicine Messages (Continued) Log Type Action Info Start Started PDTSInboxMonitor PDTSInbox Monitor StopPDTSIn Stopped PDTSInboxMonitor boxMonitor Info Description Possible Issues and Solutions Event Review or Windows successfully started PDTSInboxMonitor. Event Review or Windows successfully stopped PDTSInboxMonitor. Testing and Troubleshooting Bluetooth Devices After you have added and paired a Bluetooth device to the HeartStart MRx and selected a profile, the HeartStart MRx checks that it can communicate with the Bluetooth device, connect to the network, and connect to the HeartStart Telemedicine. This test occurs automatically whenever you change a profile for the Bluetooth device. To manually test a profile of a previously paired Bluetooth device: 1 From the HeartStart MRx 12-Lead menu, select Bluetooth Devices. A list of configured Bluetooth devices is displayed. 2 Use the Menu Select button to select a Bluetooth device. 3 Select Change Profile. A menu of configured profiles for that Bluetooth device is displayed, with the currently associated profile highlighted. 4 Select the profile you want the Bluetooth device to use to transmit 12-Lead reports. HeartStart MRx tests the profile to determine if the Bluetooth device can communicate with HeartStart Telemedicine. Progress messages, such as Transmission Test, Connecting to Device, Connecting to Network, Dialing, and Connecting to Server are displayed during the testing. If the test completes successfully, the message Transmission Test Passed is displayed. If the test fails, the message Transmission Test Failed is displayed, along with more detailed information on the failure. See Table 26 “Bluetooth Transmission Messages” on page 79 for messages and suggested solutions. NOTE: No files are transferred during the test. Bluetooth Troubleshooting Table Table 26 Bluetooth Transmission Messages User Message Network Status Log Entry Possible Cause Suggested Solution BLUETOOTH DEVICE No/Bad Bluetooth Card Bluetooth Malfunction Not available at this time HeartStart MRx does not have a Bluetooth card. Bluetooth Communication • Incompatible BT card. Failure • Corrupt BT card. None You cannot perform multiple actions with the BT card. E.g., you cannot pair while transmitting a 12-Lead report. Check to see if the BT card is installed in the PCMCIA slot. See the Service Manual. Replace the Bluetooth card. Use Philips Bluetooth cards only. Wait until one action is complete before starting another. 79 4: Testing and Troubleshooting Table 26 Transmission Activity Logs and Tables Bluetooth Transmission Messages (Continued) User Message Network Status Log Entry Possible Cause Suggested Solution BLUETOOTH DEVICE DISCOVERY No Bluetooth • No Bluetooth Profiles – Profiles 12LXmit Config Configured • No Bluetooth Devices – 12LXmit Device No Bluetooth Devices None Detected There are no profiles configured for the Bluetooth device. Create a profile for the Bluetooth device. See “Configuring a Bluetooth Device” on page 51 for more information. MRx could not discover the Bluetooth device. The BT device is turned off The Bluetooth device is not authorized to pair with the HeartStart MRx. The Bluetooth device is not within range. Try searching again for Bluetooth devices. Make sure the BT device is turned on. See the Bluetooth device’s documentation to set authorization. Move the BT device closer to the MRx, within the transmitting range. See “Configuring a Bluetooth Device”. The Bluetooth card is corrupt. Replace the Bluetooth card. BLUETOOTH DEVICE PAIRING Bluetooth Device Pairing None. Failed The wrong pass key was entered on the BT device. The pairing process timed out. The Bluetooth card is corrupt. Check the pass key. Select the device from the MRx Add Devices list and pair again. Try pairing again. Replace the Bluetooth card. SENDING Transmission Settings Have Not Been Configured No Bluetooth Devices Configured Missing settings – 12LXmit Config The Hub information settings Modify the Hub Configuration settings on are not correct. HeartStart MRx as needed. No Bluetooth Devices – 12LXmit Device The Bluetooth device has not been paired with MRx. Pair the Bluetooth device with HeartStart MRx. The BT device is turned off. Make sure the BT device is turned on. CONNECTING TO DEVICE No response – 12LXmit Device No transmission devices detected Transmission Failed. Error configuring transmission device 80 The Bluetooth device is not within range. Connection failed – 12LXmit Device Configure Failed – 12LXmit Device Move the BT device closer to the MRx, within the transmitting range. See “Configuring a Bluetooth Device”. The Bluetooth device is not See the Bluetooth device’s documentation authorized to pair with MRx. to set authorization. The Bluetooth pairing Pair the Bluetooth device with information has been lost. HeartStart MRx. The Bluetooth card is corrupt. Replace the Bluetooth card. The wrong Bluetooth Profile Check the profile to ensure it is the correct was selected. one for that Bluetooth device. The Configuration String Work with your cell phone provider to under the Phone Profile correct the Configuration String. settings is not correct. Transmission Activity Logs and Tables Table 26 4: Testing and Troubleshooting Bluetooth Transmission Messages (Continued) User Message Network Status Log Entry Possible Cause Suggested Solution Bluetooth Bluetooth Connection Lost Connection – 12LXmit Device Lost (occurs at any phase) Vary PCDT connection to Bluetooth Device for DUN or FTP transmission failed: status code nn The Bluetooth device is not within range. Move the Bluetooth device closer to HeartStart MRx, within the transmitting range. (See “Configuring a Bluetooth Device” on page 51.) • Make sure the Bluetooth device is activated. • Replace the Bluetooth device. Failure to connect to Bluetooth Device DIALING Transmission No Dial tone – 12LXmit Failed. Dialing No Dial Tone Transmission Failed. Connection Failed • Connect Failed – 12LXmit Dialing • Disconnect Failed – 12LXmit Dialing Cell phone service is unavailable. The Bluetooth modem connection is not secure. The connection you are using does not provide dial tones. Check that the cellular signal strength is sufficient. Check that the connection between the BT modem and analog line is secure. Set the Wait for Dial Tone configuration parameter to No. See the “Configuring a Bluetooth Device” on page 51. A wrong Bluetooth Profile Check the profile to ensure it is the correct selected. one for that Bluetooth device. The Dial string (Phone Profile Work with your cell phone provider to settings) is incorrect. ensure that the Dial string is correct. Data transfer service is Ensure that your cell phone plan has data unavailable on the phone. transfer capability. Wrong number. Check the number and re-send. CONNECTING TO NETWORK Invalid Password The wrong Bluetooth Profile was selected. User/pw failure – 12LXmit The PPP User Name or PPP Network Password under the Profile Phone settings is incorrect. User/pw failure – 12LXmit The server User Name or Server Password is incorrect. Check the profile to ensure it is the correct one for that Bluetooth device. Modify the Phone Profile setting as needed. Modify the Hub settings as needed. CONNECTING TO SERVER Transmission Failed. Cannot Reach Server Transmission Failed. Server unknown Transmission Failed. Settings Configured Incorrectly Unreachable – 12LXmit Server No server or the connection has been lost. Re-send the 12-Lead report. DNS query failure – 12LXmit Server The DNS has timed out or a failure in the DNS. Work with your ISP to ensure the Serial Phone Profile and Hub settings are correct. • Bad URL Format – 12LXmit Server There is a problem with the Work with your ISP to ensure the Phone Server URL, Proxy user name, • Bad proxy settings – ... Profile and Hub settings are correct. • Bad user/pw settings – ... Proxy password 81 4: Testing and Troubleshooting Table 26 Troubleshooting the Accessories Bluetooth Transmission Messages (Continued) User Message Network Status Log Entry Response message not received Unable to connect to the destination server None Possible Cause Suggested Solution Failure to transmit data due to timeout or HTTP Error. Data messenger server may be down. Contact the Network Administrator. Failure to login to data messenger server due to timeout or HTTP error. Misconfigured data messenger Check Configuration > Data server. Transmission > Sites are correct. Unable to detect Bluetooth device for FTP Failure to connect to the Unable to detect Bluetooth Bluetooth device. device for DUN Failure to transmit data due to timeout or FTP Error Loss of Bluetooth connection Unable to send message, during transfer connection not valid HeartStart MRx is too far from the Bluetooth device. Radio-frequency interference Replace the Bluetooth device. Data Messenger server is down. Contact the Network Administrator. Move closer to the Bluetooth device. TRANSMITTING The network is down Transmission Failed. Connection Interrupted. Transmission Failed Modem Connection Lost – 12LXmit Network The Bluetooth device is not within range. PPP Attach Timeout – 12LXmit Network Request Timeout – 12LXmit Server Invalid request – 12L Transmit HTTP client error – 12L Transmit The network is down. The server connection has timed out. TCP/IP Failure HeartStart Telemedicine has rejected the data. Check that the cellular signal strength is sufficient. • Resend the 12-Lead report. • Move the BT device closer to the MRx, within the transmitting range. See “Configuring a Bluetooth Device”. Check with your ISP to see if your service is down. Resend the 12-Lead report. Resend the 12-Lead report. If unsuccessful, check the MRx configuration settings. Check MRx and HS TM to ensure that the correct product versions are installed. Troubleshooting the Accessories This topic provides some guidance on troubleshooting the printer, fax, and modem. The hardware manufacturer is the ultimate authority on its devices; contact the manufacturer if these recommendations do not help. 82 Customer Support 4: Testing and Troubleshooting Printer Check the print queue for printing status. To view the print queue: Select Printers/Faxes from the Windows Control Panel. Fax • Make sure that HeartStart Telemedicine Server has the latest fax drivers installed. See the Microsoft web site at: http://www.microsoft.com for additional information. • Check the fax console for fax status. Select Printers/Faxes from the Windows control panel to view the fax console queue. • If the 12-Lead report is printing on multiple pages or is getting clipped, send a test page from another application, such as Microsoft Word. If that page is also not printing correctly, it could be the fax machine. Modem Check that the modem is configured correctly. Select the phone and modem icons from the Windows Control Panel. Customer Support At Philips, we strive to provide you with excellent customer service and technical support. For telephone assistance, call the Response Center nearest to you, or visit our web site at http://www.healthcare.philips.com/main/support/ Download the latest documentation from http://www.healthcare.philips.com/main/support/ProductDocumentation/ Our InCenter, the eSupport solution for Philips customers is located at http://incenter.medical.philips.com/ (requires registration). Supported Help Customer support technicians provide help by explaining the proper use, installation, and maintenance of HeartStart Telemedicine and answering questions about the HeartStart Telemedicine database. Before You Call You can help our technicians to give you good support by following these steps: • • • Call from a phone near your computer. Have HeartStart Telemedicine started. Have the following information: – Windows version – HeartStart Telemedicine version number (Press Help > About to find the version numbers). 83 4: Testing and Troubleshooting Customer Support How Our Support Technicians Provide Help • Explaining the proper use of the HeartStart MRx and HeartStart Telemedicine features and answering your questions about how the product works. • Explaining the proper installation, configuration and maintenance of HeartStart MRx and HeartStart Telemedicine. • Helping you to determine if the problem is not with the HeartStart MRx or HeartStart Telemedicine and directing you to the possible causes. What Our Support Technicians Do Not Support • Server hardware and software support. The support technicians cannot help you fix problems with the server hardware or operating system. Contact your hardware and software provider. • Cell phone and serial cable support. The support technicians cannot help you with cell phone or serial cable issues. Contact your cell phone service provider. • Internet service support. The support technicians cannot help you with Internet issues. Contact your ISP. • Troubleshooting defibrillators. Consult the “Troubleshooting” chapter of your HeartStart MRx Service Manual or Philips Customer Support and ask for defibrillator support. Customer Support Centers If your troubleshooting efforts do not yield a solution, please contact your regional support center as listed in Table 27: Table 27 84 Customer Support Centers Region Phone United States 800-722-9377 Canada 800-291-6743 Europe (Authorized EU Representative), Middle East, and Africa (+49) 7031 463-2254 Latin America 954-628-1022 Asia / Pacific (+852) 2821 5888 Appendix A Appendix1 Implementation Tools Overview This chapter provides additional information that you might need to set up the Data Transmission option. There is also a sample implementation plan that lists the required tasks and their estimated durations. Frequently Asked Questions Q: What types of data that can be sent from HeartStart MRx A: 12-lead reports, PCDT, or Event Summary Q: Can we use a TCP/IP port other than port 80? A: Port 80 is the preferable default. If you wish to use a different port, then you must work with your IT department to ensure the correct HeartStart MRx settings matching the IIS requirements. Q: How can we limit access to the server? A: To limit access to the server: a In the IIS Manager, right-click the EMS web site name, and then click Properties. b On the Directory Security tab, select IP Address and Domain Name Restrictions. c Set the default incoming connections to be allowed or denied, and set a list of exceptions. For example, if you know that your cell provider uses a range of dynamic IP addresses 213.158.167.0 – 213.158.167.255, you can set the default to allow only that range of incoming IP addresses. Any IP address outside that range will be denied. Q: Does the HeartStart Telemedicine System require a Public IP address? A: The HeartStart Telemedicine System requires a public IP address. The only configuration where you might not need a Public IP address is the WiFi system on the same network as the server and does not use the Internet. Q: How do we back up the database? A: The HeartStart Telemedicine database is low-maintenance compared to many other databases. Nonetheless, attention to routine maintenance tasks will help to ensure database integrity. It is the database administrator’s responsibility to set up appropriate database management tools and to check that they execute successfully. HeartStart Telemedicine uses the SQL Server Express database, which is a subset of Microsoft's SQL Server. In HeartStart Telemedicine, you can manage the database using the same tools that you use to manage SQL Server. Microsoft offers a free tool called Microsoft SQL Server Management Studio Express. You can use this tool to back up and restore the HeartStart Telemedicine database. Alternately, you can use 3rd-party tools at no cost or at a small cost to perform the same functions. For example, you can use an Internet search engine to find references to “backup SQL Server database.” The search returns references to a wide range of available database backup software. 85 A: Implementation Tools Frequently Asked Questions Q: On the HeartStart MRx, I see User Name and Password fields in the Hub configuration. Can those be used to make the transmission more secure? A: You can use the User Name and Password fields in the HeartStart MRx to authenticate specific users. However, the use of these fields does not increase the security of the ECG transmission between the HeartStart MRx and HeartStart Telemedicine. According to Microsoft, when you use the Basic Authentication method instead of the default anonymous access: “The authentication option you have selected results in passwords being transmitted over the network without data encryption. Someone attempting to compromise your system security could use a protocol analyzer to examine user passwords during the authentication process.” Philips Healthcare recommends that you use the anonymous access method with the HeartStart MRx encrypted data transmission. All file operations in IIS and the HeartStart Telemedicine application are set to use least-privileged access to minimize security risks. Q: How many locations can HeartStart Telemedicine System transmit to? A: You can configure an Auto Send List to send 12-lead reports to as many as 20 destinations. You can also configure as many as 50 Auto Send Lists on one HeartStart Telemedicine System 4.2. Q: What types of destinations can HeartStart Telemedicine System send to? A: HeartStart Telemedicine can transfer incoming 12-lead reports automatically to the following destinations: – To a network or local printer – To a fax machine – Via email – To another HeartStart Telemedicine System – To TraceMaster/TraceMasterVue – To DataMed FT (GE Muse Translator) See “Configuring HeartStart Telemedicine” on page 26. Q: What are the system requirements for HeartStart Telemedicine System? A: See “System Requirements” on page 21. Q: How does the HeartStart Telemedicine System use printing and fax machines from the software? A: HeartStart Telemedicine uses a service account to interact with the printing profiles. To modify the properties for the automatic transfer, you must log into the service account and modify the printer/fax properties there. For example, if you want to print your 12-Leads in landscape format, you must login as the service account, and change the fax printer property to print in landscape format. Q: Are my transmissions secured? A: We encrypt your Data Transmission using a 64-bit blowfish algorithm before transmission, and they are stored in the local database on our HeartStart Telemedicine encrypted as well. Q: What type of cellular devices do I need to be able to transmit? A: You must have one of: – a Wireless Link (WL), or – a Bluetooth Dial Up Networking (DUN) capable phone and a data package with tethering, or – a cellular mobile gateway. 86 Checklists A: Implementation Tools Q: Do you support VMWare or another virtual machine technology? A: Unfortunately, VMWare and other virtual machine (VM) technologies do not support fax modems. You may use a VM if you do not intend to use the fax feature of HeartStart Telemedicine, but Philips Healthcare does not recommend this technology. Q: Is the HeartStart Telemedicine System HIPAA-compliant? A: A HIPAA-compliant system is one that combines technical, physical, and administrative (through policies) attributes that protect patient’s security and privacy. The HeartStart Telemedicine System is a device and, as any device, cannot be HIPAA-compliant by itself. However, HeartStart Telemedicine has several features that facilitate a successful HIPAA-compliant implementation. For example, 12-Lead ECGs that are transmitted from the patient’s side to the HeartStart Telemedicine are encrypted and cannot be read even if the transmission is intercepted. The HeartStart Telemedicine software allows the viewing of 12-Lead, and as such it should be implemented in an environment where only the authorized personnel have access protected by the computer’s login ID and password. The fax and printer output should also be in a physical location where only clinical personnel involved in processing cardiac patients can see the printouts. The email feature of HeartStart Telemedicine includes a password option to protect the PDF attachment. Q: How does Philips Healthcare support the HeartStart Telemedicine System customers? A: See “Customer Support” on page 83. Checklists Bluetooth Device Profile Settings Bluetooth Device Profile Parameters Setting Choices Profile Name Configuration String Landline Dial Prefix Dial String Wait for Dial Tone PPP User Name PPP Password Static IP Address Primary DNS Secondary DNS http Proxy Address http Proxy Port Hub Parameters Setting Choices HeartStart Telemedicine Server machine URL User Name Not used in HeartStart Telemedicine. 87 A: Implementation Tools Checklists Bluetooth Device Profile Parameters Setting Choices Password Not used in HeartStart Telemedicine. Sitea Parameters Setting Choices Site Label Site Type Phone number URL Default Site a. The HeartStart Telemedicine documentation uses “destination” rather than “site.” Cell Phone, Modem, Service Plan, and Dial-Up Account Checklists Data Messenger See the Implementation Worksheet in the HeartStart Data Management Solutions Implementation Guide. for the Data Messenger implementation tools. Bluetooth Device Does the device support the Bluetooth wireless technology version 1.1 or greater standard? Does the device support the Bluetooth Dial-Up Networking (DUN) profile? Is the device compatible with the AT command set standards, such as ETSI TS 100916 and ITU-T V.250? Cell Phone Service Plan Does the cell phone service plan have an Internet/data plan? Dial-Up Internet Plan Does the dial-up account support PPP with PAP or MD5 CHAP? ISP Checklist 88 Does the ISP support local web hosting? Does the ISP support static IP addresses? If using a domain name, can the ISP obtain and register a domain name for you or will you do it yourself? Checklists A: Implementation Tools HeartStart Telemedicine Machine Checklist For the HeartStart Telemedicine Server and Viewer machines, make sure your installation environment satisfies the “HeartStart Telemedicine System Installation Requirements” on page 20. Configure the HeartStart Telemedicine Server machine as an Application Server. For the HeartStart Telemedicine Server machine, do not install Active Directory service, DHCP server, DNS server, Front Page extensions, or ASP. For each machine, make sure that the following is installed: For the HeartStart Telemedicine Server machine, do not delete or rename the IIS default web site page. – Microsoft Internet Explorer 7.0 or later – The latest security patches, updates, and fax drivers for the operating system. For more information, see “HeartStart Telemedicine Installation” on page 25. HeartStart Telemedicine Applications Review the README document available on the InCenter or after installation via the Help Menu. Make sure that you register each HeartStart Telemedicine Server and HeartStart Telemedicine Viewer application. Make sure that the HeartStart Telemedicine Server and, optionally, HeartStart Telemedicine Viewer applications are running. Confirm that IIS is installed and running on the HeartStart Telemedicine Server machine. The README document discusses the IIS considerations. Wireless Link Checklist The “Workflow Optimization” checklist on page 10 helps you determine your WiFi / Cellular connectivity and WL applicability. 89 A: Implementation Tools Sample Implementation Plan for Bluetooth Sample Implementation Plan for Bluetooth The following sample implementation plan provides information on the tasks required to set up the Data Transmission option and the estimated amount of time it takes. Table 28 Sample Implementation Plan Step Task 90 Time Frame 1 Purchase cell phone or Bluetooth device and cell phone service. Modify cell phone or Bluetooth settings, as needed. 2 days 2 Configure the HeartStart MRx for 12-Lead transmission. 30 minutes 3 Prepare hardware and physical location for the HeartStart Telemedicine installation. For example: 2 days • Determine if the HeartStart Telemedicine Server machine will be located in a locked room, how many data ports are needed, and whether you need an uninterrupted power source. • Determine the location of each HeartStart Telemedicine Viewer machine. • Determine the total number of network connections needed for the HeartStart Telemedicine machines. 4 Set up ISP. (Provider lead times and availability could take 2 to 3 weeks and involve telephone or cable company, ISP, domain name registrar, and physical wiring to be installed at the site.) 5 If using Bluetooth modem, set up dial-up Internet account. (Provider lead times 1 day and availability could take 2 to 3 weeks and involve telephone or cable company.) 6 Set up dedicated analog phone line for fax. (Provider lead times and availability could take up to 1 week and involve telephone or cable company.) 1 day 7 Set up and test each HeartStart Telemedicine machine operating system. 2 days 8 Install and configure each HeartStart Telemedicine application. 1 hour per machine 9 Test and verify end-to-end 12-Lead and PCDT transmissions from the HeartStart MRx to destination. 2 day 1 day Appendix B Glossary Appendix1 12-lead Abbreviation for 12-lead report ECG strip. A diagnostic test that helps identify various pathologic report conditions. The 12-lead report provides 12 views of the heart’s electrical activity. The 12 leads include: three unipolar augmented limb leads (aVr, aVt and aVf ), six unipolar precordial or chest leads (V1, V2, V3, V4, V5, and V6), and six limb leads. Each waveform reflects the orientation of a lead to the wave of depolarization passing through the myocardium. ACI-TIPI Acronym for Acute Cardiac Ischemia Time-Insensitive Predictive Instrument. A Philips software tool that can provide a second opinion and decrease the time between the onset of a patient’s acute cardiac ischemia (ACI) symptoms and the treatment of interventional cardiology. The ACI-TIPI feature computes a patient’s likelihood of having an ACI based on the patient’s age, gender, chest pain status, and acquired 12-Lead ECG. When the monitor/defibrillator runs the ACI-TIPI analysis, the interpretative block on the 12-lead report includes ACI-TIPI data. Address Address Resolution Protocol (ARP) is a telecommunications protocol used for resolution of network Resolution layer addresses into link layer addresses, a critical function in multiple-access networks. It is Internet Protocol Standard STD 37. When communicating with IT professionals, keep in mind that “ARP” could also mean the name of the program for manipulating these addresses in most operating systems. ARP See Address Resolution Protocol. Auto Send The lists configured on the Auto Send Lists workspace. An Auto Send List designates the destinations List that receive 12-Lead ECG 12-lead reports automatically. baud Units of information transmitted per second. Baud is used as a means of matching transmission and receiving speeds. Baud is not necessarily the same as bits per second, especially at higher speeds, although the terms are often used interchangeably. Baud is the number of signal level changes per second in a line, regardless of the information content of those signals. baud rate Signaling rate (not necessarily the same as bits per second), that is, the number of signaling elements transmitted each second. See also bits per second (bps). bit, byte The basic units of computer information. A bit (from binary digit) is equivalent to the result of a choice between two alternatives (as yes or no, on or off ). A byte is a group of adjacent binary digits that a computer processes as a unit; the size of a byte in practically all modern systems is eight bits. bits per Bits per second (bps) is the rate of transfer of information bits. second 91 B: Glossary Bluetooth A short-range wireless technology that uses radio links between a devices such as HeartStart MRx defibrillators, and computers, mobile computers, mobile phones, and other portable devices. bps See “bits per second.” data bits Data bits are transmitted "upside down and backwards." That is, inverted logic is used and the order of transmission is from least significant bit (LSB) to most significant bit (MSB). data Encrypting data is accomplished by applying a special scrambling code that makes the data unreadable to encryption anyone who does not have a decryption key. Authorized personnel with access to this key can unscramble it. Data Software that forwards, monitors, and manages the transfer of patient case data from defibrillators and Messenger AEDs to HeartStart Event Review Pro, folders (local and network), printers, or email. destination The intended recipient of a 12-lead report. The destination can be a 12-Lead Transfer Station application, a TraceMasterVue system, DatamedFT software, a HeartStart Telemedicine application, an email address, a printer, and a fax machine. DNS See “Domain Name Service.” domain A domain is a group of computers and devices on a network that are administered as a unit with common rules and procedures. Within the Internet, domains are defined by the IP address. All devices sharing a common part of the IP address are said to be in the same domain. domain An address of a network connection in the format that identifies the owner of that address in a name hierarchical format: server.organization.type. For example, www.whitehouse.gov identifies the Web server at the White House, which is part of the U.S. government. domain The address of a device connected to the Internet or any other TCP/IP network, in the hierarchical name system that uses words to identify servers, organizations, and types, such as www.logos.net. See also address TCP/IP. Domain The Internet utility (called DNS) that implements the domain name addresses (such as Name bluestem.prairienet.org) and IP addresses (such as 192.17.3.4). DNS servers access and maintain Service databases that contain IP addresses. The domain name address is used by human users. It is automatically translated into the numerical IP address, which is used by the packet-routing software. ECG Acronym for electrocardiogram. The electrical rhythm of the heart as detected through defibrillator pads. ePCR Electronic Patient Care report 92 B: Glossary fax A modem that sends (and possibly receives) data encoded in a fax format, which a fax machine or another modem modem decodes and converts to an image. Fax modems might be internal or external and might combine fax and conventional modem capabilities. gratuitous A simple announcement protocol useful for updating other hosts' mapping of a hardware address when ARP the sender's IP address or MAC address has changed. Such an announcement, also called a gratuitous ARP message, is usually broadcast as an ARP request containing the sender's protocol address in the target field, with the target hardware address set to zero. See also “Address Resolution Protocol” or ARP. HeartStart A software option that receives HeartStart MRx data transmissions. The HeartStart Telemedicine Classic Teleme- 12-Lead Edition can process 12-lead report transmissions, and HeartStart Telemedicine Critical Care dicine Editioncan process 12-lead reports, trigger events and waveforms, and periodic vital trends. See also PCDT. Consists of a server component that runs typically in the Information Technology server room, and a viewer component that typically runs in the clinical environment. The server component, HeartStart Telemedicine Server, consists of the application software, the database, Internet access, and the system administration user interface. The viewer component, HeartStart Telemedicine Viewer, allows clinicians to interact with the patient clinical data found in HeartStart Telemedicine Server remotely and perform limited tasks such as forwarding events. HTTP Hypertext Transfer Protocol (HTTP) is the set of rules for exchanging files (text, graphic images, sound, video, and other multimedia files) on the World Wide Web. hub A hardware device providing the interconnection between networked devices. It is called a hub because the network wiring can be sketched like a spoked wheel with the hub at the center. For 12-Lead transmission, the hub is the machine running HeartStart Telemedicine. IIS Acronym for Internet Information Service. Microsoft's brand of Web server software, utilizing Hypertext Transfer Protocol to deliver World Wide Web documents. It incorporates various functions for security, allows for CGI programs, and provides for Gopher and FTP servers. IP Acronym for Internet Protocol. The protocol within TCP/IP that governs the breakup of data messages into packets, the routing of the packets from sender to destination network and station, and the reassembly of the packets into the original data messages at the destination. IP corresponds to the network layer in the ISO/OSI model. IP address An Internet address or IP address is a unique computer (host) location on the Internet (expressed either as a unique string of numbers or as its associated domain name). Computers use IP addresses to locate and talk to each other on the Internet, much the same way people use phone numbers to locate and talk to one another on the telephone. MD5 Acronym for MD5 Challenge Handshake Authentication Protocol. A type of authentication in which CHAP the authentication agent (typically a server) sends the client a random value and an ID value. These values are used to create a hash value (a number generated from a string of text) on the client. The client encrypts the hash value, and sends it with the user’s name and password over a network. The server then 93 B: Glossary decrypts both the message and the hash, produces another hash, and compares the two. If they are the same, the client is authenticated. Microsoft The user interface for Microsoft Fax Service. Fax Console Microsoft A system service that provides fax services to local and remote network clients. Fax services include Fax receiving faxes and faxing documents, fax wizard messages, and email messages. Service MiFi Wireless router that acts as a mobile WiFi hotspot. PAP Acronym for Password Authentication Protocol. A basic form of authentication in which a user’s name and password are transmitted over a network and compared to a table of name-password pairs. Patients A feature set that allows HeartStart Telemedicine users to view the list of available patient data records that are stored in the HeartStart Telemedicine database. PCDT Acronym for Periodic Clinical Data Transmission. An HeartStart MRx data transmission option. Data can include 12-lead reports, events, and periodic vital trends. periodic A HeartStart MRx option that records patient vitals in 1-minute to 60-minute intervals and sends the vitals patient vitals to HeartStart Telemedicine in 1-minute to 5-minute intervals. HeartStart MRx records the time and date of patient vitals. such as: pulse, heart rate, airway respiration rate, EtCO2, invasive pressure values, and temperature. PPP Acronym for Point-to-Point Protocol. Provides a method for transmitting data over serial point-to-point links. profile A list of specifications that define how wireless transmission should work between different Bluetooth devices. For example, you create a profile on HeartStart MRx that defines how the Bluetooth device communicates with HeartStart MRx. protocol The special set of rules of communication that the terminals or nodes (and related software) in a telecommunication connection use when they send signals back and forth. proxy A computer program that acts as an intermediary between a web browser and a server. To give users rapid access to popular web destinations, Internet Service Providers use proxy servers as “holding bins” to store frequently requested pages, rather than going out and fetching them repeatedly from the Internet. 94 B: Glossary proxy A firewall component that manages Internet traffic to and from a local area network (LAN) and can server provide other features, such as document caching and access control. A proxy server can improve performance by supplying frequently requested data, such as a popular Web page, and can filter and discard requests that the owner does not consider appropriate, such as requests for unauthorized access to proprietary files. See also firewall. RS-232 A standard developed by the Electronic Industries Association (EIA) and other interested parties specifying the serial interface between Data Terminal Equipment (DTE) and Data Communication Equipment (DCE.) No longer used in Philips HeartStart Monitor/Defibrillator Data Transmission. SDK Acronym for Software Development Kit. HeartStart Data SDK is a set of tools to help software developers create applications that map data from your HeartStart MRx monitor/defibrillators. serial Serial transfer is the sequential transmission of the eight bit-voltages that constitute a byte. A transmitter breaks each byte into bits, then sends the bits one after another; the receiver cooperates by reassembling the set of bits into a single byte. SQL The database that stores the 12-lead reports and configuration information. Server database static IP A static IP address is a number (in the form of a dotted quad) that is assigned to a computer by an address Internet service provider (ISP) to be its permanent address on the Internet. A dot address (sometimes known as a dotted quad address) refers to the notation that expresses the four-byte (32-bit) IP address as a sequence of four decimal numbers separated by dots. Each number represents the binary value of one of four bytes. status log The HeartStart MRx status log includes entries for all errors logged during normal operating mode, Automated tests, Service and Configuration Mode, and Operational Checks. It is accessed from Service Mode. system log The log of HeartStart Telemedicine activity. The system log is available on the Administration navigation pane. TCP/IP Acronym for Transmission Control Protocol over Internet Protocol. The TCP/IP protocol defines how data can be transmitted in a secure manner between networks. TCP/IP is the most widely used communications standard and is the basis for the Internet. time sequential ECG 12-lead report An ECG 12-lead report that shows a sequential sample of 2.5 seconds of ECG data from each of the twelve channels. The format has three rows of four channels of data, with a single channel at the bottom of the page. Each successive channel has the next 2.5 seconds of data of the total of 10 seconds of data. A time sequential ECG 12-lead report marks each segment with a single vertical line. It is the preferred format in the United States. 95 B: Glossary TPI Acronym for Thrombolytic Predictive Instrument. A Philips software tool that can help physicians make thrombolytic therapy (TT) decisions when treating acute myocardial infarction (AMI). The TIPI algorithm generates a predictive probability score of a patient’s outcome with or without thrombolytic therapy. The TIPI algorithm is based on demographic patient data applied to the acquired 12-Lead ECG. Demographic patient data includes information such as the patient’s age, gender, blood pressure, weight, and history of diabetes and hypertension. When the defibrillator runs the TPI analysis, the interpretative block on the 12-lead report includes TPI data. TT Acronym for Thrombolytic Therapy. The use of drugs to break up or dissolve blood clots, which are the main cause of both heart attacks and stroke. trigger A HeartStart MRx event that initiates the transmission to Event Review. event URL Acronym for Uniform Resource Locator. The addressing system used in the World Wide Web and other Internet resources. The URL contains information about the method of access, the server to be accessed and the path of any file to be accessed. vital trends The HeartStart Telemedicine option that displays tabulated HeartStart MRx measurements for the recorded patient periodic vitals. Vital trends are available for 12 hours at 1-minute to 60-minute resolutions and display in descending order. HeartStart Telemedicine displays the vital trends in a tabular or chart format. Wireless A portable wireless communication accessory for the HeartStart MRx, providing patient data Link transmission to the Philips HeartStart Telemedicine System using WiFi or Cellular networks. workspace The right pane of the HeartStart Telemedicine window. 96 Index # 12-Lead acquisition 6 Mode, entering 54 storage requirements 24 transmission Bluetooth 15 planning 9 scenario, simple 12 scenario, Telemed 15 12-Lead layout, setting 27 12-Lead reports 18 encrypted 28 faxing 36 printing 36 sending automatically 28 manually 28 to 12LTS 36 to Auto Send Lists 36 to Telemedicine 36 settings 26 transmission failure 69 transmission process 6 12-Lead Transfer Station 4 as a destination 28 location type 29 2-way radio 16 32-bit 21 3G, usage scenario 12 64-bit blowfish algorithm 86 A abbreviations ii Access Point mode 45 mode troubleshooting flowchart 62 MRx config setting 37 priority 43 Access Point settings options 45 access, anonymous 35 accessories requirements 23 troubleshooting 82 acquisition 6 acronyms ii activation, WL cellular service 42 adapter, Bluetooth requirement 23 Add an email address, email setting 32 advanced settings, WL 49 air card, PC requirement 53 ambulance, data transmission from 13 analog line phone 53 transmission 54 anonymous access 35 AP mode 45 settings 46 troubleshooting flowchart 62 MRx config setting 37 priority 43 settings options 45 transmission problems, WL 64 APN String, cellular connection 43 application 19 destinations Auto Send List 29 forwarding to 29 worksheet 29 Apply Changes to save configuration 41 AT&T 42 audience, intended 2 authenticated access, not used for Telemed 35 authentication 86 Authentication Type AP setting 46 WiFi connection 41 authorization, Bluetooth device 54 authorized EU representative i Auto Send List application destinations 29 configuration 26 configuration destination 28 default 32 destination worksheet 33 destinations 28 email SMTP server 31 forward 28 send 12-Lead reports manually 28 settings 32 simple setup 12 specify 32 Telemedicine destination, manual 28 uses 28 B B/R mode troubleshooting flowchart 61 backup configuration settings 34 database 85 storage requirement 23 battery, low 38 bibliography 2 blowfish algorithm 86 Bluetooth 12-Lead transfer, sample 15 adapter 23 configuration menu 51 connection 80 dialing 81 DUN profile 53 Exchange Folder setting 27 modem pairing 55 Monitor 19 MRx config setting 37 network connection 81 option requirements 21 requirement 21 sending 80 server connection 81 setup skills requirement 2 stack requirements 23 transmission range requirement 23 transmission setup 15 troubleshooting 79 Bluetooth Connection Lost message 81 Bluetooth device adding 54 authorization 54 changing profile 55 discoverability 54 discovery 16 errors 80 manual testing 79 name 54 overview 16 pairing 55 errors 80 timeout 55 profile change 55 configuring 51 selection 55 requirements 53 testing 79 transmission range 54 Bluetooth Device Pairing Failed message 80 Bluetooth Malfunction message 79 Bluetooth profile add 51 delete 52 selection 55 settings checklist 87 bonding see pairing Bridge / Router mode troubleshooting flowchart 61 bridge settings, WL 40 97 Index C Carepoint Station 3 CDMA network 42 support 5 CD-ROM, requirement 22 CEL light 58 cell phone checklist 88 setup skills requirement 2 testing 68 Cellular status light 58 Status Page section 67 cellular connection, modify 44 profile setup planning 13 simple setup 13 service activation 42 service provider 42 transmission problems, WL 64 WL connection 42 cellular mobile gateway 86 central 15 Change Profile, Bluetooth 55 channel congestion 64 checklists 87 chemical content i Cipher AP setting 46 Classic edition 7 clipped images, fax 28 compliance i components 18 for Telemedicine installation 20 of Data Transmission 18 of Telemedicine 19 computer requirements system 21 Windows 21 configuration Bluetooth profile 51 computer requirements 21 export, WL 47 Fax Console 28 fax setting 30 import, WL 47 main menu 34 menu 51 modify 34 MRx password 34 MRx, skills requirement 2 overview 17 planning 14 recommendations 14 Service Manager 26 settings, backup 34 skills 2 SMTP 19 98 C configuration (continued) Telemedicine 26 WL 37 Configuration String, phone and modem settings 52 connection Bluetooth troubleshooting 80 copy 45 creating, WL 40 edit 44 management, WL 43 modify 44 priority 43 Connection Name cellular 42 WiFi 41 connection test, WL 65 connectivity icons, WL 59 test, WL 65 console application, Telemedicine 28 Copy button 45 copy connection 45 copyright i credentials change, WL 50 Critical Care edition 7 customer service 83 customization, SMTP 19 D data formats 8 management stages 3 processing software 1 tethered 53 transmission from a hospital bay 14 from an ambulance 13 options 5 solutions 11 types 1 Data Bearer 68 data flow 11 Data Messenger configuration 56 installation 56 overview 7 subnet 7 WL option 11 data transmission See transmission Data Transmission, solution components 18 database 85 dataflow pathways 4 DatamedFT as a destination 28 intro 4 location type 29 debug log, WL 66 Default Site, setting 36 Deleted patient record message 75 denial of service 59 Description application setting 29 Auto Send List setting 33 email setting 32 fax setting 30 designated fax machine, testing 68 destination application worksheet 29 Auto Send List 28 configuring 35 email 31 printer 30 Destinations Auto Send List setting 33 diagnostic, WL 65 Dial Prefix, phone and modem settings 52 Dial String, phone and modem settings 52 dialing, Bluetooth troubleshooting 81 dial-up 53 account, checklist 88 discoverability, Bluetooth device 54 discovery Bluetooth device, overview 16 Bluetooth troubleshooting 80 disk space, requirement 22 display resolution, requirement 22 DNS 18 Domain Name Service See DNS Domain Name, restriction 85 DoS 59 download, Telemedicine 24 DUN-enabled MRx 55 E edit cellular connection 44 WiFi connection 44 Edit button 44 editions of Telemedicine 7 email as a destination 28 Auto Send List 31 client requirement 23 destination 31 worksheet 32 requirements 31 settings 32 SMTP server 31 Email PDF option 31 Emailed... report, Telemed messages 75 encryption 28 algorithm 86 ePCR 16 planning 10 WL option 11 F ER Pro, WL option 11 eSupport 83 ETH light 58 Ethernet light 58 status page section 66 EU authorized representative i event 18 Exchange Folder, Bluetooth setting 27 Export button 47 export configuration, WL 47 export settings 46 Exported trigger event report for Patient, Telemed message 76 Exported trigger event report, Telemed message 75 Exported vital trends report, Telemed message 76 F Failed to connect to application, Telemed message 78 delete patient record, Telemed message 75 email 12-Lead, Telemed message 75 email patient report, Telemed message 75 email trigger event report, Telemed message 75 email vital trends report, Telemed message 75 export trigger event report, Telemed message 76 export vital trends report, Telemed message 76 fax, Telemed message 76 print 12-Lead, Telemed message 76 print patient report, Telemed message 76 print trigger event report, Telemed message 77 print vitals trend report, Telemed message 77 save 12-Lead, Telemed messages 77 save the periodic clinical data transmission, Telemed message 77 save trigger event, Telemed messages 77 save vital, Telemed message 77 send 12-Lead, Telemed message 78 send patient data, Telemed message 78 FAQ 85 fax designated machine, testing 68 destination 28 application 30 settings 30 worksheet 30 failure troubleshooting 70 manual send, troubleshooting 70 Index fax (continued) modem 23 worksheet 30 multiple machines, testing 69 requirements 30 resizing 28 sites settings 36 troubleshooting 83 failure to send multiple 72 failure to send PCDT 73 send PCDT 72 send report 70 send to multiple machines 72 Fax and Scan 28 Fax Console configure 28 Retry settings 30 Fax Number, setting 30 Faxed 12-Lead, Telemed message 76 File menu 12-Lead report 29 Print 29 file push 53 firewall 25 firmware upgrade, WL 49 flowcharts, WL troubleshooting 61 forward 12-Lead report 28 to a configured destination 29 Frequently Asked Questions 85 FTP, file push 53 FTP-enabled MRx 55 G gateway usage scenario 12 GE MUSE 15 General Devices See Rosetta LT 16 Glossary 91 gratuitous ARP 48 GSM provider 67 support 5 H hard disk space, requirement 22 hardware requirements for Bluetooth 21 system 22 HeartStart MRx battery charge for WL 38 configuration menu 34 configuring, skills requirement 2 data 12-Lead report 18 Telemedicine 18 hardware requirements 21 prerequisites for WL 38 SDK 16 software requirements 21 status log 73 HeartStart Telemedicine See Telemedicine help not provided by Philips 84 provided by Philips 83 .hic file type 8 Higher button 43 HIPAA, compliance 87 history, setting 27 hospital bay, transfer from 14 http Proxy, MRx config settings 37 http Proxy... phone and modem settings 52 HTTP service 19 hub 35 configuring 35 setup planning from an ambulance 13 simple 12 setup skills requirement 2 sites settings 36 I icons, WL 59 IIS 18 and SMTP server 31 log 25 Manager 19 Server requirements 21 setup 27 web services setup 27 IMEI as identifier 67 string 42 implementation plan 90 tools 85 import 46 Import button 47 In Motion 6 Inbox Watcher service 19 InCenter 83 indicators, WL 58 initialization, WL 39 Inop messages 59 installation skills 2 SMTP 19 system requirements 21 Internet connection requirements 22 dial-up 53 Internet Information Services, See IIS Internet Service Provider, See ISP InterNIC 18 Invalid Password, message 81 invisible WL 5 99 Index IP address PC, static 39 public 85 restriction 85 static, requirement 20 ISP 20 checklist 88 choosing 18 K Key AP setting 46 WiFi connection 41 knowledge requirements 2 L LAN, connecting Telemedicine Viewer 7 landline 53 Landline phone and modem settings 52 landscape printing 28 lights, WL 58 limit server access 85 literature 2 Location type setting 29 location types 29 login credentials change 50 password 43 username 42 low battery 38 Lower button 43 M MAC Address 66 manual destination, Auto Send List 28 manual testing Bluetooth device 79 transmission 68 manufacturer i MAPI-compliant email client 20 MD5 CHAP 88 mechanisms of data transmission 3 medical device directive i MEID 42 as identifier 42 on Status Page 67 memory, requirement 22 .mic file type 8 Microsoft Developer Network 19 Fax Console See Fax Console 28 IIC 18 MiFi 6 usage scenario 12 Mobile Equipment Identifier 67 100 K modem checklist 88 configuration menu 51 landline 53 profile settings 52 troubleshooting 83 modify, configuration settings 34 monitor, Bluetooth 19 MRx configuring for WL 37 enabled for DUN and FTP 55 MSDE 2000 24 database 85 MSDN 19 multiple fax machines, testing 69 N Name application setting 29 Auto Send List setting 33 email setting 32 fax setting 30 name, Bluetooth device 54 network connection, Bluetooth troubleshooting 81 Network Status Log 74 New Cellular button 40 New WIFi button 40 No Bluetooth Devices Configured, message 80 No Bluetooth Devices Detected, message 80 No Bluetooth Profiles Configured, message 80 No transmission devices detected, message 80 16 O Operating system, requirements 21 optimization questionnaire 10 P pairing (a.k.a. bonding) 16 pairing, Bluetooth device 16 troubleshooting 80 with MRx 55 PAP 88 passkey 55 password change 50 configuration 34 for attachment 27 for email attachment 32 service 73 Telemedicine, not needed 35 Password Config, phone and modem settings 52 Password for attachment, email setting 32 Password hub setting 35 Password protect attachment, setting 27 pathways, dataflow 4 patient data transmission after hand off 5 during care 3 PCDT acquisition 6 data transmission testing 69 planning 9 status log 74 transmission process 6 transmission scenario 12 understanding 6 PCDT connection to Bluetooth Device ... failed, message 81 PDF reader, requirement 23 .pdf file type 8 Per Data Tx Log 74 Periodic Clinical Data Transmission See PCDT phone analog line 53 numbers, support 83 profile settings 52 Phone Number setting 36 Phone/Modem Profiles 51 planning questionnaire 10 port 80 85 Power light 58 power outage 26 power-up mode 48 PPP 88 PPP Password, phone and modem settings 52 PPP User Name, phone and modem settings 52 prerequisites Bluetooth 21 Telemedicine 21 WL 38 Previous history, setting 27 Primary DNS, phone / modem settings 52 Print File menu 29 sites settings 36 toolbar 29 Print with grid, setting 27 Printed 12-Lead, Telemed message 76 patient report, Telemed message 76 trigger event report, Telemed message 76 vitals trend report, Telemed message 77 Q printer destination 30 destination worksheet 31 on auto-send list 28 option requirement 31 system requirement 23 troubleshooting 83 printing landscape 28 profiles 86 status log 74 priority highest to EMS station 14 lowest to cellular 13 processor requirement 22 speed requirement 22 profile add, Bluetooth 51 change, Bluetooth 55 deleting, Bluetooth 52 selection, Bluetooth device 16 settings, phone and modem 52 profile change, Bluetooth 55 Profile Name, phone and modem settings 52 progress messages 55 Provider Name 67 PWR light 58 Q QA planning 10 quality control planning 10 R Radio Access Network 67 radio compliance i Radio Interface 67 RAN 67 recovery plan 23 reducing faxes 28 references 2 Refresh Rate 66 Rejected by application Telemed message 78 repair, assistance 83 Reply email address setting 27 report, time-sequential format 26 requirements 32-bit 21 Bluetooth device 53 email 31 printer 31 skills 2 system 21 Telemedicine 21 Index reset statistics 67 WL 47 Response Center 83 restore settings, WL 47 roaming, WL 67 Rogers, provider 42 Rosetta-Lt 16 router lights, WL 58 router settings, WL 40 RUN light 58 RX string 66 S sample implementation plan 90 scenarios 11 Saved 12-Lead, Telemed message 77 Saved trigger event, Telemed message 77 Saved vital, Telemed message 77 scaling faxes 28 scenarios 11 SDK 16 planning 10 Secondary DNS, phone and modem settings 52 secure transmission 86 send 12-Lead reports, manually 28 sending, Bluetooth troubleshooting 80 Sent 12-Lead Telemed messages 78 Sent patient data Telemed message 78 serial number, WL 14 server access, limit 85 component 18 connection, troubleshooting 81 software requirements 21 Server Name, setting 27 Server URL, hub setting 35 Service Manager automatic start-up 26 configuration 26 service, dial-up plan 53 services password 73 plan checklist 88 Telemedicine 28 settings advanced other 49 WL 46 Bluetooth, profile checklist 87 configuration backup 34 email 32 import/export, WL 46 modify 34 profile, phone and modem 52 settings (continued) reset WL 47 restore WL 47 Telemedicine application 29 general 27 setup skills 2 Telemedicine 17 signal congestion 64 strength, Status Page 67 SIM card, WL 42 Simple Mail Transfer Protocol See SMTP Site Name setting 36 Site Type setting 36 Sites setup planning 13 simple 12 sites configuring 35 add 36 delete 37 skills requirements 2 smartphone 53 SMTP installation 19 Microsoft service 19 server 31 requirement 21 server name setting 27 service 20 on Telemedicine 20 provided by Microsoft 19 SMTP server name setting 27 software for data processing 1 requirements 21 version 21 Software Developer's Kit 10 solution data transfer 11 high level structure 9 questionnaire 10 Sorry, but that connection... message 45 SQL Server 19 Management Studio Express 85 SSID WL, pre-configured 14 SSID Name AP setting 46 WiFi connection 41 SSID Visible AP setting 46 WiFi connection 41 stack, Bluetooth requirement 23 stages of data management 3 Started Event Review Bluetooth Monitor, Telemed message 78 101 Index Started Event Review Service Manager, Telemed message 78 Started PDTSInboxMonitor 79 Started PDTSInboxMonitor, Telemed message 79 static IP PC address 39 WL broadcast 48 change 48 Static IP Address phone and modem settings 52 Static IP button 48 statistics reset 67 status page 66 status lights, WL 58 log HeartStart MRx 73 printing 74 page, WL 66 Stopped Event Review Bluetooth Monitor, Telemed message 78 Stopped Event Review Service Manager, Telemed message 78 Stopped PDTSInboxMonitor, Telemed message 79 storage requirements 23 Studio Express 85 subnet mask, WL 39 substances of very high concern i support available 83 regional centers 84 unavailable 84 sustainability i SVHC i system log Telemed 74 troubleshooting with 69 requirements 21 T TCP/IP 95 TCP/IP port 85 TCP/IP port 80 18 technical support 83 Telemedicine application as a destination 28 checklist 89 installation skills requirement 2 as a destination 4 as a Hub 4 102 T Telemedicine (continued) central 15 Classic 12-Lead Edition 18 Classic edition 7 compatibility 20 components intro 7 setup 18 configuration 26 configuration overview 17 Critical Care edition 7 destinations 28 download 24 editions 7 hub 35 install professionally 20 installation 20 package 24 process 25 required components 20 verification 25 location type 29 machines checklist 89 messages 75 other applications 20 overview 18 parts of 19 prerequisites 21 reports, print 30 requirements 21 server as a Windows service 26 installation 24 requirements 21 static IP address required 18 service 19 Service Manager 26 automatic start-up 26 settings 27 application 29 default 26 sites 36 sites settings 36 setup planning 13 simple setup 12 storage requirements 23 system requirements 21 transmit locations limit 86 understanding 7 verifying installation 25 viewer installation 24 requirements 21 web services 18 window 25 WL option 11 telephone line, requirement 22 numbers 83 test connection, WL 65 phase errors 74 testing 57 12-Lead Transmission 68 Bluetooth device 79 skills requirement 3 WL 57 WL transmission 59 tethered data 53 tethering 86 thrombolytic therapy 96 time sequential format 26 toolbar Forward report 29 Print report 29 TraceMasterVue as a destination intro 4 setup 28 location type 29 trademarks i transmission 82 12-Lead 6 Bluetooth 15 Bluetooth troubleshooting 82 by data card 5 by Rosetta-Lt 3 lines, analog 54 mechanisms 3 methods 1 pathways 4 PCDT 6 possible destinations 15 problems AP 64 cellular 64 WiFi 64 WL 63 range, Bluetooth device 54 requirement 23 scenarios 15 security 86 stages 3 test message, BT 55 WL 11 Transmission Failed. Cannot Reach Server, message 81 Connection Failed, message 81 Connection Interrupted, message 82 Error..., messages 80 message 82 No Dial Tone, message 81 Server Unknown, message 81 Settings Configured Incorrectly, message 81 Transmission Settings Have Not Been Configured, message 80 trigger event 18 U troubleshooting 57 accessories 82 Bluetooth connection 80 device 79 device, overview 16 dialing 81 discovery 80 network connection 81 pairing 80 sending 80 server connection 81 transmission 82 failure to fax 70 fax to multiple faxes 72 send 70 send PCDT 72 send PCDT to Telemedicine 73 HeartStart MRx status log 73 manual send to fax 70 send to multiple fax machines 72 sending a report 69 skills requirement 3 tables 74 Telemedicine system log 74 WL 57 AP 64 cellular 64 general 63 WiFi 64 troubleshooting flowcharts, WL 61 TX string 66 txqueuelen 66 types of transmitted data 1 U UMTS 67 upgrade firmware, WL 49 URL for this book 1 setting 36 URL or Location setting 29 User Name hub setting 35 phone and modem settings 52 user name, not needed for Telemedicine 35 Username change 50 V Verizon, provider 42 viewer component 18 virtual machine technology 87 VMWare 87 Index W Wait for Dial Tone phone and modem settings 52 web services 18 Welcome screen, WL 39 WEP key 41 WF light 58 WiFi access points setup planning 13 simple setup 13 connection copy 45 modify 44 WL 40 network usage scenario 12 status light 58 status page section 67 transmission problems, WL 64 Windows Fax and Scan 28 requirements 21 service 26 wired mode, PC 38 Wireless Channel AP setting 46 Wireless Link Disabled, DoS Inop 59 Wireless Link See WL Wireless Link Unplugged Inop 59 Wireshark 48 WL advanced settings 46 configuration export 47 import 47 utility 37 connect 50 connection management 43 controls 5 Data Messenger configuration 56 definition 5 equipment preparation 38 icons 59 invisible 5 IP address, MRx config setting 37 lights 58 MRx configuration 37 prerequisites 38 purpose 5 reset 47 restore settings 47 serial number 14 setup before you begin 38 power 38 Static IP 48 system prerequisites 38 testing 57 transmission setup 11 transmission test 59 troubleshooting 57 workflow questionnaire 10 worksheet application destination 29 Auto Send List destination 33 email destination 32 fax destination 30 printer destination 31 WPA2-PSK key 41 WPA-PSK key 41 103 Philips Healthcare is part of Royal Philips Electronics © 2013 Koninklijke Philips Electronics N.V. On the web www.philips.com/heartstart All rights are reserved. Reproduction in whole or in part is prohibited without the prior written consent of the copyright holder. By e-mail [email protected] By fax +31 40 27 64 887 By postal service Philips Healthcare 3000 Minuteman Road Andover, MA 01810-1085 Asia Tel: +852 2821 5888 Philips Healthcare reserves the right to make changes in specifications or to discontinue any product at any time without notice or obligation and will not be liable for any consequences resulting from the use of this publication. Europe, Middle East, and Africa Tel: +49 7031 463 2254 Latin America Tel: +55 11 2125 0744 North America Tel: +425 487 7000 1 800 285 5585 (USA only) Published Mar. 2013, Edition 3 453564058751 *453564058751* *3*