KR20240013311A - Robot delivery system based on authenticated user and electronic medical record and method therefor - Google Patents

Abstract

The present invention relates to a delivery method in a robotic delivery system based on an authenticated user and an electronic medical record (EMR). Because,
A user authentication server performing user authentication and transmitting hardware identification information of the user terminal to the service server; A service server establishing a connection to a user terminal and receiving delivery information; If the delivery information relates to medications, verifying whether the medications have moved by comparing them to electronic medical records; Instructing the robot to deliver; and updating the electronic medical record once delivery is complete.

Description

ROBOT DELIVERY SYSTEM BASED ON AUTHENTICATED USER AND ELECTRONIC MEDICAL RECORD AND METHOD THEREFOR}

The present invention relates to a robot delivery system and its delivery method, and more specifically, to a robot delivery system and its delivery method based on an authenticated user and electronic medical record.

Recently, with the development of medical services, specialized medical centers that are separated from the increasingly large general hospitals and provide their own specialized medical services are being actively opened.

In particular, active customer response medical services such as health checkup centers are established and operated in areas that are easily accessible to customers, and a significant portion of the medical services at the branched health checkup centers are based on each customer's hospital medical information. There are many cases where this is done, but hospital medical information is data that requires security, and there was a problem in delivery through robots in that the robots could not store the data.

Republic of Korea Patent Publication No. 10-0935710 (announced on January 7, 2010) Republic of Korea Patent Publication 91-2360651 (announced on February 10, 2022)

Based on the above-described discussion, the present invention seeks to provide a delivery method in a robot delivery system based on an authenticated user and an electronic medical record (EMR).

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

In a delivery method in a robot delivery system based on an authenticated user and an electronic medical record (EMR), which is an aspect of the present invention to solve the above-described problem, a user authentication server delivers the robot from a user terminal. Receiving a user ID and password for accessing the system; The user authentication server performing user authentication for the user based on the user ID and the password and transmitting hardware identification information of the user terminal to the service server; The service server, when the hardware identification information of the user terminal is the same as hardware identification information pre-registered in the service server, allowing access to the hardware identification information of the user terminal; When the user terminal is granted access from the service server, the service server receives delivery information including at least one of a designated delivery time, delivery location, product information, designated patient information, or prescription drug information from the user terminal. step; The service server, when the delivery information includes designated patient information and prescription drug information, checking whether there is an abnormality in the medication based on the electronic medical record (EMR) for the designated patient; The service server, when the delivery information includes designated patient information, adding patient location information for the designated patient to the delivery information based on the patient management server; The service server transmits the delivery information to a robot; setting, by the robot, delivery list information based on the delivery information; transmitting, by the robot, the set delivery list information to the user terminal through the service server; The user terminal receiving confirmation of the delivery list information from the authenticated user and transmitting delivery start to the robot through the service server; The service server monitoring delivery through the robot; And when the robot completes delivery and the delivery information includes designated patient information, updating the electronic medical record (EMR) of the designated patient associated with the delivery information.

Furthermore, the step of checking whether there is an abnormality in the type of medicine includes: checking, by the service server, information on medicines already prescribed within a preset period recorded in an electronic medical record (EMR) for the designated patient information; The service server, if the prescribed drug information and prescription drug information are different, sending a confirmation request to the user terminal; When the service server receives normal confirmation of the medicine from the user terminal, storing it in the delivery information; And when the service server receives confirmation of a medication abnormality from the user terminal, receiving re-prescribed medication information from the user terminal and storing the received re-prescribed medication information in the delivery information. can do.

Furthermore, adding patient location information about the designated patient to the delivery information includes: the service server requesting hospitalization information about the designated patient from the patient management server; and the service server receiving hospitalization information for the designated patient from the patient management server and adding 3D map information to the delivery information based on the received hospitalization information.

Furthermore, setting the delivery list information includes setting a shortest route based on the delivery location on the delivery information and setting an expected delivery time; When a difference between the delivery designated time and the expected delivery time occurs that exceeds a preset time interval, transmitting a delivery list modification request including the delivery designated time and the expected delivery time to the user terminal; and receiving a delivery list modification response from the user terminal and setting it as the delivery list information.

