Method for continuously measuring blood glucose using a sensor module, and medical device management system using the same

Abstract

Disclosed is a sensor module management system comprising a sensor module including a transcutaneous analyte sensor configured to perform a measurement indicating an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor, and a mobile device configured to wirelessly communicate with the sensor electronics unit. The sensor module is configured to, when it is confirmed that a command array included in a sub-advertisement event received from the mobile device includes a first command designating a group ID to which the sensor module belongs and a device ID of the sensor module, transmit a first response to the mobile device in response to the first command. The first response includes the analyte level.

Description

METHOD FOR CONTINUOUSLY MEASURING BLOOD GLUCOSE USING A SENSOR MODULE, AND MEDICAL DEVICE MANAGEMENT SYSTEM USING THE SAME

[0001] This application claims priority based on Korean Patent Application No. 10-2024-0152041 filed on October 31, 2024, and Korean Patent Application No. 10-2024-0104226 filed on August 05, 2024, the disclosures of which are incorporated herein by reference in their entirety.

[0002] The present invention relates to a technology for continuously measuring blood glucose using a sensor module equipped with a sensor that penetrates the user's skin, and for transmitting the measured blood glucose information from the sensor module to a mobile device. In particular, the present invention relates to a technology that supports energy-efficient bidirectional communication in a one-to-many topology composed of a plurality of sensor modules and a mobile device. The present invention also relates to a technology for providing commands to a medical device that obtains patient data or performs patient treatment, and for integrally managing responses of the medical device to such commands.

[0003] Continuous glucose monitoring system (CGMS) is a technology for monitoring changes in a patient's blood glucose in real time, in which a sensor inserted under the patient's skin measures blood glucose levels and transmits the data to a user terminal via wireless communication. Such a system allows early detection of rapid blood glucose changes or dangerous blood glucose levels by monitoring in real time, thereby enabling the patient to take immediate action. CGMS plays an important role in managing the health of diabetic patients, enabling more precise management of daily blood glucose checks and insulin administration.

[0004] In a CGMS system, since the sensor module must operate for a long period while being inserted under the patient's skin, a low-power design is essential. The sensor module has limited battery life, and it is necessary to maximize energy efficiency so that it can be used for a long time without replacing or charging the battery. For this purpose, it is important to minimize the power consumption of the sensor module and manage power efficiently during the data collection and transmission process.

[0005] Furthermore, in the case where a single user terminal is designed to receive patient data from a plurality of sensor modules, a method is required in which each sensor module can maintain low power while communicating.

[0006] The present invention aims to provide a medical device management technology that can group medical devices and reduce power consumption of each medical device in a communication environment having a one-to-many topology including a plurality of medical devices such as sensor modules and a user terminal.

[0007] The present invention may provide a medical device management method and a system using the same, employing a low-energy logical transmission method that enables energy-efficient bidirectional communication in a large-scale one-to-many topology including a plurality of medical devices and a single user terminal.

[0008] According to one aspect of the present invention, a sensor module management system may be provided, comprising: a sensor module including a transcutaneous analyte sensor configured to perform a measurement representing an analyte level, and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor; and a mobile device configured to wirelessly communicate with the sensor electronics unit. The sensor electronics unit includes a first memory, a first controller, and a first transceiver configured to wirelessly transmit sensor information related to the measurement representing the analyte level using a predetermined communication protocol. The mobile device includes a second memory, a second controller, and a second transceiver configured to wirelessly receive the sensor information transmitted by the sensor electronics unit using the communication protocol. The sensor module is configured to transmit a first response to the mobile device when it is confirmed that a first command, in which a group ID to which the sensor module belongs and a device ID of the sensor module are designated, is included in a command array included in a sub-event advertisement received from the mobile device. The first response includes the analyte level.

[0009] At this time, the sensor electronics unit is configured to determine the analyte level using the data output from the transcutaneous analyte sensor, and the first controller may be configured to receive and process the measurement value representing the analyte level from the transcutaneous analyte sensor.

[0010] In this case, the command array includes a plurality of commands including the group ID and the first command sequentially arranged, and a time section allocated to the sub-event advertisement defines a plurality of response slots in time order. The sensor module may be configured to transmit the first response during a response slot corresponding to the order of the first command in the array among the plurality of response slots.

[0011] Each of the plurality of commands may independently designate a device ID associated with the corresponding command, and the command array may include pair information of each command and the device ID designated by each command among the plurality of commands.

[0012] In this case, to synchronize a set of sensor modules having a set of device IDs designated by the plurality of commands with the mobile device, the mobile device may be configured to transmit synchronization information to the set of sensor modules before broadcasting the sub-event advertisement.

[0013] Prior to receiving the sub-event advertisement, the mobile device may match and pre-designate the group ID to the sensor module, and when the mobile device transmits the pre-designated group ID to the sensor module, the sensor module may register the group ID. The mobile device may be configured to schedule transmission of the sub-event advertisement and provide the transmission schedule to the sensor module, and transmit the sub-event advertisement according to the transmission schedule. The sensor module may be synchronized with the mobile device to receive only during the time section in which the sub-event advertisement is transmitted.

[0014] The sensor module may be a transmitter as a continuous glucose sensor module for CGMS (Continuous Glucose Monitoring System), the analyte level may be a blood glucose level, the transcutaneous analyte sensor may be a blood glucose sensor, and at least a portion of the blood glucose sensor may be disposed under the patient's skin and configured to detect the patient's blood glucose level.

[0015] According to another aspect of the present invention, a medical device management method may be provided in a medical management system including a set of medical devices and a mobile device configured to wirelessly communicate with the set of medical devices, the method managing communication between the set of medical devices and the mobile device. The method includes: a first medical device among the set of medical devices receiving a first sub-event advertisement transmitted by the mobile device and analyzing a first command array included in the first sub-event advertisement; the first medical device checking whether the first command array includes a first command designating a first group ID to which the first medical device belongs and a first device ID of the first medical device; and the first medical device transmitting a first response to the mobile device if it is confirmed that the first command array includes the first group ID and the first command.

[0016] In this case, the first medical device may be a transmitter including a transcutaneous analyte sensor configured to perform a measurement representing an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor. The first response may include the analyte level.

[0017] In this case, the first medical device may be an insulin pump, and the first response may include information on the amount of insulin administered to the patient by the insulin pump. In this case, the set of medical devices may include the first medical device and a second medical device. The first medical device may store the first group ID, and the second medical device may store a second group ID different from the first group ID. The method may further include: the second medical device receiving a second sub-event advertisement transmitted by the mobile device and analyzing a second command array included in the second sub-event advertisement; the second medical device checking whether the second command array includes a second command designating the second group ID to which the second medical device belongs and a second device ID of the second medical device; and the second medical device transmitting a second response to the mobile device if it is confirmed that the second command array includes the second group ID and the second command. In this case, one of the first medical device and the second medical device may be a transmitter including a transcutaneous analyte sensor configured to perform a measurement representing an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor. The other one of the first medical device and the second medical device may be an insulin pump.

[0018] In this case, the set of medical devices may include the first medical device and a third medical device. Both the first medical device and the third medical device may store the first group ID. The method may further include: the third medical device receiving the first sub-event advertisement and analyzing the first command array; the third medical device checking whether the first command array includes a third command designating the first group ID and a third device ID of the third medical device; and the third medical device transmitting a third response to the mobile device if it is confirmed that the first command array includes the first group ID and the third command. At this time, the transmission order between the first response and the third response may be determined according to the arrangement order of the first command and the third command in the first command array.

[0019] According to the present invention, it is possible to provide a medical device management technology that can group medical devices and reduce power consumption of each medical device in a communication environment having a one-to-many topology including a plurality of medical devices such as sensor modules and a user terminal.

[0020] FIG. 1 is a conceptual diagram showing a continuous blood glucose monitoring system according to an embodiment of the present invention.

[0021] FIGS. 2A and 2B are diagrams showing an applicator according to an embodiment of the present invention.

[0022] FIG. 3 is a diagram for explaining an operation of attaching a transmitter to the skin using the applicator.

[0023] FIG. 4 is a diagram for explaining an operation of detaching the applicator from the skin after the transmitter is attached.

[0024] FIGS. 5A and 5B illustrate an environment in which a medical device management system provided according to an embodiment of the present invention is used.

[0025] FIG. 6A shows a one-to-many topology in which a plurality of medical devices are communicatively connected to a single mobile device according to an embodiment of the present invention.

[0026] FIG. 6B shows another one-to-many topology in which a plurality of medical devices are communicatively connected to a single mobile device according to another embodiment of the present invention.

[0027] FIG. 7 shows an example of a user input / output interface provided on a screen of a mobile device to assign groups to a plurality of medical devices according to an embodiment of the present invention.

[0028] FIG. 8 shows a process performed on the screen of the mobile device when a user selects a device ID registration button shown in FIG. 7.

[0029] FIGS. 9A and 9B respectively show examples of a process on the screen of the mobile device when a user selects a group ID registration button shown in FIG. 7 in a state where a device ID that may be displayed in the device ID window shown in FIG. 7 has been determined.

[0030] FIG. 10 shows a basic structure of a communication protocol in which a mobile device and a plurality of medical devices execute bidirectional communication according to an embodiment of the present invention.

[0031] FIG. 11 shows PDU transmission that occurs when a mobile device gives a command to a single medical device in a medical device management system provided according to an embodiment of the present invention.

[0032] FIG. 12 shows PDU transmission that occurs when a mobile device gives commands to a plurality of medical devices in a medical device management system provided according to an embodiment of the present invention.

[0033] FIG. 13 shows an example of the configuration of the medical device and mobile device presented in FIGS. 5A and 5B.

[0034] FIG. 14 shows a network communication relationship between the mobile device in FIG. 13 and a predetermined server.

[0035] FIG. 15 is a flowchart illustrating a medical device management method provided according to an embodiment of the present invention.

[0036] FIG. 16 is a flowchart illustrating a medical device management method provided according to another embodiment of the present invention.

[0037] FIG. 17 illustrates an example environment in which a medical device management system supporting bidirectional communication in a one-to-many topology composed of a plurality of medical devices and a mobile device is applied according to an embodiment of the present invention.

[0038] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described in this specification and may be implemented in various other forms. The terms used in this specification are intended to facilitate understanding of the embodiments and are not intended to limit the scope of the present invention. Also, singular forms used hereafter shall be understood to include plural forms unless the context clearly indicates otherwise.

[0039] FIG. 1 is a conceptual diagram showing a continuous blood glucose monitoring system according to an embodiment of the present invention.

[0040] Referring to FIG. 1, the continuous blood glucose monitoring system according to an embodiment of the present invention may include transmitter 110 and mobile device 200.

[0041] Transmitter 110 is attached to the body of user 1, and when transmitter 110 is attached to the user's body, one end of a sensor of transmitter 110 is inserted into the skin to periodically measure blood glucose from body fluid.

[0042] Mobile device 200 may be an electronic device capable of receiving blood glucose information from transmitter 110 and displaying the received blood glucose information to the user. For example, mobile device 200 may be an electronic device capable of communicating with transmitter 110, such as a dedicated receiver, smartphone, tablet PC, notebook, medical device, or wearable device. Of course, mobile device 200 is not limited to this, and the mobile device 200 of the present disclosure may include various electronic devices that include a communication function and can have a program or application installed.

[0043] Transmitter 110 may transmit the blood glucose information to mobile device 200 either upon request from mobile device 200 or by periodically measuring at predetermined intervals. Transmitter 110 and mobile device 200 may be connected via wired or wireless communication for data transmission.

[0044] For example, in the case of a wired communication connection, transmitter 110 and mobile device 200 may be connected via at least one communication method such as USB (Universal Serial Bus), serial port, Ethernet, or HDMI (High-Definition Multimedia Interface).

[0045] For example, in the case of a wireless communication connection, transmitter 110 and mobile device 200 may be connected via at least one communication method such as Bluetooth, Bluetooth Low Energy, IrDA (Infrared Data Association), UWB (Ultra WideBand), WiFi Direct, or NFC (Near Field Communication).

[0046] Here, transmitter 110 is attached to a part of the body via applicator 100. FIGS. 2A and 2B are diagrams showing applicator 100 according to an embodiment of the present invention. Specifically, FIG. 2A shows a state in which cap 130 is mounted, and FIG. 2B shows a state in which cap 130 is removed.

[0047] Referring to FIG. 2A, applicator 100 may include upper housing 120, a button configured to be inserted and pressed on the outer circumferential surface of upper housing 120, and cap 130 that can be attached to and detached from upper housing 120.

[0048] Referring to FIG. 2B, when cap 130 of applicator 100 is removed from upper housing 120, a part of lower housing 140 may be exposed. By removing cap 130, applicator 100 may become ready for use by the user.

[0049] Transmitter 110 may be provided inside applicator 100. For example, applicator 100 may be formed in a shape with one open side, and transmitter 110 may be installed in applicator 100 through the open side. Applicator 100 may operate such that transmitter 110 is discharged outward by user 1's manipulation, and transmitter 110 is attached to a specific body part of user 1.

[0050] When attaching transmitter 110 to a body part (e.g., skin 2) using applicator 100, in order to insert one end of the sensor provided in transmitter 110 into the skin, applicator 100 may include a needle (not shown), a first elastic member (not shown), and a second elastic member (not shown). For example, the needle may be formed to enclose one end of the sensor. For example, the first elastic member may push the needle and sensor end together into the skin so that the sensor end is inserted into the skin. For example, the second elastic member may pull the needle out of the skin after the sensor end is inserted.

[0051] Specifically, by releasing the compression of the first elastic member disposed in a compressed state inside applicator 100, the needle and sensor end may be inserted into the skin simultaneously. After the sensor end is inserted into the skin, only the needle may be withdrawn from the skin by releasing the compression of the second elastic member (not shown). In this manner, the user can safely and easily attach transmitter 110 to the skin using applicator 100.

[0052] FIG. 3 is a diagram for explaining the operation of attaching transmitter 110 to skin 2 using applicator 100, and FIG. 4 is a diagram for explaining the operation of detaching applicator 100 from skin 2 after transmitter 110 is attached.

[0053] Looking at the process of attaching transmitter 110 to the body with reference to FIGS. 3 and 4, in a state where cap 130 is removed, the open side of applicator 100 (e.g., lower housing 140) may be closely adhered to a specific body area, such as skin 2. When applicator 100 is operated while being in contact with skin 2 of the body, transmitter 110 discharged from applicator 100 may be attached to skin 2.

[0054] At the bottom of transmitter 110, one end of the sensor may be exposed and arranged so as to protrude from transmitter 110. As applicator 100 is operated, one end of the sensor may be inserted into skin 2 through the needle provided in applicator 100. Accordingly, transmitter 110 may be attached to skin 2 with one end of the sensor inserted into skin 2.

[0055] On the body contact surface of transmitter 110, an adhesive material (e.g., adhesive tape) may be provided to fix transmitter 110 to skin 2. Therefore, after applicator 100 is operated, when applicator 100 is detached from skin 2, transmitter 110 may be fixed (or attached) to skin 2 by the adhesive force of the adhesive material.

[0056] When power is applied to transmitter 110 in a state attached to skin 2, transmitter 110 may be connected to mobile device 200 using a predetermined communication method for data communication. For example, transmitter 110 may transmit the measured blood glucose information to mobile device 200 using a predetermined communication method.

[0057] The transmitter 110 of the present disclosure can measure various types of biometric information such as lactate, ketones, oxygen saturation, carbon dioxide level, heart rate, or blood pressure, in addition to blood glucose information. However, in the following description, it is assumed that transmitter 110 measures blood glucose information as an example of biometric information.

[0058] According to an embodiment of the present invention, the medical device management system 1 may include a plurality of medical devices 10 and one mobile device 200 in a one-to-many topology.

[0059] FIGS. 5A and 5B illustrate environments in which the medical device management system provided according to an embodiment of the present invention is used.

[0060] Medical device 10 may be configured to perform bidirectional communication using a wireless communication protocol with mobile device 200. The wireless communication protocol may be any of the various wireless communication methods described above, but is not limited thereto.

[0061] Mobile device 200 may provide predetermined information or commands to medical device 10.

[0062] As shown in FIG. 5A, mobile device 200 may communicate with service server 300 connected to metropolitan network 500 via wireless mobile communication base station 510. Alternatively, as shown in FIG. 5B, mobile device 200 may communicate with service server 300 connected to metropolitan network 500 via WiFi access point 520.

[0063] Mobile device 200 may provide information obtained from medical device 10 or information related to medical device 10 to service server 300.

[0064] Although FIGS. 5A and 5B illustrate a state in which only one medical device 10 is connected to mobile device 200, a plurality of medical devices 10 may be communicatively connected to a single mobile device 200 as shown in FIGS. 6A or 6B.

[0065] FIG. 6A shows a one-to-many topology in which a plurality of medical devices 10 are communicatively connected to a single mobile device 200 according to an embodiment of the present invention.

[0066] As shown in the example of FIG. 6A, the plurality of medical devices 10 connected to a single mobile device 200 may all be medical devices of the same type (homogeneous).

[0067] FIG. 6B shows a one-to-many topology in which a plurality of medical devices 10 are communicatively connected to a single mobile device 200 according to another embodiment of the present invention.

[0068] As shown in the example of FIG. 6B, the plurality of medical devices 10 connected to a single mobile device 200 may be medical devices classified into different groups having different types.

[0069] In the example shown in FIG. 6B, the first group of medical devices indicated by reference numerals 11 to 13 may be, for example, the transmitters 110, and the second group of medical devices indicated by reference numerals 14 to 15 may be insulin pumps. Since the transmitter and the insulin pump have different medical purposes or functions, they may be regarded as different types of devices and grouped separately.

[0070] Although two groups of medical devices are exemplified in FIG. 6B, the plurality of medical devices 10 connected to a single mobile device 200 may be classified into three or more groups.

[0071] Among the plurality of groups, medical devices of some groups may be devices that obtain information from the patient, and medical devices of other groups may be devices that provide information to the patient or perform patient treatment.

[0072] In one embodiment of the present invention, even if some of the plurality of medical devices 10 have different hardware versions or firmware versions from others, if they have the same medical purpose or function, they may still be considered as homogeneous regardless of their version.

[0073] In one embodiment of the present invention, at least some of the set of medical devices 10 communicating with mobile device 20 may be transmitters 110.

[0074] Additionally, in one embodiment of the present invention, the medical device management system 1 may be a continuous blood glucose monitoring system including the above-described transmitter 110 and mobile device 200, or may include the continuous blood glucose monitoring system.

[0075] FIG. 7 shows an example of a user input / output interface provided on a screen of mobile device 200 to assign groups to a plurality of medical devices according to an embodiment of the present invention.

[0076] First window 210 displays matching information between a device ID and an assigned group ID shown in first window 210. If the device ID and group ID are not specified, specific values (e.g., identification codes) are not displayed in first window 210. FIG. 7 shows a state in which specific values of the device ID and group ID are not displayed.

[0077] On the screen of mobile device 200, device ID registration button ("Input DID") 221 may be provided to prompt the user to start a first registration process (i.e., device ID registration process) for registering the device ID of a given medical device 10 in mobile device 200.

[0078] In addition, on the screen of mobile device 200, group ID registration button ("Assign GID") 222 may be provided to prompt the user to start a second registration process (i.e., group ID registration process) for matching a specific group ID to the registered device ID and registering it to the medical device 10.

[0079] In one embodiment, group ID registration button 222 may be activated only when a device ID for the medical device 10 to which the group ID is to be assigned has already been input.

[0080] FIG. 8 shows a process performed on the screen of mobile device 200 when the user selects device ID registration button 221 shown in FIG. 7.

[0081] When the user selects device ID registration button 221, a device ID input window 2210 may be displayed on the screen of mobile device 200. Device ID input window 2210 may provide the user with one or more input options on the screen for entering the device ID of the medical device to be registered in mobile device 200.

[0082] In the example shown in FIG. 8, QR code scan button ("Scan QR Code") 2211 is provided as one input option to initiate the procedure of acquiring QR code information by photographing the QR code presented on the surface of medical device 10 or on the surface of the product package of medical device 10 using the camera of mobile device 200.

[0083] Also, in the example shown in FIG. 8, serial code input button ("Enter Serial No.") 2212 is presented as another input option to initiate the procedure of manually inputting the serial number shown on the surface of medical device 10 or on the product package surface of medical device 10 through another text input interface of mobile device 200.

[0084] Although not shown, a two-dimensional barcode may be used instead of the QR code. Also, the QR code or barcode may be recognized not by a camera connected to mobile device 200 but by another type of optical scanner connected to mobile device 200.

[0085] In one embodiment, the QR code, barcode, or serial number may be the device ID assigned to medical device 10. In this case, when mobile device 200 obtains the QR code, barcode, or serial number, the device ID may be registered in mobile device 200, and the device ID may be displayed in device ID window 211. In the example of FIG. 8, the device ID is illustrated as 3Dx482dA4.

[0086] In another embodiment, the QR code, barcode, or serial number may not be the device ID assigned to medical device 10, but another identification information for identifying medical device 10. In this case, mobile device 200 may connect to medical device 10 using the identification information and receive the device ID of medical device 10 stored in the connected medical device 10. Alternatively, mobile device 200 may provide the identification information to service server 300, and service server 300 may extract the device ID of medical device 10 stored in association with the identification information and provide the extracted device ID to mobile device 200. In this case as well, when mobile device 200 obtains the device ID, the device ID may be registered in mobile device 200 and displayed in device ID window 211. In the example of FIG. 8, the device ID is illustrated as 3Dx482dA4.

[0087] FIG. 8 shows a state in which the device ID of medical device 10 to be registered by the user is registered, but no specific group has yet been assigned to medical device 10.

[0088] FIGS. 9A and 9B respectively show an example of the process performed on the screen of mobile device 200 when the user selects group ID registration button 222 shown in FIG. 7 in a state where the device ID to be displayed in device ID window 211 has been determined.

[0089] When the user selects group ID registration button 222, group ID input window 2220 may be displayed on the screen of mobile device 200.

[0090] Group ID input window 2220 may include information window 2221 displaying the device ID of the medical device 10 for which the user wants to register a group ID.

[0091] Group ID input window 2220 may also include group ID input interface 2222 provided to allow the user to input the group ID to be assigned to the medical device 10 shown in information window 2221.

[0092] In one embodiment, when the user selects group ID input interface 2222, mobile device 200 may provide the user with a user interface (e.g., keyboard) for directly inputting the group ID. The user may directly input the desired group ID via this user interface. For example, if the medical device 10 is used by a patient hospitalized in room 215 of a hospital, the user may input "215" as the group ID.

[0093] In another embodiment, when the user selects group ID input interface 2222, mobile device 200 may transmit the device ID shown in information window 2221 to service server 300. Then, service server 300 may return a predefined group ID associated with the received device ID to mobile device 200, and mobile device 200 may input the returned group ID.

[0094] In yet another embodiment, when the user selects group ID input interface 2222, mobile device 200 may activate a camera or optical scanner capable of scanning a group ID, and the user may input the group ID by scanning it using the camera or optical scanner. For example, the group ID may be the room number "215" written on the nameplate attached to the door of hospital room 215.

[0095] Although the example above describes using a hospital room number as the group ID, the present invention is not limited thereto. For example, the group ID may also be set as specific information recorded in the patient's medical chart who uses the transmitter.

[0096] In one embodiment of the present invention, mobile device 200 may provide a first option and a second option for registering the group ID input via group ID input interface 2222 in association with the device ID shown in information window 2221. The first option and the second option may be executed, for example, by selecting first button ("Set") 2223 and second button ("Set (with device type)") 2224, respectively, as shown in FIG. 9A.

[0097] Referring to FIG. 9A, in the first option, the group ID input by the user via group ID input interface 2222 is directly registered in association with the device ID shown in information window 2221. For this, after the user inputs a specific group ID into mobile device 200 via group ID input interface 2222, selecting first button 2223 completes the registration.

[0098] Referring to FIG. 9B, in the second input option, supplementary information is combined with the group ID input by the user via group ID input interface 2222 to generate a corrected group ID. The corrected group ID is then registered in association with the device ID shown in information window 2221.

[0099] Here, the supplementary information may be a value indicating the device type of medical device 10 having the device ID shown in information window 2221. In the example of FIG. 9B, the device type is illustrated as the string "T1" (reference numeral 212 in FIG. 9B).

[0100] Mobile device 200 may acquire the specific value of the device type in various ways.

[0101] In a first embodiment, when the user selects second button 2224, mobile device 200 may provide a user input interface that allows the user to input the device type. This user input interface may allow the user to freely input the device type or present several predefined device types for the user to choose from.

[0102] In a second embodiment, when the user selects second button 2224, mobile device 200 may determine the device type by analyzing the device ID shown in information window 2221 or by analyzing the QR code, barcode, or serial number. For this purpose, the device ID, QR code, barcode, or serial number may include information from which the device type can be extracted. Alternatively, mobile device 200 may provide the device ID, QR code, barcode, or serial number to service server 300 and determine the device type with the assistance of service server 300. For example, server 300, upon receiving the device ID, QR code, barcode, or serial number from mobile device 200, may process the device ID, QR code, barcode, or serial number and / or refer to its database, determine a corresponding device type, and then send the corresponding device type to mobile device 200.

[0103] As described above, when the group ID to be matched with the device ID shown in information window 2221 is finally determined, the group ID may be displayed in group ID window 212.

[0104] Although FIGS. 9A and 9B illustrate examples in which information window 2221 is displayed, in another embodiment, information window 2221 may not be shown. It can be understood that the device ID shown in information window 2221 of FIGS. 9A and 9B is the same as the device ID that may be shown in device ID window 211 of FIG. 8.

[0105] In FIG. 9B, reference numeral 212 presents the string "T1" as the supplementary information. "T1" may represent a transmitter-type medical device, for example. To aid understanding, if the string "315" presented in reference numeral 212 of FIG. 9B means hospital room number 315, then the string "315 / T1" may represent a group assigned to a transmitter-type device provided to the patient in room 315.

[0106] Although "T1" is illustrated above as representing a transmitter-type medical device, it is not limited thereto. That is, "T1" may represent a medical device type different from an insulin pump, for example.

[0107] According to an embodiment, a group that is determined and input by the user according to FIGS. 9A and 9B and corresponding descriptions may correspond to the group described in reference to FIG. 6B.

[0108] Through FIGS. 7, 8, 9A, and 9B, a process was described in which the device ID of a given medical device 10 is obtained and registered in mobile device 200, and a specific group ID is matched and registered to the device ID. This process is one possible configuration for executing a medical device management method for managing a plurality of medical devices provided according to an embodiment of the present invention, which will be described later. The method of determining the device ID and its group ID of medical device 10 may be modified or differ from the above-described embodiment.

[0109] FIG. 10 shows the basic structure of a communication protocol in which a mobile device and a plurality of medical devices execute bidirectional communication according to an embodiment of the present invention.

[0110] According to the communication protocol, the mobile device transmits periodic advertising signals with a predetermined interval. In this specification, the mobile device may be referred to as a host. In one embodiment of the present invention, periodic advertising may also be referred to as regular advertising.

[0111] The periodic advertising may be divided into a main advertisement and multiple sub-advertisements included in each main advertisement.

[0112] When the mobile device generates a main advertisement once, an event called a "main advertisement event" is considered to have occurred once. The mobile device may generate or execute an event or activity to transmit the main advertisement. The event or activity during which the main advertisement is transmitted may be referred to as the main advertisement event. The main advertisement may be generated periodically with the same predetermined interval or period.

[0113] The transmitter that receives the main advertisement may respond to the main advertisement.

[0114] The main advertisement event may occur at regular intervals. Random variation may not be allowed in the scheduling of the main advertisement event. Each main advertisement event may begin at a predetermined main advertisement interval.

[0115] Each main advertisement event is composed of multiple sub-advertisement events, and advertisement packets may be transmitted during the sub-advertisement events. In other words, the concept of a main advertisement event is further specified by a plurality of sub-advertisement events. Each sub-advertisement event may be generated regularly with a predetermined interval or period. A sub-advertisement event may be referred to as a sub-event advertisement event.

[0116] The mobile device may set, for example, up to 128 sub-advertisement events per main advertisement event. Each sub-advertisement event may begin at a predetermined sub-advertisement interval.

[0117] Between two adjacent main advertisement events, a plurality of sub-advertisement events may occur periodically.

[0118] In this specification, the main advertisement interval may be referred to as a first time interval, and the sub-advertisement interval may be referred to as a second time interval (where the first time interval > second time interval).

[0119] In one embodiment of the present invention, the main advertisement interval may be determined as a fixed specific value. In that case, the mobile device may determine the number of sub-advertisement events per main advertisement event and may set the sub-advertisement interval.

[0120] Information about the number of sub-advertisement events per main advertisement event and the sub-event interval set by the mobile device may be transmitted to the medical devices.

[0121] When multiple medical devices are registered in mobile device 200, each of the multiple medical devices may be configured to receive main advertisement events and sub-advertisement events included in the main advertisement events periodically in a regular interval or period in a synchronized manner. Periodic sending the main advertisement events and sub-advertisement events by mobile device 200 and periodic receiving and processing of the main advertisement event and sub-advertisement events by medical devices are described further below.

[0122] FIG. 11 shows the PDU (Packet Data Unit) transmission that occurs when the mobile device issues a command to one medical device in the medical device management system provided according to an embodiment of the present invention.

[0123] The medical device management system 1 may include a plurality of medical devices 10 having a one-to-many topology and a single mobile device 200.

[0124] During the time section of one sub-advertisement event, mobile device 200 may broadcast a predetermined command. This command may include information indicating one group ID, information indicating the device ID of one of the medical devices having the specified group ID, and information indicating the command to be given to the device ID. In the example of FIG. 11, with respect to sub-advertisement event #1, the group ID, device ID, and command are respectively indicated as 'GID=2', 'DID=2', and 'cmd'.

[0125] In this specification, the group ID may be denoted as GID and the device ID as DID.

[0126] The command that includes one group ID, one device ID, and cmd may form a one PDU and may be referred to as one PDU command. The cmd may be a specific control command or instruction to control the corresponding medical device. The specific control command or instruction may include sensing / detecting a blood glucose of body to which the medical device is attached and / or transmitting the detected glucose to mobile device 200. The specific control command or instruction may also include setting / changing of detection / transmission schedule or intervals or synchronizing the schedule with the multiple medical devices. The specific control command or instruction may further include changing the status of the medical device, such as power on / off, a sleep mode, a standby mode, an active automatic regular transmission mode, etc. The specific control command or instruction may include detecting the blood glucose level and transmitting the detected value to the mobile device or pumping an insulin to the body in a specific amount according to the command. Thereby, mobile device 200 may control the operation of the medical device.

[0127] In FIG. 11, fifth medical device 15 is a member of GID=2. This means that it is synchronized with sub-advertisement event #1. Accordingly, mobile device 200 may generate a payload that includes one or more command arrays. In the example of FIG. 11, the command array generated by mobile device 200 is {GID=2, [DID=2, cmd]}. Here, { , } may be considered as an array. Excluding the first element GID=2, [DID=2, cmd] is the first and only command member in the array. That is, the command array includes one command: [DID=2, cmd].

[0128] This means that sub-advertisement event #1 is associated with the medical devices having GID=2, and among the medical devices with GID=2, the command expressed as "cmd" is delivered to the device having DID=2. Although the command array is broadcast and all medical devices 11 through 15 can receive it, only fifth medical device 15, which is designated by the command array, responds to it. Fifth medical device 15 may return a response corresponding to the command cmd to mobile device 200 during response slot #1 of sub-advertisement event #1.

[0129] According to an embodiment, the packet transmitted from mobile device 200 including the command array may be received simultaneously by all medical devices (14, 15) that are members of GID=2. This is because they are all synchronized and in a receiving state during sub-advertisement event #1. All other medical devices that receive the packet but are not DID=2 and GID=2 discard it. Fifth medical device 15 processes the command and transmits the response during response slot #1. Since the responded command was the first (and only) member in the command array {GID=2, [DID=2, cmd]}, medical device 15 responds in the first response slot #1.

[0130] FIG. 12 shows the PDU transmission that occurs when the mobile device issues commands to multiple medical devices in the medical device management system provided according to an embodiment of the present invention.

[0131] The medical device management system 1 may include a plurality of medical devices 10 having a one-to-many topology and a single mobile device 200.

[0132] During the time section of one sub-advertisement event, mobile device 200 may broadcast a predetermined command. This command may include information indicating one group ID, information indicating device IDs of multiple medical devices having the specified group ID, and information indicating respective commands to be issued to each of those device IDs. In the example of FIG. 12, with respect to sub-advertisement event #1, the group ID, device IDs, and commands are respectively indicated as 'GID=1', 'DID=1', 'DID=2', 'DID=3', 'cmd1', 'cmd2', and 'cmd3'.

[0133] In FIG. 12, medical devices 11 through 13 are members of GID=1. This means that they are synchronized with sub-advertisement event #1. Accordingly, mobile device 200 may generate a command array that includes one or more command elements. In the example of FIG. 12, the command array generated by mobile device 200 for sub-advertisement event #1 is {GID=1, [DID=1, cmd1], [DID=2, cmd2], [DID=3, cmd3]}. Here, { , , , } may be considered as an array. Excluding the first element GID=1, [DID=1, cmd1] is the first command member, [DID=2, cmd2] is the second, and [DID=3, cmd3] is the third. That is, the command array includes three commands: [DID=1, cmd1], [DID=2, cmd2], and [DID=3, cmd3].

[0134] This means that sub-advertisement event #1 is associated with medical devices having GID=1 and delivers the command cmd1 to the device with DID=1, cmd2 to the device with DID=2, and cmd3 to the device with DID=3. Although the command array is broadcast and all medical devices 11 through 15 can receive it, only medical devices 11 through 13 with GID=1 respond.

[0135] In more detail, the packet including the command array for sub-advertisement event #1 transmitted from mobile device 200 is received simultaneously by all medical devices 11 through 13 that are members of GID=1. This is because they are all synchronized and receiving during sub-advertisement event #1. If another medical device not shown, such as one with GID=1 and DID=5, receives the packet, it discards it.

[0136] When medical devices 11 through 15 are assigned with a group ID, such GID 1 or GID 2, by mobile device 200, devices in a same group, such as medical devices 11 through 13 in GID 1, may be configured to be synchronized to be in a standby state to receive a broadcast signal from mobile device 200 according to control of mobile device 200. For example, devices in a same group, such as medical devices 11 through 13 in GID 1, may be configured to be in a standby state in a regular schedule corresponding to the main advertisement interval or sub-advertisement interval.

[0137] First medical device 11 processes the command and transmits a first response for command cmd1 during response slot #1. Since the responded command was the first member in the command array {GID=1, [DID=1, cmd1], [DID=2, cmd2], [DID=3, cmd3]}, medical device 11 responds in response slot #1.

[0138] Second medical device 12 processes the command and transmits a second response for command cmd2 during response slot #2. Since the responded command was the second member in the command array, medical device 12 responds in response slot #2.

[0139] Third medical device 13 processes the command and transmits a third response for command cmd3 during response slot #3. Since the responded command was the third member in the command array, medical device 13 responds in response slot #3.

[0140] Response slots #1, #2, and #3 are all part of the time section of sub-advertisement event #1, and the smaller the slot number, the earlier it is arranged on the time axis.

[0141] In FIG. 12, it can be understood that the command array {GID=2, [DID=2, cmd]} generated by mobile device 200 for sub-advertisement event #2 is the same as the one shown in FIG. 11. The only difference is that in FIG. 11, it occurred as the sub-advertisement event #1.

[0142] Describing the configuration shown in FIG. 12 in another way, sub-advertisement event #1 shows the transmission of a PDU when mobile device 200 issues commands to multiple medical devices (11-13) that are members of GID=1. Sub-advertisement event #2 shows the transmission of a single command to a single medical device 15 that belongs to GID=2.

[0143] If mobile device 200 has no command to send to another medical device belonging to a group other than GID=1 or GID=2, the remaining sub-advertisement events, such as sub-advertisement event #3, may broadcast a PDU with an empty payload.

[0144] That is, while each main advertisement event includes a predetermined number of sub-advertisement events, in one main advertisement event, one or more sub-advertisement event may include a PDU with a command array with a particular GID, DID, and cmd, while a rest of sub-advertisement event may include empty payload (i.e., null value).

[0145] According to an embodiment, each medical device, at the beginning of one sub-advertisement event, may wake up from a standby mode and determine whether there is a cmd that corresponds (i.e., is directed) to itself using the GID and DID in the sub-advertisement event. If the medical device finds there is a cmd that that corresponds (i.e., is directed) to itself using the GID and DID, the medical device performs an operation according to the cmd, for example, sensing the blood glucose value and transmitting the value to the mobile device and then turns its mode to a standby mode during the rest of time in the corresponding sub-advertisement event period.

[0146] If it finds there is no cmd that corresponds (i.e., is directed) to itself using the GID and DID in a sub-advertisement event period, the medical device may change its mode to the standby mode during the entire period of the corresponding sub-advertisement period.

[0147] Also, if the medical device finds that the payload in a sub-advertisement event is empty (i.e., null), the medical device may turn into and remain in standby during the entire period of the sub-advertisement event.

[0148] According to an embodiment, one GID may be included only once in one main advertisement event, and the medical devices corresponding to the GID may turn into and remain in the standby mode during the periods of remaining subsequent sub-advertisement events after the corresponding advertisement event in the main advertisement event. Furthermore, according to an embodiment, if the payload of the first sub-advertisement period is empty (i.e., null), the medical device may turn into the standby mode during the entire period of the main advertisement period and wake up at the beginning of the next main advertisement period.

[0149] These configurations enable multiple medical devices to remain in the standby mode, which uses minimized power, especially during a time when it does not communicate with the medical device, and then wake up to check whether there is a command directed itself and perform a commended operation only when necessary.

[0150] FIG. 13 shows an example of the configuration of the medical device and the mobile device presented in FIGS. 5A and 5B.

[0151] In this specification, the medical device may also be referred to as a transmitter. The mobile device may also be referred to as a user terminal, receiver, host device or display device.

[0152] The medical device may be, for example, a device that senses and provides data from a patient like the transmitter 110, or a device that provides patient treatment such as an insulin pump.

[0153] Transmitter 110 may be regarded as a type of sensor module. Various types of sensor modules may exist, including ECG (electrocardiogram) sensors, blood pressure sensors, SpO2 (oxygen saturation) sensors, and body temperature sensors. Therefore, the present invention may be applied to applications where the medical device 10 is a sensor module of various types including the aforementioned examples.

[0154] FIG. 13 illustrates an example in which the medical device 10 is a sensor module provided for a CMS (Continuous Monitoring System).

[0155] CMS may be, for example, a CGMS (Continuous Glucose Monitoring System), and in this case, the medical device 10 may be transmitter 110.

[0156] Medical device 10 may include continuous analyte sensor 101, processor 102, communication unit 103, and memory 104.

[0157] Output signal 111 output by continuous analyte sensor 101 may be provided to processor 102. Output signal 111 may be regarded as raw data.

[0158] Processor 102 may generate analysis data based on output signal 111. The analysis data may be the output signal 111 itself, or data generated by processing output signal 111.

[0159] Mobile device 200 may include display unit 201, processor 202, communication unit 203, and memory 204.

