Health information management system and management server

Abstract

To enable a use of data by switching from a moving source to a moving destination without rebuilding a database.SOLUTION: An integrated ID used to control an integrated use of an enterprise service 101 capable of using an enterprise database 111 and a personal service 102 capable of using a personal database 112 is managed by master data of a service use management server 1, and whether or not the enterprise database 111 and the personal database 112 are associated with each other based on the integrated ID is switched according to whether or not the integrated use of the service is designated. Thus, even in the case where an employee has moved, by merely editing the association based on the integrated ID in the master data, it is possible to make the personal database unavailable in an enterprise of the moving source, and to make the personal database available in association with the enterprise database of an enterprise of the moving destination in the enterprise of the moving destination.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a health information management system and management server, and is particularly suitable for use in a system that enables integrated use of corporate services that can utilize a corporate database that stores employee health-related data acquired by the company, and personal services that can utilize a personal database that stores personal health-related data acquired by an individual. [Background technology]

[0002] Companies are now required to not only manage employee attendance but also to manage their employees' overall health. To that end, as part of labor management, each company conducts regular health checkups for employees. In addition, they conduct stress checks and mental health checks for employees, and if deemed necessary, provide face-to-face guidance by industrial physicians.

[0003] On the other hand, many employees undergo their own health checkups and stress checks, and measure vital data such as the number of steps taken, weight, and calories burned, in addition to those conducted by their companies, and manage this data themselves. In this situation, the health-related data of employees collected by the company and the health-related data collected by the employee themselves are managed separately, even though they are data on the same person.

[0004] In response to this, a comprehensive health information management system has been proposed that enables a corporate system to acquire and manage health care data managed by individual employees in an integrated manner (see, for example, Patent Document 1). In the system described in Patent Document 1, a corporate health care system that manages employee health care data for each employee in association with employee identification data acquires and stores general user health care data from a general user health care system that manages general user health care data for each general user in association with general user identification data, based on employee identification data and general user identification data (mutually corresponding data that allows different identification data to be assigned to the same person).

[0005] Specifically, when a terminal is logged in to the corporate healthcare system based on employee identification data, the terminal logs in to the general user healthcare system based on general user identification data, thereby associating the employee identification data with the general user identification data. In this double login state, the general user healthcare system transmits general user healthcare data to the corporate healthcare system based on the employee identification data and the general user identification data in response to a request from the corporate healthcare system. The corporate healthcare system then associates the general user healthcare data acquired from the general user healthcare data with the employee identification data associated with the general user identification data and stores it. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent No. 7041437 Summary of the Invention [Problem to be solved by the invention]

[0007] The system described in Patent Document 1 makes it possible to perform more comprehensive health management by combining healthcare data from the results of health checkups and stress checks conducted by a company with healthcare data managed by individual employees. However, the system described in Patent Document 1 has a problem in that when an employee changes jobs, resigns, or otherwise changes jobs, the employee's healthcare data must be deleted from the database that was integrated before the transfer, and the healthcare data must be integrated again at the company after the transfer, requiring the database to be reconstructed.

[0008] The present invention has been made to solve such problems, and aims to achieve portability, allowing data to be used by switching from the original location to the new location without rebuilding the database, even when an employee changes jobs or resigns. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems, the present invention provides an ID management unit that manages an integrated ID used to control the integrated use of corporate services that can use a corporate database that stores employee health-related data acquired by the company, and personal services that can use a personal database that stores personal health-related data acquired by an individual, and switches whether or not to associate the corporate database and personal database using the integrated ID depending on whether or not integrated use of the corporate service and personal service is specified for each employee. [Effects of the Invention]

[0010] According to the present invention configured as described above, when there is no association by an integrated ID, only data in the corporate database can be used when logging in to a corporate service, and only data in the personal database can be used when logging in to a personal service. On the other hand, when there is association by an integrated ID, when logging in to a corporate service or a personal service, data can be used with the corporate database and personal database associated.

