Using Cognos2 to keep track of patients: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
m (→‎Steps: removed addressed question from 2 weeks ago.)
Line 8: Line 8:


== Steps ==
== Steps ==
{{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)
** 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)
*** After further discussion with GRA med, they confirmed that there are two parts to this:
****(1) There is a best order in which to use the Cognos2 tools. That order should now be reflected on this page, if it's not, please help me get it right
****(2) It is still difficult to see which "peach" pluses in [[CSS]] are for a record that needs attention, and which ones are for a record that is already entered. Tina is working on that, see [[Cognos2_Service_Starter#Problem%3A_which_peach_pluses_require_action]] for specific info.
*** If (1) is addressed here, and (2) is addressed at [[Cognos2_Service_Starter#Problem%3A_which_peach_pluses_require_action]], and between the two they really do describe what is going on, then please clear out of this discussion what is no longer relevant. [[User:Ttenbergen|Ttenbergen]] 14:05, 2020 December 15 (CST)
}}


=== Finding new admissions ===
=== Finding new admissions ===

Revision as of 17:34, 2020 December 31

This page explains how the components of Cognos2 should be used together to keep track of patients.

Cognos2 consists of the following components that should ideally be used in the following order during a shift:

All of these open to Patient Viewer Tab Cognos ADT2.

Steps

Finding new admissions

Any new admission will result in a new service start. Use the Cognos2 Service Starter to find all new admissions. Records that have been added show up green, records that have not yet been added show up white. Enter all new records, including records where the patient is still in the ER (i.e. not clear yet if they will ever reach a unit or become what we used to think of as an EMIP / ECIP). When you enter a record, it opens in Patient Viewer Tab Cognos ADT2 where you can also enter any other services and units that patient is listed for in the Cognos data.

Finding new unit arrivals

Patients who are already entered and have changed location after admission can be found on the Cognos2 Unit Starter. This would catch any patients that were still in the ER when they were processed in Cognos2 Service Starter. You can open patients from here to enter the unit, and to make any required changes to the Record field. Once a corresponding entry exists in Boarding Loc the record will disappear off the Cognos2 Unit Starter.

Finding discharges

Use Cognos2 Ender to find either discharges or changes to another service. Use it to find all records that have a service ending time that doesn't have either a matching Dispo entry or a matching new Service tmp entry; once one of those is entered the record will disappear from this list.

Finish older records

Use Patient List as before to work through entering and sending discharged patients you were not just able to finish off on initial review.

Limits

Background

We initially were trying to do this with Cognos Report Integrator / Using Cognos Report Integrator to keep track of patients but the format of the data was hard to use, so this replaces it.

Left to do

  • Phase out the old forms.
  • clean out the old instructions
  • added: no added date
  • action: no action date
  • Cargo


  • Categories

Related articles

Related articles: