============================================================================= Run Date: APR 01, 2020 Designation: YS*5.01*164 Package : YS - MENTAL HEALTH Priority: Mandatory Version : 5.01 SEQ #122 Status: Released Compliance Date: MAY 02, 2020 ============================================================================= Subject: National Clozapine Registry (NCR) Hotfix version 1.0.0.6 Category: - Informational Description: ============ The purpose of Mental Health patch YS*5.01*164 is to provide information regarding a hotfix for version 1.0.0.6 of the National Clozapine Registry (NCR) graphical user interface (GUI). The NCR is maintained by the National Clozapine Coordinating Center (NCCC). The NCCC is responsible for VA's compliance with the clozapine Risk Evaluation and Mitigation Strategy (REMS), which was mandated by the Food and Drug Administration (FDA) for tracking clozapine patients. The NCR v1.0.0.6 GUI is only available to staff at the NCCC. The software for this hotfix will be hosted in the VA cloud servers. No site involvement is needed and there are no components added to VistA. This patch provides documentation of the changes made to this cloud-based application. The issues below are listed with their Team Foundation Server (TFS) and Rational Tools identifiers (IDs). Hotfix v1.0.0.6 addresses the following defects: Issue 1: Date of Death (DOD) must be later than Date of Birth (DOB) TFS ID: 2119 Rational ID: 1242046 This fix addresses a problem where user is able to enter a date of death that is the same as the date of birth. This was fixed by changes to the client and server side validation that will not allow a date that is the same as the date of birth, so that a patient's DOD must be later than the DOB. Issue 2: Prevent Date of Death Prior to Date of Birth TFS ID: 2073 Rational ID: 1238541 This fixes a problem where user is able to enter a date of death prior to the date of birth. This is fixed by changes to client and server side validation that will not allow a date that is earlier than the date of birth, so that so that a Patient's DOD must be later than the DOB. Issue 3: No Message Displayed for Search with no Results TFS ID: 2122 Rational ID: 1242053 This fixes a problem where the user would just see an empty table if there were no results from their search in the Facilities and Patients index pages. This was fixed by adding the message "(No Facilities/Patients)", so that the user is aware that there were no matching results. Issue 4: Add Validation Error if Stop Date Prior to Registration Date TFS ID: 2071 Rational ID: 1238516 This fixes a problem where the stop date field would clear if it was before the start date without informing the user. This was fixed by adding an error message under the input, so that the user is aware that they entered an invalid date. Issue 5: Update "Minimum 4 digits" Placeholder Text TFS ID: 2153 Rational ID: 1242050 This fixes a problem where the placeholder text for Social Security Number inputs were ambiguous. This was fixed by adding the word "digits" to the phrase "minimum 4", so that it reads "minimum 4 digits". Issue 6: Change Error Message for SSN to Say "Minimum" TFS ID: 2120 Rational ID: 1243109 This fixes a problem where the error message for entering less than four digits of a SSN would show an abbreviation for minimum ("min"). This is fixed by changing the abbreviation to the full word, so that it's clear what the error means. Issue 7: Telephone Number Displays Incorrectly TFS ID: 2074 Rational ID: 1238553 This fixes a problem where the extension number for a phone number was being displayed as the full phone number. This is fixed by changing the extension field reference to the extension property, so that the field correctly displays the phone extension. Issue 8: Deleting Patient Results in 500 Error TFS ID: 1518 Rational ID: 1210538 This fixes a problem where the user would receive a 500 error when trying to delete a patient due to a reference to Treatment Status on the wrong entity. This was fixed by changing the entity reference, so that the Treatment Status isn't a null reference. Issue 9: Reports Tile not Linked TFS ID: 1516 Rational ID: 1210260 This fixes a problem where the Reports tile on the administrator's homepage doesn't link to anything. This was fixed by adding a link to the configured reporting site, so that the tile redirects to the correct reporting site. Issue 10: Update to SSN Search and Validation TFS ID: 2077 Rational ID: 1238794 This fixes a problem where patients could not be searched efficiently on the index pages. This was fixed by updating the search to do partial SSN search instead of only the last 4 digits as well as adding support for searching by the Last 5 (Last Initial + Last 4 SSN digits), so that the patient and application index pages can be filtered to the desired user quickly. Issue 11: Patients Not Looked Up by Full SSN TFS ID: 2081 Rational ID: 1238802 This fixes a problem where patients were not being looked up in application forms by their exact 9 digit SSN. It was fixed by updating the patient search box to only allow the 9 digit SSN, so that only the specified patient will be found. Issue 12: Update System-wide Breadcrumbs TFS ID: 2075 Rational ID: 1239419 This fixes a problem where clicking on the current index page breadcrumbs was not clearing the search parameters to reset the form. This was fixed by updating the breadcrumb generation of all index pages with a search filter to exclude search query parameters, so that when the breadcrumb is clicked the index page will return to the default search. Issue 13: Breadcrumb Trail Includes Search Query TFS ID: 2091 Rational ID: 1238557 This fixes a problem where clicking on the final breadcrumb in Internet Explorer v. 11 (IE11) could redirect the user to unexpected URLs because of a specific IE11 incompatibility. This was fixed by changing the breadcrumb generation in the system to use .NET Core's URL generation utilities to ensure that all breadcrumbs use the specifically desired URL so that no unexpected behavior will occur. Issue 14: Verify Patient Record Can Be Deleted TFS ID: 1772 Rational ID: 1229541 This fixes a problem that prevents a patient's record from being deleted. Patients without data in any table could not be deleted. This has been fixed. Issue 15: Restrict Station ID Search to Treatment Facility TFS ID: 1517 Rational ID: 1210479 This fixes a problem where a search query would return facilities that were not in "scope". The query will now be constrained facilities that have correct parent and children relationship. Issue 16: Change Daily Dose on Prescription to be decimal TFS ID: 1972 Rational ID: 1230154 This fixes a problem where the user could not enter a decimal value for the daily dose. Users will now be able to enter a daily dose in .5 milligram increments. Issue 17: Remove REMS Reports Pane TFS ID: 2072 Rational ID: 1238536 The REMS report mockup pane was displaying in the Details screen. The fix removed this pane. Issue 18: Default Index Page Sort Not Working Properly TFS IDs: 1409, 2040 Rational ID: 1210516 As of hotfix 1.0.0.4, the default Application index page sort HAS form statuses not being grouped properly. The fix will group them correctly. Issue 19: Change "Daily Dose" to "Starting Dose" TFS IDs: 1515, 1518 Rational ID: 1211720 The Daily Dose display was ambiguous. The fix Removed "Daily Dose" row from the Current Clozapine Treatment card and changed the "Daily Dose" field label in the Treatment > Edit view to "Starting Dose". Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : MAR 27, 2020 Completed By: Date Completed: MAR 31, 2020 Released By : Date Released : APR 01, 2020 ============================================================================= Packman Mail Message: ===================== No routines included