[[{"@type":["BlogPosting"],"@id":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/#BlogPosting","@context":{"@vocab":"http:\/\/schema.org\/","kg":"http:\/\/g.co\/kg"},"url":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/","publisher":[{"@id":"https:\/\/www.schemaapp.com\/#Organization"}],"audience":"https:\/\/schema.org\/PeopleAudience","inLanguage":[{"@type":"Language","@id":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/#BlogPosting_inLanguage_Language","name":"English"}],"mentions":[{"@id":"https:\/\/www.schemaapp.com\/entity#Thing6"}],"dateModified":"2024-06-06T20:26:33+00:00","headline":"Schema.org V24.0 Release: Changes to Physician Schema Markup","datePublished":"2024-01-18T18:36:17+00:00","image":[{"@type":"ImageObject","@id":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/#BlogPosting_image_ImageObject","url":"https:\/\/www.schemaapp.com\/wp-content\/uploads\/2024\/01\/Schema.org-V24.0-release-Changes-to-Physician-Schema-Markup-1.png"}],"mainEntityOfPage":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/","name":"Schema.org V24.0 Release: Changes to Physician Schema Markup","articleBody":"On January 9, 2024, Schema.org released version 24.0 of the vocabulary. In this version, the Schema.org team added vocabulary for describing types of digital sources and new clarifying subtypes for Physicians.\nAt Schema App, the ambiguity around the use of the Physician type has long been an area of contention for many of our healthcare customers. Therefore, this article will hone in on the issues around Physician Schema Markup and how the new clarifying subtypes will resolve them.\nThe Issue With Physician Schema Markup\nPrior to Schema.org\u2019s version 24 release, the Physician type was intended to represent a doctor\u2019s office. It was a subtype of MedicalBusiness via both Organization and Place, and MedicalOrganization via Organization, as shown in the hierarchy below.\n\nThing > Organization > LocalBusiness > MedicalBusiness > Physician\nThing > Place > LocalBusiness > MedicalBusiness > Physician\nThing > Organization > MedicalOrganization > Physician\n\nThis hierarchy emphasized the categorization of Physician markup as a business with a physical location.\nHowever, naming the type \u201cPhysician\u201d caused confusion regarding how to use it properly. As a result, the Physician type was usually applied to describe an individual physician rather than a physician\u2019s office with a physical location.\nYou can read more about the issue in this GitHub ticket.\nChanges to Physician Type in Schema.org v24\nTherefore, Schema.org made a few changes to the Physician type in v24 to provide users with greater clarity in their categorization.\n1. Redefined the Physician type\nThe Physician type is now defined as \u2018an individual physician or a physician\u2019s office considered as a MedicalOrganization\u2019.\n2. Removed Physician as a subtype of LocalBusiness\nThe Physician type is now exclusively a subtype of MedicalOrganization.\n3. Added usNPI property to the Physician type\nThe Physician type now also includes the usNPI (National Provider Identifier) property, a unique 10-digit identification number issued to healthcare providers in the United States by the Centers for Medicare and Medicaid Services.\n4. Introduced two new Physician subtypes: IndividualPhysician and PhysiciansOffice\nSchema.org added IndividualPhysician and PhysiciansOffice as subtypes of Physician to disambiguate between these two interpretations of the Physician type.\nNote: Schema.org version 26.0 later went on to restore PhysiciansOffice as a subtype of MedicalBusiness, after accidentally omitting it from the v24 update.\nYou can read more about it in this GitHub ticket.\n5. Added occupationalCategory property to the Physician type\nThe occupationalCategory property is used to describe a job, preferably using a term from a taxonomy such as BLS O*NET-SOC, ISCO-08 or similar. This means you can specify whether a Physician (or its subtypes) has a specific occupational category like obstetrics or pediatrics.\n6. Added new practicesAt property to the IndividualPhysician subtype\nWe will expand on this more in the section below.\nBut before that, let\u2019s learn more about the two new Physician subtypes and how to use them.\nUsing the IndividualPhysician Subtype\nThe IndividualPhysician subtype should be used to describe an entity that is an individual medical practitioner.\nThe IndividualPhysician subtype still has properties available for things like:\n\naddress\nhospitalAffiliation\navailableService\n\nHowever, it also has the new \u2018practicesAt\u2019 property, which is unavailable to either Physician or PhysiciansOffice.\nThe practicesAt property should be used to indicate the MedicalOrganization (i.e. hospital, clinic, pharmacies, etc.) where this individual physician practices. If you have the MedicalOrganization entity defined on a different page of your site, you can connect both entities using this property.\nUsing the PhysiciansOffice Subtype\nThe PhysiciansOffice subtype should be used to describe an entity that is a doctor\u2019s office or clinic.\nIt has the exact same properties as the Physician type, so you can still associate the PhysiciansOffice with a location using the address and hospitalAffiliation properties.\nShould you Update Your Physician Markup?\nIn summary, the changes made to the Physician type in v24 will allow users to describe their content with greater specificity and help search engines better understand and contextualize the content on a page.\nIf you would like to continue using the Physician type to describe the entity on your page, you can do so since the new subtypes have almost the exact same properties. However, being specific with your Schema Markup is essential for search engines to disambiguate the entities on your site, thus allowing them to provide users with more accurate and relevant search results.\nTherefore, we recommend updating your markup if you want to:\n\nClearly distinguish between an individual physician vs a physician\u2019s office,\nLeverage the practicesAt property, which is only available under the IndividualPhysician type.\n\nThe Schema App platform already supports Schema.org V24 if you want to try out the new Physician subtypes and properties. If you are a Schema App Enterprise customer, chat with your Customer Success Manager if you have questions about using these new types and properties.\nIf your healthcare organization is in need of healthcare schema expertise, we can help!\nAt Schema App, we provide an end-to-end Schema Markup solution for healthcare organizations and other enterprise SEO teams. Contact us to learn more about our solution.\nDownload our \u2018Definitive Guide to Healthcare Structured Data\u2019 to develop a comprehensive strategy to start marking up your healthcare pages.Download the eBook\n ","description":"In Schema.org's v24 release, they made a few changes to the Physician Schema Markup including adding two new subtypes for the Physician type."},{"@context":"http:\/\/schema.org","@type":"Organization","address":{"@type":"PostalAddress","streetAddress":"201 - 412 Laird Road","postalCode":"N1G 3X7","addressRegion":"Ontario","addressLocality":"Guelph","addressCountry":"https:\/\/www.schemaapp.com\/#Country","name":"Schema App Address","@id":"https:\/\/www.schemaapp.com\/#PostalAddress"},"logo":{"@type":"ImageObject","width":"290","height":"93","url":"https:\/\/ezk8caoodod.exactdn.com\/wp-content\/uploads\/2020\/07\/SA_Logo_Main_Orange_w300-1.png?strip=all&lossy=1&ssl=1","@id":"https:\/\/ezk8caoodod.exactdn.com\/wp-content\/uploads\/2020\/07\/SA_Logo_Main_Orange_w300-1.png?strip=all&lossy=1&ssl=1"},"potentialAction":{"@type":"ScheduleAction","name":"Schedule a Demo","url":"https:\/\/www.schemaapp.com\/book-a-demo\/","@id":"https:\/\/www.schemaapp.com\/#ScheduleAction"},"image":{"@type":"ImageObject","width":"1350","height":"650","url":"https:\/\/ezk8caoodod.exactdn.com\/wp-content\/uploads\/2021\/04\/Schema-App-Featured-Image.png?strip=all&lossy=1&ssl=1","@id":"https:\/\/ezk8caoodod.exactdn.com\/wp-content\/uploads\/2021\/04\/Schema-App-Featured-Image.png?strip=all&lossy=1&ssl=1"},"description":"Schema App is an end-to-end Schema Markup solution that helps enterprise SEO teams develop a knowledge graph and drive search performance.","knowsAbout":["http:\/\/www.wikidata.org\/entity\/Q1891170","https:\/\/www.wikidata.org\/wiki\/Q6108942","https:\/\/www.wikidata.org\/wiki\/Q26813700","https:\/\/www.wikidata.org\/wiki\/Q180711","http:\/\/www.wikidata.org\/entity\/Q33002955"],"keywords":["Structured Data","Knowledge Graph","Rich Results","Semantic Search","Search Engine Optimization","Schema Markup","Semantic Technology"],"location":"http:\/\/www.wikidata.org\/entity\/Q504114","sameAs":["https:\/\/www.instagram.com\/lifeatschemaapp\/","https:\/\/www.linkedin.com\/company\/2480720\/","https:\/\/twitter.com\/schemaapptool","https:\/\/www.youtube.com\/channel\/UCqVBXnwZ3YNf2BVP1jXcp6Q"],"legalName":"Hunch Manifest Inc","name":"Schema App","telephone":"+18554448624","url":"https:\/\/www.schemaapp.com\/","email":"support@schemaapp.com","knowsLanguage":"http:\/\/www.wikidata.org\/entity\/Q1860","areaServed":"http:\/\/www.wikidata.org\/entity\/Q13780930","@id":"https:\/\/www.schemaapp.com\/#Organization"},{"@context":"http:\/\/schema.org","@type":"Thing","name":"Structured Data","sameAs":["kg:\/m\/05p2j70","http:\/\/www.wikidata.org\/entity\/Q26813700","https:\/\/en.wikipedia.org\/wiki\/Structured_data"],"description":"information with a formal data model","alternateName":"Schema Markup","@id":"https:\/\/www.schemaapp.com\/entity#Thing6"}],{"@context":"https:\/\/schema.org\/","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Schema App News","item":"https:\/\/www.schemaapp.com\/schema-app-news\/#breadcrumbitem"},{"@type":"ListItem","position":2,"name":"Schema.org V24.0 Release: Changes to Physician Schema Markup","item":"https:\/\/www.schemaapp.com\/schema-app-news\/schema-org-v24-0-release-changes-to-physician-schema-markup\/#breadcrumbitem"}]}]