Issue 21-155: Add inactive/active column after name on the Enrollment report. Enrolled is defined as “eligible on intake form and marked as enrolled.”

Solution: Added column using definition.

Reported: 2021-08-23 by Henschke.

Issues 21-156 and 21-126: Order of columns is: Name, SSN or PID, Form, Form Date, Followup, on Date. Remove When column.

Solution: Changed columns as requested.

Reported: 2021-08-23 and 2021-07-12 by Henschke.

Issue 21-173: The word baseline shows up in the on Date column when CT scan is a baseline scan.

Solution: Fixed to put in date.

Reported: 2021-09-14 by Rukavena.

Issue 21-182: Dates are being sorted as text instead of dates.

Solution: Fixed to sort as date.

Reported: 2021-09-30 by Jarapatnakul.

Issues 21-158, 21-157 and 21-120: Change followup report columns to F/U Date, Name, SSN or PID, Baseline Date, Last Form, Form Date, Recommendation, Contact Info. (Remove When.) Change title of Followup report to “Participant Follow-up,” add phone number to contact info, add other types of Follow-up.

Solution: Made changes as requested.

Reported: 2021-08-23 and 2021-07-09 by Henschke and Jirapatnakul.

Issue 21-168: The word baseline appears instead of the follow-up date sometimes.

Solution: Fix bug.

Reported: 2021-08-29 by Jirapatnakul.

Issue 21-174: The follow-up date on the follow-up form is also the date of scheduled CT, so the field name (sidoct) was different than the field name in other forms (cefud). This meant that the date on the follow-up form was not included in algorithm to determine follow-up date.

Solution: Changed field name.

Reported: 2021-09-14 by Lily.

Issue 21-175: The wrong date was being used for the intake date.

Solution: Fix bug.

Reported: 2021-09-14 by Yaw.

Issue 21-165: Missing CT report is reporting patients who do have CT evaluations.

Solution: Fixed bug.

Reported: 2021-08-31 by Murphy

Issue 21-193: Patients who had a follow-up form after a CT Eval were shown on report because algorithm stopped looking for a CT Eval in the patient graph.

Solution: Included looking for earlier CT Eval form in algorithm

Reported: 2021-10-12 by Murphy.

Issue 21-164: Inactive patients are showing up in reports that they should not be in. They should only be in enrollment and inactive reports.

Solution: Fixed to keep inactive patients out of inappropriate reports.

Reported: 2021-08-31 by the Phoenix team.

Issue 21-181: If an inactive patient has a CT Scan or other intervention the Nurse Navigator will not be alerted. The team decided to add inactive patients to the activity report so they can correct status of patient if needed and will follow-up as appropriate.

Solution: Add inactive patients to Activity report.

Reported: 2021-09-30 by Murphy.

Issues 21-161: Include CAC score field from CT Eval form in Data Dictionary.

Solution: Added field to Data Dictionaries.

Reported: 2021-08-21 by Yip and Jirapatnakul.

Issue 21-049: Allow clinicians other than the radiologist to reset the date to Followup (approximate date) on the Followup report. Change existing Followup Date field to Followup Form Date and add new date field called Next Followup Date. Computation of new CT Eval Form date will attend to this new field instead of the old one. Insert new field before Date of baseline CT.

Solution: Next CT Followup added and used to determine date for Participant Followup Report.

Reported: 2021-04-22 by Anil and Yaw.

Issues 21-181 through 21-188: Three date formats were in use in the user reports, so they were updated to consistently be MM/DD/YYYY.

Solution: Fixed inconsistencies.

Reported: 2021-09-30 by Yaw.

Issues 21-159: Change dropdown menu item from Missing Image & CT Evaluation to Intake But No CT Evaluation.

Solution: Changed item.

Reported: 2021-08-23 by Henschke.

Issue 21-146: Minor change in nodule grid to move Spiculated up under smooth edge since they are related.

Solution: Changed form.

Reported: 2021-07-25 by Chenoweth.

Issue 21-190: Next Change CT followup field name to New CT follow-up date if needed. Remove red star. Move field below Time since baseline box.

Solution: Changed field name and position.

Reported: 2021-10-14 by the Phoenix Team.

Issue 21-154: The VA firewall blocks the link to Jira, so the team decided to remove that link for all pages in the VA.

Solution: Removed submit feedback link.

Reported: 2021-07-25 by Chenoweth.

Issue m015: To prepare for non-VA installations, access/verify needs to be changed to username/password.

Solution: Parameter created to change wording.

Reported: 2021-02-24 by Beyond VAPALS team.

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:

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.

If you’ve already tried installing this once, you can use the following commands instead:

You may safely download the archive file (sami-18-14.zip) in advance of the actual install. In the following text, [now] represents a time stamp representing your current time, and [bits/sec] is a data rate and [time] is how long the file took to transfer (both of which vary based on the user’s network conditions).

Then unzip the archive file with the following command.

At this point, the web-application files must be installed. This is done with a script that backs up the affected directories before installing anything, then upgrades the web-application files. The output looks like this (where [x] represents a number).

Outside the VA firewall, VAPALS-ELCAP systems maintain up-to-date clones of the official GitHub repository, and this script will have different output.

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 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.

This installs the various M assets required by the application.