Information exchange method, program, and information system

Abstract

To make it easier for a plurality of medical professionals to work together flexibly depending on a patient's situation.SOLUTION: An information exchange method for exchanging information about a patient among a plurality of medical professionals using an information system includes receiving a group creation request that is based on at least one of patient identification information that identifies the patient and professional attribute information related to medical expertise required to provide medical care to the patient, searching for medical professionals who match the group creation request, creating, according to search results, a group that includes at least one of medical professionals in charge of the patient and medical professionals who have the medical expertise required to provide medical care to the patient, and a medical professional who requested the group creation request, outputting template data corresponding to the created group, and transmitting information about the patient inputted to input fields of the template data on a terminal of one medical professional in the group to terminals of the other medical professionals in the group.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a method, a program, and an information system for exchanging information about a patient among medical staff.

Background Art

[0002] Patent Document 1 describes a home care support system that collectively manages information on patients undergoing home treatment on a cloud server and allows multiple stakeholders to mutually use the collectively managed information. In this system, a patient and a person providing medical care for the patient are registered in the system as team members of a single team by a system administrator. Team members include patients, their families, doctors, nurses, physical therapists, home helpers, etc. In this system, a communication terminal possessed by each team member is connected to a cloud server, and patient conditions (facial expressions, blood pressure, physical condition, etc.), and medical care provided to the patient in response thereto (instructions, massages, medication, etc.) are registered as care records from the communication terminals of each team member into the storage unit of the cloud server, and each team member browses the registered information using the communication terminal. Further, in this system, when a team member registers or browses a care record, communication such as questions and comments to other team members is registered on the screen corresponding to the care record, and each team member can browse the registered communication using the communication terminal.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the medical field, it is required that multiple medical staff can flexibly cooperate according to the patient's condition.

[0005] As medical care becomes more advanced and specialized, when providing advanced nursing care such as chronic disease care and end-of-life care, specialized knowledge and skills corresponding to individual diseases are required. Therefore, for example, when a patient who was hospitalized in a hospital is to receive home care, it is desirable that a plurality of medical workers, such as visiting nurses dispatched from a visiting nursing station and specialized nurses on the hospital side who have specialized knowledge and skills regarding the care of the patient, can cooperate. In particular, depending on the type and progression of the disease, a patient may require multiple types of care. Therefore, even for the care of the same patient, it is required that medical workers with expertise corresponding to the content of the care and medical workers in charge of the care can cooperate flexibly.

[0006] However, in the system described in Patent Document 1 above, it is necessary to register team members in advance by the system administrator. When using this system to provide highly specialized home care as described above, for example, it is difficult for the system administrator to fully understand the details such as the specialties, assigned patients, and names of a plurality of medical workers belonging to different medical institutions such as hospitals and visiting nursing stations, and then register team members according to the patient.

[0007] An object of the present invention is to provide a method, program, and information system for exchanging information about a patient among medical workers, which facilitate flexible cooperation among a plurality of medical workers according to the situation of the patient.

Means for Solving the Problems

[0008] The information exchange method of the present invention is an information exchange method for exchanging information about a patient among a plurality of medical staff by an information system (1). The method receives a group creation request based on at least one of patient identification information for identifying the patient and specialized attribute information regarding the specialty of medicine required for treating the patient, searches for medical staff who match the group creation request, creates a group including at least one of the medical staff in charge of the patient and the medical staff having the specialty of medicine required for treating the patient, and the medical staff who requested the group creation request according to the search result, outputs template data corresponding to the created group, and transmits information about the patient input in the input items of the template data at the terminal (3) of one medical staff in the group to the terminals (3) of other medical staff in the group.

[0009] The program of the present invention is a program for causing a computer to function as an information processing apparatus (2) included in an information system for exchanging information about a patient among a plurality of medical staff. The program receives a group creation request based on at least one of patient identification information for identifying the patient and specialized attribute information regarding the specialty of medicine required for treating the patient, searches for medical staff who match the group creation request, creates a group including at least one of the medical staff in charge of the patient and the medical staff having the specialty of medicine required for treating the patient, and the medical staff who requested the group creation request according to the search result, outputs template data corresponding to the created group, and transmits information about the patient input in the input items of the template data at the terminal (3) of one medical staff in the group to the terminals (3) of other medical staff in the group, and is for causing a computer to function as the information processing apparatus (2).

[0010] The information system of the present invention is an information system (1) for exchanging information about a patient among a plurality of medical staff, including an information processing device (2) and a terminal (3) of the medical staff. The information processing device (2) receives a group creation request from the terminal (3) of the medical staff based on at least one of patient identification information for identifying the patient and specialty attribute information regarding the specialty of medicine required for treating the patient, searches for medical staff who match the group creation request, and creates a group including at least one of the medical staff in charge of the patient and the medical staff having the specialty of medicine required for treating the patient according to the search result, the medical staff who requested the group creation request, outputs template data according to the created group, and transmits information about the patient input in the input items of the template data at the terminal (3) of one medical staff in the group to the terminals (3) of other medical staff in the group.

Advantages of the Invention

[0011] According to the present invention, it is possible to provide a method, a program, and an information system for exchanging information about a patient among medical staff, which facilitate flexible cooperation among a plurality of medical staff according to the situation of the patient.

Brief Description of the Drawings

[0012]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40

Figure 41

Figure 42

Figure 43

Figure 44

Figure 45

Figure 46

Modes for Carrying Out the Invention

[0013] 〔Overview of Information System 1〕 The information system 1 according to this embodiment is a communication system for exchanging information about patients among medical staff within a group including a plurality of medical staff. The main feature of the information system 1 is to facilitate the flexible cooperation of a plurality of medical staff according to the patient's situation. By using the information system 1, for example, information about patients can be exchanged among medical staff who do not know each other and belong to different medical institutions, so that medical staff can cooperate flexibly in patient care. "Information about patients" includes, for example, information about medical treatment given to patients, information about patient care, information about the patient's family circumstances, and so on. Hereinafter, the information about patients to be exchanged is simply referred to as "message".

[0014] 〔Medical Staff〕 The first typical example of medical staff is medical staff with expertise in a specific field of medicine, such as a specialized nurse, a certified nurse, a physical therapist, a doctor, a pharmacist, a helper, etc. The medical staff of the first typical example is associated with "specialty attribute information" indicating expertise in medicine.

[0015] The specialty attribute information may be information indicating a medical specialty qualification. The specialty attribute information may be information indicating expertise in a specific field of nursing. The specialty attribute information may be information indicating the type of nursing. Examples of the specialty attribute information include "WOC" (Wound Ostomy Continence), which is a specialty field related to the skin or excretion, "stoma care", which is a type of nursing related to stomas, "palliative care", which is a type of nursing for relieving physical or mental pain of cancer patients, etc., and "pharmacotherapy", which is represented by chemotherapy such as anticancer drug treatment.

[0016] In this embodiment, as a first typical example of medical staff, a specialized nurse who belongs to a medical institution (such as a hospital) where a patient is admitted, has expertise in a specific field of nursing, and is responsible for the care of the patient during hospitalization will be taken as an example for explanation. In the example shown by reference numeral 1001 in FIG. 1, a specialized nurse S1 belonging to the medical institution M1 is responsible for the care of patient A who is hospitalized in the medical institution M1. The specialized nurse S1 has expertise in, for example, WOC, and it is assumed that patient A has undergone, for example, a stoma operation. Note that after patient A is discharged from the hospital, the specialized nurse S1 is removed from the responsibility of caring for patient A.

[0017] A second typical example of medical staff is a medical staff member who does not have expertise in a specific field of medicine. In this embodiment, as the second typical example of medical staff, (1) a general nurse who belongs to the medical institution M1 and is responsible for the care of patients who visit the general outpatient department of the medical institution M1 after being discharged from the medical institution M1, and (2) a visiting nurse who belongs to a medical institution M2 different from the medical institution M1 (such as a visiting nursing station) and visits the home of a patient who has been discharged from the medical institution M1 to provide care will be taken as examples for explanation. In the example shown by reference numeral 1002 in FIG. 1, a general nurse G1 belonging to the medical institution M1 is responsible for the care of patient A who visits the general outpatient department of the medical institution M1 after being discharged. In the example shown by reference numeral 1003 in FIG. 1, a visiting nurse V1 belonging to the medical institution M2 is responsible for the visiting care of patient A at home after discharge.

[0018] The specialized nurse S1 may, for example, transmit specialized information regarding WOC about patient A or confirm the situation of patient A after discharge to the general nurse G1 or the visiting nurse V1. Similarly, when caring for patient A, the general nurse G1 or the visiting nurse V1 may, for example, seek advice or consultation regarding WOC or confirm the situation of patient A at the time of admission from other medical staff such as the specialized nurse S1.

[0019] 〔Main effects achieved by using Information System 1〕 As described above, in the case where a plurality of medical staff are involved in a target patient (especially when a plurality of medical staff belonging to different medical institutions are involved), conventionally, it has been difficult to exchange messages among medical staff unless they know each other's attribute information (specialty, assigned patients, contact information, etc.). However, by using the information system 1, it is possible to easily exchange messages regarding the target patient among medical staff who do not know each other's attribute information. In particular, it is possible to easily exchange messages among medical staff who do not know each other and belong to different medical institutions. As a result, a plurality of medical staff can flexibly cooperate according to the patient's situation.

[0020] Specifically, in the information system 1, in response to a group creation request from a medical staff, a group including at least one of "medical staff in charge of the target patient" and "medical staff having the specialty required for treating the target patient and belonging to a medical institution associated with the target patient" is created, and messages can be exchanged within the group. When the latter medical staff is included in the group, it becomes possible to exchange highly specialized information within the group. Note that the "medical institution associated with the target patient" is, for example, a medical institution that has provided highly specialized medical treatment to the target patient, a medical institution where the target patient has undergone surgery, a medical institution where the target patient has been admitted, etc.

[0021] The group may include a plurality of medical staff in charge of the same patient and / or a plurality of medical staff having specialties in the same field. Therefore, for example, even in a situation where a certain medical staff within the group is absent or busy and message exchange is difficult, there is a possibility of exchanging messages with any of the other medical staff within the group, so rapid information exchange is expected.

[0022] In the information system 1, a group is created in response to a group creation request from a medical staff member who is a user of the information system 1. It is not necessary for the system administrator to intervene in the creation of the group. For example, when a visiting nurse wants to receive advice from a specialist nurse during a home visit, a group is created in response to the request from the visiting nurse. Similarly, when a specialist nurse wants to convey specialized information to general nurses and visiting nurses, a group is created in response to the request from the specialist nurse.

[0023] [Example of Group Creation] An example of group creation will be described with reference to FIG. 2. FIG. 2 illustrates a group for providing stoma care to Patient A. For example, among the medical staff belonging to medical institutions M1 and M2, a group X1 conceptually shown in FIG. 2 can be created as a group including the medical staff in charge of Patient A or the medical staff having expertise in WOC.

[0024] Group X1 includes specialist nurses S1 and S2. The reason is that although specialist nurses S1 and S2 are not in charge of Patient A, they have expertise in WOC and belong to medical institution M1 where Patient A was hospitalized. It is preferable that group X1 includes the specialist nurse who was in charge of Patient A when Patient A was hospitalized in medical institution M1. The reason is that the specialist nurse who was in charge of Patient A knows the condition of Patient A at the time of hospitalization and can easily send useful messages for the care of Patient A. Also, it is preferable that group X1 includes a plurality of specialist nurses. The reason is that even if one specialist nurse cannot immediately answer a question from a general nurse due to reasons such as being in the middle of caring for a patient other than Patient A, there is a possibility that another specialist nurse can answer. Group X1 further includes general nurse G1 and visiting nurse V1. The reason is that although general nurse G1 and visiting nurse V1 do not have expertise in WOC, they are in charge of Patient A.

[0025] On the one hand, the specialized nurse S3 is not included in group X1. The reason is that the specialized nurse S3 is not in charge of patient A and does not have expertise in WOC. Similarly, the general nurse G2 and the visiting nurse V2 are not included in group X1. The reason is that the general nurse G2 and the visiting nurse V2 are not in charge of patient A and do not have expertise in WOC.

[0026] In the information system 1, one or more groups can be created for the same patient. Specifically, in the information system 1, groups can be created for each specialized attribute information of the medical treatment given to the patient. Thereby, message exchange is possible for each group according to the specialty. When the specialized attribute information is information indicating the type of nursing care, the information system 1 can create groups for each type of nursing care given to the patient. For example, when patient A requires palliative care in addition to WOC, in the information system 1, as shown in FIG. 3 for example, for patient A, a group X1 related to the above-mentioned WOC and a group X2 related to palliative care different from group X1 can be created. Group X2 includes the union of the medical staff in charge of patient A and the medical staff belonging to medical institution M1 and having expertise in palliative care. Specifically, as shown in FIG. 3, group X2 includes the specialized nurse S4, the general nurse G1, and the visiting nurse V1. The specialized nurse S4 does not take charge of patient A but has expertise in palliative care and belongs to medical institution M1.

[0027] The information system 1 may further create a group (hereinafter referred to as the general group) for exchanging information about general matters regardless of the specialty of the medical treatment given to the target patient. General matters are, for example, matters related to the family circumstances or economic circumstances of the target patient. The first typical example of the general group is a group that includes all of the medical staff in charge of the target patient. The second typical example of the general group is a group that includes all of the medical staff included in at least one of a plurality of groups already created for the target patient. The group X3 shown in FIG. 3 is the general group of the second typical example for patient A. The group X3 includes the specialized nurses S1, S2, S4, the general nurse G1, and the visiting nurse V1.

[0028] The general group may be created, for example, at the timing when a group for the target patient is created. For example, the group X3 may be created each time the groups X1 and X2 are created. Also, the general group may be created, for example, in accordance with a creation request by a medical staff member.

[0029] 〔Thread〕 In the information system 1, for each group, a "thread", which is a collection of posted messages, is created. In the present embodiment, different threads are created for each group. That is, there is a one-to-one correspondence between the group and the thread.

[0030] Medical staff included in the same group can exchange information by posting messages in the same thread. The information exchange can be performed, for example, in a conversation format using a chat function. FIG. 4 shows an example of the thread screen displayed on the terminal 3 used by the medical staff. In the thread screen 3646 shown in FIG. 4, in the field 3648, messages regarding the patient with the patient ID "P101" are being exchanged between the medical staff with the medical staff ID "N001" and the medical staff with the medical staff ID "N002". The details of the thread screen 3646 will be described later.

[0031] 〔Configuration Example of Information System 1〕 As shown in FIG. 2, the information system 1 has a configuration including a server 2 and a plurality of terminals 3. The server 2 is a computer owned by the operator who operates the information system 1, and is an information processing device that forms the core of the information system 1. The server 2 may be realized by one computer, or may be realized by distributing functions to a plurality of computers. The terminal 3 is a computer used by medical staff who use the information system 1, and is, for example, a smartphone, a tablet terminal, or a personal computer. The server 2 and the terminal 3 are communicably connected via a communication network 4 such as the Internet. The transmission and reception of messages between the terminals 3 are performed via the server 2 and the communication network 4.

[0032] 〔Configuration Example of Server 2〕 As shown in FIG. 5, the server 2 includes, for example, a communication device 21, a storage device 22, a processor 23, a RAM (Random Access Memory) 25, and a ROM (Read Only Memory) 26. The communication device 21 is an interface that communicates with the terminal 3 according to the control by the processor 23. The storage device 22 is a memory that stores various data and various programs used by the server 2, and is, for example, a semiconductor drive such as a solid state drive, or a magnetic disk such as a hard disk. As shown in FIG. 6, the storage device 22 stores, for example, an account information database 221, a patient information database 222, and a group information database 223.

[0033] The account information database 221 is a database that stores the account information of medical staff who use the information system 1, and is, for example, a relational database (RDB). FIG. 7 is a diagram showing an example of the data structure when the account information database 221 is an RDB. As shown in FIG. 7, the account information includes, for example, a medical institution ID, a medical staff ID, specialty attribute information, an assigned patient ID, a communication address, and a password.

[0034] The medical institution ID is identification information of the medical institution to which a medical staff belongs. One or more medical staff IDs are associated with the medical institution ID. Further attribute information of the medical institution (for example, medical institution name, etc.) may be associated with the medical institution ID.

[0035] The medical staff ID is identification information of the medical staff belonging to the medical institution identified by the medical institution ID. As shown in FIG. 7, for example, specialty attribute information, assigned patient ID, communication address, and password are associated with the medical staff ID. Further attribute information of the medical staff (for example, name of the medical staff, etc.) may be associated with the medical staff ID.

[0036] The specialty attribute information is identification information for identifying the specialty that the medical staff identified by the medical staff ID has. In the case of a medical staff having multiple specialties, a plurality of specialty attribute information is associated with the medical staff ID. The value of the specialty attribute information associated with the medical staff ID of a medical staff having no specialty in a specific field of medicine is, for example, a null value (NULL).

[0037] The assigned patient ID is identification information of the patient assigned to the medical staff identified by the medical staff ID. In the case of a medical staff assigned multiple patients, a plurality of assigned patient IDs are associated with the medical staff ID. The value of the assigned patient ID associated with the medical staff ID of a medical staff having no assigned patients is, for example, a null value (NULL).

[0038] The communication address is the communication address of the terminal 3 used by the medical staff identified by the medical staff ID, and is, for example, an IP address. The password is the password for the medical staff identified by the medical staff ID to log in to the information system 1.

[0039] The patient information database 222 is a database for storing patient information, and is, for example, an RDB. FIG. 8 is a diagram showing an example of the data structure when the patient information database 222 is an RDB. As shown in FIG. 8, the patient information includes, for example, a patient ID and a medical institution ID.

