Medical cooperation server, medical cooperation system, medical cooperation method, and program

Abstract

To provide a medical cooperation server, a medical cooperation system, a medical cooperation method and a program capable of automatically providing medical cooperation information in the latest state at any time without exclusively inputting the medical cooperation information, and allowing a person related to a patient to efficiently access the medical cooperation information.SOLUTION: The medical cooperation server 10 manages items of information used for medical cooperation among the patient information and the medical examination information stored in the medical institution terminal 20, collects and updates the patient information and the like when the patient information and the like set to be used for the medical cooperation are generated or updated, generates medical cooperation information using the collected patient information and the like, and shares the medical cooperation information by distinguishing the medical cooperation information according to a relationship with the patient and a purpose of use so that the medical cooperation information can be used in the patient-related person terminal 30 of the patient-related person 3 related to the patient.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a medical collaboration server, a medical collaboration system, a medical collaboration method, and a program. [Background technology]

[0002] In recent years, regional medical cooperation has been attracting attention. In regional medical cooperation, for example, when a medical institution refers a patient to another medical institution, the medical institution generally attaches medical information to a medical information release form and hands it over to the other medical institution, or provides it by fax or mail.

[0003] Furthermore, many medical institutions have introduced electronic medical records that can electronically record a patient's medical information. This allows multiple doctors and nurses within a medical institution to share the electronic medical record of the same patient. In contrast, when attempting to share medical information between medical institutions, a method of transmitting the electronic medical record using referral information, as described in Patent Document 1, is considered. Because highly confidential information such as the electronic medical record is transmitted, communication using a virtual dedicated line, for example, may be used. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-237834 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the medical collaboration system disclosed in Patent Document 1 requires one-on-one communication between medical institutions using referral information, making it impossible to efficiently share medical collaboration information such as electronic medical records with medical professionals other than doctors involved in regional medical care. Furthermore, because communication must be performed using a virtual private line, only a portion of the information that can be shared, even if it is used for medical collaboration, can be shared. This makes it difficult to share information with patients and others. Furthermore, sharing information individually required for medical collaboration requires individual input and transmission of information, which requires time-consuming individual responses.

[0006] Therefore, the present disclosure provides a medical collaboration server, a medical collaboration system, a medical collaboration method, and a program that can automatically provide the latest medical collaboration information at any time without the need for dedicated input, and that can also make it efficiently accessible to patients and related parties. [Means for solving the problem]

[0007] In order to solve the above problems, the medical collaboration server of the present disclosure is a medical collaboration server that shares patient information and patient medical information about patients receiving treatment at a medical institution via a network with a medical institution terminal owned by a medical institution and a patient-related person terminal operated by patient-related persons including patients, and is equipped with: an update means that manages information items to be used for medical collaboration among the patient information and medical information stored in the medical institution terminal, and collects and updates the patient information and medical information when patient information and medical information set to be used for medical collaboration is generated or updated; a generation means that generates medical collaboration information using the collected patient information and medical information when the patient information and medical information to be used for medical collaboration is updated; and a sharing means that stores the medical collaboration information distinguished by its relationship with the patient and its purpose of use so that it can be used on the patient-related person terminal of a patient-related person who is related to the patient.

[0008] The medical collaboration system of the present disclosure is a medical collaboration system that includes a medical institution terminal owned by a medical institution, a patient-related person terminal operated by patient-related persons including patients, and a medical collaboration server, and the medical institution terminal, patient-related person terminal, and medical collaboration server share patient information about patients receiving treatment at the medical institution and medical information of the patients via a network, and the medical collaboration server manages information items to be used for medical collaboration among the patient information and medical information stored in the medical institution terminal, and includes an update means that collects and updates the patient information and medical information when patient information and medical information set to be used for medical collaboration is generated or updated, a generation means that generates medical collaboration information using the collected patient information and medical information when the patient information and medical information to be used for medical collaboration is updated, and a sharing means that stores the medical collaboration information separated by its relationship with the patient and its purpose of use so that it can be used on the patient-related person terminal of a patient-related person who is related to the patient.

[0009] The medical collaboration method of the present disclosure is a medical collaboration method in which a medical institution terminal owned by a medical institution, a patient-related terminal operated by a patient-related person including a patient, and a medical collaboration server share patient information and patient medical information about patients receiving treatment at the medical institution via a network, and the medical collaboration method includes a control unit provided in the medical collaboration server that manages information items to be used for medical collaboration among the patient information and medical information stored in the medical institution terminal and collects and updates the patient information and medical information when patient information and medical information set to be used for medical collaboration is generated or updated, generates medical collaboration information using the collected patient information and medical information when the patient information and medical information to be used for medical collaboration is updated, and saves the medical collaboration information separated by its relationship with the patient and its purpose of use so that it can be used on the patient-related terminal of a patient-related person related to the patient.The medical collaboration program of the present disclosure also realizes the above-mentioned medical collaboration method by a computer. [Brief explanation of the drawings]

[0010] [Figure 1]1 is a configuration diagram of a medical collaboration system 1 according to a first embodiment. [Figure 2] 2 is a block diagram showing the functional configuration of the medical collaboration server 10. FIG. [Figure 3] 3 is a block diagram showing the functional configuration of a medical institution terminal 20. FIG. [Figure 4] 3 is a block diagram showing the functional configuration of the patient-related terminal 30. FIG. [Figure 5] FIG. 10 is a diagram illustrating an example of a data configuration of medical collaboration information. [Figure 6] 3 is a sequence diagram showing an example of a processing flow in the medical cooperation system 1. FIG. [Figure 7] 10 is a sequence diagram showing the flow of processing as another example in the medical cooperation system 1. FIG. [Figure 8] 10 is a sequence diagram showing a processing flow as yet another example in the medical cooperation system 1. FIG. [Figure 9] FIG. 2 is a block diagram showing the hardware configuration of the medical collaboration server 10. [Figure 10] 10 is a conceptual diagram showing an example of regional medical cooperation by a medical cooperation system 1 according to a second embodiment. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described. Note that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all of the configurations described in the embodiments are necessarily essential components of the present disclosure. Furthermore, in all drawings describing the embodiments, common components are denoted by the same reference numerals, and repeated explanations will be omitted.

[0012] <Embodiment 1> (Overview of Medical Collaboration System 1) FIG. 1 is a configuration diagram of a medical collaboration system 1 according to a first embodiment. The medical collaboration system 1 includes a medical collaboration server 10, medical institution terminals 20 (20a, 20b) owned by a medical institution 200, and patient-related terminals 30 (30a, 30b, 30c, 30d) operated by patient-related parties 3, including patients, all of which are connected via a network NW such as the Internet. The network NW includes wired or wireless telecommunications lines, and includes not only Internet lines but also communication networks for telephones for voice calls. As shown in the figure, information collaboration is achieved by multiple medical institution terminals 20 and multiple patient-related terminals 30 accessing the medical collaboration server 10 via the network NW.

[0013] The medical institution terminal 20 shown in FIG. 1 is owned by each medical institution 200. At the medical institution 200, a medical professional 2 inputs and views patient information and the like using the medical institution terminal 20. In addition, output such as test results from medical equipment may be input to the medical institution terminal 20. As shown in the figure, in the medical collaboration system 1, the medical institution terminals 20a, 20b of multiple medical institutions 200a, 200b are connected to the medical collaboration server 10 via a network NW, allowing the multiple medical institutions 200 to share information and collaborate on medical matters. This allows patient-related personnel 3 to use patient information, treatment information, and the like from the multiple medical institutions 200 as medical collaboration information via the medical collaboration server 10.

[0014] In the present disclosure, "medical care" may include not only direct medical treatment but also health care-related treatment such as nursing care. Furthermore, medical institution 200 may include not only institutions that perform medical treatment, such as hospitals and clinics, but also organizations and groups involved in medical treatment, such as nursing homes and pharmacies. Therefore, the medical information used to generate medical collaboration information in the present disclosure may include not only the medical information of patients being treated for illnesses, but also information on home rehabilitation, home pharmacy visits, home nutrition visits, and emergency medical teams.

[0015] Medical personnel 2 include not only doctors, nurses, medical administrative staff, or medical technicians who are directly involved in medical care at medical institution 200, but also people who work in medical or nursing-related industries outside medical institution 200, such as visiting nursing stations, visiting rehabilitation stations, visiting pharmacies, visiting nutritionists, care managers, and nursing care services.

[0016] Patient-related persons 3 include not only the patient himself / herself, but also people in a position to manage and supervise the patient, such as the patient's family, relatives, and legal representatives. For example, a patient-related person 3 may be the parent of a child patient, or the child of an elderly patient. Depending on the relationship with the patient, a medical professional 2 may also be a patient-related person 3. For example, a medical professional 2 (e.g., a doctor) who receives an introduction about a patient-related person 3 who is also a patient may also be a patient-related person 3. For this reason, a medical professional 2, as a patient-related person 3, may use a medical institution terminal 20 as a patient-related person terminal 30 to view patient information and medical information as medical coordination information.

[0017] (System configuration of medical collaboration server 10) FIG. 2 is a block diagram showing the functional configuration of the medical collaboration server 10. The medical collaboration server 10 is a server device that manages medical collaboration information and includes a communication unit 11, a storage unit 12, and a control unit 13. Each unit functions as follows under the control of the control unit 13. The communication unit 11 is a communication interface that communicates with the medical institution terminal 20 and the patient-related terminal 30 via the network NW. The communication unit 11 also functions as a telephone switch that places calls to the patient-related terminal 30, which is a wired telephone, via the wired telephone network NW. The storage unit 12 is a storage device that stores patient information, medical treatment information, and the like. The storage unit 12 also stores programs such as the various applications and modules shown in FIG. 1, as well as various databases. In the following description and in each figure, applications may be abbreviated to "apps."

[0018] (Application configuration of medical collaboration server 10) The medical cooperation server 10 shares patient information and medical treatment information with the medical institution terminal 20 and the patient-related person terminal 30 via the network NW using various applications and databases shown in Fig. 1. The shared information includes at least information about patients who are receiving medical treatment from doctors at the medical institution 200 (patients who are examined at the medical institution 200) and the patient's medical treatment information. Note that the patient information may include not only information about the patient himself / herself, but also information about patient-related people 3 related to the patient.

[0019] (Module configuration) The medical collaboration server 10 comprises a medical collaboration information module 100, a shared data market 110, and a service module 120. The medical collaboration information module 100 generates medical collaboration information based on patient information and medical treatment information collected from the medical institution terminal 20, stores it in the shared data market 110 for each purpose of use, and the service module 120 provides it to the patient-related terminal 30 as medical collaboration information using modules and applications appropriate for the purpose. Note that, hereinafter, the patient information and medical treatment information used to generate the medical collaboration information may be collectively referred to as "patient information, etc."

[0020] (Configuration of each module in medical collaboration server 10) The medical cooperation information module 100 also functions as an update means for collecting and updating patient information, etc., when patient information set to be used for medical cooperation is generated or updated. Of the patient information and medical treatment information stored in the medical institution terminal 20, the information items used for medical cooperation are managed by the medical institution terminal 20. However, the management of the information items used for medical cooperation may be performed by the medical cooperation information module 100, or may be performed by both.

[0021] Furthermore, the medical collaboration information module 100 functions as a generation means for collecting patient information, etc., and generating medical collaboration information when patient information, etc., used for medical collaboration is updated. The patient information, etc., data collection application 101 collects data related to patient information, etc., from the information of the medical institution 200 generated at the medical institution terminal 20, as medical collaboration information. The patient information, etc., data collection application 101 aims to improve the efficiency of data processing by collecting only data such as patient information, etc., used for medical collaboration information. Then, the collaboration data generation application 102 converts the format of the patient information, etc., collected by the patient information, etc., data collection application 101, and generates medical collaboration information data to be used for actual medical collaboration.

[0022] In the medical collaboration server 10, the medical collaboration information module 100 may collect and update patient information, etc. from multiple medical institution terminals 20. For example, the medical collaboration information module 100 may collect and update patient information, etc. related to one patient from multiple medical institution terminals 20. This allows the medical collaboration server 10 to share patient information, etc. centralized from patient information, etc. from multiple medical institutions 200, as medical collaboration information with patient-related parties 3 (including medical-related workers 2), thereby improving the efficiency of information collection by related parties.

[0023] The shared data market 110 functions as a sharing means for storing medical collaboration information, distinguishing it by its relationship with the patient and its purpose of use, so that it can be used on the patient-related person terminal 30 of the patient-related person 3 who has a relationship with the patient. The shared data market 110 includes databases for various services, such as a push notification DB 111, a shared information DB 112, a reassurance service DB 113, and a communication DB 114. The shared information DB 112 also includes a patient referral DB 112a, a patient / guardian DB 112b, a care DB 112c, and a home nursing DB 112d. The shared data market 110 may also include databases for medical collaboration other than these. The shared information DB 112 may also include, for example, a referred patient DB for referred patients to check the referral destination.

[0024] As a result, information for push notifications, information for patient referrals, information for patients / guardians, information for care managers / care-related personnel, information for visiting nurses, information for reassurance services, and information regarding communication (question / answer) are stored and saved in the shared data market 110. In addition, in the shared data market 110, information for online conferences may be stored in the communication DB 114 as an example of communication by patient-related persons 3. Furthermore, by providing a dedicated DB in the shared data market 110, information for home rehabilitation, home pharmacy visits, home nutrition visits, or emergency teams may be stored.

[0025] The service module 120 includes a security module 121 and modules 122 to 125 for various applications. The service module 120 is configured so that the patient-related person terminal 30 can use information from the shared data market 110 by connecting to the modules 122 to 125 for various applications via the security module 121. The modules 122 to 125 for various applications communicate with the patient-related person terminal 30 via the network NW to send and receive information.

