NEC Medical Center System Operations Manual
Have a look at the manual NEC Medical Center System Operations Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1168 NEC manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
NDA-30026 Revision 6Page 19 Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION Application Configuration MCS is internally supported by the APM and must be configured in the APM environment. MCS uses an autoconfiguration utility program to automatically configure some MCS settings for the APM platform. This program utility runs upon installation. If the utility runs successfully, specific adjustments can be made to the application parameters, depending on site requirements. Note:If an error occurs during installation, you can try to run the autoconfig program again or you can enter the information into the APM manually using the information pro- vided in this chapter. After the autoconfiguration utility has run successfully, the initialization time settings for the database processing applications must now be configured. Configuring these settings is described in three steps ( on page 28, Step 9: Mcs_Recluster Control Options on page 30, Step 10: Mcs_Host_ Statistics Control Options on page 30) in the following pages. MCS is configured into the APM system using the Add command on the Application Configuration screen. To access the Application Configuration option, use the following steps: 1. Type the System Administrator password at the APM password screen. 2. Select the Application Configuration option from the System Administration menu. This section contains the data that should be entered to the configuration file for MCS. The following components must be configured: Monitor–Controls call parking and retrieval, restrictions, and DID number management. Server–Controls source caller data displayed on the attendant consoles, directory assistance, and beeper functions. You may need to set up more than one server, depending on the server ratio and the number of attendants. (Refer to the Server Ratio section in Database Requirements on page 32.) Recluster–Periodically reclusters Informix system tables for more efficient processing of the database. You must schedule this component under Control Options on the APM Operations Menu in order for it to function automatically. Host Statistics–Periodically creates a log that contains the count of records received from the Hospital Information System, including admissions, discharges, and transfers. All error transactions will appear in the log. You can display the log file from the Statistics option on the MCS Administration Menu (login: mcsadm).
Page 20NDA-30026 Revision 6 SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition Cleaner–Periodically cleans out any records of patients that have been discharged. It also makes available DID numbers that have been offered but not assigned to an admitted patient after a set amount of time. You must schedule this component under Control Options on the APM Operations Menu in order for it to function automatically. Java Services–Controls the Java graphical user interface between the host server and the Java client workstations. All component parameters are automatically configured at installation. For instructions on what these parameters mean and how to make these entries, refer to the APM Operations Manual. Step 1: Application CharacteristicsTo add MCS to the APM Application Configuration file, set up each of its components exactly as follows: Parameter Definitions: OAI Application–Whether (Yes or No) this component communicates with the NEAX2400 using OAI processes. CRT Application–Whether (Yes or No) this component runs on the same screen as the APM, rendering the APM temporarily inaccessible. Communication Queue–Whether (Yes or No) this non-OAI application needs an IPC queue to communicate with other processes. Parameter Monitor Server Cleaner ReclusterHost StatisticsJAVA Services OAI ApplicationYYNNNN CRT ApplicationNNNNNN Communication QueueNNNNNN
NDA-30026 Revision 6Page 21 Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION Step 2: Monitor ConfigurationPrimary Configuration Parameters On the APM Configuration Entry screen, make entries for each parameter shown below. The application name for the server is a derivation of the name configured in the Server Base Name field of the mcscfg database. For parameters shown with an asterisk (*) in the table below, make the entries exactly as shown. The other parameter entries are shown with sample entries that may be changed to meet site requirements. Parameter Definitions: Application Name–The name displayed in the APM menus. This name is displayed as it is entered here. You can use lowercase letters and punctuation but not spaces. Executable Filename*–The path name of the executable file. Group*–The group to which the component is tied. Response Mode*–The action that the APM is to take with the component if a member of the group terminates. Initialization Batch–Whether (Yes or No) the component is to be initialized automatically when the OAI system is initialized. Termination Mode*–How the APM is to notify the component to terminate. Standard Output–The file into which component output is redirected. Number of Restarts–How many times the APM may restart the component after it terminates in error. Facilities According to instructions in the APM Operations Manual, name the following NEAX2400 facilities for the designated components using the Facilities command on the APM Configuration Entry screen: FLF Free Location SMFN Status Notification (N) RCF Restriction Control SMFR Status Request (R) SCF Switch Control Parameter Monitor Application Name Mcs_Monitor Executable Filename* /oai/app/mcs/bin/mccdmn Group* MCS Response Mode* N(otify) Initialization Batch N(o) Termination Mode* M(essage) Standard Output /dev/null Number of Restarts *
Page 22NDA-30026 Revision 6 SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition Step 2: Monitor Configuration (Cont)OAI Configuration Use the OAI-Conf command on the APM Configuration Entry screen to make the necessary parameter entries. For parameters shown with an asterisk (*) in the table below, make entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. Use the instructions provided for this option in the APM Operations Manual: Parameter Entry Description Database Name #1* /oai/db/cur/McscfgThe path name of the database containing setup information. Database Name #2* /oai/db/cur/McsfileAll the directory and file names needed by the MCS. Timeout Value #1 10How many seconds to wait before trying to place a call again on an ANT. Timeout Value #2 5 Not Used Tenant Number 1Tenant for the conversation monitoring extension, attendant consoles, announcement and dictation trunks, and the parking monitored number. Source Link Name OAI1TCPPort on the source side of the communication link. Entry should match a link name in the APM system configuration file. Destination Link Name PBX1TCPPort on the destination side of the communication link. Entry should match a link name in the APM system configuration file. Association Recovery 40Number of seconds Mcs _Monitor waits before trying to reestablish an association with the NEAX that has been released.
NDA-30026 Revision 6Page 23 Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION Step 2: Monitor Configuration (Cont)User-Defined Parameters Make the additional parameter entries exactly as shown below through the UserDefined command on the OAI Configuration screen. User Defined # Entry Description 1 5Number of seconds to wait for a response from an attendant console before assuming that communication with it is not working. 2 600Number of seconds between handshakes between the monitor and the attendant consoles. 3 15Number of seconds that the attendant console has to respond to a handshake with the monitor before it is considered disabled. 4 600Number of seconds between checks of Server function by the monitor. 5 0#The operator to which all parked calls are recalled when the monitor is initialized. 6 5 Maximum number of Server restarts. 7 Priority access code used for multiple recall. 8 100Maximum number of records to be retrieved in any one database search. 9 37121Error code that is returned from the PBX indicating that the attendant is idle. Type 37125 for NEAX version J.4.02 or lower. Ty p e 37121 for NEAX version J.4.10 or higher. 10 37122On the MMG, the error code that is returned from the PBX indicating locked attendant memory. Leave this field blank for any other PBX version. 11 2Number of times MCS is to retry after receiving error code 37122.
Page 24NDA-30026 Revision 6 SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition Step 3: Server ConfigurationPrimary Configuration Parameters On the APM Configuration Entry screen, make entries for each parameter shown below. The application name for the server is a derivation of the name configured in the Server Base Name field of the mcscfg database. For parameters shown with an asterisk (*) in the table below, make the entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. For information on parameter definitions, see page 21. Facilities According to instructions in the APM Operations Manual, name the following NEAX2400 facilities for the designated components using the Facilities command on the APM Configuration Entry screen: SCF Switch Control SMFN Status Notification (N) SMFR Status Request (R) Parameter Server Application Name Mcs_Server1 Executable Filename* /oai/app/mcs/bin/mccsrv Group* MCS Response Mode* I(gnore) Initialization Batch N(o) Termination Mode* M(essage) Standard Output /dev/null Number of Restarts 0
NDA-30026 Revision 6Page 25 Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION Step 3: Server Configuration (Cont)OAI Configuration Use the OAI-Conf command on the APM Configuration Entry screen to make the necessary parameter entries. For parameters shown with an asterisk (*) in the table below, make entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. Use the instructions provided for this option in the APM Operations Manual: Parameter Entry Description Database Name #1* /oai/db/cur/mcscfgPath name of the database containing setup information. Database Name #2* /oai/db/cur/mcsfileAll the directory and file names needed by the MCS. Timeout Value #1 5Number of seconds to wait for a response from an attendant console before assuming that communication with it is not working. Timeout Value #2 60Number of seconds to wait before clearing lit LEDs after placing an emergency alert. Tenant Number 1Tenant for the conversation monitoring extension, attendant consoles, announcement and dictation trunks, and the parking monitored number. Source Link Name OAI1TCPPort on the source side of the communication link. Entry should match a link name in the APM system configuration file. Destination Link Name PBX1TCPPort on the destination side of the communication link. Entry should match a link name in the APM system configuration file. Association Recovery 40Number of seconds the monitor waits before trying to reestablish an association with the NEAX.
Page 26NDA-30026 Revision 6 SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition Step 3: Server Configuration (Cont)User-Defined Parameters Make the additional parameter entries exactly as shown below through the UserDefined command on the OAI Configuration screen. User Defined # Entry Description 1 Dictation trunk number for conversation monitoring. If no dictation trunk is to be used, leave this field blank. 2Mcs _Monitor Monitor component logical name. 3 10Call kind field that shows priority notification on the PBX. 4 3276 Number of the MCS shared memory key. 5 3276 Number of the MCS semaphore key. 6 If set to a value, this field enables the checking of a D term for do-not-disturb status prior to call routing. 7 3Enables MCS to process multiple recalls. Set to 3 for J.4.02 or earlier PBX firmware versions, 11 for later versions without multiple recall, or 19 for later versions with multiple recall. 8 37122On the MMG, the error code that is returned from the PBX indicating locked attendant memory. Leave this field blank for any other PBX version. 9 2Number of times MCS is to retry after receiving error code 37122. 10 /oai/app/mcs/ menus/ Mserver.cfgConfigured by MCS application
NDA-30026 Revision 6Page 27 Medical Center System Operations Manual - JAVA Edition SERVER INSTALLATION Step 4: Recluster Primary ConfigurationOn the APM Configuration Entry screen, make entries for each parameter shown below. The application name for the server is a derivation of the name configured in the Server Base Name field of the mcscfg database. For parameters shown with an asterisk (*) in the table below, make the entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. For information on parameter definitions, see page 21. Step 5: Host Statistics Primary ConfigurationOn the APM Configuration Entry screen, make entries for each parameter shown below. The application name for the server is a derivation of the name configured in the Server Base Name field of the mcscfg database. For parameters shown with an asterisk (*) in the table below, make the entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. Note:These parameters are initially configured by the MCS host interface. For information on parameter definitions, see page 21. Parameter Recluster Entry Application Name Mcs_ReclusterTables Executable Filename* /oai/app/mcs/etc/update Group* Response Mode* I(gnore) Initialization Batch N(o) Termination Mode* K(ill) Standard Output /dev/null Number of Restarts 0 Parameter Host Statistics_ Entry Application Name Mcs_Host_Statistics Executable Filename* /oai/app/mcs/host/bin/hoststats Group* Response Mode* I(gnore) Initialization Batch N(o) Termination Mode* K(ill) Standard Output /dev/null Number of Restarts 0
Page 28NDA-30026 Revision 6 SERVER INSTALLATION Medical Center System Operations Manual - JAVA Edition Step 6: Cleaner Primary ConfigurationOn the APM Configuration Entry screen, make entries for each parameter shown below. The application name for the server is a derivation of the name configured in the Server Base Name field of the mcscfg database. For parameters shown with an asterisk (*) in the table below, make the entries exactly as shown. The other parameters are shown with sample entries that may be changed to meet site requirements. For information on parameter definitions, see page 21. User-Defined Parameters Parameter Cleaner Entry Application Name Mcs_Dbclean Executable Filename* /oai/app/mcs/bin/dbclean Group* Response Mode* I(gnore) Initialization Batch N(o) Termination Mode* K(ill) Standard Output /dev/null Number of Restarts 0 User Defined # Entry Description 1 138 Discharge record release time in hours. (Records for discharged patients are removed from the database after the defined number of hours.) 2 72 DID number release time in minutes. (DID numbers for discharged patients are deleted from database after the defined number of minutes.)