Clinical Tables Tools

Configuration File: clinical_tables_tools.json Tool Type: Local Tools Count: 3

This page contains all tools defined in the clinical_tables_tools.json configuration file.

Available Tools

DiseaseNames_search (Type: ClinicalTablesTool)

Disease-name autocomplete via the NLM Clinical Table Search Service (disease_names table). Given …

DiseaseNames_search tool specification

Tool Information:

  • Name: DiseaseNames_search

  • Type: ClinicalTablesTool

  • Description: Disease-name autocomplete via the NLM Clinical Table Search Service (disease_names table). Given a partial or full disease name, returns matching disease names with their UMLS Concept Unique Identifier (CUI) in the code field. Sourced from UMLS/MedlinePlus disease vocabulary. Use to normalize a free-text disease mention to a canonical disease name and UMLS CUI for cross-vocabulary linking. No API key required.

Parameters:

  • terms (string) (required) Disease name or prefix to search, e.g. ‘cystic fibrosis’, ‘lupus’, ‘sickle cell’.

  • max_results (integer) (optional) Maximum number of matches to return (default 20, max 500).

Example Usage:

query = {
    "name": "DiseaseNames_search",
    "arguments": {
        "terms": "example_value"
    }
}
result = tu.run(query)

HealthConditions_search (Type: ClinicalTablesTool)

Health-condition / problem-list autocomplete via the NLM Clinical Table Search Service (condition…

HealthConditions_search tool specification

Tool Information:

  • Name: HealthConditions_search

  • Type: ClinicalTablesTool

  • Description: Health-condition / problem-list autocomplete via the NLM Clinical Table Search Service (conditions table). Given a partial or full condition name, returns matching clinical conditions with their formal primary name, a consumer-friendly name, and a crosswalk to ICD-10-CM and ICD-9-CM codes. Use to map free-text symptoms or problems to standardized conditions and billing codes, or to build a patient problem list. No API key required.

Parameters:

  • terms (string) (required) Condition name or prefix to search, e.g. ‘diabetes’, ‘high blood pressure’, ‘asthma’.

  • max_results (integer) (optional) Maximum number of matches to return (default 20, max 500).

Example Usage:

query = {
    "name": "HealthConditions_search",
    "arguments": {
        "terms": "example_value"
    }
}
result = tu.run(query)

RxTerms_search_drugs (Type: ClinicalTablesTool)

Drug-name autocomplete via the NLM Clinical Table Search Service (RxTerms). Given a partial or fu…

RxTerms_search_drugs tool specification

Tool Information:

  • Name: RxTerms_search_drugs

  • Type: ClinicalTablesTool

  • Description: Drug-name autocomplete via the NLM Clinical Table Search Service (RxTerms). Given a partial or full drug name, returns matching prescribable drug display names along with their available strengths and dose forms (e.g. ‘500 mg Tab’) and the corresponding RxNorm RxCUI identifiers. RxTerms is the consumer-/prescriber-friendly drug terminology derived from RxNorm. Use for medication entry, dose-form lookup, and resolving a drug name to RxCUIs for downstream RxNorm/interaction queries. No API key required.

Parameters:

  • terms (string) (required) Drug name or prefix to search, e.g. ‘metformin’, ‘atorvas’, ‘insulin aspart’.

  • max_results (integer) (optional) Maximum number of matches to return (default 20, max 500).

Example Usage:

query = {
    "name": "RxTerms_search_drugs",
    "arguments": {
        "terms": "example_value"
    }
}
result = tu.run(query)