Cognos2 Service Starter: Difference between revisions

(23 intermediate revisions by 3 users not shown)

Line 5:

Use this to figure out which service records in Cognos don't have an entry on your laptop yet, and to start an entry for it. '''Lines with a white plus don't have a profile for this pt on this laptop yet. Lines with a pink plus already have a record, but may need a new one or a new [[Service tmp entry]].

Use the O ~~and~~ + ~~buttons~~ to ~~open resp.~~ add records. Meanings of colours are at the bottom of the screen. The buttons will open the record to the [[Patient Viewer Tab Cognos ADT2]], where other service or unit entries for that record can then be entered.

Use the O button to open or the + button to add records. Meanings of colours are at the bottom of the screen. The buttons will open the record to the [[Patient Viewer Tab Cognos ADT2]], where other service or unit entries for that record can then be entered.

=== Exclusions ===

We receive some data ~~that doesn~~'t ~~really apply to us~~. You can remove it from CSS by clicking the [["exclude" button]] on that line to remove a single service/time combination; if the same pt shows up again for the same service with a different time later, a new line will show (i.e. excluding a patient once doesn't mean they will never show up again).

We receive some data for services which we don't collect. You can remove it from CSS by clicking the [["exclude" button]] on that line to remove a single service/time combination; if the same pt shows up again for the same service with a different time later, a new line will show (i.e. excluding a patient once doesn't mean they will never show up again).

You can click on the chart number field of an entry to see exclusions that have been set for this MRN. If a line was excluded accidentally, you can delete it from the exclusions and it will show up again in CSS if it is still in the most recent Cognos dump.

Use the [["View exclusions" button]] to see all lines that have been excluded, i.e. including lines for which there is not currently a record in the cognos dump; this is by hospital MRN so search/filter with that.

=== Why does this not contain unit info? ===

Line 19:

=== Which lines in CSS require action ===

'''''All''''' lines in CSS require action. See [[Using Cognos2 to keep track of patients]].

* when a patient is transferred to one of our units, ideally the first service and first [[boarding Loc]] should be the same date and time. However, often they are not. In these cases, always use the first service entry line as the date and time for first service and first [[boarding Loc]]. (make a note in the notes field to change to the first [[Boarding Loc]] date and time at a later date when reviewing the chart)

*example- patient transfers from ICU to medical unit. first medicine service=May10@1400, First boarding loc=May10@1630. While the correct first service and first [[Boarding Loc]] should be May 10@1630, enter the first service date and time from COGNOS for both first service and first [[boarding Loc]] (May 10@1400). There are two reasons for this; if you change the first service date and time without excluding that service it will fill up your CSS and you will not get the associated service end date and time. If you exclude that service entry all together than you will also not get the associated service end date and time.

~~{{Discuss| Does~~ the ~~above "exception" only apply to ICU patients transferring to med? Are there implications for patients admitted while in ER? Should collectors not be excluding incorrect~~ service ~~entries while patient is in ER ie first service is listed as surgery~~, ~~cardiology~~, ~~family med~~, ~~etc. and make notes for changes to be made later? Or is~~ the ~~current collection method ie. changing of the boarding location to match~~ the ~~correct first service~~ date/time ~~and excluding incorrect service entries continued for patients admitted while in ER? This~~ may ~~cause confusion for new collectors, even current collectors so collection instructions need to be clear to ensure consistent entry. Thanks~~, [[~~User:Ppiche|Pamela Piche~~]] ~~08:09, 2022 May 19 (CDT)~~

* for services that we really don't collect, '''exclude''' the service (e.g. Family medicine, STB Internal Med/Respiratory, Cardiology)

* for services that we do collect, enter the service as listed with the date and time as listed; this may get changed later, see [[Service tmp entry]] and [[DtTm for First Boarding Loc and First Service]] for details

~~What if collectors forget to include reminder notes? Will this create a necessity for collectors to review all service entries during profile completion? Some profiles have up to seven service entries~~ and makes for extra work to review to ensure accuracy. It would appear there is now more than one process to manage cognos entries by collectors, is this setting collectors up for entry errors? Does this complicate cross coverage? [[~~User:Ppiche|Pamela Piche~~]] 08:~~25, 2022 May 19 (CDT) }}~~

=== "Show records on laptop with same chart number" button ===

Line 33:

Line 30:

=== Cognos Import Button ===

There is a button in the top right corner of CSS that allows anyone who has the Cognos data email to import it. There is no process for this yet, and it will generally not work for collectors. It's just a contingency tool for now.

There is a button in the top right corner of CSS that allows anyone who has the Cognos data email to do a [[Cognos data import]]. There is no process for this yet, and it will generally not work for collectors. It's just a contingency tool for now.

== Related articles ==

@@ Line 5: / Line 5: @@
 Use this to figure out which service records in Cognos don't have an entry on your laptop yet, and to start an entry for it. '''Lines with a white plus don't have a profile for this pt on this laptop yet. Lines with a pink plus already have a record, but may need a new one or a new [[Service tmp entry]].
-Use the O and + buttons to open resp. add records. Meanings of colours are at the bottom of the screen. The buttons will open the record to the [[Patient Viewer Tab Cognos ADT2]], where other service or unit entries for that record can then be entered.
+Use the O button to open or the + button to add records. Meanings of colours are at the bottom of the screen. The buttons will open the record to the [[Patient Viewer Tab Cognos ADT2]], where other service or unit entries for that record can then be entered.
 === Exclusions ===
-We receive some data that doesn't really apply to us. You can remove it from CSS by clicking the [["exclude" button]] on that line to remove a single service/time combination; if the same pt shows up again for the same service with a different time later, a new line will show (i.e. excluding a patient once doesn't mean they will never show up again).
+We receive some data for services which we don't collect. You can remove it from CSS by clicking the [["exclude" button]] on that line to remove a single service/time combination; if the same pt shows up again for the same service with a different time later, a new line will show (i.e. excluding a patient once doesn't mean they will never show up again).
 You can click on the chart number field of an entry to see exclusions that have been set for this MRN. If a line was excluded accidentally, you can delete it from the exclusions and it will show up again in CSS if it is still in the most recent Cognos dump.
 Use the [["View exclusions" button]] to see all lines that have been excluded, i.e. including lines for which there is not currently a record in the cognos dump; this is by hospital MRN so search/filter with that.
 === Why does this not contain unit info? ===
