Abstract: The innovations herein concern flexible and omnichannel unified jackpot awarding systems. In particular, a hosted gaming service may provide a unified jackpot awarding system that is compatible and combinable with a variety of different gaming ecosystems, such as land-based gaming environments and online or “iGaming” environments. Specifically, the unified jackpot system may include a gaming device identifier (GID), a contributor identifier (CID), and/or a contributor type property to aid in the identifying and tracking of jackpots awarded, e.g., to multiple players playing on multiple devices and in multiple games across land-based and/or online gaming environments. Each player and device may be linked with their own gameplay session (e.g., via the use of QR codes, digital wallets, biometric information, or the like).

Abstract: The innovations herein concern flexible and omnichannel progressive jackpot systems. In particular, a hosted gaming service may provide a flexible progressive jackpot system and Application Programming Interface (API) that is compatible and combinable with a variety of different gaming ecosystems, such as land-based gaming environments and online or “iGaming” environments. Specifically, the flexible progressive jackpot API may include a progressive jackpot identifier (PID), a contributor identifier (CID), and/or a contributor type property to aid in the identifying and tracking of contributions made to multiple progressive jackpots, e.g., by multiple players and devices in multiple games across land-based and/or online gaming environments. Each progressive jackpot may be associated with its own properties, such as incremental rate, jackpot reset values, and auto-approve limits.

Abstract: A listening device is operatively connected to a plurality of EGMs, and is configured to subscribe to one or more EGM data types. The listening device receives, over a first network, data from at least one of the plurality of EGMs in accordance with the subscription, wherein the listening device is configured to receive data comporting to a plurality of data protocols. The listening device also generates a data package comprising a data structure having a static portion and a dynamic portion, wherein the static portion comprises the configuration information corresponding to the at least one of the plurality of EGMs, and wherein the dynamic portion comprises the received data, and transmits the data package across a second network to a collection server.

Abstract: An application program interface (API) provides functionality to store device data from multiple protocols. A collection server hosting the API is configured to receive a data structure from a first sending device comprising first sending device data, wherein the data structure comprises a static portion and a dynamic portion, wherein the static portion comprises identifying information for the sending device, and where in the dynamic portion comprises the device data; and store the device data in accordance with the data structure.

Abstract: A listening device is operatively connected to multiple network devices, and is configured to subscribe to one or more EGM data types, and receive first data from a first network device in accordance with the subscription. The listening device is also configured to generate a first data package in a form of a first data structure comprising the first data and configuration information related to the first network device, and transmit the data package across a second network to a collection server. The listening device is also configured to receive second data from a second network device in accordance with the subscription, wherein the second data comports with a second protocol that differs from the SAS protocol, and generate a second data package in the form of the first data structure comprising the second data and configuration information related to the second network device.

Abstract: The Episode Builder according to exemplary embodiments of the present invention is a web-based computer application and its associated architecture that allows health care professionals to define and describe episodes of care. The Episode Builder provides a unique tool for these purposes. Using industry-standard code sets, the Episode Builder describes and defines an episode of care so that the health care professional can create and modify episodes for a variety of purposes. The three main components of the Episode Builder are a configurable and extensive code set management system, a suite of display panels that define the episodes themselves based upon the code sets, and a means to export the episode definition tables thus created to be used as inputs into an analytic program or a claims adjudication engine.