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

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{PAGENAME}} 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.
{{PAGENAME}} 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]]. {{PAGENAME}} can be opened with the <big>⏱</big> button on the [[Main Form (CCMDB.accdb)|Main Form]].  
{{discuss |
* let me know if shorter or longer makes more sense
}}
 
{{PAGENAME}} can be opened with the <big>⏱</big> button on the [[Main Form (CCMDB.accdb)|Main Form]].
 
{{Discuss |
* I am not sure yet if there is a better way to do this where we don't need this query, so have not made it into a form where you could open the record from right there yet. If collectors find this query useful I can change that. [[User:Ttenbergen|Ttenbergen]] 20:38, 2021 January 2 (CST)}}
 
Use this to figure out if there are profiles that might have "lost touch" with [[Cognos2]].  


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 ender and keep listing, because if we did, correctly excluded records would also keep showing up in ender.
== Examples of why this might be needed ==
{{TT |
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.
Maybe there is a better way to do that, but I can't think of it. }}
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 ==
== 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. "
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. "
Line 25: Line 16:
}}
}}


=== No solution: Exclude via "exclude" button, much like on the other Cognos forms ===
=== Not a solution: Exclude via an "exclude" button, much like on the other Cognos forms ===
One suggeestion 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.  
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.  


You can't exclude a record from this query (short of entering a dispo or a new service or boarding loc if available), it is just what it is.  
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 ==  

Revision as of 15:44, 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.

  • not summarized
  • 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: