Skip to content

IOMED Medical Language API

If you are working with clinical data, you may have notice that a staggering amount of it is stored as text. The time will come when you need to extract insights from it and... where to start?

IOMED's Medical Language API is a simple API allowing organizations, developers and researchers to extract and codify medical concepts from unstructured medical text in Spanish.


Currently we support Spanish, with limited support for Catalan. If you would like to use this API in some other language, we would be interested in hearing it. Please let us know by sending an email to


This API allows you to easily extract medical concepts from unstructured text, allowing you to either analyze existing medical text, or build applications that automatically recognize medical concepts. Some common use cases are:

  • Data standarization: use our API to obtain codified information, reusable accross different information systems.
  • Dark data extraction: turn large amounts of medical text into something useful for analysis.
    • Obtain statistics on medications, symptoms, diseases, procedures...
    • Perform profiling and clusterization of patients, find risk groups, predict outcomes...
    • Automatically monitor patients or groups of patients.
  • Conversational interfaces: out of the box Natural Language Understanding for medical topics.


Not just diagnostics

IOMED Medical Language API is able to retrieve a large variety of medically relevant concepts from medical text. It is not limited to diagnostics: you will be able to retrieve diseases, anatomical parts, substances, symptoms, diagnostic procedures, therapeutic procedures, population groups and more. Please find an exhaustive list here.


When a concept is found in medical text, its context is important: is the concept negated? is the doctor refering to the patient, or to a relative of the patient?

IOMED Medical Knowledge API is aware of the context, and will take it into account when structuring text. It is currently able to process negations and mentions of family history, and we are continuously working to add more context awareness. You can find technical information about it here.

API keys

Please visit, sign up and get your API keys. Once you have them place them in the HTTP header:

apikey: <YOUR-API-KEY>

You can test whether your API key is working with curl:

# this command should print "pong"
curl -X POST \ \
  -H 'apikey: <YOUR-API-KEY>'
  -d '{"text": "dolor"}'


Refer to Pricing and Limits. Please contact for more information.

Help us improve the docs

Did you spot a mistake or came across any unclear explanation? We always appreciate suggestions. Send us an email.