KR20230103332A - Websocket based untact medicine realtime service providing system and method - Google Patents

Abstract

The present invention relates to a security-enhanced websocket-based non-face-to-face medical service providing system and method, which is connected to a patient terminal device to provide real-time non-face-to-face medical treatment service, and a medical staff terminal device that displays patient medical records, and a medical staff terminal When a request for sharing a patient's medical record is received from the device, a relay server requests transmission of the patient's medical record to the following EMR (Electronic Medical Record) server and transmits the patient's medical record received from the EMR server to the patient terminal device. and an EMR server that retrieves patient medical records from the EMR DB and transmits them to the relay server at the request of the relay server.

Description

Websocket based untact medicine realtime service providing system and method with enhanced security

The present invention relates to a websocket-based non-face-to-face medical service providing system and method with enhanced security, and more particularly, to provide non-face-to-face medical service by selectively using websockets and RESTful APIs to enhance the security of an EMR system. It relates to a websocket-based non-face-to-face medical service providing system and method with enhanced security.

Telemedicine or untact medicine allows a patient who wants medical treatment to consult with a doctor non-face-to-face via video at home or in a telemedicine facility using video call equipment without going to the hospital. is to have If the patient has previously undergone an imaging test or blood test, the doctor can view the test result data so that a more accurate diagnosis can be made.

By launching the telemedicine service, patients can receive medical services even in environments where face-to-face treatment is difficult, such as remote areas, and have the advantage of avoiding the hassle of going to the hospital every time when chronic diseases are managed even if they are not in remote areas.

However, there is a limit to sharing the patient's personal medical records and test results with the patient during non-face-to-face treatment due to security issues. Therefore, there is a need for a technology that enables doctors and patients to safely share medical information, such as patient personal information, medical records, and test results, while protecting them from being leaked.

Domestic Patent No. 10-1651353 (registered on August 19, 2016)

In order to solve the above problems, the technical problem to be achieved by the present invention is to selectively use websockets and RESTful APIs to enhance the security of data such as patient medical records that are sensitive to external leakage, providing security for non-face-to-face medical treatment services. It is to present a system and method for providing non-face-to-face medical services based on enhanced web sockets.

The problems of the present invention are not limited to those mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the description below.

As a means for solving the above-described technical problem, according to an embodiment of the present invention, a websocket-based non-face-to-face medical service providing system with enhanced security includes a camera and is connected to a patient terminal device to provide real-time non-face-to-face medical treatment service. a medical staff terminal device that provides and displays patient medical records; When a request for sharing a patient's medical record is received from the medical staff terminal device, a request for transmission of the patient's medical record is made to the following EMR (Electronic Medical Record) server, and the patient's medical record received from the EMR server is transmitted to the patient terminal device. a relay server; and an EMR server that retrieves patient medical records from the EMR DB and transmits them to the relay server at the request of the relay server.

The medical staff terminal device executes a non-face-to-face medical treatment program for real-time non-face-to-face medical treatment service, transmits the medical staff image captured by the camera to the patient terminal device in real time through the relay server, and executes the EMR application to record patient medical treatment is displayed on the display unit, and the relay server is requested to transmit the patient medical record to the patient terminal device.

The relay server is connected to the patient terminal device and the medical staff terminal device through a web socket to perform a relay role, requests and receives patient medical records from the EMR server through a RESTful API distributed from the EMR server, and the EMR server The patient medical record received from the terminal is transmitted to the patient terminal device through the web socket.

The EMR server creates a RESTful API that can request patient medical records stored in the EMR DB, distributes it to the relay server, retrieves the patient medical records requested from the relay server through the RESTful API from the EMR DB, and uses the RESTful API. through the relay server.

On the other hand, a websocket-based non-face-to-face medical service providing method with enhanced security includes: (A) a medical staff terminal device displaying patient medical records and providing real-time non-face-to-face medical treatment service by being connected to a patient terminal device; (B) requesting, by the relay server, transmission of the patient's medical record from an EMR (Electronic Medical Record) server when a request for sharing the patient's medical record is received from the medical staff terminal device; (C) the EMR server searching for patient medical records from the EMR DB according to the request of the relay server and transmitting the data to the relay server; and (D) transmitting, by the relay server, the patient medical record received from the EMR server to the patient terminal device.

In the step (B), the relay server receives a request for sharing the patient's medical record from the medical staff terminal device through the websocket, and requests transmission of the patient's medical record from the EMR server through the RESTful API distributed from the EMR server. , In the step (C), the EMR server transmits the patient medical record retrieved from the EMR DB to the relay server through a RESTful API, and in the step (D), the relay server transmits the patient medical record through the websocket. is transmitted to the patient terminal device.

