Health management server, health management system, and program

Abstract

To provide a health management server, a health management system, and a program which suitably manage information from a plurality of medical facilities or information shared by the plurality of medical facilities.SOLUTION: A health management server 10 includes: a first association section (control section 11) for associating a PHR account of a patient on health management service with an SNS account of the patient on SNS service by using unique identification information on a first medical facility and unique identification information on the patient; and a second association section (control section 11) for associating the PHR account of the patient with the SNS account of the patient by using unique identification information on a second medical facility and the unique identification information on the patient.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a health management server, a health management system, and a program. [Background technology]

[0002] Conventionally, medical facilities provide various information to patients who undergo diagnosis or treatment at the medical facility. In this regard, for example, Patent Document 1 proposes a technique in which an information processing device that has accepted a message transmission request from a company server transmits the message to a user.

[0003] Furthermore, the medical facility may send a message to a patient's account on a social networking service (SNS) that is linked to the medical facility's SNS account. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-4302 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, there are cases where a patient's SNS account is linked to the SNS accounts of multiple medical facilities. In this case, a health management application (hereinafter referred to as "health management app") account for the same patient is generated for each medical facility based on the link. The health app account of each medical facility is linked to the health app account of the same patient for each medical facility. In this case, there is a problem that the patient cannot collectively manage medical information from multiple medical facilities or share his / her own health record information with multiple medical facilities in the health app.

[0006] An object of the present invention is to provide a health management server, a health management system and a program that can suitably manage information from a plurality of medical facilities or information shared by a plurality of medical facilities. [Means for solving the problem]

[0007] In order to solve the above problem, the health management server according to claim 1 comprises: a first linking unit that links a PHR account of a patient on a health management service with an SNS account of the patient on an SNS service by using unique identification information of a first medical facility and unique identification information of the patient; a second linking unit that links the PHR account and the SNS account using unique identification information of a second medical facility and the unique identification information of the patient; Equipped with.

[0008] The invention described in claim 2 is the health management server described in claim 1, the first linking unit links the PHR account of the patient with the SNS account of the first medical facility in a state in which the SNS account of the patient and the SNS account of the first medical facility are linked on the SNS service; The second linking unit links the patient's PHR account with the patient's SNS account and the PHR account of the second medical facility when the patient's SNS account and the second medical facility's SNS account are linked on the SNS service.

[0009] The invention described in claim 3 is the health management server according to claim 1, The system includes a transmission unit that transmits a questionnaire that reflects the answers of the past patient to items that are common to the questionnaire results previously answered by the patient to a terminal corresponding to the patient.

[0010] The invention described in claim 4 is the health management server according to claim 1, an acquisition unit for acquiring said patient's health record information; and a matching unit that matches the health record information acquired by the acquisition unit with the patient's PHR account.

[0011] The health management system according to claim 5 comprises: A health management server according to claim 1; The SNS service includes a control unit that displays, when the patient's SNS account and the medical facility's SNS account are linked on the SNS service, an instruction means for linking the patient's PHR account and the medical facility's PHR account on a display unit of a terminal corresponding to the patient.

[0012] The program according to claim 6 comprises: The health management server computer, a first linking unit that links a PHR account of a patient on a health management service with an SNS account of the patient on an SNS service using unique identification information of a first medical facility and unique identification information of the patient; a second linking unit that links the PHR account and the SNS account using unique identification information of a second medical facility and the unique identification information of the patient; Function as. Effect of the Invention

[0013] According to the present invention, information from a plurality of medical facilities or information shared among a plurality of medical facilities can be appropriately managed. [Brief description of the drawings]

[0014] [Figure 1] 1 is a diagram showing a system configuration of a health management system according to an embodiment of the present invention. [Diagram 2] 5A to 5C are diagrams illustrating an example of the data configuration of each table stored in a storage unit of the health management server. [Diagram 3] FIG. 13 is a diagram illustrating an example of a questionnaire setting file. [Figure 4] 1 is a ladder chart showing a linkage process executed in a health management system. [Diagram 5] 13 is an example of a talk screen displayed on a patient terminal. [Figure 6] 11 is a ladder chart showing a linking request process executed in the health management system. [Figure 7] 11 is a flowchart showing a linking process executed in the health management system. [Figure 8] 13 is an example of a new registration screen displayed on a patient terminal. [Figure 9] 13 is an example of a first questionnaire screen displayed on a patient terminal. [Figure 10] 13 is an example of a link addition screen displayed on a patient terminal. [Figure 11] A diagram showing an example of linking a patient's PHR account with the patient's SNS account. [Figure 12] 13 is an example of a second questionnaire screen displayed on the patient terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of a health management system according to the present invention will be described with reference to the drawings, however, the scope of the invention is not limited to the illustrated examples.

[0016] [Health management system configuration] FIG. 1 shows a system configuration of a health management system 100 according to the present embodiment. As shown in FIG. 1, the health management system 100 includes a health management server 10, a patient terminal 20, a first medical facility terminal 30A, and a second medical facility terminal 30B. The health management system 100 can be connected to an SNS server 40 via a communication network N such as the Internet. The health management server 10, the patient terminal 20, the first medical facility terminal 30A, the second medical facility terminal 30B, and the SNS server 40 perform data communication via a communication network N.

[0017] The health management server 10 provides a health management service, and accumulates and manages medical information related to patients. The health management server 10 may be a cloud server provided in a cloud environment. The patient terminal 20 is a terminal device such as a smartphone used by a patient. The first medical facility terminal 30A is a computer device such as a PC (Personal Computer) or a tablet terminal used by a medical professional such as a doctor belonging to the first medical facility. The second medical facility terminal 30B is a computer device such as a PC or a tablet terminal used by a medical professional such as a doctor belonging to the second medical facility. Hereinafter, the first medical facility terminal 30A and the second medical facility terminal 30B are also collectively referred to as the medical facility terminal 30. The number of patient terminals 20 and medical facility terminals 30 is not limited. The patient terminal 20 and the medical facility terminal 30 are used when registering medical information in the health management server 10, when referring to medical information managed by the health management server 10, and the like.

[0018] The SNS server 40 provides each account using the SNS with a function for sending and receiving messages via a message application (hereinafter referred to as a "message app"). The standard application provided by the SNS server 40 performs registration of the official SNS account and profile of the medical facility, etc. The SNS provided by the SNS server 40 is, for example, an existing service such as LINE (registered trademark), Facebook (registered trademark), or Instagram (registered trademark).

[0019] [Health Management Server Configuration] As shown in FIG. 1, the health management server 10 includes a control unit 11, a communication unit 12, a storage unit 13, etc., and each unit is connected via a bus.

[0020] The control unit 11 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), etc., and comprehensively controls the processing operations of each unit of the health management server 10. Specifically, the CPU of the control unit 11 reads out various processing programs stored in the storage unit 13, expands them in the RAM, and executes various processes in cooperation with the programs.

[0021] The communication unit 12 is configured with a network interface and the like, and transmits and receives data to and from external devices connected via the communication network N.

[0022] The storage unit 13 includes a hard disk drive (HDD), a solid state drive (SSD), etc., and stores various processing programs, parameters and files necessary for executing the programs, etc. For example, the storage unit 13 stores a web server program for implementing a function as a web server that communicates with a web browser installed in an external device by HTTP protocol and provides various web screens to the web browser. The storage unit 13 stores application programs that run on the web server.

[0023] FIG. 2 shows an example of the data configuration of each table stored in the storage unit 13. As shown in FIG. The memory unit 13 stores a facility information table T1, a patient information table T2, a questionnaire result table T3, a medical information table T4, a blood pressure information table T5, a medication information table T6, a diet information table T7, a mood information table T8, and the like.

[0024] The facility information table T1 stores facility information for each medical facility. Specifically, the facility information table T1 associates a facility ID, a facility name, a facility address, a telephone number, a facility SNS account, and the like. The facility ID is identification information given to a facility. The facility name is the name of the facility. The facility address is the address of the facility. The telephone number is the telephone number of the facility. The facility SNS account is a user ID of the facility's account in the SNS provided by the SNS server 40. The facility SNS account is unique identification information of the medical facility.

[0025] The patient information table T2 stores patient information for each patient. Specifically, the patient information table T2 associates a patient UUID (Universally Unique Identifier), a facility ID, a name, a date of birth, an address, a sex, a current medical history, a medical history, a telephone number, a patient SNS account, and the like. The patient UUID is an identification given to a patient. The facility ID is the facility ID of the facility where the patient receives medical treatment. Name is the patient's name. Date of birth is the patient's date of birth. The address is the address of the patient. Gender is the gender of the patient. History of present illness is information about illnesses the patient currently suffers from. Medical history is information about illnesses a patient has had in the past and is now cured. The telephone number is the telephone number of the patient terminal 20. The patient SNS account is a user ID of a patient's account in an SNS provided by the SNS server 40. The patient SNS account is unique identification information of the patient.

[0026] The questionnaire result table T3 stores the questionnaire results for each patient. Specifically, the questionnaire result table T3 associates a facility ID, a patient UUID, an answer to item 1, an answer to item 2, . . . , and so on. The facility ID is the facility ID of the facility where the patient receives medical treatment. PatientUUID is the Patient UUID of the patient. The answer to item i (i=1, 2, 3, . . .) is the answer to the questionnaire for item i (survey result).

[0027] Here, a specific example of a questionnaire will be described. An example of a questionnaire setting file is shown in Fig. 3. The questionnaire setting file defines the questions and options of a questionnaire for patients, and is stored in the storage unit 13. In the questionnaire setting file, the questionnaire question text and the questionnaire options are set for each questionnaire item. The questionnaire question text and the questionnaire options are not limited to the example shown in Fig. 3.

[0028] The survey questions are those asked in surveys aimed at patients. Item 1 is a survey about the health information patients would like to receive. Item 2 is a survey about the age group for which they would like to receive notifications for children. Item 3 is a survey about whether or not they would like to receive an influenza vaccination. Item 4 is a survey about whether or not they would like to receive a fourth dose of the COVID-19 vaccine. The survey options are options that are displayed as answers to a survey. Note that options are not displayed for items in which numbers or letters are directly input.

[0029] The medical information table T4 stores medical information for each patient. Specifically, the medical information table T4 associates a patient UUID, a facility ID, a target date, medical information, etc. PatientUUID is the Patient UUID of the patient. The facility ID is the facility ID of the facility where the patient receives medical treatment and is the facility ID of the facility that generated the medical information. The date of interest is the date on which medical information was obtained at the facility. The medical information includes medical images, test result information, diagnosis result information, and the like generated in the facility.

[0030] The blood pressure information table T5 stores the blood pressure information of the patient. The blood pressure information is one of the vital information of the health record information. Specifically, the blood pressure information table T5 associates the patient UUID, the target date, the systolic blood pressure, the diastolic blood pressure, and the like. PatientUUID is the Patient UUID of the patient. The date of interest is the date on which blood pressure was measured. The systolic blood pressure and the diastolic blood pressure are the measurement results of blood pressure. Here, blood pressure is taken as an example of vital information, but heart rate, body temperature, blood glucose level, SpO2 (percutaneous arterial oxygen saturation), etc. may also be used.

[0031] The medication information table T6 stores medication information related to the patient's medication. Medication information is one type of health record information. The medication information table T6 associates patient UUIDs, target dates, drug categories, medication results, and the like. PatientUUID is the Patient UUID of the patient. The target date is the date that is the subject of the medication information. The drug category is information that indicates the distinction between therapeutic drugs and quick-acting drugs. The medication result is information indicating the result of the patient's selection of either "taken" or "taken some." If the patient does not select either, the medication result will be "not selected."

[0032] The meal information table T7 stores meal information related to the patient's meal. Meal information is one of the health record information. The meal information table T7 associates the patient UUID, the target date, the photo path, the target time, and the like. PatientUUID is the Patient UUID of the patient. The target date is the date on which the meal information was included. The photo path is a path indicating the storage location of image data of a photo taken of a meal ingested by a patient. The time of interest is the time at which the patient ingests a meal. The dietary information may also include the dietary content, nutrients contained in the diet, calorie intake, and the like.

[0033] Mood information table T8 stores mood information related to the mood of the patient. Mood information is one type of health record information. In mood information table T8, patient UUIDs, target dates, moods, etc. are associated with each other. PatientUUID is the Patient UUID of the patient. The target date is the date that was the target of the mood information. The mood is information indicating the result of the patient's selection from "good," "normal," "bad," "very bad," etc. If the patient does not select any of the above, the mood will be "unselected."

[0034] The control unit 11 obtains the patient's health record information. Health record information is information related to the health of a patient. Health record information includes, for example, vital sign information, medication information, dietary information, mood information, exercise information, and the like. Health record information is, for example, information that is continuously recorded. Health record information is information for grasping health trends. Exercise information includes information on the exercise performed by the patient (type, number of times, time, etc.), number of steps, distance traveled, and the like. Health record information may also include measurement results such as weight.

[0035] The medical information on patients managed by the health management server 10 includes medical information sent from the medical facility terminal 30, health record information sent from the patient terminal 20, and the like.

[0036] [Patient device configuration] As shown in FIG. 1, the patient terminal 20 includes a control unit 21, an operation unit 22, a display unit 23, a communication unit 24, a storage unit 25, etc., and each unit is connected via a bus.

[0037] The control unit 21 includes a CPU, a RAM, etc., and comprehensively controls the processing operations of each unit of the patient terminal 20. Specifically, the CPU of the control unit 21 reads out various processing programs stored in the storage unit 25 in response to an operation signal input from the operation unit 22 or an instruction signal received by the communication unit 24, expands the programs in the RAM, and executes various processes in cooperation with the programs.

[0038] The operation unit 22 includes operation keys such as a power key for turning the power on / off, and a touch panel laminated on the display unit 23. The operation unit 22 outputs to the control unit 21 an operation signal corresponding to each operation key and an operation signal according to the position of a touch operation by the operator's finger or the like.

[0039] The display unit 23 includes an LCD (Liquid Crystal Display) or the like, and displays various screens according to instructions of a display signal input from the control unit 21.

[0040] The communication unit 24 includes a network interface and the like, and transmits and receives data to and from external devices connected via the communication network N. The communication unit 24 performs wireless communication using a mobile phone line or the like, and transmits and receives data to and from external devices connected via the communication network N.

[0041] The storage unit 25 includes a HDD, a non-volatile semiconductor memory, etc., and stores various processing programs, parameters and files necessary for executing the programs, etc. For example, the storage unit 25 stores a Web browser program for implementing a Web browser, various application programs, etc.

[0042] A health management application program is installed on the patient terminal 20. The patient uses the health management service provided by the health management server 10 via the health management application. Specifically, the patient can register health record information (vital information, medication information, dietary information, mood information, etc.) to the health management server 10 on the health management application on the patient terminal 20. The patient can refer to medical information managed by the health management server 10 on the health management application on the patient terminal 20.

[0043] The control unit 21 transmits the health record information input from the operation unit 22 or the communication unit 24 to the health management server 10 via the communication unit 24. The health record information transmitted from the patient terminal 20 to the health management server 10 is associated with a target date (measurement date, input date, etc.). The control unit 11 of the health management server 10 stores the health record information transmitted from the patient terminal 20 in a blood pressure information table T5, a medication information table T6, a diet information table T7, and a mood information table T8.

[0044] The control unit 21 acquires the vital sign information from the vital sign measuring device via, for example, the communication unit 24. The control unit 21 may acquire the vital sign information input from the operation unit 22 by the patient. The control unit 21 acquires medication information and mood information inputted by the patient through the operation unit 22. The control unit 21 acquires, for example, image data generated by a camera mounted on the patient terminal 20 as an image of the meal. The control unit 21 may acquire the image of the meal from an external digital camera via the communication unit 24. The control unit 21 may analyze the image of the meal to acquire the meal contents, nutrients, and calorie intake, or may acquire the meal contents, nutrients, and calorie intake input by the patient via the operation unit 22.

[0045] A message application program provided by the SNS server 40 is installed in the patient terminal 20. The patient sends and receives messages to and from other accounts via the message application.

[0046] [Configuration of medical facility terminals] As shown in FIG. 1, the medical facility terminal 30 includes a control unit 31, an operation unit 32, a display unit 33, a communication unit 34, a storage unit 35, etc., and each unit is connected by a bus. The control unit 31, display unit 33, communication unit 34, and memory unit 35 of the medical facility terminal 30 are similar to the control unit 21, display unit 23, communication unit 24, and memory unit 25 of the patient terminal 20, respectively, and therefore their explanations are omitted.

[0047] The operation unit 32 includes a keyboard having cursor keys, character input keys, various function keys, etc., and a pointing device such as a mouse. The operation unit 32 outputs operation signals input by key operations on the keyboard or mouse operations to the control unit 31. When the medical facility terminal 30 is a tablet terminal or the like, the operation unit 32 includes operation keys such as a power key for turning the power on / off, and a touch panel or the like laminated on the display unit 33. The operation unit 32 outputs to the control unit 31 an operation signal corresponding to each operation key and an operation signal according to the position of a touch operation by the operator's finger or the like.

[0048] A medical facility application (hereinafter referred to as a "medical facility app") program is installed in the medical facility terminal 30. Medical staff such as doctors use the health management services provided by the health management server 10 via the medical facility app. A medical professional uploads medical information such as medical images, test results, and diagnosis results to the health management server 10 via a medical facility app on the medical facility terminal 30. The control unit 11 of the health management server 10 stores the medical information uploaded from the medical facility terminal 30 in a medical information table T4.

[0049] [Operation in health management system] Next, the operation of the health management system 100 will be described. 4 is a ladder chart showing the linking process executed in the health management system 100. The linking process is a process of linking an SNS account of a patient with an SNS account of a medical facility in an SNS provided by the SNS server 40. Linking a patient's SNS account with a medical facility's SNS account on an SNS means, for example, "adding them as friends" on LINE or Facebook, or "following" on Instagram.

[0050] (Coordination processing) The control unit 21 of the patient terminal 20 receives an operation instruction for linking to the SNS account of the medical facility in a message app provided by the SNS server 40 through an operation by the patient from the operation unit 22 (step A1). For example, the patient selects the SNS account of the medical facility to be linked on the message app and instructs linking. The patient may read a QR code (registered trademark) presented by the medical facility with a camera mounted on the patient terminal 20, set the link destination, and then instruct linking. Next, the control unit 21 transmits the link instruction information received in step A1 to the SNS server 40 (step A2).

[0051] The SNS server 40 links the patient's SNS account with the medical facility's SNS account based on the link instruction information received from the patient terminal 20 (step A3). This enables messages to be exchanged between the patient's SNS account and the medical facility's SNS account via a messaging app. 5 shows an example of a chat screen 231 with a first medical facility on a message app, which is displayed on the display unit 23 by the control unit 21. The control unit 21 displays on the chat screen 231 a menu area 231a.

[0052] Next, a description will be given of the linking request process shown in Fig. 6. The linking request process is a process for making a request to link a patient's health management application account (PHR (personal health record) account) with a PHR account of a medical facility. A patient's PHR account is identified by the patient UUID stored in patient information table T2. The PHR account of a medical facility is identified by the facility ID stored in the facility information table T1.