[0040] The patient ID is identification information of the patient and has the same code system as the patient ID managed in the account information database 221. A medical institution ID is associated with the patient ID. The medical institution ID is identification information of the medical institution responsible for the medical treatment of the patient identified by the patient ID. The medical institution indicated by the medical institution ID is, for example, a medical institution that has provided highly specialized medical treatment to the patient indicated by the patient ID, a medical institution where the patient indicated by the patient ID has undergone surgery, a medical institution where the patient indicated by the patient ID has been admitted, and the like. The medical institution ID managed in the patient information database 222 has the same code system as the medical institution ID managed in the account information database 221. Further attribute information of the patient (for example, the name of the patient, etc.) may be associated with the patient ID.

[0041] The group information database 223 is a database that stores information about groups of medical staff who exchange messages and is, for example, an RDB. FIG. 9 is a diagram showing an example of the data structure when the group information database 223 is an RDB. As shown in FIG. 9, the information about the group includes, for example, a group ID and a medical staff ID.

[0042] The group ID is identification information of the group. A plurality of medical staff IDs are associated with the group ID. The medical staff ID is identification information of the medical staff included in the group identified by the group ID and has the same code system as the medical staff ID managed in the account information database 221. Further attribute information of the group (for example, the group name, etc.) may be associated with the group ID.

[0043] The processor 23 is a control unit that overall controls the functions of the server 2. The processor 23 is, for example, a CPU (Central Processing Unit). The processor 23 may be realized by, for example, a logic circuit. The processor 23 reads the application 24 from the storage device 22, expands it to the RAM 25, and executes it. The application 24 is, for example, stored in the storage device 22 as a program for causing a computer to function as a control unit that executes various processes. The application 24 is, for example, an application dedicated to the information system 1. The application 24 is, for example, distributed or downloaded from an application providing server to the server 2 and installed in the server 2 and stored in the storage device 22.

[0044] 〔Configuration example of application 24〕 FIG. 10 shows a configuration example of the application 24. The application 24 includes, for example, an account management unit 241, a patient management unit 242, a group management unit 243, and an information exchange unit 244.

[0045] The processor 23 registers account information in response to a request from the terminal 3 according to an instruction from the account management unit 241. Specifically, the processor 23 first receives an account registration request according to an instruction from the account management unit 241. The account registration request is transmitted from the terminal 3 in response to an input operation by a medical staff member and includes, as will be described later, account information such as a medical staff member ID, a password, a medical institution ID, specialty attribute information, and a patient ID. The processor 23 stores the account information included in the account registration request in the account information database 221 according to an instruction from the account management unit 241. Regarding the communication address among the account information, it may be transmitted from the terminal 3 every time a medical staff member logs in to the information system 1 using the terminal 3 regardless of the account registration request. In this case, the processor 23 may update the account information database 221 every time it receives a communication address from the terminal 3 according to an instruction from the account management unit 241.

[0046] According to the instructions of the patient management unit 242, the processor 23 registers patient information in response to a request from the terminal 3. Specifically, according to the instructions of the patient management unit 242, the processor 23 first receives a patient registration request transmitted from the terminal 3. The patient registration request is transmitted from the terminal 3 in response to an input operation of a medical staff member who wants to register patient information, and includes, for example, a patient ID and a medical institution ID as will be described later. The processor 23 stores the patient information included in the patient registration request in the patient information database 222 according to the instructions of the patient management unit 242.

[0047] According to the instructions of the group management unit 243, the processor 23 creates a group of medical staff members who exchange information in response to a request from the terminal 3. The group creation process will be described below.

[0048] According to the instructions of the group management unit 243, the processor 23 first receives a group creation request (hereinafter simply referred to as a creation request) from the terminal 3. The creation request is transmitted from the terminal 3 in response to an input operation of a medical staff member, and is a request based on, for example, a patient ID and specialized attribute information as will be described later. When the processor 23 receives the creation request according to the instructions of the group management unit 243, it searches the patient information database 222 for the medical institution ID associated with the target patient ID. Subsequently, according to the instructions of the group management unit 243, the processor 23 searches the account information database 221 for a group of medical staff member IDs. The search pattern at this time is, for example, the following search pattern Q1 or search pattern Q2.

[0049] Regardless of whether the specified patient has an assigned staff member or not, search for medical staff of the first typical example with the specified specialty and medical staff of the second typical example who are in charge of the specified patient. Specifically, obtain a group of medical staff IDs, which is the union of the following search targets Q11 and Q12, from the account information database 221. [Search target Q11] Among the medical staff IDs associated with the medical institution ID obtained from the patient information database 222, the medical staff ID associated with the specialty attribute information included in the received creation request. [Search target Q12] The medical staff ID associated with the patient ID included in the received creation request.

[0050] (Search pattern Q2) Search for medical staff of the first typical example who are in charge of the specified patient and have the specified specialty, and medical staff of the second typical example who are in charge of the specified patient. Specifically, obtain a group of medical staff IDs, which is the union of the following search targets Q21 and Q22, from the account information database 221. [Search target Q21] Among the medical staff IDs associated with the medical institution ID obtained from the patient information database 222, the medical staff ID associated with the specialty attribute information included in the received creation request and the patient ID included in the received creation request. [Search target Q22] Among the medical staff IDs associated with the medical institution ID obtained from the patient information database 222, the medical staff ID not associated with the specialty attribute information included in the received creation request but associated with the patient ID included in the received creation request.

[0051] Also, when the specialty attribute information included in the creation request is a NULL value, the group management unit 243 searches for a group of medical staff IDs from the account information database 221 using the following search pattern Q3.

[0052] (Search pattern Q3) Search for all medical staff who are in charge of the specified patient. Specifically, obtain a group of medical staff IDs associated with the patient ID included in the received creation request from the account information database 221.

[0053] Subsequently, in accordance with the instructions of the group management unit 243, the processor 23 newly creates a group in which group IDs for identifying the obtained group of medical worker IDs from the account information database 221 as one group are associated, and stores the group in the group information database 223.

[0054] Note that the group consisting of the group of medical worker IDs searched by the search pattern Q3 is a group that has nothing to do with the specific specialty of the target patient and corresponds to the above-described "general group". Therefore, the processor 23 may create a general group consisting of the group of medical worker IDs obtained by the search pattern Q3 at the timing when the group consisting of the group of medical worker IDs obtained by the search pattern Q1 or Q2 is created, in accordance with the instructions of the group management unit 243.

[0055] Next, in accordance with the instructions of the group management unit 243, the processor 23 searches the account information database 221 and obtains the communication addresses associated with each of the medical worker IDs included in the newly created group. Subsequently, in accordance with the instructions of the group management unit 243, the processor 23 notifies each of the terminals 3 having the obtained communication addresses that a group has been created (hereinafter simply referred to as "creation notification"). The creation notification includes the group ID of the created group, the patient ID and the specialty attribute information included in the received creation request.

[0056] When the processor 23 receives message information regarding a message to be exchanged from the terminal 3 in accordance with the instructions of the information exchange unit 244, the processor 23 executes server-side information exchange processing. As will be described later, the message information includes, for example, a message ID, a thread ID, a medical worker ID, and a data body.

[0057] The server-side information exchange process will be described below. First, according to the instruction of the information exchange unit 244, the processor 23 searches the group information database 223 for the medical staff ID associated with the group ID corresponding to the thread ID included in the received message information. Subsequently, according to the instruction of the information exchange unit 244, the processor 23 searches the account information database 221 and obtains the communication address associated with the medical staff ID acquired from the group information database 223. Subsequently, according to the instruction of the information exchange unit 244, the processor 23 transmits the received message information to each of the terminals 3 having the acquired communication address (however, excluding the terminal 3 that is the source of the message information). The timing of transmitting the message information may be immediate or may be the timing when the destination terminal 3 accesses the information system 1.

[0058] 〔Configuration example of terminal 3〕 As shown in FIG. 11, the terminal 3 includes, for example, a communication device 31, an input device 32, an output device 33, a storage device 34, a processor 35, a RAM 37, and a ROM 38. The communication device 31 is an interface for communicating with the server 2 according to the control by the processor 35. The input device 32 receives the input of various data to the terminal 3. The input device 32 is, for example, a touch panel, a camera, or a microphone. The output device 33 outputs various data processed by the terminal 3. The output device 33 is, for example, a touch panel, a speaker, or a printer.

[0059] The storage device 34 is a memory that stores various data and various programs used by the terminal 3, and is, for example, a semiconductor drive such as a solid state drive or a magnetic disk such as a hard disk. As shown in FIG. 12, the storage device 34 stores, for example, a thread information database 341 and a message information database 342.

[0060] The thread information database 341 is a database that stores thread information, such as an RDB. FIG. 13 is a diagram showing an example of the data structure when the thread information database 341 is an RDB. As shown in FIG. 13, the thread information includes, for example, a thread ID, a patient ID, and specialized attribute information.

[0061] The thread ID is identification information for the thread. In the present embodiment, the thread ID and the group ID managed in the group information database 223 have a one-to-one correspondence. The thread ID and the group ID may be in the same code system or a code system that can be mutually converted.

