Sage Intergy 7.
Sage Intergy 7.00 Installation Manual Reference Confidential This document and the information it contains are the confidential information of Sage. Neither this document nor the information it contains may be disclosed to any third party or reproduced, in whole or in part, without the express prior written consent of Sage Software Healthcare, LLC. Sage Software Healthcare, LLC reserves the right to change, without notice, product offerings, product specifications and the information in this document.
Table of Contents How to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Chapter 1 - Operating System Infrastructure Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 1-2 Base Windows Settings for All Sage Intergy Servers . . . . . . . . . . 1-3 Computer Name . . . . . License Mode . . . . . . Network settings . . . . Security Configuration . Other Settings . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
Table of Contents Chapter 3 - Client Installation Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 3-2 New Windows Sage Intergy Client Installation . . . . . . . . . . . . . 3-3 Extra Steps for Terminal Services Installation Automated Upgrade Distribution . . . . . . . . Base Windows Workstation Configuration . . Workstation Configuration for Clinician . . . . Media Installation . . . . . . . . . . . . . . . . . Apply F1 Field Help Fix . . . . . . . . . . . . . .
Table of Contents Chapter 5 - Database Tuning Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 5-2 Sage Intergy Database Tuning Instructions . . . . . . . . . . . . . . . 5-3 Database Shutdown . . . . . . . . . . . . . . . . . . . . . . Database Configuration Parameter Changes . . . . . . . Application server configuration changes . . . . . . . . . Name Server Logging Settings . . . . . . . . . . . . . . . . Progress Application Server Text File Tuning Settings .
Table of Contents Chapter 7 - Document Delivery Server Configuration Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 7-2 Selection of Installation Type . . . . . . . . . . . . . . . . . . . . . . 7-3 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Installed Sage Intergy Components . . . . Microsoft Word Installation . . . . . . . . . FaxPress Hardware Installation . . . . . . Castelle FaxPress 2500 devices . OpenText FaxPress 2L devices .
Table of Contents Chapter 9 - Terminal Services Client Installation Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 9-2 Terminal Services Overview . . . . . . . . . . . . . . . . . . . . . . . 9-2 Windows Component Selection . . . . . . . . . . . . . . . . . . . . . 9-3 Windows Server 2008 Installation Options Windows Server 2003 Installation Options . . . . . . . . . . . . . . . . . . . 9-3 . . . . . . . . . . . . . . . . . . . 9-5 Windows Domain Requirement . . . . . . . . .
Table of Contents Appendix A - Backup Application Installation and Configuration Typical Installation Settings . . . . . . . . . . . . . . . . . . . . . . .12-2 Create Administrative Account . . . . . . . . . . . . . . . . . . . . .12-4 Install Symantec Backup Exec From Media . . . . . . . . . . . . . .12-5 Configuration of Backup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9 Backup Job Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Appendix D - Sage Intergy Upgrade Windows Sage Intergy Server Upgrade . . . . . . . . . . . . . . . . 15-2 Windows 2008, Windows 7 and Windows Vista Screen Updates . . Automated Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sage Intergy Primer . . . . . . . . . . . . . . . . . . . . . . AdminService Authentication Utility . . . . . . . . . . . . . . . . . . . . . N-tier and Report Server upgrades . . . . . . . . . . . . . . . . . . . . . Upgrade Preparation . . . . .
Table of Contents Appendix G - Cardio Service Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18-2 Sage Intergy server installation steps . . . Network Configuration . . . . . . Sage Intergy Services selection . Ultia Configuration . . . . . . . . Heart Centrix installation . . . . . . . . . . . Server Requirements . . . . . . . Sage Intergy system information . Client Installation . . . . . . . . . .. .. .. . . . . . . . . . . . . . . . .. .. .. . . . . . . . . . .
Introduction Introduction This document is intended for use by Sage field engineers, software installation specialists, and other technicians who may be tasked with the installation and maintenance of the Sage Intergy 7.00 product. Configuration of application functions and use of the Sage Intergy client desktop are topics that are not covered in this manual. Please refer to the appropriate customer-facing user guide or training materials for this type of information.
Introduction Installation Procedures Most chapters in this document begin with a table that lists typical installation settings used for each specific installation process. This table is followed by a series of sequential work actions. For ease of reference, these actions are divided into individual tasks with numbered steps. Most chapters will end with a section called Next Steps, which describes the work actions that must occur next. x Sage Intergy 7.
Chapter 1: Operating System Infrastructure Chapter 1: Operating System Infrastructure A typical Sage Intergy installation is a turnkey solution, meaning that all installed software and hardware is purchased from Sage as a packaged solution. For this reason, it will ordinarily be necessary for the installing technician to set up basic operating system and network infrastructure components.
Chapter 1: Operating System Infrastructure Typical Installation Settings The following table lists typical oeprating system settings used for Sage Intergy in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 1: Operating System Infrastructure Application Component Configuration Item Value or Setting Sage Intergy Client Installation for Terminal Services Temporary Directory Prompt T: in a typical installation, or available drive letter in customer environment Windows Local Securitiy Policy Password Must Meet Complexity Requirements Enabled User Name Support Full Name Support Descrption Sage Intergy Support User Password Int Group Membership Users, Administrators User Can
Chapter 1: Operating System Infrastructure 1. To access the System control panel, right-click on the Computer item in the Start menu and selecting the Properties menu item. 2. Click on the Change Settings link at the right side of the System configuration browser window to open the System Properties control panel. 3. Click on the Change button to change the name of the server.
Chapter 1: Operating System Infrastructure 2. The Licensing Mode window will be displayed. Select the ‘Per Device or Per User’ radio button and click on OK to confirm the change. 3. If this is a new setting, the Client Licensing confirmation window will be displayed. Click in the ‘I agree’ checkbox to confirm that you will comply with the new licensing terms, and the click on the OK button to proceed with the change. Network settings Configure TCP/IP for the server. 1.
Chapter 1: Operating System Infrastructure 2. In Windows Server 2003, click on the Properties button to display the Local Area Connection Properties window. In the new window, select the Internet Protocol (TCP/IP) item and click on the Properties button to display the TCP/IP settings. In Windows Server 2008, right-click on the Local Area Connection icon and select the Properties menu item to display the Local Area Connection Properties window.
Chapter 1: Operating System Infrastructure 3. The Internet Protocol Properties window is displayed. For Sage Intergy 7.00, it is acceptable to use automatic setting to have an address assigned by an external DHCP server. However, if the Sage Intergy server is also a domain controller, or if the Sage Intergy Storage Server will be installed, then a static IP address or a DHCP reservation is strongly recommended.
Chapter 1: Operating System Infrastructure For detailed information on configuration of TCP/IP Offload for Windows Server 2008, refer to the Microsoft Knowledge Base entry at http://support.microsoft.com/kb/951037. For detailed information on configuration of TCP/IP Offload for older versions of Windows, refer to the article at http://support.microsoft.com/kb/948496 instead.
Chapter 1: Operating System Infrastructure 3. Note the Domain Profile, Private Profile and Public Profile tabs in the Windows Firewall Properties window. On all three tabs, select the ‘Off’ item from the drop-down list in the Firewall State field. Click on the OK button to close the Windows Firewall Properties window and return to the Server Manager window. 4. At the Server Manager window, click on the Server Manager item in the left pane to return to the Server Summary screen.
Chapter 1: Operating System Infrastructure A Sage Intergy 7.00 environment should be installed in an environment that has a domain controller. When network infrastructure functions are provided by existing computing environment equipment, Sage Intergy servers may be joined to an existing domain. Otherwise, the Sage Intergy database server should be installed as the domain controller with the ‘Intergy’ domain name.
Chapter 1: Operating System Infrastructure 3. Note that the left pane is expanded to include additional steps that are necessary as part of Terminal Services installation. As you proceed through the installation of Terminal Services, select licensing options that apply to the customer site. Specify the installation of the Terminal Server Licensing components only if another licensing server is not already available in the customer environment.
Chapter 1: Operating System Infrastructure 1. Open the Domain Security Policy editor from the Administrative Tools menu. 2. Using the Domain Security Policy editor, enable the ‘Password Must Meet Complexity Requirements’ setting as shown below. To apply this change immediately without rebooting, run the command ‘gpupdate’ from the Start/Run window. 1 - 12 Sage Intergy 7.
Chapter 1: Operating System Infrastructure Administrative Accounts An administrative account must be created to permit testing and troubleshooting by Sage personnel. Also, an account must be created for use by the administrative service. 1. From the Administrative Tools menu, select the ‘Computer Management’ item: 2. The Computer Management console is displayed. Expand the Local Users and Groups item in the left pane and right-click on the Users folder. Select the New User menu item.
Chapter 1: Operating System Infrastructure 3. The New User dialogue window is displayed. Enter the following data in the appropriate fields to create a new user object with the following settings: • User Name – Support • Full Name – Support • Description - Sage Intergy Support User • Password – Int (note capital letter) • User cannot change password checkbox selected • Password never expires checkbox selected • Group Membership - Users, Administrators 4.
Chapter 1: Operating System Infrastructure 5. The account properties window is displayed. Click on the Add button to add the Support user to both the Users and Administrators groups. 6. Repeat steps 2 through 5 to create the IntergyService account.
Chapter 1: Operating System Infrastructure 7. Click on the OK button to close the account properties window and then exit the Computer Management console. Note that for N-tier environments, the Sage Intergy Service Account must be a domain account instead in order to permit network authentication. Refer to Chapter 4 for detailed information on installation and configuration of an N-tier environment.
Chapter 1: Operating System Infrastructure From the Start menu, open the Administrative Tools menu and select the Server Manager menu item. Click on the Add Features option to display a list of available server features. Note that by default, the .NET Framework 3.5.1 components are not selected. Click on the checkboxes to activate these features on all Sage Intergy servers, and proceed through the Select Features wizard to complete activation.
Chapter 1: Operating System Infrastructure Save the file Windows6.0-KB917607-x86.msu to a temporary directory on the Sage Intergy Appliance server, and double-click on the file in Windows Explorer to execute it. Accept the license terms when prompted and allow the installation to proceed. Registry Change Use the following procedure to modify the registry: 1. Log on using an administrator account. 2.
Chapter 1: Operating System Infrastructure Existing Windows Environment Configuration A typical new Sage Intergy installation occurs on a newly installed operating system in an environment with no other computing infrastructure. However, in some customer sites the Sage Intergy application server may be installed where there is already a domain controller, or where there are already network functions like DNS and DHCP.
Chapter 1: Operating System Infrastructure Next Steps If you are completing installation for a new customer environment, proceed to Chapter 2 to complete installation of the Sage Intergy database server. If you are installing a different type of server, proceed to the chapter that describes the appropriate application or services.
Chapter 2: Database Server Installation Chapter 2: Database Server Installation All Sage Intergy computing environments include one database server. In most environments this server will also function as the main application server, which is used to process client connections. Although other environments may require more than one application server, there will only be one database server regardless of the size of the customer site.
Chapter 2: Database Server Installation Typical Installation Settings The following table lists typical installation settings used for the Sage Intergy database server in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 2: Database Server Installation Application Component Sage Intergy EHR Settings Database Administration Configuration Item Value or Setting Clinical Server localhost Data Port 60001 Secure Proxy Port 60004 RMS Site ID Blank (not required for database server installation of IEHR client) Database Type New Install Size Typical (40 GB) Database Area AI C:/Intergy/DB (note forward slashes) Database Area BI D:/Intergy/DB (note forward slashes) Database Area Data If installing databa
Chapter 2: Database Server Installation Media Installation The Sage Intergy 7.00 DVD installation media may be copied to a shared folder on a single server. The preferred location for this share is the D: drive of the Sage Intergy Server. Use the share name \\IntergyServer\IntergyDVD and install from this location instead of physical media for installation without using the disk.
Chapter 2: Database Server Installation Select Setup Option 5. The setup options window is displayed next. The default choice is to install the client only. From the menu, select the ‘Database Server/Appserver’ item and click on the Next button to proceed. Note the other menu items available for installation here. Stand Alone AppServer installation may only occur after one or more database servers are installed first. A Report Server is used only in environments with WAN clients.
Chapter 2: Database Server Installation tuning parameters and not licensing restrictions. Make the appropriate selection and click on the Next button to proceed. Set Destination Folder 8. The destination folder window is displayed. The preferred location for Sage Intergy application components is the C: drive in a top-level folder. If necessary, change the destination folder before clicking on the Next button to proceed to the next step. Set Temporary Folder and Program Icons 9.
Chapter 2: Database Server Installation versions of the installation media may present an incorrect default value. All new installations of Sage Intergy should use the ‘C:\Intergy\Temp’ value. 10. The add program icons window is displayed. The default option will create a new program group called ‘Sage Intergy.’ Click on the Next button to proceed. Enter RMS Host ID 11. The RMS Host ID window is displayed.
Chapter 2: Database Server Installation Select Additional Sage Intergy Applications 12. The additional applications window is displayed. At this window, you may elect to install other Sage Intergy components as needed by the customer. The following options are available: • Sage Intergy Transcription Writer - For use in customer sites where transcriptions processed. Microsoft Word must be installed before Transcription Writer may be implemented.
Chapter 2: Database Server Installation Select Sage Intergy Services 13. The Sage Intergy services installation window is displayed. The following options are available: Sage • Remote Print Service - Required for environments where Sage Intergy EHR PDA clients are used for printing. It is strongly recommended that RPS be installed in customer sites that have Sage Intergy EHR PDA implemented.
Chapter 2: Database Server Installation Check the boxes for component installation required for this customer and click on the Next button to proceed. Media Installation Continues 14. A confirmation window is displayed, showing all of the options and features chosen for installation. Review this list carefully before proceeding, and make sure that selected components match the requirements of the customer site. Click on the Next button when ready to proceed. 15.
Chapter 2: Database Server Installation It is not necessary to enter the RMS Site ID unless the EHR client is installed as part of a WAN client. Under normal circumstances you do not need to enter the RMS Site ID when installing Sage Intergy EHR on a database server or application server. The Clinical Server Name is the main Sage Intergy database server name. As a best practice, use the default ‘localhost’ entry for this field when installing Sage Intergy EHR on the primary Sage Intergy database server.
Chapter 2: Database Server Installation Database Configuration Configuration of the database must occur immediately after media installation has completed. Do not attempt to install Sage Intergy clients or configure other Sage Intergy application components until the database is properly configured and serialized. 1. When the server has successfully rebooted, log on as the administrator and begin setup of the Sage Intergy database.
Chapter 2: Database Server Installation installing Sage Intergy Storage Server, or are installing Sage Intergy Storage Server to be used with an external storage array, make sure that all three database components are installed to separate physical drive arrays. Note the use of forward slashes instead of back slashes, which would ordinarily be used under Windows or DOS. This is a convention used by the Progress product and is not an error.
Chapter 2: Database Server Installation When this is complete, the main Database Administration console is displayed: Preserialization Backup 5. Before configuration occurs, you should perform a backup of the newly created database. Click on the Backup Database item in the left menu pane to display the backup configuration options: Use the filename ‘C:/Intergy/DB/preserialize.dbk’ for this backup, and note the use of forward slashes instead of back slashes.
Chapter 2: Database Server Installation Serialization and Licensing Serialization must be applied to activate Sage Intergy application components purchased by the customer. A small file with a .lic extension is distributed via physical media or electronic transmission, and should be available to the installing technician before configuring the database server or visiting the customer site. 1. To apply serialization, open the Sage Intergy System Administration Desktop.
Chapter 2: Database Server Installation Alternately, you may copy this file to the local C: drive. Select the file and click on the Open button to proceed. 5. If this serialization file includes a license for SIEHR, a warning window will also be displayed. Read the text of the warning. Because this is a new installation, you will not need to notify the customer about the restriction on OmniDoc usage. Click on the OK button to proceed.
Chapter 2: Database Server Installation 6. After several minutes, the Serialization window is displayed with content and information on licensed products and subsystems. If necessary, review this information with the customer representative to ensure that all purchased licenses are represented on the screen. Note that the Export button is available to produce an output file for troubleshooting by R&D. This file cannot be used as a replacement serialization file.
Chapter 2: Database Server Installation Verify Listed Practices 2. The Practice Maintenance window is displayed. Make sure that all licensed practices are displayed in the practice code list. Select the Close window after you have finished viewing the practice data. Configure System Administrator as Practice Administrator 3.
Chapter 2: Database Server Installation ‘Make user a practice administrator’ option. Make any necessary changes and click on the Save button to save your changes. Create Support User Account 5. While the User and Security window is open, it is also necessary to create an account for support services. Click on the Users hierarchy item in the left pane, and the click on the New button in the lower left corner. 6. The New User Account window is displayed.
Chapter 2: Database Server Installation • User Type: M • Logon: ‘support’ • Name: ‘Sage Intergy Support Admin User’ • Password: int Note that the password for the support logon is intentionally different from that used for the system administration logon. Make sure that you check the box for system administrator permissions as well. Click on the Save and Close buttons, 7. At the main Users and Security window, click on the Logon drop-down button.
Chapter 2: Database Server Installation 11. If this site is serialized for multiple practices, the practice selection window is displayed. Select the practice to configure and click on the OK button to proceed. 12. The Sage Intergy Practice Administration Desktop is displayed. Under the Setup menu, select the ‘Users and Security’ menu item. 13. The Users and Security window is displayed.
Chapter 2: Database Server Installation the unrestricted group. Click on the Save button to save this change, and then repeat this process for each practice as required. Exit the Practice Maintenance Desktop. Test Sage Intergy Desktop 14. It is now necessary to test the new support account and the Sage Intergy installation in general. Select the Sage Intergy application icon from the Sage Intergy desktop folder The standard Sage Intergy Logon window is displayed.
Chapter 2: Database Server Installation If successfully configured, the main Sage Intergy application window will be displayed. If you are familiar with Sage Intergy application functions, you may test these at this time. Select the Exit menu to close the Sage Intergy application window. 15. If server backup software is not yet installed, proceed with installation before configuring stand alone application servers or client devices.
Chapter 2: Database Server Installation Customize Backup Script Manually create C:\IntergyBackup and D:\IntergyBackup directories on the Sage Intergy database server. Open the file C:\Intergy\IntergyBackup.bat with a text editor and note the following lines of text: Make the following changes to the batch file before proceeding with scheduling: • If the database server is configured using non-standard drive configuration, change the batch location folder and the staging drive letter as needed.
Chapter 2: Database Server Installation creating a task. Use the following screen shots as guides for configuring the following parameters: When creating a task, set the following general parameters: • Set the local Backup account as the user account • Run whether user is logged on or not. • Run with highest privileges • Configure for Windows Vista or Windows Server 2008 When creating a task, set the following trigger parameters: Sage • Daily schedule starting at 10:00 pm on the current day.
Chapter 2: Database Server Installation As a best practice, test the operation of the script before any further database changes are made. Observe the Windows Server application log and the Sage Intergy logs for any errors that must be resolved. For detailed information on operation and troubleshooting of the Windows task scheduler, refer to the Microsoft documentation at the following URL: http://technet.microsoft.com/en-us/library/cc721871.aspx Next Steps All new Sage Intergy 7.
Chapter 3: Client Installation Chapter 3: Client Installation For day-to-day operation of the Sage Intergy desktop, the Sage Intergy client application components must be installed. Typically, the client is installed on desktop workstation computers for use by employees of a medical practice. Also, a client is typically installed on the Sage Intergy database server for troubleshooting and testing purposes.
Chapter 3: Client Installation Typical Installation Settings The following table lists typical installation settings used for the Sage Intergy clients in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 3: Client Installation Drive letters and directory names should always be adjusted to match actual directory locations when Sage Intergy is installed in a non-standard implementation. Detailed instructions for installation of these application components are provided in the following pages. New Windows Sage Intergy Client Installation Obtain the latest Sage Intergy installation media and hotfix downloads before proceeding with any installation.
Chapter 3: Client Installation Base Windows Workstation Configuration This section covers the configuration of the Windows workstation settings for Sage Intergy clients. For more information on the installation of Windows XP, refer to the Microsoft Knowledgebase articles at http://www.microsoft.com/windowsxp/using/setup/winxp/ install.mspx. For more information on the installation of Windows Vista, refer to the Microsoft installation reference article at http://www.microsoft.
Chapter 3: Client Installation save the file to the workstation. If you save the file to the workstation you will need to run the saved file to install the ScriptX Client before continuing to the next step. If an error message is displayed during installation, verify that the account you are using to install the ScriptX package has local administrator rights on the client computer. Label Printer Default Page Size Clinician allows configuration of different page and label types.
Chapter 3: Client Installation Intenet Explorer Configuration To support printing of customized graphical elements, usage of Clinician requires specific options of Internet Explorer to be configured: • Advanced Printing Options - Select the option to print background colors and images • Advanced Security Options - Select options “Do not save encrypted pages to disk” and “Empty Temporary Internet files when browser is closed”. • Printer page setup - Set all print margins to one-fourth inch (.
Chapter 3: Client Installation After changing settings for printing, security, and temporary files, remember to add https:// clinician.emdeon.com as a trusted site. Refer to the Sage Intergy 7.00 System Requirements document for specific information on the browsers that are supported for use with the Clinician functions of Sage Intergy EHR. Media Installation The Sage Intergy 7.00 DVD installation media may be copied to a shared folder on a single server.
Chapter 3: Client Installation Select Startup Option 3. The setup options window is displayed next. The default choice is to install the client only. From the menu, select the ‘Client’ item and click on the Next button to proceed. Note the other menu items available for installation here. The Database Server/Appserver installation is executed on the primary Sage Intergy database server and should already be completed.
Chapter 3: Client Installation Set Destination Folder 5. The destination folder window is displayed. The preferred location for Sage Intergy application components is the C: drive in a top-level folder. If necessary, change the destination folder before clicking on the Next button to proceed to the next step. Sage Sage Intergy 7.
Chapter 3: Client Installation Select Additional Sage Intergy Applications 6. The additional applications window is displayed. At this window, you may elect to install other Sage Intergy components as needed by the customer. The following options are available: • Transcription Writer - For use in customer sites where transcriptions processed. Microsoft Word must be installed before Transcription Writer may be implemented.
Chapter 3: Client Installation • Progress OpenEdge Application Components • ODSTools • Sage Intergy Client Patch • Ultia Service (status command console windows) 9. If the Sage Intergy EHR installation option is selected for a server, the client installation portion will automatically use the same server information entered for the regular Sage Intergy client. No interaction is required during installation of the Sage Intergy EHR application components on a client workstation. 10.
Chapter 3: Client Installation To download the help file software update for Windows Vista, use the following URL: http://go.microsoft.com/fwlink/?LinkID=82148 To download the help file software update for Windows 7, use the following URL: http://go.microsoft.com/fwlink/?LinkId=166421 Save the file to a temporary directory and double-click on the file in Windows Explorer to execute it. Accept the license terms when prompted and allow the installation to proceed.
Chapter 3: Client Installation Sage Intergy EHR PDA Client Installation Sage Intergy EHR PDA is the Windows CE version of the EHR client application. It is intended to be installed on network-enabled handheld computing devices using Pocket PC or Windows Mobile operating systems. On devices where EHR PDA has not yet been installed, installation is a manual process that requires user interface input. Note that not all handheld computing devices are compatible with EHR PDA. Refer to the Sage Intergy 7.
Chapter 3: Client Installation Tab the Ultia.CAB file and observe installation status bar being displayed. After a few moments, an installation location prompt is displayed. As a best practice, always select the ‘Device’ option so that EHR PDA is installed directly into the handheld computing device memory and not in removable storage. Click on the Install button at the bottom of the screen to proceed with installation. The installation status bar is displayed again.
Chapter 3: Client Installation To configure connection settings, open the EHR PDA Settings application from the Program group list on the handheld computing device: The EHR PDA Settings screen is displayed. Configure the following settings with the appropriate values for each customer environment: • Data Server - Use the DNS name or numeric IP address of the primary Sage Intergy database server. In a typical installation, use the value ‘Sage IntergyServer’.
Chapter 3: Client Installation the customer’s Internet-facing IP address. As a best practice, this address should be static, and not dynamically assigned by the customer’s Internet service provider. For EHR PDA clients connecting using the Internet Zone feature, configure the following settings with the appropriate values for each customer environment: • Data Server - Use the numeric IP address of the external-facing Internet address of the main customer site.
Chapter 4: N-tier Installation Chapter 4: N-tier Installation Sage Intergy customers whose computing environments serve more than 350 simultaneous client connections require installation of Sage Intergy components on multiple servers. This method of implementing Sage Intergy is referred to as N-tier, due to the multiple tiers of client-server connectivity and access. The instructions in this section apply to an environment where a Sage Intergy database server has already been installed.
Chapter 4: N-tier Installation Typical Installation Settings The following table lists typical installation settings used for an N-tier environment in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 4: N-tier Installation In the current version of Sage Intergy, it is possible to install application components on multiple servers to accommodate large numbers of clients, or geographically dispersed clients who are using WAN connectivity. It is also possible to distribute specific server functions to separate servers, in order to offload database or client processing workload. Deploying multiple application servers may also be less expensive than installing one large, powerful application server.
Chapter 4: N-tier Installation • Obtain the Progress serial number and control code data for the Name Server Load Balancing option from the Sage sales organization. This is a licensing component that is separate from Sage Intergy serialization and will be unique to each customer site. • Obtain Progress application update files as necessary. This will include the Progress Service Pack update packages, which is also located on the Sage Intergy installation media.
Chapter 4: N-tier Installation This window will be displayed both for new installations of Sage Intergy 7.00 and upgrades from previous versions. Note carefully the name of the displayed directory. Click on the Yes button to proceed to the next step only if the ‘C:\Intergy\ProRT’ directory is displayed in this window. If any other directory name is displayed, click on the No button and do not proceed with further installation. Contact Sage support for assistance with a manual upgrade procedure.
Chapter 4: N-tier Installation 6. The Choose Destination and Working Path Directories window is displayed. Make sure that the Destination Directory field is specified as ‘X:\Intergy\ProRT’ and that the Working Directory is specified as ‘X:\Intergy\logfiles’ before proceeding. The Progress Name Server Load Balancing components must be installed in the existing primary Sage Intergy database directory on the appropriate drive for correct operation.
Chapter 4: N-tier Installation Application or System errors which may have occurred during the upgrade, and start the local copy of Intergy using the Support account. Installing the Stand Alone Application Server A Stand Alone Application Server is a separate computing device from the database server, and is intended to facilitate distribution of the processing of user logons between several different servers. Installation is very similar to the installation of the Sage Intergy database server.
Chapter 4: N-tier Installation previous step. If you used default settings, this server will be called ‘Intergyserver.’ Click on the Next button to proceed to the next step. 3. The Load Balancing Prompt window is displayed. Always select the first option to enable load balancing for the stand-alone application server. Do not select the second option to disable load balancing except under the direction of R&D personnel. Click on the Next button to continue. 4.
Chapter 4: N-tier Installation 5. The Additional Applications window is displayed. Under normal circumstances, none of these components will be installed on a standalone application server with the exception of Sage Intergy EHR and the Transcription Writer. These components are present for support purposes, and do not indicate that the stand alone application server should also be used as a client workstation.
Chapter 4: N-tier Installation Under normal circumstances, none of these services will be selected for use on a stand alone application server. Click on the Next button to proceed to the next step. 7. A confirmation window will be displayed, listing all of the items selected for installation on the stand alone application server. Review this list, and click on the Next button.
Chapter 4: N-tier Installation configured. If you used the default settings, this will be the Site Code followed by the characters ‘int.’ 3. The System Administration Desktop is displayed. From the Setup menu, select the System Configuration menu item. 4. The System Configuration Window is displayed. Scroll down in the right pane until the ‘Plan Database Connection String’ item is displayed. Note that the field value is blank.
Chapter 4: N-tier Installation 5. To test this change, select the Insurance Plans item from the Setup menu on the main System Administration Desktop and ensure that data can be viewed or edited in the same way as it is on the main Sage Intergy application server. RxDUR Configuration The Rx Database is a third-party application component which is updated quarterly for use with Sage Intergy. It contains specific data related to prescription drugs and clinical usage.
Chapter 4: N-tier Installation 2. When settings access on both folders, give the Everyone global group read-only access. Give the local Sage IntergyService account full read and write access. Set these privileges both in the Sharing Permissions and the Share Security sections of the folder properties. Set Prescription System Parameters 1. Open the Sage Intergy System Administration desktop on the database server. From the Setup menu, select the System Configuration menu item. 2.
Chapter 4: N-tier Installation Substitute the appropriate server name if you are using a different one. Click on Save to save the changes. 3. To run the DUR Update procedure, open the Utilities menu in the Sage Intergy System Administration desktop. Open the Rx menu and select the Rx Update item. If a DUR update has not been executed in this customer’s environment before, an error message will be displayed. This error is expected and may be ignored. 4 - 14 Sage Intergy 7.
Chapter 4: N-tier Installation 4. The Rx Update window will be displayed. Click on the Update button in the lower left corner to test the update procedure. Check the naming and the permissions on each shared folder if an error is reported. Card Scan Configuration The Card Scan utility allows storage of images specific to identification cards. Sage Intergy must be specially configured to make image files available on a network share for multiple application servers. Sage Sage Intergy 7.
Chapter 4: N-tier Installation Create Shared Folders 1. In Windows Explorer, create a new shared folder. By default, scanned ID card images are stored in C:\Intergy\Images and the share name used should be \\IntergyServer\Images. 2. When settings access on this folder, give the Everyone global group read-only access. Give the IntergyService account full read and write access. This account may be either a local account or a domain account, depending on the way the customer environment is configured.
Chapter 4: N-tier Installation Configure Sage Intergy Storage Devices 1. Open the Sage Intergy System Administration desktop on the database server. Select the Storage Devices item from the Setup menu. 2. The Storage Device Maintenance window is displayed. Note that by default, only one storage device is configured. Click on the Edit button to edit the existing storage device. 3. The Storage Device fields in the Details pane are now available for editing:.
Chapter 4: N-tier Installation Next Steps After successful installation of a stand alone application server and correct configuration of Sage Intergy settings, you should proceed with Sage Intergy workstation client installation or upgrades as needed. 4 - 18 Sage Intergy 7.
Chapter 5: Database Tuning Chapter 5: Database Tuning All Sage Intergy 7.00 databases should be manually tuned before client connections are permitted. This applies to all newly implemented installations as well as all Sage Intergy upgrades. Database tuning must also occur in the event of large scale changes to an existing Sage Intergy installation, such as a serialization change that adds new user licenses, or a hardware replacement that changes the specifications of the database server.
Chapter 5: Database Tuning Typical Installation Settings The following table lists typical settings used for database tuning in most environments. Many settings require calculation based on a formula, or require information that must be gathered by the installing technician ahead of time. For numeric configuration settings, note maximum and minimum values carefully. Use this table as a reference if you are already familiar with the details of installation.
Chapter 5: Database Tuning Detailed instructions for configuration of these database tuning parameters are provided in the following pages. Sage Intergy Database Tuning Instructions You may be required to execute commands or change settings in one or more Sage Intergy application components when tuning the database. All instructions below assume that you are logged into the appropriate server with administrative privileges. To configure database tuning values, log directly on to the database server.
Chapter 5: Database Tuning Open Database Default Configuration 1. From the Start Menu, open All Programs and select the ‘Intergy’ folder, then select the Database Administration menu item. 2. From the Database Administration window, expand the Server Manager item in the left pane. Expand the Databases item and click on the ‘Intergy’ menu item to display the status of the primary Sage Intergy database. To proceed with general default configuration, click on the Properties button in the lower right corner.
Chapter 5: Database Tuning number of Sage Intergy users. This value is used to calculate other parameters as described below. • # Blocks in DB buffer - For all new installations, use 100,000 as the parameter value. For post-installation tuning, you must obtain two values from the Sage Intergy database server to calculate this parameter. Use the Windows task manager to observe the amount of physical memory that is unallocated during peak database usage.
Chapter 5: Database Tuning To determine the number of virtual processors in a Windows system, open the Windows Task Manager. In the View menu, make sure that the CPU history shows one graph for each processor. • Other server arguments - This field contains command line arguments that should be changed by the installing technician. For all installs, enter the text -basetable 1 -tablerangesize 1500 -shmsegsize 256 -napmax 250 to set database timing and allow for logging of performance statistics.
Chapter 5: Database Tuning • Maximum servers - This setting is the number of remote client server (RCS) processes. This number is a calculated value based on the number of serialized users for Sage Intergy and Sage Intergy EHR. A different formula is used for N-tier implementations. However, both formulas use the Maximum Clients per Server value entered previously, and may require that value to be changed.
Chapter 5: Database Tuning 2. From the Database Administration window, expand the Server Manager item in the left pane and then expand the AppServer item. For both the ‘Intergy’ and ‘IntergyAsync’ objects, click to display the Appserver status and click on the Properties button item in the lower right corner to configure application server settings. Apply the settings described in this section both to the ‘Intergy’ and the ‘IntergyAsync’ application server objects. Application Server settings 3.
Chapter 5: Database Tuning the database server uses a priority weight value of 350, and a stand alone application server uses a value based on the maximum number of base users that will be connected. Refer to the Sage Intergy 7.00 System Requirements document to obtain the maximum number of users that may be connected to a stand alone application server. • Server startup timeout - This value is always set to zero. • Registration Mode - By default, the Use Broker Host IP Address radio button is selected.
Chapter 5: Database Tuning 3. The name server properties window is displayed. Click on the Advanced button to display advanced settings, and click on the Edit button to make changes. In the logging level field, make sure the ‘Error Only’ value is selected from the drop down list. Click on Save to apply this change, and then click on the Close button to close the nameserver properties window.
Chapter 6: Intergy Storage Server Configuration Chapter 6: Intergy Storage Server Configuration When installing the Sage Intergy application server, other Sage Intergy applications may be installed successfully without additional configuration. However, note that Sage Intergy Storage Server (ISS) requires manual configuration before it can be used. The configuration step is performed in the System Configuration window of the Sage Intergy System Administration desktop.
Chapter 6: Intergy Storage Server Configuration Typical Installation Settings The following table lists installation settings used for the Sage Intergy Storage Server in most environments. Refer to this table if you are already familiar with the details of installation. Application Component System Configuration Settings Configuration Item Value or Setting Image Catalog Path \.
Chapter 6: Intergy Storage Server Configuration Open Sage Intergy System Configuration 1. Open the Sage Intergy desktop folder or the Sage Intergy program group from the Start menu and click on the System Administration icon, and then log on as the ‘sysadm’ user with the appropriate password for the customer environment. 2. When the Sage Intergy System Administration window is displayed, click on the Setup menu and select the System Configuration item. 3.
Chapter 6: Intergy Storage Server Configuration 1. To access the Storage Server Administrative Console, click on the Start Menu, click on the All Programs menu and open the Sage Intergy Storage Server menu. Select the Administrative Console item to proceed. 2. The logon screen will be displayed. Log in as the support user, typing in ‘Support’ for the user name as well as the appropriate password. 3.
Chapter 6: Intergy Storage Server Configuration of licenses available in an existing installation. The displayed information will automatically update after a new license has been selected and applied. Note that newly applied licenses are not effective until the Sage Intergy Storage Service is restarted. You may restart the service from the Services item of the administrative console, or from the Windows Services Control Panel. The service is also restarted when the server is rebooted.
Chapter 6: Intergy Storage Server Configuration 3. When the Administrative Console is displayed, click on the Storage item in the left pane to display the Storage configuration options. Click on the Storage Devices tab. 4. Right-click in the Storage Device list pane and select the Add New Storage Device menu item to add a storage device. The E: drive is the preferred location for the main storage device.
Chapter 6: Intergy Storage Server Configuration customized environments. Set the file to be executed from the Action tab when creating a task. Use the following screen shots as guides for configuring the following parameters: When creating a task, set the following general parameters: • Set the local ‘Backup’ account as the user account • Run whether user is logged on or not.
Chapter 6: Intergy Storage Server Configuration As a best practice, test the operation of the script before any further database changes are made. Observe the Windows Server application log and the Sage Intergy logs for any errors that must be resolved. Special instructions for 64-bit systems For installation of Sage Intergy Storage Server on a 64-bit operating system, the ‘-r’ argument must be applied to specify the directory of the PostgreSQL binary files.
Chapter 7: Document Delivery Server Configuration Chapter 7: Document Delivery Server Configuration When installing the Sage Intergy application server, other Sage Intergy applications may be installed successfully without additional configuration. However, Document Delivery Server (DDS) requires manual configuration before it can be used. Sage Intergy customers who make use of Transcription Writer, or who are Radiology Information System (RIS) users may require installation and configuration of DDS.
Chapter 7: Document Delivery Server Configuration Typical Installation Settings The following table lists typical installation settings used for DDS in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 7: Document Delivery Server Configuration Directory names should always be adjusted to match actual directory locations when Sage Intergy is installed in a non-standard implementation. Detailed instructions for installation of these application components are provided in the following pages.
Chapter 7: Document Delivery Server Configuration Installed Sage Intergy Components When installing a new stand alone server, make sure that only one of the DDS installation options is selected during the setup process: Select only the DDS Transcription Append Approve Line services option, or the RIS DDS Services option. Do not select both checkboxes. Note that the Report Cleanup Service is not selected by default since this is not the primary database server.
Chapter 7: Document Delivery Server Configuration FaxPress Hardware Installation Installation of a Castelle FaxPress 2500 server or OpenText FaxPress 2L device and client application components is required for DDS implementations that will deliver transcriptions via fax. Configuration will differ depending on the type of hardware that is installed in the customer environment. Castelle FaxPress 2500 devices Castelle FaxPress 9.
Chapter 7: Document Delivery Server Configuration Line Settings: • Call Subscriber ID - Practice Name • Local Fax Number - Phone number of connected line • Dialing Type - Tone • PBX Pre-Dial - Enter the numeric digits used for an outside line. For example, many sites require dialing ‘9’ prior to dialing a remote phone number.
Chapter 7: Document Delivery Server Configuration • Profile Path - \\\users\%username% • Group Membership - Domain Users, Domain Admins • Log On As A Service right granted Adjust these settings as necessary to suit the customer environment as appropriate. Make sure that password expiration and other security parameters are appropriately configured based on the Windows base configuration.
Chapter 7: Document Delivery Server Configuration Note that the Document Delivery menu item will appear on the Communications menu of the Sage Intergy Desktop whether or not DDS is selected as an installed component. DDS Windows Services Verify that the DDS Windows services are installed correctly, and change the accounts used for authentication as needed. Verify Installed Services 1.
Chapter 7: Document Delivery Server Configuration 4. Click on the This Account radio button and enter the domain and account name in the first field, and the password in the second and third fields. Make this change for all five services. In single queue configuration, DDS will use only the DDSApprove service. If you are installing in single queue configuration, you must disable the other four services to improve performance.
Chapter 7: Document Delivery Server Configuration Open Report Maintenance 2. The Report Maintenance window is displayed. Select the Transcription report code from the Reports pane, and then click on the Edit Options button to allow editing in the Report Output Options pane. Add Printer as Report Output 3. In the Output Destination section, make sure the Printer checkbox is selected as one of the available report destinations.
Chapter 7: Document Delivery Server Configuration 5. The New System Printer window is displayed. 6. Click on the drop-down button to the right of the O/S Printer Name field to select one of the printers configured for normal Windows printing. The Select Computer Printer window will be displayed. 7. Select the appropriate printer from the list and click on the OK button to return to the New System Printer window. 8. Note that the system printer parameters are automatically populated.
Chapter 7: Document Delivery Server Configuration Note that the selected printer is now listed as the output destination. 9. Click on the Save button to save the new settings to the Transcription report type. Click on the Close menu at the top of the window to close Report Maintenance. DDS System Administration Parameters After configuring transcription printers, specific DDS parameters must be defined by the technician. 1.
Chapter 7: Document Delivery Server Configuration • Fax Server IP Address - The numeric address of the Castelle FaxPress server on the customer’s LAN. • Fax Server User ID - The user name transmitted by the Castelle FaxPress client when connecting to the server. • Fax Server Password - The password transmitted by the Castelle FaxPress client software when connecting to the server. • Fax Server Software Location - The directory of the locally installed Castelle FaxPress client software.
Chapter 7: Document Delivery Server Configuration System Printer Maintenance Setting 2. The System Printer Maintenance window is displayed. Create Printer Location Rule 3. Click on the Printer Locations radio button, and then click on the New button to display the New Printer Location Rule window. 4.
Chapter 7: Document Delivery Server Configuration 7. Click on the Close menu at the top of the window to close the System Printer Maintenance window. 8. Repeat these configuring steps for each practice that will make use of the DDS system. Close the Sage Intergy Practice Administration desktop when finished. Referring Provider Information Setup After all printers are configured correctly, the final step in DDS configuration is the entry of referring provider contact information.
Chapter 7: Document Delivery Server Configuration Enter New Providers 3. After gathering the required information about the referring provider, click on the New button to enter a new provider. The New Referring Provider window will be displayed. 4. Note that the table at the bottom of the window contains several rows for the purpose of recording multiple phone numbers. For each provider added, make sure that the Fax field is correctly populated.
Chapter 7: Document Delivery Server Configuration Override Default Values If Necessary 6. For each provider that will receive documents via DDS, select the provider and then click on the Preferences radio button to display the Referring Provider preferences window. Note that each row in the Preferences table includes a default value. These default values were defined in the DDS settings on the Sage Intergy System Configuration window as described on page 7-12.
Chapter 7: Document Delivery Server Configuration of an outbound fax drop directory allows DDS to create image files in a UNC file share, which are then processed by a third-party fax application. This type of configuration requires Sage Intergy System Configuration changes. Note that the use of the outbound fax drop directory is considered a blind transmission solution.
Chapter 8: TMS Import Service Configuration Chapter 8: TMS Import Service Configuration When installing the Sage Intergy application server, other Sage Intergy applications may be installed successfully without additional configuration. However, the TMS Import Service supporting Transcription Management System (TMS) and Imaging bulk import requires manual configuration before it can be used.
Chapter 8: TMS Import Service Configuration Typical Installation Settings The following table lists typical installation settings used for the Transcription Management System Import Service in most environments. However, some settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 8: TMS Import Service Configuration the server or workstation where the TMS Import Service will operate to complete this type of installation. Note that the TMS Import Service may be installed on a stand alone server or workstation as a separate component, instead of on the primary Sage Intergy database server.
Chapter 8: TMS Import Service Configuration Note that the tenth line of this file defines the ImportPath parameter. Open this file in Windows Notepad on the server or workstation where the TMS Import Service has been installed, and change the name of this directory as required. Save the file after your changes have been completed. Imaging Configuration To support the import of Imaging files, an additional parameter must be entered into the TMSSvcMan.
Chapter 8: TMS Import Service Configuration Table 1: Transcription Import Text File format Column Description 3- Patient Name A field entered for reporting purposes only. This field may contain text only and may not include punctuation or nonalphanumeric characters.
Chapter 8: TMS Import Service Configuration Table 1: Transcription Import Text File format Column 11 - Encounter Number Description An optional field to define the encounter number. This field does not correspond to any value stored in Sage Intergy and is used for reporting purposes only.
Chapter 8: TMS Import Service Configuration Configure External Imaging Application Normally, Imaging data is submitted from Sage Intergy clients using the Image Manager application and a scanner or other input device. When image files are accessed by the TMS Import Service for a bulk import, an external application must create a text file that defines how image files found in the shared folder are processed. A typical example of a imaging import text file is given below: OFC,10,John Smith,PI,HOSP,image1.
Chapter 8: TMS Import Service Configuration Table 2: Imaging Import Text File format Column Description 7 - Description A text string with a user-generated description. This field corresponds to the Document.Description field in Sage Intergy. 8 - Reference Date A reference date assigned to the Imaging document.
Chapter 9: Terminal Services Client Installation Chapter 9: Terminal Services Client Installation When installing the Sage Intergy database server, Windows Terminal Services is installed by default and may service up to forty user connections. However, some Sage customers may require that a larger number of users be able to connect to a remote desktop session and use the thin client implementation of Sage Intergy.
Chapter 9: Terminal Services Client Installation Typical Installation Settings The following table lists typical settings used for Terminal Services in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Chapter 9: Terminal Services Client Installation At a high level, you will complete the following tasks when implementing Terminal Services with a Sage Intergy 7.00 installation • Implement Windows server as member of Active Directory domain. • Install Terminal Services and Licensing components of Windows. • Set application install mode for each installation. • Install Microsoft Office (for sites requiring transcriptions of DDS.) • Install Sage Intergy Client.
Chapter 9: Terminal Services Client Installation 3. Note that the left pane is expanded to include additional steps that are necessary as part of Terminal Services installation. As you proceed through the installation of Terminal Services, select licensing options that apply to the customer site. Specify the installation of the Terminal Server Licensing components only if another licensing server is not already available in the customer environment.
Chapter 9: Terminal Services Client Installation 2. Fill in the checkboxes for the Terminal Server and Terminal Server Licensing options. Click on the Next button to proceed to the steps that must be completed to gather computing environment information. Specify the installation of the Terminal Server Licensing components only if another licensing server is not already available in the customer environment.
Chapter 9: Terminal Services Client Installation 1. To install an application for use with terminal services, open the Control Panel and double-click on the Install Application on Terminal Server icon. Clicking on this control panel automatically sets the server to application install mode and proceeds directly to the add program procedure. 2. The first window of the program installation procedure is displayed. If necessary, click on the What is TS-Install Mode link to access the help content.
Chapter 9: Terminal Services Client Installation 3. The Run Installation window is displayed. Follow the instructions to execute the installation program. For most applications, installation will proceed normally. 4. After normal installation has completed, the After Installation window prompt is displayed. This window may be displayed before installation has completed. Do not click on the next button until all application installation steps have been completed, with the exception of server reboots.
Chapter 9: Terminal Services Client Installation 5. Once you have clicked next, the Finish Admin Install window is displayed. Read the prompt carefully and click on the Finish button only after installation has completed successfully. The server will automatically be set back to application execute mode after you click on the Finish button. Note that this process must be repeated for each individual application installation.
Chapter 9: Terminal Services Client Installation Set Application Mode to Install 1. Open the Add/Remove Programs control panel. 2. Click on the Add New Programs icon in the left pane of the control panel. The add programs options menu is displayed. 3. Click on the CD or Floppy button to proceed to the next step. The first window of the program installation procedure is displayed. Use of the Add/Remove programs control panel places the server in install mode. Sage Sage Intergy 7.
Chapter 9: Terminal Services Client Installation Insert Install Media 4. At this point, insert the media or mount the network drive for the application you are installing and click on the next button. The Run Installation window is displayed. 5. Follow the instructions to execute the installation program. For most applications, installation will proceed normally. After normal installation has completed, the After Installation window prompt is displayed.
Chapter 9: Terminal Services Client Installation 7. Once you have clicked next, the Finish Admin Install window is displayed. Read the prompt carefully and click on the Finish button only after installation has completed successfully. Clicking on the Finish button places the server back into execute mode. Note that this process must be repeated for each individual application installation. The terminal server must be put into application install mode for each separate installation action.
Chapter 9: Terminal Services Client Installation Manual Upgrade When performing a manual upgrade, you must log on the Windows console as an administrator. Do not use an RDP session for manual upgrades of a terminal server. After placing the terminal server into application install mode, installation of the Sage Intergy client and stand alone application server functions is identical to the procedure described in Sage Intergy Client Installation section of this document.
Chapter 9: Terminal Services Client Installation • twain.dll • twain_32.dll • Twain_32 (the directory name) If necessary, copy all five items from an existing user home directory to the home directory of any newly created users that require the use of scanning functions. Card Readers To support the use of card readers, Remote Desktop local resource redirection must be activated for Plug And Play (PnP) devices.
Chapter 9: Terminal Services Client Installation Click on the More button to display other device options. Select the checkbox for ‘Other support Plug and Play devices’. Click on the OK button to exit the window, and then return to the Remote Desktop Connection properties window and save the changes. You have successfully enabled support for card reader devices under Sage Intergy On Demand. Note that the MAGTEK Model 21040145 card reader device is not supported for use in Sage Intergy On Demand.
Chapter 10: Type II Database Conversion Chapter 10: Type II Database Conversion New implementations of Sage Intergy 7.00 are installed with the Type II database by default. This database variant is an improved structure and arrangement of the Progress database that prevents scattering of table blocks. Also, database extents and tables have been renamed for ease of troubleshooting and logging. When upgrading an existing Sage Intergy site to version 7.00 from version 5.
Chapter 10: Type II Database Conversion Type II Database Conversion Overview Conversion of Sage Intergy 7.00 databases to the type II configuration applies only to upgrades from previous versions of Sage Intergy. If you have installed a new Sage Intergy 7.00 database server in a customer environment, the type II database is already present and you may skip the work actions described in this chapter. Note that some Sage Intergy 5.50 sites and most Sage Intergy 6.
Chapter 10: Type II Database Conversion To stop Sage Intergy Windows services, open the Server Manager console on the Sage Intergy database server and access the Services management interface. Select each service that begins with the word ‘Intergy’ and manually stop each process. After stopping all Sage Intergy Windows services, manually stop the Remote Monitoring System (RMS) services.
Chapter 10: Type II Database Conversion 3. From the Start Menu or the Sage Intergy program folder, start the Database Administration tool. Click on the Dump/Load menu item in the left pane to display the Database Dump/Load Utility. Note the new text and prompts indicating that the option to convert to a type II database is available.. 4. Click on the Stop Database button in the upper right corner. A prompt will be displayed, asking you to enter the system administration logon credentials.
Chapter 10: Type II Database Conversion A prompt may also be displayed which reminds you to complete a database backup prompt. Click yes on both of these prompts to proceed. 9. The Database Administration Dump/Load Utility Status window is displayed. Each step of the type II database conversion procedure is enumerated in this window. Observe the progress of the conversion, and use the time/date stamps and status indicators to estimate the time that will be required for conversion.
Chapter 10: Type II Database Conversion Click on the OK button to close the Database Administration Dump/Load Status Utility window and return to the Database Administration tool. You have successfully completed the dump and load process. Proceed to the next section to restart services and verify client functionality. Start Services and Test Client Connectivity After successful conversion, restart the database and all Sage Intergy Windows services.
Chapter 11: Initial Printer Configuration Chapter 11: Initial Printer Configuration All implementations of Sage Intergy will require the use of printers to support the normal business functions of a medical practice. In most cases, Sage Intergy and Sage Intergy EHR client workstations may be configured to use a default Microsoft Windows printer. Some advanced Sage Intergy print functions must be configured to support the installation of Sage Intergy EHR PDA handheld devices.
Chapter 11: Initial Printer Configuration Initial Printer Configuration for Sage Intergy In most newly installed Sage Intergy customer sites, technicians will be required only to configure default Windows printers on each client workstation, and in each Remote Desktop profile for sites using Terminal Services. Sage Intergy 7.00 uses the default Microsoft Windows printing API to provide print services for reports and other hardcopy output. Customer sites that have been upgraded from Sage Intergy 5.
Chapter 11: Initial Printer Configuration Note that the print server and the Sage Intergy database server may be different devices, especially in customer sites with existing computing envirnoments already implemented. When implementing System Printers, Sage technicians may be responsible for some or all of the following work actions: • Creating printer shares - In existing computing environments not implemented by Sage, some or all printers may be locally connected only.
Chapter 11: Initial Printer Configuration configuration of system printers using the System Admnistration or Practice Administration desktop interface should be performed directly on the Sage Intergy database server and not on a workstation or on another server. Defining a System Printer Log on to the Sage Intergy database server. Open the System Administration or Practice Administration desktop and click on the Setup menu. Open the Printers menu and select the System Printers item to begin configuration.
Chapter 11: Initial Printer Configuration Click on the New button to configure a new system printer. The New System Printer window is displayed. Click on the drop-down button to the right of the O/S Printer Name field and a list of available shared printers is displayed. Select a printer from the list to automatically populate all the other fields in the New System Printer window. Click on the Save button to save the new system printer, or click on the Clear button to start over.
Chapter 11: Initial Printer Configuration Note the following configurable options: • Output Destination - For many reports, the default setting Ask User will prompt Sage Intergy desktop users to select a print destination. However, for some reports it may be necessary to configure only one specific output type. Select the Send To option only for reports that require a specific output type.
Chapter 11: Initial Printer Configuration Configuring Printer Classes When configuring a system printer, note the Printer Class options that are available for configuration. System printers may be categorized in one or more printer classes. The use of printer classes allows reports to be configured to print to a set of system printers, instead of just one printer. This type of configuration is used in large computing environments where many printers are implemented.
Chapter 11: Initial Printer Configuration Configuration of Remote Print Service Remote Print Service (RPS) is installed only for Sage Intergy sites that require the use of Sage Intergy EHR PDA handheld client devices. Since Pocket PC and Windows CE devices do not use the same printing mechanisms as standard Windows workstations, RPS is used to direct prescription printing and other print output functions that apply specifically to the EHR PDA device.
Chapter 11: Initial Printer Configuration Setting the Service Account By default, all Sage Intergy services are configured to operate as the Local System Account. However, because the RPS service will require access to shared printers on the local network, the service must be configured to operate using a service account instead. Configure this service to use the Sage Intergy Service Account defined in the Operating System Infrastructure chapter on page 1-13.
Chapter 11: Initial Printer Configuration The Remote Print Server Maintenance window is displayed. Click on the New button to define a new RPS print destination. Enter the following values for the new RPS print destination: • Remote Print Server - An arbitrary text field that defines a unique RPS service. Some environments may require more than one RPS, most often in the case of separate practices with separate printer hardware.
Chapter 11: Initial Printer Configuration Note the Remote Print Server field. Clicking in this field will display a drop-down button to the right side of the text area. Click on this button to display a list of available RPS print destinations. Select the RPS print destination you configured previously. Alterately, you may also create a new RPS print destination from this window. Click on the OK button to associate this RPS server with the system printer you have created.
Chapter 11: Initial Printer Configuration administrative credentials and use the Printer Server Properties component of the Printers control panel. Do not use vendor installation wizards to install printer drivers for Sage Intergy On Demand servers. These applications may also install multifunction application components that are not supported for use with IOD servers.
Appendix A: Backup Application Installation and Configuration Appendix A: Backup Application Installation and Configuration Database server computing environments must include a robust backup solution. For Sage Intergy customer sites that do not have their own purchased product, Sage offers Symantec Backup Exec 12.5 and Symantec System Recovery as its preferred backup solutions for use with Sage Intergy.
Appendix A: Backup Application Installation and Configuration Typical Installation Settings The following table lists typical installation settings used for Backup Exec in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Appendix A: Backup Application Installation and Configuration Application Component Configuration Item Value or Setting Drive Selection C:, D;, E: Backup Destinations Use literal backup media (or G: for mounted RDX Quickstore drive) Recovery Point Options Backup job name - Sage Intergy Nightly Backup System Recovery Backup Job Definitions Backup Batch Files Compression - High Verify recovery point after creation checkbox selected Backup Time Weekly All days selected 10:00 pm Manage Backup Dest
Appendix A: Backup Application Installation and Configuration Create Administrative Account Before installing Symantec System Recovery or Symantec Backup Exec, an administrative account must be created in Sage Intergy, or in the domain where the primary Sage Intergy database server is located. If no Windows domain is installed, create a new user in the local user group of the server. Using Active Directory Users and Computers, create a new user object in the Users organizational unit.
Appendix A: Backup Application Installation and Configuration Install Symantec Backup Exec From Media These instructions apply to the installation of Symantec Backup Exec. For instructions describing the installation of Symantec System Recovery, proceed to page 12-16. When installing Backup Exec from CD media, the CD browser window will be displayed when the disk is inserted. 1. To begin installation, select the Start Installation menu option. 2. The Backup Exec installation wizard is displayed.
Appendix A: Backup Application Installation and Configuration successfully installation of Backup Exec. If necessary, cancel the installation to address any reported problems. Otherwise, click on Next to proceed to the next step. Enter Purchased License Key 4. The license key entry window is displayed. Note that one installation of Backup Exec may require several different license keys for successful completion, depending on the installed hardware and the components purchased by the customer.
Appendix A: Backup Application Installation and Configuration products are installed, accept the default options and click on Next to continue to the next step. Enter Service Account Information 6. The Services Account Information window is displayed. If you created the backup administration account using default settings, type ‘backup’ for the user name and ‘!backup!’ for the password, and make sure the selected domain is the Intergy domain.
Appendix A: Backup Application Installation and Configuration 7. A pop-up window will be displayed indicating that the backup account has been granted new rights on the local server. Click on OK to accept these automatic changes and proceed to the next step. Enter Database Parameters 8. The Database Configuration window is displayed. Select the option called ‘Create a local Backup Exec MSDE’ or ‘Create a local Backup Exec SQL Express Instance’ to create a new local database.
Appendix A: Backup Application Installation and Configuration install the vendor driver files. For most installations you will not use drivers provided by the hardware manufacturer. Click on the Next button to proceed to the next step. 10. An overview window is displayed, describing all the selected installation components. Review this list carefully and click on Install to proceed with the installation. Several windows with progress bars will also be displayed detailing each step of the installation.
Appendix A: Backup Application Installation and Configuration 1. To configure Backup Exec, start the Backup Exec Administration console from the Symantec Backup Exec program group in the Start menu. 2. The Backup Exec Administration console is displayed. If a configuration wizard starts, click on the Cancel button to return to the Administration console and set options manually. 12 - 10 Sage Intergy 7.
Appendix A: Backup Application Installation and Configuration Create a New Backup Job 3. Clicking on the ‘New job using wizard’ item in the Backup Tasks window will display the Backup Wizard. The first window displayed is the Backup Selections window. To configure these backup selections, make sure that all physical hard drives are selected. On a server with a default configuration, this means that the C, D, and E drives are selected and the CD-ROM or DVD-ROM drive is not selected.
Appendix A: Backup Application Installation and Configuration 4. The Volume Credentials and Volume Order windows are displayed. Accept default settings for both these windows and click on Next for each. 5. The Backup Names window is displayed. Enter ‘Full System Backup’ in both fields and click on Next to proceed to the next step. 6. The Backup Device selection window is displayed. Select the tape drive and the default media set and click on Next to proceed to the next step. 12 - 12 Sage Intergy 7.
Appendix A: Backup Application Installation and Configuration 7. The Overwrite Method window is displayed. Change the selected radio button so that the Overwrite Media option is selected, and click on Next to continue. 8. The Backup Options window is displayed. Select ‘Full - Backup Files - Reset Archive Bit’ for the backup type and click in the ‘Yes, Verify after backup’ radio button to select these options. Click on Next to continue. 9. The Completion Notification window is displayed.
Appendix A: Backup Application Installation and Configuration Backup Job Scheduling The Backup Exec job scheduler will start automatically after creating the new full backup job. 1. The Job Scheduler is displayed. Click on the Edit Schedule Details button to set the following backup schedule criteria: • Time Window - start no earlier than: 11:00 pm • Time Window - start no later than: 11:01 pm • Recurring Week Days - Days that the customer is in operation (usually Monday through Friday) 2.
Appendix A: Backup Application Installation and Configuration 3. The Backup Exec Administration window is displayed again. Note that in the Job Setup tab, the backup job which you just created is now listed as a scheduled item. Copy Backup Batch Files 4. From the File Storage Area, download the Standard Intergy Backup Batch File archive and extract the files to a temporary location.
Appendix A: Backup Application Installation and Configuration Install Symantec System Recovery These instructions apply to the installation of Symantec Symantec Recovery. For instructions describing the installation of Symantec Backup Exec, proceed to page 12-5. Before installation, verify that the backup media device is properly installed. The RDX QuickStore removable drive is the default backup device configured on most new Sage Intergy 7.00 servers. Refer to the Sage Intergy 7.
Appendix A: Backup Application Installation and Configuration 2. Installation progress windows will be displayed, and at the end of the installation process an Installshield prompt window is displayed. Click on the Finish button to display a reboot prompt. 3. Click on the Yes button to proceed with the reboot. After the server has finished rebooting, log on as the administrator. The Symantec System Recovery welcome screen will be displayed automatically upon logon. 4.
Appendix A: Backup Application Installation and Configuration setting to activate the license at a later time. Click on the Next button to proceed to the next step. 5. If you have selected the trial license, the Trial Period Reminder window is displayed. Note that the Run LiveUpdate checkbox is selected automatically. Click on the Finish button to proceed to the next step. 6. The LiveUpdate Express start window is displayed.
Appendix A: Backup Application Installation and Configuration 7. The System Recovery administration application window is displayed. Click on the Define Backup Wizard link in the top pane of the window to proceed with configuration 8. The Define Backup Wizard welcome screen is displayed. Click on the radio button with the label ‘Back up my computer’ and click on the Next button to proceed to the next step. Sage Sage Intergy 7.
Appendix A: Backup Application Installation and Configuration 9. The Drive Selection window is displayed. Drive partitions will be displayed in the drive list. Typically, three logical drives are defined for most Sage Intergy database servers. Holding down the CTRL key, click on all three drives to highlight them as selections. Click on the next button to proceed to the next step. 10. The Recovery Point Type selection window is displayed.
Appendix A: Backup Application Installation and Configuration Click on the Browse button to select the appropriate backup destination device. For sites using the RDX Quickstore removable drive, configure a drive letter as the destination folder. In a typical installation, this drive will be G:. Some backup devices may not be configured to correspond to a logical drive, so click through the available backup device options to select the correct device. Click on the Next button to proceed to the next step.
Appendix A: Backup Application Installation and Configuration 14. The Command Files configuration window is displayed. No configuration settings should be changed on this window. Accept all default values and click on the Next button to proceed to the next step. 15. The Backup Time configuration window is displayed. Click on the drop-down menu and select the Weekly option for automatic recovery point creation. After selecting this option a new set of configuration parameters will be displayed.
Appendix A: Backup Application Installation and Configuration 18. The Advanced backup administration options window is displayed. Click on the Manage Backup Destination item in the Tasks list to proceed to the next step. 19. The Manage Backup Destination window is displayed. From the drop-down list, select the drive letter or device that is assigned. In a typical installation, this will be the G: drive assigned to the RDX Quickstore removable disk.
Appendix A: Backup Application Installation and Configuration 20. The Manage Backup Destination Settings window is displayed. Make sure that the ‘Automatically optimize storage’ radio button is selected. This setting will permit automatic overwriting of old backup images and prevent backup failure due to a lack of storage space. Click on the OK button to save these settings, and then click on Yes when the confirmation prompt is displayed. Copy Backup Batch Files 21.
Appendix B: Antivirus Configuration Appendix B: Antivirus Configuration All customer computing environments should include a virus protection program on all servers and all workstations. If the customer does not already have one installed or purchased, Sage offers Symantec Endpoint Protection as its preferred virus protection application. Note that not all antivirus applications are recommended for use with Sage Intergy.
Appendix B: Antivirus Configuration Typical Installation Settings The following table lists typical installation settings used for virus protection applications in most environments. Note that some settings are specific to the Symantec Endpoint Protection product, and some are generic to all virus protection applications. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment.
Appendix B: Antivirus Configuration Installation of Symantec Endpoint Protection Sage offers the Symantec Endpoint Protection product for customers who do not already have an antivirus product, or who wish to purchase one specifically for use with the Sage Intergy suite. For detailed information on installation procedures, refer to the following URL: http://service1.symantec.com/support/ent-security.
Appendix B: Antivirus Configuration All other configuration requirements also apply to the Symantec Endpoint Protection product. Configure file extension and directory exclusions for each Sage Intergy server or workstation as specified in the next section. Settings for All Antivirus Applications Many configuration options are generic to all virus protection applications.
Appendix C: Intergy Technical Process Reference Appendix C: Intergy Technical Process Reference Technicians who are responsible for implementing Sage Intergy may be required to perform certain maintenance functions in the course of installation or upgrade. This appendix provides a summary of the steps needed to complete these technical processes during installation and maintenance of Sage Intergy. Placing Sage Intergy in Maintenance Mode . . . . . . . . . . . . . .
Appendix C: Intergy Technical Process Reference Placing Sage Intergy in Maintenance Mode It is necessary to place the Sage Intergy Database in maintenance mode before proceeding with some changes to the Progress database. These instructions assume you are logged on to the Sage Intergy database server in a Windows environment, or on the AIX administrative console Windows workstation in an AIX environment. Open Sage Intergy System Maintenance 1.
Appendix C: Intergy Technical Process Reference shown. To put the Sage Intergy Database into maintenance mode, click on the schedule button to proceed. 5. The maintenance schedule dialogue is displayed. Enter the current time and date, and click on the Schedule button to proceed. If you click on the Advanced button, you will be offered the option of delaying the scheduled maintenance and sending a warning notification to users. This is not required for new installations.
Appendix C: Intergy Technical Process Reference Manually Shutting Down HL7 Processes 6. To shut down the HL7 processes manually, use the Sage Intergy System Administration Desktop again. From the Utilities menu, open the HL7 menu and select the Monitor item. 7. The HL7 monitor is displayed. Note the buttons and checkbox in the lower left corner. Uncheck the ‘Auto Start’ checkbox so that processes do not start by themselves during the upgrade process. 8.
Appendix C: Intergy Technical Process Reference Manual database shutdown 9. From the Sage Intergy programs folder, open the Database Administration tool. 10. Click on the Stop Database button to stop the database. Close the Database Administration tool. As a best practice, open the Windows Task Manager and make sure that all related Sage Intergy processes have stopped. This includes processes with the names ‘_mprosrv’, ‘_proapsv’ and ‘_progres’. End System Maintenance 11.
Appendix C: Intergy Technical Process Reference 12. The System Maintenance Scheduler window is displayed. To take the Sage Intergy Database out of maintenance mode, click on the clear schedule button. You may be required to reboot the server after taking the Sage Intergy database server out of maintenance mode. Refer to the instructions for the specific installation process for more information.
Appendix C: Intergy Technical Process Reference 2. Click on the Backup Database item in the left pane to perform a database backup. This file should be stored locally, but not in the same location as the normally scheduled backup. 3. When the backup is complete, click on the Stop Database button to stop the database.
Appendix C: Intergy Technical Process Reference 3. The Serialization window may be displayed immediately of the previous license is no longer valid. Otherwise, it will be necessary to select the Serialization item from the Utilities menu in the System Administration Desktop. 4. Previous serialization data may be displayed here, depending on what products were purchased by the customer for the version prior to the upgrade. Click on the Serialize button. 5.
Appendix C: Intergy Technical Process Reference extension LIC. Alternately, you may copy this file to the C: drive of the workstation or Windows server. Select the file and click on the Open button to proceed. 6. If this serialization file includes a license for IEHR, a warning window will also be displayed. Read the text of the warning. Notify the customer about the restriction on OmniDoc usage if necessary. Click on the OK button to proceed. 7.
Appendix C: Intergy Technical Process Reference 8. After several minutes, the Serialization window is displayed with content and information on licensed products and subsystems. If necessary, review this information with the customer representative to ensure that all purchased licenses are represented on the screen. Click on the Close button to exit the Serialization window.
Appendix C: Intergy Technical Process Reference Queue Monitor Status Check 2. In the Sage Intergy System Administration desktop, click on the Utilities menu, open the RX menu and select the Rx EDI menu item. 3. The Rx EDI Status window is displayed. Note the information displayed in the Queue Monitor Status field. If the queue monitor is in a running state, click on the Stop Monitor button in the lower left corner of the window to stop this process. Sage Sage Intergy 7.
Appendix C: Intergy Technical Process Reference 4. The Stop Monitor Information dialogue window will be displayed. Click on the OK button to return to the Rx EDI Status window. 5. Click on the Refresh button to update the displayed status field. Once the stopped state is displayed, click on the Close menu item to close this window and return to the System Administration Desktop. Media Configuration 6.
Appendix C: Intergy Technical Process Reference 7. The System Configuration window is displayed. In the left pane, expand the Prescriptions item and click on the System item. Several parameters will be displayed in the right pane. Depending on the operating system in your environment, make the following System Configuration changes: Table 1: Prescription System Configuration Parameters Parameter Sage Value Rx Update Temporary Directory C:\Intergy\RxTemp Trace Level Accept default value.
Appendix C: Intergy Technical Process Reference Before proceeding with any other part of the installation, verify that the temporary directory and the solution installation directory exist on the database server file system. You may be required to create these directories manually. Note that the Rx Update Temporary Directory in Windows environments may not be C:\Intergy\Temp due to automated cleanup procedures that affect the contents of this directory.
Appendix C: Intergy Technical Process Reference 11. The RxUpdate window is displayed. Click on the Update button to proceed. Before the update installation begins, a confirmation pop-up window may be displayed indicates which files will be changed, and provides the option of cancelling the update. Click on the OK button to continue with installation. 12. The RxUpdate window will change to include new information in the pane at the bottom. The Update Status will change to read Starting Update.
Appendix C: Intergy Technical Process Reference 13. After a few moments, Checking for Media Corruption will be displayed in the Update Status pane. 14. After a few more minutes, Loading Drugs will be displayed in the Update Status pane. Note that at this point, the number of records processed and loaded will be displayed as they increment. This part of the procedure will generally take up to four hours or more, depending on the specifications of the server. 15.
Appendix C: Intergy Technical Process Reference 16. The message ‘Update Successfully Completed’ will be displayed in the Update Status pane when the installation ends successfully. Click on the Close menu option in the menu bar to close the window and return to the Sage Intergy System Administration Desktop. The Sage Intergy database will typically grow up to three gigabytes when installing RxDUR for the first time.
Appendix C: Intergy Technical Process Reference 18. The Rx EDI Status window is displayed. Note that the Queue Monitor Status field indicates that the service is in a stopped state. Click on the Start Monitor button in the lower left corner to restart the Queue Monitor. 19. The Start Monitor Information dialogue window will be displayed. Click on the OK button to return to the Rx EDI Status window. 20. Click on the Refresh button to update the displayed status field.
Appendix C: Intergy Technical Process Reference Testing the Update To test the RxDUR installation, open the Sage Intergy Client and log on as the support user. Click on the Clinical menu, open the Rx menu and select the New Prescription menu item. For more information on the use of prescription capabilities in Sage Intergy, refer to the Sage Intergy help file topic titled ‘RXS’. In a Windows environment, you may delete the C:\Intergy\DurLocation\rxdbsold directory after a successful test.
Appendix C: Intergy Technical Process Reference Important note: It is necessary to distinguish between the RMS Host ID and the Site ID. Both are numeric values and may appear very similar, but they are not the same number. The Site ID is assigned and created when serialization is purchased and a Sage Intergy license is issued. The Site ID refers generally to all the server and workstation devices located at a customer site.
Appendix C: Intergy Technical Process Reference The Host ID dialogue is displayed. Enter the new Host ID number and click on the Next button to proceed to the next step. A completion window will be displayed. Click on the Finish button to exit the RMS maintenance. Instructions for manual RMS setup do not apply to RMS installation on workstations. RMS is installed using the Sage Intergy Primer Utility or manually from the command prompt using the rmss.exe executable.
Appendix C: Intergy Technical Process Reference From any workstation or server in the customer environment that has Internet access, log on to the RMS website using the URL http://rms.emdeonps.com and access the customer record for the Sage Intergy site. Note the Edit link in the upper right corner. Click on this link to view all devices installed at this customer site and access configurable fields for RMS data. 14 - 22 Sage Intergy 7.
Appendix C: Intergy Technical Process Reference At the right side of the Sage Intergy Host header, click on the Edit button to change RMS registration data for the Sage Intergy server that has been added to the database. The update host window is displayed. Note the Host Type field on the third line. Click on the drop-down button to select from a list of available host types. In most cases, a new server will be identified only as a Production server or as a Sage Intergy On Demand (IOD) server.
Appendix C: Intergy Technical Process Reference Change the settings in the Client Configuration Utility using following parameters: • Advanced Settings: All Workstation Users Share Registry Settings - Select this checkbox. • Support Settings: Tech Support - Select this checkbox. Click on the Save Settings buton and then close the Client Configuration Utility. Activation occurs immediately, and no reboot is required.
Appendix C: Intergy Technical Process Reference Client Connection Configuration Currently, Sage Intergy uses a combination of text files and registry settings to configure client connection parameters for Sage Intergy and Sage Intergy EHR. Beginning with Sage Intergy 7.00, client connection parameters are also enumerated in XML files located in the following client workstation or terminal server directory: C:\Intergy\Config For Sage Intergy 7.00, the ‘connections.
Appendix C: Intergy Technical Process Reference
Appendix D: Sage Intergy Upgrade Appendix D: Sage Intergy Upgrade When upgrading Sage Intergy customer sites from a previous version of Sage Intergy, technicians may choose to peform an automated upgrade or a manual upgrade. This section provides a detailed overview of the requirements for both types of installation, and the steps that must be completed to upgrade clients and servers to Sage Intergy 7.00. Windows Sage Intergy Server Upgrade . . . . . . . . . . . . . . . .
Appendix D: Sage Intergy Upgrade Windows Sage Intergy Server Upgrade An established customer site with an existing Sage Intergy installation on Windows servers may be upgraded to the current application version. The current version of Sage Intergy automates many upgrade processes, so that installation and reboots may occur during offhours or during a scheduled time. The Sage Intergy Primer Utility that prepares a customer site for an upgrade is also included on the latest Sage Intergy installation media.
Appendix D: Sage Intergy Upgrade AdminService Authentication Utility The AdminService Authentication Utility performs the following functions: • Collects information about Progress Database security • Prompts the installer for logon information if the Local System account is not used to run the Progress Administrative Service • Stores authentication information in an encrypted file for use by the installation program during the automated upgrade The technician executing the utility will be prompted t
Appendix D: Sage Intergy Upgrade Note that you may be required to use Install Mode for Sage Intergy database servers that are also configured with Terminal Services for client connectivity. Open the Install Application on Terminal Server control panel and use this dialogue to run the default setup executable, instead of clicking on the file manually. Refer to Chapter 9 for detailed information on the installation of applications for Terminal Services client connectivity. Select Setup Option 2.
Appendix D: Sage Intergy Upgrade Set Sage Intergy Admin Service Logon When Upgrading from Sage Intergy 3.50 or Older 4. If you are upgrading from Sage Intergy 3.50 or earlier and the Sage Intergy Administrative Service uses a logon account, the AdminService Login prompt window will be displayed. This window is displayed because the Sage Intergy AdminService for Progress 9.1D does not use the Local System account.
Appendix D: Sage Intergy Upgrade Progress Application Component Installation 7. The Removing Old Progress Software status message will be displayed. After a few minutes the Progress Software installation wizard window is displayed. 8. After a few minutes, several new windows will be displayed as the Progress OpenEdge installation process begins. The installation status window will change as installation progresses. Note that there is an interactive button displayed underneath the status window.
Appendix D: Sage Intergy Upgrade and all installed components. Always allow the Progress installation package to complete before taking any action against the server, and warn any customer representatives or technical support personnel of this issue as necessary. 9. For most installations, the windows that were displayed in step 8 will appear to be repeated. This may occur if additional Progress OpenEdge service packs or other software updates must be installed.
Appendix D: Sage Intergy Upgrade 13. The Sage Intergy Database Upgrade status window is displayed. The text displayed will change as the database schema is extended and modified. 14. The ODSTools setup window related to the Medcin Sage Intergy component will be displayed. At the end of this process, the Medcin configuration window will be displayed very briefly. No input is required at this point, and the window will close by itself. Other Component Installation Upgrade 15.
Appendix D: Sage Intergy Upgrade progress, the new Sage Intergy Storage Server splash screen with the current installation will be displayed. Again, do not cancel the installation and allow it to proceed. Upgrade Completion 16. Another series of status message will be displayed, depending on the components which are already installed. You may observe messages relating to Sage Intergy Interop, Practice Portal, and the updating of client components.
Appendix D: Sage Intergy Upgrade 17. When complete, the Sage Intergy Update confirmation window appears, asking you to reboot. Click on the Finish button and allow the server to reboot. If the Sage Intergy database server is configured as a Terminal Server, the reboot will also end install mode and place the server in normal operation mode again. Check Database and Windows Logs after Reboot 18. After the reboot has completed successfully, log on to the database server as the local administrator.
Appendix D: Sage Intergy Upgrade the Sage Intergy Technical Process Reference in Appendix C for detailed instructions on applying a new serialization. Existing Client Upgrade Workstations which are already running a previous version of the Sage Intergy client components may be upgraded to the new version manually with media, or automatically using the RMS client functions. This applies to Windows XP, Windows Vista and Windows 7 workstations, and Windows workstations operating as DDS or TMS servers.
Appendix D: Sage Intergy Upgrade will be displayed. Select the ‘Upgrade Sage Intergy X.XX to Sage Intergy 7.00’ option and select Next to continue. 2. Several notification screens will be displayed. During the manual upgrade process, he Sage Intergy client upgrade will proceed with no prompts. If the Sage Intergy EHR client is installed, it will be detected and a separate upgrade wizard will be started automatically. 3.
Appendix D: Sage Intergy Upgrade Automatic Upgrade If the Sage Intergy Primer is been run on the workstation and the Sage Intergy database server has already been upgraded to version 7.00, the RMS client is already installed and configured correctly to receive an automated upgrade. When prerequisite conditions are met, clicking on the Sage Intergy icon on the client workstation will display the Upgrade Notification window. To upgrade the workstation, click on the Start Upgrade button.
Appendix D: Sage Intergy Upgrade N-tier Sage Intergy Server Upgrade Some servers in large Sage Intergy environments will not be upgraded as part of the automated procedure. This includes report servers in all environments, and stand alone application servers that are part of N-tier environments. These servers should always be upgraded using CD media, or from a network share that contains all the files included on the CD media.
Appendix D: Sage Intergy Upgrade Stand Alone Sage Intergy Storage Server Upgrade Some implementations of Sage Intergy Storage Server (ISS) are installed on hardware that is separate from the Sage Intergy database server. This scenario occurs most often for customer sites that have replaced an existing FileX imaging server. Stand alone ISS servers are not upgraded automatically when the Sage Intergy database server is upgraded to version 7.00.
Appendix D: Sage Intergy Upgrade 3. Insert the Sage Intergy 7.00 installation media, or connect to the shared folder used to install the Sage Intergy database server. Browse to the X:\StorageServer folder on this media and locate the Setup.exe file located in this directory. 4. To execute the new installation, open the Windows command prompt and execute the Setup.exe from this directory using the following arguments: setup.
Appendix E: Laboratory Information System Installation Appendix E: Laboratory Information System Installation The Lab Information Server (LIS) service supports the transmission of clinical data to a laboratory server that is installed at the customer site. This service is usually implemented in Sage Intergy environments that already include comprehensive or specialized laboratory services.
Appendix E: Laboratory Information System Installation Overview The Lab Information Server (LIS) service supports the transmission of clinical data to a laboratory server that is installed at the customer site. For smaller medical practices, laboratory services are usually provided by a third party, such as LabCorp. When laboratory services are provided by a third party in this manner, the LIS service does not need to be installed.
Appendix E: Laboratory Information System Installation Service Verification After successful installation of the LIS service on the Sage Intergy database server or application server, it may be necessary to verify that the service is appropriately configured. Open the Windows server manager console and view the list of installed services. Verify that the Intergy Laboratory Information Service item in the list is set to automatically start.
Appendix E: Laboratory Information System Installation Sage Intergy System Configuration Some Sage Intergy customer sites may require LIS settings to be customized in order to match the configuration of their third-party laboratory systems. Open the System Administration window and access the System Configuration settings. Click on the Labs item in the left pane to display LIS configuration options.
Appendix F: Multiple Database Installation Appendix F: Multiple Database Installation Some customer environments may require installation of more than one database. Installation of multiple databases on a single server is not supported, but it is possible to implement a Sage Intergy environment with more than one database each on its own server.
Appendix F: Multiple Database Installation Typical Installation Settings The following table lists typical installation settings used for multiple Sage Intergy database installations in most environments. However, many settings may have to be changed to suit specific customer requirements or to conform to the standards of an existing computing environment. Use this table as a reference if you are already familiar with the details of installation.
Appendix F: Multiple Database Installation Overview Installation of more than one database server in a Sage Intergy environment is relatively uncommon, but may occur for one of several reasons. a Sage Intergy customer may have a requirement for a Sage Intergy installation that is separate from an active production database, for training or development purposes.
Appendix F: Multiple Database Installation Sequence of Installation At a high level, you will follow these steps to install a multiple database Sage Intergy environment: • Install Sage Intergy database servers and supporting servers using the normal process. • Install workstation clients using the normal process with a default configuration.
Appendix F: Multiple Database Installation Install and Configure Sage Intergy Client The standard Sage Intergy client may be configured to connect more than one database. Usage of the Client Configuration Utility permits the creation of connection profiles, which may be activated by use of the Sage Intergy System Selector. Note that these instructions do not apply to Sage Intergy EHR clients or management tools.
Appendix F: Multiple Database Installation have the name ‘Intergy’ and will include only the connection parameters specified during installation of the Sage Intergy client. 3. Click on the New button to make a new configuration profile. The first time any action is taken in the Client Configuration Utility, a confirmation window is displayed. Enter the password ‘Intergy’ with no quotes, and click on the OK button to proceed to the next step. Note that this password is not case-sensitive.
Appendix F: Multiple Database Installation 4. The new Sage Intergy Configuration window is displayed. For each Sage Intergy database configuration profile, enter these four values: • Configuration Name - Enter a meaningful name to identify the specific Sage Intergy environment for which this configuration is created. For example, ‘Sage Intergy Training’ might be used to distinguish a training environment. • Database name - This value should always be set to ‘Medman’ with no quotes.
Appendix F: Multiple Database Installation 6. After the last configuration is entered, you will return to the main Client Configuration Utility window. Note that in the drop-down list, the default Sage Intergy configuration is still listed, and the new configurations just entered are now also listed. 7. Select the default ‘Intergy’ configuration profile from the drop-down list in the Client Configuration Utility.
Appendix F: Multiple Database Installation drop-down list and click on the Test DB Connection button to test the connection. A series of message will be displayed to indicate success or failure of the connection test. If any profile indicates a connection failure, use the radio buttons in the upper right corner of the Client Configuration Utility window to select each configuration parameter tab.
Appendix F: Multiple Database Installation the Start menu or Sage Intergy folder. Instead of the Sage Intergy Desktop logon prompt, the System Selector window will be displayed. 11. Verify that all profiles configured in the previous steps are displayed in the System Selector list. Click on any profile and click on the Select button to open the Sage Intergy Desktop for that database server. The Sage Intergy desktop will be displayed.
Appendix F: Multiple Database Installation When configuring a WAN client, note the additional configuration parameters in the Client Configuration Utility. Click on the Miscellaneous radio button to display the miscellaneous client configuration parameters and note the WAN Client checkbox. Make sure this checkbox is selected for WAN clients that are configured for multiple database environments. Click on the Save Settings button to save this configuration.
Appendix F: Multiple Database Installation Do not use the Save Settings to Network function of the Client Configuration Utility. Management and maintenance functions Sage Intergy client configuration profiles are not yet implemented. Improper use of this menu option will disable Sage Intergy client connectivity and require manual configuration or reinstallation.
Appendix G: Cardio Service Installation Appendix G: Cardio Service Installation The Sage Intergy Cardio service supports the operation of a Heart Centrix ECG device for automated data entry into IEHR. For this specific service, installation of the third-party Heart Centrix application is provided by Cardiac Science corporation technicians. However, it will be the responsibility of the Sage technician to configure additional hardware and provide required configuration information.
Appendix G: Cardio Service Installation Overview The Cardio service is a Sage Intergy service that is normally installed when IEHR is configured to receive patient data from a Heart Centrix ECG device. This service provides a web authentication component on a custom TCP port. To support operation of the ECG hardware, the Heart Centrix server and client components must also be installed in the customer environment.
Appendix G: Cardio Service Installation installation script. In a typical Sage Intergy installation, this installation script is found in the C:\Intergy\Code\Shared\Support\NTServices directory. Execute this file from the command line, or open Windows Explorer and browse to this location and double-click on the ‘IntergyCardioSvc.bat’ file. Run this script only on the primary Sage Intergy database server and not on any Sage Intergy workstation or other application server.
Appendix G: Cardio Service Installation Sage Intergy system information During installation of Heart Centrix, the Cardiac Science technician will be prompted to enter information about the Sage Intergy database server and customer environment. Prepare the following information before installation occurs: • Practice ID - The Practice ID is the unique identifier used by EDI billing systems and other third parties to distinguish the Sage customer from other practices.
Appendix G: Cardio Service Installation Internet Connectivity for Sage Intergy On Demand In some cases, a Heart Centrix server and a Sage Intergy system are installed on different local area networks, and must communicate using the public Internet. This type of implmentation is typically required when the Cardio service is installed for use with Sage Intergy on Demand. If you are not installing the Cardio service for use with Sage Intergy on Demand, skip to page 18-10 to configure backup options.
Appendix G: Cardio Service Installation Several sets of bidirectional secure tunnels must be configured, one each for the Ultia connection port, web browser connectivity, and secure web browser connections. Use the following tables as a reference to configure a standardized set of tunnels. Make sure that you have applied the correct configuration type on the appropriate server for each tunnel that is configured. Use the following settings for configuration of the MIST service on the Heart Centrix server.
Appendix G: Cardio Service Installation Use the following settings for configuration of the MIST service on the Sage Intergy server. Configuration Parameter Source Tunnel Destination Tunnel Ultia Communication tunnel Name UltiaSourceEHR UltiaDestEHR Local Address “Any” “Any” Local Port 26100 26100 Remote Address Internet-facing address of Sage Intergy server 127.0.0.
Appendix G: Cardio Service Installation Modify Sage Intergy EHR Connectivity Settings In a normal installation, the Sage Intergy Cardio service is configured to connect to the Heart Centrix server directly on the same LAN. When used with Sage Intergy On Demand, the Ultia JDF configuration file must be manually edited to reflect a connection made to the localhost. In a typical installation, this file may be found in the following location: C:\Intergy\Ultia\Properties\ultiajdf.
Appendix G: Cardio Service Installation Modify Heart Centrix ECG Management Configuration Options In a normal installation, Heart Centrix server application options are automatically configured during initial installation, as described on page 18-3. It may be necessary to seek assistance from the Cardiac Science technicians who have performed this installation to modify the configuration of the Heart Centrix application to support operation with Sage Intergy on Demand.
Appendix G: Cardio Service Installation Configuring Backup Because the Sage Intergy Cardio service is installed on hardware separate from the Sage Intergy database server, the application files are not included in the main Sage Intergy backup process. This section describes the options available to Sage technicians for including the Heart Centrix server in the backup process for Sage Intergy customer site implementations.
Appendix G: Cardio Service Installation Installation of the Remote Agent from the Sage Intergy database server is known as a push installation. Select this option from the Local Administration Server interface of Backup Exec on the Sage Intergy database server. For detailed instructions on push installation, refer to the Symantec product documentation at the following URL: http://seer.support.veritas.com/docs/274163.
Appendix G: Cardio Service Installation Installation Configuration A new backup job must be configured to retain data from the Heart Centrix server. This job is separated from the main Sage Intergy database server backup for ease of troubleshooting errors and failures. Follow these numbered steps to configure a new backup job for the Heart Centrix server. After successful installation, open the Backup Exec Administration console and configure the scheduled backup jobs. 6.
Appendix G: Cardio Service Installation Scroll to the bottom of the backup selections list and select the following directories from the Heart Centrix server resource item: • C:\Program Files\Cardiac Science\HeartCentrix • C:\Program Files\Cardiac Science\HeartCentrixBackup Click on the Next button to proceed to the next step. 8. A series of prompts will be displayed to validate server logon credentials entered during initial installation, and to confirm the backup resource selections.
Appendix G: Cardio Service Installation 11. The Overwrite Method window is displayed. Change the selected radio button so that the ‘Append to media, overwrite if no appendable media is available’ option is selected, and click on Next to continue. 12. The Backup Options window is displayed. Select ‘Full - Backup Files - Reset Archive Bit’ for the backup type and click in the ‘Yes, Verify after backup’ radio button to select these options. Click on Next to continue. 18 - 14 Sage Intergy 7.
Appendix G: Cardio Service Installation 13. The Completion Notification window is displayed. Select ‘No, schedule the job’ to process the job as a scheduled item instead of running it now, and click on the Finish button to proceed to the next step. 14. The Backup Job scheduler is automatically started after the Backup Wizard is closed. Use the process described on page 12-14 to schedule a new separate time for the Heart Centrix backup.
Appendix G: Cardio Service Installation Schedule a new separate time for the Heart Centrix backup. As a best practice, schedule this backup to occur at time that does not overlap with the other backup operations in the customer environment, including the Sage Intergy database server backup. For detailed information on the administration and installation of CA Arcserve, refer to the vendor documentation at the following URL: https://support.ca.com/cadocs/0/c010891e.
Appendix H: Physician Portal Service Appendix H: Physician Portal Service The Physician Portal service allows Sage Intergy customer sites to receive referrals from other medical providers, and to communicate the status or results of referrals back to medical providers. This service makes use of a web-based connectivity between separately installed software systems.
Appendix H: Physician Portal Service Overview The Physician Portal service may be used by Sage Intergy customers to receive referrals from other medical practices. Messages and data are exchanged between different systems to facilitate automation of the referral process. Installation of the Physician Portal service for Sage Intergy 7.00 systems requires the use of the Sage Intergy installation media. The Physician Portal service is installed on a Sage Intergy server and not on client workstations.
Appendix H: Physician Portal Service IIS Installation Internet Information Services (IIS) is a required Microsoft Windows operating system component for the Physician Portal service. This server role is not installed by default on Sage Intergy database servers implemented by Sage technicians and requires separate installation. Note that installation differs for Microsoft Windows Server 2003 and 2008.
Appendix H: Physician Portal Service Microsoft Windows Server 2003 installation Log on as the Administrator to the Sage Intergy database server and open the Add or Remove Programs control panel. Click on the Add/Remove Windows Components button to open the Windows Components Wizard. Select the ‘Application Server’ option and click the Details button to open the Application Server component selection window. When prompted, select the following additional installation options: • ASP.
Appendix H: Physician Portal Service Web Services Component Installation Installation of web services related to the Physician Portal is the same for both Microsoft Windows Server 2003 and Microsoft Windows Server 2008. All instructions assume that you are logged on as the administrator to the Sage Intergy database server. Automatic Installation The Physician Portal service is one of several installation options on the Sage Intergy 7.00 installation media.
Appendix H: Physician Portal Service 2. The Installshield Wizard prerequisite installation window is displayed. Click on the Install button to proceed with installation of .NET components. 3. A number of windows will be displayed to indicate the status of .NET 4.0 and ASP.NET component installation. No input is required during this step. 19 - 6 Sage Intergy 7.
Appendix H: Physician Portal Service 4. After installation of .NET components is completed, the Web Services Installshield Wizard prompt is displayed. Click Next to proceed with installation. 5. A license agreement prompt is displayed. Select the appropriate radio button to accept the license agreement and then click on the Next button to proceed to the next step. 6. The Customer Information prompt is displayed.
Appendix H: Physician Portal Service 7. The Setup Type prompt is displayed. Select the ‘Custom’ radio button to customize installation options, and then click on the Next button to proceed to the next step. 8. The Custom Setup selection window is displayed. A number of different application features may be displayed in the list pane. Select only the ‘Referring Physician Portal’ application feature.
Appendix H: Physician Portal Service 11. The Installshield Completion window is displayed. Click on the Finish button to complete installation. You have successfully completed installation of Web Services application components. Proceed to the next section to complete activation of Physician Portal service user interface features. Sage Sage Intergy 7.
Appendix H: Physician Portal Service User Interface Activation After Physician Portal service components are installed, Physician Portal user interface components in the Sage Intergy desktop and administrative tools must be activated by running a Sage Intergy procedure file. To run this Procedure file, open the Intergy desktop folder or program group and then open the System Administration item. Log on using the ‘sysadm’ account and the appropriate password. The System Administration desktop is displayed.
Appendix H: Physician Portal Service Select the file TogglePhysicianPortal.r as shown below. Make sure that you select the “Procedure File” item in the Files of Type drop-down list. Click on Open to return to the Run Procedure dialogue box. Note that the full path and name of this procedure file are now listed in the Name text field. Click on the Run button to execute this file. A series of prompt windows will be displayed to indicate that the procedure is making changes to the database server.
Appendix H: Physician Portal Service Verify Installation To verify correct operation of the Physician Portal service, open a web browser on the Sage Intergy database server and browse to the following URL: http://localhost/AuthenticationWebService/AuthenticationService.asmx When correctly installed, the Physician Portal service authentication options page will be displayed. As a best practice, also check connectivity to the web page from the Internet.
Appendix H: Physician Portal Service • Internet-facing IP address or hostname. • The URL suffix to be used to identify the unique portal connection. • The IP address of the Sage server to be used for provisioning tasks. Use the following procedure to complete hosted server provisioning. 1. Log on to a workstation or server on the Sage corporate network. You may use the Sage VPN to make this connection. 2.
Appendix H: Physician Portal Service • Site Name - Enter the full name of the customer for which Physician Portal is being created. This name should be used to differentiate between separate customer sites or practices. • Host - The numeric IP address or fully-qualified domain name of the customer site should be entered in this field. This is the Internet-facing address for which secure web traffic on port 443 is forwarded to the Sage Intergy database server.
