KR102601053B1 - Method of inducing payment of receivables for patients visiting the hospital based on time complexity, spatial complexity, and similar complexity - Google Patents

Abstract

The present invention relates to a method for inducing payment of receivables from patients visiting a hospital based on time complexity, space complexity, and similar complexity. The present invention includes the steps of the cloud server receiving the patient ID and location information from the user terminal, determining whether the location of the user terminal is located within the hospital, and confirming whether the patient has arrived at the hospital; and the cloud server determining whether the location of the user terminal is within the hospital. In this case, the patient ID is transmitted to the hospital server, the hospital server searches patient information based on the received patient ID, and the patient information search result is transmitted to the cloud server, and the cloud server uses the location information of the user terminal. Calculating the spatial complexity, calculating the time complexity based on the payment receipt time of the user terminal, the patient's same-day treatment schedule, future advance payment time, and average hospital stay time, and the cloud server according to the calculated spatial complexity and time complexity. It includes generating an information message containing the patient's receivable status and transmitting it to the user terminal.

Description

{Method of inducing payment of receivables for patients visiting the hospital based on time complexity, spatial complexity, and similar complexity}

The present invention relates to a method of inducing payment for receivables of patients visiting a hospital based on time complexity, space complexity, and pseudo-complexity. In particular, the time complexity, space complexity, and pseudo-complexity of patients visiting the hospital are calculated in real time and the patient's receivables are calculated based on this. It is about how to provide a list and encourage payment.

The medical appointment fee (reservation consultation fee) is a fee that must be paid at the time of making a medical appointment, and is generally billed upon completion of hospital treatment. Since the medical appointment fee is not paid on the day of the medical appointment but is paid upon visiting the hospital, it is treated as an uncollected amount.

In addition, there are many cases where patients are busy completing treatment and leave without stopping by the collection counter, so hospital uncollected accounts are generated for a variety of reasons.

Recently, problems have emerged regarding the refund of prepaid medical expenses, and the Anti-Corruption and Civil Rights Commission is recommending mandatory notification of prepayment before paying medical expenses. When receiving prepayment from an unmanned payment machine, it is recommended that patients be notified in advance that prepaid medical expenses will be processed together, that prepaid medical expenses be paid only if the patient agrees, and that prepayment be made only if the patient agrees.

Prior patents include Registered Patent No. 10-2203518 (Hospital bill payment system and method using user devices and computer program for the same), but the hospital bill registered for the patient can be confirmed by users such as guardians and divided payments between family members in various ways. We are just launching technology to pay hospital bills.

The problem that the present invention aims to solve is to calculate the time complexity, space complexity, and pseudo-complexity by utilizing the location information and time information of the patient's user terminal to induce payment of the patient's receivables, and to calculate the time complexity and space complexity that enable the provision of customized services. and provides a method for inducing payment of receivables from hospital patients based on similar complexity.

In the method of inducing payment for receivables from patients visiting a hospital based on time complexity, space complexity, and similar complexity according to an embodiment of the present invention, the cloud server receives patient ID and location information from the user terminal, and determines whether the location of the user terminal is within the hospital. A step of checking whether the patient has arrived at the hospital, and if the location of the user terminal is within the hospital, the cloud server transmits the patient ID to the hospital server, and the hospital server searches the patient information based on the received patient ID and A step of transmitting information search results to the cloud server, and the cloud server calculates spatial complexity based on the location information of the user terminal, payment reception time of the user terminal, patient's same-day treatment schedule, future advance payment time, and average hospital stay time. It includes a step of calculating time complexity, and a step where the cloud server generates an information message containing the patient's receivable status according to the calculated space complexity and time complexity and transmits it to the user terminal.

According to the present invention, when a patient visits a hospital, it is confirmed whether the patient visited the hospital based on location information, and when the patient is confirmed to have visited the hospital, the patient is informed of the status of non-payment of the medical reservation fee and induces payment, thereby reducing uncollected accounts. In addition, you can automatically receive a waiting list for treatment without having to go through separate medical procedures, and provide customized recommendation services by checking the patient's previous application usage history.

In addition, it has the effect of increasing the turnover rate of medical services, reducing uncollected accounts, by providing recommendations and guidance to patients after treatment, and requesting payment for medical treatment immediately after the next treatment, thereby creating a virtuous cycle in which patients pay again.

