World Health Organization (WHO) · Schema
LinearizationEntity
Class representing a linearization entity such as a category in the MMS.
HealthGlobal HealthDisease SurveillanceImmunizationHealth StatisticsICDWHOUnited NationsOpen Data
Properties
| Name | Type | Description |
|---|---|---|
| @context | string | JSON-LD Context for the endpoint |
| @id | string | unique id for this linearization entity (URI) |
| title | object | |
| definition | object | |
| longDefinition | object | |
| fullySpecifiedName | object | |
| diagnosticCriteria | object | |
| source | string | URI of the foundation entity that this entity is derived from |
| code | string | Code for the ICD-11 category |
| codingNote | object | |
| blockId | string | Block id for the block (only applicable to the blocks (groupings). e.g. BlockL2-1A0 |
| codeRange | string | Code range for the block (only applicable to the blocks (groupings) e.g. 1A00-1A0Z |
| classKind | string | Class kind for the category. It could be one of the following - chapter : if the entity is a chapter. (i.e. at the top level of the classification - block : higher level entity which don't have codes |
| child | array | List of URIs for the child entities |
| parent | array | List of URIs for the parent entity |
| ancestor | array | List of ancestors. Provided only with include=ancestor |
| descendant | array | List of descendants. Provided only with include=descendant |
| foundationChildElsewhere | array | ICD-11 Foundation allows multiple parenting which means a category could be located in more than place in the foundation component. However, this is not possible for ICD-11 linearizations such as in I |
| indexTerm | array | ICD-11 Index terms are generated from the terms (titles, inclusions, narrower terms) included in the entity as well as from the foundation entities under the linearization shore line. The IndexTerm pr |
| inclusion | array | List of inclusions for this entity |
| exclusion | array | List of exclusions for this entity |
| relatedEntitiesInMaternalChapter | array | Related entities from the maternal chapter (J) |
| relatedEntitiesInPerinatalChapter | array | Related entities from the perinatal chapter (K) |
| postcoordinationScale | array | Contains information on which axes allows or requires postcoordination for an entity together with the value set that could be used for the postcoordination |
| browserUrl | string | ICD Browser is a web site that allows users see the ICD in its hierarchical structure at the same time providing search and post-coordination features. Browser URL property provides a direct link to t |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://id.who.int/schemas/LinearizationEntity",
"title": "LinearizationEntity",
"type": "object",
"properties": {
"@context": {
"type": "string",
"description": "JSON-LD Context for the endpoint",
"nullable": true
},
"@id": {
"type": "string",
"description": "unique id for this linearization entity (URI)",
"nullable": true
},
"title": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"definition": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"longDefinition": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"fullySpecifiedName": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"diagnosticCriteria": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"source": {
"type": "string",
"description": "URI of the foundation entity that this entity is derived from",
"nullable": true
},
"code": {
"type": "string",
"description": "Code for the ICD-11 category",
"nullable": true
},
"codingNote": {
"$ref": "#/components/schemas/LanguageSpecificText"
},
"blockId": {
"type": "string",
"description": "Block id for the block (only applicable to the blocks (groupings). e.g. BlockL2-1A0",
"nullable": true
},
"codeRange": {
"type": "string",
"description": "Code range for the block (only applicable to the blocks (groupings) e.g. 1A00-1A0Z",
"nullable": true
},
"classKind": {
"type": "string",
"description": "Class kind for the category. It could be one of the following\r\n- chapter : if the entity is a chapter. (i.e. at the top level of the classification\r\n- block : higher level entity which don't have codes\r\n- category : An ICD entity that bears a code\r\n- window : A special type of grouping which don;t have children underneath but just foundationChildElsewhere",
"nullable": true
},
"child": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of URIs for the child entities",
"nullable": true
},
"parent": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of URIs for the parent entity",
"nullable": true
},
"ancestor": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of ancestors. Provided only with include=ancestor",
"nullable": true
},
"descendant": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of descendants. Provided only with include=descendant",
"nullable": true
},
"foundationChildElsewhere": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Term"
},
"description": "ICD-11 Foundation allows multiple parenting which means a category could be located in more than place in \r\nthe foundation component. However, this is not possible for ICD-11 linearizations such as in ICD-11 MMS \r\nin which a category must be located at a single location. When looking at a linearization entity, this \r\nproperty would list the foundation children that are not children in the linearization.",
"nullable": true
},
"indexTerm": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Term"
},
"description": "ICD-11 Index terms are generated from the terms (titles, inclusions, narrower terms) included in the entity\r\nas well as from the foundation entities under the linearization shore line. The IndexTerm property includes \r\nall of the index terms of a linearization entity in one place.",
"nullable": true
},
"inclusion": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Term"
},
"description": "List of inclusions for this entity",
"nullable": true
},
"exclusion": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Term"
},
"description": "List of exclusions for this entity",
"nullable": true
},
"relatedEntitiesInMaternalChapter": {
"type": "array",
"items": {
"type": "string"
},
"description": "Related entities from the maternal chapter (J)",
"nullable": true
},
"relatedEntitiesInPerinatalChapter": {
"type": "array",
"items": {
"type": "string"
},
"description": "Related entities from the perinatal chapter (K)",
"nullable": true
},
"postcoordinationScale": {
"type": "array",
"items": {
"$ref": "#/components/schemas/PostcoordinationScaleInfo"
},
"description": "Contains information on which axes allows or requires postcoordination for an entity \r\ntogether with the value set that could be used for the postcoordination",
"nullable": true
},
"browserUrl": {
"type": "string",
"description": "ICD Browser is a web site that allows users see the ICD in its hierarchical structure at the same time providing search and post-coordination features.\r\nBrowser URL property provides a direct link to the classification in the WHO's on-line ICD Browser.",
"nullable": true
}
},
"additionalProperties": false,
"description": "Class representing a linearization entity such as a category in the MMS."
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/linearizationentity"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.