Changeset 883 for Scheduling/trunk/m/BSDX07.m

Timestamp:

Jul 18, 2010, 7:17:02 AM (14 years ago)

Author:

Sam Habiel

Message:

edits and clean-ups prior to release, first step

File:

• Scheduling/trunk/m/BSDX07.m (modified) (3 diffs)

Scheduling/trunk/m/BSDX07.m

@@ -1 @@
-BSDX07  ; IHS/OIT/HMW - WINDOWS SCHEDULING RPCS ;  ; 7/6/10 4:28pm
+BSDX07  ; IHS/OIT/HMW - WINDOWS SCHEDULING RPCS ;  ; 7/18/10 2:11pm
         ;;2.0;IHS WINDOWS SCHEDULING;;NOV 01, 2007
+    ;
+    ; Change Log:
+    ; UJO/SMH
     ; v1.3 July 13 2010 - Add support i18n - Dates input as FM dates, not US.
         ;
@@ -50 +53 @@
         ; S %DT="T",X=BSDXEND D ^%DT S BSDXEND=Y
         ; I BSDXEND=-1 D ERR(BSDXI+1,"BSDX07 Error: Invalid End Time") Q
-        I $L(BSDXEND,".")=1 D ERR(BSDXI+1,"BSDX07 Error: Invalid End Time") Q
+    ;
+    ; If C# sends the dates with extra zeros, remove them
+        S BSDXSTART=+BSDXSTART,BSDXEND=+BSDXEND
+    ;
+    I $L(BSDXEND,".")=1 D ERR(BSDXI+1,"BSDX07 Error: Invalid End Time") Q
         I BSDXSTART>BSDXEND S BSDXTMP=BSDXEND,BSDXEND=BSDXSTART,BSDXSTART=BSDXTMP
         I '+BSDXPATID,'$D(^DPT(BSDXPATID,0)) D ERR(BSDXI+1,"BSDX07 Error: Invalid Patient ID") Q
@@ -111 +118 @@
         ;Returns ien in BSDXAPPT or 0 if failed
         ;Create entry in BSDX APPOINTMENT
-    ; BSDXSTART and BSDXEND need to be stored as numeric, not string
-    ; So 3090713.0900 is incorrect --> it should be 3090713.09
         N BSDXAPPTID
-        S BSDXFDA(9002018.4,"+1,",.01)=+BSDXSTART  ; smh fix bug stores as string
-        S BSDXFDA(9002018.4,"+1,",.02)=+BSDXEND
+        S BSDXFDA(9002018.4,"+1,",.01)=BSDXSTART
+        S BSDXFDA(9002018.4,"+1,",.02)=BSDXEND
         S BSDXFDA(9002018.4,"+1,",.05)=BSDXPATID
         S BSDXFDA(9002018.4,"+1,",.07)=BSDXRESD