KR102588743B1 - Method for providing medical document and system thereof - Google Patents

Abstract

One embodiment relates to a method and system for providing medical documentation.

Description

Medical document provision method and system {METHOD FOR PROVIDING MEDICAL DOCUMENT AND SYSTEM THEREOF}

The embodiments below relate to a method and system for providing medical documents.

In general, patients directly visit a medical institution (hospital) to receive treatment and treatment, and the medical institution stores medical information about the patient's diagnosis, treatment history/disease name/results, etc. in the form of files or documents. Nowadays, most people use personal computers and servers to store medical documents in file format.

Patients will receive an oral explanation from their doctor about their diagnosis results, disease name, and treatment methods if treatment is needed. At this time, they can apply for and receive a medical certificate or necessary medical documents related to treatment.

Patients are frequently issued medical documents for various reasons, such as submitting medical documents to a company, attaching them when filling out an insurance claim, or losing the issued medical documents. In this case, the patient either directly visits the medical institution where his or her medical documents are stored (for example, a hospital where previous diagnosis and treatment was performed) and obtains the medical documents, or accesses the medical institution through the Internet and obtains a general-purpose public certificate. After performing authentication on the hospital website, it is issued through the terminal.

However, when a user directly visits a medical institution to obtain a medical document, there is a disadvantage in that time and cost are incurred due to the visit to the medical institution.

Accordingly, the need for users to easily receive the medical documents they want at the desired location is growing.

The matters described in this background art section are written to improve understanding of the background of the invention, and may include matters that are not prior art already known to those skilled in the art in the field to which this technology belongs.

The following embodiments were designed to solve the above-mentioned problems, and one embodiment aims to provide a method and system that can provide necessary medical documents with a simple operation by the user.

The problems to be solved by one embodiment are not limited to the problems mentioned above, and other problems not mentioned can be clearly understood by those skilled in the art from the description below.

One embodiment is a method of providing medical documents performed in an app server, comprising: receiving an access URL from a user terminal connected using the access URL; Analyzing the access URL and extracting hospital information and user information; providing a medical document providing interface to the user terminal; Receiving an output code from the user terminal; Analyzing the output code to identify an output device through which a user will output a medical document; And transmitting an output device control signal to a hospital server or pharmacy server to which the identified output device is connected, wherein the output device control signal includes identification information of the output device, identification information of the user, and type of the medical document. , a method of providing a medical document including at least one of the number of outputs, an output format, and output data of the medical document.

The access URL is path information through which the user terminal can access the app server, and includes the hospital information and the user information, and the user information is a patient registration number.

The output code is an identification code of the output device and is configured to be attached to the output device.

When the identified output device is an output device connected to the pharmacy server, receiving output data of the medical document from the hospital server.

Receiving an insurance claim request signal from the user terminal; and transmitting the received insurance claim request signal to the hospital server.

One embodiment is an app server that performs a method of providing medical documents, comprising: a communication unit configured to receive the access URL from a user terminal connected using the access URL and receive an output code from the user terminal; an interface providing unit configured to provide a medical document providing interface to the user terminal; an access URL analysis unit configured to analyze the access URL and extract hospital information and user information; an output code analysis unit configured to analyze the output code to identify an output device through which a user will output a medical document; and an output device control configured to generate the output device control signal including at least one of identification information of the output device, identification information of the user, type of the medical document, number of outputs, output format, and output data of the medical document. It includes a signal generator, and the communication unit provides an app server configured to generate the output device control signal to a hospital server or pharmacy server to which the identified output device is connected.

The access URL is path information through which the user terminal can access the app server, and includes the hospital information and the user information, and the user information is a patient registration number.

The output code is an identification code of the output device and is configured to be attached to the output device.

When the identified output device is an output device connected to the pharmacy server, receiving output data of the medical document from the hospital server.

The communication unit is configured to receive an insurance claim request signal from the user terminal and transmit the received insurance claim request signal to the hospital server.

One embodiment is a method of providing medical documents performed in an app server, comprising: receiving an access URL from a user terminal connected using the access URL; Analyzing the access URL and extracting hospital information and user information; providing a medical document providing interface to the user terminal; Receiving an output code from the user terminal; An operation of transmitting the output code to a hospital server or pharmacy server, wherein the output code includes identification information of the output device, identification information of the user, type of medical document, number of outputs, output format, and output data of the medical document. Provides a method of providing medical documents containing at least one of the following:

One embodiment is an app server that performs a method of providing medical documents, comprising: a communication unit configured to receive the access URL from a user terminal connected using the access URL and receive an output code from the user terminal; an interface providing unit configured to provide a medical document providing interface to the user terminal; and a connection URL analysis unit configured to analyze the connection URL and extract hospital information and user information, wherein the communication unit transmits identification information of the output device to the hospital server or pharmacy server, identification information of the user, type of medical document, A server configured to transmit the output code including at least one of the number of outputs, an output format, and output data of the medical document is provided.

According to the embodiments described above, a user can output necessary medical documents from a desired output device with a simple operation such as recognizing an output code.

And, according to one embodiment, a user can easily submit an insurance claim to the insurance company.

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

1 is a diagram illustrating the configuration of a medical document providing system according to an embodiment.
Figure 2 is a diagram illustrating the configuration of an app server according to an embodiment.
Figure 3 is a diagram illustrating the configuration of a hospital server according to an embodiment.
Figure 4 is a diagram illustrating the configuration of a pharmacy server according to an embodiment.
Figure 5 is a diagram illustrating the configuration of a user terminal according to an embodiment.
Figure 6 is a flowchart of a method for generating a connection URL according to an embodiment.
Figure 7 is a flowchart of a medical document output method according to the first embodiment.
Figure 8 is a flowchart of a medical document output method according to a second embodiment.
Figure 9 is a flowchart of a method for providing an insurance claim according to an embodiment.
Figure 10 is a diagram illustrating data flow within a medical document provision system according to an embodiment.

Hereinafter, embodiments will be described in detail with reference to the attached drawings. The same reference numerals in each drawing indicate the same members. Various changes may be made to the embodiments described below. The embodiments described below are not intended to limit the embodiments, but should be understood to include all changes, equivalents, and substitutes therefor.

Terms used in the examples are merely used to describe specific examples and are not intended to limit the examples. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “include” or “have” are intended to designate the presence of features, numbers, operations, movements, 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 it does not exclude in advance the possibility of the existence or addition of elements, numbers, actions, actions, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which the embodiments belong. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

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 embodiments, if it is determined that detailed descriptions of related known technologies may unnecessarily obscure the gist of the embodiments, the detailed descriptions are omitted.

FIG. 1 is a diagram illustrating the configuration of a medical document providing system 10 according to an embodiment.

Referring to FIG. 1, the medical document providing system 10 according to an embodiment includes an app server 100, a user terminal 200, a hospital server 300, a hospital gateway 302, a pharmacy server 400, and a pharmacy. Includes a gateway 402 and an insurance company server 500.

Communication between various entities included in the medical document providing system 10 may be performed through a wired/wireless network (not shown). Wired/wireless networks may use standard communication technologies and/or protocols.

The medical document providing system 10 may be composed of various types of networks. For example, the medical document provision system 10 may be configured as a virtual private network (VPN), which is a private network. Additionally, the medical document provision system 10 may be configured as a network using IP Protocol.

The app server 100, hospital server 300, hospital gateway 302, pharmacy server 400, pharmacy gateway 402, and insurance company server 500 are, for example, computers, UMPCs (Ultra Mobile PCs), and workstations. Stations, net-books, PDAs (Personal Digital Assistants), portable computers, web tablets, wireless phones, mobile phones, smart phones, It is one of electronic devices such as a portable multimedia player (PMP), and may include any electronic device capable of installing and executing an application related to an embodiment. The electronic device can perform overall service operations, such as configuring a service screen, inputting data, transmitting and receiving data, and storing data, under the control of an application.

The app server 100 creates a connection URL.

The access URL of one embodiment is path information through which the user terminal 200 can access the app server 100, and the access URL includes hospital information and user information.

The app server 100 generates a connection URL using the hospital information and user information received from the hospital server 300 and transmits the generated connection URL to the hospital server 300.

The app server 100 receives a connection URL from the user terminal 200.

The app server 100 analyzes the access URL and extracts hospital information and user information.

The app server 100 uses the extracted hospital information and user information to provide a medical document providing interface that can receive user commands to the user terminal 200 connected through the access URL. The user may recognize an output code or input a user command, such as a medical document output request or an insurance bill request, through the medical document provision interface output on the user terminal 200. Additionally, the user can input data related to medical document output, such as the number of prints and output format, through the medical document provision interface.

The app server 100 receives an output code from the user terminal 200.

The output code in one embodiment is an identification code of the output devices 301 and 401. The output code may be implemented as a various type of code. For example, the output code may be implemented as a barcode or QR code. The output code is attached to the output device (301, 401), and the user can recognize the output code attached to the output device (301, 401) through the camera of the user terminal (200). The user terminal 200 transmits the recognized output code to the app server 100.

The app server 100 analyzes the output code and identifies the output devices 301 and 401 through which the user will output the medical document.

Medical documents in one embodiment are various medical documents issued to users by hospitals and may include, for example, prescriptions, doctor's opinions, medical receipts, etc.

If the identified output device is the hospital output device 301, the app server 100 generates an output device control signal and transmits it to the hospital server 300.

The output device control signal of one embodiment includes at least one of identification information of the output devices 301 and 401, user identification information, type of medical document to be output, user identification information, number of outputs, and output format.

In another embodiment, the app server 100 may transmit an output code to the hospital server 300 and analyze the output code received from the hospital server 300.

