source: Scheduling/tag/1.7/README.txt

Last change on this file was 1729, checked in by Sam Habiel, 3 years ago

Typo

File size: 7.5 KB
Line 
1BSDX 1.7 for WorldVista
2Licensed under LGPL. http://www.gnu.org/licenses/lgpl-2.1.html
3
4
5This is a Scheduling GUI package for WorldVistA.
6
7Pre-requisites:
8FM 22 and above
9Kernel 8 and above
10XB 3 and above
11SD 5.3
12       
13SD 5.3 patch 11310 (to fix a problem with the code from the VA that IHS has fixed)
14       
15BMX 4 For a Virgin WorldVistA 6-08/3-09 release install the following kids builds in this order:
16
17                1. XB 4                 (in https://trac.opensourcevista.net/svn/IHS-VA_UTILITIES-XB/tag/rel_20091207/xb0400.k.WV.zip)
18
19                2. BMX 4              (in https://trac.opensourcevista.net/svn/BMXNET_RPMS_dotNET_UTILITIES-BMX/branch/BMX41000/kids/bmx_041000.kids)
20
21                3. XWB 1.1 patch 113102 (in https://trac.opensourcevista.net/svn/BMXNET_RPMS_dotNET_UTILITIES-BMX/tag/2.3/bmx_0230.zip)
22
23                4. BSDX 1.7                    (in https://trac.opensourcevista.net/svn/Scheduling/tag/1.7/bsdx_0170.zip)
24
25                5. SD 5.3 patch 11310   (in https://trac.opensourcevista.net/svn/Scheduling/tag/1.7/bsdx_0170.zip)
26
27
28                Client (in https://trac.opensourcevista.net/svn/Scheduling/tag/1.7/bsdx_0170.zip):
29                       
30ClinicalScheduling.exe
31                        BMXNET40.dll
32                       
33BMXWIN40.dll
34                        PrintPreview.dll
35                        To enable Arabic Support, use the ar folder's contents as is in the zip file.
36
37Client does not need installation.
38                        Both files have to be located in the same folder.
39                If BMX Server version is outdated, you need to install the new version.
40
41
42       
43-Post-installation tasks:
44After installation, complete the following tasks to configure Windows Scheduling:
45
46        1. Using VISTA tools, assign the BSDXMENU security key. All scheduling users
47must have the BSDXZMENU security key.
48
49        2. Users who are also scheduling managers must have the BSDXZMGR key
50assigned. The BSDXZMGR key permits access to the Scheduling Management
51menu in the client application. This menu supports the creation of clinics and
52clinic groups, assignment of users to clinics, designation of user access, and other management activities. For further details, see the User Manual.
53       
543. Make the BSDXPRC menu options available to scheduling users.
55These options must be somewhere in the user's path, either as a secondary option
56or as members of a menu to which the user has access.
57        4. Use Scheduling Management to configure
58a. Resources (clinics)
59b. Users to work with those clinics
60c. Resource Groups, then add the clinics to the resource groups.
61d. Access Types
62e. Access Type Groups
63(see below for more details).
64
65        5. Restart the program, and edit the resource availablility by right clicking on it in the tree.
66       
67
68
69If you don't do these steps, the program won't work.
70See the User Manual for detailed instructions.
71
72
73       
74Detailed Clinic Configuration Instructions:
75
76        The program is in a sort of an intermediate state; it doesn't edit PIMS clinics directly, but can be linked to them if you want appointments and check-ins to show up in PIMS.  This program can work without ever being linked to PIMS clinics.
77
78
79        If you need to use PIMS clinics, here is how you do the set-up:
80
81                0. First, make sure you have BSDXRPC in your menu path and that you have BSDXZMGR for Sched GUI set-up and DG SUPERVISOR TO set up PIMS clinics on roll and scroll.
82
83                1. Create the PIMS clinics using SDBUILD menu in VISTA. The GUI uses the following fields from the Hospital Location file
84 
85                        - Clinic Name
86 
87                        - Inactivation Date/Reactivation Date for deciding whether to display it.
88
89                         - Default Provider multiple for populating the default providers
90 
91                        - Division (not currently used, but will be in the future)
92
93                2. Create the resources in the GUI, and tie each of them to the clinics as needed.
94
95                3. For each resource, you need to add authorized users. These users must hold the BSDXZMENU key or else, they won't show up. You may see users with XUPROGMODE. These will always show up.
96               
974. Create Resource Groups, and add resources to them. Without this, the tree on the side won't show up; and without this tree, users cannot select a schedule.
98
99                5. Set-up At least 1 access type
100
101                6. Set-up At least 1 access group
102
103                7. Restart
104
105                8. Create slots for each of the clinics.
106                You can save them as files and re-use them.
107
108
109
110Known Bugs:
111       
112- Users booking appointments at exactly the same time for the same clinic doesn't work properly (concurrency issues).
113       
114- IDs in Scheduling GUI reflect the HRN not the Primary ID
115
116        - No handling of invalid access code when saving access slots.
117
118        - No Ctrl-C & Ctrl-V handling
119       
120- Appointment drag and drop to the same time at a different clinic doesn't work (complains that the patient already has an appointment at this time).
121       
122- Appointment drap and drop between different windows doesn't cancel the original appointment.
123       
124- Rebooking under certain conditions causes system hangs.
125
126Two issues: Program doesn't increment requested available appointment from VISTA, and doesn't deal properly with an appointment that doesn't have a access type (ie an appointment that is not in an Access block).
127
128       
129- When making a walk-in appointment, it lets you cancel check-in by pressing the cancel button, yet walk-in continues to be made.
130       
131- If user has no access to any schedules but has access to application (has BSDXZMENU key), opening the appointment menu causes a crash.
132       
133- Clipboard takes the same patient multiple times over.
134       
135- Patient search is slow with common names due to slow performance of FIND^DIC
136       
137- If DB has a deleted PIMS appointment but the BSDX appointment is still there, the appointment will not get deleted on a cancel.
138
139
140
141Other Bugs:
142Put them on the trac server where you got this software.
143
144Enhancement requests:
145       
146- Show Appointment Status in patient information windows. In other words show if the appointment is a future, checked-in, checked-out, or canceled status. (Oroville)
147       
148- Allow all users to access all clinics by default (EHS/PHH)
149
150        - Summary Schedule report based on Clinic Schedule report. Remove Phone, Address, Appointment Made By, and on fields.
151       
152- Alert user if a patient already has an appointment in the same clinic for today.
153       
154- Double-click should open make appoitment
155
156        - Double-click on appointment should edit appointment
157
158        - Make the manager for the division not for the Data Base <Najjar>
159       
160- Map the Clerks (Users) to the Groups not the clinics <Najjar>
161       
162- Add New Key to the system; allow the manager to map users to the clinics without having access to add and edit the clinics
163        - In the Re-book function; system should inform the users if there is no available clinic, not just do nothing.
164       
165- Select the provider from the Check-in option should print the provider on the routing slip (1.5: prints; but not stored in DB)
166       
167- Have an overbook limit and it can be edited as in VistA Scheduling
168       
169- Show a indicator if a patient got checked out or not.
170       
171- Generate a report from the system, tell us about the Check-in & Check-out status
172       
173- If the I close the Last Windows in the clinical Scheduling GUI the system should ask me "Are you sure to close this program?"
174
175        - If I apply a new template to the clinic the system should ask me if I want to delete the previous one
176
177        - If I inactivate the clinic in VistA it should reflects in GUI
178       
179- If we can make the users in groups. i.e. MRs group, OP clinics Group and map them to the resource groups
180       
181- Show today's column in a different color.
182       
183- Show Holiday columns in a different color.
184       
185- Be able to copy appointments in mass from one clinic to another.
186       
187- Manager functions: Send message and Shutdown sends message or shuts down all users, not just individual users.
188
189        - SMS to remind patients of appointments.
Note: See TracBrowser for help on using the repository browser.