| DESCRIPTION OF ENHANCEMENTS |
For tracking purposes, please add component and note the associated Jira
SDEC1: VSE-634, VSE-635, VSE-663, VSE-664, VSE-717, VSE-724,
The VS GUI is being updated to utilize RPCs returning data in JSON
format. Create new, trimmed version of SDEC RECGET in JSON format.
Resolution:
The new SDEC GET PATIENT RECALLS JSON RPC was created to return the 20
key fields needed to help populate the VS GUI screens related to the
review and processing of Recalls.
5) Jira #VSE-724 - Create new RPC to return a single Appointment Request
in JSON format.
VSE-734
Problem:
The VS GUI is being updated to utilize RPCs returning data in JSON
format. Create new SDEC GET APPT REQ BY IEN JSON format.
Resolution:
The new SDEC GET APPT REQ BY IEN JSON RPC was created to return the 39
key fields needed to help populate the VS GUI screens related to the
review and processing of the Appointment Requests.
SDEC28: VSE-168/664
6) Jira #VSE-634 - Create new RPC that will return a single recall
Problem: The VS GUI is in need of an RPC that will return a single Recall
based on the IEN being passed to Vista.
Resolution:
The new SDEC GET PATIENT RECALL BY IEN was created to return the 20
key fields needed to help populate the VS GUI screens related to the
review and processing of a single Recall.
SDEC28L: VSE-664
7) Jira #VSE-684 - Pending RTC Order Cleanup Option Enhancement:
Confirmation Message
Problem:
Request an enhancement to the RTC Cleanup tool to have it present with
user with a confirmation message before it runs. This will allow the
user to change their mind after selecting the OPTION.
Resolution:
Both SDEC PENDING RTC - FULL and SDEC PENDING RTC - DATE options were
SDEC40: VSE-693
modified to include a confirmation message to ensure that the user wants
to run the cleanup tool.
8) Jira #VSE-685 - Pending RTC Order Cleanup Option Enhancement: Date
Clarification
Problem:
Request an enhancement to the RTC Cleanup tool (SDEC PENDING RTC - DATE)
to define that the date being prompted for is the Create date.
SDEC51B: VSE-635
Resolution:
SDEC PENDING RTC - DATE was modified to present the user with a prompt
for what SDEC REQUEST Create dates should be searched on. The
information prior to the prompt also informs the user that the Cleanup
Tool will select RTCs based on create date.
9) Jira # VSE-686 - Pending RTC Order Cleanup Option Enhancement: Print
Results
Problem:
SDEC52C: VSE-634, VSE-556
Request an enhancement for the RTC Order Cleanup Options to return a
report of the RTC and Orders that were updated via the tool.
Resolution:
Added a report to both the SDEC PENDING RTC - FULL and SDEC PENDING RTC -
DATE OPTION. The user will now be prompted for a DEVICE and a report
with information regarding both the ORDER and the RTC will be printed for
any RTC that was selected and cleaned up.
10) Jira # VSE-734 - Create new RPC that will return, in JSON format, a
SDEC52CJSON: VSE-663, VSE-734
single recall based on the IEN being passed to Vista.
Problem: VS GUI is in need of an RPC that will return a single Recall
in JSON format based on the IEN being passed into Vista.
Resolution: The new SDEC GET PATIENT RECALL BY IEN JSON RPC was created to
return the 20 key fields needed to help populate the VS GUI screens
related to the review and processing of Recalls. This RPC passes back a
single record to the GUI based on the IEN being passed into Vista.
SDECCONSJSON: VSE-717
11) Jira #VSE-728 - Correct defect with new contact creation
Problem:
If a Service (Field 1.1) is passed into the RPC SDEC NEW CONTACT, it will
be concatenated with the Main Sequence (Field 2.2).
Resolution:
When setting into the global, include the system delimiter (^) in front
of the service.
SDECAR4: VSE-724
12) Jira #VSE-730 - Prevent appointment cancelation if it is in a
Checked-In status.
Problem:
When canceling an appointment, the Appointment file (409.84) would have
its status changed to Cancel prior to performing all validation. This
would cause the appointment to become stuck.
Resolution:
Ensure all validation is complete prior to updating any files.
task(s) out to the right on the same line.
SDECCON: VSE-728
13) Jira #VSE-693 - Modify Patient Letter to Remove Title (Mr/Ms)
Problem:
Requested modification to patient letters printed from VS GUI to
print name only (with no title/prefix) in the salutation
Resolution:
Modifications were completed to eliminate the Title of Mr/Ms from the
following letters: Pre-appointment, No-Show, Cancellation by Patient, and
SDECRTCF: VSE-684,685,686
Cancellation by Clinic
14) Jira #VSE-800 - VS GUI crashing when cancelling VVS Appointment
Problem:
When cancelling a VVS Appointment using Access/Verify when challenged for
Authentication and choosing cancel, the VS GUI could crash.
Resolution:
Verify authentication was completed before proceeding and if not, return
SDEC08: VSE-730
to the previous process.
15) Jira #VSE-168 - Tasks Tab - Patient Search Functionality
Problem:
Patient Search was not 508 compliant.
Resolution:
Replaced Patient Search function with pop-up search. Addressed all 508
requirements for the Patient Search function in the tasks tab.
16) Jira #VSE-188 - New Appointment - Remediate 508 findings in New
Appointment form
Problem:
New Appointment Form was not 508 compliant.
Resolution:
Addressed all 508 findings in the New Appointment form in VS GUI.
OPTIONS:
17) Jira #VSE-562 - Edit a VVS Appointment from VS GUI
Problem:
I want to be able to edit a VVS appointment from VS GUI, so that I do not
have to use multiple applications to modify a single appointment.
Resolution:
A button was added on the edit Appointment Form that allows users to edit
the corresponding video appointment.
========
18) Jira #VSE-688 - View a VVS Appointment
Problem:
I want to view an existing VVS appointment from VS GUI, so that I can
access VVS appointment details without using multiple applications.
Resolution:
A button was added to the View Appointment Form that allows users to view
the corresponding video appointment.
SDECRPC: VSE-634, VSE-635, VSE-664, VSE-717, VSE-724, VSE-734
19) Jira #VSE-689 - Resend VVS Appointment Link
Problem:
As a scheduler, I want the ability to resend the VVS appointment link to
video visit participants from VS GUI, so that I can ensure all
participants have the link available at appointment time without using
multiple applications.
Resolution:
A button was added to the VVS Appointment Form to allow users to re-send
VSE-556, VSE-663
the VVS appointment link.
20) Jira #VSE-718 - Update GUI to use new SDEC GET PAT CONSULT BY IEN RPC
Problem:
GUI needed to be updated to use new SDEC GET PAT CONSULT BY IEN RPC.
Resolution:
Updated the GUI to use SDEC GET PAT CONSULT BY IEN RPC when selecting an
appointment from the pending appointments list.
21) Jira #VSE-719 - Update GUI to use new SDEC GET PAT CONSULT RPC
Problem:
GUI needed to be updated to use new SDEC GET PAT CONSUL RPC.
Resolution:
Updated the GUI to use SDEC GET PAT CONSUL RPC.
22) Jira #VSE-725 - Remove unnecessary RPC calls
REMOTE PROCEDURES:
Problem:
There are 4 RPC calls made every time the context menu is opened in the
pending appointments list. Remove these calls, as they are unnecessary.
Resolution:
Removed the 4 unnecessary RPC calls made when opening the context menu in
the pending appointments list.
23) Jira #VSE-726 - Updates to GUI to support new SDEC ARGET RPC
==================
Problem:
Update GUI to use the new SDEC ARGET RPC that returns only needed data
for a specific appointment and incorporate into LSD service.
Resolution:
The GUI was updated to include the new SDEC ARGET RPC.
24) Jira #VSE-735 - Update GUI to use new SDEC GET PATIENT RECALL BY IEN
RPC
SDEC GET PAT CONSULT BY IEN: VSE-635
Problem:
Update the GUI to use the new SDEC GET PATIENT RECALL BY IEN RPC.
Resolution:
The GUI was updated to include the new SDEC GET PATIENT RECALL BY IEN RPC.
25) Jira #VSE-741 - Update GUI to use new SDEC GET PATIENT RECALL RPC
Problem:
SDEC GET PATIENT CONSULT JSON: VSE-717
Update the GUI to use the new SDEC GET PATIENT RECALL RPC.
Resolution:
The GUI was updated to include the new SDEC GET PATIENT RECALL RPC.
26) Jira #VSE-786 - Speed up processing of JSON RPC
Problem:
Current VSE Broker code that processes JSON responses from RPCs is slow.
If the JSON response contains a few hundred records, it can take minutes
SDEC GET PATIENT DEMOG: VSE-664
to parse all the data. That is because instead of parsing the data stream
as an array of strings, which is how VistA returns JSON, the VSE Broker
uses the code intended for single string value RPCs, which checks each
character for the end of transmission.
SDEC GET PATIENT RECALL BY IEN: VSE-634
SDEC GET PATIENT RECALLS JSON: VSE-663
SDEC GET APPT REQ BY IEN JSON: VSE-724
SDEC GET RECALL BY IEN JSON: VSE-734
SDEC GET PATIENT RECALLS: VSE-556
FILES:
JIRA tasks:
-----------
1) Jira #VSE-635 - Review Consults/Procedure RPCs
Problem:
The VS GUIs RPCs related to Consults/Procedures need to be reviewed to
determine what optimizations can be made to help improve the response time
of the VS GUI while processing these records.
======
Resolution:
The VS GUI Trace Logs were reviewed and the new SDEC GET PAT CONSULT BY
Internal Entry Number (IEN) RPC was created to return 17 key fields needed
to help populate the VS GUI screens related to the review and processing
of the Consults and Procedures.
2) Jira #VSE-717 - Create new RPC to return a single Consult in
JavaScript Object Notation (JSON) format.
Problem:
The VS GUI is being updated to utilize RPCs returning data in JSON
format. Create new SDEC GET PAT CONSULT BY IEN RPC in JSON format.
Resolution:
The new SDEC GET PATIENT CONSULT JSON RPC was created to return the 17
key fields needed to help populate the VS GUI screens related to the
review and processing of the Consults and Procedures.
3) Jira #VSE-664 - Create Patient Search RPC to return basic Patient
information
Problem:
a) While the Passed in Social Security Number (SSN) 9N format identifier
was properly executed, those SSNs that contained Hyphens ("-") were
not being recognized properly (i.e. nnn-nn-nnnn)
b) Modification was needed to only allow four numerics (4D) to be passed
in with Alpha last name.
c) Patients with a SENSITIVE data flag were not being Masked with the
"Sensitive" message.
d) A space was missing between the type of letter and the "Letter not
ROUTINES:
defined" message.
Resolution:
a) Modifications were made to recognize the hyphen within the SSN.
b) The passing in of a format of First Alpha of Last Name concatenated
with Numerics has changed from its prior functionality. Now, only A4N
format is valid, as we have invalidated the A1N, A2N, A3N formatted
type entries.
c) Modifications were made to add the Patient Sensitivity Flag as the
8th piece of data in the returned string of the RPC SDEC GET PATIENT
=========
DEMOG.
d) Added a missing "space" in the Warning message for "letter not
defined"(i.e. from "Pre-AppointmentLetter not defined for Clinic VSE
OG CLINIC."to "Pre-Appointment Letter not defined for Clinic VSE OG
CLINIC.")
4) Jira #VSE-663 - Create new RPC in JSON format to send the list of
recalls associated with a given patient.
Problem:
|