When the output device is the pharmacy output device 401, the app server 100 transmits an output data request signal to the hospital server 300. The output data of one embodiment is data of a medical document that the user wants to print, and may include data such as a prescription, a doctor's opinion, and a medical receipt.

The app server 100 uses the output data received from the hospital server 300 to generate an output device control signal and transmits the generated output device control signal to the pharmacy server 400. At this time, the output device control signal of one embodiment may further include output data.

In another embodiment, the app server 100 may transmit an output code to the pharmacy server 400 and analyze the output code received from the pharmacy server 400.

When the app server 100 receives an insurance claim request signal from the user terminal 200, it transmits the insurance claim request signal to the hospital server 300.

The configuration and function of the app server 100 will be described in detail in FIG. 3 below.

The user terminal 200 connects to the app server 100 using the access URL received from the hospital server 300 and transmits the access URL to the app server 100.

The user terminal 200 outputs a medical document provision interface provided from the app server 100 to the user, and may receive various commands and data from the user through the medical document provision interface.

The user terminal 200 can recognize the output code attached to the output devices 301 and 401 through the camera. The user terminal 200 transmits the recognized output code to the app server 100.

When the user's insurance claim command is received through the medical document providing interface, the user terminal 200 generates an insurance claim request signal and transmits it to the app server 100.

The detailed configuration and functions of the user terminal 200 will be described in detail in FIG. 6 below.

The hospital server 300 is a server installed in a hospital and performs a method of providing medical documents according to an embodiment. The hospital server 300 is wired/wireless connected to at least one hospital gateway 302 and a hospital output device 301. do.

The hospital gateway 302 is configured to allow the hospital server 300 to communicate data with external devices.

The hospital server 300 transmits hospital information and user information to the app server 100, allowing the app server 100 to create a connection URL.

The hospital server 300 receives the connection URL from the app server 100 and transmits it to the user terminal 200.

As described above, the access URL of one embodiment is path information through which the user terminal 200 can access the app server 100, and the access URL includes hospital information and user information.

If the user is a patient visiting the hospital for the first time, that is, if it is the patient's first visit, the hospital server 300 may receive user information input from the user.

When the hospital server 300 receives an output device control signal or output code from the app server 100, it identifies the hospital output device 301 by analyzing the output device control signal or output code.

The hospital server 300 controls the identified hospital output device 301 so that the hospital output device 301 outputs the medical document included in the output device control signal or output code. Additionally, the hospital server 300 may control the hospital output device 301 to output medical documents according to the number of outputs or output format included in the output device control signal or output code.

When the hospital server 300 receives an output data request signal from the app server 100, it generates output data and transmits it to the app server 100.

When the hospital server 300 receives an insurance claim request signal from the app server 100, it generates an insurance claim and transmits it to the insurance company server 500.

The pharmacy server 400 is a server installed in a pharmacy and performs a method of providing medical documents according to an embodiment. The pharmacy server 400 is wired/wireless connected to at least one pharmacy gateway 402 and a pharmacy output device 401. do.

The pharmacy gateway 402 is configured to allow the pharmacy server 400 to communicate data with an external device.

When the pharmacy server 400 receives an output device control signal or output code from the app server 100, it identifies the pharmacy output device 401 by analyzing the output device control signal or output code.

The pharmacy server 400 controls the identified pharmacy output device 401 to cause the pharmacy output device 401 to output output data included in the output device control signal or output code. Additionally, the pharmacy server 400 may control the pharmacy output device 401 to output output data according to the number of outputs or output format included in the output device control signal or output code.

The insurance company server 500 is a server installed within an insurance company. The insurance company server 500 receives an insurance bill from the hospital server 300 and performs the task of paying insurance money to the user according to the insurance bill.

FIG. 2 is a diagram illustrating the configuration of the app server 100 according to an embodiment.

Referring to Figure 2, in one embodiment, the app server 100 includes a control unit 110, a connection URL analysis unit 120, an output code analysis unit 130, an output device control signal generation unit 140, and an insurance claim request. It includes a unit 150, an interface providing unit 160, a database unit 170, a communication unit 180, and a connection URL generating unit 190.

The hardware configuration of the app server 100 may be implemented in various ways. The hardware can be configured by integrating the access URL analysis unit 120 and the output code analysis unit 130, or by integrating the output device control signal generation unit 140 and the interface provision unit 160. As such, the hardware configuration of the app server 100 is not limited to what is described in this specification, and may be implemented in various methods and combinations.

The control unit 110 includes a connection URL analysis unit 120, an output code analysis unit 130, an output device control signal generation unit 140, an insurance claim request unit 150, to perform various functions of the app server 100. Controls the interface providing unit 160, database unit 170, communication unit 180, and access URL generating unit 190.

In addition, the control unit 110 may also be called a processor, controller, microcontroller, microprocessor, microcomputer, etc., and the control unit may be hardware or firmware. It can be implemented by (firmware), software, or a combination of these.

The access URL analysis unit 120 analyzes the access URL received from the user terminal 200 and extracts hospital information and user information.

As described above, the access URL of one embodiment is path information through which the user terminal 200 can access the app server 100, and the access URL includes hospital information and user information. Here, the user information may be a patient registration number.

The output code analysis unit 130 analyzes the output code received from the user terminal 200 and identifies the output devices 301 and 401 through which the user will output the medical document.

As described above, the output code in one embodiment is an identification code of the output devices 301 and 401. The output code may be implemented as a various type of code. For example, the output code may be implemented as a barcode or QR code. The output code is attached to the output device (301, 401), and the user can recognize the output code attached to the output device (301, 401) through the camera of the user terminal (200). The user terminal 200 transmits the recognized output code to the app server 100.

The output device control signal generator 140 generates an output device control signal.

When the output device identified by the output code analysis unit 130 is the hospital output device 301, the output device control signal generator 140 generates the identification information of the hospital output device 301, the user's identification information, and the output device. Generates an output device control signal including at least one of the type, number of outputs, and output format of the medical document.

If the output device identified by the output code analysis unit 130 is the pharmacy output device 401, the output device control signal generator 140 transmits an output data request signal to the hospital server 300, and sends the output data request signal to the hospital server ( Receive output data from 300). The output device control signal generator 140 provides an output device control signal including at least one of identification information of the pharmacy output device 401, user identification information, type of medical document to be output, number of outputs, output format, and output data. creates .

The output device control signal generator 140 may determine the type, number of outputs, and output format of the medical document to be output using information input by the user through the user terminal 200.

When the insurance claim request unit 150 receives an insurance claim request signal from the user terminal 200, it transmits the insurance claim request signal to the hospital server 300.

The interface providing unit 160 uses the hospital information and user information extracted from the access URL analysis unit 120 to provide a medical document providing interface that can receive user commands to the user terminal 200 connected through the access URL. to provide.

The user may recognize an output code or input a user command, such as a medical document output request or an insurance bill request, through the medical document provision interface output from the user terminal 200. Additionally, the user can input data related to medical document output, such as the number of prints and output format, through the medical document provision interface.

The database unit 170 stores various data necessary for the app server 100 to implement an embodiment. For example, the database unit 170 may store access URL, output code, hospital information, etc.

The communication unit 180 communicates data with external devices. For example, the communication unit 180 may receive a connection URL and output code from the user terminal 200 and transmit a user interface to the user terminal 200. Additionally, the communication unit 180 may receive output data from the hospital server 300 and transmit an output device control signal or output code to the hospital server 300 and the pharmacy server 400.

Figure 3 is a diagram showing the configuration of the hospital server 300 according to one embodiment.

Referring to FIG. 3, in one embodiment, the hospital server 300 includes a hospital control unit 310, a connection URL request unit 320, an output data generator 330, an insurance claim generator 340, and an output device control unit ( 350), a user interface unit 360, a database unit 370, and a communication unit 380.

The hospital control unit 310 includes a connection URL request unit 320, an output data generator 330, an insurance claim generator 340, an output device control unit 350, and a user interface to perform various functions of the hospital server 300. Controls the unit 360, database unit 370, and communication unit 380.

The access URL request unit 320 transmits hospital information and user information to the app server 100, allowing the app server 100 to generate a access URL.

As described above, the access URL of one embodiment is path information through which the user terminal 200 can access the app server 100, for example, Internet access path information such as “https://m06qjtu0w6fq.hiwebnet.com”. It can be configured.

The access URL includes hospital information and user information, and the user information may be a patient registration number.

When the output data generator 330 receives an output data request signal from the app server 100, it generates output data.

When the insurance claim generating unit 340 receives an insurance claim request signal from the app server 100, it generates an insurance claim.

When the output device control unit 350 receives an output device control signal or output code from the app server 100, it analyzes the output device control signal or output code to identify the hospital output device 301.

The output device control unit 350 controls the identified hospital output device 301 so that the hospital output device 301 outputs the medical document included in the output device control signal or output code. Additionally, the output device control unit 350 may control the hospital output device 301 to output medical documents according to the number of outputs or output format included in the output device control signal or output code.

The user interface provider 360 provides an interface through which users can input data. For example, if the user is a patient visiting the hospital for the first time, that is, if it is the first visit, the user interface providing unit 360 may receive user information input from the user.

The database unit 370 stores various data necessary for the hospital server 300 to implement one embodiment. For example, the database unit 370 may store hospital information, user information, medical documents, output data, etc.

The communication unit 380 communicates data with external devices.

FIG. 4 is a diagram illustrating the configuration of a pharmacy server 400 according to an embodiment.