[0062] As shown in FIG. 13, the patient ID and the specialized attribute information are associated with the thread ID. Further attribute information of the thread (for example, a thread name, etc.) may be associated with the thread ID.

[0063] The patient ID is identification information for the patient who is the target of information exchange in the thread identified by the thread ID, and is in the same code system as the patient ID managed in the patient information database 222. The specialized attribute information is specialized attribute information that is the target of information exchange in the thread identified by the thread ID, and is in the same code system as the specialized attribute information managed in the account information database 221.

[0064] The message information database 342 is a database that stores message information, such as an RDB. FIG. 14 is a diagram showing an example of the data structure when the message information database 342 is an RDB. As shown in FIG. 14, the message information includes, for example, a message ID, a thread ID, a medical staff ID, and the data body.

[0065] The message ID is identification information for message information. As shown in FIG. 14, the thread ID, the medical staff ID, and the data body are associated with the message ID. Further attribute information of the message (for example, the message transmission date and time, etc.) may be associated with the message ID.

[0066] The thread ID is identification information for the thread in which messages identified by the message ID are exchanged, and has the same code system as the thread ID managed in the thread information database 341. The medical staff ID is identification information for the medical staff who sent the message identified by the message ID, and has the same code system as the medical staff ID managed in the account information database 221. The data body is the data itself of the message identified by the message ID. The data format of the data body is not limited, and is, for example, at least one of text data, still image data, moving image data, and audio data.

[0067] The processor 35 is a control unit that comprehensively controls the functions of the terminal 3. The processor 35 is, for example, a CPU. The processor 35 may be realized by, for example, a logic circuit. The processor 35 reads the application 36 from the storage device 34, expands it to the RAM 37, and executes it. The application 36 is stored, for example, in the storage device 34 as a program for causing a computer to function as a control unit that executes various processes. The application 36 is, for example, an application dedicated to the information system 1. The application 36 is distributed or downloaded from an application providing server to the terminal 3, and installed in the terminal 3 and stored in the storage device 34. The application 36 may be provided as a web application by an application providing server and operate on a web browser installed on the terminal 3.

[0068] 〔Configuration example of application 36〕 FIG. 15 shows a configuration example of the application 36. The application 36 includes, for example, an account registration unit 361, a patient registration unit 362, a thread management unit 363, and an information exchange unit 364.

[0069] The processor 35 creates an account registration screen 3611 in response to an input operation by a medical staff member according to an instruction from the account registration unit 361 and causes the output device 33 to display it. The account registration screen 3611 is a screen for accepting new registration or updated registration of account information. FIG. 16 is a diagram showing an example of the account registration screen 3611. As shown in FIG. 16, the account registration screen 3611 includes, for example, fields 3612 to 3616 and a button 3617.

[0070] The field 3612 accepts input of the medical staff member ID of the medical staff member to be registered. The field 3612 may accept input of the medical staff member ID from the medical staff member using the terminal 3, or the medical staff member ID may be automatically set. As an example of automatic setting, when displaying the account registration screen 3611, the processor 35 sends a medical staff member ID assignment request to the server 2 according to an instruction from the account registration unit 361, and sets the medical staff member ID obtained from the server 2 as a response in the field 3612.

[0071] The field 3613 accepts input of a password for the medical staff member to be registered to log in to the information system .

[0072] The field 3614 accepts input of the medical institution ID of the medical institution to which the medical staff member to be registered belongs. The field 3614 is preferably a selection type. For example, by selecting a medical institution name displayed in a pre-prepared drop-down list or the like, it is preferable that the medical institution ID corresponding to the selected medical institution name is automatically set in the field 3614.

[0073] Field 3615 receives the input of the professional attribute information of the medical staff to be registered. The number of fields 3615 can be increased or decreased according to the number of professional attribute information. It is preferable that field 3615 is a selection type. It is preferable that the professional attribute information is automatically set in field 3615 by selecting the professional attribute information displayed in a pre-prepared drop-down list or the like. Field 3615 is not an input-required field. Medical staff without medical expertise can register account information without entering field 3615.

[0074] Field 3616 receives the input of the patient ID of the patients in charge of the medical staff to be registered. The number of fields 3616 can be increased or decreased according to the number of patients in charge. Field 3616 is not an input-required field. Medical staff without patients in charge can register account information without entering field 3616.

[0075] When receiving an operation at button 3617, processor 35 sends an account registration request including the account information entered in fields 3612 to 3616 to server 2 according to the instruction of account registration unit 361.

[0076] Processor 35 creates a patient registration screen 3621 according to the instruction of patient registration unit 362 in response to the input operation of the medical staff and displays it on output device 33. Patient registration screen 3621 is a screen for receiving new registration or updated registration of patient information. FIG. 17 is a diagram showing an example of patient registration screen 3621. As shown in FIG. 17, patient registration screen 3621 includes, for example, fields 3622 to 3623 and button 3624.

[0077] Field 3622 receives an input of the medical institution ID of the medical institution associated with the patient to be registered. Field 3622 is preferably a selection type, and it is more preferable that the medical institution ID is automatically set. As an example of automatic setting, when displaying the patient registration screen 3621 in accordance with the instruction of the patient registration unit 362, the processor 35 may send a search request for the medical institution ID to the server 2 and set the medical institution ID obtained from the server 2 as a response in Field 3622. In this case, the server 2 searches the account information database 221, obtains the medical institution ID associated with the medical staff ID of the medical staff who has logged in to the information system 1 from the terminal 3 that has made the search request, and may send the medical institution ID to the terminal 3 that has made the search request.

[0078] Field 3623 receives an input of the patient ID of the patient to be registered. The patient ID input to Field 3623 may be the patient ID itself managed in the patient information database 222, or may be the number of the medical examination ticket or the medical record ID issued by the medical institution where the patient to be registered is hospitalized or visiting. In the latter case, the information combining the medical institution ID input to Field 3622 and the patient ID input to Field 3623 may be treated as the patient ID managed in the patient information database 222.

[0079] When receiving an operation at the button 3624, the processor 35 sends a patient registration request including the patient information input to Fields 3622 to 3623 to the server 2 in accordance with the instruction of the patient registration unit 362.

[0080] In accordance with the instruction of the thread management unit 363, the processor 35 creates a creation request screen 3631 for requesting the creation of a group in response to the input operation of the medical staff and causes it to be displayed on the output device 33. The creation request screen 3631 is a screen for receiving a creation request. FIG. 18 is a diagram showing an example of the creation request screen 3631. As shown in FIG. 18, the creation request screen 3631 includes, for example, Fields 3632 to 3633 and a button 3634.

[0081] Field 3632 receives an input of the patient ID of the patient for whom information is to be exchanged. Field 3633 receives an input of the specialized attribute information of the medical treatment administered to the patient indicated by the patient ID entered in Field 3632. Field 3633 is not an input-required field.

[0082] The medical staff who makes the creation request assumes that the patient ID and the specialized attribute information are available in advance. For example, a visiting nurse in charge of visiting care for a patient obtains the patient ID and the specialized attribute information in advance by means of an instruction document or an e-mail sent from the medical institution where the patient received treatment. Note that Field 3622 may be a selection type. For example, the patient ID in charge associated with the medical staff ID of the medical staff who makes the creation request may be acquired from the account information database 221 and displayed in a drop-down list.

[0083] When an operation is received at button 3634, the processor 35 transmits a creation request including the information entered in Fields 3632 to 3633 to the server 2 in accordance with the instruction of the thread management unit 363. Note that when there is no input in Field 3633, the value of the specialized attribute information is set to NULL.

[0084] Also, when the processor 35 receives a creation notification from the server 2 in accordance with the instruction of the thread management unit 363, the processor 35 creates and manages a thread. Specifically, the processor 35 creates thread information by associating the patient ID and the specialized attribute information included in the creation notification with the thread ID corresponding to the group ID included in the creation notification in accordance with the instruction of the thread management unit 363, and stores the created thread information in the thread information database 341.

[0085] The processor 35 executes terminal-side information exchange processing in accordance with the instruction of the information exchange unit 364. The terminal-side information exchange processing includes message transmission-side processing and message reception-side processing. First, the message transmission-side processing will be described.

[0086] According to the instruction of the information exchange unit 364, the processor 35 creates a thread selection screen 3641 in response to the input operation of the medical staff and causes it to be displayed on the output device 33. The thread selection screen 3641 is a screen for allowing the medical staff to select a desired thread. FIG. 19 is a diagram showing an example of the thread selection screen 3641. As shown in FIG. 19, the thread selection screen 3641 includes, for example, fields 3642 to 3643, a button 3644, and a list 3645.

[0087] The fields 3642 to 3643 receive input of conditions for searching for a desired thread. The field 3642 receives input of a patient ID. The field 3643 receives input of specialty attribute information. The field 3643 is preferably a selection type. It is preferable that the specialty attribute information is automatically set in the field 3643 by selecting the specialty attribute information displayed in a pre-prepared drop-down list or the like.

