Skip to content

Inclusion/Exclusion Register Review

Record review — instantiates Boundary Critique Audit

Audits the documented in/out record itself — the register of who and what was formally included or excluded — against evidence, to catch exclusions that were logged but never justified.

An Inclusion/Exclusion Register Review audits the paper record of a boundary: the formal register that logs what was admitted, what was excluded, and the reason attached to each decision. Its defining feature is that its object is a document, not a live system or a set of people — it works where the boundary is formal enough to have been written down, and it interrogates whether the recorded exclusions were applied consistently and are backed by anything more than a routine label. It is a desk review: it does not go out to the excluded parties or elicit fresh testimony. It re-reads the ledger of decisions already made and asks which entries, though they look procedural, are quietly deciding the outcome.

Example

A clinical-guideline panel is drafting a recommendation on blood-pressure screening, built on a systematic review whose register logs 4,200 records screened down to 38 included studies, each exclusion tagged with a reason. A register review audits that log rather than re-running the search. It reads down the exclusion column and finds two patterns the tally hid. A cluster excluded as "non-English" turns out to be the only trials conducted in low-income settings, so the recommendation is being built on high-income evidence alone. A cluster excluded as "unpublished" is disproportionately null-result industry trials, whose omission tilts the pooled effect toward benefit.

The review's output is a findings record. It separates the plainly justified exclusions (duplicates, wrong outcome measured) from the two consequential ones, states that the non-English and unpublished exclusions likely bias the recommendation, and recommends either re-including them or disclosing the limitation on the guideline's face. It never interviews a trial author or maps the wider field — it audits the register against the evidence the register itself claims to rest on.

How it works

  • Pull the documented register. Obtain the formal in/out log with the reason attached to each entry; the audit's whole target is this record.
  • Test each exclusion reason. Check that each recorded reason was applied consistently and is backed, not just a routine label doing quiet work.
  • Look for consequential clustering. Flag where exclusions concentrate on a dimension that bends the result — geography, funding source, outcome sign, language.
  • Record findings. Produce a findings record that separates justified exclusions from biasing ones and states a recommended action for each flagged entry.

Tuning parameters

  • Sampling depth — audit every register entry or a sample. Full coverage catches rare but decisive exclusions; sampling is faster but can miss the one that matters.
  • Reason-taxonomy granularity — how finely exclusion reasons are categorized. Finer categories expose inconsistent application; coarser ones hide it.
  • Consistency lens — whether the same reason was applied evenly to included and excluded items alike. Asymmetric application is the loudest signal of a boundary bent to a conclusion.
  • Reviewer independence — whether the auditor is separate from those who built the register. Independence surfaces self-serving exclusions the authors normalized.
  • Audit vs. re-adjudicate — whether the review only flags or actually re-decides entries. Flagging preserves the original owners' authority; re-adjudicating is faster but concentrates power in the auditor.

When it helps, and when it misleads

Its strength is catching the exclusion that reads as routine but bends the whole result — the language filter that erases a whole region, the publication filter that launders a null result. It is the discipline behind transparent evidence synthesis, exemplified by the PRISMA flow diagram, which requires every included and excluded record to be counted and reason-tagged precisely so a review like this is possible.[n1]

Its failure mode is that a register review can only audit what was written down. A silent exclusion — an item never entered because it was dismissed before logging — is invisible to it, so a clean register can hide an opaque evidence base. The classic misuse is treating the audited register as complete and pronouncing the boundary sound when the real distortion happened upstream of the log. The guarding discipline is to treat the register as necessary but not sufficient: cross-check it against a small sample of what the register does not contain, so the audit does not certify a boundary whose worst exclusions were never recorded.

How it implements the components

  • current_inclusion_exclusion_record — the register it audits: the documented log of what the boundary treats as inside, outside, and deferred, with reasons.
  • audit_findings_record — its output: findings that separate justified exclusions from biasing ones and attach a recommended action to each flagged entry.

Inclusion/Exclusion Register Review works from the paper record; it does not run the stakeholder_analysis of the excluded parties or open a contestation_channel for them — that is Stakeholder Exclusion Audit; the register review reads the ledger, it does not go out to the people the ledger left off.

Editorial Notes

Form Classification

Form family: Assessment, Review & Assurance

Rationale: Inclusion/Exclusion Register Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it audits the documented in/out record itself — the register of who and what was formally included or excluded — against evidence, to catch exclusions that were logged but never justified

Independent corroboration: The frozen evidence defines Inclusion/Exclusion Register Review as 'Audits the documented in/out record itself — the register of who and what was formally included or excluded — against evidence, to catch exclusions that were logged but never justified', so its operative form is Assessment, Review & Assurance.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution

Primary origin: Medicine & Healthcare

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: The explicit anchor is PRISMA systematic-review practice, which records every study included or excluded with reasons.

Related originating lineages:

Review resolution: PRISMA makes explicit inclusion/exclusion criteria and records of screened studies central to systematic-review transparency. Statistical design shapes sampling validity, but the register-review form is directly rooted in evidence-based medicine and health research. The retained alternate domains identify independent or materially shaping provenance, not downstream reach alone. domain_reach=multi_domain because the mechanism has independent established use in several fields. The encyclopedia entry deliberately composes those lineages.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.

Review outcome: Researched adjudication after independent review; high confidence.

Sources consulted:

Notes

[n1] PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) is a reporting standard whose flow diagram requires every record screened, included, and excluded to be counted with reasons, making the inclusion/exclusion register an inspectable object rather than a hidden step — the precondition for auditing it.