The present invention selectively uses web sockets and RESTful APIs to provide non-face-to-face treatment services to patient terminal devices and medical staff terminal devices, thereby blocking direct access to the EMR server from inside and outside hospitals and clinics, and sharing patient medical record information to EMR. It is possible to enhance the security of medical records related to

The effects of the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

1 is a diagram showing a websocket-based non-face-to-face medical service providing system with enhanced security according to an embodiment of the present invention;
2 is a diagram showing a communication method of a websocket-based non-face-to-face medical service providing system with enhanced security;
3 is a block diagram showing the medical staff terminal device 200 shown in FIG. 1;
Figure 4 is a block diagram showing the relay server 300 shown in Figure 1, and,
5 is a flowchart illustrating a websocket-based non-face-to-face medical service providing method with enhanced security according to an embodiment of the present invention.

The above objects, other objects, features and advantages of the present invention will be easily understood through the following preferred embodiments in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments described herein and may be embodied in other forms. Rather, the embodiments introduced herein are provided so that the disclosed content will be thorough and complete and the spirit of the present invention will be sufficiently conveyed to those skilled in the art.

In some cases, it is mentioned in advance that parts that are commonly known in describing the invention and are not greatly related to the invention are not described in order to prevent confusion for no particular reason in explaining the present invention.

When an element, component, device, or system is referred to in this specification as comprising a program or component consisting of software, even if not explicitly stated otherwise, that element, component, device, or system means that the program or software It should be understood that it includes hardware (eg, memory, CPU, etc.) or other programs or software (eg, operating system or driver required to drive hardware) required for execution or operation.

In addition, it should be understood that, unless otherwise specified, the element (or component) may be implemented in any form of software, hardware, or both software and hardware.

In addition, terms used in this specification are for describing embodiments and are not intended to limit the present invention. In this specification, singular forms also include plural forms unless specifically stated otherwise in a phrase. The terms 'comprises' and/or 'comprising' used in the specification do not exclude the presence or addition of one or more other elements.

In addition, in this specification, terms such as 'unit', 'module', 'server', 'system', 'device' or 'terminal' refer to functional and structural aspects of hardware and software driven by the hardware or for driving the hardware. It may be intended to refer to a bond. For example, the hardware herein may be a data processing device including a CPU or other processor. Also, software driven by hardware may refer to a running process, an object, an executable file, a thread of execution, a program, and the like.

Hereinafter, with reference to the accompanying drawings for the specific technical content to be carried out in the present invention will be described in detail.

Each component shown in the drawing indicates that it can be functionally and logically separated, and does not necessarily mean that each component is classified as a separate physical device or written as a separate code. An expert will be able to infer easily.

1 is a diagram showing a websocket-based non-face-to-face medical service providing system with enhanced security according to an embodiment of the present invention, and FIG. 2 is a diagram showing a communication method of a websocket-based non-face-to-face medical service providing system with enhanced security am.

Referring to FIGS. 1 and 2 , the security-enhanced websocket-based non-face-to-face medical service providing system according to an embodiment of the present invention includes a patient terminal device 100, a medical staff terminal device 200, a relay server 300, It may include an Electronic Medical Record (EMR) server 400 , an image server 500 and a data server 600 .

In FIG. 2, the image flow shows the flow of real-time image transmission between the medical staff and the patient, and the data flow shows the flow of requesting and transmitting data such as patient medical records that require security.

The patient terminal device 100 may include a camera and install and execute a non-face-to-face treatment program for real-time non-face-to-face treatment service. The patient terminal device 100 may be an electronic device such as a smart phone or a personal computer including a communication interface module, a memory, and at least one processor. Patients who want medical treatment can run a non-face-to-face treatment program and receive non-face-to-face treatment services with medical staff.

The medical staff terminal device 200 is a computer used by medical staff of hospitals and clinics, includes a camera, and is connected to the patient terminal device 100 through a relay server 300 and a web socket to provide real-time non-face-to-face medical treatment services, and EMR The patient's medical record can be displayed by executing the application.

The relay server 300 is a demilitarized zone (DMZ) server for providing non-face-to-face medical treatment services while maintaining the security of the EMR system.

The relay server 300 is communicatively connected to the patient terminal device 100 and the medical staff terminal device 200 through a web socket, and can communicate through the EMR server 400 and a RESTful API distributed from the EMR server 400. It is set to do so and can serve as a relay for non-face-to-face medical services.