[0026] The security module 121 has a firewall function and ensures safe interaction between the medical collaboration server 10 and the patient-related person terminal 30 in the medical collaboration system 1, and ensures the safety of stored data. This firewall function includes a hardware firewall function for web applications and a software authentication function such as two-step authentication and biometric authentication. As a result, the security module 121 prevents the intrusion of malicious code and the leakage of data into the various modules 122 to 125 and the shared data market 110, and the two-step authentication and biometric authentication ensure that access is from the patient-related person terminal 30 of a patient-related person 3 with legitimate authority.

[0027] In the service module 120, the modules 122 to 125 for various applications notify, send, receive, or call the patient-related person terminal 30 of medical cooperation information related to each patient-related person 3. The modules 122 to 125 for various applications enable the patient-related person 3 to access the medical cooperation system 1 within the service module 120, so that the modules can be accessed via the web browser of the patient-related person terminal 30, or can be accessed from the patient-related person terminal 30 on which a dedicated application is installed.

[0028] The push notification module 122 is a program for providing a service that notifies the patient-related person 3 of the arrival of valuable medical collaboration information in real time, in order to provide the information at the appropriate time. The push notification module 122 notifies the patient-related person 3 as a message via phone call, a message within the app, or a message email, depending on the type of contact of the patient-related person 3 with whom the medical collaboration information is shared. For example, if a phone number is registered as a contact, the push notification module 122 sends a push notification as a voice message via phone call.

[0029] The information viewing module 123 is a service program that allows the patient-related person 3 to view information received by the patient-related person terminal 30. In the information viewing module 123, in order to enable smooth sharing of highly confidential information such as patient information, the information can be viewed only when the person is authenticated as the sharing destination of the medical collaboration information. Note that the information viewing module 123 may be configured as an information viewing function in another collaboration app depending on the purpose of use and the user.

[0030] The reassurance service module 124 is a program for providing a service of contacting other patient-related persons 3 who are related to the patient, for example, when hospital visit information or medication information is not received at the patient-related person's terminal 30 of the patient-related person 3 who is a patient. In this case, the patient may be contacted by wired telephone. The reassurance service module 124 can notify the patient-related person 3 of alarm information according to the patient's behavior, thereby informing the patient-related person 3 of the possibility that the patient may be in poor health, for example, and reducing the patient's health concerns.

[0031] The communication module 125 is a program for providing a service that enables communication between patient-related parties 3 via chat or video calls. The communication module 125 may provide a chat service that enables parties to contact each other about information other than that provided by the system or to exchange questions and answers. The communication module 125 may also provide an online conference service that enables parties to hold a video conference when an important issue arises. The communication module 125 may also include a push notification function. This allows, for example, medical professionals 2 who are patient-related parties 3 to communicate with each other via the medical collaboration system 1, or allows a patient-related party 3 who is a medical professional 2 and a patient-related party 3 who is a patient to communicate via the medical collaboration system 1.

[0032] (Configuration of medical institution terminal 20) FIG. 3 is a block diagram showing the functional configuration of the medical institution terminal 20. The medical institution terminal 20 is, for example, an information processing device such as a personal computer or a server, and is a terminal owned by the medical institution 200. When a doctor, nurse, medical administrative staff, medical technician, or the like performs a medical procedure such as a medical examination, medical treatment, nursing, examination, or radiation exposure, related information is input and recorded in the medical institution terminal 20. Furthermore, the medical institution terminal 20 also performs operations related to medical administration, medical accounting, or logistics, and inputs and stores related information. Furthermore, the medical institution terminal 20 may be an in-hospital system in which multiple personal computers, servers, and the like function in cooperation with each other. For example, the medical institution terminal 20 may be an in-hospital system in which a server device operating 24 hours a day receives data such as patient information from personal computers operated by medical personnel 2 such as doctors, accumulates the patient information, and shares the data with the medical collaboration server 10 in real time.

[0033] The medical institution terminal 20 includes a communication unit 21, an input unit 22, a display unit 23, a storage unit 24, and a control unit 25, and each unit functions as follows under the control of the control unit 25. The communication unit 21 is a communication interface that communicates with the medical collaboration server 10 via the network NW. The input unit 22 is an input interface for operating the medical institution terminal 20. For example, it functions as an operation unit using a keyboard, mouse, touch panel, or microphone for voice input. Note that the input unit 22 may not only be a device that functions as an operation unit, but may also include a device that can input, for example, images and data as medical information. The input unit 22 is also used to manage and set items of information used in medical collaboration, which will be described later.

[0034] The display unit 23 is a display that displays a GUI for input and an image or the like instructed by the control unit 25, which will be described later. The display unit 23 is also used to manage and set items of information used in medical cooperation, which will be described later.

[0035] The storage unit 24 is a storage device that stores various types of information including patient information generated in the medical institution terminal 20, and includes a patient information DB 241, a medical treatment information DB 242, an accounting information DB 243, a medical cooperation DB 244, and a management information DB 245. With such a database configuration, the storage unit 24 stores a wide variety of information related to the medical institution 200, such as medical records / orders, nursing, dialysis, specimen testing, physiological tests, operating rooms, pharmacies, medical accounting, or logistics, and saves it as data. Among these, the storage unit 24 manages items of information used for medical cooperation in each of the DBs 241 to 245.

[0036] The patient information DB 241 stores information about patients, which will be described later. The medical information DB 242 stores medical information about patients, which will be described later. The accounting information DB 243 stores information about logistics, sales, expenses, and the like.

[0037] The medical collaboration DB 244 acquires and stores only information on items set to be used for medical collaboration information from among the patient information, etc. contained in the patient information DB 241 and the medical information DB 242. For example, this setting is performed by the medical professional 2 using the input unit 22 and the display unit 23 to select necessary information from the patient information, etc. Note that, although not shown, the storage unit 24 may also include a separate patient-related person information DB that stores information about the patient-related person 3, which will be described later. Furthermore, the information about the patient-related person 3 may be stored in the patient information DB 241. In this way, by making the information of the patient-related person 3 also available, the sharing of information to the patient-related person 3 in the medical collaboration system 1 may be made more efficient.

[0038] The management information DB 245 stores management information generated based on the patient information DB 241, medical treatment information DB 242, and accounting information DB 243. The management information DB 245 stores information useful for the management of the medical institution 200 based on various information stored in the storage unit 24. The management information is useful for the management of the medical institution 200 but is not necessary for medical cooperation. Therefore, information on items of patient information, etc. that are not set to be used for medical cooperation but are useful for management are managed separately from the medical cooperation DB 244.

[0039] The control unit 25 stores information input by operation of the medical practitioner 2 as data in the storage unit 24. The control unit 25 acquires items to be stored in the medical cooperation DB 244 from the patient information DB 241 and the medical treatment information DB 242 in response to input via the input unit 22 by the medical practitioner 2, who is, for example, a doctor, and stores them in the storage unit 24. The control unit 25 controls the display unit 23 to display the acquired items of information to be used for medical cooperation, for example, item by item. At this time, the medical practitioner 2, who is a doctor, may manage the display and sharing of the information by issuing an instruction using the input unit 22, such as changing the items of the information for medical cooperation.

[0040] (Configuration of patient-related terminal 30) 4 is a block diagram showing the functional configuration of the patient-related person terminal 30. The patient-related person terminal 30 is, for example, a personal computer such as a desktop computer or a laptop computer, a mobile information terminal such as a smartphone or a tablet computer, a wearable terminal such as a smart watch, or a wired telephone, and is a terminal operated by the patient-related person 3. The patient-related person 3 operates the patient-related person terminal 30 to use services provided by various modules 122 to 125 in the service module 120 of the medical cooperation server 10.

[0041] The patient-related person terminal 30 comprises a communication unit 31, an input unit 32, a display unit 33, a memory unit 34, a control unit 35, and an audio output unit 36, and each unit functions as follows under the control of the control unit 35.

[0042] The communication unit 31 is a communication interface that communicates with the medical collaboration server 10 via the network NW. The input unit 32 is an input interface for operating the patient-related person terminal 30. For example, it may be a touch panel, an operation button, or a microphone for voice input. The input unit 32 functions as an operation unit that performs login operations for the modules 122 to 125 for various applications. The input unit 32 may also include a microphone and a camera that record audio and video of the patient-related person 3 so that video conferencing, etc., is possible in the communication module 125.

[0043] The display unit 33 is a display that displays a GUI for input using a liquid crystal display or the like, and displays images and the like instructed by the control unit 35, which will be described later. For example, medical cooperation information received from the modules 122 to 125 for various applications is displayed on the display unit 33. The storage unit 34 stores the medical cooperation information and the like received from the modules 122 to 125 for various applications. The control unit 35 controls the login operation for the modules 122 to 125 for various applications and the display of the received medical cooperation information in accordance with the input from the input unit 32 by the patient-related person 3.

[0044] The audio output unit 36 ​​is a speaker, and plays back an audio message transmitted as medical cooperation information under the control of the control unit 35. The audio output unit 36 ​​may also play back an audio message transmitted by phone as medical cooperation information. For example, when hospital visit information (described later) is notified by push notification, the patient-related person 3, who is a patient, performs an operation to play back an audio message on the input unit 32, whereby the audio message is played back from the audio output unit 36.

[0045] (Medical collaboration information) 5 is a diagram showing an example of the data configuration of medical collaboration information. The medical collaboration information is generated based on patient information, etc. stored in a medical collaboration DB 244 included in the storage unit 24 of the medical institution terminal 20 at the medical institution 200 participating in medical collaboration. The medical collaboration information is collected from the medical institution terminal 20 by a patient information, etc. data collection application 101 in the medical collaboration information module 100 of the medical collaboration server 10, converted into a predetermined format by a collaboration data generation application 102, and stored in the storage unit 12. Note that the patient information, etc. and medical collaboration information may be information other than that shown in FIG. 5 as long as it can be used for medical collaboration.

[0046] The medical cooperation information includes, for example, "patient information," "medical treatment information," "patient-related information," and "medical institution information."

[0047] "Patient information" includes, for example, "patient ID," "name," "address," "contact information," "authentication information," and "related parties and relationships." This information is used to identify the patient as well as those related to the patient. For example, "contact information" is contact information including a phone number and email address. "Authentication information" is login information for various apps and setting information for the range of accessible information. "Related parties and relationships" refers to the scope of responsibilities of relatives and patient-related parties 3 who are involved in the patient's medical care, and the work they do in their relationship with the patient.

[0048] The "related person / relationship" that identifies the patient-related person 3 is registered by being input by the medical staff 2 at the medical institution terminal 20. For example, for the patient-related person 3 who is the patient's guardian, the guardian's information confirmed by the patient on a medical questionnaire is input. Also, as will be described later, when a doctor refers a patient to another doctor, the referring medical institution 200 inputs information about the other doctor to the "related person / relationship." The "related person / relationship" may be linked to detailed information about the patient-related person 3 by including a "related person ID" that will be described later.

[0049] "Medical information" includes, for example, "registration date and time," "symptoms and progress," "examination findings / orders," "test results," "medical examination appointment," "nursing progress record," "nursing summary," "dietary intake during hospitalization," "vital information," "treatment policy," and "visit information." "Medical information" is accumulated through medical treatments and other procedures performed on patients from time to time. As a result, "medical information" is managed so that it is clear when the patient was examined and registered for symptoms and progress. "Visit information" also includes the dates the patient previously visited the medical institution 200 and the future date of the patient's next visit.

[0050] "Patient-related person information" includes, for example, "related person ID," "job area," "name," "address," "contact information," and "authorization information." This "patient-related person information" makes it possible to identify the relationships between related people surrounding a patient, who can be asked to perform what tasks, where they are, and where they can be contacted to make requests. "Patient-related person information" is also used, for example, as authentication information for patient-related people 3 to use the medical collaboration system 1.

[0051] The "medical institution information" includes, for example, a "medical institution ID," a "name," a "location," and a "contact information." This information identifies which medical institution 200 sent the "patient information" and "treatment information" sent to the medical collaboration information module 100 of the medical collaboration server 10.

[0052] (Processing flow for push notifications) 6 is a sequence diagram showing an example of the processing flow in the medical collaboration system 1. In this processing, the medical collaboration server 10 sends a push notification of medical collaboration information to the patient-related person terminal 30 of the patient-related person 3. In other words, in the medical collaboration system 1, the medical collaboration information is sent to the patient-related person 3 as push notification information. Below, as an example, a case will be described in which the medical collaboration server 10 sends a push notification of the next visit date and time to the patient-related person terminal 30a of the patient based on the patient information etc. received from the medical institution terminal 20a of the medical institution 200a shown in FIG. 1.

[0053] In this process, an app for receiving push notifications to use the medical collaboration system 1 may be downloaded and installed on the patient-related person terminal 30a of the patient-related person 3a who is the patient to whom the push notification is sent from the medical institution terminal 20a of the medical institution 200a. Also, the process may be performed using a dedicated device for this process.

[0054] In step S101, when patient information and medical treatment information are input by operating the input unit 22 of the medical institution terminal 20a, etc., and thus patient information and the like is generated, the control unit 25 stores data relating to the information in the patient information DB 241 and the medical treatment information DB 242 in the storage unit 24. In this example, when the patient information and hospital visit information are input through the input unit 22, the patient information is stored in the patient information DB 241, and the hospital visit information is stored in the medical treatment information DB 242.

[0055] In step S102, the control unit 25 stores the patient information and the like stored in the patient information DB 241 and the medical treatment information DB 242 in the medical cooperation DB 244 so that the patient information and the like can be used as medical cooperation information. In this example, information regarding the patient's next visit to the hospital is stored.

[0056] In step S103, the control unit 25 transmits the patient information and medical treatment information stored in the medical cooperation DB 244 to the medical cooperation server 10 via the network NW and the communication unit 21. The medical cooperation server 10 receives the patient information via the communication unit 11. As a result, the control unit 13 of the medical cooperation server 10 collects the patient information and medical treatment information using the patient information etc. data collection app 101 and stores it in the storage unit 12. In this manner, a configuration may be adopted in which the patient information etc. data collection app 101 automatically operates 24 hours a day to collect cooperation information generated in the medical institution terminal 20a. Note that the control unit 13 may collect patient information etc. by periodically (for example, once a day) querying the medical institution terminal 20a using the patient information etc. data collection app 101. Alternatively, the collected patient information etc. may be stored in the shared data market 110 in real time and stored in the storage unit 12 so that it can be referenced by modules 122 to 125 for various applications.

[0057] In step S104, the control unit 13 generates medical collaboration information in the linked data generation app 102 based on the patient information and medical information stored in the storage unit 12. For example, in this process, to send a push notification to the patient, the control unit 13 reads the patient's name and contact information from the patient information, the hospital visit information from the medical information, and all information from the medical institution information from the storage unit 12. The control unit 13 then generates the medical collaboration information in the form of a message encouraging the patient to visit the hospital, such as "Dear Mr. / Ms. XX, your next appointment is scheduled for XX month, XX day, XX hour. Please come during business hours. XX Hospital (XX City, XX Address, XX-XXXX)." The linked data generation app 102 also sets the sending date and time of this message to a date and time, such as "6:00 p.m. the day before" included in the hospital visit information. The linked data generation app 102 also sets the patient's contact information as the message recipient. The contact information may be an email address or an ID on the push notification module 122.

[0058] In step S105, the control unit 13 stores the generated medical cooperation information, which is the message, the transmission date and time, and the transmission destination, in the push notification DB 111 in the shared data market 110 of the storage unit 12.

[0059] In step S106, the control unit 13 reads the message from the memory unit 12 when the sending date and time stored in the push notification DB 111 of the memory unit 12 arrives using the push notification module 122 of the service module 120, and sends the message to the patient's contact information via the communication unit 11.

[0060] In step S107, in the patient-related person terminal 30, the control unit 35 receives the message via the network NW and the communication unit 31. The control unit 35 also stores the received message in the storage unit 34 and displays a notification of the message reception on the display unit 33. As a result, when the patient, who is the user of the patient-related person terminal 30, performs an operation on the input unit 32 to display a message, the control unit 35 reads the message from the storage unit 34 and displays it on the display unit 33. As a result, a message encouraging the patient-related person 3, who is the patient, to visit a hospital, which is medical cooperation information, can be provided by push notification at an appropriate time. Note that the push notification described above may be performed when patient information, etc., is generated.

[0061] In this way, according to the medical collaboration system 1, medical collaboration information is provided at a convenient time by push notification, without the patient-related person 3 having to perform any special operations to collect information. Therefore, for example, a patient who is a patient-related person 3 can use this to receive medical treatment, and patient information and the like can be provided as medical collaboration information with increased added value.

[0062] (Processing flow when sharing information) FIG. 7 is a sequence diagram showing the flow of processing as another example in the medical collaboration system 1. In this processing, the medical collaboration server 10 converts the medical collaboration information into shared information whose content varies depending on the relationship between the patient and the patient of the patient-related person 3. In other words, the medical collaboration system 1 shares information whose content varies depending on the relationship between the patient and the patient of the patient-related person 3. As an example, the following describes a case where a patient referred by a doctor at medical institution 200a visits medical institution 200b based on patient information, etc. received from medical institution terminal 20a of medical institution 200a shown in FIG. 1, and the doctor at medical institution 200b views medical collaboration information (letter of referral) generated from the patient information, etc.

[0063] In this process, it is assumed that an application for the information viewing module 123 for using the medical cooperation system 1 is installed and authentication information is registered on the patient-related person terminal 30b operated by a doctor who is a patient-related person 3b who receives a referral from the medical institution terminal 20a owned by the medical institution 200a shown in Fig. 1. The process may also be performed using a dedicated device for this process.

[0064] The operation of the functional blocks in the process of generating and saving medical cooperation information based on patient information, etc. collected from the medical institution terminal 20a in steps S201 to S205 in Fig. 7 is the same as the operation of the functional blocks in the process of generating and saving medical cooperation information based on patient information, etc. collected from the medical institution terminal 20a in steps S101 to S105 in Fig. 6. Therefore, the following mainly describes the differences in the operations of the people involved in the process and the specific processing flow.

[0065] In steps S201 and S202, the doctor also registers "persons involved and relationships" as patient information. That is, for example, medical worker 2a, who is a doctor in FIG. 1, uses medical institution terminal 20a to register medical worker 2b, who is a doctor at medical institution 200b to which the patient is referred, as the doctor of the referral destination. That is, medical worker 2b, who is a doctor, is registered as person involved 3b of the patient of the referral destination. Medical worker 2a also registers patient information, etc., regarding the patient to be referred.

[0066] In steps S203 to S205, patient information, medical treatment information, patient-related information, and medical institution information are collected as medical treatment information in the medical treatment information module 100, and medical treatment information is generated. In this process, in step S204, information in a format for patient introduction corresponding to a medical treatment information report and the specific medical treatment information attached thereto is generated as medical treatment information. In step S205, this medical treatment information is saved in the patient introduction DB 112a.

[0067] 1, for example, when a patient visits the medical institution 200b, the patient gives his or her name, and in step S206, the patient-related person 3b, who is a doctor, operates the input unit 32 while looking at the display unit 33 of the patient-related person terminal 30b to access the application of the information viewing module 123 of the medical collaboration system 1 and search for medical collaboration information related to the patient. At this time, the control unit 35 requests viewing of the medical collaboration information related to the patient via the communication unit 31 and the network NW.

[0068] In response to this, the control unit 13 of the medical collaboration server 10 processes this access using the shared data market 110 and the service module 120. In step S207, when a viewing request is made to the information viewing module 123 of the service module 120, the control unit 13 requests authentication by the security module 121, and continues processing if the authentication information is appropriate. The information viewing module 123 then searches the patient referral DB 112a and reads information for patient referral related to the patient. Note that this type of information is highly confidential personal information, so the security module 121 may take measures to prevent information leaks by requiring two-step authentication or biometric authentication from the patient-related person terminal 30 that has made the viewing request.

[0069] In step S208, the control unit 13 uses the information viewing module 123 to read information about the referral letter stored in the storage unit 12, and transmits it to the patient-related person terminal 30b via the communication unit 11 and the network NW for disclosure.

[0070] In step S209, in the patient-related person terminal 30b, the control unit 35 causes the display unit 33 to display the medical cooperation information regarding the referral letter received via the network NW and the communication unit 31. This allows the medical worker 2b, who is a doctor, to view the information regarding the referral letter as the patient-related person 3b.

[0071] 7, the process of introducing a patient from a medical worker 2a who is a doctor to a medical worker 2b (patient-related person 3b) who is also a doctor has been described, but the patient-related person 3b to whom the patient is introduced may be a medical worker 2 other than a doctor who is involved in medical care or nursing. In such cases, the necessary medical cooperation information can be provided by the introduction in the same way. In this case, information can be shared in the same way using databases 112b to 112d other than the patient introduction DB 112a.

[0072] As described above, the medical cooperation system 1 can smoothly provide highly convenient medical cooperation information according to the relationship of the patient-related person 3 with the patient while ensuring security.

[0073] In the above process, an example has been described in which when a patient visits the medical institution 200b, the medical worker 2b, who is a doctor, uses the patient-related person terminal 30b as the patient-related person 3b to view information about the referral letter. However, the patient-related person 3b may request and view medical cooperation information about the patient referral in advance.

[0074] (Anshin Service Processing Flow) 8 is a sequence diagram showing the flow of processing as yet another example in the medical collaboration system 1. In this processing, the medical collaboration server 10 converts the medical collaboration information into alarm information that is notified to the patient-related person terminal 30 operated by a patient-related person 3 other than the patient, depending on the patient's behavior after notification to the patient-related person terminal 30 operated by the patient.

[0075] As an example, the following describes a case where the medical cooperation server 10 shown in Fig. 1 calls the telephone of the patient-related person terminal 30c of an elderly patient to notify the patient of hospital visit information as a push notification, but the call is not received, and then sends a push notification to the patient-related person terminal 30d of the patient-related person 3 who is a family member. In this way, the process shown in Fig. 8 can provide a peace of mind service that allows patients to be watched over.

[0076] This process will be described on the assumption that no dedicated app is installed on the medical institution terminal 20a owned by the medical institution 200a shown in Fig. 1, the patient-related person terminal 30c which is a wired telephone operated by the patient-related person 3c who is a patient, and the patient-related person terminal 30d which is a personal computer operated by the patient-related person 3 who is a family member of the patient. Alternatively, an app for using the medical collaboration system 1 may be downloaded and installed on these patient-related person terminals 30. Furthermore, the process may be performed using a dedicated device for this process.

[0077] The operation of the functional blocks in the process of sending a push notification from the medical institution terminal 20a to the patient-related person terminal 30c via the medical collaboration server 10 in steps S301 to S306 in Fig. 8 is the same as the operation of the functional blocks in the process of sending a push notification from the medical institution terminal 20a to the patient-related person terminal 30a via the medical collaboration server 10 in steps S101 to S106 in Fig. 6. For this reason, the following mainly describes the differences in the operations of the people involved in the process and the specific processing flow.

[0078] In steps S301 and S302, the medical practitioner 2 who is a doctor also registers "related persons and relationships" as patient information. For example, the medical practitioner 2a who is a doctor in FIG. 1 uses the medical institution terminal 20a to register a family member (e.g., a son) as a patient-related person 3d in the patient information. He also registers information about that family member as patient-related information.

[0079] In steps S303 to S305, the medical cooperation information module 100 collects patient information, medical treatment information, patient-related information, and medical institution information as medical cooperation information, and generates medical cooperation information in a predetermined format. As the medical cooperation information in this process, the above-mentioned message encouraging the patient to visit the hospital is generated and saved together with the telephone number to which the message is sent and the date and time of sending (date and time of the call). In this process, since the patient-related terminal 30c is a wired telephone, the message to be played after an incoming call is created as audio data.

[0080] In step S304, the linked data generation app 102 creates a message for a peace of mind alarm (alarm information) based on the patient-related person information and other information. For example, to notify the patient of the peace of mind alarm, the app reads the patient's name from the patient-related person information, the patient's name and contact information from the patient-related person information, and all information from the medical institution information, and generates the peace of mind alarm message as medical collaboration information. As an example, the medical collaboration information generated may include the following message: "Dear Mr. / Ms. XX, this is a message from XX Hospital. We tried to call your family member, Mr. / Ms. XX, at XX-XXXX today to ask you to visit the hospital, but no call was received. Mr. / Ms. XX may be feeling unwell, so please check." In step S305, the message data and the contact information of the family member to whom the message is to be sent are stored in the peace of mind service DB 113. Note that this message may also be generated when a push notification, as described below, is sent.

[0081] In step S306, the control unit 13 uses the push notification module 122 to make a push notification call to the patient-related person terminal 30c, which is the patient's wired telephone, via the communication unit 11 and the network NW, which is a wired telephone line. As a result, if the patient is healthy, the patient-related person terminal 30c, which is a wired telephone, should receive the push notification message. However, if the patient is unwell and unable to answer the call, the call will not be received and will be missed (a missed call). Of course, there is no problem if the patient is absent or asleep and does not receive the call. However, if the patient is at home and does not receive the call, it may be that the patient is experiencing some kind of unwellness. Therefore, by sending push notifications multiple times at predetermined intervals (e.g., one hour), if the patient continues to receive missed calls despite receiving the push notification calls a predetermined number of times, it can be determined that the patient is likely to be in poor health.

[0082] In step S307, the control unit 13 counts the number of missed calls and stores the count in the memory unit 12. If the count exceeds a predetermined number (e.g., three), in step S308, the control unit 13 causes the reassurance service module 124 to use the push notification module 122 to send a push notification of a reassurance alarm message to the patient-related person terminal 30d, which is the patient's family member. As a result, the patient-related person 3d, who is the family member, can receive and view the reassurance alarm on the patient-related person terminal 30d and quickly become aware of the possibility that the family member may be in poor health. This allows the patient-related person 3d, who is the family member, to check on the patient's health by visiting the patient's family member's home. This reduces the number of situations in which the patient's family member, who lives far away, becomes worried about the patient's poor health, and provides a service that reassures them. The patient-related person terminal 30 that sends the push notification of the reassurance alarm may be a terminal used by a caregiver at a home-visit care facility located near the patient.

[0083] Furthermore, the information to be sent by push notification may be not only hospital visit information but also medication information. In this case, medical cooperation information is registered in the push notification DB 111 so that push notifications are sent in accordance with the timing of when the patient takes their medication. In this case, the pharmacy participates in the medical cooperation system 1 as the medical institution 200 and registers the medication information related to the patient as medical information, or registers the medication information together with the medical information.

[0084] This allows the patient to register medication information, such as which medication to take, when, and how often, rather than sending a push notification urging the patient to visit the hospital, so that the linked data generation app 102 can send push notifications based on the medication information to coincide with the patient's medication schedule. Even in this case, if the family member does not receive a message informing them of the medication information, a reassurance alarm can be sent via push notification. The push notification may be a message on the app, in which case the message will not be opened. In this case, if a predetermined number of consecutive medication messages remain unopened, the reassurance service module 124 determines that the patient may be in poor health and sends a reassurance alarm via push notification.

[0085] In this way, the medical collaboration server 10 notifies the patient-related person terminal 30 operated by the patient-related person 3 of alarm information as medical collaboration information, depending on the patient's behavior after the medical collaboration information is notified to the patient-related person terminal 30 operated by the patient.

[0086] As explained above, according to the medical collaboration system 1, when a patient does not open a call or message as he or she should, alarm information can be shared with patient-related parties 3 other than the patient, thereby reducing the patient-related parties 3's anticipated concerns about the patient's condition.

[0087] Furthermore, the safety service module 124 for making a safety alarm call may be provided in the communication module 125. Furthermore, the communication module 125 may be provided with a push notification function.

[0088] (Hardware configuration diagram) 9 is a block diagram showing the hardware configuration of the medical collaboration server 10. The medical collaboration server 10 is implemented in a computer 901. The computer 901 includes a CPU 902, a main storage device 903, an auxiliary storage device 904, and an interface 905.

[0089] The operation of each component of the medical collaboration server 10 is stored in the form of a program in the auxiliary storage device 904. The CPU 902 reads the program from the auxiliary storage device 904, loads it into the main storage device 903, and executes the above-mentioned processing in accordance with the program. The CPU 902 also allocates a storage area in the main storage device 903 in accordance with the program. Specifically, the program is a patient information sharing program that causes the computer 901 to share medical collaboration information, including patient information, between the medical professionals 2 and the patient-related parties 3.

[0090] The auxiliary storage device 904 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, and a semiconductor memory connected via the interface 905. When the program is distributed to the computer 901 via a network, the computer 901 that receives the program may load the program into the main storage device 903 and execute the processing.

[0091] The program may also be one that realizes some of the functions described above. Furthermore, the program may be one that realizes the functions described above in combination with other programs already stored in the auxiliary storage device 904, that is, a so-called differential file (differential program). The hardware configuration shown in FIG. 9 may also be the same configuration for the medical institution terminal 20 and the patient-related terminal 30. As with the medical collaboration server 10 described above, the operation of each component of the medical institution terminal 20 and the patient-related terminal 30 is also realized by a CPU in accordance with the programs stored in the auxiliary storage device.

[0092] (Explanation of effect) In the medical collaboration system 1 according to the first embodiment, the medical collaboration information can be made accessible at any time by the patient-related person terminal 30. Furthermore, the medical collaboration information can be provided automatically without the medical-related person 2 having to input it specifically. This allows the medical-related person 2 and the patient-related person 3 to efficiently share the medical collaboration information. Furthermore, the medical collaboration information can be kept up to date at any time.

[0093] In today's medical field, all involved parties recognize the importance of information sharing in medical care and nursing care. However, there are problems, such as additional work for information providers to provide information and the significant time and effort required for recipients of medical care sharing information. As a result, current information sharing is not carried out smoothly. However, with the above-described medical collaboration system 1, the system automatically provides information for use, reducing the workload of medical professionals 2. Patient-related parties 3 can easily obtain useful information by receiving the necessary information in real time. This allows them to focus more on their primary duties. As a result, smooth information sharing can provide high-quality medical / nursing care services that satisfy patients and their guardians with peace of mind.

[0094] <Embodiment 2> In the first embodiment, the locations of the medical institutions 200 and the patient-related parties 3 are not particularly limited. However, the medical cooperation system 1 can promote regional medical cooperation in which the medical institutions 200 and the patient-related parties 3 are located in the same or nearby areas.

[0095] 10 is a conceptual diagram showing an example of regional medical collaboration by the medical collaboration system 1 according to embodiment 2. In this example, it is assumed that a medical institution 200a that plays a central role in a certain prefecture collaborates with nearby medical institutions 200b, 200c, and 200d such as hospitals and clinics, and that medical collaboration information is provided to bases 300a, 300b, 300c, and 300d where patient-related parties 3 are located.

[0096] In this example, the medical collaboration server 10 generates medical collaboration information based on patient information and the like received from medical institutions 200a, 200b, 200c, and 200d via the network NW, and shares the information with patient-related party terminals 30 at bases 300a, 300b, 300b, and 300b where patient-related parties 3 are located who are located in the same city, town, or village as the location of the medical institution 200a, in a city, town, or village adjacent to the location of the medical institution 200a, or in a city, town, or village close to the location of the medical institution 200a. Of course, medical institutions 200b, 200c, and 200d may also share medical collaboration information as bases 300 where patient-related parties 3 are located. In this way, regional medical collaboration can be promoted by sharing medical collaboration information within the same or nearby area.

[0097] In the medical collaboration system 1 according to the second embodiment, by sharing medical collaboration information with patient-related persons 3 in the same area as the medical institution 200 or in a neighboring area, the medical collaboration information can be used by patient-related persons 3 who are likely to visit the hospital and are related to the medical institution as a regional medical institution. This reduces the burden of travel on the patient-related persons 3 by sharing the medical collaboration information only with nearby patient-related persons 3. Furthermore, nurses who provide medical care by visiting patients in home medical care, etc., can also visit nearby patients. In this way, the medical collaboration system 1 can facilitate regional medical collaboration.

[0098] The present technology can be configured as follows: (1) A medical cooperation server that shares patient information and medical treatment information of patients who are receiving treatment at a medical institution with a medical institution terminal owned by the medical institution and a patient-related terminal operated by a patient-related person, including a patient, via a network, an updating means for managing items of information to be used for medical cooperation among the patient information and medical treatment information stored in the medical institution terminal, and for collecting and updating the patient information and medical treatment information when the patient information and medical treatment information set to be used for medical cooperation is generated or updated; a generating means for generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; A medical collaboration server comprising: a sharing means for storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient. (2) The medical collaboration server described in (1), in which the medical collaboration information is shared with the patient-related person terminals of the patient-related person located in the same city, town, or village as the medical institution, in a city, town, or village adjacent to the medical institution, or in a city, town, or village close to the medical institution. (3) The medical collaboration server according to (1) or (2), wherein the update means collects and updates the patient information and medical treatment information from the plurality of medical institution terminals. (4) A medical collaboration server described in any one of (1) to (3), wherein the generating means generates the medical collaboration information using the patient information, the medical treatment information, and patient-related person information regarding the patient-related person. (5) A medical collaboration server according to any one of (1) to (4), wherein the medical collaboration information is push notification information that is pushed to the patient-related person's patient-related terminal. (6) The medical collaboration server according to any one of (1) to (5), wherein the medical collaboration information is shared information whose content varies depending on the patient-related person's relationship with the patient. (7) A medical collaboration server described in any one of (1) to (6), wherein the medical collaboration information is alarm information that is notified to the patient-related person terminal operated by the patient-related person in accordance with the patient's behavior after notification to the patient-related person terminal operated by the patient. (8) A medical collaboration system comprising a medical institution terminal owned by a medical institution, a patient-related person terminal operated by a patient-related person including a patient, and a medical collaboration server, wherein the medical institution terminal, the patient-related person terminal, and the medical collaboration server share patient information and medical treatment information regarding the patient undergoing treatment at the medical institution via a network, and the medical collaboration server: an updating means for managing items of information to be used for medical cooperation among the patient information and medical treatment information stored in the medical institution terminal, and for collecting and updating the patient information and medical treatment information when the patient information and medical treatment information set to be used for medical cooperation is generated or updated; a generating means for generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; A medical collaboration system comprising: a sharing means for storing the medical collaboration information separately according to the relationship with the patient and the purpose of use so that it can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient. (9) A medical cooperation method in which a medical institution terminal owned by a medical institution, a patient-related person terminal operated by a patient-related person including a patient, and a medical cooperation server share patient information and medical treatment information of the patient who is receiving treatment at the medical institution via a network, The medical collaboration method includes: a step of managing items of information to be used for medical cooperation among the patient information and medical information stored in the medical institution terminal, and collecting and updating the patient information and medical information when the patient information and medical information set to be used for medical cooperation is generated or updated; generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; and storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient. (10) A program executed by a medical cooperation server having a control unit, for sharing patient information and medical treatment information of a patient who is receiving treatment at the medical institution via a network between a medical institution terminal owned by the medical institution and a patient-related person terminal operated by a patient-related person including a patient, and the medical cooperation server, The program causes the control unit to a step of managing items of information to be used for medical cooperation among the patient information and medical information stored in the medical institution terminal, and collecting and updating the patient information and medical information when the patient information and medical information set to be used for medical cooperation is generated or updated; generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; and storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient.

