KR20230167228A - Method and apparatus for non-face-to-face hospital reception using wireless communication, and system thereof - Google Patents

Abstract

The present invention relates to a non-face-to-face hospital reception system, device, and method. The present invention has the advantage of allowing users to easily register for hospital treatment while maintaining security by using a wireless communication method, especially a Bluetooth low energy (BLE) profile. there is.

Description

Non-face-to-face hospital reception method, device, and system using wireless communication {METHOD AND APPARATUS FOR NON-FACE-TO-FACE HOSPITAL RECEPTION USING WIRELESS COMMUNICATION, AND SYSTEM THEREOF}

The present invention relates to wireless communication technology, particularly short-range wireless communication using Bluetooth beacons.

When a patient visits the hospital for treatment, he or she must first go through an application process.

If you are visiting the hospital for the first time, you generally fill out the application form provided at the hospital or verbally convey information to the reception staff.

If it is not a first-time patient, there is no need to convey all information again, but it is necessary to convey some information to verify the patient's information, such as name or contact information.

In some hospitals, registration for first or return visits is now done using kiosks or tablets.

However, this information includes not only the patient's name and contact information, but also sensitive information such as resident registration number, address, and disease name. This information is at risk of being leaked in places where many people come and go, such as hospital waiting rooms or reception desks. There may be. In particular, in departments such as psychiatry, patients' anxiety and vigilance inevitably increase, making it more difficult to convey information.

Additionally, when entering information into the hospital system, the information may be entered incorrectly, and when the number of patients increases and the system becomes crowded, the reception time takes a long time and communication becomes difficult.

Accordingly, the inventor of the present invention completed the present invention after a long period of research and trial and error in order to provide a hospital reception system and method that accurately transmits information without error and prevents sensitive information from being exposed.

The present invention relates to wireless communication technology, and its purpose is to provide a method, device, and system that can safely transmit hospital reception information, including sensitive personal information, to a hospital reception computer while maintaining security.

Meanwhile, other unspecified purposes of the present invention will be additionally considered within the scope that can be easily inferred from the following detailed description and its effects.

In accordance with an embodiment of the present invention, in a non-face-to-face hospital treatment reception system using wireless communication consisting of a user terminal, a callback server, a hospital reception terminal, and a remote server,

The user terminal searches for the hospital reception terminal connectable through wireless communication to receive medical treatment,

The user terminal transmits the ID of the searched hospital reception terminal to the remote server,

The remote server transmits a public key corresponding to the ID of the hospital reception terminal to the user terminal,

The user terminal encrypts the user's personal information for receiving medical treatment using the received public key,

The user terminal transmits the encrypted personal information, the callback address of the user terminal, and the hospital reception terminal ID to the remote server,

The remote server transmits the encrypted user information and the callback address of the user terminal to the hospital reception terminal,

The hospital reception terminal transmits the callback address and reception result to the callback server,

The callback server transmits the reception result to the user terminal,

This is about a non-face-to-face hospital treatment reception system using wireless communication.

According to an embodiment of the present invention, the wireless communication uses one or more of Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE). It can be included.

According to one embodiment of the present invention, the hospital reception terminal and the remote server may be connected through end-to-end encryption through SSL (Secure Sockets Layer) through web socket communication or HTTP communication.

According to one embodiment of the present invention, the hospital reception terminal may further include a Bluetooth module or Bluetooth device for communication with the user terminal.

In a non-face-to-face hospital treatment reception method using wireless communication performed by a user terminal including one or more processors and memory according to an embodiment of the present invention,

Searching for a hospital reception terminal connectable through wireless communication to receive medical treatment;

transmitting the searched ID of the hospital reception terminal to a remote server;

Receiving a public key corresponding to the ID of the hospital reception terminal from the remote server;

Encrypting the user's personal information for registering for medical treatment using the public key;

Transmitting the encrypted personal information, the callback address of the user terminal, and the hospital reception terminal ID to the server; and

Receiving a reception result from a callback server;

It relates to a non-face-to-face hospital treatment reception method using wireless communication, including.

According to an embodiment of the present invention, the wireless communication is one of WiFi, Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE). It may include more.

According to one embodiment of the present invention, the step of encrypting the user's personal information for receiving medical treatment using the public key may be encrypted using an asymmetric key encryption method.

According to one embodiment of the present invention, the asymmetric key encryption may use the RSAES-OAEP algorithm.

In a non-face-to-face hospital treatment reception method using wireless communication performed by a hospital reception terminal including one or more processors and memory according to an embodiment of the present invention

transmitting the ID of the hospital reception terminal to the user terminal through the wireless communication;

Receiving user information encrypted and transmitted from the user terminal to a remote server and a callback address of the user terminal from the remote server;

Decrypting the received encrypted user information with a private key and comparing it with patient information on the EMR server; and

delivering a reception result based on a result of comparing the decrypted user information to the user terminal through a mobile callback server;

Characterized in that it includes,

Provides a non-face-to-face hospital treatment reception method using wireless communication.

According to an embodiment of the present invention, the wireless communication is one of WiFi, Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE). It may include more.

As a user terminal according to an embodiment of the present invention,

One or more processors;

a memory coupled to the one or more processors; and

a communication module connected to the one or more processors;

Including,

Computer-readable instructions are stored in the memory,

When the instructions are executed by the one or more processors, the method described above is performed,

Provides a user terminal.

As a hospital reception terminal according to an embodiment of the present invention,

One or more processors; and

a memory coupled to the one or more processors; and

a communication device coupled to the one or more processors;

Including,

Computer-readable instructions are stored in the memory,

When the instructions are executed by the one or more processors, the method described above is performed,

According to an embodiment of the present invention, the communication device may be a BLE (Bluetooth Low Energy) communication device.

According to the present invention, sensitive personal information can be safely encrypted and transmitted to the hospital reception computer without disclosing it.

Additionally, there is the advantage of being able to easily register at the hospital without having to directly record or enter personal information.

Meanwhile, it is to be added that even if the effects are not explicitly mentioned herein, the effects described in the following specification and their potential effects expected from the technical features of the present invention are treated as if described in the specification of the present invention.

1 is a structural diagram of a hospital reception system according to an embodiment of the present invention.
Figure 2 is a flowchart of a non-face-to-face hospital reception method using a user terminal according to another embodiment of the present invention.
Figure 3 is a flowchart of a non-face-to-face hospital reception method using a hospital reception terminal according to another embodiment of the present invention.
Figure 4 is a schematic structural diagram of a user terminal according to another embodiment of the present invention.
Figure 5 is a schematic structural diagram of a hospital reception terminal according to another embodiment of the present invention.
The attached drawings are intended as reference for understanding the technical idea of the present invention, and are not intended to limit the scope of the present invention.

In describing the present invention, if it is determined that related known functions may unnecessarily obscure the gist of the present invention as they are obvious to those skilled in the art, the detailed description thereof will be omitted.

The terms used in this application are only used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Hereinafter, embodiments of the non-face-to-face hospital reception method, device, and system using wireless communication according to the present invention will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, the same or corresponding components are included. will be assigned the same drawing number and overlapping description will be omitted.

1 is a structural diagram of a hospital reception system according to an embodiment of the present invention.

The hospital reception system 1 according to the present invention includes a user terminal 100, a hospital reception terminal 200, a remote server 300, and a callback server 400.

The hospital reception terminal 200 may further include a communication module 210 for wireless communication.

Additionally, the hospital reception system 1 may also include an Electronic Medical Record (EMR) server 220 that stores information on hospital patients.

The hospital reception terminal 200 is connected to the remote server 300 through a socket.

All communications in the hospital reception system (1) are end-to-end encrypted through SSL (Secure Sockets Layer) for information protection, so the content of communications cannot be discovered or modified from the outside.

The remote server 300 provides a trusted public certificate to the hospital reception terminal ( 200).

The hospital reception terminal 200 can perform socket communication with a remote server and control the communication module 210 connected to itself.

The communication module 210 includes WiFi, Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy for wireless communication with the user terminal 100. It may be a communication module 210 that supports one or more communications (BLE).

In particular, in the present invention, a BLE device that can be optimized in a hospital environment can be used as the communication module 210.

The user terminal 100 may register its callback address in the callback server 400.

The callback server 400 can transmit data through a registered callback address using a push message, etc., to a mobile app of the user terminal 100.

To this end, the user terminal 100 can create and use a new callback address every time it attempts to register at the hospital.

Since the connection between the user terminal 100 and the callback server 400 is also encrypted through SSL, the information exchanged between the two cannot be discovered or modified from the outside.

For reception, the user terminal 100 and the hospital reception terminal 200 must be connected, and here, a wireless communication method is used. As described above, various wireless communication technologies can be used, and the description here assumes a BLE connection, but the present invention is not limited thereto.

Bluetooth devices can transmit signals to nearby Bluetooth devices through advertisement mode.

At this time, the ID of the Bluetooth device that allows other Bluetooth devices to identify it is called SSID (Service Set Identifier).

Since the SSID may be set to be the same for multiple Bluetooth devices in advertising mode, in the present invention, the SSID of the communication device 210 connected to the hospital reception terminal 200 is set to have a unique value that satisfies a specific format, so that the user terminal ( 100) is able to uniquely identify the hospital reception terminal 200.

The specific format used is the regular expression `^C2_[0-9A-Fa-f]{4}_[0-9A-Za-z]{12}_[0-9A-Fa-f]{2}$ It can be defined as `, and for example, the SSID can be used as 'C2_000C_LOKSNPT6KR28_01'. In the hospital reception system (1), there must be only one hospital reception terminal (200) using the corresponding SSID.

After the socket connection is completed, the hospital reception terminal 200 provides an ID (ID) to identify itself. ) and the Bluetooth SSID you will use ( ),, public key-private key pair to use ), creating these ) is transmitted to the remote server 300 and registered.

The hospital reception terminal 200 then determines the SSID of the communication module 210. Set to start advertising mode.

The maximum communication distance of a Bluetooth device is about 10m to 30m depending on the surrounding environment, so it is sufficient for the waiting room range of a typical hospital, and therefore, patients visiting the hospital will be able to access the hospital reception terminal 200 from anywhere in the waiting room.

In this environment, the patient attempts to register at the hospital reception terminal 200 using the user terminal 100.

First, the user terminal 100 registers its callback address (callback) with the callback server 400 to transmit a push message.

For example, the callback address is https://callback.example.com/ae9fae0c76a… It can have the same format, but if you use the https protocol, the latter part of the access address is ae9fae0c76a... Since this part is encrypted, these addresses will not be exposed to the outside world.

The user terminal 100 then scans the surrounding Bluetooth signal to determine the SSID (SSID) that satisfies the specific format of the hospital reception terminal 200. ) is detected.

When such an SSID is found, it is transmitted to the remote server 300, and the remote server 300 searches for the hospital reception terminal 200 using the corresponding Bluetooth SSID.

When the remote server 300 discovers the hospital reception terminal 200 using the corresponding Bluetooth SSDI, the ID and public key of the hospital reception terminal 200 are transmitted to the user terminal 100.

The remote server 300 transmits hospital information related to the hospital reception terminal 200 to the user terminal 100, and the user terminal 100 transmits this to the user through a display device, etc., so that the hospital to which the user wishes to apply is confirmed. You can check if it is correct.

If the user confirms that the hospital to which he or she wishes to register is correct, the mobile app of the user terminal 100 receives the information required for reception (name, phone number, resident registration number, address, blood type, other notes, etc.) entered by the patient in advance. Public key of the hospital reception terminal 200 ( ) is used to encrypt using asymmetric key encryption.

The user terminal 100 transmits the generated encryption information to the remote server 300 along with its callback address and ID.

At this time, an algorithm such as RSAES-OAEP may be used as an asymmetric key encryption method.

The remote server 300 checks the received ID and transmits the callback address and encrypted information of the user terminal 100 to the corresponding hospital reception terminal 200 among the plurality of hospital reception terminals connected to it.

The hospital reception terminal 200 uses the received encrypted information with its private key ( ) can be used to decrypt it and use it to register for medical treatment.

When the application is completed, the hospital reception terminal 200 transmits the reception result along with the callback address of the user terminal 100 to the callback server 400, and the callback server 400 sends the reception result to the user terminal 100 corresponding to the callback address. The application results can be sent through push messages, etc.

Since the callback address generated in the mobile app of the user terminal 100 can be maintained for a certain period of time, the hospital reception terminal 200 can transmit data to the mobile app of the user terminal 100 at any time within a certain period of time.

