Anatomic scope
“The eligible anatomical places, tissue types, or structure types for a definition. A plain list matches any one target by default; explicit combinations can require multiple conditions to hold together.”1 Scope is a constraint on where a definition may be used, not a statement of where a particular finding was seen.
The next-generation vocabulary names two scope families. Tissue-type scope is “exemplified by pulmonary parenchyma, hepatic parenchyma, and subcutaneous fat.” Structure-type scope is “exemplified by solid organs, vessels and their artery/vein subtypes, muscles, tendons, and ligaments.” Both are collected under an anatomy scope specifier, and how these families connect to the anatomic location hierarchy is recorded as open.1
OIDM’s authoring guidance states the same requirement in prose rather than as a typed field: “broad findings should be scoped to assessable anatomy. The scope of a finding model should match what’s assessable on a given exam type, not broader.” Fracture is too broad, chest wall fracture is appropriately scoped for a chest radiograph, and upper abdominal abnormality is appropriately scoped for chest CT because the upper abdomen is in the field of view.2
Synonyms and near-synonyms
- Scope unqualified, in finding-model authoring discussions, usually means this.
- Anatomic location is the instance-level assignment; scope is definition-level eligibility.
- Component-of scope is a different constraint: which FindingClasses a component class may sit inside.
- Exam-scoped coarse region is the fallback rule the extraction pipeline applies when a finding has no anatomic noun at all.3
Identifier form
None. Scope is expressed as a list of concepts or scope specifiers.
Where it is used
Next-generation vocabulary, Why finding models, and Exam types overview.
Conflicts
There is no scope field in the OIFM format. Scope exists only as authoring guidance and as reviewer judgment, so it cannot be checked mechanically the way a typed scope specifier could.