Process for bad data in Cognos

From CCMDB Wiki
(Redirected from Eyes button)
Jump to navigationJump to search

Occasionally collectors will find Service or Unit data that is wrong in Cognos Report Integrator. This page explains what to do about it.

If you find bad patient data, click the πŸ‘€ button (Eyes button) on Patient Viewer. This will start an email to #Site Contacts who will be able to do something about the underlying error.

The email will automatically contain some patient identifiers and all Service and Unit listings currently available for that pt from Cognos. Highlight the relevant one and then send off the email.

The button will also create a Project CognosDataEmail entry in the tmp data for the profile.

Once the email is sent, move on to another patient. With some luck either you will get an answer to the email with new info, or the data will then be correct in Cognos the next day. We will need to see to what degree the sites will collaborate with us on this.

Interro-01.gif
  • should we exclude and overcome the bad records right away or wait for a correction that might never come and how would we keep track of it?
  • SMW


  • Cargo


  • Categories
Discuss@task.png

AJTT

  • To confirm: Julie, this means that if a pt was listed in Cognos as some bogus unit for the first 6 hours of their stay, we would list their stay on our unit as starting 6 hours later. this would probably trigger some of Pagasa's cross checks, and give you 6 hours of missing occupancy. I still think it's the right way to deal with this error since messing with the times would break how entries are linked to Cognos, but I want to make sure we are all aware that this is a thing and how we approach it. Ttenbergen 13:29, 2020 November 9 (CST)
    • when does this phenomenon occur - at the beginning or in between transfers? (Julie)
      • It seems to be a matter of data entry errors, so I suppose it can occur at any time. Ttenbergen 11:00, 2020 November 18 (CST)
    • if at the beginning, then just exclude. (Julie)
    • If in between transfers during an episode, is there a query done for that? Pagasa' query will crosschecks between records and not within episode. But if that happens, since only the arrived date is entered, I will always assume continuous stay defining the end date as the start date of the next boarding location. (julie)
      • Not sure what kind of query you have in mind. We only collect the unit starts, so there are no unit ends to cross check against. This means we should define how to enter these "bogus" units as either including them with the previous or including them with the next unit. I would prefer including them with previous because it doesn't break linking with Cognos for the next unit. But we should have a consistent instruction for this.Ttenbergen 14:10, 2021 January 28 (CST)
  • SMW


  • Cargo


  • Categories


Todo.svg

Swiss Army Knife.svg

This page has an evil twin, need to integrate it here: Wrong service or unit entries in Cognos.

  • added: no added date
  • action: no action date
  • Cargo


  • Categories

Examples of bad data

  • Extra entries - Service or unit entries in Cognos that never happened; likely examples would be service listings that are 1 minute long; a common scenario for these would be where a service or unit was entered accidentally and then corrected not using the proper procedures. Apparently if the proper procedures are used these lines will not show up.
  • Wrong times - service or unit date and times that are clearly wrong when you review other notes
    • a scenario that would cause this is a pt move being entered by a unit so they can generate an addressograph

Site Contacts

  • STB
    • Jamie Talbot and Caroline Deerpalsing
  • HSC
Poindexter.jpg
  • who would this be?
  • SMW


  • Cargo


  • Categories
  • GRA
Poindexter.jpg
  • who would this be?
  • SMW


  • Cargo


  • Categories

Related articles

Related articles: