Tutorials › Biostatistics › Closed Testing Procedures Explained

Multiple Testing & Multiplicity

Closed Testing Procedures Explained

A practical guide to the closure principle for controlling the family-wise error rate, including elementary and intersection hypotheses, local tests, adjusted p-values, hierarchical interpretations, a complete worked example, and the relationship between closed testing, Holm, gatekeeping, and multiple-endpoint strategies.

Advanced 16 min read

What You'll Learn

  • What the closure principle means and why it controls family-wise error
  • How elementary and intersection hypotheses are constructed
  • How local tests determine whether an individual hypothesis can be rejected
  • How adjusted p-values are obtained from the closed testing family
  • How closed testing relates to Holm, gatekeeping, and hierarchical testing
  • How to implement a closed testing strategy in a clinical trial

Introduction

Clinical trials frequently evaluate more than one hypothesis. A study may have multiple primary endpoints, several doses, multiple treatment comparisons, or a combination of efficacy and key secondary objectives.

When several hypotheses are tested, the probability of obtaining at least one false-positive result can exceed the nominal significance level.

This is the multiple testing problem.

A central goal of multiplicity control is therefore to ensure that the family-wise error rate (FWER) remains at or below a prespecified level such as 5%.

The closed testing procedure provides one of the most general and powerful frameworks for achieving strong FWER control.

Key idea: The closure principle says that an elementary hypothesis can be rejected only if every intersection hypothesis containing that elementary hypothesis is also rejected by its corresponding local test.

The Multiple Testing Problem

Suppose a clinical trial has two hypotheses:

\[ H_1 \]

and:

\[ H_2 \]

If each is tested at the 5% level independently, the probability of making at least one false rejection can exceed 5%.

If the hypotheses are independent and both are true, for example, the probability of at least one false rejection is:

\[ 1-(1-0.05)^2 = 0.0975 \]

or approximately 9.75%.

This is much larger than the desired 5% family-wise error rate.

Important: FWER is the probability of making at least one Type I error among the family of hypotheses being considered.

What Is the Family-Wise Error Rate?

Suppose the set of hypotheses is:

\[ \mathcal{H}=\{H_1,H_2,\ldots,H_m\} \]

The family-wise error rate is:

\[ FWER = P(\text{at least one true null hypothesis is rejected}) \]

A multiple testing procedure has strong FWER control at level \(\alpha\) if:

\[ FWER\le\alpha \]

for every possible configuration of true and false hypotheses.

This distinction is important. A method that controls FWER only when all null hypotheses are true provides weak control, not strong control.

The Closure Principle

The closed testing principle was introduced by Marcus, Peritz, and Gabriel (1976) as a general framework for strong control of the family-wise error rate.

The fundamental idea is to construct a family of hypotheses that is closed under intersection.

Suppose there are \(m\) elementary null hypotheses:

\[ H_1,H_2,\ldots,H_m \]

The closed family contains:

  • Every elementary hypothesis
  • Every nonempty intersection of elementary hypotheses

For two hypotheses, the closed family is:

\[ H_1,\qquad H_2,\qquad H_{12}=H_1\cap H_2 \]

For three hypotheses, the family becomes:

\[ H_1,\ H_2,\ H_3,\ H_{12},\ H_{13},\ H_{23},\ H_{123} \]
The closure rule: If an elementary hypothesis is rejected, then every intersection hypothesis containing it must also have been rejected by its corresponding local test.

Elementary Hypotheses

The original scientific questions are usually represented by the elementary hypotheses.

For example, suppose a clinical trial compares an experimental treatment with control for two endpoints. Let:

\[ H_1:\text{No treatment effect on Endpoint 1} \]

and:

\[ H_2:\text{No treatment effect on Endpoint 2} \]

These are the hypotheses investigators ultimately want to reject.

Intersection Hypotheses

The closure principle adds hypotheses representing intersections of the elementary hypotheses.

For two hypotheses:

\[ H_{12}=H_1\cap H_2 \]

The intersection hypothesis is true when both elementary null hypotheses are true.

For three hypotheses:

\[ H_{123}=H_1\cap H_2\cap H_3 \]

This represents the global null that all three elementary hypotheses are true.

Hypothesis Meaning
\(H_1\) Endpoint 1 has no effect
\(H_2\) Endpoint 2 has no effect
\(H_{12}\) Both Endpoint 1 and Endpoint 2 have no effect

Why Is the Family Called "Closed"?

The family is called closed because if a collection of hypotheses belongs to the family, the relevant intersection hypothesis also belongs to the family.

For example, with three elementary hypotheses:

\[ H_1,\ H_2,\ H_3 \]

the family also contains:

\[ H_1\cap H_2,\qquad H_1\cap H_3,\qquad H_2\cap H_3,\qquad H_1\cap H_2\cap H_3 \]

The resulting structure allows the individual hypotheses to be tested while accounting for all relevant intersections.

Local Tests

Every hypothesis in a closed testing procedure is tested using a local test.

A local test is simply the statistical test assigned to a particular intersection hypothesis.

For example:

Hypothesis Local Test
\(H_1\) Two-sided or one-sided test at \(\alpha\)
\(H_2\) Two-sided or one-sided test at \(\alpha\)
\(H_{12}\) Predefined level-\(\alpha\) test of the intersection

The local test does not necessarily have to use the same test statistic or procedure for every intersection.

What matters is that each local test has the required Type I error control.

The Closed Testing Decision Rule

For an elementary hypothesis \(H_i\), the closed testing procedure rejects \(H_i\) only if all intersection hypotheses containing \(H_i\) are rejected.

For two hypotheses:

\[ H_1\text{ is rejected} \iff H_1\text{ and }H_{12}\text{ are rejected} \]

Similarly:

\[ H_2\text{ is rejected} \iff H_2\text{ and }H_{12}\text{ are rejected} \]
This is the most important rule to remember: An impressive result for \(H_1\) by itself is not enough. Every closed-family hypothesis containing \(H_1\) must also be rejected.

A Two-Hypothesis Example

Suppose a trial has two confirmatory hypotheses:

\[ H_1:\text{No effect on the primary endpoint} \]

and:

\[ H_2:\text{No effect on a key secondary endpoint} \]

The closed testing family is:

1
\(H_1\) — Endpoint 1 null hypothesis.
2
\(H_2\) — Endpoint 2 null hypothesis.
3
\(H_{12}\) — intersection hypothesis \(H_1\cap H_2\).

Suppose all three local tests are performed at \(\alpha=0.05\).

To reject \(H_1\), we need:

\[ p_1\le0.05 \quad\text{and}\quad p_{12}\le0.05 \]

To reject \(H_2\), we need:

\[ p_2\le0.05 \quad\text{and}\quad p_{12}\le0.05 \]

Worked Example: Two Endpoints

Consider a randomized Phase III trial evaluating an experimental treatment against placebo. The study has two hypotheses:

Hypothesis Clinical Question
\(H_1\) No treatment effect on the primary endpoint
\(H_2\) No treatment effect on the key secondary endpoint

Suppose the unadjusted p-values are:

Test p-value
\(H_1\) 0.018
\(H_2\) 0.031
\(H_{12}\) 0.011

Using a closed testing procedure with level \(\alpha=0.05\):

  • \(H_1\) is rejected because both 0.018 and 0.011 are below 0.05.
  • \(H_2\) is rejected because both 0.031 and 0.011 are below 0.05.

Therefore, both endpoints can be declared statistically significant while maintaining strong FWER control at 5%.

What If the Intersection Hypothesis Is Not Significant?

Now suppose instead that:

Test p-value
\(H_1\) 0.018
\(H_2\) 0.031
\(H_{12}\) 0.072

Although both elementary p-values are below 0.05, the intersection hypothesis is not rejected.

Therefore:

\[ H_1\text{ is not rejected} \]

and:

\[ H_2\text{ is not rejected} \]

under the closed testing procedure.

Why? Because the closure principle requires rejection of the intersection hypothesis before either of its component hypotheses can be rejected.

Why This Controls FWER

The logic behind strong FWER control is elegant. Suppose \(H_i\) is a true elementary null hypothesis. If the procedure incorrectly rejects \(H_i\), then the closure principle requires the rejection of every intersection hypothesis containing \(H_i\). In particular, the intersection of all true elementary hypotheses must also be rejected.

The local test for that intersection is performed at level \(\alpha\). Therefore, the probability of incorrectly rejecting a true elementary hypothesis cannot exceed the probability of incorrectly rejecting the relevant true intersection hypothesis.

Consequently:

\[ FWER\le\alpha \]

under every configuration of true and false elementary hypotheses.

Strong FWER Control

The phrase strong control is important. Consider three possible configurations:

  • All elementary null hypotheses are true.
  • Some null hypotheses are true and some are false.
  • Only one elementary null hypothesis is true.

A properly constructed closed testing procedure controls FWER under all of these configurations.

Configuration Strong FWER Requirement
All nulls true \(FWER\le\alpha\)
Some nulls true \(FWER\le\alpha\)
One null true \(FWER\le\alpha\)

Closed Testing With Three Hypotheses

With three elementary hypotheses:

\[ H_1,\ H_2,\ H_3 \]

the closed family contains seven hypotheses:

Level Hypotheses
Elementary \(H_1,\ H_2,\ H_3\)
Pairwise intersections \(H_{12},\ H_{13},\ H_{23}\)
Global intersection \(H_{123}\)

where:

\[ H_{12}=H_1\cap H_2 \] \[ H_{13}=H_1\cap H_3 \] \[ H_{23}=H_2\cap H_3 \] \[ H_{123}=H_1\cap H_2\cap H_3 \]

To reject \(H_1\), the following four hypotheses must all be rejected:

\[ H_1,\quad H_{12},\quad H_{13},\quad H_{123} \]

To reject \(H_2\):

\[ H_2,\quad H_{12},\quad H_{23},\quad H_{123} \]

To reject \(H_3\):

\[ H_3,\quad H_{13},\quad H_{23},\quad H_{123} \]

The Number of Hypotheses Grows Quickly

For \(m\) elementary hypotheses, the complete closed family contains:

\[ 2^m-1 \]

nonempty hypotheses.

Elementary Hypotheses Closed Family Size
2 3
3 7
4 15
5 31
6 63
10 1,023

This exponential growth is one reason that practical closed testing procedures often exploit special structure to avoid explicitly performing every possible test.

Local Tests Can Be More Powerful Than Bonferroni

One of the major attractions of closed testing is that it is a framework, rather than a single fixed adjustment.

The local tests can be selected to reflect the dependence structure and scientific meaning of the hypotheses.

For example, an intersection hypothesis might be tested using:

  • Bonferroni
  • Sidak
  • Fisher's combination test
  • Parametric multiple comparison procedures
  • Likelihood-ratio tests
  • Specialized tests based on the endpoint structure

As long as the local tests satisfy the required Type I error properties, the resulting closed testing procedure can provide strong FWER control.

Important distinction: Closed testing is not synonymous with Bonferroni correction. Bonferroni can be used as a local test inside a closed testing procedure, but the closure principle is the broader framework.

Closed Testing and Adjusted p-values

Closed testing can also be expressed using adjusted p-values.

For an elementary hypothesis \(H_i\), its adjusted p-value is essentially the largest local p-value among all intersection hypotheses containing \(H_i\).

Formally:

\[ p_i^{\mathrm{adj}} = \max_{I:\,i\in I} p_I \]

where \(p_I\) is the p-value for the corresponding intersection hypothesis.

For two hypotheses:

\[ p_1^{\mathrm{adj}} = \max(p_1,p_{12}) \]

and:

\[ p_2^{\mathrm{adj}} = \max(p_2,p_{12}) \]

The hypothesis can then be rejected at level \(\alpha\) when:

\[ p_i^{\mathrm{adj}}\le\alpha \]

Adjusted p-values for the Worked Example

Using:

Hypothesis Local p-value
\(H_1\) 0.018
\(H_2\) 0.031
\(H_{12}\) 0.011

The adjusted p-value for \(H_1\) is:

\[ p_1^{\mathrm{adj}} = \max(0.018,0.011) = 0.018 \]

The adjusted p-value for \(H_2\) is:

\[ p_2^{\mathrm{adj}} = \max(0.031,0.011) = 0.031 \]

Both are below 0.05, so both elementary hypotheses can be rejected.

A Three-Hypothesis Adjusted p-value Example

Suppose the local p-values are:

Hypothesis Local p-value
\(H_1\) 0.012
\(H_2\) 0.041
\(H_3\) 0.020
\(H_{12}\) 0.025
\(H_{13}\) 0.014
\(H_{23}\) 0.035
\(H_{123}\) 0.010

For \(H_1\), the containing intersections are:

\[ H_1,\ H_{12},\ H_{13},\ H_{123} \]

Therefore:

\[ p_1^{\mathrm{adj}} = \max(0.012,0.025,0.014,0.010) = 0.025 \]

For \(H_2\):

\[ p_2^{\mathrm{adj}} = \max(0.041,0.025,0.035,0.010) = 0.041 \]

For \(H_3\):

\[ p_3^{\mathrm{adj}} = \max(0.020,0.014,0.035,0.010) = 0.035 \]

All three adjusted p-values are below 0.05. Therefore, all three elementary hypotheses are rejected.

Closed Testing vs. Bonferroni

Bonferroni is one of the simplest multiplicity procedures. For \(m\) hypotheses, each hypothesis can be tested at:

\[ \frac{\alpha}{m} \]

Closed testing can sometimes be more powerful because it can use less conservative local tests and exploit the logical relationships among hypotheses.

Feature Bonferroni Closed Testing
FWER control Yes Yes
Strong control Yes Yes
Uses intersection hypotheses Not inherently Yes
Can exploit logical structure Limited Yes
Local tests Fixed Bonferroni allocation Flexible
Potential power Often conservative Can be higher

Closed Testing and Holm's Procedure

Holm's step-down procedure is particularly important because it can be viewed as a shortcut to a closed testing procedure under appropriate local testing choices.

Holm orders the p-values:

\[ p_{(1)}\le p_{(2)}\le\cdots\le p_{(m)} \]

and compares them sequentially with:

\[ \frac{\alpha}{m}, \frac{\alpha}{m-1}, \ldots, \alpha \]

The resulting procedure strongly controls FWER.

Key relationship: Holm's procedure is not an unrelated alternative to closed testing. It can be understood as an efficient implementation of a particular closed testing strategy, avoiding the need to explicitly test every intersection hypothesis.

Why Closed Testing Can Be More General Than Holm

Holm imposes a specific step-down structure. Closed testing does not require a single universal ordering.

This allows closed testing to represent:

  • Hierarchical hypotheses
  • Multiple endpoints
  • Multiple doses
  • Composite testing strategies
  • Gatekeeping structures
  • Fallback procedures
  • Specialized intersection tests

This flexibility makes closed testing particularly useful for complex confirmatory clinical trial strategies.

Closed Testing and Gatekeeping

Gatekeeping procedures are often used when hypotheses are organized into families.

For example, a trial might have:

  • Family 1: primary endpoints
  • Family 2: key secondary endpoints
  • Family 3: exploratory secondary endpoints

A strict gatekeeping strategy may require success in Family 1 before testing Family 2.

Closed testing provides a mathematical framework for understanding many such procedures.

Concept Role
Closed testing General framework based on intersection hypotheses
Gatekeeping Controls how alpha becomes available across hypothesis families
Hierarchical testing Tests hypotheses according to a prespecified order
Holm Step-down multiplicity procedure

Hierarchical Testing as a Special Structure

Suppose the trial has:

\[ H_1\rightarrow H_2\rightarrow H_3 \]

where the arrow indicates a testing hierarchy.

The strategy might require:

  1. Test \(H_1\).
  2. If \(H_1\) is rejected, test \(H_2\).
  3. If \(H_2\) is rejected, test \(H_3\).

This can be represented within broader closed-testing and logical-testing frameworks.

Do not confuse hierarchy with closure. A hierarchy describes the logical order in which hypotheses are tested. Closure describes the complete set of intersection hypotheses required for strong FWER control.

Closed Testing With Multiple Endpoints

Multiple endpoints are one of the most common clinical applications. Suppose a Phase III trial has:

  • Overall survival
  • Progression-free survival
  • Objective response rate

If all three are confirmatory, the multiplicity strategy must specify how Type I error is controlled across them.

A closed testing framework could include:

\[ H_1,\ H_2,\ H_3, \ H_{12},\ H_{13},\ H_{23}, \ H_{123} \]

with a prespecified local test for each intersection.

Closed Testing With Multiple Treatment Comparisons

The same principle can be applied to multiple treatment comparisons. Suppose a trial compares:

  • Dose 1 vs. placebo
  • Dose 2 vs. placebo
  • Dose 3 vs. placebo

The elementary hypotheses could be:

\[ H_1:\theta_1\le0 \] \[ H_2:\theta_2\le0 \] \[ H_3:\theta_3\le0 \]

The closure includes all nonempty intersections.

This can allow the multiplicity strategy to incorporate the scientific structure of the dose-response problem.

Local Test Choice Matters

The power of a closed testing procedure depends heavily on the local tests.

Suppose an intersection hypothesis is tested using a highly conservative method. The overall procedure may remain valid but have low power.

Conversely, an appropriately chosen local test can make better use of the available information.

Therefore, closed testing should be viewed as:

1
Define the elementary scientific hypotheses.
2
Construct the complete closed family of intersections.
3
Choose a valid local test for each relevant intersection.
4
Perform the local tests.
5
Reject an elementary hypothesis only when every containing intersection is rejected.

Closed Testing Does Not Mean "Test Everything at 0.05"

A common misunderstanding is that because each local test is performed at level 0.05, the overall procedure somehow has a 5% error rate automatically.

That is not the reason closed testing works.

The key is the logical relationship among the local tests and the intersection hypotheses.

The closure principle ensures that a false elementary rejection implies a corresponding false rejection of a true intersection hypothesis.

That logical implication is what establishes strong FWER control.

A More Formal Statement of the Closure Principle

Let \(H_1,\ldots,H_m\) be elementary hypotheses. For every nonempty subset \(I\subseteq\{1,\ldots,m\}\), define:

\[ H_I=\bigcap_{i\in I}H_i \]

The closed family is:

\[ \mathcal{C} = \{H_I:I\subseteq\{1,\ldots,m\},I\ne\varnothing\} \]

Each \(H_I\) receives a level-\(\alpha\) local test. An elementary hypothesis \(H_i\) is rejected only if every \(H_I\) satisfying \(i\in I\) is rejected.

If all local tests are valid at level \(\alpha\), the resulting closed testing procedure strongly controls FWER at level \(\alpha\).

A Three-Endpoint Worked Example

Consider a Phase III trial with three confirmatory endpoints:

Hypothesis Endpoint Unadjusted p-value
\(H_1\) Overall survival 0.012
\(H_2\) Progression-free survival 0.018
\(H_3\) Objective response 0.041

Suppose the local intersection p-values are:

Intersection Local p-value
\(H_{12}\) 0.010
\(H_{13}\) 0.021
\(H_{23}\) 0.032
\(H_{123}\) 0.009

For \(H_1\), the relevant p-values are:

\[ 0.012,\quad0.010,\quad0.021,\quad0.009 \]

Therefore:

\[ p_1^{\mathrm{adj}}=0.021 \]

For \(H_2\):

\[ p_2^{\mathrm{adj}} = \max(0.018,0.010,0.032,0.009) = 0.032 \]

For \(H_3\):

\[ p_3^{\mathrm{adj}} = \max(0.041,0.021,0.032,0.009) = 0.041 \]

All three adjusted p-values are below 0.05. Thus all three hypotheses can be rejected under this particular closed testing procedure.

What Happens When One Endpoint Is Clearly Strong?

Suppose instead:

Hypothesis p-value
\(H_1\) 0.001
\(H_2\) 0.200
\(H_3\) 0.400

A closed testing procedure does not automatically prevent \(H_1\) from being rejected.

The key question is whether every intersection hypothesis containing \(H_1\) can also be rejected.

If those intersection tests are sufficiently strong, \(H_1\) may be rejected even though \(H_2\) and \(H_3\) are not.

This is one of the advantages of a properly structured multiple testing procedure: failure of one endpoint does not necessarily destroy every other hypothesis.

Closed Testing and Alpha Recycling

In more complex multiplicity strategies, Type I error can sometimes be reallocated after a hypothesis is successfully rejected.

This is often described as alpha recycling.

The idea is that rejection of one hypothesis can make some portion of the available Type I error usable elsewhere, provided the procedure is constructed to preserve strong FWER control.

Such procedures can often be represented using graphical or closed-testing frameworks.

Clinical trial implication: If alpha recycling is used, the exact transfer rules must be prespecified. It is not valid to redistribute alpha informally after seeing the results.

Closed Testing and Graphical Approaches

Graphical approaches to multiplicity provide a convenient way to represent complex alpha allocation and recycling.

A graph may specify:

  • Initial alpha weights
  • Testing priorities
  • Transition probabilities
  • Alpha recycling after rejection

The underlying statistical logic can often be understood through the closure principle.

This is particularly useful for trials containing several families of primary and key secondary endpoints.

Closed Testing in a Clinical Trial Protocol

A protocol using a closed testing strategy should describe the multiplicity procedure in enough detail that the confirmatory analysis can be reproduced without relying on post hoc decisions.

At minimum, specify:

  • The family of hypotheses
  • The elementary hypotheses
  • The intersection hypotheses
  • The local test for each relevant intersection
  • The overall Type I error level
  • The rejection rule
  • Any hierarchical relationships
  • Any gatekeeping rules
  • Any alpha recycling rules
  • How adjusted p-values will be calculated

Closed Testing in the Statistical Analysis Plan

The SAP should make the testing algorithm operationally explicit.

For example, it might specify:

Example SAP language: The family-wise Type I error rate will be controlled at the one-sided 2.5% level using a closed testing procedure. Each elementary hypothesis will be tested only if all intersection hypotheses containing that elementary hypothesis are rejected by their prespecified local tests. Adjusted p-values will be reported for all confirmatory elementary hypotheses.

The actual SAP should, of course, provide the precise statistical tests, estimands, populations, and endpoint definitions relevant to the trial.

Closed Testing and One-Sided vs. Two-Sided Alpha

