TWI552104B - Blood glucose level management system - Google Patents

Description

Blood glucose management system

The invention relates to a blood sugar value management system, a blood sugar value data transmission device, a blood sugar value data transmission program and a blood sugar value data transmission method.

More specifically, the present invention relates to a blood glucose value management system capable of collectively collecting and managing blood glucose values from a plurality of different blood glucose meters, and a blood glucose data transmission device for the blood glucose management system. Blood glucose data transmission program and blood glucose data transmission method.

As is well known, diabetes is caused by abnormal insulin secretion in the pancreas or reduced sensitivity to insulin. In particular, in patients with type 1 diabetes whose insulin secretion is stopped, it is necessary to measure the blood glucose level before eating, and to administer insulin according to the value.

In the past, in order to easily measure the blood glucose level by the patient or his/her family in the home, the applicant has developed and manufactured a small blood glucose measuring device (hereinafter referred to as a "glucometer") for self-measurement. In addition, the applicant has also developed a blood glucose meter including various management functions corresponding to a plurality of patients for the ward.

In the present specification, in order to distinguish the blood glucose meters having different specifications, the small blood glucose meter for self-measurement is referred to as a personal blood glucose meter, and the latter-oriented blood glucose meter is referred to as a ward blood glucose meter. .

Further, the applicant's patent application relating to the latter's ward blood glucose meter and blood sugar level management system is shown in Patent Document 1.

[Previous Technical Literature] [Patent Literature]

[Patent Document 1] International Publication WO2009/031636

So far, the applicant has constructed a blood glucose management system suitable for a personal blood glucose meter as a computer application, and is mainly provided for a hospital. The hospital used the blood glucose management system for both hospitalized patients and hospitalized patients.

Thereafter, the applicant developed a ward blood glucose meter disclosed in Patent Document 1 and a blood glucose level management system for the ward blood glucose meter.

However, personal blood glucose meters in hospitals have become quite popular, and it is difficult to replace these personal blood glucose meters with the cost. Therefore, in the hospital, the blood glucose level management system of the blood glucose meter and the blood glucose level management system of the blood glucose meter of the ward coexist, which poses obstacles to the management and application of the blood glucose value data.

The present invention has been made in view of the above aspects, and an object of the present invention is to provide a blood sugar value management system, a blood glucose value data transmission device, a blood glucose value data transmission program, and a blood sugar value data collection device capable of collectively collecting and managing blood glucose values from a plurality of different blood glucose meters. Blood glucose data transmission method.

In order to solve the above problems, the blood sugar level management system of the present invention includes a first blood glucose meter including a blood sugar level measuring unit and a first blood sugar level meter, wherein the blood sugar level measuring unit measures a blood sugar level of the patient, and the first blood sugar level is small. The table includes a patient ID field in which the patient identity (ID) of the patient is uniquely determined, a blood glucose value field in which the blood glucose level of the patient measured by the blood glucose level measuring unit is stored, and a blood glucose value measuring unit in which the patient is stored. blood a date and time field for measuring the date and time of the measurement of the sugar value; a second blood glucose meter comprising a blood glucose level measuring unit and a second blood glucose level table, wherein the second blood glucose level table includes a blood sugar value field and a measurement date and time field; The blood glucose value table includes a patient ID field, a blood glucose value field, and a measurement date and time field; and a blood glucose value data transmission device including a communication unit and an input/output control unit, the communication unit and the first blood glucose Considering the second blood glucose meter for data communication, the input/output control unit is connected to the server via a network and connected to the communication unit, and determines that the blood glucose meter that performs communication is the first blood glucose meter or the second blood glucose meter. In the case of the blood glucose meter, the content of the first blood glucose level table is uploaded to the server, and in the case of the second blood glucose meter, after determining the patient ID for the blood glucose value recorded in the second blood glucose level table, the second The content of the blood glucose level table is uploaded to the server along with the determined patient ID.

The blood glucose data transmission device determines the first blood glucose meter and the second blood glucose meter in the initial stage of communication. Then, if it is the first blood glucose meter, the content of the first blood glucose level table in the first blood glucose meter is immediately uploaded to the server. In the case of the second blood glucose meter, after determining the patient ID for the blood glucose value recorded in the second blood glucose level table in the second blood glucose meter, uploading the content of the second blood glucose level table together with the determined patient ID To the server.

According to the present invention, a blood glucose value management system, a blood glucose value data transmission device, a blood glucose value data transmission program, and a blood glucose value data transmission method capable of collectively collecting and managing blood glucose data from a plurality of different blood glucose meters can be provided.

[Overall composition]

Fig. 1 is a schematic view showing the overall configuration of a blood glucose level management system as an example of an embodiment of the present invention.

The blood glucose management system 101 includes a terminal 401 and a server 104. The terminal 401 receives blood glucose data from the personal blood glucose meter 102 and the ward blood glucose meter 103. The server 104 receives the blood glucose data from the terminal 401 and records the data therein. In the library.

Two terminals 401 are shown in FIG.

The first terminal 105 is configured by connecting an IC card reader 108 and a barcode reader 109 to a well-known computer to which a keyboard 106 and a mouse 107 are connected. The first terminal 105 mainly receives the blood glucose level data from the personal blood glucose meter 102, and may also correspond to the ward blood glucose meter 103.

The second terminal 110 is connected to an IC card reader 108 and a cradle 111 on a well-known computer including a keyboard. The holder 111 is a charger for a lithium ion battery built in the ward blood glucose meter 103, and also serves as an interface for performing infrared communication with the ward blood glucose meter 103. The second terminal 110 mainly receives the blood glucose level data from the ward blood glucose meter 103, but is limited to the hospitalized patient, and may also correspond to the personal blood glucose meter 102.

The keyboard 106, the mouse 107, the IC card reader 108, and the barcode reader 109 connected to the first terminal 105, and the IC card reader 108 and the bracket 111 connected to the second terminal 110 are, for example, connected by a universal serial A common interface such as a Universal Serial Bus (USB) is connected to the first terminal 105.

The first terminal 105 and the second terminal 110 are transported by the same application. Row.

The IC card reader 108 is an interface for short-range wireless communication, and the specifications of the IC card reader 108 are, for example, the well-known Felica (registered trademark).

The infrared communication function included in the holder 111 is, for example, a well-known Infrared Data Association (IrDA) function.

Each of these communication interfaces transmits and receives data such as blood glucose values as stream data in plain text.

[patient glucometer 103]

2 is a functional block diagram of the ward blood glucose meter 103. The ward blood glucose meter 103, which is also called a first blood glucose meter, is an electronic device formed mainly by a microcomputer.

The blood sugar level measuring unit 201 detects a change in the optical reflectance of the test paper 204 that causes discoloration due to the blood 205 of the measurement subject, and measures the blood sugar level.

The basic blood glucose measurement of the personal blood glucose meter 102 and the ward blood glucose meter 103 has the same configuration as in the prior art. Hereinafter, the structure for measuring the blood sugar level will be briefly described.

The user of the ward blood glucose meter 103 attaches a measurement wafer (not shown) to the ward blood glucose meter 103, and sucks the blood 205 of the measurement target to the measurement wafer. A test paper 204 made of a porous film such as polyether fluorene is incorporated in the measurement wafer. Then, when the blood 205 sucked on the wafer reaches the test paper 204, it reacts with the reagent contained in the test paper 204 to develop color. Then, the ward blood glucose meter 103 irradiates the test paper 204 with a light emitting diode (LED) 202 as a light emitting element. The emitted light receives the reflected light from the test paper 204 by the photodiode 203 as a light receiving element. Then, the ward blood glucose meter 103 converts the analog light receiving intensity signal obtained by the light receiving element into a digital value after a predetermined reaction time, and then converts the digital value into a blood sugar level.

Further, the configuration of the blood glucose level measurement is not limited to the above-described optical measurement method using a color developing reagent, and a structure which has been previously used for blood glucose measurement such as an electrochemical sensor method may be employed.

The barcode reader 206 includes the same functions as the barcode reader 109 connected to the first terminal 105 described above. The barcode reader 206 reads, for example, a barcode of the patient ID printed on the business card of the chest of the patient's chest, and a barcode of the operator ID printed on the business card of the doctor or nurse, and outputs the text encoded into the barcode. Flow data.

The Real Time Clock (hereinafter referred to as "RTC") 207 is equipped with most of the usual microcomputers to output date and time information.

In addition, the patient ID refers to a character string such as a unique value or a letter that uniquely identifies a patient (measurement target). The operator ID is also a string of characters used to uniquely determine the operator of the blood glucose meter.

The patient table 208 is a table in which the patient ID and the patient's name of the patient are recorded.

The operator table 209 is a table in which an operator ID and an operator name of an operator such as a doctor or a nurse are recorded.

The prescription table 210 is a table in which a patient ID and a prescription for insulin of the patient are recorded.

Also known as the first blood glucose level, the blood glucose value of the small table 211 is recorded. A table of patient IDs, measured blood glucose values, and date and time of measurement.

The device type name 212 is a text material indicating the device type name of the ward blood glucose meter 103.

The patient table 208, the operator table 209, the prescription table 210, the blood glucose level table 211, and the device type name 212 are stored in an Electrically-Erasable Programmable Read-Only Memory (EEPROM). In non-volatile storage devices. The device type name 212 is set to be unrewritable and deleteable, and the patient table 208, the operator table 209, the prescription table 210, and the blood glucose level table 211 are set to be rewriteable by the terminal 401.

The short-range wireless communication unit 213 is an interface for performing short-range wireless communication with the IC card reader 108 of the terminal 401 to transmit and receive data.

The infrared communication unit 214 is an interface that performs infrared communication with the holder 111 of the terminal 401 to transmit and receive data.

The ward blood glucose meter 103 can communicate with the terminal 401 by any one of the short-range wireless communication unit 213 and the infrared communication unit 214.

The input/output control unit 215 controls input and output of information. Specifically, the input/output control unit 215 displays the patient ID and the operator ID from the barcode reader 206 after displaying the screen of the guidance operation on the display unit 217 in accordance with the operation information sent from the operation unit 216. The value measuring unit 201 acquires the blood glucose level data, and acquires the date and time of acquisition of the blood glucose level data from the RTC 207, and associates the pieces of information in the blood glucose level table 211. Immediately after the blood glucose level is measured, the input/output control unit 215 reads a prescription of insulin or the like from the necessary patient prescription table 210 and displays it. In the display unit 217. Then, the input/output control unit 215 performs bidirectional communication with the terminal 401 via the short-range wireless communication unit 213 or the infrared communication unit 214, and transmits the information recorded in the blood glucose level table 211 to the terminal 401.

[Personal Blood Glucose Meter 102]

FIG. 3 is a functional block diagram of the personal blood glucose meter 102. Similarly to the ward blood glucose meter 103, the personal blood glucose meter 102, which is also referred to as a second blood glucose meter, is an electronic device formed mainly by a microcomputer. In FIG. 3, the same functional blocks as those in FIG. 2 are denoted by the same reference numerals, and description thereof will be omitted.

The personal blood glucose meter 102 lacks the barcode reader 206, the patient table 208, the operator table 209, the prescription table 210, and the infrared communication unit 214 as compared with the ward blood glucose meter 103. The functional blocks other than the infrared communication unit 214 among the functional blocks are mainly elements necessary for the blood glucose level of the plurality of patients to be measured and recorded by the ward blood glucose meter 103.

Further, the blood glucose level small table 311, which is also referred to as the second blood sugar level sub-table, is different from the blood glucose level small table 211 of the ward blood glucose meter 103, and does not include information of a plurality of patients or operators. Further, the input/output control unit 315 is different from the input/output control unit 215 of the ward blood glucose meter 103, and does not have information of a plurality of patients or operators and a function of operating a prescription.

Further, since the personal blood glucose meter 102 lacks the infrared communication unit 214, communication with the terminal 401 is performed only by the short-range wireless communication unit 213.

On the other hand, the input/output control unit 315 has a function of holding, for example, a conventionally measured blood glucose level of 500 pieces or less as history data.

[terminal 401]

4 is a functional block diagram of the terminal 401.

A terminal 401, which is also known as a blood glucose data transmission device, is a well-known computer operating system (OS). The computer reads and operates the application for the operation of the terminal 401 of the blood glucose level management system 101, and operates as the terminal 401 of the blood sugar level management system 101. The terminal 401 of the blood glucose level management system 101 and the blood glucose for the individual are used. The meter 102 and the ward communicate with the blood glucose meter 103 and receive (download) the blood glucose level data, and communicate with the server 104 to transfer (upload) the blood glucose level data to the server 104.

The network OS includes functions connected to a well-known Transmission Control Protocol/Internet Protocol (TCP/IP) network, such as a Windows operating system (Windows, registered trademark). Further, in addition to the network OS and the application, a web browser 402 to be described later is installed, and the web browser 402 is a graph for displaying a trend indicating a blood sugar level.

The entity of the short-range wireless communication unit 403 is an IC card reader 108, which is an interface for bidirectional communication with the ward blood glucose meter 103 and the short-range wireless communication unit 213 of the personal blood glucose meter 102 to download blood glucose data.

The infrared communication unit 404 is built in the holder 111 and is an interface for bidirectional communication with the infrared communication unit 214 of the ward blood glucose meter 103 to download blood glucose data.

Since both the short-range wireless communication unit 403 and the infrared communication unit 404 perform two-way communication with the blood glucose meter, these may be collectively referred to as a communication unit.

The function of the barcode reader 405 is equivalent to the function of the barcode reader 206 built in the ward blood glucose meter 103 described above. The barcode reader 405 reads the barcode of the patient ID printed on the business card of the chest of the patient's face, or the barcode of the serial number attached or printed on the frame of the personal blood glucose meter 102. , outputting text stream data encoded into a barcode.

The input/output control unit 406 controls input and output of information. Specifically, the input/output control unit 406 constantly monitors the short-range wireless communication unit 403, the infrared communication unit 404, and the operation unit 216. When data is generated, the device type determining unit 407 firstly sets the device type and device type of the blood glucose meter. A master 408 compares and determines its type. Then, if the device type of the blood glucose meter is the ward blood glucose meter 103, the input/output control unit 406 immediately controls the data transmission unit 409 to download all the blood glucose level data from the short-range wireless communication unit 403 or the infrared communication unit 404, and upload it to the servo. 104. When the device type of the blood glucose meter is the personal blood glucose meter 102, the input/output control unit 406 receives the patient ID or the serial number of the personal blood glucose meter 102 from the barcode reader 405 or the operation unit 412, and then controls the patient type determining unit 410. And communicating with the server 104 to confirm whether the patient is a hospital patient or an inpatient. When the patient is an inpatient, the input/output control unit 406 controls the data transmission unit 409 to download only the latest piece of blood glucose level data from the short-range wireless communication unit 403, and uploads it to the server 104. When the patient is a hospital patient, the input/output control unit 406 controls the data transmission unit 409 to download all the blood glucose level data from the short-range wireless communication unit 403, and uploads it to the server 104, and then the input/output control unit 406 causes the web browser 402 to start up. ,by The web browser 402 displays a blood glucose level trend graph on the display unit 411.

Further, the operation unit 412 in which the entity is the keyboard 106 and the mouse 107 is used when the patient ID or the serial number is input instead of the barcode reader 405, and when the web browser 402 is operated.

Both the barcode reader 405 and the operation unit 412 can be collectively referred to as a patient ID input portion for inputting a patient ID or a serial number.

FIG. 4 illustrates all peripheral devices connected to a computer as the terminal 401. However, if the purpose of the terminal 401 is specifically designated, there are also peripheral devices that are not necessarily required.

When the terminal 401 is specifically designated as the reception for the personal blood glucose meter 102, the infrared communication unit 404 which is a dedicated interface of the ward blood glucose meter 103 is not required.

In the case where the terminal 401 is specifically designated as the reception for the ward blood glucose meter 103, the barcode reader 405 for determining the patient ID and correlating the blood glucose level data of the blood glucose meter 102 with the patient ID is not required.

