xiphoid process in dogs
A cartilaginous extension to the distal part of the sternum. Every claim on this page comes from the Leumas anatomy graph and carries its source.
What the xiphoid process is
A cartilaginous extension to the distal part of the sternum. The atlas records it as a bone at the organ scale in the dog.
Where the xiphoid process is
It sits in the thorax and trunk, within the skeletal system. Not positioned individually. Drawn inside the structure this dataset says contains it — the containment is asserted, the exact spot within it is not.
What the xiphoid process connects to
The atlas records 7 typed relationships for it, across 4 kinds of connection. part of multicellular organism, organ and skeletal element, and 1 more.
Supply and innervation
This dataset asserts no arterial supply, venous drainage or innervation for the xiphoid process. Only a minority of structures carry those edges here, so an empty answer means nothing has been recorded — not that there is nothing to record.
Also called
Also recorded as xiphisternum, xiphoid process, xiphoid process of sternum, metasternum, processus xiphoideus and xiphoid, and 3 more. Searching any of those names reaches this page.
Source
Uberon multi-species anatomy ontology (Mungall et al.), CC BY 4.0. Term UBERON:0002207, version 2026-06-19, retrieved 2026-08-24. Licence: CC-BY-4.0.
- Part of: multicellular organism, organ, skeletal element and sternum.
- A kind of: anatomical structure.
- inserts into: abdominal internal oblique muscle.
- contains: xiphoid cartilage.
Questions
Where is the xiphoid process?
It sits in the thorax and trunk, within the skeletal system. Not positioned individually. Drawn inside the structure this dataset says contains it — the containment is asserted, the exact spot within it is not.
What does the xiphoid process connect to?
Part of: multicellular organism, organ, skeletal element and sternum.
Is the xiphoid process the same in other species?
This page describes the dog. The human record of the same structure sits beside it on /compare, over one shared model rather than two atlases built separately.