[0053] (Linking request processing) The control unit 21 of the patient terminal 20 receives an operation instruction for linking the patient's PHR account with the medical facility's PHR account in a message app provided by the SNS server 40 through the patient's operation on the operation unit 22 (step B1). It is assumed that the SNS account of the medical facility and the SNS account of the patient have already been linked in the above-mentioned linking process. In step B1, for example, if the patient wants to link the PHR account of the medical facility he or she uses (the first medical facility in the example shown in FIG. 5) to his or her own PHR account, the patient taps on the registration icon 231b in the menu area 231a. In other words, when the patient's SNS account and the medical facility's SNS account are linked on the SNS service, the control unit 21 displays a registration icon 231b (instruction means) on the display unit 23 of the patient terminal 20 (terminal corresponding to the patient) that links the patient's PHR account and the medical facility's PHR account.

[0054] In step B1, the control unit 21 may display a URL (Uniform Resource Locator) or the like for receiving an operational instruction for linking the patient's PHR account with the medical facility's PHR account on the talk screen 231. In this case, the patient taps on the URL displayed on the talk screen 231. Next, the control unit 21 transmits the linking instruction information received in step B1 to the SNS server 40 (step B2).

[0055] The SNS server 40 transmits instruction information for linking the patient's PHR account with the medical facility's PHR account to the health management server 10 based on the linking instruction information received from the patient terminal 20 (step B3). The linking instruction information includes the facility SNS account of the medical facility and the patient SNS account of the patient.

[0056] Next, the linking process shown in FIG. 7 will be described. When the control unit 11 of the health management server 10 receives instruction information for linking the patient's PHR account with the medical facility's PHR account from the SNS server 40, the control unit 11 executes the linking process.

[0057] (Linking process) The control unit 11 determines whether or not a PHR account for the patient exists based on the linking instruction information received from the SNS server 40 (step C1). Specifically, the control unit 11 determines whether or not the patient SNS account included in the received linking instruction information is stored in the patient information table T2. If the patient SNS account is not stored in the patient information table T2, that is, if the patient's PHR account does not exist (step C1; NO), the control unit 11 sends a new registration screen for the health management app to the patient terminal 20 via the SNS server 40 (skip C2). The control unit 21 of the patient terminal 20 displays the received new registration screen on the display unit 23.

[0058] FIG. 8 shows an example of a new registration screen 232 for the health management application, which is displayed on the display unit 23 of the patient terminal 20. In FIG. The new registration screen 232 includes answer fields 232a corresponding to each patient registration information, a send button 232b, etc. The patient registration information includes the patient's name, date of birth, address, sex, current medical history, past medical history, phone number, etc. The send button 232b is a button for instructing the sending of a response to the patient registration information.

[0059] The patient inputs a response to the patient registration information by operating the operation unit 22. The control unit 21 of the patient terminal 20 transmits the input response to the patient registration information to the health management server 10 via the communication unit 24.

[0060] The control unit 11 of the health management server 10 acquires the patient registration information entered on the new registration screen 232 via the communication unit 12 (step C3). Next, the control unit 11 generates a PHR account for the patient based on the patient registration information acquired in step C3 (step C4). Specifically, the control unit 11 associates the newly generated patient UUID with the acquired patient registration information and stores them in the patient information table T2. Next, the control unit 11 links the patient's PHR account generated in step C4 with the PHR account of the medical facility corresponding to the facility SNS account included in the linking instruction information (step C5). Specifically, the control unit 11 refers to the facility information table T1 and acquires a facility ID corresponding to the facility SNS account included in the linking instruction information. Next, the control unit 11 stores the acquired facility ID in the patient information table T2 in association with the patient's PHR account. This links the patient's PHR account, the patient's SNS account, and the medical facility's PHR account. That is, the control unit 11 links the patient's PHR account on the health management service and the patient's SNS account on the SNS service using the unique identification information of the first medical facility (facility SNS account) and the unique identification information of the patient (patient SNS account). The control unit 11 functions as a first linking unit. In the case where the patient SNS account is the patient's phone number, the patient's unique identification information may be the patient's phone number. In the case where the patient SNS account is the patient's email address, the patient's unique identification information may be the patient's email address.

[0061] Next, the control unit 11 generates a first questionnaire screen on which a questionnaire for the patient is described. Next, the control unit 11 transmits the generated first questionnaire screen to the patient terminal 20 via the SNS server 40 (step C6). The control unit 21 of the patient terminal 20 displays the received first questionnaire screen on the display unit 23.