Furthermore, monitoring the delivery may include the service server receiving an identification image of the designated patient from the robot; Authenticating, by the service server, whether the designated patient is the designated patient through the patient management server using the identification image; and, when the service server authenticates the designated patient based on the identification image, instructing the robot to perform delivery.

Furthermore, the service server receiving a temperature measurement order for the designated patient from the user terminal; The service server receiving an identification image of the designated patient from the robot; Authenticating, by the service server, whether the designated patient is the designated patient through the patient management server using the identification image; And characterized by further comprising the step of the service server instructing the robot to measure the body temperature of the designated patient.

According to an embodiment of the present invention, a robot delivery system and delivery method based on an authenticated user and electronic medical records can be provided.

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

1 is a flowchart for explaining the robot delivery method according to the present invention.
Figure 2 is a flowchart showing the steps in which a user terminal establishes a connection with a service server through a user authentication server according to the present invention.
Figure 3 is a flowchart showing the steps of the user terminal setting delivery information for robot delivery to the service server according to the present invention.
Figure 4 is a flowchart illustrating a process in which a robot performs delivery and a service server monitors the robot in the robot delivery system according to the present invention.

Additional objects, features and advantages of the present invention may be more clearly understood from the following detailed description and accompanying drawings.

Prior to a detailed description of the present invention, it should be noted that the present invention is capable of various modifications and may have various embodiments, and the examples described below and shown in the drawings are not intended to limit the present invention to specific embodiments. No, it should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present invention.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this specification are merely used to describe specific embodiments and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “comprise” or “have” are intended to indicate 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.

In addition, terms such as "... unit", "... unit", and "... module" used in the specification refer to a unit that processes at least one function or operation, which is hardware or software or hardware and It can be implemented through a combination of software.

In addition, when describing with reference to the accompanying drawings, identical components will be assigned the same reference numerals regardless of the reference numerals, and overlapping descriptions thereof will be omitted. In describing the present invention, if it is determined that a detailed description of related known technologies may unnecessarily obscure the gist of the present invention, the detailed description will be omitted.

1 is a flowchart for explaining the robot delivery method according to the present invention.

In the present invention, the process for robot delivery is largely carried out in three steps.

First, the user terminal first establishes a connection with the service server through the user authentication server (S101).

The user terminal sets delivery information for robot delivery to the service server (S103).

In the robot delivery system, the robot performs delivery, and the service server monitors the robot (S105).

Hereinafter, each step will be described in more detail with reference to FIGS. 2 to 4.

Figure 2 is a flowchart showing steps in which a user terminal establishes a connection with a service server through a user authentication server according to the present invention.

In a medical environment system where multiple patients are hospitalized or receiving treatment, if records such as the patient's condition or personal information are viewed or changed by someone else, it may lead to a medical accident. Therefore, unauthorized users should not access medical environment systems such as hospitals, and for this purpose, only user authentication and designated users should be able to access and modify patient data.

Accordingly, in the present invention, the user terminal accesses the service server after being authenticated through a user authentication server separate from the service server, thereby blocking direct access to the service server by any user.

The user authentication server receives a user ID and password for accessing the robot delivery system from the user terminal (S201).

The user authentication server checks whether the user ID and password match the information of an already registered user (S203). The user authentication server can check whether the user is an appropriate user by comparing the user ID and password with pre-stored user information.

If the user ID and password match the already registered user information, the user authentication server obtains the hardware identification information of the user terminal and transmits the obtained hardware identification information of the user terminal to the service server (S205).

Here, the hardware identification information may be a MAC address (Media Access Control Address) or UDID (Unique Device Identifier).

The reason that the hardware identification information of the user terminal is transmitted to the service server rather than the user ID and password in the present invention is that, unlike other systems, medical environment systems have a low possibility of working from home or remotely, and medical environment systems (e.g. hospitals) ), there is a high possibility of connection from a fixed terminal (e.g., computer), and there is a possibility that the user ID and password may be leaked to the outside, but the hardware identification information of the user terminal on a closed network such as a medical environment system may be exposed to the outside. This is because the possibility of leakage is relatively low.

If a user who has entered the same user ID and password already exists, the user authentication server may transmit the existing hardware identification information to the service server along with new hardware identification information.

The service server checks whether the hardware identification information of the user terminal matches the hardware identification information previously registered in the service server (S207)

The service server allows access to the hardware identification information of the user terminal when the hardware identification information of the user terminal is the same as the hardware identification information previously registered in the service server (S209). In other words, the service server receives the hardware identification information of the user terminal for which user authentication has been performed based on the user ID and password from the user authentication server, and determines whether the received hardware identification information is the same as the hardware identification information previously registered in the service server. judge. If the user authentication server transmits existing hardware identification information and new hardware identification information together, it checks whether there is a connected user terminal corresponding to the existing hardware identification information, and confirms whether there is a user terminal connected to the existing hardware identification information. The connection can be terminated.

Additionally, the service server may allow limited access to specific user terminals. For example, by setting an input time limit, you can terminate the connection if a specific user terminal is left defenseless, and by restricting application access rights, you can prevent access to data areas not related to the authenticated user. You can.

To allow access, the service server may transmit access permission information to the user terminal through the user authentication server. Access permission information may be routing information related to the service server. That is, in the present invention, the user terminal can access the user authentication server, but the access path (eg, routing information) to the service server configured separately from the user authentication server can be configured not to be known. Accordingly, since the service server is hidden from the user terminal on the network, it is possible to prevent the service server from being directly exposed to risks such as hacking. In this case, since the user terminal cannot access the service server, the service server can allow the user terminal to directly access the service server by transmitting access permission information to the user terminal.

When the user terminal receives access permission information from the service server, it establishes a connection with the service server using the received access permission information (S211)

Figure 3 is a flowchart showing the steps of the user terminal setting delivery information for robot delivery to the service server according to the present invention.

When the user terminal is granted access from the service server, the service server establishes a connection with the user terminal, and receives at least one of the designated delivery time, delivery location, product information, designated patient information, or prescription drug information from the user terminal with which the connection is established. Receive shipping information including (S301).

Here, the service server can receive and store delivery information received from the user terminal through a specific application, and the specific application can be used by the service server based on authenticated user information (e.g., user ID) and hardware identification information of the user terminal. You can also set limited access rights.

The service server checks whether the delivery is related to medicine based on the delivery information (S303). In the medical environment system, unlike general products, there is a high possibility that major problems will occur in the case of incorrect delivery of medicines prescribed to specific patients, and legal problems may arise if medicines whose prescription is restricted are delivered to a third party. It is necessary to perform additional verification procedures.

If the delivery information includes designated patient information and prescription drug information, the service server checks whether there is an abnormality in the drug based on the electronic medical record (EMR) for the designated patient (S305).

The service server first checks information on medications already prescribed within a preset period recorded in an electronic medical record (EMR) database (not shown) for designated patient information. Here, the preset period has the information on medicines prescribed after hospitalization as the basic period, but if the date on which a new prescription from the medical staff was prescribed exceeds 3 days, it is desirable to use the date on which the new prescription was prescribed as the standard. . Checking information on previously prescribed medicines is to check whether the newly prescribed medicine was misprescribed if it is different from the previously prescribed medicine information, and new prescriptions exceeding 3 days can be trusted.

The service server sends a confirmation request to the user terminal when the already prescribed drug information and the prescribed drug information are different. The user terminal can display to the user that the already prescribed drug information is different from the prescribed drug information, and receive confirmation from the user whether the prescribed drug information is correct.

When confirmation of normal medicine is received from the user terminal, the service server stores prescription medicine information in delivery information. Conversely, when confirmation of a medication abnormality is received from the user terminal, the service server receives re-prescription medication information from the user terminal and stores the received re-prescription medication information in delivery information.

When the delivery information is a medicine-related delivery and includes designated patient information, the service server adds patient location information for the designated patient to the delivery information based on the patient management server (S307).

The service server requests hospitalization information for the designated patient from the patient management server (not shown). Since the designated patient's hospitalization information is personal information, it needs to be stored on a separate server, and the service server separately accesses the patient management server that stores the hospitalization information to obtain the hospitalization information.

The hospitalization information stored by the patient management server includes not only the patient identification number for the designated patient, but also the ward, room, and location within the room where the patient identification number was admitted. The robot's movement is based on SLAM (Simultaneous Localization and Mapping), which requires information about a specific location to be set in advance. Accordingly, the patient management server transmits hospitalization information mapping the patient's ward, room, and location within the hospital room to 3D map information to the service server.

Accordingly, the service server receives hospitalization information about the designated patient from the patient management server, and adds 3D map information about the designated patient to the delivery information based on the received hospitalization information.

The service server transmits delivery information to the robot (S309).

The robot compares the received delivery information with the already received delivery information and sets delivery list information (S311).

The robot sets the shortest route based on the delivery location in the delivery information and sets the estimated delivery time.

If there is a difference between the specified delivery time and the expected delivery time that exceeds the preset time interval, a request to modify the delivery list including the specified delivery time and the expected delivery time is sent to the user terminal.

The user terminal receives a response to the user's request to modify the delivery list and transmits it to the robot. Accordingly, the robot receives a delivery list modification response from the user terminal and sets it as delivery list information.

The robot transmits a request to confirm delivery list information for the delivery list information set through the service server to the user terminal (S313).

The user terminal receives a delivery list information confirmation response from the authenticated user and transmits the delivery list information confirmation response and delivery instruction to the robot through the service server (S315).

Figure 4 is a reference diagram for explaining a process in which a robot performs delivery and a service server monitors the robot in the robot delivery system according to the present invention.

The robot performs delivery (S401). Since the present invention is not simply delivering goods through a robot, but rather delivering medicines to a designated patient, the service server needs to identify whether the robot is a designated patient and deliver the goods or medicines based on this. there is.

The robot once again confirms whether the patient is a designated patient through the designated patient's terminal (e.g., mobile phone, smartphone) or a band displaying an identification image issued for the designated patient. Here, the identification image can be a QR code or a barcode, and when the patient is hospitalized, the identification image can be transmitted to the terminal to the designated patient through the patient management server, or printed on a separate band and provided to the user.

Since the robot does not store the designated patient's identification image as data, the identification image captured through the designated patient's terminal or identification image display band is transmitted to the service server.

The service server receives the identification image of the designated patient from the robot and transmits the received identification image of the designated patient to the patient management server.

The patient management server extracts patient identification information from the received identification image of the designated patient, and authenticates the patient based on the extracted identification information recorded in the patient management server at the time of hospitalization.

When the service server is authenticated as a designated patient through the patient management server using an identification image, it delivers medicine or delivery goods to the designated patient.

The service server monitors the process of the robot delivering medicine or delivery goods to a designated patient, and monitors and records information such as delivery time, delivery goods, and recipient (S403).

If so, the service server can receive an order to measure the temperature of a designated patient from the user terminal. When receiving a body temperature measurement order, the service server may perform a process of measuring body temperature in addition to the process of delivering goods or medicine to the designated patient.

That is, the service server receives the identification image of the designated patient from the robot and delivers the received identification image to the patient management server.

The service server is authenticated as a designated patient through the patient management server using an identification image.

If the identification image matches the designated patient, the service server instructs the robot to measure the temperature of the designated patient.

When the robot receives an instruction regarding body temperature measurement from the service server, it measures the body temperature of the designated patient (S405).

The robot measures the body temperature of the designated patient and transmits the measurement time and measurement results to the service server.

When the robot completes delivery and the delivery information includes the designated patient information, the service server updates the electronic medical record (EMR) of the designated patient associated with the delivery information (S407). In other words, the service server can update the electronic medical record by recording and storing the medicine delivery time, medicine delivery type, measured body temperature, etc. for the designated patient in the electronic medical record.

