|
|
| Line 75: |
Line 75: |
|
| |
|
| === Special Case - Erroneous Unit information in [[Cognos EPR Report]] === | | === Special Case - Erroneous Unit information in [[Cognos EPR Report]] === |
| Sometimes there are location entries in Cognos that are errors. EG. a patient may be listed as having gone to a weird unit for 5 minutes and then moved to a more reasonable one. They were probably never on that weird unit. For those cases, just exclude the location from your list so it doesn't clutter things, and don't enter this as a location.
| | See [[Process for bad data in Cognos]] |
| | |
| {{Discuss | who = Julie |
| |
| * To confirm: Julie, this means that if a pt was listed in Congos 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. [[User:Ttenbergen|Ttenbergen]] 11:00, 2020 November 18 (CST)
| |
| ** if at the beginning, then just exclude. (Julie)
| |
| ***If we ignore it if it happens at the beginning, it will mean Cognos lines that are not linked to anything. They will either clutter the screen as "not yet entered", or will need to be excluded manually by collectors. I think manually excluding them would get them off the list, but if a collector then tries to make sense of what they see the next day it will be confusing. [[User:Ttenbergen|Ttenbergen]] 11:00, 2020 November 18 (CST)
| |
| ** 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. [[User:Ttenbergen|Ttenbergen]] 11:00, 2020 November 18 (CST)
| |
| | |
| }}
| |
|
| |
|
| == Should be entered promptly == | | == Should be entered promptly == |