RxNorm Concept Info¶
Retrieves detailed information for a specific RxNorm concept (RxCUI). You supply a JSON array of RxCUIs and choose which index to inspect, then select the type of information to fetch (name, NDCs, properties, or all related data). Returns a JSON-formatted payload with the requested data, the selected RxCUI, and a status message.
Usage¶
Use this node after you have a list of candidate RxCUIs (for example, from a drug search). Feed the JSON array of RxCUIs into this node, set the index of the RxCUI you want to examine, and pick the info_type that matches your needs. Typical workflow: Search for drugs → get list of RxCUIs → pass into this node to retrieve concept name, associated NDCs, core properties, or full related concept graph.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| rxcuis | True | STRING | A JSON array of RxNorm Concept Unique Identifiers (RxCUIs) as strings. The node will parse this JSON and pick one RxCUI by index. | ["161", "7052", "1234"] |
| selected_rxcui | True | INT | Zero-based index into the rxcuis array indicating which RxCUI to use. | 0 |
| info_type | True | CHOICE | Type of information to retrieve for the selected RxCUI. Options: name (concept name), ndcs (associated National Drug Codes), properties (concept properties), all_related (comprehensive related information). | properties |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| concept_info | STRING | JSON string containing the selected RxCUI, requested info_type, and the retrieved data payload. | { "rxcui": "161", "info_type": "properties", "data": { "propConceptGroup": { "propConcept": [ ... ] } } } |
| rxcui | STRING | The selected RxCUI from the input list that was used to fetch information. | 161 |
| status | STRING | Operation status message indicating success or describing an error. | Successfully retrieved properties for RXCUI 161 |
Important Notes¶
- Input format: rxcuis must be valid JSON representing an array of strings (e.g., ["161"]). Invalid JSON or non-array values will cause errors.
- Indexing: selected_rxcui is zero-based. If the index is outside the array bounds, the node returns an out-of-range error.
- Empty values: The chosen RxCUI string must be non-empty; otherwise the node returns an error.
- info_type choice: The node supports only: name, ndcs, properties, all_related. Any other value returns an error.
- External API dependency: Data is obtained from an RxNorm API via a utility layer; network or service issues may produce API error messages.
- Payload size: all_related can return large responses; consider performance and downstream node limits.
Troubleshooting¶
- Invalid JSON in rxcuis: Ensure the input is a properly formatted JSON array of strings (e.g., "[\"161\"]").
- Selected RXCUI index out of range: Verify selected_rxcui is within 0 and len(rxcuis)-1.
- Empty RXCUI: Confirm the rxcuis array contains non-empty string values.
- API Error responses: The status may include messages like "API Error: ...". Retry later, validate the RxCUI, or check network connectivity.
- Unexpected output shape: For all_related, the structure can be deeply nested; pass the output through a JSON inspector or parser before further processing.