> For the complete documentation index, see [llms.txt](https://edehr.gitbook.io/edehr-compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edehr.gitbook.io/edehr-compass/user-guides/student-guides/patient-chart-workflow/medication-verification.md).

# Medication Verification

In clinical practice, a nurse verifies each medication order every 24 hours. In EdEHR, the course designer pre-populates these verifications as part of the case study. A medication order can have multiple 24-hour verification records, each representing one verification cycle. When a student opens the MAR, the system displays the verification record that is current for the student's simulation time.

***

## How Verification Works

Each record captures:

* The medication order reference as recorded by the verifying provider (faculty building the case study or nurse student in more advanced courses)
* A **Verification status** (see below)
* **Notes** — free text
* **Actions taken** — free text

### Verification Status Options

| Icon                                                                                                                                                                                                                             | Status                | Description                                                                                                          |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------- |
| ![verified](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-565584e8e4df996ccbc379ebd45fd37545f5229b%2Fmed-verify-verified.png?alt=media)       | **Verified**          | The medication was confirmed correct.                                                                                |
| ![discrepancy](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-d7568277db8e9882ee69a4de30628632c043f61c%2Fmed-verify-discrepency.png?alt=media) | **Discrepancy found** | A problem was identified during verification. The MAR displays a red "Verification status: Discrepancy found" alert. |
| ![unable](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-6de73791243fef24ada9167e7df7f67bd9e064b3%2Fmed-verify-unable.png?alt=media)           | **Unable to verify**  | Verification could not be completed.                                                                                 |
| ![expired](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-7d697b8905dfafd89911656f23d3919dbce93582%2Fmed-verify-expired.png?alt=media)         | **Expired**           | The verification record is older than 24 hours of simulation time and is no longer valid.                            |

![Medication administration records grid showing the hourglass icon on two expired medication orders and a green checkmark on a verified order](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-8d03cd7fc537d9541e4ba5032ba96b974ba410d6%2Fmed-verify-mar-status.png?alt=media)

### Verification Expiry

A 24-hour verification record is valid for 24 hours of **simulation time**. If the student's current simulation time is more than 24 hours after the verification was recorded, the status indicator changes to the hourglass icon shown above.

![Medication administration record detail showing a "Medication verification: Verified. Expires Day 8 (2026-09-11) 0830" banner above the medication order](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-30c481e700cf7571a06d8111b2d46b901b1610c6%2Fmed-verify-mar-banner.png?alt=media)

***

## Adding a Verification Record to a Medication Order

![Medication orders table in Course Designer Mode, with a Verify button on each row and status icons showing an hourglass for expired verifications and a green checkmark for a verified order](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-2f6db38c68bce3d26b8c836e5ad314e1abb07b64%2Fmed-verify-order-list.png?alt=media)

1. Open the case study in Course Designer Mode and navigate to the **Medication orders** section of the patient chart.
2. Locate the medication order you want to add a verification to.
3. Click the **Verify** button on that medication order row.

![Medication Verification dialog](https://1198840737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcHC5valsK2qsuRUKHH2u%2Fuploads%2Fgit-blob-b19355a08fa869e5094449b91b3c75b528edb0d7%2Fmed-verify-dialog.png?alt=media)

4. The **Medication Verification** dialog opens, showing the full medication order details at the top for reference.
5. In the **Med name** field, enter the medication name as the verifying provider recorded it.
6. Select a **Verification status** from the dropdown: Verified, Discrepancy found, or Unable to verify.
7. Optionally add **Notes** and **Actions taken**.
8. Click **Save**.

The medication order row updates to reflect the verification status icon as described in the table above.

***

{% hint style="info" %}
The verification status shown to students reflects simulation time, not real time. Plan your case study dates and times accordingly so that verifications are still valid when students are expected to interact with them.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://edehr.gitbook.io/edehr-compass/user-guides/student-guides/patient-chart-workflow/medication-verification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.