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 | ||
}} | }} | ||
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. | |||
{{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]]. | ||
Revision as of 21:42, 2021 January 2
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.
|
|
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.
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. |
|
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: |
|