JP2017102981A - Registration method in health care system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a registration method in a system applicable over a wide range about health and capable of registering self physical conditions easily and quickly by a subject and the like.SOLUTION: A health care system includes: a region (E2) in which medical care and treatment workers and the like (31 and 41) exist; and a region (data center 100) in which data (physical information and the like) on the physical information and the like of a subject (1) and the like is stored. Further, the health care system includes: means (PC, Hh, and Ht) having a function for causing the medical care and treatment workers and the like (31 and 41) to acquire the data on the physical information and the like of the subject (1) and the like which is transmitted to the storing region (100) in the region (E2) in which the medical care and treatment works and the like (31 and 41) exist; and means having a function for outputting the data on the physical information and the like of the subject (1) and the like which is transmitted to the storing region (100) by the medical care and treatment works and the like(31 and 41).SELECTED DRAWING: Figure 1

Description

  The present invention relates to health care, and a user who is a subject can easily notify, report, transmit, and transmit his / her physical condition information and the like via the Internet, etc. The present invention relates to a registration method in a system that can always share the status information with a user.

2. Description of the Related Art Conventionally, for example, in medical practice, information (physical condition information: so-called “situation” including symptoms, conditions, conditions, etc. occurring in the body of a patient suffering from injury or illness (hereinafter referred to as “subject”). Medical data (including “receipt data”), which is particularly necessary for medical care, treatment, or health management of the person himself / herself (hereinafter referred to as “therapeutic medical personnel”). ")" Is collected only by directly diagnosing and interrogating the subject.

For example, after a series of ongoing treatments are completed, the subject is no longer under the direct control of the therapeutic medical personnel. After the subject is removed from the direct management of the medical staff, the medical staff can know the condition of the subject only at regular and irregular direct interviews.
If necessary, subjects will be in the period after the completion of a series of continuous treatments until the next direct diagnosis / interview by the medical staff (the period outside the direct control of the medical staff) The physical condition information is written and recorded by the subject himself or the caregiver.
However, it is difficult to continuously collect physical condition information of subjects who are out of direct control of the medical staff (for example, subjects who have been discharged).

Recently, with the use of information technology (IT technology), in the state where the subject is out of direct control of the treatment medical personnel, the subject notifies the medical treatment health status information via the Internet or the like, Systems have been developed that can report, communicate and transmit.
There are also cases where a service using such a system is in a test operation or an actual operation.

Here, health-related devices (for example, thermometers, sphygmomanometers, etc.) that can easily measure and record the physical condition while the subject is living normally measure only a single physical condition information. , Can not record. For example, a sphygmomanometer can only measure and record the blood pressure of a subject.
Therefore, if there are multiple types of physical condition information to be grasped by the medical staff, in order for the subject to measure and record all the physical condition information, he / she purchases multiple health-related devices, It is required to measure and record using the.
However, when a subject measures and records his / her physical condition information using a plurality of health-related devices, it is difficult to store and manage the measured physical condition information or its data in an integrated manner.

In addition, when a subject has been treated for injuries or illnesses at multiple medical institutions, the subject's physical condition information and data related to treatment / treatment are recorded for each medical institution and stored under the responsibility of each medical institution. ing.
The subject's physical condition information and data on treatment / treatment are very important data for the subject, and are also extremely effective data for the medical staff.
However, physical condition information and data on treatment / treatment are generated and scattered in each of a plurality of medical institutions. And since the physical condition information and the data related to treatment / treatment are recorded in a different format for each medical institution, a certain medical institution has the physical condition information of a subject existing in another medical institution for the same subject, Conventionally, it has been very difficult to effectively use data on treatment / treatment (physical condition information, data on treatment / treatment).

After performing direct diagnosis and interview (for example, diagnosis and interview conducted by direct interview between the subject and the treatment medical personnel) by the medical treatment personnel in a state where the subject is out of direct control of the treatment medical personnel, It may be required to record the physical condition information of the subject during the period until the next direct medical diagnosis / inquiry by the medical staff.
However, the recording of such physical condition information is performed by a one-way request from the medical treatment person to the subject, and is executed based on the subject's sense of duty. Such a record based on the subject's sense of duty is likely to be unexecuted as the subject's sense of duty fades.
In addition, when the physical condition information is recorded by the subject by writing on a paper medium, it is complicated to store and utilize (operate) the physical condition information recorded on the paper medium. There is a risk of becoming.
Furthermore, during direct diagnosis and interviews by persons involved in treatment and medical care, physical condition information is transmitted by the memory of the subject, etc., so that the condition information transmitted to treatment and medical personnel is likely to be ambiguous. There is a risk that body condition information will be transmitted due to arbitrary distortion.

In addition to this, the conventional IT service that is operated for collecting the physical condition information of the subject restricts the types of use information terminals of the subject, and may force the use of a dedicated terminal. Since the dedicated terminal is used, in the conventional IT service, only specific physical condition information (for example, heart rate) is collected and functions and services limited in relation to the specific physical condition information (for example, heart rate) are collected. It is only provided. In other words, in the conventional IT service, the information terminal and the target of the service are limited to a specific disease for the subject.
In addition, there are many conventional IT services that require a user, who is a subject, to learn and master device operations to a considerably high level.

  As another conventional technique, for example, a system has been proposed in which the blood pressure of a subject is transmitted to a health management support providing server to give an appropriate instruction to a patient with hypertension and call attention (see Patent Document 1). ).

  However, such a system is limited to blood pressure, and there is a problem that it is limited to a specific disease called hypertension.

JP 2011-180857 A

  The present invention has been proposed in view of the above-described problems of the prior art, and can provide various services over a wide range of health. The purpose is to provide a system that can register the situation.

The health management system used in the present invention includes a mobile phone device and an information-related device such as a computer connected to an open information transmission network such as the Internet, and a computer connected to a closed information transmission network such as an IP-VPN network. This is an IT system for collecting information on the physical condition of subjects, etc. and effectively utilizing them in cooperation with a server arranged in an area corresponding to the boundary of the information-related equipment.
The registration method in the health management system (500) of the present invention includes:
Area where medical / health manager (31) and system operation manager (41) exist (E2: area 2) and area for storing physical condition information such as subject (1) (physical condition information, etc.) (Data center 100)
The area (E2) where the medical / health manager (31) and the system operation manager (41) are present as data such as physical condition information of the subject (1) transmitted to the area to be stored (data center 100) ) Means (computer PC) having a function of causing the participants (31, 41) to acquire (use and use the medical care related persons 31, 41).
Means (17) having a function of outputting data such as physical condition information of the subject etc. transmitted to the storage area (data center 100) by the medical / health manager (31) and the system operation manager (41) When,
The medical / health manager (31) acquires the data such as the physical condition information of the subject transmitted to the storage area (data center 100), and the subject falls into an abnormal situation in which the subject does not answer continuously. An inquiry response status confirmation unit (19) having a function (Se7) for displaying an inquiry response status of the subject or the like necessary to determine whether or not (Se8);
Means (16, 17) having a function of providing data such as physical condition information of the subject (1) transmitted to the storage area (data center 100) to the subject,
The medical / health manager (31) and the system operation manager (41) have means (21) having a function of registering the authority, and the means (21) grants access authority to which access authority setting information is given. The block (213), the authority setting block (6) to which the authority data is sent and the access authority is sent from the access authority granting block (213), and the authority for creating the master are given from the authority setting block (6) and the master data If the accessing person is a medical / health manager (31) and a system administrator (41), authority is set (Si28, Si35), and the master data is output. In the participant registration method in the health management system (500) having the function of storing (Si30, Si37),
Whether to approve the login ID and password (Si2) of the medical / health manager (31), system administrator (41), or subject (1) who accessed the storage area (data center 100) (Si3), and if it approves (login ID and password) (Si3 is YES), a menu screen is displayed (Si4), a medical / health manager (31), a system operation manager (41 ) Or initial setting of subjects (1) (Si5), select the system participant registration menu (Si6),
It is determined whether or not the data of the medical / health manager (31), the system operation manager (41), the subject, etc. (1) accessed by the system participant registration unit (21) also exists in other systems ( Si7), medical / health manager (31), system operation manager (41) or subject etc. (1) data also exists in other systems (Si7 is YES) Data of health manager (31), system operation manager (41) or subject etc. 1 is retrieved (Si8), and the medical / health manager (31), system operation manager (41) or subject etc. who logged in the data 1 is displayed on the screen of the information device (Si9), converted into a CSV file (Si10), and the CSV file of the data is imported into the health management system (500) (Si 1),
If data of the accessed medical / health manager (31), system operation manager (41) or subject (1) does not exist in other systems (Si7 is NO), the medical / health manager (31) The system administrator (41) or the subject (1) data is inputted (Si12), the code master data is given (Si13), the individual medical / health administrator (31), the system administrator (41) ) Or a specific number for the subject (1) (Si14), and the logged-in medical / health manager (31), the system operation manager (41) or the subject (1) acquires the participant data ( Si15),
It is determined whether the person who acquired the participant data is the subject (1) (Si16),
If it is a test subject (Si6 is YES), initial setting of the test subject is performed (Si17), the test subject is selected (Si18), and the test subject and the therapeutic medical staff (31) are set with a string (link one-to-one: link) : Si19), an interview set is assigned to the subject from the interview set master (Si20), subject master data is given (Si21), and the subject master data is stored in the health management system (500) (Si22),
It is determined whether or not to set another subject (Si23), and if no other subject is set (Si23 is NO), the subject initial setting is terminated (Si24),
If the person who has acquired the participant data is not a subject (Si6 is NO), the system participant registration unit (21) determines whether the person who has acquired the participant data is a medical / health manager (31). Judgment (Si25)
If the person who acquired the participant data is a medical / health manager (31) (YES in Si25), the medical / health manager (31) is initialized (Si26), and the medical / health manager (31) (Si27) and set the authority to the medical / health manager (31) from the means (21) having the function of registering the authority with the medical / health manager (31) and the system operation manager (41). (Si28), subject administrator master data is given (Si29), medical / health manager master data is stored in the health management system (500) (Si30),
It is determined whether or not another medical / health manager (31) is set (Si31), and if no other medical / health manager (31) is set (Si31 is NO), the medical / health manager ( 31) The initial setting is finished (Si32)
If the person who acquired the participant data is not the medical / health manager (31) (Si25 is NO), the system administrator (41) is initialized (Si33), and the system administrator (41) is selected. (Si34), the authority is set to the system administrator (41) from the means (21) having the function of registering the authority of the medical / health administrator (31) and the system administrator (41) (Si35) , Giving the master data to the system administrator (41) (Si36), storing the system administrator master data in the health management system (500) (Si37),
It is determined whether or not to set another system operation manager (41) (Si38). If no other system operation manager (41) is set (Si38 is NO), the system operation manager (41) is determined. The initial setting of is finished.

In the present invention, the health management system (500) has a region (E1) where the subject (1) and the like exist,
In the first area (E1), data (physical condition information, etc.) of the patient's (physical condition), etc. (physical condition information, etc.) generated by the subject (1), etc. (physical condition information, etc.) It is preferable to have means (cell phone Hh, other information terminal Ht) having a function of transmitting (notifying, reporting, transmitting) to an area (data center 100) for storing information or the like.

Here, the subject (1) and the like are not limited to patients suffering from injuries and diseases, but are words that broadly include all users who wish to use physical condition information for their own health management. is there. For example, the wording is intended to encompass sports enthusiasts and athletes.
Treatment medical personnel (31, 41) are not only medical personnel such as doctors and nurses, but also humans involved in various treatments, inspectors performing various medical and health tests, and sports enthusiasts. It also includes health consultants who send various advice, athletes' coaches and coaches. In this specification, it may be expressed as “subject manager”.

In the implementation of the present invention, the second area (E2) is configured by an IP-VPN (250) or a more secure communication network and dedicated terminal devices (32, 42) connectable thereto. It is preferable.
In the third area, the data center (100) is preferably arranged at the boundary between the first area (E1) and the second area 2 (E2).
The third area (data center 100) includes a server that stores application software that enables the operation of the health management system according to the present invention, a server that accumulates body condition information such as collected subjects, and a backup. It is preferable that a server group such as a server for storing a file and a communication device having a function of enabling communication with the first area (E1) and the second area (E2) are installed.

In the second area (E2), it is preferable that the medical treatment personnel and the like (31, 41) have a function of browsing and acquiring physical condition information and the like of the subject subject (1) to which access permission is set in advance.
In addition to this, in order to ensure the safe operation of the system, the means (information terminals Hh, Ht) in the first area (E1) and the means (information terminal PC) in the second area (E2) It is preferable to have a function to prevent direct communication.
In implementing the present invention, when Internet communication (200) is used, the security of communication is ensured by using SSL or the like, and a function of enabling personal authentication by using an electronic signature and authentication technology is provided. Preferably it is.

  In carrying out the present invention, the first area (E1) is composed of a public communication network such as the Internet (200) and a terminal device (PC) connectable to the communication network. When it is outside the direct management of the treatment / medical personnel (31, 41) (when the subject 1 or the like has not directly interviewed or diagnosed the treatment / medical personnel 31, 41, etc.) (31, 41) With the ability to continuously collect physical condition information etc. from the subject (1), etc., without direct interviews, and send it to the medical treatment related persons (31, 41) It is preferable.

Further, in the present invention, an inquiry about a questionnaire system for reporting a physical condition adapted to the subject (1), etc. is made to the subject (1) in the first region (E1) only to the subject. It is preferable to have a function that is always provided through a website.
Here, the inquiry of the questionnaire system for reporting the physical condition according to the subject (1) etc. is described as “inquiry” in this specification, so that each subject etc. matches the subject etc. A combination of multiple interviews is provided. A combination of such a plurality of interviews is described as an “inquiry set” in this specification. In other words, the interview set is configured by combining individual interviews.
It is preferable that the subject (1) or the like to whom the interview or the interview set is provided is only the subject or the like who is permitted to connect to the IT system or the like that operates this service and is registered to that effect.

  In the present invention, means (cell phone Hh, other information terminal Ht) having a function of generating physical condition information etc. of the subject (1) etc. (simple) and analysis of the generated physical condition information of the subject etc. It is preferable to provide means having a function of performing (comparison, examination, verification, statistical analysis, etc.).

In the health management system (500) of the present invention, a message created by a system participant (MR: subject 1 or the like, a system administrator 31 or 41 such as a medical treatment related person) is sent to another system participant (MR or MR2). Means (11, Hh, Ht: information terminal such as a mobile phone) having a function of transmitting (notifying, transmitting) to
A means (18) having a function of responding (replying) a message created by the other system participant (MR) to the sender (the system participant MR who first created and transmitted the message) in response to the message; It is preferable.

In the present invention, physical condition information etc. of the subject (1) etc. and information (annotations, findings etc.) obtained from the said (data such as physical condition information of the subject 1 etc.) Means (21) having a function of registering;
Information on the physical condition of the subject, etc., and information existing outside the system (according to the present invention) (physical condition information, treatment, medication information, etc. of the subject etc. that has been made into an electronic file, electronic image or electronic document, Other means (12, 15, etc.) having a function of registering and storing information (annotations, findings, etc.) obtained from the information (information existing outside the system) and the like (items described in medical charts, etc.) 20)
Means (14, 17) having a function of outputting physical condition information etc. of the saved subjects (input, registration), etc., and information (annotations, findings, etc.) obtained therefrom;
Provided with means (13, 16) having a function of browsing the physical condition information of the saved subject (such as the subject and the medical staff), and information (annotations, findings, etc.) obtained therefrom. It is preferable.

In the present invention, the interview provided to the subject (1) or the like is not created only for the specified (limited) subject or the like (content limited to the limited purpose or only the content) It is preferable that the contents have versatility.
And it is preferable that there is no restriction | limiting and regulation about the content, category, number, etc. of the interview provided to a test subject (1).
Here, the inquiry is preferably created by a person concerned with medical treatment or the like (31: for example, a person who is suitable for making an inquiry about health like a doctor). And it is preferable that it is the content which does not become a body of a test subject's body and a mental burden in consideration of the reply situation of the test subject (1) and the environment.

The interview set is preferably created by combining individual interviews according to the subject (1) or the like (including a group including other subjects or the like regarded as the same).
The combination of individual interviews that make up the interview set is free and unlimited. The combination of the individual interviews constituting the interview set can be freely created, added, and changed by the medical staff (31) etc. regarding the types and number of interviews provided to the subject. Is preferred.

It is preferable that consideration is given to answering individual questions as easily as possible and to eliminate erroneous answers. For example, it is preferable to employ “Yes (YES), No (NO)” formulas, correct / wrong formulas, numerical input formulas, selection formulas (including multiple-choice selection formulas) for selecting answers from choices, and the like. Further, a method of selecting a divided image as an answer from an image constituted by a plurality of divided images may be used.
It is preferable that a threshold value can be set for the numerical input type inquiry, and answers that deviate from the threshold value can be excluded.

In the present invention, it is preferable to provide a function capable of recording the number of answers each time the subject (1) or the like answers an inquiry.
And it is preferable that a treatment medical staff etc. (31) or the provider (41) of this service provides a privilege to a test subject according to the cumulative number of times that the test subject (1) or the like answers an inquiry.
One of the factors hindering the subject (1) and the like from recording physical condition information and the like is that it becomes obligatory to record and execute the answer to the interview. By providing such a privilege as described above, it is possible to reduce the sense of duty and promote the answer to the inquiry.

  According to the present invention having the above-described configuration, the subject (1) or the like is directly managed by the medical treatment person (31) or the like when the subject (1) or the like answers the interview or the interview set. Even if it is not in a state, if it is in an environment that can be connected to a communication network such as the Internet (200), its own physical condition information etc. is notified, reported, transmitted, transmitted, etc. to the subject managers (1, 31, 41) can do.

The subject (1) or the like uses a dedicated connection terminal or a special service when using various services using IT that can be provided by the present invention (which may be described as “this service” in this specification). Does not require a connection terminal.
This service can be used if it has an inexpensive and general commercial connection terminal. As the connection terminal, a connection terminal that is easily available and has versatility, for example, a mobile phone (Hh), a portable information terminal device (Ht), and a personal computer (PC) can be used.
In addition, there is no restriction that dedicated or special operating software (OS), browsers, and Internet service providers of the terminal devices used must be used in the present invention. Therefore, the subject (1) or the like has a disadvantage that the service cannot be enjoyed by the operating software (OS), browser, or Internet service provider of the terminal device used by the subject (1) or the like when using the service. Not receive.

According to the present invention, the subject (1) and the like can easily transmit body condition information and the like via various information networks such as the Internet (200).
The medical care person (31) and the like can share the information (physical condition information and the like transmitted by the subject 1) with the subject (1) and the like, and if necessary, through the system according to the present invention. Thus, the subject (1) and the like and the medical treatment related person (31) and the like can communicate with each other.
Furthermore, since the interactive correspondence function is provided to the subject (1) or the like through the system (500) according to the present invention, the subject (1) or the like has the same problem (for example, the same disease). It is possible to keep in touch between those who work on.
As a result, it is possible to reduce the loneliness of the subject (1) and the like. In addition, when persons (subjects, etc.) who work on the same problem (for example, the same disease) communicate with each other, the sense of duty, which is a factor that hinders the execution of recording of physical condition information and the like, is reduced.

According to the present invention, physical condition information, diagnosis, and the like of the subject (1) and the like can be digitized and databased from generation to recording and storage. Then, it is easily executed to search the database for physical condition information and use the physical condition information.
By digitizing, the possibility of deterioration and damage is much lower than when the physical condition information and diagnostic data of the subject (1) and the like are recorded and stored on a paper medium or the like.
In addition, regarding the information obtained from a commercially available health-related device having a function of measuring and recording the health state, the subject (1) etc. can answer the interview / interview set by The system (500) according to the present invention can be centrally stored and managed.

In addition, according to the present invention, the medical treatment related person (31) about the medical treatment, the content of the treatment, the medical chart or the attached image, and the prescription issued and created for each medical facility or treatment facility, medical institution, etc. ) And the like are registered and stored in the system according to the present invention, so that unified management of data on body condition information, health status, treatment, and medication related to the subject (1) and the like becomes possible.
In the prior art, physical condition information and treatment / treatment data are scattered in each of a plurality of medical institutions and are recorded in a different format for each medical institution. It was very difficult to effectively use the physical condition information and treatment / treatment data (subject information, treatment / treatment data) of subjects present in other medical institutions. On the other hand, according to the present invention, since it is possible to centrally manage data on physical condition information, health status, treatment, and medication, if it is a medical institution using the present invention, It is possible to make effective use of physical condition information and treatment / treatment data.
And if centralized management of data related to body condition information, health condition, treatment, and medication related to the subject (1) and the like is performed according to the present invention, for example, so-called “contraindications” (for example, combinations of drugs for which side effects are a concern) Administration to the same subject or the like) can be prevented.

The physical condition information collected by direct interviews (diagnosis) between the subject (1) and the like and the medical staff (for example, the doctor 31 in charge) is detailed but intermittent.
According to the present invention, a period (hereinafter referred to as “direct interview (hereinafter referred to as“ direct interview ”)) between the subject (1) and the person concerned with medical treatment (31) and the like after conducting a direct interview (diagnosis). In this case, the subject (1) etc. answers the interview / inquiry set, and the physical condition information of the subject (1) etc. Etc. can be collected continuously.
Then, by verifying the physical condition information etc. of the subject (1) etc. continuously collected by this service, the treatment medical personnel etc. (for example, the doctor 31 in charge) can continuously change the subject (1) etc. It becomes possible to acquire physical condition information, etc., and when a change occurs in the physical condition of the subject (1) or the like, it becomes possible to search for the timing, factors, and the like.

In addition, treatment medical personnel (for example, a doctor in charge) can check the physical condition information etc. of the subject (1), etc. continuously collected by this service, during the period of direct interview (diagnosis) The physical condition information of the subject and the like can be employed as supplementary information during a direct interview (diagnosis).
Then, based on the physical condition information of the subject (1) etc. during the period during which the direct interview (diagnosis) is performed, the medical treatment personnel (eg, the doctor 31 in charge) It is also possible to judge the credibility of physical condition information reported by memory. Alternatively, it is possible to give an opportunity to urge medical care professionals (for example, the doctor 31 in charge) to confirm the credibility of the physical condition information reported from the subject (1) etc. during the direct interview (diagnosis) I can do it.

It is explanatory drawing which shows the outline | summary of embodiment of this invention. 1 is a block diagram illustrating an entire system according to an embodiment. It is a block diagram of the data center in FIG. It is a block diagram of the physical condition registration unit by a test subject. It is a flowchart which shows the procedure of the physical condition registration by a test subject. It is a block diagram of a message transmission / reception unit. It is a flowchart which shows the procedure of message transmission / reception. It is a block diagram of a question answering / diagnosis / diagnosis data browsing unit by a subject. It is a flowchart which shows the procedure of the inquiry answer / diagnosis / diagnosis data browsing by a test subject. It is a block diagram of a question answering / diagnosis / diagnosis data output unit by a subject. It is a flowchart which shows the procedure of the question answer by a test subject, medical examination, and diagnostic data output. It is a block diagram of an inquiry answer status confirmation unit from a subject by a medical / health manager. It is a flowchart which shows the procedure of the inquiry reply condition confirmation from the test subject by a medical / health manager. It is a block diagram of a registration unit of examination / diagnosis data of a subject by a medical / health manager. It is a flowchart which shows the procedure of registration of the medical examination / diagnosis data of a test subject by a medical / health manager. It is a block diagram of an inquiry answer / diagnosis / diagnosis data browsing unit from a subject by a medical / health manager. It is a flowchart which shows the procedure of the inquiry answer from the test subject by a medical / health manager, medical examination, and diagnostic data browsing. It is a block diagram of the output unit of the inquiry answer / diagnosis / diagnosis data from the test subject by the medical / health manager. It is a flowchart which shows the output procedure of the inquiry reply from the test subject, medical examination, and diagnostic data by a medical / health manager. It is a block diagram of a system participant registration unit. It is the first half part of the flowchart which shows the procedure of a system participant registration. It is the latter half part of the flowchart which shows the procedure of a system participant registration. It is a block diagram of an inquiry and inquiry set registration unit. It is a flowchart which shows the procedure of an inquiry and an inquiry set registration.

Embodiments of the present invention will be described below with reference to the accompanying drawings.
First, the overall configuration of the health management system used in the illustrated embodiment will be described with reference to FIGS.
In FIG. 1 and FIG. 2, a patient is illustrated as a subject 1 in a health management system (hereinafter sometimes referred to as “the present system”) denoted by reference numeral 500 as a whole. Further, doctors, researchers, health advisors, and the like are illustrated as treatment / medical staff 31. A system administrator / manager 41 and the like are illustrated as the subject manager.
That is, the illustrated health management system 500 includes the subject 1, the medical / health manager 31, and the system operation manager 41.

In the illustrated health management system 500, a service desk 32 is provided so that services provided to the subject 1 or the medical / health manager 31 can be smoothly operated.
The system operation manager 41 (to be described later) determines and sets all the usage related to the operation of the service provided by the illustrated health management system 500 and the operating authority of this system.
In FIG. 1, the area including the subject 1 and the Internet 200 is expressed as a first area E1, and the area including the treatment / medical staff 31, the system operation manager 41, and the VPN network 250 is referred to as a second area E2. expressing.

The test subject 1 uses a mobile phone device Hh that can be connected to the Internet 200, a tablet-type mobile terminal Ht, an information terminal such as a computer PC, or an information-related device (see FIG. 1). : Access is omitted in FIG. 1 (see FIGS. 4 and 5). Then, log in by entering a preset login ID and password.
The service in the system according to the illustrated embodiment is provided to the subject 1 after the user logs into the website.

Here, a person who is involved in the illustrated health management system 500 or intends to use the service by the illustrated health management system 500 performs user registration in the illustrated health management system 500 in advance. Authorized and usage details must be defined (see FIGS. 20-22).
In other words, even if a person who has not registered as a user (unregistered person) in the illustrated health management system 500 accesses the website of the health management system 500, it cannot log in.

Although not shown in the figure, a system administrator (a person who has been given authority by the system administrator) to a participant who is involved in the system according to the illustrated embodiment and is assumed to use the service. 41) also assigns a participant unique ID to identify the participant 41.
Subject 1 has a unique participant unique ID. For example, even when the subject 1 is transferred to another medical institution, the participant unique ID of the subject 1 is not changed and assigned again. This is for continuous and unified collection and recording of physical condition information.

A medical / health manager 31 is linked and registered for the subject 1 (see FIGS. 20 to 22). The medical / health manager 31 linked and registered to the subject 1 is a medical treatment person who manages and treats the subject 1 like a doctor in charge.
In the illustrated embodiment, there is no restriction on the number of registered settings, registration change, and deletion of the medical / health manager 31 that is registered and linked to the subject 1. Therefore, for example, when the subject 1 is transferred to a hospital and the doctor (responsible physician) 31 in charge of the treatment changes, in the illustrated embodiment, the medical / patients linked and registered with the subject 1 are registered. The health manager (new doctor in charge) 31 can be set for replacement registration.
In addition, when the subject (patient) 1 is receiving treatment at a plurality of clinics at the same time, a medical / health manager linked to the subject 1 and registered (doctor in charge of patient management treatment) There are a plurality of 31. In such a case, it is possible to register all medical / health managers (doctors in charge of patient management treatment) 31 linked and registered for the subject 1. That is, a plurality of medical / health managers 31 linked to the subject 1 can be registered.

In the illustrated embodiment, a single sign-on method is used for login, and no input of a login ID and a password is required for each movement within a site, movement to a separate page, menu, or job, and each login.
Considering the use of non-English Japanese terminals, login ID and password are assumed to be difficult for character conversion such as elderly people, physically handicapped people, IT, IT system unfamiliar users, mobile phones, etc. Only single-byte numbers are used.
Both the login ID and password can be changed and set by the user, but the system according to the illustrated embodiment is set so that the login ID and password cannot be stored or saved. Based on security perspective.

With reference to FIG. 2, the medical / health management institution (to which the medical / health manager 31 belongs) 3 and the system operation / management institution (to which the system operation / administrator belongs) 4 will be described in further detail.
In FIG. 2, the medical / health management institution 3 has a medical / health manager 31 who is a manager and a service desk 32 having input means.
The system operation / management organization 4 has a system operation / manager 41 (see FIG. 1) (not shown) and a support center 42.
In FIG. 2, a thick solid line arrow indicates a route of information transmission related to normal system use and is available. On the other hand, a dotted line with a thick arrow in FIG. 2 indicates a data path for an inquiry about system use, an inquiry about data use, other questions, and an answer to the question.

A detailed configuration of the data center 100 will be described with reference to FIG.
In FIG. 3, the data center 100 includes a message transmission / reception unit (hereinafter referred to as “subject 1 transmission / reception unit”) 11 and a physical condition registration unit (hereinafter referred to as “physical condition registration unit”) by the subject 1. 12), an inquiry answer / diagnosis / diagnosis data browsing unit (hereinafter referred to as "subject 1 side data browsing unit") 13 by an examinee 1, an inquiry answer / diagnosis / diagnosis data output unit (hereinafter referred to as "subject 1 side data browsing unit") 14) (referred to as “subject 1 side data output unit”).

  Further, the data center 100 includes a medical examination / diagnosis data registration unit (hereinafter referred to as a “data registration unit”) 15 by the medical / health manager 31, and a medical examination / answering / diagnosis of the subject by the medical / health manager 31. Diagnostic data browsing unit (hereinafter referred to as “medical / health manager 31 side data browsing unit”) 16 and medical examination / diagnosis / diagnosis / diagnosis data output unit (hereinafter referred to as “medical / health manager 31”). "A manager 31 side data output unit") 17, a message transmission / reception unit on the medical / health manager 31 side (hereinafter referred to as a "message transmission unit on the medical / health manager 31") 18, and a medical / health Interrogation response status confirmation unit from the subject 1 by the management organization 3 and the system operation / management organization 4 (hereinafter referred to as “interview response status confirmation unit”). And Tsu say the door ") 19, and a system participant registration unit 21, and an interview-examination set registration unit 22.

  The subject 1 is connected to the message transmission / reception unit 11 on the subject 1 side, the physical condition registration unit 12, the subject 1 side data browsing unit 13, and the subject 1 side data output unit 14 via the interface 5 and the line L1. Yes. The message transmission / reception unit 11, the physical condition registration unit 12, the subject 1 side data browsing unit 13, and the subject 1 side data output unit 14 on the subject 1 side are connected to the storage unit (database) 20 via the line L2. Connected.

The medical / health manager 31 receives the data registration unit 15, the medical / health manager 31 side data browsing unit 16, the medical / health manager 31 side data output unit 17, and the medical device via the interface 5B and the line L4. The message transmission / reception unit 18 on the health manager 31 side and the inquiry response status confirmation unit 19 are connected.
The system operation manager 41 receives the message transmission / reception unit 18 on the medical / health manager 31 side, the inquiry answer status confirmation unit 19, the system participant registration unit 21, the inquiry / examination set via the interface 5C and the line L5. It is connected to the registration unit 22.
The storage unit 20 (database) is connected to the units 15 to 19, 21, and 22 via the line L3.

1 and 2, the second area E2 includes a communication network having a higher security level than the IP-VPN 250 or higher, and terminal devices that can be connected to the communication network (terminal devices dedicated to the system according to the illustrated embodiment). (Not shown in FIG. 1)).
The medical / health manager 31 can access the data center 100 in the illustrated health management system 500 and view necessary physical condition information regarding the physical condition information of the subject 1 in charge of management. The medical / health manager 31 can output (download) the physical condition information from his / her dedicated terminal (computer PC or the like) as necessary.

The storage unit 20 of the data center 100 stores the answer of the subject 1 with respect to the interview set (answer to each interview) as quantified data.
Each interview consists of “question number”, “question”, “answer entry field or answer option”, “threshold value”, and “weighting value”. Will not be changed or updated. This is to maintain the consistency, accuracy, significance, continuity, and ease of comparison of questionnaire response data.
For an inquiry using the “weighting value” to give a score to an inquiry answer, the inquiry answer data is output to the outside of the health management system 500, and “weighting processing” is performed outside the health management system 500. I can do it.

Individual interviews are created by the medical / health manager 31 who is a person suitable for creating an interview, and are registered on the health management system 500 in the order of creation in accordance with a prescribed order.
A person (medical / health manager) 31 who is suitable for organizing an interview set by combining a plurality of interviews organizes an interview set using the registered individual interviews.

Answers to the interview set are stored in the storage unit 20 as quantified data.
For example, in the case of an inquiry regarding the degree of intensity, it is preferable to store the data as quantitative data.
When the answer to the interview set is qualitative data, in order to convert the data into quantitative data, in the illustrated health management system 500, the answer to the interview is divided into 3 to 5 stages. However, it is possible to change the number of sections for each inquiry according to the required level of detail.

  For example, a person who is suitable for assigning the interview set to the subject 1 like the medical / health manager 31 assigns and sets the interview set to the subject 1 (see FIGS. 20 to 22). When there are a plurality of patients with the same disease or there are a plurality of persons who have the purpose of collecting the same physical condition information, the same inquiry set is assigned to the plurality of persons.

  In the health management system 500 shown in FIGS. 1 and 2, there is an area where the medical / health manager 31 can input, register, and save the physical condition information of the subject 1, information obtained therefrom, annotations, findings, and the like. In FIG. 1 and FIG. 2, the health management system 500 registers and stores items such as medical records such as the physical condition information, treatment, and medication information of the subject 1 that has been converted into an electronic file, electronic image, or electronic document. An area where information, annotations, findings, and the like obtained from items such as medical records such as the physical condition information, treatment, and medication information of the subject 1 can be registered and stored is also secured.

  The medical / health manager 31 records the physical condition information of the subject 1 obtained at the time of direct interview (diagnosis) with the subject 1 and information obtained therefrom in a record and storage area (storage unit 20) in the health management system 500. You can enter and register directly.

  While the medical / health manager 31 conducts a direct interview with the subject 1 and makes a diagnosis (detailed but intermittent physical condition information) and during a direct interview (diagnosis) with the subject 1 It is possible to collate, collate, and verify the physical condition information of the subject continuously collected during the period (by using the service according to the illustrated embodiment). As a result, a more reliable and more effective diagnosis is realized.

In addition, according to the health management system 500 of FIGS. 1 and 2, information (medical / health manager 31 that has been stored in a different format for each medical / health manager 31 (for each medical institution 3) in the past). The physical condition information obtained when making a diagnosis by interviewing subject 1 directly, and the information obtained therefrom, annotations, findings, etc.) are directly registered and stored in the health management system 500 of FIGS. Therefore, it can be managed centrally.
And it becomes possible for the test subject 1 to always hold the data of his / her physical condition information. That is, a so-called “personal health record” is provided to the subject 1.

Next, with reference to FIG.4 and FIG.5, the physical condition registration by the test subject 1 is demonstrated.
The physical condition registration unit 12 shown in FIG. 4 is provided for performing physical condition registration by the subject 1.
The physical condition registration unit 12 includes a login approval block 121, a login approval result notification block 122, an access authority granting block 123, an inquiry block 124, and a storage unit 20.
The storage unit 20 is the same as the storage unit 20 shown in FIG. 2, and is shared with the storage unit 20 in each of units 11 to 19, 21, and 22 described later.
The inquiry block 124 includes an “inquiry part” 124A, an “abnormal answer / approval request part” 124B, an “abnormal answer / determination part” 124C, and a “message transmission block” 124D.

When the physical condition is registered by the subject 1, the subject 1 is connected to the login approval block 121 and the login approval result notification block 122 via the interface 5 and the line L12a.
In the case of access approval, the login approval result notification block 122 is connected to the access authority granting block 123 via the line L12b, the branch point B, and the line L12c (route in the case of access approval).
Further, the login approval result notification block 122 is connected to the subject 1 via the line L12b, the branch point B, and the line L12d (via the interface 5A) in the case of login non-approval (in the case of login non-approval). Route).
In FIG. 4, the subject 1 is displayed up and down for convenience of drawing, but both are the same.
The interface 5 and the interface 5A may be the same.

The login approval block 121 is connected to the storage unit (database) 20 by a line L12e and a line L12f. The login information from the login approval block 121 is transmitted to the storage unit 20 via the line L12e. Then, the collation result is transmitted from the storage unit 20 to the login approval block 121 via the line L12f.
The storage unit 20 is connected to the access authority granting block 123 by a line L12g. Access authority setting information is given from the storage unit 20 to the access authority granting block 123 via the line L12g.

The subject 1 is connected to the inquiry block 124 via the interface 5 through a line L12h. When access from the subject 1 is approved, the subject 1 is configured to input (answer) his / her physical condition to the inquiry block 124.
The storage unit 20 is connected to the inquiry block 124 via a line L12i and a line L12j.
The physical condition input by the subject 1 is registered in the storage unit 20 from the inquiry block 124 via the line L12i. Then, an inquiry set, which will be described later, is transmitted from the storage unit 20 to the inquiry unit 124A in the inquiry block 124 via the line L12j.

The storage unit 20 is connected to the “abnormal answer / determination unit” 124C in the inquiry block 124 via a line L12k. The storage unit 20 is connected to the “message transmission block” 124D in the inquiry block 124 via the line L12m.
The “abnormal answer / determination unit” 124C is configured to transmit an alert message to the storage unit 20 via the line L12k. The “message transmission block” 124D is configured to transmit a message to the storage unit via the line L12m.

The access authority granting block 123 is connected to the inquiry block 124 via a line L12n.
Access authority setting information is sent from the storage unit 20 to the access authority granting block 123 via the line L12g.
The inquiry block 124 is connected to the subject 1 via the line L12o and the interface 5A.
As described above, the interface 5 and the interface 5A may be the same.

Next, a procedure for registering physical condition in the physical condition unit 12 will be described mainly with reference to FIG.
In step Sa <b> 1 of FIG. 5, the subject 1 accesses the physical condition registration unit 12 of the data center 100. In step Sa2, the login ID and password are input.
The login approval block 121 of the physical condition registration unit 12 determines whether or not to approve login (step Sa3). If the login is not approved (step Sa3 is NO), the process returns to step Sa2, and step Sa2 and subsequent steps are repeated again.
On the other hand, if the login is approved by the login approval block 121 (YES in step Sa3), the process proceeds to step Sa4.

In step Sa4, a menu screen is displayed, an inquiry answer is started (step Sa5), and the process proceeds to step Sa6. In step Sa6, the subject 1 selects an inquiry menu.
In step Sa7, an inquiry screen is displayed. In step Sa8, the subject 1 inputs the physical condition information and the like of the subject 1 by answering the questionnaire-type inquiry posted on the inquiry website.
For example, one interview is presented for each page of the web page, and the subject 1 is requested one answer for each interview. The subject 1 can confirm that the correct value has been correctly input by performing the process of “next” after inputting the answer. If the next inquiry is presented, the subject 1 further proceeds to the next web page.

If Subject 1 confirms that the value of the entered answer is incorrect due to reasons such as incorrect input, or if he / she feels suspicion about the entered value, he / she returns to the web page where the question is presented, You can re-enter the correct value.
A threshold is provided in an inquiry requesting that a numerical value such as a body temperature be input at the time of answering to prevent an incorrect value from being input. When an input of a value exceeding the threshold, that is, an answer that is likely to be an incorrect input is executed (for example, step Sa9 is YES), this is immediately notified to the subject 1 (for example, step Sa10). The input value is confirmed up to three times (for example, a loop in which step Sa9 is YES and step Sa12 is YES is repeated three times at most).

The threshold value set for the interview requesting a numerical answer is determined by a person who is judged to be suitable for the determination of the threshold value, such as a doctor, a medical staff 31 or the like, and is set for the interview. .
In addition, although the threshold value is valid, when the subject 1 sticks to a value exceeding the threshold value for the three confirmation requests, the system according to the illustrated embodiment The value that the subject 1 sticks to is accepted as a unique value in the subject 1 and the process is executed.

A threshold is provided for an inquiry for a numerical answer so that the respondent's physical condition can be recognized. And when the answer exceeding the said threshold value is input (for example, step Sa9 is YES), a warning message is displayed (for example, step Sa10), and the test subject 1 is alerted. .
Although not explicitly shown in FIG. 5, the health management system 500 responds to a medical / health manager 31 who manages and guides the subject 1 when the subject 1 detects an answer that deserves recognition of the physical condition. Send an abnormal value occurrence message.

In step Sa9 of FIG. 5, the physical condition registration unit 12 determines whether or not there is an abnormal value in the answer (physical condition, for example, the value of heat or blood pressure) input by the subject.
If there is an abnormal value in the answer input by the subject (step Sa9 is YES), the process proceeds to the next step Sa10. On the other hand, when there is no abnormal value in the answer inputted by the subject (step Sa9 is NO), the process proceeds to Sa13.

In step Sa10, an answer (physical condition) confirmation correction request screen is displayed. The subject 1 re-inputs the answer (physical condition) in step Sa11.
In step Sa12, the physical condition registration unit 12 determines whether or not there is an abnormality in the answer re-input by the subject. As described above, in the flowchart of FIG. 5, the answer confirmation correction request in step Sa10 is up to three times in total.
If there is an abnormality in the answer re-input by the subject 1 in step Sa11 (YES in step Sa12), the process returns to step Sa10. If there is no abnormality in the answer re-input by the subject 1 (step Sa12 is NO), the process proceeds to step Sa13.

In step Sa13, an answer confirmation correction request screen is displayed. In step Sa14, the physical condition registration unit 12 determines whether or not the answer has been corrected.
If the answer has been corrected (YES in step Sa14), the process returns to step Sa7 and repeats step Sa7 and subsequent steps again. On the other hand, if the answer is not corrected (NO in step Sa14), the process proceeds to step Sa15, and the physical condition registration unit 12 determines whether or not to end the inquiry answer.
If the inquiry answer is not completed (NO in step Sa15), the process returns to step Sa7, and step Sa7 and subsequent steps are repeated again. On the other hand, if the inquiry answer is completed (YES in step Sa15), the process proceeds to step Sa16.
Here, the number of interviews is set to the number of times that the subject 1 is not burdened by answering.

In step Sa16, the physical condition registration unit 12 acquires inquiry response data. In step Sa17, a comment / message input screen for the subject manager 31 is displayed.
In step Sa17, the subject 1 can input a comment in the comment field prepared at the end of the series of questions. This comment field can be used as a free writing space and as an input field for a document diary or the like. The contents entered by the subject 1 in the comment field can be viewed by the subject himself and the medical / health manager 31 in charge of the subject.
In addition, for the contents such as a diary or a comment entered by the subject 1 in the comment field, the medical / health manager 31 in charge of the subject sends a message to the subject to respond to the comment as necessary. It can also be sent.

In step Sa18, it is determined whether or not to send a comment and / or message. If a comment and / or message is to be transmitted (YES in step Sa18), the process proceeds to step Sa19. On the other hand, if the comment and / or message is not transmitted (NO in step Sa18), the process proceeds to step Sa22.
In step Sa19, comments and / or messages are input and transmitted (step Sa20), and in step Sa21, the storage unit 20 in the present system stores the message. In step Sa22, the inquiry answer is ended, and the process proceeds to step Sa23.

In step Sa23, the physical condition registration unit 12 determines whether or not to use another menu.
If another menu is to be used (YES in step Sa23), the process returns to step Sa4 and repeats step Sa4 and subsequent steps. On the other hand, if the other menu is not used (step Sa23 is NO), the user is logged out (step Sa24), and the series of control relating to the physical condition registration is ended.

  4 and 5, the physical condition information data registered by the subject 1 in the physical condition registration unit 12 is downloaded (output) for any subject 1 (for example, see FIGS. 18 and 19). Then, download is performed in the order of all the interviews registered in the interview master list (see FIGS. 23 and 24) (in other words, in the order of “interview numbers”). This is because it is easy to compare the body condition information data between the subjects and to prevent so-called “missing” of the data.

Table 1 illustrates the inquiry response data, and Table 2 illustrates the inquiry response data record.

In the inquiry answer data exemplified in Table 1, “interview number” is described from the top to the bottom in the leftmost vertical column.
In the interview answer data records exemplified in Table 1, the interview answers are created in a column in ascending order of creation start date and time.
In the “data generation date / time” column on the leftmost side of Table 2, “Y / M / D / H / M / S” is “year / month / day / hour / minute / second” in which the inquiry answer data is generated. Means.
In Tables 1 and 2, “Null (no data)” does not mean “data is zero (0)”, but means “data has not been taken” or “data has not been taken” It is. The data formats in Tables 1 and 2 are CSV and TXT, and data formats that are easy to input and process into other health care systems are adopted.

Next, message transmission / reception by the subject, the medical / health manager, and the system operation manager will be described with reference to FIGS.
FIG. 6 shows the configuration of a unit 11 that transmits and receives messages (hereinafter referred to as “message transmitting and receiving unit”). In FIG. 3, the message transmission / reception unit is separated into a unit denoted by reference numeral 11 and a unit denoted by reference numeral 18. However, the message transmission / reception unit 11 shown in FIG. 6 integrates the units 11 and 18 in FIG. It has become the composition.
In FIG. 6, the message transmission / reception unit 11 includes a login approval block 111, a login approval result notification block 112, an access authority assignment block 113, a transmission block 114, a reception block 115, and a storage unit 20.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage units 20 of the units 11 to 19, 21, and 22 in the data center 100.

The participant MR (subject 1, medical / health manager 31, system operation manager 41) is connected to the login approval block 111 and the login approval result notification block 112 via the interface 5 and the line L11a.
When approving login, the login approval result notification block 112 is connected to the access authority granting block 113 via the line L11b, the branch point B1, and the line L11c (route in the case of login approval).
If the login approval result notification block 112 does not approve the login, the login / approval result notification block 112 uses the line L11b, the branch point B1, the line L11d, the branch point B2, and the line L111d (via the interface 5BC) to It is connected to the system operation manager 41 (route when login is not approved). Alternatively, the login approval result notification block 112 is connected to the subject 1 through the line L11b, the branch point B1, the line L11d, the branch point B2, and the line L112d (via the interface 5A) when the login is not approved. (Route when login is not approved).
The participant MR (subject 1, medical / health manager 31, system operation manager 41) is displayed in the upper and lower parts of FIG. 6 for convenience of illustration.
The interface 5 and the interface 5A may be the same.

The login approval block 111 is connected to the storage unit (database) 20 by a line L11e and a line L11f. The login information is transmitted from the login approval block 111 to the storage unit (database) 20 through the line L11e. Then, the collation result is transmitted from the storage unit 20 to the login approval block 121 via the line L11f.
The storage unit 20 is connected to the access authority granting block 113 via the line L11g, and access authority setting information is given from the storage unit 20 to the access authority granting block 113 via the line L11g.

The access authority grant block 113 is connected to the transmission block 114 via a line L11h. Then, the access authority is given from the access authority granting block 113 to the transmission block 114 via the line L11h.
The access authority granting block 113 is connected to the receiving block 115 via the line L11k. Then, the access authority is given from the access authority granting block 113 to the receiving block 115 via the line L11k.

The participant MR (subject 1, medical / health manager 31, system operation manager 41) is connected to the transmission block 114 via the interface 5 and the line L11h. Then, a message is transmitted from the participant MR to the transmission block 114.
The transmission block 114 is connected to the storage unit 20 via a line L11i and a line L11j. The message transmission destination list is transmitted from the storage unit 20 to the transmission block 114 via the line L11i. Then, an access authority grant message is transmitted from the transmission block 114 to the storage unit 20 via the line L11j.
In addition, the transmission block 114 is connected to the medical / health manager 31 and the system operation manager 41 (lower participants in FIG. 6) via the line L11o, the branch point B3, the interface 5BC, and the line L111o. It is connected to the medical / health manager 31 and the system operation manager 41) in the MR, and sends a message transmission notification.
Furthermore, the transmission block 114 is connected to the subject 1 who is the participant in the region 1 (the subject 1 in the lower participant MR in FIG. 6) via the line L11o, the branch point B3, the line L112o, and the interface 5A. And send a message transmission notification.

The participant MR (subject 1, medical / health manager 31, system operation manager 41: information participant MR in FIG. 6) is connected to the reception block 115 via the interface 5 via the line L11m, and the participant MR. Transmits to the receiving block 115 that the message has been received.
The reception block 115 is connected to the storage unit 20 via a line L11n and receives a message from the storage unit 20.
Further, the reception block 115 is connected to the medical / health manager 31 and the system operation manager 41 (participant MR in the lower part in FIG. 6) via the line L11p and the interface 5BC. Connect to the health manager 31 and the system operation manager 41) and send an alert message.
Furthermore, the reception block 115 is connected to the subject 1 who is the participant in the region 1 (the subject 1 in the lower participant MR in FIG. 6) via the line L11q, the branch point B4, the line L111q, and the interface 5A. And send a message. Then, the reception block 115 is connected to the medical / health manager 31 and the system operation manager 41 (in FIG. 6 in the lower part) through the line L11q, the branch point B4, the interface 5BC, and the line L112q. A connection is made with a medical / health manager 31 and a system operation manager 41) of the person MR, and a message is transmitted.

Next, a procedure for sending and receiving messages will be described mainly with reference to FIG.
In step Sb1 of the step of FIG. 7, the subject 1 accesses the message transmission / reception unit 11 of the data center 100, and inputs the login ID and password in step Sb2.
The login approval block 111 of the message transmission / reception unit 11 determines whether to approve login (step Sb3).
If the login is not approved (step Sb3 is NO), the process returns to step Sb2, and the steps after step Sb2 are repeated. On the other hand, if the login is approved (step Sb3 is YES), the process proceeds to step Sb4.

In step Sb4, a menu screen is displayed and message transmission / confirmation is started (step Sb5). In step Sb6, a screen for the participant MR (subject 1, medical / health manager 31, system operation manager 41) to select a message transmission / confirmation menu is displayed on the information terminal of the participant MR. .
In step Sb7, a message transmission / confirmation screen is displayed. In step Sb8, the message transmitting / receiving unit 11 determines whether a message has been transmitted.
If the message has been transmitted (YES in step Sb8), the process proceeds to step Sb9. If not transmitted (NO in step Sb8), the process proceeds to step Sb17.

  In step Sb9, the message transmission / reception unit 11 determines whether the message transmission destination is limited to one. If the message destination is limited to one (step Sb9 is YES), the process proceeds to step Sb12. If the message destination is not limited to one (step Sb9 is NO), the process proceeds to step Sb10. In step Sb10, the message transmission / reception unit 11 selects a transmission destination, and determines whether or not to change the transmission destination in step Sb11. If the transmission destination is changed (YES in step Sb11), the process returns to step Sb10. If the transmission destination is not changed (NO in step Sb11), the process proceeds to step Sb12.

If the participant MR inputs a message in step Sb12, a message content confirmation screen is displayed (Sb13).
In step Sb14, the message transmission / reception unit 11 determines whether there is a change in the message.
If there is a change in the message (YES in step Sb14), the process proceeds to step Sb15. If there is no change in the message (NO in step Sb14), the process returns to step Sb12, and steps Sb12 and after are repeated.

  In step Sb15, a message is transmitted, and in the next step Sb16, the message is displayed. Proceeding to step Sb17, the message transmitting / receiving unit 11 determines whether or not the received message has been confirmed. If the received message is confirmed (YES in step Sb17), the process proceeds to step Sb18. On the other hand, when the received message is not confirmed (step Sb17 is NO), the process proceeds to step Sb22.

In step Sb18, the participant MR selects a message transmission / confirmation menu. Then, a message is displayed in step Sb19, a received message browsing screen is displayed in step Sb20, and the process proceeds to step Sb21.
In step Sb21, the message transmission / reception unit 11 determines whether or not it has replied to the received message. If the reply is made to the received message (YES in step Sb21), the process returns to step Sb12. On the other hand, if the message has not been replied (step Sb21 is NO), the process proceeds to the next step Sa22.

  In step Sb22, the message transmission / confirmation process ends. In step Sb23, the message transmitting / receiving unit 11 determines whether to use another menu. If another menu is to be used (YES in step Sb23), the process returns to step Sb4, and step Sb4 and subsequent steps are repeated again. On the other hand, if no other menu is used (NO in step Sb23), the user logs out in step Sb24 and ends a series of processes related to message transmission / reception.

  In the illustrated embodiment, the system participant MR creates and sends a message according to the granted authority (see FIGS. 20-22). In addition, a message created by another system participant MR is received, viewed, and a reply message is created and transmitted in response to the message.

  A predetermined system participant MR (for example, an operator of the system and service according to the illustrated embodiment, a person 41 similar to the operator) has the authority and responsibility to always view and quarantine all messages. The message according to the embodiment and the maintenance and operation of the service thereby are excluded (so-called “dangerous” message), and the creator and sender of the dangerous message are specified and excluded. To take responsibility.

The system and service operator 41 according to the illustrated embodiment can transmit a message to any system participant MR at any time when it is determined that it is necessary for operation. .
The type of message is a public message to the whole, a private message to a limited target, a so-called “one-to-one” message, a so-called “one-to-multiple” message, a so-called “one-to-all” message. .
In other words, although not clearly shown, the operator (or similar person) 41 (of the system and service according to the illustrated embodiment) can send the message as described above. In addition, the message transmission / reception unit 11 in the system according to the illustrated embodiment is provided with functions of individual message distribution, broadcast distribution, and posting.

Here, the message (see FIGS. 4 and 5) that the subject 1 inputs in the comment field at the end of the inquiry is initially set so that the medical / health manager 31 in charge of the subject 1 can view (see FIG. 20 to 22).
Although not shown, the system participant MR who intends to create and send a message for all messages other than the message that the subject 1 enters in the comment field at the end of the interview, registers and sets the destination in advance. Keep it. When registering and setting as a transmission destination in advance, permission is requested (acquired) for registration and setting as a message transmission destination to a transmission destination that desires registration and setting.

The system participant MR who has been requested to register and set as a message transmission destination responds to the system administrator 41. Upon receiving the response, the system operation manager 41 notifies the system participant who desires to register and set the response (the system participant 41 who desires to register and set the message transmission destination in advance).
If you do not have permission to register and set for message transmission, you cannot register and set the destination (a destination that has not been registered or set in advance as a message destination) as a message destination. It is configured like this.
In addition to not being able to send messages to destinations that have not been permitted to register and set message transmission in advance, even when the message posting function is selected, the posted messages will not be viewed. It is configured.

Although not shown, in the system according to the embodiment, a system participant MR who intends to create and transmit a message and desires to register and set a transmission destination of the message in advance The system operation manager 41 asks the destination about whether or not to register and set the destination as the destination.
The series of processing of inquiry, reply, and notification described above is performed in the system according to the embodiment, and is not performed outside the system.

  After registering and setting as a message destination, registering as a message destination and canceling the setting (registering as a message destination, canceling the setting), receiving a message after the cancellation Rejection is made by the system participant who wants to cancel.

Next, referring to FIG. 8 and FIG. 9, the inquiry answer / diagnosis / diagnosis data browsing by the subject will be described.
FIG. 8 shows a configuration of an inquiry answer / diagnosis / diagnosis data browsing unit (hereinafter referred to as “subject 1 side data browsing unit”) 15 by the subject 1 in the data center 100.
In FIG. 8, the subject 1 side data browsing unit 13 includes a login approval block 131, a login approval result notification block 132, an access authority granting block 133, an inquiry response / diagnosis / diagnosis data transmission block (hereinafter “data transmission block”). And the storage unit 20.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3 and is common to the storage units 20 in each of the units 11 to 19, 21, and 22 in the data center 100.

The subject 1 is connected to the login approval block 131 and the login approval result notification block 132 through the interface 5 through the line L13a.
When approving login, the login approval result notification block 132 is connected to the access authority granting block 133 by the line L13b, the branch point B, and the line L13c (route in the case of login approval).
Further, when the login approval result notification block 132 does not approve the login, the login approval result notification block 132 is connected to the subject 1 via the line L13b, the branch point B, the line L13d, and the interface 5A (route when the login is not approved). .
In FIG. 8, the subject 1 is displayed up and down for convenience of drawing, but both are the same.
The interface 5 and the interface 5A may be the same.

The login approval block 131 is connected to the storage unit 20 by a line L13e and a line L13f. The login information is transmitted from the login approval block 131 to the storage unit 20 via the line L13e. Then, the collation result is transmitted from the storage unit (database) 20 to the login approval block 131 via the line L13f.
The storage unit 20 is connected to the access authority granting block 133 via the line L13g, and access authority setting information is given from the storage unit 20 to the access authority granting block 133 via the line L13g.

The subject 1 is connected to the data transmission block 134 via the interface 5 and the line L13h, and when access is approved, the subject 1 browses the data transmission block 134 for an inquiry answer / diagnosis / diagnosis data. Configured to make requests.
The storage unit 20 is connected to the data transmission block 134 via the line L13i and the line L13j. An inquiry answer / diagnosis / diagnosis data is requested from the data transmission block 134 to the storage unit 20 via the line L13i. The inquiry answer / diagnosis / diagnosis data is disclosed from the storage unit 20 to the data transmission block 134 via the line L13j.

The access authority granting block 133 is connected to the data transmission block 134 via the line L13n, and is configured to give access authority to the data transmission block 134.
The data transmission block 134 is connected to the subject 1 via the line L13o and the interface 5A, and is configured to disclose the inquiry answer / diagnosis / diagnosis data requested by the subject 1 to the subject 1.

Next, the flow of data browsing processing in the subject 1 side data browsing unit 13 will be described with reference to FIG.
In step Sc1 of FIG. 9, the subject 1 accesses the subject 1 side data browsing unit 13 of the data center 100, and inputs a login ID and a password in step Sc2.
The login approval block 131 of the subject 1 side data browsing unit 13 determines whether or not to approve login (step Sc3).
If the login is not approved (NO in step Sc3), the process returns to step Sc2, and steps after step Sc2 are repeated. On the other hand, if the login is approved (step Sc3 is YES), the process proceeds to step Sc4.

