Data sharing system and data sharing method

Abstract

Various health-related information acquired from various applications can be shared with medical institutions. A data sharing system that shares data relating to the health of a subject between a plurality of applications for acquiring data and a medical institution terminal for viewing the data, the data sharing system being provided with: a storage unit that stores the data in the medical institution terminal and stores the data in the medical institution terminal; a management unit that associates and manages cooperation between a first account ID for a subject to access the data sharing system and a second account ID for a user of a medical institution terminal to access the data sharing system with at least one application; and a control unit that, in response to a request from a medical institution terminal, specifies data acquired by an application associated with a first account ID that cooperates with a second account ID corresponding to the medical institution terminal.

Description

Technical Field

[0001] The present invention relates to a data sharing system and the like. Background Art

[0002] In recent years, a system has been proposed in which a medical institution and patients related to the medical institution share information related to the patients via a server or the like.

[0003] For example, Patent Document 1 discloses a patient information sharing server and method for sharing patient information between medical institutions and patients. Specifically, the server assigns a patient identifier to each patient, associates the patient identifier with the medical institution designated by the patient, receives input from the patient's terminal in response to notifications from the medical institution, and stores the input as patient information, associating it with the patient identifier.

[0004] However, Patent Document 1 does not disclose a method of having a plurality of applications related to a patient's health and sharing various health-related information acquired from the plurality of applications with medical institutions.

[0005] Prior art literature Non-patent literature Patent Document 1: Japanese Patent Application Laid-Open No. 2019-191765 Summary of the Invention Problems to be solved by the invention The present invention has been completed based on the above-mentioned technical background, and one of its objects is to provide a data sharing method capable of sharing various health-related information acquired from various applications with medical institutions.

[0006] Technical solutions to solve problems According to a first aspect of the present invention, there is provided a data sharing system for sharing data between a plurality of applications for acquiring data and a medical institution terminal for viewing the data, wherein the data is related to the health of a subject, wherein the data sharing system comprises: a storage unit for managing the collaboration of a first account ID and a second account ID in a corresponding relationship with at least one application, the first account ID being used for the subject to access the data sharing system, and the second account ID being used for the user of the medical institution terminal to access the data sharing system; and a control unit for determining, based on a request from the medical institution terminal, data acquired by an application that has established a corresponding relationship with the first account ID, the first account ID and the second account ID corresponding to the medical institution terminal collaborating.

[0007] According to a second aspect of the present invention, there is provided a data sharing method for a data sharing system, wherein data is shared between a plurality of applications for acquiring data and a medical institution terminal for viewing the data, the data being related to the health of a subject, wherein the collaboration of a first account ID and a second account ID is managed in a corresponding relationship with at least one application, the first account ID being used for the subject to access the data sharing system, the second account ID being used for the user of the medical institution terminal to access the data sharing system, and based on a request from the medical institution terminal, data acquired by the application having a corresponding relationship with the first account ID is determined, and the first account ID and the second account ID corresponding to the medical institution terminal collaborate.

[0008] Effects of the Invention According to the present invention, data can be shared between a plurality of applications for acquiring data related to the health of a subject and a medical institution terminal for viewing the data, wherein the data is related to the health of the subject. In addition, the collaboration of a first account ID and a second account ID is managed in a corresponding relationship with at least one application, the first account ID being used for the subject to access the data sharing system, and the second account ID being used for the user of the medical institution terminal to access the data sharing system. Therefore, according to a request from a medical institution and based on the collaboration of the managed account IDs, data associated with a specific application can be determined. In addition, by determining the data, the data can be provided to the medical institution. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 This is a flowchart showing an example of the flow of the data sharing method according to the present embodiment.

[0010] Figure 2 It is a diagram showing an example of the system configuration of the information system according to the first embodiment.

[0011] Figure 3 This is a diagram showing an example of functions implemented by the control unit of the management server according to the first embodiment.

[0012] Figure 4 This is a diagram showing an example of information stored in the storage unit of the management server according to the first embodiment.

[0013] Figure 5 FIG. 1 is a diagram showing an example of PHR user account registration data according to the first embodiment.

[0014] Figure 6 FIG. 1 is a diagram showing an example of PHR medical institution account registration data according to the first embodiment.

[0015] Figure 7 FIG. 1 is a diagram showing an example of PHR application registration data according to the first embodiment.

[0016] Figure 8 FIG. 1 is a diagram showing an example of account ID / PHR application cooperation management data according to the first embodiment.

[0017] Figure 9 FIG. 1 is a diagram showing an example of PHR application data management data according to the first embodiment.

[0018] Figure 10 This is a diagram showing an example of functions implemented by the control unit of the subject terminal according to the first embodiment.

[0019] Figure 11 1 is a diagram showing an example of information stored in the storage unit of the subject terminal according to the first embodiment.

[0020] Figure 12 This is a diagram showing an example of a screen displayed on the display unit of each terminal in the first embodiment.

[0021] Figure 13 This is a diagram showing an example of a screen displayed on the display unit of each terminal in the first embodiment.

[0022] Figure 14 This is a diagram showing an example of a screen displayed on the display unit of each terminal in the first embodiment.

[0023] Figure 15 This is a diagram showing an example of a screen displayed on the display unit of each terminal in the first embodiment.

[0024] Figure 16 This is a diagram showing an example of a screen displayed on the display unit of each terminal in the first embodiment.

[0025] Figure 17 This is a diagram showing an example of a screen displayed on the display unit of the medical institution terminal according to the first embodiment.

[0026] Figure 18 This is a diagram showing another example of a screen displayed on the display unit of the medical institution terminal according to the first embodiment.

[0027] Figure 19 1 is a flowchart showing an example of the flow of processing executed by each device of the first embodiment.

[0028] Figure 20 1 is a flowchart showing an example of the flow of processing executed by each device of the first embodiment.

[0029] Figure 21 It is an explanatory diagram of the data sharing method according to the first modification.

[0030] Figure 22 It is an explanatory diagram of the data sharing method according to the first modification.

[0031] Figure 23 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the first modification.

[0032] Figure 24 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the first modification.

[0033] Figure 25 This is a flowchart showing an example of the flow of processing executed by each device in the first modification.

[0034] Figure 26 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the first modification.

[0035] Figure 27 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the first modification.

[0036] Figure 28 This is a flowchart showing an example of the flow of processing executed by each device in the first modification.

[0037] Figure 29 This is a diagram showing an example of information stored in the storage unit of the medical institution terminal according to the first modification.

[0038] Figure 30 FIG. 1 is a diagram showing an example of applying patient identification data to a PHR according to the first modification.

[0039] Figure 31 It is a diagram showing an example of the system configuration of the information system according to the second embodiment.

[0040] Figure 32 This is a diagram showing an example of functions implemented by the control unit of the medical institution server according to the second embodiment.

[0041] Figure 33 This is a diagram showing an example of information stored in the storage unit of the medical institution server according to the second embodiment.

[0042] Figure 34 This is a diagram showing an example of EMR account registration data according to the second embodiment.

[0043] Figure 35 FIG. 1 is a diagram showing an example of EMR patient information management data according to the second embodiment.

[0044] Figure 36 FIG. 1 is a diagram showing an example of PHR / EMR associated registration data according to the second embodiment.

[0045] Figure 37 This is a diagram showing an example of a screen displayed on the display unit of each terminal according to the second embodiment.

[0046] Figure 38 This is a diagram showing an example of a screen displayed on the display unit of each terminal according to the second embodiment.

[0047] Figure 39 This is a diagram showing an example of a screen displayed on the display unit of the medical institution terminal according to the second embodiment.

[0048] Figure 40 1 is a flowchart showing an example of the flow of processing executed by each device of the second embodiment.

[0049] Figure 41 1 is a flowchart showing an example of the flow of processing executed by each device of the second embodiment.

[0050] Figure 42 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the second modification.

[0051] Figure 43 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the second modification.

[0052] Figure 44 This is a flowchart showing an example of the flow of processing executed by each device in the second modification.

[0053] Figure 45 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the second modification.

[0054] Figure 46 This is a flowchart showing an example of the flow of processing executed by each device in the second modification.

[0055] Figure 47 FIG. 1 is a diagram showing another example of EMR patient information management data according to the second modification.

[0056] Figure 48 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the third embodiment.

[0057] Figure 49 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the third embodiment.

[0058] Figure 50 1 is a flowchart showing an example of the flow of processing executed by each device of the third embodiment.

[0059] Figure 51 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the fourth embodiment.

[0060] Figure 52 It is a diagram showing an example of a screen displayed on the display unit of each terminal according to the fourth embodiment.

[0061] Figure 53 1 is a flowchart showing an example of the flow of processing executed by each device of the fourth embodiment.

[0062] Figure 54 FIG. 1 is a diagram showing an example of PHR / EMR associated registration data according to the fifth embodiment.

[0063] Figure 55 1 is a flowchart showing an example of the flow of processing executed by each device of the fifth embodiment.

[0064] Figure 56 1 is a flowchart showing an example of the flow of processing executed by each device of the fifth embodiment. DETAILED DESCRIPTION

[0065] Embodiments for implementing the data sharing method and the like of the present disclosure will be described with reference to the accompanying drawings.

[0066] In the description of the drawings, the same elements are denoted by the same reference numerals and descriptions thereof may be omitted.

[0067] In addition, the components described in the present embodiment are merely examples and are not intended to limit the scope of the present invention.

[0068] The information system 1 of this embodiment is an information system for sharing health-related data obtained from various applications used by subjects between, for example, multiple subjects and multiple medical institutions (medical practitioners). The information system 1 may also be called a data sharing system.

[0069] Hereinafter, for example, applications used to collect, record, verify, and share health-related data will be referred to as PHR (Personal Health Record) applications. Furthermore, health-related data will be referred to as PHR data. PHR data may also include, for example, various health-related information (e.g., medication records or activity logs), life logs such as blood pressure, weight, number of steps, sleep, and diet, and data generated by medical institutions that has been consented to by other practitioners or for purposes other than medical use. Furthermore, PHR data may include data in any format, such as text, numerical data, dynamic images, and still images.

[0070] Hereinafter, a subject who uses a PHR application may be referred to simply as a “user.” A subject may also be referred to as a “patient.”

[0071] In addition, the situation where users of a medical institution (e.g., medical practitioners) can use PHR applications and refer to (and may also edit) the user's PHR data is sometimes referred to as "PHR data collaboration," "PHR application collaboration," or "PHR data sharing."

[0072] Sometimes the platform that comprehensively manages accounts and PHR data in various PHR applications is called a PHR platform.

[0073] It should be noted that users who can use the PHR platform are not limited to examinees and medical institutions. For example, it can also be used by examinees and practitioners who process examinees' PHR data (for example, caregivers, special education teachers, and gym coaches).

[0074] Hereinafter, for example, an electronic medical record application intended for use by users of a medical institution mainly within the medical institution will be referred to as an EMR (Electronic Medical Record) application.

[0075] It should be noted that in this specification, in addition to the diagnosis-related information contained in the electronic medical record, EMR applications also include examination information (blood collection results, examination images, etc.), patient background / basic information (medical history, blood pressure, weight, etc.), prescription information (medical treatment behavior, medicines, etc.), and may also include the concept of EHR (Electric Health Record) applications aimed at information collaboration with external medical institutions.

[0076] In the following, applications mainly used to manage data acquired by medical institutions may be distinguished from EMR applications, and applications mainly used to manage data acquired from examinees may be distinguished from PHR applications.

[0077] In this specification, the information system 1 may be configured to include a plurality of devices, for example.

[0078] It should be noted that, in the information system 1 , for example, a plurality of devices can cooperate to perform arbitrary processing.

[0079] Furthermore, the information system 1 related to the client (client device) and the server may be, for example, a system including at least one terminal and at least one server. This example may also be a client-server system.

[0080] A server can be a single device or a combination of multiple devices (a server system). In addition, the server function can also be provided in the form of PaaS, IaaS, or SaaS in cloud computing.

[0081] It should be noted that the information system 1 may also be a system composed of a plurality of terminals.

[0082] This system may be, for example, the following system.

[0083] A system that enables terminals to function as servers (a decentralized system). This system can be implemented using blockchain technology, for example.

[0084] A system in which terminals communicate wirelessly with each other. This system can be implemented by using a short-range wireless communication technology such as Bluetooth (registered trademark) and a P2P (direct communication) method.

[0085] PHR data collected from multiple PHR applications allows medical institutions and patients to grasp comprehensive medical information. However, managing PHR applications and PHR data is complex for both medical institutions and patients.

[0086] For example, in the diagnosis and treatment of ASD, subjects use their terminals to input PHR data, such as their activity records, medication records, and weight / height, into applications dedicated to each data type. Medical institutions can use the subject's activity records, medication records, weight / height, and other PHR data as reference material for ASD diagnosis or treatment guidelines, enabling more comprehensive information-based diagnoses or selection of appropriate treatment methods. However, without a method for unified management / sharing of these PHR applications and PHR data, data analysis and comparison becomes difficult, potentially reducing the efficiency and accuracy of diagnosis or treatment.

[0087] Therefore, an efficient data sharing method for multiple applications and PHR data is sought.

[0088] It's important to note that PHR data can be not only manually entered by the patient but can also be automatically recorded or provided by others and registered in the PHR application. For example, the patient's terminal can continuously measure the patient's step count and automatically record it in the PHR application. Furthermore, the patient's terminal can also receive the patient's prescription information from a doctor or pharmacist and automatically record it in the PHR application.

[0089] First, use Figure 1 The data sharing method of this embodiment will be described.

[0090] In this embodiment, data related to a subject's health is shared between multiple applications for acquiring data related to the subject's health and a medical institution terminal for viewing the data. This data sharing method may be performed by a data sharing system (hereinafter sometimes referred to as a "sharing system").

[0091] Specifically, the collaboration between the first account ID and the second account ID is managed in a corresponding relationship with at least one application, wherein the first account ID is used for the examinee to access the shared system, and the second account ID is used for the user of the medical institution terminal to access the shared system (S1).

[0092] Then, a request is received from the medical institution terminal (S3). Specifically, for example, a request for data (e.g., a request to provide data) associated with a first account ID is received, where the first account ID is associated with a second account ID associated with the user of the medical institution terminal.

[0093] Then, based on a request from the medical institution terminal, data acquired by an application associated with the first account ID is determined, and the first account ID is coordinated with a second account ID associated with the medical institution terminal (S5). By determining the data, the data can be provided to the medical institution terminal.

[0094] It should be noted that, as will be described in detail later, data may be provided mainly by the shared system or by a system other than the shared system.

[0095] It should be noted that step S2 (for example, a step of registering data related to the subject's health into a shared system) may also be set between steps S1 and S3 as a step of registering data related to the subject's health in a corresponding relationship with the first account ID and the application that obtains the data.

[0096] It should be noted that, in this case, the order of steps S1 and S2 can be arbitrary, and they can also be performed simultaneously.

[0097] The sharing system may be, for example, a system composed of one or more management devices (eg, one or more server devices). The sharing system may also be understood as a system that manages the sharing of data related to the health of the subject.

[0098] The following describes in detail an embodiment for implementing the above-mentioned data sharing method.

[0099] <First embodiment> The first embodiment is an embodiment in which the PHR platform can be used to refer to PHR data on a medical institution terminal used by a medical institution. The PHR data is recorded in various PHR applications on a subject terminal used by a subject.

[0100] The contents described in the first embodiment are also applicable to any of the other embodiments or other modified examples.

[0101] System Structure Figure 2 This figure shows an example of the system configuration of information system 1 according to the present embodiment. In information system 1, for example, a PHR platform management server 10, one or more subject terminals 20 (20A, 20B, 20C, ...), and one or more medical institution terminals 30 (30A, 30B, 30C, ...) are connected via a network 40.

[0102] Hereinafter, the user of the subject terminal 20A communicating with the management server 10 is referred to as “user UA”, the user of the subject terminal 20B is referred to as “user UB”, and the user of the subject terminal 20C is referred to as “user UC”.

[0103] In the following description, the user of the medical institution terminal 30A communicating with the management server 10 is referred to as “medical institution HA”, the user of the medical institution terminal 30B is referred to as “medical institution HB”, and the user of the medical institution terminal 30C is referred to as “medical institution HC”.

[0104] The management server 10 is, for example, an information processing device owned by a practitioner operating a PHR platform, and has the function of providing, for example, the collection and recording of PHR data in various PHR applications and the coordination of PHR data to the subject terminal 20 via the network 40. The management server 10 may be an example of a shared system and, as described above, may be a single server or multiple server devices.

[0105] Practitioners who use the PHR platform may be practitioners who develop / use PHR applications, or practitioners who cooperate with practitioners who develop / use PHR applications.

[0106] Subject terminal 20 may be, for example, a smartphone, tablet, personal computer, or smartwatch. Subject terminal 20A, subject terminal 20B, and subject terminal 20C may have the same configuration. Hereinafter, the terminal used by user X may be referred to as subject terminal 20X, as needed.

[0107] The medical institution terminal 30 may be the same as the subject terminal 20 described above.

[0108] The network 40 has the role of connecting the devices constituting the information system 1 and providing a connection path for transmitting and receiving data. The network 40 may be, for example, a wide area network such as the Internet formed by a wired network or a wireless network.

[0109] [Hardware Structure of Each Device] (1) Terminal hardware structure Figure 2 An example of the hardware configuration of the subject terminal 20 is shown.

[0110] The subject terminal 20 includes, for example, a control unit 21 including a CPU, etc.; a storage unit 28 including RAM or ROM, etc.; a communication unit 22 having wired or wireless communication capabilities; an input / output unit 23 including a device for inputting various operations to the subject terminal 20 or a device for outputting processing results processed by the subject terminal 20; a clock unit 29A including a clock using a crystal oscillator or a clock using the NITZ (Network Identity and Time Zone) standard; and a position calculation information detection unit 29B including a sensor or unit for calculating the position of the subject terminal 20 using a satellite positioning system such as the GNSS (Global Navigation Satellite System). The hardware components of the subject terminal 20 are interconnected, for example, via a bus B. It should be noted that the subject terminal 20 may also have a configuration in which individual components or multiple components are detachable.

[0111] For example, the input / output unit 23 includes a display unit 24 such as a liquid crystal display or an OLED, a sound input unit 25 such as a microphone, a sound output unit 26 such as a speaker, and an imaging unit 27 such as a camera.

[0112] The medical institution terminal 30 may be the same as the subject terminal 20 described above.

[0113] (2) Server hardware structure Figure 2 An example of the hardware configuration of the management server 10 is shown.

[0114] The management server 10 includes, for example, a control unit 11 including a CPU, etc.; a storage unit 15 including RAM, ROM, a magnetic disk, or a semiconductor drive; a communication unit 14 with wired or wireless communication capabilities; an input / output unit 12 including a keyboard, etc.; a display unit 13 including a liquid crystal display, etc.; and a clock unit 19 including a clock using a quartz oscillator, a NITZ clock, etc. The hardware components of the management server 10 are interconnected, for example, via a bus B. It should be noted that the hardware of the management server 10 may also be configured such that individual components or multiple components are detachable.

[0115] (3) Others At least a part of the processing in the management server 10 and / or the subject terminal 20 and / or the medical institution terminal 30 may be realized by cloud computing composed of one or more computers.

[0116] A configuration may be adopted in which the management server 10 performs at least a part or all of the processing in the subject terminal 20 and / or the medical institution terminal 30 .

[0117] Conversely, a configuration may be adopted in which at least a part or all of the processing in the management server 10 is performed by the subject terminal 20 and / or the medical institution terminal 30 .

[0118] Unless otherwise specified, the determination structure of the embodiment of the present disclosure is not essential, and a predetermined process may be executed when the determination condition is satisfied, or may be executed when the determination condition is not satisfied.

[0119] [Functional Structure of Each Device] (1) Functional structure of the management server Figure 3 1 is a diagram showing an example of functions implemented by the control unit 11 of the management server 10 in this embodiment.

[0120] The control unit 11 includes, as a functional unit, a PHR application management processing unit 111 that executes a PHR application management process (also referred to as a PHR platform management process) according to a PHR application management processing program 151 stored in the storage unit 15 .

[0121] Figure 4 1 is a diagram showing an example of information stored in the storage unit 15 of the management server 10 in this embodiment.

[0122] The storage unit 15 stores, for example, a PHR application management processing program 151 , PHR user account registration data 153 , PHR medical institution account registration data 155 , PHR application registration data 157 , and account ID / PHR application cooperation management data 159 .

[0123] The PHR user account registration data 153 is registration data related to the account of the examinee on the PHR platform. Figure 5 An example of this data structure is shown.

[0124] For example, the user name, user account ID, and other registration information are associated and stored in the PHR user account registration data 153 .

[0125] The user name is the name of the account of the subject terminal 20 that uses the PHR platform, and for example, stores the name registered by the user of the subject terminal 20 when using the PHR platform.

[0126] The user account ID is information for identifying the subject's account in the PHR platform. The user account ID is preferably a unique value for each account, and is set and stored by the management server 10 , for example, as a unique value for each account (inherent value).

[0127] The user account ID is information associated with the subject terminal 20 or the user of the subject terminal 20, and may also be an example of information related to the terminal or the user of the terminal. Alternatively, the user account ID may be a first account ID. This first account ID may be an example of an ID used by the subject (or subject terminal 20) to access the shared system.

[0128] It should be noted that, when the identification information for identifying the subject terminal 20 is uniquely associated with the user account ID, the user account ID may also be referred to as the identification information of the subject terminal 20 .

[0129] For example, various information such as user information (address, birthday, gender, etc.) or identification information for identifying the subject terminal 20 (IMEI (International Mobile Equipment Identity), etc.), the telephone number of the subject terminal 20 (terminal telephone number), email address (terminal email address), passwords used for various authentications in the PHR platform or application (login password, authentication password, etc.), and other authentication information may also be stored in other registration information.

[0130] The PHR medical institution account registration data 155 is registration data related to the account of the medical institution that joins the PHR platform. Figure 6 An example of this data structure is shown.

[0131] For example, the medical institution name, medical institution account ID, and other registration information are associated and stored in the PHR medical institution account registration data 155 .

[0132] The medical institution name is the name of the account of the medical institution terminal 30 that uses the PHR platform, and for example, stores the name registered by the medical institution using the medical institution terminal 30 when using the PHR platform.

[0133] The medical institution account ID is information used to identify the medical institution account in the PHR platform. The medical institution account ID is preferably a unique value for each account, and is set and stored by the management server 10, for example, as a unique value for each account (unique value).

[0134] The medical institution account ID is information associated with the medical institution terminal 30 or the medical institution of the medical institution terminal 30, and may also be an example of information related to the terminal or the medical institution. Alternatively, the medical institution account ID may be a second account ID. This second account ID may be an example of an ID used by the user of the medical institution terminal 30 (or the medical institution terminal 30) to access the shared system.

[0135] For example, various information such as medical institution information (address or representative contact information, location information, medical department, etc.) or identification information for identifying the medical institution terminal 30 (IMEI (International Mobile Equipment Identity) etc.), the telephone number of the medical institution terminal 30 (terminal telephone number), email address (terminal email address), passwords used for various authentications in the PHR platform or application (login password, authentication password, etc.), and other authentication information may also be stored in other registration information.

[0136] It should be noted that, in the same medical institution, for example, multiple medical institution account IDs may be registered for each medical department or medical practitioner.

[0137] In addition, the medical institution account ID can also be obtained by practitioners who process PHR data on the PHR platform, such as caregivers, teachers in special education classes, and coaches in sports halls.

[0138] The PHR application registration data 157 is registration data related to applications that collaborate with the PHR platform. Figure 7 An example of this data structure is shown.

[0139] For example, the PHR application name, the PHR application ID, and other application information are associated and stored in the PHR application registration data 157 .

[0140] The PHR application name is the name of each PHR application, for example, a name set by a developer of the stored PHR application when registering the application on the PHR platform.

[0141] The PHR application ID is information for identifying each PHR application. The PHR application ID is preferably a unique value for each PHR application, and is set and stored by the management server 10 as a unique value for each PHR application (a unique value).

[0142] For example, a URI (Uniform Resource Identifier) ​​for downloading the PHR application or a description of the PHR application may also be stored in other application information.

[0143] It should be noted that various PHR applications that can be used on the PHR platform include, for example, an ASD (Autism Spectrum Disorder) diagnosis application that can record / reference records of images of the subject and / or their relatives, a home care record application that processes records of care provided by home caregivers to patients, a medication record application that records the intake of prescribed medications, and a peak flow recording application that records peak flow related to asthma. Furthermore, PHR applications may also include applications that process monitoring records related to specified health conditions such as hay fever, and applications that process information obtained through communication with devices that monitor health conditions on the subject's terminal 20, such as blood sugar monitoring devices or smart watches.

[0144] The account ID / PHR application collaboration management data 159 is management data for collaboration between the user account ID, medical institution account ID, and PHR application ID. Figure 8 An example of this data structure is shown.

[0145] For example, the user account ID, the medical institution account ID, and the PHR account ID are associated and stored in the account ID / PHR application cooperation management data 159 .

[0146] The account ID / PHR application collaboration management data 159 can be an example of data that manages the collaboration between the first account ID and the second account ID by establishing a correspondence with at least one application. The above-mentioned first account ID is used for the examinee to access the shared system, and the above-mentioned second account ID is used for the user of the medical institution terminal to access the shared system.

[0147] As a method of providing the PHR data requested by the medical institution (medical institution terminal 30 ), various methods are conceivable.

[0148] In the main embodiment, a case is exemplified in which PHR data is registered in the management server 10 and the management server 10 provides the PHR data stored in the storage unit 15 to the medical institution terminal 30 based on a request from the medical institution terminal 30 .

[0149] In this case, the storage unit 15 of the management server 10 may store, for example, Figure 9 The PHR application data management data shown is management data for each user account ID. Figure 9 The PHR application data management data of the user account ID “U0001” is illustrated as an example.

[0150] For example, the user account ID and PHR data management data may be stored in each PHR application data management data. The PHR application data management data may be an example of data for managing accounts corresponding to subjects based on a user account ID commonly used in multiple PHR applications.

[0151] The PHR data management data may be data capable of registering a plurality of PHR data corresponding to respective PHR applications. For example, the PHR application ID and the PHR data may be stored in association with each other.

[0152] (2) Functional structure of the subject's terminal Figure 10 1 is a diagram showing an example of functions implemented by the control unit 21 of the subject terminal 20 in this embodiment.

[0153] The control unit 21 includes, as a functional unit, a PHR application processing unit 211 for executing PHR application processing according to a PHR application processing program 281 stored in the storage unit 28 , for example.

[0154] Figure 11 1 is a diagram showing an example of data and the like stored in the storage unit 28 of the subject terminal 20 in this embodiment.

[0155] The storage unit 28 stores, for example, various PHR application processing programs 281A, PHR application processing programs 281B, PHR application processing programs 281C, etc., which are executed as PHR application processing, as well as device identification information 283 (for example, a telephone number or IMEI, etc.) for identifying the subject terminal 20 or the account of the user of the subject terminal 20.

[0156] It should be noted that the PHR application ID assigned to each PHR application processing program 281 may be stored. In addition, the user account ID of the subject terminal 20 may be stored in the device identification information 283 .

[0157] (3) Functional structure of medical institution terminals The functional configuration of the medical institution terminal 30 may be the same as that of the subject terminal 20 , for example.

[0158] It should be noted that the PHR application ID assigned to each PHR application processing program 381 may be stored. In addition, the medical institution account ID of the medical institution terminal 30 may be stored in the device identification information 383 .

[0159] <Display screen> The following describes an example of a display screen. The display screen transitions described below are merely examples of display screen transitions for implementing the method disclosed herein. Regarding the display screen transitions illustrated below, some display screens may be omitted, or another display screen may be added.

[0160] The following example illustrates a case where the subject terminal 20 and the medical institution terminal 30 are smartphones having a vertically long display unit 24 or display unit 34. A case where a PC having a horizontally long display unit 34 is illustrated on a portion of the display screen.

[0161] It should be noted that predetermined screens displayed on different subject terminals 20 and / or medical institution terminals 30 may be shown in one drawing or across a plurality of drawings, and the flow of screen transitions may be described.

[0162] The following example illustrates a case where the subject terminal 20 that records PHR data on the PHR platform is set to the subject terminal 20A of the user UA. The account of the subject terminal 20A or the account of the user UA can be an example of the first account.

[0163] In the following example, the medical institution terminal 30 that references PHR data based on user collaboration on the PHR platform is exemplified by the medical institution terminal 30A of the medical institution HA. The account of the medical institution terminal 30A or the account of the medical institution HA may be an example of the second account.

[0164] In this example, an ASD diagnostic application is used as an example of a PHR application. The name of the PHR application used by the examinee is described as "PHR for ASD User App." Furthermore, the name of the PHR application used by a medical institution is described as "PHR for ASD Institute App."

[0165] Figures 12 to 16 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this embodiment.

[0166] Figure 12The left side shows an example of the main menu screen of the ASD diagnostic application displayed on the subject terminal 20A. On this main menu screen, below the user name ("UA") of the subject's terminal 20A, function buttons UM1, UM2, and UM3 are displayed as a selection menu for the subject. Function button UM1 is used to record the subject's actions, function button UM2 is used to reference the recorded subject actions, and function button UM3 is used to share the recorded action records (an example of PHR data) with a medical institution.

[0167] exist Figure 12 On the left screen, if the user taps the function button UM1, the subject terminal 20A will Figure 12 The display of the action record screen in the center changes so that the user can record the subject's actions as images using the camera of the subject terminal 20A.

[0168] On the action recording screen, in this example, a message notifying the recording of the action of "UA" (starting action recording) is displayed, and a "Capture image of subject" button UM11 for recording an image (moving image) of the subject using the imaging unit 27 and a "Annotate image" button UM12 for annotating the recorded image are displayed.

[0169] Figure 12 The right side shows a state where the “capture image of subject” button is tapped to activate the imaging unit 27 (which may be an application camera) and capture the user “UA” in a moving image using the front camera (forward-looking camera).

[0170] It should be noted that, if the "Annotate Image" button is tapped, for example, a list of captured images can be displayed, and after the user selects an image, a comment can be entered using a keyboard, etc. Furthermore, the entered comment data can be stored in association with the image data.

[0171] For example, after recording the subject's actions through images, if the user returns to the main menu screen and taps the function button UM2, the display of the PHR data display screen on the subject terminal 20A changes, and the user can review the recorded images.

[0172] It should be noted that, as mentioned above, PHR data may include data in any data format, such as text data, numerical data, dynamic images (video), and static images. Figure 12 A "manual action input" button for the user to input his or her own action in text or the like is displayed on the center screen, and information on the action input using a keyboard or the like (eg, text information) is included in the PHR data and recorded.

[0173] Figure 13 The left side represents Figure 12 On the same main menu screen as on the left, if the user taps the function button UM2, on the subject terminal 20A, Figure 13 The display of the action review screen on the right side has changed.

[0174] On the action review screen, for example, PHR data based on the action record (in this example, the date when the video was recorded, the video, and comments attached to the video) is displayed as the action record of the user "UA".

[0175] Figure 14 The left side represents Figure 12 On the same main menu screen as on the left, if the user taps the function button UM3, on the subject terminal 20A, Figure 14 The display of the central PHR data sharing confirmation screen has changed.

[0176] This screen displays, for example, a notice regarding sharing (also referred to as providing or collaborating) PHR data with a medical institution. Below the notice, a checkbox UC1 is displayed for agreeing to share PHR data based on the notice, and a function button UC2 is displayed for displaying PHR application collaboration code information for reading by the medical institution terminal 30.

[0177] For example, if the user taps the check box UC1, the function button UC2 changes from the grayed-out display mode to the normal display mode, making the action effective. Then, if the user taps the function button UC2, on the subject terminal 20A, Figure 14 The display of the PHR application collaboration code information display screen on the right side changes.

[0178] This screen displays, for example, the PHR application collaboration code information represented by a QR code, the user name of the subject terminal 20A in the PHR application, and the birthday as an example of user information. It should be noted that information such as the user's gender or the name of the collaborating PHR application may also be displayed. This allows users of the medical institution terminal 30 to avoid confusion among subjects collaborating on PHR data.

[0179] Figure 15The left side shows the main menu screen of the ASD diagnostic application displayed on the medical institution terminal 30A. Below the name of the medical institution ("HA") using the medical institution terminal 30A, function buttons HM1, HM2, and HM3 are displayed as a selection menu for the medical institution. Function button HM1 is used to view the actions of subjects who have collaborated with the PHR application. Function button HM2 is used to collaborate with subjects who are already using the ASD diagnostic application (who have established an account on the PHR platform). Function button HM3 is used to instruct subjects who are not using the ASD diagnostic application to install the application and collaborate with the PHR application (also known as "application prescription").

[0180] For example, if the user taps the function button HM2, on the medical institution terminal 30A, Figure 15 The display of the central PHR application coordination code information reading screen is changed. The PHR application coordination code information reading screen displays, for example, a preview screen of the image acquired by the imaging unit 37 and guidance information prompting the subject terminal 20 to include the PHR application coordination code information displayed on the preview screen.

[0181] For example, if the PHR application cooperation code information is read by the imaging unit 37 and the PHR application account cooperation process described later is executed in the management server 10, then on the medical institution terminal 30A, Figure 15 The display of the PHR collaboration notification information display screen on the right side changes.

[0182] This screen displays, for example, information related to the medical institution sharing PHR data (e.g., medical institution name) and information related to the patient (e.g., user name, birthday, etc.) as pairs of PHR collaboration notification information. Furthermore, the PHR application sharing PHR data is displayed between the medical institution information and the patient information. Furthermore, this screen displays an icon indicating that the ASD diagnostic application has re-collaborated.

[0183] It should be noted that, if the PHR application account cooperation process is executed, PHR cooperation notification information may also be displayed on the subject terminal 20A.

[0184] After the ASD diagnosis application is coordinated with the user UA, for example, if the medical institution terminal 30A Figure 16 If you tap the function button HM1 on the main menu screen on the left, the medical institution terminal 30A will Figure 16 The display of the central PHR data reference request screen changes.

[0185] The screen displays a user information input area HR1 for narrowing down users who browse PHR data, and a PHR data reference user selection area HR2 for displaying a list of users narrowed down based on the input content in the user information input area HR1, displayed below the area.

[0186] For example, if a UA among the users displayed in the PHR data reference user selection area HR2 is selected and the PHR data reference button HR3 is tapped, then on the medical institution terminal 30A, Figure 16 The display of the PHR data display screen on the right changes.

[0187] On this screen, for example, the above-mentioned Figure 13 The same images and annotations on the right are used as PHR data.

[0188] However, it is not necessary to Figure 13 The same display on the right side may be displayed differently on the subject terminal 20 and the medical institution terminal 30 .

[0189] It should be noted that in Figure 14 On the main menu screen of the ASD diagnostic application on the left, if you tap the function button UM2, the same Figure 16 The same PHR data display screen on the right.

[0190] Figure 17 This is another example of a PHR data display screen displayed on the display unit 34 of the medical institution terminal 30. This screen is an example of a screen displayed within a PHR integration application ("PHR Institute App"), which enables PHR data collaboration between any PHR applications and allows for centralized reference to shared PHR data on the PHR platform.

[0191] On this screen, the display unit 34 displays information about the user currently viewing PHR data (e.g., user account ID or username) in the upper portion. Below this information, a list of linked applications is displayed in the left pane. Furthermore, the right pane displays PHR data (in this example, daily weight and body fat percentage) associated with the application selected for viewing PHR data (in this screen, the weight tracking app). If the medication record app is selected from the left pane, information such as the date and time of medication taken, the type and amount of medication, and so on can be displayed as PHR data. If the ASD diagnosis app is selected, information such as the recorded date and activity log can be displayed as PHR data.

[0192] It should be noted that, on the screen of the PHR integrated application, for example, Figure 18 As shown, all PHR data of the linked applications are displayed in a list without selecting a PHR application. This allows the user of the PHR integrated application to directly check the PHR data without selecting a PHR application.

[0193] The PHR integrated application can also be provided as SaaS (Software as a Service), for example. For example, the management server 10 can utilize the PHR integrated application as a web application. Furthermore, for example, the subject terminal 20 can utilize the PHR integrated application.

[0194] It should be noted that by entering information related to the examinee (such as user name or date of birth, etc.) in the PHR integrated application, Figure 16 Similarly, confirm the user account ID and fully browse the coordinated PHR data.

[0195] <Processing> Figures 19 and 20 This is a flowchart showing an example of the flow of processing performed by each device in this embodiment. Figure 19 , examples of processing executed by the control unit 21 of the subject terminal 20A of the user UA, examples of processing executed by the control unit 31 of the medical institution terminal 30X of the medical institution HX, and examples of processing executed by the control unit 11 of the management server 10 are shown in order from the left. Figure 20 An example of processing executed by the control unit 31 of the medical institution terminal 30Y when further cooperating with the medical institution terminal 30Y of the medical institution HY is shown.

[0196] It should be noted that the processing described below is merely an example of processing for implementing the method of the present disclosure and is not limiting.

[0197] In addition, other steps may be added to the processing described below, and some steps may be omitted (deleted) from the processing described below.

[0198] It should be noted that before starting the processing in this flowchart, the user UA and the medical institution HX have registered (created) accounts on the PHR platform, and a PHR application identified by the same PHR application ID (for example, an ASD diagnostic application) has been installed on the subject terminal 20A and the medical institution terminal 30X.

[0199] Below, refer to Figure 19 An example of the flow of processing executed by the control units of the subject terminal 20A, the medical institution terminal 30X, and the management server 10 will be described.

[0200] First, the control unit 21 of the subject terminal 20A executes PHR application coordination code information generation processing based on input to the input / output unit 23 (eg, user input (operation input or voice input by the user, etc.). The same may apply hereinafter). (A110).

[0201] In the PHR application collaboration code information generation process, the control unit 21 of the subject terminal 20A generates, for example, a one-dimensional code or a two-dimensional code based on the PHR application collaboration information, namely, the PHR application collaboration code information. The above-mentioned PHR application collaboration code information includes the user account ID of the subject terminal 20A and the PHR application ID of the PHR application that collaborates with the PHR data.

[0202] A code image such as a one-dimensional code or a two-dimensional code can be a type of code information. It should be noted that information encoded into a code image can also be a type of code information.

[0203] It should be noted that the PHR application collaboration information or the PHR application collaboration code information may also include information for identifying the examinee (eg, the examinee's name, birthday, gender, etc.).

[0204] Then, the control unit 21 of the subject terminal 20A displays and outputs the generated PHR application cooperation code information on the display unit 24 ( A120 ), for example.

[0205] For example, based on the user input, the control unit 31 of the medical institution terminal 30X uses the imaging unit 37 to read the PHR application cooperation code information displayed on the subject terminal 20A ( X110 ).

[0206] Then, the control unit 31 of the medical institution terminal 30X decodes the read PHR application coordination code information and acquires the PHR application coordination information.

[0207] It should be noted that the transfer of PHR application collaboration information is not limited to the method using code images. For example, the control unit 21 of the subject terminal 20A may also transfer the PHR application collaboration information by sending it to the medical institution terminal 30X through P2P communication using short-range wireless communication such as Bluetooth or NFC.

[0208] Alternatively, the control unit 31 of the medical institution terminal 30X may receive the PHR application coordination information by, for example, receiving the user account ID or the PHR application ID displayed on the subject terminal 20A through user input.

[0209] Note that, when the control unit 21 of the subject terminal 20A determines based on the user input that the user agrees to the PHR data collaboration, it may display the PHR application collaboration code information or transmit the PHR application collaboration information.

[0210] Then, the control unit 31 of the medical institution terminal 30X sends PHR application account cooperation request information to the management server 10 (X120). The PHR application account cooperation request information includes the user account ID and PHR application ID based on the PHR application cooperation information, and the medical institution account ID of the medical institution terminal 30X.

[0211] Upon receiving the PHR application account cooperation request information from the medical institution terminal 30X, the control unit 11 of the management server 10 executes a PHR application account cooperation process ( S110 ).

[0212] In the PHR application account collaboration processing, the control unit 11 of the management server 10 determines the user account ID of the collaboration source based on the received PHR application account collaboration request information, and associates the medical institution account ID of the collaboration target and the PHR application ID approved by the subject for collaboration and stores them in the corresponding user account ID of the account ID / PHR application collaboration management data 159.

[0213] It should be noted that, when the subject collaborates with PHR data without limiting the PHR application, for example, the PHR application ID in the PHR application collaboration information may include, for example, all-application permission flag information (e.g., "*") indicating that any application is permitted. The management server 10 may then store the all-application permission flag information in the PHR application ID in the account ID / PHR application collaboration management data 159 and store it in association with the medical institution account ID.

[0214] In addition, the control unit 11 of the management server 10 may also send PHR collaboration notification information indicating that PHR data collaboration has been performed to the subject terminal 20A of the user account ID that has collaborated and / or the medical institution terminal 30X of the medical institution account ID when executing PHR application account collaboration processing.

[0215] If the PHR cooperation notification information is received from the management server 10 , the subject terminal 20A and / or the medical institution terminal 30X may also output (eg, display output) the received PHR cooperation notification information.

[0216] After A120 , the control unit 21 of the subject terminal 20A executes a PHR data acquisition process based on, for example, a user input ( A130 ).

[0217] In the PHR data acquisition process, the control unit 21 of the subject terminal 20A acquires PHR data from, for example, the input / output unit 23 of the subject terminal 20A based on the PHR application processing program 281 .

[0218] It should be noted that PHR data acquisition can also be performed automatically without user input or provided by others. For example, the subject terminal 20A can continuously measure the subject's steps and acquire the measured step data as PHR data. Alternatively, the subject terminal 20A can receive the subject's prescription information from a doctor or pharmacist and acquire the received prescription information as PHR data.

[0219] Then, the control unit 21 of the subject terminal 20A transmits PHR data recording request information including the acquired PHR data, the PHR application ID of the used PHR application, and the user account ID of the subject terminal 20A to the management server 10 ( A140 ).

[0220] If the PHR data recording request information is received from the subject terminal 20A, the control section 11 of the management server 10 executes, for example, a PHR data recording process ( S120 ).

[0221] In the PHR data recording process, the control unit 11 of the management server 10 refers to, for example, the account ID / PHR application collaboration management data 159. Then, based on the PHR data recording request information, for example, the PHR application ID and the PHR data are associated with the PHR data management data (e.g., Figure 9 data shown).

[0222] Note that, in addition to acquiring and storing the PHR data itself, information on the location of the PHR data (URI, etc.) may also be acquired and stored. These processes may be examples of registering data related to the subject's health in a shared system.

[0223] It should be noted that, in the PHR data recording process, the management server 10 may store PHR data without distinguishing each PHR application ID. In other words, the application that acquired PHR data among various PHR applications may be stored in the PHR data management data in an unidentifiable manner.

[0224] After X120 , the control unit 31 of the medical institution terminal 30X transmits PHR data reference request information to the management server 10 based on, for example, user input ( X130 ).

[0225] Here, the PHR data reference request information may also include the following information.

[0226] (A1) The user account ID and medical institution account ID of the subject who is referring to the PHR data, and the PHR application ID corresponding to the referenced PHR data.

[0227] (A2) The user information (e.g., name or date of birth) of the examinee referring to the PHR data, the medical institution account ID, and the PHR application ID corresponding to the PHR data being referred to.

[0228] (A3) The user account ID and medical institution account ID of the examinee referring to the PHR data.

[0229] (A4) The user information of the examinee and the medical institution account ID are referenced in the PHR data.

[0230] Upon receiving the PHR data reference request information from the medical institution terminal 30X, the control unit 11 of the management server 10 executes, for example, a PHR data search process (also referred to as a PHR data identification process) to identify PHR data based on the PHR data reference request information ( S130 ).

[0231] During the PHR data search process, the control unit 11 of the management server 10 refers to, for example, the account ID / PHR application collaboration management data 159 to determine whether the user account ID, the medical institution account ID, and the PHR application ID included in the PHR data reference request information are associated. If the association is determined to be established, the control unit 11 of the management server 10, for example, refers to the PHR data management data to read the PHR data associated with the PHR application ID.

[0232] It should be noted that, during the PHR data search process, for example, when the information (A2) or (A4) described above is included in the PHR data reference request information, the control unit 11 of the management server 10 may also refer to the PHR user account registration data 153 to search for a user account ID that matches the user information of the subject.

[0233] Furthermore, during the PHR data search process, if the information in (A3) or (A4) above is included in the PHR data reference request information, the control unit 11 of the management server 10 may refer to the account ID / PHR application collaboration management data 159, for example, and retrieve, from the PHR data management data, the PHR data corresponding to each PHR application ID associated with the medical institution account ID included in the PHR data reference request information, for the subject's user account ID. This allows PHR data to be transmitted simultaneously for all or any of the PHR applications that collaborate with a particular medical institution on the PHR platform.

[0234] For example, when the control unit 11 of the management server 10 reads the PHR data, it transmits the data to the medical institution terminal 30X ( S140 ).

[0235] Upon receiving the PHR data from the management server 10 , the control unit 31 of the medical institution terminal 30X outputs (for example, displays and outputs on the display unit 34 ) the received PHR data ( X140 ).

[0236] Below, refer to Figure 20 An example of cooperation with the medical institution terminal 30Y will be described.

[0237] The control unit 21 of the subject terminal 20A generates ( A150 ) and displays ( A160 ) PHR application cooperation code information, for example, in the same manner as in steps A110 and A120 .

[0238] The control unit 31 of the medical institution terminal 30Y reads the PHR application coordination information ( Y110 ) in the same manner as in step X110 , and then transmits the PHR application account coordination request information ( Y120 ) to the management server 10 in the same manner as in step X120 .

[0239] Furthermore, the control unit 21 of the subject terminal 20A acquires PHR data ( A170 ) in the same manner as in steps A130 and A140 , for example, and transmits PHR data recording request information to the management server 10 ( A180 ).

[0240] Then, the control unit 11 of the management server 10 executes the PHR data recording process ( S160 ), for example, similarly to the step of S120 .

[0241] The control unit 31 of the medical institution terminal 30Y transmits PHR data reference request information to the management server 10 in the same manner as in the procedure X130 ( Y130 ), for example.

[0242] Upon receiving the PHR data reference request information from the medical institution terminal 30Y, the control unit 11 of the management server 10 executes PHR data recording processing ( S170 ) similarly to step S130 , and transmits PHR data to the medical institution terminal 30Y ( S180 ) similarly to step S140 .

[0243] Upon receiving the PHR data from the management server 10 , the control unit 31 of the medical institution terminal 30Y outputs the PHR data in the same manner as in the step X140 ( Y140 ), for example.

[0244] That is, the subject can provide PHR data acquired by one or more PHR applications to one or more medical institutions.

[0245] It should be noted that the control unit 21 of the subject terminal 20A may also transmit PHR data reference request information to the management server 10 based on, for example, user input. Furthermore, the control unit 11 of the management server 10 may transmit PHR data to the subject terminal 20A based on the received PHR data reference request information. Upon receiving the PHR data from the management server 10, the control unit 21 of the subject terminal 20A may output the received PHR data to the display unit 24.

[0246] In the first embodiment, PHR data is shared by a management server 10 that manages PHR data related to the health of a subject, a plurality of PHR applications for acquiring PHR data and registering it in the management server 10, and a medical institution terminal 30 for viewing the PHR data registered in the management server 10.

[0247] Specifically, if Figure 9 As shown in the above, the collaboration between the user account ID and the medical institution account ID is managed in a corresponding relationship with at least one application. The above-mentioned user account ID is used for the application corresponding to the examinee to access the management server 10, and the above-mentioned medical institution account ID is used for the medical institution terminal 30 to access the management server 10. The PHR data is registered in the management server 10 in a corresponding relationship with the user account ID and the application that obtains the PHR data.

[0248] Then, if Figure 19 and Figure 20 As shown in the above, a reference request for PHR data that has established a correspondence with the medical institution account ID corresponding to the medical institution terminal 30 is received from the medical institution terminal 30, and the data obtained by the application that has established a correspondence with the user account ID and the medical institution account ID is provided to the medical institution terminal 30 of the requesting party.

[0249] <Effects of the First Embodiment> In a first embodiment, a data sharing system (e.g., management server 10) enables sharing of health-related data (e.g., PHR data) between multiple applications (e.g., multiple PHR applications) for acquiring health-related data (e.g., PHR data) and medical institution terminals for viewing health-related data. Furthermore, a first account ID and a second account ID are associated and managed with at least one application. The first account ID is used by the patient to access the data sharing system, while the second account ID is used by users of the medical institution terminals to access the data sharing system. Therefore, based on requests from medical institutions and the managed account IDs, data associated with a specific application can be identified.

[0250] In addition, in the first embodiment, as Figure 7 and Figure 9 As shown in FIG. 1 and FIG. 2 , a plurality of PHR data corresponding to a plurality of applications can be registered in the storage unit 15 of the management server 10 (an example of a storage unit of the data sharing system), and thus various PHR data can be provided to medical institutions.

[0251] In addition, in the first embodiment, as Figure 11 As shown in the example, when multiple applications are running on the subject's terminal, Figure 9 As shown in FIG. 1 , there is no need to set an account in the management server 10 for each PHR application, and user usability for the subject is improved.

[0252] In addition, in the first embodiment, as Figure 9 As shown in FIG. , since a correspondence can be established between multiple PHR applications and the collaboration between user account IDs and medical institution account IDs, data obtained by each of the multiple PHR applications can be managed collectively.

[0253] In addition, in the first embodiment, as Figure 9 As shown in FIG, since a plurality of PHR applications corresponding to a user account ID can be associated with a plurality of medical institution account IDs, each of the plurality of PHR applications can collaborate with a plurality of medical institutions (terminals) to share PHR data.

[0254] In addition, in the first embodiment, as Figure 19 and Figure 20 As shown in the above, by receiving a collaboration request including a user account ID, a medical institution account ID and an application ID of at least one PHR application, and managing the collaboration with the user account ID and the medical institution account ID in association with at least one PHR application according to the collaboration request, it is possible to provide PHR data while managing the collaboration using a PHR application that can obtain PHR data.

[0255] In addition, in the first embodiment, as Figure 19 and Figure 20 As shown in the above, it is possible to provide PHR data obtained by a PHR application that has established a correspondence with the user account ID and the medical institution account ID based on a reference request containing information that can determine the user account ID and the medical institution account ID (not limited to the user account ID and the medical institution account ID themselves, as long as it is information that can determine the user account ID and the medical institution account ID).

[0256] In addition, in the first embodiment, as Figure 30 、 Figure 16 and Figure 19As shown in the figures, based on a reference request for PHR data of an object specified by the identification information (e.g., name) of the examinee, PHR data corresponding to a PHR application is provided. The PHR application is an application of a type that establishes a correspondence with a user account ID and a medical institution account ID. As a result, the medical institution side can request the required PHR data without obtaining and inputting account information, etc. (e.g., the examinee's user account ID or the medical institution account ID), thereby improving the usability for users of the medical institution.

[0257] In addition, in the first embodiment, as Figure 30 、 Figure 16 and Figure 19 As shown in the above, a reference request for PHR data of an object specified by the subject's identification information (such as name) is received, and the PHR data corresponding to the reference request is determined based on the user account ID corresponding to the subject's identification information, the medical institution account ID corresponding to the medical institution terminal 30, and the PHR application that has established a correspondence between the user account ID and the medical institution account ID. Therefore, even if the subject's user account ID is not obtained and input on the medical institution side, the PHR data to be provided can be determined and provided to the medical institution.

[0258] In the first embodiment, as Figure 16 as well as Figure 19 and Figure 20 As shown in the above, it is possible to determine the PHR application that has established a correspondence with the user account ID and the medical institution account ID based on a reference request containing information that can determine the user account ID and the medical institution account ID (not limited to the user account ID and the medical institution account ID themselves, as long as it is information that can determine the user account ID and the medical institution account ID), and provide PHR data obtained by the determined PHR application.

[0259] In addition, in the first embodiment, as Figure 14 and Figure 15 as well as Figure 19 and Figure 20 As shown in the above, it is possible to receive a collaboration request including a user account ID, an application ID, and a medical institution account ID, which is provided from a subject terminal 20 on which a PHR application is installed to a medical institution terminal 30, and to manage the collaboration between the user account ID and the medical institution account ID in a corresponding relationship with the identification information of the PHR application.

[0260] In addition, in the first embodiment, as Figure 14 and Figure 15 as well as Figure 19 and Figure 20As shown in the above, it is possible to receive a collaboration request including a user account ID, an application ID, and a medical institution account ID, which is provided from a subject terminal 20 on which a PHR application is installed to a medical institution terminal 30 based on the consent of the subject or a person related to the subject, and to manage the collaboration between the user account ID and the medical institution account ID in a corresponding relationship with the identification information of the PHR application.

[0261] In addition, in the first embodiment, as Figure 17 As shown in the figures, the medical institution application for browsing PHR data in the medical institution terminal 30 is common to multiple PHR applications. Since the medical institution staff do not need to use a different PHR application for each PHR application of the examinee, the user usability of the medical institution staff is improved.

[0262] <First Modification (1)> In the above-described embodiment, the PHR data is registered in the management server 10 and provided from the management server 10 to the medical institution terminal 30 , but the present invention is not limited thereto.

[0263] For example, the management server 10 may query (inquire) the subject terminal 20 about the PHR data acquired by the subject terminal 20 , and present the PHR data acquired from the subject terminal 20 on the medical institution terminal 30 .

[0264] Specifically, for example Figure 21 As shown, (1) the medical institution server 50 sends the above-mentioned PHR data reference request information to the management server 10, for example, to make a reference request for the PHR data of the subject being examined. (2) The management server 10 queries the subject terminal 20 of the subject being examined for PHR data in accordance with the reference request. (3) The subject terminal 20 sends the PHR data to the management server 10 in accordance with the query. (4) The management server 10 sends the received PHR data to the medical institution terminal 30. For example, (2) may be an example of determining that the control unit of the data sharing system requests the subject's terminal to receive data corresponding to each of a plurality of applications as data related to the subject's health.

[0265] It should be noted that the management server 10 may or may not register the PHR data received from the subject terminal 20 in (3). For example, the management server 10 may temporarily store the PHR data received from the subject terminal 20 in the storage unit 15, but may also delete the PHR data after transmitting the PHR data to the medical institution terminal 30.

[0266] In addition, for example, by registering PHR data from the subject terminal 20 to the management server corresponding to the PHR application, namely the PHR application management server 60, and querying the PHR data registered in the PHR application management server 60 from the management server 10, the PHR data can also be presented at the medical institution terminal 30.

[0267] The PHR application management server 60 stores (also understood as registering) PHR data acquired by the corresponding PHR application. The management server 10 provides functionality for collecting and recording PHR data and coordinating PHR data across various PHR applications (although, in this variation, PHR data registration is not required). The PHR application management server 60 and the management server 10 may be operated by different or the same operator.

[0268] Specifically, for example Figure 22 As shown, (1) the subject terminal 20, for example, sends the above-mentioned PHR data record request information to the PHR application management server 60 corresponding to the PHR application that acquired the PHR data, and makes a record request (registration request) for the PHR data. (2) The PHR application management server 60 registers the received PHR data in accordance with the record request. (3) The medical institution server 50, for example, sends the above-mentioned PHR data reference request information to the management server 10, and makes a reference request for the PHR data of the subject being examined. (4) The management server 10 queries the PHR application management server 60 for PHR data in accordance with the reference request. (5) The PHR application management server 60 sends the PHR data to the management server 10 in accordance with the query. (6) The management server 10 sends the received PHR data to the medical institution terminal 30. For example, (4) may be an example in which the control unit of the data sharing system requests the corresponding application management server for data corresponding to each of a plurality of applications as the determination of data.

[0269] It should be noted that the management server 10 may or may not register the PHR data received from the PHR application management server 60 in (5). For example, the management server 10 may temporarily store the PHR data received from the PHR application management server 60 in the storage unit 15, but may also delete the PHR data after transmitting the PHR data to the medical institution terminal 30.

[0270] It should be noted that, as in (5) and (6), the PHR data may be sent to the medical institution terminal 30 without passing through the management server 10. That is, the management server 10 may request the PHR application management server 60 to directly send the PHR data from the PHR application management server 60 to the medical institution terminal 30. This may be an example of determining the data by which the control unit of the data sharing system requests the corresponding application management server to transmit data corresponding to each of the plurality of applications to the medical institution terminal.

[0271] According to this variation, the control unit of the data sharing system (e.g., the control unit 11 of the management server 10) can request data corresponding to multiple applications (e.g., multiple PHR applications) from the subject's terminal as data related to the subject's health (e.g., PHR data). Furthermore, in this case, the subject terminal 20 corresponding to the subject can acquire multiple types of PHR data (examples of data corresponding to multiple applications), and the data sharing system can request PHR data corresponding to multiple PHR applications (examples of multiple applications) from the subject terminal 20. This eliminates the need to register the subject's health-related data corresponding to each of the multiple applications in the sharing system; instead, the sharing system can query the subject's terminal for the data, thereby providing the data to the medical institution terminal.

[0272] Furthermore, according to this variation, the control unit of the data sharing system (e.g., the control unit 11 of the management server 10) can request data corresponding to each of multiple applications (e.g., multiple PHR applications) from the corresponding application management server 60 as data related to the subject's health (e.g., PHR data). In this case, multiple types of PHR data (examples of data corresponding to multiple applications) can be registered with multiple PHR application management servers 60 (examples of multiple application management servers corresponding to multiple applications), and the data sharing system can request PHR data corresponding to each of the multiple PHR application management servers 60. This eliminates the need to register the subject's health data corresponding to each of the multiple applications in the sharing system; instead, the shared system can query the multiple application management servers for the data, thereby providing the data to the medical institution terminal.

[0273] <First Modification (2)> In the above embodiment, the PHR application coordination code information is transmitted from the subject terminal 20 to the medical institution terminal 30 , but the present invention is not limited thereto. For example, the PHR application coordination code information displayed on the medical institution terminal 30 may be read by the subject terminal 20 .

[0274] Figures 23 and 24This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this modification.

[0275] exist Figure 23 If the function button HM2 is tapped on the main menu screen of the medical institution side ASD diagnosis application of the medical institution terminal 30A on the left, the medical institution terminal 30A will Figure 23 The display of the central PHR application collaboration code information display screen changes.

[0276] On this screen, for example, PHR application cooperation code information and the medical institution name in the PHR application are displayed in a two-dimensional code. For example, the user of the subject terminal 20 can confirm the PHR data sharing destination by confirming the medical institution name.

[0277] exist Figure 23 If the function button UM3 is tapped on the subject-side ASD diagnosis application main menu screen of the subject terminal 20A on the right, the subject terminal 20A will be opened. Figure 24 The display of the PHR application coordination code information reading screen on the left side changes. If the user operates the subject terminal 20A and reads the PHR application coordination code information on the subject terminal 20A according to the guidance information for including the PHR application coordination code information displayed on the medical institution terminal 30 in the preview screen, then on the subject terminal 20A, Figure 24 The display of the central PHR data sharing confirmation screen has changed.

[0278] For example, if the user taps the checkbox UC3 for agreeing to share PHR data with the medical institution HA, the PHR data sharing function button UC4 changes from a grayed-out display mode to a normal display mode, making the action effective. Then, if the PHR data sharing function button UC4 is tapped, the PHR application account cooperation process is executed in the management server 10, and on the subject terminal 20A, Figure 24 The display of the PHR collaboration notification information display screen on the right side changes.

[0279] It should be noted that, if the PHR application account cooperation process is executed, the PHR cooperation notification information may also be displayed on the medical institution terminal 30A.

[0280] Figure 25 This is a flowchart showing an example of the flow of processing performed by each device in this modification. The figure shows, from the left, examples of processing performed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, and the control unit 11 of the management server 10.

[0281] First, the control unit 31 of the medical institution terminal 30X executes a PHR application cooperation code information generation process based on, for example, a user input ( X210 ).

[0282] During the PHR application collaboration code information generation process, the control unit 31 of the medical institution terminal 30X generates, for example, the PHR application collaboration code information, which is a one-dimensional or two-dimensional code based on the PHR application collaboration information. The PHR application collaboration information includes the medical institution account ID of the medical institution terminal 30X and the PHR application ID of the PHR application collaborating with the PHR data. It should be noted that the PHR application collaboration information or the PHR application collaboration code information may also include information identifying the medical institution (e.g., the medical institution name).

[0283] Then, the control unit 31 of the medical institution terminal 30X displays and outputs the generated PHR application cooperation code information on the display unit 34 ( X220 ), for example.

[0284] For example, based on the user input, the control unit 21 of the subject terminal 20A uses the imaging unit 27 to read the PHR application cooperation code information displayed on the medical institution terminal 30X ( A210 ).

[0285] Then, the control unit 21 of the subject terminal 20A decodes the read PHR application coordination code information and acquires the PHR application coordination information.

[0286] Note that the control unit 31 of the medical institution terminal 30X may also perform handover by transmitting PHR application cooperation information to the subject terminal 20A through P2P communication using short-range wireless communication such as Bluetooth or NFC.

[0287] Alternatively, the control unit 21 of the subject terminal 20A may receive the PHR application coordination information by receiving the medical institution account ID or the PHR application ID displayed on the medical institution terminal 30X through user input, for example.

[0288] Then, the control unit 21 of the subject terminal 20A transmits PHR application account cooperation request information including the medical institution account ID and PHR application ID based on the PHR application cooperation information and the user account ID of the subject terminal 20A to the management server 10 ( A220 ).

[0289] Note that, when the control unit 21 of the subject terminal 20A determines based on the user input that the user agrees to the PHR data collaboration, it may transmit the PHR application account collaboration request information to the management server 10 .

[0290] If the PHR application account cooperation request information is received from the subject terminal 20A, the control unit 11 of the management server 10 executes the PHR application account cooperation process (S210). The PHR application account cooperation process may also be performed with, for example, Figure 19 The same process is performed in S110.

[0291] In this modification, if Figure 23 and Figure 24 as well as Figure 25 As shown in the above, it is possible to receive collaboration requests and manage the collaboration between the user account ID and the medical institution account ID by establishing a correspondence with the application ID of the PHR application. The above collaboration request includes the medical institution account ID provided from the medical institution terminal 30 to the subject terminal 20 on which the PHR application is installed, and the user account ID and application ID.

[0292] In addition, in this modification, Figure 23 and Figure 24 as well as Figure 25 As shown in the above, it is possible to receive collaboration requests and manage the collaboration of the user account ID and the medical institution account ID in a corresponding relationship with the application ID of the PHR application. The above collaboration request includes the medical institution account ID, the user account ID and the application ID provided from the medical institution terminal 30 to the subject terminal 20 installed with the PHR application based on the consent of the subject or the subject's related person.

[0293] <First Modification (3)> In the above embodiment, the PHR application cooperation code information is sent from the subject terminal 20 to the medical institution terminal 30, but the present invention is not limited thereto. For example, the PHR application account cooperation process may be executed by selecting a medical institution to share PHR data on the subject terminal 20.

[0294] Figures 26 and 27 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this modification.

[0295] At the subject terminal 20A Figure 26 On the left side ASD diagnosis application main menu screen, if the function button UM3 is tapped, the subject terminal 20A will be Figure 26 The display of the PHR application cooperative medical institution selection screen on the right changes.

[0296] This screen displays a medical institution information input area UR1 for filtering medical institutions that share PHR data. Below this area, a filtered medical institution selection area UR2 is displayed. This area displays a list of medical institutions filtered based on the input to the medical institution information input area UR1. Below this area, for example, a nearby medical institution selection area UR3 is displayed. This area displays a list of medical institutions within a specified distance (e.g., 1 km) from the subject terminal 20A based on the location information of the subject terminal 20A.

[0297] For example, when the subject terminal 20A is inside a medical institution (eg, HA), the medical institution HA may be selectable within the nearby medical institution selection area UR3. A medical institution terminal 30A serving as a cooperative partner may be installed in the medical institution HA.

[0298] For example, if HA among the medical institutions displayed in the screening medical institution selection area UR2 is selected and PHR data sharing target medical institution selection area UR4 is tapped, on the subject terminal 20A, Figure 27 The display of the PHR data sharing confirmation screen on the left changes.

[0299] Then, if the PHR data sharing function button UC4 is tapped, the PHR application account cooperation process is executed in the management server 10, and on the subject terminal 20A, Figure 27 The display of the PHR collaboration notification information display screen on the right side changes.

[0300] Figure 28 This is a flowchart showing an example of the flow of processing performed by each device in this modification. The figure shows, from the left, examples of processing performed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, and the control unit 11 of the management server 10.

[0301] First, the control unit 21 of the subject terminal 20A transmits PHR application cooperation medical institution request information requesting a list of cooperation targets (PHR data sharing targets) to the management server 10 based on user input, for example ( A310 ).

[0302] The PHR application cooperation medical institution request information may also include the following information, for example.

[0303] (B1) User account ID of the subject's terminal 20A.

[0304] (B2) Location information of the subject's terminal 20A.

[0305] (B3) Partial or complete name of the medical institution received through user input.

[0306] (B4) Part or all of the medical institution telephone numbers received through user input.

[0307] (B5) Partial or complete address of medical institution received through user input.

[0308] If the PHR application cooperating medical institution request information is received from the subject terminal 20A, the control section 11 of the management server 10 executes a cooperating medical institution search process ( S310 ).

[0309] In the cooperative medical institution search process, the control unit 11 of the management server 10 refers to the PHR medical institution account registration data 155 and searches for the medical institution account ID based on the received PHR application cooperative medical institution request information, for example.

[0310] It should be noted that during the collaborative medical institution search process, for example, if the information in (B2) above is included in the PHR application collaborative medical institution request information, the control unit 11 of the management server 10 may also search for medical institution account IDs of medical institutions within a predetermined range (e.g., a radius of 1 km) from the location of the subject terminal 20A. In this case, for example, the control unit 11 may request location information from the subject terminal 20A and obtain it from the subject terminal 20A. Alternatively, the control unit 11 may periodically transmit location information from the subject terminal 20A to the management server 10, for example, using the most recent location information of the subject terminal 20A for the search. Furthermore, the control unit 11 of the management server 10 may also use the location information of the subject terminal 20A over a predetermined period of time (e.g., using the average location information of the past predetermined period of time).

[0311] Furthermore, in the collaborative medical institution search process, for example, when any of the information in (B3), (B4), or (B5) above is included in the PHR application collaborative medical institution request information, the control unit 11 of the management server 10 may search for the name or telephone number of the medical institution, or the medical institution account ID of the medical institution that matches the address.

[0312] Then, the control unit 11 of the management server 10 transmits the PHR application cooperating medical institution information, which is a list of medical institution account IDs found in the cooperating medical institution search process, to the subject terminal 20A ( S320 ).

[0313] It should be noted that information such as the name of the medical institution or the location of the medical institution may be associated with the medical institution account ID and included in the PHR application-cooperated medical institution information.

[0314] Upon receiving the PHR application-cooperating medical institution information from the management server 10, the control unit 31 of the medical institution terminal 30X displays the received PHR application-cooperating medical institution information (A320). The control unit 21 of the subject terminal 20A selects the desired medical institution from the PHR application-cooperating medical institution information, for example, based on user input. The control unit 21 of the subject terminal 20A then transmits PHR application account cooperation request information to the management server 10. This PHR application account cooperation request information includes the selected medical institution ID, the PHR application ID, and the user account ID of the subject terminal 20A (A330).

[0315] Thus, even when the subject terminal and the medical institution terminal are not close to each other, the subject can share PHR data with any medical institution.

[0316] <First Modification (4)> In the above embodiment, when a subject whose PHR data is to be referenced is specified on the medical institution terminal 30, the management server 10 determines the subject's user account ID. However, the present invention is not limited to this. For example, the medical institution terminal 30 may search for the user account ID based on the subject's name, date of birth, etc.

[0317] Figure 29 1 is a diagram showing an example of data and the like stored in the storage unit 38 of the medical institution terminal 30 in this modification.

[0318] The storage unit 38 stores, for example, various PHR application processing programs 381A, 381B, 381C, etc. executed as PHR application processing, device identification information 383 (eg, telephone number or IMEI), and PHR application patient identification data 385 .

[0319] The PHR application patient identification data 385 is data that manages (buffers) the binding between the subject's name, date of birth, and other information related to the subject and the subject's user account ID in the PHR platform. Figure 30 An example of this data structure is shown.

[0320] For example, the patient name, user account ID, and other registration information are associated and stored in the PHR application patient identification data 385 .

[0321] The patient name may be, for example, the name of the examinee. It should be noted that the patient name and the name of the examinee registered on the PHR platform may be different names. The patient name is an example of the examinee's identification information.

[0322] The user account ID is, for example, the user account ID of the examinee (patient) who is associated with the medical institution account ID of the medical institution terminal 30 (PHR data linkage is performed) in the PHR application account linkage process.

[0323] For example, various information such as the PHR application ID of the PHR application with which the subject has linked PHR data or the patient's date of birth may be stored in other registration information.

[0324] For example, if the PHR application account cooperation process is executed in the management server 10 and PHR cooperation notification information is received from the management server 10 , the control unit 31 of the medical institution terminal 30 may update and store the PHR application patient identification data 385 .

[0325] By storing the PHR application patient identification data 385 in the medical institution terminal 30 , the user of the medical institution terminal can identify the user account ID of the subject using information different from the identification information of the subject registered in the PHR platform.

[0326] For example, when transmitting the PHR data reference request information, the medical institution terminal 30 may refer to the PHR application patient identification data 385 and identify the user account ID based on the patient name or the like.

[0327] <Second embodiment> The second embodiment is an embodiment related to linking a PHR platform service deployed on a global network such as the Internet and an electronic medical record service deployed on a private network such as a corporate intranet.

[0328] The contents described in the second embodiment are also applicable to any of the other embodiments or other modified examples.

[0329] System Structure Figure 31 1B is a diagram showing an example of the system configuration of an information system 1B according to this embodiment.

[0330] In information system 1B, network 40 is divided into a wide area communication network 40A such as the Internet and a closed area communication network 40B such as an intranet. Wide area communication network 40A may also be called an open network or a global network. Closed area communication network 40B may also be called a closed network or a private network.

[0331] The closed communication network 40B is a network composed of, for example, a VPN or dedicated lines. Unlike the Internet, it is a network accessible only to specific individuals or locations. By utilizing the closed network, users (e.g., medical institutions) can prevent attacks from third parties outside the closed network and safely utilize systems within the closed communication network 40B.

[0332] In information system 1B, for example, a management server 10, one or more subject terminals 20, and one or more medical institution terminals 30 are connected via a wide area communication network 40A. Furthermore, in information system 1B, for example, a medical institution server 50 and one or more medical institution terminals 30 are connected via a closed area communication network 40B.

[0333] The medical institution server 50 is, for example, an information processing device owned by a practitioner using an EMR application, and has a function of providing, for example, electronic medical record services to the medical institution terminal 30 via the closed area communication network 40B. The medical institution server 50 may be a single server or multiple servers.

[0334] It should be noted that the hardware structure of the medical institution server 50 may be the same as that of the management server 10 , for example.

[0335] The medical institution terminal 30 includes, for example, a PHR application processing unit 311 and an EMR application processing unit 313 as a control unit 31. Furthermore, the medical institution terminal 30 includes, for example, a wide area network communication unit 32A for communicating with the wide area communication network 40A and a closed area network communication unit 32B for communicating with the closed area communication network 40B as a communication unit 32.

[0336] For example, the PHR application processing unit 311 can use the wide area network communication unit 32A. Also, for example, the EMR application processing unit 313 can use the closed area network communication unit 32B. It should be noted that the PHR application processing unit 311 can also use the closed area network communication unit 32B.

[0337] Figure 32 1 is a diagram showing an example of functions implemented by the control unit 51 of the medical institution server 50 in this embodiment.

[0338] The control unit 51 includes, for example, a PHR / EMR collaboration processing unit 511 as a functional unit that executes PHR / EMR account collaboration processing (also referred to as PHR application management assistance processing) based on a PHR / EMR collaboration processing program 551 stored in the storage unit 55. Furthermore, the control unit 51 includes, for example, an EMR application management processing unit 513 that executes EMR application management processing based on an EMR application management processing program 553 stored in the storage unit 55.

[0339] Figure 331 is a diagram showing an example of information stored in the storage unit 55 of the medical institution server 50 in this embodiment.

[0340] The storage unit 55 stores, for example, a PHR / EMR collaboration processing program 551 , an EMR application management processing program 553 , EMR account registration data 555 , an EMR patient information database 557 , and PHR / EMR related registration data 559 .

[0341] The EMR account registration data 555 is registration data related to the patient (subject) account of a medical institution using the EMR application. Figure 34 An example of this data structure is shown.

[0342] For example, the patient name, EMRID, and other registration information are associated and stored in the EMR account registration data 555 .

[0343] The patient name is, for example, the name of a patient receiving medical treatment at a medical institution using the EMR application. Note that, for the same examinee, the patient name and the user name in the PHR application may be the same or different.

[0344] EMRID is information for identifying a patient's account number in an EMR application. This EMRID is preferably a unique value for each account number, and is set and stored by the medical institution server 50, for example, as a unique value for each account number (unique value).

[0345] EMRID may be information associated with the medical institution terminal 30 or the medical institution of the medical institution terminal 30. In addition, EMRID may be a third account ID.

[0346] For example, various basic information such as the patient's address, date of birth, and gender may be stored in other registration information.

[0347] The EMR patient information database 557 is a database for managing information related to a patient's medical information in a medical institution, for example. Figure 35 An example of this data structure is the EMR patient information database 557A.

[0348] For example, the EMR patient information management data is stored in the EMR patient information database 557A as management data for each EMRID.

[0349] For example, EMRID and EMR data are associated and stored in each EMR patient information management data.

[0350] Various medical information of patients identified by EMRID may also be stored in the EMR data.

[0351] The PHR / EMR association registration data 559 is used to manage the correspondence between the user account ID in the PHR platform and the EMRID in the EMR service. Figure 36 An example of this data structure is PHR / EMR-related registration data 559A.

[0352] For example, the user account ID, EMRID, and the coordinated application ID are associated and stored in the PHR / EMR associated registration data 559A.

[0353] The PHR application ID of the PHR application in which the subject and the medical institution have collaborated may be stored in the application ID after collaboration.

[0354] It should be noted that the application ID after collaboration can also be obtained by, for example, querying the management server 10 based on the user account ID and the medical institution account ID through the medical institution terminal 30 or the medical institution server 50. Furthermore, if the subject collaborates with all applications on the PHR platform, all application permission flag information can be stored in the application ID after collaboration, or the storage item for the application ID after collaboration can be omitted.

[0355] <Display screen> In this example, the name of the EMR application used by a medical institution is expressed as "EHR / EMR App".

[0356] Figures 37 and 38 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this embodiment.

[0357] Figure 37 The left side shows the PHR application cooperation code information display screen displayed on the subject terminal 20A by agreeing to share PHR data on the PHR data sharing confirmation screen. Figure 37 The PHR application cooperation code information is read on the central PHR application cooperation code information reading screen, and the PHR application account cooperation process is executed in the management server 10. Then, on the medical institution terminal 30A, Figure 37 The display of the electronic medical record collaboration confirmation screen on the right changes.

[0358] This screen displays, for example, information regarding a patient with whom the PHR application is being linked, transmitted via the medical institution terminal 30X to the medical institution server 50, confirming whether the medical institution server 50 is linking the EMRIDs and user account IDs of patients with the same name, surname, and birthdate, selected from the registered EMR account registration data 555. Furthermore, function buttons MB1 and MB2 are displayed below the screen, for example: the function button MB1 is used to manually specify a linking target EMRID; the function button MB2 is used to link an EMRID automatically selected from the EMR account registration data 555.

[0359] For example, if the user taps the function button MB1, on the medical institution terminal 30A, Figure 38 The display of the collaboration target EMRID input screen changes.

[0360] On this screen, the user account ID and medical institution account ID that were linked in the PHR application account linking process are automatically entered in the linking target EMRID input area ARR and are grayed out so that they cannot be changed.

[0361] Furthermore, a text box for manually inputting EMRID and a function button MB3 for inquiring the medical institution server 50 based on patient information such as a patient name and inputting EMRID are displayed below it.

[0362] If EMRID is input in the text box and the function button MB4 for binding the input EMRID with the user account ID displayed in the cooperation target EMRID input area ARR is touched, the PHR / EMR account cooperation process described later is executed in the medical institution server 50. Thus, for example, on the medical institution terminal 30A, Figure 38 The display of the central EMR collaboration notification information display screen has changed.

[0363] On this screen, as EMR linkage notification information, for example, information on a subject who has shared PHR data and linked with an electronic medical record and patient information on the linked electronic medical record are displayed in pairs.

[0364] In addition, if the PHR / EMR account cooperation process described later is executed in the medical institution server 50, for example, on the subject terminal 20A, Figure 38 The display of the EMR collaboration notification information display screen on the right side changes.

[0365] On this screen, a medical record icon is displayed, indicating that the medical institution HA has linked with the electronic medical record. However, the EMRID or the patient's name on the medical record is not displayed.

[0366] Therefore, even if the name or gender on the electronic medical record is different from the name or gender that the examinee recognizes and registers in the PHR application, it is possible to avoid hiding the registration information on the electronic medical record from the examinee, thereby avoiding causing unnecessary panic in the examinee.

[0367] Figure 39 This is an example of the EMR data display screen when using the EMR application and referencing the linked PHR data.

[0368] On this screen, information about the patient whose EMR data is being viewed (e.g., patient name, EMRID, etc.) is displayed in the upper portion of the display unit 34. Below this, for example, a chief complaint record area or a prescription record area is displayed in the left pane, and an examination result record area is displayed in the right pane.

[0369] For example, because the user UA and the medical institution HA make the ASD diagnosis application and the medication record application work together, a “Confirm Medication Record” function button for referring to PHR data in the medication record application is displayed in the prescription record area.

[0370] In addition, the PHR data in the ASD diagnosis application is displayed synchronously in the examination result record area.

[0371] Note that, for example, instead of displaying the PHR data on the EMR data, a URI for referencing the PHR data may be displayed. Then, for example, by tapping the URI, the medical institution terminal 30X can also refer to the PHR data based on the URI from the management server 10 .

[0372] <Processing> Figures 40 and 41 This is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The figure shows, from the left, examples of processing executed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0373] It should be noted that before starting the process in this flowchart, the user UA and the medical institution HX have already registered (created) accounts on the PHR platform, and a PHR application (e.g., an ASD diagnostic application) identified by the same PHR application ID has been installed on the patient terminal 20A and the medical institution terminal 30X. Furthermore, an EMRID for storing the patient information of the user UA has been allocated to the medical institution server 50.

[0374] Below, refer to Figure 40 Provide explanation.

[0375] For example, if the control unit 31 of the medical institution terminal 30X sends PHR application account collaboration request information (X120) to the management server 10, it sends PHR / EMR account collaboration request information to the medical institution server 50. The PHR / EMR account collaboration request information includes the user account ID and PHR application ID based on the PHR application collaboration information, and the EMRID (X410) corresponding to the user of the subject terminal 20A.

[0376] The transmission of the PHR / EMR account coordination request information may also be executed in the PHR application processing unit 311. Alternatively, the transmission of the PHR / EMR account coordination request information may also be executed in the EMR application processing unit 313 using a plug-in in the EMR application.

[0377] It should be noted that the control unit 31 of the medical institution terminal 30X may also transmit the PHR / EMR account cooperation request information upon receiving the PHR cooperation notification information from the management server 10 .

[0378] Furthermore, when transmitting the PHR / EMR account collaboration request information, the control unit 31 of the medical institution terminal 30X may also transmit EMR collaboration notification information to the management server 10, indicating that the PHR data has collaborated with the EMR application. Upon receiving the EMR collaboration notification information, the control unit 11 of the management server 10 may also, based on the medical institution account ID, user account ID, and PHR application ID included in the EMR collaboration notification information, add and store EMR collaboration flag information, for example, to the medical institution account ID in the account ID / PHR application collaboration management data 159.

[0379] Alternatively, information that can identify the EMRID (eg, patient name or date of birth) may be included in the PHR / EMR account coordination request information instead of the EMRID itself. The PHR / EMR account coordination request information may not include the PHR application ID.

[0380] Upon receiving the PHR / EMR account collaboration request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes a PHR / EMR account collaboration process ( M410 ).

[0381] During the PHR / EMR account collaboration process, for example, the PHR / EMR collaboration processing unit 511 adds a record to the PHR / EMR associated registration data 559 based on the PHR / EMR account collaboration request information, and stores the record by associating the user account ID with the EMRID. It should be noted that the PHR / EMR collaboration processing unit 511 may also store the PHR application ID that was associated with the application ID after the collaboration.

[0382] It should be noted that, upon receiving the PHR / EMR account collaboration request information, the PHR / EMR collaboration processing unit 511 may also determine the EMRID based on the information capable of identifying the EMRID and then perform the PHR / EMR account collaboration processing.

[0383] Furthermore, for example, when the PHR / EMR account linkage process is executed, the control unit 51 of the medical institution server 50 may transmit EMR linkage notification information indicating that the PHR data and EMR data are linked to each other to the medical institution terminal 30X.

[0384] If the EMR cooperation notification information is received from the medical institution server 50, the medical institution terminal 30X may also output (for example, display output) the received EMR cooperation notification information (see Figure 38 Center). Then, the control unit 31 of the medical institution terminal 30X may also send EMR cooperation notification information to the subject terminal 20A via the management server 10. If the EMR cooperation notification information is received from the management server 10, the control unit 21 of the subject terminal 20A may also output (for example, display output) the received EMR cooperation notification information (see Figure 38 on the right).

[0385] Below, refer to Figure 41 Provide explanation.

[0386] When the control unit 11 of the management server 10 executes the PHR data recording process ( S120 ), the control unit 11 of the management server 10 sends PHR data update notification information to the medical institution terminal 30 of each medical institution account ID associated with the PHR application ID corresponding to the updated PHR data in the user account ID of the user whose PHR data is updated, for example, by referring to the account ID / PHR application collaboration management data 159 ( S410 ).

[0387] It should be noted that the control unit 11 of the management server 10 may also send the PHR data update notification information to the medical institution terminal 30 having the medical institution account ID to which the EMR cooperation flag information is added in the account ID / PHR application cooperation management data 159 .

[0388] In addition, the PHR data update notification information may include the user account ID and PHR application ID of the user whose PHR data is updated, and may also include the updated PHR data.

[0389] Furthermore, the PHR data update notification information may include a URI for referencing the updated PHR data. The URI may also include an access token that can reference PHR data updated within a predetermined period on the PHR platform.

[0390] Upon receiving the PHR data update notification information from the management server 10 , the control unit 31 of the medical institution terminal 30X transmits, for example, PHR data reference request information to the management server 10 ( X130 ).

[0391] It should be noted that, upon receiving the PHR data update notification information, the control unit 31 of the medical institution terminal 30X may display and output it on the display unit 34. Furthermore, the control unit 31 of the medical institution terminal 30X may send PHR data reference request information to the management server 10 based on user input.

[0392] Furthermore, upon receiving the PHR data update notification information, the control unit 31 of the medical institution terminal 30X may automatically transmit PHR data reference request information to the management server 10 based on the received PHR data update notification information.

[0393] Upon receiving the PHR data from the management server 10 , the control unit 31 of the medical institution terminal 30X transmits EMR data update request information to the medical institution server 50 , for example ( X420 ).

[0394] The EMR data update request message may also include PHR data and user account ID. The EMR data update request message may also include PHR application ID.

[0395] It should be noted that the EMR data update request information may include a URI for referencing the updated PHR data.

[0396] Upon receiving the EMR data update request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes, for example, an EMR data update process ( M420 ). The EMR data update process may also be referred to as a process of registering PHR data in the EMR data.

[0397] During the EMR data update process, for example, the control unit 51 of the medical institution server 50 refers to the PHR / EMR association registration data 559 to retrieve the EMRID corresponding to the user account ID included in the EMR data update request information. The control unit 51 of the medical institution server 50 then, for example, adds the PHR data to the EMR data in the EMR patient information database 557 using the retrieved EMRID. It should be noted that the control unit 51 of the medical institution server 50 may also add and store a URI for referencing the updated PHR data in the EMR data.

[0398] For example, the control unit 31 of the medical institution terminal 30X transmits EMR data reference request information to the medical institution server 50 based on user input (X430). For example, the EMR data reference request information may include the EMRID of the patient whose EMR data is to be referenced. It should be noted that the EMR data reference request information may also include information that can identify the EMRID of the patient whose EMR data is to be referenced (e.g., the patient's name, date of birth, user account ID, etc.).

[0399] Upon receiving the EMR data reference request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes an EMR data search process ( M430 ).

[0400] In the EMR data search process, the control unit 51 of the medical institution server 50 refers to the EMR patient information database 557 based on the EMRID included in the EMR data reference request information, and reads the EMR data from the EMR patient information management data specified by the EMRID.

[0401] Note that, in the EMR data search process, the control unit 51 of the medical institution server 50 may refer to the EMR account registration data 555 or the PHR / EMR associated registration data 559 and identify the EMRID based on information that can identify the EMRID.

[0402] Then, the control unit 51 of the medical institution server 50 transmits the read EHR data to the medical institution terminal 30X ( M440 ).

[0403] Upon receiving the EMR data from the medical institution server 50 , the control unit 31 of the medical institution terminal 30X displays and outputs the received EMR data on the display unit 34 , for example ( X440 ).

[0404] Note that, when the received EMR data includes a URI for referencing PHR data, the control unit 31 of the medical institution terminal 30X may receive the PHR data from the management server 10 based on the URI and display and output the received PHR data.

[0405] <Effects of the Second Embodiment> In the second embodiment, as Figure 36 、 Figure 40 and Figure 41 as well as Figure 37 and Figure 38 As shown in FIG. 1 , in the medical institution terminal 30 and the medical institution server 50 that provides electronic medical record information, the EMRID, which is identification information of the examinee in the medical institution server 50 , and the user account ID can be associated and managed.

[0406] In addition, in the second embodiment, as Figure 36 、 Figure 40 and Figure 41 as well as Figure 37 and Figure 38 As shown in the figures, in the medical institution terminal 30 and the medical institution server 50 that provides electronic medical record information, the identification information of the examinee in the medical institution server 50, namely, EMRID and the user account ID can be associated and managed. In addition to the management server 10, the examinee's PHR application, and the medical institution terminal 30, the PHR data related to the examinee's health can also be shared in the medical institution server 50.

[0407] In addition, in the second embodiment, as Figure 36 、 Figure 40 and Figure 41 as well as Figures 37 to 39 As shown in the figures, in the medical institution terminal 30 and the medical institution server 50 that provides electronic medical record information, the identification information of the subject in the medical institution server 50, namely, the EMRID, and the user account ID can be associated and managed, and the PHR data corresponding to the user account ID and / or the information associated with the PHR data can be associated with the EMRID and registered in the medical institution server 50, and according to the provision request of the EMRID-based EMR data from the medical institution terminal 30, the EMR data and the PHR data and / or the information associated with the PHR data can be provided to the medical institution terminal 30.

[0408] In the above embodiment, the PHR data is registered in the management server 10 , the PHR data is provided from the management server 10 to the medical institution terminal 30 , and the EMR data is updated, but the present invention is not limited thereto.

[0409] For example, the PHR data may be registered from the subject terminal 20 in the PHR application management server 60, which is a management server corresponding to the PHR application. The management server 10 may then query the PHR application management server 60. The management server 10 may then obtain the PHR data registered in the PHR application management server 60 and transmit the obtained PHR data to the medical institution server 50 and the medical institution terminal 30. It should be noted that the medical institution terminal 30 may also receive the PHR data via the medical institution server 50. The medical institution server 50 may also update the EMR data based on the received PHR data.

[0410] Alternatively, the PHR data may be transmitted to the medical institution terminal 30 without passing through either the management server 10 or the medical institution server 50. Specifically, the management server 10 may request the PHR application management server 60 to transmit the PHR data directly to the medical institution terminal 30. Upon receiving the request, the PHR application management server 60 may also transmit the PHR data directly to the medical institution terminal 30. It should be noted that the PHR application management server 60 may transmit the PHR data to the medical institution server 50, and the medical institution server 50 may update the EMR data based on the received PHR data.

[0411] It should be noted that, for example, the management server 10 may query the subject terminal 20 for the PHR data acquired by the subject terminal 20, and transmit the PHR data acquired from the subject terminal 20 to the medical institution terminal 30. Alternatively, the management server 10 may transmit the PHR data to the medical institution server 50, and the medical institution server 50 may update the EMR data based on the received PHR data.

[0412] <Second Modification (1)> In the above embodiment, the PHR application coordination code information is transmitted from the subject terminal 20 to the medical institution terminal 30 , but the present invention is not limited thereto. For example, the PHR application coordination code information displayed on the medical institution terminal 30 may be read by the subject terminal 20 .

[0413] Figures 42 and 43 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this modification.

[0414] For example, at the medical institution terminal 30A Figure 23 If the function button HM2 is tapped on the left medical institution side ASD diagnosis application main menu screen, the medical institution terminal 30A will Figure 42 The display of the PHR application collaboration code information display screen on the left side changes.

[0415] On this screen, for example, in addition to the PHR application collaboration code information and the medical institution name in the PHR application represented by a QR code, an EMRID token is also displayed.

[0416] The EMRID token is, for example, a token (eg, character string information) included in the PHR application cooperation code information, and relates to the EMRID on the electronic medical record corresponding to the subject of the subject terminal 20A.

[0417] By using the EMRID token, the user of the medical institution terminal 30A can reliably hand over the EMRID that matches the user of the subject terminal 20A.

[0418] It should be noted that, when a validity period or expiration date is set for the EMRID token, the validity period or expiration date of the EMRID token may be displayed on the PHR application cooperation code information display screen.

[0419] For example, in the subject terminal 20A Figure 23 On the right side ASD diagnosis application main menu screen, if the function button UM3 is tapped, the subject terminal 20A will be Figure 42 The display of the PHR application cooperation code information reading screen at the center changes. If the PHR application cooperation code information is read on the medical institution terminal 30A, then on the subject terminal 20A, Figure 42 The display of the PHR data sharing confirmation screen on the right changes.

[0420] On this screen, for example, it is displayed in the note column that PHR data is coordinated with EMR data based on the EMRID token being embedded in the PHR application coordination code information.

[0421] For example, if the user taps the PHR data sharing function button UC4, the PHR application account cooperation process is executed in the management server 10. Then, on the medical institution terminal 30A, Figure 43 The display of the PHR collaboration notification information display screen on the left side changes.

[0422] Displayed on this screen are a function button MB5 for cooperating with EMRID based on the EMRID token and a function button MB6 for cooperating only with PHR data without cooperating with the electronic medical record.

[0423] For example, if the user taps the function button MB5, the PHR / EMR account cooperation process is executed in the medical institution server 50, and the medical institution terminal 30A receives the PHR / EMR account information. Figure 43 The display of the central EMR collaboration notification information display screen has changed.

[0424] This screen shows that the user account ID and the EMRID account have been automatically linked based on the EMRID token.

[0425] In addition, for example, if the PHR / EMR account cooperation process is executed by the medical institution server 50, on the subject terminal 20A, Figure 43 The display of the EMR collaboration notification information display screen on the right side changes.

[0426] It should be noted that, unlike this example, the PHR / EMR account linkage process may be executed by manually inputting the EMRID on the medical institution terminal 30A without using the EMRID token.

[0427] Figure 44 This is a flowchart showing an example of the flow of processing performed by each device in this modification. The figure shows, from the left, examples of processing performed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0428] First, the control unit 31 of the medical institution terminal 30X executes a PHR application cooperation code information generation process based on, for example, a user input ( X210 ).

[0429] In the PHR application coordination code information generation process, the control unit 31 of the medical institution terminal 30X transmits, for example, EMRID token request information including the EMRID of the patient corresponding to the user of the subject terminal 20 presenting the PHR application coordination code information to the medical institution server 50 .

[0430] Upon receiving the EMRID token request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes, for example, a PHR application cooperation token generation process ( M510 ).

[0431] During the PHR application collaboration token generation process, the control unit 51 of the medical institution server 50 generates a token based on the received EMRID, for example. The control unit 51 of the medical institution server 50 then associates the generated token with the EMRID and stores it in the storage unit 55. It should be noted that the token may also be given an expiration date or validity period.

[0432] Then, the control unit 51 of the medical institution server 50 transmits EMRID token information including the generated token to the medical institution terminal 30X.

[0433] Upon receiving the EMRID token information from the medical institution server 50 , the control unit 31 of the medical institution terminal 30X generates PHR application coordination code information based on the PHR application coordination information including the token, for example, and displays and outputs the information ( X220 ).

[0434] It should be noted that the PHR application collaboration information or the PHR application collaboration code information may also include an EMRID instead of a token. In addition, the PHR application collaboration information or the PHR application collaboration code information may not include an EMRID or a token related to the EMRID.

[0435] The control unit 21 of the subject terminal 20A reads the PHR application coordination code information displayed on the medical institution terminal 30X using, for example, the imaging unit 27 , and acquires the PHR application coordination information ( A210 ).

[0436] Then, the control unit 21 of the subject terminal 20A transmits PHR application account cooperation request information including the medical institution account ID, PHR application ID, user account ID of the subject terminal 20A, and token or EMRID to the management server 10 ( A510 ).

[0437] Upon receiving the PHR application account cooperation request information from the subject terminal 20A, the control unit 11 of the management server 10 executes a PHR application account cooperation process ( S210 ).

[0438] The control unit 11 of the management server 10 then transmits PHR collaboration notification information to the medical institution terminal 30X (S510). If the PHR application account collaboration request information includes a token or EMRID, the control unit 11 of the management server 10 transmits the PHR collaboration notification information including the token or EMRID to the medical institution terminal 30X. Because the management server 10 cannot decrypt the token, using the token prevents the patient's EMRID from being leaked to the outside.

[0439] Then, the control unit 31 of the medical institution terminal 30X sends PHR / EMR account collaboration request information to the medical institution server 50, for example. The PHR / EMR account collaboration request information includes the user account ID and PHR application ID based on the PHR collaboration notification information, and the EMRID or token (X510) corresponding to the user of the subject terminal 20A.

[0440] Note that, when the PHR collaboration notification information does not include the EMRID or token, the control unit 31 of the medical institution terminal 30X may acquire the EMRID corresponding to the user of the subject terminal 20A or information capable of identifying the EMRID based on user input, for example.

[0441] Upon receiving the PHR / EMR account collaboration request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes, for example, a PHR / EMR account search process ( M520 ).

[0442] During the PHR / EMR account search process, the control unit 51 of the medical institution server 50 searches for the EMRID corresponding to the token included in the PHR / EMR account collaboration request information, for example, by referring to the token and EMRID stored during the PHR application collaboration token generation process. If the EMRID is found, the control unit 51 of the medical institution server 50 may delete the found EMRID and token from the storage unit 55.

[0443] It should be noted that, when the PHR / EMR account collaboration request information includes EMRID, the control unit 51 of the medical institution server 50 does not have to execute the PHR / EMR account search process.

[0444] <Second Modification (2)> In the above embodiment, the PHR application cooperation code information is sent from the subject terminal 20 to the medical institution terminal 30, but the present invention is not limited thereto. For example, the subject terminal 20 may select a medical institution to share PHR data to execute PHR application account cooperation processing.

[0445] Figure 45 3 is a diagram showing an example of a screen displayed on the display unit 34 of the medical institution terminal 30A in this modification.

[0446] For example, if with Figures 26 and 27 Similarly, when a medical institution to be cooperated is selected on the subject terminal 20 and the PHR application account cooperation process is executed in the management server 10, the medical institution terminal 30A is displayed. Figure 45 The PHR collaboration notification information display screen on the left.

[0447] On this screen, if the user taps the function button MB5, for example, on the medical institution terminal 30A, Figure 45 The display of the central collaboration target EMRID input screen changes.

[0448] Then, if the function button MB9 for binding the input EMRID with the user account ID displayed in the cooperation target EMRID input area ARR is touched, the PHR / EMR account cooperation process is executed in the medical institution server 50. For example, on the medical institution terminal 30A, Figure 45 The display of the EMR collaboration notification information display screen on the right side changes.

[0449] Figure 46 This is a flowchart showing an example of the flow of processing performed by each device in this modification. The figure shows, from the left, examples of processing performed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0450] For example, when executing the PHR application account cooperation process ( S210 ), the control unit 11 of the management server 10 transmits PHR cooperation notification information to the medical institution terminal 30X ( S510 ).

[0451] The PHR collaboration notification information may include, for example, the user account ID and the PHR application ID of the subject terminal 20A that has collaborated with the PHR data.

[0452] Upon receiving the PHR coordination notification information from the management server 10, the control unit 31 of the medical institution terminal 30X displays the received PHR coordination notification information on the display unit 34. The control unit 31 of the medical institution terminal 30X then executes an EMRID acquisition process (X550).

[0453] In the EMRID acquisition process, the control unit 31 of the medical institution terminal 30X receives the EMRID corresponding to the user of the subject terminal 20A or information capable of identifying the EMRID, for example, based on user input.

[0454] Then, the control unit 31 of the medical institution terminal 30X transmits PHR / EMR account cooperation request information including the acquired EMRID or information capable of identifying the EMRID to the management server 10 ( X410 ).

[0455] <Second Modification (3)> In the above embodiment, the collaboration with the PHR platform is performed without expanding the data related to the EMR service, but the present invention is not limited thereto. For example, the collaboration with the PHR platform can also be performed by expanding the EMR patient information management database 557B.

[0456] Figure 47 Another example of the data structure of the EMR patient information database 557 is the EMR patient information management database 557B.

[0457] For example, the EMR patient information management data is stored in the EMR patient information management database 557B as management data for each EMRID.

[0458] For example, the EMRID, user account ID, EMR data, and PHR data management data are associated and stored in each EMR patient information management data.

[0459] It should be noted that the PHR / EMR-related registration data 559 may not be used.

[0460] Furthermore, for example, when an API with the PHR application is implemented in the EMR application management processing program 553 , the PHR / EMR cooperation processing program 551 may not be used.

[0461] For example, the control unit 51 of the medical institution server 50 may store the EMRID and the user account ID in association with the EMR patient information management data during the PHR / EMR account linkage process.

[0462] Furthermore, the control unit 51 of the medical institution server 50 may store the PHR data in the EMR data update request information in association with the PHR data management data of the EMR patient information management data, for example, during the EMR data update process.

[0463] <Third embodiment> The third embodiment relates to a situation where a patient is registered as a patient in a medical institution's electronic medical record system, but not as a user of the PHR platform. This embodiment can also be described as an embodiment where a medical practitioner at a medical institution distributes a PHR application to the patient.

[0464] The contents described in the third embodiment can also be applied to any of the other embodiments or other modified examples.

[0465] <Display screen> Figures 48 and 49 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this embodiment.

[0466] At the medical institution terminal 30A Figure 48 On the main menu screen of the medical institution side ASD diagnosis application on the left, for example, if the user taps the function button HM3, then on the medical institution terminal 30A, Figure 48 The display of the central PHR application user account creation request information display screen has changed.

[0467] This screen displays, for example, PHR application user account creation request information represented by a QR code, the name of the PHR application that the user of the subject terminal 20A is urged to install contained in the PHR application user account creation request information before encoding, and the name of the medical institution using the medical institution terminal 30A.

[0468] For example, if the camera application is started based on the user input of the subject terminal 20A, on the subject terminal 20A, Figure 48 The camera preview screen on the right side changes its display. For example, a QR code containing PHR application user account creation request information is projected onto the preview screen of the image captured by the camera unit 37. The QR code is decoded, and a link to the URI contained in the decoded information, i.e., an "Install App" button, is displayed.

[0469] If the user taps the “Install Application” button, for example, the application specified in the PHR application user account creation request information (in this example, the ASD diagnostic application) is installed on the subject terminal 20A.

[0470] Figure 49 The left side is an example of a PHR platform user registration screen in the ASD diagnostic application that is displayed after the application is installed on the subject terminal 20A.

[0471] On this screen, for example, a text box for entering a username and password is displayed within the PHR platform user registration information input area (URR). Below this area, a medical institution account ID is automatically entered based on the PHR application user account creation request information and is grayed out to indicate that it cannot be changed. This medical institution account ID is linked to the user account ID created based on the information entered in the text box.

[0472] It should be noted that various user information such as birthday or gender can also be entered in the PHR platform user registration information input area URR.

[0473] If the user enters a user name and password in the text box and taps the account creation function button CB for creating a PHR platform user account, a user account ID is assigned to the user of the subject terminal 20A in the management server 10 and the PHR medical institution account registration data 155 is updated.

[0474] Then, for example, on the subject terminal 20A, Figure 49 The display of the central PHR data sharing confirmation screen has changed.

[0475] On this screen, for example, based on the EMRID token being embedded in the PHR application user account creation delegation information, it is displayed in the note column that the PHR data and the EMR data are linked.

[0476] For example, if the user taps the PHR data sharing function button UC4, the PHR application account cooperation process is executed in the management server 10, and the PHR / EMR account cooperation process is executed in the medical institution server 50. Then, the medical institution terminal 30A displays Figure 49 The EMR collaboration notification information display screen on the right.

[0477] It should be noted that, unlike this example, user account registration with the PHR platform can also be performed in a PHR integrated application or a web application of a PHR platform service provided as SaaS.

[0478] <Processing> Figure 50 This is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The figure shows, from the left, examples of processing executed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0479] It should be noted that before starting the process in this flowchart, the medical institution HX has already registered (created) an account on the PHR platform and installed a PHR application (e.g., an ASD diagnostic application) identified by a predetermined PHR application ID on the medical institution terminal 30X. Furthermore, an EMRID for storing patient information of the user UA is allocated to the medical institution server 50.

[0480] First, the control unit 31 of the medical institution terminal 30X executes a PHR application user account creation request information generation process based on, for example, a user input ( X610 ).

[0481] In the PHR application user account creation entrustment information generation process, the control unit 31 of the medical institution terminal 30X generates, for example, PHR application user account creation entrustment information, which includes the medical institution account ID of the medical institution terminal 30X and the PHR application ID of the PHR application requested to be installed from the subject.

[0482] The PHR application user account creation delegation information may also include, for example, installation guidance information for installing a specified PHR application (for example, the URI of an application store or download website), or account registration guidance information for user registration on the PHR platform (for example, the URI to the account creation page in the management server 10).

[0483] The PHR application user account creation authorization information may also be encoded into, for example, a one-dimensional code or a two-dimensional code.

[0484] The PHR application user account creation request information may include information for identifying a medical institution (eg, the name of the medical institution) or an EMRID corresponding to the user of the subject terminal 20A.

[0485] Note that the PHR application requested to be installed by the subject may be selected based on, for example, a user input to the medical institution terminal 30X, for example, by selecting an arbitrary application registered in the PHR application registration data 157 .

[0486] In addition, the medical institution terminal 30X and the medical institution server 50 may also be connected to Figure 44 Similarly, an EMRID token is generated and included in the PHR application user account creation delegation information.