[0011] As a result, when an employee changes jobs or resigns, simply by canceling the integrated ID at the company from which the employee was transferred and setting an integrated ID at the company to which the employee was transferred, the personal database becomes unavailable at the company from which the employee was transferred, and the personal database becomes available at the company to which the employee was transferred by associating it with the corporate database of the company to which the employee was transferred.In this way, according to the present invention, even when an employee changes jobs or resigns, portability can be achieved, allowing data to be used by switching from the company from which the employee was transferred to the company to which the employee was transferred without having to rebuild the database. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an example of the configuration of a health information management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating an example of a functional configuration of a service usage management server according to the present embodiment. [Figure 3] 3 is a diagram illustrating an example of management data stored in a management data storage unit according to the present embodiment. FIG. [Figure 4] FIG. 10 is a diagram showing state transitions related to corporate services. [Figure 5] FIG. 10 is a diagram showing state transitions related to personal services. [Figure 6] FIG. 10 is a diagram showing possible combinations of states of corporate services and states of individual services that can be taken simultaneously. [Figure 7]10 is a flowchart showing the flow of authentication processing executed when specifying integrated use of services. DETAILED DESCRIPTION OF THE INVENTION

[0013] An embodiment of the present invention will now be described with reference to the drawings. Figure 1 is a diagram showing an example of the configuration of a health information management system according to this embodiment. As shown in Figure 1, the health information management system of this embodiment is configured with a service usage management server 1 connected to a communication network 100 such as the Internet or a mobile phone network.

[0014] The service usage management server 1 manages the use of corporate services 101 and individual services 102 by user terminals 2. The corporate services 101 are web services that allow access to a corporate database 111 that stores health-related data of employees acquired by the company. The corporate database 111 is configured using unique identification information (e.g., employee number) of employees managed within the company as a primary key, and stores health-related data of employees acquired by the company (hereinafter referred to as corporate-acquired health-related data). The corporate-acquired health-related data includes, for example, data from health checkups conducted by companies for their employees, and diagnostic data from stress checks and mental health checks conducted by companies for their employees. Using the corporate database 111 means viewing or editing the data in the corporate database 111.

[0015] The personal service 102 is a web service that allows access to a personal database 112 that stores personal health-related data acquired by an individual. The personal database 112 is configured using a personal ID, which is unique identification information that identifies an individual, as a primary key, and stores personal health-related data acquired by the individual (hereinafter referred to as "individually acquired health-related data"). The personally acquired health-related data includes diagnostic data such as health checkups and stress checks that an individual has undergone, and vital data such as the number of steps taken, weight, and calories burned measured using a smartphone or wearable device. Using the personal database 112 means viewing or editing the data in the personal database 112.

[0016] The service usage management server 1 performs authentication based on the login ID input from the user terminal 2, and determines whether the service being used is a corporate service 101 or a personal service 102. There are two types of login IDs: a corporate login ID used to log in to the corporate service 101, and a personal login ID used to log in to the personal service 102. A user can have one or two login IDs. If there is one login ID, the user can receive only either the corporate service 101 or the personal service 102, and if there are two login IDs, the user can receive both the corporate service 101 and the personal service 102.

[0017] When a login is made from the user terminal 2 using a corporate login ID, the service usage management server 1 allows the corporate service 101 to use the corporate database 111 after authentication. On the other hand, when a login is made from the user terminal 2 using a personal login ID, the service usage management server 1 allows the personal service 102 to use the personal database 112 after authentication.

[0018] In this embodiment, the integrated use of the corporate service 101 and the personal service 102 can be specified from the user terminal 2. When the integrated use is specified, login using a personal login ID is prohibited, and login using only the corporate login ID is permitted. In this case, newly added personally acquired health-related data after the integrated use is specified is stored in the corporate database 111. During the period when the integrated use is specified, the service usage management server 1 synchronizes data between the corporate database 111 and the personal database 112.