Referring to FIG. 4, in one embodiment, the pharmacy server 400 includes a pharmacy control unit 410, an output device control unit 420, a database unit 430, and a communication unit 440.

The pharmacy control unit 410 controls the output device control unit 420, the database unit 430, and the communication unit 440 to perform various functions of the pharmacy server 400.

When the output device control unit 420 receives an output device control signal from the app server 100, it identifies the pharmacy output device 401 by analyzing the output device control signal or output code.

The output device control unit 420 controls the identified pharmacy output device 401 so that the pharmacy output device 401 outputs output data included in the output device control signal or output code. Additionally, the output device control unit 420 may control the pharmacy output device 401 to output output data according to the number of outputs or output format included in the output device control signal or output code.

The database unit 430 stores various data necessary for the pharmacy server 400 to implement one embodiment, and the communication unit 440 communicates data with external devices.

FIG. 5 is a diagram illustrating the configuration of a user terminal 200 according to an embodiment.

Hereinafter, we will look at the components that make up the user terminal 200 shown in FIG. 5 in turn.

The wireless communication unit 210 may include one or more components that perform wireless communication between the user terminal 200 and the wireless communication system or wireless communication between the user terminal 200 and the network in which the user terminal 200 is located. . For example, the wireless communication unit 210 may include a broadcast reception module 211, a mobile communication module 212, a wireless Internet module 213, a short-range communication module 214, and a location information module 215. .

The broadcast reception module 211 receives broadcast signals and/or broadcast-related information from an external broadcast management server through a broadcast channel. Here, broadcast channels may include satellite channels and terrestrial channels. Meanwhile, broadcast-related information may also be provided through a mobile communication network, and in this case, it may be received by the mobile communication module 212.

Additionally, the mobile communication module 212 transmits and receives wireless signals with at least one of a base station, an external terminal, and a server on a mobile communication network. Here, the wireless signal may include various types of data according to voice call signals, video call signals, or text/multimedia message transmission and reception.

The wireless Internet module 213 refers to a module for wireless Internet access and may be built into or external to the user terminal 200.

The short-range communication module 214 refers to a module for short-range communication. As short-range communication technologies, Bluetooth, RFID (Radio Frequency Identification), infrared data association (IrDA), UWB (Ultra Wideband), ZigBee, etc. can be used.

Additionally, the location information module 215 is a module for confirming or obtaining the location of the user terminal 200. An example is a GPS (Global Position System) module. The GPS module receives location information from multiple satellites. Here, the location information may include coordinate information expressed in latitude and longitude.

Meanwhile, the A/V (Audio/Video) input unit 220 is for inputting audio signals or video signals, and may include a camera 221 and a microphone 222. The camera 221 processes image frames, such as still images or moving images, obtained by an image sensor in video call mode or shooting mode. And, the processed image frame can be displayed on the display unit 251.

Image frames processed by the camera 221 may be stored in the memory 260 or transmitted externally through the wireless communication unit 210. Two or more cameras 221 may be provided depending on the configuration of the user terminal 200.

Camera 221 can recognize output codes attached to output devices 301 and 401.

The microphone 222 receives external sound signals through a microphone in call mode, recording mode, voice recognition mode, etc., and processes them into electrical voice data. Additionally, the processed voice data can be converted into a form that can be transmitted to a mobile communication base station through the mobile communication module 212 and output when in call mode. The microphone 222 may implement various noise removal algorithms to remove noise generated in the process of receiving an external acoustic signal.

The user input unit 230 receives an input action from the user and generates input data for controlling the operation of the user terminal 200.

The sensing unit 240 detects the current state of the user terminal 200, such as the location of the user terminal 200, presence or absence of user contact, orientation of the user terminal 200, acceleration/deceleration of the user terminal 200, etc. Generates a sensing signal to control the operation of the terminal 200.

The interface unit 270 serves as an interface with all external devices connected to the user terminal 200. For example, wired/wireless headset ports, external charger ports, wired/wireless data ports, memory card ports, ports for connecting devices equipped with identification modules, audio I/O (Input/Output) ports, A video I/O (Input/Output) port, an earphone port, etc. may be included.

The output unit 250 is for outputting an audio signal, a video signal, or an alarm signal, and may include a display unit 251, an audio output module 252, an alarm unit 253, etc.

The display unit 251 displays and outputs information processed by the user terminal 200. For example, when the terminal is in call mode, it displays a user interface (UI) or graphic user interface (GUI) related to the call. And, when the user terminal 200 is in a video call mode or a shooting mode, the captured and/or received video, UI, or GUI is displayed.

Meanwhile, as described above, when the display unit 251 and the touch pad form a layered structure to form a touch screen, the display unit 251 can be used as an input device in addition to an output device. The display unit 251 includes a liquid crystal display, a thin film transistor-liquid crystal display, an organic light-emitting diode, a flexible display, and a three-dimensional display ( 3D display). And, depending on the implementation type of the user terminal 200, there may be two or more display units 251. For example, the user terminal 200 may be equipped with an external display unit (not shown) and an internal display unit (not shown) at the same time.

The audio output module 252 outputs audio data received from the wireless communication unit 210 or stored in the memory 260 in call signal reception, call mode or recording mode, voice recognition mode, broadcast reception mode, etc. Additionally, the sound output module 252 outputs sound signals related to functions performed in the user terminal 200 (eg, call signal reception sound, message reception sound, etc.). This sound output module 252 may include a speaker, buzzer, etc.

The alarm unit 253 outputs a signal to notify the occurrence of an event in the user terminal 200. Examples of events that occur in the terminal include receiving a call signal, receiving a message, and inputting a key signal.

The memory 260 may store programs for processing and controlling the control unit 280 and has a function for temporarily storing input/output data (e.g., phone book, messages, still images, videos, etc.). It can also be done.

The memory 260 is a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (for example, SD or XD memory, etc.), and RAM. (RAM, Random Access Memory) SRAM (Static Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory) magnetic memory, magnetic disk, It may include at least one type of storage medium among optical disks.

And the control unit 280 typically controls the overall operation of the terminal. For example, it performs related control and processing for voice calls, data communications, video calls, etc. Additionally, the control unit 280 may be equipped with a multimedia module 281 for multimedia playback. The multimedia module 281 may be implemented within the control unit 280 or may be implemented separately from the control unit 280.

The control unit 280 controls the wireless communication unit 210 to connect to the app server 100 according to the access URL received from the hospital server 300 and transmits the access URL to the app server 100.

The control unit 280 controls the display unit 251 to output the medical document provision interface received from the app server 100 to the user, and can receive various commands and data from the user through the medical document provision interface.

The control unit 280 controls the wireless communication unit 210 and transmits the output code recognized through the camera 221 to the app server 100.

When a user's insurance claim command is received through the medical document provision interface, the control unit 280 generates an insurance claim request signal and transmits it to the app server 100.

The power supply unit 290 receives external power and internal power under the control of the control unit 280 and supplies power necessary for the operation of each component.

Figure 6 is a flowchart of a method for generating a connection URL according to an embodiment.

Referring to FIG. 6, the method for generating a connection URL according to an embodiment is performed in the hospital server 300 and includes a check operation for the first visit (S100), a user information input operation (S110), a connection URL creation request operation (S120), It includes a connection URL reception operation (S130) and a connection URL transmission operation (S140).

First, in the first visit confirmation operation (S100), the hospital control unit 310 checks if the user is a patient visiting the hospital for the first time, that is, whether it is the first visit.

And, in the user information input operation S110, the hospital control unit 310 receives user information through the user interface provider 360 when the user is a first-time patient.

Then, in the connection URL creation request operation (S120), the connection URL request unit 320 transmits hospital information and user information to the app server 100, so that the app server 100 creates a connection URL.

As described above, the access URL of one embodiment is path information through which the user terminal 200 can access the app server 100, for example, Internet access path information such as “https://m06qjtu0w6fq.hiwebnet.com”. It can be configured. The access URL includes hospital information and user information, and the user information may be a patient registration number.

And, in the connection URL reception operation (S130), the hospital control unit 310 controls the communication unit 380 to receive the connection URL from the app server 100.

Then, in the connection URL transmission operation (S140), the hospital control unit 310 controls the communication unit 380 to transmit the received connection URL to the user terminal 200.

Figure 7 is a flowchart of a medical document output method according to the first embodiment.

The medical document output method according to the first embodiment is performed when the user recognizes the output code provided in the hospital output device 301 using the user terminal 200.

Referring to FIG. 7, the medical document output method according to the first embodiment is performed in the app server 100 and includes an output code reception operation (S200), an output code analysis operation (S210), and an output device control signal generation operation (S220). ) and an output device control signal transmission operation (S230).

First, in an output code reception operation (S200), the control unit 110 receives an output code from the user terminal 200 through the communication unit 180.

The output code of one embodiment is an identification code of the output devices 301 and 401, and the output code is implemented as various types of codes, such as barcodes or QR codes, and is attached to the output devices 301 and 401. The user can recognize the output code attached to the output devices 301 and 401 through the camera of the user terminal 200.

Then, in the output code analysis operation S210, the output code analysis unit 130 analyzes the received output code and identifies the hospital output device 301 through which the user will output the medical document.

And, in the output device control signal generation operation S220, the output device control signal generator 140 generates identification information of the hospital output device 301, user identification information, type of medical document to be output, number of outputs, and output. Generates an output device control signal containing at least one of the following forms: The output device control signal generator 140 may determine the type, number of outputs, and output format of the medical document to be output using information input by the user through the user terminal 200.

Then, in the output device control signal transmission operation S230, the control unit 110 transmits the generated output device control signal to the hospital server 300 through the communication unit 180.

As described above, the app server 100 may directly transmit the output code to the hospital server 300 without analyzing the output code received from the user terminal 200. In this case, the hospital server 300 may analyze the output code and output a medical document.

Figure 8 is a flowchart of a medical document output method according to a second embodiment.

The medical document output method according to the second embodiment is performed when the user recognizes the output code provided in the pharmacy output device 401 using the user terminal 200.

Referring to FIG. 8, the medical document output method according to the second embodiment is performed in the app server 100 and includes an output code reception operation (S300), an output code analysis operation (S310), and an output data request signal transmission operation (S320). ), an output data reception operation (S330), an output device control signal generation operation (S340), and an output device control signal transmission operation (S350).

First, in an output code reception operation (S300), the control unit 110 receives an output code from the user terminal 200 through the communication unit 180.

Then, in the output code analysis operation S310, the output code analysis unit 130 analyzes the received output code and identifies the pharmacy output device 401 through which the user will output the medical document.

Then, in the output data request signal transmission operation S320, the control unit 110 transmits the output data request signal to the hospital server 300 through the communication unit 180.

Then, in the output data reception operation S330, the control unit 110 receives output data from the hospital server 300 through the communication unit 180.

And, in the output device control signal generation operation S340, the output device control signal generator 140 generates identification information of the pharmacy output device 401, user identification information, type of medical document to be output, number of outputs, and output. Generates an output device control signal containing at least one of the form and output data. The output device control signal generator 140 may determine the type, number of outputs, and output format of the medical document to be output using information input by the user through the user terminal 200.

Then, in the output device control signal transmission operation S350, the control unit 110 transmits the generated output device control signal to the pharmacy server 400 through the communication unit 180.

As described above, the app server 100 may directly transmit the output code to the pharmacy server 400 without analyzing the output code received from the user terminal 200. In this case, the pharmacy server 400 may analyze the output code and output a medical document.

Figure 9 is a flowchart of a method for providing an insurance claim according to an embodiment.

Referring to FIG. 9, the method of providing an insurance claim according to an embodiment is performed in the app server 100 and the hospital server 300, and includes an operation of receiving an insurance claim request signal (S400) and an operation of transmitting an insurance claim request signal (S410). , including an insurance claim creation operation (S420) and an insurance claim transmission operation (S430).

First, in the insurance claim request signal reception operation S400, the insurance claim request unit 150 of the app server 100 receives an insurance claim request signal from the user terminal 200 through the communication unit 180.

Then, in the insurance claim request signal transmission operation S410, the insurance claim request unit 150 of the app server 100 transmits an insurance claim request signal to the hospital server 300 through the communication unit 180.

Then, in the insurance claim generation operation (S420), the insurance claim generation unit 340 of the hospital server 300 generates an insurance claim using the insurance claim data. Insurance claim data in one embodiment is data needed to create an insurance claim.

Then, in the insurance bill transmission operation S430, the insurance bill generation unit 340 of the hospital server 300 transmits the generated insurance bill to the insurance company server 500 through the communication unit 180.

Figure 10 is a diagram illustrating data flow within a medical document provision system according to an embodiment.

S10 in the drawing shows the data flow of a method for creating a connection URL according to an embodiment. The access URL generated in the app server 100 is transmitted to the user terminal 200 through the hospital server 300, and the user terminal 200 uses the access URL to access the app server 100, hospital information and The access URL including user information is transmitted to the app server 100.

S20 in the drawing shows the data flow of the medical document output method according to the first embodiment. When the user recognizes the output code provided in the hospital output device 301, the user terminal 200 transmits the output code to the app server 100. The app server 100 generates an output device control signal and transmits it to the hospital server 300, so that the hospital server 300 controls the hospital output device 301 to output medical documents.

S30 in the drawing shows the data flow of the medical document output method according to the second embodiment. When the user recognizes the output code provided in the pharmacy output device 401, the user terminal 200 transmits the output code to the app server 100. The app server 100 receives output data from the hospital server 300 and generates an output device control signal. The app server 100 transmits an output device control signal to the pharmacy server 400, allowing the pharmacy server 400 to control the pharmacy output device 401 to output medical documents (output data).

S40 in the drawing shows the data flow of the insurance claim provision method according to one embodiment. When the hospital server 300 receives an insurance claim request signal from the app server 100, it generates an insurance claim using the insurance claim data. The hospital server 300 transmits the insurance bill to the insurance company server 500, allowing the insurance company server 500 to perform the task of paying insurance money to the user according to the insurance bill.

Various embodiments described herein may be implemented in a computer-readable recording medium, for example, using software, hardware, or a combination thereof.

According to hardware implementation, the embodiments described herein include application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and field programmable gate arrays (FPGAs). , may be implemented using at least one of processors, controllers, micro-controllers, microprocessors, and electrical units for performing functions. In some cases, such embodiments may be implemented by the control unit 280.