[0099] The aspects of the present disclosure are not limited to the individual embodiments described above, but include various modifications that may be conceived by those skilled in the art, and the effects of the present disclosure are not limited to the above-described contents. In other words, various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and spirit of the present disclosure, which is derived from the contents defined in the claims and their equivalents. [Explanation of symbols]

[0100] 1 Medical Collaboration System 2, 2a, 2b Medical personnel 3,3a,3b,3c,3d Patient relations 10 Medical Collaboration Server 11 Communications Department 12 Storage section 13 Control Unit 20, 20a, 20b Medical institution terminal 21 Communications Department 22 Input section 23 Display section 24 Memory section 25 Control Unit 30, 30a, 30b, 30c, 30d Patient-related terminal 31 Communications Department 32 Input section 33 Display section 34 Storage section 35 Control Unit 36 Audio output section 100 Medical Collaboration Information Module 101 Patient information data collection app 102 Collaborative Data Generation App 110 Shared Data Market 111 Push Notification DB 112 Shared information DB 112a Patient referral database 112b Patient / Parent DB 112c Nursing care database 112d Visiting nursing DB 113 Reliable Service DB 114 Communication DB 120 Service Module 121 Security Module 122 Push Notification Module 123 Information Viewing Module 124 Reliable Service Module 125 Communication Module 200, 200a, 200b, 200c, 200d Medical Institutions 241 Patient information DB 242 Medical information DB 243 Accounting Information DB 244 Medical Collaboration Database 245 Management Information DB 300, 300a, 300b, 300c, 300d bases 901 Computer 902 CPU 903 Main storage 904 Auxiliary storage 905 Interface NW Network

Claims

1. A medical cooperation server that shares patient information and medical treatment information of patients who are receiving treatment at a medical institution with a medical institution terminal owned by the medical institution and a patient-related person terminal operated by a patient-related person including a patient via a network, an updating means for managing items of information to be used for medical cooperation among the patient information and medical treatment information stored in the medical institution terminal, and for collecting and updating the patient information and medical treatment information when the patient information and medical treatment information set to be used for medical cooperation is generated or updated; a generating means for generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; A medical collaboration server comprising: a sharing means for storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient.

2. The medical collaboration server of claim 1, wherein the medical collaboration information is shared with the patient-related party terminals of the patient-related party located within the same municipality as the medical institution, within a municipality adjacent to the medical institution, or within a municipality close to the medical institution.

3. The medical cooperation server according to claim 1 , wherein the update unit collects and updates the patient information and medical treatment information from the plurality of medical institution terminals.

4. The medical collaboration server according to claim 1 , wherein the generating means generates the medical collaboration information using the patient information, the medical treatment information, and patient-related person information relating to the patient-related person.

5. The medical collaboration server according to claim 1 , wherein the medical collaboration information is push notification information that is sent by push notification to the patient-related terminal of the patient-related person.

6. The medical collaboration server according to claim 1 , wherein the medical collaboration information is shared information whose content varies depending on the relationship of the patient-related person with the patient.

7. 2. The medical collaboration server according to claim 1, wherein the medical collaboration information is alarm information that is notified to the patient-related person terminal operated by the patient-related person in accordance with the patient's behavior after notification to the patient-related person terminal operated by the patient.

8. A medical collaboration system comprising a medical institution terminal owned by a medical institution, a patient-related person terminal operated by a patient-related person including a patient, and a medical collaboration server, wherein the medical institution terminal, the patient-related person terminal, and the medical collaboration server share patient information and medical treatment information of the patient who is receiving treatment at the medical institution via a network, and the medical collaboration server: an updating means for managing items of information to be used for medical cooperation among the patient information and medical treatment information stored in the medical institution terminal, and for collecting and updating the patient information and medical treatment information when the patient information and medical treatment information set to be used for medical cooperation is generated or updated; a generating means for generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; A medical collaboration system comprising: a sharing means for storing the medical collaboration information separately according to the relationship with the patient and the purpose of use so that it can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient.

9. A medical cooperation method in which a medical institution terminal owned by a medical institution, a patient-related person terminal operated by a patient-related person including a patient, and a medical cooperation server share patient information about the patient undergoing treatment at the medical institution and medical treatment information of the patient via a network, The medical collaboration method includes: a step of managing items of information to be used for medical cooperation among the patient information and medical information stored in the medical institution terminal, and collecting and updating the patient information and medical information when the patient information and medical information set to be used for medical cooperation is generated or updated; generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; and storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient.

10. A program executed by a medical cooperation server having a control unit, for sharing patient information and medical treatment information of patients who are receiving treatment at the medical institution via a network between a medical institution terminal owned by the medical institution and a patient-related person terminal operated by a patient-related person including a patient, and the medical cooperation server, The program causes the control unit to a step of managing items of information to be used for medical cooperation among the patient information and medical information stored in the medical institution terminal, and collecting and updating the patient information and medical information when the patient information and medical information set to be used for medical cooperation is generated or updated; generating medical cooperation information using the collected patient information and medical treatment information when the patient information and medical treatment information used for medical cooperation are updated; and storing the medical collaboration information distinguished according to the relationship with the patient and the purpose of use so that the information can be used on the patient-related person terminal of the patient-related person who has a relationship with the patient.

Images