View source for EST 333702 NHSBT Order Entry via Portal

{{Template:Estimate
|Supimix_Client_Code=NHS
|Supimix_Project_Code=DEV
|Supimix_Site_Code=NH-ALL
|Supimix_Client_Reference=CR-Feb16-01
|Supimix_Number=333702
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference=&nbsp;
|Supimix_Priority=3
|Date_(DD/MM/YY)=29/02/2016
|Clients_Customer=&nbsp;
|System_Version_being_changed=Portal: 6.X, CTMS: 11.X
|Client_Request=Provide a facility for Internal Customer Order Entry and Hospital Collection Order Entry through the Portal, specific to NHSBT needs regarding assets. 
|OBS_Solution=
The standard ''CALIDUS'' Portal Order Entry screen can be used to generate collections and deliveries. This screen is normally available on the Orders menu, called "TMS - Order Entry", although this is configurable in title as well as position. The requested use is predominantly for Stem Cell orders, but can be used to generate any order.

It is expected that this screen can and should also be used for Hospitals arranging collections of samples, although the Portal user group will restrict the type of data that can be entered.


The screen will be modified for the purposes on NHSBT. This will be controlled through the existing Portal Order Entry Configuration Window Type, with a new value "F", for "Fixed".

The first step prompts the user for all order header information. 

[[file:EST_333702_Order1.PNG|border|600px]]
<br />''Adding an Order - Step 1''<br />

This will be modified to remove the indicated sections:
* Collection Date/Time From and To
* Delivery Date/Time From and To
* Delivery Type (Service)


The Collection and Delivery address steps will not be modified, as both collection and delivery orders may be raised using this screen.

[[file:EST_333702_Order2.PNG|border|600px]]
<br />''Adding Order Addresses''<br />

The user will be required to user to enter both locations and addresses.

It is expected that this will be limited via the Portal User Group to ensure that the user has access only to locations that are applicable to that user, to make searching for Collection and Delivery addresses easier.



A new step will be added between steps 3 (Delivery Address) and 4. This will allow entry of:
* Delivery/Collection Date
* Delivery type (Service), selecting from a drop-down list. This will default to Standard, but will allow the user to select Ad Hoc as well. No other options will be available. A restriction will be added to the Portal User's group, which can restrict the types to those that are applicable to that user group.
* Selection of standard route times for Standard type
* Selection of pre-existing trip times, or manual entry of collection and delivery dates and times, for Ad Hoc type. 
{{Note}} If Ad Hoc is chosen, an alert will be displayed informing the user that they may be charged.


Examples:

If Standard type is chosen, a drop-down list will be displayed of all the fixed routes available for that location on the selected day. The user will be able to select one of those. When selected, the collection and delivery dates and times from the route will be defaulted into the collection and delivery dates and times on the screen. These cannot be changed.


If Ad Hoc type is chosen, a warning will be displayed to the user that they may be charged for this order. A drop-down list will be displayed of all the existing trips created for that location on the selected day, and a "Manual" option. The user selects one of the pre-existing trips. When selected, the collection and delivery dates and times from the trip will be defaulted into the collection and delivery dates and times on the screen. These cannot be changed.


If Ad Hoc type is chosen, a warning will be displayed to the user that they may be charged for this order. A drop-down list will be displayed of all the existing trips created for that location on the selected day, and a "Manual" option. The user selects the Manual option. The user may now enter collection and delivery dates and times from the trip.



The user may then proceed to step 4, where they may enter products to be delivered or collected.

First, the user enters the number of items, the container type and contents, selecting from the provided lists, as well as a number of items. Dimensions and weight will default once this is selected.

Container Type will allow selection of any DU type within C-TMS. A restriction will be added to the Portal User's group, which can restrict the types to those that are applicable to that user group. For example, for Hospitals, this may be restricted just to sample types.

To enter the item details against the line, the user will click the '''Add Items''' button against the line. The screen will be modified to allow the user to specify the Asset ID.


[[file:EST_333702_Order3.PNG|border|600px]]
<br />''Adding Order Lines and Items''<br />

The Asset ID will be validated as being in the correct format for NHSBT, dependent on the asset type:
* For reusable assets, the Item ID must start with "8004". 
* For non-reusable assets, the Item ID must start with "00". 
This will also offer a lookup and matching facility, and will validate asset IDs for use at that location, and allow creation if necessary.



When updated by the user, the order will be saved in C-TMS, with the Asset ID saved in the appropriate place.


{{Note}} It is expected that all labels in this screen will be checked once complete to ensure that no spelling mistakes exist.


Orders created in this way will drop into the C-TMS order well directly.

Any Standard orders on routes with pre-existing trips will be planned onto those trips automatically.

Ad Hoc orders will ''not'' be automatically planned and can be scheduled through the normal C-TMS trip planning screens.
|Requirements_Days=0
|Estimation_Days=2.0
|Functional_Specification_Days=2.0
|Technical_Specification_Days=0
|Development_Days=9.25
|Testing_and_Release_Days=1.75
|Implementation_Days=0.50
|Project_Management_Days=0.75
|Year=2016
|Free_Of_Charge=N
}}