XooCode(){

MedicalDevice

MedicalDevice is a direct MedicalEntity subtype for hardware used in clinical care: implants, surgical instruments, diagnostic equipment, infusion pumps, monitors. It has 6 direct properties:

  • preOp (Text): pre-operative workup and patient preparation.
  • procedure (Text): how the device is used or installed.
  • postOp (Text): post-operative procedures, follow-up, monitoring.
  • contraindication (MedicalContraindication or Text): when the device must not be used.
  • adverseOutcome (MedicalEntity): possible complications and side effects.
  • seriousAdverseOutcome (MedicalEntity): serious complications, including life-threatening or surgery-requiring events.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/MedicalDevice
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": ["MedicalDevice", "Product"],
  "name": "XooMonitor C-100 Continuous Cardiac Monitor",
  "manufacturer": { "@type": "Organization", "name": "XooMed Devices" },
  "model": "C-100",
  "identifier": [
    { "@type": "PropertyValue", "propertyID": "FDA-UDI", "value": "(01)00012345678905" },
    { "@type": "PropertyValue", "propertyID": "CE", "value": "0123" }
  ],
  "preOp": "Confirm patient skin integrity at electrode sites; clip excess hair; clean and dry skin; verify battery and lead status.",
  "procedure": "Apply 5-lead ECG harness per anatomical guide; connect to bedside monitor or telemetry receiver; calibrate gain and sensitivity; verify continuous trace before leaving patient.",
  "postOp": "Inspect electrode sites every 24 hours; replace electrodes every 48 hours or with adhesion loss; document any skin reactions; download trace at end of monitoring period.",
  "contraindication": [
    { "@type": "MedicalContraindication", "name": "Severe skin reaction to medical-grade adhesive", "description": "Use alternative monitoring approach in patients with documented severe adhesive allergy." }
  ],
  "adverseOutcome": [
    { "@type": "MedicalEntity", "name": "Skin irritation at electrode sites" },
    { "@type": "MedicalEntity", "name": "False arrhythmia alerts from electrode displacement" }
  ],
  "seriousAdverseOutcome": [
    { "@type": "MedicalEntity", "name": "Missed arrhythmia from disconnected lead — verify continuous trace and use telemetry alarms" }
  ],
  "relevantSpecialty": "https://schema.org/Cardiovascular"
}
</script>

MedicalDevice vs Product

For a manufacturer's product-catalogue listing of a medical device, dual-type as ["MedicalDevice", "Product"]. The Product side carries SKU, brand, GTIN, offers, and shipping; the MedicalDevice side carries the clinical metadata. Search engines and shopping graphs read the Product properties; healthcare graphs and AI assistants read the MedicalDevice properties.

Regulatory identifiers (FDA UDI, CE mark, Health Canada licence) belong on a PropertyValue attached via identifier with a propertyID indicating the registry.

Minimal valid version

The smallest markup that still produces a valid MedicalDevice 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/MedicalDevice (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalDevice",
  "name": "XooMonitor C-100 Continuous Cardiac Monitor",
  "procedure": "Apply 5-lead ECG harness; connect to monitor; verify trace.",
  "contraindication": "Severe adhesive allergy"
}
</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.

  • Product rich result (via dual-typed Product); medical-knowledge-graph signal
    Google docs

Common MedicalDevice 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

    MedicalDevice without procedure

    Wrong
    Bare MedicalDevice with name only
    Right
    Always populate at least procedure (and ideally pre/post-op) — the clinical guidance is the value

    Without procedure, MedicalDevice carries no more information than a Product. The clinical-use detail is what the type is for.

  2. 02

    Storing FDA UDI in name

    Wrong
    name including the UDI bracketed string
    Right
    identifier with PropertyValue.propertyID = "FDA-UDI"

    Regulatory identifiers belong in identifier; mixing them into name pollutes display surfaces and breaks UDI lookup.

  3. 03

    Single MedicalDevice typing on a sold device

    Wrong
    "@type": "MedicalDevice" only on a manufacturer's catalogue listing
    Right
    Dual-type ["MedicalDevice", "Product"] so both shopping and clinical graphs see it

    Manufacturers care about both audiences; dual-typing is the established pattern.

Schema properties in this example

MedicalDeviceMedicalEntityProductnamemanufacturerOrganizationmodelidentifierPropertyValuepropertyIDvaluepreOpprocedurepostOpcontraindicationMedicalContraindicationadverseOutcomeseriousAdverseOutcomerelevantSpecialtyMedicalSpecialtyCardiovascular

Also mentioned in 1 other example

MedicalDevice also appears in MedicalTest. See the full MedicalDevice schema page for every reference.

About the example data

The XooMonitor C-100, a fictional FDA-cleared continuous cardiac monitor used at Dunmore Regional Hospital's cardiology unit.

Comments

Loading comments...

Leave a comment