JP2003500744A - Comprehensive medical information management system - Google Patents

Abstract

(57) [Summary] A comprehensive medical information management system includes at least one online central server and at least one remote access terminal. The at least one online central server includes patient-related data for at least one patient. The at least one remote access terminal interactively accesses the patient-related data for the at least one patient from the at least one online central server, and the at least one remote access terminal on the at least one online central server Used to generate an interactive report based on said patient related data for a given patient. Preferably, said at least one online central server is connected to said at least one remote access terminal through an internet connection and utilizes an internet web browser to interactively access said at least one online central server.

Description

Detailed Description of the Invention

(Related Application) This application was filed on May 20, 1999, which is specifically incorporated by reference into the present application, and entitled "D
iabetes Integrated Management System
US Provisional Patent Application No. 60 / 134,981 and September 29, 1999
In Japanese application, "Communication Station and Soft
were for Interfering with an Infusio
n Pump, Analyte Monitor, Analyte Met
US patent application Ser. No. 09 / 409,01 entitled "Er, or the like"
Claim priority of No. 4.

TECHNICAL FIELD The present invention relates to a comprehensive medical information management system, and in a specific embodiment, utilizes a telecommunications station, a facsimile, an email and the Internet to search for patient data and provide a patient, doctor, medical service. System for providing reports to individuals, HMOs, and / or insurance companies to manage diabetes.

BACKGROUND ART Currently, most of type I and type II diabetics must be administered insulin (about 40% of type II diabetics use insulin). Conventionally, insulin has not been taken orally, so it has been injected by syringe. Recently, external infusion pump therapy has been increasing in order to carry insulin, especially by putting the device on a belt or putting it in a pocket. Insulin has a percutaneous needle or cannula placed in the subcutaneous tissue. It is introduced through the catheter. For example, in 1995, less than 5% of U.S. type I diabetics were using pump therapy, but now about 7% of more than 900,000 U.S. type I diabetics have insulin pump therapy. , And the number of users is increasing at a rate of over 2% every year. In addition, the number of type I diabetic patients is increasing at a rate of 3% or more per year, and the percentage of type II diabetic patients using insulin using external insulin infusion pumps is also increasing. There is an increasing number of cases in which physicians are prescribing continuous infusions to patients, recognizing that they can better manage their condition in diabetic patients. Better management can reduce the incidence of diabetic complications.

Conventionally, diabetes treatment data is recorded in a diary or stored in the memory of the treatment or monitoring device. This information is then manually entered into the local computer or downloaded. However, this data is not easily transferred to health care providers or professionals and must be taken to people who need to see it or sent using a modem. Unfortunately, this requires a visit to the health care provider and the data must be viewed at that time. It is not feasible to regularly send data to healthcare providers for constant monitoring and analysis. This is because healthcare providers must use their own time and computer to analyze and interpret the data.

DISCLOSURE OF THE INVENTION It is an object of embodiments of the present invention to provide, for a particular purpose, a comprehensive medical information management system that eliminates the above limitations.

According to an embodiment of the present invention, a comprehensive medical information management system has at least one
Includes one online central server and at least one remote access terminal. The at least one online central server includes patient-related data for at least one patient. The at least one remote access terminal interactively accesses patient-related data for at least one patient from an online central server and the patient for the at least one patient on the at least one remote access terminal Used to generate interactive reports based on relevant data. Preferably, the at least one online central server is connected to the at least one remote access terminal through an internet connection, and the at least one remote access terminal utilizes an internet web browser to interactively communicate with the at least one online. Access the central server.

In a preferred embodiment, patient related data regarding diabetes is used. For example, patient-related data can be drug infusion data, blood glucose monitor data and / or blood glucose level measurement data, and the like.

In another embodiment of the invention, a comprehensive medical information management system includes at least one online central server, at least one medical device, at least one data receiving device, at least one remote access device. The at least one online central server includes patient-related data for at least one patient. The at least one medical device includes a memory for storing data regarding treatment of a patient's condition and use of the device by the patient. The one data receiving device receives data from the at least one medical device and uploads the data to the at least one online central server as patient related data. The at least one remote access device is for receiving patient-related data from the at least one online central server. Preferably said at least one remote access device is a remote access terminal for interactively accessing patient related data for said at least one patient, said at least one remote access terminal on said at least one remote access terminal. It is used to generate interactive reports based on patient-related data about patients.

The at least one online central server is connected to the at least one remote access terminal through an internet or intranet connection and interactively accesses the at least one online central server using an internet web browser. Also, the at least one remote access device is a facsimile. Another embodiment further includes a communication station interface between the at least one medical device and the at least one data receiving device. Preferred medical devices include infusion devices, blood glucose monitors and / or blood glucose meters.

In a preferred embodiment, patient related data regarding diabetes is used. For example, the patient-related data is drug infusion data, blood glucose monitor data and / or blood glucose meter data.

In yet another embodiment, the at least one remote access device is used to receive email reports. Further, the at least one data receiving device may receive a request for a report from the at least one online central server. In yet another embodiment, said at least one
One data receiving device can receive the request to schedule supplies and / or schedule supplies. Also, the at least one remote access device further includes the ability to order supplies through the at least one online central server based on data uploaded from the at least one medical device.

In certain embodiments, the system further comprises a data bus, which captures data from the various at least one medical device, regardless of the type of device connected to the data bus, It can be stored, processed and reported. Preferably, the data bus utilizes data elements and / or collections of data elements to process data.

In another embodiment, the at least one online central server automatically generates reports at predetermined times. The report can be sent by mail, email, internet, intranet, leased line, etc. Yet another embodiment may generate a group report for at least one or more patients. In addition to this, the report can be sent to a managed healthcare provider (HMO). Functions may also be included to schedule appointments, issue invoices to clients, and / or process insurance claims.

Further, in another embodiment, the data is collected automatically by the device and / or by manual entry of the data by an individual. In certain embodiments, the data is drug consumption data, blood glucose consumption data, exercise data, calorie burn data, infusion data, etc. from a source independent of laboratory data, etc. In another embodiment, once the at least one remote access device receives the data, the patient can view the data and analyze it to generate a report. In yet another embodiment, the data is used to create a report. For example, it is used to create a report including components selected from graphics elements, text elements, number elements, and table elements for representing data. The data is used to generate reports on the use of medical supplies and / or to generate reports that provide results of using the medical supplies. In another embodiment, a report may be created to identify problems or issues and / or to identify or suggest points in the report where recommendations may be needed. This embodiment can also utilize expert logic.

In yet another embodiment, the present system can generate reports regardless of the type of at least one medical device, at least one data receiving device, or at least one remote access device in use. . For example, the system of the present application may include the ability to combine a portion of all data on the at least one online central server into a data memory and reporting mechanism. In addition, the system of the present application includes a function of collecting a part of all the data on the at least one online central server or arranging them side by side into one report. In another example, the present system relies on a portion of the total data on the at least one online central server to associate portions of the data in a manner that is not possible by referring to each portion of the data separately. , Including the ability to derive results and recommendations.

In another embodiment, the data memory and reporting system includes a data bus, which allows data to be collected from a wide variety of medical devices that use different formats and types of data. Furthermore, the data bus allows data collection and reporting without the need for the healthcare provider, patient or system to recognize the difference in data format or type.

In yet another embodiment, the data bus is used to process data with data elements and / or collections of data. The system of the present application also converts various data formats from various medical devices into one consistent storage format.

In certain embodiments, the present system may store mixed data from different medical devices in a database in a single process. The system of the present application also converts various data formats from a wide variety of medical devices into one consistent reporting format.

In another specific embodiment, the present system may store and present data from different medical devices in a consistent presentation style. In addition, the system of the present application can store, process, and report data from different medical devices, regardless of the development of program code for specialized handling of different medical devices. In another embodiment, the system of the present application can perform simultaneous calculations on data collected from different medical devices regardless of how various medical data devices that provide data are mixed. Further, the system of the present application may be one in which calculations regarding data collected from different medical devices to be integrated as different groups are executed in a single process. For example, the system of the present application uses one of the blood glucose levels measured by different blood glucose meters for a certain period.
The daily average value can be calculated in a single process.

In yet another embodiment, the system of the present application can combine data from new and different medical devices into the system by adding a minimal program. Also, the system of the present application has different data formats and types of data, and data from different medical devices used for the same purpose can be combined into one report or graph of the same type. (For example, one patient can use two different blood glucose meters from different manufacturers at the same time. The system can combine (or intersperse) the information from these meters into one report. Can be done.)

Other features and advantages of the invention will be apparent from the following detailed description, which is taken in conjunction with the accompanying drawings, which by way of example show various features of embodiments of the invention.

BEST MODE FOR CARRYING OUT THE INVENTION As shown in the drawings for purposes of illustration, the present invention provides medical treatment for patients, health care providers, supervised medical institutions or health maintenance organizations (HMOs) and insurance companies. It will be implemented as a comprehensive medical information management system to manage the information gained from treatment and to assist in better treatment of disease symptoms and effects. The preferred embodiment utilizes an infusion device and blood glucose monitor and / or meter with the capability of storing information regarding drug infusion and measured blood glucose level for management of diabetes information. In another embodiment, the patient or local healthcare provider uses communication station I or II, a modem, etc. to download the stored data from the device to a PC, laptop or data processor, and then a modem, email. Or download to a central server either through an internet connection. The stored data is then analyzed and a preliminary report is provided to the patient's doctor, or other health care provider, by fax, email or internet. If desired or necessary, the physician can also access the data on the server through an internet (or modem) connection and have the data for that patient revealed, or a custom report created for further analysis. In yet another embodiment, the healthcare provider, HMO and insurance company store the stored data (typically in a database).
To get patient-wide statistics and receive alert signs for individual patients who appear to be out of their normal medical condition and need attention from their healthcare provider. In other embodiments, the data can be downloaded to a healthcare provider for further analysis on a PC, laptop or processor located locally by the healthcare provider. A preferred embodiment relates to the management of diabetes. However, other embodiments are also available for asthma, heart disease, AIDS, cancer and other diseases.

A comprehensive healthcare information management system provides centralized storage and processing for patients, healthcare providers, HMOs and providers. The patient takes the drug using an infusion device such as an infusion pump. The infusion device includes a memory for storing infusion history data and alerts and other relevant data needed for correct infusion. During the infusion, the patient monitors his condition using an individual finger-prick blood glucose meter and / or blood glucose monitor for continuous (or semi-continuous) monitoring of the patient's condition. These devices also store data and related information regarding the patient's condition.

In general, the patient installs an infusion device, meter and / or monitor on a communication station I or II or other suitable device every few days and sends the data to a local PC.
, Download to laptop computer, data processor, etc. In another embodiment, it can be changed to days, weeks, or months and other intervals. In yet another embodiment, the infusion device, monitor and / or meter may have the capability to transfer data directly to a PC, laptop computer, data processor, etc. After downloading the data, the patient can view and use the data for himself. As mentioned above, a comprehensive medical information management system is generally referred to in "Co," filed September 29, 1999, which is incorporated herein by reference.
mmstation Station and Software for
Interfering with an Infusion Pump,
Analyte Monitor, Analyte Meter, or t
Used in conjunction with a communication station (“comstation”), as described in US patent application Ser. No. 09 / 409,014 entitled “he like”, insulin pump, blood glucose meter (“meter”), continuous blood glucose monitor (“ The stored data is downloaded from the monitor ") to a central server, where it is analyzed and stored.
At its most basic service level, the server analyzes the uploaded data and faxes a multi-page report using graphics and tabular information to the healthcare provider before or during the patient's visit. It

In other embodiments, more advanced options for report composition and delivery are available through the Internet interface. In yet another embodiment, the data is uploaded to the central server either through a modem connection or the internet. Alternatively, the data can be uploaded directly through the communication station. Also, data is uploaded to the central server via satellite link, cellular phone link, email, etc. In yet another embodiment, the uploaded data is interpreted and used to automatically order supplies and materials to send to the patient to maintain the patient's condition.

Once the data is sent to the central server, reports are periodically generated and sent to the healthcare provider. In one embodiment, the report is sent by facsimile. However, in another embodiment, the report may be emailed and / or the raw data downloaded to a healthcare provider for review and investigation. If the healthcare provider desires more detailed analysis or a special report, the healthcare provider can order and request custom reports via email and / or online regarding specific time periods, parameters, comparisons, etc. The connection can be via the Internet, through a modem, or any other suitable method of data transfer to access and report on data for each patient of the healthcare provider. In this way, the healthcare provider can quickly interact with the data and obtain the desired report. The physician can instruct the central server to monitor specific items or parameters of patient data and issue alerts or notifications when specific events or conditions appear. As a result, health care providers will be informed about various medical conditions more often. In addition, health care providers have access to detailed data that can be viewed before the patient arrives, making the visit much more productive and informative for both the patient and the health care provider. Many.

HMOs and / or insurance companies may also benefit from a central database. This is because it is possible to monitor statistical information about all patients on the central server, monitor the patient subscribers as a group, and determine the major aspects of the illness affecting the subscribers. It can also alert and order proactive treatment when a particular patient (or group of patients) appears to have a problem.

In a preferred embodiment, a patient is identified by the serial number of the patient's device. Some form of authentication security is required to ensure that a particular device / patient identity cannot be confused or obtained without authentication. Data transmitted over public networks or the Internet is encrypted for even greater security. Besides, all internet transactions are encrypted and internet-based access is protected by username / password login.

FIG. 1 shows a system architecture of a comprehensive medical information management system 10 according to an embodiment of the present invention. Preferably, an analysis server 12 is used that accesses a patient database 14 used to store and analyze the data. This will be described in detail below. Patient data in the database 14 is generally stored for a specified period of time (eg, 3 months, 1 year, etc.) and old data is stored on offline media. The analysis server 12 is also connected to various external data sources and processors via a data modem 16, a fax modem 18 and / or a web server 20 connected to the Internet 22. As another embodiment, various servers may be grouped together or configured by a plurality of different interconnected servers, which have a system architecture, an expected number of users, a type of connection to be used, an amount of data to be handled, etc. Depends on

In a particular embodiment, the patient's home computer 24 is connected to the web server 20.
Can be connected via the Internet 22. However, in another embodiment, the computer 24 at the patient's home may be accessed through the data modem 16 (using a dedicated dial-in line or a local access number connected to a third party's network for access) or directly. It can be connected to the analysis server 12 through a wire connection or the like. Preferably, the computer 26 at the doctor's office is connected to the analysis server 12 through the data modem 16. However, in another embodiment, the computer 26 at the doctor's office can also connect to the web server 20 through the Internet 22.

Although only the computer 26 at the doctor's office has been described, the following can be connected to the computer 24 at the patient's home. In a preferred embodiment, the computer 26 at the doctor's office has a blood glucose monitor 30 (such as a MiniMed Inc. product for continuous or semi-continuous blood glucose measurement) and / or an infusion device 32 (MiniMed 407C infusion pump, 507C infusion pump, 508).
Communication station 2 that can download data from infusion pumps, etc.)
8 is connected. In another embodiment, the computer 2 in the doctor's office
6 may be omitted, and the blood glucose monitor 30 and the infusion device 32 may be connected to the communication station II 34.
Can be connected, which includes a display, additional control buttons, RF communication capabilities,
Functions such as a built-in modem are added. Communication Station and Communication Station I
A detailed description of I is incorporated by reference in its entirety into US Pat. No. 5,376.
, 070 and filed September 29, 1999, entitled "Communicati
on Station and Software for Interface
ing with an Infusion Pump, Analyte M
US Patent Application No. 09 / 409,014 entitled "Onitor, Analyte Meter, or the like" (WO00, Apr. 6, 2000).
/ 18449). The computer 26 in the doctor's office is a blood glucose meter 36 (AcuChek, Roche, Roche).
Lifescan by Nson & Johnson, Med by Abbott
It can also be connected directly to another device, such as an presence meter, Bayer Elite, etc.) through a direct wire, IR, RF connection or the like. In another embodiment, the blood glucose meter 36 is a communication station 28 or a communication station II 34.
Through, in pass-through mode, or by using station 28 or 34 as an interface. In a particular embodiment, the report and data receiving device and the data transmitting and receiving remote access device are the same device.

The integrated medical information management system 10 may be equipped with a management medical institution computer (HMO) 38 connected to the web server 20 via the Internet 22 or to the analysis server 12 via the data modem 16. . Further, another computer 40 such as a laptop, an account computer, a research computer or the like may be connected to the web server 20 via the Internet or a dedicated line, or may be connected to the analysis server 12 via the data modem 16 or the like. Other data transceivers 42, such as fax machines, scanners (not shown), etc., can be connected to the analysis server 12 via the fax modem 18 to transmit and receive data for analysis. In other embodiments, software on the computer is utilized to communicate with the analysis server 12 by other methods such as IR data links, satellite data links, cellular data links, and so on.

FIG. 2 is a diagram showing a system architecture of a comprehensive medical information management system 100 according to another embodiment of the present invention. The integrated medical information management system 100 is similar to the integrated medical information management system 10, but is designed to operate using an intranet 102 connection rather than an internet connection. This system is suitable for management within an organization with satellite offices. The system also provides higher security because the public Internet is not used for data transmission when security is an issue. The preferred embodiment utilizes an analytics server 104 that accesses a patient database 106. Database 106
Is used for storage and analysis of data, which is described in detail below.
The analytics server 104 is also connected to various external data sources through the data modem 108, the fax modem 110, and / or the intranet 102.
Connected to. Computer 112 at the doctor's office (or computer at the patient's home) is preferably connected to analysis server 104 through data modem 108. However, in other embodiments, the computer 112 at the doctor's office is connected through the intranet 102. In the preferred embodiment, the computer 112 at the doctor's office has a glucose monitor 116.
Connected to a communication station 114 capable of downloading data (such as a MiniMed Inc. product for continuous or semi-continuous blood glucose measurement) and / or infusion device 118 (MiniMed 407C infusion pump, 507C infusion pump, 508 infusion pump, etc.). It A detailed description of the communication station is provided in US Pat. No. 5,376,070, which is incorporated herein by reference in its entirety, and filed Sep. 29, 1999, “Communication Station and
Software for Interfering with an Inf
usage Pump, Analyte Monitor, Analyte
U.S. Patent Application Serial No. 09/40 entitled "Meter, or the like"
No. 9,014 (published as WO00 / 18449 on April 6, 2000). In yet another embodiment, communication station II is used as described above. The computer 112 at the doctor's office also includes a blood glucose meter 120 (Roche AccuChek, Johnson & Johnson).
n, Lifescan, Abbott's Medisense meter,
Other devices, such as Bayer Elite, etc.) can also be connected directly through wires, IR, RF connections, etc. In another embodiment, the blood glucose meter 120 is in pass-through mode through the communication station 114, or in the station 1.
It can be connected by using 14 as an interface.

The integrated medical information management system 100 may be equipped with a managing medical institution computer (HMO) 122 that is connected to the analysis server 104 through the intranet 102 or through the data modem 108. Further, the analysis server 104 may be connected to an intranet with other computers such as a laptop, an account computer, and a research computer, or through the data modem 108.
You may connect to. Other data transceivers 124, such as fax machines, scanners (not shown), etc., can be connected to the analytics server 104 through the fax modem 110 to send and receive data for analysis. In other embodiments, software on the computer is utilized to communicate with the analysis server 104 by other methods such as IR data links, satellite data links, cellular data links, etc.

FIGS. 3 to 5 are diagrams showing a reporting architecture 200 used by the comprehensive medical information management system 100 shown in FIGS. The reporting architecture 200 receives data through a receiving program 202 that manages communication with communication stations I or II, computers, medical devices and the like. The receiving program 202 saves the data in an intermediate format (disk file 206, etc.). The data is then processed by the loading program 204 for storing information in the system database 212. Loading program 20
4 uses a data bus 208 for data processing and storage, which is common to the reporting architecture and used by the rest of the application (detailed below). The data bus 208 stores and plays data from the database through a database access framework 210 that includes a database object model 214 and a database interface 216. The database access framework 210 and / or the data bus 208 support other administrative and customer service applications 218, including, for example, client and doctor account establishment, customer service assistance, billing to clients, and the like.

The reporting application 220 is used to generate various reports for use by healthcare providers, patients, HMOs, administrators, and the like. Reporting application 220 includes a report scheduler 222 that schedules when reports should be generated and sent. Reporting application 220 includes report specification logic 224 that specifies the logic and parameters used to generate using the template. Report layout module 226 and report imaging module 228 are used to generate the actual report. In addition, the plotting module 230 and the chart imaging module 232 are used to generate graphs for use in the report. In this embodiment, the report is HTML, GIF, Encapsulated PostScr.
It is generated in a plurality of formats such as ip, PostScript, PDF, TIFF or a composite format. In other embodiments, other formats such as JPEG, MPEG, etc. are used. In addition, reporting application 220 includes an exception and expert logic module 234 for identifying and communicating unusual or unusual conditions based on the report data and making suggestions accordingly.

The output of reporting application 220 is sent to report delivery queue 236 for delivery by fax or email. Fax delivery mechanism 238 includes faxing software and image generation software for faxing reports and charts to various receiving devices. The email delivery mechanism 240 sends reports via email, such as text messages, attachments, embedded graphics, combinations of these, and so on. In addition, the report is created in HTML section 242 and is published on the protected website for viewing in a web browser. The disk file 244 is used to manage the report delivery queue and HTML web-based report generation. In another embodiment, the report can be printed and sent by mail, Federal Express, UPS, etc.
In yet another embodiment, the request for the report may be received by mail, email, phone request, call to server, etc.

FIG. 6 collects data directly from medical devices, including infusion device 302, monitor 304, meters 306 and 308, and other medical devices 310, and P
FIG. 9 is a block diagram showing an application 300 for uploading to a central server via C (24, 26, etc. above). The application 300 includes a user interface that utilizes a data bus 312 (described below) to communicate with a device / data manager 314. The device / data manager 314 uses a plug-in software architecture to communicate with various medical devices. Even though these plug-in modules communicate directly with the serial port interface 316,
Alternatively, it may communicate directly with the medical device through library module 318 and / or 320. The serial port interface 316 can be connected to the communication station 322 (described above) to connect the infusion device 302 and / or the monitor 304 and / or the meter device 306 that utilize the pass through of the communication station 322. In other embodiments, the serial port interface 316 can connect to the meter 306, which can connect directly to the serial data port. The application 300 includes a file transfer module 3 for transferring a data file through the modem 326.
Including 24.

Thus, embodiments of the system allow data to be collected from a variety of medical devices that have different formats and types of data. Healthcare providers or patients do not have to consider these medical device differences. The system transforms various data formats into one consistent storage and reporting representation. This allows data from multiple devices to be stored and presented as well, and data from new devices can be incorporated into the system with little additional development work. For example, suppose patient A uses the blood glucose meter of company 1 and patient B uses the blood glucose meter of company 2. Both of these patients depend on the doctor C, and the doctor C can see the report of each patient without considering the difference between the blood glucose meters of the company 1 and the company 2. Thus, system embodiments may combine data from devices that have the same purpose but different data formats and types into a single, uniform report. For example, one patient can use two types of blood glucose meters from different manufacturers. The system can combine (or intersperse) the data from these meters into a single report. The same capabilities apply to other medical devices such as infusion devices, blood glucose monitors, etc.

In yet another embodiment, a “plug-in” architecture is used to expedite the development of drivers for additional devices (eg insulin pens with memory, smart pill boxes, other blood glucose meters, etc.). , Use software that downloads information from the device. As a result, the usefulness in consideration of a product developed in the future is realized.

FIG. 8 is a diagram illustrating an example of a data management application for a particular market segment.

9 to 15 are diagrams showing examples of reports and screens created by the comprehensive medical information management system. In general, the screens shown in Figures 9 to 15 are all part of one report. However, in other embodiments, each screen may be provided separately or some may be omitted or added as individual reports. FIG. 9 is a screenshot of an interactive report generation screen used by a healthcare provider to obtain detailed reports on the Internet. Figure 1
0 is a three-day report obtained in response to a request from the screen of FIG. FIG. 11 is an enlarged view of the first day shown in FIG. FIG. 12 is an enlarged view of the second day shown in FIG. FIG. 13 is an enlarged view of the third day shown in FIG. FIG. 14 is a comparative diagram for showing the difference for each day by superimposing the reports for three days shown in FIG. 10 on the same graph. FIG. 15 is a two-week list chart report including blood glucose monitor data, mode date, blood glucose summary statistics, and insulin usage report. Other reports are also incorporated herein by reference, filed September 29, 1999, “Communication Station and So”.
ftware for interfering with an insus
Ion Pump, Analyte Monitor, Analyte M
US patent application Ser. No. 09/409, entitled "eter, or the like",
No. 014 (published as WO00 / 18449 on April 6, 2000), which is created and used by a comprehensive medical information management system including those disclosed and described.

For example, data from a device that senses a physiological condition in a patient can be combined with data regarding drug use. The system then produces a report listing physiological and drug dosing data, blood glucose levels, carbohydrate consumption, etc. in a graphics or text format. The system can also use both physiological sensing data and drug data in a single report,
Reports can be created to assist the healthcare provider in identifying abnormal conditions or behavior, and an expert system for identifying problematic patients can also be included.

Reporting architectures typically extract information from device data stored in a database based on specified criteria, perform calculations, and chart (graph, graph,
Works by creating pie charts, bar charts, mixed etc.) and generating reports. A basic report usually spans one to a few pages and contains graphical representations of the data, aggregate statistics, exceptions, etc. In another embodiment, suggestions, conformance assessments, etc. may be included in the report. In the preferred embodiment, the system relatively easily creates new reports, draws conclusions,
It uses configurable rule-based logic to make suggestions and provides a flexible reporting structure with increased memory capacity for smarter devices.

Generally, a report consists of a set of components laid out as blocks on a page. The reporting system uses the report template to identify the layout of the report. These templates are written in standard layouts or markup languages. The template language and layout processor must be rich enough to allow arbitrary placement of report components on a page and to support various output formats as described herein. . Report components generally consist of blocks of diagrams, tables or text. In the report component,
You can mix elements using subcomponents. This allows reports to be designed hierarchically and allows multiple reports to reuse a single component. The reporting component can also mix data from different devices or different types of devices. The report layout mechanism supports text flow, line breaks, etc. Text components can use a variety of fonts, sizes and styles. (For HTML-based reports created for browsing on the Internet, there are some limitations in this respect due to the nature of the Internet browser.)

The plotting system can create plots in various formats such as bar graphs, layered graphs, line graphs, dot charts, distribution charts, and combinations thereof. The plotting system supports flexible chart axis configurations, including multiple axes for overwritten data. Many charts use some form of date or time scale on the X-axis,
This scale can be set variously from time to year. In another embodiment, the drawing system optionally also supports color charts. Chart components can be created as images using a document format other than the report template language.

In a preferred embodiment, the comprehensive healthcare information management system is based on a plurality of selected scenarios and conditions, such as pre-booking, regular (monthly or quarterly (probably managed healthcare (HMO) ) Also delivers a report, such as when a health risk exception is detected (eg, hyperglycemia or hypoglycemia persists for an extended period of time), and the system typically faxes it to the healthcare provider's office. Provide a few pages of the report sent in. In this embodiment, the patient also
Health care providers also do not need to have computers. In yet another embodiment, on-demand reporting is provided to assist in diagnosing administrative problems, maintaining and maintaining during illness, and the like. In yet another embodiment, a report is provided, such as daily at the beginning of pump therapy, every time data is uploaded to the integrated medical information management system.

In another embodiment, a user of a comprehensive medical information management system can use the system to obtain treatment options via the internet, email, fax, etc. The system also provides education for patients and physicians through proactive notification with hints and educational guidance via interactive practice software, email, fax, etc. on the Internet. This can include medical condition management and patient risk management.

Online ordering of patient supplies, medications, devices and accessories, including reorder notifications, is also available. Along with this, the comprehensive medical information management system provides comprehensive medical information such as frequently asked questions, explanation manuals, training aids (areas including interactive and non-interactive aids), programming tips, user suggestions, etc. Can provide online product support for products ordered or used by users of the management system. Yet another embodiment may also access illness-based online patient community groups for posting, searching, responding to messages, etc.

Healthcare providers using integrated healthcare information management systems generally receive individual patient data management and recommendations. However, other embodiments manage the overall medical quality, including patient examination and outcome determination (HbA1c test, optometry, etc.) and meet the quality matrix and published clinical standards. Other embodiments can be compared to other patients on a patient-by-patient and overall care basis. A managed medical (HMO) user of a comprehensive medical information management system typically receives medical condition management services. In another embodiment, managed care (HMO) users are provided with support for identifying and managing high risk patients.

In a preferred embodiment of the present invention, to provide a more complete patient record, the patient record is automatically collected and analyzed to more accurately and immediately match the patient's health status with medical regulations. Comprehensive medical information management systems are used for more frequent interactions with health care providers, for providing more information than summarized data than raw data, such as graphics and tables. Other embodiments provide other data collections based on automated patient surveys, supporting both direct patient care as well as online and market-based medical and market research. Yet another embodiment issues an alarm and calls for assistance when it is determined that an abnormal or preselected condition has occurred due to the device used by the user. As another embodiment,
Carbohydrate counters and meal planners can be included to help users assess their carbohydrate consumption and insulin supply needs.

As mentioned above, the integrated medical information management system uses one or more servers to connect to the internet and / or intranet to create the web side. A comprehensive medical information management system website integrates the services and allows you to access the services with a single login with simple and straightforward navigation. For example, a user once connected to a website can enter additional data such as diet and exercise, compose a report, create ad hoc reports as web pages as often as desired, and provide diabetes care by a healthcare provider or patient. Establish regular shipment of items (within policy limits), require extra supplies for travel, lost or spoiled supplies, changed consumption, changed meters You can order additional supplies that you need for reasons such as Supplies also include ancillary items such as syringes, tapes, and ketone test sticks. According to another embodiment, the user can also order pump accessories and other items.

As mentioned above, internet-based training is also available with this comprehensive medical information management system. Typical training modules include, for example, an introduction to diabetes, basic use of insulin pumps, advanced use of insulin pumps, how to operate other equipment, carbohydrate counting, troubleshooting, hypoglycemia prevention, poor health There are daily guidelines, injection site management, etc.
In a preferred embodiment, the carbohydrate calculator can be equipped with the ability to easily transfer the calculation results to a common food, meal planner, patient record of a medical device connected to a medical information management system.

In a particular embodiment, the integrated medical information management system utilizes an email message sent to notify or prompt the patient of various items. Typical pre-programmed emails include notifications for uploading device data, notifications of upcoming healthcare provider appointments, reminders to schedule appointments, supply order and inventory confirmation notices, Clinical or technical service bulletin,
Items such as patient satisfaction surveys can be included. The timing and specific content of these email messages can be determined by the patient, the healthcare provider, the managed healthcare (HMO) provider, all of them, and so on. Another embodiment is a service that provides a comprehensive reminder function that is used to send any reminder email messages related to diabetes care. Both health care providers and patients can decide on services that provide reminder. The system can also be configured to generate (or suggest) an automatic reminder based on the uploaded data (eg, measuring blood glucose level at 2:00 am to the patient twice a week). Urge you to).

In another embodiment, the user uses a continuous blood glucose monitor to monitor the patient's hypoglycemic condition and take action when the hypoglycemic condition is detected. A blood glucose monitor receiver is disclosed in a communication device (eg, Telemetered Characteristic Moni, filed Aug. 19, 1999, incorporated herein by reference).
tor System and Method of Using the S
US patent application Ser. No. 09 / 377,472 (PCT published patent WO
(Published as 00/18449), etc.),
The communication device monitors the blood glucose level and, when a predetermined level is reached, initiates communication with the integrated medical information management system. Next, the comprehensive medical information management system takes a selected action such as notifying a family member, a medical provider, or an emergency department.

In certain embodiments, upon request, the data files uploaded from the patient's infusion device or other device are transferred to the clinical department and the potential product,
Helps diagnose configuration problems. The ability of the clinical services to remotely signal the pump of the infusion device in real time can be optional.

In its most basic form, all interaction between the integrated medical information management system and the patient is done through the upload procedure only, and all interaction with the healthcare provider (to determine the patient in charge and configure the report template) is done by phone. (IVR or live agent) (ie no computer required). In addition, Internet access provides the healthcare provider with a secure Internet interface.

For data transmission, a flexible and robust protocol is used that allows data from a plurality of different types of devices to be combined and expanded to new devices and data types. This protocol isolates all but the bottom layer of software from the details of a particular device. This protocol incorporates a data format suitable for storing in a file. Such files can be stored for permanent storage, stored data, sent via email for forward transfer, etc.

FIG. 7 is a block diagram showing the structure of the data bus 400 used in the embodiment of the comprehensive medical information management system. The data bus has various data values 410, date and time 404, and other information (data type 406, device information 408).
) And so on. The data element 402 is a set 41 of data elements.
6 can be linked together. The data bus 400 may also include a set of data elements 412 that organizes the data elements into groups, which groups related data elements (such as data element 402) in various forms. Data element set 412
Includes a data element 402, set information 414 for linking a set 412 of data elements together, and the like. The data bus 400 also includes a database interface 418 for interfacing with a database, as described above. Using these data bus elements, the user can connect different devices without having to know the data structure of each device in detail.

The design goals of the data bus 400 are as follows. Nature: This term refers to the idea that programmers can easily write code without the need for undue complexity or regular reference to documents. Almost English-friendly code for programmers familiar with the system. Transparent: This term refers to the idea that data can be processed regardless of the data itself, or the particular number or organization of its origin. High-level operation is supported without using a complicated control structure. This is best accomplished by bringing together as many detail items as possible in the lower layers of the architecture. General: This term refers to the idea of designing a function or structure with the utmost consideration of possible problems. This feature allows the system to be applied to new data sources or applications with little or no modification.

In the preferred embodiment, the data bus 400 is implemented as a collection of taxonomies (ie, object definitions), which is used for comprehensive medical information management systems and other data types, transfer, storage, analysis, and reporting. Used internally by software applications. In the preferred embodiment, only the lowest layer of the device's communication module performs device-specific processing. In general, some reporting functions require device-specific knowledge, but this dependency is kept to a minimum and data from multiple devices can be transparently combined. Programmers using the data bus can store different types of data combinations from one or more instruments in a database in a single, simple line operation without the need for special formatting or conversion. Data can also be transparently recalled from a database based on various criteria such as instrument type (injector, monitor, meter, etc.) or date and time range.

The data bus 400 is designed to facilitate data processing and to be as unrelated to device-specific constraints as possible. The basic intent is to provide programmers with a powerful toolset that allows them to write complex reports with data by writing a small amount of natural code. For example, a programmer can express a calculation in just a few lines of code, such as "find all measured blood glucose levels for the last week and calculate the average value for each time bucket on parallel (mode) days." This calculation is complex in that it parameterizes database readings, transforms date / time stamps into only time stamps, collects data into buckets, and aggregates multiple average calculations. The data bus 400 is also tightly integrated with the report layout and rendering subsystems so that these systems can share common languages, object definitions, and data structures.

In a preferred embodiment, the data bus structure contains the report data along with the structure of the source data that mirrors the actual report. These data structures and the application programming interfaces provided to access the data structures allow the report generation mechanism to interact with the data structures and extract the data for the report in a very simple manner.

In the preferred embodiment, the individual data elements 402 represent data on the data bus 400 as a basic unit of equipment or other data. In its simplest form, data element 402 consists of a date / time stamp and a numeric value and is associated with a particular medical device and a particular patient.

The individual data elements are typically used with the data bus as follows. a) Created by the device object as part of the upload operation.
Data elements 402 from the same upload operation are associated as one dataset. b) Transferred through the modem from the remote data collection location to the system where the software application is running. c) Stored in the database. d) Searched by criteria corresponding to individual report components. e) Integrated and analyzed by report logic. A new data element 402 or set of data elements 412 can be created by the result of a calculation or transformation. f) It is output as a report through the report creating mechanism that crosses the data structure created by the report logic.

