I would like to propose some changes to the distribution function to address some current limitations:
-
When samples are retrieved for a distribution, we need to record where the retrieved samples (or boxes) are being stored in the holding tank. If a large number of samples are being retrieved daily, it’s critical we know exactly where they are located after they have been retrieved.
-
When requesting samples from certain collection protocols, the release of any samples must be approved by the custodian before the samples can be retrieved. This should be configurable per collection protocol.
-
Distribution currently doesn’t separate the request from the actual retrieval and sending of samples. Currently distribution assumes the request, retrieval and sending is all happening at the same time and by the same person. At SAHMRI we have people request samples, but the actual retrieval from the tanks and sending of samples would go to our support team to perform, which will occur sometime after the request. Being able to log when the request is submitted, when its retrieved and when its sent/received would be very useful.
-
We need to distinguish between external and internal distributions.
For external distributions things like courier pickup, delivery times and sample condition are important to capture.
For internal distributions we need to capture when the requester has collected the samples. An email would useful to indicate to an internal requestor that their samples are ready for collection. -
When a distribution request is submitted, it would be great if a retrieval queue could be displayed and for each request a pick list can be generated. Almost like a work basket for our support team.
Would be interested in how others use the distribution module and if the suggestions above would be useful?