============================================================================= Run Date: JUN 25, 2020 Designation: SD*5.3*695 Package : SD - SCHEDULING Priority: Mandatory Version : 5.3 SEQ #609 Status: Released Compliance Date: JUL 24, 2020 ============================================================================= Subject: CHANGES FOR VISTA SCHEDULING GUI 1.7.0 Category: - Informational Description: ============ The informational patch is associated with VistA Scheduling (VS) Graphical User Interface (GUI) release 1.7.0. The corresponding VistA patch is SD*5.3*694 CHANGES FOR VISTA SCHEDULING GUI 1.7.0. The GUI build cannot be installed until VistA patch SD*5.3*694 is installed. Please note that the previous versions of VS will not work after SD*5.3*694 is installed. In addition to the items listed in the defect tracking ticket review below, the following changes were made: 1. Right-clicking the Request Management (RM) Grid header opens the context menu. Irrelevant options should be disabled. 2. Right-clicking the Pending Appointments List header opens the context menu. Irrelevant options should be disabled. 3. Right-clicking the empty Pending Appointments List opens the context menu. Irrelevant options should be disabled. 4. The Trace log file is renamed at startup to include the date and time and is now retained for a week after creation. 5. A Help pane has been added to main GUI screen with links to business-defined websites and e-mail forms. 6. Numerous keyboard shortcuts have been created to access various GUI panes and dialogs. 7. The Application log was renamed from "trace.log" to "VS_GUI_Application.log." 8. Upgraded VS GUI to use .NET Framework version 4.7.1. 9. Upgraded VS GUI to use Telerik version 2018.1.220.45. Patch Components ================ Files & Fields Associated: File Name (#) Field Name (#) New/Modified/Deleted ------------- -------------- -------------------- n/a Forms Associated: Form Name File # New/Modified/Deleted --------- ------ -------------------- n/a Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- n/a Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- n/a Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- n/a Security Keys Associated: Security Key Name ----------------- n/a Templates Associated: Template Name Type File Name (#) New/Modified/Deleted ------------- ---- ------------------ -------------------- n/a Additional Information: n/a New Service Requests (NSRs): ----------------------------- n/a Patient Safety Issues (PSIs): ------------------------------ n/a Defect Tracking Ticket(s) & Overviews: -------------------------------------- 1. String not recognized as valid date/time. Problem: ------- VistA and .NET store dates and times differently so some date/time instances in one cannot be passed to the other without modification. For example, midnight in VistA is 2400 hours of the day before while in .NET it is 0000 hours of the day (e.g., 7/1@2400 in VistA is the same as 7/2@0000). Sending 7/1@2400 to .NET causes an error and sending 7/2@0000 to VistA causes an error. Resolution: ----------- The VS GUI code was modified to stop adding one minute to midnight and to correctly convert VistA date/times to .NET date/times. 2. INC0108413, Rational #714348: User preferences sometimes generate errors Problem: -------- User preferences, which control the content and display of the RM Grid, are not handled correctly by the GUI when duplicate and/or misnamed preference fields appear in the PARAMETERS File (#8989.5) entry for the user. Resolution: ----------- The GUI code was modified to ignore the preference fields if they are not in a pre-defined set of expected values. Duplicate entries are ignored. 3. R18543573FY18, I18556830FY18, Rational #701766: Future appointments show as "action required." Problem: -------- Future appointments show as 'Action Required' in the Encounter 'Action Required' Report [SCRPW ACTION REQUIRED REPORT]. An entry was added to the OUTPATIENT ENCOUNTER File (#409.68) when the future appointment was scheduled. Resolution: ----------- Modified the routine to check the status of an appointment. The status is set based on the status in the PATIENT File (#2). Modified the code to create an entry in the OUTPATIENT ENCOUNTER File (#409.68) after the appointment date/time and once the nightly SDAM BACKGROUND JOB in VistA has completed for that date. 4. Rational #826669 - disposition actions are disabled Problem: -------- For Multiple Return To Clinic (MRTC) appointment requests on the RM Grid, 2 disposition actions - Removed/Scheduled-Assigned and Removed/VA Contract Care - were disabled. This prevented schedulers from dispositioning MRTC requests. Resolution: ----------- The 2 disposition actions - Removed/Scheduled-Assigned and Removed/VA Contract Care - are enabled. 5. Rational #536870: The slider beside the provider list for clinics in the Navigation Pane is inoperative Problem: -------- The slider that appears when the list of providers for a clinic is too long to display in the available space, and does not allow users to view the entire list. Resolution: ----------- The GUI code was modified to enable the slider. 6. R18756778FY18, Rational #743697: On occasion, when an appointment is selected from the pending appointment list, a different appointment appears. Problem: -------- The GUI code that looks up an appointment was confused by another appointment when sharing common data values. Resolution: ----------- The GUI code was modified to look up an appointment by Internal Entry Number (IEN) to alleviate confusion. 7. Fortify scan: The results of the Fortify scan reported security issues with the VS GUI Problem: -------- The results of the Fortify scan reported security issues with the VS GUI. Resolution: ----------- Modified the GUI code to correct the security issues identified in the Fortify scan. 8. Section 508 Audit: The Interim Audit report from the Section 508 office indicated compliance issues. Problem: -------- The Section 508 audit dated August 23, 2019 reported compliance issues. Resolution: ----------- The GUI code was changed to comply with Section 508 requirements. 9. Rational #809445: Prevent the use of older releases of the GUI to curtail user problems and system irregularities. Problem: -------- A recent survey of schedulers showed that over 30% of them were using GUI versions other than the current version. Some of the versions in use were replaced long ago. Users who are using older versions of the software will experience errors that have subsequently been fixed and could fail to function properly with newer VistA patches that have been installed. Resolution: ----------- Refer to patch SD*5.3*694 for a full description of the VistA changes made. The GUI was modified to pass its version identifier to the SDEC SUSRINFO Remote Procedure Call (RPC). It was also changed to return any error messages it receives from the RPC. 10. Rational #719500: The clinic abbreviation is cut off in an appointment request. Problem: -------- The clinic search located in clinic schedule, new Appointment (APPT) request form, new Patient Centered Scheduling (PtCSch) form, and Xfer APPT to Electronic Wait List (EWL) form is missing the abbreviation for the clinic. Resolution: ----------- Made changes to fix the spacing issue in the clinic search to now show the following: Typing 1-7 characters: Search results will display the abbreviation and clinic name Typing 8+ characters: Search results will display the clinic name only 11. Rational #756706: The hot keys to copy and paste an appointment are disabled, but cause an exception error. Problem: -------- The Copy and Paste hot keys are causing the application to crash Resolution: ----------- The hot keys CTRL-C and CTRL-V are fully disabled 12. Rational #769823: Drag and drop Exception Error when dropping into a non-match variable length timeslot Problem: -------- Drag and drop into a new time slot is causing an error. Resolution: ----------- Drag and drop has been fixed to allow appointments to be moved from one timeslot to a non-match variable length timeslot. 13. Rational #770374: New appointment dialog; duration dropdown needs to use the CLINSET APPLEN RPC to calculate duration list, not display an increment. Problem: -------- Appointment duration in the new appointment window needs to use the clinic appointment length to calculate duration. Resolution: ----------- The duration dropdown calculates the duration list correctly. In the new appointment window, the duration dropdown menu will calculate the duration increments based on the appointment length set by the clinic. 14. Rational #774987: Labeling when scheduling MRTC appointments from the parent request does not automatically increment from 1 to 2, etc. Problem: -------- When scheduling MRTC appointments, the booking # of # is NOT displayed in the Find Appointment window. Resolution: ---------- The booking # of # is now correctly displayed in the Find Appointment window. 15. Rational #860236: Enable the Access and Verify Code login option when PIV login services are down Problem: -------- The Access and Verify Code login option needs to be available when Personal Identify Verification (PIV) services are down. Resolution: ----------- The following behaviors now exist. Acceptance Criteria (AC) 1 is currently working as designed. AC1: Given: The PIV Login services are online When: The user types in the incorrect PIV login or is not registered with the PIV login services Then: The user can use the Access and Verify Code login option AC2: Given: The PIV login services are offline Then: The user can use the Access and Verify Code login option 16. Rational #969912: No-Show/SDCANCEL appointment displays the incorrect status in pending appointments and generates an error. Problem: -------- A No-Show/SDCANCEL appointment displays the incorrect status of CANCELLED and generates an error. Resolution: ----------- The code was modified (APPTSTS in SDEC50) to handle the missing cancellation reason (SDCANCEL) using appointment status (cancelled by clinic or patient). 17. Rational #1070962: Failed test case - consult scheduling Problem: -------- Failed Test Case "Consult Scheduling" when executing Test Execution Record "Consult Status Checking"_Cancellation Comments Resolution: ----------- Modified the code to kill the temporary global (TMPD) before calling the SDECCAN^SDCNSLT code. This change removed the extra comments. 18. Rational #1173453: Drag and drop for PtCSch appointments is not available Problem: -------- Drag and drop does not work when selecting a PtCSch appointment in the calendar. Resolution: ----------- Modified the code so drag and drop would work correctly. 19. Rational #1173471: Drag and drop is enabled for view only users Problem: -------- Users with View Only access (SDECZVIEW key) can select the appointment in the calendar, move it to a future timeslot and initiate the drag and drop workflow. Resolution: ----------- Modified the code so Drag and Drop works correctly. Users with View Only access can see the appointment in the calendar view. Selecting the appointment in the calendar opens the slot viewer. Users cannot perform scheduling actions, including drag and drop. The user is not notified that they cannot move the appointment. 20. Rational #1173722: Users can drag and drop a past appointment Problem: -------- Select an APPT, EWL, Return to Clinic (RTC) or MRTC appointment scheduled prior to today's date. Drag it to different dates, previous and future. Resolution: ----------- Drag and drop works correctly. An appointment scheduled prior to today's date cannot be changed using drag and drop, including moving a past appointment to a future date. An appointment can be moved to an earlier timeslot on the same day. 21. Rational #1174165: Users can drag and drop future appointments into past Problem: -------- A drag and drop error occurs when dragging a future appointment into the past. Resolution: ----------- Modified the code so that drag and drop works correctly. Appointments cannot be dragged to a date prior to today's date. An appointment can be moved to an earlier timeslot on the same day. 22. Rational #1198624: Clinic name truncated if abbreviation contains a space Problem: -------- Clinic names that contain a space are truncated. The first few letters of the clinic name are missing. Resolution: ----------- Modified the code to display the full clinic name. 23. Rational #1213995: User preferences not saving Problem: -------- User preference changes are not saving. Resolution: ----------- The data in the RM Grid is filtered to match the User Preference settings. Filters applied to the Wait Time field are reflected in the column heading. Changes saved as default are active in future sessions, or until they are updated. 24. Rational #1214096: The User Preferences ribbon bar icon is not highlighted when updates are applied Problem: -------- After making changes to the User Preferences by selecting 'save as default', the ribbon bar icon is not highlighted to confirm that changes have been saved. Resolution: ----------- The ribbon bar icon is highlighted if default updates are applied to the user preferences. Test Sites: ----------- Martinsburg, WV Omaha, NE Fayetteville, NC System Center Configuration Manager (SCCM) packages have been developed for the distribution of the GUI to the users' workstations: VA VistA Scheduling GUI_P 1.7.0P (GUI for Production) and VA VistA Scheduling GUI_T 1.7 .0T (GUI for Test). SCCM administrators are responsible for pushing the packages to the workstations. The VistA patch installation and the SCCM push must be coordinated for each site by the patch installers and the SCCM administrators. Step 1 (Core): VistA sites using the SCCM push shall install the VSE PRODUCTION and TEST GUIs on applicable workstations using the Configuration Management Control Board (CMCB) package provided by Systems Design (SD). The TEST GUIs will be used to provide training to VS users. - CMCB Build Document (Production): https://vaww.eie.domain.ext/SysDesign/CS/DTStatus/SitePages/Build%20Documents .aspx?pid=216 - CMCB Build Document (Test): https://vaww.eie.domain.ext/SysDesign/CS/DTStatus/SitePages/Build%20Documents .aspx?pid=228 Sites that do not use the SCCM push will be alerted to the new GUI via an Action Item e-mail from Office of Information and Technology (OIT) Information Technology Operations and Services (ITOPS). Follow the detailed instructions in the Action Item e-mail for VACS installation. The IO HBMC FO Application Division will lead and coordinate deployment activities with EUO, Client Technology, Citrix Back Office and Area Managers, and other OIT and business partners as required. Implementation Manager Point of Contact: Name: Yoojin Lee Phone: 206-277-4608 Email: yoojin.lee@domain.ext Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : APR 25, 2018 Completed By: Date Completed: JUN 24, 2020 Released By : Date Released : JUN 25, 2020 ============================================================================= Packman Mail Message: ===================== No routines included