[0019] Fig. 2 is a block diagram showing an example of the functional configuration of the service usage management server 1 according to this embodiment. As shown in Fig. 2, the service usage management server 1 of this embodiment includes, as its functional configuration, an ID management unit 11, a login management unit 12, and a synchronization processing unit 13. The service usage management server 1 also includes a management data storage unit 10 as a storage medium.

[0020] The functional blocks 11 to 13 execute the following processes through the cooperation of hardware and software. For example, the processes of the functional blocks 11 to 13 are executed by the operation of a program stored in a storage medium such as RAM, ROM, a hard disk, or a semiconductor memory under the control of a microcomputer including a CPU, RAM, ROM, etc. In addition to the microcomputer, a DSP (Digital Signal Processor) may also be included.

[0021] The ID management unit 11 stores and manages management data, including various IDs used to manage the use of the corporate services 101 and the personal services 102, in the management data storage unit 10. The management data includes a corporate login ID used to log in to the corporate services 101, a personal login ID used to log in to the personal services 102, an integrated ID used to control the integrated use of the corporate services 101 and the personal services 102, an employee number which is the primary key of the corporate database 111, a personal ID which is the primary key of the personal database 112, a service flag which specifies the usage status of the service, and the like.

[0022] Fig. 3 is a diagram showing an example of management data stored in the management data storage unit 10 of this embodiment. As shown in Fig. 3, the ID management unit 11 stores and manages various management data using an employee master shown in Fig. 3(a), a personal master shown in Fig. 3(b), a login management master shown in Fig. 3(c), and a linked service management master shown in Fig. 3(d).

[0023] The employee master shown in FIG. 3(a) is a database that stores master information about employees on the enterprise service 101, and stores a company ID, which is identification information for the company, an employee number, an integrated ID, a name, a date of birth, an email address, and an enterprise login ID, which are identification information for employees within the company. Employee attribute information (company ID, employee number, name, date of birth, email address) excluding the integrated ID and enterprise login ID is input from a user terminal 2 by an administrator of the company or the like when the company is registered as a user of the enterprise service 101. The ID management unit 11 stores the attribute information of each employee input from the user terminal 2 in the employee master. Furthermore, for each employee whose attribute information is stored in the employee master, the ID management unit 11 generates a company login ID and an integrated ID that can be uniquely identified within the enterprise service 101 and stores them in the employee master. When an employee is transferred due to resignation or other reasons, the ID management unit 11 deletes the employee's data from the employee master.

[0024] Here, the corporate ID is input from the user terminal 2, but it may also be generated by the ID management unit 11. Furthermore, the corporate login ID generated by the ID management unit 11 can be changed by the employee himself / herself. However, this is only possible if the employee is logged in to the corporate service 101, and the employee's identity is verified by two-factor authentication or the like before the corporate login ID can be changed.

[0025] The personal master shown in Figure 3(b) is a database that stores master information about individuals on the personal service 102, and stores personal ID, name, date of birth, email address, mobile phone number, recovery code, and personal login ID. The individual here may or may not be an employee of the company that has registered to use the corporate service 101. In other words, an individual can use the personal service 102 regardless of whether or not they are an employee of the company that has registered to use the corporate service 101.

[0026] When an individual registers as a user of the personal service 102, the individual's attribute information (name, date of birth, email address, mobile phone number) excluding the personal ID, recovery code, and personal login ID is input by the individual from the user terminal 2. The ID management unit 11 stores the attribute information of each individual input from the user terminal 2 in the personal master. The ID management unit 11 also generates a personal ID, recovery code, and personal login ID that can be uniquely identified within the personal service 102 for each individual whose attribute information is stored in the personal master, and stores these in the personal master. If the individual instructs to stop using the personal service 102, the ID management unit 11 deletes the individual's data from the personal master.

[0027] The recovery code is a code used to initialize a user's personal login ID or password if the user forgets it, and is a code known only to the service provider and the individual. This recovery code is used for identity authentication when the individual specifies integrated use of the corporate service 101 and the individual service 102. For this purpose, the ID management unit 11 notifies the individual of the generated recovery code by sending it to the user terminal 2. When specifying integrated service use, the individual receives identity authentication by inputting the recovery code notified in advance from the user terminal 2 and sending it to the service usage management server 1. In addition to the recovery code, individual attribute information may also be used for authentication.

[0028] The individual can change the personal login ID generated by the ID management unit 11. However, this is possible only if the individual is logged in to the personal service 102 and has undergone identity verification using two-factor authentication or the like before changing the personal login ID.

[0029] The login management master shown in Figure 3(c) is a database that stores master information used to manage logins by users to the corporate services 101 and the personal services 102, and stores corporate and personal login IDs, integrated IDs, personal IDs, service flags, and login passwords. The data stored in the login management master is data used to set and release the association between the corporate database 111 and the personal database 112, and the data is updated as appropriate depending on the usage status of the corporate services 101 and the personal services 102. Note that the login password may also be stored in the employee master and the personal master.

[0030] The service flag is identification information that specifies the usage status of the service, and takes on any value from "1" to "3." When the value of the service flag is "1," it indicates that the employee is registered with the corporate service 101. When the value of the service flag is "2," it indicates that the individual is registered with the personal service 102, and integrated use with the corporate service 101 is not specified. When the value of the service flag is "3," it indicates that the individual is registered with the personal service 102, and integrated use with the corporate service 101 is specified.

[0031] If the user is an employee of a company registered with the corporate service 101, the corporate login ID, integrated ID, service flag, and login password are stored in the login management master as employee management information. In this case, the value of the service flag is "1." If the user is an individual registered with the personal service 102, the personal login ID, personal ID, service flag, and login password are stored in the login management master as personal management information. In this case, the value of the service flag is "2" or "3."

[0032] When both employee management information and personal management information are stored in the login management master, the employee number used as the primary key in the corporate database 111 (associated with the integrated ID in the employee master) and the personal ID used as the primary key in the personal database 112 (associated with the integrated ID in the login management master) are associated by the integrated ID. However, whether or not this association is utilized is determined by the value of the service flag in the personal management information. If the value of the service flag is "2," the association is not utilized, and if the value of the service flag is "3," the association is utilized.

[0033] The ID management unit 11 switches whether or not to associate the corporate database 111 and the personal database 112 with each other by an integrated ID depending on whether or not the integrated use of the corporate service 101 and the personal service 102 is specified for each employee, that is, depending on whether the value of the service flag is "2" or "3."

[0034] That is, in response to the designation of integrated use of the corporate service 101 and the personal service 102, the ID management unit 11 switches the value of the service flag from "2" to "3," thereby maintaining the association between the employee number in the corporate database 111 and the personal ID in the personal database 112. In addition, in response to the designation of integrated use being canceled, the ID management unit 11 switches the value of the service flag from "3" to "2," thereby canceling the association between the employee number and the personal ID.

[0035] 3(d) stores master information for defining database associations when the enterprise service 101 is associated with an external service (not shown). That is, when the enterprise service 101 is associated with an external service, the association between the enterprise ID of the enterprise database 111 used by the enterprise service 101 and the enterprise ID of the database used in the external service is defined, and the association between the employee number in the enterprise database 111 and the employee ID of the database used in the external service is defined.

[0036] The login management unit 12 performs authentication by referring to the management data stored in the management data storage unit 10 based on the login ID and login password input from the user terminal 2, and logs in to the corporate service 101 or the personal service 102. If the value of the service flag in the employee management information of the login management master is set to "1" and a corporate login ID is input from the user terminal 2, the login management unit 12 executes login to the corporate service 101. Also, if the value of the service flag in the personal management information of the login management master is set to "2" and a personal login ID is input from the user terminal 2, the login management unit 12 executes login to the personal service 102.

