Disease DRAFT Profile

Version: 0.2-DRAFT (11 November 2022)

If you spot any errors or omissions with this type, please file an issue in our GitHub.

Schema.org hierarchy

This Profile fits into the schema.org hierarchy as follows:

Thing > MedicalEntity > MedicalCondition

Description

This is the first draft of the Disease profile, using MedicalCondition type from schema.org as template for inheriting some properties. Version 0.2-DRAFT.

Summary of Changes

Changes since 0.1-DRAFT:

added sameAs as recommended

Latest profiles

Latest release: none

Latest draft: 0.2-DRAFT

Previous profiles

Previous version: 0.1-DRAFT

Previous release:

Contributors

The following people have been involved in the creation of this specification document. They are all members of the Diseases group.

Group Leader(s)

Marc Hanauer

Marco Roos

Other team members

Rajaram Kaliyaperumal

Group	Use Cases	Cross Walk	Task & Issues	Examples	Live Deploys
Diseases

You can read the release version of this specification here.

Key to specification table

Green properties/types are proposed by Bioschemas, or indicate proposed changes by Bioschemas to Schema.org
Red properties/types exist in the core of Schema.org
Blue properties/types exist in the pending area of Schema.org
Black properties/types are reused from external vocabularies/ontologies

CD = Cardinality

Property	Expected Type	Description	CD	Controlled Vocabulary	Example
Marginality: Minimum.
@context	URL	Used to provide the context (namespaces) for the JSON-LD file. Not needed in other serialisations.	ONE		Property ≪@context≫ example `{ "@context": "https://schema.org/" }`
@type	Text	Schema.org/Bioschemas class for the resource declared using JSON-LD syntax. For other serialisations please use the appropriate mechanism. While it is permissible to provide multiple types, it is preferred to use a single type.	MANY	Schema.org, Bioschemas	Property ≪@type≫ example `{ "@type": "MedicalCondition" }`
@id	IRI	Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach.	ONE		Property ≪@id≫ example `{ "@id": "http://example.com/entity/A12345" }`
dct:conformsTo	IRI	Used to state the Bioschemas profile that the markup relates to. The versioned URL of the profile must be used. Note that we use a CURIE in the table here but the full URL for Dublin Core terms must be used in the markup (http://purl.org/dc/terms/conformsTo), see example.	ONE	Bioschemas profile versioned URL	Property ≪dct:conformsTo≫ example `{ "http://purl.org/dc/terms/conformsTo": { "@id": "https://bioschemas.org/profiles/Disease/0.2-DRAFT", "@type": "CreativeWork" } }`
identifier	PropertyValue Text URL	Schema: The identifier property represents any kind of identifier for any kind of [[Thing]], such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.	ONE
name	Text	Schema: The name of the item.	ONE
Marginality: Recommended.
description	Text	Schema: A description of the item.	ONE
drug	Drug	Schema: Specifying a drug or medicine used in a medication procedure.	MANY
image	ImageObject URL	Schema: An image of the item. This can be a [[URL]] or a fully described [[ImageObject]].	ONE
sameAs	URL	Schema: URL of a reference Web page that unambiguously indicates the item’s identity. E.g. the URL of the item’s Wikipedia page, Wikidata entry, or official website.	MANY
url	URL	Schema: URL of the item. Link to the official webpage associated to this entity.	ONE
Marginality: Optional.
alternateName	Text	Schema: An alias for the item.	MANY
disambiguatingDescription	Text	Schema: A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.	MANY