[0487] When generating, for example, the PHR application user account creation request information which is two-dimensional code information, the control unit 31 of the medical institution terminal 30X displays and outputs the generated information on the display unit 34 ( X620 ).

[0488] Note that the control unit 31 of the medical institution terminal 30X may also perform handover by transmitting PHR application user account creation request information to the subject terminal 20A through P2P communication using short-range wireless communication such as Bluetooth or NFC.

[0489] For example, based on user input, the control unit 21 of the subject terminal 20A uses the imaging unit 27 to read the PHR application user account creation request information displayed on the medical institution terminal 30X (A610). The control unit 21 of the subject terminal 20A can then receive information required for user account registration on the PHR platform (e.g., user name, password, etc.) based on the account registration guidance information.

[0490] It should be noted that the control unit 21 of the subject terminal 20A may also receive the PHR application user account creation request information by receiving the medical institution account ID or PHR application ID displayed on the medical institution terminal 30X through user input, for example.

[0491] Then, the control unit 21 of the subject terminal 20A transmits PHR application user account creation request information including information required for user account registration, the medical institution account ID of the medical institution terminal 30X, and the PHR application ID to the management server 10 ( A620 ).

[0492] It should be noted that the EMRID token or EMRID may also be included in the PHR application user account creation request information.

[0493] Upon receiving the PHR application user account creation request information from the subject terminal 20A, the control unit 11 of the management server 10 executes, for example, a PHR application account creation process ( S610 ).

[0494] In the PHR application account creation process, the control unit 11 of the management server 10 adds and stores a record related to the new user in the PHR user account registration data 153 based on the received PHR application user account creation request information, for example.

[0495] Then, the control unit 11 of the management server 10 transmits PHR application account information including the user account ID assigned to the user of the subject terminal 20A to the subject terminal 20A ( S620 ). Note that the PHR application account information may also include installation guidance information.

[0496] Then, the control unit 11 of the management server 10 executes, for example, a PHR application account cooperation process ( S630 ).

[0497] In the PHR application account cooperation process, the control unit 11 of the management server 10 communicates with Figure 44 Similarly, step S210 associates the user account ID assigned to the user of the subject terminal 20A and the medical institution account ID based on the PHR application user account creation request information with the PHR application ID.

[0498] Upon receiving the PHR application account information from the management server 10 , the control unit 21 of the subject terminal 20A executes, for example, a PHR application installation process ( A630 ).

[0499] In the PHR application installation process, the control unit 21 of the subject terminal 20A installs a predetermined PHR application based on the installation guidance information, for example, and executes the PHR application using the user account ID received in the PHR application account information.

[0500] It should be noted that, upon receiving the PHR application user account creation request, the control unit 21 of the subject terminal 20A may, for example, execute PHR application installation processing and obtain information required for user account registration on the PHR platform within the PHR application, which is launched without user registration. Subsequently, the control unit 21 of the subject terminal 20A may, for example, transmit a PHR application user account creation request to the management server 10.

