RxNorm Approximate Match¶
Finds approximate (fuzzy) RxNorm matches for a free-text term. It queries the RxNorm service and returns a JSON string containing the search term and the service’s approximate match results, along with a status message.
Usage¶
Use this node when you have an imprecise or free-text medication term (e.g., misspellings or partial names) and you need likely RxNorm concept matches. Typical workflow: provide a drug term, run the node to get approximate matches as JSON, then downstream nodes or scripts can parse that JSON to select specific RxCUIs or concepts.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| term | True | STRING | The free-text drug term to search for approximate RxNorm matches. | acetaminophen |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| approximate_matches | STRING | A pretty-printed JSON string with the search term and the RxNorm approximate match results. | {"search_term": "acetaminophen", "results": {"approximateGroup": {"candidate": [{"rxcui": "161", "score": "100"}]}}} |
| status | STRING | Human-readable status message indicating success or describing any error. | Successfully retrieved approximate matches for 'acetaminophen' |
Important Notes¶
- The input term must be non-empty; an empty term returns "{}" and an error status.
- The 'approximate_matches' output is a JSON string; parse it before using individual fields (e.g., candidates, RxCUIs).
- If the underlying RxNorm service returns an error, the node passes it through in the JSON and status as an API error.
- Results can include multiple candidates with scores; the node does not filter or select a single best match.
- This node depends on external RxNorm API availability and may be impacted by network issues or service rate limits.
- Category: SALT/RxNorm/Utilities
Troubleshooting¶
- Input is empty: Ensure 'term' contains a non-blank string.
- API Error in status: Retry later and verify network access; if persistent, validate the term or check RxNorm service availability.
- Output not parseable: Confirm you are parsing the 'approximate_matches' field as JSON text.
- No matches returned: Try alternative spellings or broader terms to improve approximate matching.