TW201528199A - Setup synchronization apparatus and methods for end user medical devices - Google Patents

Abstract

Embodiments of the present invention enable setup synchronization of an end user medical device such as a blood glucose meter. The invention includes a controller including a memory; a transceiver operatively coupled to the controller; and a host computer interface operative to couple the controller to a host computer, wherein the memory is operative to store instructions executable on the controller. The instructions are adapted to cause the controller to scan for an advertising medical device using the transceiver, establish a communications connection with a medical device advertising for synchronization, and transmit synchronization data to a medical device once a communication connection has been established. Numerous other aspects are disclosed.

Description

Setting synchronization device and method for terminal user medical device [related application]

The present application claims the priority of U.S. Provisional Patent Application No. 61/926,215, filed on Jan. 10, 2014, and entitled "Synchronization Device and Method for End User Medical Devices" (SETUP) SYNCHRONIZATION APPARATUS AND METHODS FOR END USER DEVICES) (Attorney Docket No. BHC134020 (BHDD/045/L), the entire disclosure of which is hereby incorporated by reference in its entirety herein in its entirety herein in its entirety herein

The present invention relates to medical devices, and the present invention relates more particularly to devices, systems, and methods for setting synchronization of medical devices.

Traditional end-user medical devices, such as blood glucose meters (BGMs), are typically packaged by the manufacturer using an initial configuration that is not always the most appropriate for the intended application or patient. Good. Therefore, from time to time, the health care provider (HCP) must adjust the configuration of the meter. Thus, systems, devices, and methods are needed for facilitating the placement of such devices.

In some aspects, embodiments of the present invention provide: an apparatus for setting synchronization of a medical device, such as a blood glucose meter. The device comprises: a controller comprising a memory; a transceiver operatively coupled to the controller; and a host computer interface, the host computer interface operating to the controller Coupled to a host computer, wherein the memory is operative to store instructions executable on the controller, the instructions being adapted such that the controller uses the transceiver to scan an advertised medical device, establishing A communication connection between the medical devices, the medical device issues an announcement for synchronization, and, once a communication connection has been established, transmits the synchronization data to a medical device.

In other aspects, embodiments of the present invention provide a system for setting synchronization of a medical device, such as a blood glucose meter. The system includes: a terminal user medical device, the terminal user medical device including a startup function for causing the medical device to be in an announcement mode for requesting synchronization; and a setting synchronization device, the setting The synchronization device includes: a controller including a memory; a transceiver operatively coupled to the controller; and a host computer interface, the host computer interface operates to the controller Coupled to a host computer. The memory is operative to store instructions executable on the controller, the instructions being adapted such that the controller uses the transceiver to scan an audible medical device.

In still other aspects, embodiments of the present invention provide a method for setting synchronization of a medical device, such as a blood glucose meter. The method comprises the steps of: scanning a terminal user medical device with a setting synchronization device The terminal user medical device issues an announcement for synchronization; a terminal user medical device is discovered, the terminal user medical device issues an announcement for synchronization; and a discovered terminal user medical device is established a communication connection between the two; and synchronizing the connected end user medical device.

Many other aspects are provided in accordance with the and other embodiments of the present invention. Other features and aspects of the embodiments of the present invention will become more fully apparent from the appended claims.

100‧‧‧ system

102‧‧‧Set up synchronization device

102’‧‧‧ Circuitry

104‧‧‧Host computer

106‧‧‧Communication

108‧‧‧End user medical device

110‧‧‧Packaging

112‧‧‧ access hole

114‧‧‧Start button

202‧‧‧Shell

204‧‧‧Configuration switch

206‧‧‧ indicator

208‧‧‧Connector

208’‧‧‧Host computer interface

302‧‧‧ Controller

304‧‧‧ memory

306‧‧‧ transceiver

308‧‧‧Antenna

400‧‧‧block diagram

402‧‧‧Steps

404‧‧‧Steps

406‧‧‧Steps

408‧‧‧Steps

410‧‧‧Steps

412‧‧‧Steps

414‧‧‧Steps

500‧‧‧block diagram

502‧‧‧Steps

504‧‧‧Steps

506‧‧‧Steps

508‧‧‧Steps

510‧‧ steps

512‧‧‧Steps

514‧‧‧Steps

516‧‧‧Steps

518‧‧‧Steps

520‧‧‧Steps

600‧‧‧ method

602‧‧‧Methods/Steps

604‧‧‧Methods/Steps

606‧‧‧Methods/Steps

608‧‧‧Methods/Steps

610‧‧‧Methods/Steps

612‧‧‧Methods/Steps

614‧‧‧Methods/Steps

616‧‧‧Methods/Steps

618‧‧‧Methods/Steps

620‧‧‧Methods/Steps

Figure 1 illustrates a perspective view of an example setup synchronization system in accordance with some embodiments of the present invention.

Figure 2 illustrates a perspective view of an example setup synchronization device in accordance with some embodiments of the present invention.

Figure 3 illustrates a schematic block diagram of circuitry for setting up a synchronization device, in accordance with some embodiments of the present invention.

Figure 4 illustrates a block diagram representation of a system initial procedure in accordance with some embodiments of the present invention.

Figure 5 illustrates a block diagram representation of a synchronization procedure in accordance with some embodiments of the present invention.

Figure 6 is a flow diagram depicting a method of synchronizing a medical device in accordance with some embodiments of the present invention.

End user medical device (eg, for example, a blood glucose meter (BGM)) It is usually provided to the patient by a health care provider (HCP). The HCP may reserve some devices (as packaged by the manufacturer) and provide such devices to the patient upon request. The devices may include: an instant clock (RTC), which is conventionally set by the manufacturer prior to packaging the device. This ensures that the end user receives the device with the precisely set RTC so that the medical material can be correctly time indexed. Therefore, when the device is saved, the RTC is usually executed. Since the storage time for such devices can be as long as 15 months or longer, a large amount of battery power consumption can occur during this period. In addition, the HCP can be located in a different time zone than the manufacturer's time zone, and thus the steps of correctly setting the RTC can be further complicated.

Traditionally, manufacturers have solved these problems by using more expensive batteries with sufficient power to maintain maximum shelf life. The manufacturer also sets the RTC based on where the devices are to be located. However, both of these solutions require additional manufacturing costs and increase the cost of the medical device for the end user. Thus, there is a need for improved methods and apparatus to perform setup synchronization of such devices. Furthermore, there are various other configuration options that the HCP can set on the end user medical device (eg BGM) (eg units used (eg mg/dL and mmol/L), high/low limits, reminder alerts and many more).

Embodiments of the present invention provide: a setup synchronization device that addresses the owner of such issues. The setup synchronization device in accordance with an embodiment of the present invention can be adapted to set the RTC and other parameters of the end user medical device in a wireless manner and in an automated manner. The setting synchronization device may include: a controller (for example, a programmable microcontroller); a memory for the memory Storing a host computer application; a transceiver (eg, a transmitter/receiver) that facilitates wireless communication with the end user's medical device; and a computer interface I/O port (eg, for use with a host computer) Communicate and allow the upload/installation of the host computer application to the universal serial bus (USB) interface of the host computer).

Referring to FIG. 1, in some embodiments, system 100 of the present invention includes a setup synchronization device 102 that is adapted to be connected to host computer 104 operated by an HCP. The setup synchronization device 102 is also tuned to communicate (106) with the end user medical device 108 (e.g., BGM) in a wireless manner, while the end user medical device 108 is still contained within the package 110 from the manufacturer. In some embodiments, the package 110 can include an access hole 112 that allows the HCP to trigger a launch function on the end user medical device 108 (eg, pressing a start button 114) Device 108 is still contained within package 110.

In operation, the setup synchronization device 102 is initially connected to the host computer 104 (for example, by a USB port in the host computer 104). In some embodiments, after connecting to the host computer 104, the application executing on the setup synchronization device 102 checks to see if the host computer 104 has the host computer application installed. If not, the host computer application can be installed on the host computer 104 automatically (or with HCP authorization).

Once the host computer application is installed, the host computer application will execute in the background of the host computer 104 while waiting for the setup synchronization device 102 to request time and setup parameters. As long as the setup synchronization device 102 is connected to the host computer 104, the setup synchronization device 102 will scan the terminal user. The medical device 108 is synchronized. The host application operates to provide a user interface to the HCP for configuring parameters of the medical device. The host application can include any number of graphical user interface (GUI) controls to allow HCP to select parameter values (eg, time zone, measurement unit, alert alert, target zone level, mode of operation, sample rate, Blood glucose measurement data, patient information, etc.).

In some embodiments, the end user medical device 108 can be in a low power consumption mode (eg, in a "deep sleep" mode) or in an "off" state. In both cases, the RTC within the end user medical device 108 is not executed. The activation button 114 is pressed via the package access opening 112 to trigger an activation function that switches the end user medical device 108 to the active mode and/or powers the device 108 to an "on" state. The end user medical device 108 initiates and begins to "advertize" by broadcasting a wireless signal that uniquely identifies the device 108 and requests synchronization from any of the set up synchronization devices 102 within the broadcast range. Both data. If the setup synchronization device 102 coupled to the host computer 104 is within range, the synchronization device 102 is set up to establish a wireless connection 106 with the device 108.

Once the end user medical device 108 is connected to the setup synchronization device 102, the device 102 receives the correct time and setup parameters from the host application executing on the host computer 104 via the wireless connection 106 between the device 102 and the device 108. The host computer 104 thereby synchronizes with the end user medical device 108. In some embodiments, once synchronization is complete, a message or other indicia can be displayed on the host computer 104 and/or can be displayed on the terminal. The user's medical device 108 is on the display. In some embodiments, an indicator light or other indicia can be included on the setting synchronization device 102 and/or can be included on the end user medical device 108 to indicate a wireless connection status and/or a synchronization status. After the synchronization is completed, the end user medical device 108 can automatically disconnect from the setup synchronization device 102 and return to a lower power consumption state (but with the RTC currently being executed) (eg, "shallow sleep" mode). The setup sync device 102 can return to a scan state so that the next end user medical device 108 can be synchronized.

Referring now to Figures 2 and 3, the details of setting up the synchronization device 102 are illustrated and described. FIG. 2 depicts an enlarged perspective view of an example embodiment of setting up synchronization device 102. An example embodiment includes a housing 202 that encloses and protects the circuitry (not visible in Figure 2, but see Figure 3). The example setup synchronization device 102 depicted in FIG. 2 also includes a configuration switch 204 (eg, a dual in-line package (DIP) switch) for setting certain parameters of the device 102. And an indicator 206 (eg, a three-color LED light) that indicates the state in which the synchronization device 102 is set.

For example, in some embodiments, configuration switch 204 can be used to target parameters (eg, time zone, measurement unit, alert alert enable/disable, etc.) to be delivered to end user medical device 108, etc. ) to set the value. In some embodiments, the indicator 206 can display different colors to reflect, for example, the following operations performed by the synchronization device 102: (1) scanning the end user medical device 108 for synchronization; (2) utilizing wireless Connected to the end user medical device 108, or (3) completed for the end user medical device 108 The steps for line synchronization. The example setup synchronization device 102 depicted in FIG. 2 also includes a connector 208 (eg, a USB connector) for coupling the setup synchronization device 102 to the host computer 104.

Figure 3 is a block diagram illustrating an example embodiment of circuitry 102' for setting up synchronization device 102. Circuitry 102' can include a controller 302 (e.g., a programmed microcontroller) operatively coupled to memory 304 (e.g., non-volatile random access memory (NVRAM)), the memory The body is debugged to store instructions executed by the controller 302 and the host computer application. The controller 302 can also be operatively coupled to the transceiver 306 (eg, a Bluetooth® transceiver, a near field communication (NFC) transceiver, etc.), the transceiver comprising: a medical device for use with the end user 108 A suitable antenna 308 for wireless communication. In addition, circuit 102' can include a host computer interface 208' (e.g., a USB interface) operatively coupled to the controller 302 to facilitate communication between the set synchronization device 102 and the host computer 104.

Referring now to FIG. 4, details of an example embodiment of initial communication between setting up synchronization device 102 and host computer 104 are illustrated in block diagram 400. The setup sync device 102 is initially connected to the host computer 104 (402), and the setup sync device 102 checks the host computer 104 to determine if the host computer application has been installed on the host computer 104 (404). The host computer 104 receives the request and responds (406). If the application has not been installed, the setup sync device 102 uploads the application to the host computer 104 (408), and the host computer installs the application (410). Since the application has been installed, the synchronization device 102 is set to start scanning the terminal user. The medical device 108 performs synchronization (412), and the host computer 104 executes an application (414) as a background program.

