Index Case¶
A recognized case episode or affected person designated as the entry point for an inquiry into related cases, without thereby identifying the earliest case or causal source.
Core Idea¶
An index case is a recognized case episode or affected person designated as the entry point for an inquiry into related cases. The designation is relative to that inquiry: it says where investigation starts, not who first acquired a condition, introduced it, or transmitted it. The CDC's outbreak definition calls the index case the first case recognized or reported during an outbreak and expressly separates that role from the outbreak's source. In partner services, the case may be a discrete episode, while the index patient is the person in whom it occurs.[1]
The role also works in a different clinical setting. In a familial-hypercholesterolemia cascade trial, genetically confirmed index patients served as family referents from whom eligible first-degree relatives could be identified and offered testing. A family referent need not be the first affected relative or a source of infection. The shared structure is recognition of a case, designation as an inquiry's starting point, and extension toward related people while origin remains a separate question.[2][1]
Structural Signature¶
Sig role-phrases:
- Defined inquiry set. An outbreak, partner-services investigation, or family inquiry defines which other people or cases are relevant. Without that set, there is no entry-point relation to designate.[1][2]
- Recognized case episode or patient. A reported episode or affected person bears the role. The case and its patient must not be silently equated: CDC partner-services conventions may count recurrent curable-STD episodes separately, whereas a person's continuous HIV infection is not newly counted at each encounter.[1]
- Ascertainment or reporting event. Diagnosis, report, or genetic confirmation supplies the operational reason this case becomes the starting point. That event does not establish earliest biological onset.[3][2]
- Related-case inquiry. Investigators extend from the recognized entry to relevant contacts, records, or relatives. Interviews, genotype comparisons, family trees, and genetic tests are setting-specific means, not required techniques of every index designation.[3][2]
- Origin nonidentity constraint. The entry role remains meaningful even if an earlier case or causal source is unknown. Calling someone the index patient does not settle who infected whom, or whether transmission is even the right relation.[1][3][2]
The first four roles identify the whole investigative use; the fifth guards the inference it licenses. A well-documented patient with no inquiry into related people is a case report, but does not yet perform this bounded entry-point role.
What It Is Not¶
The index case is not necessarily the primary case, patient zero, or the first affected family member. These labels ask about causal or temporal priority, while index designation follows recognition and the defined inquiry. In the NYC HIV investigation, investigators could not establish a definite transmission chain or determine precisely how the reported index patient acquired infection.[1][3]
Nor does the name mean the first case described in medical literature: priority of publication is different from recognition as the entry to an inquiry into related cases. An arbitrary seed in a graph search also lacks the clinical case, ascertainment, and related-case purpose. A completed contact-tracing algorithm may use an index case, but it is not the case itself.
Scope of Application¶
- Outbreak and partner-services inquiry. CDC defines a recognized or reported entry case for outbreak investigation and distinguishes episodes from patients. The NYC report begins from a newly diagnosed and reported HIV patient, then investigates named partners and potentially related genotype records. Its contact and laboratory techniques belong to that report.[1][3]
- Familial genetic cascade inquiry. The CATCH trial begins from genetically confirmed familial-hypercholesterolemia index patients, builds family trees, and offers targeted testing to eligible first-degree relatives. A positive relative can become a new case patient for a later permitted cascade cycle. Neither infectious transmission nor a first-diagnosed-family-member condition is part of that use.[2]
These are two complete, unlike medical settings supporting the bounded role. They do not establish that every first noticed item in any domain is an index case, or that all investigations use the same case unit, contact method, or outcome measure.
Clarity¶
Keep four questions apart: What counts as a case? Which patient bears it? Why was this case recognized as the inquiry's entry? What, if anything, is later inferred about origin? The CDC glossary treats a curable-STD episode and a patient's continued HIV infection differently for partner-services counting. That operational rule illustrates the case/person distinction; it is not automatically a counting rule for familial genetics.[1]
The NYC report calls its newly diagnosed and reported man the index patient and investigates possible connections to others. Highly similar HIV sequences in three other patients did not prove a definite chain or direction of transmission. A recognition event can therefore be certain enough to organize inquiry while a proposed source remains unresolved.[3]
Manages Complexity¶
A named entry case bounds the initial task: investigators can specify whose partners, records, or relatives to examine, instead of speaking vaguely of all potentially related people. In NYC, the report describes inquiry into 14 named partners and a search of genotype records. In CATCH, each confirmed family referent anchors a family tree and eligible-relative testing. The entry point organizes work; it does not by itself complete the contact network, find every eligible relative, or establish causation.[3][2]
This compression is useful because the case's role and the inquiry's result can change separately. Later evidence might identify an earlier infection or an additional family branch without retroactively making the original designation a claim to biological priority.
Abstract Reasoning¶
Consider an affected person recognized today and an earlier affected person found tomorrow. If the first person initiated inquiry into related cases, the index role describes that investigative history; the newly discovered earlier case changes a temporal hypothesis, not the reason inquiry began. Conversely, calling a famous case “first in the literature” supplies publication order but no related-person inquiry. These counterfactuals isolate designation from origin and bibliographic priority.[1][3]
The two positive cases test the same distinction in different ways. A genotype resemblance among NYC cases was insufficient to infer a definite transmission chain. In a noninfectious family cascade, a confirmed patient's role is to locate relatives who may share a pathogenic variant; no infectious source is being sought. Thus entry case travels between settings, while transmission generation, primary case, and any specific ascertainment-bias correction do not become universal roles.[3][2]
Knowledge Transfer¶
The useful transfer from outbreak contacts to familial cascade screening is an analytic checklist: define the inquiry, identify the recognized case unit, state the event that made it the starting point, describe which related people can be pursued, and keep any origin inference separate. This lets the two clinical settings be compared without treating a family pedigree as an infection chain.[1][3][2]
Outside clinical investigation, “start from a seed” may resemble this pattern. That resemblance alone does not carry the named case role into generic graph traversal: it omits disease case ascertainment and the specific inquiry into related people. A broader entry-point abstraction would require separate evidence.
Examples¶
Canonical: NYC HIV contact and genotype investigation¶
A man received a new diagnosis of multidrug-resistant, dual-tropic HIV-1 infection in December 2004 and was reported to public-health authorities in January 2005. The CDC/NYC report calls him the index patient. Investigators sought information about 14 named partners and reviewed regional HIV genotype records. Three other patients had highly similar sequences, but the available epidemiologic information did not establish a definite transmission chain or precisely how the index patient acquired infection.[3]
Mapped back: the unusual reported diagnosis and potentially related cases form the defined inquiry set; the reported man is the recognized patient; diagnosis and public-health report provide ascertainment; partner and genotype investigation provide related-case inquiry; the unresolved chain and acquisition route preserve origin nonidentity. Neither sequence resemblance nor being investigated first identifies him as the source.[3]
Applied/practice: CATCH familial-hypercholesterolemia cascade trial¶
The CATCH trial enrolled 87 genetically confirmed index patients and identified 359 eligible first-degree relatives. Family trees and counseling supported targeted genetic testing; the protocol permitted up to three cascade cycles, with a variant-positive relative able to become a new case patient. Among the 359 eligible relatives, 99 underwent genetic testing during the trial. These are trial-specific counts and permitted steps, not evidence that every family completed three cycles or that all relatives were reached.[2]
Mapped back: each confirmed patient's family and eligible relatives form the defined inquiry set; the affected, genetically confirmed family referent is the recognized patient; confirmation and enrollment provide ascertainment; family mapping and testing offer the related-case inquiry; none of these steps identifies an infectious primary case or the first affected relative, preserving origin nonidentity. The trial's digital communication platform is one outreach intervention, not part of what an index case is.[2]
Structural Tensions¶
A CATCH practice tension: relative-screening reach versus privacy-constrained patient mediation. The trial reports restrictions on clinicians directly contacting at-risk relatives. Patient-mediated communication respects that constraint, but usual counseling alone reached fewer relatives for testing than the trial's supported digital-platform arm. Trying to maximize direct clinician outreach would disregard the described privacy boundary; relying only on usual patient mediation leaves some eligible relatives untested. The platform improved participation under that boundary without reaching everyone.[2]
Diagnostic: Within the actual family communication rules, how can an inquiry extend from the index patient to eligible relatives while protecting their privacy? This tension belongs to CATCH's practice setting. It is not a defining tension in every index-case designation, and the sources do not justify a second general tension. Entry status versus source inference is a distinction to maintain, not a pressure pair to balance.
Structural–Framed Character¶
The role has a structural position—a recognized case at the entry to related-case inquiry—but is framed by clinical and public-health case rules. Its evaluative weight is whether the designation clarifies inquiry without smuggling in an origin claim; tracing yield or test uptake can assess a particular program, not define the role. Human practice matters because diagnosis, reporting, counseling, and investigation create the operational starting point.[1][3][2]
Its institutional origin is visible in CDC partner-services definitions and clinical-family cascade protocols, which can count cases differently. The vocabulary travels through words such as entry point and related case, yet disease episode, patient, and genetic-relative terms do not travel unchanged. Import versus recognition asks whether a new use genuinely has a recognized clinical case and inquiry, or only borrows the name for an arbitrary graph seed. The possible broader skeleton is a recognized item from which a related-object inquiry expands; these sources alone do not establish that as a cross-domain Prime. Its character: a portable investigative role within medical settings whose meaning depends on case ascertainment and whose designation remains distinct from causal or temporal origin.
Structural Core vs. Domain Accent¶
The skeleton is a recognized entry object relative to a defined inquiry, followed by extension to related objects, with entry order distinct from causal origin. The domain-bound mechanism is a disease case episode or affected patient, a reporting or confirmation event, and contact or pedigree inquiry into medically related people. Case episode and person may be distinct; a particular interview, genotype test, family-tree method, or digital platform is an accent rather than a necessary component.[1][3][2]
The Prime bar remains unmet. NYC contact inquiry and CATCH family cascade are unlike operations but both retain the medical case and its ascertainment. A generic selected vertex drops those conditions. Shared entry-point imagery therefore does not justify classifying this named role as a substrate-neutral Prime.
Instantiates / Related Primes¶
Selection requires an available population, a criterion or pressure, and differential retention or passage. The first reported case can become the entry to an inquiry without choosing among eligible alternatives. Network Traversal requires eligible edges, a frontier of visits, and a stopping rule; an index case can be designated before any such traversal is completed. Recognizing an entry case is therefore distinct from either full operation.[1][3][2]
Field Epidemiology concerns a rapid on-site practice of investigation, whereas the index case is a possible entry object for an inquiry. The CATCH family testing trial uses index patients without requiring that on-site practice.[2]
Neighborhood in Abstraction Space¶
Index Case sits in a sparse region of the domain-specific corpus (84th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (2721 abstractions)
Nearest neighbors
- Case-Definition Drift — 0.82
- Clinical Endpoint — 0.82
- Watchful Waiting — 0.81
- Event Sampling Methodology — 0.81
- Face — 0.81
Computed from structural-signature embeddings · 2026-10-17
Not to Be Confused With¶
- Primary case or patient zero: these imply temporal or causal origin that index designation alone does not prove.[1][3]
- Proband as an automatic synonym: the family referent can be described as an index patient, but terminology and counting rules from other genetic contexts are not established by this trial.[2]
- First case described in literature: publication priority is not recognition as the start of a related-person inquiry.
- Field Epidemiology: an investigative practice, not the affected case bearing its entry role.
- Contact-Tracing Delay or Case-Definition Drift: a timing failure or changed case boundary can affect an investigation, but neither is required for a case to be its recognized entry.
- Generic graph seed: it has no necessary case episode, patient ascertainment, or clinical relatedness.
The exit test is whether removing the recognized clinical case's relation to a defined related-case inquiry leaves only a report, a suspected source, a historical first, or an arbitrary starting vertex.
References¶
[1] CDC, Recommendations for Partner Services Programs for HIV Infection, Syphilis, Gonorrhea, and Chlamydial Infection, Appendix B, “Index case” and “Index patient,” Morbidity and Mortality Weekly Report 57(RR-9) (2008). First-party operational glossary for HIV/STD partner services; its episode-counting convention is scope-specific. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n
[2] Nanchen et al., Genetic Cascade Screening for Familial Hypercholesterolemia: A Randomized Clinical Trial, JAMA Network Open (2026), DOI 10.1001/jamanetworkopen.2026.6100. Original full text; Abstract, Participants, Cascade Procedures and Family Trees, Control and Intervention, and Results. The 87/359/99 counts and up-to-three-cycle rule are trial-specific. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q
[3] CDC and collaborating investigators, Investigation of a New Diagnosis of Multidrug-Resistant, Dual-Tropic HIV-1 Infection—New York City, 2005, Morbidity and Mortality Weekly Report 55 (2006). Original full report; opening and Case Report, Contact Investigation, Laboratory Reporting, Sequencing, and Editorial Note. The investigation names an index patient and leaves acquisition and a definite transmission chain unresolved. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p