| DESCRIPTION OF ENHANCEMENTS |
VSE-979
4) Jira #VSE-1094
Problem: When scheduling an future appointment using VistA for a clinic
that has a future re-activation date, the resource is not linked to the
appointment.
Resolution: When adding the resource, do not check the inactivation
status.
VSE-1127
5) Jira #VSE-1127
Problem/Task:
The RECALL REMINDER (#403.5) file data, may sometimes be unavailable
because it was removed upon making an appointment.
Resolution:
Created an RPC (SDEC RECALLRMV BY DFN JSON) to retrieve the needed data
from the RECALL RMINDER REMOVED (#403.56) file.
6) Jira #VSE-1144
Problem:
Resolution:
7) Jira #VSE-1146
Problem: Eligibility code is not returned when an appointment does not
have resource.
Sprint 15:
Resolution: When no resource is found, get Hospital Location from the
Appointment sub file of the Patient file. Use the Hospital Location to
get the Enrollment Code and Resource.
8) Jira #VSE-1154
Problem:
Resolution:
VSE-985
9) Jira #VSE-1155
Problem:
Resolution:
10) Jira #VSE-1157
Problem:
VSE-1037
Ensure Contact Attempts for Recall Requests are included when converted
to APPT
Resolution:
Modified the Request Pointer in SDEC CONTACT (#409.86) file to reflect
the appropriate SDEC APPOINTMENT (#409.84) file entry.
11) Jira #VSE-1171
VSE-1087
Problem:
Based on the Research performed in VSE-235 it was determine that a check
on the Appt Status needs to be added to the SDEC APPADD RPC to prevent it
from returning the original Appt for the Same Patient, Date and Clinic
when the original Appt has a status of Cancelled.
Resolution:
Updated APPTGET^SDECUTL to include a status check for the following
statuses:
VSE-1094
C:CANCELLED BY CLINIC
CA:CANCELLED BY CLINIC & AUTO RE-BOOK
N:NO-SHOW
NA:NO-SHOW & AUTO RE-BOOK
PC:CANCELLED BY PATIENT
PCA:CANCELLED BY PATIENT & AUTO-REBOOK
12) Jira #VSE-1172
VSE-1144
Problem:
There were 2 issues identified during the analysis on VSE-235:
1. Locking/Unlocking of ^SDEC(409.84 was using variable DFN instead of
SDECAPPTID.
2. A more efficient cross reference could be used for the
APPTGET^SDECUTL subroutine.
Resolution:
1. Routine SDEC07 was updated to use SDECAPPTID when locking or
unlocking #409.84.
VSE-1146
2. Routine SDECUTL was updated to use the APTDT x-ref.
) Jira #VSE-
Problem:
Resolution:
) Jira #VSE-
VS GUI v. 1.7.9 Release
VSE-1154
Problem:
Resolution:
) Jira #VSE-
Problem:
Resolution:
VSE-1155
) Jira #VSE-
Problem:
Resolution:
) Jira #VSE-
Problem:
VSE-1157
Resolution:
VSE-1171
VSE-1172
FILES:
======
ROUTINES:
=========
VSE-1171 - updated to add a check for
Cancelled Appts to the
SDEC APPADD RPC
SDEC07 - VSE-1172 - updated to address Locking/Unlocking issue from
VSE-235
SDEC52CRMVJSON - VSE-1127 - Added logic to retrieve the RECALL REMINDER
data from the RECALL REMINDER REMOVED (#403.56) file.
SDEC55A VSE-1146
For tracking purposes, please add component(s) and note the associated
SDESAPPTUTIL VSE-1146
SDESCHECKIN VSE-985
SDEC50 VSE-985
SDEC08 VSE-1157
OPTIONS:
========
Jira task(s) out to the right on the same line.
REMOTE PROCEDURES:
==================
SDEC GET RECALLRMV BY DFN JSON- VSE-1127 Retrieve RECALL REMINDER data
from RECALL REMINDER REMOVED (#403.56) file.
JIRA tasks:
-----------
1) Jira #VSE-???(979)
Problem/Task:
When doing a drag and drop with a recall appointment, the request is
created on the RM Grid and not removed when the appointment is made.
This should be a behind the scene action...it shouldn't display on the
Sprint & Associated Tasks:
RM Grid.
Resolution:
2) Jira #VSE-985
Problem: Display a visual indicator for Pre-Checkin Step in VS GUI.
Resolution: Update SDEC FAPPSGET RPC to include a new field that will
==========================
indicate if the patient has completed pre-checkin step for the
appointment.
2) Jira #VSE-1037
Problem: The job SDRR CLEANUP needs to be disabled so that it cannot be
set up to run as a nightly job at sites. Follow the same pattern that
Brian Rene did for the EWL option.
Resolution: Update OPTION SDRR CLEAN-UP to include OUT OF ORDER MESSAGE
Sprint 14:
so that it will not be available. Also update routine SDRRCLR to QUIT
at the top of the routine so that it will not run. These updates
disable the menu option from being run manually or called from the
nightly Schedule/Unschedule Option under the TASKMAN MANAGEMENT option.
3) Jira #VSE-1087
Problem:
Resolution:
|