The embodiments described in this specification and the accompanying drawings merely illustratively illustrate some of the technical ideas included in the present invention. Accordingly, the embodiments disclosed in this specification are not intended to limit the technical idea of the present invention, but rather to explain it, and therefore, it is obvious that the scope of the technical idea of the present invention is not limited by these examples. All modifications and specific embodiments that can be easily inferred by a person skilled in the art within the scope of the technical idea included in the specification and drawings of the present invention should be construed as being included in the scope of the present invention.

Claims (6)

In the delivery method in a robot delivery system based on an authenticated user and an electronic medical record (EMR),
A user authentication server receiving a user ID and password for accessing the robot delivery system from a user terminal;
The user authentication server performing user authentication for the user based on the user ID and the password and transmitting hardware identification information of the user terminal to the service server;
The service server, when the hardware identification information of the user terminal is the same as hardware identification information pre-registered in the service server, allowing access to the hardware identification information of the user terminal;
The service server establishes a connection with the user terminal to which access is permitted, and receiving delivery information including at least one of a designated delivery time, delivery location, product information, designated patient information, and prescription drug information from the user terminal. ;
The service server, when the delivery information includes designated patient information and prescription drug information, checking whether there is an abnormality in the medication based on the electronic medical record (EMR) for the designated patient;
The service server, when the delivery information includes designated patient information, adding patient location information for the designated patient to the delivery information based on the patient management server;
The service server transmits the delivery information to a robot;
setting, by the robot, delivery list information based on the delivery information;
transmitting, by the robot, a delivery list information confirmation request for the set delivery list information to the user terminal through the service server;
The user terminal receiving a delivery list information confirmation response from the authenticated user, and transmitting the delivery list information confirmation response and delivery instructions to the robot through the service server;
the robot performing delivery;
Monitoring the robot by the service server; and
Including, by the service server, when the robot completes delivery and the delivery information includes designated patient information, updating the electronic medical record (EMR) of the designated patient associated with the delivery information.
Delivery method in robotic delivery system.
According to claim 1,
The step of checking whether there is an abnormality in the type of medicine is,
The service server includes checking information on previously prescribed medicines within a preset period recorded in an electronic medical record (EMR) for the designated patient information;
The service server, if the prescribed drug information and prescription drug information are different, sending a confirmation request to the user terminal;
When the service server receives confirmation of normal medicine from the user terminal, storing the prescription medicine information in the delivery information; and
When the service server receives confirmation of a medication abnormality from the user terminal, the service server receives re-prescribed medication information from the user terminal, and storing the received re-prescribed medication information in the delivery information. ,
Delivery method in robotic delivery system.
According to claim 1,
The step of adding patient location information for the designated patient to the delivery information,
The service server requesting hospitalization information for the designated patient from the patient management server; and
The service server receiving hospitalization information about the designated patient from the patient management server, and adding 3D map information about the designated patient to the delivery information based on the received hospitalization information. doing,
Delivery method in robotic delivery system.
According to claim 1,
The step of setting the delivery list information is,
Setting, by the robot, the shortest route based on the delivery location on the delivery information and setting an expected delivery time;
If a difference between the specified delivery time and the expected delivery time occurs that exceeds a preset time interval, the robot transmits a delivery list modification request including the specified delivery time and the expected delivery time to the user terminal. ; and
The robot includes receiving a delivery list modification response from the user terminal and setting it as the delivery list information,
Delivery method in robotic delivery system.
According to claim 1,
The steps for performing the delivery are:
The service server receiving an identification image of the designated patient from the robot;
Authenticating, by the service server, whether the designated patient is the designated patient through the patient management server using the identification image; and
When the service server authenticates the designated patient through the patient management server, instructing the robot to perform delivery,
Delivery method in robotic delivery system.
According to claim 1,
The service server receiving a temperature measurement order for the designated patient from the user terminal;
The service server receiving an identification image of the designated patient from the robot;
Authenticating, by the service server, whether the designated patient is the designated patient through the patient management server using the identification image; and
When the designated patient is authenticated, the service server instructs the robot to measure the body temperature of the designated patient, further comprising:
Delivery method in robotic delivery system.

Images