Figure 5 illustrates an example embodiment of the details of the synchronization procedure over time. This example is depicted in block diagram 500: an HCP that sets up the synchronization device 102, operates the host computer 104 (with the setup synchronization device 102 and the associated application installed), and the end user medical device 108 that are related to each other. Activities, such as three concurrently executed levels of process flow (which occur over time). Initially, the synchronization device 102 is set to scan the end user medical device 108 for synchronization (502), and the end user medical device 108 is in a low power consumption (eg, deep sleep) mode (where RTC is not executed) (504). After the HCP presses the activation button 114 (506) located on the end user medical device 108, the end user medical device 108 begins "advertising" (508), and the synchronization device 102 is set to discover the end user medical device. 108 (510). Once the communication connection 106 is established, the setup synchronization device 102 is synchronized with the end user medical device 108 (512), and the end user medical device 108 is synchronized with the setup synchronization device 102 (514). Once the synchronization is complete, the HCP receives a message indicating the completion status (516). The synchronization device 102 is set back to scan another device 108 for synchronization (518), and the end user medical device 108 switches to a low power consumption (eg, shallow sleep) mode (but with an RTC being executed) (520).

Referring now to Figure 6, an example method 600 of an embodiment of the present invention is depicted in a flow chart. Initially, the synchronization device 102 is set to scan the terminal user medical device 108 for synchronization (602), and the terminal user medical device 108 is in a low power consumption (eg, deep sleep) mode (where RTC is not implemented) OK) (604). After the HCP presses the activation button 114 (606) located on the end user medical device 108, the end user medical device 108 begins "advertising" (608), and the synchronization device 102 is set to discover the end user medical device. 108 (610). Once the communication connection 106 is established (612), the synchronization device 102 is set to synchronize with the end user medical device 108 (614). Once the synchronization is complete, the HCP receives a message indicating the completion status (616). The synchronization device 102 is set back to scan another device 108 for synchronization (618), and the end user medical device 108 switches to a low power consumption (eg, shallow sleep) mode (but with an RTC being executed) (620).

