A chat system that integrates with medical systems owned by healthcare institutions.

Abstract

This system utilizes chat for sharing patient information among healthcare professionals, allowing for flexible and timely selection of information sharing partners while also providing a communication tool that respects the management of patients' personal information. [Solution] The chat system 2 is linked to a medical system 3A that includes patient information held by a medical institution. A chat room is created for each patient, linked to the patient information, and the chat content can be displayed by operating an electronic button or the like on the medical system. The chat room can be launched by the user using a URL launcher. When a chat room is launched, it has a function to link each patient to the chat room with patient information, and a function to link the user who launched the chat room to the chat room.

Description

Technical Field

[0001] The present invention relates to a computer tool (device, program, method) equipped with a chat system that cooperates with a medical system (such as an electronic medical record or PACS) owned by a medical institution and is provided to medical staff within the medical institution.

Background Art

[0002] Information sharing among medical staff of multiple occupations such as doctors, nurses, pharmacists, medical laboratory technicians, and physical therapists enables smooth cooperation in treatment through appropriate communication within the team, leading to the provision of optimal care for patients. On the other hand, this communication also involves information sharing including patients' personal information, and from the perspective of protecting personal information laws, the scope of information sharing must be carefully controlled. However, setting this sharing scope is troublesome, and even now, medical institutions still use PHS phones to make calls for communication or use paper-based operations for business design. The present invention is an invention to improve this situation.

[0003] For information sharing among medical staff, the tools and systems are important. With the electronic medical record (EHR / EMR) system, patients' medical records and treatment plans are digitized, and multiple occupations can check and update information in real time, making the cooperation in medical treatment smoother. In addition, conferences for discussing patients' treatment policies and meetings for sharing cases are regularly held to provide appropriate care. In addition, "handing over," which involves orally or in writing passing on important information during shift changes, is also important as part of the communication between teams.

[0004] Conventionally, information sharing such as conferences, meetings, and handovers has generally been carried out by medical staff gathered together within a medical institution. However, recently, there are examples where it is carried out using chat tools without gathering together.

[0005] The nurse call system described in Patent Document 1 integrates a nurse call system with a chat system, sharing the content of nurse calls, response status, completion reports, etc., through chat, thereby enhancing the convenience of the team nursing approach.

[0006] The server device described in Patent Document 2 allows users to join a chat room by sending a chat room URL via SMS. It is beneficial to receive non-voice information such as text, images, or videos through chat. To prevent SMS spoofing, two-factor authentication is implemented, enabling the exchange of highly confidential information.

[0007] The chat system described in Patent Document 3 supports team-based medical care, including decision-making and treatment. The system works in conjunction with an in-hospital information system installed in a medical facility and a chat system that runs an application (medical information sharing app) for sharing information about the medical treatment among team members constituting the care team. Through the medical information sharing app, medical information related to the medical treatment is shared with team members constituting the care team via mobile devices. [Prior art documents] [Patent Documents]

[0008] [Patent Document 1] Patent No. 6941572 [Patent Document 2] Patent No. 7456881 [Patent Document 3] Japanese Patent Publication No. 2023-116287

[0009] The technologies disclosed in any of the above patent documents have limitations in terms of the circumstances, content, and scope of information sharing within the team. Specifically, Patent Document 1 generates a chat room associated with a designated patient when the patient makes a nurse call, and deletes the chat room when the response is completed, meaning it is not intended for the permanent sharing of chat content. Furthermore, since participation in the chat room is limited to healthcare professionals belonging to the team in charge of a designated patient, the people with whom information is shared are predetermined, making it difficult to respond flexibly to medical needs.

[0010] Although Patent Document 2 uses an SMS message sent to a user who has been granted access to the chat room URL as the trigger for joining the chat room, it is limited by the fact that the user and the person in charge are pre-associated, as it reads data that links the user's interaction with the person in charge of handling the user's interaction to the data of the person in charge of handling the user's interaction. Furthermore, Patent Document 2 does not have a medical perspective.

[0011] Patent Document 3 describes a system that accepts patient information and information about persons involved in the patient's treatment, and then generates a chat room that can only be used by those persons, with the patient and persons being predetermined.

[0012] Thus, in systems where information sharing partners are predetermined, the addition of new users is not anticipated, and even if new users are added, they may only be able to share information incompletely. In healthcare, patient information includes highly sensitive personal information, and while it is preferable to have information shared only among predetermined members in order to strictly handle patient information, it is more convenient to be able to add members who can respond to the ever-changing condition of patients and share information. Furthermore, real-time information sharing is especially important in emergencies, as rapid and accurate information transmission can lead to saving patients' lives.

[0013] In medical chat, it's crucial to know who shares which patient's information, as it includes patients' personal information and requires strict management. However, setting who to share with each time is cumbersome and inconvenient, and a fixed set of sharing partners lacks flexibility.

[0014] Furthermore, being able to share the patient's past chat history with newly added members is effective in preventing medical errors and patient mix-ups. Since inaccurate or ambiguous information can lead to medical accidents and mistakes, it is effective to share clear and accurate communication through chat content, such as accurately conveying medication dosages and timings, or providing detailed reports on the patient's condition before and after surgery.

[0015] In addition, with conventional chat systems, the system can only begin operation after the chat creator sets up the chat members who will be sharing the information and then links the patient to that chat. Since patient information is stored in the medical system, this cumbersome workload can be reduced by utilizing the medical system to link with the chat system.

[0016] This invention has been made in view of these problems, and provides a communication tool (chat system, medical information processing device, medical information processing method, program) for medical professionals to share patient information using chat, which allows for flexible and timely selection of information sharing partners, while also taking into consideration the management of patients' personal information. [Overview of the Initiative] [Problems that the invention aims to solve]

[0017] Specifically, the present invention provides the following: The chat system is operated on a computer server having a processor and memory. Furthermore, channels / threads can be set up in the chat room generated for each patient, depending on the purpose and topic; in this case, the chat room can be replaced with a channel or thread.

[0018] (1) The chat system of the present invention is linked to a medical system that includes patient information held by a medical institution, such as an electronic medical record or PACS. In this chat system, one or more chat rooms, chat threads, or chat channels are opened for each patient for each user or each group user, and one or more chat rooms, chat threads, or chat channels can be opened or set by one or more operations such as electronic button operation, keyboard operation, or voice operation from the screen state of the medical system that includes personal information. One or more chat rooms, chat threads, or chat channels for the patient whose patient information is said to be opened by the user who performed the operation, or set for one or more of the user who performed the operation or the group to which the user who performed the operation belongs.

[0019] A chat system is a mechanism for users to communicate with each other. This system includes the concepts of individual "users" and "group users" that group them together. Furthermore, there are concepts of "chat sharing scope," such as "chat rooms," "chat threads," and "chat channels," which define the scope within which chat content is shared. These chat sharing scopes are controlled by setting the users or group users who are eligible to view the information, ensuring that only those users can view and share it. This mechanism enables efficient and limited information sharing among specific users or groups, allowing for the fine-tuning of communication spaces as needed. By setting chat sharing scopes, flexible information sharing tailored to needs becomes possible, such as sending messages to the entire user group, creating threads for specific projects, or establishing channels for specific topics, resulting in effective communication.

[0020] Chat, a communication tool, also has the concept of "mentions," which allows you to address a specific user by name within a message. This enables smooth dissemination of information and draws attention to specific individuals, such as sending notifications to mentioned users in the chat or inviting them to the chat sharing scope. While chat systems primarily focus on sharing text information, they can also share non-text information such as images and audio. Furthermore, chat also has the concept of "topics." Topics indicate specific agendas or themes within the chat sharing scope and serve to make it easier to organize the chat conversation. Topics can be set for each chat room or chat channel, allowing users to communicate efficiently based on those topics. For example, by setting a patient's initials, patient name, or room number with a date as a topic, users can easily understand which patient the conversation is about without misunderstanding, flexibly supporting efficient communication within a specific group, organizing and sharing information, and quickly contacting specific users.

[0021] This invention relates to a chat system used in medical institutions. This system has the functionality to link with medical systems such as electronic medical records and PACS (Picture Archiving and Communication Systems) that contain patient information, and allows the creation of patient-specific chat rooms, threads, and channels for each user or group. It is integrated with systems such as electronic medical records and PACS, and allows chat rooms to be opened with simple operations from a screen containing personal information. In addition to electronic medical records or PACS, medical systems containing patient information include departmental systems that manage information for each department such as cardiology, ophthalmology, otolaryngology, anesthesiology, radiology, and pathology, as well as attendance systems for doctors and nurses.

[0022] The system allows users to initiate chats, and healthcare professionals can easily create chat rooms and threads using electronic buttons, keyboards, voice commands, and other methods. Since a separate chat room is created for each patient, healthcare professionals can establish individual chat rooms / threads / channels for each patient, enabling communication based on patient information. Opened chats are configured for the user who initiated them and their group affiliations.

[0023] "For each user, a chat room (or thread, channel) is opened for each patient" means that for each user, a chat room is opened for each patient. By creating individual chat rooms or threads for each patient assigned to each medical staff member, a dedicated environment for communication based on the information of a specific patient is provided. This is a function aimed at information management for each patient and efficient cooperation among medical staff. In order to prevent confusion about which room is for which patient when multiple chat rooms are in disarray, it becomes possible to display the patient's name, initials, ward room number, etc. as topics in each chat room. When setting the topic of the chat room with the ward room number and initials of the patient, it is necessary to synchronize information with the medical system regularly or when the user browses or works. Also, group users refer to the groups to which the users belong, specifically groups within a medical institution such as the "Medical Affairs Section", "Department of Medicine", "Nursing Department", "Clinical Path Working Group", "Radiology Department", "Pharmacy Department", etc.

[0024] (2A) In cooperation with a medical system that includes patient information held by a medical institution such as an electronic medical record or PACS, a chat room for a user who responds to a patient is opened for each patient, and the chat content can be displayed by operating an electronic button of the medical system. That is, there is no existing chat system in cooperation with the medical system, and it is possible to easily open a chat room and display chat content from a medical system such as an electronic medical record or PACS. The user who responds to the patient is a medical staff member, corresponding to a doctor, nurse, pharmacist, medical affairs, etc.

[0025] (2B) The chat room can be launched by the user's operation of a URL launcher. That is, separately from the operation of the electronic button of the medical system, the chat app can be launched by the user's operation of the URL launcher without going through the medical system, and the chat content can be displayed, viewed, and spoken. Since the chat room launched by operating the URL launcher is linked to individual patient information, the user can respond based on that information when dealing with patients. This enables smooth information sharing among multiple department systems. In addition, the user's TOKEN can be added to this URL to share login authentication.

[0026] (2C) When opening the chat room, it has a patient information acquisition unit that acquires the patient information. The patient information acquisition unit has a function of associating and linking patient information when associating each patient with a chat room ( / channel / thread), and a function of associating the user who launched the chat room with the chat room ( / channel / thread). That is, the information acquisition unit has a function of associating a patient with a chat room and linking the patient information with the chat, and also has a function of associating the user (medical staff) who launched the chat room with that chat room.

[0027] With the above configuration, a tool is provided that opens an individual chat room for each patient and effectively utilizes the data of the medical system while managing the exchanges therein. This enables medical staff to communicate in an appropriate chat room while quickly and easily sharing patient information.

[0028] (3) By the operation, the URL launcher is executed, and the URL includes the patient information, the user information of the user who performed the operation, or the processed patient information obtained by processing the patient information and the processed user information obtained by processing the user information of the user.

[0029] A URL launcher is a function that allows users to open specific URLs (links to web pages or applications) with a single click, enabling direct access to external systems and web pages from within a chat system. This allows users to quickly open and use information and links shared within the chat, facilitating smoother integration with other systems, improving work efficiency, and enabling rapid access to information. For example, it can not only facilitate information sharing from medical systems to medical chat systems, but also allow setting URLs containing patient personal information within the medical chat system to trigger access to electronic medical records or PACS, or to view test results. This invention automatically launches a URL launcher (a function to open links) in response to user actions (buttons, keyboard, voice, etc.), and the URL contains specific information. The information contained in the URL includes patient information, such as the patient's information. It may also include information about the user's communication partners, the urgency of the user's communication, the user's login information, the patient's status (first visit or follow-up, outpatient or inpatient, first outpatient visit after discharge, reception status, waiting for tests), and terminal information (location). Furthermore, it may also include user information of the medical professional who initiated the chat. Alternatively, as processed information, patient information and user information may be included not in their original form but in some processed form. For security reasons, encrypted or converted information is used. In other words, it is not just a simple chat system, but a system with improved security and convenience. As a result of the operation, the URL launcher is activated, and a mechanism is in place to access external systems and linked systems with the necessary information included.

[0030] (4) As a result of the operation, a URL launcher is executed, and the URL contains one or more of the patient information and the user information that performed the operation or information processed from the user information, and contains one or more of the user information or information processed from the user information or information of the group to which the user belongs or information processed from information of the group to which the user belongs, and one or more of the patient's chat room, chat thread, or chat channel of the patient information is opened by the user that performed the operation or set for the user that performed the operation or for the group to which the user that performed the operation belongs.

[0031] This system features a mechanism that allows for more efficient creation and management of chat rooms, threads, and channels using a URL launcher, and specifically functions in the following way: • Launching the URL launcher via user interaction When a user performs an action to open a chat room, thread, or channel, the URL launcher is activated. • Information corresponding to the URL Patient Information User information of the user who performed the operation, or information obtained by processing that user information. Information about the group to which the user belongs, or information processed from that group information. Information about the user's communication partners Urgency of user communication User login information Status of entries in electronic medical records Order shipping information Patient status (first visit or follow-up, outpatient or inpatient, first outpatient visit after discharge, registration status, waiting for test results, test results available) Device information (location) • Creating and configuring a chat room Based on the URL, a chat room, thread, or channel related to the patient is opened by the user who initiated the interaction, or is configured for that user or the group to which the user belongs.

[0032] (Note) The chat system is characterized in that one or more chat rooms, chat threads, or chat channels can be set for each patient for each user or group user, and for each chat partner user or group user, and one or more chat partner users or group users can be set for each chat partner user or group user, and one or more chat rooms, chat threads, or chat channels can be opened or set by one or more operations such as electronic button operation, keyboard operation, or voice operation from the screen state including patient information of the medical system, and one or more chat rooms, chat threads, or chat channels for the patient in said patient information are opened by the user who performed the operation, or are set for one or more of the user who performed the operation or the group to which the user who performed the operation belongs, and one or more chat partner users or group users.

[0033] "Each chat partner user or each chat partner group user" refers to the user or group of users that a user intends to set as the information sharing partner when exchanging messages or sharing information in the chat system.

[0034] (5) The system is equipped with a mention function that automatically mentions the medical affairs department when content related to medical fees arises in the chat. (6) The chat system is equipped with a mention function that automatically mentions the relevant clinical group when clinically related content arises within the chat. (7) The chat system is equipped with a mention function that automatically mentions the relevant emergency response clinical group when an urgent clinical matter arises within the chat. Each aspect of this invention implements a mention function that automatically shares chat content with different departments or groups. Depending on the chat content, it can mention the medical affairs department, clinical group, or emergency group, and share the chat with the mentioned recipient. In other words, by utilizing the mention function of the mention unit, patient information can be shared easily and simply. Since the recipients of mentions are limited to medical professionals within the medical system, there is no risk of patient information being leaked to outsiders. A mention is a function in communication tools such as social networking services that allows you to send a message or notification directly to a specific user. By using mentions, the user receives a notification, making it easier for them to notice your message.

[0035] (8) It has a function to mention a physician in charge of emergency response with an alert, and is equipped with an SMS linkage unit that automatically notifies the physician of the emergency details via SMS. (9) When an SMS notification is sent, the system is equipped with a function to anonymize the patient information, omitting the name of the ward or outpatient clinic, and reporting in the notification content in the format of "An SMS has been sent regarding Ward XX." (10) The SMS notification sent to doctors outside the hospital was equipped with a function to generate messages that included only anonymized patient information and did not contain any personal information of the patient. (11) When a physician who has received the SMS notification calls the designated phone number and enters the authentication ID notified by SMS according to the voice guidance, the AI ​​system has a voice response unit that reads out anonymized patient information based on the ID. In other words, in emergencies, an emergency mention with an alert can be sent via SMS to prompt a doctor to take immediate action. Since doctors are often outside the hospital when responding to emergencies, the SMS notification is generated in a format that includes only anonymized information and does not contain the patient's personal information. If patient information is needed, the anonymized patient information is read aloud using the authentication ID notified via SMS, thereby preventing the leakage of personal information to external parties. In other words, it strengthens alert notifications to doctors in emergency situations, sending information to doctors via SMS, especially when an emergency response is necessary. It also takes into consideration the anonymization of patient information, conveying urgency while protecting privacy.

[0036] (12) When a mention is made via chat, the system will be equipped with a knowledge support unit that will link with the knowledge support system and provide relevant clinical guidelines and medical fee information in real time based on the content of the mention. According to the present invention, the system is linked with a knowledge support system and presents relevant clinical guidelines and medical fee information in real time based on the mention content. This allows the mentioned person to be presented with the necessary knowledge in real time, thereby supporting faster patient response.

[0037] (13) When a member logs into a chat, they can see the conversations within their respective groups. According to the present invention, members of the medical affairs department, clinical group, and emergency response clinical group can view the chat content of their respective groups, thereby enabling them to understand the status of the group to which they belong. In other words, when a member of a group logs into the chat, they can view the chat content shared within that group, thereby promoting information sharing within the group and supporting smooth communication.

[0038] (14) The system includes an erasure unit that automatically erases the chat content related to an approval made within the chat, or erases the content after a certain period of time has elapsed. According to the present invention, by incorporating an automatic deletion function, it is useful in information management in medical settings for protecting security and privacy, and preventing the accumulation of unnecessary data.

[0039] (15) Register it in the medical system's to-do list. According to this invention, by registering TODOs (lists or notes for managing things to do or tasks) in a medical system, it becomes easier to manage TODOs linked to chat content.

[0040] (16) The system includes a viewing privilege granting unit that grants the attending physician the privilege to view all chat content related to the patient. According to this invention, by allowing the attending physician to view all chat content related to a patient, the physician can understand not only the details of the patient's care but also information such as medical fees and emergency responses. This provides important information to the attending physician who is directly involved in the patient's treatment, thereby improving the quality of medical care.

[0041] (17) When a chat room is created for the same patient for the second time or later, the same chat content (chat room / channel / thread) will be visible to the mentioned user. According to this invention, once a user who has been mentioned creates a chat room and is linked to the patient, subsequent mentions will also result in the same chat room being created for the same patient, and the same chat room content will be visible, which helps in understanding the patient's post-treatment situation. This promotes information sharing among stakeholders and allows for more consistent patient care.

[0042] Furthermore, the URL launcher incorporates patient ID information and chat room purpose information, making it clear which patient's information will be shared with whom and for what purpose when a chat room is launched. When people are added to the chat room, that room will appear first. The URL launcher also allows you to configure who will be sharing information based on how the URL is created.

[0043] For example, if a chat room is created for discussing patient A, as envisioned by Dr. B, Dr. C can be added via mention. When Dr. C opens a link to patient A's information using his own URL, he will be directed to a chat room if one already exists. However, Dr. C can also create a separate chat room. For example, if the collaboration of multiple specialists is needed, a new chat room can be created for the patient. When the attending physician mentions a specialist saying, "I'd like to hear your opinion on XX," the mentioned specialist is immediately invited to the chat room and can see the same content in real time. Each doctor can share their opinions and advice, and important decisions regarding patient care can be made quickly.

[0044] Regarding patient A, while multiple chat rooms for discussion should be permitted, it is preferable for patient chat room management purposes to unify discussions within an existing chat room and use that chat room as the basis for communication. [Effects of the Invention]

[0045] According to the present invention, by utilizing patient-specific chat rooms for information sharing among healthcare professionals and linking them with medical systems owned by healthcare institutions, it is possible to appropriately manage personal information within the medical system while also enabling flexible and timely configuration of information sharing partners. [Brief explanation of the drawing]

[0046] [Figure 1] A diagram showing the network configuration of chat system 2. [Figure 2] A block diagram showing an example of the configuration of chat system 2. [Figure 3] A block diagram showing an example of the functional configuration of in-hospital terminal 1. [Figure 4] A block diagram showing an example of the functional configuration of chat system 2. [Figure 5] A flowchart illustrating the processing steps of an application program executed in Chat System 2. [Figure 6]A flowchart illustrating the processing steps of an application program executed in Chat System 2. [Figure 7] An example of the chat system screen display. [Figure 8] An example of the chat system screen display. [Best Mode for Carrying Out the Invention]

[0047] Figure 1 shows the network configuration centered around chat system 2. In addition to the computer running chat system 2, hospital terminal 1, medical system 3A, and mobile terminal 4 are connected via a network using telecommunications lines such as the internet, intranet, and hospital LAN.

[0048] Chat System 2 is a computer for sharing medical information among members of a medical team for each patient using chat. In-hospital terminals 1 is a general term for terminals such as examination room terminals operated by doctors, laboratory terminals operated by laboratory technicians, medical affairs terminals operated by maintenance staff, clinical department terminals operated by clinical groups, and emergency clinical department terminals operated by emergency clinical groups. Medical system 3A manages various types of medical information related to medical treatment performed at medical facilities. It is a general term for a configuration consisting of various systems such as hospital information systems (HIS), picture archiving and communication systems (PACS), electronic medical recording systems (EMR), and radiology information systems (RIS). Mobile terminals 4 are mainly intended for medical personnel outside the hospital who can access the network from outside the hospital, and are assumed to be devices capable of SMS communication, such as smartphones and tablets.

[0049] Chat System 2 is a computer that runs an application for sharing patient medical information among healthcare professionals. Chat System 2 is linked to the medical system via a network and manages the proper sharing of medical information by appropriately referencing information within the medical system according to commands and instructions from in-hospital terminal 1 and mobile terminal 4. Primarily, Chat System 2 runs an application (chat app) for exchanging messages among members.

[0050] Figure 2 is a block diagram showing an example of the configuration of chat system 2. Chat system 2 is connected to medical system 3A via a network and is capable of communicating with in-hospital terminal 1 and mobile terminal 4. Chat system 2 is a computer connected to a network such as the Internet and includes a communication IF 22, an input / output IF 23, memory 25, storage 26, and a processor 29.

[0051] Communication IF22 is an interface for inputting and outputting signals so that the chat system 2 can communicate with external devices. Input / Output IF23 functions as an interface to an input device for receiving input operations from the user and an output device for presenting information to the user. Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM. Storage 26 is a storage device for saving data, such as flash memory or an HDD. Processor 29 is hardware for executing the instruction set written in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0052] Figure 3 is a block diagram showing an example of the functional configuration of the in-hospital terminal 1, comprising a communication IF 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19. The communication IF is an interface for inputting and outputting signals so that the in-hospital terminal 1 can communicate with external devices, and also functions as an interface to the input device 13 for receiving input operations from the user and the output device 14 for presenting information to the user. The input device 13 is an input device (such as a keyboard, touch panel, touchpad, mouse, or other pointing device) for receiving input operations from the user. The output device 14 is an output device (such as a display or speaker) for presenting information to the user.

[0053] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM. Storage unit 16 is a storage device for saving data, such as flash memory or HDD. Processor 19 is hardware for executing the instruction set written in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0054] The device is operated by medical professionals (doctors, nurses, laboratory technicians, office staff, assistants, etc.) at a medical institution. Terminal 10 connects to the network 80 by communicating with communication devices such as a wireless base station 81 that supports various communication standards such as LTE, and wireless LAN routers that support IEEE and wireless LAN standards. Terminal 10 can be a desktop or laptop PC, a tablet, or a smartphone.

[0055] In-hospital terminal 1 is a desktop or laptop PC, and mobile terminal 4 is a tablet or smartphone, etc., and generally has publicly known and general-purpose functions.

[0056] Figure 4 is a block diagram showing an example of the functional configuration of the chat system 20. The chat system 20 comprises a communication means 220, a storage means 280, and a control means 290, with each block being electrically connected by a bus or the like. The communication means 220 implements the functions of the communication IF 22, the storage means 280 implements the functions of the memory 25 and storage 26, and the control means 290 implements the functions of the processor 29.

[0057] The communication means 220 performs modulation and demodulation processing for the chat system 20 to communicate with other terminals, namely the medical system 3A, the in-hospital terminal 1, and the mobile terminal 4. It then processes the signal calculated by the control means 290 and transmits it to the external terminal. The communication means 220 processes the signal received from the outside and outputs it to the control means 290. In this way, the communication means 220 interprets commands or input content and provides them to each means, and also functions as an interface that interprets various display commands issued from the storage means 280 and controls the output.

[0058] The storage means 280 is implemented by memory (RAM) 25 and storage 26 such as a disk device (floppy disk, hard disk, or magneto-optical disk, etc.) and stores data, programs, etc. used by the chat system 20. The storage means 280 stores the application program 282 (chat app) of this system, as well as data for the work area 281, data storage area 283, and screen definition storage area 284.

[0059] The work area 281 is allocated upon startup of this system and is an area where various data input and output by this system are temporarily stored. The data storage area 283 is an area where data temporarily stored in the work area 281 is semi-permanently stored through write control when a save request is made. The screen definition area 284 is an area where screen definition information for various screens to be output and displayed to terminals 10 and 30 is stored in advance, and includes format information for the screen settings to be displayed.

[0060] The input device 230 is a device for users operating the chat system 20 to input instructions or information, and may be a keyboard, mouse, reader, or touch-sensitive device. The input device 230 also converts the instructions input by the user into electrical signals and outputs the electrical signals to the control means 290. The input device 230 also includes a receiving port that accepts electrical signals input from external input devices. The output device 240 is a display device 241 such as an LCD or organic EL for presenting information to the user operating the chat system 20. The display 241 can display data according to the control content of the control means 290 and can check the communication status between the chat system 20 and other external devices.

[0061] The control means 290 is realized when the processor 29 reads the application program 282 stored in the storage means 280 and executes the instructions contained in the application program 282. The control means 290 also controls the operation of the chat system 20, the in-hospital terminal 1 and the mobile terminal 4, and by operating according to the application program 282, it performs functions as a patient information acquisition unit 291, a mention unit 292, an SMS linking unit 293, a voice response unit 294, a knowledge support unit 295, a deletion unit 296 and a viewing privilege granting unit 297.

[0062] The patient information acquisition unit 291 acquires patient information from the medical system 3A when a patient's chat room is established. The patient information acquisition unit 291 has a function to link patient information when associating each patient with a chat room, and a function to link the user who established the chat room to the chat room. In other words, patients and medical professionals are linked through the chat room, patient and medical professional information can be obtained from the medical system 3A, and the chat room is established by the chat application of the application program 282.

[0063] The mention unit 292 links the user who made the mention with the user who was mentioned. In addition, it monitors the chat content, and the AI ​​analyzes the relevant department based on the chat content and automatically mentions that department. The relevant department can be obtained from the registration information in the medical system 3A. If a chat room for that patient already exists, the mention will direct the user to that chat room.

[0064] SMS Coordination Unit 293 notifies the group responsible for the emergency via SMS when an urgent clinical situation arises in the chat and the group responsible for the emergency response is mentioned. The SMS notification anonymizes patient information and does not include the name of the ward or outpatient clinic, reporting in the format of "An SMS has been sent regarding ward XX." The notification content from SMS Coordination Unit 293 is generated in a format that includes only anonymized information and does not include the patient's personal information.

[0065] The voice response unit 294 reads aloud anonymized patient information based on the authentication ID provided in the SMS notification when a doctor who has received the SMS notification calls the designated phone number and enters the authentication ID. The patient information includes important information that should be strictly managed from a privacy perspective, such as basic information (name, date of birth, gender, address, contact information, medical history), past illnesses and treatments (surgical history, allergies, current symptoms), chief complaint (main symptoms the patient is currently experiencing, onset date and progression, examination results), diagnosis (examination findings, test results (blood tests, imaging, etc.)), prescription / treatment policy (prescribed medications, treatment plan, necessity of surgery), lifestyle (smoking, drinking habits, diet, exercise status, living environment), and family history (presence or absence of genetic diseases in the family). The system generates anonymized patient information and reads it aloud. Profile information such as the patient's name is also included. The system primarily uses anonymization processing on personal information to create voice information to be read aloud, and then reads this voice information aloud.

[0066] The emergency response mention and alert function automatically generates an alerted mention when a highly urgent situation (e.g., "critical condition," "immediate action required") is detected in the chat. The physician in the mentioned emergency response group will receive a visually highlighted alert (sound, color, pop-up, etc.) in parallel with their regular chat notification. Additionally, emergency response physicians registered in the system will receive an additional emergency notification via SMS.

[0067] The SMS Integration Unit, which has the function to send SMS messages, obtains the contact information (such as phone numbers) of registered doctors by referring to the registered doctor information in Medical System 3. SMS sends a summary of the emergency as a short text message. For example, a notification may be sent in the following format: "Emergency response required. Patient ID: 12345, Symptoms: Sudden deterioration, please respond." Note that the patient ID: 12345 may not be included in the notification content, and the URL of the relevant chat may be sent via SMS. The patient's name, ward name, and outpatient name will not be included in the SMS notification. Specifically, the information included in the SMS will be kept to a minimum so that it cannot be identified from the outside. The URL to be notified has a filtering function that automatically masks patient information and minimizes the information included in the SMS. Since SMS communication itself is not encrypted, caution is required regarding the information sent. Therefore, only anonymized information will be sent, and detailed data will be managed within the secure Medical System 3. Detailed response information can be checked using a dedicated chat room that is accessible only to authenticated doctors.

[0068] Knowledge Support Unit 295 is linked to Knowledge Support System 3B and acquires knowledge information related to clinical guidelines and medical fees. Knowledge Support Unit 295 presents knowledge information in real time based on mentions in chat content. Since the knowledge support content does not include patients' personal information, it can be obtained from a server on the internet separate from the medical institution.

