IP Library Granted Patent US 11,587,017
Granted Patent B2
US 11,587,017 · App. 16/785,024 · Granted Feb 21, 2023

Disaggregation events and decommissioning events

Inventors: David Bolene (Austin, TX); Eric Bolinger (Broomfield, CO); Margot Drees (Boulder, CO); Janine Fornarola (Arvada, CO)
Assignee: GLOBAL HEALTHCARE EXCHANGE, LLC
G06Q10/0833G06K7/1413G06Q10/0832G16H40/20G06Q10/0637G06Q10/06315
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,587,017
App. No.
16/785,024
Granted
Feb 21, 2023
Kind
B2
Abstract

Systems and methods are directed to supply chain management. In particular, the tracking, tracing, authenticating, and reporting of supply chain events for products, is disclosed. Various embodiments can store, analyze, and track supply chain events and help to coordinate and maintain trading partner connections. Various embodiments also help to enhance patient safety, secure the supply chains for pharmaceuticals, medical devices, and other healthcare products, and help users to follow regulatory requirements.

Claims (53)

1. A method comprising:

receiving, by a processor, a disaggregation event in a supply chain,

wherein the disaggregation event includes removing items from a container, and

wherein the disaggregation event includes a parent identifier and a child identifier;

associating, by the processor, the disaggregation event with the parent identifier;

associating, by the processor, the disaggregation event with the child identifier;

storing, by the processor, the parent identifier and the child identifier in a database as ungrouped data elements formatted as a block of binary (BLOB);

tuning, by the processor, the database to optimize database performance;

obtaining, by the processor, the parent identifier and the child identifier from the database for the disaggregation event;

determining, by the processor and in a recursive manner, additional identifiers from parent and child containment relationships;

associating, by the processor, the disaggregation event with the additional identifiers;

setting, by the processor, a state of the parent identifier to a condition reflecting error, in response to the disaggregation event existing for a container associated with the parent identifier and the disaggregation event existing earlier than an aggregation event in an event sequence for the parent identifier;

setting, by the processor, a state of the child identifier to indicate a missing commissioning event, in response to the child identifier being an item and an event sequence of the child identifier beginning with the disaggregation event;

setting, by the processor, the state of the child identifier to the condition reflecting error, in response to a decommissioning event existing earlier than the disaggregation event in the event sequence of the child identifier;

setting, by the processor, the state of the child identifier to the condition reflecting error, in response to the child identifier being the container, the container being not reusable, the child identifier appears as a parent identifier earlier than the disaggregation event in the event sequence of the child identifier, and no aggregation event exists earlier than the disaggregation event in the event sequence of the child identifier.

2. The method of claim 1 , further comprising initiating, by the processor, the event sequence for the parent identifier, in response to the event sequence not previously existing for the parent identifier.

3. The method of claim 1 , further comprising setting, by the processor, the state of the child identifier to the condition reflecting error, in response to at least one of:

the child identifier is a child in an earlier aggregation event and more than one aggregation event or no aggregation event exists earlier than the disaggregation event in the event sequence of the child identifier;

the child identifier is an item and more than one commissioning event or no commissioning event exists earlier than the disaggregation event in the event sequence of the child identifier; or

the child identifier is the container, the container is not reusable, and more than one commissioning event earlier than the disaggregation event in the event sequence of the child identifier.

4. The method of claim 1 , wherein the decommissioning event includes at least one of a state or change of the state associated with the item.

5. The method of claim 1 , wherein the decommissioning event includes identifying at least one of the item that is sellable, a container associated with the item or disaggregation hierarchies for the item.

6. The method of claim 1 , further comprising receiving the decommissioning event issued in response to at least one of destruction of an unconsumed item, an expired item, a damaged item, a recalled item, an item being dispensed, an item being consumed or an item being discarded.

7. The method of claim 1 , further comprising:

determining, by the processor, whether the decommissioning event exists in the event for the item; and

generating, by the processor, an error status for the item, in response to the determination that no decommissioning event exists in the event for the item.

