PHI copy automation: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "Transition to Database Server" to "Re-platforming"
m Text replacement - "X:\" to "{{S:\MED\CCMED}}"
 
Line 11: Line 11:
Every 60 minutes it runs the batch file [[Copy PHI.bat]].
Every 60 minutes it runs the batch file [[Copy PHI.bat]].


It copies the PHI files exported by [[CCMDB.accdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to  X:\CCMDB\PHI. Then it calls the script [[Load Data.vbs]].
It copies the PHI files exported by [[CCMDB.accdb]] during [[sending]] to {{Regionalserver|Output\_PHI}} to  {{S:\MED\CCMED}}CCMDB\PHI. Then it calls the script [[Load Data.vbs]].


The script [[Load Data.vbs]] accesses [[PHI Loader.accdb]] and runs the sub ''loadAllCSVFiles'', which calls the code that imports all csv files found within the directory.  The csv loading code also moves the files again into an archive folder X:\CCMDB\PHI\PHI Archive\ to prevent duplicate processing. See [[Automatic updating of MS Access Databases using scheduled tasks]] for more info on how this works.
The script [[Load Data.vbs]] accesses [[PHI Loader.accdb]] and runs the sub ''loadAllCSVFiles'', which calls the code that imports all csv files found within the directory.  The csv loading code also moves the files again into an archive folder {{S:\MED\CCMED}}CCMDB\PHI\PHI Archive\ to prevent duplicate processing. See [[Automatic updating of MS Access Databases using scheduled tasks]] for more info on how this works.


'''If the task runs and there are no problems the task will list "0x0" in the last results column. Any other code would require review.''' - This needs to be reviewed as the last line of the batch file has changed the the return value may be altered  
'''If the task runs and there are no problems the task will list "0x0" in the last results column. Any other code would require review.''' - This needs to be reviewed as the last line of the batch file has changed the the return value may be altered  

Latest revision as of 17:18, 18 March 2025

Legacy Content

This page contains Legacy Content.

  • Explanation: This process would lock up occasionally preventing collectors from sending. So, we stopped the scheduled task that ran this every 5 minutes. We were initially going to review this to make it work again, but with COVID a desktop scheduled task became entirely impractical anyway. As of 2022-08 we are hoping for Shared Health to provide either interim functionality on the Automation PC or maybe an actual solution to our storage requirements that doesn't need this. See also Re-platforming.
  • Successor: No successor was entered

Click Expand to show legacy content.