Pneumatic tube carrier routing and tracking system

A system and method provides for a pneumatic tube carrier routing and tracking system having a system control module that captures and presents tracking information associated with sending and receiving carriers. The pneumatic tube carrier tracking system comprises sending and receiving stations connected by pneumatic tubing, and which are configured to securely send carriers, with receiving users optionally being restricted from unauthorized access of carriers. The receiving station further comprises a plurality of receiving bins, each comprising a door for preventing access to the receiving bin by unauthorized users. The sending and receiving stations have identifying tag readers configured to scan identifier tags to read carrier delivery, carrier receipt and receiving user information. Destination and intended recipient information are entered at the sending station when sending a carrier and are transmitted to a system control module, which routably delivers and secures the carriers in response the destination and intended recipient information.

FIELD OF THE INVENTION

The present principles generally relate to pneumatic tube delivery systems. More specifically, the present principles refer to a system and method for routing and tracking carriers and associated payloads in pneumatic tube delivery systems directly to an end user.

BACKGROUND OF THE INVENTION

In large institutional settings such as hospitals, the dispensing and delivery of drugs has become a time consuming process. In particular, sterile items, controlled medications, biological samples, and the like need to be prepared and transported in a secure environment while ensuring the safety of patients and hospital workers.

Transporting objects via pneumatic tubes is known to the art. Pneumatic delivery systems are used extensively for the rapid and efficient transportation of a wide variety of articles. These delivery systems are used in a number of business operations, including, but not limited to, banks, hospitals, office buildings, industrial plants, and transportation terminals.

To send a payload in a carrier, an object is placed within a carrier which is then transported within enclosed pneumatic tubing by air under either positive or negative pressure to a desired destination. The interior of the closed tube and the outer dimension of the carrier form a seal so that the carrier can be propelled between the destinations by a vacuum or positive air pressure.

One specific area of commerce which currently uses the pneumatic tube for transporting materials is the hospital or biomedical research/manufacturing industry. Pneumatic tube delivery systems have proven to be particularly useful for transporting blood samples, medicines, intravenous bags, viral samples or other biological or chemical matter within hospitals or laboratories. Some of the payloads transported may be highly addictive drugs (i.e. morphine) which need to be tightly controlled.

In a hospital environment, pneumatic tube systems are also used to transport prescriptions from a pharmacy located in the hospital facility to the patient. Such pneumatic tube systems comprise a sending station located at the pharmacy in communication with a plurality of receiving stations located throughout the hospital. Each receiving station typically includes a single receiving bin such that all carriers are delivered to the single receiving bin, regardless for which patient and room the prescription within the carrier was destined. In use, when the doctor prescribes medication, the pharmacy fills the prescription and delivers it inside a carrier to a desired receiving station via the pneumatic tube system. The user at the receiving station opens the carrier and determines to which patient at which room the user needs to deliver the prescription. User error may occur during the identification of the room and patient resulting in miss-delivery of the prescription. In addition, unauthorized users may have access to the carriers at the receiving station.

Thus, there is clearly a need for a system and method providing a secure pneumatic tube carrier delivery. Also a need exists for a system and method providing routing and tracking of carriers in a pneumatic tube system to a receiving bin at a receiving station associated with an end user to ensure the secure delivery of carrier contents to proper destinations and authorized end users. Furthermore, there is a need for an auditable trail indicating the chain of custody of carrier contents from the sending station to the end user.

According to the present principles there is provided a pneumatic tube carrier system for routing and tracking carriers in a pneumatic tube system comprising a pneumatic tube system, a connecting diverter with blower, and storage piping with diverters, sending and receiving stations, a system control module, and identifying tag readers configured to read identifying tags. The identifying tag readers scan delivery information to provide secure and authorized delivery of carriers and their contents. The identifying tag readers and system control together provide an efficient and secure method and system of routing and tracking carriers and carrier contents throughout the pneumatic tube system.

SUMMARY OF THE INVENTION

Presented herein is a pneumatic tube carrier routing and tracking system having a system control module that routes carriers and captures and presents tracking information associated with sending and receiving carriers. The system control module comprises a database module and a computer control center module in signal communication with the database module.

The pneumatic tube carrier tracking system further comprises a sending station and a receiving station in signal communication with the system control module. The sending station and the receiving station are routably connected by pneumatic tubing for the delivery of carriers.

The sending station has an identifying tag reader configured to scan identifier tags to obtain delivery and identifying information for a carrier. The identifying tag reader then transmits the delivery information to the system control module. The receiving station has an identifying tag reader configured to scan identifier tags to obtain and transmit reception information for a carrier to the system control module. The identifying tag reader transmits delivery information and reception information to the computer control center module which interprets delivery information and reception information and sends commands to the pneumatic tube system to control routing of the carrier in the pneumatic tubing. The database module is configured to receive and store delivery information sent to the System Control Module from the sending station and reception information from the receiving station.

In one embodiment, the receiving station comprises a plurality of receiving bins, wherein each receiving bin comprises a door preventing access to the receiving bin. The system control module comprises a database module for storing a list of users authorized to access each of the plurality of receiving bin of the receiving station. The sending station comprises a carrier receiving bin and a tag reader for reading an identification tag of a carrier or of contents of a carrier to obtain destination information. Preferably, the destination information comprises identification of one receiving bin of the plurality of receiving bins of the receiving station. The system control module receives the identification of the one receiving bin from the sending station and routes the carrier from the sending station to the one receiving bin of the receiving station through the pneumatic tubing. To unlock the one receiving bin, the system control module receives a selection of the one receiving bin and a user identification information from the receiving station or from a mobile device. The system control module verifies whether the user identification information matches a user from the list of users authorized to access the one receiving bin. If the user is authorized to access the one receiving bin, the system control module sends a command to the receiving station to unlock the door of the one receiving bin.

In one embodiment, the system comprises a tag reader that allows a user to capture unique identifiers for individual carriers and contents, sending stations, receiving stations and sending and receiving users. A database disposed within the system also permits the user to archive and retrieve data associated with sending and receiving deliveries through the pneumatic tube system. Further, the system comprises the ability to institute security measures such as holding a carrier until a receiving user's identification (hereinafter “ID”) is entered into, and verified by, the tracking system.

According to a method of using the present invention, the carrier contents are prepared for a carrier to be sent to the pneumatic tube carrier tracking system. Identifying tags are scanned using the identifying tag reader at the sending station to capture delivery information. The carrier is received in a carrier receiving bin of a sending station. The delivery information is transmitted from the identifying tag reader to the system control module and the carrier is sent through the pneumatic tubing system from the sending station. The system control module receives the incoming delivery information from the identifying tag readers at the sending station and the reception information from the receiving station and logs and stores this information in the database module. The computer control center module interprets the delivery information and sends commands to the pneumatic tube system to control the operations of the system and routably deliver the carrier. The carrier is routed through the pneumatic tube system in response to the delivery information and sensed by optical sensors in the branches of the pneumatic tubing until it reaches the receiving station. The carrier is delivered to the receiving station where identifier tags are scanned by an identifying tag reader to capture reception information. The reception information is transmitted to the system control module from the identifying tag reader and the sender at the sending station is optionally notified that the carrier has been delivered. The pneumatic tube carrier tracking system allows a carrier to be routed from any station on the pneumatic tubing system to any other station.

DETAILED DESCRIPTION OF THE INVENTION

Illustrative embodiments of the present principles are disclosed herein. However, techniques, systems and operating structures in accordance with the present principles may be embodied in a wide variety of forms and modes, some of which may be different from those in the disclosed embodiment. Consequently, the specific functional details disclosed herein are merely representative, yet in that regard, they are deemed to afford the best embodiment for purposes of disclosure and to provide a basis for the claims herein which define the scope of the present principles.

Some elements of the present principles are illustrated as modules for performing described functions. While these modules may be described in terms of software implementations, any hardware, or combination of hardware and software may be used to implement the present principles without deviating from the scope or spirit thereof.

Moreover, well known methods and procedures for both carrying out the objectives of the present principles and illustrating the preferred embodiment are incorporated herein but have not been described in detail as not to unnecessarily obscure novel aspects of the present principles.

Referring now toFIG. 1, a diagram illustrating a system and method for routing and tracking carriers and payloads in a pneumatic tube system100according to an embodiment of the present principles is shown. System control module222controls the operation of pneumatic tube system100, reading, storing, and presenting data, and routing and tracking the delivery of carriers in response to the collected data. One or more identifying tag readers108may read and store a unique ID tag associated with the carrier contents or payload110, or with the sending user's ID112, the receiving user's ID120, or the carrier ID114. The identifying tag readers108may also read and store a unique ID tag associated with the sending station and delivery station. In one useful embodiment, an identifying tag reader108may read the ID tag of objects using an optical scanning system to read bar codes. Alternatively, an identifying tag reader108may employ an optical scanning system to identify characters and read and store the ID or identifier information of various objects. In another embodiment, the identifying tag reader108may identify objects using RFID or other radio frequency technology. Additionally, any other identification technology known, or as yet undiscovered, may be used within the scope of the present principles. The sending user's ID may be a badge, a wristband, or the like. The identifying tag reader108may replace the need for a control panel, allowing all the necessary scanning, interpreting, and sending of a payload to be performed at one station. In alternative embodiments, the identifying tag reader108may be the sending station itself.

The identifying tag reader108sends identifier information from delivery station104to system control module222. The delivery stations104and106may be a station primarily used to send or primarily used to receive payload containing carriers. However, delivery stations104and106may be used to both send and receive carriers.

System control module222receives identifier and delivery information from the identifying tag reader108at delivery station104and determines the appropriate actions to be performed on delivery station106. For example, the system control module222may use the information from identifying tag reader108at delivery station104to determine to which delivery station106a carrier610will be routed and which receiving user ID120must be scanned in order for the receiving user to receive the carrier610(given that the sender requires the receiving user ID to be scanned prior to receiving the carrier). The receiving user at delivery station106, upon receiving the carrier delivery, uses an identifying tag reader116to scan their ID120, carrier contents118, and the carrier ID122, completing the transaction. This information is sent from the identifying tag reader116at delivery station106to system control module222to be recorded and stored in the system.

Referring now toFIG. 2, a diagram illustrating a pneumatic tube system200according to an embodiment of the present principles is shown. The pneumatic tube carrier tracking system200comprises transmission tubing228, a system control module222, and a sending station224and receiving station208for initiating the sending of carriers and receiving the sent carriers. AlthoughFIG. 2demonstrates a one zone pneumatic tube system200, a system with multiple zones and the inclusion of any number of sending224and receiving stations208is possible without deviating from the scope of the present principles. The system also includes blower214and one or more diverters216and226which direct the transportation of carriers610from storage compartment218to sending station224or receiving station208at the direction of the system control module222. Furthermore, pneumatic tube system200may include a plurality of inline identifying tag readers or optical sensors220configured to track or sense the carriers as they are transported through the tubing228. The inline identifying tag readers or optical sensors220may be implemented for example, through a window or a section of the tubing228, through an RFID antenna disposed on a recess section of the tubing228, through an optical sensor disposed in the tubing228, or the like. The inline identifying tag readers or optical sensors220read, or otherwise sense, the passage of a carrier associated with the payload being transported through the pneumatic tube system.

In one embodiment of the present principles, the ID tags may be used to record the location and ID114and122of a carrier610at various locations throughout the pneumatic tube system200to send to the system control module222in order to keep a log of each carrier's location information as they move through the pneumatic tubing228. This creates an auditable trail indicating a chain of custody. It allows the user to know where the carrier and its contents have been and where they are going.

While the present principles are described with respect to a hospital, the present principles may also be used in, but are not limited to, banks, retail stores, pharmacies, laboratories, or the like.

ID tags may also be associated with the ID of sending and receiving users. The ID tag scanning at the sending stations224and receiving stations208may be performed by an identifying tag reader such as, for example, a handheld PDA700. However, any identifying tag reader108and116configuration may be used including, but not limited to, a scanner integrated into the sending or receiving station, or any other known or as yet undiscovered configuration.

