Dev

.eslintignore

@@ -0,0 +1 @@
+mongo-init.js

.eslintrc

@@ -0,0 +1,21 @@
+{
+  "extends": [
+    "prettier",
+    "eslint:recommended", 
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "plugins": [
+    "@typescript-eslint"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {
+    "ecmaVersion": 2018,
+    "sourceType": "module"
+  },
+  "rules": {
+    "semi": ["off"],
+    "@typescript-eslint/semi": ["error", "always"],
+    "quotes": ["error", "single", { "avoidEscape": true }],
+
+  }
+}

.github/workflows/ci-workflow.yml

@@ -0,0 +1,36 @@
+name: Lint and Test
+
+on: [push, pull_request]
+
+jobs:
+  lint:
+    name: Check tsc, lint, and prettier
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+    - uses: actions/setup-node@v1
+      with:
+        node-version: '14.x'
+    - run: npm install
+    - run: npm run lint
+    - run: npm run prettier
+      env:
+        CI: true
+  test:
+    name: Test on node ${{ matrix.node-version }} and ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest, macos-latest]
+        node-version: [14]
+
+    steps:
+    - uses: actions/checkout@v1
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v1
+      with:
+        node-version: ${{ matrix.node-version }}
+    - run: npm install
+    - run: npm test
+      env:
+        CI: true

.gitignore

@@ -5,3 +5,8 @@ package-lock.json
 COVERAGE/
 logs/
 node_modules/
+dist/
+.idea/
+.DS_Store
+tingo_db/
+env.json

.prettierignore

@@ -0,0 +1 @@
+mongo-init.js

.prettierrc

@@ -0,0 +1,8 @@
+{
+  "trailingComma": "none",
+  "arrowParens": "avoid",
+  "endOfLine": "auto",
+  "printWidth": 100,
+  "tabWidth": 2,
+  "singleQuote": true
+}

.vscode/launch.json

@@ -0,0 +1,31 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        // does not work currently
+        // {
+        //     "name": "Debug REMS Backend (Docker)",
+        //     "port": 8091,
+        //     "request": "attach",
+        //     "skipFiles": [
+        //         "<node_internals>/**"
+        //     ],
+        //     "type": "node",
+        //     "localRoot": "${workspaceFolder}",
+        //     "remoteRoot": "/REMS",
+        //     "restart": true
+        // },
+        {
+            "name": "Debug REMS Backend (Local)",
+            "port": 8091,
+            "request": "attach",
+            "skipFiles": [
+                "<node_internals>/**"
+            ],
+            "type": "node",
+            "restart": true
+        }
+    ]
+}

DeveloperSetupGuide.md

@@ -169,15 +169,12 @@ Reference: https://github.com/rbenv/rbenv
 2. Now clone the DRLS component repositories from Github:
     ```bash
     cd <drlsroot>
-    git clone https://github.com/mcode/CRD.git CRD
     git clone https://github.com/mcode/test-ehr.git test-ehr
     git clone https://github.com/mcode/crd-request-generator.git crd-request-generator
     git clone https://github.com/mcode/dtr.git dtr
     git clone https://github.com/mcode/REMS.git REMS
-    git clone https://github.com/mcode/pharmacy-information-system.git pharmacy-information-system
+    git clone https://github.com/mcode/pims.git pims
 
-    cd CRD/server
-    git clone https://github.com/mcode/CDS-Library.git CDS-Library
     ```
 
 # Open DRLS REMS as VsCode workspace
@@ -299,21 +296,23 @@ Reference: https://docker-sync.readthedocs.io/en/latest/getting-started/commands
 3. Find **Jon Snow** in the list of patients and click the dropdown menu next to his name.
 4. Select **2183126 - Turalio 200 MG Oral Capsule** in the dropdown menu.
 5. Click anywhere in the row to select Jon Snow.
-6. Click **Submit to CRD** at the bottom of the page.
-7. After several seconds you should receive a response in the form of two **CDS cards**:
+6. Click **Send Rx to PIMS** at the bottom of the page to send a prescription to the Pharmacist.
+7. Click **Submit to REMS-Admin** at the bottom of the page.
+8. After several seconds you should receive a response in the form of two **CDS cards**:
     - **Drug Has REMS: Documentation Required.**
-8. Select **Patient Enrollment Form** on the returned CDS card with summary **Drug Has REMS: Documentation Required**.
-9. If you are asked for login credentials, use **alice** for username and **alice** for password.
-10. A webpage should open in a new tab, and after a few seconds, a questionnaire should appear.
-11. Fill out questionnaire and hit **Submit REMS Bundle**.
-12. A new UI will appear with REMS Admin Status and Pharmacy Status.
-13. Go to http://localhost:4200 and play the role of a pharmacist.
-14. Click on **Log in as Admin** in the top right of the page
-15. Sign in with the pre-configured user Suzy:
+9. Select **Patient Enrollment Form** on the returned CDS card with summary **Drug Has REMS: Documentation Required**.
+10. If you are asked for login credentials, use **alice** for username and **alice** for password.
+11. A webpage should open in a new tab, and after a few seconds, a questionnaire should appear.
+12. Fill out questionnaire and hit **Submit REMS Bundle**.
+13. A new UI will appear with REMS Admin Status and Pharmacy Status.
+14. Go to http://localhost:5050 and play the role of a pharmacist.
+<!-- 15. Click on **Log in as Admin** in the top right of the page -->
+<!-- 16. Sign in with the pre-configured user Suzy:
 	* Email: spharmichael@example.com
-	* Password: suzy
-16. Click **Doctor Orders** in the left hand navigation menu on the screen
-17. See the Doctor Order that was sent to the pharmacist from the prescriber in steps 1-12.
+	* Password: suzy -->
+15. Click **Doctor Orders** in the top hand navigation menu on the screen
+16. See the Doctor Order that was sent to the pharmacist from the prescriber.
+17. Repeat steps 9-12 for submitting the Prescriber Enrollment and Prescriber Knowledge Assessment Forms and check how ETASU statuses change in both the PIMS prescription UI and the Prescriber status page. 
 
 Congratulations! DRLS is fully installed and ready for you to use!
 

Dockerfile.dev

@@ -1,4 +1,6 @@
-FROM ubuntu:latest
+FROM node:18-alpine 
 WORKDIR /REMS
-COPY . .
-CMD ./dockerRunner.sh
+COPY --chown=node:node . .
+RUN npm install
+EXPOSE 8090
+CMD ./dockerRunnerDev.sh

Dockerfile.tmpl

@@ -5,38 +5,7 @@ ARG BUNDLE_DIR
 ARG DEBIAN_FRONTEND=noninteractive
 ENV DEBIAN_FRONTEND=noninteractive
 
-# RUN apt-get update && apt-get install -y ca-certificates && apt-get install -y curl
-
-# RUN curl http://pki.mitre.org/MITRE%20BA%20ROOT.crt >> /etc/ssl/certs/ca-certificates.crt && \
-#     curl http://pki.mitre.org/MITRE%20BA%20NPE%20CA-3.crt >> /etc/ssl/certs/ca-certificates.crt && \
-#     curl http://pki.mitre.org/MITRE%20BA%20NPE%20CA-4.crt >> /etc/ssl/certs/ca-certificates.crt && \
-#     update-ca-certificates
-
-# WORKDIR /pki
-# COPY Zscaler_Root_CA.pem .
-# RUN cat Zscaler_Root_CA.pem >> /etc/ssl/certs/ca-certificates.crt
-
-
-
-# # Install Git from Source to get around TLS errors with Zscaler,
-# # explicitly using openssl instead of gnutls
-# # RUN cp /etc/apt/sources.list /etc/apt/sources.list~
-# RUN sed -i -- 's/# deb-src/deb-src/' /etc/apt/sources.list
-# RUN apt-get update && \
-#     apt-get install build-essential fakeroot dpkg-dev -y && \
-#     apt-get install git-man -y && \
-#     apt-get -f build-dep git -y && \
-#     apt-get install libcurl4-openssl-dev -y
-
-# WORKDIR /sourcegit
-
-# RUN apt-get source git && \
-#     cd git-2.*.*/ && \
-#     sed -i -- 's/libcurl4-gnutls-dev/libcurl4-openssl-dev/' ./debian/control && \
-#     sed -i -- '/TEST\s*=\s*test/d' ./debian/rules && \
-#     dpkg-buildpackage -rfakeroot -b -uc -us && \
-#     dpkg -i ../git_*ubuntu*.deb
-
+COPY ./mongo-init.js ${BUNDLE_DIR}/mongo-init.js
 COPY ./.cnab/app/porter.yaml ${BUNDLE_DIR}/porter.yaml
 COPY ./docker-compose-porter.yml ${BUNDLE_DIR}/docker-compose-porter.yml
 COPY ./.env ${BUNDLE_DIR}/.env