The closure principle itself does not determine whether tests are one-sided or two-sided.

That decision comes from the scientific question and the prespecified confirmatory testing strategy.

For example, a trial might control:

\[ \alpha=0.025 \]

for a one-sided confirmatory test.

Alternatively, a two-sided 5% procedure may be used.

Important: The alpha convention should be established before unblinding and should be consistent with the estimand, hypothesis direction, regulatory strategy, and protocol.

Closed Testing vs. Fixed-Sequence Testing

Fixed-sequence testing is another common multiplicity strategy. Suppose:

\[ H_1\rightarrow H_2\rightarrow H_3 \]

The procedure may test \(H_1\) first, then \(H_2\), then \(H_3\), with the full significance level passed forward only after successful rejection.

Fixed-sequence testing can be extremely powerful when the ordering is scientifically justified.

Feature Closed Testing Fixed Sequence
Intersection hypotheses Central feature Not explicitly required
Requires hierarchy No Yes
Strong FWER control Yes, with valid local tests Yes
Flexibility High Lower
Useful when order is scientifically strong Yes Especially useful

Closed Testing vs. Hochberg

Hochberg's procedure is a step-up multiple testing method. It orders the p-values from largest to smallest and uses progressively less stringent critical values.

Like Holm's method, Hochberg provides strong FWER control under its required assumptions.

Closed testing is more general because it defines a framework in terms of intersection hypotheses and local tests rather than a single p-value ordering algorithm.

Closed Testing vs. Hommel

Hommel's procedure is another powerful FWER-controlling procedure related to the closure principle.

In fact, Hommel's procedure can be interpreted through closed testing using Simes-type local tests.

This illustrates a broader point: many familiar multiple-testing procedures can be understood as specialized or computationally efficient forms of closed testing.

Why Shortcuts Are Important

The theoretical closed testing family can become enormous. For \(m=20\) hypotheses:

\[ 2^{20}-1 = 1,048,575 \]

intersection hypotheses would exist.

It would be impractical to perform more than one million local tests explicitly in many applications.

Therefore, many practical procedures derive mathematical shortcuts that produce the same or equivalent rejection decisions without enumerating every intersection.

Closed Testing and Multiplicity Strategy Selection

Closed testing is not necessarily the best choice for every clinical trial. The appropriate strategy depends on the structure of the scientific questions.

Trial Situation Potential Strategy
Single primary endpoint No multiplicity adjustment may be needed for that endpoint
Multiple independent confirmatory endpoints Closed testing, Holm, Bonferroni, or other FWER procedure
Strong scientific hierarchy Fixed sequence or hierarchical testing
Primary → secondary endpoint families Gatekeeping or closed hierarchical strategy
Multiple doses Closed testing or specialized multiple-comparison procedure
Exploratory high-dimensional testing FDR procedures may be more appropriate

Closed Testing vs. FDR Control

Closed testing is primarily used when the goal is to control the family-wise error rate. False discovery rate procedures instead control the expected proportion of false discoveries among rejected hypotheses.

These are different objectives.

\[ FWER = P(V\ge1) \]

where \(V\) is the number of false rejections.

FDR is:

\[ FDR = E\left[ \frac{V}{\max(R,1)} \right] \]

where \(R\) is the total number of rejections.

Clinical trial perspective: Confirmatory clinical trials commonly prioritize strong FWER control because a single false-positive claim can have substantial regulatory and clinical consequences. FDR procedures are more commonly associated with exploratory settings involving many hypotheses.

Common Mistakes

  1. Thinking closed testing means testing each endpoint at 0.05. The elementary test alone is not sufficient. The relevant intersection hypotheses must also be rejected.
  2. Forgetting the intersection hypotheses. The intersection hypotheses are the core of the closure principle.
  3. Assuming closed testing is the same as Bonferroni. Bonferroni is one possible local testing approach; closed testing is a broader framework.
  4. Confusing strong and weak FWER control. Strong control requires validity regardless of which null hypotheses are true.
  5. Ignoring the local test. The power and behavior of a closed testing procedure depend heavily on how the intersection hypotheses are tested.
  6. Using a post hoc hypothesis hierarchy. The hypothesis structure should be prespecified.
  7. Reporting only unadjusted p-values. Confirmatory reporting should make clear how multiplicity was controlled.
  8. Assuming every closed testing procedure has identical power. Different local tests can produce substantially different power.
  9. Confusing closure with a simple testing order. A hierarchy or sequence describes testing order; closure concerns the complete intersection structure.

A Practical Closed Testing Workflow