[0501] <Effects of the Third Embodiment> In the third embodiment, Figure 48 、 Figure 50 As shown in the above, in response to the subject terminal 20 obtaining the medical institution account ID from the medical institution terminal 30, a user account ID is created. Since the PHR application associated with the medical institution account ID is installed on the subject terminal 20, the subject obtains the medical institution account ID from the medical institution terminal 30 by using his or her own subject terminal 20 in the medical institution, so that the subject can easily use the PHR application that the medical institution wants the subject to use.

[0502] In addition, in the third embodiment, as Figure 49 、 Figure 50 As shown in the above, by managing the user account ID and EMRID in association based on the consent of the subject in the subject terminal 20 on which the PHR application is installed, medical stakeholders of the medical institution can confirm the PHR data through the electronic medical record system. The PHR data is the data obtained by the PHR application after the PHR application is installed on the subject terminal 20 in the medical institution.

[0503] <Third Modification (1)> In the above embodiment, the PHR application installed on the subject terminal 20 (distributed by the medical institution to the subject) is specified on the medical institution terminal 30, but the present invention is not limited to this. For example, the PHR application user account creation request information may not include the PHR application ID.

[0504] In this case, for example, the control unit 11 of the management server 10 may include the PHR application list information in the PHR application account information. Then, the control unit 21 of the subject terminal 20A may also install one or more desired PHR applications from the PHR application list information onto the subject terminal 20A based on user input, for example.

[0505] Alternatively, the control unit 21 of the subject terminal 20A may specify a PHR application ID that cooperates with the medical institution terminal 30 among the installed PHR applications and transmit PHR application account cooperation request information including the specified PHR application ID to the management server 10 .

[0506] Upon receiving the PHR application account cooperation request information from the subject terminal 20A, the control unit 11 of the management server 10 may also execute the PHR application account cooperation process in the designated PHR application ID.

[0507] It should be noted that the PHR application user account creation request information may include multiple PHR application IDs that can be installed by the subject terminal 20. Furthermore, the PHR application user account creation request information may include an arbitrary PHR application ID selected by the user of the subject terminal 20.

[0508] Then, the control unit 11 of the management server 10 may include, for example, installation guidance information based on the selected arbitrary PHR application ID in the PHR application account information.

[0509] For example, the control unit 11 of the management server 10 may execute the PHR application account cooperation process for each PHR application ID selected by the user of the subject terminal 20 .

[0510] <Third Modification (2)> The above embodiment illustrates a case where the user of subject terminal 20A has not yet registered an account on the PHR platform, but the present invention is not limited to this. For example, the user of subject terminal 20A may have registered on the PHR platform (possessing a user account ID), but the user of medical institution terminal 30 may not have installed the PHR application requested from the subject.

[0511] In this case, for example, the control unit 21 of the subject terminal 20A may also execute the PHR application installation process when reading the PHR application user account creation request information. Therefore, the control unit 21 of the subject terminal 20A may also transmit, for example, PHR application account collaboration request information to the management server 10. The PHR application account collaboration request information includes the medical institution account ID, the PHR application ID, and the user account ID based on the PHR application user account creation request information.

[0512] <Fourth embodiment> The fourth embodiment is an embodiment in which the linkage between the user account ID and the medical institution account ID corresponding to the subject is released, for example.

[0513] The contents described in the fourth embodiment are also applicable to any of the other embodiments or other modified examples.

[0514] <Display screen> Figures 51 and 52 This is a diagram showing an example of a screen displayed on the display unit 24 of the subject terminal 20A or the display unit 34 of the medical institution terminal 30A in this embodiment.

[0515] At the subject terminal 20A Figure 51 On the main menu screen of the subject-side ASD diagnostic application on the left, for example, when the user taps the setting function button MNB, the PHR application setting menu area MNR is displayed.

[0516] In the PHR application setting menu area MNR, for example, if the user taps the item of canceling the PHR data cooperation with the medical institution, the subject terminal 20A will be opened. Figure 51 The display of the medical institution list information display screen changes after the central PHR application is linked.

[0517] On this screen, for example, a list of medical institutions that share PHR data in the ASD diagnosis application with the user UA is displayed. For example, if a medical institution HA is tapped, it is reversed and selected.

[0518] For example, if the medical organization HA is selected and the function button DC for canceling the cooperation of the PHR application is touched by the user, the PHR application cooperation cancellation process described later is executed in the management server 10. Then, for example, on the subject terminal 20A, Figure 51 The display of the PHR app account collaboration cancellation notification message display screen on the right side changes.

[0519] On this screen, the icon to the left of the application name indicates that the ASD diagnosis application, among the PHR applications that were linked by the medical institution HA and the subject HA, has been disconnected from the collaboration. In addition, the medication record application shows that the collaboration is maintained.

[0520] In addition, for example, if the PHR application cooperation release process is executed in the management server 10, Figure 52 The PHR application account cooperation cancellation notification information display screen on the left is displayed on the medical institution terminal 30A.

[0521] This screen shows that the ASD diagnosis application has been released from the collaboration with the user UA, but the PHR data of the ASD diagnosis application and the medication management application are recorded in the EMR data of the medical institution server 50 .

[0522] The lower part of the screen displays, for example, function buttons BT1 and BT2. Function button BT1 is used to delete the PHR data of the ASD diagnostic application recorded in the EMR data from the EMR data. Function button BT2 is used to cancel the collaboration without deleting the PHR data of the ASD diagnostic application recorded in the EMR data.

[0523] For example, if the user taps the function button BT1, the PHR / EMR account cooperation cancellation process described later is executed in the medical institution server 50. Then, for example, the medical institution terminal 30A displays Figure 52 The PHR / EMR account collaboration cancellation notification message is displayed on the right.

[0524] This screen shows that the PHR data of the ASD diagnosis application has been deleted from the EMR data. In addition, it shows that the medical institution HA and the user UA maintain the collaboration of the medication record application, and the PHR data of the medication record application is recorded in the EMR data.

[0525] <Processing> Figure 53 This is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The figure shows, from the left, examples of processing executed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0526] It should be noted that before starting the processing in this flowchart, for example, according to Figures 40 and 41 Processing, collaboration in the PHR platform between user UA and medical institution HX, and sharing of data between PHR data and electronic medical record services.

[0527] For example, based on user input, the control unit 21 of the subject terminal 20A transmits PHR application-coordinated medical institution list request information to the management server 10 , requesting a list of medical institutions cooperating with the user account ID of the subject terminal 20A ( A710 ).

[0528] For example, the medical institution list request information after PHR application collaboration may include a PHR application ID designated by the user of the subject terminal 20A.

[0529] Upon receiving the medical institution list request information after PHR application collaboration from the subject terminal 20A, the control unit 11 of the management server 10 executes, for example, a medical institution search process after PHR application collaboration ( S710 ).

[0530] In the medical institution search process after PHR application collaboration, the control unit 11 of the management server 10 refers to the account ID / PHR application collaboration management data 159, for example, and searches for the medical institution account ID after collaboration for each PHR application ID associated with the user account ID of the subject terminal 20A.

[0531] Then, the control unit 11 of the management server 10 transmits the medical institution list information after the PHR application is linked to the subject terminal 20A, the medical institution list information after the PHR application is linked to include the list of the searched medical institution account IDs.

[0532] It should be noted that the medical institution list information after PHR application linkage may also include the medical institution account ID linked to the PHR application ID specified in the medical institution list request information after PHR application linkage.

[0533] Upon receiving the medical institution list information after PHR application linkage from the management server 10 , the control unit 21 of the subject terminal 20A displays and outputs the received medical institution list information after PHR application linkage on the display unit 24 ( A720 ), for example.

[0534] For example, if a medical institution to be terminated from collaboration is selected based on user input regarding the displayed list of medical institutions after PHR application collaboration, the control unit 21 of the subject terminal 20A sends PHR application collaboration termination request information to the management server 10. The PHR application collaboration termination request information includes the user account ID of the subject terminal 20A and the selected medical institution account ID (A730).

[0535] Note that, for example, the PHR application collaboration termination request information may include the PHR application ID of the PHR application whose collaboration is to be terminated, which is specified by the user of the subject terminal 20. Furthermore, collaboration with a certain medical institution account ID may be terminated without specifying the PHR application ID.

[0536] When receiving the PHR application cooperation release request information from the subject terminal 20A, for example, the control section 11 of the management server 10 executes a PHR application cooperation release process ( S730 ).

[0537] In the PHR application cooperation release process, the control unit 11 of the management server 10 deletes the medical institution account ID in the account ID / PHR application cooperation management data 159 based on the received PHR application cooperation release request information, for example.

[0538] Then, for example, the control unit 11 of the management server 10 transmits the medical institution account ID from which the PHR application account cooperation cancellation notification information indicating that the cooperation of the PHR application is cancelled is deleted to the medical institution terminal 30X ( S740 ).

[0539] It should be noted that the PHR application account collaboration cancellation notification information may also include the PHR application ID of the PHR application whose collaboration has been cancelled.

[0540] Furthermore, the control unit 11 of the management server 10 may transmit PHR application account cooperation cancellation notification information to the subject terminal 20A.

[0541] If the PHR application account collaboration release notification information is received from the management server 10, the control unit 31 of the medical institution terminal 30X sends a PHR / EMR account collaboration release request information (X710) to the medical institution server 50, for example. The PHR / EMR account collaboration release request information includes the user account ID and PHR application ID included in the PHR application account collaboration release notification information.

[0542] The PHR / EMR account collaboration cancellation request information may also include, for example, PHR data deletion request information within the EMR data. The PHR data deletion request information within the EMR data is used to delete the PHR data stored in the EMR data.

[0543] It should be noted that the control unit 31 of the medical institution terminal 30X may also automatically transmit the PHR / EMR account collaboration termination request information upon receiving the PHR application account collaboration termination notification information from the management server 10. Alternatively, the control unit 31 of the medical institution terminal 30X may output the PHR application account collaboration termination notification information, for example, by transmitting the PHR / EMR account collaboration termination request information based on user input.

[0544] Upon receiving the PHR / EMR account cooperation cancellation request information from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes, for example, a PHR / EMR account cooperation cancellation process ( M710 ).

[0545] In the PHR / EMR account collaboration decoupling process, the control unit 51 of the medical institution server 50 refers to the PHR / EMR associated registration data 559, for example, and deletes the decoupling PHR application ID from the application IDs that have been collaborated with in the user account ID specified in the PHR / EMR account collaboration decoupling request information.

[0546] It should be noted that, for example, when it is determined that all application IDs after collaboration for a certain user account ID have been deleted or collaboration for a certain user account ID has been terminated, the control unit 51 of the medical institution server 50 can also delete the record of binding the user account ID and EMRID.

[0547] In addition, when it is determined that the PHR / EMR account collaboration termination request information includes PHR data deletion request information in the EMR data, the control unit 51 of the medical institution server 50 can also refer to the EMR patient information database 557, for example, to delete the PHR data from the EMR data of the EMRID, and the EMIID is bound to the user account ID specified in the PHR / EMR account collaboration termination request information.

[0548] Furthermore, the control unit 51 of the medical institution server 50 may transmit PHR / EMR account linkage release notification information to the medical institution terminal 30X when executing the PHR / EMR account linkage release process.

[0549] It should be noted that this flowchart provides an electronic medical record service in the medical institution server 50, but the present invention is not limited thereto. Referring to the first embodiment, even when the medical institution server 50 does not exist, the PHR account cooperation cancellation process can also be performed.

[0550] <Effects of the Fourth Embodiment> In the fourth embodiment, Figure 51 、 Figure 53 As shown in the figures, when the subject wants to stop sharing PHR data with the medical institution by canceling the collaboration between the user account ID and the medical institution account ID corresponding to the subject according to the subject's operation on the subject terminal 20, or wants to change the medical institution that is considered to be able to share PHR data, the sharing can be stopped by operating his own terminal.

[0551] In addition, in the fourth embodiment, as Figure 52 、 Figure 53 As shown in the figures, by deleting PHR data according to the operation of the medical-related personnel on the medical institution terminal 30, data management that respects the intention of the examinee not to share the PHR data can be performed in the medical institution. The above-mentioned PHR data is obtained by the PHR application and is managed by the medical institution server 50 in association with the identification information of the examinee in the medical institution terminal 30 and the medical institution server 50 that provides electronic medical record information, namely EMRID.

[0552] <Fourth Modification (1)> In the above embodiment, the PHR application cooperation is cancelled by the subject terminal 20 , but the present invention is not limited to this. For example, the PHR application cooperation may be cancelled by the medical institution terminal 30 .

[0553] For example, when the PHR application collaboration is terminated based on user input to the medical institution terminal 30, the control unit 31 of the medical institution terminal 30X may also send a PHR application collaboration termination request message to the management server 10. The PHR application collaboration termination request message includes the user account ID and PHR application ID for collaboration termination.

[0554] It should be noted that, when the set conditions are met, the control unit 31 of the medical institution terminal 30X may also automatically send PHR application cooperation termination request information to the management server 10 .

[0555] Here, the setting conditions may be as follows.

[0556] (C1) The patient has not received a medical examination at the medical institution of the medical institution terminal 30X for a predetermined period (e.g., one year) or longer. Or, the electronic medical record of a certain MERID has not been edited or viewed for a predetermined period or longer.

[0557] (C2) In a PHR application that uses PHR data, the PHR data has not been updated for a predetermined period (e.g., six months) or longer.

[0558] For example, in the case of (C1) above, the PHR application coordination release request information may include request information for releasing coordination in all PHR applications.

[0559] Furthermore, for example, in the case of (C2) above, the PHR application coordination release request information may include the PHR application ID associated with the unupdated PHR data.

[0560] In this way, by automatically releasing the linkage between the user account ID and the medical institution account ID corresponding to the subject according to the set conditions, data management can be made more efficient.

[0561] <Fifth embodiment> The fifth embodiment is an embodiment related to storing PHR data, which is information concerning privacy, in an encrypted state in the management server 10 , for example, requiring caution in processing.

