Drug Proprietary Identifiers
RxPedia Drug Proprietary Identifiers connect medication concepts with international and local medication terminology. Cross-references include ATC, NDC, RxNorm, SNOMED CT, and relevant national medication identifiers, according to the mapping scope provided for the implementation.
This creates a way to relate identifiers used by different systems to RxPedia medication knowledge. It can support medication identification and the preparation of data for a screening or information-retrieval workflow.
The source systems represent medications at different levels. An ingredient, a clinical drug, a branded product, and a package identifier are not automatically equivalent. Review the intended concept level, formulation, strength, and other relevant attributes before using a cross-reference in a clinical workflow.
NLM is the U.S. National Library of Medicine, not a standalone medication coding system. When specifying NLM-related terminology requirements, identify the actual vocabulary or resource, such as RxNorm, and the identifiers needed by the integration.
Therapeutic Classification System
RxPedia's Therapeutic Classification System provides multiple ways to categorize medications for formulary organization, navigation, and drug selection workflows. A medication can belong to multiple therapeutic classes, with links to drug concepts at different levels of the hierarchy.
This allows a system to present a broader category and then connect it to more specific classes or medication concepts. Multiple class membership helps preserve different clinically relevant perspectives instead of forcing every medication into a single category.
Classification can help organize a formulary; it does not establish a local formulary decision, reimbursement rule, or recommendation to prescribe a particular medication. Likewise, shared class membership does not by itself establish that medications are interchangeable or that their combined use is inappropriate.
Medical Proprietary Identifiers
Begin with the medication or medical code supplied by the host system. Identify its vocabulary and version, relate it to the appropriate RxPedia concept, and confirm that the relationship is suitable for the intended use.
The resulting concept can then support an available knowledge or screening service. Present the returned clinical information in the host workflow with the context and limitations needed for professional interpretation.
Not every source entry will necessarily have a usable match. Agree how your system handles missing identifiers, ambiguous relationships, unsupported concepts, and mappings that need review. An unresolved mapping must not silently become a completed clinical check.