# View Package Consumption History

The **Package Consumption History** allows users to access detailed records of package consumption, including item-wise consumption history and associated details. This ensures accurate tracking of package usage.

### Steps to View Package Consumption History

* Open the **Package Consumption** screen by navigating to **Home > Packages > Package Consumption**.
* Use the **search field** to locate the patient by **Patient PIN**, **Name**, **EID**, or **Mobile Number**.
* From the **Select Package** drop-down list, choose the relevant package to view its details.
* Click the **Show Consumption History** icon.

  <figure><img src="/files/2jjPydmOhIbpOiWNqM7p" alt=""><figcaption></figcaption></figure>
* The Package Detail pop-up displays the package code, name, and validity range.

  <figure><img src="/files/BhOSOqniJhSFKwmC5LmX" alt=""><figcaption></figcaption></figure>
* The table within the pop-up provides detailed package consumption history, item-wise. Each row represents an item associated with the package.
* Click the ![](/files/TXQ9j0pnGJ1OMxY1PkKb) icon next to an item to expand its consumption history, displaying the consumed date, consumed quantity, creator, and remarks.\
  \&#xNAN;***Note:** You can update the **Consumed Date** and **Consumed Qty** fields only if no patient visit exists on that date for the selected package.*

  <figure><img src="/files/olbmO0LdcL83jBWYnqRH" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Depending on the configuration, the package price details will either be shown or hidden.
{% endhint %}

***


---

# Agent Instructions: 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:

```
GET https://unitecare.gitbook.io/uniteemr/application-modules/packages/package-consumption/view-package-consumption-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.