AnatomicalSystem
AnatomicalSystem sits beside AnatomicalStructure under MedicalEntity. Where AnatomicalStructure is a single organ, bone, or muscle, AnatomicalSystem is the collaborating group: the cardiovascular system, the nervous system, the endocrine system.
Full example of schema.org/AnatomicalSystem json-ld markup
The markup is verified as valid with Rich Results Test from Google.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AnatomicalSystem",
"name": "Cardiovascular system",
"associatedPathophysiology": "Hypertension, atherosclerosis, arrhythmia, thromboembolism, heart failure.",
"comprisedOf": [
{ "@type": "AnatomicalStructure", "name": "Heart" },
{ "@type": "AnatomicalStructure", "name": "Aorta" },
{ "@type": "AnatomicalStructure", "name": "Coronary arteries" },
{ "@type": "AnatomicalStructure", "name": "Capillary bed" }
],
"relatedCondition": [
{ "@type": "MedicalCondition", "name": "Ischemic heart disease" },
{ "@type": "MedicalCondition", "name": "Stroke" }
],
"relatedTherapy": { "@type": "MedicalTherapy", "name": "Cardiac rehabilitation" }
}
</script>Direct properties (5)
comprisedOf: AnatomicalStructure or AnatomicalSystem — component members (heart + vessels, hypothalamus + pituitary + adrenals).relatedStructure: AnatomicalStructure — a structure associated with but not part of the system.associatedPathophysiology: Text — what goes wrong when the system fails (hypertension, arrhythmia, thromboembolism for cardiovascular).relatedCondition: MedicalCondition — diseases that affect the system.relatedTherapy: MedicalTherapy — therapies targeting the system.
Minimal valid version
The smallest markup that still produces a valid AnatomicalSystem entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AnatomicalSystem",
"name": "Cardiovascular system"
}
</script>Google rich results this unlocks
Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.
- Google docsNo dedicated rich result (medical reference markup)
Common AnatomicalSystem mistakes
Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.
- 01
AnatomicalSystem used for a single organ
Wrong"@type": "AnatomicalSystem", "name": "Heart"Right"@type": "AnatomicalStructure" for a single organ; "AnatomicalSystem" for the collaborating groupAn organ is a structure; a system is a collection of structures that work together. Cardiovascular system = heart + vessels, not just heart.
- 02
comprisedOf as a string
Wrong"comprisedOf": "Heart, arteries, veins"RightArray of AnatomicalStructure / AnatomicalSystem nodesFree text hides the component relationships crawlers and medical knowledge graphs walk through.
- 03
relatedCondition and associatedPathophysiology both filled with the same diseases
WrongDuplicating disease names in both fieldsRightassociatedPathophysiology is free text describing mechanisms and manifestations; relatedCondition points to MedicalCondition entitiesPathophysiology = the story of what fails; relatedCondition = the structured link to the named disease entity. They complement rather than duplicate.
Schema properties in this example
Also mentioned in 8 other examples
AnatomicalSystem also appears in AnatomicalStructure, Joint, LymphaticVessel, MedicalCondition, Muscle, Nerve, PhysicalActivity, and Vein. See the full AnatomicalSystem schema page for every reference.
About the example data
Reference entry from the Dunmore Medical Archive — the cardiovascular system as a teaching-level anatomical system page, the parent of the case studies Jane Xoo filed in 1945.
Comments
Loading comments...