Cognos data import: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m email now goes to Lisa, no more outlook forward from Tina |
||
Line 2: | Line 2: | ||
== Process == | == Process == | ||
[[Decision Support Services]] sends an automated email report to | [[Decision Support Services]] sends an automated email report to Lisa | ||
{{discuss | and Pagasa? [[User:Ttenbergen|Ttenbergen]] 16:18, 2024 September 4 (CDT)}} | |||
every morning. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup. | |||
=== Cognos extract via email === | === Cognos extract via email === | ||
Generally the email from [[Decision Support Services]] arrives around 7:40 +/-1hr. This can be delayed if the ETL that feeds the process is delayed. | Generally the email from [[Decision Support Services]] arrives around 7:40 +/-1hr. This can be delayed if the ETL that feeds the process is delayed. | ||
==== Process if the email does not arrive ==== | ==== Process if the email does not arrive ==== |
Revision as of 15:18, 2024 September 4
This page explains how to get data from the Cognos EPR Report into CCMDB.accdb and rolled out to collectors.
Process
Decision Support Services sends an automated email report to Lisa
and Pagasa? Ttenbergen 16:18, 2024 September 4 (CDT) |
every morning. The data is then imported into CCMDB.accdb master on Regional server and provided to collectors via regular roll-out and news and backup.
Cognos extract via email
Generally the email from Decision Support Services arrives around 7:40 +/-1hr. This can be delayed if the ETL that feeds the process is delayed.
Process if the email does not arrive
If the email has not arrived by 9:30, we contact Decision Support Services (see that page for contact info, it keeps changing).
Steps to import and roll-out
Once the email arrives each morning we run LoadCognos.bat (if the .bat isn't visible, it is the file of type "Windows Batch File"). The import and roll-out is generally done by the first of the following who is available:
What happens in the process
This information is only relevant for troubleshooting and should not usually be done manually. |
Fallback process The import can also be manually run on any computer that has CCMDB.accdb using the Cognos2_Service_Starter#Cognos_Import_Button and the data can be manually sent out to collectors following the same process as Rolling out changes. When run on Tina's computer the process will roll out any current changes in the local file; if anything was changed, update log saying it has been rolled out! |
Newly encountered units or services
If a unit or service is part of the import that is not already in our reference tables, an email will be sent to Tina and Lisa. Lisa will inform Tina what the new unit/service is about and Tina will add it to the master version of CCMDB.accdb accordingly.
Newly encountered units
Newly encountered units need to be added to the s_Cognos_Units table, see more info there about what the fields mean.
If the unit is one we collect then Level of care hierarchy needs to be determined (discuss with the Statistician if not clear) and entries need to be added to Boarding Loc and s_level_of_care table.
Newly encountered services
Newly encountered services need to be added to the s_Cognos_Services table, see more info there about what the fields mean.
If the service is one we collect then it needs to be added to Service tmp entry options.
Problem Log
This is the problem log from when the process was automated. Now that it's done manually there haven't really been problems for some time. |
The VBA logs its progress to a log file \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION\Maintenance\ccmdb_log.txt
|
Related articles
Related articles: |
|