| DESCRIPTION OF ENHANCEMENTS |
1) EDIS-1252 - Integrated site fix for scheduling applications.
assume the user is always at the primary site regardless of which
division the clinic they are trying to add the patient to.
Technical explanation:
--------
In the Mumps code where EDIS listens to the SDAM APPOINTMENT EVENTS
protocol for patient check-ins the site value for the check-in uses the
local variable DUZ(2). This value is from the CONNECTOREDIS proxy account
the EDIS JAVA GUI uses to add information to Vista. The problem is sites
only have one of these accounts and it is typically located in the
primary site. As the example above states if the connector proxy account
is at 561 then EDIS uses it's DUZ(2) value even for patients at 561A4.
Since the correct site code is never assigned to that patient they never
appear in the other division's display board.
Resolution:
-----------
EDIS now adds patients to sites based on the clinics location rather than
the location of the connector proxy account.
Problem:
--------
Scheduling applications Vista Scheduling Graphic User Interface (VS GUI)
and Integrated Scheduling Solution (ISS) are not supported for integrated
sites with multiple divisions by EDIS. For example, if a site like 561
has another division 561A4 it is currently not possible to add the
patient in the 561A4 site in EDIS. This happens because EDIS is coded to
|
