Gateway device and medical communication system
The gateway device enables secure, cost-effective communication between medical information and service systems by using WebSocket and HTTPS protocols, addressing the challenges of secure connection establishment and reducing operational costs.
Patent Information
- Application Number
- JP2022027851
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-02-25
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2042-02-25
AI Technical Summary
Establishing a secure, cost-effective, and user-friendly communication connection between medical information management systems and external medical service providing systems is challenging due to the sensitivity of medical information and the high costs associated with maintaining IP addresses and unique domains.
A gateway device that relays communication between on-premises medical information management systems and cloud-based medical service providing systems, utilizing WebSocket communication for constant connections and HTTPS for secure, one-way communication, with an authentication and determination unit to manage connections based on pre-stored permission information.
Facilitates secure, cost-effective, and efficient communication between medical information management and service providing systems, reducing operational burdens and ensuring quick updates without the need for managing IP addresses or unique domains.
Smart Images

Figure 0007595040000001 
Figure 0007595040000002 
Figure 0007595040000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a gateway device and a medical communication system that handle medical information. [Background technology]
[0002] Medical institutions manage various types of medical information, such as patients' personal information, medical history, and treatment history, as electronic medical records. Because medical information is sensitive information that requires careful handling, medical information management systems that handle medical information within medical institutions are sometimes designed as on-premise systems that are independent of the cloud.
[0003] In recent years, medical service provision systems that provide various services to patients who use medical institutions or medical staff who belong to medical institutions by using web servers built on the cloud have become widespread.Specific examples include a reservation system that accepts reservations for medical institutions from outside the medical institution, a reception system that accepts patients who visit the medical institution, a medical interview system that interviews patients in advance, a payment system that settles medical fees, and a test reservation system that makes reservations for tests at external testing institutions.
[0004] In order to provide better services in a medical service provision system, there is a demand for linking a medical information management system with a medical service provision system. Linking the medical information management system with the medical service provision system allows the medical information, such as a patient's personal information and medical history, managed by the medical information management system to be used by the medical service provision system. Patent Document 1 discloses a medical information system including a cloud integration platform that securely connects a medical information system that handles information such as electronic medical records and a terminal owned by a patient. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Patent Publication No. 2021-103348 Summary of the Invention [Problem to be solved by the invention]
[0006] However, there are many problems in terms of cost and ease of use in order to securely establish a communication connection between a medical information management system that handles electronic medical record information, which is sensitive information, and an external medical service provision system.
[0007] An object of the present disclosure is to provide a gateway device and a medical communication system that can establish a communication connection between a medical information management system and an external medical service providing system securely, inexpensively, and easily. [Means for solving the problem]
[0008] The gateway device of the present disclosure comprises: A medical information management system implemented by a computer in an on-premise environment. A gateway device that relays communication between a medical information management system that manages medical information and a medical service providing system that uses the medical information to provide various services, the gateway device being realized by a computer in a cloud environment and including an authentication unit that authenticates the medical information management system and the medical service providing system, a constant connection unit that can establish a constant connection using a first communication protocol that maintains a constant connection once communication is established with the authenticated medical information management system and enables two-way communication, and a transmission / reception unit that establishes a communication connection with the authenticated medical service providing system using a second communication protocol in which communication is disconnected when transmission and reception of information is completed, and transmits and receives the medical information. a storage unit that stores connection permission information indicating whether or not a connection between any one of the plurality of medical information management systems and any one of the plurality of medical service providing systems is permitted; and a medical information management system to which the constant connection is established, based on the connection permission information, and a determination unit that determines whether or not to permit the communication connection with the authenticated medical service providing system.
[0009] The medical communication system of the present disclosure includes a medical information management system that manages medical information, and a gateway device that relays communication between the medical information management system and a medical service providing system that provides various services using the medical information, the gateway device being realized by a computer in a cloud environment, The system stores in advance connection permission information indicating whether or not to permit a connection between any one of the plurality of medical information management systems and any one of the plurality of medical service providing systems, and is realized by a computer in an on-premise environment. a first communication protocol is used to establish a constant connection with the medical information management system, which maintains a constant connection after communication is established once and enables two-way communication, and a second communication protocol is used to disconnect communication with the medical service providing system when transmission and reception of information is completed, and whether or not to permit a communication connection; The medical information management system to which the constant connection is established, and If it is determined that the communication is permitted, the communication connection is established. Effect of the Invention
[0010] According to the present invention, communication between a medical information management system and an external medical service providing system can be established securely, inexpensively, and easily. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 is a conceptual diagram showing an example of an overall configuration of a medical communication system according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a diagram showing an example of a hardware configuration of a computer. [Diagram 3] FIG. 1 is a diagram for explaining an example of a software configuration of a gateway device. [Figure 4] FIG. 1 is a diagram for explaining an example of a software configuration of a medical information management system. [Diagram 5] FIG. 1 is a diagram for explaining an example of a software configuration of a medical service providing system. [Figure 6] A sequence diagram showing an example of the operation of the medical communication system when notifying a medical service providing system of a change in medical information. [Figure 7] A sequence diagram showing an example of the operation of the medical communication system when transmitting changed medical information to the medical service providing system. [Figure 8] A sequence diagram showing an example of the operation of the medical communication system when selecting the type of medical information to be transmitted to the medical service providing system. [Figure 9] FIG. 13 is a diagram showing an example of type information [Figure 10] A sequence diagram showing an example of the operation when a change in medical information occurs in a medical service provision system. [Figure 11] A sequence diagram to explain a usage example in which a patient uses the reservation and reception service to make a reservation at a medical institution, and the medical institution uses the reservation and reception service to accept the patient's return visit. [Figure 12] A sequence diagram to explain a usage example in which a patient visiting a medical institution for the first time uses the reservation and reception service to make a reservation at the medical institution, and the medical institution uses the reservation and reception service to accept the patient's first visit. [Figure 13] A sequence diagram to explain a usage example in which a medical institution uses the reservation and reception service to accept a patient's return visit, and also uses the medical interview service to interview the patient, and uses the examination reservation service to schedule an examination for the patient. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. However, more detailed explanation than necessary, for example, detailed explanation of already well-known matters and duplicate explanation of substantially the same configuration, may be omitted.
[0013] [Configuration of medical communication system 100] Fig. 1 is a conceptual diagram showing an example of the overall configuration of a medical communication system 100 according to an embodiment of the present disclosure. As shown in Fig. 1, the medical communication system 100 includes a gateway device 1, a medical information management system 2, and a medical service provision system 3. Note that the number of medical information management systems and the number of medical service provision systems included in the medical communication system 100 are not limited, and may be one or more.
[0014] The gateway device 1 is a device that controls communication of various information between the medical information management system 2 and the medical service providing system 3. The gateway device 1 is realized, for example, by a computer in a cloud environment. The functions of the gateway device 1 may also be realized by the hardware configuration of the medical information management system 2. The configuration and operation of the gateway device 1 will be described in detail later.
[0015] The medical information management system 2 is a system for managing medical information, which is operated and used in, for example, medical institutions (hospitals, clinics, nursing homes for the elderly, pharmacies, and other facilities providing medical care).
[0016] Examples of medical information include patient information, reception information, medical department information, and user information. Patient information includes, for example, information that can identify an individual, such as the patient's name, age, date of birth, sex, and address, and insurance information, such as insurance type and insurer number. Reception information is information used when a medical institution accepts a patient, and includes various information such as a patient code, such as a patient card number, that is determined for each medical institution, the number of people currently waiting or their order, the reception number when the patient is accepted, the appointment time, the reception time, the visit category, such as first visit or follow-up visit, the reason for the visit, past visit dates and visit history, and past medical history. Medical department information is information indicating the medical department that the patient visits or has been treated by. User information is information about a user who uses medical information, and includes, for example, information that identifies the doctor who examines the patient or the laboratory technician who performs the test.
[0017] The medical information management system 2 is realized by a computer in an on-premise environment because it manages sensitive information such as information that can identify individuals. The computer in the on-premise environment that realizes the medical information management system 2 is installed, for example, in a medical institution that uses the system. The medical information management system 2 is configured to always communicate with an external network via a gateway device 1.
[0018] The medical service providing system 3 is, for example, a device included in a medical service system that provides various services to patients or medical professionals. Note that the person using the medical service providing system 3 is not limited to a patient or a medical professional, and may be another person who wishes to use medical information, such as an employee of a pharmaceutical manufacturer. The medical service providing system 3 is, for example, a system in which various service providers outside medical institutions provide useful medical services to medical institutions and patients. The medical service providing system 3 may be configured to be realized by a computer in a cloud environment, or may be configured to be realized by a computer in an on-premise environment.
[0019] Examples of medical services provided by a medical service provision system include reservation services, reception services, medical interview services, payment services, test request services, and clinical trial management services. The reservation service is a service that enables patients to make reservations at medical institutions from outside the medical institution. The reception service is a service that receives patients at the medical institution when they visit the medical institution. The medical interview service is a service that interviews patients in advance when they are about to visit the medical institution. The payment service is a service that settles medical fees after treatment. The test request service is a service that requests tests to external testing institutions when tests are required at such institutions. The clinical trial management service is a service that manages when clinical trials are conducted on patients.
[0020] The medical service providing system 3 is communicably connected to the medical information management system 2 via the gateway device 1.
[0021] <Computer hardware configuration> Next, a description will be given of the hardware configuration of the computer 1000 that constitutes the gateway device 1, the medical information management system 2, and the medical service providing system 3. FIG.
[0022] The computer 1000 includes an input device 1001 such as a keyboard, mouse, or touchpad, an output device 1002 such as a display or speakers, a CPU (Central Processing Unit) 1003, a ROM (Read Only Memory) 1004, a RAM (Random Access Memory) 1005, a storage device 1006 such as a hard disk device or an SSD (Solid State Drive), a reading device 1007 that reads information from a recording medium such as a DVD-ROM (Digital Versatile Disk Read Only Memory) or a USB (Universal Serial Bus) memory, and a transmission / reception device 1008 that communicates via a network, and each part is connected by a bus 1009.
[0023] The reading device 1007 reads a program for implementing the functions of each of the above-mentioned devices from a recording medium on which the program is recorded, and stores the program in the storage device 1006. Alternatively, the transmitting / receiving device 1008 communicates with a system device connected to the network, and stores the program for implementing the functions of each of the above-mentioned devices, downloaded from the system device, in the storage device 1006.
[0024] Then, the CPU 1003 copies the program stored in the storage device 1006 to the RAM 1005, and sequentially reads and executes the instructions contained in the program from the RAM 1005, thereby realizing the functions of the gateway device 1, the medical information management system 2, and the medical service provision system 3.
[0025] <Software configuration of gateway device 1> 3 is a diagram for explaining an example of a software configuration of the gateway device 1. As shown in FIG. 3, the gateway device 1 includes a constant connection unit 11, a determination unit 12, a transmission / reception unit 13, an authentication unit 14, and a storage unit 15.
[0026] The constant-connection unit 11 is a communication unit capable of constant connection with the medical information management system 2. In the present disclosure, as shown in FIG. 1, WebSocket communication is adopted as a communication protocol between the constant-connection unit 11 and the medical information management system 2. WebSocket communication is a communication protocol that maintains a constant connection once communication is established, and enables two-way communication. As a result, once a constant connection is established, transmission and reception of medical information becomes possible between the gateway device 1 and the medical information management system 2.
[0027] The determination unit 12 determines whether or not to permit a communication connection with the medical service providing system 3. The determination unit 12 makes a determination based on the connection permission information stored in the memory unit 15. The connection permission information stores connection permission information indicating whether or not to permit a connection between any one of the multiple medical information management systems 2 and any one of the multiple medical service providing systems 3. In other words, the connection permission information is information that is determined for each medical information management system 2 and indicates the medical service providing system 3 to which connection is permitted. This allows the gateway device 1 to manage, for each medical information management system 2, the medical service providing system 3 to which connection is permitted.
[0028] When the determination unit 12 determines that the connection is permitted, the transmission / reception unit 13 establishes a communication connection with the medical service providing system 3 and transmits and receives medical information. In the present disclosure, HTTPS communication is adopted as the communication protocol between the transmission / reception unit 13 and the medical service providing system 3. This allows the communication connection between the gateway device 1 and the medical service providing system 3 to be established only when necessary, and makes the communication connection secure.
[0029] The authentication unit 14 authenticates the medical information management system 2 that is constantly connected to the constant connection unit 11. The authentication unit 14 also authenticates the medical service providing system 3 that is constantly connected to the transmission / reception unit 13 as necessary.
[0030] The storage unit 15 stores various types of information necessary for the operation of the gateway device 1. Examples of information stored in the storage unit 15 include connection permission information and type information. The type information, which will be described in detail later, is information that indicates the type of medical information required by the medical service providing system 3, which is predetermined for each medical service providing system 3.
[0031] <Medical Information Management System 2 software configuration> 4 is a diagram for explaining the software configuration of the medical information management system 2. The medical information management system 2 includes a transmission / reception unit 21, an change detection unit 22, an extraction unit 23, a medical information database (DB) 24, a display unit 25, and an operation unit 26.
[0032] The transmitting / receiving unit 21 establishes a constant connection (WebSocket communication) with the constant connection unit 11 of the gateway device 1, and after the establishment, transmits and receives medical information.
[0033] The change detection unit 22 detects a change when there is a change in the medical information included in the medical information DB 24. A change in the medical information occurs, for example, when a staff member of the medical institution performs an operation to change the medical information via the operation unit 26. As a specific example, a change in the medical information occurs when a staff member of the medical institution hears from a patient visiting the medical institution that the patient's last name has changed and operates the operation unit 26 to change the patient information included in the medical information DB 24 of the medical information management system 2.
[0034] Alternatively, a change in medical information occurs when changed medical information is transmitted from the medical service providing system 3 and received by the transmitting / receiving unit 21 via the gateway device 1. The change detection unit 22 executes a process to detect the change, for example, at predetermined intervals or when an operation to change the medical information is performed on the operation unit 26, and detects the change.
[0035] The extraction unit 23 extracts medical information of a type necessary for the medical service providing system 3 from among multiple types of medical information managed in the medical information DB 24. This makes it possible to detect medical information related to a specific patient or a specific type of medical information related to multiple patients, for example, in response to a request from the medical service providing system 3 via the gateway device 1. The extraction unit 23 may extract the type of medical information necessary for the medical service providing system 3, for example, when changed medical information is transmitted from the medical service providing system 3 via the gateway device 1.
[0036] The medical information DB 24 is a database that manages medical information.
[0037] The display unit 25 displays various information to staff of the medical institution that operates the medical information management system 2. The display unit 25 displays information on, for example, a liquid crystal display or an organic EL display of a terminal for the medical information management system 2 installed in the medical institution.
[0038] The operation unit 26 is installed, for example, in a medical institution where the medical information management system 2 is operated, and accepts operations from staff of the medical institution, etc. The operation unit 26 accepts input operations to a keyboard, mouse, touch panel, etc. of a terminal for the medical information management system 2 installed in the medical institution, for example.
[0039] <Software configuration of medical service provision system 3> Fig. 5 is a diagram for explaining the software configuration of the medical service provision system 3. Note that the medical service provision system 3 is operated by various companies and organizations and provides various services, so the software configuration described below is merely one example.
[0040] The medical service providing system 3 includes a transmission / reception unit 31, a service providing unit 32, a medical service database (DB) 33, a display unit , and an operation unit .
[0041] The transmitting / receiving unit 31 establishes a communication (HTTPS communication) connection with the transmitting / receiving unit 13 of the gateway device 1 as necessary, and transmits and receives medical information.
[0042] The service providing unit 32 executes the programs stored in the medical service DB 33 to provide various medical services to medical institutions or patients using various types of medical information.
[0043] The display unit 34 is installed in a medical institution that operates the medical information management system 2, and displays various information to staff of the medical institution, etc. The display unit 34 performs display on, for example, a liquid crystal display, an organic EL display, or the like provided in a terminal for the medical service providing system 3 installed in the medical institution.
[0044] The operation unit 35 is installed, for example, in a medical institution where the medical information management system 2 is operated, and accepts operations by staff of the medical institution, etc. The operation unit 35 accepts input operations to a keyboard, mouse, touch panel, etc. of a terminal for the medical service providing system 3 installed in the medical institution, for example.
[0045] <Effects of the configuration of the medical communication system 100> The configuration of the medical communication system 100 has been described above. In the medical communication system 100 according to the embodiment of the present disclosure, always-on communication is established between the gateway device 1 and the medical information management system 2 by WebSocket communication. Meanwhile, HTTPS communication is established between the gateway device 1 and the medical service providing system 3 as necessary. With this configuration, once communication is established between the gateway device 1 and the medical information management system 2, bidirectional information exchange can be performed in real time.
[0046] If one attempts to establish a real-time, two-way, and secure communication connection between an on-premise medical information management system 2 and multiple medical service provision systems 3 without using a gateway device 1, the following problems may arise.
[0047] As a method for establishing a real-time, two-way, and secure communication connection between an on-premise medical information management system 2 and an external medical service providing system 3 without using a gateway device 1, a method of connecting the medical information management system 2 and the medical service providing system 3 using HTTPS communication as necessary can be considered. In this case, in order to connect from the medical service providing system 3 to the medical information management system 2, it is necessary for the medical information management system 2 to acquire a fixed IP address or an original domain. Obtaining a fixed IP address or an original domain and maintaining security incurs significant costs for the medical institution that operates the medical information management system 2.
[0048] Even if a fixed IP address and an original domain can be obtained, in order for the medical institution operating the medical information management system 2 to efficiently cooperate with the medical service providing system 3, the medical institution needs to install and operate a dedicated client terminal for each medical service providing system 3. In addition, the medical institution may need to employ staff with specialized knowledge about networks. In this case, the medical institution will incur a large burden of equipment costs and maintenance costs. In addition, the operational burden on the staff of the medical institution will also increase. To give a specific example, when there is a change in patient information (such as a change in name, address, or insurance type), the staff of the medical institution needs to not only change the patient information in the medical information management system 2, but also reflect the changed patient information in each of the multiple medical service providing systems 3.
[0049] In addition, the medical service providing system 3 must constantly manage the IP addresses and domain information of each medical institution, which requires equipment and operating costs.
[0050] In the medical communication system 100 relating to an embodiment of the present disclosure, the above-mentioned configuration eliminates the need to manage IP addresses and domain information, and therefore, by having the gateway device 1 relay communication between the on-premise medical information management system 2 and the medical service provision system 3, collaboration between the medical information management system 2 and the medical service provision system 3 can be achieved at low cost.
[0051] In addition, in the medical communication system 100 according to the embodiment of the present disclosure, the gateway device 1 does not hold sensitive medical information, so high security can be ensured. Even if the medical information is changed on the medical information management system 2 side, the change can be quickly reflected on the medical service providing system 3 side without increasing the operational burden. Various operations of the medical communication system 100 according to the embodiment of the present disclosure will be described below with specific examples.
[0052] [Example] The following describes an operation example of the medical communication system 100. The following operation example is based on the premise that, after the gateway device 1 authenticates the medical information management system 2, a constant connection is established between the gateway device 1 and the medical information management system 2 via WebSocket communication. The following operation example is also based on the premise that, for communication between the gateway device 1 and the medical service providing system 3, HTTPS communication is established after authentication of the medical service providing system 3 as necessary, and the established HTTPS communication is disconnected when transmission and reception of necessary information is completed.
[0053] <First operation example: Notification of changes to medical information> As a first operation example, an operation example will be described in which a notification is sent to the medical service providing system 3 when there is a change in medical information managed by the medical information management system 2. FIG. 6 is a sequence diagram showing an operation example of the medical communication system 100 when a notification of a change in medical information is sent to the medical service providing system 3. Note that in the sequence diagram shown in FIG. 6, one medical information management system 2 and one medical service providing system 3 are shown to avoid complexity, but in reality, there may be multiple medical information management systems 2 and multiple medical service providing systems 3. The following sequence diagrams appearing in this specification are all based on the same premise.
[0054] In step S1, the change detection unit 22 (see FIG. 4) of the medical information management system 2 detects a change to the medical information. As described above, the medical information is changed when the staff of the medical institution operates the operation unit 26 of the medical information management system 2, or when the changed medical information from the medical service providing system 3 is received by the medical information management system 2 via the gateway device 1. The detection of the change in step S1 is performed by the change detection unit 22 (see FIG. 4), for example, at predetermined intervals or when a change operation is performed on the operation unit 26.
[0055] In step S2, the medical information management system 2 notifies the gateway device 1 that there has been a change in the medical information.
[0056] In step S3, the gateway device 1 that has received the change notification judges whether or not to permit transmission of the change notification for each medical service providing system 3. As described above, this judgment is made based on the connection permission information that the gateway device 1 has stored in advance.
[0057] In step S4, the gateway device 1 transmits a change notification to the medical service providing systems 3 that have been determined to permit the transmission. Note that, among the multiple medical service providing systems 3, the change notification is not transmitted in step S4 to those that are not permitted to connect in step S3. As a result, the medical service providing systems 3 are automatically notified that there has been a change in the medical information, eliminating the need for staff of the medical institution operating the medical information management system 2 to manually transmit the change notification.
[0058] In the above first operation example, the change notification simply notifies the user that a change has been made to the medical information, but it may also be possible to notify the user of what type of medical information has been changed, for example based on the type information described below (see the third operation example).
[0059] <Second operation example: Transmission of medical information> The second operation example is an operation example in which, when there is a change in the medical information, the medical information is transmitted to the medical service providing system 3. In the first operation example, when there is a change in the medical information, a change notification is transmitted to the medical service providing system 3, but in the second operation example, the changed medical information is transmitted. For example, when the patient information of a specific patient is changed, the patient information of the patient is transmitted to the medical service providing system 3.
[0060] FIG. 7 is a sequence diagram showing an example of the operation of the medical communication system 100 when transmitting changed medical information to the medical service providing system 3. As shown in FIG.
[0061] In step S11, the medical information management system 2 detects changes to the medical information.
[0062] In step S12, the medical information management system 2 transmits the changed medical information to the gateway device 1.
[0063] In step S13, the gateway device 1 that has received the changed medical information judges, for each medical service providing system 3, whether or not to permit transmission of the changed medical information.
[0064] In step S14, the gateway device 1 transmits the changed medical information to the medical service providing systems 3 that have been determined to permit the transmission. Note that, among the multiple medical service providing systems 3, a change notification is not transmitted in step S14 to those that have not been permitted to connect in step S13. As a result, the changed medical information is automatically transmitted to the medical service providing systems 3 and reflected therein, eliminating the need for staff of the medical institution operating the medical information management system 2 to manually transmit the updated information to the medical service providing systems 3.
[0065] <Third operation example: Select medical information to send> The third operation example is an operation example in which, when transmitting medical information from the gateway device 1 to the medical service providing system 3, the gateway device 1 selects and transmits only a preset type of information from among multiple types of medical information.
[0066] FIG. 8 is a sequence diagram showing an example of the operation of the medical communication system 100 when the type of medical information to be transmitted to the medical service providing system 3 is selected.
[0067] In step S21, the medical information management system 2 detects changes to the medical information.
[0068] In step S22, the medical information management system 2 transmits the changed medical information to the gateway device 1.
[0069] In step S23, the gateway device 1 that has received the changed medical information judges, for each medical service providing system 3, whether or not to permit transmission of the changed medical information.
[0070] In step S24, the gateway device 1 selects the type of medical information to be transmitted for each medical service providing system 3 for which it has determined that transmission is permitted, based on the type information.
[0071] In step S25, the gateway device 1 transmits the selected type of medical information to the medical service providing system 3.
[0072] Fig. 9 is a diagram showing an example of type information used in step S24. As shown in Fig. 9, the type information is information that specifies the type of medical information to be transmitted for each source medical information management system 2 and each destination medical service providing system 3.
[0073] Depending on the type of medical service provided by the medical service providing system 3, there may be types of medical information that are not required. In this way, when there is a type of medical information that is not required for the medical service providing system 3, it is better not to transmit the medical information, which is sensitive information, unnecessarily. According to the third operation example, unnecessary types of medical information are not transmitted for each medical service providing system 3, so that security can be maintained better.
[0074] <Fourth Operation Example: Medical Information Management System 2 Extracts Information Necessary for Medical Service Providing System 3> In the fourth operation example, a description will be given of an operation example in which a change in medical information occurs in the medical service providing system 3. Fig. 10 is a sequence diagram showing an operation example in which a change in medical information occurs in the medical service providing system 3.
[0075] In step S31, the medical information is changed in the medical service providing system 3. Specifically, the operation of step S31 is an operation performed when a staff member of a medical institution performs an operation to change the medical information on the operation unit 35 (see FIG. 5) of the medical service providing system 3 installed in the medical institution, for example.
[0076] In step S32, the medical service providing system 3 transmits the changed medical information to the gateway device 1.
[0077] In step S33, the gateway device 1 transmits the changed medical information received from the medical service providing system 3 to the medical information management system 2.
[0078] In step S34, the medical information management system 2 changes the medical information based on the received information.
[0079] In step S35, the medical information management system 2 extracts medical information required by the medical service providing system 3 that has transmitted the changed medical information. The operation of step S35 is performed by the extraction unit 23 (see FIG. 4) of the medical information management system 2 extracting the type of medical information preset for each medical service providing system 3.
[0080] In step S36, the medical information management system 2 transmits the extracted medical information to the gateway device 1.
[0081] In step S37, the gateway device 1 judges whether or not to permit the transmission of the medical information received from the medical information management system 2 to the medical service providing system 3 that has transmitted the changed medical information. Note that the gateway device 1 always permits the transmission of the medical information to the medical service providing system 3 that has transmitted the changed medical information.
[0082] In step S38, the gateway device 1 transmits the received medical information to the medical service providing system 3.
[0083] In this way, in the fourth operation example, the type of medical information required by the medical service providing system 3 is automatically selected by the medical information management system 2 and transmitted to the medical service providing system 3 via the gateway device 1. This eliminates the need for the medical service providing system 3 to request the information it requires from the medical information management system 2 again, thereby reducing time and labor.
[0084] [Usage example] In the following, a more specific use example of the medical communication system 100 according to the embodiment of the present disclosure will be described by combining the above-mentioned operation examples.
[0085] <First use case: Patient return reception process using reservation and reception service> 11 is a sequence diagram for explaining a usage example in which, when the medical service providing system 3 is a reservation and reception service, a patient uses the service to make a reservation at a medical institution, and the medical institution uses the reservation and reception service to accept the patient's return visit. Note that the reception and reservation service is a service that allows a patient to make a reservation at a medical institution, reflects information related to the accepted reservation in the medical information management system 2 of the medical institution where the patient made the reservation, and, when the patient actually visits the medical institution, receives the patient at the medical institution, arranges the patient's turn for an examination, notifies the patient of the number of people waiting, etc.
[0086] In the following usage example, it is assumed that staff at a medical institution who handle patient reception, etc., are able to operate both the operation unit 26 of the medical information management system 2 and the operation unit 35 of the medical service provision system 3 at hand.
[0087] Suppose a returning patient who has already made a medical appointment with the medical institution using the reservation and reception service comes to see a staff member at the reception desk of the medical institution. In step S101, the medical institution staff member who treats the patient operates a terminal for the medical service providing system 3 and requests the medical service providing system 3 to execute a reception start process.
[0088] In step S102, the medical service providing system 3 requests medical information required for reception processing of the patient from the gateway device 1. Examples of the medical information required for reception processing include various information such as the patient's name, patient ID, appointment time, past reception information, and the details of the next medical treatment.
[0089] In step S103, the gateway device 1 determines whether or not the information request from the medical service providing system 3 may be transmitted to the medical information management system 2. This determination may be made based on the connection permission information stored in the gateway device 1.
[0090] In step S104, the gateway device 1 determines information necessary for the medical service providing system 3. This determination may be made based on type information stored in the gateway device 1. Note that this step S104 is not necessary if the medical service providing system 3 has specified which information is necessary in step S102.
[0091] In step S105, the gateway device 1 requests the medical information management system 2 for necessary information.
[0092] In step S106, the medical information management system 2 extracts the requested information.
[0093] In step S107, the medical information management system 2 transmits the extracted information to the gateway device 1.
[0094] In step S 108 , the gateway device 1 transmits the information received from the medical information management system 2 to the medical service providing system 3 .
[0095] In step S109, the medical service providing system 3 displays necessary medical information on the staff member's terminal (display unit 34 in FIG. 5).
[0096] In step S110, the staff member inputs new medical information associated with the reception of the patient, using the operation unit 35 of the medical service providing system 3. Examples of the medical information newly input in step S110 include information such as reception time, reason for visit, and the department desired by the patient.
[0097] In step S111, the medical service providing system 3 transmits the newly input medical information to the gateway device 1.
[0098] In step S112, the gateway device 1 transmits the new medical information to the medical information management system 2.
[0099] In step S113, the medical information management system 2 reflects the received new medical information in the medical information DB 24 (see FIG. 4).
[0100] When the changed medical information is reflected from the medical service providing system 3, in step S114, the medical information management system 2 extracts medical information necessary for the medical service providing system 3. In this use example, the medical information necessary for the medical service providing system 3 is information such as the patient's name and appointment time described in step S102, as well as the past consultation date and time, the name of the medical department and doctor visited in the past, and the type of insurance.
[0101] In step S115, the medical information management system 2 transmits the extracted medical information to the gateway device 1.
[0102] In step S116, the gateway device 1 judges whether or not to permit transmission of the medical information received from the medical information management system 2 to the medical service providing system 3.
[0103] In step S117, the gateway device 1 transmits the medical information received from the medical information management system 2 to the medical service providing system 3.
[0104] In step S118, the medical service providing system 3 that has received the medical information necessary for the reception process displays the received medical information, allowing the staff of the medical institution to complete the reception process for the patient.
[0105] In addition, before the patient reception process is completed, the medical information, such as the patient information and reception information, may change. In this case, in step S119, the staff member uses the operation unit 26 of the medical information management system 2 to input the changes in the medical information.
[0106] In step S120, the medical information management system 2 reflects the input changes in the medical information in the medical information DB 24. Then, in step S121, the change detection unit 22 of the medical information management system 2 detects the changes in the medical information.
[0107] In step S122, the medical information management system 2 transmits the changed medical information to the gateway device 1.
[0108] In step S123, the gateway device 1 judges whether or not to permit transmission of the changed medical information to the medical service providing system 3.
[0109] In step S124, the gateway device 1 transmits the changed medical information to the medical service providing system 3.
[0110] In the first use example described in Fig. 11, the medical service providing system 3 requests the necessary information from the medical information management system 2 at the time of receiving a reception request. For example, at the time of reception, the medical service providing system 3 may not request all the information necessary for reception from the medical information management system 2, but may transmit only the information that the medical service providing system 3 has at that time to the terminal of the medical institution staff. In this case, the processes from step S102 to step S108 in Fig. 11 are not necessary.
[0111] However, in the first use example, various pieces of information about the patient that the medical service providing system 3 does not have are requested from the medical information management system 2 at the time of reception, and the following effects can be obtained. That is, if the medical service providing system 3 holds all information about the reception of the patient, the processes from step S102 to step S108 in Fig. 11 are unnecessary, but the amount of information that the medical service providing system 3 needs to hold increases, and the medical service providing system 3 ends up holding sensitive information, which may cause security issues.
[0112] However, as in the first use example, by having sensitive information managed centrally by the medical information management system 2 and not having it stored in the medical service provision system 3, the security of the entire system can be improved and the construction costs of the entire system can be reduced.
[0113] Thus, according to the first use example of the medical communication system 100, when a patient who has made a reservation through the reservation and reception service of the medical service providing system 3 visits a medical institution, the medical institution's staff inputs the minimum necessary information into the medical service providing system 3, and various medical information required for reception processing of the patient is automatically transmitted from the medical information management system 2 to the medical service providing system 3 via the gateway device 1. Therefore, the medical institution's staff does not need to operate a terminal of the medical information management system 2, for example, to obtain the medical information required for reception processing by themselves. This has the effect of significantly reducing the operational effort of the staff.
[0114] In addition, communication between the medical service providing system 3 and the gateway device 1 is performed using HTTPS communication as necessary, and communication between the gateway device 1 and the authenticated medical information management system 2 is always performed using WebSocket communication, thereby providing the effect of ensuring sufficient security between each component of the medical communication system 100 for sensitive medical information.
[0115] <Second use case: Reception processing for a patient's first visit using a reservation and reception service> Figure 12 is a sequence diagram to explain a usage example in which, when the medical service providing system 3 is a reservation and reception service, a patient visiting a certain medical institution for the first time uses the service to make a reservation at the medical institution, and the medical institution uses the reservation and reception service to receive the patient's first visit.
[0116] Suppose a patient arrives at a medical institution for the first time, but has already made a medical appointment with the medical institution using the reservation and reception service. In step S201, the medical institution staff member who is attending to the patient operates a terminal for the medical service providing system 3 and requests the medical service providing system 3 to execute a reception start process.
[0117] In step S202, the medical service providing system 3 displays medical information required for reception processing of the patient on the staff terminal (display unit 34 in FIG. 5). As in the first use example, examples of the medical information required for reception processing include the patient's name and appointment time.
[0118] At present, the reception process at the medical institution cannot be displayed on the display unit 34 of the medical service providing system 3, which is the same as the first use example.
[0119] In step S203, the staff member inputs new medical information including patient information on the first visit patient, using the operation unit 26 of the medical information management system 2. The input new medical information is registered in the medical information DB 24 of the medical information management system 2.
[0120] Meanwhile, in step S204, the staff member inputs new medical information associated with the reception process using the operation unit 35 of the medical service providing system 3. Examples of the medical information newly input in step S204 include reception time, reason for visit, and the department of medical care desired by the patient.
[0121] In step S205, the medical service providing system 3 transmits the newly input medical information to the gateway device 1.
[0122] In step S206, the gateway device 1 transmits the new medical information to the medical information management system 2.
[0123] In step S207, the medical information management system 2 updates the medical information DB 24 with the received new medical information.
[0124] With this as a trigger, in step S208, the medical information management system 2 extracts medical information necessary for the medical service providing system 3. The medical information necessary for the medical service providing system 3 here is information such as the patient's name and appointment time described in step S202, as well as past consultation dates and times, the names of departments and doctors visited in the past, and the type of insurance.
[0125] In step S209, the medical information management system 2 transmits the extracted medical information to the gateway device 1.
[0126] In step S210, the gateway device 1 determines whether or not to permit transmission of the medical information received from the medical information management system 2 to the medical service providing system 3.
[0127] In step S211, the gateway device 1 transmits the medical information received from the medical information management system 2 to the medical service providing system 3.
[0128] In step S212, the medical service providing system 3 that has received the medical information necessary for the reception process displays the received medical information, allowing the staff of the medical institution to complete the reception process for the patient.
[0129] Thus, according to the second use example of the medical communication system 100, even if the patient is visiting for the first time, it is possible to obtain the same effect as in the first use example.
[0130] <Third use case: Linking multiple medical service delivery systems3> In the third use example, a use example in which multiple medical service providing systems 3A, 3B, and 3C are linked together will be described. The medical service providing system 3A is a reception and reservation service. The medical service providing system 3B is a medical interview service that interviews patients before they visit the hospital. The medical service providing system 3C is a test reservation service that accepts reservations for tests such as X-rays and blood sampling.
[0131] Figure 13 is a sequence diagram to explain a usage example in which a medical institution uses the reservation / reception service to accept a patient's return visit, and also interviews the patient using the medical interview service, and schedules an examination for the patient using the examination reservation service.
[0132] Suppose a returning patient who has already made a medical appointment with the medical institution using the reservation and reception service comes to the staff at the reception desk of the medical institution. In step S301, the staff at the medical institution who is treating the patient operates a terminal for the medical service providing system 3A and requests the medical service providing system 3A to execute a reception start process.
[0133] In step S302, the medical service providing system 3A displays medical information required for reception processing of the patient on the staff terminal (display unit 34 in FIG. 5). As in the first and second use examples, examples of the medical information required for reception processing include the patient's name and appointment time.
[0134] At present, the reception process at the medical institution cannot be displayed on the display unit 34 of the medical service providing system 3A, which is the same as in the first and second use examples.
[0135] In step S303, the staff member inputs new medical information associated with the reception process using the operation unit 35 of the medical service providing system 3A. Examples of the medical information newly input in step S303 include reception time, reason for visit, and the department the patient desires to see.
[0136] In step S304, the medical service providing system 3A transmits the newly input medical information to the gateway device 1.
[0137] In step S305, the gateway device 1 transmits the new medical information to the medical information management system 2.
[0138] In step S306, the medical information management system 2 updates the medical information DB 24 with the received new medical information.
[0139] This triggers the medical information management system 2 to extract medical information necessary for the medical service provision system 3A, which is a reception and reservation service, in step S307. The medical information necessary for the medical service provision system 3A here includes information such as the patient name and reservation time described in step S302, as well as past consultation dates and times, departments and doctor names visited in the past, and type of insurance.
[0140] In step S308, the medical information management system 2 transmits the extracted medical information to the gateway device 1.
[0141] In step S309, the gateway device 1 judges whether or not to permit transmission of the medical information received from the medical information management system 2 to the medical service providing systems 3A, 3B, and 3C. This judgment is made based on preset connection permission information. In this example, it is assumed that transmission of the medical information to all of the medical service providing systems 3A, 3B, and 3C is permitted.
[0142] In step S310, the gateway device 1 selects the type of medical information to be transmitted for each of the medical service providing systems 3A, 3B, and 3C for which it has been determined that transmission is permitted.
[0143] In step S311, the gateway device 1 transmits the medical information received from the medical information management system 2 to the medical service providing systems 3A, 3B, and 3C.
[0144] In step S312, the medical service providing system 3A, which has received the medical information necessary for the reception process, displays the received medical information on the display unit 34. This allows the staff of the medical institution to complete the reception process for the patient.
[0145] Furthermore, in step S313, the medical service providing system 3B (medical interview service) that has received the changed medical information starts preparation for an interview with the patient. Also, in step S314, the medical service providing system 3C (examination reservation service) that has received the changed medical information starts accepting examination reservations for the patient.
[0146] In this way, when the medical communication system 100 includes multiple medical service providing systems 3, the gateway device 1 determines whether or not to permit transmission of medical information for each medical service providing system 3. This makes it possible to prevent unnecessary information from being transmitted to the medical service providing system 3, thereby improving security. [Industrial Applicability]
[0147] The present disclosure is useful for medical communication systems that handle medical information. [Explanation of symbols]
[0148] 100 Medical Communication Systems 1. Gateway device 2 Medical Information Management System 3. Medical Service Delivery System 11 Permanent connection section 12 Judgment Department 13 Transmitter / receiver 14 Authentication Section 15 Storage section 21 Transmitter / receiver 22 Change detection unit 23 Extraction part 24 Medical Information Database 25 Display section 26 Control section 31 Transmitter / receiver 32 Service Provision Department 33 Medical Service Database 34 Display section 35 Control section 1000 Computers 1001 Input Device 1002 Output device 1006 Storage device 1007 Reading device 1008 Transmitting and receiving device 1009 Bus
Claims
1. A medical information management system implemented by a computer in an on-premise environment, comprising a gateway device that relays communication between the medical information management system that manages medical information and a medical service providing system that provides various services using the medical information, the gateway device is realized by a computer in a cloud environment, an authentication unit that authenticates the medical information management system and the medical service providing system; a constant connection unit that can establish a constant connection using a first communication protocol that maintains a constant connection with the authenticated medical information management system once communication is established and enables bidirectional communication; a transmission / reception unit that establishes a communication connection using a second communication protocol with the authenticated medical service providing system, the communication being cut off when the transmission and reception of information is completed, and transmits and receives the medical information; a storage unit that stores connection permission information indicating whether or not a connection between any one of the plurality of medical information management systems and any one of the plurality of medical service providing systems is permitted; a determination unit that determines whether or not to permit the communication connection between the medical information management system to which the constant connection has been established and the authenticated medical service providing system based on the connection permission information; A gateway device comprising:
2. When the medical information is changed in the medical information management system, the transmitting / receiving unit notifies the medical service providing system of the change. The gateway device according to claim 1 .
3. When the medical information is changed in the medical information management system, the transmitting / receiving unit transmits the changed medical information to the medical service providing system. The gateway device according to claim 2 .
4. The storage unit further stores type information indicating a type preset for each of the medical service providing systems among the multiple types of the medical information, The transmitting / receiving unit transmits the medical information of the type indicated by the type information to the medical service providing system. The gateway device according to claim 2 or 3.
5. a medical information management system for managing medical information; a gateway device that relays communication between the medical information management system and a medical service providing system that provides various services using the medical information; Equipped with The gateway device includes: This is realized by computers in a cloud environment, a first communication protocol that maintains a constant connection once communication is established between the medical information management system implemented by a computer in an on-premise environment and the medical service providing system, and determines whether to permit a communication connection between the medical information management system and the medical service providing system using a second communication protocol that disconnects communication when information transmission and reception is completed, based on the medical information management system with which a constant connection has been established and the connection permission information, and performs the communication connection if it is determined that the communication connection is permitted; Medical communication systems.
6. the medical information management system extracts the medical information of a type required by the medical service providing system from among the multiple types of medical information, and transmits the extracted medical information to the medical service providing system via the gateway device; The medical communication system of claim 5.
Citation Information
Patent Citations
Method for supplying medical device to medical institution and system for confirming medical device inventory
JP2002132959A
Medical information processing system
JP2005189994A
Medical service providing system and server device
JP2013146414A
Gateway device, communication method using gateway device, and communication program used for gateway device
JP2015045897A
Medical information system
JP2017208039A