[0037] Furthermore, when the value of the service flag is set to "3" in the personal management information of the login management master, the login management unit 12 prohibits login to the personal service 102 based on the personal login ID, and permits login to the corporate service 101 only based on the corporate login ID. In other words, during the period when the integrated use of the corporate service 101 and the personal service 102 is designated, the login management unit 12 permits login only based on the corporate login ID and executes login to the corporate service 101.

[0038] During a period when integrated use of corporate service 101 and personal service 102 is designated (i.e., during a period when the value of the service flag in the personal management information of the login management master is set to "3"), synchronization processing unit 13 performs synchronization processing of health-related data between corporate database 111 and personal database 112 associated by the integrated ID. For example, synchronization processing unit 13 performs synchronization processing periodically (for example, every other day).

[0039] As described above, during the period when integrated use of services is specified, only login to corporate service 101 is permitted, and therefore, newly added data, both corporate-acquired health-related data and personally-acquired health-related data, is stored in corporate database 111 via corporate service 101. Then, as a result of synchronization processing by synchronization processing unit 13, the health-related data added to and stored in corporate database 111 is also stored in personal database 112. In this case, for personal database 112 corresponding to personal service 102 for which login is not permitted by login management unit 12, changes are made only through synchronization processing.

[0040] In this way, by associating the employee number used as the primary key in the corporate database 111 with the personal ID used as the primary key in the personal database 112 using an integrated ID, it is possible to synchronize the health-related data stored in the corporate database 111 of the corporate service 101 and the health-related data stored in the personal database 112 of the personal service 102 with each other, and to store the same health-related data in both the corporate database 111 and the personal database 112.

[0041] As a result, even if an employee resigns and is unregistered from the corporate service 101 of the company from which the employee is transferred, the synchronized health-related data is stored in the personal database 112 of the personal service 102, and can be used in conjunction with the corporate service 101 used by the company to which the employee is transferred (data portability). In this case, it is only necessary to update the management data in the management data storage unit 10, and there is no need to reconstruct the corporate database 111 and the personal database 112.

[0042] 4 is a diagram showing state transitions related to the corporate service 101. State (1) indicates a state in which a company has not yet registered with the corporate service 101, or a state in which an employee of a company registered with the corporate service 101 has been deregistered from the corporate service 101 due to resignation or the like. In this state, information about the employee is not stored in the employee master, and employee management information about the employee is not stored in the login management master either.

[0043] State (2) shows a state in which an employee is registered in the corporate service 101. When an employee's attribute information is registered in the employee master by a corporate administrator or the like, the ID management unit 11 generates a corporate login ID and an integrated ID using the employee's employee number as a key and stores them in the employee master, and also stores the employee management information in the login management master and sets the value of the service flag to "1." In this state, the corporate login ID, employee number, and integrated ID are associated with each other.

[0044] When the integrated use of the corporate service 101 and the personal service 102 is not specified, only the integrated ID is associated as employee management information using the corporate login ID as a key in the login management master, and the personal ID is not associated. Also, by setting the value of the service flag to "1", the service provided when an employee logs in with the corporate login ID is the corporate service 101.

[0045] State (3) indicates a state in which integrated use of the corporate service 101 and the personal service 102 is specified. Employees registered with the corporate service 101 can register with the personal service 102 to use the data portability function and specify integrated use of the services. In this state, the login management master stores both employee management information using the corporate login ID as a key and personal management information using the personal login ID as a key, and a personal ID is associated with the integrated ID. Then, the synchronization processing unit 13 performs synchronization processing of health-related data between the corporate database 111 and the personal database 112.

[0046] Furthermore, the value of the service flag is set to "1" in the employee management information of the login management master, and the value of the service flag is set to "3" in the personal management information (see FIG. 5). As a result, the login management unit 12 does not permit login to the personal service 102 even when a personal login ID is entered, but permits login only to the corporate service 101 when a corporate login ID is entered. This makes it possible to prevent conflicts during synchronization of health-related data performed by the synchronization processing unit 13.

