Cognos2 No Service or Loc in some time query: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 13: Line 13:


{{Discuss |  
{{Discuss |  
* Exclude via [[LastOpened DtTm field]] - We would need to define what that means, from a data perspective. The easiest would be to include the "LastOpened_DtTm"  that is set when the "Close - WITH updates" button is used. But I have  no idea how and if people are using those buttons consistently, so we would need to make sure of that. I set that up in 2016, but it was never something we pushed people to use. Part of the problem is, I am not sure when people would use the "with" and when the "no" button. Initially the "no" button was meant to address datestamps that happened when e.g. another collector would check the first collector's laptop for an admit or dispo time. I think that sort of thing no longer happens with Cognos, but am not at all sure. Maybe I should re-name these "with review" rather than "with update"; that would make it usable for this list. '''Collectors, please update
* Exclude via [[LastOpened DtTm field]] which is set by either of the [[Close - WITH or NO Updates buttons]].  
}}
}}



Revision as of 22:42, 2021 January 6

Cognos2 No Service or Loc in some time query is used as part of Using Cognos2 to keep track of patients to list profiles where the most recent Service tmp entry or Boarding Loc entry is more than 14 days old. Use this to figure out if there are profiles that might have "lost touch" with Cognos2. Cognos2 No Service or Loc in some time query can be opened with the button on the Main Form.

Examples of why this might be needed

Generally, between CSS, CE and CUS, all profiles should consistently get listed as things change. However, some known (and maybe other unknown) scenarios could cause a record to get missed by these Cognos tools. One way a record could loose touch is if e.g. a service was entered with a time other than the time listed in Cognos, and the record was excluded to get it off the list. Such a record would not then show up in Cognos Ender because it was excluded. And we can't just ignore exclusions in CE and keep listing, because if we did, correctly excluded records would also keep showing up in CE.

Suggested improvements

Button to open records right from this screen

Tina says: "I plan to turn this into a form with a button to open the records directly, just wanted to get the first round of tweaking done before. Once I make a form where I can add a button to open I will always have to edit two things, and then one gets missed. "

Profiles with a legitimate long time since last change

Of course a profile might legitimately not have service or unit changes in 14 days, but presumably you could identify those legit ones e.g. from their Record entry.

  • SMW


  • Cargo


  • Categories

Not a solution: Exclude via an "exclude" button, much like on the other Cognos forms

One suggestion was to add an exclude button. The problem with an exclude is that it would forever exclude them. And that would not be the point, the idea is that this list will flag records that might have gone stale. So it would have to me more something like a "snooze" button, and that would already be accomplished by using the Last Opened DtTm.

The problem with an "exclude" in this scenario is that it would forever exclude the profile. And that would not be the point, the idea is that this list will flag records that might have gone stale. So it would have to me more something like a "snooze" button, and that would already be accomplished by using the LastOpened DtTm field, so another "exclude" list should not be necessary.

Related articles

Related articles: