Subject: | Allow discount on Prescriptions from POS Grid |
Summary: | Hi Team, Laucala Bay Pharmacy, had requested for the ability to give discounts on prescriptions from POS. Currently, we have the option to enter discounts on the prescription screen. There are scenarios, the prescription is created and the cashier has loaded the prescription for sale. Here the customer request for a discount. - The cashier has to remove the prescription from the POS.
- Advise the Pharmacist of the discount.
- Pharmacist loads the prescription and then enter discounts.
- New Prescription label is printed and loaded in POS.
This is an additional task for the Pharmacist Improvement - Enable users to allow discounts on prescription only for authorized users.
- Discount can be of dollar value, percentage or on total.
- The prescription label will be unchanged
Email Reference Discounts to be allowed on Prescriptions only as this has become a cumbersome exercise going back and changing RX again.
Test Plan - Create Prescription 1 with Total 10.00
- Load Prescription in POS Grid
- Give a discount of $2.00
- Total should be reduced to 8.00.
- Create Prescription 2 with Total 10.00
- Load Prescription in POS Grid
- Give a discount of 2 %
- Total should be reduced to 9.80
- Create Prescription 3 with Total 10.00
- Load Prescription in POS Grid
- Give a discount on Total of $2.50
- Total should be reduced to 7.
- Create Prescription 4 with total as 20.00
- Create Prescription 5 with total as 15.00
- Load Prescription 4 and Prescription 5.
- Process discount on the above prescriptions.
- Verify the Sales Report, Discount Item Report for the above details
|
Audit Notes: | |
11 Jan 2018 | 05:24PM Comment 1 by Vineet (Link Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 11-01-2018 05:24 PM Time Taken: 2.00 |
| Development Meeting 2018 Sanjay,Vineet,Sanjeet Further investigation required to understand why prescription items are not part of the discount structure
|
|
16 Jan 2018 | 03:07PM Comment 2 by Sanjay (Link Technologies) Assigned To: Vineet (Link Business Solutions) Followup Date: 16-01-2018 03:07 PM Time Taken: 1.00 |
| Hi Vineet, the reason we do not allow Quantity, Price, and Discounts on Prescription is that the prescription item/mixture pricing is not stored in inventory. This means that quantity change calculations, which is done on the DB server will not know what the tax and cost values are. We can add a special case calculation within POS to allow prescription items to have this capability. This will mean we do not use the standard calculations for prescription items, instead, we compute this based on the loaded values. the estimated effort for this change is: D4, ST2, UAT2 Regards Sanjay |
|
18 May 2018 | 10:57AM Comment 3 by Alvis (Link Technologies) Case 8915 added to project 09.4 |
21 May 2018 | 01:07PM Comment 4 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 21-05-2018 01:07 PM Time Taken: 2.00 |
| Below s a list of concerns relating to prescription discounts on the POS form: - Discounts are enabled on the Prescription form will be lost if discounts are enabled on the POS form
- Prescription form Tax will be overridden when discount values are re-calculated
- Complexity around Prescription Admin fees:
- Admin fees have its own tax component which can be different to the medication tax code
- Do we discount admin fees when providing prescription discounts?
Since the above considerations have not been accounted for in this case, the design will need to be amended from its original simplistic form The following are design considerations: - Remove discounts on the prescription form.
- Enable Discounts POS form.
- Create a new tax function for a prescription to handle the different tax codes on medication and admin fees
|
|
22 May 2018 | 02:34PM Comment 5 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 22-05-2018 02:34 PM Time Taken: 32.00 |
| Development work for this case has been completed. The change will be available in version: 94.Beta3 1. The following changes were made(Include Database object names, Program classes and any other relevant information):| - Added ability to give discounts based on "Allow Discount" setting on inventory maintenance
- Removed "Discount" field from Prescription entry form
- We have added a separate line in the POS form when prescriptions containing different tax codes for Admin Fee and Prescription Item. See figure 1 below for an example of this.
- Prescription form now shows all amounts as TAX Inclusive
- Surcharge product code used in Prescription is the standard Surcharge code used for POS Payments as well
- Data conversion will be applied as part of the upgrade scripts
2. The issue was caused by: - Previous design did not allow discounts at POS form
3. Next Step - UAT
Figure 1 - Sample receipt with Admin Fees
|
|
24 May 2018 | 02:04PM Comment 6 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 24-05-2018 02:04 PM Time Taken: 1.00 |
| System test completed. Verified the following: - Prescription screen changes. Amounts are showing as inclusive of tax. Discount is removed. - pass
- Load prescription in POS. Admin fee is shown separately when item tax code is different to the admin fee tax code - pass
- Discount is given based on the items "Allow discount" property.
regards Alvis |
|
01 Jun 2018 | 01:54PM Comment 7 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 04-06-2018 12:00 AM Time Taken: 2.00 |
| Hi Sanjay, This case has been successfully tested. Documentation on the case has been updated. - Point of Sale -- Prescription -- Start Prescription Entry
Test Environment - Version 9400 Beta 3
- Database - LINKSOFT on QA1
- Application - LINKSOFT on QA1
- OS - Windows 7
Test Plan
|
|
05 Jun 2018 | 03:33PM Comment 8 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 05-06-2018 03:33 PM |
| Thanks Rashna |
|
09 Oct 2019 | 08:14AM Comment 9 by Sanjay (Link Technologies) Quality control status: Pass. QC Not required - This case was created before quality check was implemented in version 11 on 30/06/2019 |