[0088] When an operation is received by the button 3644, the processor 35 searches the thread information database 341 according to the instruction of the information exchange unit 364, acquires the threads having the thread IDs associated with the patient ID and the specialty attribute information input in the fields 3642 and 3643, and displays each of the acquired threads in the list 3645. In the example shown in FIG. 19, the threads having the thread IDs associated with the patient ID "P101" and the specialty attribute information "WOC" are displayed in the list 3645.

[0089] When a thread selection operation is received in the list 3645, the processor 35 searches the message information database 342 according to the instruction of the information exchange unit 364, creates a thread screen 3646 corresponding to the selected thread, and causes it to be displayed on the output device 33. FIG. 4 is a diagram showing an example of the thread screen 3646. As shown in FIG. 4, the thread screen 3646 includes, for example, fields 3647 to 3649, and buttons 3650 to 3651.

[0090] Field 3647 displays information about the thread. In the example shown in FIG. 4, as information about the thread, the thread name, patient ID, patient name, and creation date and time are displayed. Field 3648 displays the messages for which information has been exchanged in chronological order. The message is the data body stored in the message information database 342, and may be text, a still image, or a moving image. In the example shown in FIG. 4, as the data body, in addition to the text indicating the consultation item, a still image related to the patient's affected part and a moving image related to the patient's affected part are shown. Field 3649 accepts the posting of a new message. The message to be accepted may be text, a still image, or a moving image.

[0091] When an operation is received by button 3650, the processor 35 transmits the message information to server 2 according to the instruction of the information exchange unit 364. The message information includes the data body input to field 3649, the thread ID of the thread, the medical staff ID of the medical staff who posted the message, and the message ID for identifying the message information. Further, the processor 35 manages the message information transmitted to server 2 according to the instruction of the information exchange unit 364. Specifically, the processor 35 stores the message information transmitted to server 2 in the message information database 342 according to the instruction of the information exchange unit 364.

[0092] Button 3651 is a toggle button that accepts an operation to switch between displaying and hiding the attribute information (such as medical staff ID, name, etc.) of medical staff who can exchange information within a thread. The said attribute information is obtained from, for example, server 2. Specifically, processor 35 sends a medical staff acquisition request including a thread ID to server 2 according to the instruction of information exchange unit 364. Server 2 searches group information database 223 and acquires the medical staff ID associated with the group ID corresponding to the thread ID included in the medical staff acquisition request. Subsequently, server 2 searches account information database 221, acquires the attribute information of the medical staff associated with the medical staff ID obtained from group information database 223, and sends the acquired attribute information to terminal 3 that sent the medical staff acquisition request.

[0093] Next, the message receiving side processing will be described. When processor 35 receives message information from server 2 according to the instruction of information exchange unit 364, it manages the received message information. Specifically, information exchange unit 364 stores, for example, the message ID, thread ID, medical staff ID, and data body included in the message information in message information database 342.

[0094] Also, when processor 35 receives message information according to the instruction of information exchange unit 364 when thread screen 3646 is being displayed, it updates the display content of field 3648 according to the received message information.

[0095] Also, when the processor 35 receives message information according to the instruction of the information exchange unit 364 when the thread screen 3646 is not displayed, the processor 35 may cause the output device 33 to display notification information indicating that the message information has been received. The notification mode of the notification information is, for example, a notification dot, a pop-up notification, a banner notification, etc. With the notification information, it becomes easier for medical staff to recognize that they have received a message. The processor 35 may cause the output device 33 to display the thread screen 3646 according to the operation by the medical staff on the displayed notification information according to the instruction of the information exchange unit 364.

[0096] [Example of the flow of group and thread creation processing] FIG. 20 is a flowchart showing an example of the flow of group and thread creation processing, which is part of the information exchange method according to the present embodiment. First, the processing performed by the terminal 3 that transmits a creation request will be described with reference to the flowchart indicated by reference numeral 2001. Each process shown in the flowchart indicated by reference numeral 2001 is a process executed by the processor 35 of the terminal 3. First, the processor 35 causes the output device 33 to display a creation request screen 3631 according to the input operation of the medical staff according to the instruction of the thread management unit 363 (S11). Subsequently, the processor 35 receives the input of the patient ID and the specialized attribute information on the creation request screen 3631 according to the instruction of the thread management unit 363 (S12), and transmits a creation request including the input information to the server 2 (S13).

[0097] Next, the processing performed by the server 2 will be described with reference to the flowchart shown by reference numeral 2002. Each process shown in the flowchart shown by reference numeral 2002 is a process executed by the processor 23 of the server 2. When the processor 23 receives the creation request transmitted in step S13 above according to the instruction of the group management unit 243 (S21), it searches the patient information database 222 for the medical institution ID associated with the patient ID included in the received creation request (S22). Subsequently, the processor 23 searches for medical staff who match the received creation request in steps S22 to S24 according to the instruction of the group management unit 243. Hereinafter, the case where the processor 23 searches the account information database 221 according to the above-described search pattern Q1 according to the instruction of the group management unit 243 will be described. In this case, the processor 23 searches the account information database 221 for the medical staff ID associated with the specialized attribute information included in the received creation request among the medical staff IDs associated with the medical institution ID obtained from the patient information database 222 according to the instruction of the group management unit 243 (S23). Further, the processor 23 searches the account information database 221 for the medical staff ID associated with the patient ID included in the received creation request according to the instruction of the group management unit 243 (S24). Subsequently, the processor 23 creates a group in which the newly created group ID is associated with the union of the medical staff IDs searched in steps S23 and S24 and the medical staff ID of the medical staff who transmitted the creation request according to the instruction of the group management unit 243, and stores it in the group information database 223 (S25). Subsequently, the processor 23 searches the account information database 221 according to the instruction of the group management unit 243, and acquires the communication address associated with the medical staff ID included in the created group (S26). Subsequently, the processor 23 transmits a creation notification to each of the terminals 3 having the acquired communication address according to the instruction of the group management unit 243 (S27).

[0098] Next, the processing performed by the terminal 3 that receives the creation notification will be described with reference to the flowchart shown by reference numeral 2003. Each process shown in the flowchart shown by reference numeral 2003 is a process executed by the processor 35 of the terminal 3. When the processor 35 receives the creation notification transmitted in step S27 described above in accordance with the instruction of the thread management unit 363 (S31), the processor 35 creates thread information based on the creation notification (S32). Specifically, the processor 35 creates thread information by associating the patient ID and the specialized attribute information included in the creation notification with the thread ID corresponding to the group ID included in the creation notification in accordance with the instruction of the thread management unit 363, and stores the created thread information in the thread information database 341.

[0099] 〔Example of the flow of information exchange processing〕 FIG. 21 is a flowchart showing an example of the flow of information exchange processing, which is a part of the information exchange method according to the present embodiment. First, the processing performed by the terminal 3 that transmits a message will be described with reference to the flowchart shown by reference numeral 2101. Each process shown in the flowchart shown by reference numeral 2101 is a process executed by the processor 35 of the terminal 3. First, the processor 35 causes the output device 33 to display the thread selection screen 3641 in response to the input operation of the medical staff in accordance with the instruction of the information exchange unit 364, and accepts the selection of a thread (S41). Subsequently, the processor 35 causes the output device 33 to display the thread screen 3646 corresponding to the selected thread in accordance with the instruction of the information exchange unit 364, and accepts the posting of a message (S42). Subsequently, the processor 35 stores the message information including the received message in the message information database 342 and transmits it to the server 2 in accordance with the instruction of the information exchange unit 364 (S43).

[0100] Next, the processing performed by the server 2 will be described with reference to the flowchart shown by reference numeral 2102. Each process shown in the flowchart shown by reference numeral 2102 is a process executed by the processor 23 of the server 2. When the processor 23 receives the message information transmitted in step S43 described above in accordance with the instruction of the information exchange unit 244 (S51), it searches the group information database 223 and acquires the medical staff ID associated with the group ID corresponding to the thread ID included in the received message information (S52). Subsequently, the processor 23 searches the account information database 221 in accordance with the instruction of the information exchange unit 244 and acquires the communication address associated with the medical staff ID acquired from the group information database 223 (S53). Subsequently, the processor 23 transmits the received message information to each of the terminals 3 having the acquired communication address (however, excluding the terminal 3 that is the transmission source of the message information) in accordance with the instruction of the information exchange unit 244 (S54).

[0101] Next, the processing performed by the terminal 3 that receives the message information will be described with reference to the flowchart shown by reference numeral 2103. Each process shown in the flowchart shown by reference numeral 2103 is a process executed by the processor 35 of the terminal 3. When the processor 35 receives the message information transmitted from the server 2 in step S54 described above in accordance with the instruction of the information exchange unit 364 (S61), it manages the received message information (S62). Specifically, the processor 35 stores, for example, the message ID, thread ID, medical staff ID, and data body included in the message information in the message information database 342 in accordance with the instruction of the information exchange unit 364. Then, the processor 35 causes the output device 33 to display, for example, a thread screen or updates the thread screen displayed on the output device 33 in accordance with the received message information in accordance with the instruction of the information exchange unit 364 (S63). The processor 35 may cause the output device 33 to display notification information indicating that the message information has been received in accordance with the instruction of the information exchange unit 364.