System control module222may include database module202and computer control center module206in signal communication. The system control module222receives carrier information from the tag readers at the sending and receiving stations and logs the carrier information into a database module202. Additionally, the system control module222may receive carrier location information from inline identifying tag readers or optical sensors220disposed throughout the pneumatic tube system200and log this information into a database manager202.

The database module202may be, for example, a relational database, a flat file database, fixed length record database, or any other data storage mechanism known or as yet undiscovered in the art. Further, the database module202may reside on a stand-alone server, or the same machine as the computer control center module206.

The computer control center module206manages data by interpreting data stored in the database module202and sending routing commands to the pneumatic tube system based on location data and delivery information collected from sending users. In one useful embodiment, the computer control center module206performs the functions of a data manager. In an alternative embodiment, there may be a separate data manager module to interpret the data stored in the database module202and send routing commands to the computer control center module206which then sends commands to the pneumatic tube system based on location data and delivery information.

The sending station224, diverters216and226, blower214, carrier receiving bin210, and receiving station208are all in signal communication with, and controlled by, the computer control center module206. The computer control center module206interprets the data in the database module202and generates commands in the form of signals to individual elements in the pneumatic tube system200to control the actions of the system200. For example, the computer control center module206may command the pneumatic tube system to activate the blower214to transport a carrier610through the pneumatic tube system200. In response to data stored in the database module202, the computer control center module206may generate a signal to turn on blower214, which blows air to move the carrier610throughout the pneumatic tube system200. Similarly, the diverters216and226may be signaled by the computer control center module206to route a carrier to a particular branch in the pneumatic transmission tubing228to be delivered to a desired receiving station208.

The system control module222may also be configured to manage deliveries. The system control module222receives requests for delivery from a sending station224. The data input by a user at a sending station224identifying tag reader108is used to determine the physical location of a carrier610and where the carrier610should be routed to. Additionally, the system control module222uses the information from the sending station224to determine how the carrier should be delivered (i.e. secured, with alarms, etc.).

System control module222may also track carriers610as they move past inline identifying tag readers or sensors220in the pneumatic tubing228. The system control module222may generate records to show that a carrier610passed an inline identifying tag reader or sensor220at a certain time. These records may be used to ensure that carriers610are routed correctly and in the correct order. Location recordation may also be used to troubleshoot and initiate error notifications, such as a stuck or lost carrier610, or may be used to guarantee or verify a timely delivery for perishable contents (i.e. drugs or blood contents that must be refrigerated). Additionally, reports on chain of custody of carriers may be generated to keep record of who has a specific carrier at a specific point in time and where that carrier is located.

The system control module222may also control and verify delivery to receiving users at receiving stations208. In order to initialize a shipment, the sending user enters information into the sending station224that will be used to manage carrier610routing and delivery through the pneumatic tube system200. The sending user prepares the contents of the carrier610for shipment. The contents of the carrier610may be, for example, prescriptions, blood samples, patient file information, and the like.

After the sending user prepares the contents of the carrier610for shipping from the product production station232, the sending user may scan the ID of the carrier contents110with the handheld PDA700. The sending user may also scan the sending user ID112, the ID of the desired receiving station106, and the ID of the carrier114with the handheld PDA700.

In one useful embodiment, the sending user may work at a desk or station separate from the sending station and may place the carrier610on a conveyor belt at the product production station232to be delivered automatically to the sending station224. The contents and the carrier610are brought to the sending station224via an incoming conveyor from the product production station232. The product prepared by the sending user enters the carrier610through an opening in the top of the carrier610. In one embodiment, a loaded carrier610may optionally be moved to an inspection station and subsequently sent into the pneumatic tube system200where it is delivered to the proper location in response to commands from the computer control center module206. Alternatively, the contents and the carrier610may be deposited directly into the sending station224by the sending user without the aid of a conveyor belt or inspection station.

In another useful embodiment, a more passive system may be used for the scanning of the delivery information. The identifier tags may be RFID tags which can be read by an RFID identifying tag reader. In such an embodiment, the sending user at the sending station224may move near the RFID identifying tag reader while holding the carrier and its contents, and the reader will read and send the ID information from the sender, the carrier, and the contents to the system control module222. Thus, sending users may advantageously avoid physically scanning each identifier tag to obtain delivery information.

The scanned information from the handheld PDA700is transmitted to the system control module222where it is stored in the database module202and interpreted by the computer control center module206. The computer control center module206then determines the destination of a particular carrier610, and the necessary command to route the carrier610properly. The computer control center module206sends routing commands to the pneumatic tube system200to control the operations of the system.

Blower214and diverters216and226may be used to coordinate and direct the transportation of the carriers throughout the pneumatic tube system200and between the storage compartment218and the pneumatic tube system200. Carriers move through branches of the pneumatic tubing228in the system under vacuum or pressure supplied by blower214. The computer control center module206sends a signal to the blower214to blow air to transport the carrier610at the appropriate time. As the carriers move through the system, the computer control center module206controls the carriers'610routing by transmitting commands to diverters216and226which may change the position and/or direction of the carriers610. In an alternative embodiment, a vacuum system may be used in place of a blower214to move carriers610through the pneumatic tube system with negative air pressure.

In one embodiment, after the computer control center module206routes the carriers610through the tubing228via the diverters216and226, the carriers610travel to the carrier receiving bin210at the receiving station. At this station, the carrier610is opened and the contents of the carrier610are dropped in the carrier receiving bin210. The ID of the empty carrier122may then be scanned with the handheld PDA700to keep record of which carriers610are available from the storage compartment218for other shipments.

Upon receipt of the contents the receiving user may scan their ID120, and may also scan the ID tags of the carrier contents118. This information is sent to the system control module222where it is stored in the database module202and interpreted by the computer control center module206. The computer control center module may optionally notify the sending user of completion of the transaction according to the sending user's instructions entered when the carrier was initially sent.

In an alternative embodiment, a slide plate236may be disposed in the pneumatic tubing228at a location prior to the carrier receiving bin210. The slide plate236may be used as a security measure, holding the carrier610above the carrier receiving bin210until the authorized receiving user scans their ID120. The sending user may be given the option by the handheld PDA700prior to sending the carrier610from the sending station224of requiring the receiving user to scan the receiving user ID120before retrieving the contents. If the sending user requires the receiving user to scan the receiving user ID120, the computer control center module206will engage the slide plate236and hold the carrier610in the tube228above the carrier receiving bin210until the receiving user scans the receiving user ID120. If the sending user does not require this security option, the carrier610will be allowed to move through slide plate236and into the carrier receiving bin210. The inline identifying tag readers or optical sensors220disposed throughout the pneumatic tube system may also be associated with the slide plate because they are configured to sense the passage of the carrier and its contents through the pneumatic tubing until it reaches the slide plate. The inline identifying readers or optical sensors220may verify to the computer control center module that the carrier has arrived at the slide plate at which point the computer control center module may determine if a receiving user ID needs to be scanned.

In another embodiment, after each transaction is complete, the delivery information stored and recorded by the system control module222may be made accessible to users via a web browser. However, in alternative embodiments, this information may be accessible via stand-alone applications, hard copy documents, or any other useful report format. The delivery information may be used to audit compliance with delivery procedures, required time constraints, or to track any missing or problem deliveries.

Referring now toFIG. 3, a flow chart illustrating a method300for tracking carriers and payloads in a pneumatic tube system200according to an embodiment of the present principles is shown. The sending user scans the delivery information in block302. The identifying tag reader108disposed at the sending station224sends the information to the computer control center module206in block304. The computer control center module206determines the physical destination of the carrier delivery in block306. The data regarding the carrier delivery is then stored in the database module202in block308. The computer control center module206sends commands to the elements of the pneumatic tube system200in block310to route the carrier and to engage or open the slide door236. Finally, the receiving user receives the carrier610delivery in block312and notification of the carrier delivery is sent to the sending user in block314.

Referring now toFIG. 4, a flowchart illustrating a method of preparing and sending carriers and payloads400from the sending station224according to an embodiment of the present principles is shown. The sending user receives a request for a delivery (i.e. a prescription, blood sample, file information, or the like) in block402. The sending user prepares the contents and requests a carrier610from the storage compartment218of the pneumatic tube system200via the handheld PDA700in block404. Upon receipt of the carrier610, the sending user may scan the carrier ID114, content ID110, the sending user's ID112, the sending station ID104, or the receiving station ID106using the identifying tag reader108in block406. The sending user may optionally require the receiving user to scan the receiving user ID120before the carrier610moves to the carrier receiving bin210in block408. If the sending user requires the receiving user to scan their ID120before the carrier610moves to the carrier receiving bin210, then the sending user has the option of being notified if the receiving user ID120is not scanned after the carrier610moves to the carrier receiving bin210and to the receiving station208. If the sending user chooses to be notified then they may select an alarm for notification from the handheld PDA700in block410.

The sending user also has the option of being notified, for example, when the carrier610arrives at the receiving station208, gets stuck in a tube228, or contents have been spilled. If the sending user chooses to be notified when the carrier arrives at the receiving station208, gets stuck in the tube228, or contents have been spilled, then he/she selects a notification. If not, then in one embodiment, the sending user places the carrier610on the conveyor belt.

The sending user may send the carrier by pressing the send button on the handheld PDA700. To send a carrier, the delivery information is sent to the system control module222in block412. In response, the system control module222controls the pneumatic tube system to move the carrier610. The carrier610leaves the sending station224and enters the pneumatic tube system200in block414.

Referring now toFIG. 5, a flowchart illustrating a method for receiving carriers and payloads500from the receiving station208according to an embodiment of the present principles is shown. The carrier610travels through the pneumatic tube system200in block502until the carrier610reaches the slide plate236, and is retained at, or passed though, the slide plate in response to commands from the system control module in block504.

If the sending user did not request that the receiving user scan their ID120before the carrier610reaches the carrier receiving bin210, then the slide door opens in block506, allowing the carrier610to move through to the carrier receiving bin210at the receiving station208. The system control module222then determines whether or not the receiving user ID120was scanned in block508.

If the receiving user ID120was scanned then the receiving user continues to scan the receiving station ID106and carrier ID122in block514. If the receiving user ID is not scanned then the system control module222determines if the sending user requested notification if the receiving user ID120is not scanned in block510. If the sending user requested notification than the system control module222sends an alarm notifying the sending user in block512. If the sending user did not request notification then the receiving user scans the receiving station ID106and carrier ID122in block514and selects the accept button on the handheld PDA700. The system control module222then verifies and stores the delivery information in block526and sends a confirmation message to the sending user in block528. The contents110of the carrier610are then delivered to the end user in block530.

If the sending user requests that the receiving user scan their ID120before the carrier610reaches the carrier receiving bin210, then the system control module222engages the slide plate236in block516, holding the carrier610in the pneumatic tubing228. The receiving user must then scan their ID120and the receiving station ID106in block518in order to disengage the slide plate236. After the receiving user ID120is scanned, the computer control center module206verifies the user ID before unlocking the slide plate236. After verification, the computer control center module206commands the slide plate236to disengage. The receiving user then selects the drop carrier button on the handheld PDA and the slide plate236disengages in block520, moving the carrier610through to the carrier receiving bin210and to the receiving station208in block522. The receiving user scans the carrier ID122in block524. The system control module222then verifies the delivery information in block526and if selected by the sending user, a confirmation message is sent to the sending user in block528. The delivery information is sent to be stored in the database module202and the contents are delivered to the end user by the receiving user in block530.

Referring now toFIG. 6A, a diagram of the carrier610with a unique identifying, optically scannable, tag (i.e. a bar code)620according to an embodiment600of the present principles is shown. The bar code620may be disposed on any part of the carrier610, enabling the inline identifying tag readers220to scan the bar code620and transmit the delivery information and reception information to the system control module222.

Referring now toFIG. 6B, a diagram of the carrier610with a unique identifying RFID tag640according to an embodiment630of the present principles is shown. The RFID tags640may be disposed on any part of the carrier610, enabling the inline identifying tag readers220to scan the RFID tags640and transmit the delivery information and reception information to the system control module222.

Referring now toFIGS. 7A and 7B, a handheld PDA700configured for use as an identifying tag reader and user interface according to an embodiment of the present principles is depicted. While the handheld PDA700is described as a useful embodiment of the present principles, it is only exemplary of an identifying tag reader that may be used. For example, a non-handheld PDA may be used, in addition to a touch key initialization module attached to a wall, etc.

