HK1146118B - Blood glucose level measuring system - Google Patents

Description

Blood sugar level measuring system

Technical Field

The present invention relates to a technique suitably applied to a blood glucose level measuring system and a measurement data management device.

More specifically, the present invention relates to a blood glucose level measuring system capable of safely and reliably measuring blood glucose levels and administering insulin to a plurality of patients in a hospital.

Background

It is known that diabetes is caused by abnormal insulin (insulin) secretion from the pancreas. Therefore, the diabetic needs to measure the blood glucose level before meals and administer insulin in accordance with the blood glucose level.

Conventionally, the applicant has developed and sold a blood glucose level measuring apparatus that is miniaturized in order to measure the blood glucose level of a patient or a family member of the patient easily at home. Patent documents 1 and 2 show patent applications of the blood glucose level measuring apparatus of the applicant.

Patent document 1: japanese laid-open patent publication No. 10-19888

Patent document 2: japanese laid-open patent publication No. 10-318928

Disclosure of Invention

Problems to be solved by the invention

There are reports reflecting the following facts: in hospitals where many patients are hospitalized, the home blood glucose level measuring apparatus is used directly at the medical site.

However, the blood glucose level measuring device for home use has only a function of simply measuring the blood glucose level, and is not provided with a safety function for preventing accidents such as mistaken patients or repeated insulin injections.

Further, for example, a function considering the efficiency of medical work is not provided in which blood glucose level measurement processing and insulin administration processing for a large number of patients are collectively performed.

Currently, a new blood glucose level measuring device is required which is improved in terms of safety, work efficiency, and the like for medical practice.

The blood glucose level measuring apparatus for medical use needs not only a single blood glucose level measuring apparatus but also an apparatus for managing blood glucose level measurement data and insulin administration data collected by the blood glucose level measuring apparatus for each patient, because of the characteristic of handling a large number of patients.

In order to prevent medical accidents such as forgetting to measure the blood glucose level and forgetting to administer insulin, it is necessary to provide a blood glucose level measuring device with not only a function for preventing accidents but also a warning display function for a device for managing data.

The present invention has been made in view of the above circumstances, and an object thereof is to provide a safe blood glucose level measuring system that prevents medical accidents such as forgetting to measure the blood glucose level and forgetting to administer insulin.

When a blood glucose level measuring apparatus is used in a hospital, a nurse who measures blood glucose levels often measures blood glucose levels of a plurality of patients. In this case, the insulin administration treatment is often performed simultaneously.

It is well known that the work of nurses in medical practice is heavy. Therefore, medical accidents such as forgetting to measure blood glucose levels and administer insulin to a plurality of patients tend to occur.

An object of the present invention is to provide a new measurement data management device and a blood glucose level measurement system, including: in order to solve the above-described problem, it is possible to promptly warn that the blood glucose level measurement and/or the insulin administration treatment have been forgotten to be performed on a plurality of patients, and to promptly perform these treatments again.

Means for solving the problems

In order to solve the above problems, a blood glucose level measuring system according to the present invention includes: a blood glucose meter is provided with: a measurement unit for measuring a blood glucose level; a nonvolatile memory that stores a blood glucose level measurement table in which the measured blood glucose level is recorded; and a transmission unit that transmits the blood glucose level measurement table; and a measurement data management device provided with: an insulin administration instruction table having a patient ID field and a measurement scheduled time field for blood glucose level measurement; a patient history table having a patient ID field, a predetermined date and time of measurement field, a blood glucose value field, and an unfulfilled flags field; a receiving unit connected to the blood glucose meter to receive the blood glucose level measurement meter; an implemented-patient history processing unit that records a record obtained from the received blood glucose level measurement table in a patient history table as a record with an unproductive flag field of "false"; an unexecuted patient history processing unit which additionally records a record obtained by searching for a patient ID for which a blood glucose level measurement is scheduled within a predetermined time from the current time from a measurement scheduled time field of an insulin administration instruction table as a record of which an unexecuted flag field is true, to a patient history table; an unproductive patient warning processing unit that determines whether or not there is a record whose unproductive flag field is "true" by searching a patient history table; a display control unit that generates a warning display when the non-implemented patient warning processing unit determines that a record having a non-implemented flag field of "true" is present in the patient history table; and a display unit that displays the warning display generated by the display control unit.

In order to solve the above problem, a measurement data management device according to the present invention includes: a patient information table including a round type processing field (round type input field) in which instructions on whether to perform a blood glucose level measurement operation and a medication administration operation, which are included in data transmitted to a blood glucose meter, are recorded for each patient; a patient history table including a medication administration result field in which a result of execution of a blood glucose level measurement operation and a result of execution of a medication administration operation, which are included in data received from a blood glucose meter, are recorded for each patient; and a control unit that compares the values of the cycle type field and the drug administration result field during execution, generates a warning message if a mismatch is found, creates data necessary for performing a blood glucose level measurement operation or a drug administration operation for each patient associated with the mismatch, and transmits the created data to the blood glucose meter.

The non-patient history processing unit periodically searches the insulin administration instruction table, checks a patient for whom blood glucose level measurement is not performed, and writes a record of the patient for which blood glucose level measurement is not performed in the patient history table. At this point, the unfulfilled field of the record that was appended to the patient history table is set to "true".

On the other hand, the patient history processing unit writes the record of the patient whose blood glucose level has been measured into the patient history table based on the blood glucose level measurement table downloaded from the blood glucose meter. At this time, the non-implemented field of the record that is additionally recorded in the patient history table is set to "false".

The non-implemented patient warning processing unit periodically searches the patient history table, and when it is found that there is a record whose non-implemented field is "true", controls to display a warning.

The processing performed by the patient history processing unit is prioritized over the processing not performed by the patient history processing unit. The record previously additionally recorded by the non-implemented patient history processing unit can be overwritten by the implemented patient history processing unit.

The measurement data management device maintains, in a patient information table on its own side, the type of implementation content included in data transmitted from itself to the blood glucose meter. After the data received from the blood glucose meter is read and written in the patient history table, it is checked whether or not the blood glucose level measurement and/or the insulin administration is performed as instructed. If the result of the comparison shows a mismatch, it can be determined that the blood glucose level measurement and/or insulin administration has not been performed. A warning message is generated based on the determination, and a patient who has forgotten to perform blood glucose level measurement and/or insulin administration and the contents to be performed are generated again, and cycle data is transmitted to the blood glucose meter.

ADVANTAGEOUS EFFECTS OF INVENTION

According to the present invention, it is possible to provide a safe blood glucose level measurement system that prevents medical accidents such as forgetting to measure the blood glucose level or forgetting to administer insulin.

Further, according to the present invention, it is possible to provide a new measurement data management device and a blood glucose level measurement system that can promptly warn of forgetting to perform blood glucose level measurement and/or insulin administration treatment on a plurality of patients and that can promptly re-execute these treatments.

Drawings

Fig. 1 is an overall schematic diagram of a blood glucose level measurement system according to an embodiment of the present invention.

Fig. 2 is an external perspective view of a blood glucose meter according to an embodiment of the present invention.

Fig. 3 is a diagram of a blood glucose meter as an example of the present embodiment, as viewed from four directions.

Fig. 4 is an external view of the holder in a state where the blood glucose meter is separated from the holder (cradle).

Fig. 5 is an external view of the holder in a state where the blood glucose meter is attached to the holder.

FIG. 6 is an internal block diagram of a blood glucose meter.

Fig. 7 is an internal block diagram of the cradle.

Fig. 8 is a block diagram showing a connection state between the blood glucose meter, the cradle, and the measurement data management apparatus.

Fig. 9 is a block diagram of the measurement data management apparatus.

Fig. 10 is a functional block diagram of the measurement data management apparatus.

Fig. 11 shows an example of a table provided in the measurement data management apparatus.

Fig. 12 is a diagram showing a top menu window (top menu window) displayed on the display unit of the measurement data management apparatus.

Fig. 13 is a functional block diagram of a patient history processing unit.

Fig. 14 shows fields of a blood glucose level measurement table received from a blood glucose meter.

Fig. 15 is a flowchart showing a flow of the operation of the patient history processing unit.

Fig. 16 is a flowchart showing the flow of the operation of the patient history table recording process.

Fig. 17 is a schematic diagram showing an alarm window.

Fig. 18 is a functional block diagram of a patient history processing unit.

Fig. 19 is a flowchart showing a flow in which the operation of the patient history processing unit is not performed.

Fig. 20 is a functional block diagram of a patient warning processing unit.

Fig. 21 is a flowchart showing a flow of the operation of the patient warning processing unit.

Fig. 22 is a flowchart showing a flow of an operation in which the list display processing is not performed.

Fig. 23 is a diagram showing a state of the top menu window when a predetermined time has elapsed since a scheduled time for blood glucose level measurement.

Fig. 24 is a diagram showing an unexecuted person list window.

Fig. 25 is a schematic diagram illustrating a flow of a blood glucose measurement operation performed by a blood glucose meter according to an embodiment of the present invention.

Fig. 26 is a diagram recording the internal structure and relationship of each table.

Fig. 27 is a flowchart showing a flow of communication between the blood glucose meter and the measurement data management apparatus.

Fig. 28 is a flowchart showing a flow of communication between the blood glucose meter and the measurement data management apparatus.

FIG. 29 is a functional block diagram of a blood glucose meter.

FIG. 30 is a state transition diagram of the blood glucose meter.

Fig. 31 is a flowchart showing a flow of processing of the blood glucose meter.

Fig. 32 is a flowchart showing a flow of processing of the blood glucose meter.

Fig. 33 is a functional block diagram of the measurement data management apparatus.

Fig. 34 is a flowchart showing a flow of processing in which the measurement data management apparatus transmits patient data and the like to the blood glucose meter.

Fig. 35 is a flowchart showing a flow of processing in which the measurement data management apparatus receives patient measurement data from the blood glucose meter.

Fig. 36 is a flowchart showing a flow of processing in which the measurement data management apparatus receives patient measurement data from the blood glucose meter.

Fig. 37 is a diagram showing a main menu window displayed on the display unit of the measurement data management apparatus.

Fig. 38 is a schematic diagram showing changes in data existing between the measurement data management apparatus and the blood glucose meter and in the flag included in the table.

Description of the reference numerals

101: a blood glucose level measuring system; 102: a blood glucose meter; 103: a bracket; 104: a measurement data management device; 105: a USB cable; 112: an internal patient table; 114: patient data; 115: user base data; 116: chip lot data (tip lot); 117: patient measurement data; 202: an optical measuring section; 203: an LCD; 204: a power switch; 205: cursor keys (cursor keys); 206: an enter key (enter key); 207: a bar code key; 208: a bar code reader; 209: a power supply terminal; 210: an infrared communication window; 211: a battery cover; 212: a measurement chip; 302: eject lever (reject); 402: a charging terminal; 403: an infrared communication window; 602: a CPU; 603: a ROM; 604: a RAM; 605: a bus; 606: thermistors (thermistors); 607: a calendar clock; 608: an operation section; 609: a light emitting diode; 610: a driver; 611: a D/A converter; 612: a phototransistor (phototransistor); 613: an A/D converter; 614: a non-volatile memory; 615: a display unit; 616: a buzzer; 617: an infrared communication unit; 618: a power supply circuit; 702: a CPU; 703: a ROM; 704: a RAM; 705: a bus; 706: a USB interface; 717: an infrared communication unit; 718: a charging circuit; 902: a bus; 903: a CPU; 904: a ROM; 905: a RAM; 906: a non-volatile memory; 907: a display unit; 908: a USB interface; 909: an operation section; 1002: a display control unit; 1003: a data editing processing unit; 1004: a patient information table; 1005: insulin administration indicator; 1006: a patient history table; 1007: a scheduler (scheduler); 1008: a calendar clock; 1009: a non-patient history processing unit; 1010: a patient warning processing unit not being implemented; 1012: a blood glucose meter detection unit; 1011: an implemented patient history processing section; 1202: a top menu window; 1203: a glucometer status display bar; 1204: a "cycle data transfer" button; 1205: a "measurer setup transmission" button; 1302: a blood glucose meter receiving unit; 1303: a implemented patient temporary file; 1304: non-implementation of patient temporary files; 1305: a control unit; 1702: an alarm window; 1703: a "list of non-implementers" display bar; 1704: a "measure again" button; 1705: a "transmit" button; 1802: a search section; 1803: a temporary file; 1804: an additional recording unit; 2002: a search section; 2003: a temporary file; 2302: a warning message; 2402: list window of non-implementers; 2403: an "OK" button; 2404: a "back" button; 2502: a patient; 2503: a patient ID; 2504: a nurse; 2505: a user ID; 2506: a cartridge; 2507: chip batch numbering; 2508: an injector; 2509: a sliding scale (slidingscale); 2902: an input/output control unit; 2903: a display control unit; 2904: a patient data conversion unit; 2905: a patient measurement data conversion unit; 3302: a blood glucose meter detection unit; 3303: a blood glucose meter operating section; 3304: a user interface control section; 3305: a meter input/output unit; 3306: a patient measurement temporary file; 3702: a main menu window; 3703: a glucometer status display bar; 3704: illustration (illustation); 3705: a connection status display bar; 3706: a nickname display column; 3708: a warning message.

