Medical concepts

API v3 is already available!

API v3 introduces significant improvements including enhanced reasoning algorithm, which provides better diagnostic and triage accuracy. The current version API v2 will be supported for the next six months, although the medical content updates will only be continued on v3. We recommend you to adapt your application to the v3 version.

Check the API v3 migration guidelines >>

Go to the API v3 documentation >>

• Conditions
• Symptoms
• Risk factors

Diagnostic information recognized by our engine is categorized as symptoms, laboratory test results and risk factors. All three categories are also collectively referred to as observations. Conditions and observations together are referred to as medical concepts.

To take advantage of the diagnostic capabilities of our API, you must describe your patient cases in terms of observations available in our model; in other words, you need to know the IDs of the observations to be passed to the /diagnosis endpoint. To make it possible to discover and search for observations, we provide a number of endpoints described in both this and following sections.

For each medical concept category, there are two REST-inspired read-only endpoints supporting GET requests:

• one returns the list of all concepts in a given category (e.g. /conditions),
• the other returns a single concept by its ID (e.g. /conditions/c_1).

Each concept is represented by a JSON object with several attributes. Some attributes are common to all concepts:

• id – short and unique concept id,
• name – concept name (professional medical term),
• common_name – alternative name (plain language). If common_name is not defined, the API returns name instead.

Please note that endpoints returning a single concept (e.g. /conditions/c_1) may return more attributes than endpoints returning a list of concepts (e.g. /conditions).

Below you can find descriptions and examples of available endpoints for the discovery of medical concepts. Additional information can be found in the API Reference.

Conditions

Conditions represent medical pathologies, conditions, diseases, and disorders defined in our model. The IDs of conditions always start with the c_ prefix followed by an integer, e.g. c_26.

Endpoints

The /conditions endpoint responds to GET requests by returning the list of all available conditions.

curl "https://api.infermedica.com/v2/conditions" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

The /conditions/{id} endpoint also responds to GET requests, returning details of a single condition. Specifying an invalid condition ID causes an error response (404).

curl "https://api.infermedica.com/v2/conditions/c_26" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

Attributes

Apart from id, name , and common_name, each condition has several available attributes:

Example of a JSON object representing a condition, as returned by /conditions/c_26:

{
  "id": "c_26",
  "name": "Major depressive disorder",
  "common_name": "Depression",
  "sex_filter": "both",
  "categories": [
    "Psychiatry"
  ],
  "prevalence": "moderate",
  "acuteness": "chronic_with_exacerbations",
  "severity": "moderate",
  "extras": {
    "hint": "I suggest you consult a psychologist or psychiatrist.",
    "icd10_code": "F33"
  }
}

See the list of all available conditions.

Symptoms

Symptoms represent medical signs and symptoms caused by conditions from our model. The IDs of symptoms always start with the s_ prefix followed by an integer, e.g. s_962.

Symptoms in our model are organized into a parent-child hierarchy. Each symptom can have a single parent symptom assigned, e.g. severe headache is a child of headache. Each parent-child relation has a type assigned. The type of each relation is provided as the parent_relation attribute and describes how the child symptom relates to its parent; e.g. the child may refer to a specific body location (e.g. lumbar back pain or back pain) or an exacerbating factor (e.g. abdominal pain increasing after a meal or abdominal pain).

The parent-child hierarchy of symptoms plays an important role in the diagnostic process:

• reporting a child symptom automatically adds its parent symptom to the evidence list
• reporting a parent symptom as absent will inform the engine not to ask about its children.

Endpoints

The /symptoms endpoint responds to GET requests by returning the list of all available symptoms.

curl "https://api.infermedica.com/v2/symptoms" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

The /symptoms/{id} endpoint also responds to GET requests, returning details of a single symptom. Specifying an invalid symptom ID causes an error response (404).

curl "https://api.infermedica.com/v2/symptoms/s_962" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

Attributes

Like conditions, symptoms have several available attributes (including id, and name and common_name):

Example of a JSON object representing a symptom, as returned by /symptoms/s_962:

{
    "id": "s_962",
    "name": "Dysphagia",
    "common_name": "Difficulty swallowing",
    "question": "Have you observed discomfort or difficulty swallowing?",
    "sex_filter": "both",
    "category": "Signs and symptoms",
    "seriousness": "serious",
    "extras": {},
    "children": [
        {
            "id": "s_1779",
            "parent_relation": "location"
        },
        {
            "id": "s_1776",
            "parent_relation": "location"
        }
    ],
    "image_url": null,
    "image_source": null,
    "parent_id": null,
    "parent_relation": null
}

See the list of all available symptoms (only for registered users).

Risk factors

Risk factors represent a patient’s chronic conditions (e.g. diabetes), lifestyle factors (e.g. smoking), geographical locations (e.g. Central Africa), and events (e.g. insect bite or head injury) that may modify the baseline probability of conditions. The IDs of risk factors always start with the p_ prefix (as in predisposition) followed by an integer, e.g. p_28.

Endpoints

The /risk_factors endpoint responds to GET requests by returning the list of all available risk factors.

curl "https://api.infermedica.com/v2/risk_factors" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

The /risk_factors/{id} endpoint also responds to GET requests, returning details of a single risk factor. Specifying an invalid risk factor ID causes an error response (404).

curl "https://api.infermedica.com/v2/risk_factors/p_28" \
  -X "GET" \
  -H "App-Id: XXXXXXXX" \
  -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

Attributes

These are the attributes available for a risk factor (including id, and name and common_name):

Example of a JSON object representing a risk factor, as returned by /risk_factors/p_28:

{
    "id": "p_28",
    "name": "Smoking",
    "common_name": "Smoking",
    "question": "Do you smoke?",
    "sex_filter": "both",
    "category": "Risk factors",
    "extras": {},
    "image_url": null,
    "image_source": null
}