KR102203518B1 - System and method for payment of hospital expenses using user device and computer program for the same - Google Patents

Abstract

A hospital expense payment system is to perform hospital expense inquiry and payment in relation to a patient using communication with a user device. The system includes: a care management module receiving hospital expense information on a patient from a first user device of a hospital manager, registering the information, and including a database storing payment history information on the patient and user information related to the patient and at least one guardian corresponding to the patient; and a payment module providing the hospital expense information to a second user device of the at least one guardian corresponding to the patient and performing payment processing with respect to a partial amount or the whole amount of the hospital expense information in response to a payment request received from the second user device. With the hospital expenses payment system, a user such as the guardian can confirm the hospital expenses registered in relation to the patient through a dedicated application on the user device such as a smartphone. In addition, the hospital expenses can be paid in various forms such as installment payment from the family. Accordingly, there is no need to visit the hospital for hospital expense payment.

Description

A system and method for payment of hospital expenses using a user device, and a computer program for the same {SYSTEM AND METHOD FOR PAYMENT OF HOSPITAL EXPENSES USING USER DEVICE AND COMPUTER PROGRAM FOR THE SAME}

Embodiments relate to a hospital bill payment system and method and a computer program therefor. More specifically, the embodiments allow a user such as a guardian to check the hospital expenses registered to a patient through a dedicated application running on a user device such as a smartphone, and to pay the hospital expenses in various ways, such as split payment between families. By doing so, it is about an online payment management technology that can solve the inconvenience of having to visit a hospital to pay for hospital expenses.

Due to the continuous increase in the elderly population in recent years, medical expenses for the elderly are on the rise every year. In the case of Korea, after entering an aging society in 2000, it entered an aging society in 2017, and by 2060, the proportion of the elderly population is expected to reach 41% of the total population. Accordingly, the share of medical expenses for the elderly aged 65 or older among the total medical expenses, including health insurance and medical benefits, continues to increase.

Such an increase in the elderly population is increasing the demand for nursing hospitals that provide medical services to elderly patients in need of long-term treatment. A nursing hospital is a medical institution based on the medical law, and aims to provide medical services to patients in need of device treatment such as senile diseases, chronic diseases, surgical operations or injuries.

In order for a patient who uses a nursing hospital to pay for medical services, the patient's guardian must visit the hospital to pay the hospital fee, and this is a big problem in that for long-term care patients, the guardian must visit the hospital at each payment. It has been a burden. In addition, in terms of amount, in the past, large hospital expenses had to be paid alone by guardians who visited the hospital, and there was no means or procedure for multiple guardians to share the hospital expenses. In addition, from the standpoint of the hospital, there is a problem that it is easy to cause non-payment of hospital fees for patients undergoing long-term care due to reasons such as non-visit by guardians.

Unexamined Patent Publication No. 10-2008-0071211

According to an aspect of the present invention, a user, such as a guardian, can easily check the hospital expenses registered to a patient by a hospital administrator through a dedicated application running on a user device such as a smartphone, regardless of time and place. It is possible to provide a system and method for payment of hospital expenses using a user device, and a computer program for the same, which enables payment of hospital charges by card or transfer method and allows payment in various ways such as split payment among families.

A hospital bill payment system according to an aspect of the present invention includes a database configured to store user information related to a patient and one or more guardians corresponding to the patient and payment history information for the patient, and the first user device of the hospital administrator A treatment management module configured to receive and register the patient's hospital cost information from the patient; And providing the hospital bill information to a second user device of the one or more guardians corresponding to the patient, and in response to a payment request received from the second user device, payment for a partial or full amount of the hospital bill information And a payment module configured to perform processing.

In an embodiment, the treatment management module includes: a treatment information receiving unit configured to receive the hospital bill information and identification information of a patient corresponding to the hospital bill information from the first user device; And a verification unit configured to receive a request for the hospital expense information from the second user device, and verify the user corresponding to the second user device by using the user information and the patient's identification information in the database. .

In one embodiment, the payment module is a payment information generation unit configured to store payment setting information corresponding to the patient, and to generate payment information corresponding to the one or more users using the hospital fee information and the payment setting information ; And a payment processing unit configured to receive the payment request corresponding to the payment information from the second user device, and to perform hospital bill payment corresponding to the payment request by communicating with an external server.

In this case, the payment setting information includes payment classification information that defines whether to pay in installments by a plurality of users, and the payment information may include a payment amount calculated using the hospital bill information and the payment classification information. .

The hospital bill payment system according to an embodiment further includes a marketing module configured to generate marketing information based on the user information and the payment history information stored in the database, and transmit the marketing information to the second user device.

In accordance with an aspect of the present invention, a method for payment of hospital expenses includes: storing user information related to a patient and one or more guardians corresponding to the patient and payment history information for the patient in a hospital payment system; Receiving, by the hospital bill payment system, the patient's hospital bill information from a first user device of a hospital administrator and registering it in the hospital bill payment system; Providing, by the hospital bill payment system, the hospital bill information to a second user device of the one or more guardians corresponding to the patient; Receiving, by the hospital bill payment system, a payment request for the hospital bill information from the second user device; And performing, by the hospital bill payment system, processing a partial amount or a total amount of the hospital bill information in response to the payment request.

In one embodiment, registering with the hospital bill payment system includes the step of receiving, by the hospital bill payment system, patient identification information corresponding to the hospital bill information from the first user device.

In this case, the providing of the hospital bill information may include: receiving, by the hospital bill payment system, an inquiry request for the hospital bill information from the second user device; And verifying, by the hospital bill payment system, the user corresponding to the second user device by using the user information and the patient identification information stored in the hospital bill payment system.

A method of paying hospital bills according to an embodiment includes: before receiving the payment request, storing payment setting information corresponding to the patient in the hospital bill payment system; Generating, by the hospital bill payment system, payment information corresponding to the one or more users using the hospital bill information and the payment setting information; And transmitting, by the hospital bill payment system, the payment information to the second user device.

The hospital bill payment method according to an embodiment includes the steps of, by the hospital bill payment system, generating marketing information based on the user information and the payment history information stored in the hospital bill payment system; And transmitting, by the hospital bill payment system, the marketing information to the second user device.

A computer program according to an aspect of the present invention is for executing a hospital bill payment method using a user device according to the above-described embodiments by being combined with hardware, and may be stored in a computer-readable recording medium.

According to the system and method for payment of hospital expenses using a user device according to an aspect of the present invention, a patient's guardian can easily check hospital expenses through a dedicated application executed on a user device such as a smartphone, and a card or a transfer method. This allows you to pay the hospital bill in real time. Therefore, as in the prior art, there is an advantage that the guardian does not need to visit the hospital every time to pay for hospital expenses, and the payment can be made conveniently in real time regardless of time and place.

In addition, the hospital bill payment system according to an aspect of the present invention has the advantage of reducing the cost burden of each guardian by supporting a function of split payment between multiple users, for example, a guardian's family.

Furthermore, in a hospital that has introduced the hospital bill payment system and method according to an aspect of the present invention, the promotion effect can be maximized through a hospital-only application, and the receiving channel can be expanded through the hospital bill payment system and easy storage management is possible, There is an advantage of reducing the possibility of non-payment of hospital expenses due to non-visit by guardians.

1 is a schematic block diagram of a hospital bill payment system using a user device according to an embodiment.
2 is a flowchart illustrating each step of a method of paying hospital bills using a user device according to an exemplary embodiment.
3 is a flow chart showing each step of a method for paying hospital bills using a user device according to another embodiment.
4A to 4C are conceptual diagrams illustrating exemplary user interfaces on a user device using a hospital bill payment system according to an exemplary embodiment.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings.

1 is a schematic block diagram of a hospital bill payment system using a user device according to an embodiment.

Referring to FIG. 1, a hospital bill payment system 3 using a user device according to the present embodiment operates while communicating with a first user device 1 of a hospital manager and a second user device 2 of a user who will pay hospital bills. Is configured to In addition, the hospital bill payment system 3 is configured to communicate with a financial institution server 4 such as a card company server to process payment for hospital bills. In one embodiment, communication between the hospital bill payment system 3 and the financial institution server 4 may be made via the relay server 5 of a payment relay provider such as VAN.

For the above operation, the hospital bill payment system 3 is communicatively connected to the user devices 1 and 2, the financial institution server 4, and the relay server 5 through a wired and/or wireless network. The communication method through a wired and/or wireless network may include all communication methods capable of networking an object and an object, and is not limited to wired communication, wireless communication, 3G, 4G, or other methods. For example, wired and/or wireless networks include Local Area Network (LAN), Metropolitan Area Network (MAN), Global System for Mobile Network (GSM), Enhanced Data GSM Environment (EDGE), and High Speed Downlink Packet Access (HSDPA). , W-CDMA (Wideband Code Division Multiple Access), CDMA (Code Division Multiple Access), TDMA (Time Division Multiple Access), Bluetooth, Zigbee, Wi-Fi, VoIP (Voice) over Internet Protocol), LTE Advanced, IEEE802.16m, WirelessMAN-Advanced, HSPA+, 3GPP Long Term Evolution (LTE), Mobile WiMAX (IEEE 802.16e), UMB (formerly EV-DO Rev. C), Flash-OFDM, iBurst and MBWA (IEEE 802.20) systems, HIPERMAN, Beam-Division Multiple Access (BDMA), Wi-MAX (World Interoperability for Microwave Access), and refers to a communication network by one or more communication methods selected from the group consisting of ultrasonic communication. However, it is not limited thereto.

The first user device 1 refers to a device for use by a person in charge of hospital expenses who wishes to claim hospital expenses to a patient or a guardian of a patient through the hospital bill payment system 3. However, the use of the first user device 1 is not limited to the person in charge of the cost of the hospital, and is in charge of managing information such as the patient's treatment number, hospitalization date, patient name, payment amount, etc. A user of, for example, an employee of the hospital general affairs department may correspond to a user of the first user device 1, and in this specification, such a user is collectively referred to as a hospital administrator.

In general, a hospital refers to a medical institution for the purpose of treating a patient and is installed in accordance with the medical law, and hospital fees refer to the amount charged by such medical institutions for a patient's diagnosis, treatment, procedure, and surgery. However, the hospital of the present specification is not limited to these medical institutions, and any facility that provides services for the purpose of diagnosis and improvement of the patient's health condition or care of patients with disabilities may correspond to the hospital of the present specification. have. For example, the hospital of this specification may be a nursing hospital or a nursing facility installed in accordance with the Elderly Welfare Act, and the hospital fee in this specification may refer to any cost charged to a patient or a guardian of a patient in such a nursing hospital or nursing facility. have.

The second user device 2 refers to a device for use by a user, such as a patient or a guardian of a patient, who is responsible for paying hospital charges for the patient to the hospital. At this time, the guardian of the patient is not necessarily limited to relatives such as the patient's family, and may be an arbitrary user who has agreed to pay the hospital fee for the patient or wishes to voluntarily pay the hospital fee, but is not limited thereto. In some cases, the user of the second user device 2 may be the patient himself. Further, the second user device 2 may refer to a user device of each guardian when there are multiple guardians corresponding to the same patient.

In FIG. 1, the first user device 1 is shown as one device and the second user device 2 is shown as three devices, but this is illustrative, and a hospital bill payment system 3 according to embodiments of the present invention. ) Is not intended to limit the number of hospitals or users that can be used or the number of devices.

In one embodiment, the first user device 1 is implemented as a computing device capable of executing a web browser, and the hospital bill payment system 3 is a hospital administrator to pay hospital bills in the form of a web page for the administrator. It provides a user interface for using the system 3. In addition, the second user device 2 is implemented in the form of a smartphone, and can operate while communicating with the hospital bill payment system 3 through an application (or app) running on the second user device 2. I can. For the above operation, the hospital bill payment system 3 may at least partially perform a function of a web server and at least partially perform a function of an application service server.

However, the shape of each of the user devices 1 and 2 is not limited to those described above. Accordingly, each of the first and second user devices 1 and 2 is a mobile communication terminal such as a smartphone, a personal computer, a notebook computer, a personal digital assistant (PDA), a tablet, and an IPTV. It may be implemented in the form of an arbitrary computing device such as a set-top box for (Internet Protocol Television) or the like, and is not limited to a specific type of device.

In one embodiment, the hospital bill payment system 3 includes a treatment management module 31 and a payment module 32. Also in one embodiment, the hospital bill payment system 3 further includes a marketing module 33. Further, each of the modules 31 to 33 described above may be configured to include a database (DB) and one or more functional units to be described later.

The devices described herein may be entirely hardware, or may have aspects that are partly hardware and partly software. For example, each module constituting the hospital bill payment system 3 using a user device and each system, device, server, etc. that communicate with it, and each module or unit included therein, provide data of a specific format and content in an electronic communication method. A device for receiving and software related thereto may be collectively referred to. In this specification, terms such as “unit”, “module”, “server”, “system”, “platform”, “device” or “terminal” are intended to refer to a combination of hardware and software driven by the hardware. do. For example, the hardware here may be a data processing device including a CPU or other processor. In addition, software driven by hardware may refer to an executing process, an object, an executable file, a thread of execution, a program, and the like.

In addition, in this specification, each device constituting the hospital bill payment system 3 using a user device is not intended to refer to a separate component that is physically classified. That is, in FIG. 1, the hospital bill payment system 3, the modules 31-33 included therein, and the DB or functional units constituting each module are illustrated as separate blocks, which are separated from each other, but this ) Is functionally classified by the action executed by it. Depending on the embodiment, some or all of the above-described parts may be integrated into the same single device, or one or more parts may be implemented as separate devices that are physically separated from other parts. For example, the devices constituting the hospital bill payment system 3 may be components that are communicatively connected to each other in a distributed computing environment.

The treatment management module 31 stores user information related to a patient and a guardian corresponding to the patient and/or patient's payment history information in the DB 310, and communicates with the first user device 1, thereby It serves to receive information and register it in the medical treatment information receiving unit 311. In an embodiment, the treatment management module 31 may verify whether the corresponding user is a guardian with inquiry authority for a patient through the verification unit 312 when there is a request for inquiry of hospital expenses from the user in the future. In addition, in an embodiment, the treatment management module 31 may further perform a management function for a treatment schedule such as a treatment reservation of a patient through the reservation management unit 313.

In response to the inquiry request received from the second user device 2 of one or more guardians corresponding to the patient, the payment module 32 processes the hospital expenses information in the form of payment information by the payment information generation unit 321 2 Provided to the user device (2). In addition, the payment module 32, when there is a payment request from the second user device 2, payment or transfer by card through communication between the payment processing unit 322 and the financial institution server 4 and/or the relay server 5 You can pay for hospital expenses in the following way. Further, in an embodiment, the payment module 32 may transmit a notification on the payment details of hospital expenses to the first user device 1 and/or the second user device 2 through the notification transmission unit 323.

Marketing module 33, based on user information and/or payment history information stored in the DB 310 of the treatment management module 31, to the marketing information generating unit 331 And transmits it to the second user device 2 by the transceiver 332. Marketing information may be presented on the second user device 2 together with the payment information, but is not limited thereto, and is transmitted to the second user device 2 in an arbitrary form such as a separate information display form or a notification on the user device. Can be.

2 is a flowchart illustrating each step of a method of paying hospital bills using a user device according to an exemplary embodiment. For convenience of explanation, a method of paying hospital bills according to the present embodiment will be described with reference to FIGS. 1 and 2.

First, the hospital administrator may register the patient's hospital expenses in the treatment management module 31 by accessing the administrator page provided by the hospital bill payment system 3 using the first user device 1 (S1). In this case, information such as a patient name, a medical treatment number, and hospitalization date that can identify the patient may be further input together with the patient's hospital cost. The inputted information may be stored in the DB 310 of the treatment management module 3 (S2).

Meanwhile, the DB 310 may further store payment history information of each patient in the hospital. At this time, the payment history information may basically include the payment details of hospital fees made through communication between the hospital payment system 3 and the guardian's user device, but is not limited thereto, and payment details made through other channels are stored in the DB 310. By integrating and storing, it may be easier for the hospital administrator to manage the details of the hospital charges receivable through the management page provided by the hospital bill payment system 3.

For example, when the hospital payment system 3 is configured so that the physical payment terminal in the hospital uses the same payment relay business as the hospital payment system 3 (i.e., VAN), the treatment management module 3 is a relay server By receiving the payment details of the hospital from (5) and storing them in the DB 310, the payment details through the offline payment terminal and the online payment details through the hospital bill payment system 3 are integrated and stored in the DB 310. You can make it visible through the page. Alternatively, the treatment management module 31 may be configured to be linked with the hospital's Enterprise Resource Planning (ERP) system to store the entire hospital's fund management details in the DB 310 regardless of the payment method.

When there is a request for inquiry about hospital expenses from the second user device 2 of the patient guardian (S3), the payment information generation unit 321 of the payment module 32 is the guardian who requests the inquiry based on the information of the DB 310 It generates payment information to be provided to the user (S4), and transmits it to the second user device 2 (S4). The payment information may include at least identification information such as a patient's name and an amount of hospital expenses to be paid for the patient. In addition, the payment information may further include information items for facilitating patient identification, such as a patient's hospitalization date and medical number, or for delivering additional information about the patient.

In one embodiment, prior to providing payment information to a patient, the treatment management module 31 of the hospital bill payment system 3 determines whether the user of the second user device 2 requesting the inquiry is the guardian for the patient. You can also perform verification on. To this end, first, for each patient, one or more guardian identification information (e.g., name, mobile phone number, etc.) and/or identification information (e.g., IMEI) of the device used by the caller are treated for each patient. It may be stored in the DB 310 of the management module 31. In the treatment management module 31, when a hospital bill inquiry is requested from the second user device 2, identification information of the second user device 2 that has transmitted the request or the guardian input to the second user device 2 Through the identification information, the inquiry requester performs verification as to whether or not the guardian for the patient is correct, and the patient's hospital expenses information can be provided to the second user device (2) only when it is verified as a guardian registered in advance. have.

On the other hand, in the case of registering new guardian information in the DB 310, the hospital administrator must enter the guardian information into the hospital bill payment system 3 through the first user device 1, or a new second user device When there is a request for registration of a new guardian from (2), the hospital bill payment system (3) sends authentication information to the first user device (1), so that the guardian registration is made only when the authentication information is inputted. Can be configured. Through this, it is possible to prevent an unauthorized third party from inquiring the details of hospital expenses with only partial information such as the patient's name or medical treatment number.

Thereafter, when payment is requested from one or more second user devices 2 (S5), the payment processing unit 322 of the treatment management module 31 makes a payment corresponding to the guardian who requested the payment to the financial institution server 4 By requesting the payment of the amount (S7), the payment of the payment can be made in the financial institution server 4 (S8). Payment may be made in a card authorization method by communicating with a card company server or a VAN company server using, for example, card information input by a guardian. However, the payment method is not limited thereto, and in another embodiment, payment of the payment may be made by a transfer method by requesting the transfer of funds to the bank server directly or through the server of a relay operator.

In the present specification, payment of the payment amount by the money transfer method may be referred to as a so-called silver pay in that it is payment by patients such as the elderly and the like, and the payment method of the payment amount using silver pay is as follows.

For example, in an embodiment, payment of the payment may be made through a transfer relay service. Users can sign up for the transfer relay service as a member and perform procedures such as identity verification, account registration, and withdrawal agreement. In the process of account registration and withdrawal agreement, for example, in the transfer relay service, the user transfers the information included in the deposit request after remitting a predetermined amount (e.g., KRW 1) to the account entered by the user. It is also possible to authenticate that the account is the user's own account through a method of entering in

When payment through the transfer relay service is requested from the guardian, the payment processing unit 322 relays the user ID and store ID (transfer relay of the provider operating the hospital bill payment system 3) according to the definition of the information item required in the transfer relay service. Service member information), order number, and information such as a service token granted by a business operator operating the hospital bill payment system 3 may be transmitted to the financial institution server 4 (ie, a transfer relay service server). In addition, the information transmitted from the payment processing unit 322 to the transfer relay service may further include detailed information such as whether a cash receipt is issued, a result and cancellation page URL, and a return parameter.

After receiving the payment request from the payment processing unit 322, the financial institution server 4 displays information such as product name, price, name, and e-mail on the second user device 2 so that a guardian can check the payment details. , When a user inputs preset authentication information such as a payment PIN, a transfer for the requested payment amount may be requested from a financial institution such as a bank linked with a transfer broker. Meanwhile, the above process of allowing the guardian to check the payment details for the transfer relay service may be performed via the hospital bill payment system 3 or may be omitted.

In addition, in another embodiment, the process of transferring payment may be performed in a manner in which the payment processing unit 322 directly requests a transfer to a bank or the like based on open banking without going through a transfer broker. In this case, the financial institution server 4 ) May be a financial institution such as a bank where the guardian's account is opened.

Meanwhile, the requested payment amount at this time may be all of the hospital expenses of the patient, or may be an amount corresponding to part of the hospital expenses when a plurality of guardians divide and pay the hospital expenses. For example, a guardian requesting payment can select a payment method from full or partial payment through the user interface on the second user device 2, and in the case of partial payment, request payment by entering the amount to be paid by himself/herself. have.

In one embodiment, when a plurality of guardians partially pay for hospital expenses, the list of guardians to partially pay and the amount of payment to be partially paid by each guardian (i.e., burden ratio), etc. of the treatment management module 31 are provided as user information. It may be stored in the DB 310. The payment amount of each guardian may be determined by dividing hospital expenses equally by the number of guardians registered for the same patient, or by entering the burden ratio of each guardian individually by the patient or guardian. May be.

In this case, the payment amount of the payment information to be provided to each guardian who requested the inquiry of hospital expenses may include a payment amount automatically calculated according to the burden ratio of the corresponding guardian. The partial payment amount calculated as described above may be presented together with information on all hospital expenses, and may also be presented with information on amounts already paid by another guardian among all hospital expenses and/or information on balances that have not yet been paid. Alternatively, even if the guardians have not set the burden ratio in advance, the balance of the total hospital expenses excluding the payment amount of the guardians who paid first may be provided as payment information to the guardians who pay later.

The financial institution server 4 may transmit the payment result to the payment processing unit 322 of the treatment management module 31 after payment (S9). Meanwhile, the above payment and payment result reception (S7 to S9) may be performed through a relay server of a settlement relay service provider (ie, VAN company). The payment processing unit 32 transmits the hospital bill payment result received from the financial institution server 4 to the treatment management module 31 so that the hospital bill payment history is stored in the DB 310 (S10). The payment history refers to the date of occurrence, payment date, and payment amount of hospital charges for a patient, and the hospital administrator can check the hospital expenses payment history through the DB 310, and the guardian also pays the corresponding patient's hospital expenses upon request. You can check the history.

In one embodiment, the hospital bill payment history stored in the DB 310 is another payment method (e.g., offline payment) made through the server 5 of a settlement relay service provider (ie, VAN) linked with the hospital bill payment system 3 It can include payment history by terminal). To this end, the treatment management module 31 may receive a history of payment of hospital charges for the same hospital from the relay server 5 and store it in the DB 310. Through this embodiment, the hospital administrator or guardian can inquire not only the online payment history through the hospital bill payment system 3, but also the details of the hospital expenses paid offline by the guardian visiting the hospital directly in the hospital bill payment system 3 There is an advantage to be able to.

In an embodiment, the notification transmission unit 323 of the payment module 32 may transmit a notification about the payment result to the second user device 2 of the guardian who has requested the payment (S11). Alternatively, the notification transmission unit 323 may transmit a notification about the payment result to the first user device 1 of the hospital administrator so that the hospital administrator can check the payment of the guardian in real time (S12). The notification may be transmitted in various forms such as e-mail, text message, pop-up window, push notification through an application, etc. that can be checked on the user devices 1 and 2, and is not limited to a specific format.

In one embodiment, when multiple guardians are registered in advance for the same patient and hospital charges are paid in full or in part from one of the guardians, the payment result is transmitted as a notification to other guardians for the same patient. May be. The notification transmitted at this time may include identification information of a patient, information on a payment amount or payment rate paid by a guardian who paid first among the patient's hospital expenses, and identification information of a guardian who made the payment. This notification plays a role in preventing the occurrence of receivables by urging the guardians who have not yet paid for partial payment when multiple guardians pay for the same patient's hospital expenses.

3 is a flowchart illustrating each step of a method of paying hospital bills using a user device according to another embodiment. For convenience of explanation, a method for paying hospital expenses according to the present embodiment will be described with reference to FIGS. 1 and 3.

In the case of nursing hospitals or nursing facilities, compared to general medical institutions, patients who require long-term treatment or long-term hospitalization (e.g., elderly people, etc.) have a relatively large number of characteristics, and due to this, the payment of hospital fees by patients or guardians is sometimes made periodically for a long period many. In this case, since it may be cumbersome for each guardian to check the hospital charges and request payment for each payment, in this embodiment, in preparation for such periodic long-term payment, the patient or guardian registers the payment settings in advance and based on this. Payment can be made.

Specifically, the guardian may transmit payment setting information to the hospital bill payment system 3 through the second user device 2 (S21), and the transmitted payment setting information is a treatment management module ( 31) can be registered in the DB (310). In FIG. 3, it is shown that payment settings are received from the guardian's second user device 2, but this is illustrative. In another embodiment, payment settings are provided by a hospital administrator based on information confirmed face-to-face with a patient or guardian. 1 It can also be input to the hospital bill payment system 3 through the user device 1.

The payment setting information may include identification information of a patient and identification information (eg, name, mobile phone number, etc.) of one or a plurality of guardians who will pay hospital expenses for the patient. In addition, the payment setting information may include identification information or device information for authentication of each guardian. Further, the payment setting information is information on the payment method (e.g., credit card number, automatic debit account number, etc.) and payment schedule of each guardian, or information on the burden ratio between each guardian when there are multiple guardians for the same patient. And the like.

When the hospital administrator registers hospital expenses through the first user device 1 (S23), the treatment management module 31 stores the information in the DB 310 (S24), and the payment module 32 stores the corresponding information to each guardian. Corresponding payment information can be generated and notified to the guardian's second user device 2. Since the process of registering hospital bill information and generating payment information is the same as the corresponding process of the embodiment described above with reference to FIG. 2, detailed descriptions are omitted to avoid duplication of description. However, unlike the above-described embodiment, in this embodiment, the guardian does not need to directly inquire or request payment for hospital expenses, and payment information is periodically generated based on the payment settings registered in advance, and the second user device (2) is sent to.

The payment information notified to the second user device 2 is to inform the guardian of the payment amount corresponding to all or part of the hospital expenses, and when and how to pay the amount. In one embodiment, when the user's authentication information (e.g., account password, authentication certificate authentication value, etc.) needs to be entered in order to perform automatic payment, the payment information notified to the second user device 2 is such that the user authenticates. It may also include a payment uniform resource locator (URL) that allows information to be directly entered.

Automatically after notifying the guardian of payment information through the second user device 2, or in response to receiving authentication information by requesting authentication information from the guardian through the second user device 2, the payment module ( In 32), the payment of the payment is requested through communication with the financial institution server 4 (S26, S27), and the payment result may be received and stored in the DB 310 as a hospital bill payment history (S28, S29). In addition, the notification transmission unit 323 of the payment module 32 may transmit a notification on the payment result to the first user device 1 of the hospital administrator and/or the second user device 2 of one or more guardians ( S30, S31).

Since the above-described processes (S26 to S31) of the embodiment shown in FIG. 3 are the same as the corresponding processes (S7 to S12) of the embodiment described above with reference to FIG. 2, detailed descriptions are omitted to avoid redundancy.

4A to 4C are conceptual diagrams illustrating an exemplary user interface on a user device using a hospital bill payment system according to an embodiment, and illustrating a user interface on a second user device 2 (FIG. 1) of a guardian.

Referring to FIG. 4A, a guardian may request inquiry and payment of hospital expenses through an interface element (button, etc.) 401 of a user device. In addition, the guardian may check marketing information provided by the hospital bill payment system through the interface elements 402 and 404, or register an inquiry about the hospital in the hospital bill payment system through the interface element 403.

When a guardian selects the interface element 401 of FIG. 4A, as shown in FIG. 4B, interface elements 411 and 412 through which the guardian can input identification information (eg, patient name, medical number, etc.) of a target patient. Are displayed. The guardian may input necessary information through a user interface element on the screen, select an interface element such as an inquiry button 413, and request medical expenses inquiry from the hospital expenses payment system.

4C is a screen showing the result of medical expense inquiry according to the request of the guardian, and the patient's identification information 420 such as patient name 414 and hospitalization date 415, and payment information 430 such as payment amount 416 It is displayed on the screen of the device, and the guardian may request the payment of the payment amount to the hospital bill payment system by selecting an interface element such as a payment button 419. At this time, the guardian may select full payment or partial payment through the interface element 417, and in the case of partial payment, it is also possible to request payment for a desired amount by inputting the amount to be paid 418.

Referring back to FIG. 4A, in one embodiment, not only the inquiry and payment function of hospital charges, but also the introduction of the hospital's greeting, hospitalization and discharge guidance or hospital use guidance, clinic services, and other services through interface elements 402 and 404, and hospital location introduction B. Traffic information can be provided as marketing information to the user device of a guardian who uses the hospital bill payment system. In addition, in the hospital bill payment system, the notification of the hospital can be viewed on the user device through the interface element 403, or the hospital administrator can check the information by receiving the user's inquiry.

In one embodiment, the marketing information provided to the guardian through the interface elements 402-404 of FIG. 4A or other methods (eg, pop-up window, push notification, etc.) is not simply information set in advance, but a user associated with the guardian. It may be dynamic information that is customized for a user based on information and payment history information.

For example, if the caregiver paid for hospital charges for a unit period (e.g., one year) is more than a predetermined threshold, and as a result of user information verification, no other guardian has been set for the same patient, the burden of hospital expenses on the user can be reduced Marketing information may be generated to propose a partial payment function that can be performed to the user and transmitted to the user together with or separately from the payment information.

As another example, when it is confirmed from the patient's payment history information that there are multiple guardians, such as once the first user pays the hospital fee and the second user pays the hospital fee the other time for the same patient, each hospital fee is generated. The marketing information may be generated to propose that the city first and second users jointly pay for the hospital bill. In this case, since it is difficult to clearly grasp the relationship between the guardians using only the payment history information, the marketing information that proposes partial payment is the amount of payment among users who paid for the same patient's hospital expenses. The user is determined as the primary guardian (e.g., the first user) and transmitted only to the user device of the primary guardian, and the marketing information may be transmitted to the user device of another guardian (e.g., a second user) if the principal guardian approves. .

As another example, if it is confirmed from the payment history that the guardian periodically inquired and paid for hospital expenses for a certain period of time for the same patient, suggest to the guardian to pre-register the payment settings without having to query the hospital expenses for each payment. You can also create marketing information.

The operation of the hospital bill payment method using the user device according to the embodiments described above may be implemented at least partially as a computer program and recorded on a computer-readable recording medium. A recording medium in which a program for implementing an operation according to the method according to the embodiments is recorded and the computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tapes, floppy disks, and optical data storage devices. In addition, the computer-readable recording medium may be distributed over a computer system connected through a network, and computer-readable codes may be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing this embodiment may be easily understood by those skilled in the art to which this embodiment belongs.

In addition, each block or each step shown in the flowcharts herein may represent a module, segment, or part of code that includes one or more executable instructions for executing the specified logical function(s). In addition, in some alternative embodiments, it is possible that the functions mentioned in the blocks or steps occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially simultaneously, or the blocks or steps may sometimes be performed in the reverse order depending on the corresponding function.

The present invention described above has been described with reference to the embodiments shown in the drawings, but these are merely exemplary, and those of ordinary skill in the art will understand that various modifications and variations of the embodiments are possible therefrom. However, such modifications should be considered to be within the technical protection scope of the present invention. Accordingly, the true technical scope of the present invention should be determined by the technical spirit of the appended claims.

Claims (9)

A database configured to store user information related to a patient and a plurality of guardians corresponding to the patient, and payment history information for the patient, and configured to receive and register the patient's hospital cost information from the first user device of the hospital manager. Care management module; And
Provide the hospital bill information to a second user device of the plurality of guardians corresponding to the patient, and to perform payment processing for a partial amount of the hospital bill information in response to a payment request received from the second user device. Including a configured payment module,
The user information includes identification information of the plurality of guardians or identification information of user devices of the plurality of guardians,
The treatment management module,
A verification unit configured to receive a request for the hospital expense information from the second user device, and verify a user corresponding to the second user device by using the user information in the database,
In response to receiving a request for registration of a new guardian from the second user device, authentication information is transmitted to the first user device, and when the authentication information is input by the second user device, the new guardian is Is further configured to register for user information,
The payment module,
A payment information generator configured to store payment setting information corresponding to the patient, and to generate payment information corresponding to each of the plurality of guardians by using the hospital fee information and the payment setting information; And
A payment processing unit configured to receive the payment request corresponding to the payment information from the second user device, and to perform a hospital bill payment corresponding to the payment request by communicating with an external server,
The payment setting information includes information on a burden ratio of each of the plurality of guardians,
The payment information includes a payment amount calculated using the hospital cost information and the burden ratio information, and an amount previously paid before receiving the payment request among hospital expenses or an amount not paid until the payment request is received. Payment system.
The method of claim 1,
The treatment management module,
The hospital bill payment system further comprising a treatment information receiving unit configured to receive the hospital bill information and the patient identification information corresponding to the hospital bill information from the first user device.
delete The method of claim 1,
And a marketing module configured to generate marketing information based on the user information and the payment history information stored in the database, and transmit the marketing information to the second user device.
Storing user information related to the patient and a plurality of guardians corresponding to the patient, and payment history information for the patient in a hospital bill payment system;
Receiving, by the hospital bill payment system, the patient's hospital bill information from a first user device of a hospital administrator and registering it in the hospital bill payment system;
Storing payment setting information corresponding to the patient in the hospital bill payment system;
Providing, by the hospital bill payment system, the hospital bill information to a second user device of the plurality of guardians corresponding to the patient;
Receiving, by the hospital bill payment system, a payment request for the hospital bill information from the second user device; And
The hospital bill payment system, in response to the payment request, comprising the step of performing a payment processing for a partial amount of the hospital bill information,
The user information includes identification information of the plurality of guardians or identification information of user devices of the plurality of guardians,
Providing the hospital cost information,
Receiving, by the hospital bill payment system, an inquiry request for the hospital bill information from the second user device;
Verifying, by the hospital bill payment system, a user corresponding to the second user device by using the user information stored in the hospital bill payment system;
Generating, by the hospital bill payment system, payment information corresponding to each of the plurality of guardians using the hospital bill information and the payment setting information; And
The hospital bill payment system includes the step of transmitting the payment information to the second user device,
The payment setting information includes information on a burden ratio of each of the plurality of guardians,
The payment information includes a payment amount calculated using the hospital cost information and the burden ratio information, and an amount previously paid before receiving the payment request among hospital expenses, or an amount not paid until the payment request is received,
Receiving, by the hospital bill payment system, a request for registration of a new guardian from the second user device;
Transmitting, by the hospital bill payment system, authentication information to the first user device in response to receiving the registration request; And
The hospital bill payment method further comprising, by the hospital bill payment system, registering the new guardian in the user information when the authentication information is input by the second user device.
The method of claim 5,
The step of registering in the hospital bill payment system further comprises the step of receiving, by the hospital bill payment system, patient identification information corresponding to the hospital bill information from the first user device.
delete The method of claim 5,
Generating, by the hospital bill payment system, marketing information based on the user information and the payment history information stored in the hospital bill payment system; And
The hospital bill payment method further comprising the step of transmitting, by the hospital bill payment system, the marketing information to the second user device.
A computer program combined with hardware and stored in a computer-readable recording medium to perform the hospital bill payment method according to any one of claims 5, 6 and 8.

Images