XooCode(){

MedicalDevicePurpose

MedicalDevicePurpose is a 2-value MedicalEnumeration on MedicalDevice.purpose. Values: Diagnostic, Therapeutic.

Full example of schema.org/MedicalDevicePurpose json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/MedicalDevicePurpose
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalDevice",
  "name": "ECG machine",
  "purpose": "https://schema.org/Diagnostic"
}
</script>

Minimal valid version

The smallest markup that still produces a valid MedicalDevicePurpose 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.

schema.org/MedicalDevicePurpose (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalDevice",
  "purpose": "https://schema.org/Diagnostic"
}
</script>

Google rich results this unlocks

MedicalDevicePurpose is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). MedicalDevicePurpose becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common MedicalDevicePurpose 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.

  1. 01

    purpose as a sentence

    Wrong
    "purpose": "For diagnosing heart rhythm"
    Right
    "purpose": "https://schema.org/Diagnostic" + use description for prose

    The purpose field is the enum; prose belongs in description.

About the example data

Classifies Dunmore inventory by diagnostic vs therapeutic device purpose.

Comments

Loading comments...

Leave a comment