> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/implementation-guides/drug-model-implementation-guide/use-cases/snomed-ct-drug-model-use-cases.md).

# SNOMED CT Drug Model Use Cases

### Introduction

The SNOMED CT Pharmaceutical / Biologic Product hierarchy provides a structured model for representing medicinal products at multiple levels of abstraction. This hierarchy includes concepts such as Medicinal Product (MP), Medicinal Product Form (MPF), and Clinical Drug (CD), which progressively add detail about ingredients, dose form, and strength.

For example:

* A Medicinal Product (MP) represents a medicinal product defined only by its active ingredient(s), without specifying strength or dose form.
* A Clinical Drug (CD) represents a medicinal product defined by ingredient, strength, and manufactured dose form, making it suitable for use in clinical workflows.

The International Release focuses on representing medicinal products in a way that is globally consistent, while national extensions may add concepts representing actual authorized products and packaging available in specific jurisdictions, including branded medicines and product packages.

Together, the International Drug Model and National Drug Extensions support a wide range of healthcare use cases including prescribing, dispensing, logistics, reimbursement, pharmacovigilance, and clinical decision support.

## Administrative Use Cases

Administrative use cases support operational and financial aspects of healthcare systems such as procurement, logistics, and reporting.

### UC.1 Procurement and Tendering

Healthcare organizations and national procurement agencies often purchase medicines through competitive tendering processes. In these processes, the purchasing authority defines the medication required using a generic specification, allowing suppliers to compete with their own authorized products.

The SNOMED CT drug model supports this process by separating generic drug definitions from real products available on the market. Procurement specifications can reference Clinical Drug (CD) concepts, while suppliers offer their products using Real Clinical Drug (RCD) and Real packaged Clinical Drug (RPCD) concepts defined in national extensions.

This approach ensures vendor-neutral procurement while maintaining precise definitions of the medicines being purchased.

#### Concept usage

<table><thead><tr><th width="107.0390625">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>CD</td><td>Defines the medication required in the tender</td><td><em>Product containing precisely amoxicillin 500 mg oral capsule (clinical drug)</em></td></tr><tr><td>RCD</td><td>Represents the specific product offered by suppliers</td><td><em>Brand X amoxicillin 500 mg capsule manufactured by Company Y</em></td></tr><tr><td>RPCD</td><td>Represents the specific packaged product offered by suppliers</td><td><em>Brand X amoxicillin 500 mg capsule, pack of 30 capsules, manufactured by Company Y</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A hospital publishes a tender for amoxicillin 500 mg capsules (CD). Multiple suppliers submit offers for their specific authorized products (RCDs).
{% endhint %}

### UC.2 Stock Management and Pharmacy Logistics

Hospital pharmacies and distribution systems manage inventories of medications across warehouses, pharmacies, and clinical units. Stock management systems track package quantities, expiration dates, and product movement.

The SNOMED CT drug model supports these workflows by representing product packages using concepts such as Clinical Drug Package (CDP) and Real Clinical Drug Package (RPCD).

This allows inventory systems to track real packages while maintaining a link to the underlying clinical drug concept, and make this information available during the prescription process when necessary.

#### Concept usage

<table><thead><tr><th width="141.859375">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>RPCD</td><td>Actual product package stored in inventory</td><td><em>BrandX amoxicillin 500 mg capsule box of 24 capsules</em></td></tr><tr><td>CDP</td><td>Generic package representation</td><td><em>Amoxicillin 500 mg capsule box of 24 (generic package)</em></td></tr><tr><td>CD</td><td>Aggregated reporting across packages</td><td><em>Product containing precisely amoxicillin 500 mg capsule</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A pharmacy stores boxes of 24 capsules of BrandX amoxicillin (RPCD). Inventory reporting aggregates all packages under the amoxicillin 500 mg capsule clinical drug concept.
{% endhint %}

### UC.3 Financial Coverage and Reimbursement

Health insurance systems and national payers define reimbursement policies for medications based on ingredients, formulations, or specific products.

The SNOMED CT drug model enables reimbursement rules to be defined at different levels of abstraction. For example, coverage policies may apply to all products containing a given ingredient or may apply only to specific strengths or formulations.

#### Concept usage

<table><thead><tr><th width="110.7890625">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>MP</td><td>Ingredient-level reimbursement rules</td><td><em>Product containing metformin (medicinal product)</em></td></tr><tr><td>MPF</td><td>Ingredient + dose form reimbursement</td><td><em>Product containing metformin in oral tablet dose form</em></td></tr><tr><td>CD</td><td>Strength-specific reimbursement</td><td><em>Product containing precisely metformin 500 mg oral tablet</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