[0062] 9 shows an example of a first questionnaire screen 233 displayed on the display unit 23 of the patient terminal 20. The first questionnaire screen 233 includes question areas 233a and 233b, radio buttons 233c and 233d corresponding to questionnaire options, a send button 233e, and the like. A survey question is displayed in the survey areas 233a and 233b. Any of the "survey questions" contained in the survey setting file (see FIG. 3) is displayed in the survey areas 233a and 233b. The radio buttons 233c and 233d are buttons for selecting one of the survey options. The survey options corresponding to the radio buttons 233c and 233d are displayed based on the "survey options" in the survey setting file. The send button 233e is a button for instructing the sending of the answers to the questionnaire.

[0063] The patient inputs answers to the questionnaire written on the first questionnaire screen by operating the operation unit 22. The control unit 21 of the patient terminal 20 transmits the input answers (questionnaire results) to the health management server 10 via the communication unit 24.

[0064] The control unit 11 of the health management server 10 acquires the patient's questionnaire results via the communication unit 12. In response to the patient's response, the control unit 11 associates the questionnaire results with the patient UUID of the patient and the facility ID of the first medical facility, stores the results in the questionnaire result table T3 (step C7), and ends the linking process.

[0065] The control unit 11 of the health management server 10 may obtain the questionnaire results from the patient not only when the linking process is executed. That is, the control unit 11 may repeatedly execute the processes of steps C6 and C7 at any timing. The timing at which information is registered in the patient information table T2 and the questionnaire result table T3 may be different. In particular, it is desirable to re-obtain the contents of the questionnaire result table T3 at a predetermined frequency before the information becomes outdated (before a discrepancy occurs between the information and the patient's current condition).

[0066] On the other hand, if a patient SNS account is stored in the patient information table T2, that is, if a PHR account for the patient exists (Step C1; YES), then the patient's PHR account is already linked to any facility PHR account. Hereinafter, it is assumed that the facility PHR account for the first medical facility is already linked to the patient's PHR account. It is assumed that the medical facility corresponding to the facility SNS account included in the linking instruction information received from the SNS server 40 is the second medical facility. That is, in the following process, the facility PHR account for the second medical facility is linked to the patient's PHR account that is linked to the facility PHR account for the first medical facility. In this case, the control unit 11 transmits a linking addition screen to the patient terminal 20 via the SNS server 40 (skip C8). The control unit 21 of the patient terminal 20 displays the received link addition screen on the display unit 23.

[0067] FIG. 10 shows an example of a link addition screen 234 displayed on the display unit 23 of the patient terminal 20. As shown in FIG. The link addition screen 234 includes a message 234a, an approval button 234b, and the like. The message 234a is a message indicating whether or not to link the PHR account of the second medical facility corresponding to the facility SNS account included in the linking instruction information with the PHR account of the patient. The approval button 234b is a button for approving linking the PHR account of the second medical facility corresponding to the facility SNS account included in the linking instruction information with the PHR account of the patient.

[0068] When the patient approves linking the PHR account of the second medical facility with the patient's PHR account, the patient taps the approval button 234b by operating the operation unit 22. The control unit 21 of the patient terminal 20 transmits linking approval information indicating that the approval button 234b has been tapped to the health management server 10 via the communication unit 24.

[0069] The control unit 11 of the health management server 10 acquires the linking approval information from the patient terminal 20 via the communication unit 12 (step C9). Next, the control unit 11 links the patient's PHR account with the PHR account of the second medical facility corresponding to the facility SNS account included in the linking instruction information (step C10). Specifically, the control unit 11 refers to the facility information table T1 and acquires a facility ID corresponding to the facility SNS account. Next, the control unit 11 stores the acquired facility ID in association with the patient's PHR account in the patient information table T2. This links the patient's PHR account, the patient's SNS account, and the PHR account of the second medical facility. That is, the control unit 11 links the patient's PHR account on the health management service and the patient's SNS account on the SNS service using the unique identification information of the second medical facility (facility SNS account) and the unique identification information of the patient (patient SNS account). The control unit 11 functions as a second linking unit. The second linking unit (control unit 11) links the patient's PHR account with the patient's SNS account using the same patient's unique identification information as the patient's unique identification information used by the first linking unit (control unit 11) for the linking. In the case where the patient SNS account is the patient's phone number, the patient's unique identification information may be the patient's phone number. In the case where the patient SNS account is the patient's email address, the patient's unique identification information may be the patient's email address.

[0070] Figure 11 shows an example of linking a patient's PHR account on a health management service with a patient's SNS account on an SNS service. 11, on the SNS service, the SNS account of the first medical facility and the SNS account of patient A have been linked through the above-mentioned linking process. On the SNS service, the SNS account of the first medical facility and the SNS account of the second medical facility have been linked through the above-mentioned linking process, and on the SNS service, the SNS account of the second medical facility and the SNS account of patient B have been linked through the above-mentioned linking process. On the SNS service, the SNS account of the second medical facility and the SNS account of patient C have been linked through the above-mentioned linking process. In the health management service, the PHR account of the first medical facility and the PHR account of patient A are linked by the above-mentioned linking process. The PHR account of the first medical facility and the PHR account of the second medical facility are linked by the above-mentioned linking process to the PHR account of patient B. The PHR account of the second medical facility and the PHR account of patient C are linked by the above-mentioned linking process. Patient A's PHR account and Patient A's SNS account are linked by the above linking process. Patient B's PHR account and Patient B's SNS account are linked by the above linking process. Patient C's PHR account and Patient C's SNS account are linked by the above linking process. As shown in Figure 11, even if Patient B's SNS account is linked to the SNS accounts of multiple medical facilities, Patient B's PHR account is not created for each medical facility. The PHR accounts of multiple medical facilities are linked to a single PHR account of Patient B. This allows Patient B to collectively manage test result information from multiple medical facilities and share his / her own health record information with multiple medical facilities in the health app.

[0071] Next, the control unit 11 acquires the past questionnaire results stored in association with the patient UUID from the questionnaire result table T3 (step C11). The past questionnaire results are, for example, the results of the questionnaire entered on the first questionnaire screen. Next, the control unit 11 generates a second questionnaire screen on which a questionnaire for the patient is described (step C12). The questionnaire items described on the second questionnaire screen may be different from the questionnaire items described on the first questionnaire screen. Next, the control unit 11 extracts items common to the questionnaire entered on the second questionnaire screen and the past questionnaire results acquired in step C11 (step C13). Next, the control unit 11 reflects the survey results previously answered by the patient in the common items (common items) extracted in step C13 in the second survey screen. The survey results previously answered by the patient are, for example, the results of the patient's responses to the survey written on the first survey screen. Next, the control unit 11 transmits the second survey screen to the patient terminal 20 via the SNS server 40 (step C14). That is, the control unit 11 transmits a questionnaire in which the answers by the patient in the past are reflected in the items common to the questionnaire results answered by the patient in the past to the patient terminal 20 (the terminal corresponding to the patient). The control unit 11 functions as a transmission unit. The control unit 21 of the patient terminal 20 displays the received second questionnaire screen on the display unit 23.

[0072] 12 shows an example of a second questionnaire screen 235 displayed on the display unit 23 of the patient terminal 20. The second questionnaire screen 235 includes question areas 235a and 235b, radio buttons 235c and 235d corresponding to the questionnaire options, a send button 235e, and the like. A survey question is displayed in the survey areas 235a and 235b. Any of the "survey questions" contained in the survey setting file (see FIG. 3) is displayed in the survey areas 235a and 235b. The radio buttons 235c and 235d are buttons for selecting one of the survey options. The survey options corresponding to the radio buttons 235c and 235d are displayed based on the "survey options" in the survey setting file. The send button 235e is a button for instructing the sending of a response to the questionnaire.

[0073] 12, the control unit 11 displays the results of questionnaires previously answered by the patient in the radio buttons 235c corresponding to the items written in the question area 235a, which are common items. This saves the patient the trouble of having to answer the items that they have answered before.

[0074] The patient inputs answers to the questionnaire written on the second questionnaire screen by operating the operation unit 22. The control unit 21 of the patient terminal 20 transmits the input answers (questionnaire results) to the health management server 10 via the communication unit 24.

[0075] The control unit 11 of the health management server 10 acquires the patient's questionnaire results via the communication unit 12. In response to the patient's response, the control unit 11 associates the questionnaire results with the patient UUID of the patient and the facility ID of the second medical facility, and stores them in the questionnaire result table T3 (step C7). Next, the control unit 11 ends the linking process.

[0076] Next, the process that is periodically executed will be described. The patient inputs health record information on the health management app in the patient terminal 20 by operating the operation unit 22. The control unit 21 of the patient terminal 20 associates the input health record information with the target date and transmits it to the health management server 10.

[0077] The control unit 11 of the health management server 10 acquires the patient's health record information from the patient terminal 20 via the communication unit 12. The control unit 11 functions as an acquisition unit. The control unit 11 saves the patient's health record information acquired from the patient terminal 20. Specifically, the control unit 11 stores the health record information (blood pressure information, medication information, diet information, mood information, etc.) in a blood pressure information table T5, a medication information table T6, a diet information table T7, a mood information table T8, etc., in association with the patient UUID and the target date of the patient corresponding to the patient terminal 20. This associates the patient's health record information with the patient's PHR account. The control unit 11 functions as an association unit.

[0078] [others] When transitioning from a chat screen with a first medical facility displayed on display unit 23 to a health management app, and when transitioning from a chat screen with a second medical facility to the health management app, control unit 21 displays the same login screen for the health management app on display unit 23.

[0079] [effect] As described above, the health management server 10 of this embodiment is equipped with a first linking unit (control unit 11) that links the patient's PHR account on the health management service and the patient's SNS account on the SNS service using the unique identification information of the first medical facility and the unique identification information of the patient. The health management server 10 of this embodiment includes a second linking unit (control unit 11) that links the patient's PHR account and the patient's SNS account using unique identification information of a second medical facility and the unique identification information of the patient. As a result, even if a patient's SNS account is linked to the SNS accounts of multiple medical facilities, the patient's PHR account is not created for each medical facility. Therefore, the patient can collectively manage test result information from multiple medical facilities and share his / her own health record information with multiple medical facilities in the health app. In other words, information from multiple medical facilities or information to be shared with multiple medical facilities can be appropriately managed.

[0080] In the health management server 10 of this embodiment, the first linking unit (control unit 11) links the patient's PHR account with the patient's SNS account and the PHR account of the first medical facility when the patient's SNS account and the SNS account of the first medical facility are linked on the SNS service. In the health management server 10 of this embodiment, the second linking unit (control unit 11) links the patient's PHR account with the patient's SNS account and the PHR account of the second medical facility when the patient's SNS account and the SNS account of the second medical facility are linked on the SNS service. This allows the PHR accounts of multiple medical facilities to be linked to one patient's PHR account, allowing the patient to collectively manage test result information from multiple medical facilities and share their own health record information with multiple medical facilities in the health app.

[0081] The health management server 10 of this embodiment has a transmission unit (control unit 11) that transmits a questionnaire that reflects the answers given by the patient in the past to items that are common to the questionnaire results answered by the patient in the past to a terminal corresponding to the patient (patient terminal 20). This saves the patient the trouble of having to answer questions again that they had answered before.

[0082] The health management server 10 of this embodiment includes an acquisition unit (control unit 11) that acquires health record information of patients. The health management server 10 of this embodiment includes an association section (control section 11) that associates the health record information acquired by the acquisition section with the patient's PHR account. This allows patients' health records to be managed on the health app.

[0083] The health management system 100 of this embodiment includes a health management server 10 and a control unit 21 that displays, on a display unit 23 of a terminal corresponding to the patient (patient terminal 20), an instruction means (registration icon 231b) for linking the patient's PHR account with the medical facility's PHR account when the patient's SNS account and the medical facility's SNS account are linked on an SNS service. This allows patients to easily perform the instruction operation to link their PHR account with the medical facility's PHR account.

[0084] The above-described embodiments are merely examples of the health management server, the health management system, and the program according to the present invention, and are not intended to limit the scope of the present invention. The detailed configurations and operations of the devices constituting the system may be modified as appropriate without departing from the spirit of the present invention.

[0085] For example, in the above embodiment, the control unit 11 of the health management server 10 functions as the first linking unit, the second linking unit, the transmission unit, the acquisition unit, and the association unit, but this is not limited to the above. A plurality of devices in the health management system 100 may share the functions.

[0086] The programs for executing the processes in each device may be stored in a portable recording medium. A carrier wave may be used as a medium for providing the program data via a communication line. [Explanation of symbols]

[0087] 10 Health Management Server 11 Control unit (first linking unit, second linking unit, transmission unit, acquisition unit, association unit) 12 Communications Department 13 Storage section 20 Patient terminals 21 Control section 22 Control section 23 Display section 30 Medical Facility Terminals 30A First medical facility terminal 30B Second medical facility terminal 31 Control Unit 32 Operation section 33 Display section 40 Social Networking Server 100 Health Management System N Communication Network

Claims

1. a first linking unit that links a PHR account of a patient on a health management service with an SNS account of the patient on an SNS service by using unique identification information of a first medical facility and unique identification information of the patient; a second linking unit that links the PHR account and the SNS account using unique identification information of a second medical facility and the unique identification information of the patient; A health management server comprising:

2. The first linking unit links the PHR account of the patient, the SNS account of the patient, and the PHR account of the first medical facility in a state in which the SNS account of the patient and the SNS account of the first medical facility are linked on the SNS service, The health management server of claim 1, wherein the second linking unit links the patient's SNS account with the PHR account of the second medical facility when the patient's SNS account and the SNS account of the second medical facility are linked on the SNS service.

3. 2. The health management server according to claim 1, further comprising a transmission unit for transmitting a questionnaire, in which responses by the past patient are reflected in items common to the results of questionnaires previously answered by the patient, to a terminal corresponding to the patient.

4. an acquisition unit for acquiring said patient's health record information; The health management server of claim 1 , further comprising: a matching unit that matches the health record information acquired by the acquisition unit with a PHR account of the patient.

5. A health management server according to claim 1; A health management system comprising a control unit that displays, on a display unit of a terminal corresponding to the patient, an instruction means for linking the patient's PHR account with the medical facility's PHR account when the patient's SNS account and the medical facility's SNS account are linked on the SNS service.

6. The health management server computer, a first linking unit that links a PHR account of a patient on a health management service with an SNS account of the patient on an SNS service by using unique identification information of a first medical facility and unique identification information of the patient; a second linking unit that links the PHR account and the SNS account using unique identification information of a second medical facility and the unique identification information of the patient; A program to function as a

Images