Patent application number | Description | Published |
20120096451 | FIRMWARE UPDATE IN A MEDICAL DEVICE WITH MULTIPLE PROCESSORS - 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. | 04-19-2012 |
20120165614 | COMMUNICATION PROTOCOL FOR MEDICAL DEVICES THAT SUPPORTS ENHANCED SECURITY - A diabetes management system is provided that employs a communication protocol with enhanced security. The diabetes management system includes: a medical device operable to perform a diabetes care function in relation to a patient and store data related to the operation thereof; and a diabetes care manager in data communication with the medical device using a communication protocol defined in accordance with IEEE standard 11073. The diabetes care manager is able to request access to a given security role supported by the medical device, where the given security role is associated with a set of commands that are defined as a private extension of the communication protocol. | 06-28-2012 |
20120266251 | SYSTEMS AND METHODS FOR DISEASE MANAGEMENT - A computer-implemented diabetes management system is provided that supports enhanced security between a diabetes care manager in data communication with a medical device. The diabetes care manager includes: a first application that operates to request access to a first security role supported by the medical device, where the first security role is associated with a first set of commands for accessing data on the medical device that are defined as a private extension of the communication protocol; and a second application that operates to request access to a second security role supported by the medical device, where the second security role is associated with a second set of commands for accessing data on the medical device that are defined as a private extension of the communication protocol. The second set of commands has one or more commands that are mutually exclusive from the first set of commands. | 10-18-2012 |
20120269347 | Medical device with secure data transmission - Secure transmission of electronic data via a data communication link is provided between a device and an additional device with independent transmission channels, wherein at least one of the devices is a medical device. Secure transmission comprises the following steps or means: providing a password in the device, receiving the password in the a additional device separate from the data communication link, selecting one of the independent transmission channels, encrypting the channel identification of the selected independent transmission channel using the received password in the additional device, transmitting the encrypted channel identification from the additional device to the device via the data communication link and decrypting the encrypted channel identification in the device, providing a session key in the device and the additional device and transmitting encrypted electronic data between the device and the additional device via the independent transmission channel. | 10-25-2012 |
20130036210 | REMOTE CONFIGURATION AND SELECTIVE DISTRIBUTION OF PRODUCT CONTENT TO MEDICAL DEVICES - A distribution server for distributing updates for medical devices is disclosed. The distribution server can provide an update to a configuration device which configures a device to be updated. The distribution server includes a portal that allows an update provider to provide an update package including an update file and update package data relating to the update file. The update package data includes dependency data indicating a condition that must be satisfied by the configuration device or a second device so that the update file can be installed on the device to be updated. The distribution server further includes a database that is configured to store package data of a plurality of update packages and locations of update files of the plurality of update packages. The server further includes a distribution module that receives an inquiry on behalf of a medical device and provides a list of available update packages. | 02-07-2013 |
20130042117 | CRYPTOGRAPHIC DATA DISTRIBUTION AND REVOCATION FOR HANDHELD MEDICAL DEVICES - A method includes: receiving a revocation list from a remote data server at a configuration device. The revocation list includes N cryptographic certificates associated with N computer software entities, respectively, that are not to be executed by any of a group of medical devices including a handheld medical device. N is an integer greater than or equal to zero The method further includes receiving data from the handheld medical device at the configuration device. The data includes a cryptographic certificate that is associated with a given computer software entity that is presently installed in memory of the handheld medical device for execution by the handheld medical device. The method further includes comparing the cryptographic certificate with the revocation list; and selectively executing a protective function by the configuration device when the cryptographic certificate is the same as one of the N cryptographic certificates of the revocation list. | 02-14-2013 |
20140324462 | MEDICAL DATA TRANSFER COMPONENT - Diabetes care management system and method for transferring medical data from a handheld medical recording device to a host computer via a data transfer component. The steps of the data transfer component comprising detecting a data upload request and detecting a medical device ready to communicate, verifying a unique ID, receiving patient medical data, including an authentication token with patient medical data, and sending patient medical data along with the authentication token for association with a user account. | 10-30-2014 |
20140325065 | MOBILE PHONE APPLICATION FOR DIABETES CARE WITH MEDICAL FEATURE ACTIVATION - A method for activating a physician-prescribable feature of an application program executed on a mobile device is disclosed. The method includes receiving, by the application program, an activation code to activate a feature of the application program and one or more parameters associated with a prescription. The method includes transmitting, by the application program, the activation code to a server and receiving an authorization code from the server, where the authorization code indicates a validity of the activation code. The method includes activating, by the application program, the feature using the activation code, the activation being performed in response to the activation code being valid; configuring, by the application program, the activated feature using at least one of the one or more parameters associated with the prescription; and generating, using the activated feature, data based on the one or more parameters associated with the prescription. | 10-30-2014 |
Patent application number | Description | Published |
20130036412 | SOFTWARE DISTRIBUTION AMONGST MEDICAL DEVICES TAKING INTO ACCOUNT DEPENDENCIES BETWEEN DEVICES - A computer-implemented method is provided for distributing product updates from a configuration device to one or more handheld medical device. The method includes: receiving a request to download a product update to a requesting medical device; determining dependencies that must be met before the product update can be downloaded to the requesting medical device, where at least one of the dependencies specifies a version of software that resides on a device which is interoperable with the requesting medical device; receiving a listing of peer devices from the requesting medical device, such that each peer device in the listing of peer devices is distinct from and interoperable with the requesting medical device; determining software residing on a given peer device for each peer device in the listing of peer devices; comparing the at least one dependency with the software residing on each peer device in the listing of peer devices; and distributing the product update to the requesting medical device when the at least one dependency is met. | 02-07-2013 |
20130036414 | MANAGING SOFTWARE DISTRIBUTION FOR REGULATORY COMPLIANCE - A computer-implemented system is provided for distributing product updates to end user medical devices. An update interface residing on a distribution platform is configured to distribute product updates and maintain a log of such distributions in an audit database. A configuration device in data communication with the update interface registers itself with the update interface and downloads product updates from the update interface, such that the registration includes providing identifying information for a user of the configuration device and identifying information for the configuration device. A medical device in data communication with the configuration device registers itself with the configuration device and downloads a particular product update from the configuration device, such that the configuration device creates a record of the particular product update and communications the record of the particular product update to the update interface. In this way, product updates distributed via the configuration device are recorded and tracked for regulatory purposes. | 02-07-2013 |
20130036415 | SOFTWARE DISTRIBUTION TO MEDICAL DEVICES VIA AN INTERMEDIARY WHICH ENFORCES MAINTENANCE OF A TRANSACTION LOG - A software configuration device is provided for distributing product updates offline to a plurality of end user medical devices. The configuration device includes: a download manager, in selective data communication with an update interface residing at a server, that downloads product updates from the update interface and stores the product updates on a data store residing on the device; and an update distributor configured to capture identifying information for a user and operable by the user to distribute product updates to one or more end user medical devices. The update distributor further maintains distribution data for each of the distributed product updates, including identifying information for the user, in a transaction log residing on the configuration device. The download manager can subsequently upload the transaction log to the server while in data communication with the server. | 02-07-2013 |
20130167245 | CUSTOMER ERROR SCREEN CAPTURE - A method for capturing a user's view of an electronic screen having an error message in a health management application without showing private information of the user includes receiving an error message from a web service responding to a request for a web page by the user. The method includes receiving an electronic file of the web page with the error message, redacting private information of the user from the electronic file to create a redacted electronic file, and storing the redacted electronic file in a support log module. | 06-27-2013 |
20130167249 | CUSTOMER SUPPORT ACCOUNT WITH RESTRICTED PATIENT DATA ACCESS - A method for accessing a user's account by customer support without viewing the user's private data includes receiving, in an application module communicating with a web service, a request for authentication by a support person using a linked user-support login name. The method includes authenticating the user, authenticating the support person and retrieving a current session of the user as viewed by the user on an electronic screen of a processing device of the user. The method further includes dynamically redacting private data of the user from the user session to create a redacted user session, and delivering the redacted user session for display in an electronic screen of a processing device of the support person. | 06-27-2013 |
20130173473 | DATA SYCHRONIZATION SYSTEMS AND METHODS - A method performed by a medical device includes: receiving electronic medical data from one or more input devices; storing the medical data in a first datastore associated with the medical device; receiving a non-expiring, cryptographic token from a server in response to a transmission of account data, the non-expiring, cryptographic token associated with the medical device for synchronizing the medical data stored in the first datastore with the medical data stored in the second datastore that is associated with the server; transmitting the non-expiring, cryptographic token to the server for authentication by the server; selectively transmitting at least a portion of the medical data stored in the first datastore to the server for storage in the second datastore; selectively receiving at least a portion of the medical data stored in the second datastore from the server; and selectively storing the medical data received from the server in the first datastore. | 07-04-2013 |
20130179186 | SYSTEM AND METHOD FOR DATABASE SYNCHRONIZATION FOR MEDICAL RECORDS - A system and method for performing database synchronization between a first database of a first device and a second database of a second device is disclosed. The first database stores medical records having non-time based counter values associated thereto. The second database stores medical records having timestamps associated thereto. The first device includes a first database synchronization module that maintains a last timestamp indicating a last medical record that was received from the second device. The first database synchronization module transmits, to the second device, a request for synchronization and the last timestamp. The second device includes a second database synchronization module that maintains a last counter value indicative of a last medical record that was received from the first device, and that transmits, to the first device, a second request for synchronization and the last counter value. | 07-11-2013 |