Figure 1 is a flowchart explaining a method of inducing payment of receivables from patients visiting a hospital according to an embodiment of the present invention.
Figure 2 is a configuration diagram of a system for inducing payment of receivables from patients visiting a hospital according to an embodiment of the present invention.
Figures 3 and 4 are diagrams showing an example application that provides a service to induce payment of receivables from patients visiting a hospital according to an embodiment of the present invention.

Specific structural or functional descriptions of the embodiments according to the concept of the present invention disclosed in this specification are merely illustrative for the purpose of explaining the embodiments according to the concept of the present invention. They may be implemented in various forms and are not limited to the embodiments described herein.

Since the embodiments according to the concept of the present invention can make various changes and have various forms, the embodiments will be illustrated in the drawings and described in detail in this specification. However, this is not intended to limit the embodiments according to the concept of the present invention to specific disclosed forms, and includes all changes, equivalents, or substitutes included in the spirit and technical scope of the present invention.

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

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

Figure 1 is a flowchart illustrating a method of inducing payment for receivables from patients visiting a hospital based on time complexity, space complexity, and similar complexity according to an embodiment of the present invention.

Referring to FIG. 1, the method for inducing payment of receivables from patients visiting a hospital based on time complexity, space complexity, and similar complexity according to an embodiment of the present invention involves a patient holding a user terminal 200 visiting the hospital and executing a dedicated application. Perform login (S101). Depending on the embodiment, the user terminal 200 may be logged in in advance and run a dedicated application without logging in separately.

The user terminal 200 transmits the patient ID and location information of the user terminal to the cloud server 100 (S103). The cloud server 100 uses the received location information to determine whether the user terminal is located within the hospital and confirms whether the patient has arrived at the hospital (S105). If the location of the user terminal is within the hospital, the cloud server 100 transmits the patient ID to the hospital server 300 (S107). The hospital server 300 searches for patient information based on the received patient ID (S109). The patient information may be at least one of the patient-specific treatment reservation status, same-day treatment schedule, and non-payment status of treatment reservation fees, but is not limited thereto. The hospital server 300 transmits the patient information search results to the cloud server 100 (S111).

The cloud server 100 calculates spatial complexity based on the location information of the user terminal 200 (S113). The cloud server 100 calculates time complexity based on the payment receipt time of the user terminal 200, the patient's same-day treatment schedule, future prepayment time, and average hospital stay (S115). The cloud server 100 generates a guidance message containing the patient's receivable status according to the calculated space complexity and time complexity (S117). In other words, an information message containing treatment reservation status, same-day treatment schedule, and receivables status is generated according to the received patient information. The cloud server 100 transmits the generated information message to the user terminal 200 (S119). At this time, the cloud server 100 may receive location information of the user terminal 200 and determine whether to transmit a guidance message based on the location information. The type of the information message may be one of SMS, LMS, MMS, Kakao Notification Talk, and push notification, but is not limited thereto.

The user terminal 200 approves the received information message (S121) and requests payment for the receivable from the cloud server 100 (S123). The cloud server 110 requests receivable payment to the hospital server equipped with a payment module (S125). The hospital server 300 performs a payment process for receivables (S127) and sends a notification message to the cloud server when payment is completed (S129).

When the cloud server 100 receives a payment completion notification from the hospital server 300, it analyzes the recently used menu of the user terminal 200 and calculates the pseudo-complexity (S131). The cloud server 100 creates a waiting list for treatment according to the treatment information (S133). The cloud server 100 transmits the generated treatment waiting list to the user terminal 200 (S135). Once the patient pays the treatment reservation fee, the treatment process is automatically completed without any separate treatment procedures, and the patient can receive a waiting number for the treatment.

The cloud server 100 analyzes recommended services for each patient (S137). The cloud server 100 creates a recommended service menu according to the analysis results (S139). The cloud server 100 transmits the created recommended service menu to the user terminal 200 (S141).

Figure 2 is a configuration diagram of a system for inducing payment of receivables from patients visiting a hospital according to an embodiment of the present invention.

Referring to FIG. 2, the hospital visit patient receivable payment induction system 10 is composed of a cloud server 100, a user terminal 200, and a hospital server 300.

The cloud server 100 includes a user terminal location detection unit 110, a time complexity calculation unit 120, a space complexity calculation unit 130, a pseudo-complexity calculation unit 140, a guidance message generation unit 150, and a treatment waiting number table generation. It consists of a unit 160, a recommendation service menu creation unit 170, a recommendation analysis unit 180, a communication unit 191, a storage unit 193, and a control unit 195.

The user terminal location detection unit 110 may receive location information from the user terminal 100 and detect the location of the user terminal by determining whether the received location information is located within the hospital. The user terminal location detection unit 110 can detect not only whether the user is located within the hospital, but also where the user is located within the hospital.

The time complexity calculation unit 120 can check the patient's medical appointment reservation and daily schedule, and calculate time complexity through the average hospital stay time. By identifying medical appointments, you can check whether non-payment has been confirmed when performing follow-up measures (prescriptions) according to treatment, and by identifying the schedule for the day, you can check the time schedule for remaining treatment data. Notifications can be made based on same-day payment, interim payment, and uncollected recipients. You can receive notifications of registration fees, reservation test fees (sent at a specific time on the day of hospital visit), non-payment notifications (automatically sent in the form of a batch method), and inpatient interim payment notifications (sent on a specific day of the week). The time complexity calculation unit 120 determines the average payment time and stay time at the relevant hospital, and when the threshold point of stay time > average payment time is reached, it can check whether non-payment has been confirmed to the patient by sending a notification message.

Table 1 below shows the conditions of the receivables complexity table. By checking the complexity type as condition 2, condition 3, condition 4, and condition 5, a receivables notification can be sent, and a similar recommended menu can be provided to the patient according to the result processing.

Classification conditions Condition 1 Condition 2 Condition 3 Condition 4 Condition 5 Condition 6 Hospital stay time: minutes and seconds All 30 minute range 30 minute range Within the range of 30 to 2 hours Within 2 hours time range Hospitalization for less than 30 minutes or more than 6 hours Number of medical data N One less than 2 2 or more 2 or more 2 or more All Beacon signal storage window standards All doesn't exist has exist doesn't exist has exist All Notification sending result No receivables 100% 50% 100% 40% Request notification other than receivable target notification is required.

A receivables notification message can be created and provided for conditions 2 to 5. Table 2 below is an example table summarizing the timing of notification message sending according to conditions.

Case No. Data Hospital stay time (minutes/second) Number of medical data N Beacon signal result expected value Notification batch abnormality sent immediately/ 1~0.5: within 30 minutes/ 0.5 or less within 1 day One Condition 1 16 0 0 2 Condition 1 65 0 0 3 Condition 1 66 0 0 4 Condition 1 16 0 One 5 Condition 1 65 0 One 6 Condition 1 66 0 One 7 Condition 2 16 One 0 100 One immediately 8 Condition 2 65 One 0 100 One immediately 9 Condition 2 16 2 0 100 2 immediately 10 Condition 2 65 2 0 100 2 immediately 11 Condition 2 40 One 0 100 One immediately 12 Condition 3 16 One One 50 0.5 30 13 Condition 3 65 One One 50 0.5 30 14 Condition 3 16 2 One 50 One immediately 15 Condition 3 65 2 One 50 One immediately 16 Condition 3 40 One One 50 0.5 30 17 Condition 4 16 3 0 50 1.5 immediately 18 Condition 4 65 3 0 50 1.5 immediately 19 Condition 4 40 3 0 50 1.5 immediately 20 Condition 5 16 3 One 40 1.2 immediately 21 Condition 5 65 3 One 40 1.2 immediately 22 Condition 5 40 3 One 40 1.2 23 Condition 6 66 One 0 24 Condition 6 66 2 0 25 Condition 6 66 One One 26 Condition 6 66 2 One

The spatial complexity calculation unit 130 can check the location path of the person who arrived at the hospital and calculate spatial complexity through medical treatment history. By identifying the location path, you can send a welcome message or payment inducement message to the patient, and by understanding the treatment history, you can check whether or not payment has been made when approaching the relevant space (treatment department).

The pseudo-complexity calculation unit 140 analyzes the 20 most frequently used applications when a patient visits a hospital and can calculate the pseudo-complexity through similarity calculation and recommendation for the next action.

The information message generation unit 150 can generate a information message including treatment reservation status for each patient, same-day treatment schedule, and non-payment status of treatment reservation fees according to the patient information search results on the hospital server. The information message may be at least one of SMS, LMS, MMS, Kakao Notification Talk, and push notification, but is not limited thereto.

