JP2002366653A - Remote medical system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an at-home medical system for easily and flexibly introducing and updating software inside a terminal to be required for changing the kind and the number of sensors desired to be connected to an at-home medical terminal without the direct participation of a special engineer. SOLUTION: In a remote medical system in which a center server 2 and a patient terminal 1 are connected by a network, the center server stores and manages the software performed in the patient terminal together with biological data transferred from the patient terminal. When the patient terminal is connected to the server, the constitution of the software mounted on the patient terminal and the constitution of the software to be introduced are compared, a software module to be updated is detected and downloaded and the software of the patient terminal is updated to desired constitution.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a telemedicine system for managing a medical condition and health of a home patient by performing remote communication between a medical facility and a patient terminal installed in a patient's home. The present invention relates to a telemedicine system including a patient terminal capable of flexibly changing the function of a patient having a disease.

[0002]

2. Description of the Related Art In recent years, various types of home medical systems have been appearing on the market in response to the growing need for home health care and health management.

A conventional home medical system of this type is, for example, a home medical system described in Japanese Patent Application Laid-Open No. 8-275927.

This home medical system incorporates a plurality of biometric sensors for measuring biometric information such as an electrocardiogram, displays a method of measuring biometric data using the biometric sensors, displays a series of procedures for measuring a medical condition, and measures biometric information. It has functions such as recording and display, transmission of measured biometric data and medical interview results to medical institutions. By referencing the biometric data collected at the medical institution in this way, the patient's physician does not consult the patient directly, or the patient does not see the physician directly at the medical institution. In addition, the patient's medical condition and health condition can be known. Also,
The patient can spend every day with peace of mind because the doctor in charge can check his / her health condition.

Further, Japanese Patent Application Laid-Open No. Hei 9-215663 incorporates a control program required by a patient terminal for a biological sensor to receive the biological data, and the control program is transmitted to the patient terminal as necessary. With the introduction, the biosensor is connected to the patient terminal to perform transmission / reception and data processing of biometric data. Thereby, various biosensors can be connected to the patient terminal.

[0006]

However, in the above-mentioned conventional home medical system, the type of the biometric sensor connected to the patient terminal is determined in advance in the development stage by the interface of the patient terminal and built-in control software. There was a problem that.

Normally, this type of patient terminal has a built-in sensor for measuring basic biological information such as a sphygmomanometer and a thermometer, but in addition to such a sensor, responds to the disease or condition of the patient. It is desirable to have a biological sensor. For example,
As in the above-mentioned conventional example, it is necessary to provide an electrocardiograph (ECG) and a stethoscope in addition to basic biological information for a patient with a heart disease. Requires a flow meter. For a diabetic patient, a blood glucose meter and a urine glucose sensor are required, and a detailed inquiry tool for calorie intake and exercise amount is useful. As described above, the type and number of sensors to be connected to the home medical terminal largely depend on the type of disease of the patient using the sensor. In some cases, it may be necessary to update the biometric sensor due to breakage or aging, or to change the sensor in order to change the accuracy or measurement method of the biometric information according to a change in the patient's condition.

In general, when connecting a biometric sensor to a home medical terminal, apart from physical connection conditions and electrical connection conditions, software for setting a device interface and a user interface specific to the sensor to the home medical terminal is required. Required. Specifically, a device driver that transmits and receives data from the sensor according to a predetermined procedure and communicates with the OS (operating system) of the terminal, a post-processing module that converts data from the sensor into a meaningful numerical value, and the use of the sensor are used. A help module to support, a display module for measurement results, and the like. When introducing a new biometric sensor or updating a biometric sensor to a terminal,
These software modules need to be newly installed and set up, but this work usually requires specialized knowledge and technology related to the OS, and specialists who are well versed in this field can directly operate the terminal. Must be done.

On the other hand, Japanese Unexamined Patent Application Publication No. 9-215
No. 663, a control program for connecting the biosensor to the patient terminal is incorporated in the biosensor, and this control program is introduced to the patient terminal when the biosensor is connected to the patient terminal. Can be connected to the patient terminal. However, since this control program usually depends on the execution environment, that is, the hardware of the patient terminal, the biosensor includes a program executed on the patient terminal, and is therefore dedicated to the patient terminal. In addition, depending on the type of the biological sensor, adding such a function may lead to a significant increase in cost and a decrease in reliability. Furthermore,
When the version is upgraded by modifying the control program or improving the function, it is necessary to change the control program of the biometric sensor, so that it is necessary to collect each biometric sensor.

The present invention solves such a problem of the conventional patient terminal, and can easily and flexibly introduce and update software in the patient terminal and individual modules constituting the same. The purpose is to provide.

[0011]

In order to solve the above-mentioned problems, a plurality of patient terminals which are provided with biological information collecting means and accumulate and execute software composed of a plurality of modules, and a plurality of patient terminals for collecting and executing the software. , A server for storing and managing data to be referenced and edited is a telemedicine system connected by a network, wherein the server comprises:
The software executed in each patient terminal is stored and managed in module units, and when connecting to the patient terminal, the configuration of the software stored in the patient terminal is detected, and a predetermined module is detected in the patient terminal. The module is selectively downloaded from the server to the patient terminal to be executed.

According to this embodiment, the software module to be updated can be known by comparing the latest configuration of the software possessed by the patient terminal with the configuration of the software to be updated. By downloading only the information from the server to the patient terminal, the terminal software can be updated to a desired configuration.

[0013]

In order to solve the above-mentioned problems, a first embodiment of the present invention comprises a plurality of patient terminals which are provided with biological information collecting means, store software constituted by a plurality of modules, and execute the software. , Collected, referenced,
A remote medical system in which a server for storing and managing data to be edited is connected to the network by a network, wherein the server stores and manages software executed on each patient terminal in a module unit; When making a connection, the configuration of the software stored in the patient terminal is detected, and the module is selectively downloaded from the server to the patient terminal so that a predetermined module is executed in the patient terminal. It is configured as follows.

According to this embodiment, the software module to be updated can be known by comparing the latest configuration of the software of the patient terminal with the configuration of the software to be updated. By downloading only the information from the server to the patient terminal, the terminal software can be updated to a desired configuration.

According to a second aspect of the present invention, in the above-described telemedicine system, the server holds history information of a module stored in each patient terminal and update information of a module held by the server. By comparing these, a module to be transferred to the patient terminal is determined, and the module is downloaded when connected to the patient terminal.

According to this embodiment, since the server always holds the latest software configuration in each terminal,
The software modules to be updated can be known without obtaining the configuration information of the software from the terminal itself, and the server downloads only these modules to the patient terminal to configure the terminal software in the desired configuration. Can be updated.

Further, according to a third aspect of the present invention, in the above-mentioned telemedicine system, each patient terminal holds history information of its own module, and the server stores update information of its own module. Holding, when connecting the patient terminal and the server, the terminal sends the history information to the server, and the server determines the module to be transferred to the patient terminal by comparing the history information with the update information. It is configured to be downloaded.

According to this embodiment, the server obtains the latest software configuration of the terminal from the connected terminal,
By comparing this with the desired software configuration of the server, the software module to be updated is determined without having to store the software configuration information of each terminal, and downloaded to the patient terminal. The software of the terminal can be updated to a desired configuration.

Further, according to a fourth aspect of the present invention, in the above-mentioned telemedicine system, each patient terminal holds history information of its own module, and the server stores update information of its own module. Holding, when the server connects to the patient terminal, the server sends the update information to the patient terminal, and the patient terminal determines a module to be transferred to the patient terminal by comparing these information. The server is notified of the module, and the server causes the patient terminal to download the module.

According to this embodiment, the patient terminal obtains the desired software configuration from the connected server, and compares this with the current software configuration of the patient terminal itself. The software of the terminal can be updated to a desired configuration by determining the software module to be updated and downloading it from the server without storing the software configuration information.

Further, in a fifth aspect of the present invention, in the configuration of the above-described telemedicine system of the present invention, both the module history information and the module update information are software version information. is there.

According to this embodiment, the configuration information of the software in the patient terminal and the server is managed by the version number of each module constituting the software, so that the management and comparison of the modules can be performed easily and easily. .

Further, according to a sixth aspect of the present invention, in the configuration of the above-mentioned telemedicine system of the present invention, one or both of the module history information and the module update information held by the terminal are stored in the system of the patient terminal. This is the module configuration information generated from the configuration information.

According to this embodiment, the configuration information of the software in the patient terminal and the server is managed as the configuration information of the system, and the configuration information of each software module is generated from this system configuration information. It is not necessary to individually manage the history information, and the management and comparison of modules becomes easy and simple.

Further, according to a seventh aspect of the present invention, in the configuration of the above-described telemedicine system of the present invention, the server and the patient terminal further have a function of transmitting and receiving a message, and this message is transmitted when the server and the patient terminal are connected. The transmission and reception and the selective download of the software module are performed continuously by the same communication procedure.

According to this embodiment, each time the patient terminal is connected to the server for performing daily communication such as registration of measured biometric data, the configuration of the latest software module registered in the server from the terminal. The software modules at the patient terminal are always kept up to date as the information is referenced and the modules are downloaded as needed.

Further, an eighth aspect of the present invention, in the configuration of the above-mentioned telemedicine system of the present invention, a part of the software module corresponds to each of a plurality of biological information collecting means connected to the patient terminal. When the biometric information collection means connected to the patient terminal is replaced,
The connection between the replaced biological information collecting means and the patient terminal is established by downloading the module from the server.

According to this embodiment, when adding, changing, or updating the biometric sensor connected to the patient terminal, a software module associated with the change can be remotely downloaded. Operation management can be largely labor-saving.

Further, in a ninth aspect of the present invention, in the configuration of the above-described telemedicine system of the present invention, the server includes a part or all of the modules corresponding to a plurality of functions expressed in the patient terminal. The function is grouped, stored, managed, downloaded, and the corresponding function of the patient terminal is replaced by downloading the corresponding module group.

According to this embodiment, the management cost is reduced because the software modules operating on the patient terminal are managed and operated in groups each having a significantly smaller number than the total number of modules. Are grouped for each function, so that replacement or change of the function can be performed more reliably.

Further, according to a tenth aspect of the present invention, in the configuration of the above-described telemedicine system of the present invention, the server stores and manages restart command information corresponding to at least a part of software modules. When the module is downloaded, the restart command is transmitted, and the patient terminal restarts after the module has been downloaded.

According to this embodiment, when the server downloads a desired software module from the server to the patient terminal, if the server finds that the module that requires the patient terminal to be restarted has been downloaded, the server returns to the patient terminal. By sending a restart command to the terminal and restarting after the download is completed, the function corresponding to the downloaded module can be immediately activated.

An eleventh aspect of the present invention is a program for causing a computer to function as all or a part of the above-described telemedicine system of the present invention.

According to this embodiment, since it is a program, all or a part of the telemedicine system of the present invention can be easily realized using a general-purpose computer or server. Further, by recording the program on a recording medium or distributing the program using a communication line, the program can be easily distributed and installed.

[0035]

Embodiments of the present invention will be described below with reference to the drawings.

(Embodiment 1) FIG. 1 is a block diagram of a home medical system according to the present invention, in which 1 is a patient terminal, and 2 is a center server. The patient terminal 1 and the center server are connected to the terminal-side communication device 3 and the center-side communication device 4, respectively, and exchange data via the communication line 5. The patient terminal 1 is connected to a user interface (IF) device 6 such as a touch panel and a display device, a storage device 7, and a sensor interface 8.
The storage device 7 stores terminal information 9 such as operation information of the patient terminal 1 and patient information, in addition to programs executed on the patient terminal 1.
And the measurement data 10 are stored. Sensors such as a thermometer 11, a sphygmomanometer 12, and an electrocardiograph 13 that measure the biological data of a patient are connected to the sensor interface 8, and the data measured by these is recorded in a measurement data section in the storage device 7. The data is sent to the center server 2 as needed. The number and type of sensors connected to the sensor interface 8 can be changed according to the condition of the patient using the sensor. The storage device 1 is located in the center server 2.
4, the number of patient terminals connected to the server, system configuration information 16 such as information on patients and sensors allocated to each terminal, a profile of each patient, and measurement data transmitted from the patient terminal 1. A patient database 15 and the like to be stored are recorded.

FIG. 2 shows a software configuration of the patient terminal 1 in FIG. The overall operation of the patient terminal 1 is controlled by an operating system (OS) 20. Device drivers corresponding to various sensors connected to the sensor interface 8 and devices directly connected to the patient terminal are coupled to the OS 20. ing. OS
On 20, a database 22 for managing the patient information 9 and the measurement data 10 and an application program 23 operate. The application program 23 is a user I
It teaches the patient how to operate the sensor and the patient terminal 1 through the F device 6, controls input and output of data from the sensor and the patient, and communicates with the center server 2.

In FIG. 1, the center server 2 includes, in a system information area 16 in a storage device 14, an application program 23 executed by the patient terminal 1, a module constituting the application program 23, a driver 21, and the like. I remember and manage. The center server downloads specific versions of these programs and modules to the patient terminal 1 via the communication line 5 as needed. Such an operation is performed when the user wants to correct a defect in the software on the patient terminal, replaces the software with new software, or replaces the sensor connected to the patient terminal with another sensor. It is used when it is necessary to replace the information, operation support information, driver, interface program, and the like. Whether or not to replace the program by downloading to a specific patient terminal is determined by managing the software version of each patient terminal in the center server 2 and the software version to be replaced and the software of the patient terminal. Is determined by comparing with the version of Hereinafter, the operation of this download will be described.

FIG. 3 is a software configuration table for managing all software used in the patient terminal of the system shown in FIG. The software configuration table 30 includes a group name field 31 indicating a category of a software module, a module name field 3
2. From the module version field 33, the registration date field 34 of the version, the restart field 35 indicating whether the OS needs to be restarted when the module is replaced, and the storage location field 36 indicating the storage location of the module. Be composed. In the figure, three types of electrocardiograph drivers connected to the sensor interface 8 are registered. These module names are ECG module 1, ECG module 1, and ECG module 2, respectively, and their versions are 1.1, 1.2,.
0, and are stored in the directories indicated in the storage location field 36, respectively. The ECG module 1 (version 1.1) and the ECG module 2 (version 1.0) require a restart of the OS to install the driver.

FIG. 4 is a terminal software management table listing patient terminals that need to be updated in each patient terminal connected to the center server 2. When a new module is registered in the system,
A terminal requiring replacement of the module (in this case, a patient terminal equipped with an electrocardiograph operating with a specific version of an electrocardiograph driver) is searched, and necessary information is registered in this table. The terminal software management table 40 includes a terminal number field 41 for specifying a patient terminal, a current module field 42 indicating a module name currently held by the terminal, a current version field 43 indicating the version of the module, and a module name to be replaced. , A new version field 45 indicating the version of the module, and a set date field 46 indicating the date of registration. In the figure, two patient terminals that need to be replaced with an electrocardiograph driver module ECGmodule2 are registered,
1, the current module is ECGmodule1 (version 1.1), and the terminal 002 is the ECGmodule1 (version 1.1).
1 (version 1.2).

FIG. 5 is a diagram showing a procedure for updating the software module of the patient terminal in the system shown in FIG. The patient terminal normally operates offline (in a state where communication is disconnected from the center server), and connects to the center server at an appropriate interval, for example, every morning.
The data measured by the patient is transmitted to the center server 2 while the patient terminal is offline. The download of the software module is performed at the time of connection between the center server and the patient terminal together with transmission of the patient's biometric data.

The procedure for connecting to the center server will be described below with reference to FIG.

(1) When the power of the patient terminal 1 is turned on, an application program is started and connection to the center server 2 is started. When the communication line with the center server is established, the patient terminal 1 makes a connection request to the server.

(2) The center server 2 specifies the terminal number of the patient terminal 1 from the connection request message from the patient terminal and makes an authentication request.

(3) The patient terminal 1 responds to the authentication request.

(4) The center server 2 analyzes the response from the patient terminal, performs authentication processing of the patient terminal, and permits the connection if the authentication result is valid.

(5) The patient terminal 1 logs on to the center server via the communication line, and transfers the measurement data 10 recorded in the patient terminal 1. The center server 2 records these data in the database 15.

(6) From the terminal software management table 40 and the terminal number of the patient terminal, the center server 2 determines whether or not this patient terminal has a software module to be updated. Assuming that the patient terminal number is 001, ECG module 1 (version 1.1)
It is registered in the management table 40 that ECG module 2 (version 1.0) needs to be upgraded. The center server 2 notifies the patient terminal 1 that the software module is to be downloaded. The patient terminal 1 performs preprocessing for upgrading the software module.

(7) The center server 2 reads this module from the storage location of ECG module 2 (version 1.0) with reference to the software configuration table 30, and subsequently transmits this module to the patient terminal 1. The patient terminal 1 receives this and replaces the software module.

(8) The center server 2 refers to the software configuration table 30 and detects that replacement of the ECG module 2 (version 1.0) requires restarting of the OS of the patient terminal 1. Sends a restart request to. The patient terminal 1 receives this, and restarts the OS to activate the replaced module.

(9) Prior to restart, the patient terminal 1 disconnects the communication line with the center server.

(10) After the OS is restarted, the updated software module is incorporated into the system software at the patient terminal 1. Thereafter, the patient can perform a normal operation using the patient terminal.

As described above, according to the present embodiment,
The center server 2 uses the terminal software management table 4
Since the software configuration of each patient terminal is managed by 0, when it is desired to update any module throughout the system, it is possible to specify the patient terminal that needs to be updated without accessing the patient terminal. it can. Therefore, when the management terminal 1 connects to the center server 2, the center server 2 can update a specific software module of an arbitrary patient terminal to a desired software module. Usually, in order to change the software configuration of the patient terminal, it is necessary for a technician to directly operate the patient terminal to replace the software module, but according to the present embodiment, a communication line is used instead. Can be used to automatically replace modules. With this function, a problematic module can be updated to a normal module, a sensor connected to the patient terminal 1 or a driver for controlling the sensor can be remotely replaced, and software management and maintenance of the terminal can be performed. Significant labor savings.

Embodiment 2 Next, Embodiment 2 of the home medical care system of the present invention will be described. It is basically the same as the home medical system in the first embodiment, and only different points will be described. In the first embodiment, the version of the software module of the patient terminal 1 is managed by the terminal software management table 40 in the center server in order to determine the module to be downloaded. The terminal has a terminal software configuration table 50 shown in FIG. 6, sends this table to the center server 2, and compares the content with the content of the software configuration table 30 at the center server to provide the patient terminal 1 with the information. Decide which module to download.

The terminal software configuration table 50 includes a group name field 51 indicating a category of a software module, a module name field 52, a module version field 53, a registration date field 54 of the version, and a storage location indicating a storage location of the module. It is composed of a field 55. In the figure, an electrocardiograph driver and a thermometer driver connected to the sensor interface 8 are registered. These module names are ECG module 1 and TEMP module 1, respectively. The versions are 1.1 and 1.2, respectively, and are stored in the directories indicated in the storage location field 55, respectively.

FIG. 7 is a diagram showing a procedure for updating the software module of the patient terminal in the second embodiment. (1) to (5) are the same as those in the first embodiment shown in FIG. It is. The procedure (6) and subsequent steps will be described with reference to FIG.

(6) When a software module to be upgraded is newly registered in the software configuration table 30, the center server 2 informs the patient terminal 1 to download the software module. Notice. In this case, a new version of the ECG driver; ECG module 2 (version 1.0) is newly registered, and each patient terminal needs to be upgraded to this version. The patient terminal 1 performs preprocessing for upgrading the software module.

(7) The patient terminal 1 sends the terminal software configuration table 50 to the center server 2. The center server 2 compares the terminal software configuration table 50 with the software configuration table 30, and
Determine the software module to download.

(8) The center server 2 refers to the software configuration table 30, reads out this module from the storage location of ECG module 2 (version 1.0), and subsequently transmits this module to the patient terminal 1. The patient terminal 1 receives this and replaces the software module.

(9) The center server 2 refers to the software configuration table 30 and detects that the replacement of the ECG module 2 (version 1.0) requires the restart of the OS of the patient terminal 1. Sends a restart request to. The patient terminal 1 receives this, and restarts the OS to activate the replaced module.

(10) Prior to restart, the patient terminal 1 disconnects the communication line with the center server.

(11) After the OS is restarted, the updated software module is incorporated into the system software at the patient terminal 1. Thereafter, the patient can perform a normal operation using the patient terminal.

As described above, according to the present embodiment,
The center server 2 manages the version of the software module executed on the patient terminal by the software configuration table 30, and each patient terminal manages the version of the software module of the terminal itself by the terminal software configuration table 50. By comparing these in the server, the module that needs to be updated can be specified, and only that module can be downloaded and replaced. The comparison of the versions is performed on the server side by the patient terminal transmitting the terminal software configuration table 50 to the server when the center server 2 and the patient terminal 1 are connected. Therefore, the center server 2 does not need to manage the software configuration of each terminal. According to the present embodiment, as in the first embodiment, a technician can automatically replace a module using a communication line without directly operating a patient terminal to replace a software module. It is possible to update a problematic module to a normal module or to remotely replace a sensor connected to the patient terminal 1 or a driver for controlling the sensor, thereby reducing the software management and maintenance of the terminal. Significant labor savings.

In this embodiment, the comparison of the software module versions is performed on the center server side, but it is also possible to perform the comparison on the patient terminal side. In this case, instead of transferring the configuration table from the terminal to the server in step (7), the latest version information of each module is transferred from the server to the terminal, and the module that needs updating is notified from the terminal to the server. Is done. Also in this case, the center server 2 does not need to unify the version management of the module of each patient terminal, and can obtain substantially the same effect as that of the present embodiment.

Embodiment 3 Next, Embodiment 3 of the home medical care system of the present invention will be described. It is basically the same as the home medical system in the first embodiment, and only different points will be described. In the first embodiment, the software module of the patient terminal is
The software is managed on a module basis by the software configuration table 30 and the terminal software management table 40, and it is determined whether each module can be downloaded. On the other hand, in the present embodiment, the software module of the patient terminal uses the terminal server configuration table 60 shown in FIG. 8 in the center server 2 to show the device configuration information of the patient terminal 1, specifically, the configuration of the device provided by the patient terminal. Managed by
If software replacement is required due to a software module update or a change in the sensor configuration of the patient terminal, the predetermined contents of this table are changed and downloaded to the patient terminal 1 based on this device information. Decide which module to do.

The terminal configuration table 60 includes a terminal number field 61 for identifying each terminal, a configuration change date field 62 of the terminal, and a plurality of device name fields 63. In the figure, as devices that can be connected to the sensor interface 8, a thermometer, a sphygmomanometer, an electrocardiograph, a weight scale,
Blood glucose meters, blood oximeters, etc. are registered.
The terminal VSB001 is provided with a thermometer, a sphygmomanometer, an electrocardiograph, and a blood glucose meter, and the terminal VSB002 is provided with a thermometer, a sphygmomanometer, a weight scale, a blood glucose meter, a blood oximeter, and the like. The numerical value entered in the device name field in FIG. 8 indicates the status of software for the sensor installed in each terminal, 0 indicates that the sensor is not equipped,
1 indicates that the sensor is equipped and the software module does not need to be updated, and 2 indicates that the sensor is equipped and the software module needs to be updated. When a software module related to a specific sensor is updated, the corresponding device name field 63 is rewritten from 1 to 2, and from 2 to 1 when the download is completed.

FIG. 9 shows the structure of a module management table for managing software modules of each device corresponding to the device name field 63 in FIG. 8, and is stored in the center server similarly to the terminal configuration table 60. I have. The module management table 70 includes a device name field 71 indicating a type of device connected to the patient terminal, a module name field 72, a module version field 73, a registration date field 74 of the version, and a storage location field indicating a storage location of the module. 75. In the figure, the driver of the thermometer connected to the sensor interface 8 is a TEM
This indicates that the Pmodule1 is version 1.1 and is stored in the directory indicated in the storage location field 75, for example.

The means for updating the software of the patient terminal is basically the same as the procedure in the first embodiment shown in FIG. In the first embodiment, whether or not a software module can be downloaded to a specific patient terminal is determined by the terminal software management table 40, the version of software indicated in the software configuration table 30 is read, and transmitted to the patient terminal. However, in the present embodiment, whether the software module can be downloaded to a specific patient terminal is determined based on the terminal configuration table 60, and the version of the software indicated in the module management table 70 is read to read the patient terminal. Send to

