Changes between Version 3 and Version 4 of SchedTechManual/ServerChanges1_7

Timestamp:

Jul 10, 2012, 2:50:47 PM (14 years ago)

Author:

Sam Habiel

Comment:

--

SchedTechManual/ServerChanges1_7

@@ -17 +17 @@
 
 Due to all of these reasons, I decided to completely remove Mumps Transactions from the Scheduling GUI code.
+
 == Summary of Work ==
 6 routines had to be changed: BSDX07, BSDX08, BSDX25, BSDX26, BSDX29, BSDX31.
@@ -26 +27 @@
 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.
 
+== Individual Routines ==
+=== BSDX07 (Make appointment) ===
+Workflow:
+ * 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 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)
+ * OR Add a new appointment to file 2 (rollback: delete everything)
+ * Add the appointment time to file 44 appointment subfile (rollback: delete everything)
+ * Add the patient to the file 44 patient subsubfile under the appointment subfile. (rollback: delete everything)
+ * Update availablities (global sets only)
+ * Call event driver
+
+Rollback strategy: Difficult because of all the different possible failure points. Delete all appointments from all files.
+
+M Error handling: Delete all appointments where possible.
+
+Limitations of Rollback: 
+If the patient has a previous appointment in 2 and an error happens in storing the new appointments, the old appointment is deleted. From $$UNMAKE^BSDXAPI:
+{{{
+    ; TODO: If Patient Appointment previously existed as cancelled, it's removed.
+    ; How can I tell if one previously existed when data is in an intermediate  
+    ; State? Can I restore it if the other file failed? Restoration can cause   
+    ; another error. If I restore the global, there will be cross-references    
+    ; missing (ASDCN specifically).                                             
+}}}
+=== BSDX08 (Cancel appointment) ===
+Workflow:
+ * Lock appointment
+ * Check if appointment can be cancelled in PIMS
+ * Add cancellation data in ^BSDXAPPT (rollback: none needed on failure)
+ * Cancel appointment in 2 (rollback: remove cancellation data)
+ * Delete appointment in 44 (no error detection as Fileman is not expected to fail)
+ * Update availabilities (Global sets only)
+ * Call event driver (point of no return)
+
+Rollback strategy: it's easier than BSDX07 because there is only one point at which we can fail after we put data into the system. Rollback removes cancellation data from ^BSDXAPPT.
+
+M Error Handling: Same as rollback.
+
+Limitations of Rollback: If an M error occurs in the event driver, I do not uncancel in file 2 and restore the entry in file 44.
+== Unit Test Routines ==
+
+== Other Enhancements ==
+
+== TODO ==