When receiving a request for sharing patient medical records from the medical staff terminal device 200 through the websocket, the relay server 300 requests the EMR server 400 to transmit the patient medical records through a RESTful API, and the EMR server 400 ), the patient medical record received through the RESTful API may be transmitted to the patient terminal device 100 or the medical staff terminal device 200 through the web socket.

Accordingly, the relay server 300 may block direct access to the inside (eg, the EMR server 400) from the outside of the EMR system, such as the patient terminal device 100. That is, security can be strengthened by the relay server 300 performing data transmission and reception with the EMR server 400 using dynamic creation of a RESTful interface instead of web sockets.

In addition, the relay server 300 may protect packets through the establishment of a Secure Sockets Layer (SSL) secure channel between non-face-to-face treatment participants, that is, between the patient terminal device 100 and the medical staff terminal device 200.

In addition, the relay server 300 performs a role of transmitting parameters after forming a secure channel between the patient terminal device 100 and the medical staff terminal device 200 to prevent hacking attempts into the EMR server 400 from outside the EMR system in advance. can Parameter transmission creates detailed conditions for actually bringing the data to the EMR server 400 when, for example, when a sharing request of data (patient medical records) requiring security is requested from the medical staff terminal device 200, the EMR server 400 ) to convey.

The EMR server 400 may retrieve patient medical records from an EMR DB (not shown) and transmit them to the relay server 300 according to a request of the relay server 300 .

The EMR server 400 creates in advance a RESTful API that can request patient medical records stored in the EMR DB, distributes it to the relay server 300, and transmits the patient medical records requested from the relay server 300 through the RESTful API to the EMR It can be retrieved from the DB and transmitted to the relay server 300 through a RESTful API.

Alternatively, the EMR server 400 may create a RESTful API and distribute it to the relay server 300 whenever transmission of patient medical records stored in the EMR DB is requested or periodically. In this case, the security of the EMR system may be further strengthened by using a different RESTful API for each medical staff terminal device requesting information sharing or by periodically regenerating the RESTful API.

The data server 600 is a server that stores and manages management data for providing non-face-to-face medical treatment services. For example, the data server 600 stores reservation information, values managed in screen design, hospital institution information, usage log management, and the like. The relay server 300 may directly access and query the data server 600 in the jdbc method.

The image server 500 provides an image engine for providing real-time non-face-to-face medical treatment through images between the patient terminal device 100 and the medical staff terminal device 200. The video server 500 may communicate with the relay server 300 in a websocket method.

Hereinafter, the medical staff terminal device 200 and the relay server 300 will be described with reference to FIGS. 3 and 4 .

FIG. 3 is a block diagram illustrating the medical staff terminal device 200 shown in FIG. 1 .

Referring to FIG. 3 , the medical staff terminal device 200 includes a medical staff communication unit 210, a medical staff camera 220, a user interface unit 230, a display unit 240, a medical staff memory 250 and a medical staff processor 260. can do.

The medical staff communication unit 210 may include a communication module capable of communicating with the relay server 300 through a web socket.

The medical staff camera 220 captures the medical staff's face in real time.

The user interface unit 230 provides an interfacing path between the medical staff and the medical staff terminal device 200, and receives commands from the medical staff and transmits them to the medical staff processor 260. The user interface unit 230 may include, for example, a mouse, a keyboard, and a touch panel.

The display unit 240 may display a processing result of the medical staff processor 260 according to the medical staff command of the user interface unit 230 . For example, the display unit 240 may display a non-face-to-face treatment screen generated when a non-face-to-face treatment program is executed, real-time images of medical staff and patients participating in non-face-to-face treatment, and patient medical records generated when an EMR application is executed. there is.

The medical staff memory 250 may include volatile memory and/or non-volatile memory. In the medical staff memory 250, for example, commands or data related to the components 210 to 260, one or more programs and /or software, operating system, etc. may be stored.

In addition, non-face-to-face treatment programs and EMR applications may be stored in the medical staff memory 250 .

The non-face-to-face treatment program is a program that provides a real-time non-face-to-face treatment service using real-time streaming or real-time video/chat, and may be a program that uses an existing video conference program or is provided only within a hospital or clinic.

The EMR application is a program that works with the EMR server 400, displays patient medical records provided from the EMR server 400, and sends additional medical records input by medical staff through the user interface 230 to the EMR server 400. can be stored in

The medical staff processor 260 controls the overall operation of the medical staff terminal device 200 by executing one or more programs stored in the medical staff memory 250 .

For example, the medical staff processor 260 may execute a non-face-to-face treatment program stored in the medical staff memory 250 and process it so that real-time non-face-to-face treatment with the patient terminal device 100 is possible. That is, the medical staff processor 260 executes the non-face-to-face treatment program, transmits the medical staff image captured by the medical staff camera 220 to the patient terminal device 100 in real time, and transmits the patient image received from the patient terminal device 100. It can be processed to be displayed on the display unit 240 in real time.

In addition, the medical staff processor 260 may execute the EMR application to receive patient medical record information from the EMR server 400 through the relay server 300 and display it on the display unit 240 .

Also, when the medical staff requests sharing of the patient's medical record through the EMR application, the medical staff processor 260 may request the relay server 300 to transmit the patient's medical record to the patient terminal device 100 . The medical staff processor 260 generates a request including identification information of the patient's medical record (eg, patient name and chart management number of the patient), and the medical staff communication unit 210 sends the relay server 300 through a websocket. Requests can be sent.

FIG. 4 is a block diagram illustrating the relay server 300 shown in FIG. 1 .

Referring to FIG. 4 , the relay server 300 may include a relay communication unit 310 , a relay memory 320 and a relay processor 330 .

The relay communication unit 310 communicates with the patient terminal device 100, the medical staff terminal device 200, and the image server 500 through web sockets, communicates with the data server 600 through jdbc, and the EMR server 400 and a communication module that can communicate through a RESTful API.

The relay memory 320 may include volatile memory and/or non-volatile memory. In order to implement and/or provide operations and functions provided by the relay server 300, the relay memory 320 includes instructions or data related to the components 310 to 330, one or more programs and/or software, and an operating system. etc. can be stored.

In addition, the relay memory 320 serves as a relay for non-face-to-face medical treatment services, blocks the patient terminal device 100 or the medical staff terminal device 200 from directly accessing the EMR server 400, and prevents hacking. A program for doing this may be stored.

The relay processor 330 controls the overall operation of the relay server 300 by executing one or more programs stored in the relay memory 320 .

For example, when a request for sharing a patient's medical record is received from the medical staff terminal device 200, the relay processor 330 generates a parameter for requesting search and delivery of the patient's medical record, and transmits the relay communication unit 310. It is possible to control the relay communication unit 310 to transmit parameters to the EMR server 400 by using the RESTful API distributed in the EMR server 400 by controlling. Accordingly, the EMR server 400 may parse parameters to check detailed conditions, retrieve patient medical records corresponding to the detailed conditions from the EMR DB, and transmit the data to the relay server 300 through a RESTful API.

The relay processor 330 may transmit the patient medical records received from the EMR server 400 to the patient terminal device 100 or the medical staff terminal device 200 through a web socket.

5 is a flowchart illustrating a websocket-based non-face-to-face medical service providing method with enhanced security according to an embodiment of the present invention.

Referring to FIG. 5 , the patient terminal device 100 and the medical staff terminal device 200 are video-connected through the websocket to enable non-face-to-face medical treatment through relaying of the relay server 300 (S510 and S515).

When the medical staff terminal device 200 and the patient terminal device 100 complete access to the non-face-to-face system (ie, relay server) 300, the relay server 300 transmits medical treatment information to the EMR server (ie, relay server) through a RESTful API. 400) is requested and received (S520). Step S520 may be automatically performed by the relay server 300 when the medical staff terminal device 200 and the patient terminal device 100 are connected to the non-face-to-face system for the first time.

The relay server 300 transmits the medical treatment information received through the RESTful API to the patient terminal device 100 and the medical staff terminal device 200 through the web socket (S525 and S530).

When the medical staff terminal 200 requests input of additional information such as patient's body information through the running EMR application, the relay server 300 transmits the request for input of additional information such as body information to the patient terminal 100 (S535). , S540).

The patient terminal device 100 creates additional information, such as body information, and transmits it to the relay server 300 through the websocket, and the relay server 300 transmits the rewritten additional information, such as body information, through the websocket to the medical staff terminal device ( 200) (S545, S550), and at the same time it is transmitted to and stored in the EMR server 400 (S555, S560)

While the patient and the medical team are seeing medical treatment non-face-to-face, when sharing the patient's medical record is requested through the EMR application of the medical staff terminal device 200 (S565), the relay server 300 transmits the EMR server 400 through the RESTful API. Request transmission of patient medical record information (S570).

