Difference between revisions of "CPRS Configuration - Adding an executable to the Tools Menu"
DavidWhitten (talk | contribs) |
Perspectoff (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | Adding an Executable to the CPRS Tools Menu | + | == Adding an Executable to the CPRS Tools Menu == |
| − | + | In these examples, the Microsoft Windows Executable (program) that will be added is called ''exampleprogram.exe''. | |
| − | + | *Decide whether to copy the ''exampleprogram.exe'' to a folder either on a shared network resource or on each user's workstation. | |
1.1 When adequate network bandwidth is available, when the server/shared resource is a fast enough machine, when the executable does not need to be installed with a specialized install program on a local machine, and when the executable does not support a "GOLD COPY" update process, installation to a shared resource is generally recommended. | 1.1 When adequate network bandwidth is available, when the server/shared resource is a fast enough machine, when the executable does not need to be installed with a specialized install program on a local machine, and when the executable does not support a "GOLD COPY" update process, installation to a shared resource is generally recommended. | ||
| Line 10: | Line 10: | ||
You should be careful to follow the plan that your organization has established for naming computers and shares on those machines, as it will make maintenance simpler. If it has been decided to not run a Microsoft Windows operating system on the server, it is still important that SAMBA or some other network file system will work properly with the client machine's operating system. | You should be careful to follow the plan that your organization has established for naming computers and shares on those machines, as it will make maintenance simpler. If it has been decided to not run a Microsoft Windows operating system on the server, it is still important that SAMBA or some other network file system will work properly with the client machine's operating system. | ||
| − | 1.3 Ensure proper folder- or share-level permissions are applied to allow access for the users of | + | 1.3 Ensure proper folder- or share-level permissions are applied to allow access for the users of ''exampleprogram.exe''. |
1.4 For the sake of this document, a share name of VistA is assumed. If the file is placed in a shared location, the UNC path to that location can be used in the setup below. If placed on each workstation, the local path to that location must be used. | 1.4 For the sake of this document, a share name of VistA is assumed. If the file is placed in a shared location, the UNC path to that location can be used in the setup below. If placed on each workstation, the local path to that location must be used. | ||
| Line 58: | Line 58: | ||
Select Sequence: 1 if none exist or 1 greater than the highest number | Select Sequence: 1 if none exist or 1 greater than the highest number | ||
Name=Command: | Name=Command: | ||
| − | ToolMenuText="\\servername\sharename\ | + | ToolMenuText="\\servername\sharename\''exampleprogram.exe''" DFN=%DFN DUZ=%DUZ |
Optionally, you may append (after adding a space) s=server name and p=port number. | Optionally, you may append (after adding a space) s=server name and p=port number. | ||
Revision as of 01:05, 26 February 2010
Adding an Executable to the CPRS Tools Menu
In these examples, the Microsoft Windows Executable (program) that will be added is called exampleprogram.exe.
- Decide whether to copy the exampleprogram.exe to a folder either on a shared network resource or on each user's workstation.
1.1 When adequate network bandwidth is available, when the server/shared resource is a fast enough machine, when the executable does not need to be installed with a specialized install program on a local machine, and when the executable does not support a "GOLD COPY" update process, installation to a shared resource is generally recommended.
1.2 If the executable is to be stored on a server/shared resource, a server-based folder and corresponding share name would need to be created. You should be careful to follow the plan that your organization has established for naming computers and shares on those machines, as it will make maintenance simpler. If it has been decided to not run a Microsoft Windows operating system on the server, it is still important that SAMBA or some other network file system will work properly with the client machine's operating system.
1.3 Ensure proper folder- or share-level permissions are applied to allow access for the users of exampleprogram.exe.
1.4 For the sake of this document, a share name of VistA is assumed. If the file is placed in a shared location, the UNC path to that location can be used in the setup below. If placed on each workstation, the local path to that location must be used.
2. From the [OR PARAM COORDINATOR] menu select the option named "GUI Parameters"
3. From this option select: GUI TOOL MENU ITEMS
CPRS GUI Tools Menu may be set for the following:
| 1 | User | USR | [choose from NEW PERSON] |
| 2 | Location | LOC | [choose from HOSPITAL LOCATION] |
| 2.5 | Service | SRV | [choose from SERVICE/SECTION] |
| 3 | Division | DIV | [choose from INSTITUTION] |
| 4 | System | SYS | (will vary by site) |
| 9 | Package | PKG | [REMOTE ORDER ENTRY SYSTEM] |
Determine which scope selection is appropriate based on the facility's established practice(s) regarding management of the Tools menu. Ensure that the any options assocated with the executable are added at the proper level of granularity to make the option available to all identified individual users.
Enter selection: # of your choice Make your choice from the selected file: Select Sequence: 1 if none exist or 1 greater than the highest number Name=Command: ToolMenuText="\\servername\sharename\exampleprogram.exe" DFN=%DFN DUZ=%DUZ Optionally, you may append (after adding a space) s=server name and p=port number.
4. Re-enter the CPRS menu to verify that the applications appear on the tools list.
5. See the CPRS Technical Manual if further instructions are desired.
This process is similar to the installation instructions for all other RPC Broker-enabled applications, such as CPRS, BCMA, CAPRI and PCMM.
