Information processing apparatus and program

Abstract

To provide a more appropriate display mode according to a viewer of information relating to a patient.SOLUTION: A patient information management server (information processing apparatus) accepts input of a first login ID corresponding to a patient and a second login ID corresponding to a user (family member) different from the patient. The patient information management server causes patient information or health record information of the patient to be displayed on a display unit in different display modes between a case where the input of the first login ID is accepted or a case where the input of the second login ID is accepted. For example, the patient information management server changes display items and editable items in a patient detail screen 233 in accordance with the login ID.SELECTED DRAWING: Figure 21

Description

[Technical Field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] In recent years, PHR (Personal Health Record) services have been widely used to collect and centrally manage information related to a patient's health, medical care, or nursing care. It is known that PHRs allow patients and their families to share their health records. For example, a patient's family member may use a family login ID to access the patient's test results or vital signs, or enter vital signs on behalf of the patient.

[0003] Patent Document 1 describes that a family member of a subject who is a care-requiring person or a patient operates a family terminal to input basic information, health information, and activity information of the subject, and that the input information is transmitted from the family terminal to a server. In addition, the subject's own subject terminal transmits the subject's vital data and sensing data to the server. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-169193 Summary of the Invention [Problem to be solved by the invention]

[0005] However, depending on the relationship between the patient and the family, the information that the family should input, the content that the family should refer to, and the information that the patient should input or the content that the patient should refer to will vary. For example, if a patient requires care, it is conceivable that only vital information is entered automatically or manually from the patient terminal, and other information is entered by a family member on behalf of the patient. In addition, if a husband is a diabetic and his wife wants to share his information with him, the husband may want to input and view all of his health record information, while the wife may only want to view basic progress information. Also, if the patient is a child and the guardian shares the child's information with the child, it is conceivable that the child will only be shown a simple display of the child's health status, while the guardian will be allowed to enter all information, including vital signs, and to view detailed test results or medical conditions. As such, there are various appropriate forms of information sharing when sharing PHRs between patients and their families.

[0006] The present invention has been made in consideration of the above-mentioned problems in the prior art, and an object of the present invention is to provide a more appropriate display mode depending on the person viewing the patient-related information. [Means for solving the problem]

[0007] In order to solve the above problem, the invention described in claim 1 is an information processing device comprising: a reception unit capable of receiving input of a first login ID corresponding to a patient and a second login ID corresponding to a user different from the patient; and a display control unit that displays the patient information or health record information of the patient on the display unit in different display modes when input of the first login ID is received and when input of the second login ID is received.

[0008] The invention described in claim 2 is an information processing device described in claim 1, wherein the display control unit determines the display mode of the patient information or health record information of the patient based on the patient information of the patient or the user information of the user corresponding to the second login ID.

[0009] According to a third aspect of the present invention, in the information processing device of the first aspect, the reception unit receives input of patient information or health record information of the patient by a user corresponding to the second login ID.

[0010] The invention described in claim 4 is an information processing device described in claim 1, which is provided with a setting unit that can set at least one display mode of the patient information or health record information of the patient when input of the first login ID is accepted, and the display mode of the patient information or health record information of the patient when input of the second login ID is accepted.

[0011] The invention described in claim 5 is an information processing device described in claim 1, in which the user corresponding to the second login ID is a family member of the patient, and the display control unit changes the user interface when displaying the patient information or health record information of the patient based on the current patient information of the patient or the current user information of the family member of the patient when input of the second login ID is accepted.

[0012] The invention described in claim 6 is an information processing device described in claim 1, wherein the patient's health record information includes vital information of the patient, and if the patient's vital information is not entered within a predetermined period, a notification unit is provided that notifies a user corresponding to the second login ID of information indicating that the patient's vital information has not been entered.

[0013] The invention described in claim 7 is a program for causing a computer to function as a reception unit capable of receiving input of a first login ID corresponding to a patient and a second login ID corresponding to a user different from the patient, and a display control unit that displays the patient information or health record information of the patient on the display unit in different display modes when input of the first login ID is received and when input of the second login ID is received. [Effects of the Invention]

[0014] According to the present invention, a more appropriate display mode can be provided depending on the person viewing the patient-related information. [Brief explanation of the drawings]

[0015] [Figure 1]FIG. 1 is a system configuration diagram of an information sharing system. [Figure 2] FIG. 2 is a block diagram showing the functional configuration of a patient information management server. [Figure 3] FIG. 10 is a diagram illustrating an example of the data configuration of a user table. [Figure 4] FIG. 10 is a diagram illustrating an example of the data configuration of a health record information table. [Figure 5] FIG. 10 is a diagram illustrating an example of the data configuration of a family table. [Figure 6] FIG. 10 is a diagram illustrating an example of the data configuration of a relationship table. [Figure 7] FIG. 10 is a diagram illustrating an example of the data configuration of an authority master table. [Figure 8] FIG. 10 is a diagram illustrating an example of the data configuration of a display mode master table. [Figure 9] FIG. 10 is a diagram illustrating an example of the data configuration of a display patient table. [Figure 10] FIG. 10 is a diagram illustrating an example of the data configuration of an item table. [Figure 11] FIG. 10 is a diagram illustrating an example of the data configuration of a display mode item table. [Figure 12] FIG. 10 is a diagram illustrating an example of the data configuration of an item authorization table. [Figure 13] FIG. 10 is a diagram illustrating an example of the data configuration of a notification master table. [Figure 14] FIG. 10 is a diagram illustrating an example of the data configuration of a notification management table. [Figure 15] FIG. 2 is a block diagram showing the functional configuration of a user terminal. [Figure 16] FIG. 2 is a block diagram showing the functional configuration of a clinic terminal and a pharmacy terminal. [Figure 17] 10 is a flowchart showing a patient details screen display process executed in the patient information management server. [Figure 18] 10 is an example of a login screen. [Figure 19] 10 is an example of a patient list screen. [Figure 20] 10 is a flowchart showing a display patient table update process. [Figure 21]10 is an example of a patient details screen. [Figure 22] 10 is an example of a patient details screen. [Figure 23] 10 is a flowchart showing a notification process executed in the patient information management server. [Figure 24] 10 is an example of a display mode setting screen. [Figure 25] 10 is an example of a display mode detail setting screen. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Advantages and features provided by the embodiments will be understood from the following detailed description and drawings. However, the scope of the present invention is not limited to the embodiments disclosed below or the examples shown in the drawings.

[0017] [Configuration of information sharing system] FIG. 1 shows the system configuration of an information sharing system 100. As shown in FIG. 1, information sharing system 100 includes patient information management server 10, user terminal 20, clinic terminal 30, and pharmacy terminal 40. Patient information management server 10, user terminal 20, clinic terminal 30, and pharmacy terminal 40 are connected to each other so that data can be communicated via a communication network N such as the Internet. Note that the number of user terminals 20, clinic terminals 30, and pharmacy terminals 40 is not limited.

[0018] The patient information management server 10 accumulates and manages information related to the medical or health care of patients registered from the user terminal 20, clinic terminal 30, and pharmacy terminal 40. The patient information management server 10 is an information processing device that processes information shared among the patient's user terminal 20, the patient's family member's user terminal 20, and the medical professional terminals of medical professionals (clinic terminal 30, pharmacy terminal 40). The patient information management server 10 may be a cloud server provided in a cloud environment. Alternatively, the clinic terminal 30 or the pharmacy terminal 40 may have the functions of the patient information management server 10.