In the preferred embodiment, the collection of data elements 412 serves two purposes.
That is, a) represent a collection of data elements 402 that are collected or organized according to some criteria (the collection of data elements 412 is used as a container in creating any data hierarchy), and b) data elements 402. Or to represent a calculation or transformation on a set of data elements 402.

In the preferred embodiment, the following steps generally describe the flow along the data bus. Collection-An object representing a particular type of device communicates with the device for uploading information about the device, and then creates a collection of data elements 402 representing the uploaded information along with other information about the device and the upload operation. Transfer-A set of these sets is uploaded from a remote computer or other device to a server running an application. Save-The program on the server collects the transferred information and saves it in the database. Data Retrieval-The reporting application determines what kind of report should be generated. Based on the report type, the application extracts the data from the database as one or more collections of data elements 402. Data Analysis-A report is composed of individual report components that are organized hierarchically (some components can perform their own data retrieval operations).
Report components are divided into two basic types: charts and numerical / tabular information. Preferably, each component uses data bus elements and custom logic to assemble report data in a report-friendly manner and perform calculations on the data. The results of these calculations are stored in the report data structure. In general, the report data structure mirrors the structure of the report itself. Report Creation-From the top of the hierarchy, each report component is instructed to create its subreport. Reporting is accomplished using templates for each report component. Because the data structure typically reflects the report itself, the instructions to extract information from the data structure to create a tabular report can be embedded in its component template without additional computer or logic. it can. Because charts are more complex, each chart typically requires some degree of specific data processing and chart formatting logic.

While the above description is directed to specific embodiments of the present invention, it should be understood that many modifications may be made without departing from the spirit of the invention. The appended claims are intended to cover such modifications as would fall within the scope and spirit of the invention.

Accordingly, the presently disclosed embodiments are illustrative in all respects and are not limiting, the scope of the invention being indicated by the appended claims rather than the foregoing description, and All changes that come within the meaning and range of the claims are to be included therein.

[Brief description of drawings]

FIG. 1 is a system configuration diagram of a comprehensive medical information management system according to an embodiment of the present invention.

FIG. 2 is a system configuration diagram of a prototype comprehensive medical information management system according to another embodiment of the present invention.

3 is a block diagram showing in more detail a report application used by the comprehensive medical information management system shown in FIG. 1. FIG.

4 is a block diagram showing in more detail a report application used by the comprehensive medical information management system shown in FIG. 1. FIG.

5 is a block diagram showing in more detail a report application used by the comprehensive medical information management system shown in FIG. 1. FIG.

FIG. 6 is a block diagram illustrating a method for uploading data from an infusion device, monitor, meter to a PC, laptop or internet through a user interface according to an embodiment of the present invention.

FIG. 7 is a block diagram showing a structure of a data bus used in the comprehensive medical information management system.

FIG. 8 is a diagram showing an example of a data management application for a specific market field.

FIG. 9 is a diagram of an interactive reporting screen used by a healthcare provider to obtain detailed reports on the Internet.

FIG. 10 is a diagram showing reports for three days generated in response to a report generation request from the screen shown in FIG.

11 is an enlarged view of the first day shown in FIG.

FIG. 12 is an enlarged view of the second day shown in FIG.

FIG. 13 is an enlarged view of the third day shown in FIG.

FIG. 14 is a comparative diagram showing a comparison of each day by superimposing the reports for three days shown in FIG. 10 on the same graph.

FIG. 15 is a diagram showing an aggregate chart report for two weeks including blood glucose monitor data, mode date, aggregate statistics of blood glucose level, and insulin use status report.