[0160] Communication between medical device 10 and mobile device 200 may be executed using communication unit 103 of medical device 10 and communication unit 203 of mobile device 200. Communication between the medical device 10 and the mobile device 200 may be either connection-based or connectionless. In a preferred embodiment of the present invention, the communication between the medical device 10 and the mobile device 200 is connectionless.

[0161] Bluetooth technology may be used as the protocol for the communication.

[0162] Processor 202 may display the information received from medical device 10 as is, or after processing, on display unit 201 via communication unit 203. The information received by mobile device 200 from medical device 10 may include data related to the biometric analyte of a specific person. The biometric analyte may be, for example, the patient's blood glucose data. A processor in the specification may be referred to as a controller.

[0163] Preferably, communication units 103 and 203 may use short-range wireless communication protocols such as Bluetooth and NFC. However, the present invention does not exclude using wireless LAN communication, cellular network communication, or even wired communication for communication units 103 and 203. A communication unit in the specification may be referred to as a transceiver.

[0164] Medical device 10 may be transmitter 110 used according to an embodiment of the present invention or may be a non-invasive biometric data acquisition device such as a smart ring or smart watch including a sensor.

[0165] FIG. 14 shows a network communication relationship between mobile device 200 of FIG. 3 and a predetermined server.

[0166] Server 300 may include processor 302, communication unit 303, and memory 304. Mobile device 200 and server 300 may establish a data connection via a communication network such as a metropolitan network and communicate with each other. Processor 202 may process and generate analysis data acquired from medical device 10 and provide the generated first processed data to server 300 via the communication network. The first processed data may include the acquired analysis data itself, or may include data further processed from the acquired analysis data.

[0167] FIG. 15 is a flowchart illustrating a medical device management method provided according to an embodiment of the present invention.

[0168] The medical device management method is a method for managing communication between a set of medical devices and a mobile device in a medical management system including a set of medical devices comprising first medical device storing a first group ID and second medical device storing a second group ID, and the mobile device configured to wirelessly communicate with the set of medical devices. The method may include the following steps.

[0169] In step S110, the first medical device among the set of medical devices receives a first sub-event advertisement transmitted by the mobile device and analyzes a first command array included in the first sub-event advertisement.

[0170] In step S120, the first medical device checks whether the first command array includes a first command designating the first group ID to which the first medical device belongs and the first device ID of the first medical device.

[0171] In step S130, if it is confirmed that the first command array includes the first group ID and the first command, the first medical device transmits a first response to the mobile device.

[0172] In step S140, the second medical device receives a second sub-event advertisement transmitted by the mobile device and analyzes a second command array included in the second sub-event advertisement.

[0173] In step S150, the second medical device checks whether the second command array includes a second command designating the second group ID to which the second medical device belongs and the second device ID of the second medical device.

[0174] In step S160, if it is confirmed that the second command array includes the second group ID and the second command, the second medical device transmits a second response to the mobile device.

[0175] Among the first medical device and the second medical device, one may be a transmitter including a transcutaneous analyte sensor configured to perform a measurement representing an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor, and the other may be an insulin pump.

[0176] FIG. 16 is a flowchart illustrating a medical device management method provided according to another embodiment of the present invention.

[0177] The medical device management method is a method for managing communication between a set of medical devices and a mobile device in a medical management system including a set of medical devices comprising first medical device and third medical device both storing a first group ID, and the mobile device configured to wirelessly communicate with the set of medical devices. The method may include the following steps.

[0178] In step S210, the first medical device receives a first sub-event advertisement transmitted by the mobile device, analyzes a first command array included in the first sub-event advertisement, and the third medical device also receives the first sub-event advertisement and analyzes the first command array.

[0179] In step S220, the first medical device checks whether the first command array includes a first command designating the first group ID and the first device ID of the first medical device, and the third medical device checks whether the first command array includes a third command designating the first group ID and the third device ID of the third medical device.

[0180] In step S230, if it is confirmed that the first command array includes the first group ID and the first command, the first medical device transmits a first response to the mobile device, and if it is confirmed that the first command array includes the first group ID and the third command, the third medical device transmits a third response to the mobile device.

[0181] FIG. 17 illustrates an example environment in which the medical device management system supporting bidirectional communication in a one-to-many topology composed of a plurality of medical devices and a mobile device is applied according to an embodiment of the present invention.

[0182] The plurality of medical devices shown in FIG. 6A or FIG. 6B may each be worn by or disposed on different patients accommodated in a specific hospital room 81. For example, in a state where four patients are accommodated in hospital room 81, first patient, second patient, and third patient may respectively wear transmitters 11, 12, and 13 as medical devices, and third patient and fourth patient may respectively wear insulin pumps 14 and 15 as the medical devices. In this example, a medical staff user may register three transmitters 11, 12, 13 and two insulin pumps 14, 15 to mobile device 200.

[0183] That is, device IDs of transmitters 11, 12, 13 and insulin pumps 14, 15 may be registered first in mobile device 200.

[0184] Then, group IDs may be registered in association with the registered device IDs. In this example, assume that the group ID input by the user into mobile device 200 via group ID input interface 2222 for the three transmitters 11, 12, 13 and two insulin pumps 14, 15 is the room number "181" of hospital room 81.

[0185] In this case, if, as shown in FIG. 9A, the user directly registers the group ID input via group ID input interface 2222 to the device IDs in information window 2221, the five medical devices 11 to 15 including three transmitters and two insulin pumps will all be grouped into one single group (GID=181).

[0186] On the other hand, if, as shown in FIG. 9B, the user generates a corrected group ID by combining supplementary information with the group ID input via group ID input interface 2222 and registers it to the device IDs in information window 2221, the three transmitters 11, 12, 13 may be grouped into a first group (GID=181 / T1), and the two insulin pumps 14, 15 may be grouped into a second group (GID=181 / T2).

[0187] In the case where all five medical devices 11 to 15 are grouped into one single group (GID=181), for example, during sub-advertisement event #1 illustrated in FIG. 12, if mobile device 200 generates and broadcasts a command array {GID=181, [DID=1, cmd1], [DID=2, cmd2], [DID=3, cmd3], [DID=4, cmd4], [DID=5, cmd5]}, transmitters 11, 12, 13 and insulin pumps 14, 15 may respond respectively in response slots #1, #2, #3, #4, and #5. It is assumed here that the device IDs of transmitter 11, transmitter 12, transmitter 13, insulin pump 14, and insulin pump 15 are '1', '2', '3', '4', and '5' respectively.