[0019] The user terminal 20 is used by the patient or the patient's family. The user terminal 20 is a terminal device (patient terminal, family terminal) such as a smartphone. A PHR sharing application program (hereinafter referred to as the PHR sharing app) is installed in the user terminal 20. The patient or the patient's family uses the patient information sharing service provided by the patient information management server 10 via the PHR sharing app.

[0020] The clinic terminal 30 is used by medical staff (doctors, nurses, etc.) who belong to the clinic. The clinic terminal 30 is a computer device (a medical staff terminal) such as a PC (Personal Computer) or a tablet terminal. A clinic application program (hereinafter referred to as a clinic app) is installed on the clinic terminal 30. Medical staff who belong to the clinic use the patient information sharing service provided by the patient information management server 10 via the clinic app.

[0021] The pharmacy terminal 40 is used by medical professionals (pharmacists, etc.) who belong to the dispensing pharmacy. The pharmacy terminal 40 is a computer device (a medical professional terminal) such as a PC or tablet terminal. A pharmacy application program (hereinafter referred to as a pharmacy app) is installed on the pharmacy terminal 40. The medical professionals who belong to the dispensing pharmacy use the patient information sharing service provided by the patient information management server 10 via the pharmacy app.

[0022] The user terminal 20, clinic terminal 30, and pharmacy terminal 40 are used when registering medical or health information in the patient information management server 10, when referencing medical or health information managed by the patient information management server 10, etc.

[0023] For example, a patient or a patient's family member uses a user terminal 20 to register data such as the patient's vital signs, medication information, symptom information, dietary information, and exercise information in the patient information management server 10 via a PHR sharing app. A doctor registers data such as test information, medical checkup information, and prescription information of a patient in the patient information management server 10 via a clinic app on the clinic terminal 30. The pharmacist registers data such as prescription information of the patient in the patient information management server 10 at the pharmacy terminal 40 via the pharmacy app.

[0024] The patient information management server 10 allows the user terminal 20 to input or view patient information via the PHR sharing app. The patient information management server 10 allows the clinic terminal 30 to input or view information about patients receiving medical care or treatment at the clinic via the clinic app. The patient information management server 10 allows the pharmacy terminal 40 to input or view information about patients who use the dispensing pharmacy via the pharmacy app.

[0025] [Configuration of patient information management server] FIG. 2 shows the functional configuration of the patient information management server 10. 2, the patient information management server 10 includes a control unit 11, a communication unit 12, a RAM (Random Access Memory) 13, a clock unit 14, and a storage unit 15. The units constituting the patient information management server 10 are connected via a bus.

[0026] The control unit 11 includes a CPU (Central Processing Unit) and the like. The control unit 11 comprehensively controls the processing operations of each unit of the patient information management server 10. Specifically, the CPU reads out various processing programs stored in the storage unit 15, loads the read programs into the RAM 13, and performs various processes in cooperation with the programs.

[0027] The communication unit 12 is configured by a network interface, etc. The communication unit 12 transmits and receives data to and from external devices connected via a communication network N.

[0028] The RAM 13 forms a work area for temporarily storing various programs, input data, output data, parameters, etc. read from the storage unit 15 during various processes executed by the control unit 11.

[0029] The timekeeping unit 14 has a timekeeping circuit (RTC: Real Time Clock). The timekeeping unit 14 keeps track of the current date and time using this timekeeping circuit and outputs the time to the control unit 11.

[0030] The storage unit 15 is configured with a hard disk drive (HDD), a solid state drive (SSD), a non-volatile semiconductor memory, etc. The storage unit 15 stores various processing programs, parameters required for executing the programs, files, etc. For example, the storage unit 15 stores a web server program for realizing the function of a web server. The web server communicates with a web browser installed in an external device using the HTTP protocol and provides various web screens to the web browser. The storage unit 15 also stores an application program that runs on the web server and provides a patient information sharing service to operators of external devices via the web browser.

[0031] The memory unit 15 stores a user table T1, a health record information table T2, a family table T3, a relationship table T4, an authority master table T5, a display mode master table T6, a display patient table T7, an item table T8, a display mode item table T9, an item authority table T10, a notification master table T11, and a notification management table T12.

[0032] User table T1 stores user information for users who use the patient information sharing service. Figure 3 shows an example of the data configuration of user table T1. User table T1 associates each user with the user ID, user name, gender, date of birth, password, whether input assistance is required, display mode settings, etc. The user ID is the user's identification information. The user ID is used as the user's login ID. The user name is the user's name. Gender is the gender of the user. Date of Birth is the user's date of birth. The password is the password the user uses to access the patient information sharing service. The input assistance requirement is information that indicates whether the user needs assistance in inputting information. If the user is unable to input information by themselves (such as a person requiring care, a person with dementia, or an infant), the input assistance requirement is "required." If the user is able to input information by themselves, the input assistance requirement is "not required." The display mode setting is information that indicates whether the display mode ID and authority ID settings of the display patient table T7 (see Figure 9) are "manual" or "automatic." If the display mode setting is "manual," the target user is only permitted to manually update the display patient table T7. If the display mode setting is "automatic," the display patient table T7 is permitted to be automatically updated during processing by the target user.

[0033] The patient's user information corresponds to the patient information. The patient information includes age, sex, address, telephone number, email address, and the name of the medical facility currently being used (clinic name, dispensing pharmacy name, etc.). The patient information may also include the relationship to the patient or family. Since the relationship is determined by the relationship between two people, in this embodiment, the relationship is managed in the displayed patient table T7.

[0034] Health record information table T2 stores health record information for each patient. Health record information includes vital signs, test results, medication information (medication information, prescription information, dispensing information), etc. Figure 4 shows an example of the data structure of health record information table T2. Health record information table T2 associates patient ID, date, blood pressure (systolic), blood pressure (diastolic), pulse, weight, medication, mood, memos, etc. The patient ID is the patient's identification information. The patient's user ID is used as the patient ID. The date is the target date of the corresponding record. The blood pressure (systolic), blood pressure (diastolic), pulse, and weight are the values of the blood pressure (systolic), blood pressure (diastolic), pulse, and weight obtained by measuring the patient, respectively. The blood pressure (systolic), blood pressure (diastolic), and pulse are examples of vital information. The vital information may include body temperature, percutaneous arterial oxygen saturation, etc. The vital information may be input from the operation unit 22 (see FIG. 15) of the user terminal 20, or may be acquired from a vital measurement device via the Bluetooth (registered trademark) communication unit 29 (see FIG. 15). Medication is information indicating whether or not a patient has taken a medication. If multiple doses of medication are scheduled in one day, the medication is managed by distinguishing between medication 1, medication 2, etc. Furthermore, information regarding medication may include information such as the medication taken (ingested) by the patient, the amount, and the date and time of administration. Mood is information indicating the mood of the patient. Notes are information recorded by the person entering the health record information. The date, blood pressure (systolic), blood pressure (diastolic), pulse, weight, medication, mood, and notes are input by the patient or a family member of the patient through the user terminal 20.

[0035] The health record information table T2 may include symptom information, diet information, exercise information, examination information, medical checkup information, prescription information, dispensing information, and the like, in association with patient information (such as patient ID). Symptom information includes the location of pain, numbness, etc. (head, internal organs, upper and lower limbs, eyes, etc.), fatigue, loss of appetite, dizziness, insomnia, diarrhea, constipation, and time of onset. The dietary information includes images of the meals taken by the patient, the dietary contents, nutrients, calorie intake, etc. The exercise information includes the number of steps, distance traveled, and information about the exercise the patient has performed (type, number of times, duration, etc.). Symptom information, dietary information, and exercise information are input from the user terminal 20 by the patient or a family member of the patient.

[0036] The examination information is information about the examinations that the patient has undergone (examination items, examination results, etc.). The medical checkup information is information about the medical checkup that the patient has undergone (diagnosis items, diagnosis results, etc.). The prescription information is information about the prescription prescribed to the patient (drug, timing, amount, etc.). The dispensing information is information (drug, timing, amount, etc.) about the medicine dispensed at the dispensing pharmacy according to the doctor's prescription. Basically, the test information, medical checkup information, prescription information, and dispensing information are input by medical personnel belonging to medical facilities such as clinics and dispensing pharmacies via the clinic terminal 30, pharmacy terminal 40, etc. However, there are also cases where the patient or a patient's family member inputs the test information, medical checkup information, prescription information, and dispensing information via the user terminal 20.

[0037] The family table T3 defines the users who make up each family. An example of the data structure of the family table T3 is shown in Fig. 5. In the family table T3, family IDs and user IDs are associated with each other. The family ID is identification information for a family member. A user ID is a user ID of a user who makes up a family corresponding to a family ID. A group of user IDs associated with the same family ID corresponds to one family.

[0038] An example of the data configuration of the relationship table T4 is shown in Fig. 6. In the relationship table T4, relationship IDs are associated with relationships. The relationship ID is identification information of the relationship. The relationship is information indicating the relationship to the subject (patient).

[0039] An example of the data configuration of the authority master table T5 is shown in Fig. 7. In the authority master table T5, authority IDs are associated with authorities. The authority ID is identification information of the authority. The "administrator" authority is an authority that allows editing of all items. "Easy input" authority is an authority that allows editing of some items. The "reference" authority allows only viewing of all items and does not allow editing.

[0040] An example of the data configuration of the display mode master table T6 is shown in Fig. 8. In the display mode master table T6, a display mode ID, a mode name, a form, an age, etc. are associated with each display mode. The display mode ID is identification information of the display mode. The mode name is the name of the display mode. A form is information that defines the design of the screen to be displayed, and the position and size of the items to be displayed. The age is the target age of the display mode. The display modes identified by the display mode IDs "1," "2," and "3" have in common that they are intended for people 18 years of age and older, but the forms (display items) are different.

[0041] The display mode of patient information or health record information is set in the display patient table T7. An example of the data configuration of the display patient table T7 is shown in Figure 9. In the display patient table T7, an authority ID, a display mode ID, and a relationship ID are associated with each combination of a referenced person ID and a referencer ID. The referee ID is the user ID of the patient (referee) whose patient information or health record information is being referenced. The referrer ID is the user ID of the user (referrer) who refers to the patient information or health record information. In the display patient table T7, the authority ID is information indicating the authority that the user corresponding to the referrer ID has for the patient information or health record information of the patient corresponding to the referred person ID. In the display patient table T7, the display mode ID is information indicating the display mode when a user corresponding to the referrer ID refers to the patient information or health record information of a patient corresponding to the referred person ID. The relationship ID is information that indicates the relationship between the patient (referenced person) whose patient information or health record information is referenced and the user (referring person) who refers to the patient information or health record information. In the displayed patient table T7, the relationship ID indicates the relationship (position) of the referencing person from the referenced person's perspective.

[0042] In the display patient table T7, the same referrer ID can be registered with multiple referenced party IDs. In other words, the display mode can be set in the display patient table T7 when a user refers to information on multiple patients in their family. Furthermore, the display patient table T7 can register a combination of the same referenced person ID and multiple referrer IDs. In other words, the display patient table T7 can be set to display information about a patient in a different manner when multiple users (the patient's family members) refer to the information.

[0043] An example of the data configuration of the item table T8 is shown in Fig. 10. In the item table T8, an item ID and an item name are associated with each item. The item ID is identification information for an item related to patient information or health record information. The item name is the name of an item related to patient information or health record information.

[0044] An example of the data configuration of the display mode item table T9 is shown in Fig. 11. In the display mode item table T9, display mode IDs, item IDs, and display formats are associated with each other. The display format is information indicating the display format of the target item, such as text or marks. The display mode item table T9 defines the item IDs and display formats of the items to be displayed in the display mode corresponding to the display mode ID.

[0045] 12 shows an example of the data configuration of the item authority table T10. In the item authority table T10, authority IDs are associated with editable item IDs. The editable item ID is the item ID of the editable item. The item authority table T10 defines the item IDs of editable items for the authority corresponding to the authority ID.

[0046] An example of the data configuration of the notification master table T11 is shown in Fig. 13. In the notification master table T11, notification item IDs are associated with notification items. The notification item ID is identification information of the notification item. The notification items are items that may be subject to a warning notification if not entered.

[0047] 14 shows an example of the data configuration of the notification management table T12. In the notification management table T12, patient IDs, notification item IDs, number of times, time, and notification destination IDs are associated with each other. The patient ID is the user ID of the patient who is the target of notification management. The notification item ID is a notification item ID corresponding to a notification item that is the target of notification management. The number of times is the number of times that the notification item corresponding to the notification item ID should be input in one day. The time is the scheduled input time of the notification item corresponding to the notification item ID. For items that are scheduled to be input multiple times in one day, the scheduled input times are managed separately as Time 1, Time 2, etc. The notification destination ID is the user ID of the user to be notified when the notification items to be managed for the target patient are not entered. The notification destination user can be the patient, parent, child, etc.

[0048] The control unit 11 (reception unit) accepts input of a first login ID corresponding to a patient and a second login ID corresponding to a user other than the patient. The user other than the patient is assumed to be a family member of the patient. The first login ID is a user ID (patient ID) used by the patient himself / herself. The second login ID is a user ID used by a family member of the patient.

[0049] The control unit 11 (display control unit) displays the patient's patient information or health record information on the display unit 23 (see Figure 15) of the user terminal 20 in different display modes depending on whether input of the first login ID is accepted or the second login ID is accepted.

[0050] The control unit 11 determines the display mode of the patient information or health record information of the patient based on the patient information of the patient or the user information of the user corresponding to the second login ID. Specifically, the control unit 11 displays the patient information or health record information of the patient displayed using the first login ID differently from the patient information or health record information of the patient displayed using the second login ID based on the patient information of the patient himself / herself or the user information of the family member. The patient information of the patient himself / herself includes the patient's age, gender, address, relationship to the family member, etc. The user information of the family member includes the age, gender, address, relationship to the patient, etc. of the patient's family member.

[0051] The control unit 11 changes the user interface when displaying the patient information or health record information of the patient based on the patient information of the current patient or the user information of the current patient's family member when input of a second login ID corresponding to the patient's family member is accepted. For example, when the patient is an infant, the control unit 11 provides an input field on the display screen of the patient's patient information or health record information displayed using the second login ID, allowing family members to input vital values on behalf of the patient. In contrast, when the patient becomes an adult, the control unit 11 removes the input field for vital values from the display screen of the patient's patient information or health record information displayed using the second login ID, allowing only reference to vital values. In this way, the control unit 11 changes how information about the patient is viewed by family members between the past and present, depending on the patient's age, etc.

[0052] The control unit 11 (reception unit) receives input of the patient information or health record information of the patient by the user corresponding to the second login ID.

[0053] The control unit 11 (setting unit) sets at least one display mode of the patient information or health record information of the patient when input of the first login ID is accepted, and the display mode of the patient information or health record information of the patient when input of the second login ID is accepted.

[0054] If the patient's vital information is not input within a predetermined period, the control unit 11 (notification unit) notifies the user corresponding to the second login ID of information indicating that the patient's vital information has not been input. As the predetermined period, for example, the period from the last check to the scheduled time of inputting the vital information, the period from the last check to the present, etc. are used. Note that, as shown in the notification master table T11 of FIG. 13, the notification item is not limited to vital information.

[0055] [User terminal configuration] FIG. 15 shows the functional configuration of the user terminal 20. 15, user terminal 20 includes a control unit 21, an operation unit 22, a display unit 23, a communication unit 24, RAM 25, a storage unit 26, a camera 27, an acceleration sensor 28, a Bluetooth communication unit 29, etc. The components constituting user terminal 20 are connected via a bus.

[0056] The control unit 21 includes a CPU and the like. The control unit 21 comprehensively controls the processing operations of each unit of the user terminal 20. Specifically, the CPU reads out various processing programs stored in the storage unit 26 in response to an operation signal input from the operation unit 22 or an instruction signal received by the communication unit 24. The CPU loads the read program into the RAM 25 and performs various processes in cooperation with the program.

[0057] The operation unit 22 includes operation keys and a touch screen that is integrally configured with 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 on the touch screen by the operator's finger or the like.

[0058] The display unit 23 includes an LCD (Liquid Crystal Display) etc. The display unit 23 displays various screens in accordance with instructions of a display signal input from the control unit 21. For example, the display unit 23 displays various web screens based on display data for the various web screens received from the patient information management server 10.

[0059] The communication unit 24 is configured by a network interface, etc. The communication unit 24 transmits and receives data to and from external devices connected via the communication network N. The communication unit 24 also performs wireless communication using a mobile phone line, etc., and transmits and receives data to and from external devices connected via the communication network N.

[0060] The RAM 25 forms a work area for temporarily storing various programs, input data, output data, parameters, etc. read from the storage unit 26 during various processes executed by the control unit 21.

[0061] The storage unit 26 is configured with an HDD, SSD, non-volatile semiconductor memory, etc. The storage unit 26 stores various processing programs, parameters required for executing the programs, files, etc. For example, the storage unit 26 stores a web browser program for implementing a web browser, a PHR sharing app, etc.

[0062] The camera 27 is a digital camera equipped with an optical lens, an image sensor, various sensors, etc. The camera 27 takes an image of a subject and generates image data.

[0063] The acceleration sensor detects the acceleration of the user terminal 20. Based on the change in acceleration obtained by the acceleration sensor , the control unit 21 calculates the number of steps and the distance traveled by the user who carries the user terminal 20.

[0064] The Bluetooth communication unit 29 performs data communication with an external device using the Bluetooth communication method via an antenna for transmitting and receiving Bluetooth communication. For example, the Bluetooth communication unit 29 acquires vital information from a vital sign measuring device.

[0065] [Configuration of clinic terminals] FIG. 16 shows the functional configuration of the clinic terminal 30. 16, the clinic terminal 30 includes a control unit 31, an operation unit 32, a display unit 33, a communication unit 34, a RAM 35, a storage unit 36, etc. The units constituting the clinic terminal 30 are connected by a bus.

[0066] The control unit 31, display unit 33, communication unit 34, RAM 35, and storage unit 36 of the clinic terminal 30 are similar to the control unit 21, display unit 23, communication unit 24, RAM 25, and storage unit 26 of the user terminal 20, respectively, and therefore will not be described here. Note that the storage unit 36 stores a clinic app instead of the PHR sharing app.

[0067] The operation unit 32 includes a keyboard, a mouse, etc. The keyboard includes cursor keys, character input keys, various function keys, etc. The operation unit 32 outputs operation signals input by key operations on the keyboard and mouse operations to the control unit 31. When the clinic terminal 30 is a tablet terminal or the like, the operation unit 32 includes operation keys and a touch screen that is integrally configured with 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.

[0068] [Pharmacy terminal configuration] FIG. 16 shows the functional configuration of pharmacy terminal 40. 16, pharmacy terminal 40 includes control unit 41, operation unit 42, display unit 43, communication unit 44, RAM 45, storage unit 46, etc. The components constituting pharmacy terminal 40 are connected by a bus.

[0069] The control unit 41, operation unit 42, display unit 43, communication unit 44, RAM 45, and memory unit 46 of the pharmacy terminal 40 are similar to the control unit 31, operation unit 32, display unit 33, communication unit 34, RAM 35, and memory unit 36 of the clinic terminal 30, respectively, and therefore will not be described here. Note that a pharmacy app is stored in memory unit 46 instead of a clinic app.

[0070] [Operations in information sharing systems] Next, the operation of information sharing system 100 will be described. In this embodiment, the screen displayed on the PHR sharing app on the display unit 23 of the user terminal 20 is generated by the control unit 11 of the patient information management server 10.

[0071] FIG. 17 is a flowchart showing the patient details screen display process executed in the patient information management server 10. First, a patient or a user who is a family member of the patient starts the PHR sharing app on the user terminal 20 by operating the operation unit 22. Then, the control unit 11 of the patient information management server 10 displays a login screen on the display unit 23 of the user terminal 20 (step S1).

[0072] 18 shows an example of a login screen 231 displayed on the display unit 23 of the user terminal 20. The login screen 231 includes a user ID area 51, a password area 52, a login button 53, and the like. A user ID is entered in the user ID area 51 . A password is entered in the password area 52 . The login button 53 is a button for instructing login.

[0073] On the user terminal 20, the user operates the operation unit 22 to input a user ID in the user ID area 51, input a password in the password area 52, and press the login button 53. The control unit 21 of the user terminal 20 transmits the input user ID and password to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 accepts the user ID and password entered at the user terminal 20 via the communication unit 12 (step S2).

[0074] Next, the control unit 11 refers to the user table T1 in the storage unit 15 and determines whether or not there is a record that matches the combination of the user ID and password entered at the user terminal 20 (step S3). If there is no record in the user table T1 that matches the combination of the entered user ID and password (step S3; NO), the process proceeds to step S4. In step S4, the control unit 11 causes an error message to be displayed on the display unit 23 of the user terminal 20. After step S4, the process returns to step S1.

[0075] In step S3, if the user table T1 contains a record that matches the combination of the entered user ID and password (step S3; YES), the control unit 11 extracts candidate patients to be displayed (step S5). Specifically, the control unit 11 extracts records from the display patient table T7 of the storage unit 15, whose "referencer ID" matches the "user ID" of the currently logged-in user (logged-in user). The control unit 11 designates the user corresponding to the "referenced person ID" included in the extracted record as a candidate patient to be displayed.

[0076] Here, the control unit 11 determines whether there are multiple display target patient candidates (step S6). If there are multiple display target patient candidates (step S6; YES), the control unit 11 displays a patient list screen on the display unit 23 of the user terminal 20 (step S7). Specifically, the control unit 11 acquires the "user name" corresponding to the "user ID" of each display target patient candidate from the user table T1, and lists the "user ID" and "user name" of each display target patient candidate.

[0077] 19 shows an example of a patient list screen 232 displayed on the display unit 23 of the user terminal 20. The patient list screen 232 includes a patient list area 61, an OK button 62, a cancel button 63, and the like. A list of display target patient candidates is displayed in the patient list area 61. The list displays the "user ID" and "user name" of the display target patient candidates. The OK button 62 is a button for confirming the patient selected on the list in the patient list area 61 . The cancel button 63 is a button for canceling the selection of a patient on the list in the patient list area 61 .

[0078] The user selects a patient by operating the operation unit 22 of the user terminal 20. The control unit 21 of the user terminal 20 transmits information indicating the selected patient to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 designates the patient selected on the user terminal 20 as the patient to be displayed (step S8).

[0079] In step S6, if there is only one display target patient candidate (step S6; NO), the control unit 11 of the patient information management server 10 sets the display target patient candidate as the display target patient.

[0080] After step S8, or in step S6, if there is only one candidate patient to be displayed (step S6; NO), the control unit 11 of the patient information management server 10 performs a display patient table update process (step S9).

[0081] Here, the display patient table update process will be described with reference to FIG. The control unit 11 of the patient information management server 10 acquires the display mode setting of the logged-in user (step S21). Specifically, the control unit 11 references the user table T1 in the storage unit 15 and acquires the "display mode setting" corresponding to the "user ID" of the logged-in user. Note that the control unit 11 may acquire the user information of the logged-in user from the user table T1 into RAM 13 at the time of login, and then acquire the "display mode setting" from RAM 13. Similarly, in the following processing, the control unit 11 does not need to access each table each time.

[0082] Next, the control unit 11 determines whether the display mode setting of the logged-in user is automatic or not (step S22). If the display mode setting of the logged-in user is automatic (step S22; YES), the control unit 11 calculates the age of the logged-in user from the date of birth (step S23). Specifically, the control unit 11 refers to the user table T1 and acquires the "date of birth" corresponding to the "user ID" of the logged-in user. The control unit 11 acquires the current date and time from the clock unit 14, and calculates the age of the logged-in user based on the current date and time and the date of birth.

[0083] Next, the control unit 11 acquires the "display mode ID" corresponding to the "age" of the logged-in user from the display mode master table T6 of the storage unit 15 (step S24). For example, if the logged-in user is 4 years old, the display mode ID is "4" (mode infant). If the logged-in user is 14 years old, the display mode ID is "8" (mode junior high school student). If the logged-in user is 18 years old or older, mode C will be the default (display mode ID is "3"). Furthermore, form J for medical institutions (display mode ID is "10") is not subject to automatic updates in the display patient table update process.

[0084] Next, the control unit 11 acquires a display mode ID corresponding to the combination of the user ID (referenced person ID) of the display target patient and the user ID (referencer ID) of the login user from the display patient table T7 of the storage unit 15 (step S25).

[0085] Next, the control unit 11 determines whether or not the display mode ID acquired in step S24 matches the display mode ID acquired in step S25 (step S26). If the display mode ID acquired in step S24 does not match the display mode ID acquired in step S25 (step S26; NO), the process proceeds to step S27. In step S27, the control unit 11 updates the display mode ID in the display patient table T7, which corresponds to the combination of the user ID of the patient to be displayed and the user ID of the logged-in user, to the display mode ID acquired in step S24.

[0086] After step S27, or in step S26, if the display mode ID acquired in step S24 matches the display mode ID acquired in step S25 (step S26; YES), the process proceeds to step S28. In step S28, the control unit 11 updates the authority ID corresponding to the combination of the user ID of the patient to be displayed and the user ID of the logged-in user in the display patient table T7, based on the relationship between the patient to be displayed and the logged-in user, and whether input assistance is required for the patient to be displayed. Specifically, the control unit 11 acquires the relationship ID corresponding to the combination of the user ID of the patient to be displayed and the user ID of the logged-in user from the display patient table T7. The control unit 11 references the user table T1 to acquire the "input assistance required" corresponding to the "user ID" of the patient to be displayed.

[0087] For example, if the patient to be displayed is a small child and the logged-in user is a parent, the control unit 11 updates the authority ID to "1" based on the relationship of "parent" and the information on whether input assistance is required, "required." When the relationship is "parents" and the input assistance requirement is "not required," and the age of the patient to be displayed is equal to or greater than a predetermined value, the control unit 11 updates the authority ID to "3." When the patient to be displayed is a person requiring care and the logged-in user is a child, the control unit 11 updates the authority ID to "1" based on the relationship of "child" and the information on whether input assistance is required.

[0088] After step S28, or in step S22, if the display mode setting of the logged-in user is not automatic (step S22; NO), the display patient table update process ends.

[0089] In step S28 of the display patient table update process, the control unit 11 may make a determination without using the relationship between the display target patient and the login user. That is, the control unit 11 may update the authority ID corresponding to the combination of the user ID of the display target patient and the user ID of the login user in the display patient table T7 based on whether input assistance is required for the display target patient. Furthermore, in the display patient table update process, the control unit 11 does not need to perform the process of step S28. In addition, the control unit 11 may update the display mode ID corresponding to the combination of the user ID of the patient to be displayed and the user ID of the logged-in user in the display patient table T7 based on the relationship between the patient to be displayed and the logged-in user and whether or not input assistance is required for the patient to be displayed.

[0090] After step S9, the control unit 11 of the patient information management server 10 acquires the display mode ID and authority ID corresponding to the combination of the user ID of the patient to be displayed and the user ID of the logged-in user from the display patient table T7 (step S10).

[0091] Next, the control unit 11 determines the form, display items, and display format of the display screen based on the display mode ID acquired in step S10 (step S11). Specifically, the control unit 11 refers to the display mode master table T6 of the storage unit 15 to acquire a "form" corresponding to the "display mode ID." The control unit 11 refers to the display mode item table T9 of the storage unit 15 to acquire a pair of an "item ID" and a "display format" corresponding to the display mode ID. The item corresponding to the acquired "item ID" becomes the item (display item) to be displayed on the screen. The control unit 11 refers to the item table T8 of the storage unit 15 to identify the "item name" corresponding to the acquired "item ID."

[0092] Next, the control unit 11 determines editable items based on the authority ID acquired in step S10 (step S12). Specifically, the control unit 11 refers to the item authority table T10 in the storage unit 15 to acquire an "editable item ID" corresponding to the "authority ID." The control unit 11 refers to the item table T8 in the storage unit 15 to identify an "item name" corresponding to the acquired "editable item ID (item ID)." Note that the control unit 11 determines, as editable items, only those items included in the display items among the identified "item names."

[0093] Next, the control unit 11 causes the display unit 23 of the user terminal 20 to display a patient details screen (step S13). Specifically, the control unit 11 generates display data for the patient details screen in accordance with the form, display items, and display format determined in step S11 and the editable items determined in step S12. The patient details screen displays patient information and health record information of the patient to be displayed.

[0094] FIG. 21 shows an example of a patient details screen 233 displayed on the display unit 23 of the user terminal 20. The patient details screen 233 is an example when the display mode ID is "1" and the authority ID is "1." According to the display mode item table T9 and the item table T8, when the display mode ID is "1," the display items are name, date, blood pressure, pulse, medication, weight, mood, and notes, and the display format of each display item is all text. Furthermore, according to the item authority table T10, when the authority ID is "1," each display item except "name" can be edited.

[0095] The patient details screen 233 includes a name area 70, a date area 71, a morning blood pressure area 72, a morning pulse area 73, an evening blood pressure area 74, an evening pulse area 75, a morning medication area 76, a midday medication area 77, an evening medication area 78, a weight area 79, a morning mood area 80, a midday mood area 81, an evening mood area 82, and a memo area 83. The patient's name is displayed in "Kanji" in the name area 70. Editing of the name in the name area 70 is not permitted. The date is displayed in the date area 71. When date change buttons 71A and 71B provided in the date area 71 are pressed, the date displayed in the date area 71 changes. In addition, the date can be corrected in the date area 71. The blood pressure (systolic / diastolic) measured in the morning is displayed in the morning blood pressure area 72. In addition, in the morning blood pressure area 72, data can be edited (input, change, delete, etc.). The pulse measured in the morning is displayed in the morning pulse area 73. In addition, in the morning pulse area 73, data can be edited. The nighttime blood pressure area 74 is where the blood pressure (systolic / diastolic) measured at night is entered. In the night pulse area 75, the pulse measured at night is entered. The fact that the morning medication has been taken is displayed in the morning medication area 76. In addition, the morning medication area 76 allows data editing. In the daytime medication area 77 and the evening medication area 78, it is selected that daytime and evening medications have been taken, respectively. The patient's weight is displayed in the weight area 79. In addition, the weight area 79 allows data editing. The morning mood is displayed in the morning mood area 80. In addition, data in the morning mood area 80 can be edited. In the daytime mood area 81 and the evening mood area 82, daytime and evening moods are selected, respectively. Memos are entered in the memo area 83 .

[0096] FIG. 22 shows an example of a patient details screen 234 displayed on the display unit 23 of the user terminal 20. The patient details screen 234 is an example when the display mode ID is "4" and the authority ID is "2." According to the display mode item table T9 and the item table T8, the display items when the display mode ID is "4" are name (kana), date, medication, and mood, and the display format for the display items "name (kana)" and "date" is text, and the display format for the display items "medication" and "mood" is mark. Furthermore, according to the item authority table T10, when the authority ID is "2," the display items "medication" and "mood" are editable.

[0097] The patient details screen 234 includes a name area 90 , a date area 91 , a morning medication area 92 , a midday medication area 93 , an evening medication area 94 , a morning mood area 95 , a midday mood area 96 , and an evening mood area 97 . The patient's name is displayed in "kana notation" in the name area 90. Editing of the name in the name area 90 is not permitted. The date is displayed in the date area 91. When date change buttons 91A and 91B provided in the date area 91 are pressed, the date displayed in the date area 91 changes. The fact that the morning medication has been taken is displayed in the morning medication area 92. In addition, in the morning medication area 92, data can be edited (input, change, delete, etc.). Taking daytime and evening medicines can be selected in the daytime medicine area 93 and evening medicine area 94. Here, taking medicines can be input by selecting a mark. The morning mood is displayed in the morning mood area 95. In addition, data in the morning mood area 95 can be edited. The daytime mood and evening mood are selected in the daytime mood area 96 and evening mood area 97. Here, the mood is input by selecting a mark. This completes the patient details screen display process.

[0098] When the referrer is the patient himself / herself, the control unit 11 of the patient information management server 10 causes the display unit 23 of the user terminal 20 to display the patient information or health record information of the patient himself / herself. However, the display items are limited to those according to the "display mode ID" included in the record in the display patient table T7 where the "referenced person ID" and "referring person ID" are the user ID corresponding to the patient himself / herself. For example, when the patient himself / herself is an infant, the control unit 11 causes the display unit 23 of the user terminal 20 to display the patient details screen 234 shown in FIG. 22. When the patient himself / herself is 18 years of age or older, the control unit 11 causes the display unit 23 of the user terminal 20 to display the patient details screen 233 shown in FIG. 21. In this way, the control unit 11 changes the way the patient-related information is viewed by the patient himself / herself depending on the patient's age, etc.

[0099] If the referrer is a family member of the patient, the control unit 11 of the patient information management server 10 causes the display unit 23 of the user terminal 20 to display the patient information or health record information of the patient. However, this is limited to display items according to the "display mode ID" included in a record in the displayed patient table T7 where the "referenced person ID" is the user ID corresponding to the patient and the "referring person ID" is the user ID corresponding to a family member. For example, even if the patient is an infant, if the referrer is a family member aged 18 or older, the control unit 11 causes the display unit 23 of the user terminal 20 to display the patient details screen 233 shown in FIG. 21.

[0100] When the user using the user terminal 20 is the patient himself / herself, the control unit 11 of the patient information management server 10 accepts input of the patient information or health record information of the patient by the patient himself / herself (the user corresponding to the first login ID), however, this is limited to editable items according to the "authorization ID" and "display mode ID" included in the record in the displayed patient table T7 where the "referenced person ID" and "referring person ID" are the user ID corresponding to the patient himself / herself.

[0101] The patient inputs the patient's own patient information, vital signs information, examination information, medication information, symptom information, dietary information, exercise information, etc. into the PHR sharing app on the user terminal 20. When a patient inputs various information from the operation unit 22 of the user terminal 20, the control unit 21 transmits the various information to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 associates the various information acquired from the user terminal 20 with the patient (user ID, patient ID, etc.) and registers it in the user table T1 or the health record information table T2 in the memory unit 15. Alternatively, the control unit 21 of the user terminal 20 may acquire the patient's vital information from the vital sign measuring device via the Bluetooth communication unit 29, and transmit the vital information to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 registers the vital information acquired from the user terminal 20 in the health record information table T2 of the memory unit 15.

[0102] Furthermore, before a meal, the patient takes a photo of the meal they plan to eat with the camera 27 of the user terminal 20, and the control unit 21 of the user terminal 20 sends the meal image data obtained by the photo shoot to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 performs image analysis of the meal image data to determine the ingredients and amounts, automatically calculate nutrients, calorie intake, etc., and registers this meal information in the health record information table T2 in the memory unit 15.

[0103] Furthermore, the control unit 21 of the user terminal 20 calculates the number of steps or the distance traveled based on the change in acceleration detected by the acceleration sensor 28. The control unit 21 transmits the number of steps or the distance traveled as part of the exercise information to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 registers the exercise information acquired from the user terminal 20 in the health record information table T2 of the memory unit 15. It should be noted that user terminal 20 may be a PC. When user terminal 20 is a PC, control unit 21 of user terminal 20 acquires the number of steps or the distance traveled input from operation unit 22. The subsequent processing is the same as when control unit 21 calculates the number of steps or the distance traveled.

[0104] If the user using the user terminal 20 is a family member of the patient, the control unit 11 of the patient information management server 10 accepts input of the patient information or health record information of the patient by the family member (the user corresponding to the second login ID), but only for editable items according to the "authorization ID" and "display mode ID" included in a record in the displayed patient table T7 where the "referenced person ID" is the user ID corresponding to the patient and the "referee ID" is the user ID corresponding to the family member.

[0105] The patient's family members input the patient's patient information, vital signs information, examination information, medication information, symptom information, dietary information, exercise information, etc. into the PHR sharing app on the user terminal 20. The method for inputting various types of information is the same as when the patient inputs it themselves. The control unit 11 of the patient information management server 10 associates various information acquired from the user terminal 20 with the patient (user ID, patient ID, etc.) and registers it in the user table T1 or health record information table T2 of the storage unit 15.

[0106] 23 is a flowchart showing the notification process executed in the patient information management server 10. The notification process is executed at predetermined time intervals. The control unit 11 of the patient information management server 10 extracts notification information from the notification management table T12 in the storage unit 15 (step S31). The notification information is information stored in the notification management table T12. The notification information includes a patient ID, a notification item ID, a number of times, a time (scheduled input time), and a notification destination ID.

[0107] Next, the control unit 11 determines whether or not there is a notification target in the notification management table T12 (step S32). Specifically, the control unit 11 determines that there is a notification target when there is a record in the notification management table T12. If there is a notification target in the notification management table T12 (step S32; YES), the control unit 11 acquires the scheduled input time of the notification item from the notification management table T12 (step S33). The control unit 11 acquires the time (scheduled input time) included in the unprocessed record in the current notification process among the notification targets.

[0108] Next, the control unit 11 acquires the current date and time from the clock unit 14, and compares the current date and time with the scheduled input time to determine whether the scheduled input time has passed (step S34). If the scheduled input time has passed (step S34; YES), the control unit 11 determines whether data for the notification item has already been input (step S35). Specifically, the control unit 11 identifies the target patient from the "patient ID" included in the notification target record in the notification management table T12, and identifies the notification item from the "notification item ID" included in the notification target record. The control unit 11 also determines when (morning, afternoon, evening, etc.) data should be checked for input based on the "number of times" and "time" included in the notification target record. The control unit 11 refers to the health record information table T2 to determine whether data for the target time today has been input for the notification item of the target patient. For notification items that are input multiple times a day, the control unit 11 distinguishes between the target time periods to determine whether data has been input.

[0109] If the data for the notification items has not been entered (step S35; NO), the control unit 11 identifies the notification destination user from the "notification destination ID" included in the notification target record and sends a notification to the notification destination user (step S36). For example, the control unit 11 sends a push notification on the PHR sharing app to the user terminal 20 of the notification destination user to notify that the notification items for the target patient have not been entered. The control unit 11 may also notify the notification destination user that the notification items for the target patient have not been entered by sending an email or a LINE (registered trademark) notification.

[0110] In step S35, if the data for the notification item has been input (step S35; YES), the process proceeds to step S37. In step S34, if the scheduled input time has not passed (step S34; NO), or after step S36, the process proceeds to step S37. In step S37, the control unit 11 determines whether or not all notification targets set in the notification management table T12 have been confirmed.

[0111] If there is an unconfirmed notification target in the notification management table T12 (step S37; NO), the process returns to step S33. Then, the control unit 11 repeats the process with the unconfirmed notification item as the processing target.

[0112] In step S37, if all notification targets set in the notification management table T12 have been confirmed (step S37; YES), the notification process ends. In step S32, if there is no notification target in the notification management table T12 (step S32; NO), the notification process ends.

[0113] Next, a method for setting each record in the display patient table T7 will be described. The control unit 11 of the patient information management server 10 causes the display unit 23 of the user terminal 20 to display a display mode setting screen.

[0114] 24 shows an example of a display mode setting screen 235 displayed on the display unit 23 of the user terminal 20. The display mode setting screen 235 includes a patient ID area 101, a referrer ID area 102, an authority area 103, a display mode area 104, an OK button 105, a cancel button 106, etc. The patient ID area 101 is an area for inputting (selecting) the user ID of the patient (referenced person). The referrer ID area 102 is an area for inputting (selecting) the user ID of the referrer. The authority area 103 is an area for the viewer to select the authority when viewing patient information. The display mode area 104 is an area for the viewer to select a display mode when viewing patient information. The OK button 105 is a button for confirming the information set on the display mode setting screen 235 . The cancel button 106 is a button for canceling the settings on the display mode setting screen 235 .

[0115] The control unit 21 of the user terminal 20 transmits the information selected or input at the user terminal 20 to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 updates the display patient table T7 in the storage unit 15 based on the information received via the communication unit 12. Specifically, the control unit 11 stores the patient's user ID entered in the patient ID area 101 in the "referenced person ID" field of the display patient table T7. The control unit 11 stores the user ID of the referrer entered in the referrer ID area 102 in the "referee ID" field of the display patient table T7. The control unit 11 stores the authority ID corresponding to the authority selected in the authority area 103 in the "authority ID" field of the display patient table T7 (see authority master table T5). The control unit 11 stores the display mode ID corresponding to the display mode (mode name) selected in the display mode area 104 in the "display mode ID" field of the display patient table T7 (see display mode master table T6).

[0116] Next, a method for setting each record in the display mode item table T9 will be described. The control unit 11 of the patient information management server 10 causes the display unit 23 of the user terminal 20 to display a display mode detail setting screen.

[0117] 25 shows an example of a display mode advanced setting screen 236 displayed on the display unit 23 of the user terminal 20. The display mode advanced setting screen 236 includes a display mode area 111, a display mode advanced setting area 112, an OK button 113, a cancel button 114, and the like. The display mode area 111 is an area for selecting a display mode to be set. The display mode detail setting area 112 is an area for setting whether or not to display each item and the display format for the display mode to be set. The display mode detail setting area 112 is provided with a display / non-display selection field 115 and a display format selection field 116 for each item (item ID, item name). The display / non-display selection field 115 is an area for selecting whether or not to display the item to be set. The display format selection field 116 is an area for selecting the display format for an item for which "display" is selected in the display / non-display selection field 115. The OK button 113 is a button for confirming the information set on the display mode detail setting screen 236 . The cancel button 114 is a button for canceling the settings on the display mode advanced setting screen 236 .

[0118] The control unit 21 of the user terminal 20 transmits the information selected or input at the user terminal 20 to the patient information management server 10 via the communication unit 24. The control unit 11 of the patient information management server 10 updates the display mode item table T9 of the storage unit 15 based on the information received via the communication unit 12. Specifically, the control unit 11 stores in the display mode item table T9 a combination of a "display mode ID" corresponding to the display mode selected in the display mode area 111 and an "item ID" corresponding to the item for which "display" was selected in the display / non-display selection field 115 of the display mode advanced setting area 112. Furthermore, the control unit 11 stores in the display mode item table T9 the "display format" selected in the display format selection field 116 in association with the "item ID" corresponding to the item for which "display" was selected in the display / non-display selection field 115.

[0119] Here, we have explained the case where a record is added to or changed in the display patient table T7 or the display mode item table T9 from the user terminal 20. Alternatively, a system administrator of the patient information management server 10 may access the patient information management server 10 from any terminal and add or change a record in the display patient table T7 or the display mode item table T9.

[0120] As described above, according to this embodiment, the control unit 11 of the patient information management server 10 can accept input of a first login ID corresponding to a patient and a second login ID corresponding to a user other than the patient. The control unit 11 displays the patient information or health record information of the patient on the display unit 23 of the user terminal 20 in different display modes depending on whether input of the first login ID or the second login ID is accepted. The control unit 11 can select a more appropriate display mode depending on the person viewing the information about the patient. For example, the control unit 11 can customize the display screen so that the information required by the viewer is provided in a display mode appropriate for the viewer.

[0121] Furthermore, the control unit 11 determines the display mode of the patient information or health record information of the patient based on the patient information of the patient or the user information of the user corresponding to the second login ID. For example, the control unit 11 can select a more appropriate display mode for displaying the patient information or health record information of the patient based on the age of the patient, the age of the person viewing the information, the relationship between the patient and the person viewing the information, whether the patient needs input assistance, etc.

[0122] Furthermore, the control unit 11 changes the user interface when displaying the patient information or health record information of the patient when input of the second login ID corresponding to the patient's family member is accepted, based on the patient information of the current patient or the user information of the current patient's family member. For example, the control unit 11 can provide an appropriate display screen for the family member to refer to or input information about the patient, based on the patient's age, whether the patient needs input assistance, the relationship between the patient and the family member, etc.

[0123] The control unit 11 can change the display mode of patient information or health record information depending on whether, from the perspective of the referrer, the patient (referenced person) is a child (infant, elementary school student, junior high school student, high school student), a parent (elderly person), a spouse, a sibling, etc. In addition, the control unit 11 may change the display mode depending on the position of the viewer when the viewer is other than the patient's family member, for example, a medical professional (doctor, nurse, pharmacist, medical clerk, care manager, etc.) or a guardian.

[0124] The control unit 11 also accepts input of patient information or health record information of the patient by a user corresponding to the second login ID. The control unit 11 can register the patient information or health record information of the patient input by the family member for items for which the family member has the authority to edit the patient information or health record information of the patient.

[0125] Furthermore, the control unit 11 sets at least one display mode, that is, a display mode of the patient information or health record information of the patient when input of the first login ID is accepted, and a display mode of the patient information or health record information of the patient when input of the second login ID is accepted. For example, the control unit 11 can set the display mode and authority for displaying the patient information or health record information to the patient himself / herself or the patient's family, etc., based on information input on the display mode detail setting screen 235 (see FIG. 24). Furthermore, the control unit 11 can set the display items and display format corresponding to each display mode based on information input on the display mode detail setting screen 236 (see FIG. 25).

[0126] Furthermore, if the patient's vital information is not entered within a predetermined period, the control unit 11 notifies the user (family member, etc.) corresponding to the second login ID of information indicating that the patient's vital information has not been entered. For example, by notifying the patient's family member that a predetermined item has not been entered, the control unit 11 can reliably store the patient's records even if the patient himself / herself is unable to manage the input of information.

[0127] The above-described embodiments are merely examples of the information processing device and program according to the present invention, and the present invention is not limited to these. The detailed configurations and operations of the devices constituting the system can be modified as appropriate without departing from the spirit of the present invention.

[0128] For example, the control unit 11 of the patient information management server 10 may change the display mode of the patient information or health record information of the patient depending on the type of illness (diabetes, heart disease, chronic disease, etc.) of the patient.

[0129] Furthermore, a patient's family may be able to newly register user information of an unregistered patient in the patient information management server 10. For example, the patient's family may operate the operation unit 22 of the user terminal 20 to launch the PHR sharing app and select to register a new patient. The control unit 11 of the patient information management server 10 then displays a new patient registration screen on the display unit 23 of the user terminal 20.

[0130] The patient's family inputs the patient's user information (patient information) by operating the operation unit 22 on the user terminal 20. Specifically, the patient's family inputs the patient's name, sex, date of birth, password, whether input assistance is required, display mode settings, etc. The control unit 11 of the patient information management server 10 assigns a new user ID. The control unit 11 associates the user information input on the user terminal 20 with the assigned user ID and registers them in the user table T1 of the memory unit 15.

[0131] Furthermore, the patient's family may register their relationship to the patient, display mode, and authority through operation of the operation unit 22 on the user terminal 20. Here, the "display mode" refers to the display mode used by the registrant (family) to view the patient information or health record information of the newly registered patient. The "authority" refers to the authority the registrant (family) has over the patient information or health record information of the newly registered patient. The control unit 11 of the patient information management server 10 additionally registers records in the family table T3 and the displayed patient table T7 of the storage unit 15 based on the information (relationship, display mode, and authority) input (selected) on the user terminal 20. Specifically, the control unit 11 associates the "family ID" associated with the registrant (family) in the family table T3 with the "user ID" of the patient and registers them in the family table T3. Note that if there are multiple "family IDs" associated with the registrant (family), the control unit 11 identifies the "family ID" corresponding to the family member to which the patient belongs based on the "relationship" selected on the user terminal 20. Alternatively, the registrant (family member) may specify the family member to which the patient belongs. Furthermore, the control unit 11 stores the patient's user ID in the "referenced person ID" field of the displayed patient table T7, and stores the user ID of the registrant (family member) in the "referee ID" field. The control unit 11 stores the authority ID corresponding to the selected authority in the "authority ID" field of the displayed patient table T7, stores the display mode ID corresponding to the selected display mode in the "display mode ID" field, and stores the relationship ID corresponding to the selected relationship in the "relationship ID" field.

[0132] The computer-readable medium for storing the program for executing each process is not limited to the above examples. A carrier wave may also be used as a medium for providing program data via a communication line. [Explanation of symbols]

[0133] 10. Patient Information Management Server 11 Control section 12 Communications Department 15 Storage section 20 user terminals 21 Control section 22 Control section 23 Display section 24 Communications Department 30 Clinic terminals 40 Pharmacy terminal 100 Information Sharing System 233 Patient Details Screen 234 Patient Details Screen 235 Display mode setting screen 236 Display mode detailed setting screen N Communication Network T1 User Table T2 Health Record Information Table T3 Family Table T4 Relationship Table T5 Authority Master Table T6 Display Mode Master Table T7 Display Patient Table T8 Item Table T9 Display Mode Item Table T10 Item Authorization Table T11 Notification Master Table T12 Notification Management Table

Claims

1. a reception unit capable of receiving input of a first login ID corresponding to a patient and a second login ID corresponding to a user other than the patient; a display control unit that displays the patient information or health record information of the patient on the display unit in different display modes depending on whether the input of the first login ID is accepted or the input of the second login ID is accepted; An information processing device comprising:

2. The information processing device according to claim 1 , wherein the display control unit determines a display mode of the patient information or health record information of the patient based on the patient information of the patient or user information of the user corresponding to the second login ID.

3. The information processing device according to claim 1 , wherein the accepting unit accepts input of patient information or health record information of the patient by a user corresponding to the second login ID.

4. 2. The information processing device according to claim 1, further comprising a setting unit capable of setting at least one display mode of the patient information or health record information of the patient when input of the first login ID is accepted, and the display mode of the patient information or health record information of the patient when input of the second login ID is accepted.

5. the user corresponding to the second login ID is a family member of the patient; 2. The information processing device according to claim 1, wherein the display control unit changes a user interface when displaying the patient information or health record information of the patient when input of the second login ID is accepted, based on the patient information of the current patient or the user information of the current patient's family member.

6. the patient's health record information includes the patient's vital information; 2. The information processing device according to claim 1, further comprising a notification unit that, if the patient's vital information is not input within a predetermined period, notifies a user corresponding to the second login ID of information indicating that the patient's vital information has not been input.

7. Computer, a reception unit capable of receiving input of a first login ID corresponding to a patient and a second login ID corresponding to a user different from the patient; a display control unit that displays the patient information or health record information of the patient on the display unit in different display modes depending on whether the input of the first login ID is accepted or the input of the second login ID is accepted; A program to function as a

Images