[0047] 5 is a diagram showing state transitions related to the personal service 102. State (A) shows a state in which an individual has not yet registered with the personal service 102, or a state in which an individual who previously registered with the personal service 102 has subsequently canceled the service. In this state, no information about the individual is stored in the personal master, and no personal management information about the individual is stored in the login management master either.

[0048] State (B) indicates a state in which an individual has been registered with the personal service 102. A transition from state (A) to state (B) occurs when the individual performs the registration process for the personal service 102 themselves. When the individual registers the individual's attribute information in the personal master by the individual himself / herself, the ID management unit 11 generates a personal ID and a personal login ID for the individual and stores them in the personal master, and also stores the personal management information in the login management master and sets the value of the service flag to "2."

[0049] When the integrated use of the corporate service 101 and the personal service 102 is not specified, only the personal ID is associated as personal management information using the corporate login ID as a key in the login management master. Also, by setting the value of the service flag to "2", the association by the integrated ID is not utilized, and the service provided when an individual logs in with the personal login ID is the personal service 102.

[0050] State (C) indicates a state in which integrated use of the corporate service 101 and the personal service 102 is specified. If an individual registered with the personal service 102 is also an employee of a company registered with the corporate service 101, integrated use of the services can be specified in order to utilize the data portability function. In this state, both employee management information and personal management information are stored in the login management master, and a personal ID is associated with the integrated ID. Then, the synchronization processing unit 13 performs synchronization processing of health-related data between the corporate database 111 and the personal database 112.

[0051] Furthermore, the value of the service flag in the personal management information of the login management master is set to "3." As a result, the login management unit 12 does not permit login to the personal service 102 even when a personal login ID is entered, but permits login only to the corporate service 101 when a corporate login ID is entered. This makes it possible to prevent conflicts during synchronization of health-related data performed by the synchronization processing unit 13.

[0052] Fig. 6 is a diagram showing possible combinations of the states of the business services 101 shown in Fig. 4 and the states of the personal services 102 shown in Fig. 5. In Fig. 6, as a combination of the usage states of the business services 101 and the personal services 102 for a certain user, a possible combination is indicated by ◯, and a possible combination is indicated by -.

[0053] As shown in Fig. 6, states (1) and (2) of the business service 101 shown in Fig. 4 and states (A) and (B) of the personal service 102 shown in Fig. 5 exist as completely independent events, and four possible combinations of the respective states can occur: a state in which the user is not registered in either the business service 101 or the personal service 102, a state in which the user is registered in only one of the business service 101 or the personal service 102, and a state in which the user is registered in both the business service 101 and the personal service 102.

[0054] 4 and state (C) of the service for individuals 102 shown in FIG. 5 are states in which the integrated use of the service for individuals 102 and the service for individuals 101 is specified, and therefore no combinations with other states are possible. That is, no combination exists between state (3) of the service for individuals 102 and state (A) or (B) of the service for individuals 102, and no combination exists between state (C) of the service for individuals 102 and state (1) or (2) of the service for individuals 101. Furthermore, state transitions with state (3) of the service for individuals 101 occur only with state (2), and state transitions with state (C) of the service for individuals 102 occur only with state (B).

[0055] That is, the transition from state (2) to state (3) of the business service 101 and the transition from state (B) to state (C) of the personal service 102 occur simultaneously. Conversely, the transition from state (3) to state (2) of the business service 101 and the transition from state (C) to state (B) of the personal service 102 also occur simultaneously.

[0056] Fig. 7 is a flowchart showing the flow of authentication processing executed when specifying integrated use of the business service 101 and the personal service 102. The flowchart shown in Fig. 7 starts when the business service 101 is in state (2) and the personal service 102 is in state (B), and the integrated use of the services is specified by a user who is logged in to the business service 101.

