Information processing system, information processing device, information processing method, information processing program, communication terminal, and control method and control program thereof

Abstract

To narrow down a subject considering a health care state and associate selection of a subject with selection of a public health service, thereby efficiently managing the public health service.SOLUTION: An information processing system comprises: a subscriber selection unit that selects, from subscribers who subscribe an insurance, a subscriber who needs to be provided with a public health service; a public health service selection unit that selects a public health service to be provided to the subscriber; and a control unit that controls to associate the selected subscriber with the selected public health service. The subscriber selection unit has: an acquisition unit that acquires individual attribute information related to the subscriber, health state related information including medical examination information collected related to the subscriber, and health care related information including receipt information from a medical institution for the subscriber; a derivation unit that derives a risk level of subscriber's health on the basis of the health state related information; an evaluation unit that evaluates a health care state of the subscriber on the basis of the health care related information; and a selection unit that selects the subscriber who needs to be provided with the public health service considering the risk level and the health care state.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a technology for managing health care services. [Background technology]

[0002] In the above technical field, Patent Document 1 discloses a technology for implementing health care projects for insured persons, evaluating the projects based on the recipients' medical receipt data and medical examination result data, and supporting the implementation of the projects. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-177644 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the technology described in the above document, high-risk individuals for the target symptoms are selected as the subjects of the health care program, and the narrowing down of the subjects is not considered in terms of health management status.Furthermore, the efficient implementation of the health care program by matching the selection of subjects with the selection of the health care program is not considered.

[0005] An object of the present invention is to provide a technique for solving the above-mentioned problems. [Means for solving the problem]

[0006] In order to achieve the above object, an information processing system according to the present invention comprises: An acquisition unit that acquires medical history of each of a plurality of subscribers who are insured by an insurer and health program participation details of each of the plurality of subscribers; a derivation unit that derives an awareness level as a willingness to participate in a health service for each of the plurality of subscribers based on a combination of the medical history and the content of the participation in the health service; A selection unit that selects subscribers to whom health services should be offered according to the awareness level; It is an information processing system equipped with the above.

[0007] The acquisition unit: An acquisition step of acquiring medical history of each of a plurality of subscribers who are insured by the insurer and health program participation details of each of the plurality of subscribers; The derived portion is a derivation step of deriving an awareness level as a willingness to participate in a health service for each of the plurality of subscribers based on a combination of the medical history and the content of participation in the health service; The selection department: A selection step of selecting subscribers to whom health services should be offered according to the awareness level; The present invention relates to an information processing method. Effect of the Invention

[0013] According to the present invention, health care services can be managed efficiently. [Brief description of the drawings]

[0014] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to a first embodiment of the present invention. [Figure 2A] FIG. 11 is a diagram showing a configuration of an information processing system including a health care business management support server as an information processing device according to a second embodiment of the present invention. [Figure 2B] FIG. 11 is a diagram showing an outline of the operation of an information processing system including a health care business management support server as an information processing device according to a second embodiment of the present invention. [Figure 2C] FIG. 11 is a diagram showing a configuration of a database included in a health care business management support server serving as an information processing device according to a second embodiment of the present invention. [Figure 2D] FIG. 11 is a diagram showing the configuration of a selection table in a health care business management support server as an information processing device according to the second embodiment of the present invention. [Figure 3A]FIG. 11 is a sequence diagram showing an operation procedure for collecting medical information in an information processing system including a health care business management support server as an information processing device according to a second embodiment of the present invention. [Figure 3B] FIG. 11 is a sequence diagram showing an operation procedure for selecting a health service associated with a selected subscriber in an information processing system including a health service management support server as an information processing device according to the second embodiment of the present invention. [Figure 3C] 13 is a flowchart showing a processing procedure for selecting a health service associated with a selected subscriber in an information processing system including a health service management support server as an information processing device according to a second embodiment of the present invention. [Figure 3D] FIG. 11 is a sequence diagram showing detailed operation procedures for selecting subscribers who need to be provided with health care services in an information processing system including a health care service management support server as an information processing device according to a second embodiment of the present invention. [Figure 3E] FIG. 11 is a sequence diagram showing an operation procedure for selecting a subscriber associated with a selected health service in an information processing system including a health service management support server as an information processing device according to the second embodiment of the present invention. [Figure 3F] 13 is a flowchart showing a processing procedure for selecting a subscriber associated with a selected health service in an information processing system including a health service management support server as an information processing device according to a second embodiment of the present invention. [Figure 3G] FIG. 11 is a sequence diagram showing a detailed operation procedure of selecting a subscriber associated with a health service in an information processing system including a health service management support server as an information processing device according to a second embodiment of the present invention. [Figure 4A] FIG. 11 is a diagram showing an outline of an operation for selecting subscribers who require the provision of health care services by a health care service management support server as an information processing device according to the second embodiment of the present invention. [Figure 4B] FIG. 11 is a diagram showing an overview of a risk level derived taking into consideration a health management situation according to the second embodiment of the present invention. [Figure 5A] FIG. 11 is a block diagram showing a functional configuration of a cloud server according to the second embodiment of the present invention. [Figure 5B] FIG. 11 is a block diagram showing the functional configuration of a virtual health care project management support server as an information processing device generated in a cloud server according to a second embodiment of the present invention. [Figure 6] FIG. 11 is a diagram showing the configuration of an acquisition database according to the second embodiment of the present invention. [Figure 7A] FIG. 11 is a diagram showing the configuration of a processing database according to the second embodiment of the present invention. [Figure 7B] FIG. 11 is a diagram showing an example of determining target persons who are subscribers who require health care services in accordance with the second embodiment of the present invention. [Figure 7C] FIG. 11 is a diagram showing another example of determining targets who are subscribers who require health care services in accordance with the second embodiment of the present invention. [Figure 7D] FIG. 11 is a diagram showing the configuration of an awareness level derivation table for deriving the awareness level of a subscriber according to the second embodiment of the present invention. [Figure 8] FIG. 11 is a diagram showing the configuration of a health care service target selection table according to the second embodiment of the present invention. [Figure 9] FIG. 11 is a block diagram showing a hardware configuration of a virtual health care business management support server as an information processing device according to a second embodiment of the present invention. [Figure 10A] 13 is a flowchart showing a processing procedure of a virtual health care business management support server serving as an information processing device according to the second embodiment of the present invention. [Figure 10B] 10 is a flowchart showing the procedure of a management data acquisition process according to a second embodiment of the present invention. [Figure 10C] 13 is a flowchart showing the procedure of a health care project recipient selection process according to the second embodiment of the present invention. [Figure 11] FIG. 11 is a block diagram showing a functional configuration of a communication terminal according to a second embodiment of the present invention. [Figure 12A] 10 is a flowchart showing a processing procedure of a communication terminal according to a second embodiment of the present invention. [Figure 12B] 13 is a flowchart showing the procedure of health care service recipient request processing according to the second embodiment of the present invention. [Figure 13]FIG. 11 is a diagram showing an outline of the operation of an information processing system including a health care business management support server as an information processing device according to a third embodiment of the present invention. [Figure 14] FIG. 11 is a sequence diagram showing the operation procedure of an information processing system including a health service management support server as an information processing device according to the third embodiment of the present invention. [Figure 15] FIG. 13 is a block diagram showing the functional configuration of a virtual health care business management support server as an information processing device in a cloud server according to a third embodiment of the present invention. [Figure 16] FIG. 13 is a diagram showing the configuration of an acquisition database according to the third embodiment of the present invention. [Figure 17A] FIG. 13 is a diagram showing the configuration of a processing database according to the third embodiment of the present invention. [Figure 17B] FIG. 11 is a diagram showing the configuration of an awareness level derivation table for deriving the awareness level of a subscriber according to the second embodiment of the present invention. [Figure 18] FIG. 13 is a diagram showing the configuration of a health care service target selection table according to the third embodiment of the present invention. [Figure 19A] 13 is a flowchart showing the procedure of a management data acquisition process according to the third embodiment of the present invention. [Figure 19B] 13 is a flowchart showing the procedure of a health care project recipient selection process according to the third embodiment of the present invention. [Figure 20] FIG. 13 is a diagram showing an outline of the operation of an information processing system including a health care business management support server as an information processing device according to a fourth embodiment of the present invention. [Figure 21] FIG. 13 is a block diagram showing the functional configuration of a virtual health care business management support server as an information processing device in a cloud server according to a fourth embodiment of the present invention. [Figure 22] FIG. 13 is a diagram showing the configuration of a processing database according to the fourth embodiment of the present invention. [Figure 23A] FIG. 13 is a diagram showing the configuration of a health care project target selection table according to the fourth embodiment of the present invention. [Figure 23B] FIG. 13 is a diagram showing an example of calculating a required level of health care services according to the fourth embodiment of the present invention. [Figure 23C] FIG. 13 is a diagram showing the configuration of a required level derivation table for deriving a required level according to the fourth embodiment of the present invention. [Figure 24] 13 is a flowchart showing the procedure of a health care project recipient selection process according to the fourth embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. However, the components described in the following embodiment are merely examples, and are not intended to limit the technical scope of the present invention.

[0016] The following terms used in this specification are defined as follows. "Insurer" includes "public insurer" and "private insurer". For example, "public insurer" includes "health insurance association". "Target" refers to insurers who need health services among those who are insured by an insurer. "Health promotion business" is also called "health business business". "Individual attribute information" refers to information related to the insurer, such as gender, age, occupation, position, and working situation. "Health status related information" includes information that indicates the health status, such as information that indicates the health status, such as medical checkup information and stress check. "Health management related information" includes information that indicates the health management status and the intention to participate in health management actions, such as prescription information, health program participation status, and lifestyle. "Health management status" includes the status of working on health management, such as "treatment status" based on prescription information, health program participation status, and "participation content" based on lifestyle. "Health program related information" is information that indicates the implementation content of health programs, regardless of the implementer.

[0017] [First embodiment] An information processing system 100 according to a first embodiment of the present invention will be described with reference to Fig. 1. The information processing system 100 is a system for managing health care services.

[0018] As shown in Fig. 1, the information processing system 100 includes a subscriber selection unit 101, a health service selection unit 102, and a control unit 103. The subscriber selection unit 101 selects subscribers who need to be provided with health services among the subscribers who subscribe to the insurer. The health service selection unit 102 selects health services to be provided to the subscribers who subscribe to the insurer. The control unit 103 controls the association of the selected health service with the selected subscriber.

[0019] The subscriber selection unit 101 includes an acquisition unit 111, a derivation unit 112, an evaluation unit 113, and a selection unit 114. The acquisition unit 111 acquires personal attribute information on the subscriber who joins the insurer, health condition related information including medical checkup information collected on the subscriber, and health management related information including medical receipt information for the subscriber. The derivation unit 112 derives the subscriber's health risk level based on the health condition related information. The evaluation unit 113 recognizes the subscriber's health management situation based on the health management related information. The selection unit 114 selects subscribers who need to be provided with health services from among the subscribers who join the insurer, taking into consideration the risk level and the health management situation.

[0020] According to this embodiment, the health care program can be managed efficiently by narrowing down the target persons for the health care program in consideration of the health management status of the subscriber and matching the selection of the target persons with the selection of the health care program.

[0021] [Second embodiment] Next, a health business management support server as an information processing device according to a second embodiment of the present invention will be described. The health business management support server according to this embodiment controls the association of the selection of the subscriber who needs the provision of the health business with the selection of the health business to be provided. The health business management support server considers the risk level derived based on the health condition related information including the medical checkup information and the health management situation recognized based on the health management related information including the medical receipt information, particularly in selecting the subscriber who needs the provision of the health business. The health business management support server then manages the health business by selecting the subscriber who needs the provision of the health business. That is, as the selection condition of the subscriber who needs the provision of the health business, risk designation for designating the type of risk and health management situation designation for designating the health management situation are performed. The health management situation includes the treatment content extracted from the medical receipt information and the subscriber's awareness level of the treatment derived from the medical receipt information. The risk level may be derived by further considering the health management related information. The subscriber who needs the provision of the health business is selected without exclusion due to the medication information included in the health management related information or the absence of a specific risk. The health service management support server of the present embodiment has a database that stores subscribers in association with health condition-related information and health management information. Then, it presents information on subscribers who need to be provided with health services. The presentation includes presenting a list of subjects who need to be provided with health services to the operator and sending an email to notify the subscriber that they have been selected as needing to be provided with health services. Furthermore, subscribers who need to be provided with health services are selected in consideration of the risk levels of multiple types of related risks and their treatment status. That is, a treatment status designation is performed to designate a treatment status as a selection condition for subscribers who need to be provided with health services. The subscribers who need to be provided with health services include various necessary levels such as subscribers who need to be provided with services and subscribers who are desirable to be provided with services, and this may be presented. Furthermore, the health services to be provided include various participation levels such as health services that should be participated in and health services that are desirable to participate in, and this may be presented.

[0022] Information Processing System The configuration and operation of an information processing system 200 including a health care business management support server 210 as an information processing device will be described below with reference to Figures 2A to 3G. The sequences and flowcharts in Figures 3A to 3G show data flows and processing procedures in the information processing system 200, and include online processing and offline processing.

[0023] (System Configuration) FIG. 2A is a diagram showing the configuration of an information processing system 200 including a health care project management support server 210 as an information processing device according to this embodiment.

[0024] Information processing system 200 includes health care business management support server 210 as an information processing device, insurers 220 including a plurality of insurers 221-22m, and health promotion agents 230 including a plurality of health promotion agents 231-23n. Information processing system 200 also includes communication terminals 240 that receive support from health care business management support server 210, including an operator's communication terminal 241 and a subscriber's communication terminal 242.

[0025] The health business management support server 210 includes an insurer database 211 that stores health information (including personal attribute information, health condition related information such as medical checkup information, and health management related information such as medical receipt information) related to the subscriber submitted by each insurer 221-22m in a confidential manner. The health business management support server 210 also includes a health business database 212 that stores health businesses proposed by each health promotion business operator 231-23n. Note that health businesses may be proposed by the insurer 220 and stored in the health business database 212. The health business management support server 210 matches a process of selecting a target person who is a subscriber who needs a health business by referring to the health information stored in the insurer database 211 with a process of selecting a health business stored in the health business database 212 and recommending it to an insurer or a target person. Then, the server collects the implementation history of the health business, the participation history of the subscriber in the health business, and the change in the risk level of the subscriber who participated in the health business, and the like, to evaluate the health business, and improves the creation of a health business plan at the health promotion business operator 231-23n. In addition, the selection method of health services and the selection method of the target subscribers who need health services are evaluated, and more appropriate health services are implemented to improve productivity by maintaining the health of subscribers. In other words, participation history designation is performed to designate the participation history of insurance services as a selection condition for subscribers who need health services.

[0026] The communication terminals 241, 242 execute a health care business management application to connect to the health care business management support server 210 and receive support from the health care business management support server 210 such as the history of health information, selection of subjects who are subscribers who require health care services, and selection of recommended health care services.

[0027] (Operation overview) Fig. 2B is a diagram showing an outline of the operation of an information processing system 200 including a health service management support server 210 as an information processing device according to this embodiment. Note that, in the outline of the operation in Fig. 2B, display screens of communication terminals 241 and 242 are shown, but these do not show successive screen transitions, and scenes characteristic of this embodiment are selected and shown.

[0028] Fig. 2B shows an outline of the operation in which the health care project management support server 210 selects subjects who need health care projects from among the insurer's subscribers and recommends appropriate health care projects to the selected subjects based on the selection conditions set from the communication terminal 241. Fig. 2B also shows an outline of the operation in which, for the health care project selected for recommendation, subjects who need the selected health care project are selected and the health care project is recommended.

[0029] Display screen 251 is a log-on screen for the health service management application. In display screen 252, selection conditions are set to select subjects who require health services. In display screen 253, subscribers selected as subjects who require health services based on the selection conditions and "recommended health services" appropriate for the selected subscribers are selected and introduced. In display screen group 254, the health services to be implemented are notified to each subscriber by facsimile notification 250 or to the subscriber's communication terminal 242. In addition, the terminal of health service provider (health promotion provider) 230 is notified of the evaluation results of the proposed health services. When a health service is proposed from communication terminal 241 or 242, the evaluation results of the health service are notified to communication terminal 241 or 242.

[0030] On the other hand, the display screen 255 displays "recommended health services" and allows the operator to select one. On the display screen 256, subscribers who need the selected health service are displayed as potential participants. Then, the display screen group 254 is displayed.

[0031] (Database) FIG. 2C is a diagram showing the configuration of a database included in the health care project management support server 210 serving as an information processing device according to this embodiment.

[0032] The upper diagram of FIG. 2C shows the configuration of the insurer database 211 held by the health business management support server 210. Using the insurer database 211, the health business management support server 210 selects subjects who need health business from the insurers based on the selection conditions set from the communication terminal 241. The insurer database 211 stores subject selection conditions 262 and the number of selected subjects 263 for each insurer A to N in association with a combination condition ID 261 for identifying the insurer and its selection conditions. The subject selection conditions 262 include risk conditions that are risk conditions of the insurer who needs health business, the treatment conditions that the insurer is receiving and the participation status of the insurer in the health business, the necessary level of health business, etc. The subject selection conditions 262 are not limited to the conditions described above. For example, they may include the awareness level described below.

[0033] The lower diagram of FIG. 2C shows the configuration of the health care project database 212 possessed by the health care project management support server 210. Using the health care project database 212, the health care projects proposed by the health promotion business 230 or the insurer 220 are associated with the subjects who need the health care projects of each insurer. The health care project database 212 stores a health promotion business (or insurer) ID 272, health care project related information 273, and health care project participation conditions 274 in association with a health care project ID 271 for identifying the health care project proposed by the health promotion business 230. The health care project related information 273 includes the number of participants (capacity) in the health care project, the implementation period, implementation interval, the cost of implementing the health care project, the detailed contents of the health care project, and the like. In addition, the health care project participation conditions 274 store the conditions of the subscribers who are determined to need to participate in this health care project. It is preferable that the health care project participation conditions 274 correspond to the subject selection conditions 262, but the association between them may be different.

[0034] (Selection table) FIG. 2D is a diagram showing the configuration of a selection table in the health care project management support server 210 serving as an information processing device according to this embodiment.

[0035] The upper diagram of FIG. 2D is a health care project selection table 280 for selecting and implementing a health care project recommended for participation by the insurer selected based on the selection conditions. The health care project selection table 280 stores health care projects 283 recommended for the insurer of the number of subjects 282 selected based on the insurer condition ID 281 and the subject selection condition 262 shown in FIG. 2C, and implementation results 284 of the selected and implemented health care projects. The recommended health care project 283 includes a health care project ID, its priority, and the like. In addition, in the implementation results 284, when multiple health care projects are implemented, the implementation results of each are stored. Furthermore, the implementation results 284 may store an implementation history including the progress of each health care project participant.

[0036] The center diagram in Fig. 2D is a target selection table 285 for selecting insurers and their subscribers who are desired to participate in a proposed or recommended health program. The target selection table 285 stores participating insurers 287 that are suitably applied and implementation results 288 of the health program in association with the health program ID 286 shown in Fig. 2C. The participating insurers 287 include targets selected based on the insurer ID and health program participation conditions 274.

[0037] The lower diagram of Fig. 2D is a health care project evaluation table 290 for evaluating the implementation of each health care project and proposing improvements. The health care project evaluation table 290 stores an implementation history 292, each implementation evaluation 293, a total evaluation 294, and an improvement proposal 295 in association with a health care project ID 291.

