|
Parent Topic |
|
|
|
|
This report compares the available resources to what should have happened based on the defined standards. It tracks actual and budgeted volumes, productive and non-productive hours, and FTEs. It compares them to the associated target and shows the results in the form of a Target Capacity Index and a Non-Productive Index.
Report fields included the 
Budget Volume, Actual Volume, Standard Units/Hour or Hours/Unit, Target Hours, Actual Non-Prod Hours, Target Paid Hours, Actual Non-Prod FTE, Target FTE, Target Paid FTE, Available FTE, FTE Under Target Capacity, Target Capacity Index, Non-Prod Index.
The percentage of FTEs that were assigned non-productive hours during the reporting period, such as vacation or sick time.
Formula: (Non-Productive FTE / Productive FTE) * 100
The sum of the direct and indirect productive FTE values. This indicates the number of FTEs who actually worked.
Formula: Productive Direct FTE + Productive Indirect FTE
The number of FTEs working hours assigned to pay codes that are coded to be productive and indirect.
Formula: Productive Indirect Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Productive Indirect Hours (Worked, and Paid) is set to Yes. These are shifts where the employee is not directly providing patient care (for example, maintenance, laundry, or education classes).
Formula: Productive Direct Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Productive Direct Hours (Direct, Worked, and Paid) is set to Yes and where neither the job class nor any special codes are set to be Indirect. These are shifts where the employee is directly providing patient care (for example, RN or LPN).
The hours are considered to be direct when ALL of the following are true:
The number of FTEs working non-productive hours.
Formula: Non-Productive Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
Formula: ((Available FTE - Target Paid FTE) / Available FTE) * 100
Difference between the number of staff who were needed compared to the staff who were available to work.
Formula: Target Paid FTE - Available FTE
The number of FTE's configured for the productivity standard or job class/position.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
The targeted amount of pay, based on the staffing needs plus non-productive pay (such as vacation or sick).
Formula: Target FTE + Non-Productive FTE
The number of FTEs working non-productive hours.
Formula: Non-Productive Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
The number of FTEs required for the volume of work.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Formula: Target Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
The number of hours required to complete the volume of work.
Formula: Actual Volume / Units per Hour Standard
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
The standard for a particular type of productivity units is set up on the Configuration section> Productivity card> Productivities screen> Standards section.
The units of service that were performed, normalized over the number of days in the range.
-or- Actual Volume * Hours Per Unit Standard
The number of hours that it should take to accomplish one productivity unit. For example, if the productivity unit is for lab tests, and this standard is set to .25, lab technicians are expected to conduct 1 test every .25 hour (15 minutes).
The number of FTE's configured for the productivity standard or job class/position.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
The targeted amount of pay, based on the staffing needs plus non-productive pay (such as vacation or sick).
Formula: Target FTE + Non-Productive FTE
The number of FTEs working non-productive hours.
Formula: Non-Productive Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
The number of FTEs required for the volume of work.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Formula: Target Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
The number of hours required to complete the volume of work.
Formula: Actual Volume / Units per Hour Standard
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
The standard for a particular type of productivity units is set up on the Configuration section> Productivity card> Productivities screen> Standards section.
The units of service that were performed, normalized over the number of days in the range.
-or- Actual Volume * Hours Per Unit Standard
The number of hours that it should take to accomplish one productivity unit. For example, if the productivity unit is for lab tests, and this standard is set to .25, lab technicians are expected to conduct 1 test every .25 hour (15 minutes).
The number of FTEs required for the volume of work.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Formula: Target Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
The number of hours required to complete the volume of work.
Formula: Actual Volume / Units per Hour Standard
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
The standard for a particular type of productivity units is set up on the Configuration section> Productivity card> Productivities screen> Standards section.
The units of service that were performed, normalized over the number of days in the range.
-or- Actual Volume * Hours Per Unit Standard
The number of hours that it should take to accomplish one productivity unit. For example, if the productivity unit is for lab tests, and this standard is set to .25, lab technicians are expected to conduct 1 test every .25 hour (15 minutes).
The number of FTEs working non-productive hours.
Formula: Non-Productive Hours / FTE Hours Conversion
FTE hours / number of productive days in week) * number of productive days in reporting period.
Acronym for "full time equivalent". This compares the number of hours worked by employees to the value set for a full time employee. If the value for an FTE is set to 40 hours per week, then every 40 hours worked would equal 1.0 FTE.
For example, if several employees worked a total of 300 hours, this would be 7.5 FTEs, regardless of how many individual employees worked these 300 hours (300 / 40 = 7.5).
The number of hours which define the productivity FTE for the corporation are set up on the Configuration section > System card > Application screen. Enter "LBRVSN" in the Code field and Search. Open the Parameters tab.
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
The sum of the target and non-productive hours.
Formula: Target Hours + Non-Productive Hours
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
The number of hours required to complete the volume of work.
Formula: Actual Volume / Units per Hour Standard
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
The standard for a particular type of productivity units is set up on the Configuration section> Productivity card> Productivities screen> Standards section.
The units of service that were performed, normalized over the number of days in the range.
-or- Actual Volume * Hours Per Unit Standard
The number of hours that it should take to accomplish one productivity unit. For example, if the productivity unit is for lab tests, and this standard is set to .25, lab technicians are expected to conduct 1 test every .25 hour (15 minutes).
Total of the hours assigned to pay codes where report assignment Non-Productive Hours (Paid) is set to Yes. Non-productive hours are usually associated with paid time off, such as sick time, vacation, jury duty, etc.
The number of hours required to complete the volume of work.
Formula: Actual Volume / Units per Hour Standard
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
The standard for a particular type of productivity units is set up on the Configuration section> Productivity card> Productivities screen> Standards section.
The units of service that were performed, normalized over the number of days in the range.
-or- Actual Volume * Hours Per Unit Standard
The number of hours that it should take to accomplish one productivity unit. For example, if the productivity unit is for lab tests, and this standard is set to .25, lab technicians are expected to conduct 1 test every .25 hour (15 minutes).
The number of productivity units that should be accomplished in an hour. For example, if the productivity unit is for lab tests, and this standard is set to 4, lab technicians are expected to conduct 4 tests every hour.
This is also called Units Per Hour Standard.
The units of service that were performed, normalized over the number of days in the range.
The volume (units of service) that were included in the budget for the report date range. This volume has been Normalized to average the volume per day.
The mathematical process of averaging the units of service (volume) over the number of productive days in a week in order to match the time frame of the report. This is to accurately assess productivity of departments that are not open 7 days a week.
For example, Lab A is open 5 days per week and Lab B is open 7 days per week. Both labs are open 8 hours per day. Both labs completed 500 tests in a specific week.
If a user ran a productivity report for a week (7 days), the normalization of data shows that Lab A's productivity is higher because it accomplished the same number of tests in fewer hours.
This report includes Labor Distribution Drill down/roll up with in the report.
Click on the name of a labor distribution to expand to the next lower level and show details. The lowest level displayed is either the job class or the productivity standard.
If the report is run at a lower distribution level, the totals displayed when rolling up only include those from the selected organization unit. For example, if the report is run for Department A at level 5, if you open the level 1 Corporate labor distribution, the values included are only those from Department A, not from the entire corporation. However, if the report is run for the Corporate level 1, the user can drill down to level 5 and view the amounts for Department A.
Today's date is used for determining the appropriate version of any Productivity Standards to be used for processing the report.
Report parameters include the following options:
