> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale/sale-settings-3/do-not-allow-bill-saving-without-patient-and-doctor-details-for-items-in-marked-groups-at-level.md).

# Do not allow Bill saving without Patient and Doctor Details for items in Marked Groups at Level

**YouTube:** [How to Enforce Doctor and Patient Selection for Schedule H Prescription Items in Sale Bill?](https://www.youtube.com/watch?v=QsPNUEWXLfU)

## How to Enforce Doctor and Patient Selection for Schedule H Prescription Items in Sale Bill?

This tutorial demonstrates how to configure Logic ERP to **restrict bill saving** if **Patient** and **Doctor details** are missing for items that belong to special or prescription-required categories.

***

### **Enable the Setting in Logic Admin**

* Open the **Logic** installation folder.
* Run **Logic Admin**.
* Navigate to **Global Settings**.
* Go to the **Sales Settings Three** tab.
* Find the option: **“Do not allow bill saving without Patient and Doctor Details for items in marked groups at level:”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FR5yP7utUrWy0eUfhKDhc%2FAdmin%20Setup.png?alt=media&amp;token=59c6fbcf-fb6b-4f27-ac5e-75e18efd0a7b" alt=""><figcaption></figcaption></figure>

* From the dropdown menu, **select the relevant item group level**.
* Enable the checkbox and click **Save**.
* Restart the Logic ERP software to apply the new configuration.

***

### **Implement the Functionality in Sales Voucher**

* Open Logic ERP and begin creating a **Sales Voucher**.
* Skip entering **Patient** and **Doctor details and** proceed to add item(s).
* When you try to **save the voucher**, the system will display:
  * **“Patient name cannot be left blank”**
  * **“Doctor name cannot be left blank”**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F4T0mZdGlZu0xXS74Lra4%2Fprompt%20for%20Error.png?alt=media&amp;token=79a8129c-a6e6-4855-ab64-3927e0a57feb" alt=""><figcaption></figcaption></figure>

* This validation is triggered **only for items** that belong to marked item groups requiring prescriptions.

***

### **Mark Item Groups for Validation**

* Navigate to **Setup/Setup Items** then click on **Setup Item Group**.
* Create a new group or **edit an existing one** that includes regulated or prescription items.
* In the item group window, locate the column for **Patient & Doctor validation**.
* Mark **“Yes”** to enforce this validation for all items under this group.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FWdYEsQQPrU5Mn6zJUFQH%2Fgroup.png?alt=media&amp;token=7d50cb0e-c7f7-4d95-8fa3-3f19546e4082" alt=""><figcaption></figcaption></figure>

* Save the changes.

***

### **Summary**

Enabling this feature ensures that **medical or prescription-based items** are not billed without the necessary **Patient and Doctor information**. It helps in maintaining regulatory compliance and preventing unauthorized sales.


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale/sale-settings-3/do-not-allow-bill-saving-without-patient-and-doctor-details-for-items-in-marked-groups-at-level.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.