[0069] The deletion unit 296 deletes all chat content or parts of chat content in an opened chat room. When approval is made within a chat or thread, the content of the chat or thread related to the approval is automatically deleted. Alternatively, the content is automatically deleted after a certain period of time has elapsed. Automatic deletion after approval means that when approval is made within a chat or thread, the content is automatically deleted at a certain time. Approvals include, for example, confirmation of medical procedures, approval of treatment plans, and approval of medical fee applications. Information that has been approved is deleted because there is no need to retain it excessively. Automatic deletion after a certain period of time means that even if no approval is made, chat content is automatically deleted after a certain period of time has elapsed, preventing past chat history from creating unnecessary burdens or risks of information leakage. The time setting can be adjusted according to the policies of the hospital or medical institution, for example, 24 hours, 1 week, or 1 month.

[0070] The TODO registration unit 297 creates a TODO list based on the chat content and registers the created TODO list in the medical system 3A's TODO section. Based on the conversations and exchanges in the chat, important tasks are recorded without being overlooked, and staff and doctors can track and confirm those tasks. For example, if the chat contains messages such as "Please check XX" or "Please carry out YY," or if the message includes words like "task," "request," or "confirm," the content is automatically reflected in the medical system's TODO list, saving the effort of manually registering tasks and allowing necessary work to be recorded in the TODO section in a timely manner. In addition, if the user explicitly wishes to register a task, they can also manually register the chat content to the TODO section by pressing a button or entering a command.

[0071] The access privilege granting unit 298 grants the attending physician, hospital director, etc., the privilege to view all chat content related to the patient. A flag is set in chats linked between the patient and the attending physician, etc., to indicate that the attending physician has been granted access privileges. For example, when a patient is newly hospitalized, the attending physician is immediately granted access to view the chat. In addition, for information gathering during emergencies, when patient information is shared via chat in an emergency, the attending physician can check the content in real time, allowing them to understand the judgments and responses of other medical staff and to provide prompt instructions and treatment.

[0072] The URL assignment unit 299 generates and assigns URL information that allows access to a chat room for each patient. By including "information about the patient ID and the purpose of the room" in the URL, it is possible to clarify which patient's information is being shared. The way the URL is created also allows setting who the information is shared with.

[0073] Figure 5 is a flowchart illustrating the processing procedure for chat system 2, showing the flow of opening a chat room from the electronic medical record system. The electronic medical record system corresponds to medical system 3A.

[0074] The electronic medical record system electronically stores each patient's electronic medical record linked to their patient ID, and a "Chat" button is displayed on the patient's electronic medical record screen. When a healthcare professional clicks the "Chat" button (step S501), the system determines whether a chat room already exists for that patient (step S502). If a room does not exist, a new chat room is created (step S503).

[0075] Regardless of whether a new chat room needs to be created, users are linked to the room (Step S504). Users who create a chat room, such as the patient's doctor, are linked to the chat room.

[0076] In the chat room linked to the user and the patient, the URL assignment unit 299 constructs an internet / intranet URL (step S505). The constructed and assigned URL is registered in the URL launcher (step S506), and a URL link is placed on the electronic medical record "chat" button. Clicking the "chat" button jumps to the linked URL site.

[0077] Here, when generating a URL for use in the URL launcher, the URL is constructed according to the purpose and required information. That is, specific information is added using query parameters to indicate which patient the chat is about and what aspect of the patient's information (clinical, emergency care, medical fees, etc.) the chat (room / channel / thread) is about. Mentioned users can also be used to generate dynamic URLs, receiving information about the mentioned users from the medical system 3 and generating a URL that reflects this in the parameters.

[0078] Figure 6 is a flowchart showing the processing steps of the chat system 2, illustrating the process of sharing chat content using the mention function.

[0079] The mention unit 292 of the chat system 2 monitors the chat content to determine whether a mention is necessary (step S601), and uses keyword search to determine if a specific topic exists in the chat content (step S602). If there is no specific topic, it continues to monitor the chat content.

[0080] If a specific topic arises, the topic is analyzed and mentioned to the relevant department (step S603). Specific topics include, for example, content related to medical fees, content related to clinical practice, and content related to emergency clinical practice. Mentions are sent to the relevant departments, namely the medical affairs department, the clinical group, and the emergency clinical group's in-hospital terminal 1 or individual terminals connected within those groups.

[0081] Furthermore, if the content requires knowledge support as a specific topic, such as keywords related to topics like "medical fees" or "clinical guidelines," the system will present relevant information (step S604). Natural language processing (NLP) is used for analysis, allowing the AI ​​to understand the intent and theme of the mention and access information sources from the knowledge support system 3B to retrieve the information. For clinical guidelines, the system will present the latest guidelines regarding disease diagnosis and treatment policies. For information on medical fees, it will display the latest regulations and rules regarding medical fees and insurance claims based on the mention, and provide links and summaries of papers based on evidence for the relevant treatments and drugs as relevant papers and evidence.

[0082] Chat content monitoring involves analyzing the chat content using natural language processing (NLP) to analyze the text in the chat in real time and making mentions if specific trigger words (e.g., "medical fee" or "emergency") are included. Based on the analysis results, if the chat content relates to medical fees, it is automatically distributed to the "Medical Affairs Department," if it is clinically related, to the "Clinical Group," and if an emergency response is required, to the "Emergency Response Group." Each group and department is pre-registered in the medical system 3, and the mention unit refers to these groups to select the appropriate notification recipient.

[0083] Furthermore, the mention unit 292 also works in conjunction with the SMS linkage unit. In case of emergency, it notifies the emergency clinical group to which the patient belongs, sounds an alert, and notifies the emergency details via SMS. When a physician receives an emergency SMS, they call a designated phone number and enter an authentication ID. The voice response unit 294 then creates anonymized patient information based on that ID and reads that information aloud.

[0084] When a mention is made, the Knowledge Support Department 295 collaborates with the Knowledge Support System 3B to provide relevant clinical guidelines and medical fee information in real time based on the content of the mention.

[0085] When the URL launcher is operated from an in-hospital terminal 1 or mobile terminal 4, it jumps to a link to a chat room URL unique to each patient. The URL contains the patient ID and other parameters, and the system retrieves the corresponding patient's information from the medical system 3. By including parameters such as patient_id and user_id in the URL, the chat room can be linked to the patient and the corresponding user. The patient information retrieval unit uses the patient_id included in the URL to retrieve the relevant patient information (name, age, gender, examination details, test results, current medical history and treatment details, and image diagnostic data (obtained from PACS)) from the electronic medical record (EMR) or PACS, and associates it with the chat room. The user_id included in the URL can be used to record and track the medical staff who accessed the chat room. This makes it clear who is responding in which patient's chat room.

[0086] Furthermore, the operation of the URL launcher from the mobile device 4 uses a pseudo-ID that does not include patient_id to prevent the external leakage of patient ID personal information. In this case, if multiple URLs exist for the same chat room for the same patient, these URLs are merged into a unique URL in order to access the same chat room. In this case, the chat system 2 has a function to redirect to a unified URL in response to access from the mobile device 4, so that the same chat room can be used. Due to the redirect function based on patient_id, even if the user_id is different, for example, the chat room itself is consolidated based on patient_id, so multiple users can access it.

[0087] Multi-factor authentication (MFA) can be implemented to enhance member identity verification when logging into the chat. A session timeout function maintains security by automatically logging users out after a certain period of inactivity.

[0088] Figures 7 and 8 show examples of the chat system screen display. Figure 7 shows an example of the electronic medical record display of a medical system, where an electronic button B for the "Medical Office Collaboration" launcher for sharing with medical office staff and an electronic button A for "Patient Room Chat" for sharing with clinical staff are placed on a screen containing personal information such as basic information. The launcher application is activated by clicking or touching the electronic buttons. Figure 8 shows an example of the chat room display where the system monitors the user's statement "Please specify the medical fee" and automatically sets the recipient for the "medical fee" statement, and the system also monitors the user's statement "Please bill for the chronic disease management surcharge" and adds it to the to-do list. At that time, the recipient of the to-do is also automatically set. The automatically set users and mentioned users can view the chat content related to the medical fee.

