CCMDB Wiki

PHI copy automation: Difference between revisions

← Older edit
TOstryzniuk (talk | contribs)
CCMDB_legit, approved, Bureaucrats, Administrators
27,522 edits
mNo edit summary
No edit summary
 
(37 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==What does this scheduled task do?==
We store personal health information separately from our other data. This process is par of managing that data.
As part of the [[:category:2013 data upgrades|2013 data upgrades]], [[CCMDB.mdb]] will now '''move''' the csv [[PHI Data]] files
We can't have [[PHI.mdb]] on the Regional server because too many people have access and we can't log the access.
*'''from:''' {{Regionalserver|Output\_PHI}} ''("_" to sort separate from hospitals)''
*'''to:''' <file>X:\CCMDB\PHI</file>


The move is done using a scheduled task that runs on [[Trish Ostryzniuk | Trish's]] computer. It calls <file>X:\CCMDB\PHI\copy_PHI.bat</file> (see:  [[copy_PHI.bat]]).
==Process==
* During [[sending]], [[CCMDB.accdb]] exports PHI files into {{Regionalserver|Output\_PHI}} .
* Running [[Pull]] or manually running it will run [[Copy PHI.bat]]
* [[Copy PHI.bat]] copies the files from {{Regionalserver|Output\_PHI}} to {{S:\MED\MED_CCMED}}CCMDB\PHI. Then it calls the script [[Load Data.vbs]] to integrate them into [[PHI.mdb]].
* [[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\MED_CCMED}}CCMDB\PHI\PHI Archive\ to prevent duplicate processing.  


The batch file (<file>X:\CCMDB\PHI\copy_PHI.bat</file>) has a line to call the script: 'X:\CCMDB\PHI\Load Data.vbs' which opens the PHI_Loader.accdb and 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 <file>X:\CCMDB\PHI\PHI Archive\</file> to prevent duplicate processing.
=== Running this manually ===
* navigate to {{S:\MED\MED_CCMED}}CCMDB\PHI'''
* double-click [[copy_PHI.bat]] and let it finish. May take a few (<10) minutes, depending on the build-up of files
* check/refresh {{S:\MED\MED_CCMED}}CCMDB\PHI''' to make sure no *.csv files remain in that directory
** if any are left, troubleshoot; files that remain in there have likely not been integrated into [[PHI.mdb]]
{{DT| there is a data processing instruction for this on the wiki, no time to find it right now. }}


== Future of this process ==
Depending how PHI is stored in the future, [[Re-platforming]] might make this obsolete.


'''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 [[User:Bcloutier|Bcloutier]] 19:47, 2013 November 20 (CST)
{{LegacyContent
| explanation=This used to be a scheduled, automated process, but we stopped that because we spent much time troubleshooting. It is now run as part of [push pull]] only.


==Where schedule task lives==
| content=  
[[Trish Ostryzniuk | Trish's]] desktop


==How often does it Run?==
This used to be set up as a scheduled task on the [[Data Processor PC]] before COVID. It ran the batch file [[Copy PHI.bat]] every 60 minutes. See [[Automatic updating of MS Access Databases using scheduled tasks]] for more info on how this works.


The scheduled task runs every '''10 minutes'''
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.


==Comments==
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.


Hmmm? [[Centralized data.mdb]] vs [[Aggregator.mdb]]
== If the automation were not working... ==
If the [[Data Processor PC]] that this is scheduled on isn't running (shutdown) then data might be left on the server for some time. Probably OK for now since it would still only be temporary.


== Problem ==
==If X drive goes down==
If the PC that this is scheduled on isn't running (shutdown) then data might be left on the server for some time. Probably OK for now since it would still only be temporary. Ttenbergen 16:32, 2013 July 29 (CDT)
If main office notices that X drives is down, Data processor must not remove the csv files from the Regional server until:
*currently Trish locks her computer each night and reboots it in the AM.  Locking does not stop this scheduled task from running.
* computer is rebooted and network connection to X is checked to see if it has been re established, otherwise this bat files is not able to do its job.   
*If Trish is away for 2 weeks or more then this task needs to be put on another person's desktop, either Tina, Pagasa or Julie. [[User:TOstryzniuk|Trish Ostryzniuk]] 19:16, 2014 April 23 (CDT)
**occurrence: Monday June 15.14 at 1700 hrs and all day June 16.14: issue: Catastrophic hardware failure on this network drive had occurred.
}}


== Related Articles ==
{{Related Articles}}


[[Category: 2013 data upgrades]]
[[Category:2013 data upgrades]]
[[Category:Scheduled Tasks]]
[[Category:PHI]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=PHI_copy_automation"