@@ Line 19: / Line 19: @@
 === Which lines in CSS require action ===
 '''''All''''' lines in CSS require action. See [[Using Cognos2 to keep track of patients]].
-* when a patient is transferred to one of our units, ideally the first service and first [[boarding Loc]] should be the same date and time.  However, often they are not.  In these cases, always use the first service entry line as the date and time for first service and first [[boarding Loc]].  (make a note in the notes field to change to the first [[Boarding Loc]] date and time at a later date when reviewing the chart)
-*example- patient transfers from ICU to medical unit.  first medicine service=May10@1400, First boarding loc=May10@1630.  While the correct first service and first [[Boarding Loc]] should be May 10@1630, enter the first service date and time from COGNOS for both first service and first [[boarding Loc]] (May 10@1400).  There are two reasons for this; if you change the first service date and time without excluding that service it will fill up your CSS and you will not get the associated service end date and time. If you exclude that service entry all together than you will also not get the associated service end date and time.
-{{Discuss| Does the above "exception" only apply to ICU patients transferring to med? Are there implications for patients admitted while in ER? Should collectors not be excluding incorrect service entries while patient is in ER ie first service is listed as surgery, cardiology, family med, etc. and make notes for changes to be made later? Or is the current collection method ie. changing of the boarding location to match the correct first service date/time and excluding incorrect service entries continued for patients admitted while in ER? This may cause confusion for new collectors, even current collectors so collection instructions need to be clear to ensure consistent entry. Thanks, [[User:Ppiche|Pamela Piche]] 08:09, 2022 May 19 (CDT)
+* for services that we really don't collect, '''exclude''' the service (e.g. Family medicine, STB Internal Med/Respiratory, Cardiology)
+* for services that we do collect, enter the service as listed with the date and time as listed; this may get changed later, see [[Service tmp entry]] and [[DtTm for First Boarding Loc and First Service]] for details <!-- if this changes, make sure the new instructions are consistent with https://ccmdb.kuality.ca/index.php?title=DtTm_for_First_Boarding_Loc_and_First_Service -->
-What if collectors forget to include reminder notes? Will this create a necessity for collectors to review all service entries during profile completion? Some profiles have up to seven service entries and makes for extra work to review to ensure accuracy.  It would appear there is now more than one process to manage cognos entries by collectors, is this setting collectors up for entry errors? Does this complicate cross coverage? [[User:Ppiche|Pamela Piche]] 08:25, 2022 May 19 (CDT)  }}
 === "Show records on laptop with same chart number" button ===
@@ Line 33: / Line 30: @@
 === Cognos Import Button ===
-There is a button in the top right corner of CSS that allows anyone who has the Cognos data email to import it. There is no process for this yet, and it will generally not work for collectors. It's just a contingency tool for now.
+There is a button in the top right corner of CSS that allows anyone who has the Cognos data email to do a [[Cognos data import]]. There is no process for this yet, and it will generally not work for collectors. It's just a contingency tool for now.
 == Related articles ==