When payment for the treatment reservation fee is completed, the treatment waiting number table generator 160 can generate a treatment waiting number table according to the patient's treatment information. Treatment procedures are carried out automatically without the need for separate treatment procedures, and a waiting list for treatment can be provided.

The recommended service menu creation unit 170 may generate a recommended service menu according to the results of recommended service analysis according to each patient's tendencies.

The recommendation analysis unit 180 analyzes recommended services for each patient. Based on the pseudo-complexity results calculated in the pseudo-complexity calculation unit, recommended services for each patient can be analyzed and provided. The communication unit 191 can transmit and receive data between the user terminal and the hospital server. The storage unit 193 can store the generated guidance message and complexity calculation results. The control unit 195 can control each configuration of the cloud server.

Figures 3 and 4 are diagrams showing an example application that provides a service to induce payment of receivables from patients visiting a hospital according to an embodiment of the present invention.

Figure 3(a) is an example diagram of guiding payment by displaying the status of non-payment of medical reservation fee on the user terminal. Figure 3(b) is an example of a patient entering a payment password, and Figure 3(c) is an example of providing guidance on payment completion and creating a waiting list for treatment. Based on current medical information and location information, the patient can be guided to where to go next.

Figure 4(a) is a screen for payment of medical expenses on the user terminal, which provides information on medical expenses and receivables and guides the patient to make a selection. Figures 4(b) and 4(c) are post-treatment information screens for each department, which can provide information such as the next treatment date, where to go today, and tests requiring reservations.

The present invention has been described with reference to the embodiments shown in the drawings, but these are merely exemplary, and those skilled in the art will understand that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true scope of technical protection of the present invention should be determined by the technical spirit of the attached registration claims.

10; Patient receivable payment induction system 100; Cloud server
200; User terminal 300; hospital server
110; User terminal location detection unit 120; Time Complexity Calculator
130; Spatial complexity calculation unit 140; Pseudo-complexity calculation unit
150; Information message generation unit 160; Treatment waiting number table generator
170; Recommended service menu creation unit 180; Recommendation analysis department
191; storage unit 193; Ministry of Communications
195; control unit

Claims (4)

In the method of inducing payment of receivables from hospital patients based on time complexity, space complexity, and similar complexity,
(a) the cloud server receives the patient ID and location information from the user terminal, determines whether the user terminal is located within the hospital, and confirms whether the patient has arrived at the hospital;
(b) If the location of the user terminal is within the hospital, the cloud server transmits the patient ID to the hospital server, and the hospital server searches patient information based on the received patient ID and transmits the patient information search results to the cloud server. step;
(c) the cloud server calculates spatial complexity based on the location information of the user terminal, and calculates time complexity based on the user terminal's payment receipt time, the patient's same-day treatment schedule, future advance payment time, and average hospital stay time;
(d) the cloud server generates an information message containing the patient's receivable status according to the calculated space complexity and time complexity and transmits it to the user terminal;
(e) When the user terminal approves the received information message and requests payment for the treatment reservation fee to the cloud server, the cloud server requests payment for the treatment reservation fee to the hospital server equipped with the payment module, and the hospital server collects the treatment reservation fee. Proceeding with the payment process and sending a notification message to the cloud server when payment is completed; and
(f) When the cloud server receives a payment completion notification from the hospital server, analyzing the recently used menu of the user terminal, calculating the pseudo-complexity, generating a treatment waiting number table according to the treatment information, and transmitting it to the user terminal; including
The cloud server determines the average payment time and residence time based on time complexity, sets the point when the residence time becomes longer than the average payment time as the critical point, and checks whether non-receipt is confirmed.
The pseudo-complexity is calculated through similarity calculation and recommendation for the next action by analyzing 20 frequently used menus when a patient visits the hospital. Patients visiting the hospital based on time complexity, space complexity, and pseudo-complexity. Method of inducing payment of receivables.


delete delete According to paragraph 1,
(g) Patients visiting the hospital based on time complexity, space complexity, and pseudo-complexity, further including the step of the cloud server generating a recommended service menu for each patient according to the calculated pseudo-complexity and transmitting the generated recommended service menu to the user terminal. Method of inducing payment of receivables.

Images