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

From CCMDB Wiki
Jump to navigation Jump to search
m
 
Line 7: Line 7:
= Suggested improvements =
= Suggested improvements =
== Button to open records right from this screen ==
== Button to open records right from this screen ==
{{TT |
{{DiscussTask|
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. "
* Are people using this? Would it be worth having a button to open the record directly from the query screen? Would take about 30 min to set up...  
}}
}}



Latest revision as of 20:18, 2021 August 3

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 28 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 CE 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

Discuss@task.png
  • Are people using this? Would it be worth having a button to open the record directly from the query screen? Would take about 30 min to set up...
  • SMW


  • Cargo


  • Categories

Profiles with a legitimate long time since last change

Of course a profile might legitimately not have service or unit changes in 28 days, so the LastOpened DtTm field is also included to keep track of when records were last reviewed.

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.

Log

2021-04-06 increased threshold from 14 to 28 days

Related articles

Related articles: