Cognos EPR Report: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 2: Line 2:


== Delays and timing ==
== Delays and timing ==
{{Collapsable | always=The data usually arrives around 9:45 | full=  
{{Collapsable | always=The data usually arrives around 9:45. If the data doesn't arrive, follow the [[Cognos downtime procedure]] | full=  
As of 2025-07-04 the extract is routinely delayed. Based on the last 50 days:
As of 2025-07-04 the extract is routinely delayed. Based on the last 50 days:
* The report itself (sender "CognosUser@REG1MSAP0160.ad.wrha.mb.ca" and Subject "Report: CCMdb Sample New Version":  
* The report itself (sender "CognosUser@REG1MSAP0160.ad.wrha.mb.ca" and Subject "Report: CCMdb Sample New Version":  

Latest revision as of 14:28, 18 August 2025

The Cognos EPR Report is a report generated for us by Decision Support Services. It is used by the Cognos Report Integrator to facilitate data entry. The data in this report feeds the Patient Viewer Tab Cognos ADT2, Cognos2 Service Starter/Cognos2 Unit Starter and Cognos2 Ender. See Using Cognos2 to keep track of patients for how they are used together.

Delays and timing

The data usually arrives around 9:45. If the data doesn't arrive, follow the Cognos downtime procedure   

As of 2025-07-04 the extract is routinely delayed. Based on the last 50 days:

  • The report itself (sender "CognosUser@REG1MSAP0160.ad.wrha.mb.ca" and Subject "Report: CCMdb Sample New Version":
    • Count: 50
    • Min time: 08:53:50
    • Max time: 11:52:50
    • Median time: 09:41:22
    • Average time: 09:52:36
  • The automated error email about the delay (sender "PIMA.Operations@gov.mb.ca" and subject "NEW: Delay in EPR data load%")":
    • Count: 19
    • Min time: 09:35:32
    • Max time: 13:04:48
    • Median time: 10:38:51
    • Average time: 10:42:27

Details

What data is included

  • The report includes unit and service info for patients who are admitted to the services we follow.
    • if new or unexpected units were to appear, they will be included automatically, we do not need to act on this
  • See Cognos Report Time Limits for the timeframe of the data.

Process to make it available to collectors

see Cognos data import

Log

  • 2025-04-25 - confirmed with Chastity that a specific new location would show up and learned that any new location showing up under a service should be included in our report automatically
  • 2025-04-01-9 dump didn't include services for new fiscal year; Chastity updated it to remove filter that caused this and this should no longer impact future fiscal year changes
  • 2025-03-11 2025-03 COGNOS crash (as per 2025-02-13 email from LK)
  • 2025-03-03 emailed LK with a tally of the increasing number of delays with the Cognos extracts; this would only have included the ones that resulted in an email from SH, there likely were additional delays in the actual email reports received
  • 2020-09-23 gender field was restored at some point
  • 2020-06-25 as of about 2 weeks ago, gender is no longer included in the data because it was breaking the export.
  • 2020-06-01 emailed to also include SBGH-A7SO and SBGH-A7WE

Related articles

Related articles: