Using Cognos2 to keep track of patients - Revision history

Ttenbergen: /* Related articles */

2025-12-24T18:28:21Z

← Older revision		Revision as of 13:28, 24 December 2025
Line 49:		Line 49:
	[[Category:Cognos2 \| * ]]		[[Category:Cognos2 \| * ]]
	[[Category:Cognos Report Integrator]]		[[Category:Cognos Report Integrator]]
			[[Category:PatientFollow Project]]

Ttenbergen at 23:09, 27 November 2025

2025-11-27T23:09:49Z

← Older revision		Revision as of 18:09, 27 November 2025
Line 1:		Line 1:
	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 \|~~Laptops/collectors~~]].		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:		Cognos2 consists of the following components that should ideally be used in the following order during a shift:

Ttenbergen at 23:09, 27 November 2025

2025-11-27T23:09:19Z

← Older revision		Revision as of 18:09, 27 November 2025
Line 1:		Line 1:
	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]].		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 \|Laptops/collectors]].

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

Ttenbergen: /* Related articles */

2025-06-30T04:41:23Z

← Older revision		Revision as of 23:41, 29 June 2025
Line 48:		Line 48:

	[[Category:Cognos2 \| * ]]		[[Category:Cognos2 \| * ]]
			[[Category:Cognos Report Integrator]]

Ttenbergen at 22:09, 26 June 2025

2025-06-26T22:09:37Z

← Older revision		Revision as of 17:09, 26 June 2025
Line 1:		Line 1:
	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 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]].

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

Ttenbergen at 19:53, 13 March 2025

2025-03-13T19:53:47Z

← Older revision		Revision as of 14:53, 13 March 2025
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.

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

Ttenbergen: /* Steps */ we stopped the process of notifying local ADT pretty much right after we started it, so taking out the link

2022-06-30T20:31:31Z

Steps: we stopped the process of notifying local ADT pretty much right after we started it, so taking out the link

← Older revision		Revision as of 15:31, 30 June 2022
Line 8:		Line 8:

	== Steps ==		== 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 ===		=== Finding new admissions ===
	Any new admission will result in a new service start. Use the [[Cognos2 Service Starter]] ([[CSS]]) to find all new admissions.		Any new admission will result in a new service start. Use the [[Cognos2 Service Starter]] ([[CSS]]) to find all new admissions.

Ttenbergen: /* Finding new admissions */

2022-06-01T14:32:31Z

Finding new admissions

← Older revision		Revision as of 09:32, 1 June 2022
Line 24:		Line 24:
	This process should also fill in the complete [[Minimal Data Set]].		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. See [[John or Jane Doe patient]] for further instructions.		=== 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 ===		=== Finding new unit arrivals ===

Lkaita: /* Finding new admissions */

2022-05-31T19:42:06Z

Finding new admissions

← Older revision		Revision as of 14:42, 31 May 2022
Line 24:		Line 24:
	This process should also fill in the complete [[Minimal Data Set]].		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.		* 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. See [[John or Jane Doe patient]] for further instructions.

	=== Finding new unit arrivals ===		=== Finding new unit arrivals ===

Lkaita: /* Finding new admissions */

2022-05-31T19:40:24Z

Finding new admissions

← Older revision		Revision as of 14:40, 31 May 2022
Line 23:		Line 23:

	This process should also fill in the complete [[Minimal Data Set]].		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.

	=== Finding new unit arrivals ===		=== Finding new unit arrivals ===