The handheld PDA700is provided to capture and present data associated with sending and receiving pneumatic tube system deliveries. The PDA allows the user to perform operations required to send and receive a carrier delivery transaction without requiring an interface built into each station. The handheld PDA700may capture unique identifiers (bar codes, RFID tags, or the like) associated with individual carriers, sending stations, receiving stations, and sending and receiving users to help track the delivery information.

The database module202and computer control center module206may provide notification to a sending user's cell phone, PDA, e-mail, etc., regarding delivery details as well as providing notification to receiving users of incoming carriers based on options chosen from the handheld PDA700. The handheld PDA700may further provide options for secure sending, such as holding a carrier at a station slide plate236until the receiving user scans their ID.

The handheld PDA700provides real-time information to users. This information transmitted from the handheld PDA700and stored in the database module202may be password protected and accessible through a web browser or any other useful interface. Handheld PDA700is capable of collecting many types of information, including but not limited to the sending user's ID, the content's ID, the carrier's ID, the sending station's sent ID, the receiving station's ID, the time the transaction was requested, the time the carrier left the station, the travel time to carrier destination, the transaction number, whether or not it is a secure send, whether or not an alarm has been chosen, the alarm type if chosen, the time the carrier arrived at its destination, the receiving user's ID, the time the carrier was scanned upon arrival, and the receiving station ID. While the handheld PDA700has at least these capabilities, any combination of these capabilities may be used to track and record delivery information and reception information.

The steps of using the handheld PDA700from the sending user's station224can be described in reference toFIG. 7A. In one embodiment, in order to initialize a transaction, the sending user first selects the “Send” tab712on face710of handheld PDA700. The sending user then scans the sending station ID104. In one useful embodiment, the scan may be initiated by pressing the scan button706on either side of the PDA700while holding the PDA700up to the unique identifying tags (i.e. bar code, RFID, optical sensor, etc.) used for the sending station ID104. A check-mark at “Station”714may indicate that the sending station ID104has been properly scanned. The sending user may scan the receiving station ID106and the interface740may indicate that “Dest.”716or the receiving station ID106has been properly scanned. Next, the sending user may also scan the carrier ID114and the interface740may indicate, by showing a check-mark in the box next to “Carrier”718, that the carrier ID114has been properly scanned. The sending user may also scan the carrier contents110and the sending user ID112. The interface740may indicate, by a check-mark in the box next to “User”720, that the sending user ID112has been properly scanned.

The sending user then has the option of securely sending the carrier610by requiring the receiving user to scan the receiving user ID120before or after the carrier610drops into the carrier receiving bin210. If the sending user desires that the receiving user scan their ID120before the carrier610is delivered, then the sending user may select the “Before Drop”722button. A check-mark may appear in the box next to “Before Drop”722to indicate that this option has been selected. If the sending user desires that the receiving user scan their ID120after the carrier610drops, then the sending user chooses the “After Drop”724button and the interface740may indicate via a check-mark in the box next to “After Drop”724to show that this option has been selected.

If the sending user chooses “After Drop”724, the sending user also has the option of selecting “Alarm”726to be notified if the receiving user does not scan their receiving user ID120after the carrier610drops. A check-mark may appear in the box next to “Alarm”726to indicate that this option has been selected. Further, the sending user can choose to be notified when the carrier610“Arrives”728, “Flips”730, or “Alarms”732. A check-mark next to an appropriate label may indicate which options have been selected. The sending user may also send the carrier610by selecting the send button734to complete the transaction.

The steps of using the handheld PDA700from the receiving station208can be described in reference toFIG. 7B. In order to receive a carrier delivery the receiving user first selects the “Receive” tab738on the face710of handheld PDA700. Alternately, the system control module222may notify the receiving user that a carrier610has arrived. The receiving user may scan any ID, such as their user ID or the carrier ID, by pressing the scan button706on either side of the PDA700while holding the PDA700up to the unique identifying tags. A check-mark may, for example, appear in the interface740of the PDA700in the box next to “Station”704to show that the receiving station ID104has been properly scanned or the interface740may indicate by a check-mark in the box next to “User”702to show that the receiving user ID120has been properly scanned and “Carrier”708to show that the carrier ID122has been properly scanned. The receiving user may also select the “Drop Carrier”736button to manually release the carrier610into the carrier receiving bin210in the receiving station208.

The receiving user may initiate the recordation of a received carrier by selecting the “Receive” tab738. The receiving user may scan the receiving station ID106, the receiving user ID120or carrier ID122. The user interface on the PDA may show, via, for example, a check-mark next to the “Station”704, “User”702and “Carrier”708icons to indicate that the associated ID has been properly scanned. The receiving user may select the “Accept”742button on the user interface740to complete the transaction. The sending user may receive a confirmation message that the carrier610was delivered if that option was selected when the carrier610was sent. While in one useful embodiment a check mark may be used as an indicator of selections and properly scanned IDs, any other indicator may be used without deviating from the scope of the invention. For example, an “x” may indicate that an ID was properly scanned, an ID or selection may be highlighted to indicate that it was properly scanned, or any other interface may be used that is known in the art or as yet undiscovered.

While the interface for the PDA700is described herein as having a specific type of interface for reading specific types of IDs and permitting the user to interact with the tracking system, any interface permitting a user to interact with the tracking system may be advantageously disposed on the PDA700or on any other input element. Likewise, while the PDA700may actively read ID tags, such as bar codes or optical codes, the PDA700may also passively read RFID tags or other radio frequency identifiers, or may use any combination of passive and active ID detection. For example, a user may have an RFID badge that is passively read while the carrier may have an optical ID tag that is actively read. In another useful embodiment, the PDA700may be associated with a particular user, sending station, receiving station, or the like, the ID for which is stored in the PDA700or elsewhere in the tracking system for recall when a user sends a payload. In such an embodiment, the PDA700may automatically attribute the stored user ID, sending station ID, or receiving station ID to the outgoing payload.

