TraceMasterVue ECG Management System INSTALLING TRACEMASTERVUE AND CONFIGURING COMMUNICATION

Transcription

1 TraceMasterVue ECG Management System INSTALLING TRACEMASTERVUE AND CONFIGURING COMMUNICATION

2 Notice About This Edition Publication number Edition 1 Printed in USA Edition History Edition 1, April 2007 Applicable to TraceMasterVue version B.02 and later. Philips Medical Systems 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. Copyright Copyright 2007 Philips Electronics North America Corporation Andover, MA USA (978) All rights are reserved. Reproduction in whole or in part is prohibited without the prior written consent of the copyright holder. Warranty Philips Medical Systems makes no warranty of any kind with regard to this material, included, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. Responsibility of Manufacturer Philips Medical Systems only considers itself responsible for any effects on safety, reliability and performance of the M5100A TraceMasterVue server if: assembly operations, extensions, readjustments, modifications or repairs are done by persons authorized by Philips Medical Systems, and the electrical installation of the relevant room or vehicle complies with the IEC or national requirements, and the instrument is used according to the instructions for use presented in this manual. European Directives This product consists of hardware and software. The hardware carries the CE mark based on the declarations provided in the User s Guide for the IT hardware. The software is a class 1 medical device under the Medical Device Directive 93/42/EEC and carries the mark accordingly. WARNING As with all electronic equipment, Radio Frequency (RF) interference between the TraceMaster system and any existing RF transmitting or receiving equipment at the installation site, including electrosurgical equipment, should be evaluated carefully and any limitations noted before the equipment is placed in service. Radio frequency generation from electrosurgical equipment and close proximity transmitters may seriously degrade performance. Philips Medical Systems assumes no liability for failure resulting from RF interference between Philips Medical Systems medical electronics and any radio frequency generating equipment at levels exceeding those established by applicable standards. CAUTIONS In the U.S. Federal Law restricts this product to sale on or by the order of a physician. Use of accessories other than those recommended by Philips Medical Systems may compromise product performance. THIS PRODUCT IS NOT INTENDED FOR HOME USE. To ensure accuracy, all measurements of the online waveforms must be made using the electronic calipers supplied within ECGVue. Faxed waveforms do not meet the requirements of American National Standard ANSI/AAMI EC11:1991 for display of diagnostic electrocardiograms, and may not be suitable for diagnosis. Faxed reports contain information on the border to differentiate them from printed reports. Global Medical Device Nomenclature (GMDN) The 5-digit GMDN code adjacent to the symbol is defined in the EN ISO GMDN Trademarks Microsoft Windows Server 2003 is a registered trademark of Microsoft Corporation Internet Explorer is a registered trademark of Microsoft Corporation Java is a US trademark of Sun Microsystems Acrobat Reader is a trademark of Adobe Corporation. Netscape is a registered trademark of Netscape Communications Corporation

3 Contents Chapter 1. Getting Started Before You Begin About TraceMasterVue Documentation Accessing Updates at InCenter About this Guide System Requirements and Components TraceMasterVue Components About the TraceMasterVue ECG Viewer/Editor, ECGVue or PharmaVue Running TraceMasterVue Applications TraceMasterVue System Requirements Database/Web Server Requirements Database Server Configuration Client Requirements TraceMasterVue Configuration Overview Before Configuring TraceMasterVue Requirements for Running TraceMasterVue Data Communication Methods Implementation Planning Collecting Required Information PageWriter XL-Series or 200/300 Cardiographs PageWriterTouch Cardiographs PageWriter Trim Cardiographs Installing Options Chapter 2. TraceMasterVue Communication Worksheets Installation and Configuration Checklist Communication Configuration Checklist Transmission and Phone Configuration Worksheet COM Port Assignment and Phone Number Worksheet TraceMasterVue Network Configuration PageWriterTouch/Trim Cardiograph Connection Configuration PageWriter XL Cardiograph Connection Configuration Location Worksheet User-Defined Fields Worksheet User Access Worksheet TraceMasterVue Group Permissions Table Physician List Worksheet Inboxes Worksheet Automated Workflow Rules Worksheet Order Inboxes Worksheet Installing TraceMasterVue and Configuring Communication i

4 Table of Contents Chapter 3. Installing TraceMasterVue Components Before You Begin Verifying System Components Available Options Supplies Used Regularly Installing the Hardware Connecting the Server Connecting the Network Hub Connecting the LCD Display Connecting the Uninterruptable Power Source Connecting the Mouse and Keyboard Connecting the MetroLogic Bar Code Scanner Recommended Scanning Technique Resetting the Bar Code Scanner Installing Modems Connecting a Printer Turning the TraceMasterVue System On Chapter 4. Configuring the Network for TraceMasterVue Data Communication Installing Hardware and Configuring COM Ports On TraceMasterVue Setting Up the Octa-Cable Setting Up a Direct Connection Mounting the Junction Box Installing the Wall Plate Cable Option Installing Data Transfer Modems Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System 4-7 Configuring COM Ports Freeing COM Ports from the Fax Utility and RAS Verifying Correct Port Configuration for Modems Freeing Modems from the Fax Utility Freeing Ports from the Remote Access Service Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue Configuring Network Settings Assigning IP Address Setting Up a Domain Changing the Server Name ii Installing TraceMasterVue and Configuring Communication

5 Table of Contents Adding SSL Support Requesting an SSL Certificate Installing the SSL Certificate on the TraceMasterVue Server Disabling the Non-Secure Port (Port 80) Disabling the Unsecure Port (Port 80) for Cardiograph Communication with the TraceMasterVue Server Disabling the Unsecure Port (Port 80) for WebAPI Interface Communication with the TraceMasterVue Server Enabling SSL on the PageWriter Touch Cardiograph Configuring ECG Import Configuring the Processing Capacity of the Server Configuring Inbound Directories Enabling Remote Desktop Access Chapter 5. Adding and Configuring Printers and Fax Capability Connecting the Printer Configuring the Printer Adding a Printer and Setting Up a TCP/IP Printer Port Changing Printer Priority Printing a Test Page Configuring Fax Capability Configuring Fax Using a Fax Cover Page Chapter 6. Setting Up Processes and Users Configuring Windows Services for Use with TraceMasterVue TraceMaster Communications Service Settings TraceMaster IO Proxy Service Settings TraceMaster Service Manager Service Settings TraceMaster Status Manager Service Settings Configuring Miscellaneous SQL Server Jobs Deleting Old Messages from the Database Permanently Removing ECGs Flagged as Deleted from the Database Restoring the TraceMasterVue DSN ODBC Connection Setting the Search and Edit Limits Setting the Patient Domain Configuring Users and Groups About TraceMasterVue Users About TraceMasterVue-Specific Windows Groups TraceMasterVue Groups and Associated Permissions Associating Users with TraceMaster Groups Configuring Security Roles Installing TraceMasterVue and Configuring Communication iii

6 Table of Contents Setting and Enabling System Options Running TraceMasterVue Utilities Enabling System Option Changes Starting and Stopping TraceMasterVue Stopping and Restarting IIS Resetting the Application Cache Accessing Online Help Adding SSL Support Requesting an SSL Certificate Installing the SSL Certificate on the TraceMasterVue Server Ensuring SSL-Only Communication Disabling SSL on the Client Installer Enabling SSL on the PageWriter Touch Cardiograph Enabling SSL in WebSelect Enabling SSL in the WebAPI Test Client Chapter 7. Setting Up and Configuring TraceMasterVue System Options Before You Begin Setting Global Options Setting the Statement Criteria Version Setting the System Address Setting Serial Comparison Criteria Configuring Interactive Query Support on TraceMasterVue Setting ECG Confirmation Authentication Requirements Configuring Inactivity Timeout Settings for ECGVue Configuring the Remember Me Option Configuring Import Directories and Formats Before You Begin Placing New ECGs into Inbound Directories Configuring Location Information in TraceMasterVue Before You Begin Configuring Institutions Configuring Facilities Configuring Departments Configuring User-Defined Field Values in TraceMasterVue Before You Begin Configuring the Physician List Before You Begin About Associating Physicians with Locations Importing Physician Data in CSV Format Manually Entering Physician Information Setting ECG Report Options Configuring Inboxes Before You Begin Defining Inboxes iv Installing TraceMasterVue and Configuring Communication

7 Table of Contents Defining Automated Workflow Rules Commonly Used Workflow Rules Before You Begin Defining a New Workflow Rule Defining Print, Fax, and Export Rules Adding Notification to a Rule Defining Aliases and Custom Statements Before You Begin Using Statement Aliases Enabling Statement Aliasing Defining Statement Aliases Configuring Custom Modifiers, Codes, and Statements Configuring Custom Modifiers and Codes Configuring Custom Statements Enabling Settings Completing TraceMasterVue Communication Configuration Installing ECGVue/PharmaVue on Client Systems Installing the Report Manager on Client Systems Verifying that the System Works Setting Up System and File Backups Configuring Cardiographs to Communicate with TraceMasterVue Chapter 8. Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue About PageWriter Touch Cardiograph Software Versions Configuring OrderVue Settings on the PageWriter Touch Cardiograph Configuring Multiple Cardiographs Configuration Steps Connecting Communication Hardware to the PageWriter Touch Cardiograph LAN Network Connection Wireless LAN Connection Wireless Connectivity Indicators Modem Connection About Network Settings Networking Overview DHCP Fixed IP Address Auto Negotiation Device IP Address Ping Test Installing TraceMasterVue and Configuring Communication v

8 Table of Contents Configuring Cardiograph Network Settings About Wired Ethernet and Wireless LAN Connectivity Using DHCP Configuring Remote Site Settings Configuring a Remote Site Network or a Remote Access Server (RAS) Connection with Modem Remote Site Security Feature Testing TraceMasterVue Remote Site Connectivity Editing Remote Site Settings Defining Institution Settings Special Note about Location Code (LOC) Patient ID Settings Patient ID Configuration Options Configuring Patient Information Configuring Clinical Information Configuring Order Information Configuring Additional Information Configuring Optional, User Defined Patient ID fields Configuring the User Defined Fields with OrderVue Configuring the User Defined Fields for FDA XML Export Patient ID Layout Settings Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Troubleshooting a Wired Connection Using Ping to Verify TraceMasterVue Server to PageWriter Touch Cardiograph Connectivity Troubleshooting a Wireless Connection Checking the Remote Site Server Connection Resolving an Unexplained Reply Received from the Remote Site Checking the Wireless Adapter Association to an Access Point Chapter 9. Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue Selecting Options on the PageWriter Trim Cardiograph Connecting Communication Hardware to the PageWriter Trim Cardiograph Before You Begin Configuring Location Information on the PageWriter Trim Cardiograph Defining User Fields on the PageWriter Trim Cardiograph Defining User Fields for FDA XML Export Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph Ensuring Interactive Query is Enabled Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue vi Installing TraceMasterVue and Configuring Communication

9 Table of Contents Troubleshooting Communication Issues between TraceMasterVue and PageWriter Trim Cardiographs Using Ping to Verify TraceMasterVue Server to PageWriter Trim Cardiograph Connectivity Chapter 10. Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue Connecting the Communication Hardware to a Legacy Cardiograph Before You Begin Configuring Remote Sites for Communication with Legacy Cardiographs Configuring a Remote Site for a Direct Connection Configuring a Remote Site for a Modem Connection Configuring Automatic Dialing to a Remote Site Configuring Locations and User Fields on Legacy Cardiographs Performing Interactive Queries Configuring Interactive Query on Legacy PageWriter XL-Series Cardiographs Testing the Connection Between the Cardiograph and the TraceMasterVue Server Troubleshooting Communication Issues between TraceMasterVue and Legacy PageWriter Cardiographs Chapter 11. Configuring the ECGVue Training System About the ECGVue Tutorial Demo ECG Characteristics Location of the Tutorial Files Running the ECGVue Tutorial Resetting the Demo ECGs Appendix A. About TraceMasterVue Users and Groups About the TraceMasterVue Security Model A-2 Overview of Methods A-2 About the Authorization Process A-2 About Windows Users and TraceMasterVue-Specific Groups A-2 User-Related Requirements for Running TraceMasterVue A-3 About TraceMasterVue Users A-4 Users Required on the TraceMasterVue Server A-5 About TraceMasterVue-Specific Windows Groups A-7 TraceMasterVue Groups and Associated Permissions A-8 Groups Required on the TraceMasterVue Server A-11 Required User-Group Associations A-13 About Database User IDs A-15 Required Database User IDs A-15 Installing TraceMasterVue and Configuring Communication vii

10 Table of Contents Changing User Permissions Using Security Roles A-15 Process for Defining Security Roles A-16 Security Role Examples A-16 Security Role Examples A-17 Examples of Making Access to Specific ECGs More Broad A-17 Example of Making Access to Specific ECGs More Restrictive A-18 Interaction with Active Directory A-19 About Users and Groups on the TraceMasterVue Server and in Active Directory.. A-19 Common Active Directory Use Models with TraceMasterVue A-20 Appendix B. Using Location Information in TraceMasterVue Configuring TraceMasterVue and Device Location Fields B-2 Location Matching in TraceMasterVue B-2 Location Matching when Importing an ECG from a Legacy Device B-3 Location Code Mapping for Legacy Cardiographs and TraceMaster Systems B-3 3:2 Location Format Processing B-4 1:2:2 Location Format Processing B-6 Configuring the ENABLE_LOC_OVERLOAD Registry Value B-7 Location Matching when Importing ECGs from Legacy ECG Management Systems B-9 Location Matching when Importing an ECG from a Non-Legacy Device B-10 About Unidentified Locations B-15 Deleting Location Entries B-16 About the Patient Domain B-16 Appendix C. About Custom Statements and Aliases Overview C-1 About Statement Aliasing C-2 Enabling Statement Aliasing C-4 Defining Statement Aliases C-5 Configuring Custom Modifiers, Codes, and Statements C-6 Configuring Custom Modifiers and Codes C-6 Configuring Custom Statements C-7 Appendix D. About User Fields Special Purpose User Fields D-1 User Field 1 Attributes D-2 Configuring User Fields and OrderVue D-2 Overriding the Facility Field with User Defined Field D-2 viii Installing TraceMasterVue and Configuring Communication

11 Table of Contents Appendix E. Field Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue Appendix F. Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue Communication between a TraceMasterVue System and Cardiographs F-2 RAS Configuration F-2 Hardware Prerequisites F-3 TraceMasterVue (RAS Server) Hardware Prerequisites F-3 PageWriter (RAS Client) Hardware Prerequisites F-4 Configuring TraceMasterVue (RAS Server) and the PageWriter Cardiographs (RAS Clients) F-4 Setting Up TraceMasterVue as the RAS Server F-4 Verifying COM Port Assignments on TraceMasterVue F-5 Configuring ECG Transmission and/or Interactive Query via RAS in TraceMasterVue.F-6 Enabling Interactive Query F-6 Configuring Serial Ports for RAS In TraceMasterVue F-6 Configuring Local User Accounts on TraceMasterVue F-8 Configuring RAS Access for User Accounts on TraceMasterVue F-9 Restarting Internet Information Services (IIS) F-10 Configuring and Enabling Routing and Remote Access on TraceMasterVue F-10 Configuring the RAS Server Port Properties F-11 Configuring RAS Server Properties F-15 Configuring Remote Access Policies F-18 Setting up the PageWriter Touch (RAS Client) F-22 Configuring Network Settings on the Cardiograph F-23 Configuring Settings on the Remote Sites > Network Tab F-23 Configuring Settings on the Net Connect Tab F-24 Saving the Cardiograph Network Settings F-25 RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System...F-25 Adding RAS and Serial Data Communication Support to a TraceMasterVue System..F-26 Removing Serial Communication Ports from RAS Ownership F-26 Adding RAS to an Existing TraceMasterVue System that Supports Legacy Serial Data Communication F-29 Adding Legacy Serial Data Communication Support to an Existing TraceMasterVue System that Supports RAS F-30 Installing TraceMasterVue and Configuring Communication ix

12 Table of Contents Appendix G. Clinical Observation Result Interface Before You Begin G-2 Configuring HL7 Export G-2 Configuring the Interface G-3 Selecting a Mapper G-3 Collecting Transmission Information G-4 Enabling HL7 Results Export G-5 Sharing the OrderVue Folder G-5 Configuring the Scheduler G-6 Defining Delimiters in the Mappers G-7 Configuring the Results + URL Mapper G-11 Configuring the MMQTransmitter Communication Client G-13 Resuming Scheduler Operation G-16 Testing MMQTransmitter Communication G-16 Configuring Workflow Rules G-17 Validating the HL7 Export Process G-19 HL7 Data Types G-20 XML to HL7 Data Mapping G-21 Sample HL7 Transmission G-23 Appendix H. Using TraceMasterVue with the HeartStart MRx Defibrillator System Requirements H-1 Configuring TraceMasterVue and Defibrillator Communication H-2 Configuring the Defibrillator for TraceMasterVue Communication H-2 Configuring the 12-Lead Transfer Station for TraceMasterVue Communication..... H-3 Appendix I. Using TraceMasterVue with the IntelliVue Information Center System Requirements I-2 IntelliVue Requirements I-2 TraceMasterVue Requirements I-2 Installing ECGVue or PharmaVue on Client Systems I-3 Configuring TraceMasterVue and IntelliVue Communication I-3 Configuring TraceMasterVue to Communicate with IntelliVue I-3 Configuring Location Information for TraceMasterVue IntelliVue Communication I-4 Configuring TraceMasterVue and Device Location Fields I-4 Location Matching in TraceMasterVue I-4 Location Matching when Importing an ECG from an IntelliVue or Antares System. I-5 Mapping the IntelliVue/Antares Institution Code I-5 Institution Code Mapping Format I-6 Institution Code Mapping Rules I-7 x Installing TraceMasterVue and Configuring Communication

13 Table of Contents Adding and Configuring the Registry Values I-8 Adding the Registry Values I-8 Configuring the Registry Values I-10 Appendix J. Configuring OrderVue for Use with TraceMasterVue and Cardiographs About OrderVue J-2 Installing and Configuring OrderVue J-2 Configuring Order-Related Settings for TraceMasterVue J-2 Configuring Primary Fields for Order Reconciliation J-3 Exporting ECGs for Final Order Processing J-4 Setting Up Order Inboxes on the Cardiographs J-6 Creating an Inbox J-7 Creating Inboxes on PageWriter Touch Cardiographs J-7 Setting General Order Settings on the Cardiograph J-9 Setting General Order Settings J-9 Testing Order Inbox Connectivity J-9 Editing Inbox Settings J-10 Order Data Table J-11 Configuring the ADT Option J-21 Index Installing TraceMasterVue and Configuring Communication xi

14 Table of Contents xii Installing TraceMasterVue and Configuring Communication

15 1 Chapter 1Getting Started The TraceMasterVue ECG Management System stores patient ECGs. It imports and stores ECGs from cardiographs and other devices. Physicians and techs can review and edit ECGs (depending on permissions). Via interactive query, ECGs are displayed at cardiographs. ECGs can also be exported to other formats, including PDF and TIF. You can define workflow rules that will automatically perform certain actions on ECGs that match specified criteria. Primary connections are to PageWriter Touch, PageWriterTrim, and legacy PageWriter XLseries cardiographs. With appropriate options, TraceMasterVue can also communicate with other devices and systems, including the IntelliVue Information Center, HeartStart MRx defibrillators (via the 12-lead Transfer Station), and the OrderVue orders handling system. After installing the system, the client application, and possible options, as well as configuring the network and printers, you must configure TraceMasterVue for use. After configuring TraceMasterVue, you configure the devices to communicate with TraceMasterVue. This guide describes all aspects of installing and configuring the entire system. NOTE If the customer has a policy of clearing off all factory-specified configuration information, user IDs and groups, and the like, make sure you review the section, Requirements for Running TraceMasterVue on page 1-16 before proceeding. Certain user IDs, groups, user/group associations, and services must be present and configured for TraceMasterVue to run and function properly. This chapter provides the following information: Before You Begin About TraceMasterVue Documentation Accessing Updates at InCenter About this Guide System Requirements and Components TraceMasterVue Components About the TraceMasterVue ECG Viewer/Editor, ECGVue or PharmaVue Running TraceMasterVue Applications TraceMasterVue System Requirements Database/Web Server Requirements Database Server Configuration Client Requirements TraceMasterVue Configuration Overview Before Configuring TraceMasterVue Requirements for Running TraceMasterVue Data Communication Methods

16 Getting Started Implementation Planning Collecting Required Information PageWriter XL-Series or 200/300 Cardiographs PageWriterTouch Cardiographs PageWriter Trim Cardiographs Installing Options Before You Begin Before proceeding, ensure you have the following documentation available: Instructions provided in this guide TraceMasterVue System Configuration and Reference Guide Documentation for any other options you might be installing and configuring If you are connecting to a Philips IntelliVue Information Center (IIC), have available the documentation provided with the Application Server and Database server. If you are configuring OrderVue, ensure you have the LinkTools CD and the OrderVue Installation and Confiugration guide. If you are connecting to a 12-Lead Transfer Station (to get ECGs from a HeartStart defibrillator), have available the 12-Lead Transfer Station User Guide and Implementation Guide. About TraceMasterVue Documentation Philips Medical Systems provides detailed instructional and reference materials to help you get the most out of your TraceMasterVue system. The following documentation is available with TraceMasterVue. It is strongly recommended that you review all of the documentation before using the system. Online Help system Every TraceMasterVue utility and application provides its own online help system that provides detailed information about its use. To access the Help system, click Help in any utility or application to access the main table of contents. Instructions for Use A reference that provides an overview of ECGVue/PharmaVue functionality, to assist you with editing and managing ECGs. Tutorial to learn how to use ECGVue/PharmaVue. Installing TraceMasterVue and Configuring Communication, this guide, to help you configure the system. Used in conjunction with the TraceMasterVue System Configuration and Reference Guide. 1-2 Installing TraceMasterVue and Configuring Communication

17 About TraceMasterVue Documentation TraceMasterVue FDA XML Mapping Guide, which provides detailed information about exporting ECGs to FDA XML format. If you have the Web API option, TraceMasterVue Web API Reference Guide, which describes the methods for a set of web services that allow external applications access to TraceMasterVue ECG data. This is a guide for application programmers. TraceMasterVue System Configuration and Reference Guide for information about configuring and maintaining the system. Philips 12-Lead Algorithm Physician Guide, which provides detailed information about the algorithm used to interpret ECGs, as well as a listing of all of the 0A version interpretive statements and codes. If you have the OrderVue option, additional documentation is available on the OrderVue Documentation CD. Accessing Updates at InCenter Updates to the documentation are provided periodically. To access the latest documentation, visit the Philips InCenter website, at If you do not yet have an InCenter user ID, register by clicking the link Click here for access to software updates and documentation for cardiology products on the right side of the page. A user ID and password will be sent to the address you provide, enabling access to TraceMasterVue documentation updates, as well as free software updates, when available. Documentation is also available at docdownload.asp. About this Guide This guide describes how to install and configure TraceMasterVue and its components. It is organized as follows: 1 Getting Started. This chapter. Describes the system components and requirements, and also provides an overview of the installation/configuration process. 2 Worksheets. Provides worksheets so you can easily collect data from the customer, and then configure the system with all the information available. 3 Installing TraceMasterVue Components. Describes how to set up the TraceMasterVue hardware and peripherals. 4 Configuring TraceMasterVue Communication. Describes how to configure modems and network connections for the system. 5 Configuring Printers and Fax Capability. Describes how to set up and configure printers and fax. Installing TraceMasterVue and Configuring Communication 1-3

18 Getting Started 6 Setting Up TraceMasterVue Processes and Groups. Describes how to configure the processes for running the system and importing ECGs, assign users to TraceMasterVue groups, and how to set application options. 7 Setting Up and Configuring TraceMasterVue System Options. Describes how to configure the system, including setting up inboxes, physicians, locations, automated workflow rules, printed reports, and the like. Once you finish this chapter, TraceMasterVue is fully configured for use. 8 Configuring PageWriterTouch Cardiographs for Use with TraceMasterVue. Describes how to configure communication with PageWriterTouch cardiographs. 9 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue. Describes how to configure communication with PageWriter Trim cardiographs. 10 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue. Describes how to configure communication with PageWriter Trim cardiographs. 11 Setting Up an End User Training System. Describes how to set up a client system with access to the tutorial files on the server, as well as how to reset the training ECGs to their default state. A B C D E F G About TraceMasterVue Users and Groups. Provides detailed information about how TraceMasterVue controls access to the application and provides permissions for different functions, both through TraceMasterVue-specific Windows groups and security roles. Also describes interactions with Active Directory. Using Location Information in TraceMasterVue. Provides detailed information about how TraceMasterVue uses and configures location information. About Custom Statements and Aliases. Provides detailed information about how custom statements and aliases are used in the system. About User Fields. Provides detailed information about how custom user fields are used in the system. Field Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue. Provides information about how patient data entry fields at the PageWriterTouch, PageWriter Trim and PageWriter XLi cardiographs map to the TraceMasterVue data fields. Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue. Describes how to set up RAS. Clinical Observation Result Interface. Provides a high-level overview of how to configure HL7 export on your system, and also provides some details about the HL7 interface 1-4 Installing TraceMasterVue and Configuring Communication

19 System Requirements and Components H I J Using TraceMasterVue with the HeartStart MRx Defibrillator. Provides an overview of how to configure the 12-Lead Transfer Station to communicate with the TraceMasterVue system. This allows transfer of ECGs from the defibrillator to TraceMasterVue. Using TraceMasterVue with the IntelliVue Information Center. Provides an overview of how to set up data communication between the IIC and TraceMasterVue. Configuring OrderVue for Use with TraceMasterVue and Cardiographs. Provides an overview of how to set up data communication between OrderVue and TraceMasterVue. Includes a section on ADT. System Requirements and Components The TraceMasterVue ECG Management system comprises a suite of applications, including the ECG viewer/editor, PharmaVue or ECGVue; optional order handling system, OrderVue; and system tools. The system tools are accessed primarily by the TraceMasterVue administrator and Philips representatives. The following sections describe the components of the TraceMasterVue system and minimum hardware and software requirements for running the system. For details, see: TraceMasterVue Components on page 1-5 TraceMasterVue System Requirements on page 1-9 Requirements for Running TraceMasterVue on page 1-16 TraceMasterVue Components The TraceMasterVue ECG Management system comprises a suite of applications, including ECG management tools (ECGVue/PharmaVue and, optionally, CalECG (with PharmaVue only) and/or OrderVue) and system tools. The system tools are accessed primarily by the TraceMasterVue administrator and Philips representatives. Installing TraceMasterVue and Configuring Communication 1-5

20 Getting Started The TraceMasterVue system comprises the following components: Table 1-1 TraceMasterVue components Component Icon Description Client application PharmaVue client ECGVue client The TraceMasterVue client application allows the user to access the ECGs in the database. The client applications are ECGVue and PharmaVue (described below). Only one client is used with a TraceMasterVue implementation; the system is either configured for ECGVue or for PharmaVue. Some features and options are available only in conjunction with the PharmaVue. They are noted as PharmaVue only in the documentation and online help. The TraceMasterVue ECG viewer/editor, PharmaVue, provides access to the ECGs in the database, allowing you to review, annotate, compare, confirm, and print/export ECGs, as well as run clinical reports. The Trend view within the application allows you to review multiple QT measurements for a single subject to determine trends. The export option allows you to export ECGs to multiple formats, including the XML format used for FDA submissions. PharmaVue is available as an option to TraceMasterVue, and takes the place of the ECGVue application. The TraceMasterVue ECG viewer/editor, ECGVue, provides access to the ECGs in the database, allowing you to retrieve, view, edit, assign, confirm, and print or fax ECGs, as well as run clinical reports. 1-6 Installing TraceMasterVue and Configuring Communication

21 System Requirements and Components Table 1-1 TraceMasterVue components (continued) Component Icon Description OrderVue TraceMasterVue server Audit and Tracking Viewer Management Reports This optional module allows you to retrieve and reconcile ECG orders. If you have the option, orders functionality is integrated both with the ECGVue/PharmaVue client and in the System Configuration utility. If you have the bi-directional order option, functionality is also integrated with PageWriterTouch cardiographs. For details, see the documentation provided on the Documentation CD (and InCenter). The Admit/Discharge/Transfer (ADT) option allows OrderVue to accept updates to patient information in the order from the HIS. For detailed information about configuring the OrderVue or ADT option, see the ADT Installation And Configuration Guide and associated documentation, provided on the OrderVue Documentation CD. The server houses the ECG database and other TraceMasterVue components. This utility provides access to the audit and tracking functions, and is accessed by the TraceMasterVue administrator. For details, see Chapter 10, Configuring and Using the Audit and Tracking Viewer, of the TraceMasterVue System Configuration and Reference Guide. This utility provides access to the TraceMasterVue management reports. It is available on the TraceMasterVue server, and can also be installed on client systems for enduser access. Also referred to as the Report Manager. For details, see the Report Manager Instructions for Use. Installing TraceMasterVue and Configuring Communication 1-7

22 Getting Started Table 1-1 TraceMasterVue components (continued) Component Icon Description System Configuration utility System Monitor Statement Manager Log Viewer Enterprise Manager WebAPI This utility defines the configuration options, security roles, and automated workflow rules for the TraceMasterVue installation at your facility. Many of these options affect the TraceMasterVue client, ECGVue/PharmaVue. It is accessed by the TraceMasterVue administrator. This utility allows the TraceMasterVue administrator to view system status and run diagnostic tests and reports. For details, see Chapter 8, System Operation and Maintenance, of the TraceMasterVue System Configuration and Reference Guide. This utility allows the TraceMasterVue administrator to define custom coded statements and modifiers. For details, see Defining Aliases and Custom Statements on page This utility allows the TraceMasterVue administrator to review error and system logs. For details, see Chapter 9, Data Communication and Management, of the TraceMasterVue System Configuration and Reference Guide. This utility allows the TraceMasterVue administrator to export selected ECGs from the TraceMasterVue database directly to any of several supported formats, including FDA XML, Philips XML, PDF, SVG, and TIFF, depending on which options are enabled at your site. For details, see Chapter 9, Data Communication and Management, of the TraceMasterVue System Configuration and Reference Guide. This option allows you to programmatically access ECGs in the TraceMasterVue database. For details, see the WebAPI Reference Guide. 1-8 Installing TraceMasterVue and Configuring Communication

23 System Requirements and Components About the TraceMasterVue ECG Viewer/Editor, ECGVue or PharmaVue The TraceMasterVue ECG viewer/editor (also referred to as the TraceMasterVue client or client application), ECGVue or PharmaVue, allows users to retrieve, view, and edit ECGs. It is available on PCs connected to your facility s LAN, and is also accessible over the Internet from home or other web-enabled PC. The client provides several basic screens, called views, a free-floating Statement Editor, and an Action bar for working with ECGs. For an overview of ECGVue/PharmaVue, see the ECGVue Instructions for Use. For detailed information about using the client to view and edit ECGs, refer to the online help within the application. Running TraceMasterVue Applications Each utility or application has a shortcut on the TraceMasterVue server desktop. Client system desktops have a shortcut only to ECGVue/PharmaVue. Users log in with their regular Windows user ID and password into ECGVue/PharmaVue. Before they can log in, you must ensure they are enabled as an ECGVue/PharmaVue user, by being added to the appropriate TraceMaster groups. For details, see Appendix A, About TraceMasterVue Users and Groups. Application permissions are associated with the Windows user ID. For additional details about logging in, refer to the TraceMasterVue System Configuration and Reference Guide. To run TraceMasterVue applications 1 On the server desktop, double-click the desired application icon. You are prompted to log in. 2 Type your credentials and click OK. The main page of the selected application appears. To run ECGVue/PharmaVue 1 Double-click the application icon on the desktop. The splash screen appears, and after a short time interval, the Log in screen. 2 Log into the application. The Quick Search page appears. You can now specify the search criteria to locate and retrieve the ECGs to work with. TraceMasterVue System Requirements For TraceMasterVue to function properly, specified system requirements must be met. The requirements to run the components listed below are different, as described in the tables that follow. TraceMasterVue database server. Stores the TraceMasterVue database. All users access this server indirectly when using TraceMasterVue software on a client system. Direct access by logging on to the server is restricted for system administration use. You should not install third-party software on this system, as it may affect performance, reliability and security. Installing TraceMasterVue and Configuring Communication 1-9

24 Getting Started TraceMasterVue web server. Provides the TraceMasterVue web service. This system may physically be the same as the database server. TraceMasterVue standard client. Connected to the server directly over a network. TraceMasterVue software is installed on this client to enable network access to the TraceMasterVue servers. As this system is generally used for functions other than simply ECG management, third-party software may be installed. Remote TraceMasterVue web client. Connected over the web to the TraceMasterVue server(s). Access is enabled based on the level of security, for example, firewalls, you might have installed. Local TraceMasterVue web client. Equivalent to the remote client, except that the level of connection is stronger, resulting in faster response time. The local client may be within the firewall. Database/Web Server Requirements The following table describes the minimum hardware and software requirements to run the TraceMasterVue database and web servers (which may reside on the same hardware). Table 1-2 Component Server requirements Minimum Hardware/Software Specifications Computer Standard Edition, Enterprise Edition: Single Dual Core Processor, Intel Xeon Processor 5080 Dual core / 3.73 GHz / 1066MHz FSB Universal Edition: Double Dual Core Processor, Intel Xeon Processor 5080 Dual core / 3.73 GHz / 1066MHz FSB Memory Standard Edition: 2 GB Enterprise Edition: 4 GB Universal Edition: 8 GB Advanced memory protection Universal Edition: Online spare Storage Standard Edition, Enterprise Edition: Smart Array P400 Controller with 256MB memory module supports RAID 0/ 1/5 Universal Edition: (2) Smart Array P400 Controller with 512MB memory module supports RAID 0/1/5/ Installing TraceMasterVue and Configuring Communication

25 System Requirements and Components Table 1-2 Component Server requirements (continued) Minimum Hardware/Software Specifications Drives Standard Edition: (1) 8-bay cage, (2) 36GB 3G SAS 10K SFF SP HDD (RAID1 boot), (3) 36GB 3G SAS 10K SFF SP HDD (RAID5 data), (3) empty expansion slots for future MultiModality option (approx. 14,280 ECGs consume 1 GB) Enterprise Edition: (1) 8-bay cage, (2) 36GB 3G SAS 10K SFF SP HDD (RAID1 boot), (3) 146GB 3G SAS 10K SFF SP HDD (RAID5 data), (3) empty expansion slots for future MultiModality option (2 million ECGs require approx. 140 GB of storage) Universal Edition: (2) 8-bay cages, (2) 36GB 3G SAS 10K SFF SP HDD (RAID1 boot), (8) 146GB 3G SAS 10K SFF SP HDD (RAID5 data), (6) empty expansion slots for future MultiModality option Storage limit Standard Edition: 500,000 ECGs Enterprise Edition: 2,000,000 ECGs Universal Edition: 10,000,000 ECGs Backup device Standard Edition: StorageWorks DAT 72 SCSI Tape Drive (72GB/cartridge) Enterprise Edition: Ultrium 460 tape drive (400GB/cartridge) Universal Edition: Ultrium 960 tape drive (800GB/cartridge) CD/DVD DVD±R/RW Slim 16 Video UPS Network 128 bit video adapter Uninterruptible Power Supply (UPS) (recommended) For Universal Edition, redundant power supply provided. Embedded Dual NC373i Multifunction Gigabit Network Adapters with TCP/IP Offload Engine OS Standard Edition, Enterprise Edition: Windows Server 2003 Standard Edition, with Service Pack 1 Universal Edition: Windows Server 2003 Enterprise Edition Database Barcode reader/scanner SQL Server 2000 SP 4, and any current security upgrades as required For barcode support Installing TraceMasterVue and Configuring Communication 1-11

26 Getting Started Table 1-2 Component Modem Server requirements (continued) Minimum Hardware/Software Specifications External modem for exclusive support of remote support and fax. If using additional modems, RocketPort COM extender card. To connect to remote clients via modem, add additional modems. To connect to legacy PageWriter XL-series cardiographs and/or PageWriter Touch cardiographs, add additional modems. Supporting applications (Web server requirement) Microsoft SQL Server 2000 (Standard Edition and SP 4) Symantec Norton AntiVirus (v. 08 or later) AnalogX TSDropCopy (freeware) Seagate Crystal Reports IDautomation linear barcode Control * ActiveX codesigning certificate Server applications (Web server requirement) TraceMasterVue server software Bi-directional communication module (if installing OrderVue or HL7 options) Location code limits? Standard Edition: Yes Enterprise Edition: Yes Universal Edition: No Talk to your Philips representative for details on limits on number of institutions/facilities/departments that apply to the Standard and Enterprise Editions Installing TraceMasterVue and Configuring Communication

27 System Requirements and Components Database Server Configuration The database server, as shipped, is configured as follows: Table 1-3 Database server configuration Disk Array TraceMasterVue System Component Disks Configuration System Standard/ Enterprise Edition 2 x 36GB RAID 1 (Mirrored disks) Data Standard Edition 3 x 36 GB RAID 5 Enterprise Edition 3 x 146 GB RAID 5 Universal Edition 3 x 300 GB RAID 5 Table 1-4 TraceMasterVue server content, as shipped Disk Content C: Main logical unit; contains all files and programs, including the SQL Program files and dbems_data transaction log. Size 30 GB D: Utility Disk E: TraceMasterVue data Miscellaneous files and utilities, for the convenience of field support SQL databases, including TracemasterVue databases: dbems.mdb, dbemsconfig.mdb, and respective logs, except dbems_data transaction log. 5 GB Standard Edition: 72 GB Enterprise Edition: 290 GB Universal Edition: 570 GB Client Requirements A client system, connected to the server over a network, must meet the following requirements. Table 1-5 Component Processor Memory Hard disk Video Client requirements Minimum Hardware/Software Specifications Intel Pentium III 500 MHz 512 MB 4 GB Any DirectDraw capable video card capable of 1024 x 768 with 65 K (16 bit) colors Network Interface card supporting 100 Base-T communications TCP/IP protocol stack Barcode scanner Barcode scanner for rapid data entry Installing TraceMasterVue and Configuring Communication 1-13

28 Getting Started Table 1-5 Component OS Supporting applications Client requirements (continued) Minimum Hardware/Software Specifications Microsoft Windows 2000 or XP Microsoft.Net runtime environment Client applications ECGVue/ software (installed via URL to server) TraceMasterVue Report Manager client (optional) Database Microsoft OLEDB provider for SQL Server TraceMasterVue Configuration Overview This guide describes how to install and configure the TraceMasterVue system for a particular site. Each site has its own unique characteristics that must be defined for TraceMasterVue, and its own set of devices that will be connected to or interacting with the system. Most of these characteristics are set using the System Configuration utility. The options set here determine some of the default settings used by the ECG viewer/editor, ECGVue/ PharmaVue, as well as how ECGs are imported into and exported out of the system, and what type of automated processing occurs. To ensure a smooth installation, you must have certain information on hand before beginning the configuration process, described in the next section. Before Configuring TraceMasterVue At the end of this chapter is an installation checklist you can use to help ensure you have covered the essential configuration tasks. For details, see Chapter 2, TraceMasterVue Communication Worksheets. Table 1-6 Tasks to configure TraceMasterVue Information to Have Available For the medical devices that will be interacting with TraceMasterVue, note the: User field settings Location definitions and codes Referring (ordering) physicians How this Information is Used TraceMasterVue and the medical devices that will be interacting with the TraceMasterVue system, such as cardiographs and patient monitoring systems, must be in sync. That is, they must use the same location codes and user field definitions, and must be able to communicate over the network. For details about specifying this data, see Chapter 7, Setting Up and Configuring TraceMasterVue System Options. NOTE If you are also configuring OrderVue at your site, see the OrderVue Installation and Configuration Guide and related documentation, available on the OrderVue Documentation CD Installing TraceMasterVue and Configuring Communication

29 TraceMasterVue Configuration Overview Table 1-6 Tasks to configure TraceMasterVue (continued) Information to Have Available Identify all of the devices or systems that will connect to the TraceMasterVue system and determine how the connection will occur. Have available the list of user IDs for each person who will access the system, and, for each TraceMasterVue (and ECGVue/ PharmaVue) user, note the level of access the user is to have to ECGs and to the TraceMasterVue system. Determine how inboxes will be used at the site, and how to label them. Understand the ECG workflow process at the site, and identify what actions should be automated. Will the Philips order handling system, OrderVue, be installed? Will TraceMasterVue be communicating with a Philips IntelliVue Information Center? Will TraceMasterVue be communicating with cardiographs? How this Information is Used TraceMasterVue supports different communication methods, depending on the device type. For an overview, see Data Communication Methods on page Access to ECGs and specific editing capabilities are controlled by security permissions, which are associated with different TraceMasterVue-specific Windows groups. To be able to access TraceMasterVue applications, you must assign each user to one or more TraceMasterVue-specific Windows groups. For example, if Dr. Smith is a confirming cardiologist, you must add her user ID to the TraceMaster_ConfCardio group. In addition, if you need to specify additional permissions for a particular user, you will create a security role for that user in the TraceMasterVue System Configuration utility. For details about security and permissions, see Appendix A, About TraceMasterVue Users and Groups. Inboxes are containers to which ECGs are assigned. Assigning an ECG to an inbox allows a configured set of users to have quick access to these ECGs; it also allows automated workflow rules to perform defined actions on ECGs based on the inbox to which they are assigned. You will need to configure inbox names and usage. For details, see Configuring Inboxes on page For example, do ECGs at the site get printed upon confirmation, do users want notification when certain events occur, and so on. You will define automated workflow rules to execute these actions. For details, see Defining Automated Workflow Rules on page There are additional configuration requirements. For details, see the OrderVue Installation and Configuration Guide. There are additional configuration requirements. For details, see Appendix I, Using TraceMasterVue with the IntelliVue Information Center. You must configure communication. For details, see the cardiograph-related chapters in this guide. Installing TraceMasterVue and Configuring Communication 1-15

30 Getting Started Table 1-6 Tasks to configure TraceMasterVue (continued) Information to Have Available Network printers or standalone printer identifying information How this Information is Used You must configure one or more printers for the TraceMasterVue server to access. See Chapter 5, Adding and Configuring Printers and Fax Capability. Requirements for Running TraceMasterVue While configuring the TraceMasterVue system comprises many components and possible options, the following table describes the settings that must be configured and the users/groups that must be present on the system in order for it to operate properly. Some customers harden any system at their facility by removing factory-installed settings and configuring their own settings. This section describes the minimum set of information that must be configured, and how. Table 1-7 TraceMasterVue requirements Required Components Windows users Windows groups User/group correlations Database users Description TraceMasterVue uses Windows user IDs and TraceMasterVue-specific Windows group affiliations to determine access permissions. The system ships with a default set of users installed; this set must remain on the system. For details, see Appendix A, About TraceMasterVue Users and Groups. The system ships with a default set of groups installed; this set must remain on the system. For details, see Appendix A, About TraceMasterVue Users and Groups. Certain user IDs must be associated with specific groups for the system to function correctly. For details, see Appendix A, About TraceMasterVue Users and Groups. SQL Server 2000 requires two specific database users associated with TraceMasterVue; these users must remain on the system. For details, see Appendix A, About TraceMasterVue Users and Groups Installing TraceMasterVue and Configuring Communication

31 Data Communication Methods Table 1-7 TraceMasterVue requirements (continued) Required Components Share folders Windows services TraceMasterVue DSN ODBC Connection RAS Configuration of COM Ports Description Communication with the IntelliVue Information Center (IIC), option (#C20), requires that a specific shared folder be configured. For details, see Appendix I, Using TraceMasterVue with the IntelliVue Information Center. Certain Windows services are used by TraceMasterVue, and must be configured appropriately. For details, see Chapter 6, Setting Up Processes and Users. TraceMasterVue requires a DSN ODBC system data source connection, named viper, to allow the TraceMasterVue ECG Translator to access TraceMasterVue criteria and serial comparison statements. For details, see Chapter 6, Setting Up Processes and Users. TraceMasterVue requires that some COM ports be configured for Routing and Remote Access (RAS) connections, to allow cardiographs to communicate with the server via serial connections. A RAS connection is also required for Philips Medical Systems support personnel to access and support the server. For details, see Chapter 4, Configuring the Network for TraceMasterVue Data Communication. Data Communication Methods TraceMasterVue communicates with the following cardiographs, devices, and systems: PageWriterTouch and PageWriter Trim PageWriter XL-series, as well as PageWriter 200 and 300 HeartStart MRx defibrillator (using the 12-lead Transfer Station) IntelliVue monitoring system (with appropriate option) OrderVue order handling system (with appropriate option) Admit/Discharge/Transfer (ADT) (with appropriate option) Installing TraceMasterVue and Configuring Communication 1-17

32 Getting Started TraceMasterVue supports several different data transfer methods, depending on the device, as follows: Local area network (LAN) (wired and wireless, depending on device) Direct serial connection to a COM (RS-232) port, with or without modem Direct connect cable connected to a serial communications port on TraceMasterVue and on the device receiving or sending ECG data and order information Modem connected to serial communications port Table 1-10 on page 19 lists which modems are compatible with each legacy PageWriter cardiograph software version. Remote Access Service using modem; this method mimics a LAN. TraceMasterVue is set up as the RAS server and the cardiograph is set up as the RAS client Floppy diskette and PC card on some systems Table 1-8 Tables 1-8 and 1-9 provide details about each device s supported data transfer methods. Device to TraceMasterVue data transfer methods Device LAN RAS Modem Direct Serial Connection Diskette PC card PageWriterTouch cardiograph PageWriter Trim cardiograph II and III PageWriter XL-series cardiograph HeartStart MRx defibrillator IntelliVue Information Center (IIC) Table 1-9 TraceMasterVue to device data transfer methods Device LAN RAS Modem Direct Serial Connection Diskette PC card PageWriterTouch cardiograph PageWriter Trim cardiograph II and III PageWriter XL-series cardiograph IntelliVue Information Center (IIC) The following table lists which modems are compatible with which version of legacy PageWriter cardiograph software Installing TraceMasterVue and Configuring Communication

33 Data Communication Methods Table 1-10 Legacy PageWriter cardiograph modem compatibility chart M1700A Software Version Hayes Smartmodem Hayes Optima Model (288, 336, 56k) U.S. Robotics Worldport U.S. Robotics Sportster A.01.xx Yes No No No A.02xx A.03.x1 Yes No Yes No A.03.x3 Yes Yes No No A Yes Yes No Fax No DT Yes A & A Yes Yes No Yes A Yes Yes No Yes Installing TraceMasterVue and Configuring Communication 1-19

34 Getting Started Implementation Planning Before you start configuring communication between cardiographs and TraceMasterVue, you must map out your site, identifying which devices will communicate with the TraceMasterVue system, and how each one will perform this communication. Refer to Tables 1-8 and 1-9 on page 1-18 to identify the supported methods for each device. In general, this step is performed as part of the overall TraceMasterVue implementation planning process, and you will have been given a set of worksheets to complete. A copy of the worksheets is provided in Chapter 2, TraceMasterVue Communication Worksheets, at the end of this document. In a nutshell, communication is generally set up as follows: PageWriterTouch and Trim cardiographs communicate either over the LAN or using a modem through the remote access service (RAS). Legacy PageWriter XLi (and 200, 300) cardiographs communicate either through a direct connection or using a modem; transfer of ECGs via diskette is also supported. HeartStart MRx defibrillators, and the IntelliVue Information Center generally send ECGs to a designated folder over a LAN. COM ports are generally assigned using the following conventions: COM 1 is used for RAS (for remote support). If the site has a remote support network (RSN) in place that uses a router and the network, rather than a modem, you can use this port for other devices. COM 2 is used for fax. COM 3 and 4 are reserved for direct connections to legacy PageWriter XL-series cardiographs. If the site does not use these cardiographs, or will be using modems or diskettes for communication, you can use these ports for other devices. COM 5 through 10 are available for all other connections (direct or modem). Ports on the octa-cable connected to the TraceMasterVue server are associated with COM ports as described on page 4-2. Modems require analog phone lines, with a distinct phone number for each modem. The following sections describe, in detail, how to set up communication between TraceMasterVue and supported cardiographs. All configuration steps on both the cardiographs and the TraceMasterVue system are included. This guide describes how to set up TraceMasterVue first, then each of the cardiographs: PageWriterTouch, PageWriter Trim, and legacy PageWriter Installing TraceMasterVue and Configuring Communication

35 Implementation Planning Collecting Required Information Before proceeding, ensure you have the following information and hardware available: Completed TraceMasterVue Communication Worksheets (see Chapter 2, TraceMasterVue Communication Worksheets ) All required modems and cables, direct connect cables and junction box, and octa-cable Access and permissions to the TraceMasterVue server and the cardiographs/devices/ systems to configure Documentation for all the cardiographs, devices, and options you are installing and configuring Licenses for options, where appropriate To minimize the number of times you must reboot systems, we recommend that you configure communication in the following order: 1 Plan how the systems will be interconnected, and collect all information required for the Configuration worksheets. Most worksheets you will need are provided in this guide. 2 Determine all the devices that will be connected to the system, as well as all options that will be installed. 3 Connect all hardware to the TraceMasterVue system, including modems and any direct connections (if applicable). 4 Configure the hardware on the TraceMasterVue system, and assign COM ports as appropriate. 5 Configure the TraceMasterVue system: Configure IP address and network settings Configure legacy cardiograph support (if applicable) and interactive query for all applicable devices Configure location information Set up users/groups Set up inboxes Set up physician list Define automated workflow rules Define custom statements or aliases, if needed Configure share folders, if appropriate 6 Reboot the TraceMasterVue system. 7 Connect the hardware on each cardiograph. 8 Configure each cardiograph and device for communication with TraceMasterVue: Installing TraceMasterVue and Configuring Communication 1-21

36 Getting Started Configure network and remote site settings If you will be communicating with a Philips 12-Lead Transfer Station (to receive ECGs from HeartStart MRx defibrillators), configure TraceMasterVue as an application on the 12-Lead Transfer Station. Refer to Chapter H, Using TraceMasterVue with the HeartStart MRx Defibrillator and the 12-Lead Transfer Station documentation. Configure location information Configure interactive query support, if needed Define the labels for user-defined fields If your site will be exporting ECGs to FDA XML, see the FDA XML section for the appropriate cardiograph, as well as the TraceMasterVue FDA XML Mapping Guide. 9 Test communication between each device and the TraceMasterVue system. 10 Help the customer set up system backups. The information presented here is organized in this order. To help guide you through the wealth of information in this guide, find the configuration you want to set up below to direct you to the sections containing the details you need now Installing TraceMasterVue and Configuring Communication

37 Implementation Planning PageWriter XL-Series or 200/300 Cardiographs These legacy cardiographs can communicate with a TraceMasterVue system either using a direct serial connection or via a modem. Read the following sections, in order Implementation Planning on page 1-20 Chapter 2, TraceMasterVue Communication Worksheets TraceMasterVue Configuration Either of: Setting Up a Direct Connection on page 4-2 Installing Data Transfer Modems on page 4-6 Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7 Cardiograph Configuration Connecting the Communication Hardware to a Legacy Cardiograph on page 10-2 Configuring Remote Sites for Communication with Legacy Cardiographs on page 10-4 Freeing COM Ports from the Fax Utility and RAS on page 4-11 Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue on page 4-18 Configuring Interactive Query Support on TraceMasterVue on page 7-8 You generally do not need to do anything to enable a remote site for interactive query. It is ready to go. Configuring Users and Groups on page 6-17 Configuring Location Information in TraceMasterVue on page 7-15 Configuring Locations and User Fields on Legacy Cardiographs on page 10-9 Configuring the Physician List on page 7-19 Configuring Inboxes on page 7-26 Defining Automated Workflow Rules on page 7-28 Configuring Custom Modifiers, Codes, and Statements on page 7-40 Completing TraceMasterVue Communication Configuration on page 7-42 Testing the Connection Between the Cardiograph and the TraceMasterVue Server on page Installing TraceMasterVue and Configuring Communication 1-23

38 Getting Started PageWriterTouch Cardiographs These cardiographs can communicate with a TraceMasterVue system either over a LAN (wired or wireless) or via a modem using RAS. Wired or Wireless LAN Read the following sections, in order Implementation Planning on page 1-20 Chapter 2, TraceMasterVue Communication Worksheets TraceMasterVue Configuration No configuration needed. Configuring Interactive Query Support on TraceMasterVue on page 7-8 Configuring Users and Groups on page 6-17 Configuring Location Information in TraceMasterVue on page 7-15 Configuring the Physician List on page 7-19 Configuring Inboxes on page 7-26 Defining Automated Workflow Rules on page 7-28 Cardiograph Configuration Connecting Communication Hardware to the PageWriter Touch Cardiograph on page 8-3 on page 8-29 Remote Site Security Feature on page 8-17 Defining Institution Settings on page 8-21 Configuring Optional, User Defined Patient ID fields on page 8-28 If you will be exporting ECGs to FDA XML, see Configuring the User Defined Fields for FDA XML Export on page 8-29 Configuring Custom Modifiers, Codes, and Statements on page 7-40 Completing TraceMasterVue Communication Configuration on page 7-42 Testing TraceMasterVue Remote Site Connectivity on page Installing TraceMasterVue and Configuring Communication

39 Implementation Planning Modem Read the following sections, in order Implementation Planning on page 1-20 Chapter 2, TraceMasterVue Communication Worksheets TraceMasterVue Configuration Installing Data Transfer Modems on page 4-6 Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7 Freeing COM Ports from the Fax Utility and RAS on page 4-11 Configuring Interactive Query Support on TraceMasterVue on page 7-8 Configuring Users and Groups on page 6-17 Configuring Location Information in TraceMasterVue on page 7-15 Configuring the Physician List on page 7-19 Configuring Inboxes on page 7-26 Defining Automated Workflow Rules on page 7-28 Configuring Custom Modifiers, Codes, and Statements on page 7-40 Completing TraceMasterVue Communication Configuration on page 7-42 Cardiograph Configuration Connecting Communication Hardware to the PageWriter Touch Cardiograph on page 8-3 on page 8-29 Remote Site Security Feature on page 8-17 Defining Institution Settings on page 8-21 Configuring Optional, User Defined Patient ID fields on page 8-28 If you will be exporting ECGs to FDA XML, see Configuring the User Defined Fields for FDA XML Export on page 8-29 Testing TraceMasterVue Remote Site Connectivity on page 8-20 Installing TraceMasterVue and Configuring Communication 1-25

40 Getting Started PageWriter Trim Cardiographs These cardiographs can communicate with a TraceMasterVue system either over a LAN or via a modem using RAS. LAN Read the following sections, in order Implementation Planning on page 1-20 Chapter 2, TraceMasterVue Communication Worksheets TraceMasterVue Configuration No configuration needed. Configuring Interactive Query Support on TraceMasterVue on page 7-8 Configuring Users and Groups on page 6-17 Configuring Location Information in TraceMasterVue on page 7-15 Configuring the Physician List on page 7-19 Configuring Inboxes on page 7-26 Defining Automated Workflow Rules on page 7-28 Configuring Custom Modifiers, Codes, and Statements on page 7-40 Completing TraceMasterVue Communication Configuration on page 7-42 Cardiograph Configuration Connecting Communication Hardware to the PageWriter Trim Cardiograph on page 9-2 Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph on page 9-8 Ensuring Interactive Query is Enabled on page 9-14 Configuring Location Information on the PageWriter Trim Cardiograph on page 9-4 Defining User Fields on the PageWriter Trim Cardiograph on page 9-5 If you will be exporting ECGs to FDA XML, see Defining User Fields for FDA XML Export on page 9-5 Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue on page Installing TraceMasterVue and Configuring Communication

41 Implementation Planning Modem Read the following sections, in order Implementation Planning on page 1-20 Chapter 2, TraceMasterVue Communication Worksheets TraceMasterVue Configuration Installing Data Transfer Modems on page 4-6 Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7 Freeing COM Ports from the Fax Utility and RAS on page 4-11 Configuring Interactive Query Support on TraceMasterVue on page 7-8 Configuring Users and Groups on page 6-17 Configuring Location Information in TraceMasterVue on page 7-15 Configuring the Physician List on page 7-19 Configuring Inboxes on page 7-26 Defining Automated Workflow Rules on page 7-28 Configuring Custom Modifiers, Codes, and Statements on page 7-40 Completing TraceMasterVue Communication Configuration on page 7-42 Cardiograph Configuration Connecting Communication Hardware to the PageWriter Trim Cardiograph on page 9-2 Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph on page 9-8 Ensuring Interactive Query is Enabled on page 9-14 Configuring Location Information on the PageWriter Trim Cardiograph on page 9-4 Defining User Fields on the PageWriter Trim Cardiograph on page 9-5 If you will be exporting ECGs to FDA XML, see Defining User Fields for FDA XML Export on page 9-5 Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue on page 9-14 Installing TraceMasterVue and Configuring Communication 1-27

42 Getting Started Installing Options If you will be communicating with a 12-Lead Transfer Station to import ECGs from HeartStart MRx defibrillators, see Appendix H, Using TraceMasterVue with the HeartStart MRx Defibrillator, in addition to the HeartStart MRx documentation. If you have the IntelliVue Connectivity option, see Appendix I, Using TraceMasterVue with the IntelliVue Information Center, in addition to the IntelliVue documentation. If you have the Orders option, see Appendix J, Configuring OrderVue for Use with TraceMasterVue and Cardiographs, in addition to the OrderVue documentation Installing TraceMasterVue and Configuring Communication

43 Chapter 2TraceMasterVue Communication Worksheets 2 TIP The worksheets on the following pages gather all of the relevant TraceMasterVue and cardiograph information that you need to properly configure your systems. Collect the information on these worksheets from the customer before configuring communication between your cardiographs (and other devices) and TraceMasterVue. The following worksheets are available for data collection: Installation and Configuration Checklist Communication Configuration Checklist Transmission and Phone Configuration Worksheet COM Port Assignment and Phone Number Worksheet TraceMasterVue Network Configuration PageWriterTouch/Trim Cardiograph Connection Configuration PageWriter XL Cardiograph Connection Configuration Location Worksheet User-Defined Fields Worksheet User Access Worksheet TraceMasterVue Group Permissions Table Physician List Worksheet Inboxes Worksheet Automated Workflow Rules Worksheet Order Inboxes Worksheet

44 TraceMasterVue Communication Worksheets Installation and Configuration Checklist Collect Site-Specific Information For the medical devices that will be interacting with TraceMasterVue, note the: User field settings Location definitions and codes Device name/id Ordering (referring) physicians Identify all of the devices or systems that will connect to the TraceMasterVue system and determine how the connection will occur (modem, serial direct connection, LAN, RAS). Have available the list of user IDs for each person who will access the system, and, for each TraceMasterVue (and ECGVue/PharmaVue) user, note the level of access the user is to have to ECGs and to the TraceMasterVue system (for example, confirming cardiologist, system admin, and so on). Determine how inboxes will be used at the site, and how to label them. Understand the ECG workflow process at the site, and identify what actions should be automated. Have the network printer or standalone printer information. Will TraceMasterVue be communicating with cardiographs? If yes, see the cardiographrelated chapters in this guide. Will TraceMasterVue be communicating with a Philips IntelliVue Information Center? If yes, see Chapter I, Using TraceMasterVue with the IntelliVue Information Center.. Will the Philips order handling system, OrderVue, be installed? If yes, see Appendix J, Configuring OrderVue for Use with TraceMasterVue and Cardiographs. and the OrderVue Installation and Configuration Guide. Will TraceMasterVue be communicating with HeartStart MRx defibrillators? If yes, see Appendix H, Using TraceMasterVue with the HeartStart MRx Defibrillator. 2-2 Installing TraceMasterVue and Configuring Communication

45 Setup and Configuration Tasks Set up the TraceMasterVue hardware, including modems and printers (Chapter 3, Installing TraceMasterVue Components ) Configure users and associate with TraceMaster groups Configure additional security roles for users, if needed Configure locations (ensure they are the same on connected devices and TraceMasterVue) Configure device connections (Chapter 4, Configuring the Network for TraceMasterVue Data Communication ) Configure RAS (Chapter F, Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue ) Configure import directories Configure printers and fax (Chapter 5, Adding and Configuring Printers and Fax Capability ) Configure inboxes Configure ordering (referring) physicians Configure user fields (on the cardiograph) Configure printed report settings Define automated workflow rules Schedule backups (for details, refer to the TraceMasterVue System Configuration and Reference Guide) Verify the system works Installing TraceMasterVue and Configuring Communication 2-3

46 TraceMasterVue Communication Worksheets Communication Configuration Checklist Configuring communication between TraceMasterVue and devices comprises the following steps. We recommend you perform them in the order listed. Use this checklist to keep track of where you are in the process. Plan how the systems will be interconnected (page 1-20) NOTE Verify the operating system on each device to be connected, and ensure you have the correct and appropriate hardware/software, including applicable options, and documentation Review all the worksheets and ensure you have all the necessary data before proceeding If the customer has a policy of clearing off all factory-specified configuration information, user IDs and groups, and the like, make sure you review the section, User-Related Requirements for Running TraceMasterVue on page A-3 before proceeding. Certain user IDs, groups, user/group associations, and services must be present and configured for TraceMasterVue to run and function properly. If this is the situation, ensure you have all the user names and passwords you need before proceeding. Check the contents of the following sections to ensure you have this information: Users Required on the TraceMasterVue Server on page A-5 Required Database User IDs on page A-15 Configure the TraceMasterVue end of communication: Connect all hardware to the TraceMasterVue system, including modems and any direct connections (if applicable) Configure the hardware on the TraceMasterVue system, and assign COM ports as appropriate Configure legacy cardiograph (PageWriter XL, 200/300) support on the TraceMasterVue system, as needed, using the System Configuration utility Configure interactive query support on the TraceMasterVue system, if desired, using the System Configuration utility Set up users and groups Define the physician list Configure the IIC to communication with TraceMasterVue, if you have the IIC Connectivity option Set up Orders inboxes and communication, if you have the OrderVue option Configure IIC support (set up the share folder and user), if you have the IIC Connectivity option Reboot the TraceMasterVue system 2-4 Installing TraceMasterVue and Configuring Communication

47 Configure the cardiograph (or other device) end of communication: Connect the hardware (modem, LAN, direct connection) Configure remote sites Configure network settings Configure interactive query (if desired, and supported) Configure location information (location codes, and/or institution, facility, and department information) Configure user-defined fields Configure Orders inboxes and communication, if you have the OrderVue option Test communication between each device and the TraceMasterVue system Installing TraceMasterVue and Configuring Communication 2-5

48 TraceMasterVue Communication Worksheets Transmission and Phone Configuration Worksheet The following information is used to configure data communication. How will ECGs be transmitted to TraceMasterVue? Also fill out the Cardiograph Communication Worksheets. Modem connection from cardiograph Number of cardiographs Number of cardiograph modems Number of TraceMasterVue input modems Direct connection ports (for use with XL-series cardiographs only) Diskettes LAN Is there a dedicated modem for remote support? Yes No # Are there remote client systems on the network? Yes No Is Internet Explorer 5.0 or later installed? Yes No Will TraceMasterVue print to remote printers on the network? Yes No If so, list path, location, model # 2-6 Installing TraceMasterVue and Configuring Communication

49 COM Port Assignment and Phone Number Worksheet TraceMasterVue requires a phone number for each modem on the system. You will need this information both to configure the system and to enable cardiographs to call the system. Fill out the worksheet below. For COM port assignment conventions and octa-cable port associations, see page Modems for TraceMasterVue COM Port to Use Octa- Cable Port Phone Number Remote support phone number (if using RAS) Outgoing FAX number Installing TraceMasterVue and Configuring Communication 2-7

50 TraceMasterVue Communication Worksheets TraceMasterVue Network Configuration The following information is used to configure data communication between TraceMasterVue and cardiographs. TraceMasterVue Server Information TraceMasterVue server IP address TraceMasterVue server hostname TraceMasterVue domain name Subnet mask Default gateway Primary DNS Secondary DNS Primary WINS Secondary WINS RAS First IP address for RAS Second (last) IP address for RAS FAX (Cover sheet information) Fax name Fax company name Fax number Voice number TSID code 2-8 Installing TraceMasterVue and Configuring Communication

51 PageWriterTouch/Trim Cardiograph Connection Configuration The following information is used to configure data communication on the cardiographs. The Remote Site name is a descriptive label to identify each cardiograph connection to TraceMasterVue. Will you be using interactive query? Yes No Cardiograph ID IP Address Static or Reserved DHCP addresses are preferred. Location (where will the cardiograph be located) Planned Method of Connection (LAN, Modem) If Modem, list phone number Remote Site Name/Computer Name Record the user ID and password that the cardiographs will use to gain access to the TraceMasterVue system. This user must be a valid Windows user on the TraceMasterVue system, and must also be a member of a TraceMaster group with read and write permissions. For details about TraceMasterVue users and groups, see Chapter 5, Configuring TraceMasterVue Users and Groups, in the TraceMasterVue System Configuration and Reference Guide. User ID Password Installing TraceMasterVue and Configuring Communication 2-9

52 TraceMasterVue Communication Worksheets PageWriter XL Cardiograph Connection Configuration The following information is used to configure data communication on legacy PageWriter XLseries cardiographs. The Default Location refers to the Location code set in the cardiograph configuration settings. It is used at a later stage of configuration, and is included here for convenience. For details about location codes and conversion, see Location Matching in TraceMasterVue on page B-2. The Remote Site Number refers to the site number (1-4) associated with this connection to TraceMasterVue. Will you be using interactive query? Yes No Will you perform 3:2 or 1:2:2 location code conversion? 3:2 1:2:2 Cardiograph ID Default Location Code Planned Method of Connection (Diskette, Direct Connect, Modem) If Modem, list phone number Remote Site Number Record the user ID and password that the cardiographs will use to gain access to the TraceMasterVue system. This user must be a valid Windows user on the TraceMasterVue system, and must also be a member of a TraceMaster group with read and write permissions. For details about TraceMasterVue users and groups, see Chapter 5, Configuring TraceMasterVue Users and Groups, in the TraceMasterVue System Configuration and Reference Guide. User ID Password 2-10 Installing TraceMasterVue and Configuring Communication

53 Location Worksheet This worksheet lists all the institution/facility/department entries to use at the customer site. The definition on the cardiographs must match the definitions specified in TraceMasterVue. This worksheet also provides space to list existing location codes used on legacy PageWriter XL-series cardiographs. Inst. Code Inst. Name Fac.C ode Facility Name Dept. Code Dept. Name Location Code Map to Inst/Fac/Dept Installing TraceMasterVue and Configuring Communication 2-11

54 TraceMasterVue Communication Worksheets NOTE NOTE User-Defined Fields Worksheet Record the labels to use for user-defined fields on this sheet. Before proceeding, read Configuring User-Defined Field Values in TraceMasterVue on page 7-18 and Appendix D, About User Fields. If you will be exporting ECGs to FDA XML format, User fields and their associated values, if any, appear in the ECGVue/PharmaVue Additional Data section, on the right side of the Summary page. User Field 1 is different from the rest in that it allows you to specify attributes for the field value. If you are using Philips OrderVue, use User Field 2 to contain the Order ID. Users Field Number User Field Label User Field 1 Attributes (if any) 2-12 Installing TraceMasterVue and Configuring Communication

55 User Access Worksheet This worksheets allows you to list authorized users for the TraceMasterVue system, including user name and groups with which to associate the user. In addition, you can specify additional security role parameters to provide greater or more restricted access to system functions. For convenience, the TraceMasterVue Group Permissions Table is provided on the following page. For details about users, groups, and permissions, as well as information about security roles, see Chapter 5, Configuring TraceMasterVue Users and Groups, in the TraceMasterVue System Configuration and Reference Guide. User ID Name Windows Groups TraceMaster Groups Need Security Role? If so, define. Installing TraceMasterVue and Configuring Communication 2-13

56 TraceMasterVue Communication Worksheets TraceMasterVue Group Permissions Table The following table shows the exact permissions granted to each TraceMasterVue Windows group. For details, see Chapter 5, Configuring TraceMasterVue Users and Groups, in the TraceMasterVue System Configuration and Reference Guide. Table 2-1 Summary of TraceMasterVue group access permissions System Admin IT ECG Mgr ECG Head Tech ECG Tech Referring Physician Confirming Cardiologist Reviewer Verifier COBO WebAPI ** Guest None View X X X X X X X X X X Edit demographics X X X X X X X Verify ECG X X X X X X X Edit ECG X X X X X X Delete ECG X X X X Delete patient X X X Confirm X X Unconfirm X X X X /print/fax report X X X X X X X X X Assign X X X X X X X Mgmt reports X X X Serial compare X X X X X Backup X X X Restore X X Import/Export X X X X X X X Enterprise Mgr Export X WebAPI access ** X Server-side utilities X ** Available only with the WebAPI option Installing TraceMasterVue and Configuring Communication

57 Physician List Worksheet Record the entries to add to the system using the Physicians tab on this sheet. This helps you collect all the data before data entry. As an alternative, you can import an existing MD table from a previous TraceMaster NT system to populate this list. For details, see Configuring the Physician List on page The information in these entries allows a workflow rule to be defined that automatically retrieves the address or fax number of the referring physician associated with an ECG and send the ECG to that physician upon a certain action, such as ECG acquisition or confirmation. For details, see Chapter 6 of the TraceMasterVue System Configuration and Reference Guide. Phys. ID Last Name First Name Mid. Init. Fax # Associate with Inst/Fac/Dept Installing TraceMasterVue and Configuring Communication 2-15

58 TraceMasterVue Communication Worksheets Inboxes Worksheet Inboxes are containers to which ECGs are assigned. Assigning an ECG to an inbox allows a configured set of users to have quick access to these ECGs; it also allows automated workflow rules to perform defined actions on ECGs based on the inbox to which they are assigned. You associate inboxes with an ECG state, and, optionally, with a location and specified users or groups. Note the following: If specifying a location, only users with access to the associated locations will be able to see the ECGs assigned to that inbox. If specifying a user or group, only those specific users will be able to see ECGs assigned to that inbox. Members of the TraceMaster_ECGMgr and TraceMaster_SysAdmin groups can retrieve all ECGs. For details, see Chapter 6 of the TraceMasterVue System Configuration and Reference Guide. Inbox Name State Institution (opt) Facility (opt) Dept (opt) Associate with Specified User or Group 2-16 Installing TraceMasterVue and Configuring Communication

59 Automated Workflow Rules Worksheet You can configure automated rules that perform certain actions on ECGs that match a specific signature profile. For detailed information about configuring workflow rules, see Defining Automated Workflow Rules on page Remember that certain actions may not be available in all editions of TraceMasterVue. Fill out the table as follows: In the Purpose row, write a brief description of the rule. In the second row, write the specifics for each field that is in the Add Rule dialog box. In the Addt l Info row, write the appropriate printer, address, export format/location, and so on as appropriate for the selections you made in the Rules Performed section. Purpose of Rule (describe)/ ECG Signature: Location (I, F, D) ECG Signature: Source and Type ECG Signature: State, Priority, Severity ECG Signature: Patient Name ECG Signature: User Field 1 Action to Perform (Assign, Confirm, Store, Unconfirm, Compare, Delete) Rules Performed:Se rial Compare, New State, or Inbox Assignment Rules Performed: , Export, Fax, or Print Purpose: Addt l Info: Purpose: Addt l Info: Purpose: Addt l Info: Purpose: Addt l Info: Purpose: Addt l Info: Purpose: Addt l Info: Installing TraceMasterVue and Configuring Communication 2-17

60 TraceMasterVue Communication Worksheets Order Inboxes Worksheet Use with the OrderVue option only, when defining orders inboxes on PageWriter Touch and Trim cardiographs. For details on how to configure order inboxes on the cardiographs, see Setting Up Order Inboxes on the Cardiographs on page J-6. You can map multiple OrderVue outboxes to a single Inbox on the cardiograph. For each inbox, specify the status and priority of orders, as well as the originating time period for orders (Elapsed Time), to download. OrderVue Outbox (on Remote Site) Map to this Inbox on Cardiograph Status of Orders to Download (New or ALL) Priority of Orders to Download (Stat or All) Get Orders on? Find Orders on? Update Mode: Delete and Replace (DR) or Append (A) 2-18 Installing TraceMasterVue and Configuring Communication

61 3 Chapter 3Installing TraceMasterVue Components After the TraceMasterVue system is shipped, you must configure it for use at the customer site. This chapter provides the following information: Before You Begin Verifying System Components Available Options Supplies Used Regularly Installing the Hardware Connecting the Server Connecting the Network Hub Connecting the LCD Display Connecting the Uninterruptable Power Source Connecting the Mouse and Keyboard Connecting the MetroLogic Bar Code Scanner Recommended Scanning Technique Resetting the Bar Code Scanner Installing Modems Connecting a Printer Turning the TraceMasterVue System On Before You Begin Before proceeding, ensure you have available: Instructions provided in this guide TraceMasterVue System Configuration and Reference Guide CAUTION Before handling components, remember to protect them from static electricity by using an anti-static wrist strap and a grounding mat, which are included in the Electrically Conductive Field Service Grounding Kit. If you do not have anti-static devices, touch the metal surface on the back panel of the computer to discharge static electricity. 3-1

62 Installing TraceMasterVue Components Verifying System Components Locate all of the boxes to make sure you have everything. Instead of taking everything out of the boxes right away, it is a good idea to leave the hardware, CD-ROMs, and their instructions in the boxes until you are ready to install each particular piece. Keep all of the instructions; you will refer to them during installation. Depending on the system you ordered, the TraceMasterVue boxes contain the following items: Compaq ProLiant server Tower-to-rack mount kit RAID disk array and RAID controller, with 2 x 36 GB disk drives for the operating system and application files, and 3 x 36 (Standard Edition) or 3 x 146 GB (Enterprise Edition) or 3 x 300 GB (Universal Edition) disk drives for the ECG database LaserJet 4250N printer Barcode scanner LCD display Power cords (for PC, monitor, server, printer, UPS, and modems) Keyboard and mouse HP ProCurve Router Two Jet Direct network cables APC Smart Uninterruptable Power Source (UPS) Two US Robotics Courier V. Everything External 56K Modems (U.S. only) Two modem cables DAT tape drive (Ultrium drive for Enterprise Edition) (1) DAT tape containing system backup (3) Blank tapes Cleaning tape (used to clean tape drive) CDs: M5100A TraceMasterVue ECG Management System Documentation & Training CD One or more system Ghost image CD(s) Blank CDs Windows Server 2003 CD 3-2 Installing TraceMasterVue and Configuring Communication

63 Verifying System Components Available Options Depending on the system you purchased (Standard vs. Enterprise vs. Universal edition), the following options may be available and can be purchased separately: HL7 Export XML Export PDF Export TIFF Export PharmaVue clinical research application CalECG measurement and annotation application (available only with PharmaVue) in 1, 2-5, or up-to-10 user licenses Philips Clinical Interface connectivity OrderVue order handling system options Orders interface with results reporting Orders interface with billing output Orders interface with results reporting and billing output Additional billing output Contact your Philips Medical Systems representative for information about these and other available options. Supplies Used Regularly The following list includes items that are used regularly with your TraceMaster system. They include: Pre-printed red grid paper, 5000 sheets to a box (part number M1737A for letter size, M1738A for A4 size) Backup tapes 3.5 diskettes Tape drive cleaning tape A package containing these items is included with your system. For more information on ordering additional supplies, call your Philips Medical Systems service representative. Installing TraceMasterVue and Configuring Communication 3-3

64 Installing TraceMasterVue Components Installing the Hardware The TraceMaster system requires that you set up and install the following hardware components: Server (below) Network hub (page 3-5) LCD display (page 3-6) Uninterruptable Power Source (UPS) (page 3-6) Mouse and keyboard (page 3-7) Bar code scanner (page 3-7) External modems (page 3-10) Printer (optional) (page 3-10) The following sections describe how to install all of the hardware components. CAUTION Before handling components, remember to protect them from static electricity by using an anti-static wrist strap and a grounding mat, which are included in the Electrically Conductive Field Service Grounding Kit. If you do not have anti-static devices, touch the metal surface on the back panel of the computer to discharge static electricity. NOTE Connecting the Server The TraceMaster server is configured to work on its own network, as a standalone system. If this is the plan of the institution where you are performing the installation, you will not need to reconfigure the networking parameters. However, if you plan to make the server available on the local network, you must reconfigure the network parameters. If you are planning to make the server available on the network, you must leave port 1 open on the Network hub. Refer to Chapter 4, Configuring the Network for TraceMasterVue Data Communication for information on how to configure data communication. To connect the server 1 Place the server in a convenient space in your work area. Be sure you have access to the back of the system. 2 Locate the network cable and plug one end of the cable into the back of the network connector located on the Network Interface Connector (NIC) card. 3-4 Installing TraceMasterVue and Configuring Communication

65 Installing the Hardware Network connector 3 Connect one end of the power cord to the back of the server. Connecting the Network Hub To connect the network hub 1 Mount the hub or place the hub on top of the server. For information on how to permanently mount the device, see the documentation that came with the hub. The hub is a 10Base-T model with twisted-pair (TX) ports and RJ-45 jacks that provide network access to the TraceMasterVue system. By connecting network cables from the hub to an Ethernet device such as the server, your network will be operational. 2 Perform a self-test on the hub by plugging one end of a power cord into a wall socket or a power strip and the other end into the AC power connector on the back of the hub. The LEDs on the front panel of the hub turn on, then off after a few seconds. If this does not happen, refer to the documentation that came with the hub for more information. If the test was successful, proceed. 3 Remove the end of the power cord that is connected to the wall socket or power strip. You will eventually connect this to the Uninterruptable power source (UPS). 4 Connect the free end of the network connector to the back of the network hub (into any port except port 1). Port 1 is reserved for connecting to the local network.. Keep port 1 open Installing TraceMasterVue and Configuring Communication 3-5

66 Installing TraceMasterVue Components For further instructions on connecting the hub, such as how to connect to the printer, refer to the documentation that came with the hub. Connecting the LCD Display For complete instructions on installing the LCD display (monitor), refer to the installation guide that came with the monitor. To connect the monitor 1 Place the monitor on the workspace. 2 Plug one end of the 15-pin video cable into the back of the monitor and the other end into the video connector on the back of the server; then tighten the thumbscrews. Video connector 3 Plug one end of the monitor power cable into the back of the monitor. Do not plug in the other end of the monitor power cable at this time. Connecting the Uninterruptable Power Source The Uninterruptable Power Source (UPS) is used as an electrical buffering zone when there is a power failure. It provides about 20 minutes of operating power for database and network services. Having the UPS installed allows time for the system to shutdown gracefully and ensures that files are saved and backed up. For more detailed information on the UPS and how it works, see the documentation that came with the device. CAUTION Do not connect the printer to the UPS. The printer start up current is more than the UPS can handle. Connect the printer directly to a wall outlet. 3-6 Installing TraceMasterVue and Configuring Communication

67 Installing the Hardware NOTE You must connect the display to the back of the UPS. Be aware that it decreases the amount of time you have before the system goes down, should there be a problem. Check the documentation that came with the UPS for more details. To connect the UPS 1 Position the UPS with the back panel facing the back of the server. 2 Plug the power cable on the back of the UPS into a wall outlet. 3 Plug the following power cables into the UPS: Network hub Monitor Server 4 To turn on the UPS, press the ON switch located on the front panel. Connecting the Mouse and Keyboard To connect the mouse and keyboard 1 Plug the mouse connector into the mouse port in the back of the server. Mouse connector Keyboard connector 2 If you do not have a barcode scanner, plug the keyboard connector directly into the keyboard port on the back of the computer. If you are using a barcode scanner, set up the components as described in the next section. Connecting the MetroLogic Bar Code Scanner Installing TraceMasterVue and Configuring Communication 3-7

68 Installing TraceMasterVue Components CAUTION Prior to connecting the bar code scanner, ensure the system is powered off. To connect the bar code scanner 1 Plug the 10-pin RJ45 connector into the connector on the bar code scanner. You will hear a click when the connection is made. 2 If already connected, disconnect the keyboard cable from the computer. 3 Plug the keyboard cable into the 6-pin mini-din connector of the adapter cable. 4 Plug the 5-pin end of the adapter cable into the power link (Y-shaped) cable. 5 Plug the 6-pin end of the power link cable into the keyboard connector on the back of the computer. 10-pin RJ45 connector 5-pin connector Adapter cable 6-pin connector Power link (Y-shaped) cable The scanner is configured to work out of the box, without further configuration. For additional scanner details, see the Metrologic Scanner Installation and User Guide. If you need to reset the scanner, see Resetting the Bar Code Scanner on page Installing TraceMasterVue and Configuring Communication

69 Installing the Hardware Recommended Scanning Technique For optimal results when scanning bar codes, use the following technique. To scan a bar code 1 Hold the scanner no more than 4 inches away from the paper. 2 Make sure the angle from the output window of the scanner to the paper is at least 45 degrees, as shown in the following illustration. 45 o Resetting the Bar Code Scanner The scanner is configured for use out of the box. However, if you need to reset the scanner, reconfigure it by scanning the bar codes on the following pages. After scanning each bar code, wait for the designated amount of beeps before scanning the next code. If you do not hear the designated amount of beeps, re-scan the code. To reset the bar code scanner to factory defaults 1 Scan the following code, Enter/Exit Configuration Mode, first. 3 beeps 2 Scan the following code, Recall Defaults, next. 1 beep 3 Finally, scan the Enter/Exit Configuration Mode code in step 1 again. 3 beeps Installing TraceMasterVue and Configuring Communication 3-9

70 Installing TraceMasterVue Components The bar code scanner is now reset to the system defaults. NOTE Installing Modems The TraceMasterVue server supports modems for the following three functions: Remote support (using RAS) Fax Data transfer (including queries) via modems TraceMasterVue is certified for use with the US Robotics Courier V. Everything modem. You must use an analog phone line for each modem. Detailed information about setting up modems is provided in Installing Hardware and Configuring COM Ports On TraceMasterVue in the Installing TraceMasterVue and Configuring Communication. Connecting a Printer NOTE CAUTION If you set up TraceMasterVue without configuring a printer, and a user attempts to print, the Fax Wizard appears. Ensure that at least one printer is configured for the TraceMasterVue system. This section describes how to add the included HP 4250N printer to your system. The process is similar for other printers. Do not connect the printer to the UPS. The printer startup current is more than the UPS can handle. NOTE To connect the printer 1 Place the printer on the system table or on your workspace. 2 Plug one end of the network printer cable into the RJ-45 connector on the back of the printer. 3 Plug the other end of the network printer cable into Port 8 on the front of the hub. You may have the option of using another port on the hub; however, if you are planning to install the server on the local network, you must keep port 1 available. Keep port 1 open 4 Plug one end of the power cord into the back of the printer and the other end into a wall outlet Installing TraceMasterVue and Configuring Communication

71 Turning the TraceMasterVue System On The printer is now connected. To configure the printer See Chapter 5, Adding and Configuring Printers and Fax Capability. Turning the TraceMasterVue System On After all the hardware is installed and connected, you can power on the system and continue with the configuration tasks. Before powering on the system, ensure the following conditions are met: Make sure that you have completed installing all of the hardware and any necessary software. Check to be sure that all of the cables are connected to the hardware and the hardware is connected to the AC power outlets, surge protector, or UPS. Power off the server if it is turned on. To turn the TraceMasterVue system on Power on the system by turning on the UPS, modems, server, then the monitor, and printer. Proceed to the next chapter to continue configuration. Installing TraceMasterVue and Configuring Communication 3-11

72 Installing TraceMasterVue Components 3-12 Installing TraceMasterVue and Configuring Communication

73 Chapter 4Configuring the Network for TraceMasterVue Data Communication 4 This document describes how to configure communication between cardiographs (and other devices) and TraceMasterVue. The first step is setting up and configuring TraceMasterVue. This includes connecting hardware and configuring communication, and defining locations. These are the areas that require synchronization between the system and cardiographs. Installing Hardware and Configuring COM Ports On TraceMasterVue NOTE If you will use the remote access service (RAS) for remote support, or if you will be using modems to transfer data between PageWriterTouch or Trim cardiographs and the TraceMasterVue system, you must first configure RAS. For configuration details, see Appendix D, Remote Access Service (RAS) Configuration for PageWriter Cardiographs and TraceMasterVue in the TraceMasterVue System Configuration and Reference Guide. We recommended that a Philips representative configure the service. We recommend that you perform the installation and configuration steps in the order shown in this guide: Setting up the octa-cable (page 4-2) Setting up direct connections (used only for connecting legacy PageWriter XL-series and 200/300 cardiographs) (page 4-2) Setting up modems (page 4-6) Assigning COM ports (page 4-7) Freeing COM ports from RAS and Fax ownership, as appropriate (page 4-11) If applicable, configuring ports for legacy cardiograph use (page 4-18) Configuring TraceMasterVue network settings (page 4-19) If applicable, configuring and enabling SSL (page 4-20) Setting up remote access (page 4-36) Setting up import processes and services (Chapter 6, Setting Up Processes and Users ) Configuring users and groups (Chapter 6) 4-1

74 Configuring the Network for TraceMasterVue Data Communication Configuring locations (Chapter 7, Setting Up and Configuring TraceMasterVue System Options ) Defining user fields, if used (Chapter 7) Configuring the Physician list (Chapter 7) Configuring inboxes (Chapter 7) Defining automated workflow rules (Chapter 7) Completing TraceMasterVue configuration and rebooting the system (Chapter 7) Installing the client application on one or more computers (Chapter 7) Installing the Report Manager application on one or more client computers (Chapter 7) Setting Up the Octa-Cable The octa-cable is used to connect datacomm modems to the server. When you are using the octa-cable, you need to know how each 25-pin end of the cable maps to the various COM ports. The following tables provide useful information that you may want to keep handy, just in case the octa-cable you are using is not labeled. The following table lists the mappings for use with TraceMasterVue. COM Port Octa Cable Card 1 n/a Built-in COM port on computer 2 n/a Built-in COM port on computer 3 P0 8-port Rocketport card (provided with 4 P1 system) 5 P2 6 P3 7 P4 8 P5 9 P6 10 P7 NOTE In some cases, the cables are marked P1 through P8. Setting Up a Direct Connection When connecting a legacy PageWriter XL-series and 200/300 cardiograph using a direct connection, one cable connects to the back of the cardiograph and optionally, to a junction box (page 4-4). Another cable connects the junction box to the appropriate connector on an octacable, which is connected to the TraceMasterVue server. You can also thread the direct connect cables through a wall plate (page 4-5). 4-2 Configuring Cardiograph and TraceMasterVue Communication Guide

75 To set up direct cable connections Refer to the figure on the following page for an illustration of the connections. 1 Attach the appropriate port from the octa-cable to a 25-pin gender changer for each direct connection to a cardiograph. Refer to the COM Port Assignment and Phone Number Worksheet on page 2-7 to ensure each cardiograph is connected to the correct port. By convention, direct connections are made using the P0 and P1 ports of the octa-cable (corresponding to COM 3 and 4, respectively). 2 Connect an RS-232 surge protector to the gender changer. 3 Connect the surge protector to the direct connect cable attached to the junction box or wall plate. For details about setting up the junction box, see Mounting the Junction Box on page 4-4. For details about setting up the wall plate, see Installing the Wall Plate Cable Option on page Attach the second direct connect cable to the junction box. This cable will be connected to the cardiograph, but you do not need to connect it at this point. Details on connecting and configuring the cardiograph are provided in the cardiograph-related chapters of this guide (chapters 8 through 10). Junction box To cardiograph Surge protector Gender changer Ports from octa-cable connected to TraceMasterVue server 5 Repeat these steps for each direct connection to be made to the TraceMasterVue system. You are now ready to assign COM ports on the server. See Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7. Configuring Cardiograph and TraceMasterVue Communication Guide 4-3

76 Configuring the Network for TraceMasterVue Data Communication Mounting the Junction Box To mount the junction box on the wall 1 Disassemble the wall plate, junction box, and base by removing the four screws. 2 Mount the junction box base plate using two wall anchors (or another mounting device of your choice.) CAUTION Do not use double-sided tape to mount the junction box to the wall. Unplugging the cable from the junction box connector can dislodge the tape. 3 Align the junction box base so that it is vertical, then apply even pressure to attach it to the wall. Junction box base 4 Holding the junction box base and junction box cover in position, slide the direct connect cable up to the junction box cover, as shown in the following figure. Flathead screws Junction box cover Direct connect cables (connectors not shown) Junction box base 4-4 Configuring Cardiograph and TraceMasterVue Communication Guide

77 5 Fit the connectors into the slots on the cover. Junction box cover plate 6 Mount the junction box cover to the base, and the cover plate to the cover. The junction box is now ready for use, but you do not need to connect the cables to the cardiograph at this point. The next step is to configure COM ports, as described in Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7. Installing the Wall Plate Cable Option The wall plate-to-wall plate cable option provides approximately 100, 200, or 300 feet of cable length that can be used to provide direct connections from a TraceMasterVue system to a cardiograph (or more than one cardiograph) located in a different area of the hospital. Before installing the direct connect cables, take a moment to read through the following list of precautions that will help prevent damage to the pre-assembled wall plate and the connector sockets: Leave the cable ties in the wall plate holes to prevent excessive strain on the cable. Do not cut the cable ties until the other end of the cable has been pulled through the wall plate. Do not apply force to the end of the cable that contains fragile connector sockets. Grip the cable or attach a snake beyond the section that has been heat shrunk. This way, you will be applying force to the cable and not to the fragile connector sockets underneath the heat treated section. Before pulling the cable, wrap the end to prevent snagging. Before beginning, ensure that the wall openings are ready for you to begin work. Pre-Assembled End of Cable Wrapped End of Cable Signal Wire Color Pin Pin Wire Color Signal GND White 1 1 Black GND RXD Red 3 2 Red TXD TXD Orange 2 3 Orange RXD RTS Violet 4 4 Violet RTS DCD Violet 8 8 Violet DCD Configuring Cardiograph and TraceMasterVue Communication Guide 4-5

78 Configuring the Network for TraceMasterVue Data Communication Pre-Assembled End of Cable Wrapped End of Cable Signal Wire Color Pin Pin Wire Color Signal GND Yellow 7 7 Yellow GND 5 Green CTS RI Green White DTR CTS Blue 5 DTR White Blue RI To install the wall plate-to-wall plate cable option 1 Locate and open the boxes containing the cables and wall plates, and set them aside. 2 Take the direct connect cable and pull it through the wall. 3 Insert the sockets into the connectors by using the red end of an insertion/extraction tool. 4 Insert seven sockets into each connector by snapping the sockets into place. 5 Verify that each socket is completely seated by gently pulling on the wires. 6 Assemble the ground lug: a b c Remove the 4-40 screw next to pin 1 of the connector. Insert the screw through the solder lug. Reinstall the screw through the wall plate and the connector. The cable is now available for connection to the cardiograph. You do not need to connect them yet. Details on connecting and configuring the cardiograph are provided in the cardiographrelated chapters in this guide (chapters 8 through 10). You are now ready to assign the connection to a COM port, as described in Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System on page 4-7. Installing Data Transfer Modems To hook up a data transfer modem 1 Connect one end of the modem cable to the back of the modem as directed by the instructions provided with the modem, and connect the other end of the cable to the appropriate port of the octa-cable (listed on the COM Port Assignment Worksheet). You do not need to connect the modem to the cardiograph at this time. That step is described in the cardiograph-related chapters in this guide (chapters 8 through 10). Depending on the modem manufacturer, the operating system may automatically recognize the new hardware. If so, skip to step 5 on page Assign the modem to a COM port, as described next. 4-6 Configuring Cardiograph and TraceMasterVue Communication Guide

79 Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System NOTE If you are using the Remote Access Service (RAS) for remote support or for modem communication between a PageWriterTouch/Trim cardiograph and TraceMasterVue, RAS must already be configured on your system before proceeding. For details, see Appendix D, Configuring the Remote Access Service (RAS), in the TraceMasterVue System Configuration and Reference Guide. You can add as many connections as you have COM ports. Assigning COM ports comprises the following steps: 1 First, configure the modem(s) using the Phone and Modem options functionality of the operating system. See Configuring COM Ports, next. 2 Configure each modem for the function it will perform. NOTE When you add a plug-and-play modem to the system, both the system Fax utility and the RAS server take ownership of the modem. When you add a direct connection to the system, the RAS server takes ownership of the connection. You must manually free every new modem and connection from undesired assignments. See Freeing COM Ports from the Fax Utility and RAS on page For modems that will support communication with legacy PageWriter XL-series cardiographs, you must also configure settings using the TraceMasterVue System Configuration utility, on the IO tab. See Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue on page Configuring COM Ports NOTES COM1 and COM2 ports are by convention reserved for RAS and fax modems, respectively, and should not be used for data transfer operations. When you add a plug-and-play modem to the system, both the system Fax utility and the RAS server take ownership of the modem. You must manually free every new modem and direct connection from undesired assignments. For details, see Freeing COM Ports from the Fax Utility and RAS on page Because legacy PageWriter XL-series cardiographs use a different communication protocol from PageWriterTouch/Trim cardiographs, you must configure individual COM ports for communication with each type of cardiograph. That is, you cannot share a single modem for data transfer from both PageWriterTouch/Trim cardiographs and legacy PageWriter cardiographs. For additional information about RAS, see Appendix D, Configuring the Remote Access Service (RAS), in the TraceMasterVue System Configuration and Reference Guide. Configuring Cardiograph and TraceMasterVue Communication Guide 4-7

80 Configuring the Network for TraceMasterVue Data Communication NOTE To configure a modem Have available the completed COM Port Assignment and Phone Number Worksheet on page Connect the modem to the server as described in Installing Data Transfer Modems on the previous page. 2 On the TraceMasterVue server, click Start > Control Panel > Phone and Modem Options. The operating system may detect the presence of the new hardware upon booting, and automatically display the Found New Hardware Wizard. If so, skip to step 5. The Phone and Modem Options dialog box appears. 3 Click the Modems tab; then click Add. The Install New Modem screen of the Add Hardware Wizard appears. Ensure this check box remains unselected. 4 Ensure that the Don t detect my modem check box is clear (not selected); then click Next. 4-8 Configuring Cardiograph and TraceMasterVue Communication Guide

81 5 On the Welcome screen, click Next. The Select Modem screen appears. 6 Select the desired entry: For RAS, fax, or data transfer modems, select the appropriate modem from the list. Unless your exact modem is listed, select Standard Modem. For direct connection, select Communications cable between two computers. Select this option when connecting a legacy PageWriter cardiograph to the TraceMasterVue system using a direct serial connection. 7 Click Next. 8 On the final screen, click Finish to return to the Add Hardware Wizard. The system now detects your modem and displays the Install New Modem screen. Configuring Cardiograph and TraceMasterVue Communication Guide 4-9

82 Configuring the Network for TraceMasterVue Data Communication 9 Select the COM port to assign to this modem: COM1 is typically used for the remote support modem using RAS. COM2 is typically used for a fax modem. COM3-10 are used for additional fax modems, RAS for PageWriterTouch cardiographs, or direct connection or data transfer modems for legacy PageWriter cardiographs. Refer to the completed COM Port Assignment and Phone Number Worksheet on page 2-7 for the proper port assignment. 10 Click Next. The Wizard returns you to the Phone and Modem Options main dialog box, displaying the modem selection and COM port assignment you just specified. 11 Repeat these steps to configure additional modems and direct connections. You are now ready to ensure that the modems are properly configured for their intended function. See Freeing COM Ports from the Fax Utility and RAS, next Configuring Cardiograph and TraceMasterVue Communication Guide

83 Freeing COM Ports from the Fax Utility and RAS NOTE After adding all modems and direct connections to the system as described in the previous section, you must ensure that each connection and modem is assigned to the proper port and function. Because the system Fax utility and the RAS server take ownership of a newly added modem or connection, you must perform the following steps to ensure proper assignment: Verify correct port configuration for the modems you added using the Phone and Modem options dialog box. Configure port assignment in the Fax console. Perform this step for all modems so that only the modem(s) you want to use for fax is assigned to the Fax utility. You do not need to perform this step for direct connections that you have added. The Fax utility does not acquire these entries. Configure port assignment in the RAS console. Perform this step for all modems and direct connections so that only the modems you want to use for RAS are assigned to RAS. The following sections provide detailed information about each of these situations. In the example provided in the following sections, we have added a modem for communication between TraceMasterVue and a legacy PageWriter XL cardiograph. Both the Fax utility and the RAS server have taken ownership of the new modem. However, because it is for legacy communication, we need to remove the modem both from the Fax and RAS ownership. Configuring Cardiograph and TraceMasterVue Communication Guide 4-11

84 Configuring the Network for TraceMasterVue Data Communication Verifying Correct Port Configuration for Modems Perform this step for all modems to ensure proper port assignment. To verify correct port configuration 1 Click Start > Control Panel > Phone and Modem Options. The Phone and Modem Options dialog box appears. Verify that each modem is assigned to the appropriate serial communications port: COM1 is typically used for the remote support modem using RAS. COM2 is typically used for a fax modem. COM3-10 are used for additional fax modems, RAS for PageWriterTouch cardiographs, or direct connection or data transfer modems for legacy PageWriter cardiographs. 2 Keep this dialog box open while you continue to the next steps. NOTE The Fax utility and RAS windows show the modems and devices that are part of the system by name, not by port association. To ensure that you are selecting the appropriate entry, have available the Phone and Modem Options dialog box in a corner of your monitor; this dialog box shows the device names together with their assigned COM port. You can then easily look up the desired port number (for example, COM2), and get the name of the device associated with that port Configuring Cardiograph and TraceMasterVue Communication Guide

85 Freeing Modems from the Fax Utility Perform this step for all modems so that only the modem(s) you want to use for fax is assigned to the Fax utility. To verify and change Fax console settings 1 Select Start > Printers/Faxes. The Printers and Faxes window appears. 2 Double-click the entry for the fax modem or printer (in the example, TraceMasterVue FAX). The Fax Console appears. Tools menu 3 Select Tools > Configure Fax. The Fax Wizard appears. 4 Click Next. 5 On the Fax Cover Page screen, click Next. You are not configuring the fax modem in this procedure. You are freeing newly added modems from the Fax utility. To configure the fax modem, see Adding and Configuring Printers and Fax Capability, in the TraceMasterVue System Configuration and Reference Guide. Configuring Cardiograph and TraceMasterVue Communication Guide 4-13

86 Configuring the Network for TraceMasterVue Data Communication 6 On the Select Device for Sending screen, ensure that only the modem that TraceMasterVue will use for fax is selected. Clear the check boxes for modems that will not be used for fax; then click Next. TIP This screen shows the modems and devices that are part of the system by name, not by port association. To ensure that you are clearing the appropriate entries, have available the Phone and Modem Options dialog box in a corner of your monitor; this dialog box shows the device names together with their assigned COM port. You can easily look up the desired port number (for example, COM2), and get the name of the device associated with that port. To display the Phone and Modem Options dialog box, click Start > Control Panel > Phone and Modem Options. In the following example, you would clear the check box next to the Standard Bps Modem entry; this is a modem that will be used for data transfer, not for fax. Fax modem assigned to COM2 Clear this check box, as this modem will not be used for fax; it is the modem used for legacy cardiograph communication. The selection above it is clear, as well, as it is the RAS modem, assigned to COM 1. Only the modem assigned to COM 2, for fax, should be selected. 7 On the Receiving Device screen, click Next. You do not need to select anything on this screen. 8 On the TSID screen, click Next. You are not configuring the fax modem in this procedure. For details on configuring fax, see Chapter 4, Adding and Configuring Printers and Fax Capability, in the TraceMasterVue System Configuration and Reference Guide. 9 Click Next until you reach the final screen; then click Finish. The modems that are not used for fax have been freed from the Fax utility. Continue to the next step to free modems and direct connections from the remote access service, as necessary Configuring Cardiograph and TraceMasterVue Communication Guide

87 Freeing Ports from the Remote Access Service NOTE The Remote Access Service (RAS) must already be configured on your system before proceeding. For details, see Appendix D, Configuring the Remote Access Service (RAS), in the TraceMasterVue System Configuration and Reference Guide. When RAS is initially configured on a system, or whenever you add a modem or direct connection to a legacy cardiograph to your system, RAS takes ownership of the port and modem. A serial communication port cannot be configured for both RAS and legacy cardiograph or fax support. If this is the case, you must reassign the ports appropriately. You must perform this step for all modems and direct connections you add to the system. In our example, you will free the modem used for legacy cardiograph communication (Standard bps modem) from RAS ownership. To free communication ports from RAS ownership 1 On the TraceMasterVue server, click Start > All Programs > Administrative Tools > Routing and Remote Access. The Routing and Remote Access window appears. 2 In the left pane, right-click the Ports entry and select Properties from the menu. The Properties dialog box appears. Configuring Cardiograph and TraceMasterVue Communication Guide 4-15

88 Configuring the Network for TraceMasterVue Data Communication Note that the Standard bps modem, which is intended for use as a data modem for legacy XL-series cardiographs, is currently under RAS ownership, and needs to be freed. In this example, RAS has taken ownership of the Standard modem (assigned to COM5) and the Courier V Everything modem (assigned to COM1). Because COM1 is typically used for remote support communication, that assignment is correct. TIP This screen shows the modems and devices that are part of the system by name, not by port association. To ensure that you are clearing the appropriate entries, have available the Phone and Modem Options dialog box in a corner of your monitor; this dialog box shows the device names together with their assigned COM port. You can easily look up the desired port number (for example, COM2), and get the name of the device associated with that port. To display the Phone and Modem Options dialog box, click Start > Control Panel > Phone and Modem Options. This modem is assigned to COM 1 and is used for remote support. It belongs under RAS control. You will remove this modem from RAS control, as it is a data modem for use with legacy PageWriter cardiographs Configuring Cardiograph and TraceMasterVue Communication Guide

89 3 Select the device to free in the list, in our example, Standard modem, and click Configure. The Configure Device dialog box appears, with the Remote access... check box selected. Clear this check box 4 Clear any selected check boxes to free the port associated with the selected entry; then click OK. Note that the port you selected is no longer managed by RAS. The data transfer modem (associated with COM 5) is no longer associated with RAS. 5 Repeat steps 3 and 4 for all data transfer modems and direct connections for legacy cardiographs, as well as Fax modems. The only modems to remain under RAS ownership should be the remote support modem (COM 1) and data transfer modems for PageWriterTouch/Trim cardiographs, if used. Configuring Cardiograph and TraceMasterVue Communication Guide 4-17

90 Configuring the Network for TraceMasterVue Data Communication 6 Click Apply, then OK to close the dialog box. The modems and direct connections are now properly configured. Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue For TraceMasterVue to be able to communicate with legacy PageWriter XL-series and 200/ 300 cardiographs, you must enable this type of communication within the TraceMasterVue System Configuration utility. NOTE Legacy PageWriter XL-series cardiographs use a different communication protocol (HPDT) from PageWriterTouch/Trim cardiographs (XML). You must configure individual COM ports for communication with each type of cardiograph. That is, you cannot share a single modem for data transfer from both PageWriterTouch/Trim cardiographs and legacy PageWriter cardiographs. To configure communication with legacy cardiographs within TraceMasterVue 1 Run the TraceMasterVue System Configuration utility by double-clicking the icon on the desktop. The System Configuration window appears, displaying the contents of the Global tab. 2 Click the IO tab. The COM ports that are configured on the TraceMasterVue server are listed in the Serial Ports list. 3 From the list, select the port to configure for communication with legacy cardiographs, and click Configure. The Configure Serial Port dialog box appears. 4 Click the Support Legacy Cardiographs check box, then click OK. 5 When you are done setting configuration options, click Finish. This process marks the selected COM port as using the HPDT communication protocol only. 6 You must stop and restart TraceMasterVue services to enable the change. If you are continuing to configure the system, wait to restart services or reboot the server until you have made all configuration changes Configuring Cardiograph and TraceMasterVue Communication Guide

91 Configuring Network Settings The following sections describe how to set up all the hardware and configure the TraceMasterVue system. Assigning IP Address To enable communication with the TraceMasterVue server, you must assign an IP address for the network interface card (NIC). In addition, if you will have one or more PageWriterTouch or PageWriter Trim cardiographs communicating with TraceMasterVue over a modem, you must configure TraceMasterVue as a remote access service (RAS) server, and assign a separate IP address to the RAS server. For more information about RAS, see Configuring Remote Access Service (RAS) for PageWriter cardiographs and TraceMasterVue, in the TraceMasterVue System Configuration and Reference Guide. Depending on your site s needs, you can assign a static or dynamic IP address. For help on specifying IP and DNS settings, refer to the Windows Server 2003 online help accessible through the Start menu. To assign an IP address 1 Click Start > Control Panel > Network Connections > Local Area Connection. The Local Area Connection Properties dialog box appears. 2 In the Connection uses the following options list, ensure that the Internet Protocol (TCP/IP) entry check box is selected and click the entry to select it; then click Properties. The TCP/IP Properties dialog box appears. Decide whether you will assign a static IP address or have it allocated dynamically by the DHCP server. Continue with the appropriate procedure below. To assign a static IP address 1 On the General tab, select the Use the following IP address radio button. 2 Specify the IP address, subnet mask, default gateway, preferred DNS server, and optional alternate DNS server; then click OK. To obtain an IP address dynamically 1 On the General tab, select the Obtain IP address automatically radio button. 2 Click either the static or dynamic DNS server radio button. 3 If you select the Specify DNS server entry, type the preferred DNS server IP address, and optionally, an alternate address. 4 Click Advanced. The Advanced TCP/IP Settings dialog box appears. 5 On the IP Settings tab, ensure DHCP Enabled is displayed in the IP addresses list. If it is not, contact Philips support. Configuring Cardiograph and TraceMasterVue Communication Guide 4-19

92 Configuring the Network for TraceMasterVue Data Communication 6 Click the DNS tab, select the Append these DNS suffixes radio button; then click Add. The TCP/IP Domain Suffix dialog box appears. 7 Type the suffix, and click OK. 8 Click OK to finish setup. Setting Up a Domain You can either add TraceMasterVue to an existing domain or create a new domain specifically for TraceMasterVue (make it the domain controller if you choose this option). For details, refer to the Windows Server 2003 online help accessible through the Start menu. Changing the Server Name The TraceMasterVue computer can be renamed to any name as long as the new computer name does not conflict with existing computers on the network. To change TraceMasterVue s computer name 1 Click Start > All Programs > Control Panel > System. The System Properties dialog box appears. 2 Click the Computer Name tab; then click Change. The Computer Name Changes dialog box appears. 3 In the Computer Name field, type the new computer name; then click OK. 4 On the System Properties dialog box, click Apply, then OK. Adding SSL Support TraceMasterVue supports the SSL (Secure Sockets Layer) protocol, used for encrypting transmissions from the server to a cardiograph. SSL uses an encryption system that uses two keys to encrypt data: the public key, and a private key unique to the recipient. CAUTION These keys are a digital certificate key pair and cannot be separated. If you lose your public/private key file or your password and generate a new one, your SSL certificate will no longer match. You will have to request a new SSL certificate and may incur an additional charge. The following sections describe the use of an SSL certificate purchased from VeriSign ( You can purchase certificates from other vendors; the instructions for setup might be different in those cases. Setting up SSL support comprises the following steps: 1 Generating a request for a certificate (see next page). 2 Sending the request to a certificate vendor (for example, VeriSign). 3 Receiving the certificate from the vendor Configuring Cardiograph and TraceMasterVue Communication Guide

93 Adding SSL Support 4 Installing the certificate. 5 Enabling the certificate. 6 Enabling SSL support on the cardiograph. NOTE Simply installing the certificate does not enable SSL on your system. You must perform all of the steps listed above to fully install and enable SSL on your TraceMasterVue system. In addition, you must enable SSL on the cardiographs. Requesting an SSL Certificate To generate a private key pair 1 Select Start > Programs > Administrative Tools > IIS Manager. The IIS Manager console appears. 2 Right-click the Default Web Site entry, and select Properties from the popup menu. 3 Click the Directory Security tab. 4 In the Secure communications section, click Server Certificate. The Certificate Wizard appears. Configuring Cardiograph and TraceMasterVue Communication Guide 4-21

94 Configuring the Network for TraceMasterVue Data Communication 5 Click Next on the Welcome screen. The method selection screen appears. 6 Select Create a new certificate, then click Next. The Delayed or Immediate Request screen appears. 7 Select Prepare the request now, but send later option, then click Next. The Name and Security Settings screen appears Configuring Cardiograph and TraceMasterVue Communication Guide

95 Adding SSL Support 8 Specify the following options, then click Next: Name Name for the certificate, to identify this web site Bit length We recommend keeping the default of Select cryptographic service provider Ensure this check box remains clear. After clicking Next, the Organizational Information screen appears. 9 Specify the organization name and unit, then click Next. Note the following: If your company or department has an or any other symbol that requires using the Shift key in its name, you must spell out the symbol or omit it. The Organizational Unit field is the name of the department or organization unit making the request. After clicking Next, the Common Name screen appears. 10 Specify the name for the site, then click Next. The common name is a combination of the host and domain names, for example, or company.com. Configuring Cardiograph and TraceMasterVue Communication Guide 4-23

96 Configuring the Network for TraceMasterVue Data Communication Certificates can only be used on Web servers using the common name specified during enrollment (that is, the name specified on this screen). For example, a certificate for the domain server.com will receive a warning if accessing a site named or secure.server.com, because these entries are different from that defined, server.com. After clicking Next, the Geographical Location screen appears. 11 Specify the requested information, then click Next. Note the following: The Locality field is the city or town name; for example, Berkeley. Do not abbreviate the state or province name; for example, California. Use the two-letter code without punctuation for country; for example, US or CA. After clicking Next, the File Name screen appears. 12 Browse to the specific folder in which to save the certificate request file, and type the name to use for the this file, then click Next. The Request Summary screen appears, listing all the information you specified thus far. 13 Click Next to process the request, then click Finish on the final screen. 14 Send the request to VeriSign (or other certificate vendor). After receiving the certificate, proceed to the next step, Installing the SSL Certificate on the TraceMasterVue Server on page Configuring Cardiograph and TraceMasterVue Communication Guide

97 Adding SSL Support Installing the SSL Certificate on the TraceMasterVue Server Before you can perform this step, you must have already requested the certificate as described in Requesting an SSL Certificate on page When you receive the certificate file from the vendor, perform the following steps. To install an SSL certificate on the TraceMasterVue server 1 Perform steps 1 through 5 starting on page At step 5, the Pending Certificate Request screen appears. 2 Select Process the pending request and install the certificate, then click Next. The Process Pending Request screen appears. 3 Navigate to the directory in which the certificate is stored and select the certificate file (.cer extension), then click Next. The certificate is installed. Now you are ready to enable the certificate on the TraceMasterVue server, and then on the cardiographs. Configuring Cardiograph and TraceMasterVue Communication Guide 4-25

98 Configuring the Network for TraceMasterVue Data Communication Disabling the Non-Secure Port (Port 80) After requesting and installing an SSL certificate, you must disable the unsecure port, port 80, and configure the system to require the use of the secure, SSL port (port 443). You must also configure a similar setting on individual PageWriter Touch cardiographs that will communicate with the server. For details on configuring the cardiograph, refer to the cardiograph documentation. NOTE Simply installing the certificate does not fully enable SSL on your system. You must perform the following steps to fully install and enable SSL (and disable unsecure communications) on your TraceMasterVue system. In addition, you must enable SSL on the cardiographs. Disabling the Unsecure Port (Port 80) for Cardiograph Communication with the TraceMasterVue Server This process involves selecting the virtual directories used for communication with cardiographs and the WebAPI interface (if you have the WebAPI option), and disabling nonsecure communications (via port 80). Performing this step ensures that all communications between these devices and the TraceMasterVue server are secure. To disable port 80 for cardiograph communications with the TraceMasterVue server 1 Select Start > Programs > Administrative Tools > IIS Manager. The IIS Manager console appears. 2 Expand the Web Sites entry, then expand the Default Web Site entry. 3 Right-click the EMSComm entry, and select Properties from the popup menu. The EMSComm virtual directory is used for cardiograph communication. The Properties dialog box appears Configuring Cardiograph and TraceMasterVue Communication Guide

99 Adding SSL Support 4 Select the Directory Security tab, and, in the Secure communications section, click Edit. The Secure Communications dialog box appears. 5 Select the Require secure channel check box, then click OK. If you have the WebAPI option, proceed to disabling the non-secure port for WebAPI communication (next). Otherwise, proceed to enabling SSL on the cardiograph. Refer to your cardiograph documentation for details. Configuring Cardiograph and TraceMasterVue Communication Guide 4-27

100 Configuring the Network for TraceMasterVue Data Communication Disabling the Unsecure Port (Port 80) for WebAPI Interface Communication with the TraceMasterVue Server This process involves selecting the virtual directory used for communication with the WebAPI interface (if you have the WebAPI option), and disabling non-secure communications (via port 80). The virtual directory you select depends on which standards you follow: WebAPI_WebService. For use with the Philips-extended IHE implementation of the WebAPI interface. WebAPI_WebService_IHE. For use with the standard IHE implementation of the WebAPI interface. You can perform these steps for both entries, as well. Performing this step ensures that all communications with the TraceMasterVue server are secure. To disable port 80 for interactions through the WebAPI with the TraceMasterVue server 1 Select Start > Programs > Administrative Tools > IIS Manager. The IIS Manager console appears. 2 Expand the Web Sites entry, then expand the Default Web Site entry. 3 Right-click the WebAPI_WebService entry, and select Properties from the popup menu. The WebAPI_WebService virtual directory is used for WebAPI interface communication. The Properties dialog box appears. For an example, see the previous section. 4 Select the Directory Security tab, and, in the Secure communications section, click Edit. The Secure Communications dialog box appears Configuring Cardiograph and TraceMasterVue Communication Guide

101 Configuring ECG Import 5 Select the Require secure channel check box, then click OK. 6 If desired, repeat steps 3 through 5. In step 3, right-click the WebAPI_WebService_IHE entry. Proceed to enabling SSL on the cardiograph. Enabling SSL on the PageWriter Touch Cardiograph To enable SSL on the PageWriter Touch cardiograph 1 Touch the Config button on the Command Toolbar. 2 Touch the Remote Sites tab, and select the entry for the TraceMasterVue server. 3 Select the Enable SSL Security check box. 4 In the Server URL field, change the URL to specify using a secure protocol. Change http to https. The system is now configured. Configuring ECG Import TraceMasterVue polls configured directories on a regular basis to look for ECGs to import into the system, and can automatically export ECGs to specified directories based on workflow rules you define. The acquisition/import process consists of the following steps, each of which is described in detail below: Configuring the processing capacity of the server (below) Configuring the inbound directories for acquired ECGs (page 4-34) Placing new ECGs into the appropriate inbound directories Verifying file formats, translating files as needed, and validating the XML schema Saving the ECGs to the TraceMasterVue database Configuring Cardiograph and TraceMasterVue Communication Guide 4-29

102 Configuring the Network for TraceMasterVue Data Communication This section describes the first and second steps. For details about the rest of the import process, see Chapter 7, Setting TraceMasterVue System Options and Chapter 9, Data Communication and Management, in the TraceMasterVue System Configuration and Reference Guide. Configuring the Processing Capacity of the Server To be able to handle the processing of ECGs simultaneously from multiple cardiographs, you must change the settings for simultaneous transfer. To configure processing capacity 1 Right-click the My Computer icon on the desktop and select Manage. The Computer Management window appears Configuring Cardiograph and TraceMasterVue Communication Guide

103 Configuring ECG Import 2 Expand the Services and Applications entry, and then Internet Information Services (IIS) Manager. 3 Right-click Application Pools and select Properties from the popup menu. The Application Pools Properties dialog box appears. 4 Click the Performance tab. 5 Verify that Idle timeout is set to 20 and Web garden is set to 1, as shown below; then click OK. Idle timeout Web garden 6 Repeat steps 3 through 5 for the DefaultAppPools entry. Configuring Cardiograph and TraceMasterVue Communication Guide 4-31

104 Configuring the Network for TraceMasterVue Data Communication 7 Right-click Application Pools and select New > Application Pool from the popup menu. The Add New Application Pool dialog box appears. 8 Type the name EMSCommPool (as shown above) and click OK Configuring Cardiograph and TraceMasterVue Communication Guide

105 Configuring ECG Import 9 Right-click EMSCommPool and select Properties from the popup menu. The EMSCommPool Properties dialog box appears. 10 Click the Performance tab, and specify the following settings: In the Idle Timeout section, select the Shutdown worker processes... check box. Change the field value to 1. In the Web Garden section, select the Maximum number of worker processes check box. Change the field value to Click OK and exit out of the Computer Management window. These settings configure the server to handle 5 simultaneous connections from cardiographs sending 100 ECGs each. You can customize these settings to handle a greater number of simultaneous connections. For each additional connection, increase the Maximum number of processes value by 20. For example, to support 6 simultaneous connections, set the value to 270; for 10 connections, set it to Restart IIS (page 6-30). Configuring Cardiograph and TraceMasterVue Communication Guide 4-33

106 Configuring the Network for TraceMasterVue Data Communication Configuring Inbound Directories The data acquisition process starts with TraceMasterVue reading in ECGs from the configured inbound directories, each of which is associated with a different ECG acquiring device. Use the System Configuration utility Import tab to specify the inbound directories for acquired ECGs. You must also configure each device to send ECGs to these same directories. Philips PageWriter Touch and PageWriter Trim series cardiographs. These ECG files are in Philips XML format. TraceMasterVue allows you to configure a different directory for each device type, if desired. This directory is set up as follows: C:\<installdir>\inbound\PageWriterTouch PageWriter XL (and 100, 200, 300) series cardiographs and M3700 TraceMaster ECG management systems. These ECGs files are not in XML format; rather, they are saved in a proprietary format, and are referred to as PCEF files. TraceMasterVue allows you to configure multiple inbound directories for ECGs from these systems. NOTE You must, however, configure a single directory for inbound ECGs that are transmitted from legacy PageWriter XL, or 100, 200, or 00 series cardiographs. You mark this directory using the Legacy Serial support button on the Import tab. Typically, this directory is set up as follows: C:\<installdir>\inbound\pagewriterxl Philips IntelliVue Information Center. These ECG files are in XML format. They are transferred between systems using a shared directory on the TraceMasterVue server. This directory is automatically configured during the installation process. Typically, this directory is set up as follows: C:\<installdir>\inbound\pmdexport To be able to read and store ECGs captured on an IntelliVue bedside monitor in TraceMasterVue, you must have the appropriate IntelliVue option installed at your site. See your IntelliVue documentation for details. In addition, you must configure the shared directory and define a specific user ID and password to access the directory. For details, see Appendix I, Using TraceMasterVue with the IntelliVue Information Center. Another TraceMasterVue server. TraceMasterVue allows you to configure a different inbound directory for each server. Removable media (for example, diskette) using ECGVue or PharmaVue from any system with network access to the TraceMasterVue server. TraceMasterVue moves the ECGs to the appropriate inbound directory depending on the ECG format Configuring Cardiograph and TraceMasterVue Communication Guide

107 Configuring ECG Import To define import directories 1 In the System Configuration utility, click the Import tab. Two directories are already preconfigured: C:\TraceMasterVue\Inbound\PageWriterTouch C:\TraceMasterVue\Inbound\PageWriterXL, used for ECGs from legacy cardiographs 2 To add a new directory, click Add. The Add Import Process dialog box appears. 3 Set the following field values: Process Form Description Choose the format: HPDT (legacy cardiographs and M3700A TraceMaster systems) PhilipsXML Provide an optional description for the purpose of this import directory Configuring Cardiograph and TraceMasterVue Communication Guide 4-35

108 Configuring the Network for TraceMasterVue Data Communication Inbound Directory Error Directory Locate and select the directory from which to import files Locate and select the directory to which to log errors during import 4 Click OK to save the changes and create the process. 5 When finished making configuration changes, click Finish. 6 Stop and restart services to enable the changes (page 6-29). Enabling Remote Desktop Access As long as the TraceMasterVue server is accessible via the network, Philips Medical Systems support personnel can access the TraceMasterVue computer using Remote Desktop. You do not have to configure anything on the TraceMasterVue server in order to access it via Remote Desktop. Remote access is enabled by default. To enable or disable remote access 1 Click Start > Control Panel > System. The System Properties dialog box appears. 2 Click the Remote tab. 3 In the Remote Desktop section of the dialog box, select (to enable) or clear (to disable) the Allow users to connect remotely to your computer check box. 4 Click OK. To the Remote Desktop connection 1 Click Start > All Programs > Accessories > Communications > Remote Desktop Connection. The Remote Desktop Connection dialog box appears. 2 In the Computer field, type either the TraceMasterVue computer name or its IP address. 3 Click Connect. You are now connected to the server via remote desktop Configuring Cardiograph and TraceMasterVue Communication Guide

109 Chapter 5Adding and Configuring Printers and Fax Capability 5 NOTE This chapter describes how to set up and configure printers and fax capability for use with TraceMasterVue. This chapter provides the following information: Connecting the Printer Configuring the Printer Adding a Printer and Setting Up a TCP/IP Printer Port Changing Printer Priority Printing a Test Page Configuring Fax Capability Configuring Fax Using a Fax Cover Page If you set up TraceMasterVue without configuring a printer, and a user attempts to print, the Fax Wizard appears. Ensure that at least one printer is configured for the TraceMasterVue system. Connecting the Printer This section describes how to add the included HP 4250N printer to your system. The process is similar for other printers. CAUTION Do not connect the printer to the UPS. The printer startup current is more than the UPS can handle. To connect the printer 1 Place the printer on the system table or on your workspace. 2 Plug one end of the network printer cable into the RJ-45 connector on the back of the printer. 5-1

110 Adding and Configuring Printers and Fax Capability 3 Plug the other end of the network printer cable into Port 8 on the front of the hub. NOTE You may have the option of using another port on the hub; however, if you are planning to install the server on the local network, you must keep port 1 available. Keep port 1 open 4 Plug one end of the power cord into the back of the printer and the other end into a wall outlet. The printer is now connected. Configuring the Printer NOTE Your printer must be configured for TCP/IP before you can use it. You can use these instructions to configure the 4250N printer for the first time or to re-configure the printer should you encounter a problem. Before configuring your printer, you must decide whether the TraceMaster system will be set up as a standalone system or as a system on the institution s LAN. If standalone, use the IP address and SubNet Mask provided in the following steps. If on the institution s LAN, you must be assigned a unique IP address and know the appropriate SubNet Mask for the LAN. You will need to use the front panel keys on the printer, and read information from the LCD screen on the front of the printer to configure the device for network use. Refer to Figure 5-1 for the proper button locations, which are referred to in the procedure that follows. 5-2 Installing TraceMasterVue and Configuring Communication

111 Configuring the Printer Figure 5-1 HP 4250N printer controls 1 Stop button 2 Ready light 3 Data light 4 Attention light 5 Menu button 6 Control panel display 7 Down Arrow button 8 Help button 9 Select button 10 Up Arrow button 11 Back Arrow button To configure the printer 1 Press the SELECT button (#9). 2 Scroll up/down (using the down arrow (#7) or up arrow (#10)) to CONFIGURE DEVICE, and press SELECT. 3 Scroll up/down to I/O, and press SELECT. 4 Scroll up/down to EIO 2 JETDRIECT MENU, and press SELECT. 5 Highlight IPX/SPX, and press SELECT. 6 Highlight ENABLE, and press SELECT. 7 Highlight OFF, and press SELECT. 8 Press the BACK button (#11). 9 Highlight TCP/IP, and press SELECT. 10 Scroll up/down to CONFIG METHOD, and press SELECT. 11 Scroll up/down to MANUAL, and press SELECT. 12 Scroll up/down to MANUAL SETTINGS, and press SELECT. 13 Scroll up/down to IP ADDRESS, and press SELECT. Installing TraceMasterVue and Configuring Communication 5-3

112 Adding and Configuring Printers and Fax Capability 14 Change the address settings as follows, pressing SELECT after each entry: a Change IP Byte Address 1 to 172. b Change IP Byte Address 2 to 28. c Change IP Byte Address 3 to 101. d Change IP Byte Address 4 to Press SELECT again. 16 Scroll up/down to SUBNET MASK, and press SELECT. 17 Change the SM Byte settings to , pressing SELECT after each entry. 18 If the Default Gateway must be set: a b Scroll up/down to DEFAULT GATEWAY, and press SELECT. Change the DG Byte settings as indicated by local IT requirements, or set to the IP address entered above. 19 Press SELECT again. The printer is now ready for use. Adding a Printer and Setting Up a TCP/IP Printer Port NOTE You must be logged on with System Administrator privileges to perform these steps. Be sure that your printer and server are connected to the network. It is recommended that you set up at least two printers using the same port, as follows: Name one printer STAT - <printer name>, and assign it a priority of 99; use this printer for manual print requests, and set it as the default printer. Name one printer Normal - <printer name>, and assign it a priority of 1; use this printer for automatic print requests (as a result of workflow rules) To set up a TCP/IP port 1 Click Start > Printers and Faxes. The Printers window shows only one fax icon that ships with the TraceMasterVue system. 2 Double-click the Add Printer icon. The Add Printer Wizard starts. 3 Click Next. The Available Ports screen appears. 4 Click Next. The Local/Network Printer screen appears. 5-4 Installing TraceMasterVue and Configuring Communication

113 Configuring the Printer 5 On this screen, do the following: a Select Local printer attached to this computer. b Clear the Automatically detect check box. c Click Next. The Add HP JetDirect Port Wizard screen appears. 6 On this screen, do the following: a If you already have a port configured, select the port and skip to step 8. If you need to create a new port, select Create a new port. b In the Type of port section, select Standard TCP/IP Port. c Click Next. The Add Standard TCP/IP Printer Port Wizard appears. 7 For printer IP address, type ; then click Next. NOTE If you are using TraceMasterVue on the institution s LAN, specify the appropriate IP address. 8 Select the printer manufacturer and model number; then click Next. The port is configured. 9 Type the printer name; for example, STAT- ECG Department Printer. 10 To set this printer as the system default printer, set the Set as default option to Yes. 11 Click Next until you reach the final screen; then click Finish. A test page prints, indicating the printer is properly configured. 12 Repeat the above steps as many times as needed to configure all of the desired printers. The following figure shows how the printers look in the Printers and Faxes window when configured as suggested in this chapter. Installing TraceMasterVue and Configuring Communication 5-5

114 Adding and Configuring Printers and Fax Capability Changing Printer Priority To change printer priority 1 Click Start > Printers and Faxes. 2 Right-click the printer name of the printer to change, and select Properties from the menu. The Properties dialog box appears. 3 Click Advanced. 4 Set the Priority field as follows: To set a printer at a high-priority, for example, for the STAT printer, set this field to a high number, such as 99. To set a printer to a lower-priority value, for example, for the Normal printer, set this field to a low number, such as 1. 5 Click Apply, and OK to close the dialog box. Printing a Test Page To print a test page 1 Click Start > Printers and Faxes. 2 Right-click the printer name of the printer to test, and select Properties from the menu. The Properties dialog box appears. 3 Click Print Test Page. A page prints from the selected printer. Configuring Fax Capability You can fax ECGs from TraceMasterVue either manually or automatically, as a result of an automated workflow rule. TraceMasterVue uses the native Windows operating system fax capability (Windows Server 2003, Windows XP, and Windows 2000). The process for configuring the fax setup is very similar across platforms. Configure at least one fax system when setting up TraceMasterVue. 5-6 Installing TraceMasterVue and Configuring Communication

115 Configuring Fax Capability Configuring Fax To configure a fax device 1 Click Start > Control Panel > Phone and Modem Options. The Location Information dialog box appears. 2 Configure country, area code, and any other necessary information, then click OK. The Phone and Modem Options dialog box appears. 3 Click Modems, then click Add. The Add Hardware Wizard for installing a modem starts up. Installing TraceMasterVue and Configuring Communication 5-7

116 Adding and Configuring Printers and Fax Capability 4 Select the Don't detect my modem; I will select it from a list check box; then click Next. The Select Manufacturer screen appears. 5 Select the modem manufacturer and model; then click Next. 6 Select the COM2 port; then click Next. The COM2 port is reserved for Fax modem use. 7 Click Finish, then click OK to exit the dialog box. The fax modem is now configured. 5-8 Installing TraceMasterVue and Configuring Communication

117 Configuring Fax Capability Using a Fax Cover Page You can choose whether to have a cover page, and what it looks like. This section describes how to create a cover page. NOTE To successfully fax an ECG, you must create cover sheets within the Windows Fax utility. The cover sheets must be.cov files. Some sample cover pages are stored in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Common Coverpages. To create a fax cover page 1 Run the Windows Fax Cover Page Editor by selecting Start > All Programs > Accessories > Communications > Fax > Fax Cover Page Editor. 2 Follow the steps provided in the Wizard to create the cover page. Installing TraceMasterVue and Configuring Communication 5-9

118 Adding and Configuring Printers and Fax Capability 5-10 Installing TraceMasterVue and Configuring Communication

119 6 Chapter 6Setting Up Processes and Users This chapter provides a brief overview of some basic tasks you will perform during and after system configuration. For detailed information about system configuration and operation, refer to the TraceMasterVue System Configuration and Reference Guide. After installing the components, you must configure the processes and basic settings for running the system and importing ECGs. These steps are described in the this chapter. The next chapter describes how to configure additional system settings, such as locations, workflow rules, security settings, and the like. This chapter provides the following information: Configuring Windows Services for Use with TraceMasterVue TraceMaster Communications Service Settings TraceMaster IO Proxy Service Settings TraceMaster Service Manager Service Settings TraceMaster Status Manager Service Settings Configuring Miscellaneous SQL Server Jobs Deleting Old Messages from the Database Permanently Removing ECGs Flagged as Deleted from the Database Restoring the TraceMasterVue DSN ODBC Connection Setting the Search and Edit Limits Setting the Patient Domain Configuring Users and Groups About TraceMasterVue Users About TraceMasterVue-Specific Windows Groups TraceMasterVue Groups and Associated Permissions Associating Users with TraceMaster Groups Configuring Security Roles Setting and Enabling System Options Running TraceMasterVue Utilities Enabling System Option Changes Starting and Stopping TraceMasterVue Stopping and Restarting IIS Resetting the Application Cache Accessing Online Help

120 Setting Up Processes and Users Adding SSL Support Requesting an SSL Certificate Installing the SSL Certificate on the TraceMasterVue Server Ensuring SSL-Only Communication Disabling SSL on the Client Installer Enabling SSL on the PageWriter Touch Cardiograph Enabling SSL in WebSelect Enabling SSL in the WebAPI Test Client Configuring Windows Services for Use with TraceMasterVue The following Windows services support the TraceMasterVue applications: Service Name TraceMaster Communications Service TraceMaster IO Proxy Service TraceMaster Service Manager Service TraceMaster Status Manager Service Description This Windows service monitors the COM ports set up for legacy PageWriter XL-series cardiographs. When it detects activity, this service verifies that the protocol used is HPDT, and once verified, puts the ECG into the configured PageWriter XL inbound directory; also used for interactive query. This Windows service monitors all of the inbound directories configured for TraceMasterVue. When it detects ECG files, this service calls ECGTranslator to validate and/ or convert the files. This service also hands off the final, validated ECG file to the ECG Database Manager for import into the TraceMasterVue database. This Windows service controls the system status (startup/ shutdown), performs ongoing monitoring of system status (health), and reports that status on a periodic basis. Required in order for the System Monitor to run effectively. This Windows service controls the other TraceMasterVue services (IO Proxy Service, Messaging Service), and also interacts with the standard Windows services (for example, MS SQL Server service) to control the status and state of those services. The following sections show the standard settings and configurations that must be associated with each of these services for TraceMasterVue to function correctly. CAUTION Any changes made to these settings will result in reduced system function and possible loss of data. 6-2 Installing TraceMasterVue and Configuring Communication

121 Configuring Windows Services for Use with TraceMasterVue TraceMaster Communications Service Settings The following settings must be configured for the Communications service. To view or specify service settings 1 Click Start > Administrative Tools > Services. The Services window appears. 2 In the right pane, right-click the TraceMaster Communications Service entry, and select Properties from the menu. The Properties dialog box appears. 3 On the Log On tab, ensure the following settings are selected: Select the Local System account radio button. Ensure the Allow service to interact with the server check box is selected. Click Apply. Installing TraceMasterVue and Configuring Communication 6-3

122 Setting Up Processes and Users 4 On the Recovery tab, ensure the Failure settings are all set to Take No Action, and the Reset fail count field is set to 0. 5 Ensure the Dependencies tab shows no dependencies. TraceMaster IO Proxy Service Settings The following settings must be configured for the IO Proxy service. To view or specify service settings 1 Click Start > Administrative Tools > Services. The Services window appears. 2 In the right pane, right-click the TraceMaster IO Proxy Service entry, and select Properties from the menu. The Properties dialog box appears. 3 Ensure the Log On tab settings are configured as follows: : 6-4 Installing TraceMasterVue and Configuring Communication

123 Configuring Windows Services for Use with TraceMasterVue 4 On the Recovery tab, ensure the Failure settings are all set to Take No Action, and the Reset fail count field is set to 0. 5 Ensure the Dependencies tab shows the following entry: 6 Click OK to apply the settings and close the dialog box. TraceMaster Service Manager Service Settings The following settings must be configured for the Service Manager service. To view or specify service settings 1 Click Start > Administrative Tools > Services. The Services window appears. 2 In the right pane, right-click the TraceMaster Service Manager Service entry, and select Properties from the menu. The Properties dialog box appears. Installing TraceMasterVue and Configuring Communication 6-5

124 Setting Up Processes and Users 3 Ensure the Log On tab settings are configured as follows: 4 On the Recovery tab, ensure the Failure settings are all set to Take No Action, and the Reset fail count field is set to 0. 5 Ensure the Dependencies tab shows the following entries: 6-6 Installing TraceMasterVue and Configuring Communication

125 Configuring Windows Services for Use with TraceMasterVue 6 Click OK to apply the settings and close the dialog box. TraceMaster Status Manager Service Settings The following settings must be configured for the Status Manager service. To view or specify service settings 1 Click Start > Administrative Tools > Services. The Services window appears. 2 In the right pane, right-click the TraceMaster Status Manager Service entry, and select Properties from the menu. The Properties dialog box appears. Installing TraceMasterVue and Configuring Communication 6-7

126 Setting Up Processes and Users 3 Ensure the Log On tab settings are configured as follows: 4 On the Recovery tab, ensure the Failure settings are all set to Take No Action, and the Reset fail count field is set to 0. 5 Ensure the Dependencies tab shows the following entry: 6 Click OK to apply the settings and close the dialog box. 6-8 Installing TraceMasterVue and Configuring Communication

127 Configuring Miscellaneous SQL Server Jobs Configuring Miscellaneous SQL Server Jobs SQL Server is provided with some preconfigured jobs that might be useful to customize: Cleaning up error messages from the database Permanently deleting ECGs that are marked as Deleted from the database Deleting Old Messages from the Database On the TraceMasterVue server, SQL Server includes a preconfigured clean up job that runs daily to delete messages that are more than 30 days old. You can change the parameters of this job, including when to run it and the age of the messages to delete. You access this job through the SQL Server Enterprise Manager. To change when the clean up job is run 1 Display the Enterprise Manager by selecting Start > Programs > Microsoft SQL Server > Enterprise Manager. The Enterprise Manager console appears. 2 Navigate to the Job Agent entry. The clean up job is named Delete TraceMaster Logs. Installing TraceMasterVue and Configuring Communication 6-9

128 Setting Up Processes and Users 3 Double-click Delete TraceMaster Logs to display the Properties dialog box. 4 Click the Schedules tab Installing TraceMasterVue and Configuring Communication

129 Configuring Miscellaneous SQL Server Jobs 5 Click Edit, and then click Change in the Edit Job Schedule dialog box. 6 Change the time as desired, and click OK in each dialog box to save the changes. To change the age of messages to delete 1 Perform steps 1 through 3 of the previous procedure, To change when the clean up job is run. 2 In the Properties dialog box, click the Steps tab. 3 Click Edit or double-click the DeleteLogs entry. The Edit Job Steps dialog box appears. 4 Edit the command line as desired to characterize the messages to delete. By default, messages more than 30 days old are deleted from the database. 5 Click OK in each dialog box to save the changes. 6 Restart IIS (page 6-30). Installing TraceMasterVue and Configuring Communication 6-11

130 Setting Up Processes and Users Permanently Removing ECGs Flagged as Deleted from the Database On the TraceMasterVue server, SQL Server includes a preconfigured clean up job that runs daily to permanently delete ECGs flagged as Deleted that are more than 30 days old from the database. You can change the parameters of this job, including when to run it and the age of the flagged ECGs to delete (page 6-14). You access this job through the SQL Server Enterprise Manager. To change when the clean up job is run 1 Display the Enterprise Manager by selecting Start > Programs > Microsoft SQL Server > Enterprise Manager. The Enterprise Manager console appears. 2 Navigate to the Job Agent entry. The clean up job is named PurgeDeletedECGs Installing TraceMasterVue and Configuring Communication

131 Configuring Miscellaneous SQL Server Jobs 3 Double-click PurgeDeletedECGs to display the Properties dialog box. 4 Click the Schedules tab. 5 Click Edit, and then click Change in the Edit Job Schedule dialog box. 6 Change the time as desired, and click OK in each dialog box to save the changes. 7 Restart IIS (page 6-30). Installing TraceMasterVue and Configuring Communication 6-13

132 Setting Up Processes and Users To change the age of ECGs to delete 1 Perform steps 1 through 3 of the previous procedure, To change when the clean up job is run. 2 In the Properties dialog box, click the Steps tab. 3 Click Edit or double-click the PurgeDeletedECGs entry. The Edit Job Steps dialog box appears. 4 Edit the command line as desired to characterize the ECGs to delete. By default, ECGs flagged as Deleted and more than 30 days old are permanently removed from the database. 5 Click OK in each dialog box to save the changes. 6 Restart IIS (page 6-30) Installing TraceMasterVue and Configuring Communication

133 Restoring the TraceMasterVue DSN ODBC Connection Restoring the TraceMasterVue DSN ODBC Connection TraceMasterVue requires a DSN ODBC system data source connection, named viper, to allow the TraceMasterVue ECG Translator to access TraceMasterVue criteria and serial comparison statements. CAUTION If the settings for this ODBC DSN connection are changed or removed, the TraceMasterVue system will not function correctly. In the event that the TraceMasterVue DSN connection is inadvertently modified or removed, use the following procedure to restore it. To restore the TraceMasterVue DSN ODBC connection 1 Click Start > Administrative Tool > Data Sources (ODBC). The ODBC Data Source Administrator dialog box appears. 2 Click the System DSN tab, then click Add. The Create New Data Source dialog box appears. 3 In the Select list box, locate and select SQL Server; then click Finish. The Create New Data Source to SQL Server screen appears. 4 Do the following: a In the Name field, type viper. b From the Server drop-down list, select either Local or your computer s name. c Click Next. The Authentication screen appears. 5 Do the following: a b c Select the With SQL Server authentication radio button. In both the Login ID and Password fields, type viper. Click Next. 6 On the next screen, leave the selections as is, and click Next. 7 On the final screen, clear the Perform translation check box; then click Finish. The ODBC Microsoft SQL Server Setup dialog box appears. 8 Click Test Data Source. The application tests the connection. If configured properly, the message TEST COMPLETED SUCCESSFULLY! appears. If the connection was not properly restored, repeat the configuration process. If you still experience difficulties, call Philips support. 9 Click OK on each dialog box to exit. Installing TraceMasterVue and Configuring Communication 6-15

134 Setting Up Processes and Users Setting the Search and Edit Limits NOTE You can specify the maximum number of ECGs to retrieve during a search in the client application (ECGVue/PharmaVue), as well as the maximum number of ECGs that a user can select to edit at one time. These settings are captured in registry entries. By default, the Search limit is set to 500 ECGs, and the Edit limit is set to 50 ECGs to review at one time. These default settings provide optimal application performance. If you wish to change the values to allow a higher limit, be aware that system performance may be negatively impacted. The Select First <n> button that appears in the client application when more than <n> records are retrieved displays the number set for the Edit Limit registry key. For example, if the edit limit were to be set to 25 ECGs, the button label would show Select First 25. By default, the button label is Select First 50. For details on the use of this button, see the client application Instructions for Use. If you need to set these limits to a different number, contact TraceMasterVue technical support for information. Setting the Patient Domain TraceMasterVue offers three options for how patient ID uniqueness is handled across different locations. The patient ID uniquely identifies each patient as follows each option is referred to as a particular patient domain: Across the enterprise (across all institutions) (the default setting) The system views all ECGs with the same patient ID, across all institutions, facilities, and departments serviced by TraceMasterVue, as belonging to the same patient. You cannot reuse the same ID within a single TraceMasterVue system. Within an institution The system views all ECGs with the same ID within a single institution as belonging to the same patient. You can reuse the same ID in different institutions. This option is only enabled for use if you have the Universal Edition of TraceMasterVue. Within a facility The system views all ECGs with the same ID within a single facility as belonging to the same patient. You can reuse the same ID in different facilities, within the same institution. This option is only enabled for use if you have the Universal Edition of TraceMasterVue. This patient domain (enterprise, institution, or facility) is defined when the system is initially configured, and requires that the database be empty. Once selected, the domain type can only be changed by flushing the database (including tutorial records), changing the domain type, and then repopulating the database. The selected domain also affects serial comparison rules Installing TraceMasterVue and Configuring Communication

135 Configuring Users and Groups To change the patient domain 1 If you have any data in the database, back up your files and data. 2 Remove the ECGs from the demo database as described in Resetting the Demo ECGs on page Once all of the databases are empty, the Patient Domain check boxes become enabled on the System Configuration utility Global tab. 3 Select the desired domain setting, and click Finish. 4 Stop and restart TraceMasterVue services (page 6-29) for the changes to take effect. 5 Repopulate the database with the demo ECGs (page 11-4). 6 If necessary, restore additional data. Configuring Users and Groups NOTE NOTE If the customer has a policy of clearing off all factory-specified configuration information, user IDs and groups, and the like, make sure you review the appendix, Appendix A, About TraceMasterVue Users and Groups before proceeding. Certain user IDs, groups, user/group associations, and services must be present and configured for TraceMasterVue to run and function properly. If your customer does not harden their systems, you just need to add users to the appropriate TraceMasterVue groups. See Associating Users with TraceMaster Groups on page When setting up the TraceMasterVue system, it is recommended that you configure any new user IDs first, then add users to the TraceMaster groups. For details about adding new users, see Appendix A, About TraceMasterVue Users and Groups. When you add a new user or make changes to an existing user, including changing access/security permissions, it can take up to 10 minutes for the changes to propagate through the system and become effective. To make the changes effective immediately, restart IIS; you must also stop and restart TraceMasterVue services (page 6-29). Installing TraceMasterVue and Configuring Communication 6-17

136 Setting Up Processes and Users About TraceMasterVue Users NOTE This section assumes that you are familiar with the Windows 2003 Server operating system and understand Windows users and groups. For details, see the online help system provided with the operating system, accessible through the Start menu. The ECG viewer/editor, ECGVue or PharmaVue, uses standard Windows user IDs to determine access permission. You configure and maintain user accounts using the Windows 2003 Server Users and Groups Manager. To access the Windows Users and Groups Manager Use either of the following methods: Click Start > Administrative Tools > Computer Management > Local Users and Groups. In the TraceMasterVue System Configuration utility, click the System Administration tab, then click Launch Windows User Manager. For help adding users, refer to the Windows 2003 Server online help system, accessible through the Start menu. To view the list of users on your system 1 Display the Users and Groups window as described in To access the Windows Users and Groups Manager on page The Local Users and Groups window appears. 2 Click the Users folder in the left pane. The users defined on your system are listed in the right pane Installing TraceMasterVue and Configuring Communication

137 Configuring Users and Groups Windows users defined on the system About TraceMasterVue-Specific Windows Groups When installing TraceMasterVue at a site, the appropriate TraceMasterVue groups must be configured. They are used by the TraceMasterVue applications to determine individual users access permissions. When a user requires authorization for a task, for example, to confirm an ECG, TraceMasterVue first checks whether a security role is defined for the logged-in user. If no security role is found (that is, additional access permissions were not specified for this user), TraceMasterVue uses the authorization settings specified for the Windows group to which the user belongs. These groups are automatically configured when TraceMasterVue is installed on the server. However, you must still associate individual users with one or more groups. Only users that are part of a TraceMasterVue group can log into TraceMasterVue applications, including the client. The TraceMasterSysAdmin group has the broadest permissions, authorized to access all modules and perform all functions, including customizing the system and configuring security. It is the responsibility of the system administrator to maintain Windows users, passwords, group associations, and local application security policies. WebAPI option only. If you have this option, your system has an additional TraceMaster group, WebAPI. Only IDs associated with this group will be granted access using the API; that is, any application attempting to access ECGs in the database must use a valid user name/password combination, and the user ID must be a member of the WebAPI group. Installing TraceMasterVue and Configuring Communication 6-19

138 Setting Up Processes and Users TraceMasterVue Groups and Associated Permissions The TraceMasterVue installation program automatically configures the following Windows groups as part of the setup process. You do not have to make any changes to these group settings after installation. Table 6-1 TraceMasterVue groups and associated permissions TraceMasterVue-specific Windows Group Name TraceMaster_SysAdmin TraceMaster_IT TraceMaster_Manager TraceMaster_Tech Description System Administrator. Highest security level IT group. Users that allocate resources and determine system platforms, system support, and maintenance. Manager. May not generally use the system directly, but their technicians will be primary users. As resources and daily routines evolve, ECG Department Managers have a key role to play in the features of the system. Technician. Has access to the basic set of functions necessary to operate the client. In general, the technician enters edits of the reviewing cardiologist, and makes changes to patient records in case of incompleteness or error. Permission Overview Typically, there is only one SA-level password on the system. The SA must be a technically competent person who thoroughly understands the system architecture and software, as well as the Windows operating system. You must be a member of the SysAdmin group to be able to access TraceMasterVue server-side utilities, such as System Configuration, Statement Manager, and the like. Has access to all TraceMasterVue modules Able to perform all functions View ECGs using the client Back up and restore the TraceMasterVue system View, edit, print/fax, and delete ECGs using the client Delete patients from the database; Import/export ECGs using the client Run Management reports using TraceMasterVue Management Reports utility Back up the TraceMasterVue system View, edit, and print/fax ECGs using the client Perform serial comparison on ECGs using the client Import/export ECGs using the client 6-20 Installing TraceMasterVue and Configuring Communication

139 Configuring Users and Groups Table 6-1 TraceMasterVue groups and associated permissions (continued) TraceMasterVue-specific Windows Group Name TraceMaster_HeadTech TraceMaster_RefPhys TraceMaster_ConfCardio TraceMaster_RevCardio TraceMaster_Verifier TraceMaster_COBO Description Head Tech. Has access to a more limited set of functions than the system administrator. The Head Tech can perform routine maintenance procedures. Referring Physician. Needs access to results and diagnosis of ECGs after confirmation by a cardiologist. Confirming Cardiologist. Needs access to new (unconfirmed) ECGs that have been assigned to them to overread, and then confirm. Reviewing Cardiologist. Reviews ECGs, but cannot confirm them. Primarily used in a teaching environment where residents might be reviewing ECGs, and then passing their comments along to a confirming cardiologist. Verifying technician. Reviews demographic information on ECGs. Primarily used in a Pharma environment, where a technician ensures that the demographic information is correct before passing ECGs to be overread. Confirm on Behalf of. Users can confirm an ECG on behalf of a confirming cardiologist. Permission Overview Can perform most functions using the client, including viewing, editing, and printing ECGs Run Management reports using TraceMasterVue Management Reports utility Cannot confirm ECGs or delete patients View and print/fax ECGs using the client Can perform all editing, comparison, and confirming functions using the client View, edit, print/fax, and assign ECGs using the client Perform serial comparison on ECGs using the client Import/export ECGs using the client View, print/fax, assign, verify, and edit demographic (but not measurement or interpretive) information using the client Confirm ECGs using the client NOTE This is a secondary group that only has confirm permissions all users in this group must also belong to another TraceMasterVue-specific group to be able to retrieve, view, and work with ECGs. Installing TraceMasterVue and Configuring Communication 6-21

140 Setting Up Processes and Users Table 6-1 TraceMasterVue groups and associated permissions (continued) TraceMasterVue-specific Windows Group Name TraceMaster_WebAPI NOTE Available only with the WebAPI option. TraceMaster_Guest Description WebAPI user. Provides access to the database using the provided API. Only IDs associated with this group are granted access to the database using the API. Can run the client and have readonly access to ECGs. Permission Overview Can access ECGs in the TraceMasterVue database using the provided API. View ECGs using the client NOTE Table 6-2 The following table shows the exact permissions granted to each of these groups. The TraceMaster_None group is not shown in the table; this group has no access permissions. It is provided so that you can define very specific, limited access to ECGs for a user assigned to this group. For details, see the TraceMasterVue Installation and Configuration Guide. Summary of TraceMasterVue group access permissions System Admin IT ECG Mgr ECG Head Tech ECG Tech Referring Physician Confirming Cardiologist Reviewer Verifier COBO WebAPI ** Guest None View X X X X X X X X X X Edit demographics X X X X X X X Verify ECG X X X X X X X Edit ECG X X X X X X Delete ECG X X X X Delete patient X X X Confirm X X Unconfirm X X X X /print/fax report X X X X X X X X X Assign X X X X X X X Mgmt reports X X X Serial compare X X X X X Backup X X X Restore X X Import/Export X X X X X X X Enterprise Mgr Export X WebAPI access ** X 6-22 Installing TraceMasterVue and Configuring Communication

141 Configuring Users and Groups Table 6-2 Summary of TraceMasterVue group access permissions (continued) System Admin IT ECG Mgr ECG Head Tech ECG Tech Referring Physician Confirming Cardiologist Reviewer Verifier COBO WebAPI ** Guest None Server-side utilities X ** Available only with the WebAPI option. Associating Users with TraceMaster Groups NOTE After adding a new user or making changes to an existing user, including changing access/security permissions, restart IIS. You must also stop and restart TraceMasterVue services. To add users to a TraceMaster-specific group 1 Click Start > Administrative Tools > Computer Management > Local Users and Groups. The Windows Users and Groups Manager appears. 2 Click the Users folder to display the list of defined users in the right pane. Installing TraceMasterVue and Configuring Communication 6-23

142 Setting Up Processes and Users 3 Right-click the user name to associate with a group, and select Properties from the menu. The Properties dialog box appears. 4 Click the Member Of tab, then click Add. The Select Groups dialog box appears. 5 Do either of the following: Type the group name (for example, TraceMaster_ConfCardio) and click OK Click Advanced, then Find Now to view the list of group names, and select the group. 6 Click OK when finished to close each dialog box. The selected group appears in the Member of tab for this user Installing TraceMasterVue and Configuring Communication

143 Configuring Users and Groups Configuring Security Roles Security roles allow you to grant different access permissions to a user. These role definitions are generally created to give a user very specific access to a particular set of ECGs. For example, if two facilities share a TraceMasterVue system, users from each facility might be restricted to ECGs acquired at that facility. In this situation, you would define a security role for each user at each facility and limit their access to ECGs from their associated location. Before proceeding, read about security roles in Appendix A, About TraceMasterVue Users and Groups. To define a security role for a TraceMasterVue user 1 On the System Configuration utility Security Roles tab, click Add. The Add Security Role dialog box appears. 2 In the Signature section, specify the characteristics of the ECGs that the associated user can or cannot work with. See Security Role Examples on page A-17 for some examples. 3 Click Select next to the Patient Name field to specify the patient(s) whose data the user can access. The Select Patient dialog box appears. 4 Select the patient(s) to which to grant access. Options are: All Patients No restrictions. User can access all patient records. Installing TraceMasterVue and Configuring Communication 6-25

144 Setting Up Processes and Users No Patient Specified Search for a specific patient User has no access to patient data. This option might appropriate for users granted System Administrator access. Select this option to enable the location and name fields so you can retrieve a specific patient name. 1 Select the institution associated with the patient, and specify any combination of patient ID, last name, or first name. Specifying any of the last three enables the Search button. 2 Click Search. The system retrieves and displays any matching records in the Search Results list. 3 Click the desired patient entry. The example below illustrates a possible selection. 5 Click OK to accept the entry and return to the Add Security Role dialog box. 6 Click Select next to the User Name field to specify the user for whom these settings apply. The Select User dialog box appears. NOTE If Active Directory is in use at your site, the list of users that appears in this dialog box depends on the configuration of the user logged into the operating system. If the System Configuration utility user is logged into the operating system using a local account, the user list: 6-26 Installing TraceMasterVue and Configuring Communication

145 Setting and Enabling System Options Shows all local users Shows users defined in Active Directory and directly associated with a TraceMaster group Does not show users that are associated with an Active Directory group that is then assigned to a TraceMaster group If the System Configuration utility user is logged into the operating system using a domain account, the user list: Shows all local users Shows users defined in Active Directory and directly associated with a TraceMaster group Shows users that are associated with an Active Directory group that is then assigned to a TraceMaster group 7 Select the user to assign to the role you are defining, and click OK. 8 In the Role section, select the group that has the permissions you are granting to this user for the selected ECGs; then click OK. For the description of groups and associated permissions, see TraceMasterVue Groups and Associated Permissions on page Click Finish to save the role. 10 Restart IIS and TraceMasterVue services. Setting and Enabling System Options As part of configuring the system, you need to define a variety of system options and settings. The following table provides an overview of how each utility is used for configuration. Each of these functions is described in the next chapter. Utility System Configuration Used for... Setting global system options, such as system administrator , whether to use code/statement aliases, criteria version used, and serial comparison options, and for setting options related to: Printed reports Locations Inboxes Workflow rules Individual security settings Events to track Statement Manager Defining custom statements and modifiers, as well as defining code and/or statement aliases. Installing TraceMasterVue and Configuring Communication 6-27

146 Setting Up Processes and Users Utility System Monitor Configuration file Used for... Used for restarting the TraceMasterVue system and IIS, and for running diagnostic tests. Also used to run a simple billing report, as well as the daily system administrator report. Used to add custom management reports to the system. Running TraceMasterVue Utilities The TraceMasterVue utilities are on the server desktop. To launch a utility 1 On the TraceMasterVue server desktop, double-click the utility icon. 2 When prompted, type your credentials to log in. For details about the contents of the each utility, including detailed information about the fields on each tab, see Appendix C, TraceMasterVue Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. Enabling System Option Changes After you make changes to system options on one or more tabs, you must stop and restart TraceMasterVue services (in the System Monitor utility), as well as stop and restart IIS, to enable those changes in the system. In some cases, for example when adding custom statements to the system, you must also flush the cache on individual client systems to be able to immediately access the new entries. To save system option changes 1 Set the desired options as needed. 2 When done, click Finish. 3 Stop and restart TraceMasterVue services. 4 Stop and restart IIS. 5 For the changes listed below, flush the client application cache to make changes available immediately: Change in color scheme Enabling or disabling the Remember me option Custom statement entries Changes to security role assignments (additions, changes, deletions) Change to a user s Windows password 6-28 Installing TraceMasterVue and Configuring Communication

147 Setting and Enabling System Options Starting and Stopping TraceMasterVue In general, you will rarely need to shut down and restart TraceMasterVue services. This step is generally reserved for times when the system is behaving inconsistently, leading you to believe that perhaps one or more services is not running. In addition, you must shut down and restart services when you change system options using the System Configuration utility and when you edit custom statements using the Statements Manager. We recommend that you set options in the order specified in this guide to minimize the number of required restarts. You can set all TraceMasterVue-specific options, then restart once to activate all the changes. You can now restart the system with a single command, Restart. You can also still individually just shut down or start up the system. To restart TraceMasterVue services 1 Double-click the System Monitor icon on the desktop. The System Monitor window appears. 2 To restart the system, select Tools > Restart TraceMasterVue System. The Login dialog box appears. 3 Type your credentials and click OK. The system shuts down and restarts services. Installing TraceMasterVue and Configuring Communication 6-29

148 Setting Up Processes and Users To stop or start TraceMasterVue services 4 To shut down, select Tools > Shutdown TraceMasterVue System. The Login dialog box appears. 5 Type your credentials and click OK. The TraceMasterVue services are shut down. To start up the TraceMasterVue system 1 In the System Monitor menu bar, select Tools > Start TraceMasterVue System. The Login dialog box appears. 2 Type your credentials and click OK. The TraceMasterVue services are started. Stopping and Restarting IIS NOTE You must be a member of the Windows Administrator group on the TraceMasterVue server to have access to these commands. There may be times when you need to restart IIS. One case is when you add a new Windows user and you want to give them immediate access to ECGVue, or when you change a users access permissions, either by changing their Windows group assignment or by specifying a security role, and want to make the change effective immediately. For greater simplicity and ease of use, you can now restart IIS from within the System Monitor utility. You can also restart IIS from within the Computer Management console, Services and Applications section. You also need to stop and restart IIS when restoring system and database files on your system. For details, see Chapter 11, Backing Up and Restoring System Files and Databases. To stop and restart IIS 1 Double-click the System Monitor icon on the desktop. The System Monitor window appears. 2 Select Tools > Restart IIS. A batch file runs and restarts IIS. You are not prompted to confirm the action Installing TraceMasterVue and Configuring Communication

149 Adding SSL Support Resetting the Application Cache As you work with the client application (ECGVue/PharmaVue), the system temporarily stores (caches) information about your user ID, actions you are performing, system state, and the like on your system. The TraceMasterVue system automatically flushes this memory cache every 24 hours. However, when working with Philips personnel or with your TraceMasterVue administrator troubleshooting your system, you may be asked to manually flush your system s cache. To flush your system s cache In the client application menu bar, click Tools > Reset Local Caches. The system clears out the cache. Accessing Online Help Each TraceMasterVue utility and application provides a browser-based online help system to give you easy access to information. To view online help within the System Configuration utility and Statement Manager Click Help at the bottom of each tab. Proceed to the next chapter to set TraceMasterVue options, including locations, inboxes, custom statements, aliases, and the like, using the system utilities. Adding SSL Support TraceMasterVue supports the SSL (Secure Sockets Layer) protocol, used for encrypting transmissions from the server to a cardiograph. SSL uses an encryption system that uses two keys to encrypt data: the public key, and a private key unique to the recipient. CAUTION These keys are a digital certificate key pair and cannot be separated. If you lose your public/private key file or your password and generate a new one, your SSL certificate will no longer match. You will have to request a new SSL certificate and may incur an additional charge. The following sections describe the use of an SSL certificate purchased from VeriSign ( You can purchase certificates from other vendors; the instructions for setup might be different in those cases. Setting up SSL support comprises the following steps: 1 Generating a request for a certificate (see next page). 2 Sending the request to a certificate vendor (for example, VeriSign). 3 Receiving the certificate from the vendor. Installing TraceMasterVue and Configuring Communication 6-31

150 Setting Up Processes and Users 4 Installing the certificate. 5 Enabling the certificate. 6 Removing the client installer from the SSL environment. 7 Enabling SSL support on cardiographs, WebAPI (WebAPI option only), and WebSelect (if you have the OrderVue option). NOTE Simply installing the certificate does not enable SSL on your system. You must perform all of the steps listed above to fully install and enable SSL on your TraceMasterVue system. In addition, you must enable SSL on the cardiographs. Requesting an SSL Certificate To generate a private key pair 1 Select Start > Programs > Administrative Tools > IIS Manager. The IIS Manager console appears. 2 Right-click the Default Web Site entry, and select Properties from the popup menu. 3 Click the Directory Security tab. 4 In the Secure communications section, click Server Certificate. The Certificate Wizard appears Installing TraceMasterVue and Configuring Communication

151 Adding SSL Support 5 Click Next on the Welcome screen. The method selection screen appears. 6 Select Create a new certificate, then click Next. The Delayed or Immediate Request screen appears. 7 Select Prepare the request now, but send later option, then click Next. The Name and Security Settings screen appears. Installing TraceMasterVue and Configuring Communication 6-33

152 Setting Up Processes and Users 8 Specify the following options, then click Next: Name Name for the certificate, to identify this web site Bit length We recommend keeping the default of Select cryptographic service provider Ensure this check box remains clear. After clicking Next, the Organizational Information screen appears. 9 Specify the organization name and unit, then click Next. Note the following: If your company or department has an or any other symbol that requires using the Shift key in its name, you must spell out the symbol or omit it. The Organizational Unit field is the name of the department or organization unit making the request. After clicking Next, the Common Name screen appears. 10 Specify the name for the site, then click Next. The common name is a combination of the host and domain names, for example, or company.com Installing TraceMasterVue and Configuring Communication

153 Adding SSL Support Certificates can only be used on Web servers using the common name specified during enrollment (that is, the name specified on this screen). For example, a certificate for the domain server.com will receive a warning if accessing a site named or secure.server.com, because these entries are different from that defined, server.com. After clicking Next, the Geographical Location screen appears. 11 Specify the requested information, then click Next. Note the following: The Locality field is the city or town name; for example, Berkeley. Do not abbreviate the state or province name; for example, California. Use the two-letter code without punctuation for country; for example, US or CA. After clicking Next, the File Name screen appears. 12 Browse to the specific folder in which to save the certificate request file, and type the name to use for the this file, then click Next. The Request Summary screen appears, listing all the information you specified thus far. 13 Click Next to process the request, then click Finish on the final screen. 14 Send the request to VeriSign (or other certificate vendor). After receiving the certificate, proceed to the next step, Installing the SSL Certificate on the TraceMasterVue Server on page Installing TraceMasterVue and Configuring Communication 6-35

154 Setting Up Processes and Users Installing the SSL Certificate on the TraceMasterVue Server Before you can perform this step, you must have already requested the certificate as described in Requesting an SSL Certificate on page When you receive the certificate file from the vendor, perform the following steps. To install an SSL certificate on the TraceMasterVue server 1 Perform steps 1 through 5 starting on page At step 5, the Pending Certificate Request screen appears. 2 Select Process the pending request and install the certificate, then click Next. The Process Pending Request screen appears. 3 Navigate to the directory in which the certificate is stored and select the certificate file (.cer extension), then click Next. The certificate is installed. Now you are ready to enable the certificate on the TraceMasterVue server, and then on the cardiographs Installing TraceMasterVue and Configuring Communication

155 Adding SSL Support Ensuring SSL-Only Communication To ensure that all communication is secure, after requesting and installing an SSL certificate, you must disable the standard unsecure port. Disabling this port requires the system to use the secure SSL port. NOTE Simply installing the certificate does not fully enable SSL on your system. You must perform the following steps to fully install and enable SSL (and disable unsecure communications) on your TraceMasterVue system. In addition, you must enable SSL on devices and systems that communicate with the server. This includes cardiographs, WebAPI (if you have the option), and WebSelect (if you have the OrderVue option). To ensure SSL-only communication 1 Select Start > Programs > Administrative Tools > IIS Manager. The IIS Manager console appears. 2 Expand the Web Sites entry, then expand the Default Web Site entry. 3 Right-click the Default Web Site entry, and select Properties from the popup menu. The Properties dialog box appears. Installing TraceMasterVue and Configuring Communication 6-37

156 Setting Up Processes and Users 4 Select the Directory Security tab, and, in the Secure communications section, click Edit. The Secure Communications dialog box appears. 5 Select the Require secure channel check box, then click OK on each dialog box to accept the changes and exit. Proceed to disabling SSL on the smart client installer Installing TraceMasterVue and Configuring Communication

157 Adding SSL Support Disabling SSL on the Client Installer The Windows operating system generally does not allow you to install and configure a smart client within an SSL-secured environment. To disable SSL on the client installer 1 Under the Default Web Site entry, right-click the EMSClient entry, and select Properties from the popup menu. The Properties dialog box appears. 2 Select the Directory Security tab, and, in the Secure communications section, click Edit. The Secure Communications dialog box appears. Installing TraceMasterVue and Configuring Communication 6-39

158 Setting Up Processes and Users 3 Clear the Require secure channel check box, then click OK on each dialog box to accept the changes and exit. 4 Restart IIS by right-clicking the computer name and selecing All Tasks > Restart IIS. Proceed to enabling SSL on the cardiograph, WebAPI, and WebSelect. Enabling SSL on the PageWriter Touch Cardiograph To enable SSL on the PageWriter Touch cardiograph 1 Touch the Config button on the Command Toolbar. 2 Touch the Remote Sites tab, and select the entry for the TraceMasterVue server. 3 Select the Enable SSL Security check box. 4 In the Server URL field, change the URL to specify using a secure protocol. Change http to https Installing TraceMasterVue and Configuring Communication

159 Adding SSL Support Enabling SSL in WebSelect Enabling SSL in WebSelect requires a change to the OrderURL registry key. This step is best performed by a Philips representative. Enabling SSL in the WebAPI Test Client Refer to the WebAPI Reference Guide for details. The system is now configured. Installing TraceMasterVue and Configuring Communication 6-41

160 Setting Up Processes and Users 6-42 Installing TraceMasterVue and Configuring Communication

161 7 Chapter 7Setting Up and Configuring TraceMasterVue System Options After installing components and performing the initial configurations described in previous chapters, you are ready to configure TraceMasterVue system options. The following table provides an overview of how each utility is used for configuration. Each of these functions is described in this chapter. Utility System Configuration Statement Manager System Monitor Configuration file Used for... Setting global system options, such as system administrator , whether to use code/statement aliases, criteria version used, and serial comparison options, and for setting options related to: Printed reports Locations Inboxes Workflow rules Individual security settings Events to track Defining custom statements and modifiers, as well as defining code and/or statement aliases. Used for restarting the TraceMasterVue system and IIS, and for running diagnostic tests. Also used to run a simple billing report, as well as the daily system administrator report. Used to add custom management reports to the system. 7-1

162 Setting Up and Configuring TraceMasterVue System Options This chapter provides the following information: Before You Begin Setting Global Options Setting the Statement Criteria Version Setting the System Address Setting Serial Comparison Criteria Configuring Interactive Query Support on TraceMasterVue Setting ECG Confirmation Authentication Requirements Configuring Inactivity Timeout Settings for ECGVue Configuring the Remember Me Option Configuring Import Directories and Formats Before You Begin Placing New ECGs into Inbound Directories Configuring Location Information in TraceMasterVue Before You Begin Configuring Institutions Configuring Facilities Configuring Departments Configuring User-Defined Field Values in TraceMasterVue Before You Begin Configuring the Physician List Before You Begin About Associating Physicians with Locations Importing Physician Data in CSV Format Manually Entering Physician Information Setting ECG Report Options Configuring Inboxes Before You Begin Defining Inboxes Defining Automated Workflow Rules Commonly Used Workflow Rules Before You Begin Defining a New Workflow Rule Defining Print, Fax, and Export Rules Adding Notification to a Rule Defining Aliases and Custom Statements Before You Begin Using Statement Aliases Enabling Statement Aliasing Defining Statement Aliases Configuring Custom Modifiers, Codes, and Statements Configuring Custom Modifiers and Codes Configuring Custom Statements Enabling Settings Completing TraceMasterVue Communication Configuration Installing TraceMasterVue and Configuring Communication

163 Before You Begin Installing ECGVue/PharmaVue on Client Systems Installing the Report Manager on Client Systems Verifying that the System Works Setting Up System and File Backups Configuring Cardiographs to Communicate with TraceMasterVue Before You Begin Before proceeding, ensure you have all the worksheets filled out so that you can populate the system with the appropriate information. Worksheets are available in Chapter 2, TraceMasterVue Communication Worksheets. Also, we recommend you read the first six appendices to this guide to familiarize yourself with important TraceMasterVue features and concepts. Setting Global Options The System Configuration utility Global tab lets you specify system-wide settings, including whether to enable serial comparison, interactive query, code/statement aliases, electronic signature, and single confirmation, default address for administrative notification, and language and units of measure. For details about the fields on this tab, see Appendix C, TraceMasterVue Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. NOTE Setting the Statement Criteria Version ECGs recorded on selected Philips medical devices (PageWriter Touch cardiographs, IntelliVue monitors) are analyzed using the Philips 12-Lead Algorithm, which generates the interpretive statements displayed on the ECG report. The statement settings you specify determine the criteria version that is used to analyze ECGs and generate the associated interpretive statements. The interpretive statements generated are determined by the statement criteria used during analysis. TraceMasterVue arrives at your institution with codes already installed for adult criteria versions 06, 07, 08, 09, and 0A, and for pediatric criteria versions P2, P3, P4, and 0A. You can define custom statements for each criteria, or, as an alternative, define code and/or statement aliases for factory-defined statements. Aliases allow you to map codes and statements in a selected criteria version (for example, 0A) to your own site-specific nomenclature. For details, see About Statement Aliasing on page C-2. You set and view the criteria version as follows: The Statement Manager Statement Set tab allows you to select the criteria version. By default, the selected criteria version is 0A. The System Configuration utility Global tab displays the selected criteria version, as well as the serial comparison algorithm version. Installing TraceMasterVue and Configuring Communication 7-3

164 Setting Up and Configuring TraceMasterVue System Options NOTE When importing ECGs, if the system does not recognize the measurement or criteria version, one of two things happens: If you are importing an ECG from a legacy system (M3700 TraceMaster or XL-series cardiographs), the system rejects the ECG and writes an error to the error log. If you are importing an XML-format ECG, the system imports the ECG, but without interpretive statements or other data dependent on the criteria version (race, Dx/Rx codes, and the like). A warning message is written to the error log. Setting the System Address You must specify the System Administrator address. This is the default return address used in workflow-initiated notifications, and is also used for the daily System Administration report notification (if enabled). This address is specified in the System Configuration utility, on the Global tab in the section. The Default Address field shows the default address that will appear in the Sender field of notification messages triggered by automated workflow rules. This is a required field. The SMTP Server field specifies the SMTP server to be used for workflow and ad-hoc notifications. This is a required field. To set the System Administrator address 1 Run the System Configuration utility. 2 On the Global tab, click the Configure button. The Configure Settings dialog box appears. 3 Set fields as follows: The SMTP configuration is stored in tblglobal on the system. Basic SMTP Settings SMTP Server Name URL of the server to be used for workflow and ad-hoc notifications. This is a required field. 7-4 Installing TraceMasterVue and Configuring Communication

165 Setting Global Options Basic SMTP Settings Default From Set the address to use in the From field of messages sent. This address appears in the From address of system level alert messages, and is the default From address for new workflow rules. To have the system always use this address, select the Always use this as From address check box. Note that when this check box is selected, you cannot edit the From field within the workflow rule. The field is pre-filled with the address and remains read-only. NOTE It is common for SMTP servers to require that the From address be identical to the address associated with the SMTP account, so this field may be identical to the User Name field. Advanced SMTP Settings Outgoing server port number Specify the port number to use for outgoing messages. By default, set to 25. To send messages over encrypted connection using SSL, select the This server requires an encrypted connection check box. Clicking the Use SMTP Defaults button returns the settings to port 25 and disables SSL. Authorization Outgoing SMTP server requires authorization To always require secure password authentication (SPA), select the Log on using Secure Password Authentication check box. Selecting the check box enables NTLM authentication, and enables the User Name and Password fields. The password is masked on entry and is stored in the tblglobals table in the database in an encrypted format. System Alerts Installing TraceMasterVue and Configuring Communication 7-5

166 Setting Up and Configuring TraceMasterVue System Options system alerts and errors to Specify the address to which to send notification about system issues. 4 To test the settings, click Send Test . The Testing Settings dialog box appears. 5 Verify that the addresses specified in the From and To fields are correct and are the same as those specified in the Configure Settings dialog box, then click Send Test . The system sends the , which may take up to 1 minute, and returns either a Success message or an error message indicating what the problems might be. 6 Check the account to which the was sent to verify that it was successfully received. 7 When the test is finished, click Close to close the Test dialog box, then click OK to close the Configure Settings dialog box. 8 Continue setting options. When done, you will click Finish and restart services. Setting Serial Comparison Criteria You enable/disable the serial comparison function on the Global tab. On this tab, you also specify the basic parameters for performing serial comparison, including age difference thresholds, whether the previous ECG must come from the same institution, and whether the previous ECG must be confirmed. Which options are available depend in part on which patient domain is in use: When the Enterprise domain is used, you can specify whether the institution and/or facility must be the same for both ECGs to be compared. When the Institution domain is used, only ECGs from the same institution can be compared (this setting cannot be changed). You can additionally specify whether only ECGs from the same facility can be compared. When the Facility domain is used, only ECGs from the same institution and facility can be compared (this setting cannot be changed). You can also automate the occurrence of a serial comparison by defining workflow rules. For example, you can define a rule that specifies that ECGs from a particular department are 7-6 Installing TraceMasterVue and Configuring Communication

167 Setting Global Options automatically serially compared when they enter the TraceMasterVue system. For details, see Defining Automated Workflow Rules on page To set serial comparison options (ECGVue only) 1 Run the System Configuration utility. The Global tab appears. 2 In the Serial Comparison section, select the desired options, as described below. Option Enable Previous ECG must come from same institution Previous ECG must come from same facility Previous ECG must be confirmed Description Selecting this check box enables the serial comparison function. This applies both to being able to perform serial comparison in ECGVue, as well as performing serial comparison when triggered by an automated workflow rule. Selecting this check box specifies that only ECGs from the same institution can be compared using the serial comparison function. Therefore, if the previous ECG is from a different institution, the serial comparison algorithm looks for the next previous ECG from the same institution. If none is found, no comparison is performed. This check box is available if the selected patient domain is Enterprise. If the patient domain is Institution, this check box is selected and cannot be disabled. Selecting this check box specifies that only ECGs from the same institution and facility can be compared using the serial comparison function. Therefore, if the previous ECG is from a different facility, the serial comparison algorithm looks for the next previous ECG from the same facility. If none is found, no comparison is performed. This check box is available if the selected patient domain is Institution. If the patient domain is Facility, this check box is selected and cannot be disabled. Selecting this check box specifies that the current ECG can only be compared to a confirmed ECG Therefore, if the previous ECG is unconfirmed, the serial comparison algorithm looks for the next previous confirmed ECG. If none is found, no comparison is performed. Installing TraceMasterVue and Configuring Communication 7-7

168 Setting Up and Configuring TraceMasterVue System Options Option ECG Age Difference Threshold Description Specifies the required minimum time interval between the current and previous ECG in order for them to be compared. Options are minutes, hours, or days. By default, set to 30 minutes. If the previous ECG does not meet the elapsed time requirement, the serial comparison algorithm looks for the next previous ECG. If none is found, no comparison is performed. The minimum time interval is 5 minutes. 3 Continue setting options. When done, you will click Finish and restart services. Configuring Interactive Query Support on TraceMasterVue The ability to access the TraceMasterVue database and retrieve individual ECGs at the cardiograph is referred to as interactive query. You must enable this support both on the TraceMasterVue system and on each cardiograph. NOTE Interactive query is not supported with TraceMaster PharmaVue, nor on PageWriter Trim I. To configure interactive query support on TraceMasterVue 4 On the System Configuration utility Global tab, select the Interactive Query check box. 5 Continue setting options. When done, you will click Finish and restart services. For details on configuring interactive query on cardiographs, see the chapter for each cardiograph, later in this guide. Setting ECG Confirmation Authentication Requirements You can specify authentication requirements for users confirming ECGs at your site. This setting is specified on the System Configuration utility Global tab, using the Re-authentication required for ECG confirmation check box. Options are: 7-8 Installing TraceMasterVue and Configuring Communication

169 Setting Global Options Require user authentication (user name and password) for every ECG/batch of ECGs confirmed Allow the signed-in user to confirm ECGs without requiring additional authentication The first option is more secure, and is recommended for sites where multiple users share workstations; it protects ECGs from being marked as confirmed by somebody other than the logged-in user. When the user opts to confirm a batch of ECGs (from the Search page), the user only needs to re-authenticate credentials once for the full batch of ECGs. To require additional user authentication for ECG confirmation 1 On the System Configuration utility Global tab, click the Re-authentication required for ECG confirmation check box to require that the user type their user name and password for each ECG/batch of ECGs confirmation. 2 Continue setting options. When done, you will click Finish and restart services. To disable additional user authentication for ECG confirmation 3 On the System Configuration utility Global tab, clear the Re-authentication required for ECG confirmation check box. If the logged-in user has confirmation privileges, ECGs can be confirmed without requiring additional user authentication. 4 Continue setting options. When done, you will click Finish and restart services. Configuring Inactivity Timeout Settings for ECGVue To enhance system security, TraceMasterVue provides the option to specify a time interval after which ECGVue automatically logs out users that have been inactive in the application for that period of time. You configure this information on the System Configuration utility Global tab, using the Idle Editor Timeout check box and field. When enabled, once the user s inactivity time period is 30 seconds short of the scheduled disconnection, ECGVue starts a final count down that is displayed in the application title bar. By performing a simple action in the ECGVue application, for example, clicking a button in the Action bar, during this time period, the inactivity counter is reset and the count down stops. Installing TraceMasterVue and Configuring Communication 7-9

170 Setting Up and Configuring TraceMasterVue System Options If the user does not interact with the application for the configured period of time, the application logs out the user and displays the ECGVue Login page. The title bar of the page indicates that they were logged out due to inactivity. To configure the idle timeout period 1 On the System Configuration utility Global tab, select the Idle Editor Timeout check box. When selected, the Time box becomes active. 2 In the Time box, type the desired number of minutes before the user is logged out due to inactivity. For example, if you set the time interval to 45 minutes, the system logs out users after 45 minutes of inactivity in the application. 3 Continue setting options. When done, you will click Finish and restart services. Configuring the Remember Me Option The Remember Me option on the Global tab provides the option, on a user-by-user basis, to have the system remember all of a user s credentials, including user name, domain, and password. By default, this option is disabled (as shown above), requiring every user to provide their password upon each login to any TraceMasterVue application, whether on the server or a client system. For details, see Chapter 7, Setting TraceMasterVue System Options, in the TraceMasterVue System Configuration and Reference Guide. To enable or disable the Remember Me option on the TraceMasterVue system 1 In the System Configuration utility Global tab, do one of the following: To enable the option, select the Enable the Remember Me option check box. To disable the option, clear the Enable the Remember Me option check box Installing TraceMasterVue and Configuring Communication

171 Configuring Import Directories and Formats 2 Continue setting options. When done, you will click Finish and restart services. NOTES After enabling the option in the System Configuration utility, it takes two user logins for the check box to appear on the Login screen. (When first enabled, the client or other server application does not have information about the status of the Remember Me option. This information becomes available after the first login; the check box then appears on subsequent logins.) Similarly, when disabled, the check box is removed from the Login screen subsequent to the first login. If the check box was previously selected and is now cleared, the application cache must be flushed on each client system for the change to take effect. Configuring Import Directories and Formats Use the System Configuration utility Import tab to specify which directories TraceMasterVue should monitor for incoming ECGs. TraceMasterVue polls configured directories on a regular basis to look for ECGs to import into the system, and can automatically export ECGs to specified directories based on workflow rules you define. Before You Begin Before proceeding, ensure you are familiar with the import information in Chapter 9, Data Communication and Management, in the TraceMasterVue System Configuration and Reference Guide, and have available the filled out communication and cardiograph-related worksheets (Chapter 2, TraceMasterVue Communication Worksheets ). Placing New ECGs into Inbound Directories The data acquisition process starts with TraceMasterVue reading in ECGs from the configured inbound directories, each of which is associated with a different ECG acquiring device. You set up the inbound directories using the Import tab. You must also configure each device to send ECGs to these same directories. Philips PageWriter Touch and Trim series cardiographs. These ECG files are in XML format. TraceMasterVue allows you to configure a different directory for each device type. These directories are set up as follows: C:\TraceMasterVue\Inbound\PageWriterTouch PageWriter XL (and 100, 200, 300) series cardiographs and M3700 TraceMaster ECG management systems. These ECGs files are not in XML format; rather, they are saved in a proprietary format, and are referred to as PCEF files. TraceMasterVue allows you to configure multiple inbound directory for ECGs from these systems. Installing TraceMasterVue and Configuring Communication 7-11

172 Setting Up and Configuring TraceMasterVue System Options NOTE You must, however, configure a single directory for inbound ECGs that are transmitted from a legacy PageWriter XL or 100, 200, 300 series cardiograph. You mark this directory using the Legacy Serial support button on the Import tab. Typically, this directory is set up as follows: C:\TraceMasterVue\Inbound\PageWriterXL Philips IntelliVue Information Center. These ECG files are in XML format. They are transferred between systems using a shared directory on the TraceMasterVue server. This directory is automatically configured during the installation process. Typically, this directory is set up as follows: C:\TraceMasterVue\Inbound\pmdexport To be able to read and store ECGs captured on an IntelliVue bedside monitor in TraceMasterVue, you must have the appropriate IntelliVue option installed at your site. See your IntelliVue documentation for details. In addition, you must configure the shared directory and define a specific user ID and password to access the directory. For details, see Appendix D, Using TraceMasterVue with the IntelliVue Information Center. HeartStart MRx defibrillators. These ECGs are in XML format. ECGs are generally transferred from the defibrillator to the Philips 12 Lead Transfer station, and then placed in the inbound directory over the LAN. The inbound directory is the same as that for the PageWriter Touch and Trim cardiographs, C:\TraceMasterVue\Inbound\PageWriterTouch. Another TraceMasterVue server. TraceMasterVue allows you to configure a different inbound directory for each server. Removable media (for example, diskette) using ECGVue from any system with network access to the TraceMasterVue server. TraceMasterVue moves the ECGs to the appropriate inbound directory depending on the ECG format. The appropriate TraceMasterVue HTTP handler (depending on the file type) checks the inbound directories for ECG files every four (4) seconds. This interval is not configurable Installing TraceMasterVue and Configuring Communication

173 Configuring Import Directories and Formats To define import directories 1 In the System Configuration utility, click the Import tab. Two directories are already preconfigured: C:\TraceMasterVue\Inbound\PageWriterTouch C:\TraceMasterVue\Inbound\PageWriterXL, used for ECGs from legacy cardiographs 2 To add a new directory, click Add. The Add Import Process dialog box appears. 3 Set the following field values: Process Form Description Choose the format: HPDT (legacy cardiographs and M3700A TraceMaster systems) PhilipsXML Provide an optional description for the purpose of this import directory Installing TraceMasterVue and Configuring Communication 7-13

174 Setting Up and Configuring TraceMasterVue System Options Inbound Directory Error Directory Locate and select the directory from which to import files Locate and select the directory to which to log errors during import 4 Click OK to save the changes and create the process. 5 Continue setting options. When done, you will click Finish and restart services Installing TraceMasterVue and Configuring Communication

175 Configuring Location Information in TraceMasterVue Configuring Location Information in TraceMasterVue The location identifies where an ECG was acquired, and comprises three levels: institution, facility, and department. Location information is organized as a hierarchy, with institutions containing one or more facilities, which in turn comprise one or more departments. By default, TraceMasterVue ships with two institutions preconfigured: 999, for ECGs provided in the database for training purposes 000, for unassigned (undefined) ECGs (analogous to a lost and found bin) You define institutions, facilities, and departments using the System Configuration utility Locations tab. Individual locations are identified by both a code and descriptive text. Before You Begin Before proceeding, ensure you are familiar with locations by reading Appendix B, Using Location Information in TraceMasterVue, and have available the filled out Location worksheet (page 2-11). Configuring Institutions NOTE The number of different locations that you can configure on your system depends on which edition of TraceMasterVue is installed. To add an institution 1 In the System Configuration utility Locations tab, click Add Institution. The Add/Edit Institution dialog box appears. ECGVue PharmaVue Installing TraceMasterVue and Configuring Communication 7-15

176 Setting Up and Configuring TraceMasterVue System Options 2 Specify the name, code, and other attributes; then click OK. If you are configuring locations for PharmaVue, you can also set Trend thresholds for this location. For details, see Appendix A, Setting PharmaVue-Specific Options. The new institution is added to the Currently Defined Locations list. In addition, the system automatically creates an Unidentified Facility and within that facility, an Unidentified Department. For details, see Appendix B, Using Location Information in TraceMasterVue. The attributes you specify here are used as default settings for facilities and departments you associate with this institution. NOTE Once specified and saved, you cannot change the code associated with the institution. Configuring Facilities NOTE The number of different locations that you can configure on your system depends on which edition of TraceMasterVue is installed. For details on location limits, contact your Philips representative. To add a facility 1 In the System Configuration utility Locations tab, in the Currently Defined Locations list, click the institution with which to associate the new facility. A facility is always attached to an institution. 2 Click Add Facility. The Add/Edit Facility dialog box appears. ECGVue PharmaVue 7-16 Installing TraceMasterVue and Configuring Communication

177 Configuring Location Information in TraceMasterVue 3 Specify the name, code, and other attributes; then click OK. If you are configuring locations for PharmaVue, you can also set Trend thresholds for this location. For details, see Appendix A, Setting PharmaVue-Specific Options. NOTE Once specified and saved, you cannot change the code associated with the facility. The new facility is associated with the selected institution. In addition, TraceMasterVue creates an Unidentified department entry under the facility you just added. Configuring Departments To add a department 1 In the System Configuration utility Locations tab, in the Currently Defined Locations list, click the facility with which to associate the new department. A department is always attached to a facility. 2 Click Add Department. The Add/Edit Department dialog box appears. 3 Specify the name, code, and other attributes; then click OK. Note that once specified and saved, you cannot change the code associated with the department. 4 Continue setting options. When done, you will click Finish and restart services. Installing TraceMasterVue and Configuring Communication 7-17

178 Setting Up and Configuring TraceMasterVue System Options Configuring User-Defined Field Values in TraceMasterVue TraceMasterVue captures up to eight user field values that you might have set up for cardiographs at your site. On the cardiograph and in the XML files, these fields are referred to as user defined fields, or user defines. User fields are fields that can contain any information deemed important for your organization, and are defined both on the acquiring devices (cardiographs) and in TraceMasterVue. Some common user field labels are Timepoint, Cohort, Subject or Volunteer ID (for clinical trials, if used in addition to patient ID), Visit ID, and so on. NOTE If you do not need this functionality for legacy cardiograph support, (PageWriter XL, 200, 300), we strongly recommend that all user field definition and entry occur at the cardiograph. The ability to define user field labels on TraceMasterVue is provided to allow you to override the legacy cardiograph labels User Field A and User Field B with more descriptive labels, for displ.ay and report printing purposes only. User fields and their associated values, if any, appear in the ECGVue or PharmaVue Additional Data section, on the right side of the Summary page, as well as on the Advanced Search page. For details, see the ECGVue or PharmaVue online help. Before You Begin Before proceeding, ensure you are familiar with the material in Appendix D, About User Fields, and have filled out the User Field worksheet (page 2-12). To define user fields in TraceMasterVue 1 In the System Configuration utility, click the User Fields tab, and type the field labels in the appropriate fields. User fields appear in ascending order in the Additional Data section of the ECGVue/ PharmaVue Summary view. NOTES If you are using user field 2 for Order ID, set the field label to ORDERVUE ID, typed with the same capitalization as shown here. You must also ensure that the field label specified under the field rule for zpd_48 User_Defined_2 in the OrderVue Disk.mpr mapper file is identical to that specified for the user defined field (2 on PageWriterTouch/Trim, B on legacy cardiographs) on the cardiograph. That is, the two must match exactly. The mapper is stored in C:\Orderlnk\diskmapper and accessed through the LinkTools HL7 mapper. For additional details about OrderVue and HL7, refer to the OrderVue training materials. If you are using User Define 8 on the cardiograph, you must configure the field on the cardiograph as specified in the Defining User Fields section for PageWriterTouch or PageWriter Trim cardiographs, later in this guide. You do not need to configure anything on TraceMasterVue. 2 Continue setting options. When done, you will click Finish and restart services Installing TraceMasterVue and Configuring Communication

179 Configuring the Physician List Configuring the Physician List TraceMasterVue has the ability to store referring (ordering) physician information, primarily to identify a fax number or address for ECG transmission as a result of an automated workflow rule (for example, to receive a copy of the ECG report upon confirmation of the ECG). For each physician, the system can store name, address, fax number, and a physician ID. The physician ID must be unique for a specified location (institution/facility/department), but the same physician ID may be used at different locations in the hierarchy. For detailed information about associating physicians with locations, see About Associating Physicians with Locations in Chapter 6, Setting ECG Viewing and Processing Options, of the TraceMasterVue System Configuration and Reference Guide. As you define fax or workflow rules, you can, with a single click, specify that the ECG be sent to the referring physician. For details about defining rules using physician information, see Defining Print, Fax, and Export Rules on page You add and manage physician entries using any of the following methods: Import an existing list (for example, from a TraceMaster NT system) in CSV format Manually define entries using the System Configuration utility Physicians tab Before You Begin Before proceeding, have available the filled out Physician worksheet (page 2-15). About Associating Physicians with Locations You associate each physician with a location, which can be at the institution, facility, or department level. In addition, for each physician you specify a physician ID; use the same ID that other systems in the hospital use for this physician. This ID is set to be unique for each location in the institution/facility/department hierarchy, but you can use the same ID for different locations. That is, two physicians associated with the same location combination must have unique IDs. When a physician is associated with an institution or facility, all lower-level locations are indicated as All xxxxx. For example, if the physician is associated with Facility A, then that ID is associated with all departments within Facility A. Similarly, if the physician is associated with Institution 123, that ID is also associated with all facilities and departments within that institution. However, if a physician is associated with Department 01, that ID is only available for ECGs originating in that department. In the same vein, an ECG associated with a department has available to it all physicians that are associated with that department, as well as the facility that contains the department, and the institution that contains the facility, as well as those physicians who have global access. Installing TraceMasterVue and Configuring Communication 7-19

180 Setting Up and Configuring TraceMasterVue System Options The following examples use the physician information presented below: Example 1 The physician (illustrated above) with Physician ID of MC-0001 is applicable to all ECGs in the Main Campus facility, whether the ECG is located in the Heart Center, Emergency Room, or other department. On the other hand, the physician with an ID of HC-0001 is only applicable to ECGs located in the Heart Center department, and has no relevance to ECGs in the Emergency Room or any other department. Example 2 An ECG associated with a specific department can have relevant physicians that are targeted at that particular department and those targeted at its parent facility and those targeted at its parent institution and those targeted globally. For example, the following physicians (illustrated above) are relevant to an ECG located in the Heart Center: HC-0001 and HC-0002: Targeted specifically at the Heart Center MC-0001 and MC-0002: Targeted at the parent Main Campus facility TD-0001 and TD-0002: Targeted at the parent Tutorial Database Institution Global-0001: Applies to ALL institutions, facilities, and departments Importing Physician Data in CSV Format You can import existing physician data into the TraceMasterVue system in CSV format. Data must be in the following order and format. Column Data Type Length Comments PhysicianId uniqueidentifier 16 Automatically assigned by the database PhysicianNum nvarchar 64 NameLast nvarchar 40 NameFirst nvarchar 40 NameMiddle nvarchar Installing TraceMasterVue and Configuring Communication

181 Configuring the Physician List Column Data Type Length Comments InstitutionId uniqueidentifier 16 Default value if not known FFFFFFFF-FFFF-FFFF-FFFF- FFFFFFFFFFFF FacilityId uniqueidentifier 16 Default value if not known FFFFFFFF-FFFF-FFFF-FFFF- FFFFFFFFFFFF DepartmentId uniqueidentifier 16 Default value if not known FFFFFFFF-FFFF-FFFF-FFFF- FFFFFFFFFFFF nvarchar 256 FaxNumber nvarchar 30 FaxRecipient nvarchar 30 The following example shows two records in CSV format. {26A6D36C-65B7-4FCA-B30F-59C1F22D268F} Greenfield Frank {FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF} {FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF} {FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF} Greenfield Medical Group {D198B E-B71E-AE7501BE6DF1} Smith John Lee {53E1BD2F-166C FD-D9E83DC4C671} {F24D5A4C-EA59-4D82-B475-0BF4EB3FD0BC} {60A3FE13-18A B57B-20E9E30AF0DE} Dr. Smith Enterprises Manually Entering Physician Information Use the Physicians tab to enter each physician record. To add referring physician information 1 In the System Configuration utility, click the Physicians tab, then click Add. The Add Physician dialog box appears. Installing TraceMasterVue and Configuring Communication 7-21

182 Setting Up and Configuring TraceMasterVue System Options NOTE 2 Specify values for each of the fields. For details about each field, see Appendix C, TraceMasterVue Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. Note that the Physician ID field is required; the rest are not. However, if you do not specify a fax number or address, and then select a Referring Physician option in the Fax rule or rule dialog box, the ECG report will not be faxed or ed to the matching referring physician. For details about using the Referring Physician option in workflow rules, see Creating a Rule to or Fax ECGs to the Referring Physician on page Be sure to specify a valid address and/or fax number. 3 Click OK to add the physician to the system. The new entry appears in the Currently Defined Physicians list on the Physician tab. 4 To add more entries, click Add again and repeat until all entries are in. 5 Continue setting options. When done, you will click Finish and restart services Installing TraceMasterVue and Configuring Communication

183 Setting ECG Report Options Setting ECG Report Options Use the System Configuration utility Printed Reports tab to set report options. These settings affect how reports are printed both as a result of automated workflow rules that might be configured and from within the ECGVue application. Label Name Confirmed By label Confirmed On Behalf Of label Unconfirmed report label Previous label text STAT label text Confirmation date/time Description Specifies the text placed on a printed confirmed ECG report when electronic signature is enabled and the logged-in user is the confirming physician (as opposed to a user confirming on behalf of a physician). For example, typing the text Confirmed by in this field appears as follows on a printed confirmed ECG report when the logged-in user confirming the ECG is Dr. Cross. Confirmed by: Dr. Galen Cross NOTE The system automatically places a colon (:) after the label. Specifies the text placed on a printed ECG report that was confirmed by an authorized user on behalf of a confirming physician (as opposed to being confirmed directly by the confirming physician). For example, typing the text Confirmed for in this field appears as follows on a printed confirmed ECG report when the logged-in user, a Head Tech, is confirming the ECG on behalf of Dr. Cross. Confirmed for: Dr. Galen Cross NOTE The system automatically places a colon (:) after the label. The confirming user s ID is recorded in the Audit log. Specifies the text placed on a printed unconfirmed ECG report, for example, PRELIMINARY - MD MUST REVIEW. Specifies the text placed on the printed copy of the previous ECG when performing a serial comparison. Specifies the text placed on a printed STAT ECG. For example, typing STAT in this field appears as follows on the printed report: STAT Specifies whether to show the date and time the ECG was confirmed on the printed report. This option is currently not configurable and is always set to Shown. Installing TraceMasterVue and Configuring Communication 7-23

184 Setting Up and Configuring TraceMasterVue System Options Label Name Bar Codes on reports Create waveform grid lines for printed reports Create waveform grid lines for faxed reports Print statement codes Print reasons for unconfirmed reports TIFF Report Options These options are only available if you have purchased and installed the TIFF option at your site. Description Specifies whether to include bar codes on printed ECG reports. Options are: No barcodes On all reports On unconfirmed reports only Select the check box to print a grid behind the waveforms on printed ECG reports. If the check box is clear, no grid is printed. This option applies to reports printed as a result of a workflow rule. Select the check box to print a grid behind the waveforms on faxed ECG reports. If the check box is clear, no grid is included. This option applies to reports faxed as a result of a workflow rule. Select this check box to print interpretive statement codes for coded statements on the printed report. If the check box is clear, statements are printed without the associated code. Select this check box to print reasons (right-hand side statements) on printed unconfirmed reports. If the check box is clear, the reason portion of interpretive statements is not printed. Note that reasons are never printed on confirmed reports. Resolution. Define the resolution of the TIFF ECG report. Options are: 100x x200 (the default; this is the recommended resolution for faxing) 300x x600 Color Depth. Define whether the report is generated in color or black and white. Options are: 24-bit color Monochrome (b/w) Orientation. Specify whether the report is printed in Portrait (8.5 inches wide by 11 inches tall) or Landscape (11 inches wide by 8.5 inches tall) format. Print 12-Lead reports in Landscape format, Morphology reports in Portrait format Installing TraceMasterVue and Configuring Communication

185 Setting ECG Report Options To define report options 1 Double-click the System Configuration icon on the desktop. The System Configuration utility starts. 2 When prompted, type the TraceMasterVue administrator user ID and password. The Global tab of the System Configuration utility appears. 3 Click the Printed Reports tab. 4 Specify the field and label settings, as well as printing options, as appropriate for the site. 5 Continue setting options. When done, you will click Finish and restart services. Installing TraceMasterVue and Configuring Communication 7-25

186 Setting Up and Configuring TraceMasterVue System Options Configuring Inboxes Inboxes are containers to which ECGs are assigned. Depending on the workflow of a particular institution, inboxes might be set up for individuals or by function. Inboxes are associated with an ECG state and optionally, a location (institution/facility/department). Only users with access to the associated locations will be able to see the inbox and its contents. You associate inboxes with an ECG state, and, optionally, with a location and specified users or groups. Each of these options is described in the sections that follow. You define inboxes using the System Configuration utility Inbox tab. Before You Begin Before proceeding, collect the inbox information from the customer using the Inboxes worksheet (page 2-16). Defining Inboxes TIP To reduce the amount of that can be generated by specifying an address for each inbox, we suggest that you instead define a workflow rule that sends notification at set times during the day for assignments to specific inboxes. For details, see Adding Notification to a Rule on page To add an inbox 1 In the System Configuration utility, click the Inbox tab, then click Add. The Add/Edit Inbox dialog box appears. 2 Specify the name for the inbox and type (applicable ECG state). 3 (Optional) Select the location (institution, facility, and/or department) to associate with the inbox. Remember that only users with access to these locations will be able to retrieve and view ECGs that are assigned to this inbox. The exception to this rule is that users with ECG Manager or System Administrator privileges can retrieve and work with all ECGs regardless of inbox affiliation Installing TraceMasterVue and Configuring Communication

187 Configuring Inboxes 4 (Optional) Specify a specific user or a group of users to associate with the inbox. a b Click Select to specify a user or group to associate with the inbox. The Select User dialog box appears, which lists the users and groups that have been defined on, and have access to, the TraceMasterVue system (including within Active Directory). Groups are presented in a tree view; to view users within a group, click the + to the left of the group name to expand it and see the included users and groups. Select the user or group, then click OK. 5 When finished specifying options, click OK to add the inbox. NOTE The feature is not yet implemented. The new inbox is added to the system and displayed in Currently Defined Inboxes list. 6 Continue setting options. When done, you will click Finish and restart services. Installing TraceMasterVue and Configuring Communication 7-27

188 Setting Up and Configuring TraceMasterVue System Options Defining Automated Workflow Rules TraceMasterVue allows you to define rules that automate the handling and processing of ECGs. Each ECG that is stored in TraceMasterVue has a signature; that is, a defining set of characteristics that includes (among others) the acquiring location, source, and ECG type, as well as patient ID and ECG state. You can configure automated rules that perform certain actions on ECGs that match a specific signature profile. For additional information, see Defining Workflow Rules in Chapter 6, Setting ECG Viewing and Processing Options, in the TraceMasterVue System Configuration and Reference Guide. You create workflow rules in the System Configuration utility Workflow tab. When defining workflow rules, keep in mind the following: Several actions, including notification, printing, exporting, and faxing, can be performed as a batch at set times of the day. The rule is triggered on all of the matching ECGs that have accumulated in the queue by the specified time. Many of the Workflow dialog box dropdown lists offer, among other options, the value ALL. When ALL is selected, TraceMasterVue matches ECGs that have any value specified for the field. For example, if you set the ECG Source field to ALL, TraceMasterVue matches ECGs that have any value, including PageWriter Touch, M3700A, XLI, and so on, specified for this field. When including an address to a workflow rule, by default, the rule references the address specified in the From field in the dialog box (accessed from the Global tab). You can specify a different address if desired. Note, however, that if you later change the From address, these changes apply only to subsequent workflow rules; they do not ripple back through already defined rules. When you define a workflow rule that exports ECGs to a shared drive, you must first map the shared drive to a logical drive name, then specify the export path using that drive name. For an example, see Defining Workflow Rules in Chapter 6, Setting ECG Viewing and Processing Options, in the TraceMasterVue System Configuration and Reference Guide Installing TraceMasterVue and Configuring Communication

189 Defining Automated Workflow Rules Commonly Used Workflow Rules The following list shows some commonly used processes that you can automate by defining a rule: When an ECG enters the system, print the new ECG, as well as the previous ECG When an ECG enters the system, or fax it to the referring physician When an ECG is confirmed, print two copies so that one is sent to Billing When an ECG is confirmed, send it to a specific fax printer When an ECG is confirmed, it is also printed on a particular printer and exported to a specified location in a particular format If you are using OrderVue, upon confirmation, the ECG is exported to the Results queue Instructions for creating many of these types of rules are provided later in this chapter, starting with Defining Print, Fax, and Export Rules on page 7-31 Once you understand how to create workflow rules, the possibilities are as flexible as you need them to be. Before You Begin Before proceeding, collect the inbox information from the customer using the Workflow Rules worksheet (page 2-17). Defining a New Workflow Rule You can add new rules using either of two methods: Add a workflow rule from scratch Add a workflow rule using a template You can use an existing rule as a template for a new rule. This saves you a lot of time if you are creating a set of rules that have very similar signatures, but different outcomes. By default, workflow rules are displayed in the order created. It is easy to sort them in ascending or descending alphabetical order, however. Installing TraceMasterVue and Configuring Communication 7-29

190 Setting Up and Configuring TraceMasterVue System Options To define a new workflow rule 1 In the System Configuration utility click the Workflow tab, then click Add. The Add Workflow Rule dialog box appears. For a detailed description of all of the fields in the dialog box, see Appendix C, TraceMaster Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. 2 In the Signature section of the dialog box, specify the criteria for the ECGs that will be affected by this rule. For example, to affect only ECGs for a particular patient, select the patient ID from the Patient ID dropdown list. 3 In the Action dropdown list, select the action that will trigger this rule. For example: If you are defining a rule that prints ECGs upon confirmation, select Confirm. If you are defining a rule that assigns compared ECGs to a particular inbox, select Compare. If you are defining a rule to notify a user of an ECG assignment, select Assign Installing TraceMasterVue and Configuring Communication

191 Defining Automated Workflow Rules 4 In the Rules section of the dialog box, select the action to perform on ECGs that match the criteria. For example, to print matching ECGs, select Print, and specify the print settings. To export ECGs, select Export and specify export format and destination. 5 When finished, click OK. The new rule appears in the Currently defined rules list. You can continue adding rules, as needed. 6 Continue setting options. When done, you will click Finish and restart services. To define a new rule using an existing rule as a template To make it easier to find a particular rule to use as a template, sort the list by any column by clicking the column heading. 1 On the Workflow tab, select the rule (in the Currently defined rules list) to use as a template for the new rule and click Replicate. The Add Workflow Rule dialog box appears displaying all of the values specified for the selected rule. 2 Change the settings in the Signature, Action, and Rules sections, and click OK. The new rule is added to the system and displayed in the Currently Defined Rules list. 3 Continue setting options. When done, you will click Finish and restart services. Defining Print, Fax, and Export Rules You can create an automated rule that directs the TraceMasterVue system to print, fax, and/or export an ECG when a specific action occurs with ECGs that match certain criteria. The following sections describe how to define automated workflow rules to Print newly acquired ECGs Print and export an ECG upon confirmation Configuring a fax rule is similar to these actions and is not illustrated here. Installing TraceMasterVue and Configuring Communication 7-31

192 Setting Up and Configuring TraceMasterVue System Options Creating a Rule to Print Newly Acquired ECGs A commonly performed action is to print ECGs when they enter the system or are confirmed. This section shows you how to define an automated workflow rule to print new ECGs. NOTE You can specify print options for any automated rule you define, and can change these options at any time. To print new ECGs 1 In the Signature section of the Workflow Rules dialog box, specify the criteria to match. In the State dropdown list, select New. 2 In the Action list, select Store. 3 After specifying the criteria of ECGs to print, select the Print check box in the Rules section of the Add/Edit Workflow Rule dialog box. The Add/Edit Print Rules dialog box appears. 4 Specify the print settings, including the printer to print to and the number of reports to print. To print the previous ECG as well, select the Print Previous ECG check box. The specified number of reports to print applies to the previous ECG, as well. 5 To print reports at specified times of the day, select the Batch check box. The Add, Edit, and Remove buttons become enabled, allowing you to specify the times at which to send accumulated messages. a b c d To add a new time, click Add, and specify the time at which to send messages. To change an existing time, select the time in the list and click Edit. Then specify the new time. To delete an existing time, select the time in the list and click Remove. Click OK to save your changes. 6 When finished setting up the full rule, click OK in the Workflow Rules dialog box Installing TraceMasterVue and Configuring Communication

193 Defining Automated Workflow Rules Creating a Rule to or Fax ECGs to the Referring Physician The following procedures use the example of ing or faxing a newly acquired ECG to the ECG referring physician, although the procedure is essentially the same regardless of the action (specified in step 2) that triggers the ing or faxing of the ECG. To a new ECG to the referring physician 1 In the Signature section of the Workflow Rules dialog box, specify the criteria to match. In the State dropdown list, select New. 2 In the Action dropdown list, select Store. 3 After specifying the criteria of ECGs to , click the check box. The Add Rule dialog box appears. 4 Specify the address(es) to send notification to, separated by a comma. To only send the ECG to the referring physician, skip this step and proceed to the next one. NOTE The referring physician associated with the ECG must be defined on the TraceMasterVue system. Verify that the physician is listed on the Physician tab, and that a valid address is specified for that entry. 5 To send the ECG to the referring physician, click the appropriate Also to Ordering or Referring Physician check box. You can include the referring physician with or without specifying additional addresses. 6 To send accumulated messages at specified times of the day, select the Batch check box. The Add, Edit, and Remove buttons become enabled, allowing you to specify the times at which to send accumulated messages. a b c To add a new time, click Add, and specify the time at which to send messages. To change an existing time, select the time in the list and click Edit. Then specify the new time. To delete an existing time, select the time in the list and click Remove. Installing TraceMasterVue and Configuring Communication 7-33

194 Setting Up and Configuring TraceMasterVue System Options d Click OK to save your changes. 7 Click OK in the Workflow Rules dialog box to save your changes. To create a rule to fax a new ECG to the referring physician 1 In the Signature section of the Workflow Rules dialog box, specify the criteria to match. In the State dropdown list, select New. 2 In the Action list, select Store. 3 After specifying the criteria of ECGs to , click the Fax check box. The Add Fax Rule dialog box appears. 4 Click the Ordering or Referring Physician radio button to fax the ECG to the referring physician associated with the ECG. NOTE The referring physician associated with the ECG must be defined on the TraceMasterVue system. Verify that the physician is listed on the Physician tab, and that a valid fax number is specified for that entry. 5 Specify the fax settings, including whether to include a cover sheet. To fax the previous ECG as well, select the Fax previous ECG check box. 6 To fax reports at specified times of the day, select the Batch check box. The Add, Edit, and Remove buttons become enabled, allowing you to specify the times at which to send accumulated messages. a b c d To add a new time, click Add, and specify the time at which to send messages. To change an existing time, select the time in the list and click Edit. Then specify the new time. To delete an existing time, select the time in the list and click Remove. Click OK to save your changes Installing TraceMasterVue and Configuring Communication

195 Defining Automated Workflow Rules 7 When finished setting up the full rule, click OK in the Workflow Rules dialog box. Creating a Rule to Print and Export Confirmed ECGs To print and export confirmed ECGs For details about exporting ECGs, see Exporting ECGS in Chapter 9, Data Communication and Management, in the TraceMasterVue System Configuration and Reference Guide. 1 In the Signature section of the Workflow Rules dialog box, specify the criteria to match. 2 In the Action dropdown list, select Confirm. 3 After specifying the criteria of ECGs to print, select the Print check box in the Rules section of the Add/Edit Workflow Rule dialog box. The Add/Edit Print Rules dialog box appears. 4 Specify the print settings, including the printer to print to. To print the previous ECG as well, select the Print Previous ECG check box. 5 Select the Export check box. The Add Export Rule dialog box appears. a Select the export format. b Select the destination. Options are queue or directory. c Click OK to save your changes. 6 When finished setting up the full rule, click OK in the Workflow Rules dialog box. NOTE Adding Notification to a Rule You can create an automated rule that directs the TraceMasterVue system to send an when a specific action occurs with ECGs that match certain criteria. The 12-Lead ECG report is always attached to the . If you have the TIFF option, the attachment is sent in TIF format. If you have the PDF option, the attachment is always sent in PDF, even if you have the TIFF option. For example, you can have the system send you when ECGs are assigned to a specific inbox, when EASI ECGs are imported into the database, or when ECGs for a particular patient or department are confirmed. You can also add notification to any automated rule you define. You can change the specified addresses at any time. Installing TraceMasterVue and Configuring Communication 7-35

196 Setting Up and Configuring TraceMasterVue System Options TIP To avoid receiving every time a rule is triggered, we suggest that you choose the Batch option, which accumulates notification messages and sends them at set times during the day. To add notification to a rule 1 On the Workflow tab, in the Currently Defined Rules list, select the rule to add notification to, and click Edit. The Edit Workflow Rules dialog box appears. 2 Select the check box in the Rules section of the dialog box. The Add/Edit Rules dialog box appears. The From field is automatically filled in with the address specified in the Global tab Settings dialog box. 3 In the To, CC, and or BCC fields, specify the address(es) to send notification to, separated by a comma. You can change the From field, if necessary, unless the Always use this as From address check box is selected in the Global tab Settings dialog box. If it is selected, this field is read-only and cannot be modified. If it must be changed, first deselect the check box on the Global tab and then return to this dialog box and make the necessary edits. 4 Click the Also to Ordering or Referring Physician check box to send the ECG to the referring physician associated with the ECG. NOTE The referring physician associated with the ECG must be defined on the TraceMasterVue system. Verify that the physician is listed on the Physician tab, and that a valid address is specified for that entry Installing TraceMasterVue and Configuring Communication

197 Defining Automated Workflow Rules 5 To send accumulated messages at specified times of the day, select the Batch check box. The Add, Edit, and Remove buttons become enabled, allowing you to specify the times at which to send accumulated messages. a b c d To add a new time, click Add, and specify the time at which to send messages. To change an existing time, select the time in the list and click Edit. Then specify the new time. To delete an existing time, select the time in the list and click Remove. Click OK to save your changes. 6 Click OK in the Workflow Rules dialog box to save your changes. Installing TraceMasterVue and Configuring Communication 7-37

198 Setting Up and Configuring TraceMasterVue System Options Defining Aliases and Custom Statements The Statement Manager allows you to customize codes, severities, and interpretive statements. The TraceMasterVue system allows you to define an unlimited number of your own custom supplementary uncoded interpretive statements and modifiers, as well as Dx, Hx, Sx, DRG, and Rx codes. For details, see Appendix C, About Custom Statements and Aliases. In addition to defining custom statements and codes, you can also map codes and statements in a selected criteria version (for example, 0A) to your own site-specific nomenclature, or aliases. For details, see Appendix C, About Custom Statements and Aliases. Aliases and custom statements are associated with a specific criteria version (selected on the Statement Set tab), and are available for use in the client application when that criteria version is enabled. Before You Begin Before proceeding, ensure you have read Appendix C, About Custom Statements and Aliases. Using Statement Aliases Using aliases is a two step process: Enable code/statement aliasing using the System Configuration utility Define code/statement aliases using the Statement Manager utility Enabling Statement Aliasing Aliasing can be enabled and available, or disabled. Note that you enable aliasing using the System Configuration utility Global tab, and define aliases using the Statement Manager. For details, see Defining Statement Aliases on page To enable statement aliasing 1 On the System Configuration utility Global tab, select either or both of the check boxes in the Statement Aliasing section. Select Code Alias to mapping your own statement codes to defined codes. Select LHS Alias to map the text associated with a coded statement to defined statements. Select both to allow mapping of both the code and the statement text Installing TraceMasterVue and Configuring Communication

199 Defining Aliases and Custom Statements 2 Continue setting options. When done, you will click Finish and restart services. When users are reviewing and editing ECGs that are using a criteria version for which aliases have been defined, those aliases are available for use. To disable statement aliasing 1 On the System Configuration utility Global tab, clear either or both of the check boxes in the Statement Aliasing section. 2 Continue setting options. When done, you will click Finish and restart services. Any defined aliases will not be available to the user when these options are disabled. Defining Statement Aliases Use the Statement Manager utility to define code and/or statement aliases for a specific criteria version. Note that you must also enable the use of aliases in the System Configuration utility, on the Global tab, as described on the previous page. To define statement aliases 1 Launch the Statement Manager utility, and log in. 2 On the Statement Set tab, specify the criteria version to work with. 3 Click the Statement tab. 4 Scroll through the list and select a statement for which to define an alias, then click Edit. To sort the list of statements so you can quickly find the statement to alias, click the column heading by which to sort. In general, you will most likely sort by Code. For example, click Code to sort the list by code in alphabetical order. Click it again to reverse the order from ascending to descending, and vice versa. NOTE You cannot specify an alias for a new custom statement that you add to the system. It is unlikely that you will need an alias for a custom statement. The Edit Statement dialog box appears. Installing TraceMasterVue and Configuring Communication 7-39

200 Setting Up and Configuring TraceMasterVue System Options 5 Type the code (in the Code Alias field) and/or statement alias (in the LHS Alias field) to use for the selected criteria-defined statement, then click Save. 6 Repeat steps 4 and 5 for each statement for which to define an alias. 7 Continue setting options. When done, you will click Finish and restart services. Configuring Custom Modifiers, Codes, and Statements You configure custom modifiers and codes using the Statement Manager Rx, Sx, Hx, Dx, Race, and DRG tabs, as described in Configuring Custom Modifiers and Codes, below. Create custom statements using the Statements tab as described in Configuring Custom Statements on page Configuring Custom Modifiers and Codes The procedure for adding, editing, and deleting modifiers, severities, and codes (Rx, Sx, Hx, Dx, Race, and DRG) is essentially the same. This section describes how to add, edit, and delete various items. NOTE You can only edit items that you have previously added to the system. Factory-defined entries cannot be edited or deleted. To add custom values 1 Display the tab for the item to add. For example, click the Race tab to add custom race codes. 2 Click Add. The Add/Edit <Item> dialog box appears. 3 Specify a code for the new entry, an abbreviated name for the entry, and the full name for the item. 4 Click OK. The new item is added to the bottom of the Currently Defined list. 5 Continue setting options. When done, you will click Finish and restart services Installing TraceMasterVue and Configuring Communication

201 Defining Aliases and Custom Statements Configuring Custom Statements The statement, as it appears formatted for reading, consists of modifiers, followed by the text of the LHS, with appropriate substitution of variable values. The printed statement may include the RHS, although it does not appear in the on-screen version of the report (in ECGVue).The RHS is shown in Statement view when the RHS includes editable variables. Use the Statement Manager Statements tab to define custom coded and quality statements at your site. For details about the fields on this tab, as well as the Add/Edit Statement dialog box, see About the Statement Manager Tabs on page C-49. You can also choose to define a statement or code alias for factory-defined statements. There are situations in which this approach might be preferable. For details, see Appendix C, About Custom Statements and Aliases. To add custom statements 1 Click the Statements tab. 2 Click Add. The Add Custom Statement dialog box appears. For details about the fields, see Appendix C, TraceMasterVue Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. 3 Specify the desired statement values, including whether the new statement is a quality or coded statement, the code, description, optional modifiers, and so on. For a detailed description of the fields, see the Statement Manager online help. 4 Click OK. The statement is added to the bottom of the Currently Defined Statements list. 5 Continue setting options. When done, you will click Finish and restart services. Installing TraceMasterVue and Configuring Communication 7-41

202 Setting Up and Configuring TraceMasterVue System Options Enabling Settings After you set all the options described in this chapter, you must stop and restart TraceMasterVue services (in the System Monitor utility), as well as stop and restart IIS, to enable those changes in the system. In some cases, for example when adding custom statements to the system, you must also flush the cache on individual client systems (in ECGVue or PharmaVue) to be able to immediately access the new entries. Before proceeding, read the section, Enabling System Option Changes on page To enable system settings Perform the following steps: Starting and Stopping TraceMasterVue on page 6-29 Stopping and Restarting IIS on page 6-30 Resetting the Application Cache on page 6-31 Proceed to the next section, below. Completing TraceMasterVue Communication Configuration TIP Whenever you make a configuration change using the System Configuration utility, you must stop and restart TraceMasterVue services for the changes to take effect. The procedure for doing so is included here for your convenience. However, after adding and configuring modems and making the changes described in this guide to the TraceMasterVue system using the System Configuration utility, you must reboot the TraceMasterVue server. Before proceeding, connect and configure all communication devices on the TraceMasterVue end. That is, make sure all of the ports you will use for cardiograph/fax/remote support communication are configured, and all the modems, LAN cables, or direct connection cables are connected. By doing so, you will only have to reboot the server once. To complete TraceMasterVue communication configuration Reboot the TraceMasterVue server. When the server restarts, all services are also restarted, and the system is ready to go. You can now connect and configure the cardiographs that will interact with the TraceMasterVue system Installing TraceMasterVue and Configuring Communication

203 Installing ECGVue/PharmaVue on Client Systems Installing ECGVue/PharmaVue on Client Systems The client system must be running Windows XP Pro SP2 or Windows 2000 Pro SP4, or Windows 2003 Server SP 2, and must have network access to the TraceMasterVue server. NOTE If upgrading to a newer version of ECGVue/PharmaVue, uninstall the previous version first. To uninstall ECGVue 1 Launch Internet Explorer. 2 Specify the following URL: of TraceMasterVue server>/emsclient/welcome.aspx The Install/Remove page appears. 3 Click Remove Client. 4 Follow the steps presented in the Wizard to remove the application. To install ECGVue/PharmaVue on a client system 1 Launch Internet Explorer. 2 Specify the following URL: of TraceMasterVue server>/emsclient/welcome.aspx The Install/Remove page appears. 3 Click Install Client. The Setup page appears, where you select which application to install. 4 Select the check box for ECGVue Application, and click Begin. 5 Follow the steps presented in the Wizard, clicking Yes at all prompts. The installer installs the.net runtime on the client system, and places the ECGVue/ PharmaVue icon on the desktop. The icon is labeled TM Client Application. 6 Double-click the TM Client Application icon. The Login screen appears. By default, the Domain field is set to the name of the system on which you are installing ECGVue/. Installing TraceMasterVue and Configuring Communication 7-43

204 Setting Up and Configuring TraceMasterVue System Options 7 Set the Domain field to the name of the domain of either the TraceMasterVue server or the domain on which the user account is defined (the domain controller), if different. NOTE You only have to perform this step the first time you run ECGVue/ on this system. On subsequent logins, the new domain name appears in this field. 8 Type a valid user ID and password to start using ECGVue/. NOTE When a user logs into the application, the system checks the age of the cache. If it is older than 24 hours, the system automatically flushes the cache. You can also manually flush the cache as described in the TraceMasterVue System Configuration and Reference Guide. For detailed information about using the application, refer to the online help and to the ECGVue Instructions for Use. Installing the Report Manager on Client Systems The client system must be running Windows XP, and must have network access to the TraceMasterVue server. NOTE The Report Manager application can only be run on a client running the Windows XP operating system; it cannot be run on a remote client running Windows To install the Report Manager application on a client system 1 Launch Internet Explorer. 2 Specify the following URL: of TraceMasterVue server>/emsclient/welcome.aspx For example, The Install/Remove page appears. 3 Click Install. The Setup page appears, where you select the application to install. 4 Select the check box for Management Reports Application, and click Begin Installing TraceMasterVue and Configuring Communication

205 Installing the Report Manager on Client Systems NOTE 5 Follow the steps presented in the Wizard, clicking Yes at all prompts. The installer installs the.net runtime on the client system, and places the Reports Manager icon on the desktop. The icon is labeled TM Management Reports. 6 Double-click the TM Management Reports icon. The Login screen appears. By default, the Domain field is set to the name of the system on which you are installing the application. 7 Set the Domain field to the name of the domain of either the TraceMasterVue server or the domain on which the user account is defined (the domain controller), if different. You only have to perform this step the first time you run the application on this system. On subsequent logins, the new domain name appears in this field. 8 Type a valid user ID and password to start using the Report Manager. Verifying that the System Works Perform the following tests to ensure that the system is configured properly. Test Block Name Test or Inspection to Perform Expected (Passing) Test Results Data to Record x=p (pass) or F (fail) Problem Duplication If performance verification is following servicing, attempt to duplicate reported problem. Unable to duplicate problem Problem: x PC Test Server CPU Verify the TraceMasterVue services were properly configured and installed. 1 Double-click the System Monitor icon. All of the check boxes show a green check mark, showing that all services and entries were properly installed. PC: x 2 In the View menu, select System Report. 3 Click Run Self-Test. 4 Click Start. Display Test Inspect the TraceMasterVue display; assess ability to read characters. Display characters are in focus and easy to read. Display: x Ensure resolution is set to a minimum of 800x600; 1024x768 recommended. Installing TraceMasterVue and Configuring Communication 7-45

206 Setting Up and Configuring TraceMasterVue System Options Test Block Name Test or Inspection to Perform Expected (Passing) Test Results Data to Record x=p (pass) or F (fail) Keyboard Test Start a command prompt or open a new text file. Press each key on the keyboard. With each key press, the corresponding character appears on the display. Keyboard: x Mouse Test Move the mouse around on a flat surface to several points on the display. Mouse arrow appears on the display and reacts appropriately. Mouse: x Printer Test Print an ECG stored in ECGVue/PharmaVue. Text report printed in landscape mode. Printer: x 1 Log into ECGVue/ PharmaVue. 2 Do a quick search for unconfirmed ECGs for the last 3 years. 3 Select an entry and click Print. 4 Select 12 lead as the report type and click OK. Bar codes printed in lower right side of report. (Ensure that printing barcodes is enabled. See Setting ECG Report Options on page 7-23.) Appropriate number of channels displayed. Printout clean; no smudged toner. 5 Keep the printed report for use in the next test. Bar codes print NOTE If customer does not use bar codes, skip this test. Verify that bar codes print on reports. Check that the bar code printed on the report you already printed for the Print test. The ECG reports should have a bar code along the right side of the report. Barcode: x If no bar code was printed on the report, verify that printing bar codes is enabled on the Printed Reports tab of the System Configuration utility. See Setting ECG Report Options on page Installing TraceMasterVue and Configuring Communication

207 Setting Up System and File Backups Test Block Name Test or Inspection to Perform Expected (Passing) Test Results Data to Record x=p (pass) or F (fail) Bar Code Wand Ensure the wand scans barcodes appropriately. 1 Log into TraceMasterVue. The ECG in the print out is shown on the monitor. Barcode: x NOTE If customer does not use bar codes, skip this test. 2 Click Barcode in the Action bar. 3 Run the wand across the bar code printed (in the previous step) on the ECG report. Setting Up System and File Backups It is a good idea to help the customer put a backup system in place during system setup. If the customer does not have a third party backup solution, refer to Chapter 11, Backing Up and Restoring System and Database Files in the TraceMasterVue System Configuration and Reference Guide for a detailed guide to setting up Windows-based backup. Configuring Cardiographs to Communicate with TraceMasterVue After configuring data communication on the TraceMasterVue end (both in terms of connecting and setting up hardware, and configuring settings on the server), you are now ready to connect and configure cardiographs. In addition, if you wish to use interactive query, you must also configure that functionality on the cardiographs. Refer to the chapters that follow for detailed information about configuring PageWriterTouch, PageWriter Trim, and legacy PageWriter XLi/200/300 cardiographs. Installing TraceMasterVue and Configuring Communication 7-47

208 Setting Up and Configuring TraceMasterVue System Options 7-48 Installing TraceMasterVue and Configuring Communication

209 Chapter 8Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 8 After configuring data communication on the TraceMasterVue end (both in terms of connecting and setting up hardware, and configuring settings on the server), you are now ready to connect and configure cardiographs. In addition, if you wish to use interactive query, you must also configure that functionality on the cardiographs. Before proceeding, ensure that you have configured the communication hardware and connections on the TraceMasterVue end first, as described in Chapters 1 through 7. This chapter provides the following information: About PageWriter Touch Cardiograph Software Versions Configuring OrderVue Settings on the PageWriter Touch Cardiograph Configuring Multiple Cardiographs Configuration Steps Connecting Communication Hardware to the PageWriter Touch Cardiograph8-3 LAN Network Connection Wireless LAN Connection Wireless Connectivity Indicators Modem Connection About Network Settings Networking Overview DHCP Fixed IP Address Auto Negotiation Device IP Address Ping Test Configuring Cardiograph Network Settings About Wired Ethernet and Wireless LAN Connectivity Using DHCP Configuring Remote Site Settings Configuring a Remote Site Network or a Remote Access Server (RAS) Connection with Modem Remote Site Security Feature Testing TraceMasterVue Remote Site Connectivity Editing Remote Site Settings Defining Institution Settings Special Note about Location Code (LOC)

210 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Patient ID Settings Patient ID Configuration Options Configuring Patient Information Configuring Clinical Information Configuring Order Information Configuring Additional Information Configuring Optional, User Defined Patient ID fields Configuring the User Defined Fields with OrderVue Configuring the User Defined Fields for FDA XML Export Patient ID Layout Settings Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Troubleshooting a Wired Connection Using Ping to Verify TraceMasterVue Server to PageWriter Touch Cardiograph Connectivity Troubleshooting a Wireless Connection Checking the Remote Site Server Connection Resolving an Unexplained Reply Received from the Remote Site Checking the Wireless Adapter Association to an Access Point About PageWriter Touch Cardiograph Software Versions NOTE This chapter describes configuration of the PageWriter Touch cardiograph with installed software version B.01 for use with TraceMasterVue. Instructions for configuring TraceMasterVue settings on the PageWriter Touch cardiograph with installed software version C.01 are not included in this document. Software version C.01 supports ECG data acquisition for up to 16 leads for both adult and pediatric application. For information on configuring TraceMasterVue and other networking settings with software version C.01, see the PageWriter Touch Cardiograph Instructions for Use, part number M , Edition 7. This document will be available for download from the InCenter site as of June, Configuring OrderVue Settings on the PageWriter Touch Cardiograph For information on configuring settings used with the OrderVue order management software that resides on the TraceMasterVue ECG Management System, see the Using OrderVue with PageWriter Cardiographs Instructions for Use, available in the OrderVue or PageWriter Touch User Documentation CD, or download the file from the InCenter site. Information on configuring OrderVue settings with installed software version C.01 will be available from the InCenter site as of June, Installing TraceMasterVue and Configuring Communication

211 Configuring Multiple Cardiographs Configuring Multiple Cardiographs When configuring multiple cardiographs with the same TraceMasterVue settings, you can save all settings to a PC card, diskette, or to a USB memory stick, and then upload them to additional cardiographs. We recommend that all cardiograph settings included in this chapter and in Chapter 3 of the PageWriter Touch Cardiograph Instructions for Use be configured on the cardiograph before saving the settings as a custom settings file. For information on creating a custom settings file, see Saving Custom Settings on page 3-40 of the PageWriter Touch Cardiograph Instructions for Use. NOTE Wireless LAN card settings specified in the Aironet Client Utility (ACU) are saved with the configuration settings file. Configuration Steps NOTE Perform the following steps, in order, to configure the cardiographs for communication with TraceMasterVue: 1 Connect the communication hardware, either LAN or modem. 2 Configure cardiograph network or modem settings.test network connectivity. 3 Configure Remote Site settings. Test Remote Site connectivity. 4 Configure the cardiograph location information. 5 Configure Patient ID settings including any optional user-defined fields. The following procedures are provided here for your convenience. If necessary, refer to the cardiograph documentation for the most up-to-date information on configuring settings. Before proceeding, have available the completed worksheets found in Chapter 2, TraceMasterVue Communication Worksheets. They contain all the network settings, location information, user name, and other information required for configuration. Connecting Communication Hardware to the PageWriter Touch Cardiograph Before proceeding, ensure you have connected all the hardware to, and configured, the TraceMasterVue system. For details, see the Chapter 1 to 7 in this guide. PageWriter Touch cardiographs can communicate with TraceMasterVue either using a local area connection (LAN) or over a modem, using RAS. The cardiograph uses a PC card modem that supports printing to Group 3 Fax machines, as well as the Class 1 and 2 Fax modem protocol (USA and Canada only). For additional details about PC card modems, refer to the PageWriter Touch Instructions for Use. Installing TraceMasterVue and Configuring Communication 8-3

212 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue LAN Network Connection To connect the cardiograph to the LAN Insert the LAN cable connector into the network port on the back of the cardiograph. Network port on rear panel of cardiograph Wireless LAN Connection The PageWriter Touch cardiograph supports the Cisco Aironet Wireless LAN card and is compatible with the b wireless standard. The Cisco Aironet Client Utility (ACU) driver is included in the PageWriter Touch cardiograph software. The wireless adapter may be configured to support the following security options. PageWriter Touch Wireless Adapter Setting No Security Static WEP Access Point Setting No Security WEP with Static Keys LEAP LEAP and WEP LEAP and WEP with Per Packet Keying For more detailed information on wireless security options and features, see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE available for download from To install and configure the wireless LAN card 1 Ensure that the cardiograph is in Standby mode. If the cardiograph is not in Standby mode, press the On/Standby button on the front of the cardiograph. 2 Insert the wireless LAN card into the PC Card slot on the rear of the cardiograph. Ensure that the card is fully inserted into the slot. 8-4 Installing TraceMasterVue and Configuring Communication

213 Connecting Communication Hardware to the PageWriter Touch Cardiograph NOTE Only insert the wireless LAN card when the cardiograph is in Standby mode or the card will not be recognized by the cardiograph. The green Status indicator on the front of the card illuminates when the card is properly inserted. A B A Red activity indicator B Green status indicator 3 Press the On/Standby button. 4 Touch the Config button on the Command Toolbar. 5 Touch the Defaults button. A series of tabs appear at the top of the screen. 6 Touch the Network tab. The network configuration screen appears. 7 Touch the Wireless Network tab (top right of screen). 8 Under Wireless Adapter (bottom right of screen) touch the Configure button. The Cisco License Agreement appears. Installing TraceMasterVue and Configuring Communication 8-5

214 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 9 Agree to the terms of the license and touch OK. The Aironet Client Utility window appears. The Profiles tab is selected. 10 Press the Tab key on the keyboard until the Edit button is highlighted. 11 Press the Enter key on the keyboard. The profile properties window appears. Specify the wireless network settings applicable for your facility, described in the following table. Setting Description Philips Recommended Default Setting SSID The Service Set Identifier Consult your network administrator for more information on this setting. NOTE If the SSID field is left blank, the cardiograph can associate with any access point on the network that is configured to accept broadcast SSIDs. Client Name Infrastructure Mode Defining a name for the specific cardiograph enables an administrator to determine what devices are connected to the network. The client name is limited to 16 characters in length. This setting specifies the type of network in which the cardiograph is being installed. Consult your network administrator for more information on this setting. Yes NOTE The PageWriter Touch cardiograph does not support ad hoc or peer-to-peer communication. 8-6 Installing TraceMasterVue and Configuring Communication

215 Connecting Communication Hardware to the PageWriter Touch Cardiograph Setting Description Philips Recommended Default Setting Power Save Mode Network Security Type This setting defines the power consumption level for the wireless adapter. This setting specifies the type of b authentication that the wireless adapter will use. Fast PSP (Power Save Mode) NOTES Fast PSP is a power saving mode that automatically adjusts battery consumption based upon the amount of network traffic. For example, during periods of low network activity, less power is consumed. CAM (Constantly Awake Mode) is not recommended for use due to high power consumption. The Max PSP (Max Power Savings) setting is not recommended due to the low level of data throughput. For more information see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE. None or LEAP Consult your network administrator for more information on this setting. NOTE The PageWriter Touch cardiograph does not support EAP- FAST authentication. Installing TraceMasterVue and Configuring Communication 8-7

216 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Setting Description Philips Recommended Default Setting WEP Authentication Type User Name User Password User Domain Mixed Mode This setting specifies the type of Wired Equivalency Privacy (WEP) that the wireless adapter will use. This setting defines how the wireless adapter will attempt to authenticate to an access point. This setting is only used with LEAP. This setting is only used with LEAP. This setting is only used with LEAP. This setting indicates if the wireless adapter can associate to an access point that allows both WEP and non-wep associations. None or Static WEP Consult your network administrator for more information on this setting. NOTES The wireless adapter allows up to four static WEP keys with 40-bit or 128-bit encryption. The PageWriter Touch cardiograph does not support dynamic WEP keys. If multiple static WEP keys are being used, the transmit key must be configured as the first WEP key. On the access point, the first WEP key must match the first key on the wireless adapter. The index of the WEP transmit key must match the index of the client adapter. For example, the first WEP key on the access point must match the first key on the wireless adapter. Open Consult your network administrator for more information on this setting. Consult your network administrator for more information on this setting. Consult your network administrator for more information on this setting. Consult your network administrator for more information on this setting. 8-8 Installing TraceMasterVue and Configuring Communication

217 Connecting Communication Hardware to the PageWriter Touch Cardiograph Setting Description Philips Recommended Default Setting World Mode Data Rate Transmit Power Offline Channel Scan This setting allows the wireless adapter to automatically adjust to the maximum power level and frequency range of access points in different regions of the world. This setting specifies the rate at which the wireless adapter should transmit or receive packets to or from the access point. This setting defines the power level at which the wireless adapter transmits to the access point. This setting enables the wireless adapter to periodically scan for a better access point with the same SSID if the signal strength falls below 50%. Disabled NOTE For more information on this setting, see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE. Auto Max Enabled 12 After making all selections, touch OK (upper right corner of window). All of the configured settings are automatically saved to a profile. The cardiograph automatically restarts. The new wireless settings are applied and are saved to the profile named PageWriter_Touch in the Aironet Client Utility. This profile is automatically selected as the active profile in the Select Active Profile drop-down list in the Aironet Client Utility. Installing TraceMasterVue and Configuring Communication 8-9

218 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Wireless Connectivity Indicators There status of the wireless LAN connection displays on the Status Bar of any cardiograph software screen. Or, there are LED indicators located on the wireless LAN card that indicate the current wireless LAN connectivity status. Figure 8-2 Wireless LAN Connectivity Status Icons on Status Bar A A Wireless LAN Connectivity Status Icon on the Status Bar Table 8-3 Icon Wireless LAN Connectivity Status Icons on Status Bar Description Indicates the signal strength of a the wireless LAN connection. Green bars indicate that the wireless adapter is associated to an access point. The higher the number of green bars, the better the connection. Red bars indicate that the cardiograph is losing the wireless LAN signal and that the cardiograph should be moved to an area with a stronger signal. A red x indicates that the wireless adapter is unable to associate to an access point. Table 8-4 Wireless Adapter LED Indicators Green LED Status Amber LED Status What LEDs indicate Blinking quickly (every 0.5 seconds) Blinking quickly Wireless adapter is not associated to an access point. Off Blinking quickly Wireless adapter is associated to an access point (with Power Save Mode set to default Fast PSP) Off Off Wireless adapter is not receiving power, or an error has occurred Installing TraceMasterVue and Configuring Communication

219 Connecting Communication Hardware to the PageWriter Touch Cardiograph Table 8-4 Wireless Adapter LED Indicators (continued) Green LED Status Amber LED Status What LEDs indicate Blinking slowly (every 1.5 seconds) Blinking quickly Wireless adapter is associate to an access point (with Power Save Mode set to CAM; not recommended due to increased power consumption). Proceed to the following sections to continue the configuration process. For information on troubleshooting a wireless connection, Troubleshooting a Wireless Connection on page Modem Connection To connect the cardiograph using a modem connection WARNING Do not connect the modem card to a phone line when the cardiograph is connected to a patient. 1 Insert the PC card modem into the card slot in the back of the cardiograph and gently push it in. PC card slot PC card Eject button 2 Insert the PC card end of the cable into the phone connector on the PC card. 3 Insert the other end of the cable into the modem port used for communication with TraceMasterVue. You are now ready to configure network and TraceMasterVue Remote Site settings on the cardiograph, including defining locations and any needed user fields, as well as specifying settings to use the modem connection. Connection configuration consists of setting up a remote site and configuring the modem settings. Installing TraceMasterVue and Configuring Communication 8-11

220 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue About Network Settings The settings described in this section include the network protocol settings used with the wired or wireless network LAN connection. The network settings on the cardiograph support TCP/IP protocol using a static IP address, dynamic IP address, or a DNS or WINS server. The network settings also allow for specifying Ethernet data transmission settings. This setting can be specified to Auto Negotiation (default setting), or to a manual transmission rate setting with Full or Half Duplex. See Auto Negotiation on page 8-12 for more information on data transmission rates and the PageWriter Touch cardiograph. Networking Overview The PageWriter Touch cardiograph communicates with the TraceMasterVue ECG Management System using a wired or wireless network connection, or a modem connection. In the cardiograph network configuration settings, all TCP/IP settings are configurable based on the specific needs of the clinical environment. Both DHCP (Dynamic Host Configuration Protocol) and fixed IP (Internet Protocol) address settings are available. DHCP With DHCP, the LAN automatically provides a dynamic IP address to the cardiograph. The LAN records the unique MAC (Media Access Control) address of the cardiograph and provides a temporary DHCP IP address. Fixed IP Address Fixed IP addresses allow the cardiograph to be recognized throughout a network. With a fixed IP address, the cardiograph will be recognized at multiple locations throughout a LAN, and will not require that the IP address be reset in order to be recognized. Using fixed IP addresses will also avoid the problem of having multiple IP addresses assigned to a single cardiograph. Auto Negotiation When the cardiograph is connected to a LAN using Auto Negotiation, it automatically configures the correct settings for Ethernet speed and mode (half or full duplex). If the autonegotiation fails, it may be necessary to lock a specific switch or router port to a fixed setting (for example, 100BaseT Full Duplex) in order to obtain a connection. Issues with the timing of the PageWriter Touch Auto Negotiation have been reported with certain CISCO switches (such as the CISCO 4506). To obtain a LAN connection with these switches, the specific LAN port and the port on the PageWriter Touch cardiograph may have to be locked down with fixed Ethernet port settings using the Ethernet Adapter settings available on the Network configuration screen. The cardiograph should only be connected to these locked down ports. For more information on networking options or to troubleshoot specific networking issues, consult your network administrator Installing TraceMasterVue and Configuring Communication

221 Configuring Cardiograph Network Settings Device IP Address The Device IP Address feature displays the current IP address for the cardiograph. The IP address is automatically refreshed each time that the cardiograph is fully reset. This feature may also be useful when configuring the cardiograph with a TraceMasterVue ECG Management System. On the Network Configuration screen (the Network tab is selected), touch the Wire Network or Wireless Network tab (right side of screen) to view the IP address information for each type of network connection. Ping Test The Ping Test feature can be used to test or to troubleshoot a cardiograph network connection. For information on using the Ping Test, See Testing TraceMasterVue Remote Site Connectivity on page 20.. Configuring Cardiograph Network Settings NOTE If assistance is required with any of the settings described in this section, please consult your network administrator. To configure cardiograph network settings 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Network tab (top of screen). The selected tab is indicated in blue. 4 Under Network ID touch the field next to Computer Name. The cursor appears in the field. Type in a unique name to identify the specific cardiograph on the network (up to sixteen letters or numbers). The Computer Name is a required field and cannot be left blank. The Computer Name field cannot be left blank and cannot contain any special characters. This field can only contain the letters A-Z or the numerical digits 0-9. Do not enter spaces in the Computer Name field. If any spaces are entered, the entered Computer Name will be replaced with the text WinCE. 5 Select the Wire Network or Wireless Network tab (right of screen). The selected tab is indicated in blue. 6 If a static IP address is available on the network, select Specify IP Address. If the network supports DHCP (Dynamic Host Configuration Protocol) select Obtain IP Address Automatically. Touch the text to select the radio button. For more information on these settings, see your network administrator. 7 If Specify IP Address is selected, touch the first field next to IP Address. The cursor appears in the field. Type in the first number of the IP address, no separating period (.) is required. Press the Tab key (on keyboard) to scroll between the fields. Continue to enter information for the Subnet Mask, and Default Gateway fields. Installing TraceMasterVue and Configuring Communication 8-13

222 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 8 If Obtain IP Address Automatically is selected, touch the first field next to Primary DNS Server. The cursor appears in the field. Type in the first number of the address, no separating period (.) is required. Press the Tab key (on keyboard) to scroll between the fields. Enter information for the Primary WINS field. Both of these fields are optional. 9 If configuring a wired connection, under Ethernet Adapter, select either Auto Negotiate Settings (default setting) or manually specify the Ethernet transmission settings by selecting Manual Settings and then selecting the specific transmission settings (mbps transmission rate and duplex settings). For more information on these settings, see your network administrator. The cardiograph must restart to apply the new network settings. 10 Touch another Configuration tab (top of screen). The selected tab is indicated in blue. The Save Network Settings dialog box appears. 11 Touch Yes to apply the new network settings. The cardiograph restarts and the new network settings are applied. NOTE Touching the No button on the Save Network Settings dialog box discards the selected network settings. About Wired Ethernet and Wireless LAN Connectivity Using DHCP If the PageWriter Touch cardiograph is configured to support both a wired Ethernet and wireless LAN connection using DHCP, connectivity issues may occur when the Ethernet LAN cable is disconnected from the cardiograph, and the wireless LAN card is either already inserted into the PC card slot, or it is inserted at a later time. In both instances, the wireless LAN card will be unable to associate to an access point once the Ethernet LAN cable is disconnected from the cardiograph. If the cardiograph must support both a wired and wireless connection using DHCP, follow the procedure below to modify the Ethernet LAN settings when switching from the wired Ethernet to a wireless LAN connection. Please note that both the wired Ethernet and wireless LAN connection using DHCP will function normally when the Ethernet LAN cable is connected to the cardiograph. To modify the wired Ethernet LAN settings 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Network tab (top of screen). The selected tab is indicated in blue Installing TraceMasterVue and Configuring Communication

223 Configuring Cardiograph Network Settings 4 Touch the Wire Network tab. If the wired network settings are configured for DHCP, the Obtain IP Address Automatically option is selected. To use a wireless LAN connection with DHCP, the wired network settings will need to be changed to a static IP address. Select the Specify IP Address option. 5 In the IP Address field, enter 0 into each field, to configure an IP address of No separating period (.) is required. 6 In the Subnet Mask field enter 255 into each of the first three fields, and then enter 0 into the last field to configure a Subnet Mask address of Touch the R/T ECG button. The Save Network Settings window appears. 8 Touch the Yes button to apply the new network settings. The cardiograph automatically restarts. The new network settings are applied, and the entered static IP address for the wired connection is seen on the Network configuration screen under Device IP Address (Wired Network). Touch the Wire Network or Wireless Network tab (right side of screen) to view the current IP address information for each connection. 9 To reestablish the wired Ethernet LAN settings with DHCP, return to the Network settings screen in Configuration and select the Obtain IP Address Automatically setting, and then reenter all DHCP settings. Configuring Remote Site Settings The Remote Sites feature on the cardiograph is used to configure the connectivity settings used with a specific TraceMasterVue ECG Management System server. TraceMasterVue ECG Management System Remote Sites (one or more) transmit ECG data to the cardiograph, and receive ECG data from the cardiograph. ECG data transmission to and from a Remote Site can be done with a modem, or with a wireless or wired network connection. The following illustration provides an overview of how ECG data can be transferred between a cardiograph and a TraceMasterVue ECG Management System. For information on configuring fax transmission from the cardiograph, see Chapter 3 of the PageWriter Touch Cardiograph Instructions for Use. The file is available for download from the InCenter site (incenter.medical.philips.com). Figure 8-3 PageWriter Touch to TraceMasterVue Remote Site Transfer Installing TraceMasterVue and Configuring Communication 8-15

224 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Configured TraceMasterVue Remote Sites appear in the Selected Archive drop-down list on the Archive screen. The Archive is used to transmit ECGs to and from the cardiograph, and to search a configured Remote Site for ECGs to save to the cardiograph and to print on the cardiograph. For more information on using the Archive to transmit ECGs to TraceMasterVue, see Chapter 8 Transferring ECGs and Using the Archive the PageWriter Touch Cardiograph Instructions for Use Installing TraceMasterVue and Configuring Communication

225 Configuring Cardiograph Network Settings Configuring a Remote Site Network or a Remote Access Server (RAS) Connection with Modem The cardiograph transmits ECG and order data to a TraceMasterVue ECG Management System using a wired or wireless network connection, or through a Remote Access Server (RAS) connection using a modem. The cardiograph uses a PCMCIA card modem inserted into the PC card slot on the rear of the cardiograph. Figure 8-4 Using the PC Card Slot For information on compatible PCMCIA card modems used outside of the USA and Canada, contact the nearest Philips Response Center or your local distributor. WARNING Never connect the modem card to a phone line when the cardiograph is connected to a patient. Remote Site Security Feature The cardiograph offers a Secure Sockets Layer (SSL) encryption protocol feature for the secure transmission of ECG and order data between a TraceMasterVue Remote Site and the cardiograph. The SSL security feature is applied to both LAN and modem connections. NOTE NOTE The SSL security feature should only be enabled on the cardiograph when it is enabled on the TraceMasterVue server that contains the configured Remote Site. For details, see Adding SSL Support on page Do not enable this setting on the cardiograph only. To configure a remote site with a network or modem connection 1 If configuring a modem card, push the On/Standby button on the cardiograph to put the cardiograph into Standby. The cardiograph will not recognize the modem card if the cardiograph is placed in QuickStart. 2 Insert the PC card modem into the PC card slot on the rear of the cardiograph. 3 Touch the On/Standby button to return the cardiograph to active use. Installing TraceMasterVue and Configuring Communication 8-17

226 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 4 Touch the Config button on the Command Toolbar. 5 Touch the Defaults button on the Configuration Context Toolbar. 6 Touch the Remote Sites tab (top of screen). The selected tab is indicated in blue. 7 Under Remote Sites Archive touch the Network radio button to select it. The Network configuration screen appears. NOTE NOTE NOTE For information on configuring the fax feature, see Chapter 3 of the PageWriter Touch Cardiograph Instructions for Use. 8 Select or clear the check boxes for Receive (Query) and Copy/Transfer (left of screen). The Receive (Query) feature allows the user to search the configured TraceMasterVue Remote Site for ECGs to download and print on the cardiograph. The Copy/Transfer feature allows the user to transfer ECGs to the Remote Site. 9 Touch the Network tab (right side of screen). 10 Touch the field next to Server URL (required field that must be completed). The cursor appears in the field. Type in the URL address of the TraceMasterVue file server URL. The TraceMasterVue file server address uses the TraceMasterVue computer name or IP address, and ends with EMSCOMM. For example, some valid URL addresses are EMSCOMM or 11 Touch the field next to User Name. The cursor appears in the field. Type in the user name. If a modem connection is used for the specified Remote Site, you must also specify the domain name (the computer name of the TraceMasterVue (RAS) server) with the user name. For example, if the domain name for the Remote Site is TMVue1, and the user name is pwt, enter TMVue1/pwt into the User Name field. The same Domain name is entered into the Domain field under the Net Connect tab. The user name specified must be a member of a TraceMaster group that has View privileges to TraceMasterVue. 12 Touch the field next to Password. The cursor appears in the field. Type in the password assigned to the specified user. 13 Select the Enable SSL Security check box to enable the Secure Socket Layer (SSL) encryption protocol. This setting is applicable for both LAN and modem connections. NOTE The SSL security feature should only be enabled on the cardiograph when it is also enabled on the TraceMasterVue server that contains the configured Remote Site. For details, see Adding SSL Support on page Do not enable this setting on the cardiograph only Installing TraceMasterVue and Configuring Communication

227 Configuring Cardiograph Network Settings 14 Touch the Net Connect tab (top right of screen). The selected tab is indicated in blue. Select Always Connected (LAN, wireless LAN) or Dial-up (modem) connection. Touch the text to select the radio button. If selecting the Always Connected setting, proceed to step If Dial-up (modem) connection is selected, touch the drop-down arrow button next to Dialing Devices (required field that must be completed) to display the drop-down list. 16 Select the US Robotics 56K modem card (or other installed modem card). If the exact model name of your modem is not listed, selected Standard Modem. Do not select Hayes-Compatible Modem. 17 Touch the field next to Phone (required field that must be completed). The cursor appears in the field. Enter the TraceMasterVue RAS server modem telephone number. 18 Touch the field next to User Name (required field that must be completed). The cursor appears in the field. Enter a valid user account that has permission to log in through RAS. NOTE CAUTION If the specified user name is not configured for RAS access, the user will be unable to transmit ECGs or perform interactive queries to TraceMasterVue using the modem RAS connection. 19 Touch the field next to Password. The cursor appears in the field. Enter the password for the specified user name. 20 Touch the field next to Domain. The cursor appears in the field. Enter the domain name for the TraceMasterVue (RAS server). 21 At the top of the screen a check mark and the word Modified (in blue) appears. Touch the Add New button. The Add New Remote Site window appears. 22 Enter a name for this Remote Site and touch the OK button. The Remote Site appears in the Remote Sites Archive drop-down list (top of screen) and may be selected in the Archive. Do not add blank spaces to the Remote Site name or the modem connection may not connect to the TraceMasterVue ECG Management System. The new settings are applied. Proceed to test connectivity with TraceMasterVue. Or, touch the R/T ECG button to return to normal cardiograph operation. Installing TraceMasterVue and Configuring Communication 8-19

228 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Testing TraceMasterVue Remote Site Connectivity Follow the procedure below to test the connectivity settings between the PageWriter Touch cardiograph and the newly defined TraceMasterVue Remote Site. To ping the TraceMasterVue server from the PageWriter Touch cardiograph 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Network tab (top of screen). The selected tab is indicated in blue. 4 Under Network Test, type in the IP address of the TraceMasterVue server in the IP Address field. 5 Touch the Ping button. If the test succeeds, proceed to the next step. If the test fails, consult your network administrator for further networking assistance. Editing Remote Site Settings To change remote site network or modem settings 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Remote Sites tab (top of screen). The selected tab is indicated in blue. 4 Under Remote Sites Archive touch the drop-down arrow button to display the drop-down list of configured TraceMasterVue Remote Sites, and touch the Remote Site to select it. The settings for the selected Remote Site appear on the screen. 5 Make changes to the Remote Site settings, as necessary. When all changes are complete, a check mark and the word Modified (in blue) appears at the top of the screen. 6 Touch the Save button to save the changes to the selected Remote Site. The new settings are applied. 7 Touch the R/T ECG button to return to normal cardiograph operation Installing TraceMasterVue and Configuring Communication

229 Configuring Cardiograph Network Settings Defining Institution Settings The optional settings in this section provide information about the location of a specific cardiograph. The information entered into this section must be consistent with the location information defined on TraceMasterVue. This location-specific information is transferred with the ECG data, and appears on the printed ECG report. These optional fields include: Location Code (LOC) Device ID (identification number to track a specific cardiograph) Institution Label Institution Number Facility Label Facility Number Department Label Department Number Each of these fields may be customized with any thirty-two letters or numbers. Location Code (LOC) is limited to five numbers only. Device ID is limited to thirty-two numbers only. This information appears on the printed ECG. Special Note about Location Code (LOC) The Location Code (LOC) is only used with legacy versions of the TraceMaster NT system. The LOC does appear on the printed ECG. Configuring the LOC disables the Institution Number and Department Number fields as the Location Code provides the same information. Do not use the Location Code (LOC) field with a TraceMasterVue ECG Management System. If you are configuring the LOC with a TraceMaster NT system, see the M3700A TraceMaster NT documentation. To configure institution information 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Institution tab (top of screen). The selected tab is indicated in blue. 4 Touch the field to the right of the institution information type. 5 Type in the label exactly as it should appear on the printed ECG report (up to thirty-two letters or numbers). NOTES The Location Code is limited to five numbers. The first three numbers are used to identify an institution number, and the last two numbers are used to identify a department number. The Device ID is limited to thirty-two numbers. The new settings are applied. Installing TraceMasterVue and Configuring Communication 8-21

230 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 6 Touch the R/T ECG button to return to normal cardiograph operation, or proceed to configure Patient ID settings. Patient ID Settings The Patient ID settings are used to configure the amount and type of patient information fields that appear on the Patient ID screen, that appear on the printed ECG report, and that are transferred to a TraceMasterVue ECG Management System.The configuration of Patient ID settings must be coordinated with other TraceMasterVue settings. On the configuration screen for Patient ID settings, the patient information fields are grouped into four main categories. The categories are: Patient Information, Clinical Information, Order Information, and Additional Information. The order that the patient information fields appear in on the Patient ID screen can also be specified. Figure 8-5 Configured Patient ID screen A B A B Required Patient ID fields are indicated in blue, the order that fields appear in on the screen can be specified Press the Pg Up or Pg Dn key (on keyboard) to scroll up or down on the screen To open the Patient ID screen 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Patient ID tab (top of screen). The selected tab is indicated in blue. Five tabs appear at the top of the screen. The MagCard tab contains settings for the magnetic card reader. For information on configuring magnetic card reader settings, see Chapter 3 of the PageWriter Touch Cardiograph Instructions for Use Installing TraceMasterVue and Configuring Communication

231 Configuring Cardiograph Network Settings Figure 8-6 Patient ID Configuration Screen Patient Info. Clinical Info. Order Info. Add l Info. MagCard (page 8-24) (page 8-25) (page 8-26) (page 8-27) See the PageWriter Touch Instructions for Use Patient ID Configuration Options Each patient information field on the cardiograph may be configured with up to four options as described in Table 8-1. These options appear as columns of check boxes on the left side of each Patient ID configuration screen. Select the check box underneath the option to enable it. Table 8-1 Setting Patient ID information configuration options Description Enabled Select this check box to make this type of patient information appear on the Patient ID screen. This patient information is stored with the ECG when transferred to a TraceMasterVue ECG Management System. Required Select this check box to require that this type of patient information be completed in full in order to transfer an ECG to removable media or to a Philips TraceMasterVue ECG Management System. Required patient information is indicated in blue text on the Patient ID screen. Indexed Select this check box to make this type of patient information appear as a column on the Archive or Orders screen. Printed ECGs can be sorted in the Archive or in Orders using this type of patient information. Select this check box to include this type of patient information on the printed ECG report. Installing TraceMasterVue and Configuring Communication 8-23

232 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Configuring Patient Information The Patient Information fields include demographic information about the patient including: name, ethnicity, age, gender and other configurable information fields. NOTE Age and Gender patient information are required if using the Philips 12-Lead Algorithm for ECG interpretation. For more information see the Philips 12-Lead Algorithm Physician Guide on the PageWriterTouch Cardiograph User Documentation CD, or download the file from the Philips InCenter site (incenter.medical.philips.com). There are two optional user defined drop-down lists that can be configured to appear on the Patient ID screen. For information on configuring the optional patient information fields, see Configuring Optional, User Defined Patient ID fields on page Each type of Patient Information can be configured using up to four different settings: Enabled, Required, Indexed, and Printed (see Table 8-1, Patient ID information configuration options, on page 8-23). Table 8-2 Patient Information description Patient Information Description Patient ID Number Up to sixteen characters in length Patient First Name Patient Last Name Patient Additional Name This field cannot be disabled Up to forty characters in length Up to forty characters in length Up to forty characters in length Race (Ethnicity) Drop-down list selection Pre-defined drop-down list Patient Age Configurable units (years, hours, days, weeks, months) Patient Gender Date of Birth (month, day, year) Drop-down selection (male, female, unknown) User Defined drop-down list Drop-down list label up to sixteen characters in length Drop-down list selections up to thirty-two characters in length For information on configuring the user defined fields, see page Installing TraceMasterVue and Configuring Communication

233 Configuring Cardiograph Network Settings To configure Patient Information 1 Touch the Patient Info. tab (top of screen). The selected tab is indicated in blue. Press the Tab key (on keyboard) to highlight the option check boxes on the left side of the screen (see Table 8-1 on on page 8-23). Press the space bar (on keyboard) to select a check box. A check mark appears in the selected check box and enables the feature. 2 Touch the drop-down arrow button next to Age (DOB) to select a default age unit (DOBdate of birth, Years, Days, Weeks, Hours). Touch the age unit to select it as the default. The Default Age (Years) selection specifies the default age that is used for ECG interpretation (using the Philips 12-Lead Algorithm) when no patient age is entered. The recommended default age is 50 years. Configuring Clinical Information The available configurable Clinical Information fields include: Symptoms (Sx) History (Hx) Prescriptions (Rx) Diagnoses (Dx) Diagnostic Related Group (DRG) During a patient session the user selects a pre-defined selection for each type of Clinical Information from a drop-down list, or manually enters specific information with the keyboard. There are two optional user defined drop-down lists that can be configured to appear on the Patient ID screen. For information on configuring the optional clinical information fields, See Configuring Optional, User Defined Patient ID fields on page 28.. Each type of Clinical Information can be configured using four different settings: Enabled, Required, Indexed, and Printed (see Table 8-1 on page 8-23). To configure Clinical Information 1 Touch the Clinical Info. tab (top of screen). The selected tab is indicated in blue. Press the Tab key (on keyboard) to highlight the option check boxes on the left side of the screen (see Table 8-1 on on page 8-23). Press the space bar (on keyboard) to select a check box. A check mark appears in the selected check box and enables the feature. 2 Touch the drop-down arrow button next to the empty field that appears to the right of each type of Clinical Info (Sx, Hx, Rx, Dx, and DRG). Press the up or down arrow key (on keyboard) to scroll through the selections in the list, and review the available selections. Installing TraceMasterVue and Configuring Communication 8-25

234 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 3 To delete a selection from the list, touch a clinical description to select it. Touch the Delete button to delete this clinical description from the selections in the dropdown list. 4 Touch the Add button to add a new clinical information selection to the drop-down list. Type in the clinical information description on the keyboard. 5 Touch the OK button. The entry now appears in the drop-down list and may be selected during a patient session. The new settings are applied. 6 Touch the R/T ECG button to return to normal cardiograph operation. Configuring Order Information The available Order information fields include: Order Reason Physician Name and UPIN (Universal Physician Identification Number) Order Number Encounter ID STAT ECG designation; this specifies the ECG as a STAT ECG and provides for special processing of the ECG on the TraceMasterVue ECG Management System There are two optional user defined drop-down lists that can be configured to appear on the Patient ID screen. For information on configuring the optional order information fields, See Configuring Optional, User Defined Patient ID fields on page 28.. For the fields Reason for Order and Physician Name/UPIN, the user selects an entry from the available choices in the drop-down list, or enters specific information into the field using the keyboard. Each type of Order Information can be configured using four different settings: Enabled, Required, Indexed and Printed (see Table 8-1 on on page 8-23). To configure Order Information 1 Touch the Order Info. tab (top of screen). The selected tab is indicated in blue. Press the Tab key (on keyboard) to highlight the option check boxes on the left side of the screen (see Table 8-1 on on page 8-23). Press the space bar (on keyboard) to select a check box. A check mark appears in the selected check box and enables the feature 2 Touch the Add button to the right of Reason for Order or Physician Name to add a new entry to the drop-down list. A window appears. 3 Type in the selection (using keyboard) as it should appear on the drop-down list Installing TraceMasterVue and Configuring Communication

235 Configuring Cardiograph Network Settings 4 Touch OK. The entry now appears in the drop-down list and may be selected during a patient session. The new settings are applied. 5 Touch the R/T ECG button to return to normal cardiograph operation. Configuring Additional Information The available Additional Information fields include: Facility identification; by code or by name Department identification; by code or by name Operator identification Room number Patient weight and height There are two optional user defined drop-down lists that can be configured to appear on the Patient ID screen. For information on configuring the optional additional information fields, See Configuring Optional, User Defined Patient ID fields on page 28.. For the selections Department and Operator ID, the user selects a pre-defined selection from a drop-down list. The drop-down list can only be changed on the Configuration screen. Each type of Order Information can be configured using four different settings: Enabled, Required, Indexed, and Printed (see Table 8-1 on on page 8-23). To configure Additional Information 1 Touch the Add l Info. tab (top of screen). The selected tab is indicated in blue. Press the Tab key (on keyboard) to select the option check boxes on the left side of the screen (see Table 8-1 on on page 8-23). Press the space bar (on keyboard) to select a check box. A check mark appears in the selected check box and enables the feature 2 Touch the drop-down arrow button next to the white blank box that appears to the right of Department and Operator ID. 3 Touch the Add button to add a new entry to the drop-down list. A window appears. 4 Type in the entry (using keyboard) as it should appear on the drop-down list. 5 Touch the OK button. The entry now appears in the drop-down list and may be selected during a patient session. The new settings are applied. 6 Touch the R/T ECG button to return to normal cardiograph operation. Installing TraceMasterVue and Configuring Communication 8-27

236 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Configuring Optional, User Defined Patient ID fields There are eight optional drop-down lists that can be customized for any clinical purpose. These drop-down lists are labeled <User Field 1> through <User Field 8>, and appear at the bottom of each Patient ID configuration screen. A customized label is assigned to each optional drop-down list, and individual entries are specified for the drop-down list selections. During a patient session, an entry in the drop-down list can be selected, or free text can be entered into the optional field directly on the Patient ID screen. Accurate and consistent labeling of the user defined fields on the cardiograph and on TraceMasterVue is crucial for optimal connectivity and performance. User fields defined on the cardiograph map directly to user fields on TraceMasterVue. Figure 8-7 A Optional drop-down list as it appears on the Patient ID screen during an active patient session B A Drop-down list label B Individual drop-down list entries Configuring the User Defined Fields with OrderVue NOTE If configuring the cardiograph for use with OrderVue order handling software, User Field 2 must be configured with the Enabled, Required, Indexed, and Printed options enabled. The field must contain the text Order ID. This text is case-sensitive and there must be a space included between the words Order and ID. User Field 1 can also be specified with the text Order ID. If User Field 1 is used, you lose the ability to use the attributes associated with User Field 1. Unless your site has legacy cardiographs that already use User Field 1 for Order ID, User Field 2 is recommended. The field label specified under the field rule for zpd_48_user_defined_2 in the OrderVue Disk.mpr mapper file must be identical to that specified for the User Field 2 on the PageWriter Touch cardiograph. The two fields must identically match. The mapper is stored in C:\Orderlnk\diskmapper and is accessed through LinkTools HL7 mapper. For more detailed information about OrderVue and HL7, refer to the OrderVue documentation available download from the Philips InCenter site: (incenter.medical.philips.com). To put the order ID in a field other than user field 2, you must also change OrderVue configuration Installing TraceMasterVue and Configuring Communication

237 Configuring Cardiograph Network Settings Configuring the User Defined Fields for FDA XML Export If you will be exporting ECGs to FDA XML format, you must configure user field labels on the cardiograph using predefined labels, as described in this section, for proper export. In the pharma environment, ECGs related to drug studies are submitted to the FDA for review, which must be submitted in the FDA XML format. The FDA output file format corresponds to the January 2004 Approved Ballot FDA schema and the recommendations in the aecg Implementation Guide (version Final 3, updated May 23, 2005). This standard has been adopted by the U.S. Food and Drug Administration (FDA) for digital submission of ECGs as part of a drug clinical trial submission. NOTE This standard is subject to change. Copies of the HL7 aecg schema, as well as the latest version of the Implementation Guide, can be found at: When an ECG is exported to FDA XML, either through an automated workflow rule within TraceMasterVue or manually using the Enterprise Manager, the system calls the FDA converter, TraceMasterVue\EMS Server\bin\PhilipsXMLECGtoFDA.exe. The converter maps fields from Philips XML ECGs created using the Philips XML 1.04 schema file, PhilipsECG.xsd, and the FDATemplate.xml template file, to the FDA XML format. These field mappings are illustrated in the spreadsheet provided in the following location: TraceMasterVue\Help\PhilipsXMLECGtoFDA_Field_Mapping_Table.xls. For detailed information about user-defined fields and how they are used in FDA XML file export, as well as how to use the conversion template and read the conversion spreadsheet, see the TraceMasterVue FDA XML Mapping Guide. The guide is provided on the TraceMasterVue Documentation and Training CD, as well as on the TraceMasterVue server in the Help\TraceMasterVue_Manuals directory. In TraceMasterVue, User Field 1 supports individual attributes that can be used as triggers of workflow rules. If you are in a pharma environment and need an additional field to contain Study ID, use User Field 8 and define the label as Facility, exactly as shown here. When the label is set to Facility, and a value is entered at the cardiograph, the specified value will appear as the Facility code on the ECG when imported into TraceMasterVue and displayed in PharmaVue. For details, Installing TraceMasterVue and Configuring Communication Guide available for download from the Philips InCenter web site (incenter.medical.philips.com). To configure the drop-down list label 1 Touch the field under <User Field 1> or any other user field to select it. The cursor appears in the field. 2 Type in any sixteen letters or numbers with the keyboard to describe the drop-down list label. Installing TraceMasterVue and Configuring Communication 8-29

238 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue To add an entry to the drop-down list 1 Touch the Add button (right side of screen) next to <User Field 1> or any other user field. 2 The Add Custom Entry window appears. Type in any thirty-two letters or numbers with the keyboard. 3 Touch the OK button. The new drop-down entry appears in the field to the right of <User Field 1> or any other user field. Add more entries as needed. To delete an entry from the drop-down list 1 Touch the drop-down arrow button (to the left of the Add button) to display the existing drop-down list. 2 Touch the entry to be deleted. The drop-down list closes with the selected entry highlighted in blue. 3 Touch the Delete button (right side of screen). The Delete Custom Field Entry window appears with the message Delete Selected Label? The name of the entry to be deleted appears in gray (bottom of window). 4 Touch the OK button to delete the entry. Touch the Cancel button to not delete the entry. The new settings are applied. 5 Touch the R/T ECG button to return to normal cardiograph operation. Patient ID Layout Settings The order in which the configured patient information fields appear on the Patient ID screen during an active patient session can be specified. Follow the procedure below to configure the layout of the patient information fields after all Patient ID settings have been configured. To configure the Patient ID layout settings On the left side of the Patient ID configuration screen under Patient ID Layout, all of the configured patient information fields appear in a list. The order in which the fields appear on this list defines the order the fields appear in on the Patient ID screen during an active patient session. 1 To move an individual patient information field up or down on the list, touch the field to select it. The selected field is highlighted in blue. 2 Touch the Move Up or Move Dn buttons (bottom of screen) to move the fields up or down on the list. The new settings are applied. 3 Touch the R/T ECG button to return to normal cardiograph operation Installing TraceMasterVue and Configuring Communication

239 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs As you configure the communication between the cardiographs and TraceMasterVue, and test each connection, you may encounter some problems with the configuration. The following sections describe some of the more common communication issues, and each section includes solutions to help you solve various communication issues. This section is broken down into two sections: troubleshooting a wired or a wireless connection. Follow the steps outlined in each section in the order shown. The following suggestions assume that you have tested ECG transmission between the cardiograph and TraceMasterVue and it failed. Troubleshooting a Wired Connection Table 8-5 Troubleshooting PageWriter Touch Cardiograph/TraceMasterVue Communication Issues What to do... Next steps... 1 Check all hardware connections. If any cables are loose, re-attach them and test transmission again. 2 Ping the TraceMasterVue server from the cardiograph. Before proceeding, ensure you have the appropriate IP addresses available. See Using Ping to Verify TraceMasterVue Server to PageWriter Touch Cardiograph Connectivity on page Ping the cardiograph from the server. See To ping the cardiograph from the server on page On the cardiograph, verify the IP address, ensure that the correct IP address type is set (DHCP or static), and ensure the computer name is unique. See Networking Overview on page If transmission fails, proceed to step 2. Proceed to step 3. If ping fails, proceed to step 4. If there was an error in either field, repeat steps 2 and 3. The computer name must be unique. If multiple devices have the same name, one or more devices will not be recognized on the network. In addition, one or more cardiographs may lock up in this case. If the settings were correct, proceed to step 5. Installing TraceMasterVue and Configuring Communication 8-31

240 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Table 8-5 Troubleshooting PageWriter Touch Cardiograph/TraceMasterVue Communication Issues (continued) What to do... Next steps... 5 If the cardiograph connects to the server via a hub, switch, or router, disconnect it, and connect it directly to the TraceMasterVue server hub. See Connecting Communication Hardware to the PageWriter Touch Cardiograph on page 8-3 and Chapter 4, Configuring the Network for TraceMasterVue Data Communication. 6 Contact the hospital network administrator to determine the LAN port Ethernet settings (speed and duplex). For proper communication, the port must be configured to one of the following three settings: Auto Negotiate 100 Mbps Half Duplex 10 Mbps Half Duplex See Auto Negotiation on page Once directly connected, repeat steps 2 and 3. If the ping is successful when directly connected, the problem is most likely in the network switch or router the cardiograph was originally connected through. Contact the site s network administrator to determine the LAN port ethernet settings (see step 6). If transmission still fails, contact the Philips Response Center. If ping fails with the LAN port set to any of these settings, it might be necessary to lock down the cardiograph to a specific setting combination. 7 If interactive query is enabled, but fails, ensure that the user specified on the cardiograph is a member of a TraceMaster group that has View privileges to TraceMasterVue Installing TraceMasterVue and Configuring Communication

241 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Using Ping to Verify TraceMasterVue Server to PageWriter Touch Cardiograph Connectivity The ping command is a simple way to determine whether a device is accessible over a network. You must confirm communication from both ends of the line: from the cardiograph to the TraceMasterVue server, and from the server to the cardiograph. Before proceeding, have available the IP address of the TraceMasterVue server. To ping the TraceMasterVue server from the PageWriter Touch cardiograph 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Network tab (top of screen). The selected tab is indicated in blue. 4 Under Network Test, type in the IP address of the TraceMasterVue server in the IP Address field. 5 Touch the Ping button. If the test succeeds, ensure that you can ping the cardiograph from the server, as described below. Then retest ECG transmission. If the test fails, see Table 8-5 on page 31. To ping the cardiograph from the server This procedure is the same for all cardiographs. Before proceeding, have available the IP address of the target cardiograph. 1 On the TraceMasterVue server, select Start > Run, and type cmd in the Run dialog box. 2 In the Command shell, type the following: ping <cardiograph IP address> For example, ping Installing TraceMasterVue and Configuring Communication 8-33

242 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Troubleshooting a Wireless Connection All PageWriter Touch and TraceMasterVue wireless troubleshooting topics are listed in Table 8-6. For additional information on troubleshooting and diagnostic tests for the Cisco Aironet 350 wireless adapter, see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE available for download from For further information on troubleshooting issues with a specific access point, see the product documentation and other support information provided by the access point manufacturer, or consult your network administrator. Table 8-6 Troubleshooting topics Topic Aironet Client Utility (ACU) Error Messages PageWriter Touch Cardiograph Wireless Error Messages PageWriter Touch Cardiograph ECG Transmission Error Messages Wireless Adapter is not associated to an access point Page Number page 8-34 page 8-35 page 8-36 page 8-38 Table 8-7 Aironet Client Utility (ACU) error messages Error Message Possible Cause Recommended Solution Cisco Wireless LAN Adapter Not Found! Client Adapter Not Found WEP Key X Must Be 10 Hex Digits! The ACU was launched without the wireless adapter being inserted into the cardiograph The wireless adapter was ejected from the cardiograph An invalid number of characters or an incorrect character was entered for the WEP key indicated. 40-bit keys must have 10 total characters. 1 Touch OK to close the error message. 2 Press the On/Standby button on the cardiograph. 3 Insert the wireless adapter into the PC Card slot. 4 Press the On/Standby button. 1 Touch OK to close the error message. 2 Re-enter the characters for the invalid key Installing TraceMasterVue and Configuring Communication

243 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Table 8-7 Aironet Client Utility (ACU) error messages (continued) Error Message Possible Cause Recommended Solution WEP Key X Must Be 26 Hex Digits! You must enter a WEP Key! 350 Series Radio is Not Associated An invalid number of characters or an incorrect character was entered for the WEP key indicated. 128-bit keys must have 26 characters. A WEP key was not entered on the WEP keys window. The wireless adapter is not associated to an access point. 1 Touch OK to close the error message. 2 Reenter the characters for the invalid key. 1 Touch OK to close the error message. 2 Enter a WEP key in the WEP Keys window. There are several reasons why the wireless adapter may not be associated to an access point. Follow the steps in the procedure Checking the Wireless Adapter Association to an Access Point on page Table 8-8 PageWriter Touch cardiograph wireless error messages Error Message Possible Cause Recommended Solution Unidentified PC Card Adapter: Enter the name of the PC Card driver. Driver name: The wireless adapter is inserted incorrectly into the PC card slot on the cardiograph The wireless adapter was inserted into the cardiograph when the cardiograph was in active use (not in Standby mode) An unsupported wireless adapter was inserted into the cardiograph 1 Press the Esc key to close the dialog. 2 Press the On/Standby button on the cardiograph. 3 Insert the wireless adapter card into the PC card slot. 4 Press the Reset button on the rear panel of the cardiograph. For more information, see Chapter 7 of the PageWriter Touch Cardiograph Instructions for Use. Installing TraceMasterVue and Configuring Communication 8-35

244 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Table 8-9 PageWriter Touch cardiograph ECG transmission error messages Error Message Possible Cause Recommended Solution No Reply Received From Remote Site Server Unexpected Reply Received from Remote Site The wireless connection to the access point does not exist The network connection to the TraceMasterVue Remote Site server does not exist or is not configured properly The cardiograph did not receive a response from the TraceMasterVue Remote Site server within a specified period of time A connection to the TraceMasterVue Remote Site server exists, but the server is not properly acknowledging receipt of the packet data. Follow the steps in the procedure Checking the Remote Site Server Connection on page Follow the steps in the procedure Resolving an Unexplained Reply Received from the Remote Site on page Checking the Remote Site Server Connection Use the following procedure to check that the wireless adapter is communicating with a TraceMasterVue Remote Site. To check the remote site server connection 1 Check the LEDs on the wireless adapter. LED Indicators Red LED: blinking quickly Green LED: blinking quickly Recommended Solution 1 Move the cardiograph to an area with a strong wireless signal. The green LED should then blink slowly or turn off completely indicating that the wireless adapter is associated with an access point. 2 If the green LED continues to blink quickly indicating that the wireless adapter is still not associated to an access point, follow the steps in the procedure Checking the Wireless Adapter Association to an Access Point on page Installing TraceMasterVue and Configuring Communication

245 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs LED Indicators Red LED: off Green LED: off Red LED: blinking quickly Green LED: off or blinking slowly Recommended Solution 1 Ensure that the wireless adapter is securely inserted into the PC card slot on the rear of the cardiograph. 2 Push the On/Standby button to put the cardiograph into Standby. 3 Push the On/Standby button again. 4 Check the status LEDs on the wireless adapter. If the LEDs are still not illuminated, contact the Philips Response Center for further assistance. The wireless adapter is associated to an access point. Go to Step 2 in this procedure. 2 Launch the Aironet Client Utility. On the cardiograph, touch Config, then Defaults. Then touch the Network tab, the Wireless Network tab, and finally, touch Configure, next to CISCO Aironet In the ACU, touch the Status tab. If green or yellow bars appear on the Signal Strength or Signal Quality fields, this indicates an active connection. If the bars are red, try moving the cardiograph to an area with a stronger wireless signal. For information on performing additional diagnostic tests from the Status tab, see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE available for download from 4 Verify that the IP address information on the cardiograph network screen is correct (DHCP or Static IP) and that the computer name is also correct. The DHCP IP address is displayed on the ACU screen. If DHCP is being used, the DHCP lease may have expired. To reacquire an IP address, press the On/Standby button on the cardiograph to enter Standby mode, then press the button again to return the cardiograph to active use. 5 Ping the TraceMasterVue server from the cardiograph as described in Using Ping to Verify TraceMasterVue Server to PageWriter Touch Cardiograph Connectivity on page If the access point ping test fails, most likely there is an IP configuration issue. Consult your network administrator for further assistance. It may be helpful to connect the cardiograph to a hardwired Ethernet connection for further IP configuration troubleshooting. Installing TraceMasterVue and Configuring Communication 8-37

246 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue Resolving an Unexplained Reply Received from the Remote Site Use the following procedure if the error message Unexpected Reply received from Remote Site appears when transmitting ECGs to a TraceMasterVue ECG Management System. To resolve an unexplained reply received from the remote site 1 On the Configuration screen, check that the Remote Site server URL is in the correct format. Ensure that the Remote Site Server URL includes a forward slash at the end of the URL. An example of a valid URL is: 2 If the URL is correct, consult the TraceMasterVue system administrator for more information. The TraceMasterVue server may need to be reset. Checking the Wireless Adapter Association to an Access Point Use the following procedure when a wireless adapter is not associating with an access point. 1 Check the LEDs on the wireless adapter. See Table 8-10 for further steps. Table 8-10 LED Indicators LED Indicators Red LED: blinking quickly Green LED: blinking quickly Recommended Solution 1 Move the cardiograph to an area with a strong wireless signal. The green LED should then blink slowly or turn off completely indicating that the wireless adapter is associated with an access point. 2 If the green LED continues to blink quickly indicating that the wireless adapter is still not associated to an access point, go to step 2 in this procedure. Red LED: off Green LED: off 1 Ensure that the wireless adapter is securely inserted into the PC card slot on the rear of the cardiograph. 2 Push the On/Standby button to put the cardiograph into Standby. 3 Push the On/Standby button again. 4 Check the status LEDs on the wireless adapter. If the LEDs are still not illuminated, contact the Philips Response Center for further assistance Installing TraceMasterVue and Configuring Communication

247 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Touch Cardiographs Table 8-10 LED Indicators (continued) LED Indicators Red LED: blinking quickly Green LED: off or blinking slowly Recommended Solution The wireless adapter is associated to an access point. Go to Step 2 in this procedure. 2 Launch the Aironet Client Utility. On the cardiograph, touch the Config button, then the Defaults button, the Network tab, the Wireless Network tab, then touch the Configure button next to CISCO Aironet Ensure that the correct profile is selected in the Select Active Profile drop-down list. 4 Ensure that the message 350 Series Radio is Associated appears on the Aironet Client Utility window. If it does not, proceed to step 5. 5 Ensure that the access point is turned on and is operating. 6 If the wireless adapter still cannot associate with the access point, contact your network administrator to ensure that all settings are correct for both the wireless adapter and for the access point. If MAC or IP filtering is enabled at the access point, ensure that the wireless adapter MAC address or IP address is added to the list. If multiple static WEP keys are being used, the transmit key must be configured as the first WEP key. On the access point, the first WEP key must match the first key on the wireless adapter. If the cardiograph is configured with both wired Ethernet and wireless LAN DHCP settings, the wired Ethernet settings are taking precedence and will need to be modified. See About Wired Ethernet and Wireless LAN Connectivity Using DHCP on page 8-14 for more information. For further information see the Cisco Aironet Wireless LAN Client Adapters Installation and Configuration Guide for Windows CE available for download from: Installing TraceMasterVue and Configuring Communication 8-39

248 Configuring PageWriter Touch B.01 Cardiographs for Use with TraceMasterVue 8-40 Installing TraceMasterVue and Configuring Communication

249 9 Chapter 9Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue After configuring data communication on the TraceMasterVue end (both in terms of connecting and setting up hardware, and configuring settings on the server), you are now ready to connect and configure cardiographs. In addition, if you wish to use interactive query, you must also configure that functionality on the cardiographs. This chapter provides the following information: Selecting Options on the PageWriter Trim Cardiograph Connecting Communication Hardware to the PageWriter Trim Cardiograph.9-2 Before You Begin Configuring Location Information on the PageWriter Trim Cardiograph Defining User Fields on the PageWriter Trim Cardiograph Defining User Fields for FDA XML Export Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph Ensuring Interactive Query is Enabled Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue Troubleshooting Communication Issues between TraceMasterVue and PageWriter Trim Cardiographs Using Ping to Verify TraceMasterVue Server to PageWriter Trim Cardiograph Connectivity Perform the following steps, in order, to configure the PageWriter Trim cardiographs for communication with TraceMasterVue: 1 Connect the communication hardware, either LAN or modem. 2 Configure locations. 3 Configure user-defined fields. 4 Configure remote sites. 5 Configure network information. This step is saved for last because it requires a cardiograph restart after completion. 6 Test communication between the systems. 9-1

250 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue NOTE The following procedures are provided here for your convenience. If necessary, refer to the cardiograph documentation for the most up-to-date information on configuring settings. Selecting Options on the PageWriter Trim Cardiograph The PageWriter Trim cardiographs use a combination of keyboard commands and the Trim Knob to navigate between fields, as well as to make selections, as follows: Keyboard key sequences are shown in the following format: Alt-T. This indicates you are to hold down the Alt key and press the T key, as well. Each screen or tab displays the tab name, followed by the keyboard key in parentheses. To access each tab, hold down the Alt key and press the listed letter key. Turn the Trim Knob to the right or left to move between buttons and fields, stopping when the desired entry is highlighted. Press the Trim Knob to select a highlighted entry. Connecting Communication Hardware to the PageWriter Trim Cardiograph PageWriter Trim cardiographs can communicate with TraceMasterVue either using a local area connection (LAN) or over a modem, using RAS. The cardiograph uses a PC card modem that supports printing to Group 3 Fax machines, as well as the Class 1 and 2 Fax modem protocol (USA and Canada only). For additional details about PC card modems, refer to the PageWriter Trim Instructions for Use. Before You Begin If you are setting up a new TraceMasterVue system and associated cardiographs and devices, ensure you have already configured the TraceMasterVue system, as described in Chapters 1 through 7. If you are adding a cardiograph to an already operational TraceMasterVue system, have available all configuration information before proceeding. Refer to filled out worksheets and settings configured for other cardiographs, including locations, user fields, user ID, and the like. See Chapter 2, TraceMasterVue Communication Worksheets. To connect the PageWriter Trim cardiograph to the LAN Insert the LAN card into the PC card slot on the rear of the cardiograph. CAUTION Only use the shielded LAN cable provided with the PageWriter Trim cardiograph. Do not use LAN cables with the cardiograph that have not been approved by Philips Medical Systems. 9-2 Installing TraceMasterVue and Configuring Communication

251 Connecting Communication Hardware to the PageWriter Trim Cardiograph PC card eject button You are now ready to configure the cardiograph, including defining locations and any needed user fields, as well as specifying settings to use the modem connection. Connection configuration consists of setting up a remote site and configuring the modem settings. To connect the PageWriter Trim cardiograph using a modem connection WARNING Do not connect the modem card to a phone line when the cardiograph is connected to a patient. 1 Insert the PC card modem into the card slot in the back of the cardiograph and gently push it in. PC card eject button 2 Insert the PC card end of the cable into the phone connector on the PC card. 3 Insert the other end of the cable into the modem port used for communication with TraceMasterVue. You are now ready to configure the cardiograph, including defining locations and any needed user fields, as well as specifying settings to use the modem connection. Connection configuration consists of setting up a remote site and configuring the modem settings. Installing TraceMasterVue and Configuring Communication 9-3

252 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue Configuring Location Information on the PageWriter Trim Cardiograph The location information uniquely identifies the cardiograph at your site. It is important that the location-related information that you specify on the cardiograph match the location information defined in TraceMasterVue. For detailed information about locations on TraceMasterVue, see Configuring TraceMasterVue and Device Location Fields on page B-2. Before configuring TraceMasterVue or the cardiographs, complete the Location worksheet (page 2-11), noting the definitions to use. Then configure the location-related fields on the cardiograph to match, using the Institution tab. To configure location fields (institution, facility, and department) on the PageWriter Trim cardiograph 1 In the tool bar at the bottom of the screen, turn the Trim Knob to highlight Config, then press the knob to display the Configuration screen. 2 Press Alt-C to display the Cardiograph tab. Location fields Cardiograph tab NOTE 3 Fill in the fields as appropriate. Remember to configure the fields with the same values in TraceMasterVue, using the System Configuration utility. See Using Location Information in TraceMasterVue on page B-1. Do not configure a location code unless you are connecting the PageWriter Trim cardiograph to a legacy TraceMaster NT system. If this is the case, refer to the M3700A TraceMaster NT documentation, in addition to the cardiograph documentation. 4 Save your changes. 5 Press Enter to exit configuration, or press Alt-<tab letter> to display a different tab. 9-4 Installing TraceMasterVue and Configuring Communication

253 Defining User Fields on the PageWriter Trim Cardiograph Defining User Fields on the PageWriter Trim Cardiograph Configure the user fields on the cardiograph, using the various Patient ID tabs. Each of the three tabs, Patient Info, Clinical Info, and Order Info allows you to define two user fields, for a total of six fields. User field numbering is significant, as the values map to user fields in TraceMasterVue. For information about how to define field labels if ECGs will be exported to FDA XML format, see Defining User Fields for FDA XML Export, below For important notes and additional general information about user fields, see Configuring User-Defined Field Values in TraceMasterVue on page 7-18 and your cardiograph documentation. NOTES If you have the OrderVue option to TraceMasterVue, you must reserve a user field to contain the Order ID. By default, OrderVue is configured to look for Order ID in user field 2. The field must be labeled ORDERVUE ID, exactly as shown (case sensitive). You must also ensure that the field label specified under the field rule for zpd_48 User_Defined_2 in the OrderVue Disk.mpr mapper file is identical to that specified for the user defined field (2 on PageWriterTouch/Trim, B on legacy cardiographs) on the cardiograph. That is, the two must match exactly. The mapper is stored in C:\Orderlnk\diskmapper and accessed through the LinkTools HL7 mapper. For additional details about OrderVue and HL7, refer to the OrderVue training materials. For Pharma users. If you need to override the Facility setting for a specific cardiograph with a different Study ID, you can use User Field 8, if properly configured. User Field 8 must be labeled Facility, exactly as shown (capital F, followed by lower case letters). For details, see Overriding the Facility Field with User Defined Field 8 on page D-2. NOTE Defining User Fields for FDA XML Export If you will be exporting ECGs to FDA XML format, you must configure user field labels on the cardiograph using predefined labels, as described in this section, for proper export. In the pharma environment, ECGs related to drug studies are submitted to the FDA for review, which must be submitted in the FDA XML format. The FDA output file format corresponds to the January 2004 Approved Ballot FDA schema and the recommendations in the aecg Implementation Guide (version Final 3, updated May 23, 2005). This standard has been adopted by the U.S. Food and Drug Administration (FDA) for digital submission of ECGs as part of a drug clinical trial submission. This standard is subject to change. Copies of the HL7 aecg schema, as well as the latest version of the Implementation Guide, can be found at: When an ECG is exported to FDA XML, either through an automated workflow rule within TraceMasterVue or manually using the Enterprise Manager, the system calls the FDA converter, TraceMasterVue\EMS Server\bin\PhilipsXMLECGtoFDA.exe. The converter maps fields from Philips XML ECGs created using the Philips XML 1.04 schema file, PhilipsECG.xsd, and the FDATemplate.xml template file, to the FDA XML format. These field mappings are illustrated in the spreadsheet provided in the following location: TraceMasterVue\Help\PhilipsXMLECGtoFDA_Field_Mapping_Table.xls. Installing TraceMasterVue and Configuring Communication 9-5

254 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue For detailed information about user-defined fields and how they are used in FDA XML file export, as well as how to use the conversion template and read the conversion spreadsheet, see the TraceMasterVue FDA XML Mapping Guide. The guide is provided on the TraceMasterVue Documentation and Training CD, as well as on the TraceMasterVue server in the Help\TraceMasterVue_Manuals directory. To configure the User Field labels 1 Turn the Trim Knob to highlight the Config button in the tool bar; then press the knob to display the Configuration screen. 2 On the keyboard, press Alt-I to select and display the Patient ID tab. Patient ID tab 3 On the keyboard, press Alt-T to select the Patient Info tab (if not displayed). User fields 1 and 2 Select appropriate check boxes to display user fields 4 Turn the Trim Knob to highlight the appropriate check box for User Field 1 and/or User Field 2 (either Enabled, Required, Indexed, or Printed), depending on whether you will use one or both fields; then press the knob to select each check box. You must select at least one check box for the field to appear on the Patient Info screen, as described in the following table. Check Box Setting Description Enabled Allows the associated field to appear on the Patient ID screen. The associated information is transferred with the ECG to an TraceMasterVue. 9-6 Installing TraceMasterVue and Configuring Communication

255 Defining User Fields on the PageWriter Trim Cardiograph Check Box Setting Required Indexed Printed Description Indicates that the associated field must be completed before the ECG can be transferred to TraceMasterVue. Indicates that the associated field will appear as a column on the Archive or Orders screen. Indicates that the associated field appears on the printed ECG report. 5 Turn the knob to highlight the field label, and type the text (any 16 letters or numbers). In TraceMasterVue, User Field 1 supports individual attributes that can be used as triggers of workflow rules. If you have the OrderVue option to TraceMasterVue, you must reserve a user field to contain the Order ID. By default, OrderVue is configured to look for Order ID in user field 2. The field must be labeled ORDERVUE ID, exactly as shown (case sensitive). NOTE To put the order ID in a field other than user field 2, you must also change OrderVue configuration. You must also ensure that the field label specified under the field rule for zpd_48 User_Defined_2 in the OrderVue Disk.mpr mapper file is identical to that specified for the user defined field (2 on PageWriterTouch/Trim, B on legacy cardiographs) on the cardiograph. That is, the two must match exactly. The mapper is stored in C:\Orderlnk\diskmapper and accessed through the LinkTools HL7 mapper. For additional details about OrderVue and HL7, refer to the OrderVue training materials. 6 Define user fields as needed on each of the three Info tabs, making sure to select the appropriate check boxes and defining the appropriate field label. User fields 3 and 4 User fields 5 and 6 Installing TraceMasterVue and Configuring Communication 9-7

256 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue 7 To continue making other configuration changes, press Alt-<tab letter> to display the screen and make changes. You are now ready to define network settings and create a remote site on the cardiograph to enable communication with the TraceMasterVue server. Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph The data you specify for the remote site depends on whether you are connecting to the TraceMasterVue system over a LAN or over modem (page 9-10). You must configure both network settings and remote sites. To configure a remote site on the PageWriter Trim cardiograph over a LAN connection 1 Turn the Trim Knob to highlight the Config button in the tool bar; then press the knob to display the Configuration screen. 2 On the keyboard, press Alt-R to select and display the Remote Sites tab. 3 On the Remote Sites screen, do the following. a Press Alt-Z to display the Net Connect tab. Net Connect tab b c Select the Always Connected radio button. Press Alt-Y to display the Network tab. 9-8 Installing TraceMasterVue and Configuring Communication

257 Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph Network tab Interactive query and transmission settings d e Select the Network radio button on the left, and ensure the Receive (Query) and Copy/ Transfer check boxes are both selected. These check boxes determine whether interactive query and data transfer are enabled on this cardiograph. Configure the following network entries. The figure above shows an example of the completed fields. Server URL Type the URL in the form: where xxx.xxx.xxx.xxx is the IP address of the TraceMasterVue system. If your facility supports name server entries, you can also specify the TraceMasterVue server by name. Example: User Name Local user account on TraceMasterVue that is configured for access to ECGs on TraceMasterVue. Example: pwt Note: The user must be a member of a TraceMaster group that has View privileges to TraceMasterVue. Password Password associated with the specified user ID. Example: pwt 4 Turn the Trim Knob to highlight the Add New button, and press the knob to select it. This will save this information as a new remote site. The Add New Remote Site dialog box appears. Installing TraceMasterVue and Configuring Communication 9-9

258 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue 5 Name the remote site with a descriptive name that will identify this site as the TraceMasterVue connection, for example, TraceMasterVue; then select OK. 6 Save the configuration. 7 Proceed with the next step to configure the network ID and IP address of the cardiograph, on page To configure a remote site on the PageWriterTouch cardiograph over a modem connection 1 In the tool bar at the bottom of the screen, touch Config, then Defaults. 2 Touch the Remote Sites tab at the top of the screen. 3 On the Remote Sites screen, do the following: a Press Alt-Z to display the Net Connect tab. Net Connect tab 9-10 Installing TraceMasterVue and Configuring Communication

259 Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph b Configure the following fields as specified. The previous figure shows an example of the completed fields. Network connection type Dialup devices Select the Dial-up radio button. Select the appropriate modem from the list. NOTE If the exact model name of your modem is not listed, selected Standard Modem. Do not select the Hayes-Compatible Modem entry. Example: 3Com_Megahertz-3CXM756/3CCM756 Phone User name TraceMasterVue s (RAS server s) modem phone number. Example: Local user account on TraceMasterVue that is configured to log in through RAS. This user ID must be a member of at least two Windows groups: one that has remote access to the system, for example, Remote Desktop User group; and one that has the appropriate permissions to access TraceMasterVue, for example, TraceMaster-Tech group. Example: pwt NOTE ECG transmission and interactive query between PageWriterTouch and TraceMasterVue will be unsuccessful if you specify a user ID (on TraceMasterVue) that is not configured for RAS access, or if you do not include that user in the required Windows groups. Password Domain Password associated with the specified user ID. Example: pwt Computer name of TraceMasterVue (RAS server). Example: TMVue1 c Press Alt-Y to display the Network tab within the Remote Sites tab. Network tab Interactive query and transmission settings Installing TraceMasterVue and Configuring Communication 9-11

260 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue d e Select the Network radio button on the left, and ensure the Receive (Query) and Copy/Transfer check boxes are both selected. These check boxes determine whether interactive query and data transfer are enabled on this cardiograph. Configure the following network entries. The previous figure shows an example of completed fields. Server URL Type the URL in the form: where xxx.xxx.xxx.xxx is the IP address of the TraceMasterVue system. Example: User Name Local user account on TraceMasterVue that is configured for access to ECGs on TraceMasterVue. Example: pwt Password Password associated with the specified user ID. Example: pwt 4 Turn the Trim Knob to highlight the Add New button, and press the knob to select it. This will save this information as a new remote site. The Add New Remote Site dialog box appears. 5 Name the remote site with a descriptive name that will identify this site as the TraceMasterVue connection, for example, TraceMasterVue; then select OK. 6 Save the configuration. 7 Proceed with the next step, to configure the network ID and IP address of the cardiograph, on page Installing TraceMasterVue and Configuring Communication

261 Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph To configure the network ID and IP address for the PageWriter Trim cardiograph 1 Press Alt-N to display the Network tab. Ensure the Wire Network screen is displayed. Unique cardiograph name Dynamic IP address Static IP address 2 In the Computer Name field, type a unique name to identify this cardiograph on the network. For example, PWT####, where #### is the last four digits of the cardiograph serial number. 3 Specify the IP address for the cardiograph on the network. Refer to the worksheets you completed for this information. They are available in Chapter 2, TraceMasterVue Communication Worksheets. NOTE If you are using dynamic IP configuration DHCP, do not fill in the DNS or WINS values; they will not be saved. 4 Save the configuration. You must now restart the cardiograph. 5 Hold down the On/Standby button for 3 seconds to shut down the cardiograph. Hold the button down again to restart it. The network settings and remote site are now configured. Installing TraceMasterVue and Configuring Communication 9-13

262 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue Ensuring Interactive Query is Enabled To be able to use interactive query, you must ensure that the following check boxes are selected on the Remote Sites tab (step 3.d on page 9-9): Receive (Query) Copy/Transfer NOTE Remember that ECG transmission and interactive query between PageWriter Trim and TraceMasterVue will be unsuccessful if you specify a user ID (on TraceMasterVue) that is not configured for RAS access, or if you do not include that user in an appropriate TraceMaster group that has at least View access to ECGs. You must also ensure that interactive query is properly configured for this cardiograph on the TraceMasterVue server. For details, see Configuring Interactive Query Support on TraceMasterVue on page 7-8. The next step is to test the connection, as described next. Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue After configuring the remote site and network identification, test that ECGs are properly transmitted from the cardiograph to TraceMasterVue, as well as the ability to retrieve ECGs at the cardiograph using interactive query. To test ECG transmission to TraceMasterVue 1 On the cardiograph, save some ECGs to the archive. For details, refer to the PageWriter Trim Instructions for Use. 2 In the tool bar at the bottom of the screen, turn the Trim Knob and highlight the Archive button, then press the knob to display the Archive screen Installing TraceMasterVue and Configuring Communication

263 Testing the Connection between the PageWriter Trim Cardiograph and TraceMasterVue 3 Use the arrow keys to select an ECG to transmit. A check mark to the left of an ECG indicates that it can be transmitted. 4 Using the Trim Knob, highlight and select the Transfer button. The Transfer Selected ECGs dialog box appears. 5 Select the remote site listing for the TraceMasterVue server. If the transfer is successful, the Archive list is updated, and the Last Xmt Dest column shows the remote site to which the ECG was transmitted. 6 In ECGVue, perform a search for the ECG you transmitted. If the transfer was successful, you will be able to retrieve the ECG in ECGVue. If the transmission was not successful, review your configuration settings as directed in the Troubleshooting section, next. Installing TraceMasterVue and Configuring Communication 9-15

264 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue Troubleshooting Communication Issues between TraceMasterVue and PageWriter Trim Cardiographs As you configure the communication between the cardiographs and TraceMasterVue, and test each connection, you may encounter some problems with the configuration. The following section describes some of the more common symptoms and provides information regarding possible causes, and solutions to help you solve potential problems. Follow the steps outlined below in the order shown. The following suggestions assume that you have tested ECG transmission between the cardiograph and TraceMasterVue and it failed. Table 9-1 Troubleshooting PageWriter Trim /TraceMasterVue Communication Issues What to do... Next steps... 1 Check all hardware connections. If any cables are loose, re-attach them and test transmission again. 2 Ping the TraceMasterVue server from the cardiograph. Before proceeding, ensure you have the appropriate IP addresses available. See Using Ping to Verify TraceMasterVue Server to PageWriter Trim Cardiograph Connectivity on page Ping the cardiograph from the server. See Using Ping to Verify TraceMasterVue Server to PageWriter Trim Cardiograph Connectivity on page On the cardiograph, verify the IP address, ensure that the correct IP address type is set (DHCP or static), and ensure the computer name is unique. See Configuring Network Settings and Remote Sites on the PageWriter Trim Cardiograph on page 9-8. If transmission fails, proceed to step 2. Proceed to step 3. If ping fails, proceed to step 4. If there was an error in either field, repeat steps 2 and 3. The computer name must be unique. If multiple devices have the same name, one or more devices will not be recognized on the network. In addition, one or more cardiographs may lock up in this case. If the settings were correct, proceed to step Installing TraceMasterVue and Configuring Communication

265 Troubleshooting Communication Issues between TraceMasterVue and PageWriter Trim Cardiographs Table 9-1 Troubleshooting PageWriter Trim /TraceMasterVue Communication Issues (continued) What to do... Next steps... 5 If the cardiograph connects to the server via a hub, switch, or router, disconnect it, and connect it directly to the TraceMasterVue server hub. See Connecting Communication Hardware to the PageWriter Trim Cardiograph on page 9-2 and Installing Hardware and Configuring COM Ports On TraceMasterVue on page 4-1. Once directly connected, repeat steps 2 and 3. If the ping is successful when directly connected, the problem is most likely in the network switch or router the cardiograph was originally connected through. Contact the site s network administrator to determine the LAN port ethernet settings (see step 6). If transmission still fails, contact the Philips Response Center. Using Ping to Verify TraceMasterVue Server to PageWriter Trim Cardiograph Connectivity The ping command is a simple way to determine whether a device is accessible over a network. You must confirm communication from both ends of the line: from the cardiograph to the TraceMasterVue server, and from the server to the cardiograph. To ping the TraceMasterVue server from the PageWriter Trim cardiograph 1 Launch the service utility as follows: a Place the cardiograph in Off mode. NOTE Entering the Service Utility reboots the cardiograph. Any unsaved patient data will be lost. b c Press the On/Standby button to power on the unit. After approximately 20 seconds, the PageWriter Trim software identification screen appears, followed by an audible beep. Quickly, while the software identification screen is displayed, hold down the left CTRL and SHIFT keys together and press the Trim knob. NOTE The software identification screen disappears after five seconds. If you miss it, you must reset the cardiograph again. An Access Code window appears. If the Access Code window does not appear, try the left CTRL-SHIFT-Trim knob sequence again. Installing TraceMasterVue and Configuring Communication 9-17

266 Configuring PageWriter Trim Cardiographs for Use with TraceMasterVue d Type the access code. The factory default code is The Service Utility screen appears. 2 In the Diagnostic Tests dropdown list, select Network Ping, then select Start. 3 Enter the IP address of the TraceMasterVue server. A message appears indicating whether the ping was successful. If the ping is unsuccessful, see Table 9-1 on page 16. To ping the cardiograph from the server This procedure is the same for all cardiographs. Before proceeding, have available the IP address of the target cardiograph. 1 On the TraceMasterVue server, select Start > Run, and type cmd in the Run dialog box. 2 In the Command shell, type the following: ping <cardiograph IP address> For example, ping Installing TraceMasterVue and Configuring Communication

267 10 Chapter 10Configuring Legacy PageWriter XL- Series Cardiographs for Use with TraceMasterVue NOTE After configuring data communication on the TraceMasterVue end (both in terms of connecting and setting up hardware, and configuring settings on the server), you are now ready to connect and configure cardiographs. In addition, if you wish to use interactive query, you must also configure that functionality on the cardiographs. This chapter provides the following information: Connecting the Communication Hardware to a Legacy Cardiograph Before You Begin Configuring Remote Sites for Communication with Legacy Cardiographs Configuring a Remote Site for a Direct Connection Configuring a Remote Site for a Modem Connection Configuring Automatic Dialing to a Remote Site Configuring Locations and User Fields on Legacy Cardiographs Performing Interactive Queries Configuring Interactive Query on Legacy PageWriter XL-Series Cardiographs Testing the Connection Between the Cardiograph and the TraceMasterVue Server Troubleshooting Communication Issues between TraceMasterVue and Legacy PageWriter Cardiographs Perform the following steps, in order, to configure the cardiographs for communication with TraceMasterVue: 1 Connect the communication hardware, either direct serial connection or modem. 2 Configure remote sites. 3 Ensure interactive query is enabled, if appropriate. 4 Configure locations. 5 Configure user-defined fields. 6 Test communication between the systems. Some of the following procedures are provided here for your convenience. If necessary, refer to the cardiograph documentation for additional information. 10-1

268 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue Connecting the Communication Hardware to a Legacy Cardiograph Before You Begin If you are setting up a new TraceMasterVue system and associated cardiographs and devices, ensure you have already configured the TraceMasterVue system, as described in Chapters 1 through 7. If you are adding a cardiograph to an already operational TraceMasterVue system, have available all configuration information before proceeding. Refer to filled out worksheets and settings configured for other cardiographs, including locations, user fields, user ID, remote site number to use for this cardiograph, and the like. See Chapter 2, TraceMasterVue Communication Worksheets. Legacy PageWriter cardiographs can communicate with TraceMasterVue either using a direct serial connection or over a modem (page 10-6). To connect the cardiograph using the direct connection Connect the serial direct connection cable that is connected to TraceMasterVue (generally, via a junction box or wall plate) to the appropriate port on the back of the cardiograph. Cardiograph Junction box with connection to TraceMasterVue system Direct connect cable 10-2 Installing TraceMasterVue and Configuring Communication

269 Connecting the Communication Hardware to a Legacy Cardiograph To connect the cardiograph using a modem Refer to the figure below and perform the steps listed on the following page to install the modem. Cardiograph Modem power cord Phone line connector Modem data cable Modem 1 Turn the cardiograph to Standby. 2 Turn the modem power switch off. WARNING Equipment connected to the cardiograph s RS-232 connector can cause ground leakage current exceeding the maximum specified in UL544/IEC601-1 safety standards. Do not connect any equipment to the RS-232 connector during cardiograph operation when the patient cable is connected to a patient. NOTE NOTE Make sure that the battery level is sufficient to prevent any loss of configuration settings and software in the cardiograph when AC power is removed. Check the Battery Level indicator lights on the cardiograph key panel to ensure that they are all on. 3 Turn the cardiograph AC switch off. 4 Insert the larger connector end of the modem cable (24252M) into the RS-232C plug on the back of the modem, and tighten the retaining screws. 5 Insert the smaller end of the modem cable into the plug on the back of the cardiograph marked Data Comm, and tighten the retaining screws. Connect the modem to the cardiograph and to the telephone line in the following order. This will avoid the possible electrical hazards from the outlet and telephone line. 6 Plug the modem power cable into the plug on the modem marked 9.0V ~AC. 7 Plug the other end of the modem power cable into the cardiograph. 8 Insert either end of the telephone cable into the connector on the back panel of the modem marked To Line. Installing TraceMasterVue and Configuring Communication 10-3

270 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue 9 Insert the free end of the telephone cable into the telephone wall jack. 10 Plug the cardiograph power cable into the cardiograph and an AC outlet, if not already plugged in. 11 Turn the cardiograph AC power switch on. 12 Turn the modem on. 13 Turn the cardiograph on. The cardiograph is now connected and ready to be configured. Configuring Remote Sites for Communication with Legacy Cardiographs Once connected, you must configure the remote site associated with each connection. See the following sections for details: Configuring a remote site for a direct connection (page 10-4) Configuring a remote site for a modem connection (page 10-6) Configuring a Remote Site for a Direct Connection To configure a remote site for a direct connection 1 On the cardiograph, press the Menu key until the following options appear: Transmit Store Config CheckDisk Files 2 Press Config (F3). The main Configuration menu appears. Configuration Global ID Transmit Files Exit 3 Press Transmit (F3). The Transmit Configuration menu appears. Configuration Transmit Receive AutoDial Exit 4 Press Transmit (F1) to configure any of four transmission sites. The Configure Site menu appears. Configure Site #1 #2 #3 #4 Exit 10-4 Installing TraceMasterVue and Configuring Communication

271 Configuring Remote Sites for Communication with Legacy Cardiographs 5 Select an unassigned site number (1 4). The Connection menu appears. Direct is selected by default. Connection? Direct Enter Choose Previous Exit 6 Press Enter (F1) to select Direct as the connection option. The Baud Rate menu appears is selected by default. Baud rate? 9600 Enter Choose Previous Exit 7 Press Enter to select 9600 as the baud rate setting. When the Direct Connection option is selected, the default baud rate is The system returns you to the Configuration menu. 8 Once you are finished with all configuration tasks, press Exit to save the settings. The cardiograph is now configured to connect to the TraceMasterVue server as the assigned remote site. You now need to test the connection, as described on page Configuring a Remote Site for a Modem Connection When you specify the phone number for a site, you might need to insert one or more of the following options as part of the number:, (Pause key); w (Tone key); and X. A comma (,) inserts a pause in the number dialing sequence to avoid dialing errors if the number is sent too rapidly. You press the Pause key to enter a comma in the number. For example, the entry, 234,567,8900, instructs the modem to send the first three digits, 234, then wait for the specified length of time, then send the following three digits, 567, wait again, and finally, send the final four digits. Set the length of the pause using the Pause length parameter. A w instructs the modem to wait for a dial tone before completing the dialing sequence. You press the Tone key to enter a w in the number. You typically use this option when you must dial for an outside line before dialing the called number. For example, 9w567,8900 instructs the modem to dial the 9, then wait for a dial tone. An X instructs the modem not to wait for a dial tone. This might be required when you dial through a PBX system or with some non-u.s. modems. For example, X567,8900 instructs the modem not to wait for a dial tone before it dials the rest of the number. Installing TraceMasterVue and Configuring Communication 10-5

272 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue The following table lists the settings to choose when using a modem, as described in the following procedure. Each site may have its own requirements. Table 0-1 Parameter Choice Baud Rate? 9600 Connection? Phone #? Dial Type? Pause Length? Programmable Modem Phone number, 36 characters max. Tone, Pulse 2, 4, 6, 8, 10 (secs) To configure a remote site for a modem connection 1 On the cardiograph, press the Menu key twice until the following menu appears. Transmit Store Config CheckDisk Files 2 Press Config (F3). The main Configuration menu appears. Configuration Global ID Transmit Files Exit 3 Press Transmit (F3). The Transmit Configuration menu appears. Configuration Transmit Receive AutoDial Exit 4 Press Transmit (F1) to configure any of four transmission sites. The Configure Site menu appears. Configure Site #1 #2 #3 #4 Exit 5 Select an unassigned site number (1 4). The Connection menu appears. By default, the option is set to Direct. Connection? Direct Enter Choose Previous Exit 10-6 Installing TraceMasterVue and Configuring Communication

273 Configuring Remote Sites for Communication with Legacy Cardiographs 6 Press Choose (F2) until the option, Programmable Modem, appears. Connection? Programmable Modem Enter Choose Previous Exit 7 Press Enter (F1) to select this option. The Baud Rate menu appears is selected by default. Baud rate? 2400 Enter Choose Previous Exit 8 Press Choose (F2) until 9600 appears as the setting. 9 Press Enter (F1) to select the baud rate. The Phone Number menu appears. Phone number? Enter Pause (,) Tone (w) Previous Exit 10 Using the keypad, type the phone number for the modem line connected to the TraceMasterVue server. For details about the phone number options, see page If you make a mistake, use the arrow keys at the bottom right of the keypad and the backspace key to erase and re-type the number. 11 Press Enter (F1) to save the number. The Dial Type menu appears. Tone is selected by default. Dial type? Tone Enter Choose Previous Exit 12 To select Tone, press Enter (F1). To select Pulse, press Choose (F2) until the option, Pulse, appears; then press Enter (F1). The Pause Length menu appears. 2 seconds is the default setting. Pause length? 2 seconds Enter Choose Previous Exit 13 Press Choose (F2) to display the desired setting (2, 4, 6, 8, or 10 seconds); then press Enter (F1) to select it. The system returns you to the Configuration menu. 14 Once you are finished with all configuration tasks, press Exit to save the settings. The cardiograph is now configured to connect to the TraceMasterVue server as the assigned remote site. If you want to configure automatic dialing to a specified site upon pressing the Transmit button, proceed to the next section. Otherwise, you are ready to test the connection, as described on page Installing TraceMasterVue and Configuring Communication 10-7

274 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue Configuring Automatic Dialing to a Remote Site To configure the cardiograph for automatic dialing AutoDial is for users who always transmit to the same site. 1 On the cardiograph, press the Menu key until the following menu appears. Transmit Store Config CheckDisk Files 2 Press Config (F3). The main Configuration menu appears. Configuration Global ID Transmit Files Exit 3 Press Transmit (F3). The Transmit Configuration menu appears. Configuration Transmit Receive AutoDial Exit 4 Press AutoDial (F3). The Site Selection menu appears. None is selected by default. AutoDial site? None Enter Choose Previous Exit 5 Press Choose (F2) to display the site (1 4) to which the cardiograph will automatically transmit when the operator presses Transmit; then press Enter (F1) to select the site. 6 Press Choose to select the site (1 4) to which the cardiograph will automatically transmit when the operator presses Transmit; then press Enter. The system returns you to the Configuration menu. 7 Once you are finished with all configuration tasks, press Exit to save the settings. The cardiograph is now configured for expedited transmission to the specified site Installing TraceMasterVue and Configuring Communication

275 Configuring Locations and User Fields on Legacy Cardiographs Configuring Locations and User Fields on Legacy Cardiographs Because PageWriter XL-series cardiographs are already onsite and configured for use, this guide does not cover how to define the location and device codes, and user fields. All of these fields are defined in the Global settings on the cardiograph. If you need this information, refer to the documentation provided with the cardiograph. However, you must ensure that the location codes and definitions, as well as the user field (A and B) definitions on the cardiograph match those in TraceMasterVue. Use the worksheets to ensure a match. They are available in Chapter 2, TraceMasterVue Communication Worksheets. For further information about location matching and user fields, see Configuring TraceMasterVue and Device Location Fields on page B-2 and Configuring User-Defined Field Values in TraceMasterVue on page Performing Interactive Queries NOTE Interactive query refers to the ability to access ECGs stored in the TraceMasterVue database directly from a cardiograph. Interactive queries can be performed from Philips cardiographs, including PageWriterTouch, PageWriter Trim II and III, and PageWriter XL-series. You cannot access the TraceMasterVue database from the PageWriter Trim I cardiograph. For an interactive query, the cardiograph user selects the ECG to receive. The full ECG report (report and waveform) can be retrieved at the cardiograph. Both the cardiographs and TraceMasterVue must be configured to support interactive queries, as described in the following sections. For details on enabling interactive query on TraceMasterVue, see Configuring Interactive Query Support on TraceMasterVue on page 7-8. Configuring Interactive Query on Legacy PageWriter XL- Series Cardiographs Interactive query refers to the ability to access ECGs stored in the TraceMasterVue database directly from a cardiograph. Interactive queries can be performed from Philips cardiographs, including PageWriterTouch, PageWriter Trim, PageWriter XL, and so on. Both the cardiographs (with the exception of legacy cardiographs) and TraceMasterVue must be configured to support interactive queries. In general, legacy cardiographs are already configured for interactive query use. If for some reason this feature is not enabled, refer to the user or configuration documentation provided with the cardiograph. Installing TraceMasterVue and Configuring Communication 10-9

276 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue Testing the Connection Between the Cardiograph and the TraceMasterVue Server To test the connection to the TraceMasterVue server 1 On the cardiograph, insert a diskette containing some ECGs to transmit to the TraceMasterVue system. 2 Press the Menu key twice until the following menu appears. Transmit Store Config CheckDisk Files 3 Press Transmit. The Transmit menu appears. Transmit Selected All New Group Query Exit 4 To transmit all of the ECGs on the diskette, choose All (F2). The cardiograph selects all of the ECGs and transmits them to the configured site. 5 To transmit selected ECGs from the diskette: a Press Selected (F1). The cardiograph reads the contents of the diskette and prompts you to select the ECG(s) to transmit. The illustration below shows a sample ECG heading. Half STD 12/08/04 09:26:02AM Select Transmit Next Previous More b Use the Next (F3) and Previous (F4) buttons to navigate the ECGs on the diskette. When an ECG you want to transmit is listed, press Select (F1). An asterisk appears to the left of a selected ECG s name. * Half STD 12/08/04 09:26:02AM Select Transmit Next Previous More c d To select additional ECGs, repeat step b until all ECGs to transmit are selected. Press Transmit (F2) to send the ECGs to the configured site. 6 Verify on the cardiograph that the ECGs were successfully transmitted. 7 On TraceMasterVue, verify that the ECG(s) were successfully received and stored using one or more of the following methods: Installing TraceMasterVue and Configuring Communication

277 Troubleshooting Communication Issues between TraceMasterVue and Legacy PageWriter Cardiographs If a workflow rule is set to print new incoming ECGs, a report should print for each ECG that was successfully transmitted. Start up ECGVue and conduct a search for the transmitted ECGs. If the transmission fails: Verify that your connection and configuration settings are properly set, both on the cardiograph and on TraceMasterVue. Ensure that you rebooted the TraceMasterVue server after making all the configuration changes to connect cardiographs. Run the DCMonitor application, located in TraceMasterVue\EMS Server\bin\DCMonitor.exe. Then, transmit an ECG and review the entries in the DCMonitor window. Verify that the modem answering the transmission call is the intended modem. It is possible you might be attempting to connect to the RAS modem. Troubleshooting Communication Issues between TraceMasterVue and Legacy PageWriter Cardiographs As you configure the communication between the cardiographs and TraceMasterVue, and test each connection, you may encounter some problems with the configuration. The following section describes some of the more common symptoms and provides information regarding possible causes, and solutions to help you solve potential problems. Follow the steps outlined below in the order shown. The following suggestions assume that you have tested ECG transmission between the cardiograph and TraceMasterVue and it failed. Table 10-1 Legacy PageWriter /TraceMasterVue communication issues What to do... Next steps... 1 Check all hardware connections. If any cables are loose, re-attach them and test transmission again. If transmission fails, proceed to step 2. 2 For direct connect: a Verify the baud rate. Should always be set to b Verify cable connections. c Run the DCMonitor application, located in TraceMasterVue\EMS Server\bin\DCMonitor.exe. Then, transmit an ECG and review the entries in the DCMonitor window. Verify that the COM port is correctly configured for this cardiograph, ensuring that no other program has reserved the port (for example, RAS or FAX). See Configuring COM Ports on page 4-7 and Configuring Remote Sites for Communication with Legacy Cardiographs on page Installing TraceMasterVue and Configuring Communication 10-11

278 Configuring Legacy PageWriter XL-Series Cardiographs for Use with TraceMasterVue Table 10-1 Legacy PageWriter /TraceMasterVue communication issues (continued) What to do... Next steps... 3 For modem connection: a Verify that the transmitting and receiving modems are connected to a power supply, and verify cable connections. b Verify the baud rate. Should always be set to c d e f Verify that supported modems are connected and the appropriate drivers are installed. Verify that the cardiograph is dialing the correct phone number and the correct modem (the receiving modem should ring). Verify that the phone line is connected to the proper connector on the modem (Line or Jack, NOT Phone). Run the DCMonitor application, located in TraceMasterVue\EMS Server\bin\DCMonitor.exe. Then, transmit an ECG and review the entries in the DCMonitor window. Verify that the COM port is correctly configured for this cardiograph, ensuring that no other program has reserved the port (for example, RAS or FAX) Installing TraceMasterVue and Configuring Communication

279 11 Chapter 11Configuring the ECGVue Training System The TraceMasterVue system ships with a browser-based (HTML) tutorial for ECGVue users. The tutorial comprises seven modules, each of which can be completed at any time. This appendix provides the following information: About the ECGVue Tutorial Demo ECG Characteristics Location of the Tutorial Files Running the ECGVue Tutorial Resetting the Demo ECGs About the ECGVue Tutorial The ECGVue tutorial is a set of HTML files that can be accessed through any browser. Figure 11-1 Tutorial Table of Contents 11-1

280 Configuring the ECGVue Training System Figure 11-2 Tutorial content page example Click to display Table of Contents Quick links to the rest of this module Click to go to next and previous page of this module Quick links to next module Main lesson content Exercises to try Demo ECG Characteristics The Demo ECGs in the system have the following distinguishing characteristics: The patient ID is preceded by three dollar signs ($$$) The institution code is 999 These symbols make it easy to distinguish the demo data from your live patient ECGs Installing TraceMasterVue and Configuring Communication

281 Location of the Tutorial Files Location of the Tutorial Files The tutorial files are stored in the Help directory, within the EMS Client folder, as follows: C:\TraceMasterVue\EMS Client\bin\Help\ClientHelp\Tutorial The main table of contents and the primary entry point for the tutorial is the file TOC_Training.htm. TraceMasterVue provides scripts that refresh the database with new, untouched ECGs. The demo ECGs and the scripts are stored in TraceMasterVue\Training, as follows: TraceMasterVue\Training\ECGs This directory contains demo ECGs in XML format. The tutorial files make reference to specific elements of these ECGs. TraceMasterVue\Training\Scripts Scripts used to refresh the database: InsertDemoECGs.bat, RemoveDemoECGs.bat, and ResetDemoECGs.bat CAUTION Do not move or modify these files! The demo ECGs in the ECGs folder are untouched, and will be used to refresh the training database. If you modify these files directly in this folder, you will not be able to restore the training database to a default factory-fresh state for use with the tutorial. Running the ECGVue Tutorial You can access the tutorial files from within the ECGVue online help system or directly off the server. To access the tutorial from the online Help 1 In ECGVue, click Help. 2 On the Content page, click the Run the Tutorial link. The Using the Tutorial page opens. 3 Click the Start the Tutorial link. The Tutorial table of contents page opens. To access the tutorial files directly on the server 1 Navigate to the tutorial folder: TraceMasterVue\EMS Client\bin\Help\ClientHelp\Tutorial 2 Double-click the file TOC_Training.htm. The Tutorial table of contents page opens. Installing TraceMasterVue and Configuring Communication 11-3

282 Configuring the ECGVue Training System Resetting the Demo ECGs Demo ECGs are provided as part of the TraceMasterVue database. After a user modifies the demo ECGs as part of the training exercises, you must reset the ECGs to their default state so the next user can start with a fresh set. CAUTION Do not move or modify the demo ECGs! The demo ECGs in the ECGs folder are untouched, and will be used to refresh the training database. If you modify these files directly in this folder, you will not be able to restore the training database to a default factory-fresh state for use with the tutorial. TraceMasterVue provides scripts that refresh the database with new, untouched ECGs. The scripts are stored in TraceMasterVue\Training\Scripts. InsertDemoECGs.bat inserts ECGs into the database. RemoveDemoECGs.bat deletes the demo ECGs from the database. ResetDemoECGs.bat removes the demo ECGs and reinserts a fresh set. You will use this script most often. To insert the ECGs into the database for the first time Run InsertDemoECGs.bat to inject the ECGs into the database. This script assumes that the ECGs are not yet in the database. To remove ECGs from the database Run RemoveDemoECGs.bat to remove the set of demo ECGs from the TraceMasterVue database. You might use this script to remove the demo ECGs from the database once all your users have completed training. To reset the demo ECGs in the database Run ResetDemoECGs.bat to remove the set of demo ECGs from the TraceMasterVue database (if present) and insert the fresh untouched demo ECGs Installing TraceMasterVue and Configuring Communication

283 A Appendix LAbout TraceMasterVue Users and Groups NOTE This appendix provides detailed information about TraceMasterVue users and groups, as well as security roles and interaction with Active Directory. If the customer has a policy of clearing off all factory-specified configuration information, user IDs and groups, and the like, make sure you review the section, User-Related Requirements for Running TraceMasterVue on page A-3 before proceeding. Certain user IDs, groups, user/group associations, and services must be present and configured for TraceMasterVue to run and function properly. If your customer does not harden their systems, you just need to add users to the appropriate TraceMasterVue groups. See Associating Users with TraceMaster Groups on page This appendix provides the following information: About the TraceMasterVue Security Model A-2 Overview of Methods A-2 About the Authorization Process A-2 About Windows Users and TraceMasterVue-Specific Groups A-2 User-Related Requirements for Running TraceMasterVue A-3 About TraceMasterVue Users A-4 Users Required on the TraceMasterVue Server A-5 About TraceMasterVue-Specific Windows Groups A-7 TraceMasterVue Groups and Associated Permissions A-8 Groups Required on the TraceMasterVue Server A-11 Required User-Group Associations A-13 About Database User IDs A-15 Required Database User IDs A-15 Changing User Permissions Using Security Roles A-15 Process for Defining Security Roles A-16 Security Role Examples A-16 Security Role Examples A-17 Examples of Making Access to Specific ECGs More Broad..... A-17 Example of Making Access to Specific ECGs More Restrictive.. A-18 Interaction with Active Directory A-19 About Users and Groups on the TraceMasterVue Server and in Active Directory A-19 Common Active Directory Use Models with TraceMasterVue A-20 A-1

284 About TraceMasterVue Users and Groups About the TraceMasterVue Security Model TraceMasterVue controls access to ECGs using two primary methods: Windows user IDs and group permission settings TraceMasterVue-specific permission settings and security roles For detailed information about using security roles, as well as using roles with Active Directory, see Changing User Permissions Using Security Roles on page A-15 and Interaction with Active Directory on page A-19. For the TraceMasterVue groups/permissions table, see Table A-4, TraceMasterVue groups and associated permissions, on page A-8. Overview of Methods NOTE TraceMasterVue uses the existing Windows user ID and password to authenticate users when logging into the application. It also uses the permissions set for the TraceMasterVue-specific Windows group to which the user belongs to determine, at a high level, which ECGs a particular user has access to. By default, Windows Server 2003 does not allow any users outside of the Administrator group to physically log into the server system. Thus, if, for example, a technician who is a member of a different Windows group were to physically walk up to the TraceMasterVue server and attempt to log on (to the Windows operating system) they would not be able to. You can configure the server to allow nonadministrators to log on locally, but this ability is prevented by default for security reasons. All users who will be logging into the TraceMasterVue system must be members of one or more TraceMasterVue-related Windows groups. About the Authorization Process When a user requires authorization for a task, for example, to confirm an ECG, TraceMasterVue first checks whether a security role is defined for the logged-in user. If no security record is found (that is, additional access permissions were not specified for this user), TraceMasterVue uses only the authorization settings specified for the Windows group to which the user belongs. About Windows Users and TraceMasterVue-Specific Groups The TraceMasterVue server runs on the Microsoft 2003 Server operating system. All users must first log into Windows before gaining access to TraceMasterVue applications, including the client application. TraceMasterVue uses Windows user IDs and TraceMaster-specific Windows group affiliations to determine access permissions. When setting up the TraceMasterVue system, it is recommended that you configure any new user IDs first, then add users to the TraceMaster groups. A-2 Installing TraceMasterVue and Configuring Communication

285 About Windows Users and TraceMasterVue-Specific Groups NOTE When you add a new user or make changes to an existing user, including changing access/security permissions, it can take up to 10 minutes for the changes to propagate through the system and become effective. To make the changes effective immediately, restart IIS. You must also stop and restart TraceMasterVue services. See Chapter 8, System Operation and Maintenance in the TraceMasterVue System Configuration and Reference Guide. The following sections tell you about users and groups, as well as how to add and configure them: User-Related Requirements for Running TraceMasterVue on page A-3 About TraceMasterVue Users on page A-4 About TraceMasterVue-Specific Windows Groups on page A-7 In addition to Windows users, TraceMasterVue also requires the presence of two database user IDs. See About Database User IDs on page A-15. User-Related Requirements for Running TraceMasterVue TraceMasterVue ships with a default set of users and groups, and associations between the two, that are necessary for the system to operate. Whether you are at a site where the customers harden any system at their facility by removing factory-installed settings and configuring their own settings, or whether you are adding or modifying entries, it is important to know which elements are essential to the operation of the system. The following table provides an overview of the users and groups, as well as the associations between the two, that must be present on the system in order for it to operate properly. For each item, the table lists the section to go to for detailed information. Table A-2 Required settings for running TraceMasterVue Required Components Description For details, see... Windows users Windows groups User/group correlations Database users TraceMasterVue uses Windows user IDs and TraceMasterVue-specific Windows group affiliations to determine access permissions. The system ships with a default set of users installed; this set must remain on the system. The system ships with a default set of groups installed; this set must remain on the system. Certain user IDs must be associated with specific groups for the system to function correctly. SQL Server 2000 requires two specific database users associated with TraceMasterVue; these users must remain on the system. Users Required on the TraceMasterVue Server on page A-5 Groups Required on the TraceMasterVue Server on page A-11 Required User-Group Associations on page A-13 About Database User IDs on page A-15 Installing TraceMasterVue and Configuring Communication A-3

286 About TraceMasterVue Users and Groups About TraceMasterVue Users NOTE This section assumes that you are familiar with the Windows 2003 Server operating system and understand Windows users and groups. For details, see the online help system provided with the operating system, accessible through the Start menu. The ECG viewer/editor, ECGVue or PharmaVue, uses standard Windows user IDs to determine access permission. You configure and maintain user accounts using the Windows 2003 Server Users and Groups Manager. To access the Windows Users and Groups Manager Use either of the following methods: Click Start > Administrative Tools > Computer Management > Local Users and Groups. In the TraceMasterVue System Configuration utility, click the System Administration tab, then click Launch Windows User Manager. For help adding users, refer to the Windows 2003 Server online help system, accessible through the Start menu. To view the list of users on your system 1 Display the Users and Groups window as described in To access the Windows Users and Groups Manager on page A-4. The Local Users and Groups window appears. 2 Click the Users folder in the left pane. The users defined on your system are listed in the right pane. A-4 Installing TraceMasterVue and Configuring Communication

287 About Windows Users and TraceMasterVue-Specific Groups Windows users defined on the system Users Required on the TraceMasterVue Server The following table shows the Windows users that are defined on the server at shipment. These user IDs are shipped with the system by default, and are required for TraceMasterVue operation. Two database user IDs must also remain configured. See About Database User IDs on page A-15. You only need to reconfigure this information if the customer has a policy of clearing off all factory-specified configuration information, user IDs and groups, and the like. Certain user IDs, groups, user/group associations, and services must be present and configured for TraceMasterVue to run and function properly. Passwords are not provided in this document (except for the tutorial user). Ensure you have them available before proceeding with configuration. CAUTION Changing the permissions, password, or configuration of any of these users, or removing them from the system will result in suboptimal- or non-performance of some or most of the TraceMasterVue functionality. Installing TraceMasterVue and Configuring Communication A-5

288 About TraceMasterVue Users and Groups Table A-3 Required Windows users configured on the TraceMasterVue server User ID Password Description TraceMasterVue-specific Users PMDExport PMDAppSrv PHSUPPORT Used for IntelliVue support if you have the IntelliVue Information Center connectivity option (#C20). See Appendix E, Using TraceMasterVue with the IntelliVue Information Center. Used for IntelliVue support if you have the IntelliVue Information Center connectivity option (#C20). See Appendix E, Using TraceMasterVue with the IntelliVue Information Center. User for remote support access. NOTE This user is defined on the local system, and is associated with the TraceMaster_SysAdmin group. If you are using Active Directory, do not associate this user with any AD group. Training Learning Used for the client application tutorial; used for general demo and training TrainingOverreader Learning Used for the client application tutorial; used for COBO training. Windows Server 2003 Users Administrator ASPNET Guest IUSR_PHILIPS-JL6H07A IWAM_PHILIPS- JL6H07A SQLDebugger SUPPORT_388945a0 Built-in account for administering the computer/domain. ASP.NET machine account. Used for running the ASP.NET worker process (aspnet_wp.exe). Built-in account for guest access to the computer/domain. Internet Guest Account. Built-in account for anonymous access to Internet Information Services. Built-in account for Internet Information Services to start out of process applications. SQL Debugger Vendor s account for the Help and Support Service. A-6 Installing TraceMasterVue and Configuring Communication

289 About Windows Users and TraceMasterVue-Specific Groups About TraceMasterVue-Specific Windows Groups When installing TraceMasterVue at a site, the appropriate TraceMasterVue groups must be configured. They are used by the TraceMasterVue applications to determine individual users access permissions. When a user requires authorization for a task, for example, to confirm an ECG, TraceMasterVue first checks whether a security role is defined for the logged-in user. If no security role is found (that is, additional access permissions were not specified for this user), TraceMasterVue uses the authorization settings specified for the Windows group to which the user belongs. These groups are automatically configured when TraceMasterVue is installed on the server. However, you must still associate individual users with one or more groups. Only users that are part of a TraceMasterVue group can log into TraceMasterVue applications, including the client. The TraceMasterSysAdmin group has the broadest permissions, authorized to access all modules and perform all functions, including customizing the system and configuring security. It is the responsibility of the system administrator to maintain Windows users, passwords, group associations, and local application security policies. WebAPI option only. If you have this option, your system has an additional TraceMaster group, WebAPI. Only IDs associated with this group will be granted access using the API; that is, any application attempting to access ECGs in the database must use a valid user name/password combination, and the user ID must be a member of the WebAPI group. Installing TraceMasterVue and Configuring Communication A-7

290 About TraceMasterVue Users and Groups TraceMasterVue Groups and Associated Permissions The TraceMasterVue installation program automatically configures the following Windows groups as part of the setup process. You do not have to make any changes to these group settings after installation. Table A-4 TraceMasterVue groups and associated permissions TraceMasterVue-specific Windows Group Name TraceMaster_SysAdmin TraceMaster_IT TraceMaster_Manager Description System Administrator. Highest security level IT group. Users that allocate resources and determine system platforms, system support, and maintenance. Manager. May not generally use the system directly, but their technicians will be primary users. As resources and daily routines evolve, ECG Department Managers have a key role to play in the features of the system. Permission Overview Typically, there is only one SA-level password on the system. The SA must be a technically competent person who thoroughly understands the system architecture and software, as well as the Windows operating system. You must be a member of the SysAdmin group to be able to access TraceMasterVue server-side utilities, such as System Configuration, Statement Manager, and the like. Has access to all TraceMasterVue modules Able to perform all functions View ECGs using the client Back up and restore the TraceMasterVue system View, edit, print/fax, and delete ECGs using the client Delete patients from the database; Import/export ECGs using the client Run Management reports using TraceMasterVue Management Reports utility Back up the TraceMasterVue system A-8 Installing TraceMasterVue and Configuring Communication

291 About Windows Users and TraceMasterVue-Specific Groups Table A-4 TraceMasterVue groups and associated permissions (continued) TraceMasterVue-specific Windows Group Name TraceMaster_Tech TraceMaster_HeadTech TraceMaster_RefPhys TraceMaster_ConfCardio TraceMaster_RevCardio Description Technician. Has access to the basic set of functions necessary to operate the client. In general, the technician enters edits of the reviewing cardiologist, and makes changes to patient records in case of incompleteness or error. Head Tech. Has access to a more limited set of functions than the system administrator. The Head Tech can perform routine maintenance procedures. Referring Physician. Needs access to results and diagnosis of ECGs after confirmation by a cardiologist. Confirming Cardiologist. Needs access to new (unconfirmed) ECGs that have been assigned to them to overread, and then confirm. Reviewing Cardiologist. Reviews ECGs, but cannot confirm them. Primarily used in a teaching environment where residents might be reviewing ECGs, and then passing their comments along to a confirming cardiologist. Permission Overview View, edit, and print/fax ECGs using the client Perform serial comparison on ECGs using the client Import/export ECGs using the client Can perform most functions using the client, including viewing, editing, and printing ECGs Run Management reports using TraceMasterVue Management Reports utility Cannot confirm ECGs or delete patients View and print/fax ECGs using the client Can perform all editing, comparison, and confirming functions using the client View, edit, print/fax, and assign ECGs using the client Perform serial comparison on ECGs using the client Import/export ECGs using the client Installing TraceMasterVue and Configuring Communication A-9

292 About TraceMasterVue Users and Groups Table A-4 TraceMasterVue groups and associated permissions (continued) TraceMasterVue-specific Windows Group Name TraceMaster_Verifier TraceMaster_COBO TraceMaster_WebAPI NOTE Available only with the WebAPI option. TraceMaster_Guest Description Verifying technician. Reviews demographic information on ECGs. Primarily used in a Pharma environment, where a technician ensures that the demographic information is correct before passing ECGs to be overread. Confirm on Behalf of. Users can confirm an ECG on behalf of a confirming cardiologist. WebAPI user. Provides access to the database using the provided API. Only IDs associated with this group are granted access to the database using the API. Can run the client and have readonly access to ECGs. Permission Overview View, print/fax, assign, verify, and edit demographic (but not measurement or interpretive) information using the client Confirm ECGs using the client NOTE This is a secondary group that only has confirm permissions all users in this group must also belong to another TraceMasterVue-specific group to be able to retrieve, view, and work with ECGs. Can access ECGs in the TraceMasterVue database using the provided API. View ECGs using the client NOTE Table A-5 The following table shows the exact permissions granted to each of these groups. The TraceMaster_None group is not shown in the table; this group has no access permissions. It is provided so that you can define very specific, limited access to ECGs for a user assigned to this group. For details, see the TraceMasterVue Installation and Configuration Guide. Summary of TraceMasterVue group access permissions System Admin IT ECG Mgr ECG Head Tech ECG Tech Referring Physician Confirming Cardiologist Reviewer Verifier COBO WebAPI ** Guest None View X X X X X X X X X X Edit demographics X X X X X X X Verify ECG X X X X X X X Edit ECG X X X X X X Delete ECG X X X X Delete patient X X X A-10 Installing TraceMasterVue and Configuring Communication

293 About Windows Users and TraceMasterVue-Specific Groups Table A-5 Summary of TraceMasterVue group access permissions (continued) System Admin IT ECG Mgr ECG Head Tech ECG Tech Referring Physician Confirming Cardiologist Reviewer Verifier COBO WebAPI ** Guest None Confirm X X Unconfirm X X X X /print/fax report X X X X X X X X X Assign X X X X X X X Mgmt reports X X X Serial compare X X X X X Backup X X X Restore X X Import/Export X X X X X X X Enterprise Mgr Export X WebAPI access ** X Server-side utilities X ** Available only with the WebAPI option. Groups Required on the TraceMasterVue Server The following table shows the Windows groups that are defined on the server at shipment. These groups are shipped with the system by default, and are required for TraceMasterVue operation. CAUTION Removing the TraceMaster-specific groups from the system will result in non-performance of some or most of the TraceMasterVue functionality. Users must be a member of a TraceMaster-specific group to be able to use TraceMasterVue applications, including PharmaVue. Table A-6 Required Windows groups configured on the TraceMasterVue server Group Name Administrators Backup Operators Guests Members of this group have the following permissions... Have complete and unrestricted access to the computer/ domain. Have the ability to override security restrictions for the sole purpose of backing up or restoring files. Have the same access as members of the Users group, except for the Guest user account, which is further restricted. Installing TraceMasterVue and Configuring Communication A-11

294 About TraceMasterVue Users and Groups Table A-6 Required Windows groups configured on the TraceMasterVue server Group Name Network Configuration Operators Performance Log Users Performance Monitor Users Power User Print Operators Remote Desktop Users Replicator Users HelpServicesGroup IIS_WPG TelnetClients TraceMaster_COBO TraceMaster_ConfCardio TraceMaster_Guest TraceMaster_HeadTech TraceMaster_IT TraceMaster_Manager Members of this group have the following permissions... Have some administrative privileges to manage configuration of networking features. Have remote access to schedule logging of performance counters on this computer. Have remote access to monitor this computer. Have most administrative powers with some restrictions; they can run legacy applications, in addition to certified applications. Can administer domain printers. Can log into the system remotely. Support file replication in a domain. Can run certified applications, but not most legacy applications; they are prevented from making system-wide changes. Group for the Help and Support Center. IIS Worker Process group. Have access to Telnet Server on this system. For a description of the TraceMaster groups, see About TraceMasterVue-Specific Windows Groups on page A-7. ** The TraceMaster_WebAPI group is for use only with the WebAPI option. TraceMaster_None TraceMaster_RefPhys TraceMaster_RevCardio TraceMaster_SysAdmin TraceMaster_Tech TraceMaster_Verifier TraceMaster_WebAPI ** A-12 Installing TraceMasterVue and Configuring Communication

295 About Windows Users and TraceMasterVue-Specific Groups Figure 1 Default groups shipped on TraceMasterVue Required User-Group Associations Upon shipment of the system, the following associations are set between users and groups on the TraceMasterVue system; these relationships must be maintained in order for the system to function correctly. CAUTION Removing the TraceMaster-specific groups from the system or removing any of the listed users from the associated group will result in non-performance of some or most of the TraceMasterVue functionality. Table A-7 Required user-group associations User Name Administrator ASPNET Guest IUSR_PHILIPS-JL6H07A IWAM_PHILIPS-JL6H07A Groups Administrators TraceMaster_SysAdmin Users Guests Guests IIS_WPG Installing TraceMasterVue and Configuring Communication A-13

296 About TraceMasterVue Users and Groups Table A-7 User Name Required user-group associations (continued) Groups PHSUPPORT PMDAppSrv PMDExport SQLDebugger SUPPORT_388945a0 Training Training Overreader Administrators Remote Desktop Users TraceMaster_SysAdmin Users TraceMaster_Tech Users Users HelpServicesGroup TraceMaster_COBO TraceMaster_HeadTech Users TraceMaster_ConfCardio Users For additional information about configuring users and TraceMasterVue groups, refer to Configuring TraceMasterVue Users and Groups in the TraceMasterVue System Configuration and Reference Guide. A-14 Installing TraceMasterVue and Configuring Communication

297 About Database User IDs About Database User IDs TraceMasterVue uses SQL Server 2000 as a database engine. Two database user IDs associated with TraceMasterVue must be left unmodified on the system. CAUTION Removing either of these users from the system will result in non-performance of some or most of the TraceMasterVue functionality. Required Database User IDs The following user IDs are required for database access. Passwords are not included here for security reasons. Have available the passwords before proceeding. Table A-8 Required database users User ID sa viper Password These passwords are stored as encrypted strings in the TraceMasterVue registry. You can have the password changed, if desired. To change the database user password(s) Contact Philips Medical Systems support. Changing User Permissions Using Security Roles If your site requires a greater level of access control than is possible with the all-or-none approach of the Windows Group settings, you can specify additional access restrictions for specific users or a group of users. Security roles are designed to be used only when you need to restrict access to ECGs for individuals or a group of users. Groups can also be associated with specific locations. TraceMasterVue allows you to restrict access based on various factors, including acquiring location (from the institution down to the department level), ECG source, ECG type, patient ID, and patient type. For example, if multiple organizations are sharing a single TraceMasterVue system, you will most likely define multiple institutions, one for each organization, each with its own set of facilities and departments. If the organizations do not want to share patient information, you must define and configure a security role for each user (or group) within each organization to have access only to ECG records associated with the institution configured for that organization. For example, if Institution A and Institution B are both using a single TraceMasterVue system, you must configure all users at Institution A with a security role that gives them access only to Installing TraceMasterVue and Configuring Communication A-15

298 About TraceMasterVue Users and Groups ECGs originating at Institution A; similarly, you must configure all users at Institution B with a role that gives them access only to ECGs originating at that institution. You define these roles using a combination of TraceMaster groups and the System Configuration utility, on the Security Roles tab. NOTES If you use the COBO (confirm on behalf of) TraceMaster group and Active Directory, refer to the section, Interaction with Active Directory on page A-19 for configuration details. After adding a new user or group, or making changes to an existing user or group, including changing access/security permissions, restart IIS. You must also stop and restart TraceMasterVue services. See Chapter 8, System Operation and Maintenance. Process for Defining Security Roles There are basically two main approaches for defining roles: Additive. With this method, users for whom to define more restrictive access are first associated with the TraceMaster_None group, giving them no access to any ECGs. You then create one or more roles to grant access to just the desired ECGs and roles (for example, Head Technician). This approach is appropriate for granting access to a small subset of ECGs. Subtractive. With this method, users for whom to define more restrictive access are first associated with the regular TraceMaster group that provides the desired level of functional access (for example TraceMaster_HeadTech). You then create one or more roles to specify the conditions under which the user does not have access (for example, specify the institution to which a user should not have access) and select the No Permissions role. This approach is appropriate for restricting access to a small subset of ECGs. Security Role Examples The following examples illustrate both approaches. Additive Example Give the user JohnB confirmation-level access only to ECGs that are associated with Institution 1 and Facility 2. 1 Associate the user JohnB with the TraceMasterVue-specific Windows group, TraceMaster_None. This group removes all permissions from associated users, allowing you to add very specific access to the database. For details, see About TraceMasterVue-Specific Windows Groups on page A-7. 2 In the Add Security Role dialog box, select the following fields: Institution: Institution 1 Facility: Facility 2 Role: Confirming Cardiologist A-16 Installing TraceMasterVue and Configuring Communication

299 Changing User Permissions Using Security Roles Subtractive Example Prevent the confirming cardiologist user JohnB from being able to view ECGs from Institution 1, Facility 2. 1 Associate the user JohnB with the TraceMasterVue-specific Windows group, TraceMaster_ConfCardio. This group provides associated users with confirming cardiologist rights. For details, see About TraceMasterVue-Specific Windows Groups on page A-7. 2 In the Add Security Roles dialog box, select the following fields: Institution: Institution 1 Facility: Facility 2 Role: No permissions This role serves the same function as the TraceMaster_None group. When selected in the Security Roles dialog box, it applies just to the ECGs that match the other specified criteria. For details about defining roles, see Configuring Security Roles on page Security Role Examples You can both enlarge a user s access to ECGs or restrict access, depending on the group you select in the Role section of the Add/Edit Security Role dialog box. The effect of the role you choose is directly related to the TraceMaster-specific group the user already belongs to, as well. For permission details, see TraceMasterVue Groups and Associated Permissions on page A-8. Examples of Making Access to Specific ECGs More Broad If you have a user that you want to have access only to a very limited set of ECGs, consider first associating the user s ID with the group TraceMaster_None. This group has no access at all, not even view permission. Adding the ID to this group, however, makes the ID available in the Add Security Role dialog box User ID field. You can now specify the subset of ECGs that this user will have access to, select the user ID, and in the Role section, select the group that has the desired permissions (view, edit, and/or confirm). Now this user will be able to perform the approved actions on only those ECGs that match the criteria specified in the Signature section. If you have a user that you want to give broader permissions to for a subset of ECGs, use the Add Role dialog box to define a security role as follows: Specify the criteria for ECGs that the user will have additional privileges for. Specify the user ID. Installing TraceMasterVue and Configuring Communication A-17

300 About TraceMasterVue Users and Groups Select the group that has the desired permissions (view, edit, and/or confirm). For the ECGs that match the criteria, this user will have the permissions associated with the role selected here. For all other ECGs, this user will have the permissions associated with the TraceMaster group s/he is already associated with. Example of Making Access to Specific ECGs More Restrictive To allow users at a particular institution to have access only to ECGs within that institution, use the Add Role dialog box to define a security role for each TraceMasterVue user at that institution as follows: Select the institution to which the user has access. Specify the user ID to associate with this role. Select the role for this user. Once set, the specified user will have the permissions associated with the selected role for all ECGs associated with the selected institution. The user will not have access to ECGs from other institutions. To grant a user access only to ECGs from a particular facility, do the following: a b Associate the user with the TraceMaster_None Windows group. See Associating Users with TraceMaster Groups on page In the Add Role dialog box: Specify the facility to provide access to. Specify the user ID. Choose the role that has the desired access permissions. Once saved, this user will be able to perform the actions associated with the selected role only for ECGs acquired in the selected facility; the user will not be able to view any other ECGs. To prevent a user from having access to a subset of ECGs, use the Add Role dialog box to define a security role for each TraceMasterVue user at that institution as follows: Select the patient ID to remove access to. Specify the user ID. Select a role that has lesser permissions than the TraceMaster group to which the user already belongs. For example, if the user is a member of the TraceMaster_ConfCardio group, which can confirm ECGs, but you do not want him to be able to edit ECGs for a particular patient, select a group that does not have edit permissions, for example TraceMaster_Guest. This user will be able to edit and confirm all ECGs except for those associated with the listed patient. A-18 Installing TraceMasterVue and Configuring Communication

301 Interaction with Active Directory Interaction with Active Directory TraceMasterVue users and groups can be integrated with an Active Directory (AD) installation. You configure settings at a network level and at the application level. For detailed information about AD configuration, refer to the documentation provided with Active Directory. To integrate TraceMasterVue into your Active Directory Domain 1 Add the computer hosting the TraceMasterVue server to the Active Directory domain by adding it to the computer list on the Active Directory server. 2 Add the TraceMasterVue server machine to the Active Directory domain via computer properties. NOTE For Philips remote support, you must add the PHSUPPORT user to the TraceMaster_SysAdmin group, either locally or globally, depending on how you implement Active Directory at your site. About Users and Groups on the TraceMasterVue Server and in Active Directory It is important to understand the difference between local (on the TraceMasterVue server) vs. global (in Active Directory) users and groups, as it affects how users can interact with the TraceMasterVue system. Local user Global user User that is defined on the TraceMasterVue server host machine. This user may not have access to other systems. A local user is associated with a local TraceMasterVue group to determine application access and permissions. For example, John Smith is a user added to the TMVue server machine, and is associated with the TraceMaster_ConfCardio group. He has all the privileges that are associated with that group, including viewing, editing, confirming, and deleting ECGs. User that is defined in the Active Directory service. This user has access to all systems to which he is given permissions in Active Directory. A global user can be associated with either a local TraceMasterVue group or to a global group to determine application access and permissions. For example, you can associate an AD user, Elizabeth Card, to a TraceMaster group on the server, TraceMaster_Tech or to an AD group, HospitalTechGroups. If associating with an AD group, that group (in this example, HospitalTechGroups) is then associated with a TraceMaster group (in our example, TraceMaster_Tech). Installing TraceMasterVue and Configuring Communication A-19

302 About TraceMasterVue Users and Groups Local group Global group Group that is defined on the TraceMasterVue server host machine. You can associate local, as well as global, users to this group. You can also associate global groups to a local group. Group that is defined in AD. This group is added to a TraceMaster group on the TraceMasterVue server. This implies that all the users associated with this group have the rights of the associated TraceMaster group. Common Active Directory Use Models with TraceMasterVue There are a few common models for using Active Directory with TraceMasterVue: 1 No AD use. All users and groups are managed on the TraceMasterVue server. 2 Define users in AD and associate them with local TraceMaster groups 3 Define users in AD and associate them with a global non-tracemaster group in AD, then associate the global group with a local TraceMaster group 4 Define users in AD and associate them with global TraceMaster groups defined in AD 5 Define users in AD and associate them with a global non-tracemaster group in AD, then associate the global non-tm group with global TraceMaster groups defined in AD Table A-1 Use Model Examples of configuring users and groups with Active Directory Examples 1 User and assigned groups on TraceMasterVue server TMVue Local Security Members of TraceMaster_Tech group: TMV: Sam Elliot, hospital tech (individual hospital technician) TMV: George Elliot, hospital tech (individual hosp. tech) TMV: Edgar Elliot, hospital tech (individual hosp. tech) This option does not involve AD at all. In this scheme, you must perform all user and group configuration and maintenance on the TraceMasterVue server. NOTE A COBO user can only access locally defined confirming cardiologists. A-20 Installing TraceMasterVue and Configuring Communication

303 Interaction with Active Directory Table A-1 Use Model Examples of configuring users and groups with Active Directory (continued) Examples 2 User in AD, assigned to local group on TraceMasterVue server TMVue Local Security Members of TraceMaster_Tech group: AD: Sam Elliot, hospital tech (individual hospital technician) AD: George Elliot, hospital tech (individual hosp. tech) AD: Edgar Elliot, hospital tech (individual hosp. tech) Active Directory (highest level) Members of AD: HospitalTechs group (group of hospital techs): AD: Sam Elliot, hospital tech (individual hospital technician) AD: George Elliot, hospital tech (individual hosp. tech) AD: Edgar Elliot, hospital tech (individual hosp. tech) NOTE A COBO user can only access locally defined confirming cardiologists. 3 User in AD, assigned to global group in AD; AD group assigned to local group on TraceMasterVue server TMVue Local Security Members of TraceMaster_Tech group: AD: HospitalTechs group (group of hospital techs) Active Directory (highest level) Members of AD: HospitalTechs group (group of hospital techs): AD: Sam Elliot, hospital tech (individual hospital technician) AD: George Elliot, hospital tech (individual hosp. tech) AD: Edgar Elliot, hospital tech (individual hosp. tech) This option involves both AD and the TraceMasterVue server. In this scheme, you must maintain users and groups in both locations. 4 User in AD, assigned to global TraceMasterVue group defined in AD Active Directory Local Security (highest level) Members of AD: TraceMaster_Tech group (group of hospital techs): AD: Sam Elliot, hospital tech (individual hospital technician) AD: George Elliot, hospital tech (individual hosp. tech) AD: Edgar Elliot, hospital tech (individual hosp. tech) This option does not involve the local TraceMasterVue server at all. In this scheme, you perform all user and group configuration and maintenance in Active Directory. NOTE You cannot use TraceMasterVue security roles to further restrict a user s permissions. A COBO user can access confirming cardiologists defined in AD, as well as locally on the TraceMasterVue server, if defined. Installing TraceMasterVue and Configuring Communication A-21

304 About TraceMasterVue Users and Groups Table A-1 Use Model Examples of configuring users and groups with Active Directory (continued) Examples 5 User in AD, assigned to global group in AD; AD group assigned to global TraceMasterVue group defined in AD Active Directory Local Security (highest level) Members of AD: TraceMaster_Tech group (group of hospital techs): AD: HospitalTechs group (group of hospital techs) A-22 Installing TraceMasterVue and Configuring Communication

305 B Appendix MUsing Location Information in TraceMasterVue The location identifies where an ECG was acquired, and comprises three levels: institution, facility, and department. Location information is organized as a hierarchy, with institutions containing one or more facilities, which in turn comprise one or more departments. By default, TraceMasterVue ships with two institutions preconfigured: 999, for ECGs provided in the database for training purposes 000, for unassigned (undefined) ECGs (analogous to a lost and found bin) You define institutions, facilities, and departments using the System Configuration utility Locations tab. Individual locations are identified by both a code and descriptive text. This appendix provides the following information: Configuring TraceMasterVue and Device Location Fields B-2 Location Matching in TraceMasterVue B-2 Location Matching when Importing an ECG from a Legacy Device B-3 Location Code Mapping for Legacy Cardiographs and TraceMaster Systems B-3 3:2 Location Format Processing B-4 1:2:2 Location Format Processing B-6 Configuring the ENABLE_LOC_OVERLOAD Registry Value.....B-7 Location Matching when Importing ECGs from Legacy ECG Management Systems B-9 Location Matching when Importing an ECG from a Non-Legacy Device...B-10 About Unidentified Locations B-15 Deleting Location Entries B-16 About the Patient Domain B-16 B-1

306 Using Location Information in TraceMasterVue Configuring TraceMasterVue and Device Location Fields It is important that the location-related information that you specify in TraceMasterVue match the location information configured for the cardiographs and other medical devices (for example, bedside monitors and other TraceMaster ECG management systems) at your site that will send ECGs to the TraceMasterVue database. In addition, the naming convention you decide to use for institutions may be different depending on whether your site uses PageWriterTouch or Trim cardiographs, legacy PageWriter XL-series cardiographs, or a mixed fleet. But first, you must understand how TraceMasterVue processes location information on incoming ECGs. Location Matching in TraceMasterVue TraceMasterVue processes location information differently depending on whether the ECG is being imported or exported, and which device sourced the ECG or will be the recipient of the ECG (during interactive query). These different combinations are described in detail in the following sections: Location Matching when Importing an ECG from a Legacy Device on page B-3 Location Matching when Importing an ECG from a Non-Legacy Device on page B-10 In the location matching combinations listed above, TraceMasterVue performs the matching calculations in the following order, using the code and/or name in each case: 1 Institution information 2 Facility information 3 Department information Each location evaluation is performed using the following rules: 1 In situations in which the ECGs from legacy devices do not contain facility code information, TraceMasterVue assigns the default Unidentified facility code that applies to the associated institution. 2 If the institution code for the legacy or non-legacy ECG is not specified or not defined on TraceMasterVue, TraceMasterVue assigns the default Unidentified institution code, code If the facility code for the legacy or non-legacy ECG is not specified or not defined on TraceMasterVue for the institution, TraceMasterVue assigns the default Unidentified facility code for the current institution. This default facility code comprises the associated institution code plus 00. For example, if the current institution is 524, the default facility code is set to If the department code for the legacy or non-legacy ECG is not specified or not defined on TraceMasterVue for the facility, TraceMasterVue assigns the default Unidentified department code for the current facility. The default department code is 00. B-2 Installing TraceMasterVue and Configuring Communication

307 Location Matching when Importing an ECG from a Legacy Device Location Matching when Importing an ECG from a Legacy Device TraceMasterVue imports ECGs from legacy devices, including cardiographs (PageWriter XLi, PageWriter 300pi) and ECG management systems (TraceMaster C), as well as the IntelliVue Information Center (if you have option #C20 or TraceMasterVue Enterprise Edition). In most cases, ECGs from legacy devices only contain institution and department code information. However, in some instances, the location code might also contain facility code information. ECGs from Legacy Cardiographs. For ECGs originating on legacy cardiograph systems, all location information is stored in a single five-digit field, Location Code. Before the translator can start location matching, it must first map the location code into the appropriate institution, facility, and department values used by TraceMasterVue. After mapping the location code to the TraceMasterVue three-tier hierarchy, the location matching rules described on page B-2 are applied. ECGs from legacy TraceMaster ECG management systems. ECGs from legacy ECG management systems (TraceMaster C) may consist of a pair of files, PCEF and TM12Lead. For details on importing ECGs from legacy TraceMaster systems, see also Location Matching when Importing ECGs from Legacy ECG Management Systems on page B-9. ECGs from the IntelliVue Information Center. If you are sourcing ECGs on an IntelliVue system, the location matching rules are different from those presented here. For details, see Using TraceMasterVue with the IntelliVue Information Center in the TraceMasterVue System Configuration and Reference Guide. Location Code Mapping for Legacy Cardiographs and TraceMaster Systems TraceMasterVue offers two options for matching legacy cardiograph and TraceMaster ECG management system location codes to the new three-tier location hierarchy: 3:2. The first three digits of the location code map to the institution, and the second two digits map to a department. This is the default setting. Example: The location code breaks down to institution code 524 and department code 89. This option is useful if you do not need the middle facility layer in the hierarchy, or if you only need one entry in the middle layer. In the latter case, you can rename the description associated with facility code 000 from Unidentified to the appropriate label for your site. For details about location processing for this format, see 3:2 Location Format Processing on page B-4. Installing TraceMasterVue and Configuring Communication B-3

308 Using Location Information in TraceMasterVue 1:2:2. The first digit of the location code maps to a single-digit institution code, the second two digits correspond to a facility code, and the last two digits map to a department code. This option is referred to as overloading the location code. Example: The location code breaks down to institution code 5, facility code 24, and department code 89. This option is useful if you need the middle facility layer of the hierarchy. The limitation is that you cannot have more than 10 institution listings (0-9). For details about location processing for this format, see 1:2:2 Location Format Processing on page B-6. A registry key controls which of these options is enabled at your site. The DWORD registry key, ENABLE_LOC_OVERLOAD, has two settings: 0 Use the default 3:2 conversion option 1 Use the 1:2:2 conversion option For details on adding and updating the registry key, see Configuring the ENABLE_LOC_OVERLOAD Registry Value on page B-7. 3:2 Location Format Processing The location code elements are processed as follows when you use the 3:2 format. For each example, assume the original location code is Institutions, facilities, and departments are defined using the TraceMasterVue System Configuration utility. Institution code defined in TMVue The first three digits of the location code, in this case 524, are assigned to the institution code. Institution code remains 524. Institution code not defined in TMVue Institution code is set to either 000:524 or 000, where 000 is the newly assigned institution code and 524 is the original code. Institution code is set to 000:524 if the combination of the new and original codes does not exceed 32 characters in length. Otherwise, it is set to 000, which is the code for Unidentified institution. NOTE The institution code is shown as 000 in dropdown lists in ECGVue/PharmaVue. The extended notation appears on the report in Report view and on hard copy, as well as in the XML file. B-4 Installing TraceMasterVue and Configuring Communication

309 Location Matching when Importing an ECG from a Legacy Device Institution code defined in TMVue Facility code assignment if Institution code defined in TMVue The facility code is created by appending 00 to the end of the institution code. This is the default, Unidentified facility code associated with the 524 institution, and is referred to as the calculated facility code. If the institution code 524 is defined in TraceMasterVue, the facility code is set to Department code defined in TMVue The last two digits of the location code, in this case 89, are assigned to the department code. Department code remains 89 if code 89 is defined under the calculated facility code (as described above). Institution code not defined in TMVue Facility code assignment if Institution code not defined in TMVue Facility code is set to is the default Unidentified facility code associated with the Unidentified institution code, 000. Department code not defined in TMVue Department code is set to either 00:89 or 00, where 00 is the newly assigned department code and 89 is the original code. Department code is set to 00:89 if the combination of the new and original codes does not exceed 32 characters in length. Otherwise, it is set to 00, which is the code for Unidentified department. Note: The department code is shown as 00 in dropdown lists in ECGVue/PharmaVue. The extended notation appears on the report in Report view and on hard copy, as well as in the XML file. Installing TraceMasterVue and Configuring Communication B-5

310 Using Location Information in TraceMasterVue 1:2:2 Location Format Processing The location code elements are processed as follows when you use the 1:2:2 format. For each example, assume the original location code is Institutions, facilities, and departments are defined using the TraceMasterVue System Configuration utility. Institution code defined in TMVue The first digit of the location code, in this case 5, is assigned to the institution code, and is referred to as the calculated code. Institution code is set to 5. Facility code assignment if defined for calculated institution in TMVue The second two digits of the location code, in this case 24, are assigned to the facility code, which is referred to as the calculated code. Facility code is set to 24 if this code is defined under the calculated institution code. Institution code not defined in TMVue Institution code is set to either 000:5 or 000, where 000 is the newly assigned institution code and 5 is the calculated code. Institution code is set to 000:5 if the combination of the new and calculated codes does not exceed 32 characters in length. Otherwise, it is set to 000, which is the code for Unidentified institution. NOTE The institution code is shown as 000 in dropdown lists in ECGVue/PharmaVue. The extended notation appears on the report in Report view and on hard copy, as well as in the XML file. Facility code assignment if not defined for calculated institution in TMVue Facility code is set to either 500:24 or 500, where 500 is the newly assigned facility code and 24 is the original calculated code. Facility code is set to 500:24 if the combination of the new and calculated codes does not exceed 32 characters in length. Otherwise, it is set to 500, which is the default Unidentified facility code associated with the calculated institution 5. NOTE The facility code is shown as 500 in dropdown lists in ECGVue/PharmaVue. The extended notation appears on the report in Report view and on hard copy, as well as in the XML file. B-6 Installing TraceMasterVue and Configuring Communication

311 Location Matching when Importing an ECG from a Legacy Device Department code defined for calculated facility in TMVue The last two digits of the location code, in this case 89, are assigned to the department code. Department code remains 89 if code 89 is defined under the calculated facility code. Department code not defined for calculated facility in TMVue Department code is set to either 00:89 or 00, where 00 is the newly assigned department code and 89 is the original code. Department code is set to 00:89 if the combination of the new and original codes does not exceed 32 characters in length. Otherwise, it is set to 00, which is the code for Unidentified department. NOTE The department code is shown as 00 in dropdown lists in ECGVue/PharmaVue. The extended notation appears on the report in Report view and on hard copy, as well as in the XML file. Configuring the ENABLE_LOC_OVERLOAD Registry Value The ENABLE_LOC_OVERLOAD registry value allows you to specify whether location codes from legacy devices are converted using the 3:2 format or 1:2:2 format, as described in Location Code Mapping for Legacy Cardiographs and TraceMaster Systems on page B-3. You must first add the registry value to the registry key, and then configure the desired setting. To add the ENABLE_LOC_OVERLOAD value to the registry 1 Run regedit and navigate to the HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS registry key. 2 Right-click the EMS registry key and select New, then DWORD Value from the popup menus. Installing TraceMasterVue and Configuring Communication B-7

312 Using Location Information in TraceMasterVue An entry appears in the right pane, labeled New Value #1. 3 Type the name ENABLE_LOC_OVERLOAD. The registry value is now added. To configure the value now, continue to step 2 of the next procedure. Otherwise, close out of the registry editor. The next step is to configure the registry value to determine which location code conversion method to use, as described next. To configure the ENABLE_LOC_OVERLOAD registry value 1 Run regedit and navigate to HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS/ ENABLE_LOC_OVERLOAD. 2 Double-click the ENABLE_LOC_OVERLOAD entry. The Edit DWORD Value dialog box appears. 3 In the Value data field, type 0 or 1, then click OK to save your changes. 0 Use the default 3:2 conversion option (page B-4) 1 Use the 1:2:2 conversion option (page B-6) 4 Close the registry editor. B-8 Installing TraceMasterVue and Configuring Communication

313 Location Matching when Importing ECGs from Legacy ECG Management Systems Location Matching when Importing ECGs from Legacy ECG Management Systems When ECGs are migrated from legacy ECG management systems (for example, TraceMaster C) to TraceMasterVue, each ECG comprises a pair of files: PCEF (PageWriter XL Cardiograph ECG Format) TM12Lead (this file is transparent to the user and is only used by TraceMasterVue internal files) Within the pair, the TM12Lead file can contain optional facility information, as shown in the following example in the MiscData tag: <?xml version="1.0" encoding="utf-8"?> <!-- TraceMasterXmlVersion=" " --> <!DOCTYPE Patient SYSTEM "/TMData/TM12lead.dtd"> <Patient> <PatID Edited="0"> </PatID> <Institution Code="327" Edited="0"/> <EcgReport EditedBy="" DbTimestamp="0x BF9C" ReadOnly="1" EverEdited="0"> <Date Edited="0">1997/04/08</Date> <Time Edited="0">11:47:39</Time> <Demographics> <Name Edited="0"></Name> <Age Code="38" Units="yrs" Edited="0">38</Age> <Sex Code="0" Edited="0">Male</Sex> <Height Code="72" Units="in" Edited="0">72</Height> <Weight Code="238" Units="lb" Edited="0">238</Weight> </Demographics> <Measurements MsmtVer=""> <Rate Edited="0">0</Rate> <PR Edited="0">141</PR> <QRSD Edited="0">94</QRSD> <QT Edited="0">425</QT> <QTc Edited="0">403</QTc> <FrntAxis_P Edited="0">46</FrntAxis_P> <FrntAxis_QRS Edited="0">14</FrntAxis_QRS> <FrntAxis_T Edited="0">3</FrntAxis_T> </Measurements> <Findings CriteriaVer="M8"> <Severity Code="2"></Severity> <Statements> </Statements> <ConfirmingMD ConfirmedStatus="0"> <MD_Initials/> <MD_Name>PRELIMINARY - MD MUST REVIEW.</MD_Name> </ConfirmingMD> </Findings> <MiscData> <Dept Code="60" Edited="0"/> <Facility Code="74"/> <UserAField Label="" Edited="0"/> <UserBField Label="" Edited="0"/> <TechID Edited="0">14</TechID> <Room Edited="0"></Room> <RequestingMD Edited="0"></RequestingMD> <Stat Edited="0">0</Stat> </MiscData> </EcgReport> </Patient> Installing TraceMasterVue and Configuring Communication B-9

314 Using Location Information in TraceMasterVue The facility code information is optional in this file (in this example, the code is 74). The facility code is always numeric, and can contain between one and thirty-two digits, although typical use is between three and five. The presence of a facility code in the TM12Lead file, in combination with the setting of the ENABLE_LOC_OVERLOAD registry value determine how the location code is imported to the TraceMasterVue three-tier hierarchy: If the file does not specify a facility code, the system checks the setting of the ENABLE_LOC_OVERLOAD registry value. If the setting of the registry value is 0, the location code is processed as a 3:2 location format. If the setting of the value is 1, the code is processed as a 1:2:2 format. For details on each processing option, see Location Code Mapping for Legacy Cardiographs and TraceMaster Systems on page B-3. If the file specifies a facility code, the 5-digit location code is processed as a 3:2 location format, and the facility code information is used in the location matching process as described in 3:2 Location Format Processing on page B-4. In this case, the setting of the registry value is ignored. Location Matching when Importing an ECG from a Non- Legacy Device TraceMasterVue imports ECGs from a multitude of devices, including the PageWriterTouch and Trim cardiographs and IntelliVue systems. These new systems are referred to as nonlegacy devices to differentiate them from the legacy PageWriter XL/300pi cardiographs and TraceMaster C (and earlier) ECG management systems. ECGs from these devices may specify zero or more of the following optional location components: 1 Institution code 2 Institution name 3 Facility code 4 Facility name 5 Department code 6 Department name NOTE Unlike ECGs from legacy devices, an ECG from a non-legacy device can specify location information that comprises any combination of the above elements, such as institution name, facility code, facility name, and department name. B-10 Installing TraceMasterVue and Configuring Communication

315 Location Matching when Importing an ECG from a Non-Legacy Device NOTE Location matching for non-legacy ECGs is performed in the order shown in the previous list, from institution code to department name. In each case, the system checks the values specified in the XML ECG file and compares them to the values defined in TraceMasterVue. It is important to note the following precedence rules: For each location field, the code setting specified in TraceMasterVue takes precedence over the code setting in the ECG file. In addition, the location name associated with a given code in TraceMasterVue takes precedence over the name for that location specified in the ECG file. The following pages describe these rules in more detail. Remember that institutions, facilities, and departments are defined in TraceMasterVue using the System Configuration utility. The following sample XML ECG file lists some values for each location field; these values are used in the table below describing how location information is processed for ECGs from nonlegacy devices. <departmentid>89</departmentid> <departmentname>ed</departmentname> <institutionid>524</institutionid> <institutionname>mary Hospital</institutionname> <institutionlocationid>52411</institutionlocationid> <institutionlocationname>pediatric Unit</institutionlocationname> The steps in the following table are performed in order. Department code Department name Institution code Institution name Facility code Facility name Installing TraceMasterVue and Configuring Communication B-11

316 Using Location Information in TraceMasterVue 1 Institution code defined in TMVue Institution code not defined in TMVue or not specified in ECG If the institution code specified by the institutionid tag in the ECG file (in this example 524) is defined in TraceMasterVue, the code remains 524 upon import. a b c If the institution code is defined in the ECG, but not in TraceMasterVue, the institution code is set to either 000:524 or 000, where 000 is the newly assigned institution code and 524 is the original code. Institution code is set to 000:524 if the combination of the new and original codes does not exceed 32 characters in length. Otherwise, it is set to 000, which is the code for Unidentified institution. If the institution code is not specified in the ECG, but the institution name is, the system looks up the specified name in TraceMasterVue, retrieves the associated code, and assigns this institution code to the ECG. This is referred to as the calculated institution code. If the institution code is not defined in the ECG, and the specified institution name is not defined in TraceMasterVue, the institution code is set to Institution name defined in TMVue Institution name not defined in TMVue or not specified in ECG If the institution name specified by the insitutionname tag in the ECG (in this case, Mary Hospital) is the same as the name associated with the calculated code (determined in step 1), the institution name remains Mary Hospital upon import. In both of the following situations, the system retrieves the name associated with the calculated institution code (determined in step 1) and assigns it to the ECG upon import: The institution name is not specified in the ECG The institution name specified in the ECG (insitutionname tag) does not correspond to the name associated with the calculated code B-12 Installing TraceMasterVue and Configuring Communication

317 Location Matching when Importing an ECG from a Non-Legacy Device 3 Facility code defined in TMVue Facility code not defined in TMVue or not specified in ECG If the facility code specified by the institutionlocationid tag in the ECG file (in this example 52411) is defined under the calculated institution code (determined in step 1) in TraceMasterVue, the code remains upon import. a b c If the facility code is specified in the ECG, but is not defined on TraceMasterVue, the facility code is set to either 52400:52411 or 52400, where is the new facility code and is the original code. Facility code is set to 52400:52411 if the combination of the new and original facility codes does not exceed 32 characters in length. Otherwise, it is set to 52400, which is the code for Unidentified facility associated with institution 524. If the facility code is not specified in the ECG, but the facility name is and it is associated with the specified institution, the system looks up the specified name in TraceMasterVue, retrieves the associated code, and assigns this facility code to the ECG. This is referred to as the calculated facility code. If the facility code is not defined in the ECG, and the specified facility name is not defined in TraceMasterVue, the facility code is set to Facility name defined in TMVue Facility name not defined in TMVue or not specified in ECG If the facility name specified by the insitutionlocationname tag in the ECG (in this case, Pediatric Unit) is the same as the name associated with the calculated code (determined in step 3), the facility name remains Pediatric Unit upon import. In both of the following situations, the system retrieves the name associated with the calculated facility code (determined in step 3) and assigns it to the ECG upon import: The facility name is not specified in the ECG The facility name specified in the ECG (insitutionlocationname tag) does not correspond to the name associated with the calculated code Installing TraceMasterVue and Configuring Communication B-13

318 Using Location Information in TraceMasterVue 5 Department code defined in TMVue Department code not defined in TMVue or not specified in ECG If the department code specified by the departmentid tag in the ECG file (in this example 89) is defined under the calculated facility code (determined in step 3) in TraceMasterVue, the code remains 89 upon import. a b c If the department code is specified in the ECG, but is not defined on TraceMasterVue, the department code is set to either 00:89 or 00, where 00 is the new department code and 89 is the original code. Department code is set to 00:89 if the combination of the new and original department codes does not exceed 32 characters in length. Otherwise, it is set to 00, which is the code for Unidentified department. If the department code is not specified in the ECG, but the department name is and it is associated with the specified facility, the system looks up the specified name in TraceMasterVue, retrieves the associated code, and assigns this department code to the ECG. This is referred to as the calculated department code. If the department code is not defined in the ECG, and the specified department name is not defined in TraceMasterVue, the department code is set to Department name defined in TMVue Department name not defined in TMVue or not specified in ECG If the department name specified by the departmentname tag in the ECG (in this case, ED) is the same as the name associated with the calculated code (determined in step 5), the department name remains ED upon import. In both of the following situations, the system retrieves the name associated with the calculated department code (determined in step 5) and assigns it to the ECG upon import: The department name is not specified in the ECG The department name specified in the ECG (departmentname tag) does not correspond to the name associated with the calculated code Before proceeding with defining location information on TraceMasterVue, ensure you have completed the Location Definition Worksheet (page 2-11). The worksheet provides space for you to record the location information for your site. You can then define these entries on the TraceMasterVue system, as well as on devices that will send and receive information to the system. The worksheet is a good way to ensure that entries are defined in the same manner across systems. B-14 Installing TraceMasterVue and Configuring Communication

319 About Unidentified Locations About Unidentified Locations When TraceMasterVue encounters an ECG that does not have adequate information to accurately identify the associated location (institution, facility, and/or department), it associates the ECG with the appropriate Unidentified location, as follows: If the incoming ECG does not have an institution code or description that matches the entries defined in TraceMasterVue, it is associated with Unidentified Institution, code 000. For additional matching rules, see the Installing TraceMasterVue and Configuring Communication, provided on the TraceMasterVue Documentation and Training CD; also available on the server in TraceMasterVue\Help\TraceMasterVue_Manuals. If the ECG has an identifiable institution, but not facility, it is associated with Unidentified Facility, code XXX00, where XXX are the first three digits of the associated institution code. If the ECG has an identifiable institution and facility, but not department, it is associated with Unidentified Department, code 00, within that facility. By default, when you define a new institution, TraceMasterVue automatically creates associated Unidentified Facility and Unidentified Department entries. Similarly, when you define a new facility, TraceMasterVue automatically creates the associated Unidentified Department entry. The following example illustrates how this works. Top-level Unidentified Institution (shipped by factory) Create institution (Unidentified Facility and Unidentified Department created by default) Create facility (Unidentified Department created by default) Create department Installing TraceMasterVue and Configuring Communication B-15

320 Using Location Information in TraceMasterVue TIP If you are finding that a significant number of ECGs are going into the Unidentified categories, it is a clear sign that the cardiographs and TraceMasterVue system are not in sync. Review the location information configured on each of the devices, and ensure they match. Philips recommends that, in most cases, you not change the names of these entries, for easier identification. Deleting Location Entries To protect your site s clinical data, you can only remove locations (institutions, facilities, and departments) if they meet certain criteria, listed below, including not having any associated ECGs and not comprising lower-level locations that have associated ECGs. The Remove button is enabled for each location when the following conditions are met: The selected location (institution, facility, or department) has no associated ECGs The selected location is not associated with any inbox The selected location is not used in a workflow rule The selected location is not associated with a security role The selected location does not have any associated lower-level facilities or departments* The selected location is not an automatically created Unidentified Facility or Unidentified Department entry; you cannot delete these entries* * When you define a new institution or facility, TraceMasterVue automatically creates associated Unidentified Facility and Unidentified Department entries, as appropriate. You cannot delete these Unidentified entries. However, if these entries are the only items associated with an institution or facility (and all the other conditions above are met), TraceMasterVue enables the Remove button, allowing you to delete the institution or facility. If you are trying to delete a location and the Remove button is disabled, ensure that the above requirements are met. About the Patient Domain TraceMasterVue offers three options for how patient ID uniqueness is handled across different locations. The patient ID uniquely identifies each patient as follows each option is referred to as a particular patient domain: Across the enterprise (across all institutions) (the default setting) The system views all ECGs with the same patient ID, across all institutions, facilities, and departments serviced by TraceMasterVue, as belonging to the same patient. You cannot reuse the same ID within a single TraceMasterVue system. Within an institution The system views all ECGs with the same ID within a single institution as belonging to the same patient. You can reuse the same ID in different institutions. This option is only enabled for use if you have the Universal Edition of TraceMasterVue. B-16 Installing TraceMasterVue and Configuring Communication

321 About the Patient Domain Within a facility The system views all ECGs with the same ID within a single facility as belonging to the same patient. You can reuse the same ID in different facilities, within the same institution. This option is only enabled for use if you have the Universal Edition of TraceMasterVue. This patient domain (enterprise, institution, or facility) is defined when the system is initially configured, and requires that the database be empty. Once selected, the domain type can only be changed by flushing the database (including tutorial records), changing the domain type, and then repopulating the database. For details, see Setting the Patient Domain on page The selected domain also affects serial comparison rules. Installing TraceMasterVue and Configuring Communication B-17

322 Using Location Information in TraceMasterVue B-18 Installing TraceMasterVue and Configuring Communication

323 C Appendix NAbout Custom Statements and Aliases The TraceMasterVue system allows you to define an unlimited number of your own custom supplementary uncoded interpretive statements and modifiers, as well as Dx, Hx, Sx, DRG, and Rx codes. The Statement Manager allows you to customize codes, severities, and interpretive statements. In addition to defining custom statements and codes, you can also map codes and statements in a selected criteria version (for example, 0A) to your own site-specific nomenclature, or aliases. This appendix provides the following information: Overview C-1 About Statement Aliasing C-2 Enabling Statement Aliasing C-4 Defining Statement Aliases C-5 Configuring Custom Modifiers, Codes, and Statements C-6 Configuring Custom Modifiers and Codes C-6 Configuring Custom Statements C-7 Overview You generally either use aliases or create custom statements and modifiers because, among other reasons, your site: Uses an already defined lexicon (perfect for aliasing) Has other medical equipment and you need the statements to be the same (can use aliasing or custom statements) Commonly adds particular statements to a computer-generated interpretive report (custom statements work best) Aliases and custom statements are associated with a specific criteria version (selected on the Statement Set tab), and are available for use in the client application when that criteria version is enabled. The custom statements and modifiers are editable in the same manner as the factory-supplied statements. They are visible in all subsequent reports, reviews, and data transfers. These changes apply to statements after the ECGs have been interpreted, and should not be confused with customized criteria. C-1

324 About Custom Statements and Aliases NOTE Custom statements are not taken into account when TraceMasterVue performs serial comparison between two ECGs. For this reason, you may sometimes receive results that appear to be logically inconsistent. This does not apply to aliases, however. Because an alias is simply a mapping of a factorydefined code and/or statement to your own entry, the underlying data is unchanged. About Statement Aliasing Statement aliasing allows you to map codes and statements in a selected criteria version (for example, 0A) to your own site-specific nomenclature. The TraceMasterVue system supports several criteria versions (08, 09, 0A, and so on), as well as custom statements that might be added at your site. Your users may, however, prefer to use different codes and/or statement (the LHS, or left hand side) text to describe what is essentially the same condition. For example, for the 0A criteria statement, SR sinus rhythm, you might be used to using NSR, normal sinus rhythm. You can define an alias for the SR statement and map it to NSR so that reviewers can find and edit the statement using NSR. Aliases are associated with a single specified criteria version. You can define aliases for any number of criteria versions. You do not need to specify an alias for every statement in the criteria set. Those statements that do not have defined aliases are displayed using the factorydefined code and/or statement. This option is enabled on the System Configuration utility Global tab. You also use the Statement Manager to define the aliases for each coded statement. Unlike with custom statements, which are not subject to the Philips 12-Lead algorithm or serial comparison, statement aliasing merely substitutes your own site s preferred codes and/or text to describe the same conditions as the standard statements in the selected criteria. NOTES It is important that the LHS text, if modified, reflect the same condition as described in the criteria, as these statements are generated by the Philips 12-Lead algorithm. The aliasing process simply maps the statements in the criteria to your site s custom wording. NOTE The LHS defined at the factory may contain variables. Statement aliasing does not support variables at this time. The alias LHS will replace the factory LHS, and will not present any variables. This setting is applied globally. That is, if enabled at your site, the aliases used are applied across all systems at the site, for all users. In addition, everywhere that statements are displayed in the client, including in Statement View, in the Code list, in Report view, and on printed reports, the aliases are displayed (in place of the standard code and/or text). You do not have to define an alias for all statements within the criteria. When an alias is defined, that statement is displayed. If an alias is not defined for a given statement, the statement defined for the criteria is used. C-2 Configuring Cardiograph and TraceMasterVue Communication Guide

325 About Statement Aliasing You can enable either of the following three options: Use code aliases only In this case, your site-specific codes are mapped to the text defined in the selected criteria. Use LHS aliases only In this case, your site-specific statement text (LHS) is mapped to the code defined in the selected criteria. Use code and LHS aliases In this case, your site-specific codes and LHS text are mapped to those defined in the selected criteria. Example The following examples show how you might map selected statements in the 0A criteria. 0A code and/or statement text Defined alias Code and text change SR Sinus rhythm PRAA Probable right atrial abnormality NSR Normal sinus rhythm PRAE Probable right atrial enlargement Code change only AMI44 Consider anterior infarct LQTB Borderline prolonged QT interval CAMI Consider anterior infarct BLQT Borderline prolonged QT interval Statement change only LBBB Left bundle branch block REPNS Nonspecific repolarization abnormalities LBBB Complete left bundle branch block REPNS Nonspecific ST-T changes Configuring Cardiograph and TraceMasterVue Communication Guide C-3

326 About Custom Statements and Aliases Enabling Statement Aliasing Aliasing can be enabled and available, or disabled. Note that you enable aliasing using the System Configuration utility Global tab, and define aliases using the Statement Manager. For details, see Defining Statement Aliases on page C-5. To enable statement aliasing 1 On the System Configuration utility Global tab, select either or both of the check boxes in the Statement Aliasing section. Select Code Alias to mapping your own statement codes to defined codes. Select LHS Alias to map the text associated with a coded statement to defined statements. Select both to allow mapping of both the code and the statement text. 2 Click Finish. 3 Stop and restart the TraceMasterVue services to enable the changes. For details, see Starting and Stopping TraceMasterVue on page When users are reviewing and editing ECGs that are using a criteria version for which aliases have been defined, those aliases are available for use. To disable statement aliasing 1 On the System Configuration utility Global tab, clear either or both of the check boxes in the Statement Aliasing section. 2 Click Finish. 3 Stop and restart the TraceMasterVue services to enable the changes. For details, see Starting and Stopping TraceMasterVue on page Any defined aliases will not be available to the user when these options are disabled. C-4 Configuring Cardiograph and TraceMasterVue Communication Guide

327 About Statement Aliasing Defining Statement Aliases Use the Statement Manager utility to define code and/or statement aliases for a specific criteria version. Note that you must also enable the use of aliases in the System Configuration utility, on the Global tab, as described on the previous page. To define statement aliases 1 Launch the Statement Manager utility, and log in. 2 On the Statement Set tab, specify the criteria version to work with. 3 Click the Statement tab. 4 Scroll through the list and select a statement for which to define an alias, then click Edit. To sort the list of statements so you can quickly find the statement to alias, click the column heading by which to sort. In general, you will most likely sort by Code. For example, click Code to sort the list by code in alphabetical order. Click it again to reverse the order from ascending to descending, and vice versa. NOTE You cannot specify an alias for a new custom statement that you add to the system. It is unlikely that you will need an alias for a custom statement. The Edit Statement dialog box appears. 5 Type the code (in the Code Alias field) and/or statement alias (in the LHS Alias field) to use for the selected criteria-defined statement, then click Save. 6 Repeat steps 4 and 5 for each statement for which to define an alias. 7 When done, click Finish. 8 Stop and restart the TraceMasterVue services to enable the changes. For details, see Starting and Stopping TraceMasterVue on page Configuring Cardiograph and TraceMasterVue Communication Guide C-5

328 About Custom Statements and Aliases Configuring Custom Modifiers, Codes, and Statements You configure custom modifiers and codes using the Statement Manager Rx, Sx, Hx, Dx, Race, and DRG tabs, as described in Configuring Custom Modifiers and Codes, below. Create custom statements using the Statements tab as described in Configuring Custom Statements on page C-7. Configuring Custom Modifiers and Codes The procedure for adding, editing, and deleting modifiers, severities, and codes (Rx, Sx, Hx, Dx, Race, and DRG) is essentially the same. This section describes how to add, edit, and delete various items. NOTE You can only edit items that you have previously added to the system. Factory-defined entries cannot be edited or deleted. To add custom values 1 Display the tab for the item to add. For example, click the Race tab to add custom race codes. 2 Click Add. The Add/Edit <Item> dialog box appears. 3 Specify a code for the new entry, an abbreviated name for the entry, and the full name for the item. 4 Click OK. The new item is added to the bottom of the Currently Defined list. 5 When done, click Finish. 6 Stop and restart the TraceMasterVue services to enable the changes. For details, see Starting and Stopping TraceMasterVue on page C-6 Configuring Cardiograph and TraceMasterVue Communication Guide

329 Configuring Custom Modifiers, Codes, and Statements To edit existing values 1 Display the tab for the item to edit. For example, click the Dx tab to edit custom diagnosis codes. 2 In the Currently Defined list, click the entry to change. 3 Click Edit. You can only edit entries that you previously added. You cannot edit factory-specified items. The Add/Edit <Item> dialog box appears, displaying all of the values specified for the selected entry. The dialog box is the same as that used for adding codes. 4 Change or add the appropriate values; then click OK. 5 When done, click Finish. 6 Stop and restart the TraceMasterVue services to enable the changes. For details, see Starting and Stopping TraceMasterVue on page To delete custom values 1 Display the tab for the item to edit. For example, click the Dx tab to edit custom diagnosis codes. 2 In the Currently Defined list, click the entry to delete. You can only delete entries that you previously added. You cannot delete factory-specified items. 3 Click Remove. You may be prompted to verify the deletion. 4 Click OK to delete the item from the system. 5 When done, click Finish. 6 Stop and restart the TraceMasterVue services to enable the changes (page 6-29). Configuring Custom Statements The statement, as it appears formatted for reading, consists of modifiers, followed by the text of the LHS, with appropriate substitution of variable values. The printed statement may include the RHS, although it does not appear in the on-screen version of the report (in the client application).the RHS is shown in Statement view when the RHS includes editable variables. Use the Statement Manager Statements tab to define custom coded and quality statements at your site. For details about the fields on this tab, as well as the Add/Edit Statement dialog box, see About the Statement Manager Tabs on page C-49. You can also choose to define a statement or code alias for factory-defined statements. There are situations in which this approach might be preferable. For details, see About Statement Aliasing on page C-2. Configuring Cardiograph and TraceMasterVue Communication Guide C-7

330 About Custom Statements and Aliases To add custom statements 1 Click the Statements tab. 2 Click Add. The Add Custom Statement dialog box appears. For field details, see Appendix C, TraceMasterVue Interface Reference, in the TraceMasterVue System Configuration and Reference Guide. 3 Specify the desired statement values, including whether the new statement is a quality or coded statement, the code, description, optional modifiers, and so on. For a detailed description of the fields, see the Statement Manager online help. 4 Click OK. The statement is added to the bottom of the Currently Defined Statements list. 5 When done, click Finish. 6 Stop and restart the TraceMasterVue services to enable the changes (page 6-29). C-8 Configuring Cardiograph and TraceMasterVue Communication Guide

331 D Appendix OAbout User Fields Use the System Configuration utility User Fields tab to define custom fields in TraceMasterVue. User fields and their associated values, if any, appear in the ECGVue or PharmaVue Additional Data section, on the right side of the Summary page, as well as on the Advanced Search page. For details, see the ECGVue or PharmaVue online help. This appendix provides the following information: Special Purpose User Fields D-1 User Field 1 Attributes D-2 Configuring User Fields and OrderVue D-2 Overriding the Facility Field with User Defined Field D-2 Special Purpose User Fields Some user fields have special purposes: User field 1 is different from the rest in that it allows you to specify attributes for the field value. For example, you can label the field Smoker and have the attributes Yes and No, which are then specified at the cardiograph as appropriate. See User Field 1 Attributes on page D-2. You can also define workflow rules that will trigger an action based on individual attributes of User Field 1. For details, see Defining Automated Workflow Rules in the TraceMasterVue System Configuration and Reference Guide. If you have the OrderVue option to TraceMasterVue, you must reserve User Field 2 for the Unique Order ID. For details, see Configuring User Fields and OrderVue on page D-2. See also the OrderVue Installation and Configuration Guide. For pharma users, the Facility location field stores the Study ID. It is not uncommon for a single cardiograph to support multiple studies, but only a single Facility field is available. To support this model, User Field 8 on the cardiograph can be configured to store study information. For details, see Overriding the Facility Field with User Defined Field 8 on page D-2. If ECGs will be exported to FDA XML, you must define user fields as specified in the PhilipsXMLECGtoFDA_Field_Mapping_Table_Worksheets.xls, on the User Defines tab. For details, see the TraceMasterVue FDA XML Mapping Guide. D-1

332 About User Fields User Field 1 Attributes The first user field, User Field 1, can be used in automated workflow rules and have attributes associated with it. These attributes allow you to create custom workflow operations based on their values. For example, if UF1 is set to Priority with three attributes: 1 = High, 2 = Patient Admit, and 3=Standard, you could define a workflow rule that specifies how to handle ECGs with different priority values, sending priority 1 ECGs to a particular inbox, printing priority 2 ECGs and sending them to a different inbox, and so on. Configuring User Fields and OrderVue If your site also has the Philips OrderVue option AND uses either legacy PageWriter XLseries cardiographs or a mixed fleet that includes these legacy cardiographs, User Field 2 is reserved for Order ID. You must configure the field both on the cardiographs and in TraceMasterVue. If you have Philips OrderVue installed, you must use User Field 2 for OrderVue unique ID. The field label is usually set to OrderVue ID, all in capital letters, on both the TraceMasterVue system and on the cardiograph. In addition, you must ensure that the field label specified under the field rule for zpd_48 User_Defined_2 in the OrderVue Disk.mpr mapper file (stored in C:\Orderlnk\diskmapper and accessed through the LinkTools HL7 mapper) is identical to that specified in a user field (2 on PageWriterTouch/Trim, B on legacy cardiographs) on the cardiograph. Refer to the OrderVue training materials for additional information about configuring OrderVue and HL7. Overriding the Facility Field with User Defined Field 8 PageWriterTouch cardiographs only. In Pharma studies, Facility is used to store the Study ID. It is not uncommon for a single cardiograph to support multiple studies, but only a single Facility field is available on the PageWriterTouch cardiograph. To support this model, User Field 8 on the cardiograph can be configured to store study information. NOTE Remember that PharmaVue uses the labels, Institution/Facility/Department, which correspond to Sponsor/Study/Site in a Pharma implementation. This is how the Facility field override works: 1 As part of cardiograph configuration, specify the field label Facility for User Field 8 on the cardiograph (on the Addt l Info tab on the Configuration screen, accessed by touching Config > Defaults). Refer to the cardiograph documentation for details on using the Defaults screen. Note that the label is case sensitive and must be spelled exactly as shown, with a capital F. 2 At the cardiograph, the operator types the specific facility value into the User Field 8 (which is labeled Facility). D-2 Installing TraceMasterVue and Configuring Communication

333 Overriding the Facility Field with User Defined Field 8 3 When TraceMasterVue reads in the ECG, it checks whether the incoming User Field 8 is labeled Facility. If it is, the system then checks whether the ECG has a value specified for this field. If it does, the system overwrites the Facility name associated with the ECG with the value in the incoming User 8 field. If it is not, the system simply populates User Field 8 in PharmaVue with the incoming value. For example: Assume that on cardiograph A, User Define Field 8 is labeled Facility, and on cardiograph B, it is not. Cardiograph A is used to record ECGs for subjects participating in studies 101, 201, and 301. The Facility code for this cardiograph is set to 101. When the operator is recording ECGs associated with either study 201 or study 301, the operator types the appropriate study code (201 or 301) into the User Define Field 8 labeled Facility on the cardiograph. When TraceMasterVue reads in these ECGs, it detects that User Field 8 on the incoming ECG is labeled Facility, and that it contains a value. The system then overwrites the default Facility code 101 with the specified value, 201 or 301. However, when an ECG comes into TraceMasterVue from cardiograph B, any value that is present in User Field 8 will simply appear in the PharmaVue Summary view Addt l Details section, in the UF8 field. Installing TraceMasterVue and Configuring Communication D-3

334 About User Fields D-4 Installing TraceMasterVue and Configuring Communication

335 E Appendix PField Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue This information can be used to configure a PageWriterTouch or PageWriter Trim that is added to a hospital with a fleet of PageWriter XLi cardiographs. Print out the configuration of the PageWriter XLi. You can then see which fields are enabled and what labels are being used for User A and User B. You can then enable the equivalent fields at the PageWriterTouch or PageWriter Trim. See the tables below to see what PageWriterTouch or PageWriter Trim field maps to what PageWriter XLi field. The following table that lists the patient data entry fields at the PageWriterTouch, PageWriter Trim and PageWriter XLi cardiographs and maps the data to the TraceMasterVue data fields. Table E-1 Patient data field mapping between cardiographs and TraceMasterVue PageWriter Touch Field PageWriter Trim Field PageWriter XLi Field TraceMasterVue Database Field TraceMaster Vue XML Report Field Patient ID Patient ID Patient ID# tblpatients / patientnum patientid PID-3 First Name First Name Name tblpatients / namefirst AND tblecgmain / Patientinfo / firstname (in compressed XML fragment) Last Name Last Name tblpatients / namelast AND tblecgmain / Patientinfo / lastname (in compressed XML fragment) firstname lastname TraceMaster Vue HL7 Field PID-5.1 PID-5.2 E-1

336 Field Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue Table E-1 Patient data field mapping between cardiographs and TraceMasterVue (continued) PageWriter Touch Field PageWriter Trim Field PageWriter XLi Field TraceMasterVue Database Field TraceMaster Vue XML Report Field TraceMaster Vue HL7 Field Add l Name Additional Name tblpatients / namemiddle AND tblecgmain / Patientinfo / middlename (in compressed XML fragment) middlename PID-5.3 Race Race Race tblpatients / raceid race id PID-5.10 Date of Birth Age / DOB Age tblecgmain / age OR tblecgmain / dateofbrth dateofbirth Gender Gender Sex tblecgmain / sex sex PID-8 User Field 1 User Field 1 User A tblecgmain / userdefines (in compressed XML fragment) User Field 2 User Field 2 User B tblecgmain / userdefines (in compressed XML fragment) Sx Sx tblecgmain / Patientinfo / symptom id (in compressed XML fragment) Hx Hx tblecgmain / Patientinfo / history id (in compressed XML fragment) Rx Rx RX tblecgmain / Patientinfo / medication id (in compressed XML fragment) Dx Dx DX tblecgmain / Patientinfo / diagnosis id (in compressed XML fragment) First userdefine / value Second userdefine / value symptom id history id medication id diagnosis id OBR_2 E-2 Installing TraceMasterVue and Configuring Communication

337 Table E-1 Patient data field mapping between cardiographs and TraceMasterVue (continued) PageWriter Touch Field PageWriter Trim Field PageWriter XLi Field TraceMasterVue Database Field TraceMaster Vue XML Report Field TraceMaster Vue HL7 Field DRG DRG tblecgmain / Patientinfo / drgcategory id (in compressed XML fragment) Blood Pressure Blood Pressure Systolic BP tblecgmain / Patientinfo / systolic (in compressed XML fragment) Diastolic BP tblecgmain / Patientinfo / diastolic (in compressed XML fragment) User Field 3 User Field 3 tblecgmain / userdefines (in compressed XML fragment) User Field 4 User Field 4 tblecgmain / userdefines (in compressed XML fragment) Reason for Order Physician Name Physician UPIN Order Number Encounter ID Reason for Order Physician Name Physician UPIN Order Number Encounter ID Requested by tblecgmain / orderinfo / reasonfororder (in compressed XML fragment) tblecgmain / requestingmd tblecgmain / Acquisitioninfo / orderingclinicianupin (in compressed XML fragment) tblecgmain / orderinfo / ordernumber (in compressed XML fragment) tblecgmain / orderinfo / encounterid (in compressed XML fragment) drgcategory id systolic diastolic Third userdefine / value Fourth userdefine / value reasonfororder ordering clinicianname ordering clinicianupin ordernumber encounterid Installing TraceMasterVue and Configuring Communication E-3

338 Field Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue Table E-1 Patient data field mapping between cardiographs and TraceMasterVue (continued) PageWriter Touch Field PageWriter Trim Field PageWriter XLi Field TraceMasterVue Database Field TraceMaster Vue XML Report Field TraceMaster Vue HL7 Field STAT STAT ECG Mgr Priority or Stat tblecgmain / statflag statflag User Field 5 User Field 5 tblecgmain / userdefines (in compressed XML fragment) User Field 6 User Field 6 tblecgmain / userdefines (in compressed XML fragment) Department Department Department If two digits entered, look in tblecgmain / Acquisitioninfo / departmentid (Department portion of the Location code is changed to the two digits) (in compressed XML fragment) If other than two digits entered, look in tblecgmain / Acquisitioninfo / departmentname (in compressed XML fragment) Fifth userdefine / value Sixth userdefine / value tblecgmain / Acquisition info / departmentid tblecgmain / Acquisition info / department name Operator ID Operator ID Operator tblecgmain / operatorid operatorid Room Room Room tblecgmain / Acquisitioninfo / room (in compressed XML fragment) room Weight Weight Weight tblecgmain / weight weight Height Height Height tblecgmain / height height User Field 7 tblecgmain / userdefines (in compressed XML fragment) Seventh userdefine / value E-4 Installing TraceMasterVue and Configuring Communication

339 Table E-1 Patient data field mapping between cardiographs and TraceMasterVue (continued) PageWriter Touch Field PageWriter Trim Field PageWriter XLi Field TraceMasterVue Database Field TraceMaster Vue XML Report Field TraceMaster Vue HL7 Field User Field 8 tblecgmain / userdefines (in compressed XML fragment) Eight userdefine / value Installing TraceMasterVue and Configuring Communication E-5

340 Field Mappings between PageWriterTouch/Trim, Legacy Cardiographs, and TraceMasterVue E-6 Installing TraceMasterVue and Configuring Communication

341 Appendix QConfiguring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue F Setting up RAS support on TraceMasterVue is primarily for ECG transmission and interactive query between TraceMasterVue and PageWriter cardiograph using dialup modems. A RAS connection is also required for Philips Medical Systems support personnel to access and support the server. This appendix describes how to configure remote access service (RAS) support on both the PageWriter Touch/Trim cardiograph and the TraceMasterVue ECG management system. This appendix provides the following information: Communication between a TraceMasterVue System and Cardiographs.....F-2 RAS Configuration F-2 Hardware Prerequisites F-3 TraceMasterVue (RAS Server) Hardware Prerequisites F-3 PageWriter (RAS Client) Hardware Prerequisites F-4 Configuring TraceMasterVue (RAS Server) and the PageWriter Cardiographs (RAS Clients) F-4 Setting Up TraceMasterVue as the RAS Server F-4 Verifying COM Port Assignments on TraceMasterVue F-5 Configuring ECG Transmission and/or Interactive Query via RAS in TraceMasterVue F-6 Enabling Interactive Query F-6 Configuring Serial Ports for RAS In TraceMasterVue F-6 Configuring Local User Accounts on TraceMasterVue F-8 Configuring RAS Access for User Accounts on TraceMasterVue...F-9 Restarting Internet Information Services (IIS) F-10 Configuring and Enabling Routing and Remote Access on TraceMasterVue F-10 Configuring the RAS Server Port Properties F-11 Configuring RAS Server Properties F-15 Configuring Remote Access Policies F-18 Setting up the PageWriter Touch (RAS Client) F-22 Configuring Network Settings on the Cardiograph F-23 Configuring Settings on the Remote Sites > Network Tab F-23 Configuring Settings on the Net Connect Tab F-24 Saving the Cardiograph Network Settings F-25 F-1

342 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System F-25 Adding RAS and Serial Data Communication Support to a TraceMasterVue System F-26 Removing Serial Communication Ports from RAS Ownership....F-26 Adding RAS to an Existing TraceMasterVue System that Supports Legacy Serial Data Communication F-29 Adding Legacy Serial Data Communication Support to an Existing TraceMasterVue System that Supports RAS F-30 Communication between a TraceMasterVue System and Cardiographs The TraceMasterVue system can be configured to communicate with cardiographs as follows. TraceMasterVue can be configured: As a RAS server, to support communication with a PageWriter Touch cardiograph over a dialup modem for transmitting or querying ECGs. Most of the sections in this appendix describe this option. To support serial data communication to support communication with a legacy PageWriter XL-series cardiograph (through a direct connection or over dialup modem) for transmitting or querying for ECGs. For details, see the Installing TraceMasterVue and Configuring Communication. To support both environments simultaneously. RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System on page F-25 describes this option. RAS Configuration When you configure RAS, TraceMasterVue is the RAS server and the cardiograph is the RAS client, as illustrated in Figure F-1, RAS Configuration using dialup modems between PageWriter cardiographs and TraceMasterVue, on page F-3. TraceMasterVue is installed with a Comtrol 8-port Rocketport card, which provides eight additional serial communication ports. A dialup modem is connected to each serial port of the Comtrol 8-port Rocketport card. With eight modems for its use, TraceMasterVue (RAS server) can simultaneously transmit or receive ECGs from up to eight PageWriter cardiographs (RAS clients). To support network communication and the functions of a RAS server, TraceMasterVue must be configured with the following IP addresses: A static or a DHCP assigned IP address to support the NIC card A static IP address for the RAS server F-2 Installing TraceMasterVue and Configuring Communication

343 Hardware Prerequisites A static pool of IP addresses to be assigned to each RAS client connecting with the RAS server Figure F-1 RAS Configuration using dialup modems between PageWriter cardiographs and TraceMasterVue PageWriter Touch (RAS Client) TALK / DATA TALK RS CS TR RD TD CD Dial-up Modem Analog phone line TALK / DATA TALK TALK / DATA TALK TALK / DATA TALK TALK / DATA TALK TALK / DATA TALK TALK / DATA TALK RS CS TR RD TD CD RS CS TR RD TD CD RS CS TR RD TD CD RS CS TR RD TD CD RS CS TR RD TD CD RS CS TR RD TD CD Dial-up Modem Serial comm line Dial-up Modem Serial comm line Dial-up Modem Serial comm line Dial-up Modem Serial comm line Dial-up Modem Serial comm line Dial-up Modem Comtrol 8-Port Rocketport Card 1) TraceMasterVue is also the RAS server. 2) In addition to having a (static or DHCP assigned) IP address to its ethernet card, an IP address must be assigned to the RAS server. 3) The RAS server will assign a temporary IP address to each RAS client that connects with the RAS server. 4) If TraceMasterVue is installed with the Comtrol 8-port Rocketport card, TraceMasterVue will be able to communicate with 8 different RAS clients at the same time. TraceMasterVue (RAS Server) Serial comm line TALK / DATA TALK RS CS TR RD TD CD Dial-up Modem Serial comm line Analog phone line TALK / DATA TALK RS CS TR RD TD CD Dial-up Modem TALK / DATA TALK RS CS TR RD TD CD Dial-up Modem Serial comm line PageWriter Trim (RAS Client) Hardware Prerequisites Your system must meet the following hardware prerequisites to be able to configure RAS. TraceMasterVue (RAS Server) Hardware Prerequisites If TraceMasterVue will use more than two serial communication ports (standard with the system), the system must already have the Comtrol 8-Port Rocketport card installed. Installing TraceMasterVue and Configuring Communication F-3

344 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue All dialup modems must already be connected to the serial communication lines that will be dedicated for RAS communication. PageWriter (RAS Client) Hardware Prerequisites The following Philips Medical Systems cardiographs can be configured as a RAS client: PageWriter Touch The dialup modem must be connected to the PageWriter cardiograph. Configuring TraceMasterVue (RAS Server) and the PageWriter Cardiographs (RAS Clients) It is strongly recommended that you configure the TraceMasterVue system (RAS server) first, as each cardiograph (RAS client) references the RAS server IP address. When the RAS server is configured, configure the RAS client as described in Setting up the PageWriter Touch (RAS Client) on page F-22. Setting Up TraceMasterVue as the RAS Server To set up TraceMasterVue as the RAS server, complete the following steps, each of which is described in this appendix: All serial communication ports that will be used in RAS communication must be assigned to dialup modems. See Verifying COM Port Assignments on TraceMasterVue on page F-5 (in this appendix) and the Installing TraceMasterVue and Configuring Communication. Using the TraceMasterVue System Configuration utility, configure TraceMasterVue for interactive query and configure the serial communication ports that will be used in RAS communication. For details, see the Installing TraceMasterVue and Configuring Communication. All local user accounts (on TraceMasterVue) that will be used for RAS access must be configured for RAS access. See Configuring Local User Accounts on TraceMasterVue on page F-8. Routing and remote access must be configured and enabled on TraceMasterVue. See Configuring and Enabling Routing and Remote Access on TraceMasterVue on page F-10. F-4 Installing TraceMasterVue and Configuring Communication

345 Setting Up TraceMasterVue as the RAS Server Verifying COM Port Assignments on TraceMasterVue All serial communication ports that will be used for RAS communication must be configured and assigned to a modem. For details about configuring COM ports, see the Installing TraceMasterVue and Configuring Communication. To verify COM port assignments 1 Click Start > Control Panel > Phone and Modems Options. The Phone and Modem Options dialog box appears. Installing TraceMasterVue and Configuring Communication F-5

346 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue Proceed as follows: If all serial communications ports that will be used for RAS communication are assigned to the correct modems, proceed to the section, Configuring ECG Transmission and/or Interactive Query via RAS in TraceMasterVue on page F-6. If you need to configure serial communication ports and assign modems to these ports for RAS communication, see the Installing TraceMasterVue and Configuring Communication, provided on the TraceMasterVue Documentation and Training CD, as well as on the TraceMasterVue server in TraceMasterVue\Help\ TraceMasterVue_Manuals. Configuring ECG Transmission and/or Interactive Query via RAS in TraceMasterVue After setting up all desired serial communications ports to dialup modems as described in Verifying COM Port Assignments on TraceMasterVue on page F-5, run the TraceMasterVue System Configuration utility to Enable interactive query Make the desired serial communications ports available for RAS Enabling Interactive Query If the current TraceMasterVue system will support interactive query with PageWriter Touch and/or a legacy PageWriter XL-series cardiographs, you must enable this functionality in the TraceMasterVue System Configuration utility, on the Global tab. For details, see Configuring Interactive Query Support in the Installing TraceMasterVue and Configuring Communication. Configuring Serial Ports for RAS In TraceMasterVue If one or more serial ports will be used for RAS support, you must ensure that the affected ports are configured properly. Review port settings using the TraceMasterVue System Configuration utility, on the IO tab. For details, see Appendix C, TraceMasterVue Interface Reference in the TraceMasterVue System Configuration and Reference Guide. F-6 Installing TraceMasterVue and Configuring Communication

347 Setting Up TraceMasterVue as the RAS Server NOTE The following sections primarily discuss setting up ports for RAS communication. For all other serial port configuration information, see the Installing TraceMasterVue and Configuring Communication. A serial communication port can be dedicated to only one function: RAS, which is ECG transmission and/or interactive query between TraceMasterVue and a PageWriter Touch or Trim cardiograph using a dialup modem. The Legacy Support column must show No for ports that are used for RAS. For details, see To enable or disable legacy cardiograph support for a port on page F-8. Legacy cardiograph communication, which is ECG transmission and/or interactive query between TraceMasterVue and a legacy (PageWriter XL-series) cardiograph using a direct connect serial cable or modem communication. The Legacy Support column must show Yes for ports that are used for legacy cardiograph communication. For details, see Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue in the Installing TraceMasterVue and Configuring Communication. Fax The Legacy Support column must show No for ports that are used for fax. For details, see the Installing TraceMasterVue and Configuring Communication. Installing TraceMasterVue and Configuring Communication F-7

348 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue To enable or disable legacy cardiograph support for a port 1 On the System Configuration utility IO tab, select the port to work with from the Serial Ports list, and click Configure. The Configure Serial Port dialog box appears. 2 To enable legacy support, click the Support Legacy Cardiographs check box, then click OK. To disable legacy support, ensure the check box is clear. 3 On the IO tab, click Finish to save the changes. 4 Remember to stop and restart TraceMasterVue services to enable the change. See Starting and Stopping TraceMasterVue on page Configuring Local User Accounts on TraceMasterVue In order for a PageWriter Touch or PageWriter Trim cardiograph (RAS client) to transmit ECGs to TraceMasterVue (RAS server) or for the cardiograph to engage in an interactive query session with TraceMasterVue, the local user accounts that are defined on TraceMasterVue and are used by the cardiograph to gain access to TraceMasterVue must be a member of at least one TraceMaster group. For details about users and groups, including the access permissions associated with each group, see Appendix A, About TraceMasterVue Users and Groups. You must configure user accounts that will have RAS access as follows: The user ID must be associated with an appropriate TraceMaster group (see Associating Users with TraceMaster Groups on page 6-23) The user ID must be configured for RAS access (next) F-8 Installing TraceMasterVue and Configuring Communication

349 Setting Up TraceMasterVue as the RAS Server Configuring RAS Access for User Accounts on TraceMasterVue You must configure RAS access for all user accounts that will be used by the cardiograph to gain access to TraceMasterVue. To configure user accounts for RAS access 1 Click Start > All Programs > Administrative Tools > Computer Management. The Computer Management window appears. 2 In the left pane, select Local Users and Groups, then select the Users folder. 3 In the right pane, right-click the user whose access you are configuring, and select Properties from the menu. For illustration purposes, the Administrator user is selected here. The Properties dialog box appears. Installing TraceMasterVue and Configuring Communication F-9

350 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 4 Click the Dial-in tab. 5 In the Remote Access section, ensure the Allow access radio button is selected. 6 Click Apply, then OK to save the changes. NOTE Remember that when you add a new user or make changes to an existing user, it can take up to 10 minutes for the changes to propagate through the system and become effective. To make the changes effective immediately, restart IIS, as described next. NOTE Restarting Internet Information Services (IIS) If an existing user account that is used for TraceMasterVue is modified in any way, one of the following actions must be performed: Wait 10 minutes before any changes applied to the user account will become effective. IIS caches all user account properties, and IIS will not refresh and get the latest user account properties until approximately 10 minutes have elapsed. Reboot the TraceMasterVue server to force IIS to get the latest user account properties. Manually restart IIS to get the latest user account properties. See Stopping and Restarting IIS on page Restarting IIS is recommended, because all changes become effective immediately and requires the least amount of time. Configuring and Enabling Routing and Remote Access on TraceMasterVue To use RAS, TraceMasterVue must be configured and enabled for routing and remote access. Configuration is a two-part process; refer to the following sections for details: Configuring the RAS Server Port Properties, below Configuring Remote Access Policies on page F-18 F-10 Installing TraceMasterVue and Configuring Communication

351 Setting Up TraceMasterVue as the RAS Server Configuring the RAS Server Port Properties To configure and enable routing and remote access on TraceMasterVue 1 Click Start > All Programs > Administrative Tools > Routing and Remote Access. The Routing and Remote Access window appears. Note that the server icon is red. 2 Right-click the server name that has a red status and select Configure and Enable Routing and Remote Access from the menu. The Routing and Remote Access Wizard appears. 3 Click Next. On the Configuration screen, select Remote access; then click Next. 4 On the Remote Access screen, select Dial-up; then click Next. Installing TraceMasterVue and Configuring Communication F-11

352 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 5 On the IP Address Assignment screen, select From a specified range of addresses; then click Next. 6 On the Address Range Assignment screen, click New. F-12 Installing TraceMasterVue and Configuring Communication

353 Setting Up TraceMasterVue as the RAS Server NOTE The IP Address dialog box appears. 7 In the IP Address dialog box, define the Start IP address (assigned to the RAS server), and the End IP address (include enough addresses to encompass all of the RAS clients); then click OK. Specify a range of IP addresses that is large enough to support the RAS server and all serial communication ports that will be supporting RAS. The entry in the Number of Addresses field must include the server and all of the ports supporting RAS. See below for an example. For example, if the RAS server has a Comtrol 8-port Rocketport card in which 4 of the 8 serial communications ports will be used for RAS, the Number of Addresses entry must, at a minimum, be 5 or greater, since the first IP address is always assigned to the RAS server. NOTE The range of IP addresses defined for the RAS server and its clients must be unique; they must not have been assigned to other RAS servers, RAS clients, or network devices. Installing TraceMasterVue and Configuring Communication F-13

354 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 8 On the Address Range Assignment screen, click Next. The Managing Multiple Remote Access Servers screen appears. 9 Select No, use Routing and Remote Access...; then click Next. 10 On the final screen, click Finish. The following alert may appear. 11 Click OK to close the alert return to the Routing and Remote Access window. 12 Verify that the RAS setup was successful by selecting the Ports entry in the left pane, and checking whether there is a full list of ports in the right pane, as shown in the next figure. F-14 Installing TraceMasterVue and Configuring Communication

355 Setting Up TraceMasterVue as the RAS Server If the right pane does not display these ports, the RAS server is not properly configured. Start the steps over again or contact Philips support. Proceed to the following section, Configuring RAS Server Properties, to further configure the RAS server. Configuring RAS Server Properties To configure RAS server properties 1 In the Routing and Remote Access window (Start > All Programs > Administrative Tools > Routing and Remote Access), right-click the RAS server entry, which now shows a green icon, and select Properties from the menu. The Properties dialog box appears. 2 On the General tab, ensure the Remote access server check box is selected. 3 Click the Security tab. Installing TraceMasterVue and Configuring Communication F-15

356 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue Ensure that the following settings are specified: Authentication provider Accounting provider Windows authentication Windows accounting 4 Click Authentication Methods. The Authentication Methods dialog box appears. 5 Ensure that the following check boxes are selected; then click OK. Microsoft encrypted authentication version 2 Microsoft encrypted authentication Encrypted authentication Unencrypted password 6 Click the IP tab, and ensure that the following items are selected; then click Apply: F-16 Installing TraceMasterVue and Configuring Communication

357 Setting Up TraceMasterVue as the RAS Server Static address pool radio button Enable IP routing Allow IP-based remote access and demand-dial connections Enable broadcast name resolution 7 Click the PPP tab and ensure all of the check boxes are selected; then click Apply. 8 Click the Logging tab and select Log errors and warnings; then click Apply. Installing TraceMasterVue and Configuring Communication F-17

358 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 9 Click OK to close the dialog box. The RAS server properties are now set. Proceed to Configuring Remote Access Policies on page F-18, next. Configuring Remote Access Policies 1 In the Routing and Remote access window, select Remote Access Policies in the left pane. In the right pane, right-click Connections to Microsoft Routing and Remote Access server, and select Properties from the menu. F-18 Installing TraceMasterVue and Configuring Communication

359 Setting Up TraceMasterVue as the RAS Server The Connections Properties dialog box appears. 2 Select Grant remote access permission. 3 Change the policy conditions as follows: a b Remove the default Policy conditions entry, MS-RAS-Vendor matches ^311, by selecting the entry and clicking Remove. Click Add. The Select Attribute dialog box appears. Installing TraceMasterVue and Configuring Communication F-19

360 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue c Select the Framed-Protocol item and click Add. The Framed Protocol dialog box appears. d Select the PPP menu item and click Add >> to add it to the list; then click OK to close the dialog box and return to the Properties dialog box. The Properties dialog box should now be configured as shown. 4 Click Edit Profile. The Edit Profile Properties dialog box appears. 5 On the Dial-in Constraints tab, select the Minutes server can... check box and specify the time before hanging up, as shown. F-20 Installing TraceMasterVue and Configuring Communication

361 Setting Up TraceMasterVue as the RAS Server CAUTION In some cases, a cardiograph might fail to send a hang-up signal to TraceMasterVue s modem (for example, if a problem occurred on the cardiograph). in this case, TraceMasterVue s modem would wait indefinitely for additional communication from the cardiograph, leaving the modem in an unusable state. To eliminate this possibility, select the Minutes server can remain idle before it is disconnected check box, and specify the length of time (in minutes) that the RAS server should wait for a response from the cardiograph before hanging up the modem. In the example above, the time is set to 15 minutes. 15 minutes is the recommended time to wait before RAS sends a hangup signal to the modem. This value can, however, be changed, as appropriate. 6 Click the Authentication tab, and configure it as shown. 7 Click the Encryption tab and configure it as shown. Installing TraceMasterVue and Configuring Communication F-21

362 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 8 Click Apply, then OK to return to the Properties dialog box. 9 Click Apply and OK to close the dialog box. At this point, routing and remote access has been completely configured. Setting up the PageWriter Touch (RAS Client) In addition to setting up the phone number of the modem that is connected to the desired TraceMasterVue serial communications port, you must configure RAS access for each cardiograph that will connect to the RAS server, using the Remote Site of the cardiograph Configuration screen. Before you begin, have available: IP address of the TraceMasterVue (RAS) server The available assigned IP addresses for the cardiographs (RAS clients) The computer name assigned to the TraceMasterVue server You specified the IP address range during server configuration. For details, see Configuring RAS Server Properties on page F-15. To look up the IP addresses to use 1 Click Start > All Programs > Administrative Tools > Routing and Remote Access. The Routing and Remote Access window appears. 2 Right-click the TraceMasterVue server entry and select Properties from the menu. The Properties dialog box appears. 3 Click the IP tab, which displays the Start IP address, which is assigned to the RAS server, and the End IP address. You can assign any IP address between these two values, including the End value, to each cardiograph. F-22 Installing TraceMasterVue and Configuring Communication

363 Setting up the PageWriter Touch (RAS Client) To view the TraceMasterVue server name 1 On the server, right-click the My Computer icon, and select Properties from the menu. 2 In the Properties dialog box, click the Computer Name tab. This tab shows the full name assigned to the computer. To configure the PageWriter Touch cardiograph 1 Touch Config at the bottom of the cardiograph screen. 2 Touch Defaults at the bottom of the screen. 3 Touch the Remote Sites tab at the top of the screen. 4 Touch the Network radio button on the left. Ensure the Receive (Query) and Copy/Transfer check boxes are selected. 5 On the Remote Sites tab, touch the Network tab. You are now ready to configure network settings, as described next. Configuring Network Settings on the Cardiograph Configuring network settings on the cardiograph comprises two main steps, each of which is described in detail in the following sections: Configuring Settings on the Remote Sites > Network Tab (below) Configuring Settings on the Net Connect Tab on page F-24 Configuring Settings on the Remote Sites > Network Tab You must configure the following items on the Remote Sites > Network tab: Server URL User name Password After specifying the settings, be sure to save the changes. NOTE To set the server URL In the Server URL field, type the URL in the form where xxx.xxx.xxx.xxx is the IP address of the TraceMasterVue (RAS) server. The trailing slash / is required. This is the server IP address specified in Configuring RAS Server Properties, step 7, on page F-13. In the example provided in that section, the RAS server IP is Using this example, the server URL setting would be Installing TraceMasterVue and Configuring Communication F-23

364 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue NOTE To set the user name to use for RAS access Type the appropriate user name in the User Name field. The specified user name must be a local user account on the TraceMasterVue server that is configured for RAS access. For details, see Configuring RAS Access for User Accounts on TraceMasterVue on page F-9. For example, a valid user might be Administrator. ECG transmission and interactive query between the PageWriter Touch cardiograph and TraceMasterVue will be unsuccessful if the specified user account (on TraceMasterVue) is not configured for RAS access. To set the password to use Type the password associated with the selected user account in the Password field. The entry in the Password field is the password associated with the specified user. Configuring Settings on the Net Connect Tab You must configure the following items on the Net Connect tab: Network connection type Dialup devices Phone User Name Password Domain After specifying the settings, be sure to save the changes. To set the network connection type In the Network Connection Type field, touch the Dial-up radio button. To select the dialup device Touch the Dialup Devices field and select the appropriate modem from the list. For example, 3Com_Megahertz-3CXM756/3CCM756 To specify the phone number In the Phone field, type the RAS server s modem number. For example, F-24 Installing TraceMasterVue and Configuring Communication

365 RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System To specify the user name This is the same user name specified on the Network tab. Type the appropriate user name in the User Name field. To set the password to use Type the password associated with the selected user account in the Password field. The entry in the Password field is the password associated with the specified user. To specify the server s domain In the Domain field, type the RAS server computer name. Saving the Cardiograph Network Settings After configuring the Network and Net Connect tab settings, save the configuration. To save the configuration settings Touch Save. RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System The TraceMasterVue system can be configured to communicate with cardiographs as follows. It can be configured: As a RAS server, to support communication with a PageWriter Touch cardiograph over a dialup modem for transmitting or querying for ECGs. The previous sections of this appendix described this option. To support communication with a legacy PageWriter XL-series cardiograph (through a direct connection or over dialup modem) for transmitting or querying for ECGs. See the Installing TraceMasterVue and Configuring Communication, on the TraceMasterVue Documentation and Training CD; also provided on the TraceMasterVue server in TraceMasterVue\Help\TraceMasterVue_Manuals. To support both environments simultaneously (referred to as having a mixed fleet of cardiographs). The following sections describe this option. Adding RAS and Serial Data Communication Support to a TraceMasterVue System (below) Adding RAS to an Existing TraceMasterVue System that Supports Legacy Serial Data Communication on page F-29 Installing TraceMasterVue and Configuring Communication F-25

366 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue Adding RAS and Serial Data Communication Support to a TraceMasterVue System When adding RAS and legacy serial data communication support to a new or existing TraceMasterVue system, you must perform the following steps, in order: 1 Install RAS on the TraceMasterVue system by making TraceMasterVue a RAS server. See Setting Up TraceMasterVue as the RAS Server on page F-4. 2 For ports that will be used for legacy cardiograph support, remove RAS ownership of these ports. You must free all ports that you do not want RAS to manage, including the Fax port and all legacy direct connect ports. NOTE When RAS is initially configured on a system, RAS takes ownership of every serial communication port. A serial communication port cannot be configured for both RAS and legacy cardiograph support; you must reassign the ports as needed. See Removing Serial Communication Ports from RAS Ownership on page F For ports that will be used for legacy cardiograph support, reassign these ports to legacy data communication support. You use the TraceMasterVue System Configuration utility to configure ports in this manner. For details, see Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System in the Installing TraceMasterVue and Configuring Communication. 4 Reboot the system. NOTE If you do not reboot the TraceMasterVue system, none of the serial communication ports configured for legacy cardiograph support will support legacy data communication. Removing Serial Communication Ports from RAS Ownership To free serial communication ports from RAS ownership 1 On the TraceMasterVue server, click Start > All Programs > Administrative Tools > Routing and Remote Access. The Routing and Remote Access window appears. 2 In the left pane, right-click the Ports entry and select Properties from the menu. The Properties dialog box appears. F-26 Installing TraceMasterVue and Configuring Communication

367 RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System In the example above, the following serial communication ports are used by RAS: Courier V Everything EXT PnP (V90-X2) (COM4) Communications cable between two computers (COM3) 3 To free a port, in this example, Communication cable..., right-click this entry in the right pane and select Properties from the menu. The Properties dialog box appears. 4 Select the port to free in the list, in our example, Communication cable..., and click Configure. Installing TraceMasterVue and Configuring Communication F-27

368 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue 5 Clear all of the check boxes to free the serial communication port associated with the selected entry; then click OK to save your changes and return to the Ports Properties dialog box. Note that the port is no longer managed by RAS. 6 Click OK to close the dialog box and return to the Routing and Remote Access window. F-28 Installing TraceMasterVue and Configuring Communication

369 RAS and Serial Data Communication Co-Existing on a Single TraceMasterVue System Note that the selected port no longer appears in the Ports list. In this example, COM3 is no longer being used by RAS and can be configured for legacy cardiograph support. Adding RAS to an Existing TraceMasterVue System that Supports Legacy Serial Data Communication When adding RAS to an existing TraceMasterVue system that supports legacy serial data communication, you must perform the following steps, in order: 1 Using the TraceMasterVue System Configuration utility IO tab, verify which serial communication ports are currently configured for legacy cardiograph support. For details, see Configuring Ports for Legacy Cardiograph Communication in TraceMasterVue in the Installing TraceMasterVue and Configuring Communication. 2 Install RAS on TraceMasterVue by making TraceMasterVue a RAS server. See Setting Up TraceMasterVue as the RAS Server on page F-4. 3 For ports that will be used for legacy cardiograph support, remove RAS ownership of these ports. You must free all ports that you do not want RAS to manage, including the Fax port and all legacy direct connect ports. NOTE When RAS is initially configured on a system, RAS takes ownership of every serial communication port. A serial communication port cannot be configured for both RAS and legacy cardiograph support; you must reassign the ports as needed. See Removing Serial Communication Ports from RAS Ownership on page F Reboot the system. NOTE If you do not reboot the TraceMasterVue system, none of the serial communication ports configured for legacy cardiograph support will support legacy data communication. Installing TraceMasterVue and Configuring Communication F-29

370 Configuring Remote Access Service (RAS) for PageWriter Cardiographs and TraceMasterVue Adding Legacy Serial Data Communication Support to an Existing TraceMasterVue System that Supports RAS NOTE NOTE When adding legacy communication support to an existing TraceMasterVue system that supports RAS, you must perform the following steps, in order: 1 For ports that will be used for legacy cardiograph support, remove RAS ownership of these ports. You must free all ports that you do not want RAS to manage, including the Fax port and all legacy direct connect ports. When RAS is initially configured on a system, RAS takes ownership of every serial communication port. A serial communication port cannot be configured for both RAS and legacy cardiograph support; you must reassign the ports as needed. See Removing Serial Communication Ports from RAS Ownership on page F For ports that will be used for legacy cardiograph support, reassign these ports to legacy data communication support. You use the TraceMasterVue System Configuration utility to configure ports in this manner. For details, see Assigning COM Ports to Direct Connections and Modems on the TraceMasterVue System in the Installing TraceMasterVue and Configuring Communication. 3 Reboot the system. If you do not reboot the TraceMasterVue system, none of the serial communication ports configured for legacy cardiograph support will support legacy data communication. F-30 Installing TraceMasterVue and Configuring Communication

371 G Appendix RClinical Observation Result Interface NOTE NOTE HL7 is an ANSI standard for the exchange of health care-specific data computer applications. The name comes from Health Level 7, which refers to the top layer (Level 7) of the Open Systems Interconnection (OSI) layer protocol for the health environment. There are many resources on the World Wide Web that provide detailed information about HL7, the standards, components of a message, and the like. This appendix provides a high-level overview of how to configure HL7 export on your system, and also provides some details about the HL7 interface. It is intended to be used in conjunction with the OrderVue Installation and Configuration Guide (provided on the OrderVue Documentation CD). TraceMasterVue s HL7 interface does not support order entry requests (available with the OrderVue option), reporting of filter information, or querying ECG reports. The HL7 Export option provides you with multiple preconfigured result interface modules, described later in this appendix. If your site requires additional functionality, you can purchase the Philips order handling application, OrderVue. Each interface module requires a small amount of customization, described here. You will see many references to OrderVue in the configuration steps. The HL7 Export functionality relies on services and applications, including data mappers, that are shared with the OrderVue application. This appendix provides the following information: Before You Begin G-2 Configuring HL7 Export G-2 Configuring the Interface G-3 Selecting a Mapper G-3 Collecting Transmission Information G-4 Enabling HL7 Results Export G-5 Sharing the OrderVue Folder G-5 Configuring the Scheduler G-6 Defining Delimiters in the Mappers G-7 Configuring the Results + URL Mapper G-11 Configuring the MMQTransmitter Communication Client G-13 Resuming Scheduler Operation G-16 Testing MMQTransmitter Communication G-16 Configuring Workflow Rules G-17 Validating the HL7 Export Process G-19 G-1

372 Clinical Observation Result Interface HL7 Data Types G-20 XML to HL7 Data Mapping G-21 Sample HL7 Transmission G-23 Before You Begin Before proceeding, ensure you have this appendix, as well as the OrderVue Installation and Configuration Guide (provided on the OrderVue Documentation CD) printed and available for reference. Configuring HL7 Export The configuration process generally proceeds as follows: 1 First, determine which of the preconfigured interface modules best fits your needs, and choose the mapper to export ECG data. See page G-3. Options are text-only result (the default), text plus URL to TIFF image of ECG, and text plus Hex-encoded TIFF image of ECG, and text plus URL to PDF of the ECG. 2 Collect other transmission data, including server name, delimiters, HL7 version, and communication socket. See page G-4. 3 Enable HL7 export. See page G-5. 4 Configure a shared OrderTM folder **. See page G-5. 5 Add the appropriate scheduler. See page G-6. 6 Configure the Results + URL mapper (TMXML2HL7URL.MPR) **. See page G Set up the MMQTransmitter communication client. See page G Configure automated workflow rules in TraceMasterVue to export results. See page G Stop and restart TraceMasterVue services to incorporate your changes. See page Validate data communication. See page G-19. This appendix describes each of these steps in detail. ** These steps are only required if you are using the Results + URL mapper (TMXML2HL7URL.MPR). G-2 Configuring Cardiograph and TraceMasterVue Communication Guide

373 Configuring HL7 Export Configuring the Interface To be able to configure the mapper for use at your site, you need some information: The mapper you will use (see below) Transmission information, including the delimiters used in your data, as well as the HL7 version you are using (page G-4) Selecting a Mapper The HL7 Export option offers several configured result interfaces (called mappers) for your data export. Mapper Name HL7 ECG text-only result TMXML2HL7.MPR HL7 ECG text result and URL to TIFF image or PDF image of ECG TMXML2HL7URL.MPR HL7 ECG text result and HEX encoded TIFF image of ECG TMXML2HL7HEX.MPR Description Used for one-way standard HL7 text result output, and is used to process the ECG results directly from TraceMasterVue. There is no ECG order associated with this result. This is the default interface. Used for standard HL7 text result output, together with a URL pointer to a TIFF image or PDF image of the ECG. This image is temporarily stored in the OrderVue Interface folder, before it is transmitted to the HIS. Choosing this option requires the following adjustments: Reconfigure the OrderVue Scheduler Task column by replacing the entry TMXML2HL7.MPR with TMXML2HL7URL.MPR. Adjust the URL path in the mapper template HL7 segment 010_5 in Mapper Field rules. Used for standard HL7 text result output, together with a Hex-encoded TIFF image of the ECG. Choosing this option requires the following adjustments: Reconfigure the OrderVue Scheduler Task column by replacing the entry TMXML2HL7.MPR with TMXML2HL7HEX.MPR. Configure TraceMasterVue to export both a TIFF image and the ECG result (with the same filename) to a private queue. Record the mapper you selected for future reference. Selected Mapper Configuring Cardiograph and TraceMasterVue Communication Guide G-3

374 Clinical Observation Result Interface Collecting Transmission Information You will need the following information, as described in the steps below: The TraceMasterVue server name You will use this name when configuring data transmission, starting on page G-13. MSH delimiters and HL7 version You will specify the delimiters in use when configuring the mapper, on page G-7. You will specify the HL7 version number when configuring data transmission, starting on page G-13. Socket for data transfer You will use this information when configuring data transmission, starting on page G-13. To retrieve the TraceMasterVue server name 1 Right-click the My Computer icon on the TraceMasterVue server desktop and select Properties. 2 In the Properties dialog box, click the Computer Name tab, and record the full computer name in the space provided below, for future reference. Computer Name To record the MSH delimiters and HL7 version Determine the delimiters used by your interface in the MSH_1 field, and record them in the table on the following page for future reference. The first segment embedded in your HL7message is the message header (MSH). MSH_1 defines the delimiters used in your HL7 messages. These delimiters define the structure of the message, including the separators used for fields, components, and subcomponents, as well as the repeating and escape characters. Although these delimiters are normally standard within an interface (for example, HBOC or McKessan), you can customize them for your own site. For example, in the line below, ^~\& are the valid delimiters. MSH ^~\& IDX-PLW SFHM EKG ORM^O01 LW P 2.3 G-4 Configuring Cardiograph and TraceMasterVue Communication Guide

375 Configuring HL7 Export 3 Determine the Processing ID used in the MSH_11 field, and record it in the table below for future reference. For example, in the line below, P is the Processing ID: MSH ^~\& IDX-PLW SFHM EKG ORM^O01 LW P 2.3 Delimiters Processing ID 4 Determine the HL7 version used in the MSH_12 field, and record it in the table below for future reference. For example, in the line below, 2.3 is the HL7 version number: MSH ^~\& IDX-PLW SFHM EKG ORM^O01 LW P 2.3 Delimiters Version To determine the socket (IP address and port number) for HL7 result export Contact the system administrator and get the IP address and port number for the target HIS system. This is the system to which the transmitter will send the result data. You will need this information when configuring the transmitter, starting on page G-13. IP Address Port Enabling HL7 Results Export The HL7 Export functionality relies on services and applications, including data mappers, that are shared with the OrderVue application. To enable HL7 export, you must install the OrderVue application. This does not, however, enable OrderVue application access; that requires separate license activation. For details on enabling HL7 results export and configuring the Service Maker for MMQ, refer to Chapter 2 of the OrderVue Installation and Configuration Guide. Sharing the OrderVue Folder This step is only required if you are using the Results + URL mapper, TMXML2HL7URL.mpr. In order to the URL pointer to access the TIFF image or PDF image that is exported with the results, you must share the OrderTM Interface folder on the network. For details on setting up the share folders, refer to Chapter 2 of the OrderVue Installation and Configuration Guide. Configuring Cardiograph and TraceMasterVue Communication Guide G-5

376 Clinical Observation Result Interface Configuring the Scheduler The scheduler manages the transfer of exported ECG data from the TraceMasterVue server to the target system. To configure the scheduler 1 Click Start > OrderVue WebSelect > MMQ > MMQ Scheduler. The Scheduler window appears. 2 Click Pause. 3 Click File > Configuration. The Scheduler Configuration dialog box appears. G-6 Configuring Cardiograph and TraceMasterVue Communication Guide

377 Configuring HL7 Export 4 Place a check mark in the Minimize LINKScheduler check box. 5 In the Repetitive Tasks section, ensure that the command associated with the MMQ entry lists the mapper you have selected (see page G-3). By default, the command line is set to c:\ordertm\ltup.exe c:\ordertm\tmxml2hl7.mpr (for the Text Results Only mapper). For the Results + URL mapper, change the command line to c:\ordertm\ltup.exe c:\ordertm\tmxml2hl7url.mpr For the Results + Hex TIFF mapper, change the command line to c:\ordertm\ltup.exe c:\ordertm\tmxml2hl7hex.mpr 6 Click OK. 7 Minimize the Scheduler window by clicking the Minimize button. Continue to defining delimiters, as described next. Defining Delimiters in the Mappers You must define the delimiters in use at your site in the mapper that you will be using. Results-only (TMXML2HL7.mpr) Results + URL (TMXML2HL7URL.mpr) Results + HEX TIFF (TMXML2HL7HEX.mpr) Configuring Cardiograph and TraceMasterVue Communication Guide G-7

378 Clinical Observation Result Interface To define the delimiters for the mapper 1 In Windows Explorer, navigate to C:\OrderTM and double-click the entry, LTMapper.exe. The LINKTools HL7 Mapper window appears. Hold mouse over Mapper icon; it becomes the Config button G-8 Configuring Cardiograph and TraceMasterVue Communication Guide

379 Configuring HL7 Export 2 Place the mouse cursor over the Mapper icon; it changes to Config. Click Config or type Ctrl-N. Config button The Configuration window appears. 3 Select File > Open. The standard Windows Open dialog box appears. Configuring Cardiograph and TraceMasterVue Communication Guide G-9

380 Clinical Observation Result Interface 4 Open the appropriate mapper file in C:\OrderTM\: TMXML2HL7.mpr or TMXML2HL7URL.mpr or TMXML2HL7HEX.mpr The Configuration window appears. Delimiter field 5 In the Delimiters field, specify the delimiters your site uses for HL7 messages. You recorded this information previously on page G-4. 6 Click Save to save the entry and close the dialog box. When prompted to save the settings, click OK. 7 If you are using the Results + URL mapper, continue to the next step, Configuring the Results + URL Mapper on page G-11. If you are using either of the other mappers (Results only or Results + HEX TIFF), click Save in the Configuration window and exit the application. Then proceed to Configuring the MMQTransmitter Communication Client on page G-13. G-10 Configuring Cardiograph and TraceMasterVue Communication Guide

381 Configuring HL7 Export Configuring the Results + URL Mapper This step is only required if you are using the Text Results + URL mapper, TMXML2HL7URL.mpr. You must change the OrderVue configuration to point to this mapper instead of to the default. The screens may be slightly different than what is displayed here (they may show some additional fields), but the steps are the same. To configure the Results + URL mapper 1 Ensure you have already defined the delimiters, as described in Defining Delimiters in the Mappers on page G-7. You should now be displaying the Mapper Configuration window. 2 Click Show All. Show All button 3 Using the scroll bar on the right, scroll down to Segment 10_5, and double-click the Field Rule (M) in that row. Double-click M The Field Rules window appears. Configuring Cardiograph and TraceMasterVue Communication Guide G-11

382 Clinical Observation Result Interface Replace YOURSERVERSNAME with the name of your TraceMasterVue server machine 4 On the second line, between ADDINTOP=\\ and \OrderTM$\resultTIF\, type over the text YOURSERVERSNAME, and replace it with the name of the TraceMasterVue server (page G-4); then click Save to save the entry and close the dialog box. 5 In the Configuration dialog box, click Save again, and when prompted to replace the existing text, click Yes. Click OK to dismiss any other popup dialog boxes. 6 Click the close box (X at the top right of the windows) to close the mapper windows and exit. G-12 Configuring Cardiograph and TraceMasterVue Communication Guide

383 Configuring HL7 Export Configuring the MMQTransmitter Communication Client The transmitter is responsible for moving HL7 data from the TraceMasterVue system to the target HIS. To configure the MMQTransmitter client 1 Click Start > OrderVue WebSelect > MMQ > MMQ Transmitter. The OrderVue Result Configuration window appears. Options button 2 Click Options. The Options dialog box appears. Configuring Cardiograph and TraceMasterVue Communication Guide G-13

384 Clinical Observation Result Interface 3 Do the following: a b c d Ensure the Minimize on start application check box is selected. If desired, clear the Do not minimize after 3 minutes check box. Ensure the Detail log files check box is selected. These log files are useful for troubleshooting. They are saved within the OrderTM directory on the server. To enable the Detail log file: i In the Protocols section, ACK field, select Validate HL7 Message, and click Options. ii In the HL7 Validation Parameters dialog box, select the Write ACK File check box, then click... iii Navigate to C:\OrderTM\Config\MMQ\Archive!\SEND! and click Open. G-14 Configuring Cardiograph and TraceMasterVue Communication Guide

385 Configuring HL7 Export The dialog box now appears as follows: e f iv Click OK. In the TCP/IP address and Port # fields, set the HIS communication client socket information. This is the information you collected on page G-5. In the Protocols section ACK dropdown list, select Validate HL7 message; then click Options. The HL7 Validation Parameters dialog box appears. Configuring Cardiograph and TraceMasterVue Communication Guide G-15

386 Clinical Observation Result Interface g h In the Processing ID dropdown list, select the entry that matches what you already collected at your site (page G-4). In general, this will be P-Production. In the HL7 Version field, type the version number in use at your site (page G-4); then click OK. 4 Click OK to save changes and close the Options dialog box. 5 Click OK to save changes in the Configuration window. Do not close out of the application yet. You will test the connection in the next step, after restarting the scheduler. The Transmitter is now configured. The next step is to test the connection. Resuming Scheduler Operation Before you can test communication with the HIS, you must unpause (resume) Scheduler operation. To resume Scheduler operation 1 In the Task bar, click the Scheduler button to maximize it. 2 Click Resume in the menu bar. All OrderVue applications are now activated. You can now check the connection to the HIS, as described next. Testing MMQTransmitter Communication To test communication with the HIS 1 In the Transmitter for MMQ window, click Info. Click the Info button. The Remote IP address is displayed together with the time at which the connection was initiated. It may take a few minutes for this information to be displayed. 2 Minimize or close the window. As an alternative, you can use the ping command to validate the connection. G-16 Configuring Cardiograph and TraceMasterVue Communication Guide

387 Configuring HL7 Export To validate the connection using the ping command 1 Click Start > Run; then type cmd in the Run dialog box. A DOS prompt window appears. 2 Type the following command, substituting the actual IP address of the HIS machine: > ping <IP address> You should see Reply text indicating the connection is successful. 3 Close the Command window. Configuring Workflow Rules To export results from TraceMasterVue, you configure one or more automated workflow rules that are triggered when an ECG is confirmed. To export the clinical observation result, you configure a workflow rule, triggered by ECG confirmation, to export the result to the following queue: private$\mmqueue If you are using either the Result + URL or the Result + Hex TIFF mapper, you must configure a second workflow rule to export the TIFF or PDF file. For detailed information about workflow rules and how to define them, see Defining Automated Workflow Rules on page To configure a clinical observation result export rule 1 On the TraceMasterVue server, double-click the TM System Configuration icon, and log in. The System Configuration utility is launched, displaying the Global tab. 2 Click the Workflow tab, then click Add. The Add Workflow Rule dialog box appears. 3 Do the following: a b In the Action dropdown list, select Confirm. Select the Export check box. The Export Rule dialog box appears. c Specify the following values, then click OK: Format: Destination: PhilipsXML Queue Configuring Cardiograph and TraceMasterVue Communication Guide G-17

388 Clinical Observation Result Interface Queue: private$\mmqueue 4 Click OK in the Add Workflow Rule dialog box to save the rule and return to the Workflow tab. 5 Proceed as follows: If you are using the default Results-only mapper, TMXML2HL7.mpr, you are almost done. Restart TraceMasterVue services (page 6-29). If you are using either the Result + URL (TMXML2HL7URL.mpr) or the Result + Hex TIFF (TMXML2HL7HEX.mpr) mapper, proceed to the next step to add a second workflow rule. To configure a TIFF or PDF export workflow rule 1 On the Workflow tab, select the workflow rule you just added from the Currently defined rules list, and click Replicate. The Replicate command prepopulates the Add dialog box with the settings of the selected rule, making it easy to quickly change just the export format and directory, and leave the rest of the settings the same as the rule you just added. The Add Workflow Rule dialog box appears, with the same settings specified as the rule you selected. 2 Click Configure to the right of the Export check box. The Export Rule dialog box appears. d Specify the following values, then click OK: Format: Destination: Directory: TIFF or PDF Directory C:\OrderTM\ResultTIF or C:\OrderTM\ResultPDF G-18 Configuring Cardiograph and TraceMasterVue Communication Guide

389 Validating the HL7 Export Process 3 Click Finish in the System Configuration utility to exit the application. 4 You must stop and restart TraceMasterVue services for the changes to take effect (page 6-29). Validating the HL7 Export Process After configuring the mapper and export rules, you must verify that the system works properly and is transmitting data as expected. This example exports with a TIFF image. To validate data communication 1 From a client system using ECGVue/PharmaVue, confirm a test ECG. 2 Using Windows Explorer, navigate to C:\OrderTM\Backup\ResultS. 3 Using Wordpad, open the appropriate HL7 result message, and verify that the text result file (TMXML2HL7 output) is properly formatted. For example, the text result file (TMXML2HL7 output) should look similar to the following: MSH ^~\& TMV TMV HIS ECG ORU^R P 2.3 PID $$$ Fromberg^James^Mi M OBR Standard 12 Lead Report ^^^ F ^^^^^ OBX 1 ST HEXENCODE F 4 Verify that the TMXML2HL7URL message is properly formatted. Also check that the pointer to the TIFF image is correct, and the TIFF image is viewable. For example, the text result file should look similar to the following: MSH ^~\& TMV TMV HIS ECG ORU^R P 2.3 PID $$$15906 HALFERSTON^MARY ANNE^ F OBR Standard 12 Lead Report ^^^ F ^^^^^ OBX 1 ST TIFFile \\tracemastervue3\ordertm$\resulttif\ d e77c5f0029.TIF F 5 Verify that the TMXML2HL7HEX file is 500K or greater in size and includes the Hex encoded TIFF image. For example, the text result file should look similar to the following: MSH ^~\& TMV TMV HIS ECG ORU^R P 2.3 PID $$$ Fromberg^James^Mi M OBR Standard 12 Lead Report ^^^ F ^^^^^ OBX 1 ST HEXENCODE 49492a002cb fe d b864361d0f a4562d178c...(very long encoded image 500k plus) 00803fe d b864361d0f a4562d 6 Verify that the result has been exported to your HIS and that the format is correct. The configuration process is now complete. Configuring Cardiograph and TraceMasterVue Communication Guide G-19

390 Clinical Observation Result Interface HL7 Data Types The HL7 interface supports the following data types: Patient information Age/sex/medications (used for computer analysis) Name/patient ID Previous diagnosis used by human overreader Additional patient information Waveform data for each lead of each channel for which the ECG has been recorded Channel definition Timing information Waveform data points Computer-generated analysis Measurements based on waveform data G-20 Configuring Cardiograph and TraceMasterVue Communication Guide

391 HL7 Data Types XML to HL7 Data Mapping The Message Mapper application is responsible for mapping all data from the XML ECG to the appropriate segments in the HL7 message. ## Field Description Value or XML tag from ECG Notes MSH_3 SendingApplication LINKTools hard coded in mapper MSH_4 SendingFacility Trace Master hard coded in mapper MSH_5 ReceivingApplication ECG hard coded in mapper MSH_6 ReceivingFacility HIS hard coded in mapper MSH_7 MessageDateTime YYYYMMDDhhmmssuuu assigned on transmission MSH_9 MessageType ORU^R01 hard coded in mapper MSH_11 ProcessingID P hard coded in mapper MSH_12 HL7VersionID 2.3 hard coded in mapper PID_3 MRN <patientid> PID_5_1 LAST NAME <lastname> PID_5_2 FIRST NAME <firstname> PID_5_3 MIDDLE NAME <middlename> PID_7 DATE OF BIRTH <dateofbirth> unmapped PID_8 SEX <sex> PID_10 RACE PID_18 PatientAccountNumber not in XML PID_19 PatientSocialSecurityNumber not in XML OBR_2 EXTRA FIELD 1 <userdefine> <value> first user-defined value OBR_4 ReportDescription <reportdescription> OBR_6 RequestedDateTime assigned by mapper OBR_7 ObservationDateTime assigned by mapper OBR_8 ObservationEndDateTime assigned by mapper OBR_16_2 OBR_16_3 OBR_16_4 REQUESTED BY LAST NAME REQUESTED BY FIRST NAME REQUESTED BY MIDDLE NAME not in XML not in XML not in XML Configuring Cardiograph and TraceMasterVue Communication Guide G-21

392 Clinical Observation Result Interface ## Field Description Value or XML tag from ECG Notes OBR_25 ResultStatus C hard coded in mapper OBR_27_6 STAT unmapped OBX - ALL OBX_11 ObservationResultStatus C hard coded in mapper OBX- Variation 1 tags within <globalmeasurements> OBX_3 ObservationIdentifier element name OBX_5 ObservationValue element value OBX- Variation 2 Tags following <severity> up to </interpretations> OBX_2 ValueType ST hard coded in mapper OBX_3 ObservationIdentifier element name OBX_5 ObservationValue element value OBX- Variation 3 OBX_2 ValueType ST hard coded in mapper OBX_3 ObservationIdentifier TIFFile hard coded in mapper OBX_5 ObservationValue <documentname> augmented in mapper G-22 Configuring Cardiograph and TraceMasterVue Communication Guide

393 HL7 Data Types Sample HL7 Transmission HL7 Transmission from TraceMasterVue (LinkMedical). This information obtained empirically from an actual HL7 transmission of a full TraceMasterVue ECG, combined with mapper information via LinkTools. MSH ^~\& LINKTools Trace Master ECG HIS ORU^R P 2.3 PID lname^fname^mn M OBR Standard 12 Lead Report ^^^ C ^^^^^ OBX 1 NH qtintdispersion 1 0 C OBX 2 NH numberofcomplexes 1 0 C OBX 3 NH numberofgroups 1 0 C OBX 4 NH qamessagecode 1 Missing lead(s) C OBX 5 NH qaactioncode 1 Poor ECG, retry if possible C OBX 6 NH atrialrate 1 0 C OBX 7 NH lowventrate 1 0 C OBX 8 NH meanventrate 1 0 C OBX 9 NH highventrate 1 0 C OBX 10 NH deltawavecount 1 0 C OBX 11 NH deltawavepercent 1 0 C OBX 12 NH bigeminycount 1 0 C OBX 13 NH bigeminystring 1 0 C OBX 14 NH trigeminycount 1 0 C OBX 15 NH trigeminystring 1 0 C OBX 16 NH wenckcount 1 0 C OBX 17 NH wenckstring 1 0 C OBX 18 NH flutterfibcount 1 0 C OBX 19 ST severity 1 - DEFECTIVE ECG - C OBX 20 ST statementcode 1 12ML C OBX 21 ST leftstatement 1 ALL 12 LEADS ARE MISSING C OBX 22 ST statementcode 1 QMMLD C OBX 23 ST leftstatement 1 MISSING LEAD(S): I II III avr avl avf V1 V2 V3 V4 V5 V6 C OBX 24 ST TIFFile \\viperrd-ml350\ordertm$\resulttif\02f e-11d f20029.tif C Configuring Cardiograph and TraceMasterVue Communication Guide G-23

394 Clinical Observation Result Interface G-24 Configuring Cardiograph and TraceMasterVue Communication Guide

395 H Appendix SUsing TraceMasterVue with the HeartStart MRx Defibrillator The 12-Lead Transfer Station can transmit ECGs to a TraceMasterVue system. This allows ECGs acquired at a HeartStart MRx defibrillator to be stored, viewed, and processed in the TraceMasterVue system. Before proceeding, ensure you have available the HeartStart 12-Lead Transfer Station version 2.8 User Guide and the 12-Lead Transmission Implementation Guide. This appendix provides the following information: System Requirements H-1 Configuring TraceMasterVue and Defibrillator Communication H-2 Configuring the Defibrillator for TraceMasterVue Communication.... H-2 Configuring the 12-Lead Transfer Station for TraceMasterVue Communication H-3 System Requirements To communicate with a 12-Lead Transfer Station, the following application versions must be installed on their respective systems: 12-Lead Transfer Station, version 2.8 (or later) TraceMasterVue, version B.02 (or later) The systems must be able to access each other over the LAN. H-1

396 Using TraceMasterVue with the HeartStart MRx Defibrillator Configuring TraceMasterVue and Defibrillator Communication TraceMasterVue supports import of ECGs from the HeartStart MRx defibrillator via the 12-Lead Transfer Station. You need to configure all three components for data transfer to occur: On TraceMasterVue, no changes are required. The 12-Lead Transfer Station transmits ECGs to the EMSCOMM virtual directory. These ECGs are then imported into the TraceMasterVue database in the same manner as other PageWriter Touch ECGs. On the defibrillator, you must configure the TraceMasterVue server as a transmission site. On the 12-Lead Transfer Station, you must configure the TraceMasterVue server as an Application Destination. You can then also add TraceMasterVue to an Auto Send list to have ECGs automatically sent to the system upon receipt. Configuring the Defibrillator for TraceMasterVue Communication On the defibrillator, you must configure the TraceMasterVue server as a transmission site (a site is the final destination of a 12-lead report). NOTE In 12-Lead Transfer Station, a site is called a destination. This information is provided here for your convenience, and is excerpted from the 12-Lead Transmission Implementation Guide. Refer to the documentation provided with the HeartStart MRx for the most up-to-date instructions. To add a site on the HeartStart MRx defibrillator 1 From the 12-Lead Transmission Configuration menu, select Sites. A list of configured sites is displayed. If fewer than 20 sites are defined, the Add Sites button is available. 2 Click Add Site. The Sites screen is displayed. 3 Enter the site information. 4 In the Site Type field, select TraceMaster and specify the IP address, domain name, or computer name of the TraceMasterVue server. You do not need to enter the prefix ( To send the report to multiple TraceMaster systems, you must also configure Auto Send Lists in 12-Lead Transfer Station. Refer to the 12-Lead Transmission Implementation Guide for details. H-2 Installing TraceMasterVue and Configuring Communication

397 Configuring TraceMasterVue and Defibrillator Communication Configuring the 12-Lead Transfer Station for TraceMasterVue Communication You can configure the 12-Lead Transfer Station to automatically forward ECGs coming from defibrillators, or you can transmit them manually. You must add each TraceMasterVue server (if more than one) to the TraceMaster tab (in Tools > Options). To configure automatic transmission, you must also define an Auto Send list for TraceMasterVue. Use the Configuration Auto Send Lists window to create the list. This information is provided here for your convenience, and is excerpted from the HeartStart 12-Lead Transfer Station 2.8 User Guide. Refer to the documentation provided with the 12-Lead Transfer Station for the complete and most up-to-date instructions. To specify TraceMasterVue as an application destination Use the Configuration Application window to set up an application destination. An application destination requires a name, location, and type of data connection. NOTE To complete the dial-up connection for an application, you might need to know the User Name and Password for the machine account you are using to connect. For more information, see Adding Network Connections in the 12-Lead Transfer Station 2.8 User Guide. 1 In the Configuration Auto Send Lists window, select or type an Auto Send List name in the Name field. 2 In Application, select Add from the list. 12-Lead Transfer Station displays the Configuration - Application window. 3 In Name, type a name for the application destination. 4 In Description, type a brief description that describes the use of the application. 5 In Select a type, select TraceMasterVue from the list. 6 In Location, type the IP address, domain name, or computer name, for the TraceMasterVue server in the form 7 Specify the connection type. 8 Click OK to add the destination in the Summary area. 9 Click Apply to save the destination in the Auto Send List. For additional information about configuring the 12-Lead Transfer Station to TraceMasterVue communication, refer to the HeartStart 12-Lead Transfer Station version 2.8 User Guide and the 12-Lead Transmission Implementation Guide. Installing TraceMasterVue and Configuring Communication H-3

398 Using TraceMasterVue with the HeartStart MRx Defibrillator H-4 Installing TraceMasterVue and Configuring Communication

399 Appendix TUsing TraceMasterVue with the IntelliVue Information Center I This appendix describes how to set up the Philips IntelliVue Information Center (IIC) to enable access between IntelliVue bedside and hallway monitors and the TraceMasterVue ECG database. Once enabled, users can quickly and easily view individual patients ECGs at the monitor. This appendix provides the following information: System Requirements I-2 IntelliVue Requirements I-2 TraceMasterVue Requirements I-2 Installing ECGVue or PharmaVue on Client Systems I-3 Configuring TraceMasterVue and IntelliVue Communication I-3 Configuring TraceMasterVue to Communicate with IntelliVue I-3 Configuring Location Information for TraceMasterVue IntelliVue Communication I-4 Configuring TraceMasterVue and Device Location Fields I-4 Location Matching in TraceMasterVue I-4 Location Matching when Importing an ECG from an IntelliVue or Antares System I-5 Mapping the IntelliVue/Antares Institution Code I-5 Institution Code Mapping Format I-6 Institution Code Mapping Rules I-7 Adding and Configuring the Registry Values I-8 Adding the Registry Values I-8 Configuring the Registry Values I-10 I-1

400 Using TraceMasterVue with the IntelliVue Information Center System Requirements You must have the following options installed and enabled at your site to allow ECG transmission between the IntelliVue and TraceMasterVue systems. For details on ordering options, see your Philips representative. IntelliVue Requirements Check with your Philips representative for the supported versions. IntelliVue Information Center (IIC) Application Server option TraceMasterVue Requirements TraceMasterVue version B or later Philips Clinical Interface option I-2 Installing TraceMasterVue and Configuring Communication

401 Installing ECGVue or PharmaVue on Client Systems Installing ECGVue or PharmaVue on Client Systems The client system must be running Windows XP or Windows 2000, and must have network access to the TraceMasterVue server. For detailed information, see Installing ECGVue/ PharmaVue on Client Systems on page Configuring TraceMasterVue and IntelliVue Communication TraceMasterVue supports import and export of ECGs with the Philips IntelliVue Information Center (IIC). On the TraceMasterVue side, the installation program creates, by default, the IntelliVue shared directory. The share name for the directory is set to PMDExport. In addition, TraceMasterVue configuration requires a Philips representative to: Enable IntelliVue support Create a specific IntelliVue user and password for access to the TraceMasterVue database On the IntelliVue side, your site must have the Application Server option installed. In addition, IntelliVue configuration requires a Philips representative to: Enable TraceMasterVue support on the database server Ensure the TraceMasterVue server hostname comprises alphanumeric characters only Enable 12-lead export on each client (bedside and hallway monitors) Configure the Application Server, including installing ECGVue/PharmaVue and running the Application Server Configuration utility to make ECGVue/PharmaVue available to all of the linked bedside monitors Once configured, the user can both export a recently acquired ECG to TraceMasterVue, and pull up a patient s ECG at the bedside. NOTE Configuring TraceMasterVue to Communicate with IntelliVue Contact your Philips representative to enable the IntelliVue option in TraceMasterVue and set up the appropriate user and group association, once purchased. Use a hostname for the TraceMasterVue server that contains only a maximum of 15 alphanumeric characters. The IIC cannot resolve hostnames that are greater than 15 characters in length or that contain special characters, including any of the following:., - _ * (period, comma, hyphen, underscore, asterisk, and so on) The IntelliVue system uses the Windows user, PMDAppSrv, which is associated with the TraceMaster_Tech group. The permissions associated with the TraceMaster_Tech group are given to the bedside user. For details about the permissions associated with TraceMaster groups, see About TraceMasterVue-Specific Windows Groups on page A-7. Installing TraceMasterVue and Configuring Communication I-3

402 Using TraceMasterVue with the IntelliVue Information Center SEARCH In the System Configuration utility online help, click the Search button and type permissions to quickly retrieve detailed information. When the end user launches ECGVue/PharmaVue at the bedside, the application automatically logs the user into the system using this user ID and the permissions associated with the TraceMaster_Tech group. Configuring Location Information for TraceMasterVue IntelliVue Communication The location identifies where an ECG was acquired, and, on TraceMasterVue, comprises three levels: institution, facility, and department. Location information is organized as a hierarchy, with institutions containing one or more facilities, which in turn comprise one or more departments. You define institutions, facilities, and departments using the System Configuration utility Locations tab. Individual locations are identified by both a code and descriptive text. For additional information about locations, refer to Appendix B, Using Location Information in TraceMasterVue. Configuring TraceMasterVue and Device Location Fields It is important that the location-related information that you specify in TraceMasterVue match the location information configured for the cardiographs and other medical devices (for example, bedside monitors) at your site that will send ECGs to the TraceMasterVue database. In addition, the naming convention you decide to use for institutions may be different depending on whether your site uses PageWriter Touch or Trim cardiographs, legacy PageWriter XL-series cardiographs, IntelliVue, or a mixed fleet. But first, you must understand how TraceMasterVue processes location information on incoming ECGs. Location Matching in TraceMasterVue TraceMasterVue processes location information differently depending on whether the ECG is being imported or exported, and which device sourced the ECG. TraceMasterVue performs the matching calculations in the following order, using the code and/or name in each case: 1 Institution information 2 Facility information 3 Department code Each location evaluation is performed using the following rules: 1 In situations in which the ECGs from legacy devices do not contain facility code information, TraceMasterVue assigns the default Unidentified facility code that applies to the associated institution. I-4 Installing TraceMasterVue and Configuring Communication

403 Configuring Location Information for TraceMasterVue IntelliVue Communication 2 If the legacy or non-legacy ECG institution code is not specified or not defined on TraceMasterVue, TraceMasterVue assigns the default Unidentified institution code, code If the legacy or non-legacy ECG facility code is not specified or not defined on TraceMasterVue for the institution, TraceMasterVue assigns the default Unidentified facility code for the current institution. This default facility code comprises the associated institution code plus 00. For example, if the current institution is 524, the default facility code is set to If the legacy or non-legacy ECG department code is not specified or not defined on TraceMasterVue for the facility, TraceMasterVue assigns the default Unidentified department code for the current facility. The default department code is 00. Location Matching when Importing an ECG from an IntelliVue or Antares System TraceMasterVue imports ECGs from legacy devices, including cardiographs (PageWriter XLi, PageWriter 300pi) and ECG management systems (TraceMaster C), as well as the IntelliVue Information Center (if you have option C20 or TraceMasterVue Enterprise Edition, which includes this option). In most cases, ECGs from legacy devices only contain institution and department code information. ECGs source with an IntelliVue system have institution and department information; there is no concept of a facility. With ECGs from an IntelliVue system, the institution code can be mapped to an institution and facility code in TraceMasterVue. If the institution code is not mapped, the default Unidentified facility (described in item 3, above) is used. Mapping the IntelliVue/Antares Institution Code TraceMasterVue allows you to map the incoming IntelliVue (or Antares) Institution code to the TraceMasterVue Institution Facility hierarchy through the use of two registry keys: ENABLE_LOC_OVERLOAD DWORD registry key that controls whether IntelliVue institution code mapping is enabled. Options are 0 (disabled) and 1 (enabled). NOTE This key also controls the format used for mapping legacy cardiograph Location field information to the TraceMasterVue three-tier hierarchy. For details, refer to the Installing TraceMasterVue and Configuring Communication, provided on the TraceMasterVue Documentation and Training CD, as well as on the TraceMasterVue server, in TraceMasterVue\Help\TraceMasterVue_Manuals. LOC_OVERLOAD_SETTING String registry key that specifies the format for mapping the IntelliVue Institution code to the TraceMasterVue Institution and Facility codes, as described below. The setting for this key only applies when ENABLE_LOC_OVERLOAD = 1. Installing TraceMasterVue and Configuring Communication I-5

404 Using TraceMasterVue with the IntelliVue Information Center For details on adding and updating these registry keys, see Adding and Configuring the Registry Values on page I-8. Institution Code Mapping Format When the ENABLE_LOC_OVERLOAD registry key is set to 1, TraceMasterVue maps the incoming IntelliVue (or Antares) Institution code to the TraceMasterVue Institution Facility codes based on the setting of the LOC_OVERLOAD_SETTING registry key, as follows. The registry key value is defined as: LOC_OVERLOAD_SETTING = X:Y. The first X digits of the Institution code map to the new Institution code, and the next Y digits map to a Facility code. The Institution code may contain a maximum of 32 digits, including the colon. LOC_OVERLOAD_SETTING = <empty> or the registry key does not exist. When the registry key either does not exist or does not have a specified value, the default mapping of 1:2 is used. When the default setting is used, the incoming Institution code must have exactly 3 digits. Otherwise, the code is not mapped to Institution/Facility; rather, it remains as the Institution code and the default Unidentified facility setting is used. For detailed information about how mapping takes place, see Institution Code Mapping Rules on page I-7. Examples Example 1: The IntelliVue Institution code (6 digits) can be mapped to Institution and Facility codes in TraceMasterVue using any of these settings (X+Y must equal 6): 1:5, 5:1, 2:4, 4:2, 3:3 If LOC_OVERLOAD_SETTING = 2:4, the ECG in TraceMasterVue will show Institution code 14 and Facility code If 3:3 is specified, the Institution code will be 146 and the Facility code will be 806. And so on. Example 2: The IntelliVue Institution code (18 digits) can be mapped to Institution and Facility codes in TraceMasterVue using any of these settings (X+Y must equal 18): 1:17, 17:1, 2:16, 16:2, 3:15, 15:3,... If LOC_OVERLOAD_SETTING = 3:15, the ECG in TraceMasterVue will show Institution code 123 and Facility code If 1:17 is specified, the Institution code will be 1 and the Facility code will be And so on. I-6 Installing TraceMasterVue and Configuring Communication

405 Configuring Location Information for TraceMasterVue IntelliVue Communication Institution Code Mapping Rules The incoming Institution code will be mapped when ALL of the following conditions are met. Each condition is checked in the order shown below: 1 ECG sourcing device is IntelliVue or Antares. 2 The registry DWORD value ENABLE_LOC_OVERLOAD is set to 1. 3 The registry string value LOC_OVERLOAD_SETTING is either: a Present and set to a particular X : Y value b Present and not set to any value (empty) c Absent In the case of options b or c, the default X:Y format of 1:2 is used. 4 The number of digits in the Institution code (<institutionid> XML node) has the same number of digits as the sum of the X:Y value. Therefore, in the case of options 3.b and 3.c, where the sum of the X:Y value is 3, the Institution code must have 3 digits. 5 The XML node <institutionlocationid> (which corresponds to the Facility code) is absent or empty. If any of these conditions is not met, that is, ENABLE_LOC_OVERLOAD = 0, or the number of digits does not match the sum of the X:Y registry value, or the <institutionlocationid> node has a value, the incoming Institution code is not mapped to Institution/Facility in TraceMasterVue. The ECG in TraceMasterVue will show the Institution code with the same value as in the incoming ECG, and the Facility code will be set to the default Unidentified facility setting. For details about Unidentified locations, see About Unidentified Locations on page B-15. Installing TraceMasterVue and Configuring Communication I-7

406 Using TraceMasterVue with the IntelliVue Information Center Adding and Configuring the Registry Values To enable Institution mapping, two registry values must be added to your system, and configured: ENABLE_LOC_OVERLOAD (below) LOC_OVERLOAD_SETTING Adding the Registry Values You must first add the registry values to the registry key, and then configure the desired settings. To add the ENABLE_LOC_OVERLOAD DWORD value to the registry 1 Run regedit and navigate to the HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS registry key. 2 Right-click the EMS registry key and select New, then DWORD Value from the popup menus. An entry appears in the right pane, labeled New Value #1. 3 Type the name ENABLE_LOC_OVERLOAD. The registry value is now added. I-8 Installing TraceMasterVue and Configuring Communication

407 Configuring Location Information for TraceMasterVue IntelliVue Communication To add the LOC_OVERLOAD_SETTING string value to the registry 1 Run regedit and navigate to the HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS registry key. 2 Right-click the EMS registry key and select New, then String Value from the popup menus. An entry appears in the right pane, labeled New Value #1. 3 Type the name LOC_OVERLOAD_SETTING. The registry value is now added. To configure the value now, continue to step 2 of the next procedure. Otherwise, close out of the registry editor. The next step is to configure the registry values to determine whether and how the Institution code will be mapped. Installing TraceMasterVue and Configuring Communication I-9

408 Using TraceMasterVue with the IntelliVue Information Center Configuring the Registry Values To configure the ENABLE_LOC_OVERLOAD DWORD value 1 Run regedit and navigate to HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS/ ENABLE_LOC_OVERLOAD. 2 Double-click the ENABLE_LOC_OVERLOAD entry. The Edit DWORD Value dialog box appears. 3 In the Value data field, type 0 or 1, then click OK to save your changes. 0 Do not enable Institution code mapping 1 Enable Institution code mapping To configure the LOC_OVERLOAD_SETTING string value 1 Run regedit and navigate to HKEY_LOCAL_MACHINE/SOFTWARE/Philips/EMS/ LOC_OVERLOAD_SETTING. 2 Double-click the ENABLE_LOC_OVERLOAD entry. The Edit String dialog box appears. 3 In the Value data field, type the appropriate X:Y value pair, then click OK to save your changes. For details on the format, see Institution Code Mapping Format on page I-6. I-10 Installing TraceMasterVue and Configuring Communication

409 Appendix UConfiguring OrderVue for Use with TraceMasterVue and Cardiographs J This appendix provides a high-level overview of the Philips order handling system, OrderVue, and provides information about configuring the Results queue for ECG export upon confirmation. This appendix provides the following information: About OrderVue J-2 Installing and Configuring OrderVue J-2 Configuring Order-Related Settings for TraceMasterVue J-2 Configuring Primary Fields for Order Reconciliation J-3 Exporting ECGs for Final Order Processing J-4 Setting Up Order Inboxes on the Cardiographs J-6 Creating an Inbox J-7 Creating Inboxes on PageWriter Touch Cardiographs J-7 Setting General Order Settings on the Cardiograph J-9 Setting General Order Settings J-9 Testing Order Inbox Connectivity J-9 Editing Inbox Settings J-10 Order Data Table J-11 Configuring the ADT Option J-21 Before proceeding, ensure you have available the filled out Order Inboxes worksheet (page 2-18). For additional information about OrderVue, see the following documentation: Using OrderVue with TraceMasterVue. Describes how to search for and review orders, and reconciling them with ECGs within the TraceMasterVue client application. Also describes order workflow, order states, and use of the order outbox (inbox, on the cardiograph). PageWriter Touch Instructions for Use and WebSelect Utility Quick Help Card. Describes how to configure OrderVue and cardiographs, as well as how to download orders to the cardiographs. OrderVue Installation and Configuration Guide. Describes how to configure OrderVue for use at your site, including configuring communication with TraceMasterVue and your HIS. J-1

410 Configuring OrderVue for Use with TraceMasterVue and Cardiographs About OrderVue The OrderVue order handling system allows your site to manage the flow of order information from your HIS to the cardiographs, then into TraceMasterVue, and finally back to the HIS for billing and final processing. Used in conjunction with TraceMasterVue, OrderVue helps automate the process of reconciling acquired ECGs to outstanding orders. OrderVue is a set of applications and utilities that are installed on the TraceMasterVue server, with which users generally do not interact directly. Rather, they use the cardiograph and the TraceMasterVue client application, ECGVue or PharmaVue, to locate and retrieve orders, then match them to acquired ECGs, and finally to export the results back to the HIS. After an order is entered into the information system in use at the site, salient information about the order, including patient name, ID, location, date, order ID, and so on is passed to OrderVue. Cardiograph users can download orders from the OrderVue database to the cardiographs, then send the acquired ECG to TraceMasterVue. ECGVue/PharmaVue users can retrieve and review ECGs and orders, and manually reconcile those orders that cannot be automatically matched with an ECG. After the ECG is acquired, overread, and confirmed in ECGVue/PharmaVue, TraceMasterVue exports the ECG data (via an automated workflow rule) to a configured queue or directory. OrderVue regularly polls this location and retrieves the contents. Finally, OrderVue sends the results and confirmed ECG report back to the HIS for final processing. Installing and Configuring OrderVue For details on installing the OrderVue option and configuring communication with the TraceMasterVue system, refer to the OrderVue Installation and Configuration Guide. For additional configuration information, see: For details on configuring order reconciliation and result settings in TraceMasterVue, see Configuring Order-Related Settings for TraceMasterVue, below. After ECGs are acquired and imported into TraceMasterVue, they are reconciled to orders, and overread. Once confirmed, ECGs are exported, as the result of a workflow rule, to a configured location (either a queue or directory). The Results queue is configured upon system installation and configuration. However, you must configure workflow rules to export ECGs as appropriate. For details on configuring order inboxes on the PageWriter Touch cardiograph, see Setting Up Order Inboxes on the Cardiographs on page J-6. Configuring Order-Related Settings for TraceMasterVue Once OrderVue is installed, communication is established, and mappers are defined (as described in the OrderVue Installation and Configuration Guide and related documents), you can configure order settings using the TraceMasterVue System Configuration utility. You will define primary fields for reconciliation (below), as well as define one or more workflow rules to process results once an ECG is confirmed and matched to an order (page J-4). J-2 Installing TraceMasterVue and Configuring Communication

411 Configuring Order-Related Settings for TraceMasterVue Configuring Primary Fields for Order Reconciliation If you purchased the Orders option or the HL7 option, the System Configuration utility Orders tab allows you to configure message queues for communication between TraceMasterVue and other applications, such as your HIS or order management system. In addition, you can specify which fields must match between an order and an associated ECG for them to be automatically reconciled within TraceMasterVue. The Order Match settings section displays the fields you can set as primary fields, that is, they must match between an order and the associated ECG for them to be marked as Reconciled. You can select zero or more options. If the primary fields in an incoming ECG do not match an existing order, the ECG is identified as missing an order, which can be manually reconciled within ECGVue/PharmaVue. To specify primary fields 1 Select the check boxes for the fields whose values must match in order for the ECG and associated order to automatically reconcile. Field Order Number Patient ID Account Number Description This option is required and is always selected. At a minimum, the order number must match between the order and ECG for automatic reconciliation to occur. When selected, the patient ID specified in the order and ECG must match for automatic reconciliation to occur. When selected, the account number specified in the order and ECG must match for automatic reconciliation to occur. Installing TraceMasterVue and Configuring Communication J-3

412 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Field Last Name Description When selected, the last name specified in the order and ECG must match for automatic reconciliation to occur. * If you use PageWriter XL-series cardiographs, see Note below. Date of Birth When selected, the date of birth specified in the order and ECG must match for automatic reconciliation to occur. * If you use PageWriter XLi cardiographs, see Note below. Sex When selected, the gender specified in the order and ECG must match for automatic reconciliation to occur. NOTE If your site uses PageWriter XLi cardiographs (whether alone or in addition to PageWriter Touch cardiographs), do not select Date of Birth or Last Name as primary fields. The PageWriter XLi cardiograph uses a single field, Name, to contain both the first and last name of the patient; it also uses an Age, rather than Date of Birth, field. Since the content of these fields cannot match the values in the ECG in TraceMasterVue, if they are specified as primary fields, these ECGs will not be able to be automatically reconciled with an associated order. 2 Click Finish to accept the changes. 3 Restart IIS and TraceMasterVue services for the changes to take effect. Exporting ECGs for Final Order Processing When working with orders, you can define a variety of workflow rules to export ECG and order information back to the OrderVue system for further processing. The following two rules are commonly used to work with ECGs and order data. Export upon import into the TraceMasterVue database (upon store) Used primarily to notify the HIS that an ECG associated with an order has been acquired and is pending verification and overread. Export upon confirmation of a reconciled ECG (page J-5) Used to send results back to the HIS to complete processing of an order. The following examples illustrate how to define each of these rules. To define an Export Upon Store rule 1 On the System Configuration utility Workflow tab, click Add. The Add Workflow Rule dialog box appears. 2 In the Action list, select Store. J-4 Installing TraceMasterVue and Configuring Communication

413 Configuring Order-Related Settings for TraceMasterVue 3 In the Rule section, select Export. The Export dialog box appears. 4 In the Export dialog box, select the following options: Format: Destination: Queue Name: Orders HL7 Queue private$\results To define an Export Upon Confirm rule 1 On the System Configuration utility Workflow tab, click Add. The Add Workflow Rule dialog box appears.. 2 In the Action list, select Confirm. 3 In the Rule section, select Export. The Export dialog box appears. 4 In the Export dialog box, select the following options: Format: Destination: Queue Name: Orders HL7 Queue private$\results Installing TraceMasterVue and Configuring Communication J-5

414 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Setting Up Order Inboxes on the Cardiographs The OrderVue order handling software that resides on the TraceMasterVue ECG Management System has a specific group of settings that need to be defined on the cardiograph. These settings determine what orders are assigned to a specific inbox on the cardiograph, and what functions are available for this specific inbox. An inbox resides solely on the cardiograph, and may consist of several OrderVue outboxes. A cardiograph inbox can be assigned any name that gives meaning to the cardiograph user, or provides meaning within a larger configured orders system. Figure J-2 OrderVue outbox to Cardiograph inbox configuration Briefly, the configuration process for OrderVue settings on cardiographs includes the following steps: 1 Ensure that all TraceMasterVue Remote Site settings are accurate and complete. 2 Test the connectivity between the cardiograph and the configured TraceMasterVue Remote Site. If it is successful, proceed to configure OrderVue settings on the cardiograph. 3 On the Orders screen in Configuration, select a TraceMasterVue remote site. J-6 Installing TraceMasterVue and Configuring Communication

415 Setting Up Order Inboxes on the Cardiographs 4 Select the applicable OrderVue outbox(es) from the selected remote site that will be accessed by the cardiograph. 5 Assign functions to the selected OrderVue outbox(es). These functions define: Which orders are specified to be downloaded to the cardiograph; the orders can be sorted by status (new or all), priority (STAT or all others) and when the orders are due (the current day only, or the current day and the following day, or other options) Whether amended or updated orders downloaded to the cardiograph replace the existing order or are added to the list as a new order Whether the assigned cardiograph user is permitted the ability to download orders only or is permitted access to download and search for orders 6 All of the settings defined in this process are contained in an individual inbox. The inbox is then given a name. This name can be any name that provides meaning to the cardiograph user; a single cardiograph inbox may consist of several different OrderVue outboxes. 7 Conduct a test search for orders for the new inbox. 8 Select general order settings, including settings for orders loaded onto the cardiograph using removable media (diskette, PC card, USB memory stick). These orders originate from the WebSelect Utility application. Creating an Inbox You cannot create inboxes on legacy PageWriter XL-series cardiographs; rather users access the WebSelect utility and manually transfer orders and ECGs using diskettes. For details on setting up the WebSelect utility, see the OrderVue Installation and Configuration Guide. Creating Inboxes on PageWriter Touch Cardiographs Follow the procedure below to create an order inbox on the cardiograph. To create an inbox 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Orders tab. The selected tab is indicated in blue. The Orders configuration screen appears. 4 Select a configured TraceMasterVue Remote Site from the Remote Orders inboxes dropdown list. Touch the drop-down arrow button or the displayed Remote Site name to open the dropdown list. 5 Touch a remote site to select it. 6 Touch the Refresh button under Available Remote Site Folders (bottom of screen) to display the OrderVue outboxes available on the remote site. Installing TraceMasterVue and Configuring Communication J-7

416 Configuring OrderVue for Use with TraceMasterVue and Cardiographs 7 Touch an OrderVue outbox name to select it. You can select multiple outboxes. All of the selected outboxes are configured into a single inbox. Once selected, the outboxes appear under Selected Remote Site Folders (middle of screen). Touch the Clear Selection button to clear the selected outbox(es). 8 Under Status, touch an entry to select which orders are downloaded to the inbox. The <All> option downloads all orders to the inbox. The New option only downloads orders that are new in the system, and that have not previously been downloaded to the cardiograph. 9 Under Priority, touch an option to select the priority level for orders downloaded to the inbox. The <All> option downloads all orders, regardless of their priority. The STAT option only downloads orders that are designated with a STAT priority. The +/- Elapsed Time setting designates the originating time period for orders downloaded to the inbox. For example, orders that are scheduled for the current day, or the following week can be designed for download to the inbox. This feature can be set in units of hour or days. The range that this feature can be set for is from up to 99 hours or days previous to the current time or date, or 99 hours or days ahead of the current time or date. To designate a range of hours or days in the past, enter - and then the number of hours or days. For example, to enter up to 8 days or hours in the past, enter -8. To enter up to 8 days or hours in the future, enter +8. This value also determines the time or date range in which users can search for orders (if the search feature is enabled). NOTE Entering 0 into the field does not require a + or - sign, and only allows for the download and search of orders for the current hour or day. 10 Under Inbox List Assignments, select the Get Orders check box to allow the user to download orders to the inbox. Select the Find Orders check box to allow the user to search for orders. 11 Under Update Mode, select Delete and Replace to have all existing orders deleted from the inbox each time that orders are downloaded, or select Append to have the new or updated orders added to the bottom of the Pending Orders List (no existing orders are deleted). 12 At the top of the screen, a blue check mark and the word Modify appears. a Touch the Add New button to create a new inbox with the selected settings. The Add Remote Orders inbox window appears. b Enter a name for the inbox. c Touch OK when done. The new inbox appears on the Remote Orders inboxes pull-down list (top of screen). Proceed to the next section to specify general order settings. J-8 Installing TraceMasterVue and Configuring Communication

417 Setting Up Order Inboxes on the Cardiographs Setting General Order Settings on the Cardiograph Follow the procedure below to specify settings that apply to all inboxes and to all orders that are manually downloaded to the cardiograph using a USB memory stick, PC card, or diskette using the WebSelect Utility application. Setting General Order Settings To specify general order settings on the PageWriter Touch cardiograph 1 Under PC Card, Floppy, USB (right side of screen), select Delete and Replace to delete all existing orders stored on the cardiograph from removable media when new orders are downloaded to the cardiograph. 2 Select Append to add the new orders to the existing Pending Orders List (no existing orders are deleted). This setting is only applicable to orders that are downloaded to the cardiograph from removable media. The Delete Order after Archiving the ECG option automatically deletes an order from an inbox once the ECG associated with the order is taken and saved to the Archive. Touch the text to select the checkbox. Now, proceed to the next section to test order connectivity with the new inbox. Testing Order Inbox Connectivity Test the connectivity settings of a newly created Order inbox following the procedure described below. To test Order inbox connectivity 1 Touch the R/T ECG button to exit the Configuration screens. 2 Touch the Orders button. The Orders screen appears. 3 Touch the Find Orders button (top of screen). The Find Order window appears. 4 The Remote Orders inbox drop-down list appears at the top of the screen. If the newly created inbox is not selected on the drop-down list, touch the drop-down arrow button, or the displayed inbox name to open the drop-down list. Select the newly created inbox (if necessary). 5 Enter information into the applicable Patent Data fields. This information will be used to search for orders. Use the wildcard character (*) to expand the search criteria. Enter as much information as necessary to retrieve an order. 6 Touch the Find Network Orders button. Orders that match the entered search criteria appear on the screen. Installing TraceMasterVue and Configuring Communication J-9

418 Configuring OrderVue for Use with TraceMasterVue and Cardiographs 7 If the test is successful, continue configuring the cardiograph. If the test is not successful and no orders appear on the screen, try entering more specific search information, or consult your network administrator if network connectivity issues occur. Editing Inbox Settings Follow the procedure below to edit setting for a configured inbox. To edit inbox settings 1 Touch the Config button on the Command Toolbar. 2 Touch the Defaults button on the Configuration Context Toolbar. 3 Touch the Orders tab. The selected tab is indicated in blue. 4 Under Remote Orders inbox (top of screen), touch the drop-down arrow button or the displayed inbox name to open the drop-down list. Select an inbox. 5 The settings for the selected inbox appear on the screen. Edit the settings as necessary. 6 When done, a blue check mark and the word Modified appears at the top of the screen. Touch the Save Changes button to save the new settings to the selected inbox. Touch the Add New button to create a new inbox with the displayed settings. Touch the Delete button to delete the selected inbox. J-10 Installing TraceMasterVue and Configuring Communication

419 Order Data Table Order Data Table The table on the following pages shows all of the data that is present in an order (in the XML file), which products (cardiograph or TraceMasterVue) support display of the field, and how values that differ between the order and ECG are reconciled. The table columns show the following information: Orders Fields. Lists the order-related field names. XML 1.03: restingecgdata/ Shows the location in the order XML file where the listed order field is defined. ECGs exported from the cardiographs are generally in XML The path shown is within the top-level restingecgdata/ node. XML 1.04: restingecgdata/ Shows the location in the order XML file where the listed order field is defined in XML schema version All ECGs stored in TraceMasterVue are XML The path shown is within the top-level restingecgdata/ node. Orders List. Indicates whether the order field is displayed in the PageWriter Touch Orders list. This column shows whether the field can be displayed in the order list (yes/no) and whether the field can be displayed in a popup tool tip when touching the leftmost column. For the field to be displayed in the Orders list and/or in the tool tip, the field must also have the Indexed check box selected in the cardiograph Patient ID Configuration screen. For details, see the cardiograph documentation. Patient ID Dialog, PWT A Indicates whether the field can be displayed in the PageWriter Touch (version A.02.00) Patient ID dialog box. For the field to be displayed in the dialog box, the field must also have the Enabled check box selected in the cardiograph Patient ID Configuration screen. For details, see the cardiograph documentation. Patient ID Dialog, PWT B Indicates whether the field can be displayed in the PageWriter Touch (version B.01.00) Patient ID dialog box. For the field to be displayed in the dialog box, the field must also have the Enabled check box selected in the cardiograph Patient ID Configuration screen. For details, see the cardiograph documentation. Report Object, PWT B Indicates whether the order field is included on the ECG report printed from the cardiograph. The cardiograph must be running software version B or later. For the field to be displayed on the report, the field must also have the Printed check box selected in the cardiograph Patient ID Configuration screen. For details, see the cardiograph documentation. Display/Edit in TMVue. Indicates whether the order field is displayed in the TraceMasterVue client, and if so, whether it is editable. Display indicates the field appears in the client in read-only form, Edit indicates it appears and is editable, No indicates it is not displayed in the client. Installing TraceMasterVue and Configuring Communication J-11

420 Configuring OrderVue for Use with TraceMasterVue and Cardiographs On Reconcile, Copy into ECG. Indicates whether data in the order field is copied into the same field in the ECG upon reconciliation. If the order field is empty, the ECG field is left untouched. Order Reconciliation, Matching Field. Indicates whether the order field is set as a primary field in TraceMasterVue. This setting is made using the System Configuration utility, on the Orders tab. For details, see Configuring Primary Fields for Order Reconciliation on page J-3. Report Object, TMVue. Indicates whether the data field is displayed on a 12-lead report printed from within the TraceMasterVue client. J-12 Installing TraceMasterVue and Configuring Communication

421 Configuring OrderVue for Use with TraceMasterVue and Cardiographs XML 1.03 XML 1.04 (Feb ) Orders Fields restingecgdata/ restingecgdata/ Patient Info Patient ID patient/ generalpatientdat a/patientid patient/ generalpatientdat a /patientid Patient Last Name patient/ generalpatientdat a/name/lastname patient/ generalpatientdat a /name/lastname Patient First Name patient/ generalpatientdat a/name/firstname patient/ generalpatientdat a /name/ firstname Patient Middle Name patient/ generalpatientdat a/name/ middlename patient/ generalpatientdat a /name/ middlename Account Number -- patient/ generalpatientdat a /MRN Patient DOB patient/ generalpatientdat a/age/dateofbirth patient/ generalpatientdat a /age/dateofbirth Age patient/ generalpatientdat a/age/ patient/ generalpatientdat a /age/ Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Yes, Tooltip Edit Edit Yes Edit Yes Yes Yes Yes,Tooltip Edit Edit Yes Edit Yes Yes Yes Yes,Tooltip Edit Edit Yes Edit Yes No Yes Yes,Tooltip Edit Edit Yes Edit Yes No Yes No No No No Display Yes Yes No Yes, Tooltip Edit Edit Yes Edit Yes Yes Yes Yes Edit Edit Yes Edit Yes No Yes J-13 Installing TraceMasterVue and Configuring Communication

422 Configuring OrderVue for Use with TraceMasterVue and Cardiographs XML 1.03 Orders Fields restingecgdata/ Age Units patient/ generalpatientdat a/age/ Gender patient/ generalpatientdat a /sex Race patient/ generalpatientdat a /race Weight patient/ generalpatientdat a /weight Weight Units patient/ generalpatientdat a /weight Height patient/ generalpatientdat a /height Height Units patient/ generalpatientdat a /height Systolic BP patient/ patientmedicaldat a /bloodpressure/ systolic XML 1.04 (Feb ) restingecgdata/ patient/ generalpatientdat a /age/ patient/ generalpatientdat a /sex patient/ generalpatientdat a /race patient/ generalpatientdat a /weight patient/ generalpatientdat a /weight patient/ generalpatientdat a /height patient/ generalpatientdat a /height patient/ patientmedicalda ta / bloodpressure/ systolic Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Yes Display Display Yes Edit Yes No Yes Yes Edit Edit Yes Edit Yes Yes Yes Yes Edit Edit Yes Edit Yes No Yes Yes Edit Edit Yes Edit Yes No Yes Yes Display Display Yes Edit Yes No Yes Yes Edit Edit Yes Edit Yes No Yes Yes Display Display Yes Edit Yes No Yes Yes Edit Edit Yes Edit Yes No Yes J-14 Installing TraceMasterVue and Configuring Communication

423 Configuring OrderVue for Use with TraceMasterVue and Cardiographs XML 1.03 Orders Fields restingecgdata/ Diastolic BP patient/ patientmedicaldat a /bloodpressure/ systolic Visit Info Institution Name dataacquisition/ acquirer/ institutionname Institution Id dataacquisition/ acquirer/ institutionid Facility Name dataacquisition/ acquirer/ institutionlocatio nname Facility Id dataacquisition/ acquirer/ institutionlocatio nid Dept. Name dataacquisition/ acquirer/ departmentname XML 1.04 (Feb ) restingecgdata/ patient/ patientmedicalda ta / bloodpressure/ systolic dataacquisition/ acquirer/ institutionname dataacquisition/ acquirer/ institutionid dataacquisition/ acquirer/ facilityname dataacquisition/ acquirer/ facilityid dataacquisition/ acquirer/ departmentname Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Yes Edit Edit Yes Edit Yes No Yes No No No Yes Edit No No Yes No No No Yes Edit No No No Yes Facility Id or Name, configurable No Edit Facility Id or Name, configurable Yes Edit No No Yes Yes Facility Id or Name, configurable No Edit Facility Id or Name, configurable Yes Edit No No No Yes Dept. Id or Name, configurable,tooltip Edit -shared with Dept Name Edit Dept. Id or Name, configurable Yes Edit No No Yes J-15 Installing TraceMasterVue and Configuring Communication

424 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Orders Fields XML 1.03 restingecgdata/ XML 1.04 (Feb ) restingecgdata/ Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Dept. Id dataacquisition/ acquirer/ departmentid dataacquisition/ acquirer/ departmentid Yes Dept. Id or Name, configurable,tooltip Edit - shared with Dept Id Edit Dept. Id or Name, configurable Yes Edit No No No Unit Number na No No No No No No No No Room Number dataacquisition/ acquirer/room dataacquisition/ acquirer/room Yes,Tooltip Edit Edit Yes Display Yes No Yes Bed Number -- dataacquisition/ acquirer/bed No No No No Display Yes No No Order Info Unique Order Id orderinfo/ viperuniqueorderi d orderinfo/ uniqueorderid Tooltip only No No NO Display Yes Yes No Order Number orderinfo/ ordernumber orderinfo/ ordernumber Yes,Tooltip Edit Edit Yes Display Yes Yes Yes Order Request Date orderinfo/ datesubmitted orderinfo/ orderrequestdate Yes,Tooltip No No No Display Yes No No Order Request Time orderinfo/ timesubmitted orderinfo/ orderrequesttime Yes,Tooltip No No No Display Yes No No Operator Id dataacquisition/ acquirer/ operatorid dataacquisition/ acquirer/ operatorid Yes Edit Edit Yes No Yes No Yes J-16 Installing TraceMasterVue and Configuring Communication

425 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Orders Fields Operator Name Order Priority Order Billing Code Order Remarks Reason for Order Encounter Id Orders Status Orders Status Date Orders Status Time Process Status Process Status Date XML 1.03 restingecgdata/ XML 1.04 (Feb ) restingecgdata/ Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) -- dataacquisition/ acquirer/ operatorname No No No No No Yes No No orderinfo/priority orderinfo/priority Yes,Tooltip No No No Display Yes No Yes -- orderinfo/ orderbillingcode No No No No No Yes No No -- orderinfo/ orderremarks No No No No No Yes No No orderinfo/ reasonfororder orderinfo/ reasonfororder Yes, Tooltip Edit Edit Yes No Yes No Yes dataacquisition/ acquirer/ encounterid dataacquisition/ acquirer/ encounterid Yes, Tooltip Edit Edit Yes No Yes No Yes orderinfo/ orderstatus Yes, Tooltip No No No Display No No No No No No No Display No No No No No No No Display No No No No No No No Display Yes No No orderinfo/ dateprocessed orderinfo/ dateprocessed No No No No Display Yes No No J-17 Installing TraceMasterVue and Configuring Communication

426 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Orders Fields XML 1.03 restingecgdata/ XML 1.04 (Feb ) restingecgdata/ Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Process Status Time orderinfo/ timeprocessed orderinfo/ timeprocessed No No No No Display Yes No No Device ID dataacquisition/ machine dataacquisition/ machine No No No No Display No No Yes inbox -- orderinfo/inbox No No No No Display Yes No No User define 1 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 2 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 3 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 4 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 5 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 6 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 7 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes User define 8 userdefines userdefines Yes Edit Edit Yes Edit Yes No Yes Drg [4] orderinfo/ drgcategory patient/ patientmedicalda ta/drgcategory Yes Edit Edit Yes No Yes No Yes J-18 Installing TraceMasterVue and Configuring Communication

427 Configuring OrderVue for Use with TraceMasterVue and Cardiographs XML 1.03 XML 1.04 (Feb ) Orders Fields restingecgdata/ restingecgdata/ Rx[4] patient/ patientmedicaldat a/medication patient/ patientmedicalda ta/medication Dx[4] patient/ patientmedicaldat a/diagnosis patient/ patientmedicalda ta/diagnosis Hx[4] patient/ patientmedicaldat a/history patient/ patientmedicalda ta/history Sx[4] patient/ patientmedicaldat a/symptom patient/ patientmedicalda ta/symptom Clinician/ Physician Ordering Clinician UPIN dataacquisition/ acquirer/ orderingclinician UPIN dataacquisition/ acquirer/ orderingclinician id Ordering Clinician Name dataacquisition/ acquirer/ orderingclinician name dataacquisition/ acquirer/ orderingclinician name Attending Physician UPIN -- dataacquisition/ acquirer/ attendingid Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) Yes Edit Edit Yes Edit No No Yes Yes Edit Edit Yes Edit No No Yes Yes Edit Edit Yes No No No Yes Yes Edit Edit Yes No No No Yes Yes Edit Edit Yes No Yes No No Yes Edit Edit Yes No Yes No Yes No No No No No Yes No No J-19 Installing TraceMasterVue and Configuring Communication

428 Configuring OrderVue for Use with TraceMasterVue and Cardiographs Orders Fields Attending Physician Name Referring Physician UPIN Referring Physician Name XML 1.03 XML 1.04 (Feb ) restingecgdata/ restingecgdata/ -- dataacquisition/ acquirer/ attendingid name -- dataacquisition/ acquirer/ referringclinician id -- dataacquisition/ acquirer/ referringclinician name Orders List (Yes/No) (ToolTip) INDEXED= true Patient Id Dialog (PWT A.02.00) (Display/ Edit/No) ENABLED= true Patient Id Dialog (PWT B.01.00) (Display/ Edit/No) ENABLED= true Report Object (PWT B.01.00) (Yes/No) PRINTED= true Display/ Edit in TMVue (Display/ Edit/No) On Reconcile, Copied from Order to ECG (* See Note) Order Reconciliation Matching Field Report Object (TMVue) (Yes/No) No No No No No Yes No No No No No No Yes No No No No No No Yes No No J-20 Installing TraceMasterVue and Configuring Communication

429 Configuring the ADT Option Configuring the ADT Option The Admit/Discharge/Transfer (ADT) option allows OrderVue to accept updates to patient information in the order from the HIS. For detailed information about configuring the ADT option, see the ADT Installation And Configuration Guide and associated documentation, provided on the OrderVue Documentation CD (as well as on InCenter). Installing TraceMasterVue and Configuring Communication J-21

430 Configuring OrderVue for Use with TraceMasterVue and Cardiographs J-22 Installing TraceMasterVue and Configuring Communication

431 Index A Accessories 3-3 aliases about C-2 defining 7-39, C-5 enabling/disabling 7-38, C-4 auto negotiation 8-12 B bar code scanner resetting to factory defaults 3-9 technique for using 3-9 Bar code scanner, installing 3-7 C cardiographs configuring for use with TraceMasterVue 1-1, 6-1, 7-1, C-1 enabling interactive query with TraceMasterVue 10-9 client application cache flushing to enable system changes 6-28 clinical information configuring 8-25 code aliases about C-2 defining 7-39, C-5 enabling/disabling 7-38, C-4 COM ports configuring serial port for dialup modem to PageWriter Touch/Trim cardiographs 4-8 verifying configuration 4-12 computer accessories, optional 3-3 configuration configuring multiple cardiographs 8-3 network and modem settings 8-17 Patient ID screen default settings 8-22 Patient ID screen layout settings 8-30 Configure Site 10-4 Configure Site menu 10-4 configuring TraceMasterVue users/ groups required groups A-11 required user-group associations A-13 required users A-5 custom criteria, defining 7-38, C-1 custom interpretive statements and codes defining 7-38, 7-41, C-1, C-8 D demo ECGs in ECGVue tutorial, resetting to default state 11-4 department identification configuring fields 8-27 departments adding 7-17 configuring on TraceMasterVue and cardiographs B-2, I-4 deleting B-16 undefined, about B-15 Device ID configuring 8-21 Device IP Address setting 8-13 DHCP 8-12, 8-14 using for wired and wireless connectivity 8-14 display, installing 3-6 Display, LCD 3-6 DRG codes defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 Dx codes defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 E ECGVue installing on client systems 7-43 running 1-9 ECGVue tutorial about 11-1 demo information in database 11-2 location of files 11-3 resetting demo ECGs to default state 11-4 running address for system admin, setting 7-4 notification adding to a workflow rule 7-35 error messages changing how and when deleted from database 6-9 deleting from database 6-9 Ethernet settings 8-12 F facilities adding 7-16 configuring on TraceMasterVue and cardiographs B-2, I-4 deleting B-16 undefined, about B-15 facility identification configuring fields 8-27 Fax cover page customizing 5-9 fax print sites 5-9 field service kit 3-1, 3-4 Fixed IP Address 8-12 G global options, setting 7-3 Global tab, setting options 7-3 grounding kit 3-1, 3-4 groups. See Windows groups H hardware junction box, mounting 4-4 octa-cable, about 4-2 wallplate cable option, installing 4-5 hardware components, installing 3-4 Hardware, installing 3-4 HL7, about mapping G-1 Hx codes defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 Index-1

432 Index I idle timeout about 7-9 configuring 7-9 importing ECGs configuring 4-29 configuring inbound directories 4-34, 7-11 inbound directories, configuring 4-34, 7-11 inboxes, adding 7-26 Installation LCD display 3-6 Network Hub 3-5 printers 5-1 installing ECGVue 7-43 LCD display 3-6 Netserver 3-4 Report Manager 7-44 server 3-4 wallplate cable option 4-5 installing modem 3-1, 3-4 institution settings 8-21 institutions adding 7-15 configuring on TraceMasterVue and cardiographs B-2, I-4 deleting B-16 undefined, about B-15 Instructions for Use organization of 1-3 IntelliVue Information Center, configuring for use with TraceMasterVue H-1, I-1 interactive query about 10-9 enabling 10-9 enabling on PageWriter Trim 9-14 interpretive statements, defining custom 7-38, 7-41, C-1, C-8 IP address 8-13 assigning to server 4-19 J Junction box 4-4 junction box, mounting 4-4 L LAN settings using DHCP for wired and wireless 8-14 LCD display 3-6 installing 3-6 UPS 3-7 LCD display, installing 3-6 LOC, configuring 8-21 Local network 3-4 locations deleting B-16 undefined, about B-15 locations fields configuring on TraceMasterVue and cardiographs B-2, I-4 M modems fax 3-1, 3-4 installing 3-1, 3-4 octa-cable, about 4-2 modem card, configuring settings 8-17 modifiers defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 N NetServer, installing 3-4?? NetServer, turning on 3-11 Network Hub installing 3-5 local network 3-4 network hub, using Port 1 3-4, 3-10, 5-2 Network Interface Connector (NIC) 3-4, 3-5 network settings configuring on a PageWriterTouch cardiograph 8-12 ping test 8-13 network settings, configuring 4-19 O octa cable, using COM port identifiers 4-2 for 8 additional ports 4-2 octa-cable, about 4-2 online help Statement Manager 6-31 System Configuration utility 6-31 operator identification configuring fields 8-27 optional accessories 3-3 order information configuring 8-26 Orders option about 1-7, J-1 OrderVue configuring optional Patient ID fields on cardiograph 8-28 creating an Inbox on the PageWriterTouch cardiograph J-7 organization of the Instructions for Use 1-3 P PageWriter Touch/Trim cardiographs configuring for use with TraceMasterVue 1-1, 6-1, 7-1, C-1 configuring ports to communicate with TraceMasterVue 4-8 PageWriter Trim enabling interactive query 9-14 PageWriter XL-series cardiographs configuring for use with TraceMasterVue 1-1, 6-1, 7-1, C-1 PageWriterTouch cardiograph configuring network settings 8-12 configuring Remote Site settings 8-15 institution settings 8-21 modem configuration 8-17 Patient ID information default settings 8-22 Patient ID screen configuration options 8-23 configuration overview 8-22 configuring clinical information fields 8-25 configuring miscellaneous information fields 8-27 configuring optional fields 8-28 configuring order information fields 8-26 configuring patient information fields 8-24 configuring the layout of the screen 8-30 patient weight and height configuring fields 8-27 Index-2 Installing TraceMasterVue and Configuring Communication

433 Index physician data importing in CSV format 7-20 manually entering 7-21 Physicians tab add entries 7-21 associating physicians with locations 7-19 importing physician data in CSV format 7-20 manually entering data 7-21 ping test 8-13 Port, TCP/IP 5-4 Print site, fax 5-9 Printer installing 5-1 TCP/IP port 5-4 UPS 3-6 R race defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 Remember me option configuring 7-10 enabling and disabling for the entire TraceMasterVue system 7-10 Remote Access Server (RAS) 8-17 remote desktop access, configuring 4-36 Remote Site Settings 8-15 Remote Sites modem connection 8-17 network connection 8-17 remote support modem connecting 3-1, 3-4 remote support, configuring 4-36 Report Manager installing on client systems 7-44 resetting bar code scanner 3-9 room number configuring field 8-27 Rx codes defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 S scanning bar codes 3-9 Secure Sockets Layer (SSL) 8-17 security about A-2 about groups A-2 about users A-2 permissions associated with each TraceMasterVue group 6-20, A-8 security roles about 6-25, A-15 additive approach A-16 approaches for defining A-16 defining 6-25 examples of A-17 processing for defining A-16 subtractive approach A-16 serial comparison about 7-6 enabling/disabling 7-7 setting options 7-7 serial port configuring for dialup modem to PageWriter Touch cardiograph 4-8 server, installing 3-4 server name, changing 4-20 severities defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 simultaneous connections, setting maximum number of 4-30 sorting the statement list in the Statement Manager 7-39, C-5 SSL adding support for 4-20 enabling on cardiograph 4-29, 6-40 installing certificate on TMVue 4-25 requesting certificate 4-21 statement aliases about C-2 defining 7-39, C-5 enabling/disabling 7-38, C-4 Statement Manager accessing online help 6-31 setting the criteria version to use 7-3 sort statement list 7-39, C-5 Supplies 3-3 supplies, ordering 3-3 Sx codes defining custom 7-40, C-6 deleting custom C-7 editing custom C-7 System Configuration utility accessing online help 6-31 saving and enabling changes 6-28 setting global options 7-3 viewing the criteria version in use 7-3 system messages changing how and when deleted from database 6-9 deleting from database 6-9 system options enabling 6-28 setting 6-28 system requirements 1-9 database server 1-13 local client 1-13 required database users to run system A-15 required groups A-11 required settings A-3 required users A-5 web server 1-10 system security. See security T TIFF options, about 7-24 timeout interval about 7-9 configuring 7-9 TraceMaster system powering on 3-11 setup 5-2 TraceMaster_COBO group 6-21, A-10 TraceMaster_ConfCardio group 6-21, A-9 TraceMaster_Guest group 6-22, A-10 TraceMaster_HeadTech group 6-21, A-9 TraceMaster_IT group 6-20, A-8 TraceMaster_Manager group 6-20, A-8 TraceMaster_RefPhys group 6-21, A-9 TraceMaster_RevCardio group 6-21, A-9 TraceMaster_SysAdmin group 6-20, A-8 TraceMaster_Tech group 6-20, A-9 TraceMaster_Verifier group 6-21, A-10 TraceMaster_WebAPI group, about 6-22, A-10 Installing TraceMasterVue and Configuring Communication Index-3

434 Index TraceMasterVue groups 6-20, A-8 settings required to run the system A-3 users required to run the system A-5 TraceMasterVue applications, about 1-5 TraceMasterVue groups associating users with 6-23 permissions associated with each group, about 6-20, A-8 required to run system A-11 required user-group associations A-13 TraceMaster_COBO 6-21, A-10 TraceMaster_ConfCardio 6-21, A-9 TraceMaster_Guest 6-22, A-10 TraceMaster_HeadTech 6-21, A-9 TraceMaster_IT 6-20, A-8 TraceMaster_Manager 6-20, A-8 TraceMaster_RefPhys 6-21, A-9 TraceMaster_RevCardio 6-21, A-9 TraceMaster_SysAdmin 6-20, A-8 TraceMaster_Tech 6-20, A-9 TraceMaster_Verifier 6-21, A-10 TraceMaster_WebAPI 6-22, A-10 TraceMasterVue security roles. See security roles TraceMasterVue server name, changing 4-20 TraceMasterVue system configuring for use with cardiographs 1-1, 6-1, 7-1, C-1 configuring for use with IntelliVue Information Center H-1, I-1 ECGVue tutorial, about 11-1 resetting demo ECGs to default state 11-4 turning on TraceMaster 3-11 tutorial, running 11-1 U undefined institutions, facilities, departments. See listings under institutions, facilities, departments undefined locations, about B-15 Uninterruptable Power Source installing 3-6?? Uninteruptable Power Source (UPS) 3-6 UPIN (Universal Physician Identification Number) configuring 8-26 UPS 3-6 user defined fields configuring 8-28 configuring on TraceMasterVue and OrderVue D-2 field 1 attributes, about D-2 users about 6-18, A-2, A-4 associating with TraceMasterVue groups 6-23 changing access permissions with security roles A-15 database, required A-15 enabling changes to settings 6-28 required for system operation, list of A-5 required to run TraceMasterVue (database) A-15 required user-group associations A-13 viewing list of on TraceMasterVue system 6-18, A-4 W wallplate cable option, installing 4-5 WebAPI option about 1-8 Windows groups about A-2 default configuration A-13 permissions associated with each TraceMasterVue-specific group 6-20, A-8 required to run TraceMasterVue A-11 required user-group associations A-13 Windows Users and Groups Manager, accessing 6-18, A-4 wireless LAN card using with DHCP 8-14 workflow rules add notification to a rule 7-35 defining 7-30 defining export rules 7-31 defining fax rules 7-31 defining print rules 7-31 print and export confirmed ECGs rule 7-35 print newly acquired ECGs rule 7-32 Index-4 Installing TraceMasterVue and Configuring Communication

435

436 Copyright 2007 Koninklijke Philips Electronics N.V. All rights are reserved. Permission is granted to copy and distribute this document for educational purposes. Printed in the U.S.A. April 2007 Edition * * *1*