Skip to content

RxNorm Concept Info

Retrieves detailed information for a specific RxNorm concept (RxCUI). You provide a JSON array of RxCUIs and select which one to inspect by index. Depending on the chosen info_type, it returns the concept's name, NDCs, core properties, or all related information as formatted JSON.
Preview

Usage

Use this node after obtaining one or more RxCUIs (for example, from a drug search or mapping by NDC). Pass the RxCUIs as a JSON array string, choose which RxCUI to inspect with selected_rxcui (0-based index), and select the type of information to retrieve. The node outputs the requested concept data in JSON, the selected RxCUI, and a status message for flow control and logging.

Inputs

FieldRequiredTypeDescriptionExample
rxcuisTrueSTRINGA JSON array string of RxCUIs to choose from. The node will parse this and select one by index.["161", "16120", "198440"]
selected_rxcuiTrueINT0-based index into the rxcuis array indicating which RxCUI to inspect.0
info_typeTrue["name", "ndcs", "properties", "all_related"]Specifies which information to fetch for the selected RxCUI: name (RxNorm name), ndcs (linked National Drug Codes), properties (core concept properties), or all_related (comprehensive related info).properties

Outputs

FieldTypeDescriptionExample
concept_infoSTRINGFormatted JSON string containing the requested information for the selected RxCUI. Structure includes rxcui, info_type, and data.{ "rxcui": "161", "info_type": "properties", "data": { ... } }
rxcuiSTRINGThe RxCUI that was selected and queried.161
statusSTRINGHuman-readable status message indicating success or error details.Successfully retrieved properties for RXCUI 161

Important Notes

  • Input format: rxcuis must be a valid JSON array string (e.g., "[\"161\"]"). Invalid JSON will cause an error.
  • Indexing: selected_rxcui is 0-based. If the index is out of range, the node returns an error.
  • Empty values: If the chosen RxCUI is an empty string, the node returns an error.
  • Info type options: Only the listed values are accepted: name, ndcs, properties, all_related.
  • Error propagation: If the upstream service returns an error, the node returns a JSON error payload in concept_info and an error message in status.
  • Output structure: On success, concept_info wraps the raw data with rxcui and info_type for consistent downstream parsing.

Troubleshooting

  • Selected RXCUI index out of range: Ensure selected_rxcui is less than the length of the rxcuis array.
  • Invalid rxcuis JSON: Provide a properly formatted JSON array string. Example: "[\"161\", \"198440\"]".
  • Empty RXCUI string: Verify that the selected element in the rxcuis array is a non-empty string.
  • Unknown info_type: Use only one of the supported values: name, ndcs, properties, all_related.
  • API Error in status: Inspect concept_info for the error payload and retry later or adjust the input. Network or service issues may cause transient failures.