[0038] (Operation sequence) FIG. 3A is a sequence diagram showing the operation procedure of medical information collection in an information processing system 200 including a health care business management support server 210 as an information processing device according to this embodiment.

[0039] In step S301, the health care project management support server 210 provides the health care project management application to the communication terminals 241, 242. Then, in step S302, the communication terminals 241, 242 cooperate with the health care project management support server 210 to start up the health care project management application.

[0040] In step S303, the insurer 220 submits the attribute information of the registered individual (subscriber) and the health condition-related information including the acquired medical checkup information to the health care project management support server 210. In step S304, the health care project management support server 210 stores and holds the individual attribute information and health condition-related information submitted by the insurer 220 in a database.

[0041] In step S305, insurer 220 submits health management related information including medical receipt information and the like to health business management support server 210. Health business management support server 210 stores and holds the health management related information submitted by insurer 220 in a database. Note that health condition related information or health management related information extracted from stress checks, questionnaire information, and the like may be transmitted from communication terminals 241, 242 to health business management support server 210 at any time in step S307.

[0042] Fig. 3B is a sequence diagram showing the operation procedure of selecting a health service associated with a selected subscriber in an information processing system 200 including a health service management support server 210 as an information processing device according to this embodiment. In Fig. 3B, when conditions for selecting a subscriber who needs a health service are set from an operator's communication terminal 241, an appropriate health service proposed by a health promotion company 230 is selected for the subscriber who needs a health service, and information about the health service is notified to the subscriber's communication terminal 242 to encourage participation. Then, the operation procedure is shown in which the results or effects of the health service are reflected in subsequent subscriber searches and health service selections.

[0043] In step S311, the communication terminal 241 inputs judgment conditions that are standards for selecting subscribers who require health care services, such as a risk level threshold. In step S312, the health care service management support server 210 sets the received judgment conditions. In step S313, the health promotion agent 230 proposes the generated health care service plan. In step S314, the health care service management support server 210 sets health care service related information and health care service selection conditions for selecting the health care services as the health care service plan.

[0044] In step S315, the communication terminal 241 inputs subject selection conditions such as risk type and medical examination content for selecting subscribers who need health services. In step S316, the health service management support server 210 selects subjects who need health services and their groups according to the various subject selection conditions. Then, in step S317, the health service management support server 210 selects appropriate health services for the selected subject group.

[0045] In step S318, the communication terminal 241 instructs the health project management support server 210 to send emails to the selected target group all at once. In step S319, the health project management support server 210 predicts cost-effectiveness based on the health project and the target person, and presents information on recommendation or invitation to the health project in descending order of profitability to the communication terminal 242 by email. In step S320, the communication terminal 242 displays the recommendation / invitation information for the health project received by email. The email may include photos and videos of the health project. Although the present embodiment shows the simultaneous sending by email, it may also be sent by facsimile or by telephone.

[0046] In step S321, the communication terminals 241 and 242 input the health service implementation history and the subscriber participation history, for example, monthly or irregularly. In step S322, the health service management support server 210 accumulates the health service implementation history and the subscriber participation history.

[0047] Furthermore, in step S323, the health project management support server 210 periodically evaluates the results of the health project based on the implementation history of the health project, the participation history of the insured, and changes in the insured's risk level. Then, in step S324, the health project management support server 210 reflects the evaluation results of the health project in the selection of health projects, derivation of risk levels, etc.

[0048] FIG. 3C is a flowchart showing the processing procedure for selecting a health service associated with a subject who is a selected subscriber, in an information processing system 200 including a health service management support server 210 as an information processing device according to this embodiment.

[0049] In step S330, the information processing system 200 registers the subscriber with the insurer. In step S331, the information processing system 200 collects data for supporting health project management. In collecting data for supporting health project management in step S331, the information processing system 200 performs processing equivalent to step S304 in FIG. 3A. That is, the information processing system 200 acquires information including the subscriber's personal attribute information or medical history, acquires health condition-related information including medical checkup information from the subscriber's health checkup results, and acquires health management-related information including the subscriber's prescription information from hospitals and medical facilities. The information processing system 200 then acquires other health-related information, such as the subscriber's participation history, by processing equivalent to step S306 in FIG. 3A.

[0050] In step S332, the information processing system 200 derives the risk level of the subscriber for each check target risk from the health condition related information collected in step S332. In step S333, the information processing system 200 evaluates the subscriber's health management situation, including medical examination status, from the health management related information collected in step S332. In step S334, the information processing system 200 selects a target subscriber who needs a health program based on the subscriber's risk level and health management situation. In step S335, the information processing system 200 selects an appropriate health program for the selected target subscriber, or plans an appropriate health program by itself. In step S336, the information processing system 200 presents information recommending or inviting the subscriber to participate in the health program, for example by email or facsimile. In step S337, the information processing system 200 analyzes the subscriber's participation history in health programs, implementation history of health programs, and changes in risk level, evaluates the results of the health programs, and reflects this in presenting future health programs to subscribers (target persons) who require such programs.

[0051] Fig. 3D is a sequence diagram showing detailed operation procedures for selecting subscribers who need to be provided with health care services in the information processing system 200 including the health care service management support server 210 as an information processing device according to this embodiment. Fig. 3D shows operation procedures for the health care service management support server 210 to notify subjects who need to participate in health care services based on health care related information including medical receipt information and health condition related information including medical checkup information in response to an inquiry or selection instruction from the operator's communication terminal 241. In Fig. 3D, steps S341 to S348 correspond to S315 to S317 in Fig. 3B, and steps S351 to S353 correspond to S318 to S320 in Fig. 3B.

[0052] In step S341, the communication terminal 241 requests the health insurance business management support server 210 to select all subjects who currently need to be provided with health insurance business. In step S342, the health insurance management support server 210 receives the selection request and generates information on all subjects who need to be provided with health insurance business, such as the total number of subjects and a list of information, based on the existing guidelines of the Ministry of Health, Labor and Welfare (legal hierarchy) and the hierarchy of this embodiment described later in Figures 7B and 7C. Then, in step S343, the communication terminal 240 outputs the information on all subjects who need to be provided with health insurance business acquired from the health insurance business management support server 210 as a display or information list. Output includes display and printing, but may also include transmission and output to a storage medium. Note that the communication terminal 241 is preferably configured to display a list of subjects by selecting a breakdown of all subjects as in the display screen 442 of Figure 4A, and to output detailed information on a selected subject by selecting a specific subject from the subject list. Furthermore, in step S344, the health care project management support server 210 may set flags for all subjects to whom health care projects need to be provided and for subject risks stored in the database, and retain the selection results.

[0053] In step S345, the health care project management support server 210 generates subject selection conditions and transmits them to the communication terminal 241, and in step S346, the communication terminal 241 displays a setting screen such as the display screen 443 in Fig. 4A including the received subject selection conditions. In this embodiment, the subject selection conditions include, for example, risk conditions and examination conditions.

[0054] In step S347, the communication terminal 241 sets a target selection condition for narrowing down the target persons who need to be provided with the health care service, and requests the health care service management support server 210 to select the target persons who need to be provided with the health care service according to the set target selection condition. In response to the target selection request, in step S348, the health care service management support server 210 generates information on the target persons who need to be provided with the health care service narrowed down by the target selection condition, for example, the number of targets and a list of information. Note that the generation of information on the target persons who need to be provided with the health care service is performed based on the existing guidelines of the Ministry of Health, Labor and Welfare (legal hierarchical structure) and the hierarchical structure of this embodiment described later in Figs. 7B and 7C. Then, in step S349, the communication terminal 241 outputs the information on the target persons who need to be provided with the health care service acquired from the health care service management support server 210 as a display or an information list. Output includes display and printing, and may further include transmission and output to a storage medium. It is preferable that the communication terminal 241 is configured to display a list of subjects as shown on the display screen 442 in Fig. 4A, and to output detailed information of a selected subject by selecting a specific subject from the list. In addition, the health service management support server 210 may set flags for subjects to whom health service provision is required and for subject risks stored in the database in step S351 and hold the selection results.

[0055] In step S352, the communication terminal 241 issues a notification instruction to the health project management support server 210 to send a mass e-mail containing content recommending or inviting the selected health project to the subjects who need the provision of the health project. In step S353, the health project management support server 210 receives the notification instruction and executes mass e-mail transmission to the recipients. The e-mail may include photos or videos of the health project. In this embodiment, mass transmission by e-mail is shown, but it may also be by facsimile transmission, telephone notification, or written delivery.

[0056] Fig. 3E is a sequence diagram showing the operation procedure of selecting a subject associated with a selected health service in an information processing system 200 including a health service management support server 210 as an information processing device according to this embodiment. In Fig. 3E, the same step numbers are assigned to steps similar to those in Fig. 3B, and duplicated explanations are omitted.

[0057] In step S361, the operator's communication terminal 241 receives information on the health service plan stored in the health service database 212 of the health service management support server 210 and selects a recommended health service. In step S362, the health service management support server 210 selects a recommended health service from the health service plan stored in the health service database 212. The health service is selected taking into consideration the goal of the health service, the number of participants, and the cost. In step S363, the health service management support server 210 selects a target person or a group of subscribers who need to participate in the selected health service and notifies the communication terminal 241. In addition, when the health service management support server 210 selects the recommended health service, it also notifies the selected health service. In step S364, the communication terminal 241 notifies the selected health service and the target person or group of subscribers who need the health service.

[0058] Fig. 3F is a flowchart showing the processing procedure for selecting subjects associated with a selected health service in an information processing system 200 including a health service management support server 210 as an information processing device according to this embodiment. In Fig. 3F, steps similar to those in Fig. 3C are given the same step numbers, and duplicated explanations are omitted.

[0059] In step S371, the information processing system 200 selects health services to be recommended to insurers and subscribers from the accumulated health service plans. Then, in step S372, the information processing system 200 selects subjects who are subscribers who need to participate in the selected health service and their groups.

[0060] FIG. 3G is a sequence diagram showing a detailed operation procedure of selecting a subject associated with a health service in the information processing system 200 including the health service management support server 210 as an information processing device according to this embodiment. FIG. 3G shows an operation procedure in which the health service management support server 210 notifies a health service subject who needs to participate in the selected health service in response to the selection of a health service recommended by the operator's communication terminal 241 or the health service management support server 210. Here, the selection of a health service subject who needs to participate in the health service by the health service management support server 210 is performed based on health management related information including medical receipt information and health condition related information including medical examination information. In FIG. 3G, steps S381 to S383, S348, and S349 correspond to S361 to S364 in FIG. 3B. In FIG. 3G, the same step numbers are assigned to steps similar to those in FIG. 3D, and duplicated explanations are omitted.

[0061] In step S381, the communications terminal 241 selects a recommended health service from the health service plans accumulated in the health service database 212. In step S382, the health service management support server 210 selects a recommended health service from the health service plans accumulated in the health service database 212. In step S383, the health service management support server 210 generates subject selection conditions for selecting subjects who are subscribers who need to participate in the selected health service. In addition, if the health promotion business operator 230 sets the subject selection conditions, the subject selection conditions are acquired.

[0062] <<Overview of the Health Care Management Support Server Operation>> Fig. 4A is a diagram showing an outline of the operation of selecting a target person to whom a health service should be provided by a health service management support server as an information processing device according to this embodiment. Note that, in the outline of the operation of Fig. 4A, four display screens 441 to 444 are shown, but these do not show successive screen transitions, and scenes characteristic of this embodiment are selected and shown.

[0063] FIG. 4A shows an outline of the operation of selecting subjects who need health insurance programs from among the subscribers of the insurer in the health insurance program management support server 210 by operation from the communication terminal 241. The display screen 441 is a log-on screen of the health insurance program management application. When logged on, the display screen 442 displays the total number of subjects who need health insurance programs based on default conditions from the health checkup information and disease information of the currently registered subscribers. Note that the number of people derived as "specific health guidance subjects (motivated)" and "specific health guidance subjects (active)" as a duplicated breakdown of the total number of subjects who need health insurance programs in the display screen 442 is a number that can be derived according to the existing guidelines (legal stratification) of the Ministry of Health, Labor and Welfare. On the other hand, the number of people derived as "other health insurance program subjects" is the number of people who are overlooked in the existing guidelines (legal stratification) of the Ministry of Health, Labor and Welfare and are not derived even though they need health insurance programs. An example of deriving such "other health insurance program subjects" will be described below with reference to FIG. 7B and FIG. 7C.

[0064] Display screen 443 is a screen for inputting subject selection conditions for narrowing down the target health care projects and the number of subjects from the total number of subjects who require health care projects, taking into consideration risks and costs in accordance with the health care project plan. Display screen 443 is not a format for inputting a subject selection condition formula, but is a format in which the operator can select from two major conditions, risk conditions and medical examination conditions. As the risk conditions, the type of risk held by the insured person or a combination thereof is selected. Furthermore, as the medical examination conditions, it is selected whether or not the insured person has undergone medical examination corresponding to the type of risk he or she has. Although display screen 443 shows some of the risk conditions and medical examination conditions, the present invention is not limited to these and various combinations of risks and medical examinations are possible, making it possible to narrow down the target health care projects and the number of subjects who require health care projects.

[0065] Display screen 444 displays a list of subject information selected from the database of health care project management support server 210 based on the risk conditions and consultation conditions entered on display screen 443. Although not shown, if the operator determines that the target health care project and the selected number of subjects are appropriate, he / she may instruct the sending of a notification to the selected subjects, for example by e-mail, recommending or inviting them to the target health care project. On the other hand, if the operator determines that the target health care project and the selected number of subjects are not appropriate, he / she changes the risk conditions and consultation conditions to search for an appropriate health care project.

[0066] (Risk Level) FIG. 4B is a diagram showing an overview of a risk level derived in consideration of the health management situation according to this embodiment. That is, in this embodiment, the risk level is derived from health condition-related information including health check information, but as shown in FIG. 4B, the risk level may be derived in consideration of the health management situation. In this case, the selection of subjects who are subscribers who require health services is performed not in consideration of the risk level and the health management situation but in consideration of the risk level, but it is essentially the same. FIG. 4B illustrates an example of the stratification of blood pressure risk into risk levels, but for other risk types, appropriate stratification corresponding to the risk is performed. For example, the stratification of risk levels such as smoking risk without health check information is performed with reference to questionnaire information. Note that the stratification of risk levels in FIG. 4B is one example, and is not limited to this, and various stratifications that can appropriately classify subscribers in health services are possible.

[0067] The blood pressure risk in Figure 4B is hierarchically divided into five risk levels. From the highest level, the levels are: high risk 440 → risk 450 → invitation to see a doctor 460 → health guidance 470 → no risk 480. In addition, at the high risk 440 and risk 450 levels, classification is made based on receipt information, such as whether a doctor has already seen a doctor or not, and if a doctor has already seen a doctor, whether medication is being prescribed or not (490).

[0068] In selecting members who require simple health programs, those other than those without risk (480) are added to the number of people who require health programs. However, the number of people who require health programs can be narrowed down to those at risk levels such as those with medical consultation invitations (460) or health guidance (470), or those at high risk (440) and risk (450) who have not yet been examined. It is desirable to plan how to implement health programs so that costs can be kept low while risks are kept low.

[0069] In Figure 4B, "not visited" and "visited but not prescribed medication" indicate health management status, while "continued risk" indicates risk level. Health programs are set and matched for each of the targets (number of target subscribers) indicated by the numbers in each box. In addition to health management and treatment status, receipt data also contains information that can be used to estimate the severity of illness, and this information can also be used to assess risk level.

[0070] Cloud server functional configuration FIG. 5A is a block diagram showing the functional configuration of a cloud server 510 according to this embodiment.

[0071] Cloud server 510 includes a communication control unit 501, a health service acquisition unit 502, a database 503, an information input unit 540, and virtual health service management support servers 210-1 to 210-n as information processing devices of this embodiment generated in cloud server 510. Communication control unit 501 controls communication with operator's communication terminal 241, subscriber's communication terminal 242, and the terminal of health promotion agent 230. Health service acquisition unit 502 acquires health services input from information input unit 540 or received by communication control unit 501 from the terminal of health promotion agent 230. The health service acquired by health service acquisition unit 502 is held in health service holding area 530 in the database.

[0072] Subscriber information, medical checkup information, and medical receipt information are input from information input unit 540 to virtual health service management support servers 210-1 to 210-n generated in cloud server 510. Health-related information such as questionnaire information received by communication control unit 501 from communication terminals 241, 242 is also input to virtual health service management support servers 210-1 to 210-n. Virtual health service management support servers 210-1 to 210-n store the acquired information in server areas 503-1 to 503-n of database 503, which are secretly separated. Then, based on the acquired information, subscribers selected as needing health service provision are associated with the selected health service provided by the health promotion agent, and solicitation information for the health service is transmitted to communication terminal 242. Incidentally, facsimile transmission may be used.

[0073] <<Functional configuration of a virtual health business management support server>> Fig. 5B is a block diagram showing the functional configuration of a virtual health project management support server 210 as an information processing device generated in a cloud server according to this embodiment. Hereinafter, the functional configuration of the virtual health project management support server 210 will be described, focusing on the configuration for narrowing down the target persons who require health projects taking into account their health management status, which is a feature of this embodiment. Note that in Fig. 5B, the configuration of one virtual health project management support server 210 as an information processing device will be described. In Fig. 5B, functional components that are less related to the processing of this embodiment are omitted. Also, in Fig. 5B, the same reference numbers are used for functional components similar to those in Fig. 5A, and duplicated explanations will be omitted.

[0074] The virtual health business management support server 210 includes a database 503. The database 503 includes an acquisition database 531 and a processing database 532 as the server areas in FIG. 5A. The acquisition database 531 includes personal attribute information, medical receipt information, medical checkup information, and other health condition related information. The personal attribute information is information for identifying the subscriber and information related to the subscriber, and includes the subscriber's sex, age, and social environment, such as the subscriber's place of affiliation information and the environmental information of the subscriber's place of affiliation. The medical receipt information is information related to the subscriber's medical checkup results. The other health condition related information is information related to the subscriber's health, and includes, for example, the subscriber's medical history, medical treatment history, and questionnaire information. The other health condition related information may include the subscriber's chart information, if possible. The processing database 532 stores the risk level derived by the risk level derivation unit 545, the treatment content extracted by the treatment content extraction unit 546, and the consciousness level derived by the consciousness level derivation unit 547 in association with each subscriber.

[0075] The virtual health business management support server 210 also includes an individual attribute information acquisition unit 541, a medical receipt information acquisition unit 542, a medical checkup information acquisition unit 543, an information storage processing unit 544, and an optional health condition related information acquisition unit 552. The individual attribute information acquisition unit 541, the medical receipt information acquisition unit 542, and the medical checkup information acquisition unit 543 acquire each piece of information from the information input unit 540 of the cloud server 510. The information input unit 540 may be input offline, online, or via a storage medium. The individual attribute information acquisition unit 541 acquires information identifying the registered or input subscriber and information related to the subscriber. The medical receipt information acquisition unit 542 acquires medical receipt information. The medical checkup information acquisition unit 543 acquires medical checkup information. The health condition related information acquisition unit 552 acquires health condition related information other than medical checkup information input from the communication terminal 240, such as questionnaire information. The information storage processing unit 544 matches the information acquired by the personal attribute information acquisition unit 541, the prescription information acquisition unit 542, the health check information acquisition unit 543, and the health condition related information acquisition unit 552 by subscriber and stores it in the database 503 as an acquired database 531.

[0076] Moreover, the virtual health care project management support server 210 includes a risk level derivation unit 545, a treatment content extraction unit 546, and an awareness level derivation unit 547. Furthermore, the virtual health care project management support server 210 includes a health care project recipient selection unit 548, a recipient selection condition acquisition unit 550, and a health care project recipient notification unit 551.

[0077] The risk level derivation unit 545 derives a risk level for each risk of each subscriber from the matched health checkup information. The risk level derivation unit 545 may derive the risk level according to the present embodiment described above in FIG. 4B in addition to the existing guidelines of the Ministry of Health, Labor and Welfare (legal stratification). The treatment content extraction unit 546 extracts the treatment content of each subscriber from the matched medical receipt information. The awareness level derivation unit 547 derives the health awareness level of each subscriber by referring to the treatment history from the matched medical receipt information.

[0078] The health service recipient selection unit 548 has a health service recipient selection table 549, and selects a subscriber who needs to be provided with a health service based on a risk level and a treatment status such as a treatment content and a consciousness level. If there are recipient selection conditions acquired by the recipient selection condition acquisition unit 550, the health service recipient selection unit 548 selects a recipient according to the acquired recipient selection conditions. On the other hand, if there are no selection conditions acquired by the recipient selection condition acquisition unit 550, the health service recipient selection unit 548 selects a recipient according to default conditions. The recipient selection condition acquisition unit 550 sends a setting screen for the recipient selection conditions to the communication terminal 241 and acquires the recipient selection conditions selected by the operator. The health service recipient notification unit 551 notifies the communication terminal 241 of information on the recipients who need to be provided with a health service, which is the selection result by the health service recipient selection unit 548, such as the number of recipients and a list of recipients.

[0079] 5B does not show the configuration for sending e-mails to all the people who need to receive health services. However, if you insert information about the subscriber and the health services into a template that corresponds to the content of the e-mail stored in advance in database 503 in response to a request from operator's communication terminal 241, and send it to the subscriber's communication terminal 242, it is possible to send the e-mails all at once.

[0080] (obtained database) 6 is a diagram showing the configuration of the acquisition database 531 according to this embodiment. The acquisition database 531 stores the acquisition data collected by the health project management support server 210 to be used for health insurance management. The acquisition database 531 stores subscriber information 610 including personal attribute information acquired from the information input unit 540, health management related information 620 including medical receipt information, and health condition related information 630 including medical checkup information or questionnaire information acquired from the communication terminal 241, by name of the subscriber.

[0081] As the subscriber information 610, a name 612, an address 613, contact information 614 such as a telephone number and an email address, attribute information 615, medical history 616, and living environment 617 including working conditions are stored in association with a subscriber ID 611. The attribute information 615 includes the date of birth, sex, age, relationship to the subscriber, subscriber classification indicating the participation position in the health insurance, etc. The subscriber information 610 also includes a medical treatment history of the illness.

[0082] The health care related information 620 stores the medical institution 622, the consultation date and time 623, the consultation details 624, the cost expressed in reward points 625, and the subscriber ID 626, which are acquired by the receipt information acquisition unit 542, in association with the receipt ID 621. The consultation details 624 include the name of the disease and the details of treatment.

[0083] As the health condition related information 630, health check information 632 acquired by the health check information acquisition unit 543 and questionnaire information 633 acquired from the communication terminal 241 are stored in association with a subscriber ID 631.

[0084] Although FIG. 6 shows the subscriber information 610, health management related information 620, and health condition related information 630 separately, they may be stored as one table corresponding to the subscriber ID.

[0085] (Processing Database) 7A is a diagram showing the configuration of the processing database 532 according to this embodiment. The processing database 532 stores processing data generated by the health care project management support server 210 by processing data stored in the acquisition database 531 for managing the health care project.

[0086] The processing database 532 stores individual attribute information 712, which is subscriber information, and risk level information 713 derived from health condition related information such as medical checkup information and questionnaire information, in association with the subscriber ID 711. The processing database 532 also stores health management status 714, including treatment status extracted from health management related information such as medical receipt information, and cost information 715, in association with the subscriber ID 711. The processing database 532 then stores a flag 716 indicating whether or not a health project is necessary, which is the result selected by the health project management support server 210 with reference to the risk level information 713, health management status 714, cost information 715, etc.

[0087] The risk level information 713 stores information about each risk, such as an obesity risk level 731, a BMI (Body Mass Index) level status 732, a smoking level 733, and a blood pressure risk level status 734. Each risk includes a measured value if there is one, the presence or absence of the risk, the risk level, and a status (e.g., risk rising, falling, or remaining the same).

[0088] The health management status including treatment status 714 includes, in association with each target risk 741, treatment details 742, which are actual treatment information from medical receipt information, and awareness level 743, which indicates the degree of consideration for the subscriber's health, derived from medical receipt information, questionnaire information, etc. The treatment details 742 include the date and time of treatment, the details of treatment including prescriptions, treatment results, etc. The awareness level 743 includes the awareness level for each risk and the total awareness level for overall health.

[0089] (Health service required participants) Fig. 7B is a diagram showing an example of determining a target insured who needs a health program according to this embodiment. Fig. 7B shows a method of selecting insureds who need a health program, which is overlooked in the existing guidelines (legal stratification) of the Ministry of Health, Labor and Welfare, from a combination of obesity risk, smoking risk and disease risk level, in this embodiment. In Fig. 7B, insureds who need a health program are selected as targets, taking into consideration the protection guidance level or higher of disease risk.

[0090] In Figure 7B, the “Total of Candidates for Intervention” in the lower left corner is the number of people who require health care projects, derived in accordance with existing Ministry of Health, Labour and Welfare guidelines (statutory stratification).

[0091] In contrast, 540 people (752) were excluded from the target group because they were taking medication, and 1,868 people (751) were excluded from the target group because they were not at risk of obesity, totaling 2,408 people (753). This number was excluded from those who needed health care programs despite being at risk of disease.

[0092] By selecting Figure 7B, subscribers who would have been excluded from the list of those who require health care programs in the derivation based on the existing Ministry of Health, Labour and Welfare guidelines (statutory stratification) are added to the list of those who require health care programs, thereby reducing the number of people who are overlooked in health care programs and improving efficiency.

[0093] Fig. 7C is a diagram showing another example of determining the target insured who needs the health program according to the present embodiment. Fig. 7C also shows a method of selecting the target insured who needs the health program, who is overlooked in the existing guidelines of the Ministry of Health, Labor and Welfare (legal stratification), from the combination of obesity risk, smoking risk and disease risk level in the present embodiment. In Fig. 7C, the insured who needs the health program is selected as the target in consideration of the disease risk level of medical examination recommendation or higher.

[0094] In Figure 7C, the "subtotal" at the bottom left is the number of people who require health care programs, derived in accordance with existing Ministry of Health, Labour and Welfare guidelines (statutory stratification).

[0095] In contrast, of the 1,375 people (761) who had at least one disease-related risk level that was high enough to recommend medical treatment, 308 people (762) were taking medication and were excluded from the list of people who needed health promotion programs, even though they had other risks that recommended medical treatment even while taking medication.

[0096] By selecting Figure 7C, subscribers who would have been excluded from the list of those who require health care programs in the derivation based on the existing Ministry of Health, Labour and Welfare guidelines (statutory stratification) are included as those who require health care programs, thereby reducing the number of people who are overlooked in health care programs and improving efficiency.

[0097] (Level of consciousness derivation table) 7D is a diagram showing the configuration of the consciousness level derivation table 780 for deriving the consciousness level of the subscriber according to this embodiment. The consciousness level derivation table 780 is used by the consciousness level derivation unit 547 to derive the degree of consciousness of the subscriber to reduce risk, taking into consideration the risk level and the treatment status / handling status as the health management status for each risk. Note that the consciousness level derivation table 780 is only an example, and is not limited to this. Using information that can be collected by the health project management support server 210, various information and combinations thereof for deriving the degree of consciousness of the subscriber to reduce risk are possible.

[0098] The consciousness level derivation table 780 stores a combination of a risk level 782 and a treatment status / handling status 783 as a health management status for each target risk 781. Then, a consciousness level 784 is stored in association with the combination of the risk level 782 and the treatment status / handling status 783 as a health management status.

[0099] (Health care project target selection table) 8 is a diagram showing the configuration of a health care service recipient selection table 549 according to this embodiment. The health care service recipient selection table 549 is used by a health care service recipient selection unit 548 to select recipients who are subscribers who require health care services, based on default conditions or recipient selection conditions set from the communication terminal 241.

[0100] The health service subject selection table 549 stores selection results 802 in association with subject selection conditions 801. Subject selection conditions include risk types and risk level thresholds related to risk levels, and whether or not a health service has been administered and awareness levels related to health management status. The selection results 802 store selection results indicating subjects who are subscribers who require health services for each risk type, a combination logical formula for how to combine the selection results, and a total result 821 indicating subjects who are subscribers who require health services for the set risk type. The combination logical formula can include all subjects without duplication, select subjects with multiple risks, or prioritize subjects according to risk type.

[0101] In this embodiment, a total result 821 indicating the number of subjects who require health care projects and the subjects is notified to the communication terminal 241 from the health care project management support server 210 as a selection result. The subjects at risk for all risk types are the total number of subjects shown on the display screen 442 in Fig. 4A.

[0102] <Hardware configuration of the health business management support server> FIG. 9 is a block diagram showing the hardware configuration of a health care project management support server 210 serving as an information processing device according to this embodiment.

[0103] In FIG. 9, a CPU (Central Processing Unit) 910 is a processor for arithmetic control, and executes a program to realize the functional components of FIG. 5. There may be one or more CPUs 910. A ROM (Read Only Memory) 920 stores fixed data and programs such as initial data and programs. A network interface 930 controls communication with communication terminals 241, 242 via a network. The CPU 910, ROM 920, and network interface 930 are shared functional components provided in the cloud server 510, and are indicated by bold frames. The other functional components shown below indicate one of the virtual health care business management support servers 210-1 to 210-n.

[0104] The RAM (Random Access Memory) 940 is a random access memory used by the CPU 910 as a work area for temporary storage. An area for storing data necessary for realizing this embodiment is secured in the RAM 940. The personal attribute information 941 is the attribute information of the subscriber acquired from the information input unit 540. The medical checkup information 942 as the health condition related information is the medical checkup information acquired from the information input unit 540. The medical receipt information 943 as the health management related information is the medical receipt information acquired from the information input unit 540. The other health condition related information 946 is information including questionnaire information acquired from the communication terminals 241, 242. The database storage information 944 is information stored in the acquisition database 531 of the database 503. The subject selection information 945 is information including risk level information and health management status as a result of name matching by subscriber from the acquisition database 531 and processing by the health business management support server 210, and is information stored in the processing database 532 of the database 503. The health care program recipient selection table 549 is a table used for selecting subscribers who require health care programs as recipients according to the recipient selection conditions shown in Fig. 8. Health care program recipients (total results) 821 is information on recipients who require health care programs selected using the health care program recipient selection table 549. Health care program notification information 947 is information for notifying recipients who require health care programs and encouraging them to participate in the health care programs, and in this embodiment, is notified by e-mail, for example. Transmission and reception data 948 is data transmitted and received with external devices such as the communication terminals 241, 242 via the network interface 930.

[0105] The storage 950 stores databases and various parameters used by the CPU 910, or the following data or programs required to realize this embodiment. The database 503 has an acquisition database 531 and a processing database 532. The acquisition database 531 stores data collected by the health care project management support server 210, as shown in Fig. 6. The processing database 532 stores data generated from the acquisition database 531 through processing by the health care project management support server 210, as shown in Fig. 7A.

[0106] The storage 950 stores the following programs. The health service management support server control program 951 is a program that controls the entire health service management support server 210 as an information processing device. The database generation module 953 is a module that generates the acquired database 531 that is matched by subscriber from the data collected by the health service management support server 210. The risk level derivation module 954 is a module that derives the risk level of each subscriber from the health condition-related data stored in the acquired database 531. The health management status evaluation module 955 is a module that evaluates the health management status, including the treatment status, of each subscriber from the health management-related data stored in the acquired database 531. The health service target selection module 956 is a module that selects subscribers who need health service as targets according to target selection conditions, taking into account the risk level and health management status. The health service notification module 957 is a module that transmits a recommendation notification for the health service to targets who need the health service.

[0107] It should be noted that the RAM 940 and storage 950 in FIG. 9 do not show programs and data related to the general-purpose functions of the health care project management support server 210 as an information processing device or other feasible functions.

[0108] <<Processing procedure of the health business management support server>> Fig. 10A is a flowchart showing the processing procedure of the health care business management support server 210 as an information processing device according to this embodiment. The flowchart in Fig. 10A is executed by the CPU 910 in Fig. 9 using the RAM 940 to realize the functional configuration unit in Fig. 5B.

[0109] In step S1011, the health care project management support server 210 judges whether or not the data to be acquired is to be used for the management of the insurer by the health care project management support server 210. If it is judged that the data to be acquired is to be used for the management of the insurer, the health care project management support server 210 executes management data acquisition processing in step S1013.

[0110] If it is determined that the data to be used for insurer management is not to be acquired, the health care project management support server 210 determines in step S1021 whether or not the process is for health care project management. If it is determined that the process is for health care project management, the health care project management support server 210 executes a process for selecting a health care project recipient in step S1023. Then, in step S1025, the health care project management support server 210 executes a process for notifying the recipient of the necessary health care project.

[0111] If it is determined that the process is not for obtaining data used in insurer management and is not for health project management, the health project management support server 210 determines whether or not the process is for other processes in step S1031. If it is determined that the process is for other processes, the health project management support server 210 executes the other processes in step S1033.

[0112] (Management data acquisition process) FIG. 10B is a flowchart showing the procedure of the management data acquisition process (S1013) according to this embodiment.

[0113] In step S1041, the health care business management support server 210 waits to acquire personal attribute information from the information input unit 540, and if personal attribute information is input, the health care business management support server 210 registers the acquired personal attribute information in the database 503 in step S1043.

[0114] In step S1045, the health project management support server 210 waits to acquire health condition-related information such as medical checkup information from the information input unit 540, or to acquire questionnaire information from the communication terminals 241, 242. If health condition-related information such as medical checkup information or questionnaire information is acquired, the health project management support server 210 registers the acquired health condition-related information in the database 503 in step S1047.

[0115] In step S1049, health care project management support server 210 waits to acquire medical receipt information as health care related information from information input unit 540. If medical receipt information is acquired, health care project management support server 210 registers the health care related information including the acquired medical receipt information in database 503 in step S1051.

[0116] In step S1053, the health project management support server 210 waits to receive other health condition-related information from the communication terminals 241, 242 via the communication control unit 501. If any such information is received, the health project management support server 210 registers the received other health condition-related information in the database 503 in step S1053.

[0117] (Health business target selection process) FIG. 10C is a flowchart showing the procedure of the health care service recipient selection process (S1023) according to this embodiment.

[0118] In step S1061, the health project management support server 210 acquires health condition related information including medical checkup information of each subscriber from the acquisition database 531 of the database 503. In step S1063, the health project management support server 210 derives a risk level for each risk from the health condition related information including the medical checkup information of each subscriber, and sets the risk level in the processing database 532 of the database 503.

[0119] In step S1065, the health care project management support server 210 acquires health care related information including medical receipt information of each subscriber from the acquisition database 531 of the database 503. In step S1067, the health care project management support server 210 extracts a health care situation including treatment details from the health care related information including medical receipt information of each subscriber, and sets it in the processing database 532 of the database 503. In step S1069, the health care project management support server 210 derives an awareness level from the health care related information such as medical receipt information of each subscriber, and sets it in the processing database 532 of the database 503.

[0120] In step S1071, the health project management support server 210 determines whether or not all registered subscribers have been processed. If it is determined that not all subscribers have been processed, the health project management support server 210 returns to step S1061 and repeats the processes from steps S1061 to S1069 for the next subscriber.

[0121] If it is determined that all subscribers have been processed, the health project management support server 210 determines in step S1073 whether or not the subject selection conditions have been received from the communication terminal 241. If it is determined that the subject selection conditions have not been received, the health project management support server 210 selects a health project subject by legal hierarchical classification and present hierarchical classification in step S1073. On the other hand, if it is determined that the subject selection conditions have been received, the health project management support server 210 selects a health project subject who has a risk level that matches the subject selection conditions and corresponds to the treatment content and consciousness level as the health management status in step S1075. Then, the health project management support server 210 outputs the selection result to the communication terminal 241 (or 242) in step S1079.

[0122] <Functional configuration of communication terminal> Fig. 11 is a block diagram showing the functional configuration of the communication terminal 241 according to this embodiment. Note that functional components that are less related to the processing of this embodiment are omitted in Fig. 11. Also, Fig. 11 shows the configuration of the communication terminal 241 for the operator, and omits the configuration of the communication terminal 242 for the subscriber.

[0123] The communications terminal 241 includes a communications control unit 1101, an application acquisition unit 1102, an application execution unit 1103, and an input / output interface 1104. A display unit 1141 that displays output information and the state of the communications terminal 241, an operation unit 1142 that instructs the operation of the communications terminal 241, and, as options, a printing unit 1143 and a storage medium 1144 are connected to the input / output interface 1104. The communications control unit 1101 controls communication with the health care project management support server 210 via the network. The application acquisition unit 1102 acquires a health care project management application for subscribers provided by the health care project management support server 210.

[0124] The application execution unit 1103 includes a display / operation control unit 1131 , a subject selection condition acquisition unit 1136 , a subject selection condition transmission unit 1137 , a health service subject acquisition unit 1138 , and a health service subject output unit 1139 .

[0125] The display / operation control unit 1131 controls the output to the display unit 1141 and the input from the operation unit 1142. The subject selection condition acquisition unit 1136 acquires the subject selection conditions set by the operation unit 1142 from the subject selection condition setting screen displayed on the display unit 1141. The subject selection condition transmission unit 1137 transmits the subject selection conditions acquired by the subject selection condition acquisition unit 1136 to the health care project management support server 210. The health care project subject acquisition unit 1138 acquires the selection result of subjects who are subscribers who require the provision of health care projects using the subject selection conditions in the health care project management support server 210. The health care project subject output unit 1139 outputs information on subjects who are subscribers who require the provision of health care projects acquired by the health care project subject acquisition unit 1138 from the health care project management support server 210 to the display unit 1141, the printing unit 1143, or the storage medium 1144.

[0126] In FIG. 11, the configuration for instructing simultaneous transmission of e-mails or facsimile transmissions regarding health services to subscribers is omitted.

[0127] <<Processing procedure of communication terminal>> 12A is a flowchart showing a processing procedure of the communication terminal 241 according to this embodiment. In this flowchart, a CPU executes a program stored in a storage constituting the communication terminal 241 by using a RAM, thereby realizing the functional configuration units of FIG.

[0128] In step S1231, the communication terminal 241 determines whether the instruction is for selecting a subject to whom a health care service needs to be provided. If it is determined that the instruction is for selecting a subject, the communication terminal 241 executes a subject selection request process in step S1233.

