Cognos2 No Service or Loc in some time query: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 3: | Line 3: | ||
* let me know if shorter or longer makes more sense | * let me know if shorter or longer makes more sense | ||
}} | }} | ||
{{PAGENAME}} can be opened with the "⏱" button on the [[Main Form (CCMDB.accdb)|Main Form]]. | {{PAGENAME}} can be opened with the "⏱" button on the [[Main Form (CCMDB.accdb)|Main Form]]. | ||
Line 15: | Line 14: | ||
{{TT | | {{TT | | ||
Maybe there is a better way to do that, but I can't think of it. }} | Maybe there is a better way to do that, but I can't think of it. }} | ||
== 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. | |||
{{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" (https://ccmdb.kuality.ca/index.php?title=LastOpened_DtTm_field) 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. | |||
}} | |||
=== No solution: Exclude via "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. | |||
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. | 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. | ||
== Related articles == | == Related articles == |
Revision as of 15:19, 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.
Cognos2 No Service or Loc in some time query can be opened with the "⏱" button on the Main Form.
|
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.
Maybe there is a better way to do that, but I can't think of it. |
|
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.
No solution: Exclude via "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.
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.
Related articles
Related articles: |
|