In step Sc4, a menu screen is displayed, and in step Sc5, data browsing related to an inquiry answer / diagnosis / diagnosis is started. Then, in step Sc6, the subject 1 selects an inquiry answer / diagnosis / diagnosis data browsing menu.
In step Sc7, the inquiry response data / diagnosis / diagnosis data stored in the system is called, and in step Sc8, the inquiry answer / diagnosis / diagnosis data is displayed on the information terminal screen of the subject 1.
In step Sc9, the subject 1 side data browsing unit 13 determines whether or not the browsing target is related to the inquiry answer data. If the browsing target relates to the inquiry response data (YES in step Sc9), the process proceeds to step Sc10.
In step Sc10, the subject 1 selects an inquiry reply date, the interview reply data selected in step Sc11 is selected, and the interview reply data is displayed on the information terminal screen of the subject 1 in step Sc12.

In step Sc9, if the browsing target is not related to the inquiry response data (NO in step Sc9), the process proceeds to step Sc13.
In step Sc13, a diagnosis / diagnosis data file is selected, and in step Sc14, diagnosis / diagnosis data stored in the system is selected. In step Sc15, the corresponding diagnosis / diagnosis data is displayed on the information terminal screen of the subject 1, and the process proceeds to step Sc16.

In step Sc <b> 16, the subject 1 side data browsing unit 13 determines whether or not browsing of data related to another inquiry answer / diagnosis / diagnosis is requested. If data browsing related to another inquiry answer / diagnosis / diagnosis is requested (YES in step Sc16), the process returns to step Sc8, and step Sc8 and subsequent steps are repeated again.
If data browsing related to other inquiry answers / diagnosis / diagnosis is not requested (NO in step Sc16), the inquiry answer / diagnosis / diagnosis data browsing process is terminated in step Sc17, and the process proceeds to step S18.
In step Sc18, it is determined whether or not another menu is to be used. If another menu is to be used (YES in step Sa18), the process returns to step Sc4 and repeats step Sc4 and subsequent steps. On the other hand, if no other menu is used (NO in step Sc18), the user logs out in step Sc19 and ends a series of controls relating to the data browsing process.

Next, referring to FIG. 10 and FIG. 11, the question answering / diagnosis / diagnosis data output by the subject will be described.
FIG. 10 shows the configuration of the subject 1 side data output unit 14 in the data center 100.
Here, in the interview answer / diagnosis / diagnosis data output by the subject and the interview answer / diagnosis / diagnosis data output by the subject, the “access right grant block” from the “access authorization granting block” for “login approval” in FIGS. "Is different. Since the output result remains as various media in “output”, the access authority of the person who can perform “output” is set to hardness as compared with the case of “view”. That is, for “output”, higher authority than “view” is required.

10, the subject 1 side data output unit 14 includes a login approval block 141, a login approval result notification block 142, an access authority granting block 143, an inquiry response / diagnosis / diagnosis data transmission block (hereinafter referred to as “data transmission block”). And the storage unit 20.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage unit 20 of each unit in the data center 100.

The subject 1 is connected to the login approval block 141 and the login approval result notification block 142 via the interface 5 and the line L14a.
When approving login, the login approval result notification block 142 is connected to the access authority granting block 143 via the line L14b, the branch point B, and the line L14c (route in the case of login approval).
On the other hand, when the login is not approved, the login approval result notification block 142 is connected to the subject 1 via the line L14b, the branch point B, the line L14d, and the interface 5A (route when the login is not approved). .
In FIG. 10, the subject 1 is displayed up and down for convenience in drawing, but both are the same.
The interface 5 and the interface 5A may be the same.

The login approval block 141 is connected to the storage unit (database) 20 via a line L14e and a line L14f. The login information is transmitted from the login approval block 141 to the storage unit 20 via the line L14e. Then, the verification result is transmitted from the storage unit 20 to the login approval block 141 via the line L14f.
The storage unit 20 is connected to the access authority granting block 143 via the line L14g, and access authority setting information is given from the storage unit 20 to the access authority granting block 143 via the line L14g.

The subject 1 is connected to the data transmission block 144 via the interface 5 and the line L14h.
When the access is made by the merchant, the subject 1 requests the data transmission block 144 to output an inquiry answer / diagnosis / diagnosis data.
The storage unit 20 is connected to the data transmission block 144 via the line L14i and the line L14j. An inquiry answer / diagnosis / diagnosis data is requested from the data transmission block 144 to the storage unit 20 via the line L14i. The inquiry answer / diagnosis / diagnosis data is disclosed from the storage unit 20 to the data transmission block 144 via the line L14j.

The access authority grant block 143 is connected to the data transmission block 144 via the line L14n, and is configured to give access authority to the data transmission block 144.
The data transmission block 144 can be connected to the subject 1A via the line L14o and the interface 5A, and is configured to output the inquiry answer / diagnosis / diagnosis data requested by the subject 1 to the subject 1.

Next, with reference to FIG. 11, the procedure of the data output in the test subject 1 side data output unit 14 is demonstrated.
In step Sd1 of FIG. 11, the subject 1 accesses the subject 1 side data output unit 14 of the data center 100, and inputs the login ID and password in step Sd2.
The login approval block 141 of the subject 1 side data output unit 14 determines whether or not to approve login (step Sd3).
If the login is not approved (step Sd3 is NO), the process returns to step Sd2, and the steps after step Sd2 are repeated again. On the other hand, if the login is approved (step Sd3 is YES), the process proceeds to step Sd4.

In step Sd4, a menu screen is displayed, and data output related to the inquiry answer / diagnosis / diagnosis is started (step Sd5). In step Sd6, the subject 1 selects an inquiry answer / diagnosis / diagnosis data output menu.
In step Sd7, inquiry response data / diagnosis / diagnosis data is called from the system, and in step Sd8, an inquiry answer / diagnosis / diagnosis data output screen is displayed.
In step Sd9, the subject 1 side data output unit 14 determines whether or not the output target relates to the inquiry answer data. If the output target is related to the inquiry response data (YES in step Sd9), the process proceeds to step Sd10.
In step Sd10, the subject 1 selects the first day and the last day of the inquiry answer data, selects the answer data stored in the system (step Sc11), and the CSV file of the answer data to be output in step Sd12. To do. In step Sd13, the output of the inquiry response data is terminated, and the process proceeds to step Sd18.

On the other hand, if the output target is not related to the inquiry response data (NO in step Sd9), the process proceeds to step Sc14.
In step Sd14, a diagnosis / diagnosis data file is selected, and in step Sd15, a diagnosis / diagnosis data file stored in the system is selected. Then, the process proceeds to step Sd16, the corresponding diagnosis / diagnosis data is output, and the diagnosis / diagnosis data output process is terminated (step Sd17). Then, the process proceeds to step Sd18.

In step Sd18, the subject 1-side data output unit 14 determines whether or not to output data relating to other inquiry answers / diagnosis / diagnosis. If data related to another inquiry answer / diagnosis / diagnosis is to be output (YES in step Sd18), the process returns to step Sd8, and step Sd8 and subsequent steps are repeated again. On the other hand, if data related to another inquiry answer / diagnosis / diagnosis is not output (NO in step Sd18), the inquiry answer / diagnosis / diagnosis data output process is terminated in step Sd19.
In step Sd20, the subject 1-side data output unit 14 determines whether to use another menu. If another menu is to be used (YES in step Sd20), the process returns to step Sd4, and step Sd4 and subsequent steps are repeated again. On the other hand, if no other menu is used (NO in step Sd20), the user logs out in step Sd21 and ends a series of controls relating to the data output process.

Next, referring to FIG. 12 and FIG. 13, an explanation will be given on the status of the inquiry / answer from the subject 1 by the medical / health manager 31.
In FIG. 12, the inquiry response status confirmation unit 19 includes a login approval block 191, a login approval result notification block 192, an access authority grant block 193, an inquiry response / diagnosis / diagnosis data transmission block (hereinafter referred to as “data transmission block”). 194) and a storage unit 20.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage unit 20 in each of the units 11 to 19, 21, and 22 in the data center 100.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the login approval block 191 and the login approval result notification block 192 via the interface 5 by the line L19a.
The login approval result notification block 192 is connected to the access authority granting block 193 by a line L19b, a branch point B, and a line L19c (route in the case of approval).
The login approval result notification block 192 is connected to the participant MR2 (the medical / health manager 31, the system operation manager 41) via the line L19b, the branch point B, and the line L19d (via the interface 5BC). (Route for unapproved).
In FIG. 12, a participant MR2 (medical / health manager 31, system operation manager 41) is displayed vertically for convenience in drawing.
The interface 5 and the interface 5BC may be the same.

The login approval block 191 is connected to the storage unit (database) 20 via a line L19e and a line L19f. The login information is transmitted from the login approval block 191 to the storage unit 20 via the line L19e. Then, the collation result is transmitted from the storage unit 20 to the login approval block 191 via the line L19f.
The storage unit 20 is connected to the access authority granting block 193 via the line L19g. Access authority setting information is given from the storage unit 20 to the access authority granting block 193 via the line L19g.

The participant MR2 is connected to the data transmission block 194 via the interface 5 and the line L19h. When the access is approved, the participant MR2 is configured to make an inquiry response status confirmation request to the data transmission block 194.
The storage unit 20 is connected to the data transmission block 194 via the line L19i and the line L19j. The inquiry response status data is requested from the data transmission block 194 to the storage unit 20 via the line L19i. The inquiry response status data is disclosed from the storage unit 20 to the data transmission block 194 via the line L19j.

The access authority grant block 193 is connected to the data transmission block 194 via the line L19n. The access authority is transmitted from the access authority granting block 193 to the data transmission block 194 via the line L19n.
The data transmission block 194 can be connected to the participant MR2 via the line L19o and the interface 5A. The data transmission block 194 is configured to output and disclose the inquiry answer / diagnosis / diagnosis data requested by the participant MR2 to the subject.

Next, with reference to FIG. 13, the procedure of the inquiry response status confirmation process in the inquiry response status confirmation unit 19 will be described.
In step Se1 of FIG. 13, the participant MR2 accesses the inquiry response status confirmation unit 19 of the data center 100, and inputs the login ID and password in step Se2.
The login approval block 191 of the inquiry response status confirmation unit 19 determines whether or not to approve the login (step Se3).
If the login is not approved (NO at Step Se3), the process returns to Step Se2 and repeats Step Se2 and the subsequent steps. On the other hand, if the login is approved (step Se3 is YES), the process proceeds to step Se4.

In step Se4, a menu screen is displayed, and in step Se5, inquiry response data is displayed. In step Se6, the participant MR2 selects the inquiry response status confirmation menu, and in step Se7, the inquiry response status confirmation screen is displayed on the screen of the information device of the participant MR2.
In step Se8, the inquiry response status confirmation unit 19 determines whether or not the subject 1 who is the subject of the inquiry response status confirmation is in a continuous unanswered state, that is, an abnormal state. If it is found that the subject 1 who is the subject is in an abnormal state (YES in Step Se8), the process proceeds to Step Se9. On the other hand, if the subject 1 to be processed is not in an abnormal state (NO in Step Se8), the process returns to Step Se4, and Step Se4 and subsequent steps are repeated for the other subjects 1.

In step Se9, the inquiry response status confirmation unit 19 contacts the subject 1 in the continuous unanswered state (subject 1 in the abnormal state) and inquires about the cause of the continuous unanswered state.
In step Se10, the inquiry response status confirmation unit 19 investigates the history of the subject's inquiry response, and in step Se11, determines whether or not the subject has recognized a physical condition abnormality.
If the subject recognizes abnormal body condition (step Se11 is YES), the process proceeds to step Se12.
On the other hand, if the subject does not recognize the abnormal body condition (NO in Step Se11), the process returns to Step Se4, and Step Se4 is repeated for the other subjects 1.

In step Se12, the inquiry response status confirmation unit 19 arranges a measure (rescue response) for the subject 1 who has not yet responded.
Then, in step Se13, the inquiry response status confirmation and the response are finished.
In step Se14, the inquiry response status confirmation unit 19 determines whether or not to use another menu. If another menu is to be used (YES at Step Se14), the process returns to Step Se4 and repeats Step Se4 and the subsequent steps. On the other hand, if no other menu is used (NO in step Se14), the user logs out in step Se15 and ends a series of controls related to the inquiry answer status confirmation process.

Here, in the interview answer status confirmation unit 19, the answer pattern, cycle, and frequency are set in advance by the subject 1 and the medical / health manager 31, and the answer status to the interview by the subject 1 is monitored by the interview answer status confirmation unit 19 doing.
The answer status from the subject 1 to the medical inquiry is displayed to the medical / health manager 31 by, for example, a calendar-like table (hereinafter referred to as “calendar table”) as shown in Table 3 below.

In Table 3, “◯” indicates that the subject answered the interview, and “●” indicates that the subject did not answer the interview. “N”, “N + 1” to “N + 8” indicate dates.
For example, if the answer status to the subject's interview is displayed in the calendar table as shown in Table 3, the medical / health manager 31 is answering the question appropriately by examining the calendar table. It is possible to grasp whether or not.
A calendar table as shown in Table 3 can be presented not only to the medical / health manager 31 but also to the service provider 41. The medical / health manager 31 and the service provider 41 can monitor the answer status of the subject 1 with respect to the inquiry. Here, the service provider 41 means, for example, a person or an institution that provides various services other than answers to messages relating to medical examinations and health.

Next, referring to FIG. 14 and FIG. 15, registration of examination / diagnosis of a subject by a medical / health manager will be described.
FIG. 14 shows a configuration of a diagnosis / diagnosis data registration unit (hereinafter referred to as “data registration unit”) 15 of the subject 1 by the medical / health manager 31 in the data center 100.
14, the data registration unit 15 includes a login approval block 151, a login approval result notification block 152, an access authority granting block 153, a data fetching block 154, an external system data conversion processing block 155, and a data storage processing block. 156 and a storage unit 20.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage unit 20 in each of the units 11 to 19, 21, and 22.

The medical / health manager 31 is connected to the login approval block 151 and the login approval result notification block 152 via the interface 5 and the line L15a.
When the login is approved, the login approval result notification block 152 is connected to the access authority granting block 153 via the line L15b, the branch point B, and the line L15c (login approval path).
When the login is not approved, the login approval result notification block 152 is connected to the medical / health manager 31 via the line L15b, the branch point B, the line L15d, and the interface 5B (login non-approved route). .
In FIG. 14, for the convenience of illustration, the medical / health manager 31 is displayed both vertically.
The interface 5 and the interface 5B may be the same.

The login approval block 151 is connected to the storage unit (database) 20 via a line L15e and a line L15f. Login information is transmitted from the login approval block 151 to the storage unit 20 via the line L15e. The verification result is transmitted from the storage unit 20 to the login approval block 151 via the line L15f.
The storage unit 20 is connected to the access authority grant block 153 via the line L15g. Access authority setting information is given from the storage unit 20 to the access authority granting block 153 via the line L15g.

