DATABASE TERM AUTHORITY
The authority file for anatomy terms used in the anatomical database is the UMLS metathesaurus. Anatomy terms are defined by a UMLS concept UI and a string ID (UI | ID):
Since the character 'C' is constant for all anatomical UMLS UIs, it is not included in the term UI. The UMLS metathesaurus did not exhaust the set of all anatomical terms during the development of the anatomical database. Therefore temporary concept UIs were created when newly segmented structures are added to the database. New concept UIs were created by modifying a closely related UMLS UI. Presently all anatomical database terms imported from the UMLS metathesaurus begin with the character '0'. Therefore new terms were generated my modifying the first '0' in the UI and attaching 6 trailing characters of an existing UI:
The image database defines a lexicon for identifying anatomical relations. This lexicon is the relational mapping source for all anatomical database terms.
String ID: (UMLS ID, ASCII)
Anatomical Parent: (7 byte UMLS UI)
Structure type: (1 byte,S-> structure, P-> System, R-> Region)
Physiological: Systems (array 7 byte UMLS UIs, 4 max)
Body region: (array 7 byte UMLS UIs, 4 max)
Concept UI: (7 byte UMLS UI)
Has_Parts: (Anatomical substructures, 7 byte UMLS UI)
The UMLS string ID (preferred name) for each anatomy term.
Anatomical parents are the superior anatomy structure for a specific anatomical part. Anatomical parents are of the same structure type as its child structure.
Presently three structure types are defined: anatomical structures of type ‘S’, physiological systems of type ‘P’, and body regions of type ‘R’. Anatomical structures (type S) are the various body parts such as organs, tissue, bone, muscle, etc.
Physiological systems are collections of anatomical structures that perform related body processes and functions. Lexical entries of structure types ‘P’ represent the various physiological systems for the body. ie, respiratory system, cardiovascular system, etc.
Body Regions are collections of anatomical structures located within a given division or subdivision of the human body. Lexical entries of structure types ‘R’ represent the various regions for the body. ie, head, thorax, abdomen, etc.
The UMLS UI(tag) for each anatomy term.
Has_Parts represent the child structures of an anatomical entity. As an example, the Right Lung lexical entry will have Has_Parts which includes its upper lobe, middle lobe, lower lobe, etc).
Excluding generic images of the Visible Human data set, all image data imported to the database are submitted as file pairs, an image file and knowledge frame file.
Catalog objects contain data for each anatomical structure submitted and processed within the database. knowledge frame file data is validated and stored within a catalog object. Catalog objects are identified and linked by their UMLS ID, specimen ID, and relationship to other catalog objects.
A file object is created for each image processed for database storage. Imported images are initially stored as file attachments to a knowledge frame file. File objects are created as images are processed into an approved file format. These objects are linked to one or more catalog objects.