An insurer reimburses all oral metformin tablets (MPF) but applies different reimbursement levels depending on tablet strength (CD).
{% endhint %}

### UC. 4 Business Intelligence and Drug Utilization Reporting

Healthcare organizations and public health authorities routinely analyze medication usage data to monitor prescribing patterns, drug costs, and treatment trends, and to support business intelligence activities such as forecasting demand, planning procurement, and optimizing medication supply.

The hierarchical structure of the SNOMED CT drug model enables aggregation of medication data at different levels of granularity. Data recorded at the clinical drug level can be automatically aggregated at higher levels, such as ingredient or drug class.

#### Concept usage

<table><thead><tr><th width="125.90625">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>MP</td><td>Ingredient-level reporting</td><td><em>Product containing insulin (medicinal product)</em></td></tr><tr><td>MPF</td><td>Ingredient + dose form analysis</td><td><em>Product containing insulin in injectable solution</em></td></tr><tr><td>CD</td><td>Detailed drug usage statistics</td><td><em>Insulin glargine 100 units/mL solution for injection</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A national health authority analyzes total insulin usage by aggregating prescriptions recorded at the clinical drug level.
{% endhint %}

## Clinical Use Cases

Clinical use cases focus on the use of medications in patient care workflows.

### UC.5 Electronic Prescribing

Electronic prescribing systems allow clinicians to select medications and send prescriptions electronically to pharmacies. These systems must represent medications with sufficient detail to ensure accurate dispensing.

SNOMED CT Clinical Drug (CD) concepts provide the appropriate level of detail for prescribing because they specify ingredient, strength, and dose form. In some cases, clinicians may prescribe a specific brand or package using Real Clinical Drug (RCD) or Real Packaged Clinical Drug (RPCD) concepts.

#### Concept usage

<table><thead><tr><th width="145.3828125">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>CD</td><td>Generic prescribing</td><td><em>Product containing precisely amoxicillin 500 mg oral capsule</em></td></tr><tr><td>RCD</td><td>Brand-specific prescribing</td><td><em>BrandX amoxicillin 500 mg capsule</em></td></tr><tr><td>CDP / RPCD</td><td>Prescribing by package</td><td><em>BrandX amoxicillin 500 mg capsule box of 24</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A physician prescribes amoxicillin 500 mg capsules using a clinical drug concept. The pharmacy system receives the prescription and selects the appropriate product.
{% endhint %}

### UC.6 Pharmacy Dispensing

When a pharmacy receives a prescription, the pharmacist selects a product that fulfills the prescription. In many healthcare systems, pharmacists are allowed to substitute equivalent generic medicines.

The SNOMED CT drug model supports this workflow by linking Clinical Drug concepts with Real Clinical Drug concepts, enabling pharmacy systems to match prescriptions with available products.

#### Concept usage

<table><thead><tr><th width="116.12890625">Concept</th><th width="228.7578125">Role</th><th>Example</th></tr></thead><tbody><tr><td>CD</td><td>Prescribed drug</td><td><em>Product containing precisely amoxicillin 500 mg capsule</em></td></tr><tr><td>RCD</td><td>Dispensed product</td><td><em>BrandX amoxicillin 500 mg capsule</em></td></tr><tr><td>RPCD</td><td>Dispensed package</td><td><em>BrandX amoxicillin 500 mg capsule box of 24 capsules</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A prescription for amoxicillin 500 mg capsules is filled by dispensing a generic product from manufacturer Y.
{% endhint %}

### UC.7 Medication Administration

In hospitals and other care settings, nurses administer medications to patients according to physician orders. Medication administration systems must record the exact product administered and verify that it matches the prescribed medication. Clinical decision support systems can support the administration step by checking contraindications, potential drug interactions, and dose appropriateness before the medication is given.

Closed-loop medication administration systems often use barcode scanning to identify the medication product before administration.

#### Concept usage

<table><thead><tr><th width="200.4921875">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>RCD</td><td>Product administered</td><td><em>Morphine sulfate 10 mg/mL solution for injection – BrandX</em></td></tr><tr><td>CD</td><td>Clinical equivalence</td><td><em>Product containing precisely morphine sulfate 10 mg/mL solution for injection</em></td></tr><tr><td>Route concepts</td><td>Administration route</td><td><em>Intravenous route (qualifier value)</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A nurse administers morphine 2 mg IV and records the administration using the details of the branded product. The decision support system validates the safety against recorded patient data.
{% endhint %}

### UC.8 Adverse Drug Reaction Reporting

Pharmacovigilance systems collect reports of adverse reactions associated with medications. These systems must accurately identify the suspected drug to detect safety signals. If adverse reaction reports are generated directly from medication administration data recorded in the clinical record, the exact product administered can be captured without information loss, ensuring that the same product is reported to pharmacovigilance systems.

