RxNorm Drug Interactions¶
Retrieves drug interaction data for one or more RxNorm concept identifiers (RxCUI) and a specified relationship type. Returns a JSON-formatted summary and a status message. Accepts a single RxCUI or a JSON array of RxCUIs and aggregates results.
Usage¶
Use this node when you need to look up potential drug interactions or related relationship data for specific RxNorm concepts. It fits into medication analysis or safety workflows, often after obtaining RxCUIs from search or concept nodes. You can query multiple RxCUIs at once and select the relationship type to explore.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| rxcui | True | STRING | RxNorm Concept Unique Identifier(s). Provide a single RxCUI as a plain string (e.g., "161") or multiple as a JSON array string (e.g., "[161, 198440]"). | [161] |
| relationship_type | True | STRING | The RxNorm relationship type to query for interactions/relations. Must be one of: boss_of, consists_of, constitutes, contained_in, contains, dose_form_of, doseformgroup_of, form_of, has_boss, has_dose_form, has_doseformgroup, has_form, has_ingredient, has_ingredients, has_part, has_precise_ingredient, has_quantified_form, has_tradename, ingredient_of, ingredients_of, inverse_isa, isa, part_of, precise_ingredient_of, quantified_form_of, reformulated_to, reformulation_of, tradename_of. | contained_in |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| drug_interactions | STRING | JSON string containing the inputs and fetched interaction data. Structure: { "rxcui": [list_of_rxcui_strings], "relationship_type": "...", "data": { " | { "rxcui": ["161"], "relationship_type": "contained_in", "data": { "161": { /* interaction/relationship payload from service */ } } } |
| status | STRING | Human-readable status message indicating success or the nature of any error. | Successfully retrieved drug interactions for RXCUI ['161'] with relationship type contained_in |
Important Notes¶
- Input format: Provide multiple RxCUIs as a JSON array string (e.g., "[161, 198440]"). A single RxCUI can be provided without brackets (e.g., "161").
- Required inputs: Both rxcui and relationship_type are required; an empty rxcui returns an error.
- Relationship types: Only the listed relationship types are supported; choose from the provided options.
- Output structure: Results aggregate per RxCUI under the data field and include the original rxcui list and relationship_type for clarity.
- API dependency: This node relies on an internal RxNorm service; any service issues will be reflected in the returned status and payload.
Troubleshooting¶
- Empty RXCUI error: If status reads "Error: RXCUI cannot be empty", ensure rxcui is a non-empty string or a valid JSON array string.
- Malformed array input: If providing multiple RXCUIs, ensure the rxcui input is a valid JSON array string (e.g., "["161", "198440"]" or "[161, 198440]").
- API Error: If status contains "API Error: ...", the underlying service returned an issue. Retry later or verify the rxcui and relationship_type.
- Unexpected results: Verify you selected the intended relationship_type. Different types return different relationship data.
- No data returned: Interaction or relationship data may not exist for the given RxCUI/type. Try alternate relationship types or validate the RxCUI.