RxTerms Information¶
Retrieves RxTerms details for one or more RxNorm concepts (RXCUIs) using the RxNorm API. Accepts a single RXCUI or a JSON array of RXCUIs and returns JSON-encoded summaries including the full name, strength, route, and dose forms for each concept. Designed to provide quick, structured drug terminology data keyed by RXCUI.
Usage¶
Use this node when you need standardized drug terminology data from RxNorm RxTerms for downstream processing, display, or validation. Provide a single RXCUI for one concept, or pass a JSON array of RXCUIs to batch fetch details and receive consolidated JSON outputs keyed by each RXCUI.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| rxcui | True | STRING | RxNorm Concept Unique Identifier. Can be a single RXCUI (e.g., "313") or a JSON array string of RXCUIs (e.g., "[\"313\", \"123\"]"). | 313 |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| rxterms_info | STRING | JSON string mapping each RXCUI to the full RxTerms API response object for that concept. | { "313": { "rxtermsProperties": { "fullName": "Acetaminophen 325 MG Oral Tablet", "strength": "325 mg", "route": "Oral", "rxnormDoseForm": "Oral Tablet" } } } |
| full_name | STRING | JSON string mapping each RXCUI to its RxTerms fullName. | { "313": "Acetaminophen 325 MG Oral Tablet" } |
| strength | STRING | JSON string mapping each RXCUI to its strength value from RxTerms. | { "313": "325 mg" } |
| route | STRING | JSON string mapping each RXCUI to its route of administration from RxTerms. | { "313": "Oral" } |
| forms | STRING | JSON string mapping each RXCUI to its dose form (rxnormDoseForm) from RxTerms. | { "313": "Oral Tablet" } |
Important Notes¶
- Input format: The input accepts either a single RXCUI string or a JSON array string (e.g., "[\"313\", \"123\"]").
- Batch behavior: When a JSON array is provided, all outputs are JSON objects keyed by each RXCUI.
- Empty or invalid RXCUI: Blank or invalid RXCUIs yield empty strings for the specific fields in the per-RXCUI mappings.
- Error handling: On unexpected errors, all outputs default to empty JSON objects ("{}").
- External dependency: Requires network access to the RxNorm API via the underlying service; connectivity or service issues can affect results.
- Output format: All outputs are JSON-encoded strings; parse them before programmatic use.
Troubleshooting¶
- All outputs are {}: This indicates an exception occurred during retrieval. Check network connectivity, RXCUI validity, and service availability; try a single known-good RXCUI.
- Fields are empty strings for some RXCUIs: The specific RXCUI may be invalid or returned an error. Verify the RXCUI and retry; ensure there is no leading/trailing whitespace.
- 'rxcui' array not recognized: Ensure you pass a valid JSON array string with properly escaped quotes (e.g., "[\"313\", \"123\"]").
- Unexpected parsing issues: Confirm that the input is either a plain RXCUI string or a valid JSON array string; avoid passing Python-style lists or malformed JSON.
- Missing properties in output: Some concepts may not have all RxTerms properties populated. Validate data presence before downstream usage.