Referring toFIG. 8, a diagram illustrating a pneumatic tube system800according to another embodiment of the present principles is shown. The pneumatic tube system800utilizes, in one non-limiting embodiment, a sending station824and a receiving station808, for sending and receiving pneumatic carriers, such as carrier810. Stations824and808connect to a pneumatic tube system800via transmission tubing828a-dand communications capability823. The system also includes blower814that blows air into pneumatic tubing828a-dto move the carrier810throughout the pneumatic tube system800. The system further includes one or more diverters816and826which direct the transportation of carriers810from sending station824to receiving station808at the direction of the system control module822. The configuration of the pneumatic tube system800shown inFIG. 8is only exemplary. The pneumatic tube system800of the present invention can comprise any number of sending and receiving stations and diverters as required. In a preferred embodiment, system800is utilized in a hospital setting for delivering prescription from a pharmacy to the patient. Accordingly, system800may utilize a single sending station824located at the pharmacy of the hospital and a plurality of receiving stations808each preferably located at each nursing station throughout the hospital. This enables system800to deliver prescriptions from the sending station824to any nursing station within the hospital equipped with a receiving station808. While the present principles are described with respect to a hospital, the present principles may also be used in, but are not limited to, banks, retail stores, pharmacies, laboratories, or the like.

System control module822controls the operation of pneumatic tube system800, reading, storing, and presenting data, and tracking the delivery of carriers in response to the collected data. System control module822may include database module802and computer control center module806in signal communication. The sending station824, diverters816and826, blower814, and receiving station808are all in signal communication with, and controlled by, the computer control center module806. The database module802may be, for example, a relational database, a flat file database, fixed length record database, or any other data storage mechanism known or as yet undiscovered in the art. Database module802may reside on a stand-alone server, or the same machine as the computer control center module806. The computer control center module806interprets the data in the database module802and generates commands in the form of signals to individual elements in the pneumatic tube system800to control the actions of the system800.

In a preferred embodiment, sending station824is located within a pharmacy to deliver prescriptions to hospital patients. Sending station824may contain touch screen827, which allows for user input and communication. Preferably, touch screen827has at least the same interface functionality of PDA700. Touch screen827allows a user to identify the destination for the carrier and input any other instructions for the handling of the carrier. Instructions may include options such as “Before Drop”, “After Drop”, “Arrives”, “Flips” or “Alarms” options, and the user may request notification if the carrier gets stuck in a tube or the contents have spilled. In an alternative embodiment, the functions of touch screen827may be accomplished using manual buttons, switches or other controls, in which event a screen without touch capability may be used.

Station824also contains a card reader804. Card reader804may read and store information from a unique ID card associated with the carrier contents or payload, the sending user's ID card, the receiving user's ID card, or a unique ID card associated with the carrier itself. The card reader804may also read and store information from a unique ID card associated with the sending station and/or delivery station. Preferably, card reader804is designed to read cards swiped through the card reader804. In alternative embodiments, card reader804may read the ID card of objects using an optical scanning system to read bar codes, characters or other objects. The card reader804may identify objects using RFID or other radio frequency technology, and may actively or passively read cards. Additionally, any other identification technology known, or as yet undiscovered, may be used within the scope of the present principles.

Station824also contains a tag reader815. Tag reader815may read and store a unique ID tag801associated with the carrier ID disposed on pneumatic carrier810, or unique ID tags associated with the carrier contents or payload, the sending user's ID, or the receiving user's ID. The tag reader815may also read and store a unique ID tag associated with the sending station, the receiving station, and/or the receiving bin of the receiving station (as will be later described). Preferably, tag reader815is designed to read the ID tag of objects using an optical scanning system to read bar codes, characters or other objects. The tag reader815may identify objects using RFID or other radio frequency technology, and may actively or passively scan IDs. Additionally, any other identification technology known, or as yet undiscovered, may be used within the scope of the present principles.

Preferably, card reader804and tag reader815are affixed to station824. Alternatively, card reader804and/or tag reader815may be embodied in a handheld device in signal communication with station824. Handheld device may comprise a portable or mobile communication device, a cellular phone, a smart phone, a tablet computer, a mini tablet computer, and any handheld device known in the art.

Sending station824further contains a carrier receiving bin812for receiving a pneumatic carrier810. Station824is in signal communication with the system control module822, and information is communicated between station824and system control module822.

In an alternative embodiment, sending station824may be located within a fully automated pharmacy, as described in U.S. Pat. No. 6,202,004, the entire contents of which is hereby being incorporated by reference. The product prepared by the automated pharmacy may be delivered to the sending station824via a conveyor belt. Sending station824automatically scans the ID tag on the product using tag reader815and transmits this information to the system control module822to determine the appropriate station to send the product based upon information associated with the product ID. At the sending station824, the product is automatically loaded into a carrier810, inserted into the receiving bin812of the sending station824, and routed to the correct location.

Sending station824may also be connected via network to other information systems. In a hospital environment, station824can be linked to other hospital systems such as pharmacy management, laboratory management and security management systems. Such communication may be made by wired or wireless connection, packet-switched network, or other communications system. In this regard, information from the pneumatic tube system may be integrated into a larger hospital system, and information from the hospital system may be used by station824and other elements of the system.

Lights or speakers may be included in, or connected to, station824. These may be used to notify users that a carrier has been received, that an error has occurred, that maintenance is required, or for any other suitable purpose.

In a preferred embodiment, each nursing station at a hospital includes a receiving station808for receiving patient prescriptions. Like sending station824, receiving station808may comprise a touch screen829, a card reader832, and one or more tag reader833. Each receiving station808preferably comprises a plurality of receiving bins811, each for receiving a pneumatic carrier810. Receiving station808is shown to contain six receiving bins811, however, any number of receiving bins may be included in the receiving station808without departing from the scope of the present invention. Preferably, the number of receiving bins811is associated with the number of patient rooms handled by the nursing station. So if there are six patient rooms, the receiving station808will comprise six receiving bins811. In another embodiment, the number of receiving bins811is associated with the number of patient beds handled by the nursing station.