README.md

@@ -15,9 +15,25 @@ You can find complete end-to-end full-stack set up guides for DRLS REMS at the f
     ```
 2. Run dockerRunner.sh script
     ```bash
-    ./dockerRunner.sh  
+    npm run start
     ```
 
+## Running the Mongo DB instance 
+1. On the first run use the following command to create a docker mongo instance:
+    ```bash
+        docker run --name rems_local_pims_remsadmin_mongo --expose 27017 -p 27017:27017 -e MONGO_INITDB_ROOT_USERNAME='rems-admin-pims-root' -e MONGO_INITDB_ROOT_PASSWORD='rems-admin-pims-password' -v rems_local_pims_remsadmin_mongo:/data/db -v "$(pwd)"/mongo-init.js:/docker-entrypoint-initdb.d/mongo-init.js mongo
+    ```
+    To stop the running container, simply use ctrl + c
+
+
+2. On subsequent runs use the following command to start the existing mongo container: 
+    ```bash
+        docker start rems_local_pims_remsadmin_mongo
+    ```
+    To stop the running container, simply run the below command
+    ```bash
+        docker stop rems_local_pims_remsadmin_mongo
+    ```
 # REMS Administrator
 NOTE: The REMS Administrator is a work in progress.
 

REMS.code-workspace

@@ -3,13 +3,6 @@
 		{
 			"path": "../test-ehr"
 		},
-		{
-			"name": "CRD-CDS-Library",
-			"path": "../CRD/server/CDS-Library"
-		},
-		{
-			"path": "../CRD"
-		},
 		{
 			"path": "../crd-request-generator"
 		},
@@ -20,7 +13,7 @@
 			"path": "."
 		},
 		{
-			"path": "../pharmacy-information-system"
+			"path": "../pims"
 		}
 	],
 	"launch": {
@@ -39,13 +32,11 @@
 			  "stopAll": true,
 			  "preLaunchTask": "Launch Chrome in Debug Mode",
 			  "configurations": [
-				  "Debug CRD (Local + Docker)", 
 				  "Debug DTR Backend (Docker)", 
 				  "Debug Test-EHR (Local + Docker)", 
 				  "Debug DTR Frontend (Attach Local + Docker)", 
 				  "Debug CRD-Request-Generator (Attach Docker)", 
-				  "Debug Pharmacy-Information-System Backend (Docker)", 
-				  "Debug Pharmacy-Information-System Frontend (Attach Local + Docker)",
+			//  ToDO: Add in PIMS Debugging and REMS debugging in docker
 				  "Post Debug Task - Terminate Chrome (This is not a Debugger)"
 				],
 			}
@@ -58,13 +49,13 @@
 				"type": "shell",
 				"label": "Launch Chrome in Debug Mode",
 				"linux": {
-					"command": "google-chrome http://localhost:3000 http://localhost:4200 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
+					"command": "google-chrome http://localhost:3000 http://localhost:5050 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
 				},
 				"osx": {
-					"command": "/Applications/Google\\ Chrome.app/Contents/MacOS/Google\\ Chrome http://localhost:3000 http://localhost:4200 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
+					"command": "/Applications/Google\\ Chrome.app/Contents/MacOS/Google\\ Chrome http://localhost:3000 http://localhost:5050 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
 				},
 				"windows": {
-					"command": "for /f \"usebackq tokens=1,2,3,4,5\" %a in (`reg query HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\ /s /f \\chrome.exe ^| findstr Application`) do set CHROMEPATH=%c%d%e & set CHROMEPATH=%CHROMEPATH:ProgramFiles=Program Files% & \"%CHROMEPATH%\" http://localhost:3000 http://localhost:4200 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
+					"command": "for /f \"usebackq tokens=1,2,3,4,5\" %a in (`reg query HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\ /s /f \\chrome.exe ^| findstr Application`) do set CHROMEPATH=%c%d%e & set CHROMEPATH=%CHROMEPATH:ProgramFiles=Program Files% & \"%CHROMEPATH%\" http://localhost:3000 http://localhost:5050 http://localhost:3005/register --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug"
 				},
 				"presentation": {
 					"close": true,

SimpleSetupGuide.md

@@ -73,7 +73,9 @@ Your computer must have these minimum requirements:
 ```
 
 #### Windows 
