· Mar 9, 2020 2m read

InterSystems IRIS for Health ENSDEMO (supports arm64)

InterSystems IRIS for Health ENSDEMO

Yet another basic setup of ENSDEMO content into InterSystems IRIS for Health.

Make sure you have Docker up and running before starting.


Clone the repository to your desired directory

git clone

Once the repository is cloned, execute:

Always make sure you are inside the main directory to execute docker-compose commands.

docker-compose build

Run your Container

After building the image you can simply execute below and you be up and running 🚀:

-d will run the container detached of your command line session

docker-compose up -d

You can now access the manager portal through http://localhost:9092/csp/sys/%25CSP.Portal.Home.zen

  • Username: SuperUser
  • Password: SYS
  • SuperServer port: 9091
  • Web port: 9092
  • Namespace: ENSDEMO


To start a terminal session execute:

docker exec -it ensdemo iris session iris

To start a bash session execute:

docker exec -it ensdemo /bin/bash

Using InterSystems ObjectScript Visual Studio Code extension, you can access the code straight from vscode


Stop your Container

docker-compose stop

Support to ZPM

zpm "install irishealth-ensdemo"
Discussion (14)3
Log in or sign up to continue

Also available as ZPM module now: 

USER>zpm "install irishealth-ensdemo"
[irishealth-ensdemo]    Reload START (/usr/irissys/mgr/.modules/USER/irishealth-ensdemo/1.0.0/)
[irishealth-ensdemo]    Reload SUCCESS
[irishealth-ensdemo]    Module object refreshed.
[irishealth-ensdemo]    Validate START
[irishealth-ensdemo]    Validate SUCCESS
[irishealth-ensdemo]    Compile START
[irishealth-ensdemo]    Compile SUCCESS
[irishealth-ensdemo]    Activate START
[irishealth-ensdemo]    Configure START
[irishealth-ensdemo]    Configure SUCCESS
[irishealth-ensdemo]    MakeDeployed START
[irishealth-ensdemo]    MakeDeployed SUCCESS
[irishealth-ensdemo]    Activate SUCCESS


Here is the set of productions available:

I see that the documentation pages are IRIS CSP classes. So I guess it could work if installed in IRIS. I guess also there is a set of static files (FILECOPY could help).

IMHO, the reasonable approach to have a separate repo ensdemo-doc and a separate module the, which will be a dependent module to irishealth-ensdemo

So people could contribute to documentation independently and update it independently too.