Cognos data import: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (Text replacement - "Sub CognosImport" to "Function CognosImport")
 
(13 intermediate revisions by 2 users not shown)
Line 2: Line 2:


== Process ==
== Process ==
Tina receives the data in a scheduled, automated email from [[Chastity]] every morning as early as possible, usually before 8. The data is then imported into [[CCMDB.accdb]] master on Regional server and provided to collectors via regular roll-out and news and backup.
[[Decision Support Services]] sends an automated email report to Tina 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.


=== Outlook Rule in Tina's profile to get data to Pagasa ===
=== Cognos extract via email ===
Decision Support Services sends a report to Tina. The report needs to go to Pagasa so we can schedule the automated import on a machine that sits on WRHA network at all times. So, there is an outlook rule "Cognos to Pagasa" in Tina's Outlook profile to forward the email to Pagasa from [[Chastity]].  
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.  


=== Scheduled Task on Pagasa's PC ===
=== Outlook Rule in Tina's profile to get data to Pagasa and Lisa ===
There is a scheduled task on Pagasa's PC that calls [[LoadCognos.bat]] early each morning.
Decision Support Services emails a report to Tina. The report needs to go to Pagasa and Lisa so it can be imported and rolled out; this is accomplished by outlook rule "Cognos to Pagasa" in Tina's Outlook.
 
==== 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:
# [[Database Manager]]
# [[Data Processor]]
 
==== What happens in the process ====
{{Collapsable | always=This information is only relevant for troubleshooting and should not usually be done manually. | full=
* [[LoadCognos.bat]] calls
* [[LoadCognos.bat]] calls
* [[LoadCognos.vbs]] which calls  
* [[LoadCognos.vbs]] which calls  
Line 14: Line 26:
* process then returns to [[LoadCognos.bat]] which copies [[CCMDB.accdb]] to the [[Regional Server]] and then calls [[Updt all.bat]] to [[Rolling out changes | roll it out]] to all collectors
* process then returns to [[LoadCognos.bat]] which copies [[CCMDB.accdb]] to the [[Regional Server]] and then calls [[Updt all.bat]] to [[Rolling out changes | roll it out]] to all collectors


==== Fallback process ====
'''Fallback process'''
The import can also be manually run on any laptop 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]].  
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! '''
'''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 ===
=== Newly encountered units or services ===
If a unit is encountered that isn't in [[s_Cognos_Units table]], an email will be sent to Tina and Herman. One of them will contact a data collector at the site where the new unit appeared to find out whether this is a unit we collect.
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.
Regardless whether we collect the new unit, the new unit then needs to be added to [[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 Julie if not clear) and entries need to be added to [[Boarding Loc]] and [[s_level_of_care table]].  
==== 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.  


=== newly encountered services ===
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]].  
If a service is encountered that isn't in [[S Cognos Services table]] an email will be sent to Tina and Herman. One of them will contact a data collector at the site where the new service is located to find out if this is a service we collect.  


Regardless whether we collect the new unit, the new service needs to be added to [[s_Cognos_Services table]], see more info there about what the fields mean.
==== 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.
If the service is one we collect then it needs to be added to [[Service tmp entry]] options.
== Known problems with data import ==
=== Shared Health Re-boots ===
The task requires the user be logged in. If Shared Health re-boots the computer over night, the task won't run until Pagasa logs on.
=== [[CFE]] or [[TISS28.accdb]] left open on Pagasa's PC ===
'''[[CFE]] and [[TISS28.accdb]] needs to be closed at the end of the work day on Pagasa's computer.''' The update process needs to download the newest version of [[CCMDB.accdb]] from the [[Regional Server]] before it runs so that it doesn't overwrite the master version with an older version from Pagasa's PC. This download of the newest version is blocked when [[CFE]] is open.


== Problem Log ==
== Problem Log ==
{{Collapsable
| always= 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.
| full=
The VBA logs its progress to a log file \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION\Maintenance\ccmdb_log.txt
The VBA logs its progress to a log file \\ad.wrha.mb.ca\wrha\REGION\Shared\ICU_DATA_COLLECTION\Maintenance\ccmdb_log.txt


* 2021-03-04 - Pagasa provided screen shot of error "Error in sub notify_about_new_Congos: The operation failed. The messaging interfaces have rerutned an unknown error. If the problem persists, restart Outlook. - -2147467259"
* 2021-03-04 - Pagasa provided screen shot of error "Error in sub notify_about_new_Congos: The operation failed. The messaging interfaces have rerutned an unknown error. If the problem persists, restart Outlook. - -2147467259"
** This happened when PC was rebooted at the end of the day before, locked in and then left like that over night.  
** This happened when PC was rebooted at the end of the day before, locked in and then left like that over night.  
{{Collapsable
| always= detailed log
| full=
*'''2020-Nov-10''' - email was delayed to 9:17, then rolled out ok
*'''2020-Nov-10''' - email was delayed to 9:17, then rolled out ok
*'''2020-Nov-09''' - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back
*'''2020-Nov-09''' - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back

Latest revision as of 09:13, 2023 September 27

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 Tina 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.

Outlook Rule in Tina's profile to get data to Pagasa and Lisa

Decision Support Services emails a report to Tina. The report needs to go to Pagasa and Lisa so it can be imported and rolled out; this is accomplished by outlook rule "Cognos to Pagasa" in Tina's Outlook.

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:

  1. Database Manager
  2. Data Processor

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

  • 2021-03-04 - Pagasa provided screen shot of error "Error in sub notify_about_new_Congos: The operation failed. The messaging interfaces have rerutned an unknown error. If the problem persists, restart Outlook. - -2147467259"
    • This happened when PC was rebooted at the end of the day before, locked in and then left like that over night.
  • 2020-Nov-10 - email was delayed to 9:17, then rolled out ok
  • 2020-Nov-09 - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back
  • 2020_Oct_23 - Chastity report came late @ 08:46, Run manually cognos.
  • 2020_Oct_21 - Chastity email -ETL failed last night so there will be no report today. No new cognos.
  • 2020_Oct_9 - task was stuck because CFE was open
  • 2020_Oct_8 - Task schedule did not run because computer were rebooted by EHealth overnight.
  • Pagasa changed the Task schedule so it does not run on weekends. Concern will be this long weekend and the task may hang because data from email not deleted before it runs on Tues AM.
  • 2020-Oct-6 & 7 - Tuesday - ran at 0740. No issues.

Related articles

Related articles: