Patent application number | Description | Published |
20090150176 | Patient-centric healthcare information maintenance - A system for facilitating patient centric healthcare information maintenance. For example, a health management software system may be operated to receive, organize, and use patient medical information. The health management software may comprise a database for storing, retrieving, organizing, displaying, and, generally, for managing a patient's health. In one exemplary embodiment, the health management software system is used in conjunction with a healthcare maintenance device, such as a blood glucose monitoring system. The blood glucose monitoring system may contain several database objects in the form of data records. Typically in a portable blood glucose monitor, each data record contains a time and a concentration data element, or a time-amount point. Similarly, an insulin pump, which is another exemplary embodiment of a healthcare maintenance device, may maintain data records with time and dosage information, or a time-dosage point. | 06-11-2009 |
20090150181 | Method and system for personal medical data database merging - A method and system for merging databases containing medical, patient and/or healthcare, information is provided, which may be utilized to merge a source database containing medical information into a new or existing destination database. The method may include the steps of identifying a source database containing medical information, identifying a destination database for the receipt of the medical information from the source database, selecting rules for governing the migration of medical information into the destination database, and migrating the medical information from the source database to the destination database. In one exemplary embodiment, the medical information is a plurality of individual patient's medical records. In another exemplary embodiment, the medical information is a plurality of healthcare provider records. | 06-11-2009 |
20090150377 | Method and system for merging extensible data into a database using globally unique identifiers - A method of merging data from one database into another database uses metadata identifiers to indicate the type of data. One of the databases can be stored on a medical device, and the other of the databases can be stored on a computer. When transferring data from the first database to the second database, the metadata identifiers are used to identify and merge common data types. | 06-11-2009 |
20090150439 | Common extensible data exchange format - A medical data system wherein data is exchanged internally and externally by a common data exchange format. | 06-11-2009 |
20090150451 | Method and system for selective merging of patient data - A method and system for merging patient data in the form of medical information, e.g., patient and/or healthcare provider information, is provided, which may be utilized to identify medical information stored in a first location that is unique to, a duplicate of, and/or a potential duplicate of medical information stored in a second location. In one exemplary embodiment, the present invention is utilized in conjunction with or incorporated into medical management software. In one exemplary embodiment, the medical management software is disease management software, such as diabetes management software. In medical management software, it is important to ensure that specific, individual records containing medical information are properly associated with an individual patient and/or healthcare provider. | 06-11-2009 |
20090150454 | System and method for database integrity checking - A method is disclosed for checking the integrity of a database through a test of database integrity information provided in the database and integrity information provided external to the database. The integrity information may be provided in a configuration file. | 06-11-2009 |
20090150683 | Method and system for associating database content for security enhancement - A system and method for associating database content for security enhancement is provided, the method being applicable to a system comprising a computer configured to process a data management application and to store data in databases. According to one embodiment of the method according to the invention, the application uses an encryption key to encrypt data. The application stores the encrypted data in two or more databases. The databases may comprise a system database for storing encrypted user access data and one or more results databases for storing patient data. Databases may be stored locally, remotely, or both locally and remotely. | 06-11-2009 |
20090150758 | Method and system for creating user-defined outputs - A system and method for creating a template configured to generate reports for reporting medical information. The method allows a user to generate a single template that may be then utilized in order to create a plurality of reports for numerous patients. The template is created by dragging and dropping the desired information onto a blank report. Once the desired format of the template has been set by the user, the user may save the template for future use. | 06-11-2009 |
20090150812 | Method and system for data source and modification tracking - A system and method for displaying data are disclosed, the method being applicable to a system comprising a computing device having an output device and software programs, and, optionally, an input device. The programs are configured to provide a screen display having display objects. The display objects distinguish the data according to the sources of the data. | 06-11-2009 |
20090192813 | INFORMATION TRANSFER THROUGH OPTICAL CHARACTER RECOGNITION - A medical data receiver configured to optically capture medical data, extract the medical data from the optical capture as alphanumeric characters, and provide the alphanumeric medical data for analysis. | 07-30-2009 |
20100076784 | PATIENT DIABETES DATA INTERCHANGE WITH ELECTRONIC MEDICAL RECORDS - A system and method for transferring patient diabetes information into an electronic medical record on a health record system with user validation are disclosed. After testing a patient's blood glucose levels over a period of time with a blood glucose meter which stores the patient diabetes information and the blood glucose levels in a first electronic format record, and after a user transfers the first electronic format record from the blood glucose meter into a diabetes management system on a computer, the invention provides a service which automatically monitors an output folder to determine when an export file containing the patient diabetes information is stored therein and after detection, automatically processes the export file into a default electronic medical report which can be copied into a clipboard utility provided by the computer and pasted into the electronic medical record of the patient on the health record system. | 03-25-2010 |
20110093510 | METHODS AND SYSTEMS FOR SERIALLY TRANSMITTING RECORDS IN XML FORMAT - A portable electronic medical device and method for serially transmitting one or more records from the portable electronic medical device are disclosed. The portable electronic medical device includes a processor and memory for storing the one or more records, each record having one or more data entries. An XML (Extensible Markup Language) template may be parsed by the processor, wherein the XML template has one or more XML elements associated with the one or more data entries. The one or more records may be read as well as the XML elements appended to the associated data entries of each record by the processor such that the appended data entries are in XML format. The processor may then serially transmit the appended data entries of each record. | 04-21-2011 |
20110246242 | PATIENT-CENTRIC HEALTHCARE INFORMATION MAINTENANCE - A system for facilitating patient centric healthcare information maintenance. For example, a health management software system may be operated to receive, organize, and use patient medical information. The health management software may comprise a database for storing, retrieving, organizing, displaying, and, generally, for managing a patient's health. In one exemplary embodiment, the health management software system is used in conjunction with a healthcare maintenance device, such as a blood glucose monitoring system. The blood glucose monitoring system may contain several database objects in the form of data records. Typically in a portable blood glucose monitor, each data record contains a time and a concentration data element, or a time-amount point. Similarly, an insulin pump, which is another exemplary embodiment of a healthcare maintenance device, may maintain data records with time and dosage information, or a time-dosage point. | 10-06-2011 |
20120066185 | SYSTEM AND METHOD FOR DATABASE INTEGRITY CHECKING - A method is disclosed for checking the integrity of a database through a test of database integrity information provided in the database and integrity information provided external to the database. The integrity information may be provided in a configuration file. | 03-15-2012 |
20120095313 | MEDICAL DEVICES THAT SUPPORT ENHANCED SYSTEM EXTENSIBILITY FOR DIABETES CARE - A medical device or medical software is provided that supports system extensibility for diabetes care. The medical device or software is comprised of an application and particular data structures that support diabetes care. The data structures include: a patient class that has attributes and methods associated with a person receiving medical treatment for diabetes; a patient log class that has a composition relationship with the patient class and attributes and methods that log actions taken by the patient; a treatment plan class that has a composition relationship with the patient class and attributes and methods that define a series of planned actions related to medical treatment of the patient; and an adherence class that has a composition relationship with the patient log class and attributes and methods define relationships between actions planned for the patient and actions taken by the patient. The application instantiates an object from at least one of the patient log class, the adherence class and the treatment plan class, having only external-to-the-composition knowledge of which objects are instantiated, and performs a function using the instantiated object. | 04-19-2012 |
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 |
20130173307 | INTERFACE FOR AN ELECTRONIC MEDICAL RECORD SYSTEM - An interface for an electronic medical record (EMR) system is configured to receive messages and documents having a message data format and a document data format respectively, transmitted to EMR system in accordance with a first and second device healthcare interoperability standard. The interface is further configured to determine whether a given message or document pertains to blood glucose measures and to generate records in a custom format of the EMR system. The interface is further configured to parse the messages and documents for a structure collection procedure from a comment field in the given messages and documents and to map the structured collection procedure data to applicable data fields in a corresponding record of the EM system. | 07-04-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 |
20130185396 | DYNAMIC COMMUNICATION STACK - A method of facilitating communication between a resource and a computer is described. The computer employs a software application that allows the computer to communicate with the resource. The resource may comprise a medical device such as a blood glucose meter or an insulin pump. In order to facilitate communication between the computer and the resource, the software constructs a communication protocol particular to the type of resource connected to the computer. The stack comprising the communication protocol allows the computer to communicate with the resource. Once the resource and computer cease communication, the stack may be removed from the memory of the computer. | 07-18-2013 |
20140324445 | DIABETES MANAGEMENT SYSTEM MEDICAL DEVICE USAGE STATISTICS - A computer-implemented method for sharing information and managing diabetes diagnosis and treatment. The method comprises providing a web portal account accessible by both a patient and health care provider. The account may be associated with a portable medical device. The method includes receiving, at one or more servers, medical and usage data from the portable medical device. The medical data may be associated with the patient and the usage data may be associated with usage of the medical device by the patient. Statistics related to the medical or usage data are accumulated at one or more servers over a period of time, and may be accessible in the web portal account. The method includes evaluating the statistics in relation to a treatment criteria, and sending a treatment recommendation to the patient or the health care provider when at least one of the statistics meets or exceeds a predetermined treatment criteria. | 10-30-2014 |
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 |
20140324463 | WEB ACCOUNT CREATION AND MANAGEMENT, DATA SHARING, HOME PAGE SETTING, AND DATA REPORTING - A method includes: receiving, at a computing device, diabetes management data from a diabetes management device, wherein the diabetes management data does not include a blood glucose (bG) measurement; using the computing device, transmitting an indicator of an account and the diabetes management data to a diabetes management server. The method further includes, using the diabetes management server: creating a bG measurement entry for the account in a database, leaving empty a field of the bG measurement entry for a bG measurement in the bG measurement entry based on the diabetes management data not including a bG measurement; and storing the diabetes management data in one or more respective fields of the bG measurement entry. The method further includes, using the diabetes management server, generating a user interface for displaying data stored in the bG measurement entry and at least one other bG measurement entry associated with the account. | 10-30-2014 |
20140324464 | SYSTEM PORTAL CONTROL FOR A DIABETES MANAGEMENT SYSTEM - A computer-implemented method for managing accounts in a diabetes management system. The method includes receiving, by an account manager, a request to deactivate a first account associated with a healthcare provider. The first account may be associated with a plurality of patient accounts. The account manager may be implemented as computer executable instructions executing on a computer processor of a server device. The method includes removing, by the account manager, access to data associated with the first account. Each of the patient accounts associated with the first account are identified and may be deactivated by the account manager. An electronic notification may be sent to a person associated with each of the identified patient accounts, advising the person that the corresponding patient account has been deactivated. An audit record may be created in a data store, the audit record indicating the deactivation of the first account. | 10-30-2014 |