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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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).
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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:
Job Class Indicator Productivity Standard 1 is set to "D".
Special Code Indicator is set to
Pay Code Reporting Category Productive Direct Hours (Direct, Worked and Paid) is set to Yes.
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
The number of hours required to complete the volume of work.
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.
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
The number of hours required to complete the volume of work.
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.
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 difference between the actual hours per unit and the standard hours per unit.
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).
This is also called 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).
This is also called Hours Per Unit Standard.
The number of hours that it actually took to complete one productivity unit. For example, if the productivity unit is for lab tests, and technicians did 24 tests in 8 hours, the actual hours per unit would be .25 hours.
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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).
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).
10 employees each working 30 hours = 300 hours or 7.5 FTEs.
12 employees each working 25 hours = 300 hours or 7.5 FTEs.
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.
LBRVSN Application Parameter Productivity Standard Hour 1 defines the weekly hours for an FTE.
LBRVSN Application Parameter Productivity Standard Hour 2 defines the daily hours for an FTE.
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:
Job Class Indicator Productivity Standard 1 is set to "D".
Special Code Indicator is set to
Pay Code Reporting Category Productive Direct Hours (Direct, Worked and Paid) is set to Yes.
The total number of primary payable hours as designated by the calculations process.
Example: An employee works 82.00 hours in the pay period, of which 12.00 hours occur during the evening shift. The employee receives 80.00 hours associated with the REG pay code, 2.00 hours associated with the OT pay code, and 12.00 hours associated with the additional EVE pay code. The actual hours are 82.00.
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.
Lab A's normalized volume is 100 tests per day (500 hours / 5 days). Their tests per hour volume equals 12.5 (100 tests / 8 hours).
Lab B's normalized volume is 71.4 tests per day (500 hours / 7 days). Their tests per hour volume equals 8.9 (71.4 tests / 8 hours).
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.
The following options can be toggled within the resulting report in the display screen:
Show Graphs or Hide Graphs
The Show Graphs option shows a Productivity Summary - Volume bar graph for Budget and Actual values and also a Productivity Summary - Hours/Unit for Standard and Actual values.
The Hide Graphs option does not display any of the graphs.
Labor Distribution Drill down
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 "drilling 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.
Report parameters include the following options:
Which organization unit to include.
Whether to include employees from all labor groups (by leaving the field blank) or selecting a labor group.
The start and end dates of the range to include in the report.
Whether this report is broken down by day, week, pay period, month or year.
Whether to include only a specified shift, or all shifts.
Whether to show shift details or summary information only.
Whether or not to show graphs of the information.
Whether to include all Standard Reporting Categories (by leaving this field blank) to specify a certain option.
Which Standard Category to include, or to include the Productivity Standard indicated as the default (which is selected in the Productivity Unit configuration screen>Standards section).
Whether to display drill down values by job class regardless of the Productivity Standard 4 Indicator setting (Always), or whether to display either the job class or productivity standard--whichever is selected by the indicator setting (Set Up), or whether to NOT display job class drill down information (Never).
Whether to display job classes that do not have any hours assigned (Yes/No).
Budget Volume, 