The medical / health manager 31 can connect to the data fetch block 154 via the interface 5 and the line L15h. The medical / health manager 31 can make a data capture request to the data capture block 154.
The data fetch block 154 is connected to the data storage processing block 156 via the line L15i and the line L15j. The diagnosis / diagnosis data is sent from the data acquisition block 154 to the data storage processing block 156 via the line L15i. Then, the data storage result is transmitted from the data storage processing block 156 to the data fetch block 154 via the line L15j.

The data fetch block 154 is connected to the external system data conversion processing block 155 via a line L15k. The external system diagnosis / diagnosis data is transmitted from the data acquisition block 154 to the external system data conversion processing block 155 via the line L15k.
The external system data conversion processing block 155 and the data storage processing block 156 are connected via a line L15m. The converted diagnosis / diagnosis data is sent from the external system data conversion processing block 155 to the data storage processing block 156 via the line L15m.

The data storage processing block 156 and the storage unit 20 are connected via a line L15n. Then, a data registration and its storage request are transmitted from the data storage processing block 156 to the storage unit 20 via the line L15n.
The access authority granting block 153 and the data fetching block 154 are connected by a line L15o. When access is permitted via the line L15o, the access authority is given from the access authority granting block 153 to the data fetching block 154.
The data acquisition block 154 can be connected to the medical / health manager 31 via the line L15p and the interface 5B. Then, the data storage result is transmitted from the data fetch block 154 to the medical / health manager 31.

Next, referring to FIG. 15, the procedure for registering the diagnosis / diagnosis data in the data registration unit 15 will be described.
In step Sf1 of FIG. 15, the data registration unit 15 determines whether or not there is subject examination data stored electronically in another system.
If there is subject examination data stored electronically in another system (step Sf1 is YES), the process proceeds to step Sf2, and if there is no subject examination data electronically saved in another system (step Sf1 is NO), step Proceed to Sf9.

In step Sf2, subject examination data stored in another system is stored and registered in the data registration unit 15.
In step Sf3, the subject examination data stored and registered in step Sf2 is taken out and displayed (step Sf4). In step Sf5, the subject examination data is filed, and the process proceeds to step Sf16.

In step Sf6, the medical / health manager 31 accesses the data registration unit 15 of the data center 100, and inputs the login ID and password in step Sf7.
Here, in FIG. 6, the reason why the process is not connected from the start to step Sf6 is that the case of accessing the system (this system) according to the illustrated embodiment is considered regardless of the presence or absence of data in other systems. . Regardless of the presence or absence of data in other systems, when accessing this system, the procedure starts from step Sf6.
In step Sf8, the login approval block 151 of the data registration unit 15 determines whether or not to approve login.
If the login is not approved (NO in step Sf8), the process returns to step Sf7, and steps Sf7 and subsequent steps are repeated again. On the other hand, if the login is approved (step Sf8 is YES), the process proceeds to step Sf9.

  In step Sf9, a menu screen is displayed. In step Sf10, the data registration unit 15 determines whether or not to take subject examination data electronically stored in another system. If the subject examination data stored electronically in another system is not taken in (NO in step Sf10), the process proceeds to step Sf11. In step Sf11, the subject examination data is displayed on the monitor of the information device (computer or the like) of the medical / health manager 31. After the subject examination data is input and saved in step Sf12, the process proceeds to step Sf17.

In step Sf10, if subject examination data electronically stored in another system is to be taken in (step Sf10 is YES), the process proceeds to step Sf13. In step Sf13, the data registration unit 15 captures and stores external subject examination data. In step Sf14, a job relating to the capture and storage of external subject examination data is selected, and in step Sf15, a data storage destination is selected.
In step Sf16, the data registration unit 15 uploads the subject examination data, and registers the subject examination data in step Sf17.

  In step Sf18, the data registration unit 15 determines whether the registration / storage of the subject examination data has been completed. If registration / storage of the subject examination data has been completed (Sf18 is YES), the process proceeds to step Sf19. On the other hand, if registration / storage of the subject examination data has not been completed (NO in Sf18), the process returns to step Sf15 and repeats step Sf15 and subsequent steps.

  In step Sf19, the data registration unit 15 determines whether to use another menu. If another menu is to be used (YES in step Sf19), the process returns to step Sf9, and step Sf9 and subsequent steps are repeated again. On the other hand, if no other menu is used (NO in step Sf19), the user logs out in step Sf20 and ends a series of controls related to the registration process of the diagnosis / diagnosis data.

Next, referring to FIG. 16 and FIG. 17, a medical / health manager's question answering / diagnosis / diagnosis data browsing of a subject will be described.
FIG. 16 shows the configuration of a subject inquiry answer / diagnosis / diagnosis data browsing unit (hereinafter referred to as a “medical / health manager 31 side data browsing unit”) 16 by a medical / health manager in the data center 100. .
In FIG. 16, the medical / health manager 31 side data browsing unit 16 includes a login approval block 161, a login approval result notification block 162, an access authority granting block 163, an inquiry response / diagnosis / diagnosis data transmission block (hereinafter, 164) and a storage unit 20 are provided.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage units 20 of the units 11 to 19, 21, and 22 in the data center 100.

The medical / health manager 31 is connected to the login approval block 161 and the login approval result notification block 162 via the interface 5 and the line L16a.
When the login is approved, the login approval result notification block 162 is connected to the access authority granting block 163 via the line L16b, the branch point B, and the line L16c (login approval path).
If the login is not approved, the login approval result notification block 162 connects to the medical / health manager 31 via the line L16b, the branch point B, the line L16d, and the interface 5A (login non-approved route).
In FIG. 16, the medical / health manager 31 is displayed above and below for the convenience of illustration.
The interface 5 and the interface 5B may be the same.

The login approval block 161 is connected to the storage unit (database) 20 via a line L16e and a line L16f. The login information is transmitted from the login approval block 161 to the storage unit 20 via the line L16e. The verification result is transmitted from the storage unit 20 to the login approval block 161 via the line L16f.
The storage unit 20 is connected to the access authority grant block 163 via the line L16g. Access authority setting information is given from the storage unit 20 to the access authority granting block 163 via the line L16g.

The medical / health manager 31 can be connected to the data transmission block 164 via the interface 5 and the line L16h. When the access is approved, the medical / health manager 31 requests the data transmission block 164 to browse the inquiry answer / diagnosis / diagnosis data.
The storage unit 20 is connected to the data transmission block 164 via the line L16i and the line L16j. An inquiry answer / diagnosis / diagnosis data is requested from the data transmission block 164 to the storage unit 20 via the line L16i. The inquiry answer / diagnosis / diagnosis data is disclosed from the storage unit 20 to the data transmission block 164 via the line L16j.

The access authority granting block 163 is connected to the data transmission block 164 via the line L16n, and transmits the access authority to the data transmission block 164.
The data transmission block 164 can be connected to the medical / health manager 31 via the line L16o and the interface 5B. The inquiry response / diagnosis / diagnosis data requested by the medical / health manager 31 is transmitted from the data transmission block 164 to the medical / health manager 31 and disclosed.

Next, with reference to FIG. 17, the procedure of the data browsing process in the data browsing unit 16 on the medical / health manager 31 side will be described.
In step Sg1 of FIG. 17, the medical / health manager 31 accesses the medical / health manager 31 side data browsing unit 16 of the data center 100, and inputs the login ID and password in step Sg2.
In step Sg3, the login approval block 161 of the data browsing unit 16 on the medical / health manager 31 side determines whether to approve the login.
If the login is not approved (step Sg3 is NO), the process returns to step Sg2, and steps Sg2 and after are repeated again. On the other hand, if the login is approved (step Sg3 is YES), the process proceeds to step Sg4.

In step Sg4, a menu screen is displayed. In step Sg5, data browsing related to inquiry response data / diagnosis / diagnosis is started. To do.
In step Sg7, the inquiry response data / diagnosis / diagnosis data stored in the system is called. In step Sg8, the inquiry response data / diagnosis / diagnosis data is displayed on the screen of the information device (for example, computer) of the medical / health manager 31. Is displayed.
In step Sg9, the medical / health manager 31 selects the subject 1 who should browse the inquiry response data / diagnosis / diagnosis data.
In step Sg10, the medical / health manager 31 side data browsing unit 16 determines whether or not the browsing target is related to the inquiry response data. If the browsing target is related to the inquiry answer data (YES in step Sg10), the process proceeds to step Sg11.
In step Sg11, the medical / health manager 31 selects an inquiry reply date, and selects the inquiry reply data on the answer date (step Sg12). In step Sg13, the inquiry response data is displayed on the screen of the information device (for example, computer) of the medical / health manager 31. Then, the process proceeds to step Sg17.