Each receiving bin811may comprise a tag reader818for detecting the presence of a carrier810in the carrier receiving bin811. Tag reader818detects the presence of the carrier810by scanning the ID tag801of the carrier. Tag reader818sends a signal to the station808and/or system control module822indicating that the carrier810has arrived at the receiving bin811. Alternatively or in addition, each receiving bin811contains a presence sensor, such as a pressure sensor, to detect presence of the carrier and activate tag reader818. Each receiving bin811may further comprise a visual indicator819on the exterior of the receiving bin811to visually display that a carrier has arrived at the receiving bin811. The visual indicator819may be activated upon the detection by the tag reader818and/or a presence sensor of the presence of the carrier810. Visual indicator819may comprise a light, a colored light (e.g., a green light), a flashing light, or the like.

In a preferred embodiment, each receiving bin811comprises a door813for preventing access to the receiving bin811by unauthorized users. The door813may be a hinged door, a sliding door, a bi-fold door, a telescoping door, or any other door known in the art. The door comprises a lock which is controlled by the receiving station808and/or the system control module822. Any lock known in the art may be used, such as a turn lock, an electromagnetic lock, or the like. The door813may be unlocked by an authorized user in a number of ways. The user may use the touch screen829to enter user identifying information and identify the bin811of the plurality of bins the user wishes to unlock. The user may swipe a user ID card using card reader832and select the bin811the user wishes to unlock using the touch screen829. The user may utilize a mobile communication device834preloaded with an application to select the bin811the user wishes to unlock as well as to enter user identifying information. Each door may comprise an ID tag817in a form of a barcode, a RFID tag, or the like, which the user may scan with the mobile communication device834. In an alternative embodiment, each door813may be equipped with a scanning device or a sensor817. A user may carry an ID tag preloaded with user information that may be scanned by the door scanning device or a sensor817to unlock the particular door813. Regardless of the means used to unlock the door, the selected bin information and the user identification information is sent via the receiving station808or the mobile communication device834to the system control module822which determines whether the user is authorized to unlock the particular bin811. System control module822may store a list or a log of authorized users allowed to unlock a particular bin such that only designated users may be allowed to unlock certain bins. For example, a head nurse in charge of the nursing station may have access to any one of the bins811of the receiving station808. However, a nurse or a doctor that only attends a patient associated with only one of the bins will have access to that one particular bin, but not the other bins of the receiving station808. The system control module822receives the selected bin information and the user identification information and determines whether the user is authorized to unlock the particular bin811. If so, the system control module instructs the receiving station808to unlock the particular bin811. The system control module822may log in database802that a particular user has unlocked the particular bin to retrieve the delivered carrier810for chain of custody purposes.

Receiving station808may further contain a separate carrier receiving bin830for dispatching empty pneumatic carriers810back to the sending station824via pneumatic tubing828band828dand diverter826. When the system is free from delivering carriers from sending station824, it may return empty carriers810from separate carrier receiving bin830to the sending station824. In addition, separate carrier receiving bin830may be used to send carriers810from the receiving station808to other stations of the pneumatic tube system800via pneumatic tubing828band additional tubing and diverters. In another embodiment, a separate zone, with a separate blower, diverter(s), and pneumatic tubing may be used to return empty carriers from receiving station808to a separate receiving bin at the sending station824, thus not disturbing the flow of carriers from the sending station824to any receiving station808and any receiving bin811of the receiving station808.

Pneumatic tube system800preferably comprises diverter816in direct communication with the receiving station808for directing the pneumatic carriers810to an appropriate receiving bin811. Diverter816preferably comprises a single inlet port in communication with the sending station824via one or more tubing828aand828dand one or more diverters826for receiving a pneumatic carrier810. Diverter816further comprises a plurality of outlet ports each in communication with a selected receiving bin811via tubing828cfor delivery of a carrier810to a particular receiving bin811. Diverter816may be any diverter known in the art. It is in communication with and controlled by the system control module822for routing of the carrier to the appropriate outlet port.

Furthermore, pneumatic tube system800may include a plurality of inline identifying tag readers or optical sensors820configured to track or sense the carriers as they are transported through the tubing828a-d. The inline identifying tag readers or optical sensors820may be implemented for example, through a window or a section of the tubing828a-d, through an RFID antenna disposed on a recess section of the tubing828a-d, through an optical sensor disposed in the tubing828a-d, or the like. The inline identifying tag readers or optical sensors820read, or otherwise sense, the passage of a carrier associated with the payload being transported through the pneumatic tube system. The ID tags may be used to record the location and ID114and122of a carrier810at various locations throughout the pneumatic tube system800to send to the system control module822. The system control module822receives carrier information from the tag readers at the sending and receiving stations as well as from inline identifying tag readers or optical sensors820and logs the carrier information into a database module802in order to keep a log of each carrier's location information as they move through the pneumatic tubing828. This creates an auditable trail indicating a chain of custody. As described above, the carrier information from the various tag readers enable the system control module822to manage deliveries, determine how the carrier should be delivered (i.e. secured, with alarms, etc.), track carriers810as they move past inline identifying tag readers or sensors820in the pneumatic tubing828a-d, generate records to show that a carrier810passed an inline identifying tag reader or sensor820at a certain time, and generate reports on chain of custody.

Advantageously, the pneumatic tube system800of the present invention allows for a series of carriers810to be sent simultaneously in series from the sending station824to the receiving station808(or a plurality of receiving stations808). Upon approach to the diverter816, the carrier ID tag801of a first carrier810in series may be scanned at the inlet port of the diverter816by an inline tag reader820. The carrier ID information may be sent to the system control module822, which may direct the diverter816to dispatch the carrier810to the appropriate receiving bin811. Then the second carrier810in series would be scanned at the inlet port of the diverter816by the inlet tag reader820and be dispatched to an appropriate receiving bin811in the same manner, and so forth.

The pneumatic tube system800of the present invention effectively allows a drug to be delivered directly from the pharmacy to the patient. The architecture of the pneumatic tube system800allows for the creation of a complete chain of custody of a drug or any other payload from the pharmacy to the patient. It also enables the isolation of drugs between patients reducing errors of administering drugs to the wrong patient and improving patient security. Using the pneumatic tube system800, the patient may be billed directly for the prescribed drug. To effectively and securely deliver content in pneumatic tube system800, database802of the pneumatic tube system800may store files associated with each patient, and preferably with the patient's unique ID accorded to the patient during admission to the hospital. Each file may include, for example:

