Decision Support Services: Difference between revisions

m Text replacement - "[[Category: " to "[[Category:"
No edit summary
Line 1: Line 1:
Decision Support Services is a department within Shared Health that makes available data for analysis and reporting purposes. They provide the [[Cognos EPR Report]].  
Decision Support Services is a department within Shared Health that makes available data for analysis and reporting purposes. They provide the [[Cognos EPR Report]].  


== Contact ==
== [[Cognos EPR Report]] troulbeshooting ==
If there is a problem with the data, email
If there is a problem with the [[Cognos EPR Report]], email
:: <code>data@wrha.mb.ca; PIMA@gov.mb.ca</code>
:: <code>data@wrha.mb.ca; PIMA@gov.mb.ca</code>
and tell them the problem (no report, old data, ...). Reference the following:  
and tell them the problem (no report, old data, ...). Reference the following:  
Line 10: Line 10:


Our contact used to be '''Chastity Cleofas''', but she no longer works there.  <!-- please leave this in so we can find this via search for "Chastity" --> She still works elsewhere in Shared Health and has been helpful with questions at times, but shouldn't be the primary contact any longer. However, when it comes to actually updating and troubleshooting the report, including her in conversations early can speed things up.
Our contact used to be '''Chastity Cleofas''', but she no longer works there.  <!-- please leave this in so we can find this via search for "Chastity" --> She still works elsewhere in Shared Health and has been helpful with questions at times, but shouldn't be the primary contact any longer. However, when it comes to actually updating and troubleshooting the report, including her in conversations early can speed things up.
=== Background ===
Our email is sent through report schedule automation. This is set for a specific time of day, and it also triggers an email to DSS so they know if it stops running.
One source of failure: "the behind-the-scenes trigger for this report schedule fired about ten minutes after the report schedule stopped checking for the trigger.  The report waits for this trigger because the trigger only fires after all of the EPR data updating is completed"; if the ETL that provides our data is delayed past the end of the schedule window, our email won't get sent. PIMA increased this window to make the scheduled report more resilient.


== Related articles ==  
== Related articles ==