According to software implementation, embodiments such as procedures or functions may be implemented with a separate software module that performs at least one function or operation. Software code can be implemented by a software application written in an appropriate programming language. Additionally, software code may be stored in the memory 260 and executed by the control unit 280.

The embodiments described above may be implemented with hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods and components described in the embodiments may include, for example, a processor, a controller, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), an ALU ( arithmetic logic unit, digital signal processor, microcomputer, field programmable gate array (FPGA), programmable logic unit (PLU), microprocessor, application specific integrated circuits (ASICS), or instructions ( Like any other device capable of executing and responding to instructions, it can be implemented using one or more general-purpose or special-purpose computers.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. -Includes optical media (magneto-optical media) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited drawings, various modifications and variations can be made by those skilled in the art from the above description. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent. Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the claims described below.

Claims (12)

A method of providing medical documents performed on an app server,
An operation of receiving the access URL from a user terminal connected using the access URL;
Analyzing the access URL and extracting hospital information and user information;
providing a medical document providing interface to the user terminal;
Receiving an output code from the user terminal;
Analyzing the output code to identify whether the output device through which the user will output the medical document is an output device within a hospital (hereinafter, hospital output device) or an output device within a pharmacy (hereinafter, pharmacy output device); and
Transmitting an output device control signal to a hospital server or pharmacy server,
The output device control signal transmission operation is,
If the identified output device is the hospital output device, the output device control signal containing identification information of the hospital output device, identification information of the user, type of medical document, number of outputs, and output format is sent to the hospital server. send,
When the identified output device is the pharmacy output device, an output data request signal is transmitted to the hospital server, and when the output data is received from the hospital server, the pharmacy server is sent the identification information of the pharmacy output device and the user's information. transmitting the output device control signal containing identification information, type of the medical document, number of outputs, output format, and the output data;
The output code is identification information of the hospital output device or identification information of the pharmacy output device, and is configured to be attached to the hospital output device or the pharmacy output device and recognized through the camera of the user terminal,
The access URL is generated by the app server based on the user information of the first patient and the hospital information received from the hospital server and transmitted to the hospital server,
When the access URL is transmitted from the hospital server to the user terminal, the user terminal is connected to the app server through the access URL at a location where the user wants to print the medical document, and the medical service provided from the app server The type of medical document that the user wants to print, the number of print copies, and the print format are input through the document providing interface,
The hospital output device or the pharmacy output device outputs the medical document according to the type of the medical document, the number of outputs, and the output format.
How to provide medical documentation.
According to claim 1,
The access URL is path information through which the user terminal can access the app server,
The user information is the patient registration number
How to provide medical documentation.
delete delete According to claim 1,
Receiving an insurance claim request signal from the user terminal; and
Including transmitting the received insurance claim request signal to the hospital server.
How to provide medical documentation.
An app server that performs a medical document provision method,
a communication unit configured to receive the access URL from a user terminal connected using the access URL and receive an output code from the user terminal;
an access URL analysis unit configured to analyze the access URL and extract hospital information and user information;
an interface providing unit configured to provide a medical document providing interface to the user terminal;
An output code analysis configured to analyze the output code to identify whether the output device from which the user will output the medical document is an output device in a hospital (hereinafter, hospital output device) or an output device in a pharmacy (hereinafter, pharmacy output device). wealth; and
An output device control signal generator configured to generate an output device control signal and transmit it to a hospital server or pharmacy server through the communication unit,
The output device control signal generator,
If the identified output device is the hospital output device, the output device control signal containing identification information of the hospital output device, identification information of the user, type of medical document, number of outputs, and output format is sent to the hospital server. send,
When the identified output device is the pharmacy output device, an output data request signal is transmitted to the hospital server, and when the output data is received from the hospital server, the pharmacy server is sent the identification information of the pharmacy output device and the user's information. transmitting the output device control signal containing identification information, type of the medical document, number of outputs, output format, and the output data;
The output code is identification information of the hospital output device or identification information of the pharmacy output device, and is configured to be attached to the hospital output device or the pharmacy output device and recognized through the camera of the user terminal,
The access URL is generated by the app server based on the user information of the first patient and the hospital information received from the hospital server and transmitted to the hospital server,
When the access URL is transmitted from the hospital server to the user terminal, the user terminal is connected to the app server through the access URL at a location where the user wants to print the medical document, and the medical service provided from the app server The type of medical document that the user wants to print, the number of print copies, and the print format are input through the document providing interface,
The hospital output device or the pharmacy output device outputs the medical document according to the type of medical document, the number of outputs, and the output format,
App server.
According to claim 6,
The access URL is path information through which the user terminal can access the app server,
The user information is the patient registration number
App server.
delete delete According to claim 6,
The Department of Communications
configured to receive an insurance claim request signal from the user terminal and transmit the received insurance claim request signal to the hospital server.
App server.
delete delete