Detailed Description

An embodiment of the present invention will be described below with reference to fig. 1 to 38.

Two embodiments are described in this embodiment.

First, an embodiment common to both embodiments will be described with reference to fig. 1 to 9.

Next, the first embodiment will be described with reference to fig. 10 to 24.

Next, a second embodiment will be described with reference to fig. 25 to 38.

[ blood sugar level measurement System 101]

Fig. 1 is a schematic diagram of the entire blood glucose level measurement system as an example of the present embodiment.

Blood glucose level measurement system 101 is composed of blood glucose meter 102 as a blood glucose level measurement device, cradle 103, and measurement data management device 104.

The blood glucose meter 102 is a portable device that operates using a secondary battery such as a lithium ion battery, and has a size approximately equal to the size of a palm of an adult.

When a doctor, a nurse, or the like measures a blood glucose level of a patient, the blood glucose meter 102 is generally taken to a ward in a hospital, and a very small amount of blood of the patient is extracted to measure the blood glucose level.

After the blood glucose level is measured and insulin is administered, the blood glucose meter 102 must be placed on the cradle 103.

The cradle 103 takes on the role of an interface for charging the battery of the blood glucose meter 102 and for transmitting and receiving data between the blood glucose meter 102 and the measurement data management apparatus 104.

The subject of the blood glucose meter 102 transmitting and receiving data through the cradle 103 is the measurement data management apparatus 104.

A measurement data management apparatus 104 constituted by a personal computer is connected to the cradle 103 via a USB cable 105.

A known OS (operating system) runs on the measurement data management device 104. And a program that causes the personal computer to realize the function as the measurement data management apparatus 104 is run on the OS.

When the blood glucose meter 102 is mounted to the cradle 103, communication is immediately performed between the blood glucose meter 102 and the measurement data management apparatus 104 via the cradle 103. At this time, if the internal patient table 112 is stored in the blood glucose meter 102, the measurement data stored in the internal patient table 112 is converted into patient measurement data 117, and immediately thereafter, the converted measurement data is transmitted to the measurement data management apparatus 104.

Further, by transmitting a predetermined command from the measurement data management apparatus 104, the measurement data management apparatus 104 can download blood glucose meter setting data, not shown, from the blood glucose meter 102.

Also, the measurement data management device 104 can upload the patient data 114, the user basic data 115, and the chip batch data 116 to the blood glucose meter 102.

These data are described in detail later.

[ appearance: blood glucose meter 102)

Fig. 2 (a) and (b) are external perspective views of the blood glucose meter 102.

Fig. 3 (a), (b), (c), and (d) are views of the blood glucose meter 102 viewed from four directions.

For convenience of explanation, the side provided with the LCD shown in fig. 2 (a) and 3 (a) is referred to as a main body front side, and the side provided with the battery cover shown in fig. 2 (b) is referred to as a main body rear side.

As shown in fig. 3 (a) and (c), an optical measurement unit 202 is provided at the distal end of the blood glucose meter 102.

The optical measurement unit 202 has a shape in which a blood glucose measurement chip 212 (hereinafter referred to as "measurement chip 212") can be attached and detached. By operating the eject lever 302, the used measurement chip 212 can be removed from the optical measurement section 202.

On the side (main body surface) where the LCD 203 as a liquid crystal display device is provided shown in fig. 2 a and 3 a, a power switch 204, a cursor key 205, an input key 206, and a barcode key 207 are provided beside the LCD 203.

The power switch 204 is a switch for turning on and off the power of the blood glucose meter 102.

The cursor key 205 is a key that moves a cursor to select one of a plurality of items displayed in the LCD 203.

The input key 206 is a key that performs an instruction of "execute" or "select" an item selected by the cursor.

The barcode key 207 is a button for operating a barcode reader 208 shown in fig. 3 (d), and the barcode reader 208 is provided on the side opposite to the optical measurement section 202 of the blood glucose meter 102.

The barcode reader 208 is a barcode reader configured by a combination of a known red laser diode and a light receiving element such as a phototransistor. Further, an image sensor such as a CCD or a CMOS can be used instead of the light receiving element.

The basic structure of the blood glucose meter 102 for measuring blood glucose is the same as that of the related art. The outline will be briefly described below.

The measurement chip 212 is mounted on the optical measurement unit 202, and the measurement chip 212 absorbs blood of a measurement target person who has punctured a fingertip with a puncture tool and has oozed out, for example. The measurement chip 212 contains a test paper made of a porous membrane (e.g., polyethersulfone (polyethersulfone)). When the blood drawn by the measurement chip 212 permeates into the test paper (test paper), it reacts with the reagent contained in the test paper and develops color. This color reaction takes several seconds to about ten and several seconds, but the reaction time is affected by the ambient temperature.

After a predetermined reaction time has elapsed, the test piece is irradiated with light by causing the light-emitting element to emit light, and the light-receiving element receives the reflected light from the test piece. Then, the analog light reception intensity signal obtained from the light receiving element is converted into a digital value, and the digital value is converted into a blood glucose level and displayed on the LCD 203.

The blood glucose level measurement structure on the blood glucose meter 102 side is not limited to the optical measurement method using a color developing reagent, and a conventionally available blood glucose measurement structure such as an electrochemical sensor method can be used.

As shown in fig. 2 (b), a power supply terminal 209 and an infrared communication window 210 are provided on the barcode reader 208 side on the back surface of the main body. When the blood glucose meter 102 is mounted on the cradle 103, the power supply terminal 209 comes into contact with a charging terminal 402 (see fig. 4) provided on the cradle 103 to perform charging, and performs infrared communication with the cradle 103. In addition, a battery cover 211 is provided on the rear surface of the main body.

[ appearance: bracket 103)

Fig. 4 (a) and (b) are external views of the cradle 103 in a state where the blood glucose meter 102 is detached from the cradle 103, and fig. 5 (a) and (b) are external views of the cradle 103 in a state where the blood glucose meter 102 is attached to the cradle 103.

As shown in fig. 4 (a) and (b), a charging terminal 402 is provided on the cradle 103 at a position facing the power supply terminal 209 of the blood glucose meter 102. Similarly, an infrared communication window 403 is provided in the cradle 103 at a position facing the infrared communication window 210 of the blood glucose meter 102.

The infrared communication window 210 of the blood glucose meter 102 and the infrared communication window 403 of the cradle 103 are respectively provided with an infrared light emitting diode and a phototransistor. They constitute an Infrared serial communication interface complying with the well-known IrDA (Infrared Data Association) standard.

As shown in fig. 1, the cradle 103 is connected to the measurement data management apparatus 104 via a USB cable 105. Since the cradle 103 has a function of charging the battery of the blood glucose meter 102 and a plurality of cradles 103 can be connected to one measurement data management apparatus 104, the cradle 103 is configured as a self-powered device that does not receive power supplied from the USB terminal of the measurement data management apparatus 104.

[ hardware: blood glucose meter 102)

Fig. 6 is an internal block diagram of the blood glucose meter 102.

The blood glucose meter 102 includes a CPU 602, a ROM 603, a RAM 604, and a bus 605 connecting these components. The bus 605 is connected to a portion that provides a data input function and a portion that provides a data output function, in addition to the above-described configuration.

Hereinafter, the CPU 602, ROM 603, RAM 604, and bus 605 will be referred to as a microcomputer constituting the blood glucose meter 102 for convenience.

The data input function portion of the blood glucose meter 102 includes an optical measurement unit 202 for obtaining blood glucose level measurement data, a thermistor 606 for obtaining temperature data, a barcode reader 208, a calendar clock 607, and an operation unit 608.

The optical measurement unit 202 includes a light emitting unit including a light emitting diode 609, a driver 610 thereof, and a D/a converter 611 connected to the driver 610, and a light receiving unit including a phototransistor 612 and an a/D converter 613.

The light emitting diode 609 needs to irradiate test paper in the measurement chip 212 with light of an appropriate intensity, and therefore the light emitting diode 609 is controlled to emit light based on intensity data stored in advance in a nonvolatile memory 614 described later. That is, the light emission intensity data is read from the nonvolatile memory 614, converted into an analog voltage signal by the D/a converter 611, and then power-amplified by the driver 610, thereby driving the light emitting diode 609 to emit light.

On the other hand, the a/D converter 613 converts the intensity signal voltage of the light received by the phototransistor 612 into numerical data. The converted numerical data is converted into blood glucose level data by predetermined arithmetic processing performed by the CPU 602, and the blood glucose level data is then recorded in a predetermined area of the RAM 604 and the nonvolatile memory 614.

The blood glucose meter 102 includes a thermistor 606, and the temperature of the environment in which the blood glucose meter 102 is located can be measured from the change in resistance of the thermistor 606. Similarly to the phototransistor 612, the resistance value of the thermistor 606 is digitized by the a/D converter 613, and the numerical data is recorded in a predetermined region of the RAM 604 and the nonvolatile memory 614. Further, since it is not necessary to measure the light reception intensity and the air temperature at the same time, the a/D converter 613 is shared between the phototransistor 612 and the thermistor 606.

The barcode reader 208 emits light from the red laser diode 622, reads a barcode by receiving reflected light by the phototransistor 623, and outputs data recorded in the barcode to the bus 605.

The calendar clock 607 is a well-known IC providing a date and time data output function, also referred to as a "real time clock", and is installed in specifications in many microcomputers, personal computers, and the like.

In the blood glucose meter 102 according to the embodiment of the present invention, date and time information of the time at which the blood glucose level is measured needs to be obtained, and therefore, the date and time information is important information. That is, there is a large relationship between the collected data and the date and time information. It is also necessary to record the date and time information of the time when the blood glucose level is measured, together with the blood glucose level, in the internal patient table 112. Therefore, the calendar clock 607 is expressly and explicitly described in the drawing.

The operation unit 608 is a key switch including a known push button, and includes a cursor key 205 and an input key 206. The operation unit 608 is used when the user operates the blood glucose meter 102 in accordance with the contents displayed on a display unit 615 formed of an LCD, which will be described later.

As a data output function portion of the blood glucose meter 102, there are a display portion 615, a buzzer 616, and an infrared communication portion 617, which are constituted by the LCD 203.

The display unit 615 displays various screens using programs stored in the ROM 603 and executed by the CPU 602. The display screen will be described in detail later.

Buzzer 616 is mainly used to notify the operator of normal reading of the barcode by barcode reader 208, completion of measurement in blood glucose level measurement, completion of infrared communication, or an error message. Depending on the setting, it is also possible to generate a sound every time the operation unit 608 is operated.

As described above, the infrared communication unit 617 is connected to the infrared light emitting diode 619 and the phototransistor 620, and forms an IrDA-standard serial interface. When the power supply circuit 618 detects that power is supplied from the cradle 103 based on a change in the voltage of the power supply terminal 209, the power supply circuit 618 notifies the CPU 602 via the bus 605. Then, when the infrared communication function of the infrared communication unit 617 is activated under the control of the CPU 602 to perform infrared communication with the cradle 103, the various tables stored in the nonvolatile memory 614 are transmitted to and received from the measurement data management device 104 and updated.

That is, when performing infrared communication with the cradle 103, the operation portion 608 or the like of the blood glucose meter 102 does not need to be operated, and infrared communication is performed immediately when the cradle 103 is attached.

The blood glucose meter 102 includes a nonvolatile memory 614 made of an EEPROM, which provides a data storage function, in addition to a data input/output function. The nonvolatile memory 614 stores a patient table 1109, a user table 1113, a chip lot table 1117, a prescription information table 1502, a measurement prescription table 1602, a measurement prescription result table 1408, and the like, which are described later in fig. 11, 14, 15, and 16. These tables are updated upon communication with the measurement data management apparatus 104 via the cradle 103. In addition, a flash memory or the like may be used instead of the EEPROM.

[ hardware: bracket 103)

Fig. 7 is an internal block diagram of the carriage 103.

Fig. 8 is a schematic diagram showing a connection state between the blood glucose meter 102, the cradle 103, and the measurement data management apparatus 104.

As shown in fig. 7, the cradle 103 is configured by a CPU 702, a ROM703, a RAM 704, an infrared communication unit 717 to which an infrared light emitting diode 719 and a phototransistor 720 are connected, a USB interface (I/F)706, a charging circuit 718, and a bus 705 connecting these components, which constitute a personal computer.

When it is detected that the blood glucose meter 102 as a load is connected based on a voltage change of the charging terminal 402, the charging circuit 718 notifies the CPU 702 of the detection via the bus 705. Then, the infrared communication function of the infrared communication unit 717 is activated by the control of the CPU 702, and communication is performed between the blood glucose meter 102 and the measurement data management apparatus 104 via the infrared communication unit 717 and the USB interface 706.

As described above, the blood glucose meter 102 and the cradle 103 are connected by IrDA, and the cradle 103 and the measurement data management apparatus 104 are connected by USB. In this regard, the cradle 103 plays the role of an interface for relaying data communication between the measurement data management apparatus 104 and the blood glucose meter 102.