-> Note: The install on Windows requires additional steps in order to expose the WSL Docker Daemon to Porter. The way to do this is to run the porter commands inside an additional windows specific container running in interactive mode, which exposes that container's terminal instance. 
+> Note: The Porter Installation on Windows is currently broken, to run the REMS prototype on Windows please refer to the [Running Docker Compose without Porter](#docker-compose-without-porter) section of this guide.
+
+<!-- > Note: The install on Windows requires additional steps in order to expose the WSL Docker Daemon to Porter. The way to do this is to run the porter commands inside an additional windows specific container running in interactive mode, which exposes that container's terminal instance. 
 
 > Note: replace ${vsac_api_key} in the below commands with your own VSAC api key obtained in the previous step.
 
@@ -99,7 +101,7 @@ Your computer must have these minimum requirements:
     porter install fullstack_rems --param vsac_api_key=${vsac_api_key} --allow-docker-host-access  # Subsequent runs can use the local installation
 ```
 
-> Note: Any porter comannds below such as [stopping the server](#stop-server), [updating the porter application](#updating-porter-application), or [uninstalling the porter application](#cleanup) should be run within the windows specific docker container terminal instance started in step 2. To exit the interactive shell started in step 2, use **ctrl + d**
+> Note: Any porter comannds below such as [stopping the server](#stop-server), [updating the porter application](#updating-porter-application), or [uninstalling the porter application](#cleanup) should be run within the windows specific docker container terminal instance started in step 2. To exit the interactive shell started in step 2, use **ctrl + d** -->
 
 ### 4. Verify everything is working
 
@@ -110,21 +112,23 @@ Your computer must have these minimum requirements:
 3. Find **Jon Snow** in the list of patients and click the dropdown menu next to his name.
 4. Select **2183126 - Turalio 200 MG Oral Capsule** in the dropdown menu.
 5. Click anywhere in the row to select Jon Snow.
-6. Click **Submit to CRD** at the bottom of the page.
-7. After several seconds you should receive a response in the form of two **CDS cards**:
+6. Click **Send Rx to PIMS** at the bottom of the page to send a prescription to the Pharmacist.
+7. Click **Submit to REMS-Admin** at the bottom of the page.
+8. After several seconds you should receive a response in the form of two **CDS cards**:
     - **Drug Has REMS: Documentation Required.**
-8. Select **Patient Enrollment Form** on the returned CDS card with summary **Drug Has REMS: Documentation Required**.
-9. If you are asked for login credentials, use **alice** for username and **alice** for password.
-10. A webpage should open in a new tab, and after a few seconds, a questionnaire should appear.
-11. Fill out questionnaire and hit **Submit REMS Bundle**.
-12. A new UI will appear with REMS Admin Status and Pharmacy Status.
-13. Go to http://localhost:4200 and play the role of a pharmacist.
-14. Click on **Log in as Admin** in the top right of the page
-15. Sign in with the pre-configured user Suzy:
+9. Select **Patient Enrollment Form** on the returned CDS card with summary **Drug Has REMS: Documentation Required**.
+10. If you are asked for login credentials, use **alice** for username and **alice** for password.
+11. A webpage should open in a new tab, and after a few seconds, a questionnaire should appear.
+12. Fill out questionnaire and hit **Submit REMS Bundle**.
+13. A new UI will appear with REMS Admin Status and Pharmacy Status.
+14. Go to http://localhost:5050 and play the role of a pharmacist.
+<!-- 15. Click on **Log in as Admin** in the top right of the page -->
+<!-- 16. Sign in with the pre-configured user Suzy:
 	* Email: spharmichael@example.com
-	* Password: suzy
-16. Click **Doctor Orders** in the left hand navigation menu on the screen
-17. See the Doctor Order that was sent to the pharmacist from the prescriber in steps 1-12.
+	* Password: suzy -->
+15. Click **Doctor Orders** in the top hand navigation menu on the screen
+16. See the Doctor Order that was sent to the pharmacist from the prescriber.
+17. Repeat steps 9-12 for submitting the Prescriber Enrollment and Prescriber Knowledge Assessment Forms and check how ETASU statuses change in both the PIMS prescription UI and the Prescriber status page. 
 
 Congratulations! DRLS is fully installed and ready for you to use!