[0102] In order to make the information exchange among medical staff via the thread screen 3646 shown in FIG. 4 smoother, information exchange may be performed using template data for inputting the message content. The template data is data in which input items, input formats, layouts, etc. of the message are set in advance. Thereby, a medical staff member who posts a message can input the message via a predetermined input form according to the template data instead of in a free input format, so that the input work can be facilitated, omission of input of necessary items can be prevented, and the input content can be unified.

[0103] FIG. 35 is a screen showing an example of a thread screen 3646 having a template function. As shown in FIG. 35, the thread screen 3646 includes a button 3667. When the processor 35 receives an operation of the button 3667, for example, it causes the output device 33 to display a template list shown in FIG. 36. The template list shown in FIG. 36 includes a list of template data corresponding to the thread being handled on the calling thread screen 3646. More specifically, the template list shown in FIG. 36 includes a list of template data corresponding to the specialized attribute information associated with the thread ID of the thread. In the example shown in FIG. 36, a list of three types of template data for stomas is displayed. When a medical staff member who intends to send a message selects one template data from the template list displayed on the output device 33, the processor 35 causes the output device 33 to display an input form according to the selected template data. When there is only one template data corresponding to the specialized attribute information, the display of the template list may be omitted, and an input form according to the template data may be displayed. Note that the template data is stored in advance in the storage device 22 of the server 2, and the terminal 3 may receive the template data from the server 2 and display it on the output device 33.

[0104] FIG. 37 is a diagram showing an example of an input form displayed on the output device 33. When a medical worker fills in the necessary items in each input item according to the input form and operates the button 3650A, the processor 35 transmits message information including the information input in each input item of the input form to the server 2. FIG. 38 is a diagram showing the thread screen 3646 after the message information is transmitted to the server 2. In the thread screen 3646 shown in FIG. 38, in the field 3648, instead of messages being exchanged in a free-form conversation style, the information input according to the input form is displayed.

[0105] When the thread screen 3646 shown in FIG. 35 is not a thread screen according to the medical specialty but a thread screen corresponding to the above-described general group (not limited to matters related to the medical specialty of the medical treatment applied to the target patient, but a group for information exchange on all general matters related to the patient), when the processor 35 receives the operation of the button 3667, the processor 35 causes the output device 33 to display template data for reporting all general matters related to the patient associated with the thread. Since this template data is used not limited to matters related to medical specialty, for example, it is used for reporting to a doctor who manages the entire treatment of the patient or for reporting to a regional cooperation room that mediates reports to doctors in each medical institution.

[0106] Template data can be freely created and used by each medical practitioner. For example, it can be created for each medical institution according to the treatment policies, preferences, etc. of professional nurses, doctors, etc. in each medical institution. FIG. 39 is a diagram showing an example of a template creation screen for creating template data. The template creation screen is displayed on the output device 33 of the terminal 3 by the processor 35. As shown in FIG. 39, the template creation screen 3680 includes, for example, fields 3681 to 3683 and buttons 3684 to 3686. Field 3681 accepts the input of the name of the template data. In field 3682, the template tags currently set for this template data are displayed. The template tag is identification information used when the processor 23 of the server 2 reads the template data corresponding to the thread from the storage device 22. Field 3683 displays the content of each input item currently set for this template data. Button 3684 is a button for editing the template tag. When this button is selected, the processor 35 causes the tag selection screen 3690 shown in FIG. 40 to be displayed on the output device 33.

[0107] As shown in FIG. 40, the tag selection screen 3690 includes, for example, button groups 3691 and 3692, and a field 3693. The button group 3691 is used to select specialized attribute information to be associated with template data. The button group 3692 is used to select report format information to be associated with template data. When creating template data to be used in a thread screen according to medical specialty, one or more buttons are selected from the button group 3691, and the specialized attribute information corresponding to the selected button is associated with the template data. Each medical staff can select specialized attribute information according to the type and specialty of nursing for which the template data is used. Among the multiple buttons displayed in the button group 3691, buttons to which specialized attribute information has not yet been assigned display "Specialized Attribute 1", "Specialized Attribute 2", and "Specialized Attribute 3". When these buttons are selected, medical staff can assign specialized attribute information with an arbitrary name on another transition screen. When creating template data to be used in a thread screen for information exchange on general matters of patients, one button is selected from the button group 3692, and the report format information corresponding to the selected button is associated with the template data. The template data associated with the report format information is used for reporting on a specific patient regardless of the type and specialty of nursing. Therefore, the processor 35 receives the patient ID of the patient for whom this template data is to be used in the field 3693. When a medical staff associated with a responsible patient ID is operating the template creation screen 3680, the field 3693 may be omitted, and the responsible patient ID associated with the medical staff may be associated with the template data.

[0108] Also, on the template creation screen 3680 shown in FIG. 39, by operating the button 3685, medical staff can freely edit each input item of the currently set template data. When the processor 35 receives the operation of the button 3685, for example, it causes the output device 33 to display a setting screen for setting changes such as the change of the input item name, the change of the unit, the addition of input items, the addition of options, and the change of the layout of each input item, and can receive the editing of each input item through the screen. When the button 3686 is operated, the processor 35 transmits the information received on the template creation screen 3680 to the server 2, and the server 2 creates template data according to the received information and stores it in the storage device 22.

[0109] As shown in FIG. 41, the storage device 22 of the server 2 stores a template information database 225. The template data created using the template creation screen 3680 is stored in the template information database 225. The template information database 225 is, for example, an RDB. FIG. 42 is a diagram showing an example of the data structure when the template information database 225 is an RDB. As shown in FIG. 42, in the template information database 225, for example, template data is stored in association with a template ID. The template data includes information necessary for generating an input form, such as a template name, item information, and layout information. Also, as shown in FIG. 41, the storage device 22 stores an account information database 221A. As shown in FIG. 43, in the account information database 221A, in addition to the data of the account information database 221 shown in FIG. 7, a template ID is stored in association with a medical institution ID. When specialized attribute information is associated with the template data, in the account information database 221A, the specialized attribute information is stored in association with the template ID. The medical institution ID is stored in association with the template ID by the server 2 obtaining the medical institution ID associated with the medical staff ID of the medical staff who searched the account information database 221A and made a template creation request via the terminal 3. Thereby, the template data can be managed for each medical institution. Also, as shown in FIG. 41, the storage device 22 stores a patient information database 222A. As shown in FIG. 44, in the patient information database 222A, in addition to the data of the patient information database 222 shown in FIG. 8, a template ID can be stored in association with a patient ID. In the case of template data associated with report format information, in the patient information database 222A, the template ID is stored in association with the patient ID input in the field 3693 of the tag selection screen 3690.Since each of the specialty attribute information and the patient ID is associated with a specific one or more thread IDs, the storage device 22 can store the template data in association with the specialty attribute information or the patient ID, thereby storing the template data in association with a specific thread, that is, a specific group.

[0110] FIG. 45 is a flowchart showing an example of the flow of a process for performing information exchange using template data. First, the flowchart indicated by reference numeral 2104 shows the process executed by the processor 35 of the terminal 3 on the message transmission side, and the flowchart indicated by reference numeral 2105 shows the process executed by the processor 23 of the server 2. First, when the processor 35 receives an operation of the button 3667 on the thread screen 3646 shown in FIG. 35, it transmits a template data request (including the patient ID and specialty attribute information associated with the thread ID) corresponding to the thread to the server 2 (S71). When the processor 23 receives the template data request transmitted from the terminal 3 (S81), it acquires the template data corresponding to the thread from the storage device 22 based on the information included in the template data request (S82). Specifically, in S82, the processor 23 acquires the medical institution ID from the patient information database 222A in FIG. 44 using the received patient ID as a key. If there is a template ID associated with the received patient ID in the patient information database 222A, the processor 23 also acquires the template ID and acquires the template data corresponding to the template ID from the template information database 225 in FIG. 42. If there are multiple template IDs corresponding to the patient ID in the patient information database 222A, those multiple template IDs are acquired. Note that the template ID associated with the patient ID is associated with the template data used on the thread screen for reporting general matters of the patient. If there is no template ID associated with the received patient ID in the patient information database 222A, the processor 23 uses the medical institution ID associated with the patient ID and the specialty attribute information received from the terminal 3 as keys to acquire the template ID from the account information database 221A in FIG. 43, and acquires the template data corresponding to the template ID from the template information database 225. If there are multiple template IDs corresponding to the key information in the account information database 221A, those multiple template IDs are acquired.For example, when the specialized attribute information included in the template data request is "chemotherapy", the template ID associated with the specialized attribute information "chemotherapy" is read from the account information database 221A. Even if other specialized attribute information is associated in addition to the specialized attribute information "chemotherapy", as long as it is the template ID associated with at least "chemotherapy", it is read from the account information database 221A. The processor 23 transmits the template data acquired from the template information database 225 to the terminal 3 (S83). When a plurality of template IDs are read in S82, the processor 23 transmits a template list showing a list thereof to the terminal 3, and transmits one template data received by accepting selection from the template list by the terminal 3 to the terminal 3.