[Server 104]

FIG. 5 is a functional block diagram of the server 104.

The server 104 doubles as a web server and a database server.

The web server program 501 accepts the request of the terminal 401, and transmits a hypertext markup language (html) document file to the terminal 401 according to the request of the terminal 401, and starts a common gateway interface corresponding to the requested content (common gateway interface). , cgi), and the result is sent to the terminal 401.

The terminal authentication cgi502 is implemented to confirm according to the request of the terminal 401. The terminal authentication of the terminal 401 is justified. Therefore, the terminal authentication cgi 502 and the terminal main control unit 503 exchange the login information.

The database operation cgi504 performs operations such as searching or recording the record of the patient main control unit 505 and the blood glucose level table 506 in accordance with the request of the terminal 401.

The data registration cgi 507 records the blood glucose level data sent from the terminal 401 in the blood glucose level table 506.

The graph shows that the cgi 508 retrieves the blood glucose value data of the designated patient from the blood glucose value table 506 according to the request of the terminal 401, and forms an image file directory 509 according to the blood glucose value data according to the blood glucose value data. Send to terminal 401.

The terminal main control unit 503, the patient main control unit 505, and the blood glucose level table 506 can perform operations such as searching or registration by the database management unit 510.

The database operation shell (shell) 511 is a command interpreter, which is a protocol number agreement with the web server program 501, that is, http (TCP number No. 80), and an application layer protocol. Various operations are performed on the terminal main control unit 503, the patient main control unit 505, and the blood glucose level table 506.

That is, the communication means of the operation terminal main control unit 503, the patient main control unit 505, and the blood glucose level table 506 are not necessarily only http, and various protocols can be utilized.

[Field composition of the table]

Fig. 6 is a view showing the structure of fields of various tables.

The blood glucose level table 211 of the ward blood glucose meter 103 includes a patient ID field, a blood glucose value field, a measurement date and time field, and a measurer ID field.

A patient ID is stored in the patient ID field.

The patient's blood glucose level is stored in the blood glucose value field.

The date and time when the blood glucose level of the patient is measured is stored in the measurement date and time field.

In the measurer ID field, the measurer ID of the person in charge such as a doctor or a nurse who measures the blood sugar level of the patient by the ward blood glucose meter 103 is stored.

Since the blood glucose level of a plurality of patients is measured by the ward blood glucose meter 103, the blood glucose level table 211 has a patient ID field in order to distinguish the measured blood glucose values for each patient.

The blood glucose level table 311 of the personal blood glucose meter 102 includes a blood sugar value field, a postprandial flag field, and a measurement date and time field.

The blood glucose level field and the measurement date and time field are the same as the blood glucose value field and the measurement date and time field of the blood glucose level small table 211 of the ward blood glucose meter 103.

In the post-meal flag field, a flag indicating whether or not the blood glucose level of the patient is measured after the meal by the personal blood glucose meter 102 (hereinafter referred to as "post-meal flag") is stored.

Since the blood glucose level of one patient is measured by the personal blood glucose meter 102, the blood glucose level table 311 is different from the blood glucose level table 211 of the blood glucose meter 103 for the ward, and there is no patient ID field for distinguishing the measured blood glucose values from each patient. .

Furthermore, the blood glucose level table 311 can store the previously measured blood glucose values and their accompanying data within 500 pieces.

The patient control unit 505 of the server 104 includes a patient name field and a patient The ID field, the hospital admission flag field, and the blood glucose meter serial number field.

The patient's name is stored in the patient name field.

In the patient ID field, the patient ID is stored in the same manner as the patient ID field of the blood glucose level table 211 of the ward blood glucose meter 103 and the blood glucose level table 311 of the personal blood glucose meter 102.

In the hospitalized hospital flag field, a flag indicating that the patient is an inpatient or a hospital patient is stored.

In the blood glucose meter serial number field, when the patient is a hospital patient, the serial number of the personal blood glucose meter 102 possessed by the patient is stored.

The blood glucose meter serial number is information that can be uniquely associated with the patient ID, and thus can also be referred to as patient ID related information. Therefore, the blood glucose meter serial number field can also be referred to as a patient ID related information field.

The blood glucose value table 506 of the server 104 includes a patient ID field, a blood glucose value field, a postprandial flag field, a device type name field, a measurement date and time field, and a measurer ID field.

The patient ID field is the same as the patient ID field of the patient control section 505.

In the blood glucose level field, the blood sugar level value of the patient is stored in the blood glucose value table 211 of the blood glucose meter 103 of the ward, and the blood glucose value field of the blood glucose level table 311 of the personal blood glucose meter 102.

The postprandial flag field is the same as the postprandial flag field of the blood glucose level small table 311 of the personal blood glucose meter 102. Furthermore, in the case of the glucometer 103 for the ward, the post-meal flag field is ignored.

In the device type name field, the device type name 212 of the blood glucose meter that measures the blood glucose level of the patient is stored.

In the measurement date and time field, the date and time when the blood glucose level of the patient is measured is stored.

In the measurer ID field, the measurer ID of the person in charge such as a doctor or a nurse who measures the blood sugar level of the patient by the ward blood glucose meter 103 is stored.