[0129] If it is determined that the instruction is not an instruction to select a target person, the communication terminal 241 determines whether or not the instruction is another process in step S1241. If it is determined that the instruction is another process, the communication terminal 241 executes the other process in step S1243.

[0130] (Processing requests from health service recipients) FIG. 12B is a flowchart showing the procedure of the health care service recipient request process (S1233) according to this embodiment.

[0131] In step S1251, the communication terminal 241 waits for reception of information on all subjects who require the provision of health care services and who have not entered subject selection conditions from the health care service management support server 210. When information on all subjects has been received, in step S1253, the communication terminal 241 outputs, in a predetermined format, the information on all subjects who require the provision of health care services received from the health care service management support server 210.

[0132] In step S1255, the communications terminal 241 waits for transmission of the subject selection conditions to the health care project management support server 210. When the subject selection conditions are transmitted to the health care project management support server 210, in step S1257, the communications terminal 241 waits for reception of the selection results from the health care project management support server 210. When the selection results are received from the health care project management support server 210, in step S1259, the communications terminal 241 outputs information on the subjects who require the provision of health care projects, which is the received selection result.

[0133] In step S1261, the communication terminal 241 determines whether or not there is an instruction to notify the subjects who need the health service by email of the health service. If it is determined that there is an instruction to notify by email, in step S1263, the communication terminal 241 transmits the notification of the health service to the subjects all at once.

[0134] According to this embodiment, the target persons are narrowed down in consideration of the subscriber's health management status including the risk level and treatment status, and the selection of the target persons and the selection of the health service are associated with each other, so that the health service can be managed efficiently. In particular, since the subscriber's health consciousness level is considered from the treatment status, the health service can be implemented within an appropriate range where the invitation to the health service is successful.

[0135] [Third embodiment] Next, a health service management support server as an information processing device according to a third embodiment of the present invention will be described. The health service management support server according to this embodiment differs from the second embodiment in that it further acquires the subscriber's participation history in the health service and derives the subscriber's awareness level of health management by referring to the participation history in the health service. The health service management support server of this embodiment stores the subscriber, health condition related information, and health management related information such as prescription information and participation history in the health service in a database in association with each other. Then, when the type of risk is designated as risk, the server selects a target subscriber who is a subscriber who needs to be provided with the health service, taking into consideration the risk level corresponding to the designated type of risk and the treatment status and participation history in the health service as health management related information. Other configurations and operations are the same as those of the second embodiment, and the same configurations and operations are denoted by the same reference numerals and detailed description thereof will be omitted.

[0136] Information Processing System 13 and 14, the operation of an information processing system 1300 including a health care business management support server 1310 as an information processing device of this embodiment will be described.

[0137] (Operation overview) Fig. 13 is a diagram showing an outline of the operation of an information processing system 1300 including a health service management support server 1310 as an information processing device according to this embodiment. In Fig. 13, the same components as those in Fig. 4A are given the same reference numerals, and duplicated explanations will be omitted.

[0138] Display screen 1343 is an input screen for target selection conditions in this embodiment for efficiently selecting (narrowing down) subscribers who are recommended or invited to participate in the health care program. Display screen 1343 includes risk conditions, examination conditions, and health care program conditions. The health care program conditions also show settings for participation / non-participation in program A and participation / non-participation in program B. Note that the types of target selection conditions are not limited to those shown in FIG. 13.

[0139] (Operation sequence) Fig. 14 is a sequence diagram showing the operation procedure of an information processing system 1300 including a health service management support server 1310 as an information processing device according to this embodiment. In Fig. 14, the same steps as those in Fig. 3A are given the same step numbers, and duplicated explanations will be omitted.

[0140] In step S1408, the insurer 220 reports the subscriber's participation information in health care programs as health management related information to the health care program management support server 1310. In addition, in step S1410, the communication terminals 241, 242 report the subscriber's participation information in health care programs as health management related information to the health care program management support server 1310. The health care program management support server 1310 acquires the subscriber's participation information in health care programs from the insurer 220 or the communication terminals 241, 242, and stores the information in database 503 in association with the subscriber.

[0141] Virtual health business management support server Fig. 15 is a block diagram showing the functional configuration of a virtual health service management support server 1310 as an information processing device according to this embodiment. In Fig. 15, the same reference numerals are given to the same functional components as those in Fig. 5B, and duplicated explanations will be omitted.

[0142] The virtual health project management support server 1310 includes a database 1503. The database 1503 includes an acquisition database 1531 including information related to participation in health projects as health management related information. The database 1503 also includes a processing database 1532 including details of the health projects in which the subscriber participated and an awareness level derived from receipt information and health project participation information as health management related information.

[0143] The virtual health service management support server 1310 also includes a health service participation information acquisition unit 1543, an awareness level derivation unit 1547, a health service recipient selection unit 1548, and a health management related information acquisition unit 1552. The health service participation information acquisition unit 1543 acquires health service participation information from the information input unit 540 or the communication terminals 241 and 242. The health management related information acquisition unit 1552 acquires other health management related information from the communication terminals 241 and 242. The awareness level derivation unit 1547 derives the subscriber's awareness level of health maintenance from the treatment contents the subscriber has received and the health service contents in which the subscriber has participated, which are stored in the processing database 1532 as health management related information. The health service recipient selection unit 1548 includes a health service recipient selection table 1549, and selects a subscriber who is a target to whom a health service is recommended or invited, taking into consideration the subscriber's history of participation / non-participation in a health service.

[0144] (obtained database) Fig. 16 is a diagram showing the arrangement of an acquisition database 1531 according to this embodiment. In Fig. 16, the same components as those in Fig. 6 are given the same reference numerals, and duplicated explanations will be omitted.

[0145] The acquired database 1531 further includes health project information 1630 that is collected and held in advance by the health project management support server 1310 or acquired from the operator's communication terminal 241. The health project information 1630 stores health project participation information 1632 in association with a subscriber ID 1631. The health project participation information 1632 includes the date and time of participation in a health project and the project content.

[0146] (Processing Database) Fig. 17A is a diagram showing the arrangement of a processing database 1532 according to this embodiment. In Fig. 17A, the same components as those in Fig. 7A are given the same reference numerals, and duplicated explanations will be omitted.

[0147] The processing database 1532 includes the subscriber's health management status 1714 evaluated from health management related information including the treatment status and health program participation status. The health management status 1714 stores health program participation details 1742 and an awareness level 1743 derived from the treatment details and the health program participation details. The health program participation details 1742 stores the participation date and time of the health program, the health program details, and the participation results including the participation impressions, etc., in association with a program ID that identifies the health program. Here, the awareness level 1743 may include an awareness level derived from the treatment details 742 that the subscriber received, an awareness level derived from the health program participation details 1742 in which the subscriber participated, and further an awareness level derived from the treatment details 742 and the health program participation details 1742. The awareness level 1743 also includes an awareness level for each risk and a total awareness level for the overall health.

[0148] (Level of consciousness derivation table) FIG. 17B is a diagram showing the configuration of the consciousness level derivation table 1780 for deriving the consciousness level of the subscriber according to this embodiment. The consciousness level derivation table 1780 is used by the consciousness level derivation unit 1547 to derive the degree of consciousness of the subscriber to reduce the risk, taking into consideration the risk level, the treatment status / handling status as the health management status, and the participation status of the health project for each risk. Note that the consciousness level derivation table 1780 is an example, and is not limited thereto. Using information that can be collected by the health project management support server 1310, various information and combinations thereof for deriving the degree of consciousness of the subscriber to reduce the risk are possible. Note that in FIG. 17B, the same reference numbers are given to components similar to those in FIG. 7D, and duplicated explanations are omitted. FIG. 17B shows only an example of the consciousness level derived from the treatment content 742 and the health project participation content 1742.

[0149] In the consciousness level derivation table 1780, the participation status in health care activities is stored as a health management status 1783 as a condition for deriving a consciousness level 784.

[0150] (Health care project target selection table) Fig. 18 is a diagram showing the configuration of a health care project target selection table 1549 according to this embodiment. In Fig. 18, the same components as those in Fig. 8 are given the same reference numerals, and duplicated explanations will be omitted.

[0151] The health service subject selection table 1549 considers the awareness level in which the medical examination details and the participation details of the health service are referenced as the awareness level of the subject selection conditions 1801 .

[0152] (Management data acquisition process) Fig. 19A is a flowchart showing the procedure of the management data acquisition process (S1013) according to this embodiment. In Fig. 19A, the same steps as those in Fig. 10B are given the same step numbers, and duplicated explanations will be omitted.

[0153] In step S1945, health project management support server 1310 waits to acquire health project related information and questionnaire information of the participant from information input unit 540 and communication terminals 241, 242. If health project related information and questionnaire information are acquired, in step S1947, health project management support server 1310 registers the health management related information including the acquired health project participation information in database 503 in association with the subscriber. Furthermore, in step S1955, health project management support server 1310 receives other health condition related information or other health management related information from communication terminals 241, 242 and registers it in database 503 in association with the subscriber.

[0154] (Health business target selection process) Fig. 19B is a flow chart showing the procedure of the health service recipient selection process (S1023) according to this embodiment. In Fig. 19B, the same steps as those in Fig. 10C are given the same step numbers, and duplicated explanations will be omitted.

[0155] In step S1968, the health care project management support server 1310 acquires health care project participation information of each subscriber from the acquisition database 1531 of the database 1503. In step S1969, the health care project management support server 1310 derives the consciousness level from the treatment details and health care project participation details as the health care related information of each subscriber, and sets it in the processing database 1532 of the database 1503.

[0156] If it is determined that processing has been completed for all subscribers, the health care project management support server 1310 determines in step S1973 whether or not subject selection conditions including health care project participation have been received from the communication terminal 241. If it is determined that subject selection conditions have been received, the health care project management support server 1310 selects health care project subjects in step S1975 who have a risk level that matches the subject selection conditions and who correspond to the treatment content, health care project participation content, and awareness level as their health management status.