The SNOMED CT drug model allows adverse reactions to be recorded at different levels of specificity depending on available information.

#### Concept usage

<table><thead><tr><th width="114.4140625">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>RCD</td><td>Specific product causing reaction</td><td><em>BrandX amoxicillin 500 mg capsule</em></td></tr><tr><td>CD</td><td>Generic drug reaction reporting</td><td><em>Product containing precisely amoxicillin 500 mg capsule</em></td></tr><tr><td>MP</td><td>Ingredient-level safety monitoring</td><td><em>Product containing amoxicillin (medicinal product)</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A patient develops a rash after taking amoxicillin. The adverse reaction report is created with the accurate and appropriate information.
{% endhint %}

### UC.9 Clinical Decision Support

Clinical decision support systems analyze medication orders and patient information to provide alerts and guidance to clinicians.

Typical decision support functions include drug–drug interaction checking, allergy alerts, and dose range validation.

#### Concept usage

<table><thead><tr><th width="121.28515625">Concept</th><th width="250.48828125">Role</th><th>Example</th></tr></thead><tbody><tr><td>MP</td><td>Ingredient-based CDS rules</td><td>Interaction rule for <em>warfarin (medicinal product)</em> with NSAIDs</td></tr><tr><td>MPF</td><td>Form-specific rules</td><td>Alert for <em>insulin injectable products</em></td></tr><tr><td>CD</td><td>Dose validation</td><td>Maximum dose rule for <em>paracetamol 500 mg tablet</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A CDS rule alerts the physician if a patient with a penicillin allergy is prescribed amoxicillin.
{% endhint %}

## Knowledge and Secondary Use Cases

The SNOMED CT drug model also supports knowledge management, research, and secondary uses of medication data.

### UC.10 Clinical Drug Knowledge Bases

Healthcare organizations and knowledge provider companies maintain drug knowledge databases containing information about drug interactions, contraindications, dosing guidance, and therapeutic indications.

The SNOMED CT drug model allows knowledge to be linked to standardized drug concepts, enabling consistent application and simple integration across clinical systems.

#### Concept usage

<table><thead><tr><th width="121.046875">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>MP</td><td>Ingredient-level knowledge</td><td>Interaction between <em>warfarin</em> and <em>ibuprofen</em></td></tr><tr><td>MPF</td><td>Form-specific rules</td><td>Dosing recommendations for <em>inhaled salbutamol</em></td></tr><tr><td>CD</td><td>Strength-specific rules</td><td>Maximum daily dose for <em>paracetamol 500 mg tablet</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A drug knowledge base defines an interaction between warfarin and NSAIDs, which is triggered during prescribing.
{% endhint %}

### UC.11 Medication History and Patient Medication Lists

Electronic health records maintain medication lists representing drugs that a patient is currently taking or has taken previously. These lists support medication reconciliation and continuity of care.

Medication records may represent drugs at different levels depending on available information.

#### Concept usage

<table><thead><tr><th width="151.375">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>CD</td><td>Generic medication record</td><td><em>Metformin 500 mg oral tablet</em></td></tr><tr><td>RCD</td><td>Exact product taken</td><td><em>BrandX metformin 500 mg tablet</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

A patient’s medication list includes metformin 500 mg tablets as a generic and Tylenol 500mg tablets as a branded product.
{% endhint %}

### UC.12 Research and Pharmacoepidemiology

Researchers and public health authorities analyze medication data to study treatment outcomes, safety, and prescribing trends. Current medication use is also commonly used as a criterion for patient selection and eligibility in clinical studies.

The hierarchical structure of SNOMED CT drug concepts allows researchers to aggregate medication data at different levels.

#### Concept usage

<table><thead><tr><th width="136.84765625">Concept</th><th>Role</th><th>Example</th></tr></thead><tbody><tr><td>MP</td><td>Population-level studies</td><td>Study of all <em>statin medicinal products</em></td></tr><tr><td>MPF</td><td>Therapeutic category analysis</td><td>Analysis of <em>oral statin tablets</em></td></tr><tr><td>CD</td><td>Specific dosage analysis</td><td>Study of <em>atorvastatin 20 mg tablet</em></td></tr></tbody></table>

{% hint style="info" icon="hexagon" %}

#### Example scenario:

Researchers study cardiovascular outcomes in patients taking atorvastatin 20 mg tablets.
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Drug+Extension+Guide&#x26;entry.670899847=SNOMED%20CT%20Drug%20Model%20Use%20Cases" class="button primary">Provide Feedback</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/implementation-guides/drug-model-implementation-guide/use-cases/snomed-ct-drug-model-use-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.