[0057] The user enters the login ID integration service (data portability service) from the web screen of the corporate service 101 and inputs a personal login ID. The ID management unit 11 refers to the personal master in the management data storage unit 10 and determines whether the input personal login ID exists (step S1). If the personal login ID does not exist in the personal master, the processing of the flowchart shown in FIG. 7 ends.

[0058] On the other hand, if the input personal login ID exists in the personal master, the ID management unit 11 accepts input of the name, date of birth, email address, and recovery code from the user terminal 2 as information for identity verification (step S2). Then, the ID management unit 11 determines whether the information input from the user terminal 2 matches the information in the personal master (step S3). Here, if the input information does not match the information in the personal master, the processing of the flowchart shown in FIG. 7 ends.

[0059] On the other hand, if the input information matches the information in the personal master, the ID management unit 11 uses the mobile phone number stored in the personal master to send a code for two-factor authentication and accepts input of the code from the user terminal 2 (step S4). Then, the ID management unit 11 determines whether the input code matches the sent code (step S5). Here, if the input code does not match the sent code, the processing of the flowchart shown in FIG. 7 ends.

[0060] On the other hand, if the entered code matches the transmitted code, the ID management unit 11 updates the value of the service flag in the personal management information of the login management master from "2" to "3," thereby associating the employee number in the corporate database 111 with the personal ID in the personal database 112 by the integrated ID (step S6). As a result, the corporate service 101 transitions to state (3), and the personal service 102 transitions to state (C).

[0061] This state transition causes the synchronization processing unit 13 to start synchronization processing between the corporate database 111 and the personal database 112 (step S7). Furthermore, the login management unit 12 prohibits login to the personal service 102 based on the personal login ID, and permits login only to the corporate service 101 based on the corporate login ID (step S8). This completes the processing of the flowchart shown in FIG. 7.

[0062] As explained in detail above, in this embodiment, depending on whether or not integrated use of the corporate service 101 and the personal service 102 is specified for each employee, whether or not the employee number used as the primary key in the corporate database 111 and the personal ID used as the primary key in the personal database 112 are associated by an integrated ID is switched.

[0063] According to this embodiment configured as described above, when there is no association based on an integrated ID, when a user logs in to the corporate service 101 using a corporate login ID, only the data in the corporate database 111 can be used, and when a user logs in to the personal service 102 using a personal login ID, only the data in the personal database 112 can be used. On the other hand, when there is association based on an integrated ID, when a user logs in to the corporate service 101 using a corporate login ID, data can be used with the corporate database 111 and personal database 112 associated with each other.

[0064] Specifically, by updating health-related data in the corporate database 111 while synchronizing the health-related data between the corporate database 111 and the personal database 112, it becomes possible to store the same health-related data in both the corporate database 111 and the personal database 112.

[0065] As a result, when an employee changes jobs, resigns, or otherwise changes jobs, simply by canceling the integrated ID at the company from which the employee was transferred and setting an integrated ID at the company to which the employee is transferred, personal database 112 becomes unavailable at the company from which the employee was transferred, and personal database 112 becomes available at the company to which the employee is transferred by associating it with corporate database 111 of the company to which the employee is transferred. At this time, because the health-related data synchronized before the transfer is stored in personal database 112, it can be used in conjunction with corporate service 101 used by the company to which the employee is transferred. As such, according to this embodiment, even when an employee changes jobs, resigns, or otherwise changes jobs, portability can be achieved, in which health-related data can be used by switching from the company from which the employee was transferred to the company to which the employee was transferred, by simply updating the management data in management data storage unit 10, without rebuilding the database.

[0066] In the above embodiment, an example was described in which, when both employee management information (including an integrated ID) and personal management information are stored in the login management master, the value of the service flag in the personal management information is updated from "2" to "3" to switch whether or not the corporate database 111 and the personal database 112 are associated by an integrated ID, but the present invention is not limited to this. For example, whether or not the corporate database 111 and the personal database 112 are associated by an integrated ID may be switched depending on whether or not the integrated ID is stored in the employee management information, depending on whether or not the integrated use of the corporate service 101 and the personal service 102 is specified.