[0089] This embodiment describes a process for capturing screens of medical systems used within a medical institution and sending them as digital data to a chat channel using OCR (Optical Character Recognition) technology. For example, scanned information from patient documents or screens of electronic medical records can be captured and sent to the chat. In this process, area extraction and OCR technology can be automatically applied to the captured information to extract text information from the image and send it to the chat channel as text data in real time. This process makes it possible to easily digitize and share image information, allowing medical professionals such as doctors and nurses to efficiently access patient information. It is also possible to automatically extract the screen of an electronic medical record, identify the previous text or the most recent medical record entry, and send the content written there to the chat.

[0090] The specific operation flow is as follows: when information containing personal information is displayed on the medical system screen, the user can take a screenshot of the medical system screen by using electronic buttons, keyboard input, or voice commands. This screenshot is then sent as data to the chat room or channel of the chat system. At this time, it is possible to send the screenshot as image data, or to use OCR technology to convert the content into text before sending it.

[0091] In this way, the integration of chat systems and OCR technology allows for the efficient digitization and sharing of analog handwritten information and information displayed on medical system screens, improving the speed and accuracy of information transmission and contributing to the efficiency of patient care and medical treatment.

[0092] (Copy to clipboard) This embodiment describes a process for sending text data from a medical system used within a healthcare facility to a channel in a chat system. It describes a function that copies the content of the most recently focused information block (such as a text area or data field) within the medical system to the clipboard and then sends that content to a channel in the chat system. With this function, when a user selects specific information (such as a patient's vital signs or medical notes) in the medical system, they can operate a shortcut key or a dedicated button, which automatically copies that information to the clipboard and then sends it as text to the chat channel. Because it transmits content that already exists as digital text without using OCR (Optical Character Recognition), information sharing is quick and easy. Specifically, the user copies the focused text to the clipboard using a keyboard shortcut, electronic button, or voice command, and simultaneously sends the text to the chat system. This process is simple and speedy, and because it allows for the transmission of information directly from the screen, information can be shared while maintaining accuracy.

[0093] (Workflow integration) This embodiment describes a method for efficiently and accurately performing tasks related to the calculation of outpatient surcharges and other additional charges by implementing a chat system linked to the workflow as a function to prevent omissions in medical fee calculations. Specifically, multiple buttons are installed in the system, each with a designated medical fee surcharge item. When a medical professional presses one of these buttons, a workflow is triggered in which the medical staff receiving the chat information selects the appropriate surcharge. The medical office staff then automatically presents the basis for the surcharge and an explanation of the related medical treatment to the administrative staff via chat, enabling error-free calculation by the medical office staff. For example, when a patient receives a specific procedure, pressing the outpatient surcharge button copies the contents of the medical record to the chat, and the administrative staff can join the room and calculate the medical fee while reviewing the information. This mechanism ensures that the information necessary for calculating medical fees is provided in a timely manner through the chat system, preventing omissions and errors. Furthermore, because the chat system and workflow are linked, the operation status of the set buttons and the progress of the surcharge work are displayed as a checklist in the chat room. This checklist allows administrative staff to quickly understand which additional charges have been selected and what the basis for those charges is, and it also functions as a tool to verify that medical fee calculations are being performed accurately and appropriately.

[0094] This system eliminates the need for medical staff to worry about which additional charges to claim, and allows for more efficient information provision to administrative staff. Furthermore, the system supports an automated process of presenting and verifying information, improving administrative efficiency and reducing instances of missed or inaccurate calculations of outpatient medical fees. As a result, it enables the optimization of revenue across the entire healthcare institution and ensures accurate operational performance.

[0095] (TODO management) This embodiment describes a method for adding patient-related tasks to a "TODO list management system" linked to a chat system through operations on the medical system, and sharing them with relevant parties. By performing specific operations from the medical system screen, tasks corresponding to the patient's medical treatment and procedures can be efficiently added to the TODO list, allowing for smooth management of the overall workflow. Specifically, when a patient's medical information or test results are displayed in the medical system, performing a necessary action (such as clicking a button, selecting a menu item, or entering a shortcut key) automatically registers a task related to that patient into the to-do list. This action links the chat system and the to-do list management system, automatically sharing the details of the added task (task content, assigned person, deadline, etc.) with relevant parties. For example, if a patient requires additional tests, clicking the "Request Test" button in the medical system generates a to-do task related to the tests, and a real-time notification is sent to the relevant personnel in charge of the tests. In this way, tasks can be added directly from the medical system to the to-do list, eliminating the need for information transcription and manual input, and significantly improving work efficiency. Tasks are shared through the chat system, allowing staff to quickly see new tasks and respond promptly based on priority and deadlines. For example, various patient-related tasks, such as calculating medical fees, rescheduling treatments, and adjusting patient prescriptions, can be easily registered to the to-do list through operations within the medical system. Furthermore, tasks registered in the to-do list can be viewed and completed by relevant parties within the chat system, allowing for real-time tracking of task progress. This makes the status of work visible and prevents tasks from being missed or delayed. In addition, when the progress or completion status of a task is updated, all relevant parties are notified, facilitating smooth information sharing throughout the team.

[0096] This type of collaboration is expected to enable the addition and management of patient-related tasks through operations from the medical system, thereby improving operational efficiency, supporting smooth team communication, and contributing to an improved quality of patient care.

[0097] (Return the information to the electronic medical record) This embodiment describes a function that automatically returns information shared in a chat system to the electronic medical record. When important information such as conversations about patients, treatment details, and test results are shared in the chat, a button is provided to seamlessly reflect that information in the electronic medical record. Because this function integrates the chat system and the electronic medical record system, manual transcription work is eliminated, and the accuracy of information and work efficiency can be greatly improved. Specifically, when doctors and nurses share patient treatment details and test results via the chat system, a button is available that allows them to return that information to the electronic medical record with a single click. By pressing this button, the selected chat content is automatically registered in the electronic medical record, and the medical records and instructions are reflected in the chart. This eliminates the need for healthcare professionals to manually transcribe patient medical information, ensuring information consistency. Furthermore, because notes and instructions made in the chat are directly registered in the electronic medical record, real-time updates of the medical process become possible. This function can be integrated with URL launchers and RPA (Robotic Process Automation) to configure the data return process. Through these functions, information sharing within the chat system and information reflection in the electronic medical record are seamlessly linked, leading to timely updates of patient care information and increased efficiency in medical practice. Ensuring data accuracy and speed of operation reduces the burden on healthcare professionals and significantly contributes to improving the quality of patient care.

[0098] (Updated when moving to an anonymous room) In this embodiment, a method will be described in which topics and chat rooms describing patient information in the chat system are automatically synchronized according to the movement of the patient. This function has two approaches. One is a method of sending a push notification when updating information from the electronic medical record (EMR) to the chat system, and the other is a method of checking information each time the user browses a chat room. In actual operation, the latter method of checking during user browsing is assumed to be the main method. In the push notification approach, when updates such as a patient's ward transfer or department change are made on the electronic medical record side, the information is automatically notified to the chat system. As a result, the chat system is immediately informed that related chat rooms and topics in the chat system have been updated, and a mechanism is in place to immediately reflect changes in patient information in the chat system. This makes it possible to automatically update information when topics are anonymized using the patient's room number or initials, etc.

[0099] In this embodiment, a function for the user to list and check chat rooms, TODO lists, and workflows related to themselves will be described. In a medical setting, there are a wide variety of tasks related to assigned patients, team tasks, and ongoing work procedures, so efficient information management and checking are required. With this function, the user can efficiently check information related to themselves in one place and smoothly take necessary actions.

[0100] <<List of Chat Rooms>> The user can check a list of all chat rooms in which they are involved. The chat rooms are divided by patient, department, specific task, etc., and related topics are clearly displayed. Each chat room shows the number of unread messages, the number of mentioned messages, and the latest update information, so the user can quickly identify the rooms that need to be prioritized for checking. Also, with the filter function, it is possible to display only chats related to specific patients or tasks, enabling efficient access to information. <<Checking the TODO List>> The user's assigned to-do list can also be viewed from the same screen. The to-do list displays tasks such as patient care, administrative work, test requests, and treatment plan updates for each individual user. Each task has a priority and deadline, allowing users to efficiently complete tasks according to their daily schedule and workload. In addition, the status of each task (not started, in progress, completed) is visible at a glance, and relevant parties are notified when the status is updated, enabling real-time sharing of work progress. <<Workflow Progress Management>> Furthermore, users can also check the progress of the workflows (business procedures) they are involved in. Workflows visually display a series of procedures that occur in a medical setting, such as patient treatment procedures, examination schedules, and medical fee calculation flows. Each step of the workflow has a designated person in charge and a deadline, and the progress and the next actions to be taken are clearly indicated. This allows the entire team to get an overview of the workflow and prevent tasks from being missed or delays from occurring.

[0101] In this embodiment, the chat system can grasp parameter information pre-configured in the electronic medical record (EMR) and perform the following operations and display information according to the parameter status (input of examination examples, input of prescription examples, input of copied medical record contents, display of endoscopic examinations, display of templates, display of buttons linked to instructions for the EMR). This function allows doctors and medical staff to quickly access necessary information according to the situation during patient consultations, as well as to efficiently record medical content and prescribe medications. Furthermore, the parameter information used and the specific content to be displayed are adjusted based on the following elements. <<Patient's condition (Examples of initial visit / follow-up visit)>> The parameter settings determine whether the patient is a first-time or returning patient, an outpatient or inpatient, or a first outpatient visit after discharge, and then provide functions within the chat system accordingly. For example, first-time patients will be offered suggestions for necessary tests, while returning patients will be shown buttons for copying and entering past medical records. The situation is confirmed based on information from the electronic medical record, and notifications and suggestions tailored to that information are automatically presented. <<User Information (Example of Medical Department)>> The system retrieves medical department information from the user's device and displays buttons associated with instructions relevant to that department. For example, in gastroenterology, the option for endoscopy is presented, and in ophthalmology, information related to fundusoscopy is displayed, providing guidance on necessary examinations and procedures for each medical department. <<Device Information (Example Location)>> The system retrieves parameter information about the location of the terminal being used by the user and displays buttons associated with instructions relevant to that location. For example, in an operating room, it provides instructions for ordering blood transfusions or blood gas analysis, and in an endoscopy room, it provides instructions for endoscopy-related procedures, etc., providing guidance tailored to the specific location. <<Contents of the electronic medical record>> Based on the information and circumstances recorded in the electronic medical record, notifications and suggestions are automatically sent to healthcare professionals. Depending on the contents of the medical record, suggestions for additional necessary tests, advice on medication prescriptions, and prompts for confirmation of medical records and input of additional information may be made. In addition, templates and buttons are provided as needed for each medical department, enabling efficient input and recording in the electronic medical record. In this way, by using set parameters and real-time status monitoring, healthcare professionals can quickly and efficiently obtain the information and perform the necessary actions for patient care, thereby improving the quality and efficiency of medical treatment. [Industrial applicability]

[0102] This invention utilizes chat for sharing patient information among healthcare professionals, and by using the mention function, it is possible to flexibly set who shares the chat content, making it a useful communication tool among healthcare professionals.

[0103] [Note B] The program runs on a computer server having a processor and memory. [B1] A chat system program that runs on a computer server having a processor and memory, and is linked to a medical system. The aforementioned chat system allows for the creation of one or more chat rooms, chat threads, or chat channels for each patient, for each user or group of users. From the screen state containing personal information of the aforementioned medical system, one or more user operations such as electronic button operation, keyboard operation, or voice operation can open or set one or more chat rooms, chat threads, or chat channels. The patient's chat room, chat thread, or chat channel is opened by the user who performed the operation, or is set for the user who performed the operation or for one or more of the groups to which the user who performed the operation belongs. [B2] One or more of the aforementioned chat rooms, chat threads, or chat channels can be opened by a user or group user using a URL launcher. When opening, the processor has a patient information acquisition unit that acquires the patient information, The aforementioned patient information acquisition unit, • A function to link patient information when associating each patient with a chat room, The program described in [B1] is characterized by having a function to associate a user who has opened a chat room with the chat room. [B3] The above operation executes the URL launcher, The program according to [B1] or [B2], characterized in that the URL includes the patient information, the user information of the user who performed the operation, or processed patient information obtained by processing the patient information, and the user information or processed user information obtained by processing the user information. [B4] The above operation executes the URL launcher, The URL includes one or more of the following: the patient information and the user information that performed the operation or information processed from the user information, and also includes one or more of the following: the user information or information processed from the user information or information of the group to which the user belongs or information processed from information of the group to which the user belongs. The program according to [B1] or [B2], characterized in that one or more of the patient's chat room, chat thread, or chat channel of the patient's information is opened by the user who performed the operation, or is set for the user who performed the operation or for the group to which the user who performed the operation belongs. [B5] The program described in [B1] or [B2] is A program characterized by its ability to automatically mention the medical affairs department (in the processor's mention section) when content related to medical fees arises within a chat. [B6] The program described in [B1] or [B2] is A program characterized by its ability to automatically mention relevant clinical groups when clinically related content arises within a chat (in the processor's mention section). [B7] The program described in [B1] or [B2] is A program characterized by its ability to automatically mention relevant emergency response clinical groups when urgent clinical matters arise within a chat (in the processor's mention section). [B8] [B7] The program is characterized by having a function in the processor's SMS communication section to further mention a physician in charge of emergency response with an alert, and to automatically notify the physician of the emergency details via SMS. [B9] [B8] A program characterized by the function of anonymizing the patient information when an SMS notification is sent and notifying the recipient in the format of "An SMS has been sent regarding ward XX." [B10] [B8] is a program that enables the generation of SMS notifications sent to doctors outside the hospital, which contain only anonymized patient information and do not include the patient's personal information. [B11] [B8] A program characterized in that when a doctor who has received the SMS notification calls the designated phone number and enters the authentication ID notified via SMS, the AI ​​system (by the voice response unit) implements a function to read aloud anonymized patient information based on the ID. [B12] In the program described in [B1] or [B2], A program characterized by its ability to, when a user is mentioned in a chat, integrate with a knowledge support system and (through the knowledge support department) provide real-time information on relevant clinical guidelines and medical fee schedules based on the content of the mention. [B13] In the program described in [B1] or [B2], This program implements a feature that allows members of a group to view the chat content of each group once they log in. [B14] In the program described in [B1] or [B2], If approval is given within the chat or thread, The contents of the chat or thread related to the approval will be automatically deleted, or, A function to automatically delete the content after a certain period of time has elapsed. A program characterized by being implemented (by an erase unit). [B15] A program described in [B1] or [B2] that is characterized by implementing a function to register to the medical system's TODO. [B16] A program described in [B1] or [B2], characterized in that it grants the attending physician the privilege to view all chat content related to the patient. [B17] A program described in [B1] or [B2] that, when a chat room is created for the same patient, enables the user to see the same chat content.

