XooCode(){

DiagnosticLab

DiagnosticLab is a direct MedicalOrganization subtype for clinical laboratories: bloodwork, microbiology, molecular diagnostics, genetic testing, pathology, toxicology, imaging-read facilities. It is notable for being a MedicalOrganization without MedicalBusiness in its parent chain, which means it is not a LocalBusiness in schema.org's sense; the LocalBusiness-style properties (address, openingHours) still work via Organization, but Google's local-business rich result is not the primary target.

It adds 1 direct property:

  • availableTest (MedicalTest): the catalogue of tests the lab runs. Array-valued; DiagnosticLabs can list hundreds of tests.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/DiagnosticLab
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DiagnosticLab",
  "@id": "https://lackawannadiag.example/#lab",
  "name": "Lackawanna Diagnostic Services",
  "url": "https://lackawannadiag.example",
  "description": "CLIA-accredited regional reference laboratory serving Lackawanna and surrounding counties. Blood chemistry, hematology, microbiology, molecular diagnostics, histopathology.",
  "telephone": "+1-570-555-0320",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "50 Industrial Drive",
    "addressLocality": "Dunmore",
    "addressRegion": "PA",
    "postalCode": "18512",
    "addressCountry": "US"
  },
  "medicalSpecialty": "https://schema.org/LaboratoryScience",
  "availableTest": [
    { "@type": "MedicalTest", "name": "Complete blood count (CBC)" },
    { "@type": "MedicalTest", "name": "Comprehensive metabolic panel (CMP)" },
    { "@type": "MedicalTest", "name": "Lipid panel" },
    { "@type": "MedicalTest", "name": "Hemoglobin A1c" },
    { "@type": "MedicalTest", "name": "Thyroid-stimulating hormone (TSH)" },
    { "@type": "MedicalTest", "name": "SARS-CoV-2 PCR" },
    { "@type": "MedicalTest", "name": "Histopathology (surgical biopsy review)" }
  ],
  "paymentAccepted": "Aetna, Blue Cross, Cigna, Medicare, Medicaid, UnitedHealthcare",
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "06:30",
    "closes": "18:00"
  }
}
</script>

Why DiagnosticLab is shaped this way

Most diagnostic labs do not have walk-in patients; they receive specimens from physicians and clinics and return results. The primary consumers of DiagnosticLab markup are insurance directories, health-information exchanges, and AI healthcare assistants that need to answer "where can my doctor send this test?"

Minimal valid version

The smallest markup that still produces a valid DiagnosticLab 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/DiagnosticLab (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "DiagnosticLab",
  "name": "Lackawanna Diagnostic Services",
  "availableTest": [{ "@type": "MedicalTest", "name": "Complete blood count (CBC)" }]
}
</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.

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

    availableTest as free strings

    Wrong
    "availableTest": ["CBC", "CMP", "A1c"]
    Right
    Typed MedicalTest objects: { @type: MedicalTest, name: "Complete blood count" }

    Typed tests resolve to the healthcare knowledge graph; bare strings are ignored by test-matching consumers.

  2. 02

    DiagnosticLab on an imaging centre

    Wrong
    DiagnosticLab on a facility whose output is imaging, not lab assays
    Right
    MedicalClinic with medicalSpecialty: Radiography

    DiagnosticLab implies clinical-laboratory assays. Radiology / imaging centres are better modelled as MedicalClinic or ImagingLab (where supported).

  3. 03

    Omitting medicalSpecialty

    Wrong
    Plain DiagnosticLab with no medicalSpecialty
    Right
    Always set medicalSpecialty: LaboratoryScience (or a more specific child)

    The specialty signal is what lets healthcare consumers route orders to the right lab.

Schema properties in this example

DiagnosticLabMedicalOrganizationnameurldescriptiontelephoneaddressPostalAddressmedicalSpecialtyLaboratoryScienceavailableTestMedicalTestpaymentAcceptedopeningHoursSpecification

About the example data

Lackawanna Diagnostic Services, a fictional regional reference lab running CBCs, metabolic panels, histopathology, and molecular diagnostics.

Comments

Loading comments...

Leave a comment