1
Define the confirmatory family of hypotheses.
2
Define each elementary null hypothesis.
3
Construct the required intersection hypotheses.
4
Choose a valid local test for each intersection.
5
Prespecify the overall Type I error level.
6
Define the rejection rules for elementary hypotheses.
7
Perform the local intersection tests.
8
Reject each elementary hypothesis only when all containing intersections are rejected.
9
Calculate adjusted p-values where appropriate.
10
Document the complete procedure in the protocol and SAP.

R Implementation: A Simple Two-Hypothesis Example

A basic closed testing calculation can be represented directly in R. Suppose the local p-values are:

p1  <- 0.018
p2  <- 0.031
p12 <- 0.011

alpha <- 0.05

The adjusted p-values are:

p1_adj <- max(p1, p12)
p2_adj <- max(p2, p12)

p1_adj
p2_adj

The result is:

p1_adj
# 0.018

p2_adj
# 0.031

Both are below 0.05.

Decision Rules in R

reject_h1 <- p1_adj <= alpha
reject_h2 <- p2_adj <= alpha

reject_h1
reject_h2

Both hypotheses are rejected:

# TRUE
# TRUE

A Generic Function for Two Hypotheses

closed_test_2 <- function(p1, p2, p12, alpha = 0.05) {

  p1_adj <- max(p1, p12)
  p2_adj <- max(p2, p12)

  data.frame(
    hypothesis = c("H1", "H2"),
    unadjusted_p = c(p1, p2),
    adjusted_p = c(p1_adj, p2_adj),
    reject = c(
      p1_adj <= alpha,
      p2_adj <= alpha
    )
  )
}

closed_test_2(
  p1 = 0.018,
  p2 = 0.031,
  p12 = 0.011
)

Understanding the R Logic

The function works because each elementary hypothesis is compared with the largest p-value among all relevant closed-family hypotheses. For \(H_1\):

\[ p_1^{\mathrm{adj}} = \max(p_1,p_{12}) \]

For \(H_2\):

\[ p_2^{\mathrm{adj}} = \max(p_2,p_{12}) \]

The maximum operation captures the requirement that all relevant intersection tests must be significant.

Implementing a Three-Hypothesis Closure

For three hypotheses, a simple adjusted-p-value calculation can be written as:

p1   <- 0.012
p2   <- 0.041
p3   <- 0.020

p12  <- 0.025
p13  <- 0.014
p23  <- 0.035
p123 <- 0.010

p1_adj <- max(p1, p12, p13, p123)
p2_adj <- max(p2, p12, p23, p123)
p3_adj <- max(p3, p13, p23, p123)

data.frame(
  hypothesis = c("H1", "H2", "H3"),
  adjusted_p = c(
    p1_adj,
    p2_adj,
    p3_adj
  ),
  reject = c(
    p1_adj <= 0.05,
    p2_adj <= 0.05,
    p3_adj <= 0.05
  )
)

The resulting adjusted p-values are:

Hypothesis Adjusted p-value Reject at 0.05?
\(H_1\) 0.025 Yes
\(H_2\) 0.041 Yes
\(H_3\) 0.035 Yes

Closed Testing and Software

In real clinical trial analyses, closed testing is often implemented through specialized statistical procedures rather than manually calculating every intersection.

Depending on the design, software may need to account for:

  • Correlated endpoints
  • Repeated measurements
  • Time-to-event endpoints
  • Multiple treatment comparisons
  • Stratification
  • Covariate adjustment
  • Hierarchical testing
  • Graphical alpha recycling

The statistical software should reproduce the prespecified multiplicity strategy rather than determine the strategy after the data are examined.

Closed Testing and Regulatory Submissions

For confirmatory clinical trials, multiplicity procedures should be defined before the primary analysis.

The regulatory documentation should make it possible to determine:

  • Which hypotheses belong to the confirmatory family
  • Which hypotheses are elementary
  • Which intersection hypotheses are relevant
  • Which local tests are used
  • How Type I error is controlled
  • Which hypotheses can be declared successful
  • How adjusted p-values are obtained
Practical principle: A reviewer should be able to reconstruct the multiplicity decision from the protocol, SAP, and analysis output without relying on undocumented analyst judgment.

Closed Testing and Estimands

Multiplicity and estimands are different statistical concepts, but they interact in confirmatory trial design.

Each elementary hypothesis should correspond to a clearly defined scientific question and estimand.

For example, the trial might define:

\[ H_1:\theta_1\le0 \]

where \(\theta_1\) is the treatment effect under a prespecified estimand.