[0111] The processor 35 receives the template data transmitted from the server 2, and causes the output device 33 to display an input form corresponding to the received template data (see, for example, FIG. 37) (S72). When message information is input via the input form, the processor 35 transmits the message information to the server 2 (S73). When the processor 23 receives the message information from the terminal 3 (S84), it transmits the message information to the terminal 3 on the message receiving side.

[0112] The template information database 225 stored in the memory device 22 can be utilized as a template library for sharing template data among a plurality of medical staff belonging to different medical institutions. FIG. 46 is a search screen 3695 for each medical staff to search for desired template data, and is displayed on the output device 33 by the processor 35. The processor 35 transmits the search conditions input via the search screen 3695 to the server 2, and the processor 23 of the server 2 reads out the template data that matches the received search conditions from the template information database 225 and transmits it to the terminal 3. The search conditions include the template name, keywords, the name of the medical institution that created the template data, and the like. The processor 35 causes the output device 33 to display the template data received from the server 2 as search results, and the medical staff selects the desired template data from the template data displayed on the output device 33, and can newly save the selected template data in the template information database 225 as the template data for the medical institution to which the medical staff belongs. Thereby, the template data created by other medical institutions can be utilized in the information exchange on the thread screen.

[0113] 〔Modification Example 1: Video Call〕 The information system 1 may have a function of enabling video calls among medical staff within a group. By making video calls among medical staff, information can be exchanged while visually recognizing the patient's condition. The video call function may be provided with a function of superimposing characters and images on the moving image using a paint tool in addition to transmitting and receiving moving images.

[0114] The operation that triggers the execution of a video call may be received, for example, on the thread screen 3646. FIG. 22 is a diagram showing an example of the thread screen 3646 according to this modified example. As shown in FIG. 22, the thread screen 3646 according to this modified example includes a button 3652. The button 3652 receives an operation to execute a video call. When an operation is received at the button 3652, the information exchange unit 364, for example, calls a video call application to execute a video call.

[0115] The destination of the video call request may be all or some of the medical staff within the group. The processing flow when making a video call request to all of the medical staff within the group will be described. The processor 35, in accordance with the instruction of the information exchange unit 364, transmits a video call request including the thread ID of the thread displayed on the thread screen 3646 where the operation was received at the button 3652 to the server 2. The server 2 searches the group information database 223 and acquires the medical staff ID associated with the group ID corresponding to the thread ID included in the video call request. Subsequently, the server 2 searches the account information database 221 and acquires the communication address associated with the medical staff ID acquired from the group information database 223. Subsequently, the server 2 transmits a video call request to the terminals 3 having the acquired communication address, excluding the terminal 3 that is the source of the video call request. When a power reception operation is received from a medical staff at any of the terminals 3 that received the video call request, a video call is started between the terminal 3 that is the source of the video call request. The information exchange unit 364 of the terminal 3 where the video call is started causes the video call screen 3653 to be displayed on the output device 33.

[0116] FIG. 23 is a diagram showing an example of a video call screen 3653. As shown in FIG. 23, the video call screen 3653 includes, for example, fields 3654 to 3655 and a button 3656. The field 3654 displays information on a medical worker who is a video call partner. The field 3655 displays a moving image captured by the terminal 3 of the medical worker who is a video call partner. In the example shown in FIG. 23, a moving image of the affected part of the patient is displayed in the field 3655. When an operation is received via the button 3656, the processor 35 ends the video call according to the instruction of the information exchange unit 364. Note that the information system 1 may have a function of enabling voice calls among medical workers within a group.

[0117] 〔Modification Example 2: Video Call Reservation〕 The information system 1 may have a function of reserving video calls to be made among medical workers. The reservation function is useful for making video calls with medical workers who have difficulty immediately responding to video call requests.

[0118] The server 2 according to this modification example has a function of managing video call reservations. As shown in FIG. 24, in addition to the account information database 221, the patient information database 222, and the group information database 223, the storage device 22 of the server 2 according to this modification example further stores a video call reservation information database 224. The video call reservation information database 224 is a database that stores video call reservation information, and is, for example, an RDB. FIG. 25 is a diagram showing an example of the data structure when the video call reservation information database 224 is an RDB. As shown in FIG. 25, the video call reservation information includes, for example, a reservation ID, a group ID, and a reservation time zone.

[0119] The reservation ID is identification information for a reservation. As shown in FIG. 25, for example, a group ID and a reservation time zone are associated with the reservation ID. Further attribute information regarding the reservation (e.g., reservation name, reserving person, etc.) may be associated with the reservation ID. The group ID is the group ID of the group that conducts the reserved video call identified by the reservation ID, and has the same code system as the group ID managed in the group information database 223. The reservation time zone is the time zone during which the reserved video call identified by the reservation ID is executed.

[0120] As shown in FIG. 26, the application 24 of the server 2 according to this modification example further includes a video call reservation management unit 245 in addition to the account management unit 241, the patient management unit 242, the group management unit 243, and the information exchange unit 244. The processor 23 receives a video call reservation request transmitted from the terminal 3 in response to an input operation by a medical staff member according to an instruction from the video call reservation management unit 245, and stores the video call reservation information included in the video call reservation request in the video call reservation information database 224.

[0121] Also, when the processor 23 receives a video call reservation search request transmitted from the terminal 3 in response to an input operation by a medical staff member according to an instruction from the video call reservation management unit 245, the processor 23 searches the video call reservation information database 224, acquires reservation information indicated by a reservation ID associated with the group ID corresponding to the thread ID included in the video call reservation search request, and transmits the acquired reservation information to the terminal 3 that is the source of the video call reservation search request.

[0122] Further, the processor 23 may transmit, according to the instruction of the video call reservation management unit 245, notification information indicating that the start time of the reserved video call is approaching to the terminal 3. In this case, the processor 23 searches the video call reservation information database 224 according to the instruction of the video call reservation management unit 245, and checks whether there is reservation information associated with a reservation time zone after a predetermined time (for example, 15 minutes later) from the current time. If such reservation information exists, the processor 23 searches the group information database 223 according to the instruction of the video call reservation management unit 245, and acquires the medical staff ID associated with the group ID included in the reservation information. Subsequently, the processor 23 searches the account information database 221 according to the instruction of the video call reservation management unit 245, and acquires the communication address associated with the medical staff ID acquired from the group information database 223. Subsequently, the processor 23 transmits, according to the instruction of the video call reservation management unit 245, the notification information indicating that the start time of the video call is approaching to each of the terminals 3 having the acquired communication address. The terminal 3 that has received the notification information displays the notification information on the output device 33. The notification mode of the notification information is, for example, a pop-up notification, a banner notification, or the like.

[0123] The information exchange unit 364 of the terminal 3 according to this modification example has a video call reservation function and a video call reservation search function. First, the video call reservation function will be described.

[0124] The operation for starting a video call reservation is received, for example, on the thread screen 3646. FIG. 27 is a diagram showing an example of the thread screen 3646 according to this modification example. As shown in FIG. 27, the thread screen 3646 according to this modification example includes a button 3661. When an operation is received by the button 3661, the processor 35 creates a video call reservation screen 3657 according to the instruction of the information exchange unit 364, and causes it to be displayed on the output device 33.

[0125] The video call reservation screen 3657 is a screen for accepting reservations for video calls. FIG. 28 is a diagram showing an example of the video call reservation screen 3657. As shown in FIG. 28, the video call reservation screen 3657 includes, for example, a list 3658 and a button 3659. The list 3658 displays the available time slots for video call reservations and accepts the selection input of the desired reservation time slot. The available time slots may be set, for example, in consideration of the work schedule of medical staff obtained from the schedule management system in the medical institution to which the medical staff in the group belongs. The button 3659 is a toggle button that accepts an operation to switch between the display and non-display of the available time slots.

[0126] When the selection input of the desired reservation time slot is received in the list 3658, the processor 35 may create a confirmation screen 3660 shown in FIG. 29 according to the instruction of the information exchange unit 364 and display it on the output device 33. When the acceptance of the reservation time slot is determined, the processor 35 transmits a video call reservation request including the video call reservation information to the server 2 according to the instruction of the information exchange unit 364. The reservation information includes the newly created reservation ID, the reservation time slot received in the list 3658, and the thread ID of the thread displayed on the thread screen 3646 which is the calling source of the video call reservation screen 3657.

[0127] Next, the video call reservation search function will be described. The processor 35 creates a video call reservation search screen 3662 according to the instruction of the information exchange unit 364 in response to the input operation of the medical staff and displays it on the output device 33. The video call reservation search screen 3662 is a screen for accepting the search for the desired reservation information. FIG. 30 is a diagram showing an example of the video call reservation search screen 3662. As shown in FIG. 30, the video call reservation search screen 3662 includes, for example, fields 3663 to 3664, a button 3665, and a list 3666.

