$TXT by YAW,LINDA linda.yaw@vistaexpertise.net (KIDS) 2022-01-21t22:37z
Initial Data Import
SAMI (VAPALS-ELCAP) 18-x-16-t3
(SAMI*18.0*16 SEQ #16 T3)
George P. Lilly,
Domenic DiNatale,
Larry G. Carlson
& Frederick D. S. Marshall
2022-01-21
i. Front matter
App |
SAMI (VAPALS-ELCAP) |
Version |
18-x-16-t3 |
Vista ID |
SAMI*18.0*16 SEQ #16 T3: Version 18.0, Patch ID #16, Seq #16, Test 3 |
Priority |
High |
Categories |
Routine |
Status |
Test Patch: sami-18-x-16-t3.zip |
Depends on |
SAMI 18-1 (SAMI*18.0*1 SEQ #1) |
ii. Contents
1. Description
SAMI 18-x-16-t3 adds the ability to convert intake data from institutions that don’t currently use the VAPALS-ELCAP system but plan to start. There is also test code as a step towards adding the capability to match and merge duplicate patient records.
The definitive source for the VAPALS-ELCAP application—codebase, package distributions (including this patch), and documentation—is a public GitHub repository.
These instructions are for your Vista environment’s sysadmin. As usual, please capture the complete dialog of your install and send it to your VAPALS-ELCAP support team.
The following list shows changes for:
-
Conversion capability for .tsv files (high priority)
3. Prepare for installation
This involves creating a directory to work in, then going through steps to back up M routines that will be replaced by the patch.
3.1. Assume the identity of your osehra Unix user
This step assumes you use a dzdo or sudo command to do this; here, the symbol $DEMAND will stand for whichever command you use. (Also, in all the command-line examples below, $ simply means your command-line prompt.) If your configuration is different, please adjust this step to match your configuration:
$ $DEMAND su - osehra $ _
3.2. Prepare install directory
If this is your first time installling this, execute the following commands. They create a shell variable, and then creates the work directory and sets it as your current directory.
$ INDIR=~/run/in/sami/18-x-16/t3 $ mkdir -p $INDIR $ cd $INDIR $ _
If you’ve already tried installing this once, you can use the following commands instead:
$ INDIR=~/run/in/sami/18-x-16/t3
$ cd $INDIR
$ rm -rf ./sami*.{txt,kid}
$ _
3.3. Download and prepare the archive file
You may safely download the archive file (sami-18-x-16-t3.zip) in advance of the actual install. In the following text, [now] represents a time stamp representing your current time.
Then unzip the archive file with the following command.
3.4. Back up M routines
Before the installation, we also need to back up existing VAPALS-ELCAP routines that will be overwritten by this install. To do this, you will have to start a Caché or GT.M/YottaDB session (depending on your particular installation), sign in to Vista, and then call the direct-mode interface ^%RO (“routine out”).
We have made efforts to display accurate instructions, but there are likely to be minor differences between implementations. Be sure to follow the correct dialog for your implementation.
3.4.1. Enter M
At the Unix prompt, enter the M environment in direct mode, using the csession command on Caché or the mumps command on YottaDB/GT.M:
On Caché
$ csession vapals Node: vapalscache, Instance: VAPALS > _
On YottaDB/GT.M
$ mumps -dir > _
3.4.2. Sign into Vista
At the M prompt, call Vista’s direct-mode interface, enter your access code, and then just press return at the OPTION NAME prompt to return to direct mode. This sets up your authentication variables. Here’s a sample capture of this step:
> do ^XUP Setting up programmer environment This is a TEST account. Access Code: ******* Terminal Type set to: C-VT100 Select OPTION NAME: > _
3.4.3. List of routines
The routine names to save are listed below; you may copy the list and paste it at the appropriate Routine prompt. At the final Routine prompt, press return to indicate the list of routines is done.
3.4.4. Run the backup
Creating the routine backup file differs by implementation.
On Caché
Note that routines that don’t currently exist will result in a warning message (specifically, the routine name will have [???] after it, and the line [does not exist] after that). These messages can be safely disregarded.
In addition to naming the routines and routine-out file, we also provide a Description and press return at the Parameters and Printer Format prompts to accept the defaults of WNS and No, respectively:
On YottaDB/GT.M
Note that routines that don’t currently exist will result in the routine name not appearing under the input line, and won’t count towards the number of routines. These can be safely disregarded.
In addition to naming the routines and routine-out file, we also provide a Header Label and press return at the Strip comments prompt to accept the default of no:
You’ll remain in the M environment for the next section.
4. Main install instructions
This consists of loading, verifying and installing the KIDS package, and importing some test data for the new import feature.
4.1. Installing the KIDS package
This installs the various M assets required by the application.
4.1.1. Enter the KIDS Installation menu
At the OPTION NAME prompt select XPD MAIN to enter the Kernel Installation & Distribution System main menu, and at the Select ... Option prompt select Installation:
4.1.3. Install KIDS package
Select option 6, enter the space bar at the INSTALL NAME prompt, and press return at the next three prompts. Note that [now] denotes the current time when you’re doing the install.
You now have VAPALS-ELCAP 18-14-16-t2 (SAMI*18.0*16 SEQ #14 T2) installed in your M environment. The install is now complete. We recommend running tests of your VAPALS-ELCAP application to confirm the environment is operational and bug-free, before notifying users that VAPALS-ELCAP is ready for their use.
4.1.4. Testing and use
The VAPALS-ELCAP team has implemented a method of collecting data for patient intake forms at a site prior to the installation of the VAPALS-ELCAP software. In essence, it is a spreadsheet version of all the questions on the intake form. This patch includes new routines to support the import of this data.
For instructions on how to perform an import, see the Importing patient intake data to VAPALS-ELCAP document.
5. Optional backout instructions
Should errors or other problems result from installing this package, contact the VAPALS-ELCAP development team for package-backout instructions.
6. Routines
Lines 2 and 3 of each of these routines now look like:
The checksums below are Vista Type B checksums (do CHECK1^XTSUMBLD).
7. Authors
| Dates | By | |
|---|---|---|
Developed |
2021-10-20/2022-01-14 |
George P. Lilly (VEN) |
Tested |
2021-10-25/2022-01-14 |
George P. Lilly (VEN) |
Released |
2022-01-21 |
Frederick D. S. Marshall (VEN) |
$END TXT