[0067] That is, if the user is an employee of a company registered with the corporate service 101, the ID management unit 11 stores the service flag "1" and the login password in the login management master as employee management information using the corporate login ID as a key. The integrated ID is not stored in the login management master when integrated use of the services is not specified (2), but is stored in the login management master when integrated use is specified (3). Also, if the user is an individual registered with the personal service 102, the ID management unit 11 stores the personal ID, service flag, and login password in the login management master as personal management information using the personal login ID as a key. The value of the service flag is set to "2" when integrated use of the services is not specified (B), and to "3" when integrated use is specified (C).

[0068] That is, in response to the designation of integrated use of the service, the ID management unit 11 stores an integrated ID in the login management master, thereby associating the employee number used as a primary key in the corporate database 111 with the personal ID used as a primary key in the personal database 112. In addition, in response to the designation of integrated use being canceled, the ID management unit 11 deletes the integrated ID from the login management master, thereby canceling the association between the employee number and the personal ID.

[0069] Furthermore, in the above embodiment, a configuration has been described in which, during a period in which integrated use of the corporate service 101 and the personal service 102 is designated, logins are permitted only from corporate login IDs, and changes are made only through synchronization processing to the personal database 112 corresponding to the personal service 102 for which logins are not permitted, but the present invention is not limited to this. For example, a configuration may be adopted in which only logins from personal login IDs are permitted, and changes are made only through synchronization processing to the corporate database 111 corresponding to the corporate service 101 for which logins are not permitted.

[0070] 3 is an example and is not limited to this. For example, the integrated ID may be stored in the personal master instead of the employee master, and the employee number may be stored in the login management master instead of the integrated ID as employee management information, and the integrated ID and personal ID may be stored as personal management information.

[0071] Furthermore, the above-described embodiments are merely examples of specific embodiments for carrying out the present invention, and the technical scope of the present invention should not be construed as being limited thereby. In other words, the present invention can be carried out in various forms without departing from the gist or main characteristics thereof. [Explanation of symbols]

[0072] 1. Service Usage Management Server (Management Server) 2. User terminal 10 Management data storage unit 11 ID Management Department 12 Login Management Department 13 Synchronization processing section 101 Corporate Services 102 Personal Services 111 Corporate Databases 112 Personal Database

Claims

1. an ID management unit that manages an integrated ID used to control the integrated use of a corporate service that can use a corporate database that stores employee health-related data acquired by a company and an individual service that can use a personal database that stores the individual health-related data acquired by an individual, The ID management unit switches whether or not to associate the corporate database and the personal database with each other by the integrated ID, depending on whether or not integrated use of the corporate service and the personal service is specified for each employee. A health information management system characterized by:

2. The health information management system described in claim 1, further comprising a synchronization processing unit that performs synchronization processing of the health-related data between the corporate database and the personal database associated by the integrated ID during a period in which integrated use of the corporate service and the personal service is designated.

3. a login management unit that permits only login based on either a corporate login ID used to log in to the corporate service or a personal login ID used to log in to the personal service during a period in which integrated use of the corporate service and the personal service is designated; Of the corporate database and the personal database, databases corresponding to services for which login is not permitted by the login management unit are changed only by the synchronization process. The health information management system according to claim 2 .

4. an ID management unit that manages an integrated ID used to control the integrated use of a corporate service that can use a corporate database that stores employee health-related data acquired by a company and an individual service that can use a personal database that stores the individual health-related data acquired by an individual, The ID management unit switches whether or not to associate the corporate database and the personal database with each other by the integrated ID, depending on whether or not integrated use of the corporate service and the personal service is specified for each employee. A management server comprising:

Images