When changing the sensor configuration of a specific patient terminal, the value of the field in the terminal configuration table 60 is changed. For example, the patient terminal VSB001 in FIG.
Although a thermometer, a sphygmomanometer, an ECG, and a blood glucose meter are provided as biological sensors, if a new blood oximeter is to be provided and the blood glucose meter is to be removed, the terminal configuration table is edited as shown in FIG. . In this state, when the patient terminal VSB001 is connected to the center server 2, the measurement module of the sphygmomanometer is upgraded, and at the same time, the measurement module of the blood oximeter is introduced into the patient terminal VSB001. As a result, in the patient terminal VSB001, after connection with the server, measurement with the blood glucose meter is disabled, the blood oximeter can be used, and the measurement module of the sphygmomanometer is updated. After connection with the server, the items of the sphygmomanometer and SpO2 meter in the row of the patient terminal VSB001 in the terminal configuration table 80 in FIG. Similarly, when the patient terminal VSB002 is connected to the center server 2, the measurement modules of the sphygmomanometer and the blood glucose meter are downloaded to the patient terminal. In VSB002, the configuration of the biological sensor does not change. Similarly to the VSB001, after connection with the server, the items of the blood pressure monitor and the blood glucose meter in the row of the patient terminal VSB002 in the terminal configuration table 80 in FIG. 10 are rewritten from 2 (version required) to 1 (version required). Can be

As described above, according to the present embodiment,
The center server 2 manages software modules executed on the patient terminal at a device level, and updates the software of each patient terminal on a device basis.
Management is easier and more intuitive than in the case of managing software in units of modules. Also, the center server 2 does not need to manage the software configuration of each terminal, and the technician automatically replaces the module using the communication line without directly operating the patient terminal to replace the software module. Can be performed, a problematic module can be updated to a normal module, a sensor connected to the patient terminal 1 or a driver for controlling the sensor can be remotely replaced, and software management of the terminal can be performed. The advantage that the labor and maintenance are greatly reduced is exhibited similarly to the first embodiment.

Further, according to the present embodiment, the replacement of the device (biological sensor) of the patient terminal can be easily performed.
For example, VSB0 in the terminal configuration table 60 in FIG.
When a new weight scale is added in the configuration of 01, the field of the weight scale is rewritten from 0 to 2. By this rewriting, the software module related to the scale is downloaded the next time the terminal VSB001 is connected to the center server, and the patient terminal can be equipped with the scale. In the terminal configuration table 60, an update flag field is added in addition to the configuration change date field, a flag is set when the configuration is changed, the flag is reset when the download to the patient terminal is executed, and the device field 63 is rewritten to 0 to change the center. If the server is configured to instruct the patient terminal to delete the module, the device can be replaced, the sensor configuration of the patient terminal can be remotely performed, and terminal management can be reduced. You.

In the present embodiment, the configuration of the device of the patient terminal is performed by the terminal configuration table 60 of the center server 2, but it is also possible to perform the configuration on the patient terminal side as in the second embodiment. In this case, in the version upgrade procedure, the terminal configuration table of the terminal itself is transferred from the patient terminal to the server. Alternatively, the latest version information of each device may be transferred from the server to the terminal, and the device that needs updating may be notified from the terminal to the server. In this case, the center server 2 does not need to unify the management of the devices of the individual patient terminals, and the terminal management in the center server is reduced.

The center server and the patient terminal have the same configuration as a computer or the like, and the CPU compares the history information of the modules stored in each terminal with the update information of the modules held by the server.

[0074]

As described above, in the telemedicine system of the present invention, the server manages all the software modules executed on the patient terminal and compares them with the modules executed on each patient terminal. Thus, the server can remotely update the module of the patient terminal without directly operating the patient terminal.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of a remote medical system according to a first embodiment of the present invention.

FIG. 2 is a configuration diagram showing a software configuration of a patient terminal in the telemedicine system of FIG. 1;

FIG. 3 is an explanatory diagram showing the structure of a software configuration table stored by a center server in FIG. 1;