In step Sg10, if the browsing target is not related to the inquiry response data (NO in step Sg10), the process proceeds to step Sg14.
In step Sg14, a diagnosis / diagnosis data file is selected, in step Sg15, the diagnosis / diagnosis data stored in the system is selected, and in step Sg16, the corresponding diagnosis / diagnosis data is sent to the medical / health manager 31 information device ( (E.g., computer) screen, and the process proceeds to step Sg17.

In step Sg17, the medical / health manager 31 side data browsing unit 16 determines whether or not the physical condition data of the subject 1 is abnormal (whether or not the subject physical condition is recognized). If the physical condition data of the subject 1 is abnormal (YES in step Sg17), the process proceeds to step Sg18. In step Sg18, the subject 1 is contacted, the physical condition is inquired, or a direct interview is requested. Then, the process proceeds to step Sg20.
If the physical condition data of the subject 1 is not abnormal in step Sg17 (NO in step Sg17), the process proceeds to step Sg19.
In step Sg19, it is determined whether or not to browse data related to other inquiry answers / diagnosis / diagnosis. If data relating to other inquiry answers / diagnosis / diagnosis is to be browsed (YES in step Sg19), the process returns to step Sg8, and step Sg8 and subsequent steps are repeated again. On the other hand, if data related to other inquiry answers / diagnosis / diagnosis is not to be browsed (step Sg19 is NO), the process proceeds to step Sg20.

In step Sg20, the browsing process related to the inquiry response data / diagnosis / diagnosis data is terminated, and the process proceeds to step Sg21.
In step Sg21, it is determined whether or not another menu is to be used. If another menu is to be used (YES in step Sg21), the process returns to step Sg4, and step Sg4 and subsequent steps are repeated again. On the other hand, if no other menu is used (NO in step Sg21), the user logs out in step Sg22 and ends a series of controls related to the data browsing process.

Next, with reference to FIG. 18 and FIG. 19, an explanation will be given on the output of the inquiry answer / diagnosis / diagnosis data of the subject 1 by the medical / health manager 31.
FIG. 18 shows a configuration of an inquiry answer / diagnosis / diagnosis data output unit (hereinafter, referred to as “medical / health manager 31 side data output unit”) 17 of the subject 1 by the medical / health manager 31 in the data center 100. ing.
Here, with regard to the inquiry answer / diagnosis / diagnosis data browsing by the medical / health manager 31, and the inquiry answer / diagnosis / diagnosis data output by the medical / health manager 31, the “login approval” in FIG. 17 and FIG. The contents of the “access right source” from the “access right grant block” are different. Since the output result remains as various media in “output”, the access authority of the person who can perform “output” is set to hardness as compared with the case of “view”. That is, for “output”, higher authority than “view” is required.

18, the medical / health manager 31 side data output unit 17 includes a login approval block 171, a login approval result notification block 172, an access authority granting block 173, an inquiry response / diagnosis / diagnosis data transmission block (hereinafter, 174) and a storage unit 20 (referred to as “data transmission block”).
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage unit 20 in each of the units 11 to 19, 21, and 22 in the data center 100.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the login approval block 171 and the login approval result notification block 172 via the interface 5 and the line L17a.
When the login is approved, the login approval result notification block 172 is connected to the access authority granting block 173 via the line L17b, the branch point B, and the line L17c (login approval path).
When the login is not approved, the login approval result notification block 172 communicates with the participant MR2 (the medical / health manager 31, the system operation manager 41) via the line L17b, the branch point B, the line L17d, and the interface 5BD. Connected (login unapproved route).
The medical / health manager 31 and the system operation manager 41 are displayed on the upper side and the lower side in FIG. 18 for convenience of illustration.
The interface 5 and the interface 5BD may be the same.

The login approval block 171 is connected to the storage unit (database) 20 via a line L17e and a line L17f. Login information is transmitted from the login approval block 171 to the storage unit 20 via the line L17e. Then, the collation result is transmitted from the storage unit 20 to the login approval block 171 via the line L17f.
The storage unit 20 is connected to the access authority granting block 173 via the line L17g, and access authority setting information is given from the storage unit 20 to the access authority granting block 173.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the data transmission block 174 via the interface 5 and the line L17h. When the access is approved, the participant MR2 (the medical / health manager 31, the system operation manager 41) requests the data transmission block 174 to output an inquiry answer / diagnosis / diagnosis data.
The storage unit 20 is connected to the data transmission block 174 via the line L17i and the line L17j. An inquiry answer / diagnosis / diagnosis data is requested from the data transmission block 174 to the storage unit 20 via the line L17i. Then, the inquiry answer / diagnosis / diagnosis data is transmitted from the storage unit 20 to the data transmission block 174 via the line L17j.

The access authority granting block 173 is connected to the data transmission block 174 via the line L17n, and gives the access authority to the data transmission block 174.
The data transmission block 174 is connected to the participant MR2 (the medical / health manager 31 and the system operation manager 41) via the line L17o and the interface 5BD. The data transmission block 174 is configured to disclose the inquiry response / diagnosis / diagnosis data requested by the participant MR2 (medical / health manager 31, system operation manager 41) to the participant MR2.

Next, with reference to FIG. 19, the procedure of the data output process in the medical / health manager 31 side data output unit 17 is demonstrated.
In step Sh1 of FIG. 19, the participant MR2 (medical / health manager 31, system operation manager 41) accesses the data output unit 17 on the medical / health manager 31 side, and in step Sh2, provides a login ID and password. input.
The login approval block 171 of the medical / health manager 31 side data output unit 17 determines whether or not to approve the login (step Sh3).
If the login is not approved (step Sh3 is NO), the process returns to step Sh2, and the steps after step Sh2 are repeated. On the other hand, if the login is approved (step Sh3 is YES), the process proceeds to step Sh4.

In step Sh4, a menu screen is displayed, and in step Sh5, data output related to inquiry response data / diagnosis / diagnosis is started. In step Sh6, the medical / participant MR2 (medical / health manager 31, system operation manager 41) selects the inquiry response data / diagnosis / diagnosis data browsing menu.
In step Sh7, the inquiry response data / diagnosis / diagnosis data stored in the system is called, and in step Sh8, the information device screen of the medical / participant MR2 (medical / health manager 31, system operation manager 41) is displayed. Questionnaire response data, medical examination and diagnostic data are displayed in
In step Sh9, the medical / participant MR2 (the medical / health manager 31, the system operation manager 41) selects the subject 1 to whom the inquiry response data / diagnosis / diagnosis data is to be output.
In step Sh10, the medical / health manager 31 side data output unit 17 determines whether the output target is related to the inquiry answer data. If the output target relates to the inquiry response data (YES in step Sh10), the process proceeds to step Sh11.
In step Sh11, the medical / participant MR2 (medical / health manager 31, system operation manager 41) selects the first day and the last day of the inquiry answer data generation, thereby selecting the inquiry answer data to be output. (Step Sh12). In step Sh13, the inquiry response data is converted to a CSV file, and in step Sh14, the output of the inquiry response data is completed.

In step Sh10, if the output target does not relate to the inquiry response data (NO in step Sh10), the process proceeds to step Sh15.
In step Sh15, an inquiry response data file is selected, and a diagnosis / diagnosis data file to be output is determined in step Sh16. In step Sh17, the inquiry response data is converted into a file and a diagnosis / diagnosis data file is output. If the output of the diagnosis / diagnosis data file is completed in step Sh18, the process proceeds to step Sh19.

In step Sh19, it is determined whether or not to output the inquiry answer data of other subjects. If the other patient's inquiry response data is to be output (YES in step Sh19), the process returns to step Sh8 and repeats step Sh8 again. On the other hand, if the inquiry response data of other subjects is not output (NO in step Sh19), the process proceeds to step Sh20.
In step Sh20, the inquiry answer data / diagnosis / diagnosis data output ends, and the process proceeds to step Sh21.

  In step Sh21, it is determined whether or not another menu is used. If another menu is to be used (YES in step Sh21), the process returns to step Sh4 and repeats step Sh4 and subsequent steps. On the other hand, if no other menu is used (NO in step Sh21), the user logs out in step Sh22 and ends a series of controls relating to the data output process.

Next, system participant registration will be described with reference to FIGS.
FIG. 21 and FIG. 22 show one control flowchart together.
20, the system participant registration unit 21 includes a login approval block 211, a login approval result notification block 212, an access authority granting block 213, a participant data fetching block 214, a data storage processing block 215, and an external system. The data conversion processing block 216, the code granting block 217, the grantor master creation block 218, the authority setting block 6, the inquiry set allocation block 7, and the storage unit 20 are provided.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage unit 20 in each of the units 11 to 19, 21, and 22.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the login approval block 211 and the login approval result notification block 212 via the interface 5 and the line L21a.
When the login is approved, the login approval result notification block 212 is connected to the access authority granting block 213 via the line L21b, the branch point B1, and the line L21c (login approval path).
When the login is not approved, the login approval result notification block 212 communicates with the participant MR2 (medical / health manager 31, system operation manager 41) via the line L21b, the branch point B1, the line L21d, and the interface 5BC. Connect (login unapproved route). In the login non-approval route, a login rejection notification is transmitted from the login approval result notification block 212 to the participant MR2 (medical / health manager 31, system operation manager 41).
The participant MR2 (medical / health manager 31, system operation manager 41) is displayed above and below in FIG. 20 for convenience of illustration.
The interface 5 and the interface 5BC may be the same.

The login approval block 211 is connected to the storage unit (database) 20 via the line L21e and the line L21f. Login information is transmitted from the login approval block 211 to the storage unit 20 via the line L21e. Then, the verification result is transmitted from the storage unit 20 to the login approval block 211 via the line L21f.
The storage unit 20 is connected to the access authority granting block 213 via the line L21g, and access authority setting information is given from the storage unit 20 to the access authority granting block 213.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the participant data capturing block 214 via the interface 5 and the line L21h. Make a participant data capture request.
The participant data fetch block 214 is connected to the data storage processing block 215 via the line L21i and the line L21j. Participant data is sent from the participant data capture block 214 to the data storage processing block 215 via the line L21i. Then, the data storage result is transmitted from the data storage processing block 156 to the participant data fetching block 214 via the line L21j.

The participant data capturing block 214 is connected to the external system data conversion processing block 216 via the line L21m, and transmits external system participant data from the participant data capturing block 214 to the external system data conversion processing block 216. .
The external system data conversion processing block 216 and the data storage processing block 215 are connected via a line L21n, and the participant data is transmitted from the external system data conversion processing block 216 to the data storage processing block 215.
The data storage processing block 215 and the storage unit 20 are connected via a line L21o, and a data registration / storage request is transmitted from the data storage processing block 215 to the storage unit 20.

The access authority granting block 213 and the participant data capturing block 214 are connected via the line L21k, the branch point B2, and the line L211k, and the access authority is sent from the access authority granting block 213 to the participant data capturing block 214.
The access authority granting block 213 and the code granting block block 217 are connected via the line L21k, the branch point B2, the line L212k, the branch point B3, and the line L213k, and the access authority granting block 213 accesses the code granting block block 217. Will be sent.
The access authority granting block 213 and the inquiry set assignment block 7 are connected via the line L21k, the branch point B2, the line L212k, the branch point B3, the line L214k, the branch point B4, and the line L215k. Access authority is sent to the set allocation block 7.
The access authority granting block 213 and the authority setting block 6 are connected via the line L21k, the branch point B2, the line L212k, the branch point B3, the line L214k, the branch point B4, and the line L216k. Access authority is sent to 6.

The storage unit 20 and the authority setting block 6 are connected via a line L21t, a branch point B5, and a line L211t, and participant data is transmitted from the storage unit 20 to the authority setting block 6.
Further, the storage unit 20 and the authority setting block 6 are connected via a line L21u, and authority data is sent from the storage unit 20 to the authority setting block 6 via the line L21u.
The storage unit 20 and the interview set allocation block 7 are connected via the line L21t, the branch point B5, and the line L212t, and the participant data is sent from the storage unit 20 to the interview set allocation block 7.
Further, the storage unit 20 and the interview set allocation block 7 are connected by a line L21s, and the interview set data is sent from the storage unit 20 to the interview set allocation block 7 via the line L21s.

The code assignment block 217 and the storage unit 20 are connected via a line L21p and a line L21r. Participant data is requested from the code grant block 217 to the storage unit 20 via the line L21p. Then, the participant data is sent from the storage unit 20 to the code assigning block 217 via the line L21r.
The code grant block 217 and the grantor master creation block 218 are connected via a line L21q, and a code is given from the code grant block 217 to the grantor master creation block 218 via a line L21q.

The authority setting block 6 and the grantor master creation block 218 are connected via a line L21v, and the authority for creating a master is given from the authority setting block 6 to the grantor master creation block 218.
The interview set assignment block 7 and the grantor master creation block 218 are connected via a line L21w, and the interview set is assigned from the interview set assignment block 7 to the grantor master creation block 218.
The grantor master creation block 218 and the storage unit 20 are connected via a line L21y, and participant master data is sent from the grantor master creation block 218 to the storage unit 20. The storage unit 20 stores the participant master data sent via the line L21y.
The grantor master creation block 218 is connected to the participant MR2 (the medical / health manager 31, the system operation manager 41) via the line L21z and the interface 5BC, and data is transferred from the grantor master creation block 218 to the participant MR2. The storage results of are disclosed.

Next, a procedure related to system participant registration will be described with reference to FIGS.
In step Si1 of FIG. 21, the participant MR2 (medical / health manager 31, system operation manager 41) accesses the system participant registration unit 21 of the data center 100 and inputs the login ID and password (step). Si2).
In step Si3, the system participant registration unit 21 determines whether or not to approve the login ID and password. If the login ID and password are not approved (NO in step Si3), the process returns to step Si2, and step S2 and subsequent steps are repeated. On the other hand, if the login ID and password are approved (YES in step Si3), the process proceeds to step Si4.

In step Si4, a menu screen is displayed. In step Si5, initial setting of system participants is performed. In step Si6, a system participant registration menu is selected.
In step Si7, the system participant registration unit 21 determines whether the registration data exists in another system. If the registration data exists in other systems (YES in step Si7), the process proceeds to step Si8.
In step Si8, the participant data is extracted from another system, and the participant data is displayed in the screen of the information device of the participant MR2 who logged in in step Si9. In step Si10, the participant data is converted to a CSV file, and in step Si11, the CSV file of the participant data is taken into the system. Then, the process proceeds to Step Si13.

If the registration data does not exist in another system at step Si7 (NO at step Si7), the participant data is input at step Si12, and the process proceeds to step Si13.
In step Si13, code master data is acquired, and in step Si14, a unique number is assigned to each participant. Then, the process proceeds to Step Si15 in FIG.

In step Si15 of FIG. 22, the participant data is acquired, and in step Si16, it is determined whether or not the participant is a subject.
If the participant is a subject (step Si6 is YES), the process proceeds to step Si17.
If the participant is not a subject (step Si6 is NO), the process proceeds to step Si25.
In step Si17 (participant is subject: step Si6 is YES), the subject is initially set, in step Si18, the subject is selected, and in step Si19, the subject and the subject manager are set with a string (one-to-one). Connect: link). Then, the process proceeds to step Si20.

In step Si20, an interview set is assigned to the subject from the interview set master, subject master data is acquired in step Si21, and the participant master is stored in the system in step Si22. Then, the process proceeds to Step Si23.
In step Si23, it is determined whether to set another subject. If another subject is to be set (YES in step Si23), the process returns to step Si18, and step S18 and subsequent steps are repeated again. On the other hand, unless another subject is set (step Si23 is NO), the subject initial setting is finished (step Si24), and the process proceeds to step Si40.

