Difference between revisions of "Booking In"

From TMS Support Wiki
Jump to navigation Jump to search
Line 1: Line 1:
[[File: ActionsMenu.png |200px|thumb|The booking in screen is accessed by clicking Book-in from the actions menu.]]The prescription life cycle starts with booking in.
=The booking in screen=
 
The booking in screen looks like this.
Booking in refers to inputting the prescription's information into a dedicated booking in screen in PTS. Doing so creates a record of the prescription in the PTS database, which will make it appear in any relevant [[User Views & Homepages|user views]] ready to be progressed and tracked through the prescription lifecycle in accordance with the [[Prescription Types|prescription type]] setup.
[[File: BookingInScreen.png |600px|thumb|center|The booking in screen. It's quite a common practice to leave the booking in screen open on a certain PC.]]
 
The screen is designed so that it can be filled out with just the keyboard by "tabbing" to the next field, and if any particular field only has one applicable option, the field is skipped over. This will save time as you get used to how the screen works, but it can of course be used like any other web form with the mouse if you prefer.
Booking in is usually done manually as per the directions on this page, but it can automated via the optional e-prescribing module.
==Prescription details==
<ul>
<li><strong>Dispensary</strong><br/>
The dispensary that the prescription is being booked into. This will usually show the user's pre-defined default dispensary, but can be changed to another dispensary, if applicable. This is to accommodate users who work at multiple sites across the Trust.</li>
<li><strong>Printer</strong><br/>
The printer from which to produce the prescription label and ticket. Defaults to the default printer for this dispensary.</li>
<li><strong>Booked-in by</strong><br/>
Here you can override the user that is said to be booking in the prescription. Defaults to the current user. This field is sometimes used by Trusts who decide to leave the booking in screen open to save time, meaning the user booking in can just select themselves from this list rather than logging out and back in to PTS with their own account. If the user has their BOOKINUSER permission set to No, they will not be able to change this field and therefore booking in will always be assigned to the current logged in user.</li>
<li><strong>Type</strong><br/>
The prescription type being booked in. Each prescription type will have different information, demographics and target time requirements, and the screen will update the required fields once a prescription type is selected. In newer version of PTS the prescription type may have been handled already, in which case this field can just be used to make last minute changes.</li>
<li><strong>Ward</strong><br/>
The ward that the prescription belongs to.</li>


More often than not, booking in a prescription will simultaneously produce a barcode label for the prescription so that it can be progressed with a barcode scanner. For certain prescription types (e.g. TTO) a ticket may also be produced to hand to the patient for them to monitor the prescription on an outpatient display screen.
</ul>


Once booked in the prescription can then be progressed through its sequence of pre-defined [[Activities|dispensing stages]] ([[Activities|activities]]) followed, optionally, by collection and [[Mobile App User Guide|delivery]].
=Accessing the booking in screen=
The actions menu can be accessed using the actions menu button at the top right of the screen [[File:ActionsMenuButton.png|25px]]. Click Book-in to open the booking in screen.


<i>Later versions of PTS will prompt you to choose the prescription type from a drop down list before the booking in screen opens. This is largely inconsequential but the reason for this change is discussed in the next section.</i>
If a user is allocated to a single Ward (usually users that have
=The booking in screen=
DISPENSARYSTAFF = No and BOOKIN = Yes permissions set) then this field will be hidden.
The booking in screen looks like this.
Required Date
[[File: BookingInScreen.png |600px|thumb|center|The booking in screen.]]
Each prescription type will have a target dispensing time attributed to it and based upon this time PTS 5 will calculate the required date.
The screen is designed so that it can be filled out repeatedly with just the keyboard by "tabbing" to the next field. This will save time as you get used to how the screen works, but it can of course be used like any other web form with the mouse if you prefer. It's quite a common practice to leave the booking in screen open on a certain PC.
Required Time
==Prescription details==
Each prescription type will have a target dispensing time attributed to it and based upon this time PTS 5 will calculate the required time.
If the Date/Time that a Prescription is required is changed from the default target date/time for the Prescription Type being entered, then this date/time is NOT added to if the Prescription is Suspended.
If the logged-on User has the BOOKINTARGET permission set to ‘No’ then they will not be able to amend the required time and the required date and time fields will be hidden.
Request Time
It is possible in PTS 5 to set-up a prescription type that asks you to record when the prescription was requested / prescribed. This gives you the ability to establish how long it has taken from when the prescription was requested to being started. This field will not be displayed if the prescription type selected does not have this as a required entry.

Revision as of 17:04, 15 November 2022

The booking in screen

The booking in screen looks like this.

The booking in screen. It's quite a common practice to leave the booking in screen open on a certain PC.

The screen is designed so that it can be filled out with just the keyboard by "tabbing" to the next field, and if any particular field only has one applicable option, the field is skipped over. This will save time as you get used to how the screen works, but it can of course be used like any other web form with the mouse if you prefer.

Prescription details

  • Dispensary
    The dispensary that the prescription is being booked into. This will usually show the user's pre-defined default dispensary, but can be changed to another dispensary, if applicable. This is to accommodate users who work at multiple sites across the Trust.
  • Printer
    The printer from which to produce the prescription label and ticket. Defaults to the default printer for this dispensary.
  • Booked-in by
    Here you can override the user that is said to be booking in the prescription. Defaults to the current user. This field is sometimes used by Trusts who decide to leave the booking in screen open to save time, meaning the user booking in can just select themselves from this list rather than logging out and back in to PTS with their own account. If the user has their BOOKINUSER permission set to No, they will not be able to change this field and therefore booking in will always be assigned to the current logged in user.
  • Type
    The prescription type being booked in. Each prescription type will have different information, demographics and target time requirements, and the screen will update the required fields once a prescription type is selected. In newer version of PTS the prescription type may have been handled already, in which case this field can just be used to make last minute changes.
  • Ward
    The ward that the prescription belongs to.


If a user is allocated to a single Ward (usually users that have DISPENSARYSTAFF = No and BOOKIN = Yes permissions set) then this field will be hidden. Required Date Each prescription type will have a target dispensing time attributed to it and based upon this time PTS 5 will calculate the required date. Required Time Each prescription type will have a target dispensing time attributed to it and based upon this time PTS 5 will calculate the required time. If the Date/Time that a Prescription is required is changed from the default target date/time for the Prescription Type being entered, then this date/time is NOT added to if the Prescription is Suspended. If the logged-on User has the BOOKINTARGET permission set to ‘No’ then they will not be able to amend the required time and the required date and time fields will be hidden. Request Time It is possible in PTS 5 to set-up a prescription type that asks you to record when the prescription was requested / prescribed. This gives you the ability to establish how long it has taken from when the prescription was requested to being started. This field will not be displayed if the prescription type selected does not have this as a required entry.

Retrieved from ‘https://tmsinsight.com/TMSWiki/index.php?title=Booking_In&oldid=1516’