The blood glucose level table 506 is a field configuration, and this field constitutes all the data including both the blood glucose level table 211 of the ward blood glucose meter 103 and the blood glucose level table 311 of the personal blood glucose meter 102. However, the patient ID field does not exist in the blood glucose level table 311 of the personal blood glucose meter 102. Therefore, when the blood glucose level data is acquired from the personal blood glucose meter 102, the terminal 401 performs processing for determining the patient ID for correlating the patient ID with the blood glucose level data. The details of the process of obtaining and determining the patient ID will be described in the flowcharts of Figs. 7 and 8 below.

The device type master 408 of the terminal 401 includes a device type name field and a category field.

The device type name field is the same as the device type name field of the blood glucose value table 506.

A blood glucose meter indicating that the type of the device is stored in the category field is a flag of the ward blood glucose meter 103 or the personal blood glucose meter 102.

Further, in the blood glucose level management system 101 of the present embodiment, the device type main control unit 408 is owned by the terminal 401, but may be owned by the server 104.

[action]

Starting from this, the operation flow of the blood glucose level management system 101 of the present embodiment will be described using the flowcharts of Figs. 7 and 8 .

FIG. 7 is a flowchart showing the flow of the blood glucose level data registration operation of the terminal 401.

When the processing is started (S701), the input/output control unit 406 of the terminal 401 executes the device type determination processing (S702). In the device type determination processing, the terminal 401 determines the type of the blood glucose meter through the short-range wireless communication unit 403 (IC card reader 108) or the infrared communication unit 404 (bracket 111), and sets a flag for determining the device type. Details of this device type determination process will be described in Figure 8 below.

When the device type determination processing is ended, any one of the personal flag and the ward flag is erected in a random access memory (RAM) (not shown) inside the terminal 401. Therefore, the input/output control unit 406 of the terminal 401 successively confirms which one of the personal flag and the ward flag is erected, that is, which blood glucose meter is currently used for the blood glucose meter 103 and the personal blood glucose meter 102. Count (S703).

When the result of the confirmation is the ward blood glucose meter 103 (NO in S703), the input/output control unit 406 of the terminal 401 downloads all of the blood glucose meter 103 from the ward by the short-range wireless communication unit 403 or the infrared communication unit 404. The blood glucose level data is transmitted to the server 104 (S704), and the series of processing ends (S705).

When the result of the confirmation in step S703 is the personal blood glucose meter 102 (YES in S703), the input/output control unit 406 of the terminal 401 further queries the server 104 for the patient ID acquired in the device type determination processing. Or the serial number (S706), confirming that the patient is an inpatient or a hospital patient, that is, the content of the hospital admission flag of the patient control unit 505 (S707). Furthermore, when the information acquired in the device type determination processing in step S706 is the serial number of the personal blood glucose meter 102, the input/output control unit 406 of the terminal 401 not only obtains the hospitalization of the patient control unit 505 from the server 104. The hospital ID is also obtained.

When the result of the confirmation is that the patient is an inpatient (NO in S707), only the latest piece of blood glucose data is downloaded from the personal blood glucose meter 102, and transmitted to the server 104 together with the patient ID (S708), ending one Series of processing (S705).

If the result of the confirmation in step S707 is that the patient is a hospital patient (YES in S707), all of the blood glucose data is downloaded from the personal blood glucose meter 102, and transmitted to the server 104 together with the patient ID (S709). Then, in conjunction with the server 104, a process of displaying a blood glucose level trend chart of the patient is performed (S710), and a series of processes are terminated (S705).

FIG. 8 is a flowchart showing the flow of the device type determination processing of the terminal 401. It is the detail of step S702 of FIG.

When the processing is started (S801), the input/output control unit 406 first resets an internal timer (not shown) (S802). Then, the input/output control unit 406 performs short-time monitoring of the input of the short-range wireless communication unit 403, the infrared communication unit 404, the barcode reader 405, the cradle 111, or the keyboard 106 (S803). The short time is, for example, about 0.5 seconds to 3 seconds. When the data is input from the short-range wireless communication unit 403, the barcode reader 405, the infrared communication unit 404, or the keyboard 106 during the waiting time, the input/output control unit 406 immediately proceeds to the next processing. In addition, when the waiting time has elapsed, the next processing is also performed.

After the input in step S803 is waited, the input/output control unit 406 confirms whether or not the patient ID or the serial number has been acquired from the short-range wireless communication unit 403, the barcode reader 405, or the keyboard 106 (S804).

When the patient ID or the serial number is not available (NO in S804), the input/output control unit 406 confirms whether or not the device type name 212 has been acquired from the short-range wireless communication unit 403 or the infrared communication unit 404 (S805).

When the device type name 212 cannot be acquired (NO in S805), the input/output control unit 406 then confirms the timer and confirms whether or not a predetermined time has elapsed (S806). The predetermined time is an allowable range for setting the patient ID and the device type name 212 by the personal blood glucose meter 102, and is, for example, about 30 seconds.

If the predetermined time has not elapsed (NO in S806), the input/output control unit 406 returns to step S803 to perform input wait.

When the predetermined time has elapsed (YES in S806), since the timeout has elapsed, the input/output control unit 406 discards all the data such as the acquired patient ID, serial number, or device type name 212, and resets the timer (S807). ), returning to step S803 again, the input waits.

If the material acquired in step S805 is the device type name 212 (YES of S805), the input/output control unit 406 then activates the device type determining unit 407. The device type determining unit 407 searches the device type main control unit 408 with the acquired device type name 212, and confirms that the device type is the ward blood glucose meter 103 or the personal blood glucose meter 102 (S808). If it is the ward blood glucose meter 103 (YES of S808), the input/output control unit 406 has obtained When the patient ID or the serial number is used, it is discarded (S809), and the blood glucose meter is erected as the ward flag of the ward blood glucose meter 103 (S810), and the series of processes is terminated (S811).

