| DESCRIPTION OF ENHANCEMENTS |
1) EDIS-1285: INC38814644 - EDIS Vitals saves incorrect time zone.
Resolution:
----------
The current time was passed from the web server to VistA using Java's
date/time method which would then store that value in VistA. Now the
application does not use the Java date/time but instead uses VistA's
$$NOW^XLFDT Application Programming Interface (API) call which will
provide the time at that selected site. The time zone stamp on the vitals
was removed in EDP*2*41 because there is no mechanism currently for EDIS
to know what time zone the selected site belongs to.
2) EDIS-1348: INC39251650 - Tracking Code does not update in VistA.
Problem:
--------
When changing the name of the Status in EDIS under Configure > Selections
> Status, the name updates in the Selections page and on the CPE screen.
The new name of the Status does not update in the TRACKING CODE file
(#233.1). The new name is also not visible in the Configure > Colors
page. This appears to be an issue with all tracking codes -- dispositions,
delays, etc.
Problem:
Resolution:
-----------
When EDIS saves the updates on the Configure page the backend VistA code
does not update the TRACKING CODE file. This VistA code has been updated
to save changes to the TRACKING CODE file and to display the changes
correctly in EDIS for any non-national code.
3) EDIS-1459: INC39876676 - EDIS creates duplicate encounters when a
historical visit is entered in the ER clinic.
--------
Problem:
--------
The site uses a Computerized Patient Record System (CPRS) note as a warm
hand-off when a patient is coming to the ER from another clinic or
hospital location. The CPRS note is created as historical and linked to
the ER clinic. This creates a historical encounter in the Patient Care
Encounter (PCE) package. The note alerts the ER staff of the
incoming patient. Once the patient enters the ER, the ER staff create an
appointment for the patient putting the patient on the EDIS board. A nurse
When adding vitals to a patient in EDIS the timestamp always displays
is assigned the patient in EDIS. EDIS checks the PCE package for existing
encounters and finds the historical encounter. Encounter data (nurse
assignment) cannot be added to historical encounters so a new encounter
is created by EDPF Tracking System using the same date/time of the
encounter. Now there are 2 selectable visits in CPRS, one for the
scheduled appt and one for the EDIS created encounter. When users select
the correct scheduled appointment and link their notes to it in CPRS, it
creates a second encounter with the appt date/time.
Resolution:
central time regardless of where the site is located. This is because
-----------
When EDIS is checking for a previous visit it will now ignore those
marked as "historical".
EDIS currently uses the time zone from the web server which is located in
the central time zone.
|
