Using Cognos2 to keep track of patients: Difference between revisions

(7 intermediate revisions by 2 users not shown)

Line 1:

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

This page explains how the components of [[Cognos2]] should be used together to keep track of patients. Use [[Cognos downtime procedure]] when the report doesn't arrive. This is one of the [[Vacation and staff shortage collection priorities]]. The process uses definitions of the [[PatientFollow Project]] to assign workload to collectors by assigning it to their [[Laptop identifier | laptop]].

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

Line 8:

== Steps ==

~~If you come across wrong unit or service info while following the steps below, see [[Process for bad data in Cognos]].~~

=== Finding new admissions ===

Any new admission will result in a new service start. Use the [[Cognos2 Service Starter]] ([[CSS]]) to find all new admissions.

Line 24:

Line 22:

This process should also fill in the complete [[Minimal Data Set]].

* Occasionally a patient will show up on the CSS with a service date that is well before the latest COGNOS data dump. The most likely reason for this is that the patient was originally a John Doe and was given a MRN (usually beginning with 300 or 301 at HSC) that chart number is changed on discharge if the patient was identified and has a pre-existing MRN. To resolve this, and to avoid the patient being entered twice, check with your fellow DC's and confirm that it has in fact been entered and then make a decision as to who will keep the profile.

=== Exception: [[John or Jane Doe patient]] ===

Occasionally a patient will show up on the CSS with a service date that is well before the latest COGNOS data dump. The most likely reason for this is that the patient was originally a [[John or Jane Doe patient]] and was given a MRN (usually beginning with 300 or 301 at HSC) that chart number is changed on discharge if the patient was identified and has a pre-existing MRN. To resolve this, and to avoid the patient being entered twice, check with your fellow DC's and confirm that it has in fact been entered and then make a decision as to who will keep the profile. See [[John or Jane Doe patient]] for further instructions.

=== Exception: HSC IICU ===

See [[HSC_IICU_Collection_Guide#Workload_Sharing_for_HSC_IICU]]

=== Finding new unit arrivals ===

Line 46:

Line 48:

[[Category:Cognos2 | * ]]

[[Category:Cognos Report Integrator]]

@@ Line 1: / Line 1: @@
-This page explains how the components of [[Cognos2]] should be used together to keep track of patients.
+This page explains how the components of [[Cognos2]] should be used together to keep track of patients. Use [[Cognos downtime procedure]] when the report doesn't arrive. This is one of the [[Vacation and staff shortage collection priorities]]. The process uses definitions of the [[PatientFollow Project]] to assign workload to collectors by assigning it to their [[Laptop identifier | laptop]].
 Cognos2 consists of the following components that should ideally be used in the following order during a shift:
@@ Line 8: / Line 8: @@
 == Steps ==
-If you come across wrong unit or service info while following the steps below, see [[Process for bad data in Cognos]].
 === Finding new admissions ===
 Any new admission will result in a new service start. Use the [[Cognos2 Service Starter]] ([[CSS]]) to find all new admissions.
@@ Line 24: / Line 22: @@
 This process should also fill in the complete [[Minimal Data Set]].
-* Occasionally a patient will show up on the CSS with a service date that is well before the latest COGNOS data dump.  The most likely reason for this is that the patient was originally a John Doe and was given a MRN (usually beginning with 300 or 301 at HSC) that chart number is changed on discharge if the patient was identified and has a pre-existing MRN.  To resolve this, and to avoid the patient being entered twice, check with your fellow DC's and confirm that it has in fact been entered and then make a decision as to who will keep the profile.
+=== Exception: [[John or Jane Doe patient]] ===
+Occasionally a patient will show up on the CSS with a service date that is well before the latest COGNOS data dump.  The most likely reason for this is that the patient was originally a [[John or Jane Doe patient]] and was given a MRN (usually beginning with 300 or 301 at HSC) that chart number is changed on discharge if the patient was identified and has a pre-existing MRN.  To resolve this, and to avoid the patient being entered twice, check with your fellow DC's and confirm that it has in fact been entered and then make a decision as to who will keep the profile. See [[John or Jane Doe patient]] for further instructions.
+=== Exception: HSC IICU ===
+See [[HSC_IICU_Collection_Guide#Workload_Sharing_for_HSC_IICU]]
 === Finding new unit arrivals ===
@@ Line 46: / Line 48: @@
 [[Category:Cognos2 | * ]]
+[[Category:Cognos Report Integrator]]