If the data acquired in step S804 is the patient ID (YES in S804), the input/output control unit 406 then confirms whether or not the device type name 212 has been acquired at that time (S812). When the device type name 212 has been acquired (YES in S812), the input/output control unit 406 erects the personal flag indicating that the blood glucose meter is the personal blood glucose meter 102 (S813), and ends the series of processes (S811).

When the device type name 212 has not been acquired in step S812 (NO in S812), the input/output control unit 406 starts the timer in order to acquire the device type name 212 (S814), and returns to step S803 to perform input wait.

When the personal blood glucose meter 102 is in step S808 (NO in S808), the input/output control unit 406 next confirms whether or not the patient ID has been acquired (S815). When the patient ID has been acquired (YES in S815), the input/output control unit 406 erects the personal flag indicating that the blood glucose meter is the personal blood glucose meter 102 (S813), and ends the series of processes (S811).

When the patient ID has not been acquired in step S815 (NO in S815), the input/output control unit 406 starts the timer to acquire the patient ID (S814), and returns to step S803 to perform the input wait.

The input/output control unit 406 performs the following determination processing in accordance with the flowchart of the device type determination processing shown in FIG.

. If the result of entering the information obtained by waiting (S803) is the blood in communication When the glucometer is the ward blood glucose meter 103 (YES in S808), the input/output control unit 406 first obtains the patient ID or the serial number due to an erroneous operation or the like, and discards it because it is unnecessary (S809), and immediately sets the ward. Use the flag (S810).

. When the result of the information obtained by the waiting (S803) is that the blood glucose meter in communication is the personal blood glucose meter 102 (NO in S808), the input/output control unit 406 further confirms whether or not the patient ID or the serial number has been acquired at the time ( S815). If the patient ID or the serial number has been obtained (YES of S815), the input/output control unit 406 is provided because the necessary information, that is, the personal blood glucose meter 102 and the associated patient ID or the like is already provided. Set the personal flag (S813).

. When the result of the information obtained by the waiting (S803) is that the input information is the patient ID (YES in S804), the input/output control unit 406 further confirms whether or not the device type name 212 has been acquired at this time (S812). If the device type name 212 has been obtained (YES of S812), it is apparent that it is the personal blood glucose meter 102 (when it is the ward blood glucose meter 103 (YES of S808), it does not return to the input waiting for step S803, so it is not It is possible to proceed to step S812), so the input/output control unit 406 sets the personal flag (S813).

. If the result of the information obtained by the waiting (S803) is that the input information is the patient ID (YES in S804) and the device type name 212 has not been acquired (NO in S812), the input/output control unit 406 acquires the device type name 212. On the other hand, the timer is started (S814), and the input waits again (S803).

. If the result of the information obtained by waiting for (S803) is the personal blood glucose meter 102 (NO of S808), and the patient ID or serial number has not been obtained (S815) In the NO), the input/output control unit 406 starts the timer in order to acquire the patient ID or the serial number (S814), and waits again for input (S803).

As described above, when the terminal 401 downloads the blood glucose level data from the personal blood glucose meter 102 and uploads it to the blood glucose level table 506 of the server 104, it is necessary to obtain the patient ID that cannot be directly obtained from the personal blood glucose meter 102, and is associated with it. The blood glucose value data downloaded. When the device type determination unit 407 determines that the personal blood glucose meter 102 is present, the input/output control unit 406 of the terminal 401 obtains the patient ID or the serial number by the barcode reader 405 or the operation unit 412, and causes the patient to The ID is associated with blood glucose data.

Further, when the input/output control unit 406 of the terminal 401 downloads the blood glucose level data to the personal blood glucose meter 102, the patient type determining unit 410 confirms that the target patient is an inpatient or a hospital patient. Then, in the case of a hospital patient, all of the blood glucose level data contained in the personal blood glucose meter 102 is downloaded, and the blood glucose level trend graph is displayed on the display unit 411 via the web browser 402. On the other hand, if it is an inpatient, only the latest latest blood glucose data contained in the personal blood glucose meter 102 is downloaded. Moreover, the blood glucose value trend chart is not displayed at this time.

FIG. 9 is a view showing an example of a blood glucose level trend chart.

After the input/output control unit 406 of the terminal 401 sends the character string of the Uniform Resource Locator (URL) as a parameter to the web browser 402, the web browser 402 is started, and the URL character string is used for the server 104. The chart shows the cgi508 for access.

The web browser 402 accesses the graph display cgi 508 in accordance with the URL character string sent as a parameter.

The graph display cgi 508 determines the patient ID from the most recent record recorded in the blood glucose level table 506 based on the terminal ID of the terminal 401 having been accessed, and creates the image data of the patient's blood sugar level trend chart. Image archive directory 509. The web browser 402 reads the image data of the blood sugar level trend chart 901 that has been created into the image file directory 509, and displays it on the display unit 411.

In the blood glucose level trend graph displayed on the display unit 411, an image of a line graph in which the horizontal axis takes the measurement date and time and the vertical axis takes the blood glucose level is displayed, and the patient's name is displayed.

The web browser 402 has a function as a graph display control unit for displaying the blood glucose level trend graph 901 on the display unit 411.

In the present embodiment, the blood sugar level management system 101 is disclosed.

