# US 2024/0383694 A1 · Routing of totes and bottles within a pharmacy conveyor system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0383694 A1
- Document ID: US20240383694A1
- Status: Published application
- Kind: A1
- Application number: 18/787,331
- Filed: 2024-07-29
- Published: 2024-11-21
- Earliest claimed: 2021-03-23
- Assignees: Innovation Associates, Inc.
- Applicants: Innovation Associates, Inc.
- Inventors: Fletcher A. Chapin, JR.; Todd Bower
- Web page: https://patentgrep.com/patent/US20240383694A1

## CPC

- B65G 43/08: Control devices operated by article or material being fed, conveyed or discharged {(and controlling the discharging devices B65G47/42)}
- B65G 47/50: according to destination signals stored in separate systems
- B65G 43/10: Sequence control of conveyors operating in combination
- B65G 47/48: according to bodily destination marks on either articles or load-carriers
- B65G 47/53: between conveyors which cross one another
- B65G 47/82: Rotary or reciprocating members for direct action on articles or materials, e.g. pushers, rakes, shovels {(means for pushing glass articles onto a conveyor C03B9/453)}
- G06Q 10/083: Shipping
- G16H 20/10: relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/67: for remote operation
- B65G 47/503: {the system comprising endless moving means}
- B65G 2201/0244: Bottles
- B65G 2201/0258: Trays, totes or bins
- B65G 2201/027: Tablets, capsules, pills or the like
- B65G 2203/0216: Codes or marks on the article
- B65G: TRANSPORT OR STORAGE DEVICES, e.g. CONVEYORS FOR LOADING OR TIPPING, SHOP CONVEYOR SYSTEMS OR PNEUMATIC TUBE CONVEYORS (packaging B65B; handling thin or filamentary materials, e.g. paper sheets or thread, B65H; cranes B66C; portable mobile or lifting or hauling appliances, e.g. hoists, B66D; devices for lifting or lowering goods for loading or unloading purposes, e.g. fork-lift trucks, B66F9/00; emptying bottles, jars, casks, barrels or similar containers, not otherwise provided for, B67C9/00; delivering or transferring liquids B67D; filling or discharging vessels for liquefied, solidified or compressed gases F17C; pipe-line systems for fluids F17D)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A system, method, and apparatus for the routing of totes and bottles within a pharmacy fulfillment center are disclosed. The system, method, and apparatus are configured to transmit routing tables from an application server to station controllers (e.g., PLCs) to enable each station to locally make a routing decision. Since the routing logic is locally stored at each station, the controllers do not need to transmit request messages to the server every time a tote or bottle is scanned. The system, method, and apparatus increase conveyor throughput by enabling each station to make a routing decision without having to wait for a response from a server.

## Claims

### Claim 1

A pharmacy conveyor system comprising:
a memory device configured to store a data structure of at least one bottle lookup table, each bottle lookup table including a bottle identifier and an assigned destination of the bottle;
a pharmacy conveyor belt including a plurality of stations, the conveyor belt for each station including:
a reader configured to read a barcode on a bottle,
a router configured to divert the bottle from the conveyor belt to a medication fulfillment area, and
a controller configured to receive at least one of the bottle lookup tables and determine whether the router is to be activated based on the read barcode matching a bottle identifier in the received at least one bottle lookup table; and
an application server communicatively coupled to the memory device, the application server configured to:
receive a prescription for filling through a pharmacy workflow,
assign the prescription to a bottle,
determine routing information for the bottle,
create a bottle element within one of the bottle lookup tables in the memory device using an assigned bottle identifier,
determine a route code with a destination identifier specified in the respective routing information, and
transmit the bottle lookup table with the bottle element to at least one controller before the bottle is received on the conveyor belt.

### Claim 2 (depends on 1)

The system of claim 1, wherein the application server includes an interface to the controllers of each station for transmitting at least one of the bottle lookup tables.

### Claim 3 (depends on 1)

The system of claim 1, wherein the controllers of each station include an interface to the application server for receiving at least one of the bottle lookup tables.

### Claim 4 (depends on 1)

The system of claim 1, wherein the application server is configured to transmit the bottle lookup table with the bottle element to the controllers of the stations for which the bottle is to be diverted before the bottle has arrived at the respective station.

### Claim 5 (depends on 1)

The system of claim 1, wherein the plurality of stations is associated with manual fill areas, auto-fill areas, semi-auto-pack areas, manual pack areas, auto-pack areas, and at least one collator.

### Claim 6 (depends on 1)

The system of claim 1, wherein the bottle lookup table with the bottle element includes a seal flag to indicate whether the bottle should be sealed.

### Claim 7 (depends on 1)

The system of claim 1, wherein the controllers include programmable logic controllers (“PLCs”).

### Claim 8 (depends on 1)

The system of claim 1, wherein the controller for each station is further configured to:
receive at least one of the bottle lookup tables;
store the at least one of the bottle lookup tables to a local memory;
receive from the reader of the same station, information that is indicative of a bottle identifier;
identify the bottle identifier respectively within the at least one of the bottle lookup tables;
determine if the specified destination identifier corresponds to an identifier of the controller; and
cause the router to divert the bottle from the conveyor belt when the specified destination identifier corresponds to the identifier of the controller.

### Claim 9 (depends on 8)

The system of claim 8, wherein the controller for each station is configured to:
determine the bottle identifier is not located in the at least one of the bottle lookup tables;
cause the bottle to pass through; and
transmit an alert to the application controller indicative of the bottle identifier not being located in the at least one of the bottle lookup tables.

### Claim 10 (depends on 1)

The system of claim 1, wherein the bottle includes a one-dimensional barcode or a two-dimensional barcode including the identifier of the bottle that is printed on a label, the one-dimensional barcode or the two-dimensional barcode being readable by the readers of the stations.

### Claim 11

A pharmacy conveyor system comprising:
a memory device configured to store a data structure of at least one tote lookup table, each tote lookup table including a tag name corresponding to a respective tote identifier of a tote and a route code indicative of a current location or an assigned destination of the corresponding tote;
a pharmacy conveyor belt including a plurality of stations, the conveyor belt for each station including:
a reader configured to read a barcode on a tote,
a pusher configured push the tote from the conveyor belt to a medication fulfillment area, and
a controller configured to receive at least one of the tote lookup tables and determine whether the pusher is to be activated based on the read barcode matching a tote identifier in the received at least one tote lookup table; and
an application server communicatively coupled to the memory device, the application server configured to:
receive a prescription for filling through a pharmacy workflow,
assign the prescription to a tote,
determine routing information for the tote,
select a tote element in one of the tote lookup tables in the memory device,
update the route code with a destination identifier specified in the respective routing information, and
transmit the tote lookup table with the tote element to at least one controller before the tote is received on the conveyor belt.

### Claim 12 (depends on 11)

The system of claim 11, wherein the tote includes a radio frequency (“RF”) tag placed on a bottom of the tote, the RF tag including the tote identifier and being readable by the readers of the stations.

### Claim 13 (depends on 11)

The system of claim 11, wherein the application server includes an interface to the controllers of each station for transmitting at least one of the tote lookup tables.

### Claim 14 (depends on 11)

The system of claim 11, wherein the controllers of each station include an interface to the application server for receiving at least one of the tote lookup tables.

### Claim 15 (depends on 11)

The system of claim 11, wherein the application server is configured to transmit the tote lookup tables to the controllers of the stations for which the tote is to be pushed before the tote has arrived at the respective station.

### Claim 16 (depends on 11)

The system of claim 11, wherein the plurality of stations is associated with manual fill areas, auto-fill areas, semi-auto-pack areas, manual pack areas, auto-pack areas, and at least one collator.

### Claim 17 (depends on 11)

The system of claim 11, wherein the controllers include programmable logic controllers (“PLCs”).

### Claim 18 (depends on 11)

The system of claim 11, wherein the application server is further configured to:
receive a message from one of the controllers that the tote has passed through;
update the tote routing table associated with the tote with a next destination identifier of the routing information; and
transmit the updated tote routing table to the controller that corresponds to the next destination.

### Claim 19 (depends on 11)

The system of claim 11, wherein the controller for each station is further configured to:
receive at least one of the tote lookup tables;
store the at least one of the tote lookup tables to a local memory;
receive from the reader of the same station, information that is indicative of a tote identifier;
identify the tote identifier respectively within the at least one of the tote lookup tables;
determine if the specified destination identifier corresponds to an identifier of the controller; and
cause the pusher to push the tote off the conveyor belt when the specified destination identifier corresponds to the identifier of the controller.

### Claim 20 (depends on 19)

The system of claim 19, wherein the controller for each station is further configured to:
determine the tote identifier is not located in the at least one of the tote lookup tables;
cause the tote to pass through; and
transmit an alert to the application controller indicative of the tote identifier not being located in the at least one of the tote lookup tables.