[0128] Fields 3663 to 3664 accept the input of conditions for searching for a desired reservation. Field 3663 accepts the input of a patient ID. Field 3664 accepts the input of specialty attribute information. Field 3664 is preferably a selection type. It is preferable that the specialty attribute information is automatically set in Field 3664 by selecting the specialty attribute information displayed in a pre-prepared drop-down list or the like.

[0129] When an operation is received at button 3665, the processor 35 searches the thread information database 341 according to the instructions of the information exchange unit 364, and obtains the thread ID associated with the patient ID and specialty attribute information entered in fields 3663 and 3664. Then, the information exchange unit 364 sends a video call reservation search request including the obtained thread ID to server 2, and displays the reservation information returned from server 2 as a response in list 3666.

[0130] When a selection operation of reservation information is received in list 3666, the processor 35, according to the instructions of the information exchange unit 364, for example, when the reserved time zone associated with the selected reservation information arrives, calls the video call application to execute a video call.

[0131] 〔Modification Example 3: Report Creation〕 The information system 1 may be able to create a report including messages exchanged by threads. Thereby, the burden on medical staff required for report creation can be reduced.

[0132] As shown in FIG. 31, the application 36 of the terminal 3 according to this modification example includes, in addition to an account registration unit 361, a patient registration unit 362, a thread management unit 363, and an information exchange unit 364, a report creation unit 365. An operation for starting report creation is received, for example, on the thread screen 3646. FIG. 32 is a diagram showing an example of the thread screen 3646 according to this modification example. As shown in FIG. 32, the thread screen 3646 according to this modification example includes a button 3676. When an operation is received at the button 3676, the processor 35 creates a report creation screen 3671 according to the instruction of the report creation unit 365 and causes it to be displayed on the output device 33.

[0133] The report creation screen 3671 is a screen for creating a report from the messages exchanged for information in the thread. FIG. 33 is a diagram showing an example of the report creation screen 3671. As shown in FIG. 33, the report creation screen 3671 includes, for example, a field 3672, a checkbox 3673, and a button 3674. The field 3672 displays the message. The checkbox 3673 receives a selection as to whether to output the message to the report.

[0134] When an operation is received at the button 3674, the processor 35 causes the output device 33 to output a report 3675 including the messages selected at the checkbox 3673 according to the instruction of the report creation unit 365. FIG. 34 is a diagram showing an example of the report 3675.

[0135] 〔Modification Example 4: Patient Information〕 The patient information database 222 may further store specialized attribute information indicating the specialty of the medical treatment provided to the patient identified by the patient ID, in association with the patient ID. In this case, the patient registration screen 3621 shown in FIG. 17 may be further provided with a field for accepting input of the specialized attribute information. In this case, in the creation request screen 3631 shown in FIG. 18, when a creation request is made with the patient ID input and the specialized attribute information not input, the processor 23 may, according to the instruction of the group management unit 243, obtain the specialized attribute information associated with the patient ID included in the creation request from the patient information database 222, obtain the medical staff associated with the obtained specialized attribute information from the account information database 221, and create a group including the obtained medical staff.

[0136] 〔Modification Example 5: Group〕 The group X1 created by the information system 1 may include the general nurse G2 and the visiting nurse V2 in charge of patient A, and the specialized nurses S1 and S2, and may be a group consisting of specialized nurses without including the general nurse G2 and the visiting nurse V2.

[0137] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope shown in the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

Explanation of Reference Numerals

[0138] 1 Information system 2 Server (information processing device) 3 Terminal 22, 34 Storage device 23, 35 Processor (control unit) 24, 36 Application 3675 Report M1, M2 Medical institution S1, S2, S3, S4 Specialized nurse (medical staff) G1, G2 General nurse (medical staff) V1, V2 Visiting nurse (medical staff) X1, X2, X3 groups

Claims

1. An information exchange method for exchanging information about a patient among a plurality of medical professionals using an information system, comprising: receiving a group creation request based on at least one of patient identification information identifying the patient and professional attribute information relating to medical expertise required to provide medical care to the patient; Searching for healthcare professionals who meet the group creation request; According to the search results, a group is created that includes at least one of a medical professional in charge of the patient and a medical professional having the medical expertise required to provide medical care to the patient, and the medical professional who made the group creation request; outputting template data corresponding to the created group; transmitting information about the patient input into the input fields of the template data at a terminal of one medical worker in the group to terminals of other medical workers in the group; A method of information exchange, including:

2. the group includes medical professionals with the medical specialty; The template data includes template data according to the medical specialty.

2. The information exchange method according to claim 1.

3. outputting a creation screen for creating the template data; creating the template data in response to an input from the medical professional via the creation screen; and storing the created template data in association with the group.

2. The information exchange method according to claim 1.

4. Accepting input of search conditions for template data; searching a database that stores the created template data in association with the group for one or more template data that match the search conditions, and outputting the search results in a selectable manner.

4. The information exchange method according to claim 3.

5. In the searching, the medical personnel in charge of the patient and the medical personnel having the medical specialty are searched for as the medical personnel that match the group creation request; In creating the group, the group is created to include the medical professional in charge of the patient, the medical professional having the medical specialty, and the medical professional who requested the group creation request.

2. The information exchange method according to claim 1.

6. the group creation request is based on the patient identification information and the professional attribute information; 6. The information exchange method according to claim 5.

7. In the searching, the medical professional who matches the group creation request is searched for from a database that stores medical professional identification information for identifying the medical professional and at least one of the patient identification information and the professional attribute information in association with each other.

7. The information exchange method according to claim 1.

8. the group creation request is based on the patient identification information; The database stores the patient identification information and the professional attribute information in association with each other.

8. The information exchange method according to claim 7.

9. The group is a group including at least one of the medical professional in charge of the patient and the medical professional having the medical specialty, the group including a plurality of medical professionals; 2. The information exchange method according to claim 1.

10. The medical professional with the medical expertise is a person who belongs to a medical institution associated with the patient.

2. The information exchange method according to claim 1.

11. In receiving a group creation request, the group creation request is received from a terminal of the medical worker who has made the group creation request.

2. The information exchange method according to claim 1.

12. The group is created for each of a plurality of patients who are the targets of information exchange by the information system.

2. The information exchange method according to claim 1.

13. a plurality of group creation requests different from each other are received for the same patient, and the group is created for each of the plurality of group creation requests; 2. The information exchange method according to claim 1.

14. a group is created that includes all of the medical professionals included in at least one of the groups created for the same patient; 14. The information exchange method according to claim 13.

15. and storing medical professional identification information for identifying a medical professional in association with at least one of the patient identification information and the professional attribute information.

2. The information exchange method according to claim 1.

16. generating a report including information about the patient transmitted from the terminal of the one medical professional in the group; 2. The information exchange method according to claim 1.

17. the information about the patient transmitted from the terminal of the one medical worker in the group is at least one of text data, still image data, and moving image data; 2. The information exchange method according to claim 1.

18. and further comprising: in response to a call request transmitted from the terminal of the one medical worker in the group, executing a voice call or a video call between the terminal of the one medical worker and the terminal of the other medical worker.

2. The information exchange method according to claim 1.

19. The medical professional with the medical expertise is a person who has a medical professional qualification, 2. The information exchange method according to claim 1.

20. The professional attribute information includes information indicating nursing expertise.

2. The information exchange method according to claim 1.

21. The professional attribute information is information indicating a type of nursing care, The group is created for each type of care provided to the patient.

2. The information exchange method according to claim 1.

22. The group includes a plurality of medical professionals who belong to different medical institutions.

2. The information exchange method according to claim 1.

23. A program for causing a computer to function as an information processing device included in an information system for exchanging patient information among a plurality of medical professionals, comprising: receiving a group creation request based on at least one of patient identification information identifying the patient and professional attribute information relating to medical expertise required to provide medical care to the patient; Searching for healthcare professionals who meet the group creation request; According to the search results, a group is created that includes at least one of a medical professional in charge of the patient and a medical professional having the medical expertise required to provide medical care to the patient, and the medical professional who made the group creation request; outputting template data corresponding to the created group; A program for causing a computer to function as the information processing device that transmits information about the patient entered into the input fields of the template data on the terminal of one medical professional in the group to the terminals of other medical professionals in the group.

24. An information system for exchanging patient information among a plurality of medical professionals, comprising: an information processing device and a terminal of the medical worker; The information processing device includes: receiving, from the terminal of the medical worker, a group creation request based on at least one of patient identification information for identifying the patient and professional attribute information related to medical expertise required to provide medical care to the patient; Searching for healthcare professionals who meet the group creation request; According to the search results, a group is created that includes at least one of a medical professional in charge of the patient and a medical professional having the medical expertise required to provide medical care to the patient, and the medical professional who made the group creation request; outputting template data corresponding to the created group; transmitting information about the patient input into the input fields of the template data at a terminal of one medical worker in the group to terminals of other medical workers in the group; Information systems.

Images