If the estimand changes after the multiplicity strategy has been designed, the interpretation of the hypotheses may also change.

Best practice: Define the estimands and elementary hypotheses first, then construct the multiplicity strategy around those scientific questions.

Closed Testing and Missing Data

Closed testing does not solve missing-data problems. The local tests must still be based on appropriately specified analyses and prespecified estimands.

If an endpoint has missing observations, the analysis method used to obtain its local test statistic and p-value should follow the prespecified primary analysis.

Multiplicity adjustment should then be applied to the resulting family of valid hypothesis tests.

Closed Testing Does Not Rescue a Poor Analysis

A closed testing procedure can control multiplicity only if the component tests themselves are valid.

For example, closure does not compensate for:

  • An incorrectly specified statistical model
  • Invalid variance estimation
  • Uncontrolled informative missingness
  • Post hoc endpoint definitions
  • Unplanned treatment comparisons
  • Incorrect analysis populations

Multiplicity control and model validity are separate requirements.

When Closed Testing Is Particularly Attractive

Closed testing can be especially useful when:

  • Several hypotheses are confirmatory.
  • Strong FWER control is required.
  • The hypotheses have meaningful logical relationships.
  • Different intersection tests can exploit different statistical structures.
  • The trial contains multiple endpoints or treatment comparisons.
  • Hierarchical or gatekeeping relationships are important.
  • A transparent adjusted p-value framework is desired.

When a Simpler Procedure May Be Better

Closed testing is powerful and flexible, but it can be unnecessarily complicated for simple multiplicity problems.

For example, if a study has two equally important hypotheses and no special structure, Holm's procedure may provide an easier-to-communicate solution.

Likewise, if there is a compelling fixed hierarchy, fixed-sequence testing may be more efficient and easier to explain.

Do not choose the most complicated method automatically. The best multiplicity strategy is the one that matches the scientific objectives, preserves the required error control, and can be implemented and explained clearly.

Closed Testing Design Checklist

Question Check
What is the confirmatory family? Clearly defined
What are the elementary hypotheses? Prespecified
What are the intersection hypotheses? Defined by the closure
What local test is used? Prespecified for each intersection
What is the overall alpha? Prespecified
Is strong FWER control demonstrated? Yes
Are adjusted p-values defined? Yes, where applicable
Are hierarchical relationships specified? If applicable
Are alpha recycling rules specified? If applicable
Is the strategy documented before unblinding? Yes

The Most Important Concept

The most important idea in closed testing is simple:

\[ \boxed{ \text{Reject }H_i \text{ only if every intersection hypothesis containing }H_i \text{ is rejected.} } \]

This requirement creates the logical structure that provides strong family-wise error control.

For two hypotheses:

\[ H_1,H_2,H_{12} \]

For three:

\[ H_1,H_2,H_3,H_{12},H_{13},H_{23},H_{123} \]

And in general, for \(m\) elementary hypotheses:

\[ 2^m-1 \]

nonempty intersection hypotheses form the complete closure.

Bottom line: Closed testing is a general framework for strong family-wise error control in which elementary hypotheses are embedded in a complete family of intersection hypotheses. Each intersection receives a valid local test, and an elementary hypothesis can be rejected only when every intersection containing it is rejected. This framework underlies or connects to many important multiplicity procedures, including Holm, Hommel, hierarchical testing, gatekeeping, and certain graphical procedures. Its major strength is flexibility: the local tests and logical structure can be tailored to the scientific questions of a clinical trial while preserving strong control of the family-wise Type I error rate.

References

Marcus, R., Peritz, E., & Gabriel, K.R. (1976). On closed testing procedures with special reference to ordered analysis of variance. Biometrika, 63(3), 655–660.
Holm, S. (1979). A simple sequentially rejective multiple test procedure. Scandinavian Journal of Statistics, 6(2), 65–70.
Hochberg, Y. (1988). A sharper Bonferroni procedure for multiple tests of significance. Biometrika, 75(4), 800–802.
Hommel, G. (1988). A stagewise rejective multiple test procedure based on a modified Bonferroni test. Biometrika, 75(2), 383–386.
Westfall, P.H. & Young, S.S. (1993). Resampling-Based Multiple Testing: Examples and Methods for P-Value Adjustment. Wiley.
Bretz, F., Maurer, W., Brannath, W., & Posch, M. (2009). A graphical approach to sequentially rejective multiple test procedures. Statistics in Medicine, 28, 586–604.
Dmitrienko, A., Tamhane, A.C., & Bretz, F. (2009). Multiple Testing Problems in Pharmaceutical Statistics. Chapman & Hall/CRC.