Difference between revisions of "Our prescriptions are not clearing automatically"

From TMS Support Wiki
Jump to navigation Jump to search
 
(22 intermediate revisions by the same user not shown)
Line 1: Line 1:
The prescription lifecycle is highly configurable by system administrators. Sometimes, due to a misconfiguration, prescriptions may not organically disappear from your user views even though they are considered "done".
The prescription lifecycle is highly configurable by system administrators. Sometimes, due to a misconfiguration, prescriptions may not organically disappear from your user views even though they are considered "done".
=Symptoms=
=Symptoms=
Despite completing every activity in the sequence, the prescription remains on the user view/homepage, causing confusion and clutter. Given enough time the sheer number of prescriptions building up can even start to cause performance problems.
Despite a prescription being considered finished, the prescription remains on the user view/homepage, causing confusion and clutter. As a result staff may find themselves regularly clearing all prescriptions off throughout the day - indeed over the years we've encountered a number users who have assumed this is normal.
=Cause=
[[File:CollectButton.png|250px|thumb|Hover over the progress button to determine what the prescription is waiting for you to do. In this example, the prescription is waiting for colelction.]]
Either not all of the activities or tasks that have been configured for the prescription type are being completed, or (less likely) the user view is set up in a way that it shows completed prescriptions.


The task that is at the heart of the issue can be determined by looking at one of the prescriptions that is "stuck". The clearest indication is to look at what the green "progress" button is currently expecting.
Given enough time the sheer number of prescriptions building up can even start to cause performance problems.


Whether the task <strong>should</strong> be completed, or if the task is surplus to requirements and should be removed, is a discussion for pharmacy management, but both avenues are discussed below.
=Causes=
[[File:CollectButton.png|250px|thumb|Hover over the progress button to determine what the prescription is waiting for you to do. In this example, the prescription is waiting for collection.]]
The underlying cause is that not all of the activities or tasks that have been configured for the prescription type are being done. Or less likely, the user view is set up in a way that it displays completed prescriptions.
 
The task that is at the heart of the issue can be determined by looking at one of the prescriptions that is "stuck". The clearest indication is to look at what the green "progress" button is currently expecting. Make a note of what the majority of the prescriptions are waiting for, and then move on to the appropriate solution below.
 
Whether the task should be completed, or if the task is surplus to requirements and should be removed, is a discussion for pharmacy management, but both avenues are discussed below.


=Solutions=
=Solutions=
<ol>
<ol>
<li>[[Database_Indexing|Index the PTS database]].</li>
 