During this time, the hospital reception terminal 200 uses the callback address to provide not only the reception result, but also the reception status (e.g., current number of people waiting, turn number, expected waiting time, etc.) or information messages (e.g., information about the examination room, treatment room, etc.) Entrance information, etc.), prescription data, etc. can be transmitted to the user terminal 100.

The callback server 400 will need to delete the callback address after a certain period of time (eg, 12 hours).

Registration information including resident registration number, name, address, phone number, etc. is stored only in the user terminal 100, and is temporarily stored in the remote server 300 only in encrypted form.

The hospital reception terminal 200 must periodically change the public key for encryption.

In addition, the EMR server 220 within the hospital contains patient information that has gone through a personal information use consent process, but this is only used to identify the patient.

Additionally, real-name authentication information using a telecommunication company, etc. can be included in the reception information, and in such cases, it can be confirmed whether real-name authentication has been performed properly.

In Figure 2, a non-face-to-face hospital reception method performed by the user terminal 100 is disclosed.

For registration, the user terminal 100 first searches for the hospital reception terminal 200 (S110).

When the hospital reception terminal 200 is discovered, the ID of the hospital reception terminal 200 is transmitted to the remote server 300 (S120).

The remote server 300, which has received the ID of the hospital reception terminal 200, transmits the public key of the hospital reception terminal 200 using the ID to the user terminal 100, and the user terminal 100 receives it. (S130).

The user terminal 100, which has received the public key, encrypts personal information such as the user's name, phone number, resident registration number, and address using the public key (S140).

Next, the user terminal 100 transmits the encrypted personal information along with the callback address of the user terminal 100 and the ID of the hospital reception terminal to the remote server 300 (S150), and the remote server 300 transmits the encrypted personal information. and the callback address are transmitted to the hospital reception terminal (200) (S160).

The hospital reception terminal 200 decrypts the received encrypted personal information with a private key, checks the hospital EMR server for patient information that matches the personal information, and then registers for treatment.

The hospital reception terminal 200 transmits the reception result along with the callback address of the user terminal 100 to the callback server 400 (S170), and the user terminal 100 receives the reception result through the callback server 400. (S180).

Figure 3 is a schematic flowchart of a hospital reception method performed by the hospital reception terminal 200.

The hospital reception terminal 200 first transmits its ID to the user terminal 100 through wireless communication (S210). If the wireless communication method used at this time is BLE, the hospital reception terminal 200 can transmit the SSID to the user terminal 100 through advertising mode.

Next, the hospital reception terminal 200 receives the personal information and callback address encrypted by the user terminal 100 through the remote server 300 (S220).

The received encrypted personal information is decrypted with the private key of the hospital reception terminal 200 and compared with the patient information stored in the EMR server (S230).

If the comparison results match the patient information, treatment is registered, and the results are delivered to the user terminal through the mobile callback server (S240, S250).

Figure 4 is a schematic structural diagram of a user terminal according to another embodiment of the present invention.

The user terminal 100 may include one or more processors 110, memory 120, and communication module 130.

Memory 120 is connected to processor 110, and computer-readable instructions that can be executed on one or more processors 110 are stored in memory 120.

The communication module 130 is connected to the processor 110 and is controlled by the processor 110 and connected to the hospital reception terminal 200.

The communication module 130 communicates with the hospital reception terminal ( 200).

When the instructions stored in the memory 120 are executed by one or more processors 110, they can perform the hospital reception methods described above.

Figure 5 is a schematic structural diagram of a hospital reception terminal according to another embodiment of the present invention.

The hospital reception terminal 200 may include one or more processors 210 and memory 220.

The hospital reception terminal 200 may further include a communication device 230. The communication device 230 may not be built into the hospital reception terminal 200 but may be an external, independent device.

Memory 220 is connected to processor 210, and computer-readable instructions that can be executed on one or more processors 210 are stored in memory 220.

The communication device 230 is connected to the processor 210 and is controlled by the processor 210 and connected to the user terminal 100.

The communication device 230 communicates with the user terminal 100 by one or more communication methods among Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE). ) can communicate with.

When the instructions stored in the memory 120 are executed by one or more processors 110, they can perform the hospital reception methods described above.

The scope of protection of the present invention is not limited to the description and expression of the embodiments explicitly described above. In addition, it is added once again that the scope of protection of the present invention may not be limited due to changes or substitutions that are obvious in the technical field to which the present invention pertains.

Claims (13)

In a non-face-to-face hospital treatment reception system using wireless communication consisting of a user terminal, a callback server, a hospital reception terminal, and a remote server,
The user terminal searches for the hospital reception terminal connectable through wireless communication to receive medical treatment,
The user terminal transmits the ID of the searched hospital reception terminal to the remote server,
The remote server transmits a public key corresponding to the ID of the hospital reception terminal to the user terminal,
The user terminal encrypts the user's personal information for receiving medical treatment using the received public key,
The user terminal transmits the encrypted personal information, the callback address of the user terminal, and the hospital reception terminal ID to the remote server,
The remote server transmits the encrypted user information and the callback address of the user terminal to the hospital reception terminal,
The hospital reception terminal transmits the callback address and reception result to the callback server,
The callback server transmits the reception result to the user terminal,
Non-face-to-face hospital treatment reception system using wireless communication.
According to paragraph 1,
The wireless communication includes one or more of WiFi, Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE).
Non-face-to-face hospital treatment reception system using wireless communication.
According to paragraph 1,
The hospital reception terminal and the remote server are end-to-end encrypted and connected through SSL (Secure Sockets Layer) through web socket communication or HTTP communication,
Non-face-to-face hospital treatment reception system using wireless communication.
According to paragraph 1,
The hospital reception terminal further includes a Bluetooth module or Bluetooth device for communication with the user terminal,
Non-face-to-face hospital treatment reception system using wireless communication.
In a non-face-to-face hospital medical treatment reception method using wireless communication performed by a user terminal including one or more processors and memory,
Searching for a hospital reception terminal connectable through wireless communication to receive medical treatment;
transmitting the searched ID of the hospital reception terminal to a remote server;
Receiving a public key corresponding to the ID of the hospital reception terminal from the remote server;
Encrypting the user's personal information for registering for medical treatment using the public key;
Transmitting the encrypted personal information, the callback address of the user terminal, and the hospital reception terminal ID to the server; and
Receiving a reception result from a callback server;
Non-face-to-face hospital treatment reception method using wireless communication, including.
According to clause 5,
The wireless communication includes one or more of Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE).
Non-face-to-face hospital treatment registration method using wireless communication.
According to clause 5,
The step of encrypting the user's personal information for receiving medical treatment using the public key is encrypted using an asymmetric key encryption method.
Non-face-to-face hospital treatment registration method using wireless communication.
In clause 7,
The asymmetric key encryption uses the RSAES-OAEP algorithm,
Non-face-to-face hospital treatment registration method using wireless communication.
In a non-face-to-face hospital treatment reception method using wireless communication performed by a hospital reception terminal including one or more processors and memory
transmitting the ID of the hospital reception terminal to the user terminal through the wireless communication;
Receiving user information encrypted and transmitted from the user terminal to a remote server and a callback address of the user terminal from the remote server;
Decrypting the received encrypted user information with a private key and comparing it with patient information on the EMR server; and
delivering a reception result based on a result of comparing the decrypted user information to the user terminal through a mobile callback server;
Characterized in that it includes,
Non-face-to-face hospital treatment registration method using wireless communication.
According to clause 9,
The wireless communication includes one or more of Near Field Communication (NFC), Radio-Frequency Identification (RFID), Bluetooth, and Bluetooth Low Energy (BLE).
Non-face-to-face hospital treatment registration method using wireless communication.
As a user terminal,
One or more processors;
a memory coupled to the one or more processors; and
a communication module connected to the one or more processors;
Including,
Computer-readable instructions are stored in the memory,
When the instructions are executed by the one or more processors, the method of any one of claims 5 to 8 is performed,
User terminal.
As a hospital reception terminal,
One or more processors; and
a memory coupled to the one or more processors; and
a communication device coupled to the one or more processors;
Including,
Computer-readable instructions are stored in the memory,
When the instructions are executed by the one or more processors, the method of claim 9 or 10 is performed,
Hospital reception terminal.
According to clause 12,
The communication device is a BLE (Bluetooth Low Energy) communication device,
Hospital reception terminal.