> 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/information-models-and-terminology-bindings/drug-concept-classes-across-workflows.md).
# 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.
| Concept Class | Role | Example |
| ------------- | ------------------- | ---------------------------------- |
| CD | Generic prescribing | Amoxicillin 500 mg capsule |
| RCD | Brand prescribing | Brand X amoxicillin 500 mg capsule |
| CDP / RPCD | Package prescribing | Brand X amoxicillin box of 24 |
## Dispensing
Dispensing translates the prescribed drug into a specific product (RCD) or packaged product (RPCD), reflecting what is actually supplied.
| Concept Class | Role | Example |
| ------------- | ----------------- | ---------------------------------- |
| CD | Prescribed drug | Amoxicillin 500 mg capsule |
| RCD | Dispensed product | Brand X amoxicillin 500 mg capsule |
| RPCD | Dispensed package | Brand X amoxicillin box of 24 |
## Medication Administration
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.
| Concept Class | Role | Example |
| ------------- | -------------------- | --------------------------- |
| RCD | Product administered | Morphine injection BrandX |
| CD | Clinical equivalence | Morphine injection 10 mg/mL |
| Route | Administration route | Intravenous route |
## Inventory and Logistics
Inventory systems operate primarily at the package level (RPCD/CDP), while CD supports aggregation and reporting across products.
| Concept Class | Role | Example |
| ------------- | --------------- | ----------------------------- |
| RPCD | Stock package | Brand X amoxicillin box of 24 |
| CDP | Generic package | Amoxicillin box of 24 |
| CD | Aggregation | Amoxicillin 500 mg capsule |
## Procurement
Procurement processes typically specify requirements using CDs, allowing suppliers to respond with RCDs and associated packaged products (RPCDs).
| Concept Class | Role | Example |
| ------------- | ------------------ | --------------------------- |
| CD | Tender requirement | Amoxicillin 500 mg capsule |
| RCD | Supplier product | Brand X amoxicillin capsule |
| RPCD | Packaged offer | Brand X amoxicillin box |
## Reimbursement
Reimbursement rules may apply at different levels of abstraction, from ingredient (MP) to form (MPF) to specific strength (CD).
| Concept | Role | Example |
| ------- | ------------------- | ----------------------- |
| MP | Ingredient coverage | Metformin |
| MPF | Form coverage | Metformin tablet |
| CD | Strength coverage | Metformin 500 mg tablet |
#### Clinical Decision Support
Clinical decision support operates across multiple levels, depending on the rule:
* MP for interactions
* MPF for form-specific logic
* CD for dose validation
| Concept Class | Role | Example |
| ------------- | ------------------- | ------------------ |
| MP | Interaction rules | Warfarin |
| MPF | Form-specific rules | Insulin injectable |
| CD | Dose rules | Paracetamol 500 mg |
## Adverse Drug Reaction Reporting
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.
| Concept Class | Role | Example |
| ------------- | ---------------- | ------------------- |
| RCD | Specific product | Brand X amoxicillin |
| CD | Generic drug | Amoxicillin 500 mg |
| MP | Ingredient | Amoxicillin |
## Analytics and Reporting
Analytics typically uses MP and MPF for aggregation, with CD enabling more detailed analysis when needed.
| Concept Class | Role | Example |
| ------------- | ----------------- | ------------------ |
| MP | Aggregation | Insulin |
| MPF | Form analysis | Injectable insulin |
| CD | Detailed analysis | Insulin glargine |
Provide Feedback
---
# 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/information-models-and-terminology-bindings/drug-concept-classes-across-workflows.md?ask=&goal=
```
`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.