[ hardware: measurement data management apparatus 104

Fig. 9 is a block diagram of the measurement data management apparatus 104.

As described above, the entity of the measurement data management apparatus 104 is a well-known personal computer.

The measurement data management device 104 has a bus 902 therein. The bus 902 is connected with a CPU 903, a ROM 904, a RAM 905, a nonvolatile memory 906 such as a hard disk drive, a display portion 907 such as an LCD, and a USB interface (I/F) 908. The USB interface 908 is connected to the cradle 103 in addition to an operation unit 909 such as a keyboard and a mouse.

[ first embodiment ]

[ software: measurement data management apparatus 104

Fig. 10 is a functional block diagram of the measurement data management apparatus 104. Fig. 10 is a diagram schematically illustrating the function of a program that realizes the measurement data management function.

A window such as an operation panel as a user interface created by the display control unit 1002 is displayed on the display unit 907 as a display.

Operation information generated from an operation unit 909 such as a keyboard and a mouse is transmitted to each function unit.

The data edit processing unit 1003 operates data of the patient information table 1004, the insulin administration instruction table 1005, the patient history table 1006, and the like.

The scheduler 1007 acquires date and time information from the calendar clock 1008 in real time, and executes a designated program according to an internally stored schedule. The designated program includes the non-patient history processing unit 1009 and the non-patient warning processing unit 1010.

The scheduler 1007 starts the non-patient history processing unit 1009 at predetermined intervals. In the present embodiment, the data editing processing unit 1003 can change the predetermined interval m. For example, 60 minutes.

The patient history record non-implementation processing unit 1009 performs the following processing:

date and time data scheduled for measurement of blood glucose level of a patient who is determined not to have blood glucose level measured is collected and created from insulin administration instruction table 1005,

if a record of the measurement scheduled date and time data of the same patient as the collected and created data is not recorded in the patient history table 1006, the record is added. This process is described in detail later.

The scheduler 1007 starts the non-patient warning processing unit 1010 at predetermined intervals.

When a record satisfying a predetermined condition is found in the patient history table 1006, the patient warning processing unit 1010 does not perform processing for displaying a warning of the patient and various information corresponding to the record. This process is described in detail later.

When the blood glucose meter detecting unit 1012 detects that the blood glucose meter 102 is mounted on the cradle 103, the implemented patient history processing unit 1011 is activated.

The implemented-patient history processing unit 1011 verifies whether or not there is an unproductive patient in the blood glucose level measurement table downloaded from the blood glucose meter 102, and if there is an unproductive patient, performs processing to cause the display unit 907 to display an alarm display for notifying this. This process is described in detail later.

For simplicity of explanation, the present embodiment will be described with the patient measurement data 117 being equal to a blood glucose level measurement table described later.

When the blood glucose meter detecting unit 1012 detects that the blood glucose meter 102 is mounted on the cradle 103, it notifies the display control unit 1002 of the detection.

Upon receiving this, the display control unit 1002 performs display control to be described later.

The program that realizes the function of the measurement data management apparatus 104 is composed of a plurality of programs.

The non-patient history processing unit 1009, the non-patient warning processing unit 1010, and the executed patient history processing unit 1011 are programs that operate independently of each other. Since these programs operate simultaneously and in parallel, the OS is preferably a multitask OS.

Alternatively, instead of a plurality of programs, a single program having a multi-thread function may be used. In this case, it may be a single-tasking OS.

These programs and threads perform exclusive control when performing write operations to various tables using a known file locking mechanism or the like.

Fig. 11 shows an example of a table provided in the measurement data management apparatus 104. These three tables are illustrated in terms of sampled data.

The patient information table 1004 is a table that is unique to each patient ID and is composed of a patient ID field and a patient name field.

The insulin administration instruction table 1005 is a table for specifying the time for which blood glucose level measurement and insulin administration are performed from the morning to the evening and the prescription raft data used when insulin is administered to each patient. The table is composed of a serial number field for uniquely identifying each record, a patient ID field, a measurement scheduled time field, an insulin therapy classification field, and a scale ID field.

The reason why the same patient ID is present in a plurality of numbers in the patient ID field is that the time for which the blood glucose level measurement and the insulin administration are performed for each patient is present in a plurality of numbers.

In order to cope with a case where a fixed amount of insulin is administered to a patient regardless of the level of the blood glucose level (hereinafter, referred to as "fixed administration"), an insulin therapy classification field including a flag variable is provided. The value of this field is logically "false" indicating that insulin is administered according to the scale ID and logically "true" indicating that a predetermined amount of insulin is administered regardless of the value of the measured blood glucose level.

The scale ID means prescription raft data. This is a table listing the amount of insulin to be administered for a range of measured blood glucose levels, otherwise referred to as a "sliding scale". A plurality of the slide scales are prepared and selected according to the state of the patient. In addition, when the scale ID field is blank, it means that only blood glucose level measurement is performed without insulin administration.

The patient history table 1006 is a table storing data such as the blood glucose level of the patient measured by the blood glucose meter 102 and the amount of insulin administered. It can be said to be a log (log). The table is composed of a patient ID field, a scheduled measurement date and time field, a scale ID field, a measurement date and time field, a blood glucose level field, an insulin input amount field, an unproductive flag field, and an alarm confirmation flag field.

The measurement schedule date and time field is generated based on the value of the measurement schedule time field of the insulin administration instruction table 1005. That is, the date and time of the current time is added to the value of the measurement schedule time field, thereby obtaining the measurement schedule date and time.

The record is additionally recorded in the patient history table 1006 by the patient history record non-execution processing unit 1009 and the patient history record execution processing unit 1011 of fig. 10.

As for the additional recording by the non-patient history processing unit 1009,

patient ID field, measurement schedule date and time field, scale ID field are filled, but

The date and time of measurement field, the blood glucose value field, the insulin input amount field are empty,

the not implemented flag field is set to "true" and the alarm acknowledge flag field is set to "false".

As for the additional recording by the implemented patient history processing unit 1011,

the patient ID field, the measurement schedule date and time field, the scale ID field are filled,

the date and time of measurement field, the blood glucose value field, and the insulin input amount field are also filled,

the not implemented flag field is set to "false", and the alarm acknowledge flag field is also set to "false".

Fig. 12 (a) and (b) are diagrams showing a top menu window displayed on the display unit of the measurement data management apparatus 104.

Fig. 12 (a) shows a top menu window 1202 in a state where the blood glucose meter 102 is mounted on the cradle 103.

An illustration of the blood glucose meter 102 is displayed in the blood glucose meter status display field 1203.

A "cycle data transmission" button 1204 and a "meter setting transmission" button 1205 are provided immediately below the blood glucose meter status display field 1203.

The "cycle data transmission" button 1204 is a button that is pressed when data necessary for measuring the blood glucose level of a patient by a blood glucose meter is transmitted to the blood glucose meter.

The "meter setting transmission" button 1205 is a button that is pressed when various environment setting values of the blood glucose meter are transmitted to the blood glucose meter.

Fig. 12 (b) shows a top menu window 1202 in a state where the blood glucose meter 102 is removed from the cradle 103.

In the illustration of the blood glucose meter displayed in the blood glucose meter status display field 1203, there is a display of "not connected" indicating that the blood glucose meter 102 is not mounted. At this time, the display of the "loop data transfer" button 1204 and the "measurement device setting transfer" button 1205 is darkened, and the mouse or the like cannot be clicked.

Further, an "not-performed list" button 1206 in an un-clickable state is provided immediately above the blood glucose meter state display field 1203.

The display control unit 1002 receives the notification from the blood glucose meter detection unit 1012, and changes the blood glucose meter status display field 1203.

[ implemented patient history processing section ]

Fig. 13 is a functional block diagram of the implemented patient history processing unit 1011.

When the blood glucose meter 102 is mounted on the cradle 103, the blood glucose meter detecting unit 1012 detects the mounting state of the blood glucose meter 102 via the USB interface 908. The blood glucose meter detecting unit 1012 polls the cradle 103 at predetermined time intervals.

When the blood glucose meter detection unit 1012 detects the blood glucose meter 102, the blood glucose level measurement meter reception unit 1302 is activated. The blood glucose level measurement table receiving unit 1302 receives the command from the blood glucose meter detecting unit 1012, and downloads the blood glucose level measurement table from the blood glucose meter 102. The blood glucose level measurement table receiving unit 1302 divides the downloaded blood glucose level measurement table data into a patient who has performed blood glucose level measurement and a patient who has not performed blood glucose level measurement, and writes the data in the patient temporary file 1303 and the patient temporary file 1304, respectively.

When the blood glucose level measurement table reception unit 1302 completes the downloading of the blood glucose level measurement table, the blood glucose meter 102 deletes the internal patient table 112, the user basic data 115, and the chip batch data 116.

The implemented patient temporary file 1303 and the non-implemented patient temporary file 1304 are read into the control unit 1305.

The controller 1305 records the contents of the implemented patient temporary file 1303 in the patient history table 1006. Then, the controller 1305 determines whether or not the content of the non-implemented patient temporary file 1304 is empty. If it is confirmed that the content of the patient-unexecuted temporary file 1304 is not empty, that is, if there is only one patient whose blood glucose level has not been measured, the controller 1305 causes the display controller 1002 to display an alarm on the display 907. Then, the selection result selected by the operator is received from the operation section 909. That is, when there is an undeplorer, the control unit 1305 makes an inquiry as to whether or not to record the data of the undeplorer in the patient history table. When the user expresses that the data of the non-patient is to be recorded as a result of the inquiry, the control unit 1305 records the data of the non-patient in the patient history table. Otherwise, the control section 1305 reads the patient ID and the measurement scheduled date and time data from the data of the non-implemented patient temporary file 1304. Then, using the read patient ID and the date and time data scheduled for measurement, the insulin administration instruction table 1005 is searched, a data file necessary for measuring the blood glucose level, such as a patient table and prescription raft data, is created, and the data file is transmitted to the blood glucose meter 102.

Fig. 14 shows fields of the blood glucose level measurement table according to the present embodiment received from the blood glucose meter 102.

When the blood glucose meter 102 measures the blood glucose level of the patient, the blood glucose level measurement flag field becomes "true".

When the blood glucose meter 102 is inputted with the meaning of insulin administration, the insulin administration check flag field is written with "true".

In addition, since the insulin administration is not performed for the patient whose sliding scale ID is not recorded in the scale ID field, the insulin administration check flag is always "false" in this case.

Fig. 15 is a flowchart showing the flow of operations performed by the patient history processing unit 1011.

When the blood glucose meter detecting unit 1012 detects that the blood glucose meter 102 is mounted on the cradle 103 (S1501), the blood glucose level measurement meter receiving unit 1302 is activated. The blood glucose level measurement table receiving unit 1302 downloads the blood glucose level measurement table 1401 from the blood glucose meter 102 (S1502). Then, the blood glucose level measurement table receiving unit 1302 separates the downloaded blood glucose level measurement tables into a patient who has performed blood glucose level measurement and a patient who has not performed blood glucose level measurement, and creates two temporary files, i.e., the patient temporary file 1303 and the patient temporary file 1304 (S1503).

Next, the control unit 1305 reads the implemented patient temporary file 1303 and performs a process of recording the file in the patient history table 1006 (S1504).

Next, the controller 1305 reads the non-implemented patient temporary file 1304 and checks whether or not patient data is present (S1505).

If, as a result of the confirmation, no patient data is present in the patient temporary file 1304, that is, if no patient for which blood glucose level measurement is not performed is present (S1505: "no"), both the patient temporary file 1303 and the patient temporary file 1304 that have been performed are deleted (S1512), and the process ends (S1513).

If the patient data is not stored in the patient temporary file 1304 as a result of the confirmation, that is, if there is a patient for which blood glucose level measurement is not performed (S1505: "yes"), the controller 1305 first controls the display controller 1002 to display an alarm window on the display 907 in order to notify the measurer or the like of the alarm (S1506). Then, the control unit 1305 waits for an input by the operator using the operation unit 909 (S1507).

If the button selected by the operation unit 909 formed of a keyboard or a mouse is a "transfer" button (S1508: yes), the content of the non-implemented patient temporary file 1304 is recorded in the patient history table 1006 (S1509).

When the button selected by the operation unit 909 formed of a keyboard or a mouse is not the "transfer" button but the "re-measurement" button (S1508: no), a data file necessary for measuring the blood glucose level, such as a patient table and prescription raft data, is created again from the patient ID included in the data in the non-implemented patient temporary file 1304, and is transmitted to the blood glucose meter again (S1510).

When any one of the "transmit" button and the "remeasure" button on the alarm window is pressed, the alarm window is deleted (S1511). Then, both the implemented patient temporary file 1303 and the non-implemented patient temporary file 1304 are deleted (S1512), and the process ends (S1513).

Fig. 16 is a flowchart showing the flow of operation of the patient history table recording process. The processing of steps S1504 and S1509 of fig. 15 is shown in detail.

When the process starts (S1601), the control unit 1305 first initializes a count variable i included in the inside for a loop process to be described later to 1 (S1602).

This is followed by a loop process.

The controller 1305 sets the patient ID of the ith data in the temporary file 1303 and the value of the scheduled measurement date and time as search keys, and searches the patient history table 1006 (S1603).

If a record matching the search exists in the patient history table 1006 (S1604: YES), the control unit 1305 updates the measurement date and time field, the blood glucose level field, and the insulin input amount field of the matching record according to the content of the ith record in the temporary file 1303 (S1605).

In this case, the record is a record additionally recorded by the patient history record non-execution processing unit 1009 described later, and the non-execution flag is set to "true". When the update is performed in step S1605, the non-execution flag is rewritten to false. That is, "the record written without performing the blood glucose level measurement is overwritten with the fact that the blood glucose level measurement is performed".

If there is no record matching the search of step S1603 (S1604: no), the control section 1305 writes a new record to the patient history table 1006 in accordance with the content of the i-th record of the temporary file 1303 (S1606). The contents are as follows:

patient ID, measurement scheduled date and time, scale ID, measurement scheduled date and time;

date and time of measurement, blood glucose level, insulin input; and

the non-execution flag is set to "false", and the alarm confirmation flag is set to "false".

Then, the control unit 1305 increments the count variable i (S1607), and observes whether or not the ith data is still present in the temporary file 1303 (S1608). If the ith data remains in the temporary file 1303 (S1608: NO), the process returns to step S1603 and repeats. Otherwise (YES in S1608), the patient warning processing unit 1010 is started (S1609), the blood glucose level measurement table 1401 of the blood glucose meter 102 is deleted (S1610), and the process is terminated (S1611).

Fig. 17 is a schematic diagram showing an alarm window 1702.

An alarm window 1702 is displayed in an overlaid manner on top menu window 1202.

A "list of undeplers" display field 1703 is displayed in the alarm window 1702, and a "remeasurement" button 1704 and a "transmission" button 1705 are provided.

The temporary file 1303 is read by the control unit 1305 to create a "list of undeployed users" display field 1703.

When the "re-measurement" button 1704 is pressed, the controller 1305 records the data of the patient whose blood glucose level has been measured in the patient history table 1006, and creates a data file necessary for measuring the blood glucose level such as a patient table and prescription raft data for the patient who has not yet performed blood glucose level measurement, and sends the data file to the blood glucose meter 102 again. Thereafter, the alarm window 1702 is deleted. The measurement clerk again pulls out the blood glucose meter 102 from the cradle 103, and performs measurement or insulin administration on the patient who is not performing the measurement.

When "transmission" button 1705 is pressed, control unit 1305 records received blood glucose level measurement table 1401 in patient history table 1006 as it is, deletes internal patient table 112 inside blood glucose meter 102 together with user basic data 115 and chip batch data 116, and then deletes alarm window 1702.

It is difficult to confirm whether or not a patient who has forgotten to measure is present with a single blood glucose meter during a blood glucose level measurement operation.

On the other hand, the timing at which the blood glucose level measurement operation is ended and blood glucose level measurement table 1401 is transferred to measurement data management apparatus 104 is a timing suitable for checking whether or not there is a patient who has forgotten to measure.

Therefore, after blood glucose level measurement table 1401 is temporarily downloaded, the blood glucose level measurement flag is checked. An alarm window 1702 is displayed whenever an unmeasured patient is identified. At this time, the internal patient table 112 in the blood glucose meter is deleted, and if the nurse has indeed forgotten to measure the blood glucose level or administer insulin, the data of the patient is downloaded again, and the measurement, administration, and other treatment are performed.

Thus, the present system can prevent an error of forgetting to measure the blood glucose level.

[ non-implementation of patient history processing Unit ]

Next, the operation of the patient history processing unit 1009 not being performed will be described with reference to fig. 18 and 19.

Fig. 18 is a functional block diagram of the patient history record processing unit 1009.

Fig. 19 is a flowchart showing the flow of the operation of the patient history processing unit 1009.

The scheduler 1007 that monitors the date and time information of the calendar clock 1008 starts the search unit 1802 (S1901).

When the scheduler 1007 starts the search unit 1802, the search unit 1802 acquires date and time information from the calendar clock 1008 (S1902), and searches the insulin administration instruction table 1005 for a scheduled measurement time within the range of "current date and time-m" minutes (S1903). Further, m minutes can be set to an arbitrary value. For example, 60 minutes.

The search results are recorded in a temporary file 1803. The temporary file 1803 lists only the serial numbers of the insulin administration instruction table 1005.

The additional recording unit 1804 is started in response to the existence of the temporary file 1803.

The additional recording unit 1804 first initializes the internal count variable i to 1 (S1904).

This is followed by a loop process.

The additional recording unit 1804 searches the insulin administration instruction table 1005 using the serial number in the temporary file 1803. Then, the patient ID and the measurement scheduled time are obtained from the record conforming to the search (S1905). After the measurement scheduled time is converted into a measurement scheduled date and time (S1906), the patient history table 1006 is searched as a search key together with the patient ID (S1907).

If there is no record matching the search (S1908: NO), the following is additionally recorded in the patient history table 1006 (S1909).

Content of record of insulin administration instruction table 1005 serving as a basis of search keyword

Conversion of the measurement schedule time into a measurement schedule date and time

The non-enforcement flag is set to "true", and the alarm confirmation flag is set to "false".

If there is a record that matches the search (S1908: YES), no operation is performed.

Then, the search unit 1802 increments the count variable i (S1910), and checks whether or not the ith sequence number is present in the temporary file 1803 (S1911). If the ith record exists in the temporary file 1803 (S1911: NO), the process is repeated again (S1905). Otherwise (S1911: YES), the process is ended (S1912).

The non-patient history processing unit 1009 is a process for recording a history of "non-blood glucose level measurement" in the patient history table 1006.

In contrast, the executed patient history processing unit 1011 is a process for recording the history of "blood glucose level measurement was executed" in the patient history table 1006.

At the same measurement scheduled date and time with the same patient ID, any one of the processes is added to the patient history table 1006.

Here, in order to prevent erroneous recording, the unproductive patient history processing unit 1009 confirms in advance whether or not there is a recorded record in the patient history table 1006. That is, whether or not a record has been recorded by the implemented patient history processing unit 1011 before the observation. If there is a recorded record, no additional recording is performed. If no recorded record exists, additional recording is performed. The record of the additional record is displayed in a list by the patient warning unproductive processing unit 1010 described later.

The record recorded by the implemented patient history processing unit 1011 takes precedence over the record additionally recorded by the non-implemented patient history processing unit 1009.

It is assumed that measurement data management apparatus 104 also downloads blood glucose level measurement table 1401 from blood glucose meter 102 when a person in charge of blood glucose level measurement, such as a nurse, places blood glucose meter 102 on cradle 103 after a predetermined time m minutes for blood glucose level measurement has elapsed and a warning display has been performed by patient non-execution warning processing unit 1010.

Then, the executed patient history processing unit 1011 records the fact that the blood glucose level measurement was executed in the patient history table 1006 from the blood glucose level measurement table 1401 obtained by downloading.

In this case, the record added to the record of the non-implementation of the patient history processing unit 1009 includes the record of "the blood glucose level measurement is not implemented".

Therefore, the implemented patient history processing unit 1011 searches the patient history table 1006 and checks whether or not there is a record to which the implemented patient history processing unit 1009 has not added a record. If the record exists, the data is overwritten to the empty field, and the non-implemented flag written to "true" by the non-implemented patient history processing unit 1009 is rewritten to "false". If the record does not exist, additional recording of the record is performed.

[ section for warning treatment of non-implemented patient ]

Next, the operation of the patient warning processing unit 1010 not being executed will be described with reference to fig. 20 and 21.

Fig. 20 is a functional block diagram of the patient warning processing unit 1010.

Fig. 21 is a flowchart showing the flow of operation of the patient warning processing unit 1010.

The scheduler 1007 that monitors the date and time information of the calendar clock 1008 starts the search unit 1802 (S2101).

When the searching section 2002 is started by the scheduler 1007, the searching section 2002 acquires date and time information from the calendar clock 1008 (S2102), and searches for a record of the patient history table 1006 whose non-implemented flag is "true" and whose alarm confirmation flag is "false" within a time period divided from the latest m to the current date and time (S2103). Further, m minutes can be set to an arbitrary value. For example, 60 minutes.

The search results are recorded in a temporary file 2003. The temporary file 2003 includes a patient ID, a date and time scheduled for measurement, and an unexecuted flag.

If the search unit 2002 has all finished the temporary file creation process, the search unit 2002 confirms whether or not there is at least one recorded data in the created temporary file 2003 (S2104). If data exists in the temporary file 2003, the search section 2002 controls the display control section 1002 to display an alarm message in the top menu window 1202 displayed on the display section 907. Then, the "not implemented list" button 1206 is enabled to be pressed (S2105), and the process is ended (S2106).

Fig. 22 is a flowchart showing an operation flow in which the list display processing is not performed. This is internal processing of the data editing processing section 1003.

When the operator presses the "list not implemented" button 1206 (S2201), the data edition processing unit 1003 searches the patient information table 1004 using the patient ID in the temporary file 2003 created by the search unit 2002, and creates a display list (S2202).

Next, the data edit processing unit 1003 controls the display control unit 1002 based on the display list, and the display unit 907 displays an unexecuted list window (S2203). Then, the operation of the button in the list window of non-implemented persons is waited for (S2204).

If the button pressed is the "confirm" button (S2205: YES), the alarm confirm flag of the record of the patient history table 1006 corresponding to the patient ID and the measurement scheduled date and time existing in the temporary file 2003 is rewritten to "true" (S2206). Then, the "list not implemented" button 1206 in the top menu window 1202 is invalidated and deleted (S2207).

If the button pressed is the "back" button (S2205: NO), no operation is performed.

Then, the unexecuted list window is deleted (S2208), and the process ends (S2209).

Fig. 23 is a diagram showing a state of top menu window 1202 when a predetermined time has elapsed since a scheduled time for blood glucose level measurement.

The "list not implemented" button 1206 is clearly displayed and can be pressed.

A warning message 2302 is displayed immediately above the "not implemented list" button 1206.

Fig. 24 is a diagram showing an unexecuted person list window.

The non-practitioner list window 2402 lists and displays patients who are determined to have forgotten to measure the blood glucose level and/or to administer insulin in a table form from the top.

When the "ok" button 2403 is pressed, the alarm ok flag of the record of the patient history table 1006 corresponding to the patient ID and the measurement scheduled date and time existing in the temporary file 2003 is rewritten to "true". Then, the "list of undeleted" button 1206 is deleted, and the list of undeleted windows 2402 is deleted. Therefore, the "list not implemented" button 1206 cannot be pressed without displaying the warning message.

When the "back" button 2404 is pressed, nothing is done in the patient history list 1006, and the non-practitioner list window 2402 is deleted. Therefore, the alarm message remains displayed, and the "list not implemented" button 1206 remains depressible.

The present embodiment discloses a blood glucose level measurement system.

The non-patient history processing unit periodically searches an insulin administration instruction table in which measurement scheduled times are listed for each patient, and temporarily creates a list of patients for whom no measurement or the like is performed. After that, the patient history table is searched to check whether or not a record already exists, and then an additional record is added in which a non-execution flag is set to true. That is, the fact that no measurement or the like is performed is recorded in the patient history table.

In the processing of displaying the warning on the display unit by the non-implemented patient warning processing unit, the non-implemented flag may be searched for in the patient history table. This operation can be performed asynchronously with the non-patient history processing unit.

The implemented patient history processing unit downloads the blood glucose level measurement table 1401 from the blood glucose meter and temporarily stores the blood glucose level measurement table in a temporary file. The records in the temporary file are searched one by one in the patient history table, and it is checked whether or not the record of the same content has been additionally recorded by the non-patient history processing unit. If the measurement data has already been additionally recorded, the non-execution flag is rewritten to false, and the measurement data is recorded in a field that is a blank field. That is, records that are considered as unimplemented are overwritten with the fact of the measurement and the measurement data.

Since these processes operate independently, when the fact of measurement is preferentially recorded in the patient history table and there is a possibility that the measurement or the like is forgotten, the patient warning processing unit is not executed to reliably display a warning. By this processing, forgetting of measurement can be prevented for a required time interval.

The implemented-patient history processing unit checks the blood-glucose level measurement table 1401 which has been downloaded from the blood-glucose meter and stored in a temporary file, and if a patient whose blood-glucose level measurement has not been implemented is found, an alarm window is displayed to inquire whether to receive data directly or to measure a patient who has forgotten to measure the blood-glucose level. That is, at the moment the blood glucose meter is placed in the cradle, it is immediately known that the measurement was forgotten. This is a function that cannot be implemented in a single individual of a blood glucose meter.

[ second embodiment ]

[ blood glucose measurement work of the blood glucose meter 102]

Next, a flow of a blood glucose measurement operation performed by the blood glucose meter 102 will be described with reference to fig. 25.

Fig. 25 is a schematic diagram illustrating a flow of a blood glucose measurement operation performed by the blood glucose meter 102.

(1) A patient ID2503 made up of a barcode attached to the name plate or the like of the patient 2502 is read by the barcode reader 208.

The read patient ID2503 is first used for the search key of the internal patient table 112.

The patient data 114 transmitted from the measurement data management device 104 is converted into the internal patient table 112 inside the blood glucose meter 102 in advance, and is stored in the nonvolatile memory 614. The internal patient table 112 is searched using patient ID 2503. The records that are consistent with the search are records of the corresponding patient in the internal patient table 112 where the various data are to be recorded at a later time.

(2) Next, the user ID2505 made of a barcode attached to the name card or the like of the nurse 2504 is read by the barcode reader 208.

It is verified whether the read user ID2505 is included in the user basic data 115. The user basic data 115 is searched for the user ID as a search key, and if the user ID exists, the user ID is overlaid on the "user ID" field of the previously determined record of the internal patient table 112.

(3) Next, the chip lot number 2507 made of a barcode printed on the cassette 2506 of the measurement chip 212 is read by the barcode reader 208.

It is verified whether the read chip batch number 2507 is included in the chip batch data 116 (refer to fig. 1). The chip batch data 116 is searched for using the chip batch number as a search key and, if present, is overlaid onto the "chip batch number" field of the previously determined record of the internal patient table 112.

(4) Immediately after the chip batch number is recorded on the "chip batch number" field of the internal patient table 112 in (3), the atmospheric temperature is measured using the thermistor 606. Then, if it is determined that the atmospheric temperature is within the prescribed range, the "temperature at measurement" field of the previously determined record of the internal patient table 112 is overwritten.

(5) The measurement chip 212 is attached to the optical measurement unit of the blood glucose meter 102 to measure the blood glucose level. Then, date and time data of the time at which the measurement was made is obtained from the calendar clock 607.

The measured blood glucose values are overlaid onto the "blood glucose value" field of the previously determined record of the internal patient table 112. Date and time data is overlaid onto the "date and time of measurement" field of the previously determined record of the internal patient table 112.

In addition, a flag indicating "fact" that "blood glucose level is measured" is recorded in the "measurement/display/input flag" field.

Then, the measured blood glucose level is displayed on the LCD 203 (display unit 615).

(6) The slide scale 2509 of the patient 2502 is searched using the measured blood glucose level, and the type of the drug such as insulin dispensed to the patient 2502 and the amount of the drug to be administered are displayed on the LCD 203. A slide scale 2509 is stored for each patient ID in the internal patient table 112. The slide scale 2509 is described in detail in fig. 26 described later.

(7) The nurse 2504 inputs insulin or the like by the syringe 2508 in accordance with the prescription displayed on the LCD 203, and then inputs the fact by the input key 206. Thus, a flag indicating "dispensed" this "fact" is recorded on the "measurement/display/administration flag" field of the internal patient table 112.

With the measurement work shown above, the following is recorded to the internal patient table 112:

for which patient

The predetermined moment of time is measured and,

which measurer

Which chip is used for the batch numbering of chips,

in which environment of atmospheric temperature,

whether or not the blood glucose level is measured,

why (if the blood glucose level is measured) the blood glucose level,

when (if blood glucose values are measured) the current date and time,

whether or not the dispensing of insulin or the like is performed.

The blood glucose level measurement operation and the insulin dispensing operation are performed approximately at a predetermined time period after the patient eats the food. In addition, the food may be taken a predetermined time period before eating. The measurement and dispensing operations are collectively performed for a plurality of patients in a predetermined time period.

Such a unit of operation for measuring blood glucose levels and/or dispensing insulin in a plurality of patients collectively in a predetermined time period is called a "cycle". For example, the treatment is performed by a method called "one cycle 30 minutes after breakfast".

In order to avoid errors in blood glucose level measurement and insulin dispensing operations, only data required for one cycle is transmitted from measurement data management apparatus 104 to blood glucose meter 102. These data are patient data 114, user base data 115, and chip batch data 116.

After the cycle is completed, the blood glucose meter 102 must be placed on the holder 103. When the blood glucose meter 102 is mounted on the cradle 103, the patient measurement data 117 is created by immediately extracting a predetermined field of the internal patient table 112, and then the patient measurement data 117 is transmitted from the blood glucose meter 102 to the measurement data management apparatus 104. The measurement data management device 104 receives the data and records it in an internal patient history table 1006.

Fig. 26 is a diagram showing the internal structure and relationship of each table. FIG. 26 is a diagram also called "ER map" according to the first letter of Entity-Relationship. Further, fig. 26 is depicted in accordance with the relationship of the table shown in fig. 1, which is transmitted and received between the measurement data management apparatus 104 and the blood glucose meter 102.

Regarding the patient data 114 transmitted from the measurement data management apparatus 104, all fields except the "insulin therapy classification" field are recorded as they are to the internal patient table 112. The internal patient table 112 is disposed in a non-volatile memory 614 internal to the blood glucose meter 102.

The "insulin therapy classification" field of the patient data 114 is recorded in the "measurement/display/administration flag" field and the "measurement presence/absence flag" field of the internal patient table 112 by a prescribed conversion process.

The chip batch data 116 and the user basic data 115 transmitted from the measurement data management apparatus 104 are stored in the nonvolatile memory 614 inside the blood glucose meter 102 as they are. The data (chip batch number and user ID) read from the barcode reader 208 during the measurement operation is recorded in the internal patient table 112 every time it is read.

Sometimes more than two agents are administered to a patient. Although not shown in fig. 26, the type of the drug and the insulin administration check flag for each drug are set in the internal patient table. When a plurality of insulin administration confirmation flags are present for a certain patient, the result is recorded for each drug in the measurement/display/administration flag.

[ patient data 114]

Next, each field of the patient data 114 is explained.

Any of the following is recorded in the "insulin therapy classification" field of the patient data 114:

0: performing blood glucose level measurement only

1: blood glucose level measurement + insulin administration using sliding scale

2: blood glucose level measurement + insulin administration without sliding scale (hereinafter "fixed administration")

5: only insulin administration using a sliding scale was performed (blood glucose level measurement was not performed)

6: only a fixed insulin administration was performed (blood glucose level measurement was not performed).

The sliding scale means prescription raft data. The sliding scale is a table listing the amounts of drugs such as insulin to be administered to the measured range of blood glucose levels.

"fixed administration" means a case where a fixed amount of a drug such as insulin is administered regardless of the measurement result of the blood glucose level.

The sliding scale is saved in the "sliding scale engagement information" field of the patient data 114.

The value of the "insulin therapy classification" field of the patient data 114 is flag information indicating to the blood glucose meter 102 the job to be performed for each patient. For example,

if "0", only the blood glucose level of the patient is measured.

If "1", the blood glucose level of the patient is measured and insulin is administered using a sliding scale.

The same applies to "2", "5" and "6" below.

The "patient ID" field is a number for identifying the patient, and is recorded in a bar code attached to clothing worn by the patient 2502, as illustrated in fig. 25. The "patient japanese hiragana" field is japanese hiragana based on the japanese katakana of the patient's name. The "patient japanese hiragana" field is displayed in the LCD 203 of the glucose meter 102 along with the patient ID for the measurer operating the glucose meter 102 to correctly identify the patient in front of him.

The "blood glucose measurement scheduled time" field is a scheduled time at which a cycle is performed, and also serves as a search key when the measurement data management apparatus 104 side determines data.

The "measurement value lower limit value" field and the "measurement value upper limit value" field indicate the range of blood glucose levels in which insulin administration can be performed. This is set for indirectly knowing the state of the patient and preventing an accident caused by an improper insulin input, particularly in the case where the value of the "insulin therapy classification" field is "1" or "2". In short, if the blood glucose level is outside the range, the patient's condition is not good, and therefore it can be determined that insulin administration is not appropriate.

The "patient measurement history data" field is a field in which a plurality of pieces of recent blood glucose level measurement history information of the patient are stored. When the value of the "insulin therapy classification" field is "5", the blood glucose level measured most recently is stored in advance, and insulin administration is performed using a sliding scale based on the value.

The above is a description of the fields of the patient data 114.

[ internal patient table 112]

Next, each field of the internal patient table 112 is explained.

The "measurement/display/administration flag" field is a field in which three flags, that is, a "blood glucose level measurement flag", an "insulin administration confirmation flag", and an "insulin administration amount display flag" are stored.

In the "measurement presence or absence flag" field,

record a "1" indicating logical "true" when the "insulin therapy classification" field of the patient data 114 is "0", "1", or "2",

record "0" indicating logical "false" when the "insulin therapy classification" field of the patient data 114 is "5" or "6".

The "measurement/display/administration flag" field changes when (1) immediately after completion of the blood glucose level measurement operation, (2) when the insulin administration amount is displayed, and (3) when the meaning of insulin administration is input.

The "blood glucose level measurement flag" field of the patient measurement data 117 reflects the contents of the "measurement/input/display flag" field and the "measurement presence/absence flag" field.

Further, the contents and variations of these flags are described in detail later.

A "patient ID" field, a "patient japanese hiragana" field, a "blood glucose measurement scheduled time" field, a "measurement value lower limit" field, a "measurement value upper limit" field, a "sliding scale engagement information" field, and a "patient measurement history data" field are copied from the patient data 114 as they are.

The user ID read by the barcode reader 208 is collated with the chip batch data 116 and recorded in the "user ID" field.

The chip lot number read by the bar code reader 208 is registered in the "chip lot number" field after being collated with the user basic data 115.

As described with reference to fig. 25, the values of the fields "date and time of measurement" field, "blood glucose level" field, and "temperature at measurement" field are recorded during the blood glucose level measurement operation of the blood glucose meter 102.

The above is a description of the fields of the internal patient table 112.

[ patient measurement data 117]

In the internal patient table 112, a "patient ID" field, a "user ID" field, a "date and time of measurement" field, a "blood glucose level" field, a "temperature at the time of measurement" field, a "chip lot number" field, and a "scheduled blood glucose measurement time" field, which are required by the measurement data management apparatus 104, are output as patient measurement data 117 without change.

The contents of the "measurement/input/display flag" field and the "measurement presence/absence flag" field are subjected to predetermined conversion processing and output as data of the "blood glucose level measurement flag" field.

The above is a description of each field of the patient measurement data 117.

Fig. 27 and 28 are flowcharts showing the flow of communication between the blood glucose meter 102 and the measurement data management apparatus 104.

The measurement data management device 104 always polls the carriage 103 (S2701). In this state, when the blood glucose meter 102 is mounted to the cradle 103, the blood glucose meter 102 responds to a polling command issued from the measurement data management apparatus 104. The measurement data management device 104 accepts the response and immediately identifies the presence of the blood glucose meter 102. Such an operation until the blood glucose meter 102 and the measurement data management apparatus 104 establish communication is referred to as negotiation (S2702).

A user such as a nurse operates the measurement data management device 104 to create data for circulation (S2703). Then, when "transmission" is instructed, the patient data 114, the user basic data 115, and the chip batch data 116 are sent to the blood glucose meter 102 (S2704). At this time, a part of the contents of the patient data 114 is written into the patient information table 1004 in the measurement data management apparatus 104 (S2706).

The user pulls out the blood glucose meter 102 from the cradle 103 and performs blood glucose measurement and insulin dispensing for the patient (S2707).

After the user completes all measurements and dispensing, the blood glucose meter 102 is placed on the holder 103. Therefore, a negotiation is established between the blood glucose meter 102 and the measurement data management apparatus 104 in the same manner as described above (S2708 and S2709).

The measurement data management apparatus 104 requests the blood glucose meter 102 to transmit the patient measurement data 117 after establishing the negotiation (S2710). The blood glucose meter 102 receives the request, creates patient measurement data 117 from the internal patient table 112, and transmits the patient measurement data 117 to the measurement data management apparatus 104 (S2711).

The measurement data management device 104 records the content of the received patient measurement data 117 to the patient history table 1006 (S2713). Then, the contents recorded in the patient history table 1006 are collated with the contents previously recorded in the patient information table 1004 (S2714). This comparison is to verify whether the job is completed in accordance with the content indicated to the blood glucose meter 102.

For example, if the instruction content is "only blood glucose level measurement", it is checked whether or not blood glucose level measurement is performed.

Similarly, if the instruction content is "blood glucose level measurement and insulin administration", it is checked whether or not blood glucose level measurement and insulin administration have been performed.

If the result of performing this collation job is that only one person does not agree between the instruction content and the execution result, the measurement data management apparatus 104 displays a warning (alarm) on its display portion 907 (S2715).

The description is continued with reference to fig. 28.

After displaying the warning, the measurement data management apparatus 104 requests a prescribed operation to the operator (S2816). The operation is as follows: whether or not to perform data transmission for re-execution for a patient who has not performed either or both of blood glucose level measurement and insulin administration, i.e., who has forgotten to perform the blood glucose level measurement and insulin administration. When the operator performs an operation to command data retransmission, the measurement data management apparatus 104 creates data (S2817), and retransmits the patient data 114 and the like to the blood glucose meter 102 (S2818). In addition, predetermined data is also written in the patient information table 1004 in the same manner as described above (S2819).

Thereafter, the same operation as described above is continued.

The user pulls out the blood glucose meter 102 from the cradle 103 and performs blood glucose measurement and insulin dispensing for the patient (S2820).

After the user completes all measurements and dispensing, the blood glucose meter 102 is placed on the holder 103. Then, negotiation is established between the blood glucose meter 102 and the measurement data management apparatus 104 (S2821 and S2822).

The measurement data management device 104 requests the blood glucose meter 102 to transmit the patient measurement data 117 after establishing the negotiation (S2823). The blood glucose meter 102 receives the request, creates patient measurement data 117 from the internal patient table 112, and transmits the patient measurement data 117 to the measurement data management apparatus 104 (S2824).

The measurement data management device 104 records the content of the received patient measurement data 117 in the patient history table 1006 (S2825). Then, the content recorded in the patient history table 1006 is collated with the content previously recorded in the patient information table 1004 (S2826).

If the result of the collation job is that the instruction contents and the execution results match with each other for all patients, the measurement data management apparatus 104 displays "OK" on the display portion 907 (S2827).

On the other hand, the blood glucose meter 102 deletes the internal patient table 112(S2828) after transmitting the patient measurement data 117 to the measurement data management apparatus 104 (S2824). By this operation, the blood glucose meter 102 can guarantee that blood glucose level measurement or insulin administration is always performed only based on the latest data.

The flow of the above operation is briefly described again, and this flow is as follows.

(1) First, patient data 114 and the like are transmitted from the measurement data management apparatus 104 to the blood glucose meter 102.

(2) Completing blood sugar measurement, insulin dispensing, and the like.

(3) If all measurements and dispensing are completed, the blood glucose meter 102 is placed on the tray 103.

(4) Then, the patient history table 1006 in which the content of the received patient measurement data 117 is recorded is compared with the patient information table 1004, and if a mismatch is found, a warning is displayed on the display portion 907 of the measurement data management apparatus 104.

(5) Patient data 114 for the non-implemented patient, etc. is again transmitted to the blood glucose meter 102.

(6) Completing blood sugar measurement, insulin dispensing, and the like.

(7) If all measurements and dispensing are completed, the blood glucose meter 102 is placed on the tray 103.

(8) Therefore, the patient history table 1006 in which the contents of the received patient measurement data 117 are recorded is compared with the patient information table 1004, and all patients match, and the series of processes is terminated.

The blood glucose meter 102 stores patient data that is the subject of only one cycle.

If it is assumed that the blood glucose level measurement or insulin administration of some of the patients has been forgotten, the measurement data management device 104 verifies the received patient measurement data and identifies the patient who has not performed the blood glucose level measurement or insulin administration. The determined patient is then again prepared with data for the required treatment to be performed. Namely, "recycling" is performed.

The design of the blood glucose meter 102 "execute only one cycle" is based on the idea that errors in blood glucose level measurement and insulin administration are absolutely impossible.

Fig. 29 is a functional block diagram of the blood glucose meter 102.

Data and the like sent from the barcode reader 208, the thermistor 606, the phototransistor 612 that is a part of the optical measurement unit also called a blood glucose sensor, and the operation unit 608 are input to the input/output control unit 2902.

The input/output control unit 2902 also inputs and outputs data among the user basic data 115, the chip batch data 116, and the internal patient table 112 in the nonvolatile memory 614.

A content to be presented to the user is created by the input/output control unit 2902, and the content is displayed on the display unit 615 by the display control unit 2903.

The patient data conversion unit 2904 converts the patient data 114 received from the infrared communication unit 617 to create the internal patient table 112. The internal patient table 112 is converted into the patient measurement data 117 by the patient measurement data conversion unit 2905, and is transmitted to the measurement data management device 104 by the infrared communication unit 617.

Fig. 30 is a state transition diagram of the blood glucose meter 102.

When there are a plurality of insulin prescriptions to be administered, an insulin administration confirmation flag corresponding to the number is set.

First, when the power is turned on, the blood glucose meter 102 enters the menu display state S3001. By performing a predetermined operation from the menu display state S3001, the blood glucose meter 102 enters the patient ID scanning state S3002 in which the barcode reader 208 reads the patient ID.

In the patient ID scanning state S3002, when the patient ID is read by the barcode reader 208, the input/output control unit 2902 observes the blood glucose level measurement flag and the insulin administration check flag in the record of the patient ID in the internal patient table 112 (branch point S3003).

At the time of the branch point S3003, when the blood glucose level measurement flag of the patient is "true" and one or more insulin administration check flags are "false", the blood glucose meter 102 transitions to the blood glucose level display (2) state S3004. Otherwise, that is, when the blood glucose level measurement flag is "false" or all insulin administration check flags are "true", the blood glucose meter 102 shifts to the blood glucose level measurement state S3005.

When the blood glucose level is measured at the time of the blood glucose level measurement state S3005, the blood glucose meter 102 then shifts to a blood glucose level display (1) state S3006.

Next, from the time point when the blood glucose level is displayed in the state (1) S3006, the input/output control unit 2902 checks all the insulin administration check flags for the patient (branch point S3007). That is, the blood glucose meter 102 shifts from the state of blood glucose level display (1) S3006 to the next state in accordance with the state of all insulin administration check flags for the patient (branch point S3007).

At the time of the branch point S3007, if all the insulin administration confirmation flags are "true", the flow shifts to a "remeasurement/next patient" selection state S3008. At the time of the branching point S3007, if one or more insulin administration check flags are "false", the system transitions to the "remeasurement/insulin/next patient" selection state S3009.

At the time point of the branching point S3007, "one or more insulin administration check flags are" false ", which means that there is a drug not administered to the patient. In contrast, "all insulin administration confirmation flags are 'true' means that administration of a medicament is completed for the patient without the presence of an unadministered medicament. Therefore, at the time of the branch point S3007, if there is a medicine that has not been administered, the state can be shifted to the insulin administration amount display state S3010 according to the subsequent operator' S option, but if there is no medicine that has not been administered, the state cannot be shifted to the insulin administration amount display state S3010.

In the "re-measurement/next patient" selection state S3008, a character string of "re-measurement" and a character string of "next patient" are displayed as selection items on the display unit 615. The operator operates the operation unit 608 to select any one of the items.

When the operator selects "re-measurement", at the time of the "re-measurement/next patient" selection state S3008, the blood glucose level measurement flag is set to "false" in the processing S3011, and the process returns to the patient ID scan state S3002.

When the operator selects "next patient" at the time of the "re-measurement/next patient" selection state S3008, the blood glucose level measurement flag is set to "true" in the process S3012, and the process returns to the patient ID scan state S3002.

In the "re-measurement/insulin/next patient" selection state S3009, a character string of "re-measurement", a character string of "next patient", and a character string of "insulin" are displayed as selection items on the display unit 615. The operator operates the operation unit 608 to select any one of the items.

When the operator selects "re-measurement" at the time of the "re-measurement/insulin/next patient" selection state S3009, the blood glucose level measurement flag is set to "false" in the processing S3011, and the system returns to the patient ID scan state S3002.

When the operator selects "next patient" at the time of the "re-measurement/insulin/next patient" selection state S3009, the blood glucose level measurement flag is set to "true" in the processing S3012, and the process returns to the patient ID scan state S3002.

When the operator selects "insulin" at the time of the "re-measurement/insulin/next patient" selection state S3009, the blood glucose level measurement flag is set to "true" in the processing S3012, and the process proceeds to the insulin input amount display state S3010.

When the operator selects "insulin" at the time of the "re-measurement/insulin/next patient" selection state S3009, or after the blood glucose level display (2) state S3004, the operation proceeds to the insulin input amount display state S3010.

In the insulin administration amount display state S3010, the type and the administration amount of insulin to be administered to the patient are displayed on the display unit 615.

In the insulin input amount display state S3010, only the input key 206 is operable. Also, when the input key 206 is pressed, the blood glucose meter 102 shifts to the "put/not put" selection state S3013.

In the "put/not put" selection state S3013, a character string of "put" and a character string of "not put" are displayed as selection items on the display unit 615. The operator operates the operation unit 608 to select any one of the items.

At the time of the "thrown/not thrown" selection state S3013, when the operator selects "thrown", the insulin thrown amount display flag is set to true in the processing S3014, and the process proceeds to the "thrown" display state S3015.

When the operator selects "not-on" at the time of the "already-on/not-on" selection state S3013, the insulin input amount display flag is set to "true" in the processing S3014, and the process proceeds to the "not-on" display state S3016.

In the "put" display state S3015, the display unit 615 displays, as selection items, a display-dedicated character string of "put" and, in addition, a character string of "OK" and a character string of "return". The operator operates the operation unit 608 to select an item of "OK" or "return".

When the operator selects "OK" in the "input" display state S3015, the insulin input confirmation flag for the medicine displayed in the insulin input amount display state S3010 is set to true in processing S3017, and the process proceeds to the branch point S3018.

At the time of the "thrown" display state S3015, when the operator selects "return", the operation returns to the "thrown/not thrown" selection state S3013. This option is an option set to prevent an erroneous operation.

In the "not-put-in" display state S3016, the display unit 615 displays, as selection items, a display-dedicated character string of "not put in" and a character string of "OK" and "return". The operator operates the operation unit 608 to select an item of "OK" or "return".

When the operator selects "OK" in the "not-engaged" display state S3016, the process proceeds to a branch point S3018.

That is, in the "not-administered" display state S3016, unlike the "administered" display state S3015, the insulin administration check flag relating to the drug, which is displayed in the insulin administration amount display state S3010, is not set to "true".

At the time of the "not-thrown" display state S3016, when the operator selects "return", the operation returns to the "thrown/not-thrown" selection state S3013. This option is an option set to prevent an erroneous operation.

At the branch point S3018, the status of all insulin administration confirmation flags for the patient is confirmed. If all the insulin administration check flags of the patient are "true", that is, if all the medicines have been administered, the process proceeds to the administration list display (1) state S3019.

If one or more of the insulin administration check flags of the patient are "false", that is, if there is a drug that has not been administered, the state shifts to the administration list display (2) state S3020.

In the administration list display (1) state S3019, the character string "complete" is displayed as a unique selection item in addition to the medicines administered to the patient in the list on the display unit 615. When the operator presses the input key 206 after confirming the contents of the list display of the medicines administered to the patient, the system proceeds to a "next patient/menu" selection state S3022.

In the administration list display (1) state S3019, administration of all the medicines necessary for the patient is completed.

In the administration list display (2) state S3020, the display unit 615 displays a list of the medicines administered to the patient, and also displays a character string of "complete" and a character string of "return" as selection items. After confirming the contents of the list of the medicines administered to the patient, the operator operates the operation unit 608 to select the item "complete" or "return".

When the operator selects "complete" at the time of the drop list display (2) state S3020, the process proceeds to a completion confirmation state S3021.

When the operator selects "return" at the time of the input list display (2) state S3020, the insulin input amount display state S3010 is returned to.

In the state S3020 of the administration list display (2), administration of the medicine required by the patient is not completed. Therefore, when the state returns to the insulin input amount display state S3010, the input amount of the medicine not to be input is displayed.

In the completion confirmation state S3021, the display unit 615 displays "there is a medicine that has not been administered. Can? In addition to the character string for warning the operator, a character string for "return" and a character string for "yes" are displayed as selection items. The operator operates the operation unit 608 to select an item of "return" or "yes".

At the time of completion of the confirmation state S3021, when the operator selects "return", the process returns to the branch point S3018. Then, since there is no medicine to be administered, the state returns to the administration list display (2) state S3020 again.

At the time of completion of the confirmation state S3021, when the operator selects "yes", a transition is made to a "next patient/menu" selection state S3022.

In the "next patient/menu" selection state S3022, a character string of "next patient" and a character string of "menu" are displayed as selection items on the display unit 615. The operator operates the operation unit 608 to select items of "next patient" or "menu".

At the time of the "next patient/menu" selection state S3022, when the operator selects "next patient", it returns to the patient ID scan state S3002.

At the time of the "next patient/menu" selection state S3022, when the operator selects "menu", it returns to the menu display state S3001.

In the state transition diagram described above, there are three portions where the content of the flag is confirmed by the input/output control unit 2902.

One is to observe the time when the blood glucose level measurement flag and all insulin administration check flags are logically combined after the patient ID is read in the patient ID scan state S3002 (branch point S3003).

In the other case, after the blood glucose level is displayed in the state S3006 of blood glucose level display (1), the logic timing of all insulin administration check flags is observed (branch point S3007).

Further, the logic timing of all the insulin administration check flags is observed after the "administered" display state S3015 and the "not administered" display state S3016 (branch point S3018).

In the state transition diagram described above, there are four places where the input/output control unit 2902 rewrites the flag.

One is a process of setting the blood glucose level measurement flag to "false" in the "re-measurement/next patient" selection state S3008 and the "re-measurement/insulin/next patient" selection state S3009 (step S3011).

On the other hand, in the "re-measurement/next patient" selection state S3008 and the "re-measurement/insulin/next patient" selection state S3009, the blood glucose level measurement flag is set to "true" (processing S3012).

Further, after the "input/non-input" selection state S3013, a process of setting the insulin input amount display flag to "true" (process S3014).

Further, when the operator selects "OK" at the time of the "already-on" display state S3015, the process sets the insulin on confirmation flag to "true" (processing S3017).

When insulin is administered to a patient after the blood glucose level of the patient is measured, the process flow is as in S3002-S3005-S3006-S3009-S3010-S3013-S3015-S3019 or S3020-S3002.

When the blood glucose level of the patient is measured without administering insulin to the patient after the blood glucose level of the patient is measured, the process flow of S3002 to S3005 to S3006 to S3009 to S3002 is followed.

When insulin is administered to a patient whose blood glucose level has been measured, or when only insulin is initially administered, the process flow is as in S3002-S3004-S3010-S3013-S3015-S3019 or S3020-S3002.

When only the blood glucose level of the patient is measured from the beginning or when the blood glucose level of the patient for which the insulin administration amount has been already indicated is measured again, the processing flow of S3002 to S3005 to S3006 to S3008 to S3002 is followed.

Fig. 31 and 32 are flowcharts showing the flow of processing of the blood glucose meter 102. Fig. 31 and 32 are diagrams for explaining the operation flow of the state transition diagram of fig. 30.

When the power switch 204 and the like are turned on to start the process (S3101), the blood glucose meter 102 first performs a menu display process (S3102 is S3001 of fig. 30). Here, when the power switch 204 is turned off, the process is ended (S3103).

When the menu display process is ended (S3102), the blood glucose meter 102 performs a patient ID scanning process of reading the patient ID by the barcode reader 208 by an operation of the operator (S3104 — S3002 of fig. 30).

When the patient ID or the like is read in the patient ID scanning process (S3104), the input/output control unit 2902 observes the blood glucose level measurement flag and all insulin administration check flags in the record of the patient ID in the internal patient table 112 (S3105 is S3003 in fig. 30).

Here, if the blood glucose level measurement flag is "true" and one or more insulin administration check flags are "false" (S3105: no), the blood glucose meter 102 performs the blood glucose level display (2) (S3106: S3004 of fig. 30). Otherwise, that is, when the blood glucose level measurement flag is "false" or all the insulin administration check flags are "true" (S3105: "yes"), the blood glucose meter 102 performs the blood glucose level measurement process (S3107: "S3005 of fig. 30).

When the blood glucose level is measured in the blood glucose level measurement process (S3107), the blood glucose meter 102 performs the blood glucose level display process (1) (S3108 is equal to S3006 of fig. 30).

When the blood glucose level is displayed in the blood glucose level display (1) process (S3108), the input/output control unit 2902 then checks all the insulin administration check flags (S3109 — S3007 in fig. 30). If all the insulin administration check flags are "true" (S3109: yes), the "re-measurement/next patient" selection process is performed (S3112 ═ the "re-measurement/next patient" selection state S3008 of fig. 30). Otherwise, that is, if one or more insulin administration check flags are "false" (S3109: no), the blood glucose meter 102 performs a "re-measurement/insulin/next patient" selection process (S3110 ═ re-measurement/insulin/next patient "selection state S3009 in fig. 30).

After the "re-measurement/insulin/next patient" selection process S3110, the process branches according to the operation of the operator.

When the operator selects "insulin" (S3111: "yes"), the blood glucose level measurement flag of the patient is set to "true" (S3112), and the process proceeds to insulin administration amount display processing (S3217 in fig. 32 is the insulin administration amount display state S3010 in fig. 30).

When the operator selects "next patient" (S3114: YES), the blood glucose level measurement flag for the patient is set to "true" (S3116), and the process returns to the patient ID scanning process (S3104).

When the operator selects "re-measurement" (S3114: NO), the blood glucose level measurement flag for the patient is set to "false" (S3115), and the process returns to the patient ID scanning process (S3104).

The description is continued with reference to fig. 32.

When the insulin input amount display process is finished (S3217), the blood glucose meter 102 receives an operation of the input key 206 by the operator, and shifts to an "input/non-input" selection process (S3218 — selection state S3013 of fig. 30). Thereafter, regardless of the result of the selection operation performed by the operator on the operation unit 608, the insulin input amount display flag is set to true (S3219, processing S3014 in fig. 30).

After step S3219, if "thrown" is selected as a result of the operator' S selection operation on the operation unit 608 (S3220: "yes"), the blood glucose meter 102 displays a character string of "thrown" on the display unit 615 (S3221 ═ thrown "display state S3015).

After step S3219, if "not plunge" is selected as a result of the operator' S selection operation on the operation unit 608 (S3220: "no"), the blood glucose meter 102 displays a character string of "not plunge" on the display unit 615 (S3224 ═ not plunge "display state S3016).

After the character string "dropped" is displayed on the display unit 615 in step S3221, the blood glucose meter 102 branches processing according to the result of the selection operation performed by the operator on the operation unit 608.

After step S3221, if "OK" is selected as a result of the selection operation performed by the operator on the operation unit 608 (S3222: "yes"), the blood glucose meter 102 sets the insulin intake confirmation flag to "true" (S3223 ═ processing S3017 in fig. 30), and then the routine proceeds to a branch of step S3226.

After step S3221, if "return" is selected as a result of the selection operation performed by the operator on the operation unit 608 (S3222: "no"), the blood glucose meter 102 returns to the "thrown/unsprung" selection process (S3218).

In step S3224, the blood glucose meter 102 displays a character string of "not thrown in" on the display unit 615 in the same manner as in step S3221, and thereafter, branches processing according to the result of the selection operation performed by the operator on the operation unit 608.

After step S3224, when "OK" is selected as a result of the operator' S selection operation on the operation portion 608 (S3225: "yes"), the blood glucose meter 102 branches to step S3226.

After step S3224, if "return" is selected as a result of the selection operation performed by the operator on the operation unit 608 (S3225: "no"), the blood glucose meter 102 returns to the "thrown/unsprung" selection process (S3218).

The blood glucose meter 102 confirms all the insulin administration confirmation flags of the patient as the current processing target in step S3226.

If the all-insulin-administration check flag is "true", that is, if all the medicines have been administered (S3226: "yes"), the blood glucose meter 102 proceeds to the administration list display processing (1) (S3227 ═ state S3019 of the administration list display (1) in fig. 30).

When one or more insulin administration check flags are "false", that is, when there is a drug that has not been administered (S3226: "no"), the blood glucose meter 102 proceeds to an administration list display process (2) (S3228 ═ state S3020 of the administration list display (2) in fig. 30).

After the drop list display processing (2) in step S3228, the blood glucose meter 102 branches processing according to the result of the selection operation performed by the operator on the operation unit 608.

After step S3228, if yes is selected as a result of the selection operation performed by the operator on the operation unit 608 (yes in S3229, state S3020 of the input list display (2) in fig. 30), the blood glucose meter 102 determines that the operator has left the remaining insulin input process for the patient, and shifts to the branch process for confirmation (S3230, state S3021 of fig. 30).

After step S3228, if "return" is selected as a result of the selection operation performed by the operator on the operation unit 608 (no in S3229 is in the state S3020 of the administration list display (2) in fig. 30), the blood glucose meter 102 determines that the operator continues the remaining insulin administration process for the patient, and shifts to the insulin administration amount display process (S3217).

In the branching process for confirmation in step S3230, the blood glucose meter 102 branches the process in accordance with the result of the selection operation performed by the operator on the operation unit 608.

When the operator selects "yes" as a result of the selection operation performed on the operation unit 608 (yes in S3230, which is the completion confirmation state S3021 in fig. 30), the blood glucose meter 102 determines that the operator has determined that the remaining insulin administration process for the patient remains, and branches to processing to determine whether to return to the menu (S3231, which is the "next patient/menu" selection state S3022 in fig. 30).

When the operator selects "return" as a result of the selection operation performed on the operation unit 608 (no in S3230 — completion confirmation state S3021 in fig. 30), the blood glucose meter 102 determines that the operator wants to restart the remaining insulin administration process for the patient, and the process proceeds to a branch process of step S3226. As a result, since there is no medicine to be administered (S3226: "NO"), the process proceeds to the administration list display processing (2) in step S3228 again.

In the branching processing of whether or not to return to the menu in step S3231, the blood glucose meter 102 branches the processing in accordance with the result of the selection operation performed by the operator on the operation unit 608.

When the "MENU" is selected as a result of the selection operation performed by the operator on the operation unit 608 (yes in S3231, i.e., in the "next patient/MENU" selection state S3022 in fig. 30), the blood glucose meter 102 returns to the MENU display process (S3102 in fig. 31).

When the "next patient" is selected as a result of the selection operation performed by the operator on the operation unit 608 (no in S3231, i.e., in the "next patient/menu" selection state S3022 in fig. 30), the blood glucose meter 102 returns to the patient ID scanning process (S3104 in fig. 31).

Fig. 33 is a functional block diagram of the measurement data management apparatus 104.

The measurement data management device 104 has various functions in addition to the functions disclosed in the present embodiment, but in the present embodiment, only the functions related to the comparison between the patient information table 1004 and the patient history table 1006 will be described throughout.

The blood glucose meter detection unit 3302 constantly monitors whether or not the blood glucose meter 102 is mounted on the cradle 103 via the USB interface 908. When the blood glucose meter 102 is mounted on the tray 103 or when the blood glucose meter 102 is detached from the tray 103, the blood glucose meter detecting unit 3302 notifies the blood glucose meter operating unit 3303 of the fact.

The blood glucose meter operation unit 3303 mainly performs two kinds of operations.

One is a necessary data communication operation that is performed directly without making an inquiry to the user basically if the blood glucose meter detection unit 3302 notifies that the blood glucose meter 102 is mounted on the cradle 103.

The other is an arbitrary data communication job for transmitting data necessary for the blood glucose meter 102 to circulate to the blood glucose meter 102 in response to an operation by the user.

That is, the operation of the measurement data management apparatus 104 to collect the patient measurement data 117 and the like from the blood glucose meter 102 is basically automatically performed immediately after the blood glucose meter 102 is placed on the cradle 103.

On the other hand, the measurement data management apparatus 104 must transmit the patient data 114 and the like to the blood glucose meter 102 in response to a user operation (manual operation).

The operation unit 909 is a keyboard, a mouse, or the like. The display portion 907 is an LCD display or the like. The operation section 909 and the display section 907 are connected to the user interface control section 3304.

The user interface control unit 3304 displays a predetermined operation screen on the display unit 907. Further, the user's operation is received from the operation unit 909, and the operation screen displayed on the display unit 907 is changed, a predetermined command is transmitted to the blood glucose meter detection unit 3302, or necessary data is input and output from the meter input/output unit 3305.

The table input/output unit 3305 is an interface for inputting and outputting a large amount of table data such as the patient history table 1006, the patient information table 1004, and the patient measurement temporary file 3306 stored in the nonvolatile memory 906 of the measurement data management device 104 between the user interface control unit 3304 and the blood glucose meter operation unit 3303. Specifically, it is a database manager called middleware (middle ware).

The measurement data management device 104 needs to hold a large amount of data. In particular, patient measurement data 117 is downloaded from the glucose meter 102 at each end of the cycle and saved to the non-volatile memory 906, so the amount of data swells daily. When a rapid data input/output function is implemented for such a large amount of data, it is preferable that middleware be present. In addition, in terms of building programs, if middleware exists, the production efficiency is also improved.

In fig. 33, only the patient history table 1006 and the patient information table 1004 are displayed, but actually, there are many more tables. In fig. 26, a table that is not necessary for the description of the present embodiment is omitted.

A patient history table 1006 is created for each patient. Therefore, the table names of the patient history table 1006 include patient IDs. This is a result of considering data saving efficiency. Further, it is also possible to configure a single table in which fields of patient IDs are set.

Fig. 34 is a flowchart showing a flow of processing in which the measurement data management apparatus 104 transmits patient data 114 and the like to the blood glucose meter 102.

When the process is started (S3401), the measurement data management apparatus 104 enters a state of waiting for an operation by the user. The user selects the time of the circulation and the patient to be circulated, and presses the "transmission" button displayed on the display portion 907 (S3402). Then, the user operation is input from the operation section 909 to the user interface control section 3304. The user interface control unit 3304 controls the table input/output unit 3305, and records the cycle information for each patient specified by the user in the patient history table 1006, and records the information (cycle type) of whether to measure the blood glucose level and whether to administer insulin in the "cycle type under implementation" field of the patient information table 1004 (S3403).

Next, the user interface control unit 3304 creates the patient data 114 from the contents recorded in the patient history table 1006 and the patient information table 1004 via the table input/output unit 3305. Then, the user interface control unit 3304 controls the table input/output unit 3305 and the blood glucose meter operation unit 3303, and transmits the patient data 114 together with the user basic data 115 and the chip batch data 116 to the blood glucose meter 102 via the USB interface 908 (S3404). If the transmission is completed, the user interface control unit 3304 performs a display of "rotatable" in the display unit 907 (S3405).

Next, the blood glucose meter operation unit 3303 checks whether the blood glucose meter detection unit 3302 is out of contact with the blood glucose meter 102 (S3406). If the connection with the blood glucose meter 102 is disconnected (S3406: YES), the blood glucose meter operating section 3303 notifies the user interface control section 3304 of the meaning. Upon receiving this, the user interface control unit 3304 deletes the "recyclable" display displayed on the display unit 907 (S3407), and ends the series of processing (S3408).

Fig. 35 and 36 are flowcharts showing the flow of processing in which the measurement data management apparatus 104 receives the patient measurement data 117 and the like from the blood glucose meter 102.

When the process is started (S3501), the blood glucose meter operation unit 3303 checks whether or not the blood glucose meter detection unit 3302 detects the connection of the blood glucose meter 102 (S3502). When the connection with the blood glucose meter 102 is established (S3502: yes), first, the blood glucose meter operating part 3303 acquires the serial number of the blood glucose meter 102 (S3503). Next, the user interface control unit 3304 sets (initializes) an internal alarm flag (not shown) to "false" (S3504).

Next, the blood glucose meter operation unit 3303 downloads the patient measurement data 117 from the blood glucose meter 102, and creates a patient measurement temporary file 3306 with the file name of the serial number acquired before through the table input/output unit 3305 (S3505). In response, the user interface controller 3304 focuses on the head record of the patient measurement temporary file 3306 (S3506).

This is followed by a loop process.

The user interface controller 3304 reads the currently focused record of the patient measurement temporary file 3306, and records the content of the current record in the corresponding record of the corresponding patient history table 1006 (S3507). Next, the information on the cycle type, that is, whether or not the blood glucose measurement value is performed and whether or not the insulin administration is performed, recorded in the corresponding record of the patient information table 1004 is compared with the content of the flag recorded in the "insulin administration result" field of the current record of the patient history table 1006 in the past (S3508).

If the contents do not match as a result of the collation (S3509: no), the user interface control unit 3304 sets the alarm flag to true (S3510). Then, patient data 114 for re-measurement is created based on the data recorded in the current patient history table 1006 and stored in a temporary file (not shown) (S3511).

In the case where the respective contents are identical as a result of the collation (S3509: YES), no operation is performed.

Then, the user interface controller 3304 confirms whether the record of the current interest of the patient measurement temporary file 3306 is the final record (S3512). If the record is not the final record (S3512: NO), the next record is focused on (S3513), and the series of processing is continued (S3507).

The description is continued with reference to fig. 36.

In step S3512, if the record of current interest is the final record (S3512: YES), the user interface control unit 3304 confirms the alarm flag (S3614). In the case where the alarm flag is "true" (S3614: YES), a warning message is displayed (S3615). Then, an input by the user is waited (S3616).

If the user presses the "transmission" button (S3617: YES), the warning message is deleted without any operation (S3619). However, if the button pressed is not the "transfer" button (S3617: NO), the user interface control unit 3304 controls the input/output unit 3305 and the blood glucose meter operating unit 3303, and transmits the patient data 114 held in the temporary file created previously to the blood glucose meter 102 (S3618).

Regardless of which option is selected, the user interface control unit 3304 finally deletes the temporary file (S3620), and ends the process (S3621).

FIG. 37 is a view showing a display part 907 of the measurement data management apparatus 104

The main menu window of (1). Fig. 37 is a diagram showing an example of warning display.

A blood glucose meter status display section 3703 is provided on the lower side of the center of main menu window 3702. An inset 3704 of the glucose meter 102 is displayed in the glucose meter status display column 3703. A portion of this inset 3704 that corresponds to an LCD is a connection state display column 3705.

A nickname composed of an arbitrary character string assigned to the blood glucose meter 102 is displayed in a nickname display field 3706.

When the measurement data management device 104 determines that there is a patient who has forgotten to measure the blood glucose level or forgets to administer insulin, a warning message 3708 is displayed. In fig. 37, "[ warning ] is displayed that there is an unfulfilled plan. "such a message. The display determination is made by the coincidence/non-coincidence of the values in the "circulation type during execution" field in the patient information table 1004 and the "insulin administration result" field in the patient history table 1006 described in fig. 35.

Fig. 38 is a schematic diagram showing changes in data existing between the measurement data management apparatus 104 and the blood glucose meter 102 and flags included in the table.

A "loop type during implementation" field is provided in the patient information table 1004 stored in the nonvolatile memory of the measurement data management apparatus 104. In this field, it is in this field,

record "1" when only the blood glucose level is measured,

record "2" in the case of insulin administration alone,

record "3" when both blood glucose level measurement and insulin administration were performed. These contents represent the implementation contents instructed to the blood glucose meter 102.

The patient data 114 is created from the contents recorded in the patient information table 1004 and the patient history table 1006. An "insulin therapy classification" field is present in the patient data 114. In this field, as illustrated in fig. 26,

record "0" when only blood glucose level measurement is performed,

record "1" when blood glucose level measurement and insulin administration using a sliding scale are performed,

record "2" in the case of blood glucose level measurement and a fixed insulin administration,

record "5" when only insulin administration using the sliding scale is performed,

record "6" in the case of a fixed insulin infusion only.

When the blood glucose meter 102 reads the patient data 114, the patient data 114 is recorded to the internal patient table 112. Here, the value of the "insulin therapy classification" field of the patient data 114 is converted into the following four flags as the value of the "measurement/administration/display flag" field:

blood sugar level measurement marker

Insulin administration confirmation marker

Insulin administration amount display mark and

a measurement presence flag that is a value of the "measurement presence flag" field.

When only blood glucose level measurement is performed, the blood glucose level measurement flag is set to "false", and the insulin administration check flag is set to "true" so that insulin administration is not performed.

The insulin input amount display flag is set to "true" only by the insulin input amount display processing, and therefore the initial value must be set to "false".

Since the blood glucose level is measured, the measurement presence flag is set to true.

That is, the flag is set to "0101" in the order of the flags.

Since the insulin administration check flag is data with data of a drug to be administered, when only blood glucose level measurement is performed, virtual drug administration information is assigned to the patient in order to add the insulin administration check flag.

In the case where only insulin administration is performed, the blood glucose level measurement flag is set to "true", and since insulin administration is necessary, all insulin administration check flags are set to "false" for each drug administered to the patient.

As described above, the initial value of the insulin input amount display flag is "false".

Since the blood glucose level is not measured, the measurement presence flag is set to false.

That is, the flag is set to "1000" in the order of the above flags.

When both blood glucose level measurement and insulin administration are performed, the blood glucose level measurement flag is "false", the insulin administration confirmation flag is "false", the insulin administration amount display flag is "false", and the measurement presence/absence flag is "true". Thus, it becomes "0001".

When only blood glucose level measurement is performed, the blood glucose level measurement flag is set to true when blood glucose level measurement is completed, and therefore, the flag changes from 0101 to 1101.

In the case of performing only insulin administration, when insulin administration is completed, the insulin administration confirmation flag and the insulin administration amount display flag are set to "true", respectively, and thus are changed from "1000" to "1110".

In the case where both blood glucose level measurement and insulin administration are performed, when both are completed, the blood glucose level measurement flag, the insulin administration confirmation flag, and the insulin administration amount display flag are all set to "true", and therefore, the level is changed from "0001" to "1111".

The values of these flags of the internal patient table 112 are converted into the values of the "blood glucose level measurement flag" field of the patient measurement data 117.

If the flag is "1101", the state is changed to "1" in which only the blood glucose level measurement is completed,

when the flag is "1110", the input is changed to "2" in which only insulin administration is completed,

if the flag is "1111", the flag is converted to "3" which completes both the blood glucose level measurement and the insulin administration.

The transformed value is recorded directly into the "insulin delivery results" field of the patient history table 1006.

The value of the "circulation type during execution" field of the patient information table 1004 is compared with the value of the "insulin administration result" field of the patient history table 1006, and if they match, it can be determined that the operation has been completed as instructed, and if they do not match, it can be determined that the operation has not been performed as instructed.

If the values of the respective flags in the internal patient table 112 are kept in the state of "0101", "1000", or "0001", these indicate that neither blood glucose level measurement nor insulin administration is performed. In this case, "0" is recorded in the "blood glucose level measurement flag" field of the patient measurement data 117.

In addition, in the case of "measurement + administration", only blood glucose level measurement is performed and insulin administration may be forgotten. At this time, the flag changes from "0001" to "1001" in which only blood glucose level measurement is performed and insulin administration check processing is forgotten, or "1101" in which insulin administration check is performed but insulin administration amount display is not performed. The values of these two flags correspond to "1" of the "measurement only" field of the "blood glucose value measurement flag" of the patient measurement data 117.

When the value of the "loop type during execution" field of the patient information table 1004 is "1" indicating only blood glucose level measurement, but the value of the "insulin administration result" field of the patient history table 1006 is "0", it can be determined that the blood glucose level of the patient has been forgotten to be measured.

When the value of the "circulation type during execution" field in the patient information table 1004 is "2" indicating only insulin administration, but the value of the "insulin administration result" field in the patient history table 1006 is "0", it can be determined that the patient has forgotten insulin administration.

When the value of the "circulation type during execution" field in the patient information table 1004 is "3" indicating blood glucose level measurement and insulin administration, but the value of the "insulin administration result" field in the patient history table 1006 is "0", it can be determined that both blood glucose level measurement and insulin administration of the patient have been forgotten.

When the value of the "circulation type during execution" field in the patient information table 1004 is "3" indicating blood glucose level measurement and insulin administration, but the value of the "insulin administration result" field in the patient history table 1006 is "1", it can be determined that the patient has forgotten insulin administration.

The measurement data management device 104 can determine whether or not the patient is administered by comparing the value of the "cycle type during administration" field of the patient information table 1004 with the value of the "insulin administration result" field of the patient history table 1006 as described above.

For a patient who has forgotten to measure the blood glucose level or administer insulin, cycle data is automatically created again and transmitted to the blood glucose meter 102, thereby eliminating implementation omission. In this case, since the cycle data creating process is automatically performed by the measurement data management device 104, the user can quickly perform the cycle again without performing a complicated operation such as confirming the patient who has forgotten to be performed again.

The cycle data was again prepared as follows.

(1) The same data is directly transmitted when only blood glucose level measurement and only insulin administration are performed.

(2) In the case where both blood glucose level measurement and insulin administration are not performed despite the instruction of both, the same data is directly transmitted.

(3) When only blood glucose level measurement is performed and insulin administration is not performed despite instructions for both blood glucose level measurement and insulin administration, only data for insulin administration is created and transmitted.

At this time, the blood glucose level of the patient included in the patient measurement data 117 received from the blood glucose meter 102 is recorded as the latest data in the "patient measurement history data" field of the newly created patient data 114.

When it is detected that the "insulin therapy classification" field of the patient data 114 is set to "5" indicating only insulin administration using a sliding scale, the blood glucose meter 102 reads the latest blood glucose level in the "patient measurement history data" field. Then, the blood glucose level is compared (searched) with the sliding scale 2509 in the "sliding scale administration information" field, and the type of insulin to be administered to the patient and the insulin administration amount are obtained.

The present embodiment discloses a blood glucose level measurement system.

The measurement data management device holds the type of implementation content included in the cycle data transmitted from the measurement data management device to the blood glucose meter in its own patient information table. After the data received from the blood glucose meter is written in the patient history table, it is checked whether or not the blood glucose level measurement and/or the insulin administration is performed as instructed. If the result of the comparison shows a mismatch, it can be determined that the blood glucose level measurement and/or insulin administration has not been performed. Based on this determination, the measurement data management apparatus displays a warning message on the display unit, and notifies a user such as a nurse that there is a patient who has forgotten to perform blood glucose level measurement and/or insulin administration.

In response to the notification, the user automatically creates again a patient who has forgotten to perform blood glucose measurement and/or insulin administration and the contents to be performed by the patient, and transmits cycle data to the blood glucose meter.

With the above-described configuration, the user can quickly grasp whether or not to forget to perform the blood glucose level measurement and/or insulin administration. In addition, recirculation can be performed quickly.

The embodiments of the present invention have been described above, but the present invention is not limited to the above embodiments, and other modifications and application examples can be included without departing from the spirit of the present invention described in the claims.

Claims (3)

1. A blood glucose level measurement system comprising:

a blood glucose meter is provided with: a measurement unit for measuring a blood glucose level; a nonvolatile memory that stores a blood glucose level measurement table in which the measured blood glucose level is recorded; and a transmission unit that transmits the blood glucose level measurement table; and

a measurement data management device is provided with: an insulin administration instruction table having a patient ID field and a measurement scheduled time field for blood glucose level measurement; a patient history table having a patient ID field, a predetermined date and time of measurement field, a blood glucose value field, and an unfulfilled flags field; a receiving unit connected to the blood glucose meter to receive the blood glucose level measurement meter; an implemented-patient history processing unit that records a record obtained from the received blood glucose level measurement table in the patient history table as a record with the non-implemented flag field being "false"; an unexecuted patient history record processing unit configured to additionally record, as a record in which the unexecuted flag field is "true", a record obtained by searching for a patient ID for which a blood glucose level measurement is scheduled within a predetermined time from a current time from the scheduled measurement time field of the insulin administration instruction table, in the patient history record table; an unexecuted patient warning processing unit which searches the patient history table to determine whether or not there is a record in which the unexecuted flag field is "true"; a display control unit that generates a warning display when the non-implemented patient warning processing unit determines that a record having the non-implemented flag field "true" is present in the patient history table; and a display unit that displays the warning display generated by the display control unit.

2. The blood glucose level measurement system according to claim 1,

when the blood glucose level measurement has been performed by the patient whose addition was recorded in the patient history table by the non-implemented patient history processing unit, the implemented patient history processing unit sets the non-implemented flag field of the record additionally recorded in the patient history table by the non-implemented patient history processing unit to false.

3. The blood glucose level measurement system according to claim 1,

the implemented-patient history processing unit detects whether or not there is a patient for which blood glucose level measurement is not implemented in the received blood glucose level measurement table, and causes the display control unit to display an alarm.