[NOTE: This document addresses a previous release of OVID. It is recommended that you redirect to https://medsphere.org/docs/DOC-1719 for installing a more recent version of OVID]
- Install the attached KIDS builds
- Download the attached MSCRES and MSCFM KID files to you local directory. (e.g. /tmp).
- Install both as follows:
$ mumps -dir
GTM>D ^XUP
Setting up programmer environment
Identity = MAN,SYS MANAGER,SYSTEM pb SYSTEM MANAGER
Terminal Type set to: C-VT102
You have 24 new messages.
Select MENU OPTION: EVE// Systems Manager Menu
WARNING -- TASK MANAGER DOESN'T SEEM TO BE RUNNING!!!!
Core Applications ...
Device Management ...
Menu Management ...
Programmer Options ...
Operations Management ...
Spool Management ...
Information Security Officer Menu ...
Taskman Management ...
User Management ...
FM VA FileMan ...
MM Manage Mailman ...
Application Utilities ...
Capacity Planning ...
HL7 Main Menu ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Systems Manager Menu Option: Programmer Options
KIDS Kernel Installation & Distribution System ...
PG Programmer mode
Delete Unreferenced Options
Error Processing ...
Global Block Count
Routine Tools ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Programmer Options Option: KIDS Kernel Installation & Distribution Syste
m
Edits and Distribution ...
Utilities ...
Installation ...
Patch Monitor Main Menu ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Kernel Installation & Distribution System Option: Installation
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
2 Run XINDEX against a Distribution
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Installation Option: 1 Load a Distribution
Enter a Host File: /tmp/MSCRES.1.1.KID
KIDS Distribution saved on Mar 30, 2009@18:22:12
Comment: update
This Distribution contains Transport Globals for the following Package(s):
MSC RES*1.0*1
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
MSC RES*1.0*1
Use INSTALL NAME: MSC RES*1.0*1 to install this Distribution.
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
2 Run XINDEX against a Distribution
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: MSC RES*1.0*1 Loaded from Distribution
4/1/09@09:54
=> update ;Created on Mar 30, 2009@18:22:12
This Distribution was loaded on Apr 01, 2009@09:54:33 with header of
update ;Created on Mar 30, 2009@18:22:12
It consisted of the following Install(s):
MSC RES*1.0*1
Checking Install for Package MSC RES*1.0*1
Install Questions for MSC RES*1.0*1
Want KIDS to INHIBIT LOGONs during the install? YES//
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//
Enter options you wish to mark as 'Out Of Order':
Enter protocols you wish to mark as 'Out Of Order':
Delay Install (Minutes): (0-60): 0//
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// TELNET
Install Started for MSC RES*1.0*1 :
Apr 01, 2009@09:54:58
Build Distribution Date: Mar 30, 2009
Installing Routines:
Apr 01, 2009@09:54:58
Updating Routine file...
Updating KIDS files...
MSC RES*1.0*1 Installed.
Apr 01, 2009@09:54:59
No link to PACKAGE file
NO Install Message sent
Install Completed
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
2 Run XINDEX against a Distribution
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Installation Option: 1 Load a Distribution
Enter a Host File: /tmp/MSCFM.1.1.KID
KIDS Distribution saved on Mar 30, 2009@18:22:51
Comment: update
This Distribution contains Transport Globals for the following Package(s):
MSCFM*1.0*1
Distribution OK!
Want to Continue with Load? YES//
Loading Distribution...
MSCFM*1.0*1
Use INSTALL NAME: MSCFM*1.0*1 to install this Distribution.
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
2 Run XINDEX against a Distribution
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Installation Option: 6 Install Package(s)
Select INSTALL NAME: MSCFM*1.0*1 Loaded from Distribution 4/1/09@09:55
=> update ;Created on Mar 30, 2009@18:22:51
This Distribution was loaded on Apr 01, 2009@09:55:10 with header of
update ;Created on Mar 30, 2009@18:22:51
It consisted of the following Install(s):
MSCFM*1.0*1
Checking Install for Package MSCFM*1.0*1
Install Questions for MSCFM*1.0*1
Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//
Want KIDS to INHIBIT LOGONs during the install? YES//
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//
Enter options you wish to mark as 'Out Of Order':
Enter protocols you wish to mark as 'Out Of Order':
Delay Install (Minutes): (0-60): 0//
Enter the Device you want to print the Install messages.
You can queue the install by enter a 'Q' at the device prompt.
Enter a '^' to abort the install.
DEVICE: HOME// TELNET
Install Started for MSCFM*1.0*1 :
Apr 01, 2009@09:55:26
Build Distribution Date: Mar 30, 2009
Installing Routines:
Apr 01, 2009@09:55:26
Installing PACKAGE COMPONENTS:
Installing REMOTE PROCEDURE
Installing OPTION
Apr 01, 2009@09:55:26
Updating Routine file...
Updating KIDS files...
MSCFM*1.0*1 Installed.
Apr 01, 2009@09:55:26
No link to PACKAGE file
NO Install Message sent
Call MENU rebuild
Starting Menu Rebuild: Apr 01, 2009@09:55:29
Collecting primary menus in the New Person file...
Primary menus found in the New Person file
------------------------------------------
OPTION NAME MENU TEXT # OF LAST LAST
USERS USED BUILT
EVE Systems Manager Menu 2 04/01/09 03/11/08
XMUSER MailMan Menu 8 05/09/08 03/11/08
FHDIET Clinical Dietetics 1 05/09/08 03/11/08
LRMENU Laboratory DHCP Menu 1 05/09/08 03/11/08
Building secondary menu trees....
Merging.... done.
Menu Rebuild Complete: Apr 01, 2009@09:55:33
Install Completed
1 Load a Distribution
2 Verify Checksums in Transport Global
3 Print Transport Global
4 Compare Transport Global to Current System
5 Backup a Transport Global
6 Install Package(s)
Restart Install of Package(s)
Unload a Distribution
2 Run XINDEX against a Distribution
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Installation Option:
Edits and Distribution ...
Utilities ...
Installation ...
Patch Monitor Main Menu ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Kernel Installation & Distribution System Option:
KIDS Kernel Installation & Distribution System ...
PG Programmer mode
Delete Unreferenced Options
Error Processing ...
Global Block Count
Routine Tools ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Programmer Options Option:
Core Applications ...
Device Management ...
Menu Management ...
Programmer Options ...
Operations Management ...
Spool Management ...
Information Security Officer Menu ...
Taskman Management ...
User Management ...
FM VA FileMan ...
MM Manage Mailman ...
Application Utilities ...
Capacity Planning ...
HL7 Main Menu ...
You have PENDING ALERTS
Enter "VA to jump to VIEW ALERTS option
Select Systems Manager Menu Option:
Do you really want to HALT? YES// yes YES
Halting at 09:55:43
GTM>halt
- Create an OVID user that has a non-expiring password and the MSC FM RESOURCE USER option.
$ mumps -dir
GTM>D P^DI
MSC FileMan 22.1030
Identity = MAN,SYS MANAGER,SYSTEM pb SYSTEM MANAGER
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
Input to what File: NEW PERSON// NEW PERSON (54 entries)
EDIT WHICH FIELD: ALL// .01 NAME
THEN EDIT FIELD: 7.2 VERIFY CODE never expires
THEN EDIT FIELD: 2.1 Want to edit ACCESS CODE (Y/N)
THEN EDIT FIELD: 11.1 Want to edit VERIFY CODE (Y/N)
THEN EDIT FIELD: 203 SECONDARY MENU OPTIONS (multiple)
EDIT WHICH SECONDARY MENU OPTIONS SUB-FIELD: ALL// .01 SECONDARY MENU OPTION
S
THEN EDIT SECONDARY MENU OPTIONS SUB-FIELD:
THEN EDIT FIELD:
Select NEW PERSON NAME: USER,OVID
Are you adding 'USER,OVID' as a new NEW PERSON (the 55TH)? No// Y (Yes)
Checking SOUNDEX for matches.
USER,MEDSPHERE TWELVE
USER,NURSE
USER,PHARMACIST
USER,LAB
USER,DIETITIAN
USER,RADIOLOGIST
USER,PT
USER,ANESTHESIA
USER,SURGEON
USER,PSYCHIATRIST
USER,SOCIAL
USER,PHYSICIAN
USER,MEDSPHERE TWENTY-FOUR
USER,MEDSPHERE TWENTY-FIVE
USER,MEDSPHERE TWENTY-SIX
USER,MEDSPHERE TWENTY-SEVEN
Press Return to Continue.
USER,MEDSPHERE TWENTY-EIGHT
USER,MEDSPHERE TWENTY-NINE
USER,MEDSPHERE THIRTY
USER,MEDSPHERE THIRTY-ONE
USER,MEDSPHERE THIRTY-TWO
USER,MEDSPHERE THIRTY-THREE
USER,MEDSPHERE THIRTY-FOUR
USER,MEDSPHERE THIRTY-FIVE
USER,MEDSPHERE THIRTY-SIX
USER,MEDSPHERE THIRTY-SEVEN
USER,MEDSPHERE THIRTY-EIGHT
USER,MEDSPHERE THIRTY-NINE
USER,MEDSPHERE FORTY
USER,MEDSPHERE FORTY-ONE
USER,MEDSPHERE FORTY-TWO
USER,MEDSPHERE FORTY-THREE
Press Return to Continue.
USER,MEDSPHERE FORTY-FOUR
USER,MEDSPHERE FORTY-FIVE
USER,MEDSPHERE FORTY-SIX
USER,MEDSPHERE FORTY-SEVEN
USER,MEDSPHERE FORTY-EIGHT
USER,MEDSPHERE FORTY-NINE
USER,MEDSPHERE FIFTY
USER,MEDSPHERE FIFTY-ONE
USER,MEDSPHERE FIFTY-TWO
Do you still want to add this entry: NO//YES
NEW PERSON INITIAL: OVU
NEW PERSON MAIL CODE:
VERIFY CODE never expires: Y Yes
Want to edit ACCESS CODE (Y/N): Y
Enter a new ACCESS CODE <Hidden>: OV1234
Please re-type the new code to show that I have it right: OV1234
OK, Access code has been changed!
The VERIFY CODE has been deleted as a security measure.
The user will have to enter a new one the next time they sign-on.
Want to edit VERIFY CODE (Y/N): Y
Enter a new VERIFY CODE: OV1234!!
Please re-type the new code to show that I have it right: OV1234!!
OK, Verify code has been changed!
Select SECONDARY MENU OPTIONS: MSC FM RESOURCE USER
Are you adding 'MSC FM RESOURCE USER' as
a new SECONDARY MENU OPTIONS (the 1ST for this NEW PERSON)? No// (No) ? Y (Yes)
Select SECONDARY MENU OPTIONS:
Select NEW PERSON NAME:
Select OPTION:
GTM>halt
- Next, VistaLink needs to be installed and running. On cache` systems, it is merely a matter of executing:
Cache> J LISTENER^XOBVTCLP(8002)
... where 8002 is the chosen port on which VistaLink will listen for connections.
However, on GT.M, there is a custom VistaLink listener that must be used instead. It is available from Sea Island Systems, Inc. Just following the instructions in the ReadMe.txt found here. If you are installing VistaLink for the first time, the following instructions, adapted from the ReadMe.txt should work:
Save xobv-gtm.ro to the current directory.
$ mumps -dir
GTM>D ^%RI
Routine Input Utility - Converts RO file to *.m files.
Formfeed delimited <No>?
Input device: <terminal>: xobv-gtm.ro
Modified VistALink Listener for GT.M
GT.M 02-APR-2004 11:52:42
Output directory :
XOBVLL XOBVRH XOBVSKT XOBVTCP XOBVTCPL
Restored 786 lines in 5 routines.
GTM>halt
$ mv XOBV*.m <your gtm routines directory>/development
$ mumps -dir
GTM>J LISTENER^XOBVTCPL(8002)
GTM>halt
$ lke show all
DEFAULT
^XOB(18.01,"VistALink Listener","DEMO","DEMO","DEMO:scilla",8002)
Owned by PID= 31543 which is an existing process
No locks were found in SCRATCH
- Test out the connection by:
- Unpack the ovid.tgz package, for example: tar xvf ovid.tgz
- Execute the get-patients.sh script (get-patients.bat on windows).
- when prompted, enter localhost for vistalink host, 8002 for port, OV1234 for access code and OV1234!! for verify code. Adjust input for any differences in your setup. You can supply the values on the command line as: sh get-patients.sh localhost 8002 OV1234 OV1234\!\!
- You should get output similar to:
sh get-patients.sh localhost 8002 OV1234 OV1234\!\!
patient: AYERS,ASHLEY
sex = FEMALE
dob = Wed Dec 08 17:00:07 CST 1999
eid = 1234567899
id = 1234567899
age = 9.0
display age = 9
room-bed = null
current room = null
attending = null
ward = null
current movement = null
current admission = null
admitting physician = null
admitting diagnosis = null
patient: BAKER,OLIVIA
sex = FEMALE
dob = Thu Mar 13 17:00:07 CST 1969
eid = 111112005
id = 111112005
age = 40.0
display age = 40
room-bed = null
current room = null
attending = null
ward = null
current movement = null
current admission = null
admitting physician = null
admitting diagnosis = null
patient: BENNING,GEORGE
sex = MALE
dob = Sat Aug 09 17:00:07 CDT 1930
eid = 111112013
id = 111112013
age = 78.0
display age = 78
room-bed = null
current room = null
attending = null
ward = null
current movement = null
current admission = null
admitting physician = null
admitting diagnosis = null
patient: BLANKENSHIP,BRAD
sex = MALE
dob = Thu Mar 17 17:00:07 CST 1960
eid = 456771321
id = 456771321
age = 49.0
display age = 49
room-bed = 4N403-1
current room = 4N403-1
attending = USER,MEDSPHERE TWENTY-NINE
ward = 4 NORTH - SURGERY
current movement = JUL 26,2006@13:59:57
current admission = 24
admitting physician = 29
admitting diagnosis = S/P TKA
......
If you get output like this, then the OVID OpenVista Server install is successful. Its recommended that you next install the demo web application and peruse the OVID sources. A good place to start would be the PatientRepository class, which produced the output above.
Note: VistaLink on GT.M is quite a bit slower than VistaLink on Cache` -- especially making connections, it seems. For this reason, we'll soon be refactoring the code to allow a choice between using RPCBroker or VistaLink Broker as the transport.