8. The method of claim 1 , further comprising:

determining, by the processor, whether a plurality of decommissioning events exist in the event for the item; and

generating, by the processor, a suspect status for the item, in response to the determination that the plurality of decommissioning events exists in the events for the item.

9. The method of claim 1 , further comprising:

determining, by the processor, whether a receiving event exists in the event for the item;

determining, by the processor, whether an associated shipping event exists for the receiving event; and

generating, by the processor, an error status for the item, in response to the determination that there is not the associated shipping event for the receiving event.

10. The method of claim 1 , further comprising:

determining, by the processor, whether any shipping events exist in the event for the item;

determining, by the processor, whether an associated receiving event exists for each of the shipping events; and

generating, by the processor, an error status for the item, in response to the determination that there is not an associated receiving event for at least one of the shipping events.

11. The method of claim 1 , further comprising:

identifying, by the processor, one or more contiguous chains of events within the event sequence;

matching, by the processor, one or more pairs of events;

forming, by the processor, one or more trees of links from the matched pairs of events; and

identifying, by the processor, each tree as one of the contiguous chains of events.

12. The method of claim 1 , further comprising adding, by the processor and in response to a condition reflecting error, a subset of the items associated with the parent identifier to be commissioned at least one of on the production line, as a shipment is being packed, or by a wholesaler.

13. The method of claim 1 , further comprising creating, by the processor, at least one of a new link for related events or an unlinked event by utilizing a rules engine.

14. The method of claim 1 , further comprising removing, by the processor and in response to the condition reflecting error, a subset of the items associated with the parent identifier.

15. The method of claim 1 , further comprising:

receiving, by the processor, a set of custom rules from an entity in the supply chain; and

assessing, by the processor, the receiving event by utilizing the set of custom rules.

16. The method of claim 1 , further comprising:

reading, by the processor, a plurality of stored parameters from an entity in the supply chain;

creating, by the processor, a set of custom rules for the entity; and

assessing, by the processor, the receiving event by utilizing the set of custom rules.

17. The method of claim 1 , further comprising reporting, by the processor and in accordance with a rule, a new commissioning event as suspect, in response to the item having a commissioning event, and no previous decommissioning associated with the item.

Assignments (6)
RELEASE OF SECURITY INTEREST IN PATENT RIGHTS AT RF 056360/0746 Recorded Dec 30, 2024
From: ARES CAPITAL CORPORATION, AS AGENT
To: GLOBAL HEALTHCARE EXCHANGE, LLC
Reel/Frame 069799/0438 →
RELEASE OF SECURITY INTEREST REEL/FRAME (056360/0726) Recorded Dec 30, 2024
From: JPMORGAN CHASE BANK, N.A.
To: GLOBAL HEALTHCARE EXCHANGE, LLC
Reel/Frame 069810/0793 →
SECURITY INTEREST Recorded Dec 27, 2024
From: GLOBAL HEALTHCARE EXCHANGE, LLC, AS GRANTOR
To: ARES CAPITAL CORPORATION, AS AGENT
Reel/Frame 069690/0297 →
SECURITY INTEREST Recorded May 26, 2021
From: GLOBAL HEALTHCARE EXCHANGE, LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 056360/0726 →
SECURITY INTEREST Recorded May 26, 2021
From: GLOBAL HEALTHCARE EXCHANGE, LLC
To: ARES CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 056360/0746 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 7, 2020
From: BOLENE, DAVID; BOLINGER, ERIC; DREES, MARGOT; FORNAROLA, JANINE
To: GLOBAL HEALTHCARE EXCHANGE, LLC
Reel/Frame 051754/0504 →
Continuity (6)
Continuation 16778348 · Jan 31, 2020
Continuation 15461294 · Mar 16, 2017
Continuation 13804955 · Mar 14, 2013
Continuation 13804572 · Mar 14, 2013
Provisional Application 61725350 · Nov 12, 2012
Related Publication 20200175469A1 · Jun 4, 2020