Drug Concept Classes Across Workflows

Different healthcare workflows require the use of different SNOMED CT drug model concept levels, depending on whether the focus is on clinical intent, real-world products, packaging, or aggregation.

This section summarizes how SNOMED CT concepts are typically bound to data elements across common use cases, ensuring consistent and safe interpretation of medication data.

Prescribing

Prescribing is typically based on Clinical Drugs (CD) to represent the intended medication. In some cases, prescribing may specify a brand (RCD) or a package (CDP/RPCD), depending on clinical or regulatory requirements.

Dispensing translates the prescribed drug into a specific product (RCD) or packaged product (RPCD), reflecting what is actually supplied.

Administration records the actual product (RCD) given to the patient. The Clinical Drug (CD) may be used for equivalence checks or clinical reasoning. The route is captured separately, typically using SNOMED CT qualifier values.

Inventory systems operate primarily at the package level (RPCD/CDP), while CD supports aggregation and reporting across products.

Procurement processes typically specify requirements using CDs, allowing suppliers to respond with RCDs and associated packaged products (RPCDs).

Reimbursement rules may apply at different levels of abstraction, from ingredient (MP) to form (MPF) to specific strength (CD).

Clinical decision support operates across multiple levels, depending on the rule:

• MP for interactions

• MPF for form-specific logic

• CD for dose validation

Adverse event reporting may require different levels of detail, from specific product (RCD) to generic drug (CD) or ingredient (MP), depending on data availability and reporting requirements.

Analytics typically uses MP and MPF for aggregation, with CD enabling more detailed analysis when needed.