Technical Efficiency

Technical Efficiency: Concept Architecture

Orientation and learning roadmap

The page begins with the relationship between resources used and services or outcomes produced. It then explains how an estimated production frontier supports input- and output-oriented comparisons, works through an illustrative clinic comparison, and shows why a frontier score needs careful interpretation before it informs a health system decision.

Compare like with like on a feasible frontier

A production frontier represents the best feasible combinations of measured inputs and outputs under a specified technology and comparison set. An organization below that frontier might be able to use fewer inputs for its current outputs or produce more outputs with its current inputs. The conclusion depends on how inputs, outputs, quality, and operating conditions have been defined.

In health care, inputs may include clinical staff time, beds, medicines, and equipment; outputs may include risk-adjusted episodes, completed services, or appropriately measured health gains. A simple count of visits can reward more activity even if care quality falls or unnecessary treatment rises. Choose outputs and comparison units that correspond to the purpose of care rather than equating activity with health benefit.

The frontier may be estimated from observed peers using data envelopment analysis (DEA), modeled statistically through stochastic frontier analysis, or constructed using other defensible production assumptions. An observed-peer frontier identifies performance relative to the included units; it is not proof of an absolute physical optimum. Statistical noise, measurement error, and omitted case-mix differences can move a unit's apparent distance from the frontier.

Input and output orientations answer different questions

An input-oriented assessment asks how much measured resource use could be reduced while maintaining specified outputs. An output-oriented assessment asks how much output could rise with specified inputs. The orientation should reflect what a manager can plausibly change and which outcomes must be protected.

For an input-oriented radial measure with input vector $x$ and output vector $y$, a conceptual score is:

$$\theta=\min\{\lambda:0<\lambda\leq1,\ (\lambda x,y)\text{ is feasible under the chosen frontier}\}.$$

A value of $\theta=1$ indicates that the unit lies on the estimated radial input frontier for the modeled inputs and outputs. A score below one represents a proportional input reduction under the model's assumptions; additional non-radial input slack can remain after that reduction. Different returns-to-scale assumptions or a different peer set can change the score.

Technical efficiency is distinct from allocative efficiency, which also considers whether the chosen input or output mix is the right one given prices, values, and objectives. A unit can be technically efficient in producing a service that is not the best use of scarce resources. Likewise, low monetary cost per visit is not by itself proof of technical efficiency if output mix or quality differs.

A worked clinic comparison

Suppose a clinic uses 10 comparable staff-days to deliver 1,000 appropriately defined visits in a period. A credible frontier for clinics with comparable patients and quality indicates that 8 staff-days could produce the same 1,000 visits. With one input in this simplified illustration, the input-oriented radial score is $8/10=0.80$.

$$\theta=\frac{\text{frontier input for the same output}}{\text{observed input}}=\frac{8}{10}=0.80.$$

Under the assumptions, a 20% reduction in the measured input would reach the modeled frontier while preserving measured output. It does not establish that two staff-days can safely be removed from this particular clinic: unmeasured complexity, staffing minima, access, and care quality could invalidate the comparison. The score also does not identify the operational change needed to achieve the frontier.

What a frontier study must check

A benchmark can mislead if providers face different patient needs or if important outputs are omitted. For example, a hospital treating more severe cases may appear to use more resources per episode even when it is well managed. Conversely, coding more episodes without improving outcomes can create an apparent efficiency gain.

1. Define the decision unit and scope. State whether the comparison concerns clinics, hospitals, districts, or whole health systems and over what period.
2. Select meaningful measures. Record inputs, outputs, quality, and relevant risk adjustment before fitting a frontier.
3. Choose orientation and scale assumptions. Explain why input or output changes are feasible and whether constant or variable returns to scale are appropriate.
4. Test sensitivity. Examine measurement error, outliers, missing variables, peer composition, and alternative model specifications.
5. Investigate practice. Use the score to identify questions for operational review, not as automatic proof of waste or a staffing target.

DEA is sensitive to measurement errors and unusual observations because its frontier is constructed from the observed comparison set. Stochastic frontier methods explicitly model random noise but require distributional and functional-form choices. Neither method removes the need to inspect clinical comparability and the likely consequences of changing resource use.

How efficiency connects to health decisions

Technical efficiency can release resources or expand feasible output when the identified improvement is real and implementable. Whether that would improve population health depends on which services change and where released resources go. The opportunity cost and distributional consequences must therefore be considered alongside the frontier score.

A good report identifies the comparator group, input and output definitions, estimation method, uncertainty, and safeguards for quality and equity. It keeps a relative performance signal separate from a claim that a particular budget cut is harmless. Efficiency analysis is most useful when it points to a testable operational change whose costs and health effects can then be evaluated.

Evidence used for this explanation

Farrell's foundational work separates technical and allocative aspects of productive efficiency. WHO and the European Observatory provide health-sector context and discuss frontier methods, case mix, and limitations of health system comparisons.

• Farrell MJ. The Measurement of Productive Efficiency. Journal of the Royal Statistical Society, Series A (1957);120:253–281.
• WHO. Technical efficiency in health financing and economics.
• European Observatory on Health Systems and Policies. Health system efficiency: measurement and policy.