Cognos downtime procedure: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
''Also consider [[Vacation and staff shortage collection priorities]]'' | |||
We use [[Cognos EPR Report]] data as part of [[Using Cognos2 to keep track of patients]]. This page gives explains what to do if data is not available. | We use [[Cognos EPR Report]] data as part of [[Using Cognos2 to keep track of patients]]. This page gives explains what to do if data is not available. | ||
If Cognos data is '''not available on a day''', do not enter new patients for this day. You will be able to enter them next shift. | If Cognos data is '''not available on a day''', do not enter new patients for this day. You will be able to enter them next shift. | ||
*work on finishing oldest discharge patients | *work on finishing oldest discharge patients | ||
*do NOT enter records manually | *do NOT enter records manually unless you have received an email from the main office to do so. | ||
== Why not to | == Why not to enter manually == | ||
* Risk of entering is inaccuracy and slower process. | * Risk of entering is inaccuracy and slower process. | ||
* we get a consistent [[Visit Admit DtTm]] from the import | |||
* we get [[ClientGUID field]] and [[ClientGUID field]] when we enter from COGNOS, but not when we enter manually | |||
== Why/When we might want to enter manually == | |||
* Risk of not entering is possibly idling collectors and difficulty accessing charts after discharge. | * Risk of not entering is possibly idling collectors and difficulty accessing charts after discharge. | ||
== | ==Considerations for when to eventually enter manually== | ||
* | * we need to meet process commitments: | ||
* | ** [[Project Overstay2]] commits us to provide data | ||
* we need to meet data and reporting commitments: | |||
** ??? | |||
{{DJ | Are there any ''hard'' commitments? ''Soft'' commitments? | |||
{{DiscussTask | | |||
* are there other considerations? Can we pin this down as a contingency rather than a specific number of days? | |||
* should we include an escalation path to contact | |||
== Related articles == | == Related articles == | ||
Revision as of 14:28, 18 August 2025
Also consider Vacation and staff shortage collection priorities
We use Cognos EPR Report data as part of Using Cognos2 to keep track of patients. This page gives explains what to do if data is not available.
If Cognos data is not available on a day, do not enter new patients for this day. You will be able to enter them next shift.
- work on finishing oldest discharge patients
- do NOT enter records manually unless you have received an email from the main office to do so.
Why not to enter manually
- Risk of entering is inaccuracy and slower process.
- we get a consistent Visit Admit DtTm from the import
- we get ClientGUID field and ClientGUID field when we enter from COGNOS, but not when we enter manually
Why/When we might want to enter manually
- Risk of not entering is possibly idling collectors and difficulty accessing charts after discharge.
Considerations for when to eventually enter manually
- we need to meet process commitments:
- Project Overstay2 commits us to provide data
- we need to meet data and reporting commitments:
- ???
{{DJ | Are there any hard commitments? Soft commitments?
{{DiscussTask |
- are there other considerations? Can we pin this down as a contingency rather than a specific number of days?
- should we include an escalation path to contact
Related articles
| Related articles: |