Cognos2 Unit Starter: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) (Sounds to me like work as intended?) |
||
| Line 8: | Line 8: | ||
{{Discuss| | {{Discuss| | ||
I had an incident today where I did my CSS, and then went to do my CUS but the binoc button was linking me to an incorrect profile. On investigation, I had a patient who was discharged but hadn't yet has his dispo date/time entered, and then returned to hospital a day later. It was flagging him in CUS as a bed move to ER on his previous profile and didn't recognize that it was a new admission. Once I put in his dispo date/time he was removed from the CUS list. Is this something that can be sorted out? We do have patients that we move to ER to board before going to ICU so this can create some confusion. Sequence of button usage should be CSS then CE and then CUS until this can be sorted out. [[User:Surbanski|Surbanski]] 12:32, 2020 December 3 (CST)}} | * I had an incident today where I did my CSS, and then went to do my CUS but the binoc button was linking me to an incorrect profile. On investigation, I had a patient who was discharged but hadn't yet has his dispo date/time entered, and then returned to hospital a day later. It was flagging him in CUS as a bed move to ER on his previous profile and didn't recognize that it was a new admission. Once I put in his dispo date/time he was removed from the CUS list. Is this something that can be sorted out? We do have patients that we move to ER to board before going to ICU so this can create some confusion. Sequence of button usage should be CSS then CE and then CUS until this can be sorted out. [[User:Surbanski|Surbanski]] 12:32, 2020 December 3 (CST) | ||
** That is exactly what I would have expected to happen: a unit changed and the change was flagged. Upon review, you knew exactly what you needed to do. What is there to fix? To be clear, this change should also have shown up in [[Cognos2 Ender]] because the original service would have ended. And it should have shown (albeit as a pink plus) in CSS, because a new service would have started for the pt. Do you know if those two things happened? To summarize, I see CUS and CE as checklist generators: something needs to be done, and once it's done the record drops off the list - sounds like that happened. And yet: if you think there is something wrong with how this worked, then chances are so do at least a few other collectors. So how do we reconcile that? [[User:Ttenbergen|Ttenbergen]] 10:08, 2020 December 10 (CST) | |||
}} | |||
== Related articles == | == Related articles == | ||
Revision as of 11:08, 2020 December 10
Cognos2 Unit Starter lists new unit entries that came in on the Cognos EPR Report and matches them to the likely local record they belong to. It's part of Cognos2 and can be opened with the "CUS" button on the Main Form (CCMDB.accdb).
Cognos2 Unit Starter should be used after Cognos2 Service Starter: that one will start any new records, and most unit starts would be entered because they would show up in Patient Viewer Tab Cognos ADT2. After all has been entered in Cognos2 Service Starter, the only things that show in Cognos2 Unit Starter would be the unit starts that have happened to existing records since they were entered.
Cognos2 Unit Starter will open a patient record to the Patient Viewer Tab Cognos ADT2.
Once either a Boarding Loc entry has been created for that unit entry the line will disappear from Cognos2 Unit Starter, so this list should usually be empty when you are done.
|
|