How to Setup VistA/RPMS on a Docker Container

How to Setup VistA/RPMS on a Docker Container

This instruction is based on the Dockerized VistA instances instruction created by Christopher Edwards of KRM Associates, Inc. It is designed for installation of the OSEHRA VistA on a Docker container. Many thanks to Christopher Edwards for this open source contribution.

Prerequisites:

A working Docker installation on the platform of choice. On Windows, Docker requires Microsoft Windows 10 Professional or Enterprise 64-bit. See Docker installation instruction to verify that Docker is working properly.

FOIA VistA

FOIA VistA docker image is provided as is for people who want VistA completely unmodifed. If you download FOIA VistA, you are on your own for getting the VistA clients to connect and for getting the normal background processes (Taskman, Mailman) to start.

> docker run -p 9430:9430 -p 8001:8001 -p 2222:22 -d -P --name=foiavista osehra/foiavista

This will require several minutes before the system completes the setup. Type the following command to see if FOIA VistA container is running

> docker ps

You should see the following response:

CONTAINER ID       IMAGE               COMMAND                    CREATED             STATUS               PORTS                                                                              NAMES
ab7de0849700       osehra/foiavista    "/bin/sh -c /home/..."     16 hours ago      Up 16 hours         0.0.0.0:9430->9430/tcp, 0.0.0.0:2222->22/tcp, 0.0.0.0:8006->8001/tcp     foiavista

Docker Container User Accounts:

NOTE: by default ${instance} is osehra. The GT.M system runs under the “osehra” system account.

Linux User Name Password
root docker
osehratied tied
osehraprog prog

VistA User Accounts:

None.

Accessing VistA Using the CPRS, Vitals, and BCMA Demo Client Applications

You need to download the clients from http://foia-vista.osehra.org/.

Stop OSEHRA VistA Container

Exit from the OSEHRA session, and then from the shell type

> docker stop foiavista

Restart OSEHRA VistA Container

To start up the OSEHRA VistA, from the shell type

> docker start foiavista

Delete OSEHRA VistA Container

To remove the osehravista container, run this:

> docker rm foiavista

OSEHRA VistA

> docker run -p 9430:9430 -p 8001:8001 -p 2222:22 -d -P --name=osehravista osehra/osehravista

This will require several minutes before the system completes the setup. Type the following command to see if OSEHRA VistA container is running

> docker ps

You should see the following response:

CONTAINER ID      IMAGE             COMMAND             CREATED            STATUS              PORTS                                                        NAMES
6f26dfab803f        osehra/osehravista   "/bin/sh -c /home/..."   6 minutes ago           Up 6 minutes         0.0.0.0:8001->8001/tcp, 0.0.0.0:9430->9430/tcp, 0.0.0.0:2222->22/tcp   osehravista

Accessing VistA

The Docker container sets up the RPC broker, a TCPIP socket-based protocol, which is used for data exchange between VistA and clients such as CPRS, Vitals, and other GUIs. The container also sets up the SSH service to support the terminal-based Roll-and-Scroll UI. The container is accessable via the ip address=127.0.0.1 from the following ports:

  • 9430 - RPC Broker
  • 2222 - SSH

NOTE: CPRS uses the RPC Broker and the correct command line arguments are: S=127.0.0.1 P=9430

You can also access the container using SSH client such as PuTTY by using the address as described in the note above and using the correct port 2222 for container install.

Docker Container User Accounts:

There are two operation systems user accounts that are created automatically during the installation process that make accessing the VistA Roll-and-Scroll UI easier. The use of the accounts becomes clear when you use the Roll-and-Scroll UI in the later section below:

NOTE: by default ${instance} is osehra. The GT.M system runs under the “osehra” system account.

Linux User Name Password
root docker
osehratied tied
osehraprog prog

 

VistA User Accounts:

User Role Access Code Verify Code Electronic Signature
System Manger SM1234 SM1234!!! n/a
Doctor fakedoc1 1Doc!@#$ ROBA123
Nurse fakenurse1 1Nur!@#$ MARYS123
Clerk fakeclerk1 1Cle!@#$ CLERKJ123

Accessing VistA Using the CPRS, Vitals, and BCMA Demo Client Applications

Go to the clients page

Stop OSEHRA VistA Container

Exit from the OSEHRA session, and then from the shell type

> docker stop osehravista

Restart OSEHRA VistA Container

To start up the OSEHRA VistA, from the shell type

> docker start osehravista

Delete OSEHRA VistA Container

To remove the osehravista container, run this:

> docker rm osehravista

FOIA VistA/VEHU Instance
(aka CPRS Demo)

Go to https://hub.docker.com/r/osehra/vehu/ for instructions.

vxVistATM

This downloads vxVistA 15.0 on GT.M.

> docker run -p 9430:9430 -p 8001:8001 -p 2222:22 -d -P --name=vxvista osehra/vxvista

This will require several minutes before the system completes the setup. Type the following command to see if vxVistA VistA container is running.

> docker ps

You should see the following response:

CONTAINER ID     IMAGE                 COMMAND                 CREATED              STATUS               PORTS                                                                               NAMES
fcad559fbbdc   krmassociates/vxvista   "/bin/sh -c /home/..."  About an hour ago    Up About an hour     0.0.0.0:9430->9430/tcp, 0.0.0.0:2222->22/tcp, 0.0.0.0:8006->8001/tcp    vxvista

Accessing VistA

The Docker container sets up the RPC broker, a TCPIP socket-based protocol, which is used for data exchange between VistA and clients such as CPRS, Vitals, and other GUIs. The container also sets up the SSH service to support the terminal-based Roll-and-Scroll UI. The container is accessable via the ip address=127.0.0.1 from the following ports:

  • 9430 - RPC Broker
  • 2222 - SSH

NOTE: CPRS uses the RPC Broker and the correct command line arguments are: S=127.0.0.1 P=9430

You can also access the container using SSH client such as PuTTY by using the address as described in the note above and using the correct port 2222 for container install.

Docker Container User Accounts:

There are two operation systems user accounts that are created automatically during the installation process that make accessing the VistA Roll-and-Scroll UI easier. The use of the accounts becomes clear when you use the Roll-and-Scroll UI in the later section below:

NOTE: by default ${instance} is vxvista. The GT.M system runs under the “vxvista” system account.

Linux User Name Password
root docker
vxvistatied tied
vxvistaprog prog

VistA User Accounts:

The VistA User Accounts are presented in the introduction message. Use one of the ones listed.

Accessing VistA Using the CPRS, Vitals, and BCMA Demo Client Applications

Go to the clients page

Stop vxVistA Container

Exit from the OSEHRA session, and then from the shell type

> docker stop vxvista

Restart vxVistA Container

To start up the OSEHRA VistA, from the shell type

> docker start vxvista

Delete vxVistA Container

To remove the osehravista container, run this:

> docker rm vxvista

RPMS

Go to https://hub.docker.com/r/osehra/rpms for instructions.