©CSA (ISD) 2006
|
SCI Protocol Verification Tool
©CSA (ISD) 2006 |
Version: 16.0 |
The following are pre-requisites before installing, configuring and using the SCI Protocol Verification Tool (PVT).
The SCI PVT has been designed to run on both stand-alone Microsoft Windows machines and where a separate Microsoft Web Server is available. Where the application is to be used on a stand-alone machine, a local installation of a Microsoft Web Server is required. For users running Windows 98, use Microsoft's Personal Web Server (PWS). For users running Windows NT or 2000, use Microsoft's IIS (Internet Information Server) 4 (WinNT option pack) or IIS 5 (Windows 2000). All users need to be running Microsoft Internet Explorer v6 browser or higher to use the SCI PVT.
The SCI PVT uses XML technology provided by Microsoft. For your convenience, this can be downloaded here: Microsoft XML Parser v4 SP2 .
The SCI PVT uses Windows scripting technology to load and save files within the configured working directory for the application.
Note. Many Windows installations will already have this component, but you can download it from
Microsoft Windows Scripting v5.6
.
d) Microsoft .NET Framework Version 2.0
The SCI PVT uses the .NET Framework provided by Microsoft. For your convenience, this can be downloaded here: Microsoft .NET Framework Version 2.0
Use the following guidelines to install and configure the application depending on how it is to be used.
Install the application on the target machine by unzipping the zip file "protocol_verification_tool.zip". By default, the installation directory should be set to "c:\inetpub\wwwroot\protocol_verification_tool\", this can be changed if required. The web application files for the SCI PVT will be copied into this directory.
Create a virtual root, suggested name "Protocol_Verification", on the local Web Server (PWS or IIS) and configure this to point to the application installation directory. The configuration of the virtual root needs to allow 'Read' and 'Script' access (the application uses Microsoft's Active Server Pages technology). Set the default document for the virtual root to "default.asp" which is the entry page for the application.
Install the SCI PVT server components by executing the "prot_verification_tool.msi" file. By default, the installation directory is set to "C:\Program Files\SCI\Protocol Verification Tool\", this can be changed if required. Please select the 'Everyone' option as shown below before clicking 'Next'.
Once the installation wizard has finished, the components are ready for use.
NOTE: If the SCI PVT is to be used in conjunction with either GPASS or another third party application, then additional configuration steps are required to allow prepopulation of the protocol forms. These steps are outlined in steps 3 and 4 below.
To load the SCI PVT application, launch "default.asp" within the Internet Explorer browser. For example http://{localhost}/Protocol_Verification/default.asp, replacing {localhost} with the name of your machine.
The application uses a Microsoft ActiveX control to access the local hard disk. Ensure that the Security Settings within Internet Options for the "Local intranet" zone are set for "Download signed ActiveX controls" to either "Enable" or "Prompt".
The "Working Directory" is where protocol and stylesheet definitions are stored.
By default, the application looks for a directory "C:\My Documents\Protocols\" and "C:\My Documents\Stylesheets\",
but this can be changed if required. To default to a different directory, open
config.inc from the includes directory of the web site in notepad and edit the
following lines by specifying a different path:
Const PVT_CLIENT_PROTOCOL_PATH = "C:\My Documents\Protocols\"
Const PVT_CLIENT_STYLESHEET_PATH = "C:\My Documents\Protocols\"
The application will automatically search sub-directories for protocol XML
definitions which must named with the file extension "*.xml" and stylesheet files ending with "*.xslt" files
The application will write files to the "Working Directory" therefore ensure that the Windows user group "Everyone" has Write permissions to this directory.
Install the application on the target machine by unzipping the zip file "protocol_verification_tool.zip". By default, the installation directory should be set to "c:\inetpub\wwwroot\protocol_verification_tool\", this can be changed if required. The web application files for the SCI PVT will be copied into this directory. Install the application on the target machine by unzipping the zip file "protocol_verification_tool.zip". By default, the installation is set to "c:\inetpub\wwwroot\protocol_verification_tool\", this can be changed if required. The web application files for the SCI PVT will be copied into this directory.
Create a virtual root, suggested name "Protocol_Verification", on the Web Server and configure this to point to the application installation directory. The configuration of the virtual root needs to allow 'Read' and 'Script' access (the application uses Microsoft's Active Server Pages technology). Set the default document for the virtual root to "default.asp" which is the entry page for the application.
Install the SCI PVT server components by executing the "prot_verification_tool.msi" file. By default, the installation directory is set to "C:\Program Files\SCI\Protocol Verification Tool\", this can be changed if required. Please select the 'Everyone' option as shown below before clicking 'Next'.
Once the installation wizard has finished, the components are ready for use.
NOTE: If the SCI PVT is to be used in conjunction with either GPASS or another third party application, then additional configuration steps are required to allow prepopulation of the protocol forms. These steps are outlined in steps 3 and 4 below.
To load the SCI PVT application, launch "default.asp" within the Internet Explorer browser. For example http://{servername}/Protocol_Verification/default.asp, replacing {servername} with the name of the web server.
The application uses a Microsoft ActiveX control to access the local hard disk. Ensure that the Security Settings within Internet Options are set for "Download signed ActiveX controls" to either "Enable" or "Prompt". In most cases these will be for the "Local intranet" zone, but if you experience any difficulties please add your web server name to the Trusted Sites zone with the same security settings as above.
The "Working Directory" is where protocol definitions are stored. Where a separate Web Server is used, the working directory must be accessible by both the Web Server AND the user's local machine. In most cases this is best achieved using a mapped drive. Use the radio buttons to show/hide a second working directory configuration box.
The first "Working Directory" must be the path from the user's machine to the shared directory. The second directory, the "Server's path to working directory" must be the path from the Web Server to the same shared directory. The application will write files to the "Working Directory" therefore ensure that the Windows user group "Everyone" on the Web Server has Write permissions to this directory.
Back to the main page.
In order to have the screen prepopulate from GPASS in the SCI PVT, you must insert a hyperlink into: C:\Program Files\SCI\Gateway
Client\default.html which is part of the
SCI Gateway Client install. Make sure that the link you insert contains
the "?gpassaction=referral" query string, as this initialises the Gateway
Consulting Room Extension, for prepopulation, like this:
<a href= "http://{servername[or]localhost}/protocol_verification/default.asp?gpassaction=referral">Protocol Verification Tool</a>
Once this has been configured, it is possible to pre-populate patient information into the SCI PVT. Steps to achieve this would be:
Note: The GPASS Configuration needs to include the Referral Provider "SCI Hospital" entry. To check the list of Referral Providers:
Click on the Referrals tab to display the screen shown in the image below
If SCI Hospital is not in the Referral Providers list then click on Add, and enter the details as in image below. Clicking on OK will add the SCI Hospital to the Referral Providers list.
4) Third Party Application (Non-GPASS) pre-population Configuration
In order to have the screen pre-populate from a Third Party Application in the SCI PVT the following steps have to be taken:
a) Install the Third Party Application according to the manufactures instructions
b) Run regedit.exe and navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\SCI\GWLogon
The two string values within this key should be altered to reflect the urls of the SCI PVT and the Third Party Interface.
The first of these values, URL, should be set
to the URL of the installed SCI PVT.
e.g. "http://{servername}/Protocol_Verification/" , replacing
{servername} with the name of the web server followed by the virtual directory
assigned to the SCI PVT.
NOTE: Do not include the inverted commas and be sure to attach
the trailing forward slash at the end of the URL string.
The second of these values, WebServicesURL, should be set to the url of the Third Party Interface.
e.g. "http://{servername}/Protocol_Verification/thirdpartyinterface/services/thirdpartyinterface.asmx", replacing {servername} with the name of the web server followed by the virtual directory assigned to the SCI PVT
NOTE: Do not include the inverted commas.
The registry entries will look similar to the following:
c) The "ThirdPartyInterface" folder should be configured as an application from within IIS Management Console.
- Open the IIS Management Console
- Expand the virtual directory that has been assigned to the SCI PVT
- Right click on the "ThirdPartyInterface" folder and select "Properties"
- In the "Directory" tab click on the "Create" button in the "Application Settings"
- Click on "OK" to exit the property page.
- The "ThirdPartyApplication" folder will now be configured as an application.
d) The permissions on the physical folder corresponing to the virtual "ThirdPartyInterface" folder must be changed.
- Using Explorer, navigate to the SCI PVT web files on the web server. (The place they were unzipped too.)
- Locate the "ThirdpartyInterfaceFolder", right click it and select "Properties"
- Select the "Security" tab
- Add the following users and give them full controll to the folder
- IUSR_<computername>
- IWAM_<computername>
- Everyone
e) As the .Net framework needs access to the Windows "Temp" folder during application execution the following permissions have to be applied to that folder:
- Locate the "Temp" folder using Explorer. It will either be in the "Winnt" folder or the "Windows" folder depending on the operating system
- Right click the "Temp" folder and select "Properties"
- Select the "Security" tab
- Add the following users and give them "Read" and "Write" permissions
- IUSR_<computername>
- IWAM_<computername>
f) Third Party Application prepopulation configuration is complete.