The terminal 401 of the blood glucose level management system 101 discriminates the ward blood glucose meter 103 and the personal blood glucose meter 102 by querying the device type name at the initial stage of communication. Then, if the glucometer 103 is used for the ward, the blood glucose value data is immediately downloaded and uploaded to the server 104.

However, in the case of the personal blood glucose meter 102, when the blood glucose level data is downloaded from the personal blood glucose meter 102 and uploaded to the blood glucose level table 506 of the server 104, it is necessary to obtain the patient ID that cannot be directly obtained from the personal blood glucose meter 102. And associated with the downloaded blood glucose data. When the device type determination unit 407 determines that the personal blood glucose meter 102 is present, the input/output control unit 406 of the terminal 401 obtains the patient ID or the serial number by the barcode reader 405 or the operation unit 412, and causes the patient to The ID is associated with blood glucose data.

By configuring the blood glucose level management system 101 in this way, not only the ward blood glucose meter 103 and the personal blood glucose meter 102 can be operated in a common system, but also the blood sugar levels of all patients can be collectively and collectively managed.

Further, when the input/output control unit 406 of the terminal 401 downloads the blood glucose level data to the personal blood glucose meter 102, the patient type determining unit 410 confirms that the target patient is an inpatient or a hospital patient. Then, in the case of a hospital patient, all of the blood glucose level data contained in the personal blood glucose meter 102 is downloaded, and the blood glucose level trend graph is displayed on the display unit 411 via the web browser 402. On the other hand, if it is an inpatient, only the latest latest blood glucose data contained in the personal blood glucose meter 102 is downloaded. Moreover, the blood glucose value trend chart is not displayed at this time.

By configuring the blood glucose level management system 101 in this manner, even when the user of the personal blood glucose meter 102 is different between the hospital patient and the hospitalized patient, it is possible to cope with it extremely carefully.

The embodiment of the present invention has been described above, but the present invention is not limited to the above-described embodiment, and other modifications and application examples are included as long as they do not deviate from the gist of the invention described in the claims.

101‧‧‧Blood Value Management System

102‧‧‧personal blood glucose meter

103‧‧‧ ward with blood glucose meter

104‧‧‧Server

105‧‧‧First terminal

106‧‧‧ keyboard

107‧‧‧ Mouse

108‧‧‧IC card reader

109, 206, 405‧‧‧ barcode reader

110‧‧‧second terminal

111‧‧‧ bracket

201‧‧‧ Blood sugar value measurement department

202‧‧‧LED

203‧‧‧Photoelectric diode

204‧‧‧ test paper

205‧‧‧ blood

207‧‧‧RTC

208‧‧‧ patient table

209‧‧‧ Operator Table

210‧‧‧Prescription Schedule

211, 311‧‧ ‧ blood sugar value table

212‧‧‧Device type name

213, 403‧‧‧ Close Range Wireless Communication Department

214, 404‧‧‧Infrared Communication Department

215, 315, 406‧‧‧ input and output control department

216, 412‧‧‧ Operation Department

217, 411‧‧‧ Display Department

401‧‧‧ Terminal

402‧‧‧web browser

407‧‧‧Device Type Determination Department

408‧‧‧Device Type Control Department

409‧‧‧Data Transmission Department

410‧‧‧Patient category determination department

501‧‧‧web server program

502‧‧‧ Terminal Certification cgi

503‧‧‧ Terminal Control Department

504‧‧‧Database operations cgi

505‧‧‧ Patient Control Department

506‧‧ ‧ blood sugar value table

507‧‧‧Information login cgi

508‧‧‧Chart shows cgi

509‧‧‧Image archive directory

510‧‧‧Database Management Department

511‧‧‧Database operation shell program

901‧‧‧ blood glucose value trend chart

S701~S710, S801~S815‧‧‧ steps

Fig. 1 is a schematic view showing the overall configuration of a blood glucose level management system as an example of an embodiment of the present invention.

Figure 2 is a functional block diagram of a glucometer for a ward.

Figure 3 is a functional block diagram of a personal blood glucose meter.

Figure 4 is a functional block diagram of the terminal.

Figure 5 is a functional block diagram of the server.

Fig. 6 is a view showing the structure of fields of various tables.

Fig. 7 is a flow chart showing the flow of a blood sugar level data registration operation of the terminal.

FIG. 8 is a flowchart showing the flow of device type determination processing of the terminal.

FIG. 9 is a view showing an example of a blood glucose level trend chart.

S701~S710‧‧‧Steps

Claims (6)