[0562] The contents described in the fifth embodiment are also applicable to any of the other embodiments or other modified examples.

[0563] System Structure Figure 54 Another example of the PHR / EMR-related registration data 559 according to this embodiment is shown as PHR / EMR-related registration data 559B.

[0564] For example, in the PHR / EMR associated registration data 559B, in addition to the user account ID, EMRID, and the application ID after collaboration, a PHR data decryption key is also stored in association.

[0565] The PHR data decryption key is a decryption key for decrypting encrypted PHR data (referred to as "encrypted PHR data").

[0566] The encryption method of the PHR data may be, for example, a general key encryption method or a public key encryption method.

[0567] In common key encryption, the PHR data decryption key can also be called a secret key bound to the user account ID. In addition, in public key encryption, the PHR data decryption key can also be called a public key bound to the user account ID.

[0568] It should be noted that the decryption key may be different for each PHR application ID.

[0569] <Processing> Figures 55 and 56 This is a flowchart showing an example of the flow of processing executed by each device in this embodiment. The figure shows, from the left, examples of processing executed by the control unit 21 of the subject terminal 20A of the user UA, the control unit 31 of the medical institution terminal 30X of the medical institution HX, the control unit 51 of the medical institution server 50, and the control unit 11 of the management server 10.

[0570] Note that, in the case of the common key encryption method illustrated in this flowchart, a secret key is generated in the subject terminal 20A and stored in the storage unit 28 before the process.

[0571] Below, use Figure 55 Provide explanation.

[0572] The control unit 21 of the subject terminal 20A executes a process of generating the cooperation code information with the PHR application decryption key based on, for example, a user input ( A810 ).

[0573] In the collaborative code information generation process with the PHR application decryption key, the control unit 21 of the subject terminal 20A generates a QR code, i.e., the collaborative code information with the PHR application decryption key, based on the collaborative information with the PHR application decryption key including the PHR application collaborative information and the secret key stored in the storage unit 28.

[0574] Then, the control unit 21 of the subject terminal 20A displays and outputs the generated collaboration code information with the PHR application decryption key on the display unit 24 ( A820 ), for example.

[0575] For example, based on the user input, the control unit 31 of the medical institution terminal 30X uses the imaging unit 37 to read the collaboration code information with the PHR application decryption key displayed on the subject terminal 20A ( X810 ).

[0576] Then, the control unit 31 of the medical institution terminal 30X decodes the read coordination code information with the PHR application decryption key, and acquires coordination information with the PHR application decryption key.

[0577] It should be noted that the transfer of collaboration information including the PHR application decryption key is not limited to the method using a code image. For example, the control unit 21 of the subject terminal 20A may transfer the collaboration information including the PHR application decryption key by transmitting it to the medical institution terminal 30X through P2P communication using short-range wireless communication such as Bluetooth or NFC.

[0578] For example, the PHR application account cooperation request information may not include the decryption key. In other words, the decryption key may not be stored in the management server 10.

[0579] For example, when transmitting the PHR application account cooperation request information to the management server 10 , the control unit 31 of the medical institution terminal 30X transmits the user account ID, PHR application ID, EMRID, and PHR / EMR account cooperation request information with a decryption key including the decryption key to the medical institution server 50 ( X820 ).

[0580] Upon receiving the PHR / EMR account collaboration request information with a decryption key from the medical institution terminal 30X, the control unit 51 of the medical institution server 50 executes a PHR / EMR account collaboration process with a decryption key ( M810 ).

[0581] In the PHR / EMR account collaboration processing with decryption key, for example, the PHR / EMR collaboration processing unit 511 adds a record to the PHR / EMR associated registration data 559 based on the PHR / EMR account collaboration request information with decryption key, and stores the user account ID, EMRID and decryption key in association.

[0582] For example, when executing the PHR data acquisition process ( A130 ), the control unit 21 of the subject terminal 20A executes the PHR data encryption process ( A830 ).

[0583] In the PHR data encryption process, the control unit 21 of the subject terminal 20A encrypts the acquired PHR data using, for example, a secret key stored in the storage unit 28 to generate encrypted PHR data.

[0584] Then, the control unit 21 of the subject terminal 20A transmits encrypted PHR data recording request information including the encrypted PHR data to the management server 10 ( A840 ).

[0585] Upon receiving the encrypted PHR data recording request from the subject terminal 20A, the control unit 11 of the management server 10 executes an encrypted PHR data recording process (S820). During the encrypted PHR data recording process, the control unit 11 of the management server 10 associates the encrypted PHR data with the PHR application ID and stores it in the PHR data management database, for example.

[0586] In the management server 10 , since the decryption key has not been acquired, the PHR data cannot be retrieved from the encrypted PHR data.

[0587] For example, when executing the PHR data search process ( S130 ), the control unit 11 of the management server 10 transmits the encrypted PHR data to the medical institution terminal 30X ( S830 ).

[0588] In the medical institution terminal 30X, for example, since the decryption key is not stored, the PHR data cannot be retrieved from the encrypted PHR data.

[0589] Below, use Figure 56 Provide explanation.

[0590] For example, when EMR data reference request information is received from the medical institution terminal 30X and the EMR data search process is executed ( M430 ), the control unit 51 of the medical institution server 50 executes the PHR data decryption process ( M820 ).

[0591] During the PHR data decryption process, the control unit 51 of the medical institution server 50, for example, references the PHR / EMR associated registration data 559 and uses the PHR data decryption key to decrypt the encrypted PHR data stored in the EMR data of the EMR patient information management data, thereby obtaining the PHR data. The control unit 51 of the medical institution server 50 then transmits the EMR data, including the decrypted PHR data, to the medical institution terminal 30X (M440).

[0592] It should be noted that the control unit 51 of the medical institution server 50 may also perform PHR data decryption processing when performing EMR data update processing, and save the decrypted PHR data in the EMR data of the EMR patient information management data.

[0593] Alternatively, the control unit 31 of the medical institution terminal 30X may store the decryption key based on the collaboration information with the PHR application decryption key in association with the user account ID in the storage unit 38. Upon receiving the encrypted PHR data from the management server 10, the control unit 31 of the medical institution terminal 30X may decrypt the PHR data and obtain the PHR data. The decrypted PHR data may also be included in the EMR data update request.

[0594] <Effects of the Fifth Embodiment> In the fifth embodiment, Figure 54 、 Figure 55 and Figure 56 As shown in FIG, etc., PHR data encrypted with an encryption key corresponding to the PHR application is registered in the management server 10, and the encrypted PHR data is provided to the medical institution terminal 30 having a decryption key corresponding to the encryption key. By encrypting the PHR data registered in the management server 10, security risks such as data leakage are reduced.

[0595] In addition, in the fifth embodiment, as Figure 54 、 Figure 55 and Figure 56 As shown in FIG, etc., PHR data encrypted with an encryption key corresponding to the PHR application is registered in the management server 10, and the encrypted PHR data is provided to the medical institution terminal 30 having a decryption key corresponding to the encryption key. The decryption key is provided only to the medical institution terminal 30 that has completed ID cooperation. Since the decryption key is provided only to the medical institution terminal 30 that has completed ID cooperation, it is possible to prevent PHR data from being provided to unintended medical institutions.

[0596] <Fifth Modification (1)> In the above embodiment, the decryption key is exemplified as a secret key in a common key encryption method, but the present invention is not limited thereto. For example, the decryption key may be a secret key of the medical institution server 50 in a public key encryption method.

[0597] In this case, before processing, a secret key and a public key are generated in the subject terminal 20A and the medical institution server 50, and stored in the storage unit 28 or the storage unit 55. Hereinafter, the secret key and the public key of the subject terminal 20A are referred to as "secret key A" and "public key A", respectively, and the secret key and the public key of the medical institution server 50 are referred to as "secret key H" and "public key H", respectively.

[0598] For example, the control unit 21 of the subject terminal 20A transmits collaboration information including a PHR application decryption key including a public key A based on the secret key A to the medical institution terminal 30X via code information or P2P communication. The control unit 31 of the medical institution terminal 30X then transmits PHR application account collaboration request information including the public key A as the decryption key to the management server 10.

[0599] Furthermore, the control unit 31 of the medical institution terminal 30X receives the public key H based on the secret key H from the medical institution server 50, and transmits the collaboration information including the public key H and the PHR application decryption key to the subject terminal 20A via code information or P2P communication. The control unit 21 of the subject terminal 20A then stores the received public key H in the storage unit 28, for example, in association with the medical institution account ID.

[0600] In the PHR data encryption process, for example, the control unit 21 of the subject terminal 20A encrypts the PHR data based on the public key A to generate first encrypted PHR data. Alternatively, for example, the control unit 21 of the subject terminal 20A encrypts the PHR data based on the public key H to generate second encrypted PHR data.

[0601] The first encrypted PHR data may also be referred to as encrypted PHR data decryptable by the user of the subject terminal 20A. In addition, the second encrypted PHR data may also be referred to as encrypted PHR data decryptable by the user of the medical institution server 50.

[0602] It should be noted that, when there are multiple cooperation destinations for PHR data, the control unit 21 of the subject terminal 20A may further generate multiple encrypted PHR data based on the public key H corresponding to each medical institution account, for example.

[0603] In the PHR data decryption process, for example, upon receiving the second encrypted PHR data, the control unit 51 of the medical institution server 50 decrypts the second encrypted PHR data based on the secret key H to obtain the PHR data.

[0604] It should be noted that the secret key and public key of the medical institution server 50 may also be those generated by the medical institution terminal 30. That is, key exchange may be performed for each medical institution terminal 30 and the subject terminal 20. Furthermore, upon receiving the second encrypted PHR data from the management server 10, the control unit 31 of the medical institution terminal 30 may decrypt the PHR data and obtain the PHR data. The decrypted PHR data may also be included in the EMR data update request.

[0605] In addition, the control unit 21 of the subject terminal 20A can also perform PHR application account collaboration processing in the management server 10, and when receiving PHR collaboration notification information, send PHR data reference request information, which requests the first encrypted PHR data that has been recorded in the application that collaborates with the management server 10.

[0606] Then, the control unit 21 of the subject terminal 20A uses the secret key A to decrypt the first encrypted PHR data. If the PHR data is obtained, the PHR data is encrypted using the public key H of the re-collaborated medical institution terminal 30 or medical institution server 50 and is added and stored in the management server 10.

[0607] Description of Reference Numerals 1 Information System 10 Management Server 20 Subject terminal 30 Medical institution terminals 40 Network 50 medical institution servers 60 PHR application management server

Claims

1. A data sharing system for sharing data related to the health of a subject between a plurality of applications for acquiring data and a medical institution terminal for viewing the data, wherein: The data sharing system comprises: a storage unit configured to manage a collaboration between a first account ID and a second account ID, established in correspondence with at least one of the applications, wherein the first account ID is used by the subject to access the data sharing system, and the second account ID is used by a user of the medical institution terminal to access the data sharing system; as well as A control unit determines, based on a request from the medical institution terminal, the data acquired by the application associated with the first account ID, the first account ID being associated with the second account ID corresponding to the medical institution terminal.

2. The data sharing system according to claim 1, wherein: The control unit registers the data corresponding to each of the plurality of applications in the storage unit.

3. The data sharing system according to claim 1, wherein: As the determination of the data, the control unit requests the data corresponding to each of the plurality of applications from the terminal of the subject.

4. The data sharing system according to claim 1, wherein: As the determination of the data, the control unit requests the data corresponding to each of the plurality of applications from a corresponding application management server.

5. The data sharing system according to claim 1, wherein: The storage unit manages the account corresponding to the subject based on the first account ID commonly used in the plurality of applications running on the terminal of the subject.

6. The data sharing system according to claim 1, wherein: The storage unit manages the plurality of applications in a correspondence relationship with the collaboration between the first account ID and the second account ID.

7. The data sharing system according to claim 1, wherein: The storage unit manages the plurality of applications corresponding to the first account ID in correspondence with the plurality of second account IDs.

8. The data sharing system according to claim 1, wherein: The control unit further receives an ID collaboration request including the first account ID, the second account ID, and identification information of at least one of the applications, The storage unit manages the collaboration between the first account ID and the second account ID in correspondence with at least one of the applications according to the ID collaboration request.

9. The data sharing system according to claim 1, wherein: The request from the medical institution terminal includes information that can identify the first account ID and the second account ID. The control unit determines the data acquired by the application that has established a correspondence between the first account ID and the second account ID.

10. The data sharing system according to claim 1, wherein: The request from the medical institution terminal includes: specifying the data of the object based on the identification information of the subject; The control unit determines the data corresponding to the request of the medical institution terminal based on the first account ID corresponding to the identification information, the second account ID corresponding to the medical institution terminal, and the application associated with the first account ID and the second account ID.

11. The data sharing system according to claim 1, wherein: The request from the medical institution terminal includes information that can identify the first account ID and the second account ID. The control unit determines the application that has established a correspondence with the first account ID and the second account ID, and determines the data obtained by the determined application.

12. The data sharing system according to claim 1, wherein: The control unit further receives an ID cooperation request provided to the medical institution terminal from the terminal on which the application is installed, the ID cooperation request including the first account ID, identification information of the application, and the second account ID. The storage unit manages the association between the first account ID and the second account ID and the identification information of the application in a corresponding relationship.

13. The data sharing system according to claim 1, wherein: The control unit further receives an ID collaboration request provided to the medical institution terminal from the terminal on which the application is installed based on the consent of the examinee or a person related to the examinee, wherein the ID collaboration request includes the first account ID, identification information of the application, and the second account ID. The storage unit manages the association between the first account ID and the second account ID and the identification information of the application in a corresponding relationship.

14. The data sharing system according to claim 1, wherein: The control unit further receives an ID cooperation request provided from the medical institution terminal to the terminal where the application is installed, the ID cooperation request including the second account ID, the first account ID and the identification information of the application, The storage unit manages the association between the first account ID and the second account ID and the identification information of the application in a corresponding relationship.

15. The data sharing system according to claim 1, wherein: The control unit further receives an ID collaboration request from the medical institution terminal to the terminal on which the application is installed, based on the consent of the subject or a person related to the subject, wherein the ID collaboration request includes the second account ID, the first account ID, and identification information of the application. The storage unit manages the association between the first account ID and the second account ID and the identification information of the application in a corresponding relationship.

16. The data sharing system according to claim 1, wherein: The medical institution application for browsing the data in the medical institution terminal is common to the plurality of applications.

17. The data sharing system according to claim 1, wherein: In the medical institution terminal and the electronic medical record system providing electronic medical record information, the storage unit associates and manages the third account ID, which is identification information of the subject in the electronic medical record system, with the first account ID.

18. The data sharing system according to claim 1, wherein: In the medical institution terminal and the electronic medical record system providing electronic medical record information, the storage unit associates and manages the subject's identification information in the electronic medical record system, namely, the third account ID, with the first account ID. The control unit registers the data corresponding to the first account ID and / or information associated with the data in the electronic medical record system in association with the third account ID.

19. The data sharing system according to claim 1, wherein: In the medical institution terminal and the electronic medical record system providing electronic medical record information, the storage unit associates and manages the subject's identification information in the electronic medical record system, namely, the third account ID, with the first account ID. The control unit registers the data corresponding to the first account ID and / or information associated with the data in the electronic medical record system in association with the third account ID, and provides the electronic medical record information and the data and / or information associated with the data to the medical institution terminal based on a request from the medical institution terminal for providing the electronic medical record information based on the third account ID.

20. The data sharing system according to claim 1, wherein: The control unit creates the first account ID in response to the subject's terminal acquiring the second account ID from the medical institution terminal, and requests installation of the application associated with the second account ID on the subject's terminal.

21. The data sharing system according to claim 20, wherein: The storage unit manages the first account ID and the third account ID corresponding to the subject in association with each other based on the consent of the subject or the subject's related person in the terminal where the application is installed. The third account ID is the identification information of the subject in the medical institution terminal and the electronic medical record system that provides electronic medical record information.

22. The data sharing system according to claim 1, wherein: The storage unit releases the linkage between the first account ID and the second account ID corresponding to the subject according to an operation on the subject's terminal.

23. The data sharing system according to claim 1, wherein: The storage unit releases the linkage between the first account ID and the second account ID corresponding to the subject according to a set condition.

24. The data sharing system according to claim 22 or 23, wherein: The storage unit deletes the data acquired by the application and managed by the electronic medical record system in association with a third account ID based on the operation of the user of the medical institution terminal. The third account ID is the identification information of the subject in the medical institution terminal and the electronic medical record system that provides electronic medical record information.

25. The data sharing system according to claim 1, wherein: The data is encrypted using an encryption key corresponding to the application, The control unit provides the encrypted data to the medical institution terminal having a combined key corresponding to the encryption key.

26. The data sharing system according to claim 25, wherein: The combined key is provided only to the medical institution terminal that has performed ID collaboration.

27. A data sharing method in a data sharing system, wherein data related to the health of a subject is shared between a plurality of applications for acquiring data and a medical institution terminal for viewing the data, wherein: The collaboration between the first account ID and the second account ID is managed in a corresponding relationship with at least one of the applications, wherein the first account ID is used for the subject to access the data sharing system, and the second account ID is used for the user of the medical institution terminal to access the data sharing system. According to a request from the medical institution terminal, the data acquired by the application corresponding to the first account ID is determined, and the first account ID cooperates with the second account ID corresponding to the medical institution terminal.

Images