─────────────────────────────────────────────────── ─── Continued front page    (81) Designated countries EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, I T, LU, MC, NL, PT, SE), OA (BF, BJ , CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, K E, LS, MW, MZ, SD, SL, SZ, TZ, UG , ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, CA, CH, CN, C U, CZ, DE, DK, EE, ES, FI, GB, GD , GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, KP, KR, KZ, LC, L K, LR, LS, LT, LU, LV, MD, MG, MK , MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, T M, TR, TT, UA, UG, UZ, VN, YU, ZW

Claims (65)

[Claims] 1. A comprehensive medical information management system comprising: at least one online central server containing patient-related data for at least one patient and interactively accessing patient-related data for at least one patient. At least one remote access terminal, the remote access terminal being used to generate an interactive report on the at least one remote access terminal based on the patient-related data for the at least one patient; A comprehensive medical information management system including: 2. The comprehensive medical information management system according to claim 1, wherein the at least one online central server is connected to the at least one remote access terminal through an Internet connection. Medical information management system. 3. The integrated medical information management system of claim 2, wherein the at least one remote access terminal interactively accesses the at least one online central server using an internet web browser. A characteristic comprehensive medical information management system. 4. The comprehensive medical information management system according to claim 1, wherein the patient-related data is data on diabetes. 5. The comprehensive medical information management system according to claim 4, wherein the patient-related data is drug injection data. 6. The comprehensive medical information management system according to claim 4, wherein the patient-related data is blood glucose monitor data. 7. The comprehensive medical information management system according to claim 4, wherein the patient-related data is blood glucose meter data. 8. A comprehensive medical information management system, comprising: at least one online central server containing patient-related data for at least one patient; and at least one medical device for treatment of a patient's illness, A medical device having a memory for storing data relating to the device; and at least one data receiving device for receiving data from the at least one medical device and uploading the data to the at least one online central server as patient-related data. , An at least one remote access device for receiving patient-related data from the online central server. 9. The integrated medical information management system of claim 8, wherein the at least one remote access device interactively accesses the patient related data for the at least one patient, A comprehensive medical information management system for use on at least one remote access terminal to generate an interactive report based on the patient-related data for the at least one patient. 10. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system according to claim 1, wherein the at least one online central server is connected to the at least one remote access device through an internet connection. 11. The integrated medical information management system according to claim 10, wherein the at least one remote access device interactively accesses the at least one online central server using an internet web browser. Comprehensive medical information management system featuring. 12. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system, wherein the patient-related data is data on diabetes. 13. The comprehensive medical information management system according to claim 12, wherein the patient-related data is drug injection data. 14. The comprehensive medical information management system according to claim 12, wherein the patient-related data is blood glucose monitor data. 15. The comprehensive medical information management system according to claim 12, wherein the patient-related data is blood glucose meter data. 16. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the at least one remote access device is a facsimile. 17. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system, wherein the at least one medical device is an injection device. 18. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system, wherein the at least one medical device is a blood glucose monitor. 19. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system, wherein the at least one medical device is a blood glucose meter. 20. The comprehensive medical information management system according to claim 8,
The integrated medical information management system, wherein the at least one remote access device is used to receive an email report. 21. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system according to claim 1, wherein the at least one data receiving device includes a device capable of receiving a report creation request from the at least one online central server. 22. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system according to claim 1, wherein the at least one data receiving device includes a device capable of receiving a request for ordering supplies. 23. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system according to claim 1, wherein the at least one data receiving device includes a device capable of receiving a request for establishing a reservation schedule. 24. The comprehensive medical information management system according to claim 8,
Further, regardless of configuration programming, by the at least one patient,
A comprehensive medical information management system, comprising a data bus enabling different types of said at least one medical device to access said at least one data receiving device. 25. The comprehensive medical information management system according to claim 8,
The at least one remote access device further includes the ability to order supplies through the at least one online central server based on data uploaded from the at least one medical device. Management system. 26. The comprehensive medical information management system according to claim 8,
Further, the comprehensive medical information management system includes a communication station between the at least one medical device and the at least one data receiving device. 27. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system according to claim 1, wherein the at least one online central server automatically generates a report at a predetermined time. 28. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized by reports sent by mail. 29. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized by creating a group report of at least one patient or more. 30. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that reports are sent to a managed healthcare provider (HMO). 31. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the at least one online central server is connected to the at least one remote access device through an intranet connection. 32. The comprehensive medical information management system according to claim 8,
Furthermore, a comprehensive medical information management system characterized by including a function for setting up a reservation schedule. 33. The comprehensive medical information management system according to claim 8,
Further, a comprehensive medical information management system including a function of issuing a bill to a client. 34. The comprehensive medical information management system according to claim 8,
Further, a comprehensive medical information management system including a function of processing an insurance claim. 35. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is blood glucose consumption data. 36. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is automatically taken in by the at least one medical device. 37. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is manually input by the patient. 38. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is exercise data. 39. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is calorie burn data. 40. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is drug consumption data obtained from an information source independent of infusion data. 41. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that the data is inspection data in an inspection room. 42. The comprehensive medical information management system according to claim 8,
An integrated medical information management system, wherein the patient can view the data when the at least one remote access device receives the data. 43. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that the data is used to create a report. 44. The comprehensive medical information management system according to claim 8,
The data is a graphics element, a text element, a numeric element, which indicates the data.
A comprehensive medical information management system characterized by being used to create a report including components selected from a group of table elements. 45. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that the data is used to create a report on the use of medical supplies. 46. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, wherein the data is used to create a report that provides results regarding the use of the medical supplies. 47. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system, characterized in that the data is used for defining a problem or problem, or for creating a report for identifying and executing adjustment. 48. The comprehensive medical information management system according to claim 47, wherein the comprehensive medical information management system uses an expert logic to clearly indicate a problem or a problem. system. 49. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that the data is used to create a report that clearly indicates or proposes matters to be adjusted in a treatment plan. 50. The comprehensive medical information management system according to claim 8,
A comprehensive medical information management system characterized in that the data is used to create a report that clearly indicates or suggests matters to be adjusted in a lifestyle. 51. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system uses the same report format regardless of the type of at least one medical device, at least one data receiving device, or at least one remote access device used in the comprehensive medical information management system. A comprehensive medical information management system characterized by creating reports using it. 52. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system includes a function of collecting a part of all the data on the at least one online central server into a single data storage device and a report creating mechanism. . 53. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system includes a function of gathering or arranging a part of all the data on the at least one online central server into one report. 54. The comprehensive medical information management system according to claim 8,
The comprehensive medical information management system may refer to different parts of the data separately to different parts of the data based on a part of the total data on the at least one online central server. A comprehensive medical information management system characterized by including a function of summarizing results and suggestions by associating them in a way that is possible. 55. A data storage and reporting system, comprising a data bus that enables collecting data from a wide variety of medical devices that use a wide variety of data formats and types, the data bus comprising: Collect data in a way that is independent of the provider, patient or system that requires awareness of the different formats and types of data,
A comprehensive medical information management system characterized by being able to report. 56. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system converts various data formats from the various medical devices into one consistent storage format. Comprehensive medical information management system characterized by: 57. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system stores mixed data from the various medical devices in a database in a single process. A comprehensive medical information management system characterized by being capable of 58. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system converts various data formats from various medical devices into one consistent reporting format. A comprehensive medical information management system characterized by that. 59. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system can store and represent data from different medical devices in a consistent display format. A comprehensive medical information management system characterized by that. 60. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system develops a program code for handling data from different medical devices and handling each of the different medical devices individually. A comprehensive medical information management system characterized by being able to store, process, and report regardless of. 61. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system operates from different medical devices irrespective of the mixture of different medical data devices from which data is provided. A comprehensive medical information management system that is capable of simultaneous calculation of combined data. 62. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system combines data from different medical devices and integrates them as different groups into one calculation. A comprehensive medical information management system that can be performed by processing. 63. The comprehensive medical information management system according to claim 62, wherein the comprehensive medical information management system is a daily average of blood glucose levels measured by a plurality of different blood glucose meters during a certain period. A comprehensive medical information management system characterized in that values can be calculated in a single process. 64. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system uses data from new different medical devices with the addition of minimal programming. A comprehensive medical information management system characterized by being incorporated into an information management system. 65. The comprehensive medical information management system according to claim 55, wherein the comprehensive medical information management system has different data formats and types of data that can be combined into one uniform report or graph. However, a comprehensive medical information management system is characterized in that data obtained from different medical devices having the same purpose can be used.