WO2014062797A1

WO2014062797A1 - Methods for configuring biometric devices for transmitting health information

Info

Publication number: WO2014062797A1
Application number: PCT/US2013/065231
Authority: WO
Inventors: Toufic V. BACHOUR
Original assignee: Numera
Priority date: 2012-10-16
Filing date: 2013-10-16
Publication date: 2014-04-24

Abstract

Methods, systems, and computer implemented programs to configure biometric and connectivity devices for transmitting health information are disclosed. They are designed to provide flexibility in specifying and ordering HMD's, Hubs, and adaptors tailored to a consumer's needs, even when the number of possible combinations among these parts is extremely high.

Description

METHODS FOR CONFIGURING BIOMETRIC DEVICES FOR TRANSMITTING HEALTH INFORMATION

CROSS-REFERENCES TO RELATED APPLICATIONS

[001] This application claims priority to U.S. Provisional Application Ser. No.

61/714,579 filed Oct. 16, 2012, the disclosure of which is incorporated herein by reference in its entirety.

BACKGROUND

Field

[002] The present disclosure relates to a system, method, and computer program product for configuring biometric devices for transmitting health information based on consumer information.

Related Art

[003] There are dozens of consumer HMDs (health monitoring devices) on the market and many more are being released at an accelerating pace. These HMDs fall into seven main categories:

Glucose meters

Blood pressure monitors

Weight scales

Activity monitors

Peak flow meters

Pulse oximeters

- PT-INRs.

[004] There is currently no standard way for these HMDs to connect with and communicate with an external system. Manufacturers often support different transport mechanisms using serial cables, USB cables, or wireless using infrared (IR), ANT+, or Bluetooth. Furthermore, the protocols used to transmit data from the HMDs vary across manufacturers and devices.

[005] Devices (Hubs) and computer implemented software (Gateway) connect various HMDs and allow them to transmit their biometric data to a health monitoring system. A Hub or Gateway provides end users with a single data collection hub that can connect with various HMDs through cables, or wirelessly. The Hub or Gateway also understands the protocol that these HMDs use to transmit the biometric data they hold in their memory.

[006] To address this wide variety of connections, the consumer would have to pick between many different cables and adapters. Furthermore, once a Hub or Gateway has established connection with a HMD, it needs to connect with a network server (Numera Net, for example) that routes the biometric data to the appropriate health coaching and condition management programs. A consumer will then need to pick the connection option(s) between the Hub or Gateway and the Numera Net system.

[007] The same HMD may require different cables, if it uses a wired connection, when connecting with a Hub or Gateway. The same is true when a HMD needs to connect through the wireless ANT+ protocol to the Gateway for PC or the Gateway for iOS. Different wireless adapters are needed in each of these cases. It should also be noted that the Hubs or Gateways do not all support the same set of HMDs.

[008] From an internal product management perspective, the situation is further complicated by the fact that some parts differ based on the locale where they will be used. The system that records what parts are needed for each HMD, Hub, and Gateway would have to duplicate many of the same parts just because they need to serve a different locale. The Fig. 1 shows examples of these locale dependent parts.

[009] Thus, there is a need for improved methods for configuring HMD's and the necessary connectivity equipment for communicating biometric information.

SUMMARY

[010] Accordingly, provided are methods and systems to provide consumers with the desired flexibility in specifying and ordering HMD's, Hubs, and adaptors tailored to their needs, even when the number of possible combinations among these parts is extremely high. A consumer may use these methods to select the correct components and parts they need regardless of:

1) the Hub or Gateway selection, or

2) the number and choice of HMDs they want to connect with the selected Hub or

Gateway, or

3) the way(s) the Hub or Gateway is connecting with the Numera Net system, or

4) whether or not they already own the Hub or Gateway (i.e. they are adding an HMD to a Kit they previously ordered, or 5) whether or not they already own the HMD(s) (i.e. in cases where the HMD(s) were provided by an organization that is sponsoring or managing their health or wellness program.

[Oi l] Provided are methods and systems for configuring biometric and connectivity devices for transmitting health information comprising:

populating a digital repository with information corresponding to a plurality of biometric and connectivity device components; interviewing a consumer having a need thereof to determine at least one consumer attribute;

storing the at least one consumer attribute in a memory; and

querying the digital repository for a subset of biometric and connectivity device components based on the at least one consumer attribute, the subset of biometric device and connectivity components collectively forming a system meeting the need of the consumer.

[012] The present inventors have further determined that it would be advantageous to have the ability to determine certain properties of the system as configured prior to placing an order. Accordingly, another object is to provide summary information pertaining to a configured system, or portion thereof. As consumers have individualized cost constraints, cost information may be available to determine a system price as configured.

[013] The inventors further recognized that recent advances in health care business systems make it desirable to allow for the integration of a medical device configuration tool with a variety of other applications related to the provider's business. Accordingly, another object is to provide a configuration system that may be integrated with a variety of consumer management and office management systems. For example, the system may include, for example, consumer identification information, reimbursement code information, and consumer historical information that allows the system to interface with, for example, commercially available consumer management systems and billing systems, thereby reducing the need for redundant data entry to the various systems used in running a practitioner's practice. This information is also used by the system to populate template letters of necessity that are used to obtain approval for funding from the consumer's payment source.

[014] Provided is a novel computer-based system, method, and computer program product through which a salesperson or consumer may enter consumer-specific information through, for example, a personal data assistant (PDA). The information is processed to arrive at potential system configurations having the major components that satisfy the consumer- specific needs. The potential solutions are ranked according to some criteria (e.g., cost, connectivity, functionality, inventory, etc.). The consumer or salesperson may then select one of the potential solutions and provide further refinements to it prior to placing an order. These refinements may include, for example, changing out proposed components or deselecting those portions of the suggested system that the consumer does not wish to order. Since the system provides complete solutions including all of the major components for a device based on consumer-specific information, the consumer or salesperson is not required to work through the many complexities in arriving at the suggested systems. Accordingly, salespersons using the system may focus more of their time on the customer-oriented aspects of their business, and less time dealing with the complexities of configuring the systems for their consumers.

[015] In one embodiment, the method is implemented as a system for configuring a system for transmitting health information based on minimal input information, the required input information being consumer-related data rather than device component information. A customer or salesperson may select a complete system or customize it to further meet the needs of a particular customer. The system includes the ability to order either a complete system, or a subset of a system, based on the customer's particular needs. Customer information is maintained such that the system of the present disclosure may interface with, for example, customer management systems, reimbursement systems, and billing systems alleviating the need for redundant data entry.

BRIEF DESCRIPTION OF THE OF THE DRAWINGS

[016] The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings, in which like reference numerals refer to like parts, and in which:

[017] FIG. 1 is a diagram showing regional differences in biometric and connectivity devices; and

[018] FIG. 2 is a diagram showing the Data Model; and

[019] FIG. 3 is an ER diagram showing the relationships between devices accessories and products; and

[020] FIG. 4 is an ER diagram showing the relationships between HMDs and Gateway or Hub categories; and

[021] FIG. 5 is an ER diagram showing the relationships for category Gateways and Hubs with Products and Numera Net through the Gateway Category Connections and Gateway Category Connection Types tables; and [022] FIG. 6 is an ER diagram showing the relationships for the localized Gateways and Hubs; and

[023] FIG. 7 is an ER diagram showing the Product specific relationships; and.

[024] FIG. 8 is a screen shot for a DKW Configurator; and

[025] FIG. 9 is a screen shot for additional accessories that may be selected from the Associate Accessories; and

[026] FIG. 10 is a screen shot of the Devices-Gateway Categories-Accessories interface; and

[027] FIG. 11 is a screen shot of the screen that is activated when the DKW

Administrator clicks on the Gateway Categories-Connections-Accessories button; and

[028] FIG. 12 is a screen shot of the screen that is activated through the localized Hub configuration screen that is accessible through the Gateway-Connections-Accessories button; and

[029] FIG. 13 is a diagram showing the relationship between category Hubs or

Gateways and localized Hubs or Gateways; and

[030] FIG. 14 is a screen shot of the first step of the DKW as implemented in the Numera Store; and

[031] FIG. 15 is a screen shot showing the connection options between the Home Hub and the Numera Net system; and

[032] FIG. 16 is a screen shot showing the HMD options that the user needs to select in the third step; and

[033] FIG. 17 is a screen shot showing the full Kit options that the user needs to select in the third step; and

[034] FIG. 18 is a screen shot showing the use of the DKW selection wizard in the Numera Store to select a Kit for diabetes that includes a Home Hub connecting with the Numera Net system using GSM cellular connection and a previously purchased Abbott FreeStyle Lite glucose meter; and

[035] FIG. 19 is a screen shot showing the use of the DKW selection wizard in the Numera Store to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have; and

[036] FIG. 20 is a screen shot showing the first step of the use of the DKW selection wizard in the Numera Store to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have to connect through Ethernet cable; and [037] FIG. 21 is a screen shot showing the second step of the use of the DKW selection wizard in the Numera Store to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have to connect through Ethernet cable; and

[038] FIG. 22 is a screen shot showing the third step of use of the DKW selection wizard in the Numera Store to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have to connect through Ethernet cable; and

[039] FIG. 23 is a screen shot showing the final result of the use of the DKW selection wizard in the Numera Store to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have to connect through Ethernet cable; and

[040] FIG. 24 is a screen shot showing the use of the DKW selection wizard in the

Numera Store to order an Abbott FreeStyle Lite glucose meter cuff to work with the

MetrikLink Hub they already have to connect through Ethernet cable; and

[041] FIG. 25 is a screen shot showing the use of the DKW selection wizard in the

Numera Store to order a blood pressure monitor and a weight scale, both of which will be connecting with an iPad device using the ANT+ protocol; and

[042] FIG. 26 is a screen shot showing the second step of use of the DKW selection wizard in the Numera Store to order a blood pressure monitor and a weight scale, both of which will be connecting with an iPad device using the ANT+ protocol; and

[043] FIG. 27 is a screen shot showing the third step of use of the DKW selection wizard in the Numera Store to order a blood pressure monitor and a weight scale, both of which will be connecting with an iPad device using the ANT+ protocol; and

[044] FIG. 28 is a screen shot the Review and Order result screen showing that the Kit includes only one ANT+ adapter (Wahoo ANT plus Key for iPhone); and

[045] FIG. 29 is a screen shot showing the use of the DKW for Sales Wizard in the

Numera Store; and

[046] FIG. 30 is a screen shot showing the use of the DKW for Sales Wizard only the list of connection options and HMDs that are applicable to the Home Hub; and

[047] FIG. 31 is a screen shot showing DKW for Sales Wizard application showing that the cellular connection in step #2 and the Abbott FreeStyle glucose meter; and

[048] Fig. 32 is a screen shot showing DKW for Sales Wizard application displaying the same results for the query. DETAILED DESCRIPTION

Abbreviations and Definitions

[049] To facilitate understanding of the disclosure, a number of terms and abbreviations as used herein are defined below as follows:

[050] When introducing elements of the present disclosure or the preferred

embodiment(s) thereof, the articles "a", "an", "the" and "said" are intended to mean that there are one or more of the elements. The terms "comprising", "including" and "having" are intended to be inclusive and mean that there may be additional elements other than the listed elements.

[051] The term "and/or" when used in a list of two or more items, means that any one of the listed items can be employed by itself or in combination with any one or more of the listed items. For example, the expression "A and/or B" is intended to mean either or both of A and B, i.e. A alone, B alone or A and B in combination. The expression "A, B and/or C" is intended to mean A alone, B alone, C alone, A and B in combination, A and C in

combination, B and C in combination or A, B, and C in combination.

[052] The term "biometric device" refers to a device that measures or senses biological or biomedical information. A consumer may have a preferred biometric device as determined by the consumer's measurement needs, their healthcare provider's requirements, connectivity (internet, WiFi, etc.), insurance reimbursement, and cost. They may also prefer devices based on size, weight, and features that enhance portability. The consumer may also have aesthetic preferences including shape, color or other design features such as button size, or readability of a dial or screen.

[053] The term "Health Monitoring Device" (HMD) refers to a third party measurement device that allows a consumer to collect biometric data to help them manage one or more health conditions.

[054] The term "consumer attribute" represents data that reflects a consumer's needs or preferences.

[055] The term "connectivity device" represents any device that provides connectivity between biometric devices, hubs and gateways. Examples of connectivity devices include cables, adapters, and other accessories. A consumer may have a preferred connectivity device as determined by the consumer's measurement needs, their healthcare provider's requirements, connectivity (internet, WiFi, etc.), insurance reimbursement, and cost. They may also prefer devices based on size, weight, and features that enhance portability. The consumer may also have aesthetic preferences including shape, color or other design features such as button size, or readability of a dial or screen.

[056] The term "health information" represents measurable physiological data or parameters. Examples may include blood pressure, blood glucose concentration, weight, and heart rate.

[057] The term "digital repository" refers to a collection of digital information. The digital information is associated with individual biometric and connectivity device components.

[058] The term "Hub" refers to a hardware device that consumers may use at home to connect various HMDs they have allowing them to transmit their biometric data to a health monitoring and management system or application as part of a health coaching and condition management program.

[059] The terms "interview" or "interviewing" refers to asking questions of the consumer or salesperson, analyzing responses, and presenting product recommendations via a computer server.

[060] The term server is intended to refer to a set of one or more processes executed on a data processing system under control of an operating system, and operable to provide a processing service, e.g. a data processing service, a signal processing service, etc. The server may be operable to provide said service to one or more client programs executed on the same or a different data processing system. In particular, the term server is intended to comprise a set of processes executed in a virtualized environment, e.g. utilizing a hardware virtualization technique.

[061] The term "Gateway" refers to a software Hub that consumers can download and run on their PC (Gateway for PC) or on their iPad or iPhone (Gateway for iOS).

[062] The term "Kit" refers to a collection of HMDs, with the necessary connectivity equipment (Hub or Gateway, cables, adapters, and other accessories) and related user documentation, which may be used by a consumer to monitor and manage one or more health conditions.

[063] The term "Numera Net" refers to a system that provides objective, real-time biometrics from a wide range of HMDs, integrating directly into health coaching and condition management programs. The Numera Net system transfers health measurements via standard phone lines, VoIP, wireless or broadband connections, using a Hub or a Gateway. Methods

[064] Certain embodiments as disclosed herein provide methods and systems for configuring biometric and connectivity devices for transmitting health information comprising: populating a digital repository with information corresponding to a plurality of biometric and connectivity device components; interviewing a consumer having a need thereof to determine at least one consumer attribute; storing the at least one consumer attribute in a memory; and querying the digital repository for a subset of biometric and connectivity device components based on the at least one consumer attribute, the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.

[065] Provided is a system for configuring biometric and connectivity devices for transmitting health information, comprising: means for populating a digital repository with information corresponding to a plurality of biometric and connectivity device components; means for interviewing a consumer having a need thereof to determine at least one consumer attribute; means for storing the at least one consumer attribute in a memory; and means for querying the digital repository for a subset of biometric and connectivity device components based on the at least one consumer attribute, the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.

[066] Provided is a system for configuring biometric and connectivity devices for transmitting health information, comprising: a digital repository populated with entries defining a plurality of biometric and connectivity device components, each entry associated with an individual biometric or connectivity device component and having a component identification indicator, a component class indicator, and at least one consumer attribute indicator; a processor; and a computer readable medium encoded with processor readable instructions that when executed by the processor implement a customer user interface mechanism configured to provide a consumer with access to entries in the digital repository via a network and to allow the consumer to provide at least one consumer interview answer indicator, a consumer interview mechanism configured to receive over the network the at least one consumer interview answer indicator corresponding to an attribute of a consumer and to store the at least one consumer interview answer indicator in a memory, and configurator mechanism configured to select a subset of entries from the digital repository based on the at least one consumer interview answer indicator in the memory, the subset of entries including entries corresponding to individual device, components that collectively form a system for transmitting health information meeting a need of the customer.

[067] After reading this description, it will become apparent to one skilled in the art how to implement the disclosure in various alternative embodiments and alternative applications. However, although various embodiments of the present disclosure will be described herein, it is understood that these embodiments are presented by way of example only, and not limitation. As such, this detailed description of various alternative embodiments should not be construed to limit the scope or breadth of the present disclosure as set forth in the appended claims.

[068] The DKW framework uses a tiered architecture and consists of the five parts illustrated in Fig. 2. The data model is implemented using a SQL Server database. The other parts are implemented using C# and Visual Studio 2012.

HMDs:

[069] The ER diagram in Fig. 3 shows the relationships between HMDs (Devices), accessories that can be associated with these Devices (Device Accessories), and Products:

Devices are Products

Devices can have one or many accessories associated with them

Accessories are Products.

HMDs and Gateways/Hubs relationship:

[070] The ER diagram in Fig 4. shows the many-to-many relationship between HMDs and Gateway or Hub categories. Gateway or Hub categories are the locale independent Gateways or Hubs as discussed previously. The diagram also shows how accessories (Device Gateway Category Accessories) can be associated with the Devices/Gateway Categories connection. Note: All tables that have Gateway in their name cover both Gateways and Hubs.

Gateways/Hubs and Numera Net:

[071] The ER diagram in Fig 5. shows the relationships for category Gateways and Hubs primarily with Products and with Numera Net through the Gateway Category

Connections and Gateway Category Connection Types tables.

[072] The ER diagram in Fig 6. shows the same relationships except for the localized Gateways and Hubs. Products:

[073] All HMDs, Hubs, Gateways and their accessories 'inherit' from Products. The ER diagram in Fig 7. shows the Product specific relationships. The extended data (Base Cost, Sale Price, Fulfillment Cost, etc.) and relationships (Product Classifications and Margins) are used to support the DWK for Sales Wizard application.

The DKW Configurator

[074] The DKW Configurator is a DKW tool that can be used by a DKW Administrator to enter the product data and configure the relationships between HMDs, Hubs and

Gateways, and all related accessories and manuals needed to support the DKW Selection Wizard. The DKW Configurator is also used to configure any extended data and relationships that are needed to support any additional applications like the DKW for Sales Wizard application or other applications that can be developed using the DKW framework.

[075] One of the key goals of the DKW Configurator is to make it easier for the DKW Administrator to add new HMDs, Hubs or Gateways, relationships, and accessories in the most efficient way.

[076] Fig 8. shows the main screen of the DKW Configurator. The buttons represent entities in the DKW data model and are laid out in a way to represent best the relationships between these entities. For example, the Devices-Accessories button represents the accessories that are associated with a specific HMD. By clicking this button, the DKW Administrator will be able to create, update, or delete associations between HMDs and accessories as shown in the screen shot below.

[077] For example, the A&D LifeSource UC321PL weight scale has been associated with the serial cable 'LifeSource UC321PL serial cable - 6FT' from the same manufacturer showing in the middle table. Anytime a user of the DKW Selection Wizard or the DKW for Sales Wizard selects the A&D LifeSource UC321PL weight scale, the DWK will know that this HMD will require the serial cable and will include it in the Kit when requested through the DKW API.

[078] The DKW Administrator shown in Fig. 9 can associate additional accessories by selecting accessories from the list showing at the bottom table and clicking the Associate Accessories with selected Device button.

[079] Another area of the DKW Configurator is the ability it provides to associate parts or accessories at the connection level. If the KDW Administrator clicks the Devices- Gateway Categories-Accessories button, they will be able to perform two actions as shown in Fig. 10.

[080] On the left side, the DKW Administrator can create associations between an HMD and any Hub or Gateway that supports this HMD in its library. In the screen shot, the A&D LifeSource UA-767PC Arm blood pressure monitor is associated with the Gateway for PC, the MetrikLink hub, and the Home Hub. This HMD is therefore not supported on the Gateway for iOS.

[081] Once a HMD has been associated with a Hub or Gateway, the DKW

Administrator can associate accessories with the HMD/Hub or HMD/Gateway association. In the screen shot, on the right side, the Numera Adapter #13 and a Numera Cable have been associated with the connection that links the LifeSource UA-767PC Arm device to the Gateway for PC. Anytime a user of the DKW Selection Wizard or the DKW for Sales Wizard selects the A&D LifeSource UA-767PC Arm and the Gateway for PC, the DWK will know that this combination of HMD/Gateway will require the Numera Adapter #13 and the Numera Cable and will include these in the Kit when requested through the DKW API.

[082] The DKW Administrator can also setup the connections between a Hub or Gateway and Numera Net system. Here, the DKW Configurator makes a distinction between a category Hub or Gateway and a localized Hub or Gateway. A category Hub (or Gateway) is an entity that represents all the common properties of a Hub (or Gateway). These properties (associations, connections, etc.) remain the same regardless of the locale where the Hub (or Gateway) will be used. For example, a Hub connecting with Numera Net using Ethernet connection will always connect through a standard Ethernet cable. In this case, the Ethernet cable is an accessory that will be associated with the category Hub. This is what the word 'Categories' showing on some of the buttons refers to.

[083] The Fig. 11 shows the screen that is activated when the DKW Administrator clicks on the Gateway Categories-Connections-Accessories button. On the left side of the screen, the (category) Home Hub has been associated with cellular, Ethernet, Phone, and Wi- Fi connection options. On the right side, the screen shows the Home Hub Cellular connection option (highlighted on the left side), a GSM Cellular adapter would be needed to enable this connection. The cellular adapter requires a GSM data plan (provided through a SIM card). However, the data plan can vary depending on the carrier and the country.

[084] To add a data plan to the Home Hub, the DKW Administrator can do this through the localized Hub configuration screen that is accessible through the Gateway-Connections- Accessories button as shown in Fig. 12. This is where the DKW Administrator can associate other locale dependent accessories or parts such as phone cable, user manuals and other. This is where branded versions of the Hubs and Gateways may be added. The screen shot below shows a couple of Home Hub versions, one with dark grey color and one with white color.

[085] This separation between category Hubs or Gateways and localized Hubs or Gateways simplifies the process of configuring new localized Hubs or Gateways. If a new Hub is available in blue color for example, the DKW Administrator does not need to recreate all the HMD associations. They can add the Hub with the new color to the localized Hubs, using the screen at the Gateways button and indicate that this Hub has a Numera Home Hub category, and this new Hub will automatically get all the HMD associations that have been established with the generic Home Hub, , as shown Fig. 12.

Part II: The Business Logic

Part III: The Configurator Tool

[086] Following is the class used by the DKW Selection Wizard data layer to retrieve Gateway or Hub data. In the current implementation, the DKW Selection Wizard is implemented such that the Hub or Gateway selection is the first step of the selection wizard. The order of steps 1 to 3 can be modified, for example to have the HMD selection be performed in the first step. This is why you see the code below accepting a list of HMDs (lstOfDeviceExternallDs) or a list of Gateway or Hub Connection options

(IstOfGatewayConnectionsIDs) as input,

using System;

using System. Collections. Generic ;

using System.Linq;

using System.Text;

//added

using System.Data.SqlClient;

using System. Configuration;

using System.Reflection;

namespace Numera.Marketplace {

class Gateways {

private List<string> JstOfDeviceExternallDs; //list of devices

private List<string> JstOfGatewayConnectionsIDs; //list of Gateway connection types

private string _connectionString;

public List<string> DeviceExternallDs {

get { return JstOfDeviceExternallDs; }

set { _lstOfDeviceExternalIDs = value; }

}

public List<string> GatewayConnectionsExternallDs {

get { return JstOfGatewayConnectionsIDs; }

set { _lstOfGatewayConnectionsIDs = value; }

}

public Gateways() {

_connectionString = ConfigurationManager. AppSettings["ConnectionString"] ;

}

//Input: None.

//Output: List of Gateways and Hubs that Numera supports currently

public List<ProductData> GetRecords()

{

List<ProductData> IstOfParts = new List<ProductData>();

string query = getGateway Query (); getGatewayData(query, ref lstOfParts);

return lstOfParts;

}

private void getGatewayData(string queryString, ref List<ProductData> 1st) {

using (SqlConnection connection =

new SqlConnection(_connectionString))

{

SqlCommand command = new SqlCommand(queryString, connection); try

{

connection. Open() ;

SqlDataReader reader = command. ExecuteReader();

if (reader. HasRows == true)

{

ProductData newPart;

while (reader.Read()) {

newPart = new ProductData();

newPart.ID = Convert.ToInt32(reader["PProductID"]);

newPart. Description = (string)reader["PDescription"];

newPart. ExternallD = (string)reader["ExternalID"]; newPart. Is Active = (bool)reader["IsActive"];

newPart.Manufacturer.Description =

(string)reader[ "MDescription" ] ;

newPart.Manufacturer.ExternallD = (string)reader["MExternalID"]; newPart. ProductType =

ProductTypes.GetProductType((string)reader["Type"]); newPart. Category =

ProductTypes . GetProductCategory (newPart. ProductType,

(s tring)reader [ " CExternallD " ] ) ;

lstAdd(newPart);

newPart = null;

}

connection. Close() ;

}

else {

Logger.Info("Could not find product info.",

MethodBase.GetCurrentMethod().DeclaringType.Name + "-" + MethodB ase. GetCurrentMethod() . Name) ;

}

reader. Close();

}

catch (Exception ex) {

Logger. Error(ex,

}

private string getGatewayQuery() {

//return the full list of Gateways

string stringQuery = "SELECT gc.ExternallD as CExternallD," + " m.Description as MDescription, m.ExternallD as MExternallD," + " pc.ExternallD as PCExternallD,"

+ " p.ID as PProductID, p.Description as PDescription, p.ExternallD, p.ManufacturerlD, p. Type,"

+ " p.ClassificationID, p.IsActive"

+ " FROM ProductClassifications pc INNER JOIN (Gate way Categories gc INNER JOIN (Manufacturers m INNER JOIN Products p ON m.ID =

p.ManufacturerlD)"

+ " ON gc.ID = p.GatewayCategorylD) ON pc.ID = p.ClassificationID"

+ " WHERE (p.Type = '" +

ProductTypes.GetProductTypeForDB(ProductType.GatewayOrHub) + "') AND (p.IsActive = 'True')"

+ " ORDER BY p.zOrder;";

return stringQuery;

}

Part IV: The Application Program Interface (API)

Sample DKW Selection Wizard API and business layer implementation

[087] Following is the class used by the DKW Selection Wizard as access point for Main User Interfaces (MUI) such as the DKW Selection Wizard User Interface to retrieve Gateway or Hub selection options for the first step of the DKW Selection Wizard. Business rules can be applied as noted in the comment below before serving the Gateway or Hub data to the client side:

using System;

using System. Collections. Generic ;

using System.Linq;

using System.Text;

//added

using System.Reflection; namespace Numera.Marketplace

{

class B_Gateways

{

//Input: None.

//Output: List of Gateways and Hubs that Numera supports currently public List<ProductData> GetRecords()

{

List<ProductData> IstOfParts = new List<ProductData>();

if (validlnput() == false)

{

return IstOfParts;

}

Gateways g = new Gateways();

IstOfParts = g.GetRecords();

// business rules are applied here before returning the data t return IstOfParts;

}

private Boolean validlnput()

{

//nothing to validate for now

return true;

}

} Part V: The Main User Interfaces (MUI) Examples

Using the DWK in an eCommerce solution

[088] A consumer, an Administrator or a CSR can use the DKW selection wizard in the Numera Store (or an eCommerce site in general) to select the correct components or parts of the Kit they need in only three steps regardless of:

The Hub or Gateway selection, or

The number and choice of HMDs they want to connect with the selected Hub or Gateway, or

The way(s) the Hub or Gateway is connecting with the Numera Net system, or

Whether or not they already own the Hub or Gateway (i.e. they are adding an HMD to a Kit they previously ordered

Whether or not they already own the HMD(s) (i.e. in cases where the HMD(s) were provided by an organization that is sponsoring or managing their health or wellness program

Use case #1:

[089] A consumer or Administrator or CSR using the DKW selection wizard in the Numera Store to select a Kit for diabetes that includes a Home Hub connecting with the Numera Net system using GSM cellular connection, and the Abbott FreeStyle Lite glucose meter.

[090] The following screen shot shows the first step of the DKW as implemented in the

Numera Store. The system and user actions are as follows:

The Numera Store application requests the list of all Hubs and Gateways that can be offered from the DKW database by calling a DKW API.

The Numera Store then filters out the options that are not applicable (see note 1 below).

The user selects the Hub or Gateway. In this case, the Home Hub was selected.

When a Hub or Gateway is selected, the system displays a checkbox labeled Ί already have this item'. The user can check this box if they already have the Hub or Gateway. In this case, the user may be interested in ordering accessories and/or HMD(s) only. If the Ί already have this item' box is checked, the Hub or Gateway will be used to pull the correct and remaining parts of the Kit, but will not be included in the final results shown in the Review and Order step. The user clicks 'Next' to move to the second step, as shown Fig. 13. Note 1: This allows the Numera Store, which is a multi-store solution that Numera offers to its customers, to customize the options based on what each store offers in its catalog. This way, the DKW database would hold the complete configuration with all Hubs, Gateways, HMD's and associated accessories, and it is up to each client (or store) to filter out the lists to match what is available in its own catalog that is usually a subset of what is held in the DKW database. This filtering logic is applied for each of the three steps of the DKW Selection Wizard.

[091] Fig. 14 shows the connection options between the Home Hub and the Numera Net system. The list of options was requested from the DKW through the DKW API. The list of options will change depending on the selection made in the first step. Here, the screenshot shows the full list of options available for a Home Hub. The user can select zero of more options. In this case, the option to connect using cellular connection is checked. The user is ready now to move to the third and last selection step.

[092] The following screen shot shows the HMD options that the user needs to select in the third step. The list of HMDS was retrieved from the DKW database through the DKW API. The list depends on the Hub or Gateway selection made in the first step.

[093] The Numera Store application filters out any HMDs that are not relevant for the store that is requesting them. The user can make zero or more selection. Once an HMD is selected, the system displays a checkbox labeled Ί already have this item'. The user can check this box if they already have the HMD(s) they intend to select. In this case, the user may be interested in ordering a Hub or Gateway or maybe they are just interested in ordering accessories. If the Ί already have this item' box is checked, the selected HMD(s) will be used to pull the correct parts of the Kit, but will not be included in the final results shown in the Review and Order step.

[094] The user selects the Abbott FreeStyle Lite glucose meter and clicks 'Next' , as shown Fig. 15.

[095] The DKW selection wizard has now all the information it needs to build the dynamic kit and display it to the user. The Numera Store application sends the selection data to the DKW through the API and gets back the full Kit as shown in the following screen snapshot. The user can review and make any updates they may need such as increasing quantities (an Administrator may be ordering a quantity of the same Kit for example) or removing any of the displayed items in the result list. If the user is satisfied with the results, they can add all these items to their Wishlist or to their shopping Cart and go to the checkout for payment and order submission, as shown Fig. 16. Use case #2:

[096] A consumer or Administrator or CSR using the DKW selection wizard in the Numera Store to select a Kit for diabetes that includes a Home Hub connecting with the Numera Net system using GSM cellular connection. The user already has the Abbott FreeStyle Lite glucose meter (it could have been provided to them by their health

administrator or their health plan for example):

[097] In this case, the first two steps are the same as in Use case #1. When the user gets to the third step, they do the following (as shown in the screen shot below):

User selects the Abbott FreeStyle Lite glucose meter

The DKW selection wizard displays the Ί already have this item. ' box

User checks the Ί already have this item.' Box

User clicks 'Next, as shown Fig. 17.

[098] Fig. 18 shows the result at the 'Review and Order' step. Notice that the Abbott FreeStyle Lite is not included in the list. However, the DKW is still providing the user with the list of accessories that they need to connect the glucose meter with the Home Hub. In this case, the accessories are the Numera Cable and the Adapter #7.

Use case #3:

[099] A consumer, Administrator, or CSR have previously ordered the Kit referenced in Use Case #1 and Use Case #2. They need to order an Omron HEM-705CP blood pressure cuff to work with the Home Hub they already have. They also want to be able to connect through Ethernet cable (in addition to the cellular connection they already have).

[0100] At the first step of the DKW selection wizard, the user does the following:

User selects the Home Hub

The DKW selection wizard displays the Ί already have this item. ' box

User checks the Ί already have this item.' Box

User clicks 'Next', as shown Fig. 19.

At the second step, the user selects the 'Ethernet' connection option as shown in the screen shot below and clicks 'Next', as shown Fig. 20.

At the third step, the user selects the Omron HEM-705CP blood pressure cuff as shown in the screen shot below and clicks 'Next', as shown Fig. 21. [0101] The DKW selection wizard displays the final result at the 'Review and Order' screen as shown in Fig. 22. Notice that the list does not include the Home Hub. It now shows the Adapter #14 and Numera Cable that are needed to connect the new HMD (HEM- 705CP) to the Home Hub, the HEM-705CP device, the network cable for the Ethernet connection, and the Home Hub user manuals for convenience (at no cost to the user).

Use case #4:

[0102] What if the user was using the MetrikLink hub using an Ethernet connection instead of the Home Hub, and they needed to order the same Kit for diabetes as shown in Use Case #1 above.

[0103] Fig. 23 shows the results of the user selections. In this case that the MetrikLink does not need the Numera Cable to connect with the glucose meter. This shows how the DKW can provide the correct parts, not only at the HMD or Hub/Gateway level, but also at the connection level between these two components. This is one of the important features of the DKW that will be covered in more details in the Technical Overview section of the document. In addition, there is no Ethernet cable in this case. Instead, the DKW is offering the MetrikLink USB cable that allows a MetrikLink hub to connect to a PC to get access to the Ethernet, which is the only way a MetrikLink can have an Ethernet connection.

Use case #5:

[0104] This use case shows how the DKW can appropriately set the number of parts or accessories needed in a Kit depending on the type of accessory or on the connection capabilities of a Hub or a Gateway. This is accomplished in the DKW business logic where business rules and special technical or physical considerations can be enforced.

[0105] Here, the user will be selecting a blood pressure monitor and a weight scale, both of which will be connecting with an iPad device using the ANT+ protocol. The user first selects the Gateway for iOS as indicated in the screen shot below and then clicks 'Next', as shown Fig. 24.

[0106] The user then selects the Wi-Fi connection option indicating that their iPad will be connecting through Wi-Fi with the Numera Net system as shown in the screen shot below. Notice that the list shows three connection options whereas the Home Hub was showing four. These connection options are configured for each Hub or Gateway using the DKW

Configurator. The user clicks 'Next' to move to the third step, as shown Fig. 25.

[0107] On the third step, the user selects the A&D LifeSource UA-851ANT blood pressure cuff and the A&D UC-324ANT weight scale as shown in the screen shot below. These two HMDs use the ANT+ protocol to connect with the Gateway for iOS that will be running on the iPad device. Notice that the DKW Selection Wizard is showing three HMDs only. These are the HMDs that are currently supported in the Gateway for iOS library and were configured using the DKW Configurator. The user clicks 'Next' to move to the result screen, as shown Fig. 26.

[0108] On the Review and Order result screen shown below, the Kit includes only one ANT+ adapter (Wahoo ANT plus Key for iPhone). The DKW business logic limits the number of the ANT+ adapters to one as the user will only need one adapter that they can use to connect and upload biometric data from the two HMDs, simultaneously if needed.

[0109] There are similar cases where the DKW business logic is used to make sure that the user will be getting the correct number of parts in their Kit. Another example is the user orders a MetrikLink hub that has only one physical plug. In this case, if the user selects multiple HMDs that require the same adapter (i.e. Adapter #15), the resulting Kit will include only one Adapter #15 and not two, recognizing the fact that the MetrikLink device can accommodate one HMD at a time, as shown Fig. 27.

Using the DKW to support the sales representative

[0110] As mentioned above, the DKW may be extended to support sales representatives in selecting the correct Kits in order to submit a quote to their customers. This also shows an example how the DKW framework can be extended to support other uses. A sales representative can use the DKW for Sales Wizard application to:

Quickly select a Kit based on customer requirements and submit a quote to the customer

Compare prices between different Kits for the same health condition (e.g.,. diabetes Kits) to offer an HMD alternative to the customer

Have direct visibility to costs and margins at the Kit component level to offer best price based on quantities or other considerations

[0111] The Fig. 28 shows the DKW for Sales Wizard application when it is first started. The DKW for Sales Wizard application uses the DKW API to get access to the same 'kitting' services discussed above with the DKW selection wizard used in the Numera Store application. In some embodiments, the sales representative has the same 3 steps to select in the same sequence:

The first step: Select Gateway or Hub The second step: Select the connection option between the Gateway or Hub and the Numera Net system, and

- The third step: Select the HMD(s)

[0112] Using the same Kit for diabetes as was described in Use Case #1 above, the sales representative selects the Home Hub in Step #1.

[0113] The DKW for Sales Wizard application now shows only the list of connection options and HMDs that are applicable to the Home Hub as shown in Fig 29.

[0114] The sales representative now select cellular connection in step #2 and the Abbott FreeStyle glucose meter in step #3 as shown in Fig. 30.

[0115] The sales representative clicks on the 'Get BOM' button. The DKW for Sales Wizard application will display the same results as seen in Use Case #1. In some embodiments, additional cost, price, and margin data is available to the sales representative to make a quote to the customer as shown in Fig. 31.

[0116] The sales representative also has the option to Export the results to an Excel spreadsheet and update the list by adding/removing parts or by changing the price or margin of a specific item to offer volume -pricing discount for example.

Other Embodiments

[0117] The detailed description set-forth above is provided to aid those skilled in the art in practicing the present disclosure. However, the disclosure described and claimed herein is not to be limited in scope by the specific embodiments herein disclosed because these embodiments are intended as illustration of several aspects of the disclosure. Any equivalent embodiments are intended to be within the scope of this disclosure. Indeed, various modifications of the disclosure in addition to those shown and described herein will become apparent to those skilled in the art from the foregoing description, which do not depart from the spirit or scope of the present inventive discovery. Such modifications are also intended to fall within the scope of the appended claims.

[0118] All references cited in this specification are hereby incorporated by reference. The discussion of the references herein is intended merely to summarize the assertions made by their authors and no admission is made that any reference constitutes prior art relevant to patentability. Applicant reserves the right to challenge the accuracy and pertinence of the cited references.

Claims

CLAIMS What is claimed is:

1. A method for configuring biometric and connectivity devices for transmitting health information comprising the steps of:

interviewing a consumer having a need thereof to determine at least one consumer attribute;

storing the at least one consumer attribute in a memory;

and querying a digital repository populated with information corresponding to a plurality of biometric and connectivity device components for a subset of biometric and connectivity device components based on the at least one consumer attribute, the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.

2. The method of claim 1 , wherein the at least one consumer attribute is a preferred biometric device.

3. The method of claim 1, wherein the at least one consumer attribute is a preferred connectivity device.

4. The method of claim 1 , further comprising the step of displaying the subset of

biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.

5. The method of claim 1, further comprising the step of allowing the consumer to select the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer for purchase.

6. A system for configuring biometric and connectivity devices for transmitting health information, comprising:

means for populating a digital repository with information corresponding to a plurality of biometric and connectivity device components;

means for interviewing a consumer having a need thereof to determine at least one consumer attribute;

means for storing the at least one consumer attribute in a memory;

and means for querying the digital repository for a subset of biometric and connectivity device components based on the at least one consumer attribute, the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.

7. The system of claim 6, wherein the at least one consumer attribute is a preferred biometric device.

8. The system of claim 6, wherein the at least one consumer attribute is a preferred

connectivity device.

9. The system of claim 6, further comprising a means for displaying the subset of

10. The system of claim 6, further comprising a means for allowing the consumer to select the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer for purchase.

11. A system for configuring biometric and connectivity devices for transmitting health information, comprising:

a digital repository populated with entries defining a plurality of biometric and connectivity device components, each entry associated with an individual biometric or connectivity device component and having a component identification indicator, a component class indicator, and at least one consumer attribute indicator;

a processor;

and a computer readable medium encoded with processor readable instructions that when executed by the processor implement a customer user interface mechanism configured to provide a consumer with access to entries in the digital repository via a network and to allow the consumer to provide at least one consumer interview answer indicator, a consumer interview mechanism configured to receive over the network the at least one consumer interview answer indicator corresponding to an attribute of a consumer and to store the at least one consumer interview answer indicator in a memory, and configurator mechanism configured to select a subset of entries from the digital repository based on the at least one consumer interview answer indicator in the memory, the subset of entries including entries corresponding to individual device, components that collectively form a system for transmitting health information meeting a need of the customer.

12. The system of claim 11, wherein the consumer attribute is a preferred biometric

device.

13. The system of claim 11, wherein the consumer attribute is a preferred connectivity device.

14. The system of claim 11, the processor readable instructions further displaying the subset of biometric device and connectivity components collectively forming a system for transmitting health information meeting the need of the consumer.