A blood glucose level management system includes: a first blood glucose meter including a blood glucose level measuring unit and a first blood glucose level meter, wherein the blood sugar level measuring unit measures a blood sugar level of the patient, wherein the first blood glucose level table includes a unique stored value The patient ID field of the patient ID of the patient is determined, the blood glucose value field storing the blood glucose level of the patient measured by the blood glucose level measuring unit, and the blood glucose level measuring unit storing the blood glucose level of the patient. a measurement date and time field of the measurement date and time; the second blood glucose meter includes the blood glucose level measurement unit and the second blood glucose level table, wherein the second blood glucose level table includes the blood glucose value field and the measurement date and time field; The blood glucose value table includes the patient ID field, the blood glucose value field, and the measurement date and time field, and a blood glucose value data transmission device including a communication unit and an input/output control unit, and the communication unit and the communication unit The first blood glucose meter and the second blood glucose meter perform data communication, and the input/output control unit passes through the network Connected to the server and connected to the communication unit, and determined that the blood glucose meter to communicate is the first blood glucose meter or the second blood glucose meter, and in the case of the first blood glucose meter, the first blood glucose level is small The content of the table is uploaded to the server, and in the case of the second blood glucose meter, the second blood glucose value is in the small table. After the recorded blood glucose level determines the patient ID, the content of the second blood glucose level sub-table is uploaded to the server together with the determined patient ID. The blood glucose value management system according to claim 1, wherein the server further includes a patient control unit, wherein the patient control unit includes the patient ID field and the patient ID associated with the patient ID is stored. a patient ID related information field of the information, and a hospitalized hospital flag field storing a hospital admission flag indicating that the patient is an inpatient or a hospital patient; the blood glucose data transmission device includes a device type determination unit and a patient ID input unit The patient type determining unit and the data transfer unit, wherein the device type determining unit queries the device according to the blood glucose meter that communicates to determine whether the blood glucose meter is the first blood glucose meter or the second blood glucose meter, and the patient The ID input unit is configured to acquire the patient ID or the patient ID related information, and the patient type specifying unit acquires the above-described patient ID input unit when the device type determining unit determines that the blood glucose meter is the second blood glucose meter. After the patient ID or the above patient ID related information, the above patient is obtained from the server Inpatient hospital flag through the data transfer from said first portion and said second blood glucose meter blood glucose meter blood glucose level data is transmitted to the above-described server; output control unit determines the input to the upper portion is determined by the patient category When the patient is in the hospitalized patient, the data transmission unit is controlled to transmit the latest one of the blood glucose level data from the second blood glucose meter to the server, and the patient type determination unit determines that the patient is the In the case of a hospital patient, the data transfer unit is controlled and all of the blood glucose data is transmitted from the second blood glucose meter to the server. The blood glucose level data management system according to claim 2, wherein the blood glucose level data transmission device includes a display unit and a graph display control unit, wherein the display unit displays a blood glucose level trend graph, and the graph display control unit from the servo The image data of the blood glucose level trend graph is received, and the blood glucose level trend graph is displayed on the display unit, and the input/output control unit activates when the patient type determining unit determines that the patient is the hospital patient. The graph display control unit receives the image data of the blood glucose level trend graph from the server in the graph display control unit, and displays the blood glucose level trend graph on the display unit. A blood glucose value data transmission device includes: a communication unit that performs data communication with a first blood glucose meter and a second blood glucose meter, wherein the first blood glucose meter includes a blood glucose level measuring unit and a first blood glucose level meter, and the blood sugar level is measured The blood glucose level of the patient is measured, and the first blood glucose level table includes a patient ID field in which the patient ID of the patient is uniquely determined, and the patient is measured by the blood glucose measuring unit. a blood glucose value field of the blood glucose level, and a measurement date and time field of the measurement date and time when the blood glucose level measuring unit measures the blood glucose level of the patient, wherein the second blood glucose meter includes the blood sugar level measuring unit and the second blood sugar level In the small table, the second blood glucose level sub-table includes the blood glucose value field and the measurement date and time field; and an input/output control unit connected to the server via a network and connected to the communication unit, and determining that the blood glucose meter for communication is In the case of the first blood glucose meter, the first blood glucose meter or the second blood glucose meter uploads the content of the first blood glucose level sub-table to the server, and in the case of the second blood glucose meter After determining the patient ID for the blood glucose level recorded in the second blood glucose level sub-table, the content of the second blood glucose level sub-table is uploaded to the server together with the determined patient ID. A blood glucose value data transmission program for causing a computer to function as a blood glucose level data transmission device including: a communication unit that performs data communication with a first blood glucose meter and a second blood glucose meter, the first blood glucose meter The blood glucose level measuring unit and the first blood sugar level measuring unit measure the blood sugar level of the patient, and the first blood sugar level small table includes a patient ID field in which the patient ID of the patient is uniquely determined, and the stored a blood glucose level field of the blood glucose level of the patient measured by the blood glucose level measuring unit, and a measurement date and time field of the measurement date and time when the blood glucose level measuring unit measures the blood glucose level of the patient, the second blood glucose meter The blood sugar level measuring unit and the second blood sugar level small table, wherein the second blood sugar level sub-table includes the blood sugar value field and a measurement date and time field; and an input/output control unit connected to the server via a network and connected to the communication unit, and determining that the blood glucose meter to be communicated is the first blood glucose meter or the second blood glucose meter In the case of the first blood glucose meter, the content of the first blood glucose level sub-table is uploaded to the server, and in the case of the second blood glucose meter, the blood glucose value recorded in the second blood glucose level table is determined. After the patient ID, the content of the second blood glucose level sub-table is uploaded to the server together with the determined patient ID. A blood glucose value data transmission method, comprising: a device type name obtaining step, obtaining a device type name from a blood glucose meter; and a first blood glucose value data transmitting step, wherein the blood glucose meter includes a plurality of patients in the device type name obtaining step In the case of the glucometer of the blood glucose data, all the blood glucose data are obtained from the ward using the blood glucose meter and transmitted to the server; the patient ID acquisition step is performed to obtain the patient ID uniquely determining the patient or the above The information of the patient ID; and the second blood glucose value data transmission step, in the case of the device type name obtaining step, when the blood glucose meter is a personal blood glucose meter containing the blood glucose value data of a single patient, the blood glucose from the individual is used The blood glucose level data is obtained and transmitted to the server together with the patient ID acquired in the patient ID acquisition step.