FIG. 4 is an explanatory diagram showing a structure of a terminal software management table stored in a center server in FIG. 1;

FIG. 5 is a flowchart illustrating a software version upgrade procedure between the center server and the patient terminal according to the first embodiment of the present invention.

FIG. 6 is an explanatory diagram showing the structure of a terminal software configuration table stored in a center server in a second embodiment of the present invention.

FIG. 7 is a flowchart showing a software version upgrade procedure between a center server and a patient terminal according to the second embodiment of the present invention.

FIG. 8 is an explanatory diagram showing a structure of a terminal configuration table stored in a center server in a third embodiment of the present invention.

FIG. 9 is an explanatory diagram showing the structure of a software module management table stored in a center server in a third embodiment of the present invention.

FIG. 10 is an explanatory diagram showing a structure of a terminal configuration table stored in a center server in a third embodiment of the present invention.

[Explanation of symbols]

 Reference Signs List 1 patient terminal 2 center server (server) 3 patient side communication device 4 center side communication device 5 communication line 6 user IF device 7, 14 storage device 8 sensor interface 9 terminal information storage region 10 measurement data storage region 15 patient database storage region 16 System information storage area 20 Operating system 21 Device driver 22 Database 23 Application program 24 Device user interface 30 Software configuration table 40 Terminal software management table 50 Terminal software configuration table 60 Terminal configuration table 70 Software module management table

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 12/00 545 G06F 9/06 610Q 640A 650B 610L

Claims (11)

[Claims] 1. A plurality of patient terminals which are provided with biological information collecting means and store and execute software constituted by a plurality of modules, and store and manage data collected, referenced and edited by these patient terminals. And a server for storing and managing software executed on each patient terminal in a module unit, and connecting to the patient terminal when connecting to the patient terminal. Wherein the module is selectively downloaded from the server to the patient terminal so that a predetermined module is executed in the patient terminal. . 2. The server holds history information of a module stored in each patient terminal and update information of a module held by the server, and determines a module to be transferred to the patient terminal by comparing these. do it,
2. The telemedicine system according to claim 1, wherein the module is downloaded when connected to the patient terminal. 3. Each patient terminal holds history information of its own module, the server holds update information of its own module, and when the patient terminal and the server are connected, the terminal stores the update information of the module. 2. The remote medical system according to claim 1, wherein history information is sent to a server, and the server compares the history information with the update information to determine and download a module to be transferred to the patient terminal. . 4. Each patient terminal holds history information of its own module, the server holds update information of its own module, and when the patient terminal is connected to the server, the server stores the update information of the module. The update information is sent to the patient terminal, the patient terminal determines a module to be transferred to the patient terminal by comparing the information, notifies the server, and the server notifies the patient terminal of the module. 2. The telemedicine system according to claim 1, wherein the remote medical system is downloaded. 5. The telemedicine system according to claim 2, wherein both the module history information and the module update information are software version information. 6. The module according to claim 2, wherein one or both of the module history information and the module update information is module configuration information generated from the system configuration information of the patient terminal. Telemedicine system. 7. The server and the patient terminal further have a message transmission / reception function, and when the server and the patient terminal are connected, transmission / reception of this message and selective download of a software module are continuously performed in the same communication procedure. The telemedicine system according to claim 1, wherein: 8. A part of the module is configured corresponding to each of a plurality of biological information collecting means connected to the patient terminal, and when the biological information collecting means connected to the patient terminal is replaced, the module is connected to the server. 2. The remote medical system according to claim 1, wherein a connection between the replaced biological information collecting means and the patient terminal is established by downloading the module. 9. The server accumulates, manages and downloads some or all of the modules in a group corresponding to each of a plurality of functions expressed in the patient terminal,
2. The remote medical system according to claim 1, wherein the replacement of the corresponding function of the patient terminal is performed by downloading the module group. 10. The server stores restart command information corresponding to at least some software modules.
2. The system according to claim 1, wherein the restart instruction is transmitted when the module is downloaded and the module is downloaded, and the patient terminal restarts after the module has been downloaded.
The telemedicine system as described. 11. A program for causing a computer to function as all or a part of the telemedicine system according to claim 1.