Abstract:
A diabetes management system having a reliable data management scheme is disclosed. The system comprises a plurality of devices, each device performing a different function relating to treatment of diabetes. Each device has a device identifier and each device generates data records relating to the function of the device. Each device includes a metadata generator configured to generate a metadata tag for a data record generated by the device. A metadata tag includes the device identifier of the corresponding device, a record identifier, and a source identifier indicating whether the record was originated by a human or the device. The system further includes a diabetes management device in communication with the plurality of devices and configured to manage records received from the plurality of devices. When a first device of the plurality of devices generates a new record to be communicated to the diabetes management device, the metadata generator of the first device generates a new unique record identifier and a new metadata tag based on the new unique record identifier and the device identifier of the first device, and the first device propagates the new record and the new metadata tag to the second device.
Abstract:
A diabetes management system having a reliable data management scheme is disclosed. The system comprises a plurality of devices, each device performing a different function relating to treatment of diabetes. Each device has a device identifier and each device generates data records relating to the function of the device. Each device includes a metadata generator configured to generate a metadata tag for a data record generated by the device. A metadata tag includes the device identifier of the corresponding device, a record identifier, and a source identifier indicating whether the record was originated by a human or the device. The system further includes a diabetes management device in communication with the plurality of devices and configured to manage records received from the plurality of devices. When a first device of the plurality of devices generates a new record to be communicated to the diabetes management device, the metadata generator of the first device generates a new unique record identifier and a new metadata tag based on the new unique record identifier and the device identifier of the first device, and the first device propagates the new record and the new metadata tag to the second device.
Abstract:
A computer-implemented method is presented for synchronizing time between two handheld medical devices that interoperate with each other. The method includes: determining a first time as measured by a first clock residing in the first medical device; determining a second time as measured by a second clock residing in a second medical device; evaluating whether the first clock is synchronized with the second clock; determining whether at least one of the first clock and the second clock was set manually by a user; and setting time of the first clock in accordance with the second time when the second clock was set manually by the user.
Abstract:
A diabetes treatment system that includes an insulin pump and a remote pump controlling device is disclosed. The remote controller, upon receiving a request (68) for the pump to perform an operation such as starting particular insulin delivery scheme, queries (70) the pump for its current state (e.g. running, suspended, stopped delivery) and determines (73) whether the current state of the pump matches the required state for performing (76) the requested operation.
Abstract:
The present disclosure describes a handheld diabetes management device that implements a failsafe firmware upgrading protocol to reduce required user interaction and risk of device downtime. The general processing module executes first software from nonvolatile memory. The general processing module receives second software from an external port and writes the second software to the nonvolatile memory. Based on an upgrade signal, the general processing module switches execution from the first software to the second software, evaluates proper operation of the general processing module, and switches execution back to the first software from the second software when proper operation of the general processing module using the second software is not detected. A communications module, in electrical communication with the general processing module, stores third software and executes the third software. The general processing module receives fourth software from the external port and replaces the third software with the fourth software.
Abstract:
Un dispositivo de control de bomba (18) que es operable para controlar una bomba de insulina (12) que comprende: - un componente de comunicaciones (29) que es operable para proporcionar una comunicación bidireccional con la bomba de insulina (12); - un componente de entrada (31) configurado para recibir una solicitud para que la bomba de insulina (12) realice una operación solicitada, en el que iniciar y completar la operación solicitada depende de que la bomba de insulina (12) esté en un estado especificado, en el que el estado especificado comprende uno de un estado de funcionamiento en 10 el que la bomba de insulina (12) puede administrar insulina, un estado de parada en el que la bomba de insulina (12) no puede administrar insulina y un estado de pausa en el que la bomba de insulina (12) no puede temporalmente administrar insulina, y en el que la operación solicitada comprende una de comenzar a bombear insulina y parar de bombear insulina; y - un procesador (22) que es operable - para solicitar un estado de operación actual de la bomba de insulina (12) a la bomba de insulina (12) por medio del componente de comunicaciones (29) en respuesta a la solicitud recibida del componente de entrada (31), en el que el estado de operación actual comprende uno del estado de funcionamiento, el estado de parada y el estado de pausa, - para recibir el estado de operación actual de la bomba de insulina (12) desde la bomba de insulina (12) por medio del componente de comunicaciones (29), - para determinar si el estado de operación actual de la bomba de insulina (12) coincide con el estado especificado de la bomba de insulina (12), - en respuesta a una determinación de que el estado de operación actual de la bomba de insulina (12) coincide con el estado especificado de la bomba de insulina (12), para enviar un comando que corresponde con la solicitud recibida del componente de entrada (31), el comando enviado por medio del componente de comunicaciones (29) a la bomba 30 de insulina (12) para realizar la operación solicitada, caracterizado por que, - en respuesta a una determinación de que el estado de operación actual de la bomba de insulina (12) no coincide con el estado especificado de la bomba de insulina (12), el procesador (22) envía otro comando, por medio del componente de comunicaciones (29) a la bomba de insulina (12), para cambiar el estado de operación actual de la bomba de insulina (12) al estado especificado de la bomba de insulina (12).