The foregoing description discloses only example embodiments of the invention. Modifications of the above-disclosed devices, systems, and methods that are within the scope of the present invention will be apparent to those skilled in the art. Thus, while the invention has been described in connection with the exemplary embodiments, it should be understood that other embodiments may fall within the scope of the invention (as defined by the scope of the appended claims).

100‧‧‧ system

102‧‧‧Set up synchronization device

104‧‧‧Host computer

106‧‧‧Communication

108‧‧‧End user medical device

110‧‧‧Packaging

112‧‧‧ access hole

114‧‧‧Start button

Claims (21)

A device comprising: a controller, the controller comprising a memory; a transceiver operatively coupled to the controller; and a host computer interface, the host computer interface operating to control the control The device is coupled to a host computer, wherein the memory is operative to store instructions executable on the controller, the instructions being adapted to cause the controller to perform the following steps: using the transceiver to scan an advertised Medical device; establishing a communication connection with a medical device that issues an announcement for synchronization and, once a communication connection has been established, transmits the synchronization data to a medical device. The device of claim 1, wherein the memory is further operative to store a host application, the host application being installed on a host computer and executed on the host computer. The device of claim 2, wherein the instructions are further debugged to cause the controller to determine whether the host application is installed on the host computer. The device of claim 1, wherein the instructions are further debugged to cause the controller to synchronize an instant clock executed in the medical device receiving the synchronization data. The device of claim 4, wherein the instructions are further adapted to cause the controller to transmit configuration parameter values to the medical device, and to configure the medical device based on the configured parameter values. The device of claim 4, wherein the instructions are further debugged such that the controller facilitates a connected host computer to display a synchronization completion indication once the medical device has been synchronized. The device of claim 4, wherein the instructions are further debugged such that the controller returns to a scan mode once the medical device has been synchronized. A system comprising: an end user medical device, the end user medical device comprising an activation function for causing the medical device to be in an announcement mode for requesting synchronization; and a setting synchronization device, the setting The synchronization device includes: a controller including a memory; a transceiver operatively coupled to the controller; and a host computer interface, the host computer interface operates to the controller The memory is coupled to a host computer, wherein the memory is operative to store instructions executable on the controller, the instructions being debugged to cause the controller to use the transceiver to scan an advertised medical device. The system of claim 8 further comprising: a host computer executing a host application adapted to allow a health care provider to configure the end user medical device. The system of claim 8, wherein the instructions are further debugged to cause the controller to establish a communication connection with the medical device once the medical device issues an announcement for synchronization, and once established A communication connection transmits synchronization data to the medical device. The system of claim 10, wherein the memory is further operative to store a host application, the host application being installed on a host computer and executed on the host computer. The system of claim 11, wherein the instructions are further adapted to cause the controller to determine whether the host application is installed on the host computer. The system of claim 10, wherein the instructions are further adapted to cause the controller to synchronize an instant clock executed in the medical device receiving the synchronization data. The system of claim 13, wherein the instructions are further debugged to cause the controller to transmit configuration parameter values to the medical device and to configure the medical device based on the configured parameter values. The system of claim 13 wherein the instructions are further debugged such that the controller facilitates a connected host computer to display a synchronization completion indication once the medical device has been synchronized. The system of claim 13 wherein the instructions are further adapted such that the controller returns to a scan mode once the medical device has been synchronized. A method comprising the steps of: scanning a terminal user medical device using a setting synchronization device, the terminal user medical device issuing an announcement for synchronization; discovering a terminal user medical device, the terminal user medical device issuing Notification for synchronizing; establishing a communication connection with a discovered end user medical device; and synchronizing the connected end user medical device. The method of claim 17, further comprising the step of displaying an indication that the end user medical device has been synchronized. The method of claim 17, further comprising the step of returning to scan another end user medical device, the other end user medical device issuing an announcement for synchronization. The method of claim 17, further comprising the step of determining whether a host computer connected to the set sync device has an installed host application. The method of claim 17, wherein the step of synchronizing the connected end user medical device comprises the step of configuring the connected end user medical device with the configuration parameter value.