Company: Link Technologies
Case No: L09152. Project: 10.10: LinkSOFT Version 10.1
Logged By: Rashna (Edge Business Solutions) on 01 Mar 2018 01:17PM
Priority: Medium
Product: Point of Sale
Group: Enhancement
Time Taken: 14.50 (Weight: 14.50)
Version: 10.155.0117
Assigned To: Sanjay (Link Technologies)
Circulation: Alvis, Development, Rashna, Sanjay
Resolve By: Friday, 02 March 2018 12:00 AM [2220 days since logged date]
Status: Closed
Subject: Improvements to Prescription Repeats
Summary:    
Requirements
We have the facility to enter how many "Repeats" a patient can have for a prescription. Currently, we are unable to see how many we have dispatched. We need the "Repeat" sequence to reduce as we dispatch items.

Proposed Design

  1. Add ability to load a prescription and have the option to print repeats
  2. The repeat count should reduce by 1
  3. The original and Repeated transaction should be read only once printed.
Test Plan

  1. Create a Prescription
  2. Set the Repeat as 5.
  3. Sell the Prescription
  4. Load the Prescription again
  5. Copy the Prescription. All lines that have repeat greater than 0 should be loaded only. Here the Repeat Number should be updated at "Save".
  6. The Repeat should be correctly printed on the Prescription Label
  7. If user copy's the record and does not save the record, the repeat number should not be changed.
  8. Users may be able to change and save the number.

Audit Notes:Edited by sanjay on 05/03/19 10:24. Edited by sanjay on 04/10/18 13:19. Edited by sanjay on 04/10/18 13:08. Edited by sanjay on 04/10/18 13:08. Edited by rashna on 27/07/18 07:07. Edited by rashna on 27/07/18 07:04. Edited by rashna on 27/07/18 07:02. 
06 Sep 201810:14AM Comment 1 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 06-09-2018 10:14 AM
Closing this case due to "No Response". Create a new case if this is still required. 

02 Oct 201806:55AM Comment 2 by Rashna (Edge Business Solutions) Assigned To: Rashna (Edge Business Solutions) Followup Date: 02-10-2018 06:55 AM Time Taken: 0.50
Case opened for further discussions.

02 Oct 201809:31AM Comment 3 by Sanjay (Link Technologies) Case 9152 added to project 10.1
02 Oct 201809:45AM Comment 4 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 02-10-2018 09:45 AM Time Taken: 1.00

Hi Sanjay, 

I have updated case with the test plan.

Thanks
Rashna


03 Oct 201810:57AM Comment 5 by Alvis (Link Technologies) Case 9152 removed from project 10.1
03 Oct 201810:57AM Comment 6 by Alvis (Link Technologies) Case 9152 added to project 10.0
04 Oct 201801:44PM Comment 7 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 04-10-2018 01:44 PM Time Taken: 3.00 Notes: Edited by sanjay on 04/10/18 14:30. Edited by sanjay on 04/10/18 14:27. Edited by sanjay on 04/10/18 14:08. Edited by sanjay on 04/10/18 14:02. 

The design proposed does not solve the requirements. The requirement states " we are unable to see how many we have dispatched"

We have created a use case to help with this design:

Part A - USE CASE:

  1. A patient comes into the pharmacy with a prescription which has 1 repeats
  2. Pharmacist issues medication with REPEAT marked as 1. Items are dispatched and sold through POS as Prescription label PR001
  3. A week later, the patient comes in with Prescription no. PR001 which shows 1 repeat
  4. The Pharmacist loads PR001 and verifies the 1 repeat. The pharmacist does not have a convenient way to see if any repeat has been issued after PR001.

Part B - Design:

  1. To resolve # 4 above, we will add a BUTTON that will show any prescriptions linked to PR001
  2. The pharmacist needs to verify that there are no other LABELS related to PR001
  3. To issue a REPEAT for PR001, Load label PR001, COPY and Save. We will Link PR001 to the new prescription, therefore, we can no show what entries relate to this prescription. Let's say label PR010 is printed with ZERO repeats.
  4. If the patient comes in the third time, with either PR001 or PR010, The pharmacist can load the label, select to view what copies have been issued and decide which repeat to copy.

PART C - Here are the changes we are making:

  1. Add a button above SAVE [F2] called "View Copies"
  2. The button will load a list of prescription "labels" that were copied. The display will show all copied entries with the following fields:
    1. ReferenceNo
    2. LineNo
    3. DateIssued
    4. PatientName
    5. TotalValue
    6. Repeat
    7. CopiedLabelNo
    8. Status
  3. To make a REPEAT transaction, perform these steps:
    1. Load the presented label
    2. View Copies to verify related entries
    3. Save the new label with the correct number of repeats

04 Oct 201803:17PM Comment 8 by Sanjay (Link Technologies) Assigned To: Development Followup Date: 04-10-2018 03:17 PM Time Taken: 8.00 Notes: Edited by sanjay on 04/10/18 15:19. 
Development work for this case has been completed.
The change will be available in version: 10.06

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

  1. Refer to comment 7 part C
  2. When a "View Copies" row is clicked, the row is loaded on the main form.

2. The issue was caused by:

  1. Improvement

    3. Next Step

    1. UAT

    05 Oct 201801:39PM Comment 9 by Sanjay (Link Technologies) Assigned To: Rashna (Edge Business Solutions) Followup Date: 05-10-2018 01:39 PM Time Taken: 1.00
    System test completed. proceed with UAT

    08 Oct 201804:23PM Comment 10 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 08-10-2018 04:23 PM
    Hi Sanjay
    QA Results
    Tests carried out according to requirements specified on the case header

    Test Results Summary

    Table 1 - Summarised list of issues
    NoTest DescriptionPass/Fail
    1"View Copies" button has been added to see the number of repeats pendingPass
    2Create a prescription with the repeat as 3. Save the prescription. View Copies Repeat should be 3Pass
    3Copy the prescription, update the repeat to 2.  View Copies Repeat. Both repeat prescription 1 and 2 should appear with repeats as 3 and 2 respectively.  Pass
    4Void the 2nd prescription. The status of the prescription in view copy should be canceledPass
    5Sell the 1st prescription. The prescription should get paid and closed.Pass

    Environment Details

    1. OS version: Windows Server 2012
    2. Application version: 10 Beta 7
    3. Setup: Demo
    4. Server : 10.0.0.10
    5. Database: LINKSOFT-DEMO-10-RASHNA

    Steps to reproduce failed scenarios: N/A

    Next Step: for documentation


      09 Oct 201809:36AM Comment 11 by Rashna (Edge Business Solutions) Assigned To: Sanjay (Link Technologies) Followup Date: 09-10-2018 09:36 AM Time Taken: 1.00

      Hi Sanjay, 

      Documentation has been updated under POS -- Prescription -- Start Prescription Entry.

      Thanks
      Rashna


      09 Oct 201810:08AM Comment 12 by Sanjay (Link Technologies) Assigned To: Sanjay (Link Technologies) Followup Date: 09-10-2018 10:08 AM
      Thanks Rashna 

      09 Oct 201908:14AM Comment 13 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
      If you have any queries regarding this support incident, please email admin@linktechnologies.com.au and include the Case No: L09152 in the subject line of all emails regarding this issue.

      Document size: 10.3 KB
      For call complaints, please contact the Managing Director of the company using this form