[0104] [Note C] A method is a function implemented by a program and is an execution procedure performed on a computer server having a processor and memory. [C1] A chat method that is integrated with a medical system and runs on a computer server having a processor and memory, The aforementioned chat method allows for the creation of one or more chat rooms, chat threads, or chat channels for each patient, for each user or group of users. From the screen state containing personal information of the aforementioned medical system, one or more user operations such as electronic button operation, keyboard operation, or voice operation can open or set one or more chat rooms, chat threads, or chat channels. The patient's chat room, chat thread, or chat channel is opened by the user who performed the operation, or is set for the user who performed the operation or for one or more of the groups to which the user who performed the operation belongs. [C2] One or more of the aforementioned chat rooms, chat threads, or chat channels can be opened by a user or group user using a URL launcher. When opening, the processor has a patient information acquisition unit that acquires the patient information, The aforementioned patient information acquisition unit, • When associating each patient with a chat room, link it to the patient's information. The chat method described in [C1], characterized by associating the user who opened the chat room with the chat room. [C3] The above operation executes the URL launcher, The chat method according to [C1] or [C2], characterized in that the URL includes the patient information, the user information of the user who performed the operation, or processed patient information obtained by processing the patient information, and the user information or processed user information obtained by processing the user information. [C4] The above operation executes the URL launcher, The URL includes one or more of the following: the patient information and the user information that performed the operation or information processed from the user information, and also includes one or more of the following: the user information or information processed from the user information or information of the group to which the user belongs or information processed from information of the group to which the user belongs. The chat method according to [C1] or [C2], characterized in that one or more of the patient's chat room, chat thread, or chat channel of the patient's information is opened by the user who performed the operation, or is set for the user who performed the operation or the group to which the user who performed the operation belongs. [C5] The chat method described in [C1] or [C2] is: A chat method characterized by automatically mentioning the medical affairs department (in the processor's mention section) when content related to medical fees arises in the chat. [C6] The chat method described in [C1] or [C2] is: A chat method characterized by automatically mentioning relevant clinical groups to the appropriate clinical groups (in the processor's mention section) when clinically relevant content arises within the chat. [C7] The chat method described in [C1] or [C2] is: A chat method characterized by automatically mentioning the relevant emergency response clinical group (in the processor's mention section) when an urgent clinical matter arises within the chat. [C8] [C7] A chat method characterized by further mentioning a physician in charge of emergency response with an alert (to the SMS linkage section of the processor) and automatically notifying the physician of the emergency details via SMS. [C9] [C8] A chat method characterized in that, when an SMS notification is sent, the patient information is anonymized and the notification content is in the format of "An SMS has been sent regarding Ward XX". [C10] [C8] is a chat method characterized in that notifications sent via SMS to doctors outside the hospital contain only anonymized patient information and are generated in a format that does not include the patient's personal information. [C11] [C8] A chat method characterized in that when a doctor who receives the SMS notification calls the designated phone number and enters the authentication ID notified via SMS, the AI ​​system reads aloud anonymized patient information based on the ID. [C12] In the chat method described in [C1] or [C2], A chat method characterized by its ability to link with a knowledge support system when a user is mentioned in a chat, and to present relevant clinical guidelines and medical fee information in real time based on the content of the mention. [C13] In the chat method described in [C1] or [C2], This chat method allows members of a group to view the chat content of each group once they log in. [C14] In the chat method described in [C1] or [C2], If approval is given within the chat or thread, The contents of the chat or thread related to the approval will be automatically deleted, or, A chat method characterized by automatically deleting the content after a certain period of time has elapsed. [C15] A chat method described in [C1] or [C2], characterized by registering in the TODO of the medical system. [C16] A chat method described in [C1] or [C2], characterized in that the attending physician is granted the privilege of being able to view all chat content related to the patient. [C17] A chat method characterized by providing a function that allows users to see the same chat content when a chat room is created for the same patient, in the program described in [C1] or [C2]. [Explanation of symbols]

[0105] 1. In-hospital terminals 2. Chat system 3. Medical system 3B Knowledge support system 4 Mobile device

Claims

1. A chat system that integrates with the medical system. The aforementioned chat system allows for the creation of one or more chat rooms, chat threads, or chat channels for each patient, for each user or group of users. From the screen state containing personal information of the aforementioned medical system, one or more user operations such as electronic button operation, keyboard operation, or voice operation can open or set one or more chat rooms, chat threads, or chat channels. A chat system characterized in that one or more of the patient's chat room, chat thread, or chat channel is opened by the user who performed the operation, or is set for one or more of the user who performed the operation or to one or more of the groups to which the user who performed the operation belongs.

2. One or more of the aforementioned chat rooms, chat threads, or chat channels can be opened by a user or group user using the URL launcher. When opening, it has a patient information acquisition unit that acquires the patient information, The aforementioned patient information acquisition unit, - A function to link patient information when associating each patient with a chat room, The chat system according to claim 1, further comprising a function for linking a user who has opened a chat room to that chat room.

3. The above operation executes the URL launcher, The chat system according to claim 1 or 2, characterized in that the URL includes the patient information, the user information of the user who performed the operation, or processed patient information obtained by processing the patient information, and the user information or processed user information obtained by processing the user information.

4. The above operation executes the URL launcher, The URL contains one or more of the following: the patient information and the user information that performed the operation or information processed from the user information, and also contains one or more of the following: the user information or information processed from the user information or information of the group to which the user belongs or information processed from information of the group to which the user belongs. The chat system according to claim 1 or 2, characterized in that one or more of the patient's chat room, chat thread, or chat channel of the patient's information is opened by the user who performed the operation, or is set for the user who performed the operation or the group to which the user who performed the operation belongs.

5. The chat system according to claim 1 or 2 is A chat system characterized by having a mention function that automatically mentions the medical affairs department when content related to medical fees arises within the chat.

6. The chat system according to claim 1 or 2 is A chat system characterized by having a mention function that automatically mentions relevant clinical groups when clinical-related content arises within the chat.

7. The chat system according to claim 1 or 2 is A chat system characterized by having a mention function that automatically mentions the relevant emergency response clinical group when an urgent clinical matter arises within the chat.

8. The chat system according to claim 7, further comprising an SMS linkage unit that has a function to mention a physician in charge of emergency response with an alert, and that automatically notifies the physician of the emergency details via SMS.

9. In claim 8, A chat system characterized by having a function that, when an SMS notification is sent, anonymizes the patient information and notifies the user in the format of "An SMS has been sent regarding ward XX."

10. In claim 8, A chat system characterized by its ability to generate SMS notifications to doctors outside the hospital that include only anonymized patient information and do not contain the patient's personal information.

11. In claim 8, A chat system characterized by having a voice response unit in which, upon receiving an SMS notification, a doctor calls a designated phone number and enters the authentication ID notified via SMS, and the AI ​​system reads aloud anonymized patient information based on the ID.

12. In the chat system according to claim 1 or 2, A chat system characterized by having a knowledge support unit that, when a user is mentioned in a chat, links with a knowledge support system and presents relevant clinical guidelines and medical fee information in real time based on the content of the mention.

13. In the chat system according to claim 1 or 2, This chat system allows members of a group to view the chat content of their respective groups once they log in.

14. Automatic deletion In the chat system according to claim 1 or 2, If approval is given within the chat or thread, The contents of the chat or thread related to the approval will be automatically deleted, or, The content will be automatically deleted after a certain period of time has elapsed. A chat system characterized by having an erasure unit.

15. A chat system according to claim 1 or 2, characterized in that it registers to the TODO list of the medical system.

16. A chat system according to claim 1 or 2, characterized in that it includes a viewing privilege granting unit that grants the attending physician the privilege to view all chat content related to the patient.

17. A chat system according to claim 1 or 2, characterized in that when a chat room is created for the same patient, the same chat content is visible to the user.

Images