2. Name of the patient;

3. Room number of the patient;

4. Bed number of the patient;

5. Receiving station ID associated with the patient;

6. Receiving bin ID associated with the patient;

7. Name, strength, and diluent of drug to be delivered to the patient; and

8. IDs of authorized users allowed access to the receiving bin associated with the patient.

Database802may store additional information or less of the above listed information without departing from the scope of the present invention. The system control module822uses the above information to properly route drugs from the sending station to the receiving bin associated with the patient. During delivery the system control module822will also keep a log of chain of custody of the drug based on the information collected before, during, and after transportation.

As discussed above, the present invention may be scaled to any desired size.FIG. 9illustrates an exemplary embodiment of the pneumatic tube system900of present invention in a hospital. As shown, the hospital may include a sending station906within a pharmacy904in a separate building connected via pneumatic tubing908to a plurality of nursing stations901,902, and903within the hospital. Each nursing station901,902, and903may be located in a wing in charge of a plurality of rooms. For example, nursing station901may be in charge of six rooms911a-911f, nursing station902may be in charge of six rooms912a-912f, and nursing station903may be in charge of four rooms913a-913d. Each nursing station901,902,903will include a receiving station921,922,923, respectfully, comprising a plurality of receiving bins corresponding to the number of rooms in the wing of the nursing station. As such, nursing station901comprises receiving station921comprising six bins connected to a six port diverter931, nursing station902comprises receiving station922comprising six bins connected to a six port diverter932, and nursing station903comprises receiving station923comprising four bins connected to a four port diverter933. Diverters931,932, and933are connected to sending station906via diverter905. Each bin corresponds to the respective room associated with the nursing station, such that drugs for a particular patient are delivered to the bin associated with the room occupied by the patient.

Referring now toFIG. 10(as well asFIG. 8), a flowchart illustrating a method of sending carriers and payloads810from the sending station824to the receiving station808according to an embodiment of the present principles is shown. Initially, when a patient is admitted to the hospital, the hospital assigns the patient a patient ID and a receiving bin. Specifically, the hospital creates an electronic file of the patient that is stored in database802in step1001. The file may include the patient ID, name of the patient, room number of the patient, bed number of the patient, receiving station ID associated with the patient, receiving bin ID associated with the patient, and IDs of authorized users allowed access to the receiving bin associated with the patient. The information may be dynamic and updated by the hospital staff as required. For example, the IDs of authorized users allowed access to the receiving bin may change from time to time depending on the changes of shifts of hospital personnel. Next, in step1002, the doctor prescribes a drug, for example penicillin, to the patient and the patient file is updated with the drug information, for example, with the name, strength, and diluent of drug to be delivered to the patient. The prescription is sent to the pharmacy to be filled out. For example, the prescription may be electronically sent to the pharmacy via receiving station808by entering information through touch screen829or via a mobile communication device834. Other system may also be utilized without departing from the scope of the present invention.

After the pharmacy fills out the prescription, the drug container is labeled in step1003with a unique ID tag which upon scanning retrieves the patient file. The drug container is then delivered to the sending station824. To send a carrier from sending station824, a user prepares contents of the carrier810for shipment. In step1004, the sending user scans the delivery information, specifically the sending user ID, the ID tag801of the carrier810, and the unique ID tag of the filled out prescription using tag reader815. The sending user then inserts the filled out prescription into the carrier810and deposits the carrier810into the receiving bin812of the sending station224. Tag reader815disposed at the sending station824sends the scanned information to the system control module822in step1005. Using the unique ID tag of the filled out prescription, the system control module822accesses the patient file stored in database802and determines the physical destination of the carrier delivery in step1006. Specifically, the system control module822retrieves the receiving bin ID associated with the patient. Relevant data received from the sending station824is logged in the database802in step1007. This data may include the time the carrier was sent, the ID of the sending station824, the sending user ID, and the ID tag801of the carrier.

The system control module822sends commands to the components of the pneumatic tube system800in step1008to route the carrier from the sending station824to a particular receiving bin811associated with the patient at the receiving station808. As the carrier is transported within the pneumatic tube system800, inline tag readers820scan the ID tag801of the carrier810and transmit that information to the system control module822to be logged as tracking information in database802in step1009.

When the carrier arrives at the destined bin811of the receiving station808in step1010, the carrier ID810is automatically scanned at the receiving station808to verify delivery, and the visual indicator819may light up to notify that a carrier has been received in step1011. In addition, a notification may be send to a mobile communication device834of the receiving user that the prescription has been filled out and received by the receiving station808. The receiving user may be a head nurse of the nursing station, or a doctor or nurse attending the patient. In step1012, the receiving user unlocks the bin811associated with the patient at the receiving station808by transmitting selected bin information and the user identification information to the system control module822. The receiving user may do so by scanning an ID tag817associated with the receiving bin with a mobile communication device834and entering the user identification information into the mobile communication device834. The mobile communication device834transmits the information to the system control module822, which looks up the patient file to determine whether the receiving user is authorized to access the receiving bin. If so, the system control module822sends a command to the receiving station808to unlock the receiving bin811associated with the patient. In step1013, the system logs relevant reception data, including, for example, the carrier ID, the receiving station ID, the receiving bin ID, the time the carrier arrived at the receiving bin811, the time the receiving bin has been unlocked, and the receiving user identification information. The contents of the carrier810are then delivered to the patient in step1014. In that step, the mobile communication device834may be used to scan an ID tag on the patient's wristband or other ID tag located in the proximity of the patient, as well as the ID tag of the prescription to create a log that the prescription has been delivered to the patient. The patient may then receive an invoice directly for the filled prescription without hospital involvement.

It will be appreciated that although the above pneumatic tube carrier tracking system description is described as used in a hospital, the present principles are not limited to such use. For instance, the principles could be used in any other businesses or enterprises where customized product deliver is desired. While the foregoing embodiments of the principles have been set forth in considerable detail for the purposes of making a complete disclosure of the principles, it will be apparent to those of skill in the art that numerous changes may be made to such features without departing from the spirit and the scope of the present principles.