Changes between Version 10 and Version 11 of SchedTechManual/ServerChanges1_7

Timestamp:

Jul 10, 2012, 8:33:16 PM (12 years ago)

Author:

Sam Habiel

Comment:

--

SchedTechManual/ServerChanges1_7

@@ -24 +24 @@
  2. in PIMS, and then 
  3. run the Appointment Event driver (SDAM APPOINTMENT EVENTS in the Protocol File). This last step is the point of no return.
-If we fail in 1, we don't need to roll back anything. If we fail in 2, we need to rollback #1. If we fail in 3, we really don't have any recourse.
+If we fail in 1, we don't need to roll back anything. If we fail in 2, we need to rollback 1. If we fail in 3, we really don't have any recourse.
 For practical reasons, I decided that I will handle errors that can be reported to me (e.g. Fileman failing to store data). Mumps level errors I cannot handle gracefully; however, I put code to try to recover in certain places where I thought it would be practical to do so.
 
@@ -32 +32 @@
  * Lock node by patient ID
  * Check if appointment can be stored in PIMS if applicable (i.e. if this is a linked resource)
- * File data into ^BSDXAPPT - on failure, nothing to rollback
+ * File data into !^BSDXAPPT - on failure, nothing to rollback
  * File word processing field - no error checking is done here (easy to detect by end users if they lose data)
  * If applicable, uncancel existing appointment in file 2 (rollback: delete everything)
@@ -143 +143 @@
 
 == Other Enhancements ==
+ * As stated above, there is a fix in the Scheduling GUI C# code in v1.7 to prevent crashing if an unlinked clinic (unlinked to PIMS that is) exists. This bug was introduced in v1.6.
+ * No-show now calls the PIMS event driver.
+ * Cancel and Remove check-in check for check-out data on the PIMS appointment.
 
 == TODO ==
+ * No-show check doesn't do anything right now. It needs more coding and comparison with PIMS.
+ * PIMS lets you cancel appointments without removing the check-in (different behavior in VISTA than in RPMS!). Right now, the Scheduling GUI emulates RPMS behavior.