[0188] Conversely, if transmitters 11, 12, 13 are grouped into the first group (GID=181 / T1), and insulin pumps 14, 15 are grouped into the second group (GID=181 / T2), for example, during sub-advertisement event #1 illustrated in FIG. 12, if mobile device 200 generates and broadcasts a command array {GID=181 / T1, [DID=1, cmd1], [DID=2, cmd2], [DID=3, cmd3]}, then transmitters 11, 12, and 13 may respond respectively in response slots #1, #2, and #3. Then, during sub-advertisement event #2 illustrated in FIG. 12, if mobile device 200 generates and broadcasts a command array {GID=181 / T2, [DID=4, cmd4], [DID=5, cmd5]}, insulin pumps 14 and 15 may respond respectively in response slots #1 and #2. Again, it is assumed that the device IDs of transmitter 11, transmitter 12, transmitter 13, insulin pump 14, and insulin pump 15 are '1', '2', '3', '4', and '5' respectively.

[0189] By using the embodiment of the present invention, in a one-to-many topology composed of multiple medical devices and a mobile device, multiple medical devices registered and connected with mobile device 200 can receive main / sub- advertisement event in a periodic and synchronized manner and process them. This configuration enables low power communication between the multiple medical devices and the mobile device. In other words, when multiple sensor modules communicate simultaneously (i.e., in a synchronized manner) with the same user terminal, low-power communication technology is possible, in which each module is activated only at the necessary moment and switches to standby mode during the remaining time.

[0190] By using the embodiments of the present invention described above, those skilled in the art can easily make various modifications and changes within the scope not departing from the essential characteristics of the present invention. Also, it is noted that any one feature of an embodiment of the present disclosure described in the specification may be applied to another embodiment of the present disclosure. Similarly, the present invention encompasses any embodiment that combines features of one embodiment and features of another embodiment.

[0191] The content of each claim in the claims may be combined with other claims in the scope understandable through this specification, even if not having explicit reference relationships.

Claims

1.A sensor module management system comprising:a sensor module comprising a transcutaneous analyte sensor configured to perform a measurement indicating an analyte level, and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor; anda mobile device configured to wirelessly communicate with the sensor electronics unit,wherein the sensor electronics unit comprises a first memory, a first controller, and a first transceiver configured to wirelessly transmit sensor information related to a measurement value indicating the analyte level using a predetermined communication protocol,wherein the mobile device comprises a second memory, a second controller, and a second transceiver configured to wirelessly receive the sensor information transmitted by the sensor electronics unit using the communication protocol,wherein the sensor module is configured to, when it is confirmed that a command array included in a sub-advertisement event received from the mobile device includes a first command designating a group ID to which the sensor module belongs and a device ID of the sensor module, transmit a first response to the mobile device in response to the first command,wherein the first response includes the analyte level.2.The sensor module management system of claim 1,wherein the sensor electronics unit is configured to determine the analyte level using data output from the transcutaneous analyte sensor, andwherein the first controller is configured to receive the measurement value indicating the analyte level from the transcutaneous analyte sensor and process the received measurement value.3.The sensor module management system of claim 1,wherein the command array includes a plurality of commands sequentially arranged, each including the group ID and the first command,wherein a time section assigned to the sub-advertisement event defines a plurality of response slots in chronological order, andwherein the sensor module is configured to transmit the first response during a response slot corresponding to an order of the first command in the command array among the plurality of response slots.4.The sensor module management system of claim 3,wherein each of the plurality of commands independently designates a device ID associated with the respective command, andwherein the command array includes pair information of each command and the device ID designated by the respective command.5.The sensor module management system of claim 4,wherein the mobile device is configured to transmit synchronization information to a set of sensor modules having a set of device IDs designated by the plurality of commands before broadcasting the sub-advertisement event, so that the mobile device and the set of sensor modules are synchronized with each other.6.The sensor module management system of claim 1,wherein the mobile device is configured to pre-assign the group ID to the sensor module by matching the group ID to the sensor module before the sensor module receives the sub-advertisement event, and the mobile device is configured to transmit the pre-assigned group ID to the sensor module so that the sensor module registers the group ID.7.The sensor module management system of claim 1,wherein the mobile device is configured to schedule transmission of the sub-advertisement event and provide the transmission schedule to the sensor module, and transmit the sub-advertisement event according to the transmission schedule, andwherein the sensor module is synchronized with the mobile device so as to receive only during a time section when the sub-advertisement event is transmitted.8.The sensor module management system of claim 1,wherein the sensor module is a transmitter as a continuous glucose monitoring system (CGMS) sensor module,wherein the analyte level is a blood glucose level,wherein the transcutaneous analyte sensor is a blood glucose sensor, andwherein at least a portion of the blood glucose sensor is configured to be located beneath a patient's skin to detect the patient's blood glucose level.9.A method for managing medical devices in a medical management system comprising a set of medical devices and a mobile device configured to wirelessly communicate with the set of medical devices, the method comprising:receiving, by a first medical device among the set of medical devices, a first sub-advertisement event transmitted by the mobile device, and analyzing a first command array included in the first sub-advertisement event;determining, by the first medical device, whether the first command array includes a first command designating a first group ID to which the first medical device belongs and a first device ID of the first medical device; andtransmitting, by the first medical device, a first response to the mobile device when it is confirmed that the first group ID and the first command are included in the first command array.10.The method of claim 9,wherein the first medical device is a transmitter comprising a transcutaneous analyte sensor configured to perform a measurement indicating an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor, andwherein the first response includes the analyte level.11.The method of claim 9,wherein the first medical device is an insulin pump, andwherein the first response includes information regarding an amount of insulin administered to a patient by the insulin pump.12.The method of claim 9,wherein the set of medical devices comprises the first medical device and a second medical device,wherein the first medical device stores the first group ID,wherein the second medical device stores a second group ID different from the first group ID,the method further comprising:receiving, by the second medical device, a second sub-advertisement event transmitted by the mobile device, and analyzing a second command array included in the second sub-advertisement event;determining, by the second medical device, whether the second command array includes a second command designating the second group ID to which the second medical device belongs and a second device ID of the second medical device; andtransmitting, by the second medical device, a second response to the mobile device when it is confirmed that the second group ID and the second command are included in the second command array.13.The method of claim 12,wherein one of the first medical device and the second medical device is a transmitter comprising a transcutaneous analyte sensor configured to perform a measurement indicating an analyte level and a sensor electronics unit communicatively connected to the transcutaneous analyte sensor, andwherein the other is an insulin pump.14.The method of claim 9,wherein the set of medical devices comprises the first medical device and a third medical device,wherein both the first medical device and the third medical device store the first group ID, the method further comprising:receiving, by the third medical device, the first sub-advertisement event and analyzing the first command array;determining, by the third medical device, whether the first command array includes a third command designating the first group ID and a third device ID of the third medical device; andtransmitting, by the third medical device, a third response to the mobile device when it is confirmed that the first group ID and the third command are included in the first command array.15.The method of claim 14,wherein a transmission order between the first response and the third response is determined based on an arrangement order of the first command and the third command in the first command array.

Images