[0157] According to this embodiment, the target persons are narrowed down in consideration of the subscriber's risk level, the medical treatment status as a health management status, and the participation information of the health service, and the selection of the target persons and the selection of the health service are associated with each other, so that the health service can be managed efficiently. In other words, since the willingness to participate in the health service is taken into consideration, the health service can be implemented in an appropriate range where the invitation to the health service is more successful.

[0158] [Fourth embodiment] Next, a health care business management support server as an information processing device according to a third embodiment of the present invention will be described. The health care business management support server according to this embodiment differs from the above second and third embodiments in that it determines a necessary level, which is the degree to which health care services need to be provided to the subscriber, and manages the health care business according to the necessary level. In this embodiment, the necessary level indicating the degree to which health care services need to be provided to the subscriber is set by referring to at least one of the severity of the risk level, the risk number, which is the severe level, and the treatment level. The other configurations and operations are similar to those of the second or third embodiment, so the same reference numerals are used for the same configurations and operations and detailed explanations thereof will be omitted.

[0159] <<Outline of operation of information processing system>> Fig. 20 is a diagram showing an outline of the operation of an information processing system 2000 including a health service management support server 2010 as an information processing device according to this embodiment. In Fig. 20, the same components as those in Fig. 4A are given the same reference numerals, and duplicated explanations will be omitted.

[0160] Display screen 2033 is an input screen for subject selection conditions in this embodiment for efficiently selecting (narrowing down) subscribers who are recommended or invited to participate in the health care program. The subject selection conditions on display screen 2033 include risk conditions, examination conditions, and level conditions. The level conditions also show settings for the required level threshold (α) and risk level threshold (β). Note that the types of subject selection conditions are not limited to those shown in FIG. 20.

[0161] Virtual health business management support server Fig. 21 is a block diagram showing the functional configuration of a virtual health service management support server 2010 as an information processing device according to this embodiment. In Fig. 21, the same reference numerals are given to the same functional components as those in Fig. 5B, and duplicated explanations will be omitted.

[0162] The virtual health service management support server 2010 includes a database 2103. The database 2103 has a transaction database 2132 including risk levels, treatment details, awareness levels, and further required levels of participation among subscribers who require the provision of health services.

[0163] The virtual health care project management support server 2010 includes a health care project recipient selection unit 2148, a recipient selection condition acquisition unit 2150 including a required level, and a required level derivation unit 2152. The health care project recipient selection unit 2148 includes a health care project recipient selection table 2149, and selects a recipient who needs a health care project from among the subscribers, taking into consideration the required level as a recipient selection condition. The recipient selection condition acquisition unit 2150 acquires the recipient selection condition including the required level from the communication terminal 241. The required level derivation unit 2152 derives the required level for the subscriber to participate in the health care project, taking into consideration the risk level derived by the risk level derivation unit 545, the treatment content extracted by the treatment content extraction unit 546, and the consciousness level derived by the consciousness level derivation unit 547. The consciousness level may be derived by the consciousness level derivation unit 1547 in the third embodiment. The required level is stored in the processing database 2132 and is taken into consideration as a condition for selecting subjects in the health service subject selection unit 2148 .

[0164] (Processing Database) Fig. 22 is a diagram showing the arrangement of a processing database 2132 according to this embodiment. In Fig. 22, the same components as those in Fig. 7A are given the same reference numerals, and duplicated explanations will be omitted.

[0165] The processing database 2132 further stores a required level 2218 derived by the required level derivation unit 2152. The processing database 2132 may also include the health management status 1714 including the treatment status and health service participation status in the third embodiment.

[0166] (Health care project target selection table) Fig. 23A is a diagram showing the configuration of a health care project target selection table 2149 according to this embodiment. In Fig. 23A, the same components as those in Fig. 8 are given the same reference numerals, and duplicated explanations will be omitted.

[0167] The health service recipient selection table 2149 includes a required level as a recipient selection condition 2301 .

[0168] Fig. 23B is a diagram showing an example of determining the required level of the health care project according to this embodiment. Fig. 23B shows an example of deriving the required level when risks overlap, but is not limited thereto.

[0169] The overlapping status of risks 2310 illustrates the degree of overlap of risks. The number of overlapping risks 2320 is also used as a required level, as shown in a risk overlap table 2330. Furthermore, a required level for the subscriber to participate in the health program is derived from a combination of the types of overlapping risks, a combination of the risk levels of each risk, etc. The required level may be set for each subscriber, or may be set as a participation priority of the subscriber for each health program.

[0170] (Required level derivation table) FIG. 23C is a diagram showing the configuration of a required level derivation table 2340 for deriving a required level according to this embodiment. The required level derivation table 2340 is used by the required level derivation unit 2152 to derive the degree of the required level for each subscriber to participate in a health program, taking into consideration the risk situation, and the treatment situation / handling situation and health program participation situation as the health management situation, for each subscriber. Although it is possible to use each risk level as it is as the required level, FIG. 23C shows derivation of the required level taking into consideration the treatment situation and health program participation situation as the health management situation. The required level derivation table 2340 in FIG. 23C is an example, and is not limited thereto. Various information and combinations thereof for deriving the degree of the required level for participating in a health program are possible using information that can be collected by the health program management support server 2010.

[0171] The required level derivation table 2340 stores a risk status 2342 and a health management status 2343 including a treatment status and a health program participation status in association with a subscriber ID 2341. The required level derivation table 2340 stores a required level 2344 derived based on the risk status 2342 and the health management status 2343 including a treatment status and a health program participation status. The risk status 2342 includes overlapping risks and a risk level for each risk. The health management status 2343 including a treatment status and a health program participation status includes treatment details, program participation details, and a derived awareness level. The required level 2344 includes a required level for each risk and an overall required level for the subscriber.

[0172] (Health business target selection process) Fig. 24 is a flow chart showing the procedure of the health service recipient selection process (S1023) according to this embodiment. In Fig. 24, the same steps as those in Fig. 10C are given the same step numbers, and duplicated explanations will be omitted.

[0173] In step S2470, the health care project management support server 2010 derives a required level from the risk level and the details of treatment and awareness level as the health care situation, and sets a required level for each subscriber and each risk of each subscriber.

[0174] If it is determined that processing has been completed for all subscribers, the health care project management support server 2010 determines in step S2473 whether or not subject selection conditions including a required level have been received from the communication terminal 241. If it is determined that the subject selection conditions have been received, the health care project management support server 2010 selects health care project subjects in step S2475 who have a risk level that matches the subject selection conditions and who correspond to the treatment content, health care project participation content and awareness level, and required level as their health management status.

[0175] According to this embodiment, the target persons are narrowed down in consideration of the subscriber's risk level, the medical treatment status as a health management status, and the necessary level of the health service, and the selection of the target persons and the selection of the health service are associated with each other, so that the health service can be managed efficiently. In other words, the target persons are selected in consideration of the importance of the subscriber's participation in the health service, so that the health service can be implemented effectively and efficiently.

[0176] [Other embodiments] In addition, the information exchange between the health service management support server and the subscriber's communication terminal was explained as being via e-mail, but it is not limited to e-mail, and the subscriber's communication terminal may have a specific application for making inquiries and displaying information. In addition, it may be configured to use communication means such as written documents or telephone.

[0177] In the above embodiment, the cost is not taken into consideration when selecting the health insurance program recipients. However, it is possible to adjust the selection results of the health insurance program recipients by taking into consideration the expenses incurred when the insured is hospitalized or examined due to illness, the loss to the company due to the insured's hospitalization, the implementation cost of the health insurance program and its effect, and such processing is also included in the present invention.

[0178] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. In addition, systems or devices that combine separate features included in each embodiment in any way are also included in the scope of the present invention. In other words, health care services can be managed more appropriately and efficiently by various combinations that are not limited to the subscriber's risk level, treatment status, health care service participation information, and health care service requirement level.

[0179] The present invention may be applied to a system consisting of multiple devices, or to a single device. Furthermore, the present invention is also applicable to a case where an information processing program for realizing the functions of the embodiments is supplied directly or remotely to a system or device. Therefore, the scope of the present invention also includes a program installed on a computer to realize the functions of the present invention by a computer, a medium storing the program, and a WWW (World Wide Web) server for downloading the program. In particular, the scope of the present invention includes at least a non-transitory computer readable medium storing a program for causing a computer to execute the processing steps included in the above-mentioned embodiments.

Claims

1. An acquisition unit that acquires medical history of each of a plurality of subscribers who are insured by an insurer and health program participation details of each of the plurality of subscribers; a derivation unit that derives an awareness level as a willingness to participate in a health service for each of the plurality of subscribers based on a combination of the medical history and the content of participation in the health service; A selection unit that selects subscribers to whom health services should be offered according to the awareness level; An information processing system comprising:

2. The information processing system according to claim 1 , further comprising an extraction unit that extracts the medical treatment history from medical receipt information of each of the plurality of subscribers.

3. The information processing system according to claim 1 , wherein the health care service participation details include a date and time of participation in the health care service and details of the service.

4. 2. The information processing system according to claim 1, wherein the deriving unit further derives the awareness level from the results of a questionnaire administered to each of a plurality of subscribers to measure a degree of concern for health.

5. The information processing system according to claim 1 , wherein the treatment history includes treatment dates and times, prescriptions, and treatment results.

6. An acquisition step in which an acquisition unit acquires the medical history of each of a plurality of subscribers who are insured by an insurer and the health program participation details of each of the plurality of subscribers; a derivation step of deriving an awareness level as a willingness to participate in a health care program for each of the plurality of subscribers based on a combination of the medical history and the health care program participation content; A selection step in which a selection unit selects subscribers to whom health care services should be recommended according to the awareness level; An information processing method comprising:

Images