<li>Turn off [[Label_Printer_Installation|bi-directional support]].<br/>
<li>Prescriptions are <strong>waiting for collection</strong>:<br/>
<i>(Please do not underestimate the performance impact of this setting even if you have never heard of it before)</i></li>
<i>(By a long way, this is the most common situation)</i>
<li>Consider whether your prescription types are set up correctly so that they [[Our prescriptions are not clearing automatically|clear automatically when finished]]. Also see [[User_Views_%26_Homepages#Actions_menu|how to clear lots of prescriptions at once]].</li>
<ol type="a">
<li>Use a resource monitor or the SQL performance dashboard to identify the application at fault and then contact the manufacturer.</li>
<li><i>[[Progressing_a_Prescription_%26_Scanning_Barcodes#Collect_a_prescription_or_bag|Collect the prescriptions]], or:</i></li>
<li>Use SQL performance dashboard to identify the expensive query and have IT or the manufacturer optimise it and/or reduce its frequency.<br/>
<li><i>In the prescription type's setup page, [[Prescription_Types#Type_details_tab|turn off "record collection"]].</i></li>
<i>(This issue seems to be becoming more common, please test your queries for performance at scale before rollout)</i></li>
</ol>
<li>Consider upgrading your server hardware to the [[High_Level_Design_Document|recommended PTS 5 specification]].</li>
</li>
<li>In Setup > Application Settings, locate the "skip checking if PTS is online" setting (OFFLINE) and set to Yes. This tells PTS not to attempt any remote connections.</li>
 
<li>Prescriptions are <strong>waiting for delivery</strong>:
<ol type="a">
<li><i>Use the mobile app to [[Mobile_App_User_Guide|deliver the prescriptions]], or:</i></li>
<li><i>In the prescription type's setup page, [[Prescription_Types#Type_details_tab|turn off "record delivery"]].</i></li>
</ol>
</li>
 
<li>Prescriptions are <strong>waiting for an activity</strong> e.g. Start Labelling:
<ol type="a">
<li><i>[[Progressing_a_Prescription_%26_Scanning_Barcodes#Progressing_a_prescription|Record the activity]], or:</i></li>
<li><i>In the prescription type's setup page, [[Prescription_Types#Scanning_sequence_tab|remove the activity from the scanning sequence]].</i></li>
</ol>
</li>
 
<li>Prescriptions are waiting for <strong>"Start Completion", "Start Prescription Complete", "Start Final Check Complete"</strong> or similar:<br/>
<i>(For context these are the most common examples of [[Activities#Instant_activity_examples|instant activities]] set up by users to provide a firm stopping point to the end of the prescription lifecycle)</i>
<ol type="a">
<li><i>[[Progressing_a_Prescription_%26_Scanning_Barcodes#Progressing_a_prescription|Record the activity]], or:</i></li>
<li><i>Find the activity in the activities setup page, and make sure it is configured as an instant activity, and:</i></li>
<li><i>In the prescription type's setup page, [[Prescription_Types#Scanning_sequence_tab|make sure the activity is at the end of the scanning sequence]], or:</i></li>
<li><i>In the prescription type's setup page, [[Prescription_Types#Scanning_sequence_tab|remove the activity from the scanning sequence]].</i></li>
</ol>
</li>
 
</ol>
</ol>
If none of these examples apply, it's possible (though much less likely) that the user view has been incorrectly configured to return completed prescriptions. If you are sure that the prescriptions are not waiting for any further input, yet are still erroneously showing up, see the [[Setting_Up_User_Views#Filters_tab|filters tab]] of the [[Setting Up User Views]] page to learn how to ensure the user views are set up correctly.

Latest revision as of 15:41, 20 December 2023

The prescription lifecycle is highly configurable by system administrators. Sometimes, due to a misconfiguration, prescriptions may not organically disappear from your user views even though they are considered "done".

Symptoms

Despite a prescription being considered finished, the prescription remains on the user view/homepage, causing confusion and clutter. As a result staff may find themselves regularly clearing all prescriptions off throughout the day - indeed over the years we've encountered a number users who have assumed this is normal.

Given enough time the sheer number of prescriptions building up can even start to cause performance problems.

Causes

Hover over the progress button to determine what the prescription is waiting for you to do. In this example, the prescription is waiting for collection.

The underlying cause is that not all of the activities or tasks that have been configured for the prescription type are being done. Or less likely, the user view is set up in a way that it displays completed prescriptions.

The task that is at the heart of the issue can be determined by looking at one of the prescriptions that is "stuck". The clearest indication is to look at what the green "progress" button is currently expecting. Make a note of what the majority of the prescriptions are waiting for, and then move on to the appropriate solution below.

Whether the task should be completed, or if the task is surplus to requirements and should be removed, is a discussion for pharmacy management, but both avenues are discussed below.

Solutions

  1. Prescriptions are waiting for collection:
    (By a long way, this is the most common situation)
    1. Collect the prescriptions, or:
    2. In the prescription type's setup page, turn off "record collection".
  2. Prescriptions are waiting for delivery:
    1. Use the mobile app to deliver the prescriptions, or:
    2. In the prescription type's setup page, turn off "record delivery".
  3. Prescriptions are waiting for an activity e.g. Start Labelling:
    1. Record the activity, or:
    2. In the prescription type's setup page, remove the activity from the scanning sequence.
  4. Prescriptions are waiting for "Start Completion", "Start Prescription Complete", "Start Final Check Complete" or similar:
    (For context these are the most common examples of instant activities set up by users to provide a firm stopping point to the end of the prescription lifecycle)
    1. Record the activity, or:
    2. Find the activity in the activities setup page, and make sure it is configured as an instant activity, and:
    3. In the prescription type's setup page, make sure the activity is at the end of the scanning sequence, or:
    4. In the prescription type's setup page, remove the activity from the scanning sequence.

If none of these examples apply, it's possible (though much less likely) that the user view has been incorrectly configured to return completed prescriptions. If you are sure that the prescriptions are not waiting for any further input, yet are still erroneously showing up, see the filters tab of the Setting Up User Views page to learn how to ensure the user views are set up correctly.