ICU Utilization Report

Reports
Report:	ICU Utilization Report
StartDtTm:	2026-01-01
EndDtTm:
Contact Person :	Dr Allan Garland
Recipients:	* Critical Care Directors and Site Managers* see also: Distribution of Annual and Quarterly Reports
Frequency:	quarterly
MailingList:	{{{MailingList}}}
Data Dependencies(Reports/Indicators/Data Elements):
SASFiles:

 

• Cargo

used to include | DataDependencies = but that is now handled by Template:Data Dependencies

• Helper template:

• Cargo

• Categories

none

• Default form: none, this is populated by Template:Report and Template:Reporting Indicators and their respective forms.

• Categories

• Default form:

The organization for new reporting of ICU Utilization. (Still in progress)

Step 0

• Every ICU record in the ICU database will be categorized, per items 1-3, and then collated for reporting, per item#4

Step 1

• Create Initial ICU Reporting Dataset derived from all ICU database records representing just first ICU admissions during that reporting period -- i.e. does not include ICU database records of receiving ICU services in direct ICU service-to-ICU service transfer
  • As appropriate, subdivide each such ICU database record into rows in Initial ICU Reporting Dataset, which has 4 variables: Intended1st Service, Service/Loc, Boarding Loc, Interval.
    • Interval = # of 24 hours periods the patient with that Intended1st Service and that Service/Loc had that Boarding Loc. e.g. if for that patient’s combination of a given Intended1st Service and Service/Loc, Boarding Loc was MICU from noon on Monday to 5pm on Wednesday, then that Interval=2.21
    • If a given initial ICU database record has the same Boarding Loc for the entire record, then it generates just one row of Initial ICU Reporting Dataset. More generally, the number of Initial ICU Reporting Dataset rows generated from a given initial ICU database record will be the same as the number of different Boarding Locs for that record.
  • To create the portion of the report for a given ICU (we’ll use MICU as example) from all initial ICU admissions, identify all rows in Initial ICU Reporting Dataset for which MICU is any of Intended1st Service, Service/Loc, or Boarding Loc
    • Across all these rows of Initial ICU Reporting Dataset, collate/accumulate as follows (again using MICU as the example of the service we’re creating the report on):

Group	Intended1stSrvc	Service/Loc	Boarding Loc	Cumulative interval over all rows in Initial ICU Reporting Dataset
A	MICU	MICU	MICU	whatever
B	MICU	MICU	other	whatever
C	other	other	MICU	whatever
D	MICU	other	other	whatever
E	other	MICU	MICU	whatever

Step 2

• For ICU database records with direct ICU service-to-ICU service transfer, for the receiving ICU services create Receiving ICU Service Dataset
  • As appropriate, subdivide each such ICU database record into rows in Receiving ICU Service Dataset, which has 5 variables: Sending service, Service/Loc, Boarding Loc, Reason for transfer, Interval.
    • Reason for transfer is either Bed Management or Medical Necessity, as indicated by the value of Transfer for bed management
    • Interval = # of 24 hours periods the patient with that Service/Loc had that Boarding Loc
    • If a given receiving ICU database record has the same Boarding Loc for the entire record, then it generates just one row of Receiving ICU Service Dataset. More generally, the number of Receiving ICU Service Dataset rows generated from a receiving ICU database record will be the same as the number of different Boarding Locs for that record.
  • Note that it is NOT possible for a given ICU database record to be included in #1 and #2 (here)
  • To create the portion of the report for a given ICU (we’ll use MICU as example) as the receiving ICU in such transfers, identify all rows in Receiving ICU Service Dataset for which MICU is any of Sending service, Service/Loc, or Boarding Loc
    • Across all these rows of Receiving ICU Service Dataset, collate/accumulate as follows (using MICU as the example of the ICU service we’re creating the report on):

Group	Sending service	Service/Loc	Boarding Loc	Reason for transfer	Cumulative interval over all rows in Receiving ICU Service Dataset
F	other, not MICU	MICU	MICU	Bed management	whatever
G	other, not MICU	MICU	other, not MICU	Bed management	whatever
H	other, not MICU	MICU	MICU	Medical necessity	whatever
J	other, not MICU	MICU	other, not MICU	Medical necessity	whatever

Step 3

• For ICU database records with direct ICU service-to-ICU service transfer, for the sending ICU services create Sending ICU Service Dataset
  • Note that it IS possible for a given ICU database record to be part of #1 (above) and #3 (here)
  • As appropriate, subdivide each such ICU database record into rows in Sending ICU Service Dataset, which has 5 variables: Sending service, Service/Loc, Boarding Loc, Reason for transfer, Interval.
    • Reason for transfer is either Bed Management or Medical Necessity, as indicated by the value of Transfer for bed management
    • Interval = # of 24 hours periods the patient with that Sending service had that Boarding Loc
    • If a given sending ICU database record has the same Boarding Loc for the entire record, then it generates just one row of Sending ICU Service Dataset. More generally, the number of Sending ICU Service Dataset rows generated from a sending ICU database record will be the same as the number of different Boarding Locs for that record.
  • To create the portion of the report for a given ICU (we’ll use MICU as example) as the sending ICU in such transfers, identify all rows in Sending ICU Service Dataset for which MICU is any of Sending service, Service/Loc, or Boarding Loc
    • Across all these rows of Receiving ICU Service Dataset, collate/accumulate as follows (using MICU as the example of the ICU service we’re creating the report on):

Group	Sending service	Service/Loc	Boarding Loc	Reason for transfer	Cumulative interval over all rows in Receiving ICU Service Dataset
K	MICU	other, not MICU	other, not MICU	Bed management	whatever
L	MICU	other, not MICU	MICU	Bed management	whatever
M	MICU	other, not MICU	other, not MICU	Medical necessity	whatever
N	MICU	other, not MICU	MICU	Medical necessity	whatever

Step 4

• Here is the reporting template, shown for a single service, but this should be generated for EACH ICU service:

Bed-days under care of that service 1	Prior column/calendar days in reporting period 2	Bed-days in that service’s physical unit 1	Prior column/calendar days in reporting period 2
Actual = A+B+E+F+G+H+J		Actual = A+C+E+F+H+L+N
Should not have been but were=E+F+G		Should not have been but were=C+E+F+N
Should have been but weren’t= D+K+L		Should have been but weren’t=B+D+J+K

1 calculate as sum of fractional bed-days by patient, but report to 1 decimal place; 2 report to 2 decimal places