In step Si25 (step Si6 is NO: the participant is not a subject), the system participant registration unit 21 determines whether the accessed participant is a subject manager.
If the participant is the subject manager (YES in step Si25), the process proceeds to step Si26.
If the participant is not the subject manager (step Si25 is NO), the process proceeds to step Si33.
In step Si26 (participant is subject manager: step Si25 is YES), initial setting of the subject is performed, the subject is selected in step Si27, and in step Si28, the authority master (authorization setting block 6 in FIG. Set the authority to the subject administrator.

In the next step Si29, subject manager master data is acquired, and the participant master is stored in the system (Si30).
In step Si31, it is determined whether or not another subject administrator is set. If another subject manager is to be set (YES in step Si31), the process returns to step Si27, and step Si27 and subsequent steps are repeated again. On the other hand, if another subject manager is not set (NO in step Si31), the initial setting of the subject manager is ended (step Si32), and then the process proceeds to step Si40.

In step Si33 (step Si25 is NO: the participant is not the subject manager), an initial setting of “other participant” is performed, and in step Si34, the “other participant” who has finished the initial setting is selected, and in step Si35 Authority is set from the authority master (authorization setting block 6 in FIG. 20) for “other participants”.
In step Si36, “other participant” master data is acquired, and in step Si37, the participant master is stored in the system.
In step Si38, it is determined whether or not another “other participant” is set. If another “other participant” is to be set (YES in step Si38), the process returns to step Si34, and step Si34 and subsequent steps are repeated again. On the other hand, if no “other participant” is set (NO in step Si38), the initial setting of “other participant” is terminated (step Si39), and then the process proceeds to step Si40.

  In the next step Si40, the system participant registration unit 21 determines whether to use another menu. If another menu is to be used (YES in step Si40), the process returns to step Si4 in FIG. 21, and step Si4 and subsequent steps are repeated again. If no other menu is used (NO in step Si40), logout is performed in step Si41, and a series of control relating to system participant registration is terminated.

Next, referring to FIGS. 23 and 24, the inquiry / examination set registration will be described.
FIG. 23 shows the configuration of the inquiry / examination set registration unit 22.
In FIG. 23, the inquiry / examination set registration unit 22 includes a login approval block 221, a login approval result notification block 222, an access authority granting block 223, an inquiry set creation block 224, an inquiry creation block 225, and a storage unit 20. And.
The storage unit 20 is the same as the storage unit 20 illustrated in FIG. 3, and is shared with the storage units 20 of the units 11 to 19, 21, and 22 in the data center 100.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the login approval block 221 and the login approval result notification block 222 via the interface 5 and the line L22a.
When the login is approved, the login approval result notification block 222 is connected to the access authority granting block 223 via the line L22b, the branch point B1, and the line L22c (login approval path).
When the login is not approved, the login approval result notification block 222 communicates with the participant MR2 (medical / health manager 31, system operation manager 41) via the line L22b, the branch point B1, the line L22d, and the interface 5BC. Connect (login unapproved route).
The participant MR2 (medical / health manager 31, system operation manager 41) is displayed above and below in FIG. 23 for convenience of illustration.
The interface 5 and the interface 5BC may be the same.

The login approval block 221 is connected to the storage unit (database) 20 via the line L22e and the line L22f. Login information is transmitted from the login approval block 221 to the storage unit 20 via the line L22e. Then, the collation result is transmitted from the storage unit 20 to the login approval block 221 via the line L22f.
The storage unit 20 is connected to the access authority granting block 223 via the line L22g, and access authority setting information is sent from the storage unit 20 to the access authority granting block 223.

The participant MR2 (medical / health manager 31, system operation manager 41) is connected to the interview set creation block 224 via the interface 5 and the line L22h, and when access is approved, the interview set creation block 224. Make an inquiry set creation request.
The participant MR2 is connected to the inquiry creation block 225 via the interface 5 and the line L22i. When access is approved, the participant MR2 makes an inquiry creation request to the interview creation block 225.

The access authority grant block 223 is connected to the interview set creation block 224 via the line L22n, the branch point B2, and the line L221n, and the access authority is given to the interview set creation block 224 from the access authority grant block 223.
The access authority granting block 223 is connected to the inquiry creation block 225 via the line L22n, the branch point B2, and the line L222n, and the access authorization is given from the access authority granting block 223 to the interview creation block 224.

  The storage unit 20 is connected to the inquiry set creation block 224 via a line L22o, a line L22p, and a line L22q. The inquiry data is sent from the storage unit 20 to the inquiry set creation block 224 via the line L22o. Then, the disease list data is sent from the storage unit 20 to the inquiry set creation block 224 via the line L22p. Further, the inquiry set data is sent from the inquiry set creation block 224 to the storage unit 20 via the line L22q.

  The storage unit 20 is connected to the inquiry creation block 225 via a line L22j, a line L22k, and a line L22m. A request for a diagnosis creation template is sent from the inquiry creation block 225 to the storage unit 20 via the line L22j. Then, the inquiry data is sent from the inquiry creation block 225 to the storage unit 20 via the line L22k. The inquiry creation template is sent from the storage unit 20 to the inquiry creation block 225 via the line L22m.

The interview set creation block 224 is connected to the participant MR2 (medical / health manager 31, system operation manager 41) via the line L22t, the confluence G, the line L22u, and the interface 5BC, and the interview set creation block 224. The registration result of the interview set is sent to the participant MR2.
The interview creation block 225 is connected to the participant MR2 (medical / health manager 31, system operation manager 41) via the line L22r, the confluence G, the line L22u, and the interface 5BC, and is involved from the interview creation block 225. The inquiry registration result is sent to the person MR2.

Next, referring to FIG. 24, a procedure related to inquiry / examination set registration will be described.
In step Sj1 of FIG. 24, the participant MR2 (medical / health manager 31, system operation manager 41) accesses the inquiry / diagnosis set registration unit 22 of the data center 100, and in step Sj2, enters the login ID and password. input.
In the next step Sj3, it is determined whether or not to approve the input login. If the input login is not approved (step Sj3 is NO), the process returns to step Si2 and repeats step Sj2 and subsequent steps. On the other hand, if the input log-in is approved (step Sj3 is YES), the process proceeds to step Sj4.

In step Sj4, a menu screen is displayed. In step Sj5, it is determined whether or not to perform an inquiry. If an inquiry is to be performed (step Sj5 is YES), the process proceeds to step Sj6. If an inquiry is not to be performed (step Sj5 is NO), the process proceeds to step Sj14.
In step Sj6, the participant MR2 (medical / health manager 31, system operation manager 41) registers an inquiry, selects an inquiry creation menu in step Sj7, and proceeds to step Sj8.

  In step Sj8, it is determined whether or not the accessing participant MR2 has the authority to create an inquiry. If the accessing participant MR2 has the authority to create an inquiry (YES in step Sj8), the process proceeds to step Sj9. On the other hand, if the accessing participant MR2 has no authority to create an inquiry (NO in step Sj8), the process returns to step Sj4.

In step Sj9, the participant MR2 (medical / health manager 31, system operation manager 41) selects the type of interview, creates an interview table according to the selected interview format (step Sj10), and registers the interview ( In step Sj11), an inquiry master is registered (step Sj12), and then the inquiry registration process is terminated (step Sj13).
Then, the process proceeds to step Sj23.

In step Sj14 (NO in step Sj5: no inquiry is performed), it is determined whether or not to create an inquiry set. If an inquiry set is to be created (YES in step Sj14), the process proceeds to step Sj15.
On the other hand, when an inquiry set is not created (step Sj14 is NO), the process proceeds to step Sj23.
In step Sj15 (when creating an interview set: YES in step Sj14), it is determined whether the accessing participant has authority to create an interview set. If the accessed participant has the authority to create an inquiry set (YES in step Sj15), the process proceeds to step Sj16. On the other hand, if the accessing participant does not have authority to create an inquiry set (NO in step Sj15), the process returns to step Sj4.

In step Sj16 (when the accessing participant has the authority to create an interview set), the interview set is registered, and the participant MR2 (medical / health manager 31, system operation manager 41), in step Sj17, the disease name / inquiry The disease name / inquiry purpose is selected from the purpose name master, and the inquiry is selected in step Sj18.
In the subsequent step Sj19, the participant MR2 creates an interview set (answers the matters described in the interview set), and registers the interview set created in step Sj20. In step Sj21, the inquiry set master is registered. In step Sj22, the process related to the inquiry set registration is terminated, and the process proceeds to step Sj23.

  In step Sj23, it is determined whether or not another menu is to be used. If another menu is to be used (step Sj23 is YES), the process returns to step Sj2, and steps Sj2 and after are repeated again. On the other hand, if no other menu is used (Sj23 is NO), the user is logged out in step Sj24, and a series of controls relating to the inquiry / examination set registration is terminated.

Regarding the inquiry / diagnosis set registration, each inquiry consists of an unchangeable “question number”, “question”, “answer input field or answer option”, “threshold value”, and “weighting value”. This structure, its contents, and the order of the list in the individual interviews that are master-listed on this system are to maintain the consistency, accuracy, significance, continuity, and comparability of the questionnaire response data. , Never changed or updated.
The method of using the "weighting value" to give a score to an inquiry answer uses a method that outputs the inquiry answer data and processes it outside this system.

  Individual interviews are created by a person who is suitable for creating an interview, such as a medical / health manager, and are registered on the system according to a specified order in the order of creation. A person who is suitable for organizing an interview set such as a medical / health manager selects an optimal (individual) interview for each target disease from the interview master list and organizes the interview set.

Table 4 illustrates an interview set.

The interview set prepares N times the number of subjects (N is the number of types of diseases, physical condition information, and other collection purposes).
General interviews such as body temperature interviews are likely to be employed in many types of interview sets.
When a certain subject suffers from a plurality of diseases and a number of interview sets corresponding to the type of the disease are assigned, the same interview may be adopted for the plurality of interview sets. In such a case, an interview set in which only one overlapping interview remains is assigned to the subject (a subject suffering from a plurality of diseases).
For example, when a question set A and a question set B shown in Table 4 are assigned to a subject in combination, the question code 1 is duplicated in the question set A and the question set B. In this case, the interview set for the subject is composed of four types of interviews of interview codes 1, 2, 3, and 5. In the interview set for the subject, two interview codes 1 are not included.

According to the illustrated embodiment, the subject 1 and his / her medical / health manager 31 can establish a remote online relationship.
Subject 1 uses information terminal equipment that can be easily obtained without a direct interview with medical / health manager 31, and is able to monitor the subject's condition on a daily, continuous, and long-term basis ( (To medical / health manager).
Then, the physical condition information of the subject 1 who has transmitted the physical condition to the medical / health manager 31 through the illustrated embodiment can be stored as a database from the initial stage (occurrence time). And useful information regarding the health of the subject 1 can be obtained relatively easily from the physical condition information stored in the database.
In particular, according to the illustrated embodiment, since the physical condition information of the subject 1 is continuously collected every day, it is possible to know a change in physical condition over time.

When the subject 1 regularly diagnoses or directly interviews the medical / health manager 31, the physical condition information that the subject 1 himself / herself (to the medical / health manager 31) relies heavily on the memory of the subject 1 Yes, often inaccurate and unclear.
On the other hand, the physical condition information collected by the illustrated embodiment can ensure objectivity by answering the interview / interview set, so that the subject 1 diagnoses or directly interviews the medical / health manager 31. Compared to the case of performing, the physical condition information obtained from the subject 1 is accurate and clear. And when the subject 1 makes a diagnosis or direct interview with the medical / health manager 31 based on the physical condition information collected by the illustrated embodiment, the diagnosis or direct interview becomes more effective.

In the illustrated embodiment, medical records, treatment contents, medical facilities, treatment facilities, and other medical / health managers (natural persons or institutions) 31 issued and created by the subject 1 such as medical records, images, prescriptions, etc. The digitized data is stored in an area prepared as storage in the data center 100.
By storing the digitized data as described above, according to the illustrated embodiment, the subject 1 can obtain his / her health information such as physical condition information, health status, treatment, and medication type by himself / herself. , It becomes possible to centrally manage. The subject 1 can manage the information about his / her health in a unified manner, so that the subject 1 can hold data such as his / her physical condition information and can own a personal health record by the subject 1 himself / herself. Become.

Then, when the subject 1 starts a new treatment at the new medical institution 3, etc., the physical condition information and data stored as described above according to the illustrated embodiment is used as a doctor or the like at the new medical institution 3. If this information is disclosed and provided to the medical / health manager 31, it will help to execute the new treatment safely and effectively.
Here, according to the illustrated embodiment, by managing the body condition information of the subject 1 in a unified manner, even when there is a change in the treatment period, a so-called “contraindication” (for example, a combination of drugs in which side effects are a concern) Can be prevented from being administered to the same subject 1 or the like.

  Further, according to the illustrated embodiment, the subject 1 can easily obtain his / her physical condition information by using an information terminal device which can be easily obtained by answering the interview and the interview set in a simple manner. -Can be transmitted to the health manager 31. Therefore, compared with the prior art, the economic, mental, and physical burdens required for the subject 1 to transmit physical condition information to the doctor 31 in charge can be reduced. Then, it is promoted that the subject 1 continuously reports the physical condition information to the medical / health manager 31.

The illustrated embodiment can be applied not only to the management of the prognosis of patients with illnesses but also as a management system for general health information and physical condition information.
Furthermore, in the illustrated embodiment, by using a function related to so-called “correspondence” such as message transmission / reception as a value-added service, the subject 1 is motivated to answer an inquiry (inquiry set). Can be maintained and improved.
Alternatively, according to the illustrated embodiment, the management of the physical condition and the follow-up in the prognosis of the treatment (including organ transplantation, etc.) of patients suffering from injuries and diseases, the effect measurement and verification of the medication treatment are performed continuously and over a long period of time. Can be implemented.

  It should be noted that the illustrated embodiments are merely examples, and are not intended to limit the technical scope of the present invention.

DESCRIPTION OF SYMBOLS 1 ... Test subject 6 ... Authority setting block 7 ... Interview set allocation block 11 ... Message transmission / reception unit 12 ... Physical condition registration unit 13 ... Interview answer / diagnosis / diagnosis data browsing unit by test subject 14 ··· Interrogation response / diagnosis / diagnosis data output unit 15 by test subject ··· Examination / diagnosis data registration unit 16 for subject by medical / health manager ··· Interview / answer / examination of subject by medical / health manager Diagnostic data browsing unit 17 ... Interrogation / examination / diagnosis / diagnosis data output unit 18 of the subject by the medical / health manager ... Message transmission / reception unit 19 ... Interrogation / answer status confirmation unit 20 from the subject ... Storage unit 21 ... System participant registration unit 22 ... Interview / examination set registration unit

Claims (2)

An area (E2) where the medical / health manager (31) and the system operation manager (41) exist, and an area (100) for storing data such as physical condition information of the subject (1), etc.
Data such as physical condition information of the subject (1) transmitted to the storage area (100) is stored in the area (E2) where the medical / health manager (31) and the system operation manager (41) exist. Means (PC) having a function of acquiring the participants (31, 41);
Means (17) having a function of outputting data such as physical condition information of the subject etc. transmitted to the storage area (data center 100) by the medical / health manager (31) and the system operation manager (41) When,
Whether the subject is in an abnormal situation in which data such as physical condition information of the subject etc. transmitted to the storage area (100) is given to the medical / health manager (31) and the subject etc. does not answer continuously An inquiry response status confirmation unit (19) having a function (Se7) for displaying an inquiry response status of the subject or the like necessary for determining (Se8),
Means (16, 17) having a function of providing data such as physical condition information of the subject (1) transmitted to the storage area (data center 100) to the subject,
The medical / health manager (31) and the system operation manager (41) have means (21) having a function of registering the authority, and the means (21) grants access authority to which access authority setting information is given. The block (213), the authority setting block (6) to which the authority data is sent and the access authority is sent from the access authority granting block (213), and the authority for creating the master are given from the authority setting block (6) and the master data If the accessing person is a medical / health manager (31) and a system administrator (41), authority is set (Si28, Si35), and the master data is output. In the participant registration method in the health management system (500) having the function of storing (Si30, Si37),
Whether to approve the login ID and password (Si2) of (1) medical / health manager (31), system administrator (41), or subject (1) who accessed the storage area (100) If it is judged (Si3) and approved (Si3 is YES), the menu screen is displayed (Si4), and the initial stage of the medical / health manager (31), system administrator (41), or subject (1) Make settings (Si5), select the system participant registration menu (Si6),
It is determined whether or not the data of the medical / health manager (31), the system operation manager (41), the subject, etc. (1) accessed by the system participant registration unit (21) also exists in other systems ( Si7), medical / health manager (31), system operation manager (41) or subject etc. (1) data also exists in other systems (Si7 is YES) Data of health manager (31), system operation manager (41) or subject etc. 1 is retrieved (Si8), and the medical / health manager (31), system operation manager (41) or subject etc. who logged in the data 1 is displayed on the screen of the information device (Si9), converted into a CSV file (Si10), and the CSV file of the data is imported into the health management system (500) (Si 1),
If data of the accessed medical / health manager (31), system operation manager (41) or subject (1) does not exist in other systems (Si7 is NO), the medical / health manager (31) The system administrator (41) or the subject (1) data is inputted (Si12), the code master data is given (Si13), the individual medical / health administrator (31), the system administrator (41) ) Or a specific number for the subject (1) (Si14), and the logged-in medical / health manager (31), the system operation manager (41) or the subject (1) acquires the participant data ( Si15),
It is determined whether the person who acquired the participant data is the subject (1) (Si16),
If it is a subject (Si6 is YES), the initial setting of the subject is performed (Si17), the subject is selected (Si18), the subject and the medical staff (31) are set with a string (Si19), and from the interview set master Interview set is assigned to the subject (Si20), subject master data is given (Si21), subject master data is stored in the health management system (500) (Si22),
It is determined whether or not to set another subject (Si23), and if no other subject is set (Si23 is NO), the subject initial setting is terminated (Si24),
If the person who has acquired the participant data is not a subject (Si6 is NO), the system participant registration unit (21) determines whether the person who has acquired the participant data is a medical / health manager (31). Judgment (Si25)
If the person who acquired the participant data is a medical / health manager (31) (YES in Si25), the medical / health manager (31) is initialized (Si26), and the medical / health manager (31) (Si27) and set the authority to the medical / health manager (31) from the means (21) having the function of registering the authority with the medical / health manager (31) and the system operation manager (41). (Si28), subject administrator master data is given (Si29), medical / health manager master data is stored in the health management system (500) (Si30),
It is determined whether or not another medical / health manager (31) is set (Si31), and if no other medical / health manager (31) is set (Si31 is NO), the medical / health manager ( 31) The initial setting is finished (Si32)
If the person who acquired the participant data is not the medical / health manager (31) (Si25 is NO), the system administrator (41) is initialized (Si33), and the system administrator (41) is selected. (Si34), the authority is set to the system administrator (41) from the means (21) having the function of registering the authority of the medical / health administrator (31) and the system administrator (41) (Si35) , Giving the master data to the system administrator (41) (Si36), storing the system administrator master data in the health management system (500) (Si37),
It is determined whether or not to set another system operation manager (41) (Si38). If no other system operation manager (41) is set (Si38 is NO), the system operation manager (41) is determined. The registration method in the health management system is characterized in that the initial setting of the health care system is terminated. The health management system (500) has an area (E1) where the subject (1) etc. exists,
The first area (E1) is a means (Hh) having a function of transmitting data such as information on the physical condition generated by the subject (1) and the like to the area (100) storing data such as the physical condition information. , End Ht).

Images