RxNorm · SCDF · 1856683

1856683

SCDF · Clinical drug form

common wasp venom protein / eastern yellow jacket venom protein / German wasp venom protein / southern yellow jacket venom protein / western yellow jacket venom protein Injectable Solution

Concept
RxCUI1856683
Namecommon wasp venom protein / eastern yellow jacket venom protein / German wasp venom protein / southern yellow jacket venom protein / western yellow jacket venom protein Injectable Solution
Term typeSCDF · Clinical drug form
LanguageENG
Cross-maps
UMLS CUIC4293587
Synonyms

No additional synonyms recorded.

# same page, as API
GET autoicdapi.com/api/v1/reference/rxnorm/1856683
GET autoicdapi.com/api/v1/translate?code=1856683&from=rxnorm&to=umls

Common questions

What is the RxNorm code for common wasp venom protein / eastern yellow jacket venom protein / German wasp venom protein / southern yellow jacket venom protein / western yellow jacket venom protein Injectable Solution?

common wasp venom protein / eastern yellow jacket venom protein / German wasp venom protein / southern yellow jacket venom protein / western yellow jacket venom protein Injectable Solution is coded as 1856683 in RxNorm.

What is RxNorm code 1856683?

1856683 is the RxNorm identifier for common wasp venom protein / eastern yellow jacket venom protein / German wasp venom protein / southern yellow jacket venom protein / western yellow jacket venom protein Injectable Solution. It is included in the current monthly NLM RxNorm release.

What term type is RxCUI 1856683?

1856683 is a SCDF (Clinical drug form) in RxNorm.

What is the UMLS mapping for 1856683?

1856683 maps to UMLS C4293587.

RxNorm, plainly answered

What is RxNorm?
RxNorm is the NLM's normalized naming system for clinical drugs and dose forms. It collapses brand variants, packaging differences, and source-vocabulary noise into a single, stable identifier (RxCUI) per concept, with explicit links to ingredients, brands, and clinical drug forms.
What are RxCUIs?
An RxCUI is the persistent ID for a single RxNorm concept. The same RxCUI keeps pointing at the same drug concept release after release, even when names or sources change. That stability is what makes RxNorm useful for medication reconciliation and analytics.
How does RxNorm relate to NDC codes?
NDC codes describe a specific package SKU at a specific manufacturer. RxNorm describes the clinically relevant drug. One RxCUI can map to dozens of NDCs (different manufacturers, different package sizes), and we list those NDC mappings on each concept page.
How does RxNorm cross-map to other standards?
RxNorm concepts carry direct links to UMLS CUIs and SNOMED CT product codes when available. Through the UMLS bridge they can also reach ICD-10 codes (for instance, for indication-based coding) and LOINC observations. Our API exposes all of this on the cross_references field.
Is the API free to use?
Browsing concepts is free. Programmatic access at /api/v1/reference/rxnorm/* requires an API key. RxNorm itself is in the public domain, so there is no upstream license fee, but our bandwidth and uptime are not.
How fresh is the RxNorm data?
RxNorm releases monthly. We rebuild within a few business days of each release, and the concept-id history is preserved so previous lookups continue to resolve.