The EMR server 400 retrieves patient medical record information from the EMR DB according to the request received through the RESTful API and transmits it to the relay server 300 through the RESTful API again (S575 and S580).

The relay server 300 transmits the received patient medical records to the patient terminal device 100 or the medical staff terminal device 200 through a web socket (S585 and S590).

The patient terminal device 100 displays the received patient medical records (S595), and the doctor terminal device 200 simultaneously displays the received patient medical records (S600).

In the above, even though all the components constituting the embodiment of the present invention have been described as being combined or operated as one, the present invention is not necessarily limited to these embodiments. That is, within the scope of the object of the present invention, all of the components may be selectively combined with one or more to operate. In addition, although all of the components may be implemented as a single independent hardware, some or all of the components are selectively combined to perform some or all of the combined functions in one or a plurality of hardware. It may be implemented as a computer program having. Codes and code segments constituting the computer program can be easily inferred by a person skilled in the art. Such a computer program may implement an embodiment of the present invention by being stored in a computer readable storage medium, read and executed by a computer.

On the other hand, although the above has been described and illustrated in relation to preferred embodiments for illustrating the technical idea of the present invention, the present invention is not limited to the configuration and operation as shown and described in this way, and departs from the scope of the technical idea. It will be apparent to those skilled in the art that many changes and modifications can be made to the present invention without modification. Accordingly, all such appropriate alterations and modifications and equivalents are to be regarded as falling within the scope of the present invention. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the attached claims.

100: patient terminal device 200: medical staff terminal device
300: relay server 400: EMR server
500: video server 600: data server

Claims (6)

In the websocket-based non-face-to-face medical service providing system with enhanced security,
a medical staff terminal device that includes a camera, is connected to a patient terminal device, provides real-time non-face-to-face medical treatment service, and displays patient medical records;
When a request for sharing a patient's medical record is received from the medical staff terminal device, a request for transmission of the patient's medical record is made to the following EMR (Electronic Medical Record) server, and the patient's medical record received from the EMR server is transmitted to the patient terminal device. a relay server; and
an EMR server that retrieves patient medical records from the EMR DB according to a request of the relay server and transmits the data to the relay server;
Security-enhanced websocket-based non-face-to-face medical service providing system that includes.
According to claim 1,
The medical staff terminal device,
By executing a non-face-to-face medical treatment program for real-time non-face-to-face medical treatment service, the medical staff image captured by the camera is transmitted to the patient terminal device in real time through the relay server, and the EMR application is executed to display a screen showing patient medical records on the display unit. A websocket-based non-face-to-face medical service providing system with enhanced security, characterized in that for displaying and requesting the relay server to transmit the patient's medical records to the patient's terminal device.
According to claim 1,
The relay server,
It is connected to the patient terminal device and the medical staff terminal device through a websocket to perform a relay role, requests and receives patient medical records from the EMR server through the RESTful API distributed from the EMR server, and receives patient care from the EMR server. A websocket-based non-face-to-face medical service providing system with enhanced security, characterized in that the record is transmitted to a patient terminal device through a websocket.
According to claim 1,
The EMR server,
A RESTful API that can request patient medical records stored in the EMR DB is created and distributed to the relay server, and the patient medical records requested from the relay server through the RESTful API are retrieved from the EMR DB and transmitted to the relay server through the RESTful API. Websocket-based non-face-to-face medical service providing system with enhanced security, characterized in that.

In the security-enhanced websocket-based non-face-to-face medical service providing method,
(A) a medical staff terminal device displaying patient medical records and providing real-time non-face-to-face medical treatment services by being connected to a patient terminal device;
(B) requesting, by the relay server, transmission of the patient's medical record from an EMR (Electronic Medical Record) server when a request for sharing the patient's medical record is received from the medical staff terminal device;
(C) the EMR server searching for patient medical records from the EMR DB according to the request of the relay server and transmitting the data to the relay server; and
(D) transmitting, by the relay server, the patient medical record received from the EMR server to the patient terminal device;
Security-enhanced websocket-based non-face-to-face treatment service providing method comprising a.
According to claim 5,
In step (B),
The relay server receives a request for sharing a patient medical record from a medical staff terminal device through a web socket, requests transmission of a patient medical record from the EMR server through a RESTful API distributed from the EMR server,
In step (C),
The EMR server transmits the patient medical records retrieved from the EMR DB to the relay server through a RESTful API;
In the step (D),
A websocket-based non-face-to-face medical service providing method with enhanced security, characterized in that the relay server transmits the patient's medical records to the patient terminal device through the websocket.

Images