Related symptoms

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

Request
Response

Providing initial symptoms and risk factors is crucial for the /diagnosis to return meaningful results. There are different ways of gathering the initial evidence from a user, with the /search and /parse endpoints being the most useful. The /suggest endpoint aims to further enhance this process in interactive applications by encouraging users to provide additional symptoms. This is achieved by suggesting other possible symptoms that have frequently been reported by other users of the same sex and similar age. The /suggest endpoint also takes into account previously reported evidence. The AI behind the /suggest endpoint has been trained on data from several million interviews already performed by the Infermedica API.

After a user of your application selects some symptoms with /search or /parse, you can use /suggest to generate suggestions of other symptoms that might be present (think of a recommendation system such as "Other users with your symptoms also reported..."). The /suggest endpoint can also be used without sending any selected symptoms, in order to generate a list of the most commonly reported symptoms. This can be useful before or instead of /search in some scenarios.

Please note, however, that /suggest shouldn't be used as a replacement for /diagnosis. The /suggest endpoint cannot perform differential diagnosis and uses a different statistical engine. After you've gathered 3-6 initial symptoms, you're safe to start making calls to /diagnosis.

The /suggest endpoint is available in all languages, but can only work with the Infermedica default model.

Request

The /suggest endpoint responds to POST requests of the same structure as /diagnosis:

curl "https://api.infermedica.com/v2/suggest" \
  -X "POST" \
  -H "App-Id: XXXXXXXX" -H "App-Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
  -H "Content-Type: application/json" -d '{
        "age" : 25,
        "sex" : "female",
        "evidence" : [ 
            {
                "choice_id" : "present",
                "id" : "s_305"
            }
        ]
}'

The example above describes the case of a 25 year old female patient who has already reported vomiting (represented here by the symptom ID s_305).

Response

The response contains a list of symptoms that have often been reported together with the provided observations by other patients of the same sex and similar age. Each returned symptom is represented by a JSON object with the following attributes: id, name , and name_common. These values are consistent with the database of medical concepts understood by the Infermedica API.

[
    {
        "id": "s_156",
        "name": "Nausea",
        "common_name": "Feeling sick"
    },
    {
        "id": "s_13",
        "name": "Abdominal pain",
        "common_name": "Stomach pain"
    },
    {
        "id": "s_8",
        "name": "Diarrhea",
        "common_name": "Diarrhea"
    }
]

Please note that the free trial plan for Infermedica API allows for only a limited number of calls to the /suggest endpoint. Please contact us for other plan options.

Medical concepts Red flags