Electronic payment support system and application software

Abstract

We provide an electronic payment support system that works in conjunction with an invoice creation system to facilitate electronic payments, and is easy to implement and maintain. [Solution] The electronic payment support system 10 comprises a linking application 33 implemented on an existing facility-installed terminal 20 and an electronic payment terminal 40. The linking application 33 obtains screen data of the receipt screen generated by the receipt program 32 and displayed on the display 25 from the OS 31. The linking application 33 obtains electronic payment information, including the patient number, patient name, and total billing amount shown on the receipt, from the screen data using an OCR function. The linking application 33 transmits the electronic payment information to the electronic payment terminal 40 by one of the following means: "transmission via the internet," "transmission via LAN," or "code printing." The transmission means is specified by the operator in the initial setup according to the specifications of the facility-installed terminal 20 and peripheral equipment.

Description

Technical Field

[0001] The present invention relates to an electronic payment support system that supports electronic payment in cooperation with a billing creation system such as a receipt computer, and to application software used for the electronic payment support system.

Background Art

[0002] Receipt computers that create medical fee statements (receipts) in medical facilities such as hospitals, clinics, and dental clinics are known. A receipt computer is implemented by a receipt program installed on a personal computer. The receipt program receives input from an operator such as a nurse or office worker and creates a receipt. The operator bills the patient for medical fees based on the receipt.

[0003] Patent Document 1 discloses a support system that supports electronic payment in cooperation with an existing receipt computer. The support system includes a post-payment reception terminal and a processing server. The post-payment reception terminal reads a receipt printed by the receipt computer with a scanner to generate image data, and uploads the image data to the processing server via the Internet. The processing server acquires payment information including a patient number and a billed amount from the image data, and registers the payment information in a database. A patient accesses the processing server using a patient terminal owned by the patient, acquires the registered payment information, and pays the fee (medical fee) by post-payment using credit card payment. After the patient post-pays the medical fee, the processing server registers the completion of payment in the database.

Prior Art Literature

Patent Literature

[0004]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0005] The support system disclosed in Patent Document 1 requires a management server to accept access from patient terminals via the internet and to manage whether or not patients have paid their medical fees. However, for small-scale medical facilities, the introduction and maintenance of a system using a management server is cumbersome.

[0006] This invention was made against this background, and its purpose is to provide an electronic payment support system that supports electronic payments in cooperation with invoice creation systems such as medical billing computers, and that is easy to implement and maintain. [Means for solving the problem]

[0007] (1) The electronic payment support system according to the present invention comprises application software implemented on a facility-installed terminal having a terminal memory for storing an OS and an invoice creation program, a terminal computer, a display, and an input interface, and an electronic payment terminal having a communication interface, a reader, and a controller. The application software causes the terminal computer to execute the following based on receiving an output instruction through the input interface: a screen data acquisition process that acquires invoice screen data showing the invoice screen displayed on the display by the invoice creation program through the OS, a first acquisition process that acquires electronic payment information including user identification information and the invoice amount from the invoice screen data, and an electronic payment information output process that outputs the electronic payment information. The controller executes a second acquisition process that acquires the electronic payment information output by the facility-installed terminal, an electronic payment process using the acquired electronic payment information, a completion notification reception process that receives an electronic payment completion notification through the communication interface, and a payment completion notification output process that outputs a payment completion notification.

[0008] The operator creates invoices, such as medical claims, using a terminal installed at the facility. The created invoices are displayed on a screen. The operator inputs an output command while the invoice is displayed on the screen. Upon receiving the output command, the application software acquires the invoice screen data through the OS, obtains electronic payment information from the invoice screen data, and outputs the electronic payment information. Output of electronic payment information includes, for example, transmission via the internet or LAN, and code printing. The code is a code that can read information, such as a QR code (registered trademark) or a barcode. The electronic payment terminal acquires the electronic payment information output by the terminal installed at the facility and performs electronic payment processing using that information. Electronic payment processing is performed using conventional methods. For example, the controller of the electronic payment terminal displays a code on the screen indicating the electronic payment information, the communication address of the electronic payment server, and the biller ID. The user scans the code using their user terminal and obtains the electronic payment information, communication address, and biller ID. The user terminal accesses the electronic payment server indicated by the acquired communication address and performs electronic payment with the electronic payment server using the electronic payment information, the biller ID, and the personal information for electronic payment stored in the user terminal's memory. Alternatively, the controller of the electronic payment terminal captures a code displayed by the user on the user terminal and acquires the user's personal information for electronic payment. The controller performs electronic payment with the electronic payment server using the electronic payment information, the biller ID, and the personal information for electronic payment. When the electronic payment is completed, the controller outputs a payment completion notification. The payment completion notification is output, for example, by outputting (displaying) it on a display device or by outputting (transmitting) it to a terminal installed at the facility. In this way, the electronic payment support system according to the present invention can support electronic payment in cooperation with a terminal installed at the facility, which is an invoice creation system. Furthermore, since the electronic payment support system according to the present invention can perform electronic payment using application software implemented on the terminal installed at the facility and an electronic payment terminal, it is easy to introduce and maintain.

[0009] (2) The application software may further cause the terminal computer to execute a specification acceptance screen display process that displays a specification acceptance screen on the display that accepts the specification of one of the output means, which is either a first output means that indicates printing of a code indicating the electronic payment information or a second output means that indicates transmission of the electronic payment information; and a specification acceptance means acquisition process that acquires the specification output means which is the output means specified on the specification acceptance screen. The application software causes the terminal computer to execute the electronic payment information output process that generates the code and outputs it to the printing device based on the fact that the specification output means is the first output means. Based on the fact that the specification output means is the second output means, the application software causes the terminal computer to execute the electronic payment information output process that transmits the electronic payment information to the electronic payment terminal.

[0010] Various types of facility-installed terminals exist, including those that can communicate with electronic payment terminals via the internet, local area networks (LANs), proximity wireless communication, and communication cables, as well as those that do not have means of communication with electronic payment terminals. The operator selects the optimal output method during initial setup, taking into account the specifications, performance, and peripheral equipment of the facility-installed terminal. The selection of the optimal output method can be done for each facility-installed terminal. In other words, even if multiple types of facility-installed terminals with different specifications are installed in the facility, electronic payment information can be output using the optimal output method according to the specifications. Therefore, the electronic payment support system according to the present invention can be made compatible with various types of facility-installed terminals.

[0011] (3) The application software may have the terminal computer perform the initial setup process. The initial setup process includes: an identification information acquisition process to acquire program identification information indicating the invoice creation program; a first position information acquisition process to acquire first position information indicating a first position on the invoice screen, where the user identification information is acquired, by receiving a specification of the first position through the input interface; and a second position information acquisition process to acquire second position information indicating a second position indicating a second position on the invoice screen, where the invoice amount is acquired, by receiving a specification of the second position through the input interface. The screen data acquisition process is a process of passing an image data acquisition instruction including the program identification information to the OS and receiving the invoice screen data from the OS. The first acquisition process includes a process of acquiring the user identification information based on the invoice screen data and the first position information, and a process of acquiring the invoice amount based on the invoice screen data and the second position information.

[0012] The application software captures user identification information and invoice amount displayed at the location specified by the operator on the invoice screen as information for electronic payment. Therefore, the application software can reliably capture user identification information and invoice amount regardless of the type of invoice screen.

[0013] (4) The application software may further cause the terminal computer to execute a confirmation screen display process that displays a confirmation screen on the display having the user identification information and the billing amount obtained in the first acquisition process, and a confirmation icon.

[0014] The operator selects the confirmation icon if the user identification information and billing amount shown on the invoice screen match the user identification information and billing amount shown on the confirmation screen. Therefore, the electronic payment support system according to the present invention can prevent electronic payments from being made based on incorrect electronic payment information.

[0015] (5) The invoice created by the invoice creation program may be a medical claim form. The application software causes the terminal computer to perform an initial setup process. The initial setup process includes an item information import process that stores item information, including the item name and item price, in the terminal memory. Based on receiving an item information display instruction from the user through the input interface, the application software causes the terminal computer to perform an item list display process that displays a list of item names stored in the terminal memory on the display, and based on receiving an item specification from the user through the input interface, a settlement information generation process that generates the electronic settlement information including the item indicated by the item specification and the corresponding item price. The invoice amount is the sum of the item price and the medical fee.

[0016] The electronic payment support system according to the present invention, with the above configuration, can simultaneously perform electronic payments for medical fees and goods purchases.

[0017] (6) The application software may, based on the determination that the designated output means is the second output means and that the second output means is unexecutable, cause the terminal computer to execute an inquiry screen display process that displays an inquiry screen on the display asking whether or not to make the first output means the designated output means. Based on the receipt of a change instruction to make the first output means the designated output means through the input interface on the inquiry screen, the terminal computer is caused to execute the electronic payment information output process that generates the code and outputs it to the printing device.

[0018] In the event of communication failures such as internet or LAN disconnections or collisions, the system will accept instructions from the operator and print a code indicating electronic payment information. Therefore, electronic payments can be made even in the event of communication failures.

[0019] (7) The application software according to the present invention is implemented in a facility-installed terminal having a terminal memory for storing an OS and an invoice creation program, a terminal computer, a display, and an input interface. Based on receiving an output instruction through the input interface, the application software causes the terminal computer to execute a screen data acquisition process that acquires invoice screen data showing the invoice screen displayed on the display via the OS by the invoice creation program, a first acquisition process that acquires electronic payment information including user identification information and the invoice amount from the invoice screen data, and an electronic payment information output process that outputs the electronic payment information.

[0020] The operator creates invoices, such as medical claims, using a terminal installed at the facility. The created invoices are displayed on a screen. While the invoice is displayed on the screen, the operator inputs an output command. Upon receiving the output command, the application software acquires the invoice screen data through the OS, obtains electronic payment information from the invoice screen data, and outputs the electronic payment information. Outputting the electronic payment information includes, for example, transmission via the internet or LAN, and code printing. In this way, the application software according to the present invention can support electronic payments in cooperation with a facility-installed terminal that is an invoice creation system. Furthermore, since the application software according to the present invention can be used without modifying existing invoice creation systems, it is easy to introduce and maintain.

[0021] (8) The application software according to the present invention may cause the terminal computer to further execute: a specification reception screen display process of causing the display to display a specification reception screen that receives specification of one output means from among a first output means configured to output printing of a code indicating said electronic payment information and a second output means configured to output transmission of said electronic payment information; and a specified output means acquisition process of acquiring a specified output means that is said output means specified on said specification reception screen. The application software according to the present invention causes the terminal computer to execute said electronic payment information output process of generating said code and outputting it to a printing device based on the fact that said specified output means is said first output means, and causes the terminal computer to execute said electronic payment information output process of transmitting said electronic payment information to an electronic payment terminal based on the fact that said specified output means is said second output means.

[0022] There are various facility-installed terminals including: facility-installed terminals having communication means such as communication means via the Internet, communication means via a local area network (LAN), communication means by proximity wireless communication, and communication means via a communication cable; and facility-installed terminals not having any of these communication means. An operator selects an optimal output means in initial setting in consideration of the specifications, performance, and peripheral devices of the facility-installed terminal. Selection of the optimal output means can be performed for each facility-installed terminal. That is, even when a plurality of types of facility-installed terminals with different specifications are installed in a facility, electronic payment information can be output by the optimal output means corresponding to the specifications. Therefore, the application software according to the present invention can be compatible with various facility-installed terminals. [Effects of the Invention]

[0023] The electronic payment support system and the application software according to the present invention can support electronic payment in cooperation with an invoice creation system, and can facilitate introduction, maintenance and management. [Brief Description of the Drawings]

[0024] [Figure 1]FIG. 1 is a functional block diagram of an electronic payment support system 10 according to an embodiment of the present invention. [Figure 2] FIG. 2(A) is a diagram showing an article table, and FIG. 2(B) is a diagram showing a template image. [Figure 3] FIG. 3 is a flowchart showing initialization processing executed in a facility-installed terminal 20. [Figure 4] FIG. 4 is a flowchart showing initialization processing executed in the facility-installed terminal 20. [Figure 5] FIG. 5 is a menu screen 60 and a receipt screen 70 displayed on a display 25 of the facility-installed terminal 20. [Figure 6] FIG. 6(A) is a first coordinate setting screen 71, FIG. 6(B) is another setting screen 73, and FIG. 6(C) is a product master import screen 90. [Figure 7] FIG. 7 is a second coordinate setting screen 80. [Figure 8] FIG. 8 is a second coordinate setting screen 80 on which a designation frame 89 is arranged. [Figure 9] FIG. 9 is a flowchart of payment support processing. [Figure 10] FIG. 10 is a flowchart of payment support processing. [Figure 11] FIG. 11(A) is a confirmation screen 101, FIG. 11(B) is an article purchase screen 102, and FIG. 11(C) is an inquiry screen 103. DESCRIPTION OF EMBODIMENTS

[0025] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings as appropriate. It goes without saying that these embodiments are merely one aspect of the electronic payment support system according to the present invention, and the embodiments may be modified without altering the essence of the present invention. Furthermore, the execution order of processes (steps) in the flowcharts shown in Figures 3, 4, 9, and 10 is merely an example, and the execution order of each process may be changed as appropriate, other processes may be added, or parts of the processes may be omitted without altering the essence of the present invention.

[0026] Figure 1 is a functional block diagram of an electronic payment support system 10 according to one embodiment of the present invention.

[0027] [Overview of Electronic Payment Support System 10]

[0028] The electronic payment support system 10 shown in Figure 1 is a system that is installed in addition to existing invoice creation systems, such as medical billing computers, that do not support electronic payments, thereby enabling them to support electronic payments. In other words, the electronic payment support system 10 is a system that enables electronic payments without changing the specifications of existing invoice creation systems.

[0029] In this embodiment, an example is described in which the electronic payment support system 10 supports electronic payments to a claims processing computer operated in a medical facility 11 such as a clinic, hospital, or dental office. In other words, the electronic payment support system 10 is described using a claims processing computer, which is an existing invoice creation system, as an example. However, the electronic payment support system 10 may also be introduced to industries that use invoice creation systems other than claims processing computers. Such industries include, for example, "sports facility provision businesses" such as golf courses and sports clubs, "accommodation businesses" such as hotels and inns, "lifestyle-related service businesses" such as hot springs and public baths, "food and beverage service businesses" such as restaurants and cafes, "goods rental businesses" such as car rental businesses, "wedding and funeral businesses" such as wedding halls and funeral halls, and "wholesale businesses" and "retail businesses" such as distribution businesses, shops, bookstores, and antique dealers. In other words, the electronic payment support system 10 can be used in a variety of facilities such as golf courses, sports clubs, hotels, inns, hot springs, public baths, restaurants, cafes, car rental companies, wedding venues, funeral homes, shops, bookstores, and antique dealers.

[0030] The electronic payment support system 10 includes a linked application 33 and an electronic payment terminal 40.

[0031] The linked application 33 is a program implemented on the facility-installed terminal 20 located in the medical facility 11. The linked application 33 is a type of application software. The electronic payment terminal 40 is installed in the medical facility 11 together with the facility-installed terminal 20.

[0032] The facility-installed terminal 20 is an existing personal computer installed for the purpose of creating medical claim forms (medical fee statements). In other words, the facility-installed terminal 20 is a so-called medical claim computer. One facility-installed terminal 20 is installed in one medical facility 11, or multiple facility-installed terminals 20 are installed in one medical facility 11.

[0033] The electronic payment terminal 40 is a terminal for performing electronic payments such as credit card payments, QR code (registered trademark) payments, prepaid card payments, and IC card payments. The electronic payment terminal 40 is, for example, an existing product.

[0034] The linked application 38 and the electronic payment terminal 40 are provided to the medical operators of the medical facilities 11 by the operating company. The operating company provides electronic payment support services to the medical operators through the linked application 38 and the electronic payment terminal 40, or sells the linked application 38 and the electronic payment terminal 40 to the medical operators.

[0035] [Facility-installed terminal 20]

[0036] The facility-installed terminal 20 comprises a terminal controller 21, an input interface 24, a display 25, and a communication interface 26. The input interface 24 can be a keyboard, mouse, microphone, or touch sensor. If the input interface 24 is a touch sensor, then the input interface 24 and the display 25 are a so-called touch panel.

[0037] The terminal controller 21 includes a central processing unit (CPU) 22 and a terminal memory 23. The CPU 22 corresponds to the "terminal computer" as described in the claims.

[0038] The terminal memory 23 stores the operating system OS 31, the claims processing program 32, the linked application 33, and Excel 34. The OS 31 includes an API (Application Programming Interface). The OS 31, the claims processing program 32, the linked application 33, and Excel 34 are executed by the CPU 22. In addition to the OS 31, the claims processing program 32, the linked application 33, and Excel 34, the terminal memory 23 further stores information necessary for their execution, as well as information such as communication addresses necessary for communication with the electronic payment terminal 40 and the printer 12. The claims processing program 32 corresponds to the "invoice creation program" described in the claims. The linked application 33 corresponds to the "application software" described in the claims. The printer corresponds to the "printing device" described in the claims.

[0039] Furthermore, the terminal memory 23 stores the item list data as Excel data.

[0040] Figure 2(A) is the item list shown in the item list data. Figure 2(B) is a template image of the item list.

[0041] As shown in Figure 2(A), the inventory list has columns labeled "Item Name" and columns labeled "Item Price [yen]". Each row (record) associates the name of an item with the price of that item. In the inventory list shown in Figure 2(A), the item name "Children's Toothbrush" is associated with the item price "300 yen", and the item name "Face Towel" is associated with the item price "500 yen".

[0042] The linked application 33 has template image data that shows a template image for creating an item list (see Figure 2(B)). The template image is, for example, a table in which each field of the item list shown in Figure 2(A) is left blank.

[0043] Furthermore, the linked application 33 has an OCR function. The OCR function is a function that, based on image data and location information being input as arguments, reads the characters located at the location information in the image data and outputs the read characters as a return value. The OCR function may also be a class that generates a string as an object by taking image data and location information as input. Alternatively, the OCR function may be stored in the terminal memory 23 separately from the linked application 33 as an OCR program. In that case, the linked application 33 passes the path and location information indicating the image data to the OCR program via the OS 31 and obtains the path indicating the string output by the OCR program via the OS 31.

[0044] The communication interface 26 shown in Figure 1 manages the input and output of information. Furthermore, the communication interface 26 performs input and output of information in a data format corresponding to a predetermined communication protocol, such as the Internet Protocol.

[0045] The communication interface 26 includes all or one or more of the following communication interfaces: a communication interface connected to the Internet 16 via a gateway device (not shown), a communication interface connected to the LAN 15 or WAN, and a communication interface connected to a communication cable. In other words, the facility-installed terminal 20 may have any type of communication interface. The electronic payment support system 10 provides electronic payment services to various facility-installed terminals 20.

[0046] In the example shown in Figure 1, one facility-installed terminal 20 is connected to the internet 16 via a communication interface 26. Another facility-installed terminal 20 is connected to the LAN 15 and printer 12 via a communication interface 26.

[0047] [Electronic payment terminal 40]

[0048] The electronic payment terminal 40 comprises a payment controller 41, a touch panel 44, a camera 45, a card reader 100, and a communication interface 46. The payment controller 41 corresponds to the "controller" described in the claims.

[0049] The payment controller 41 has a CPU 42, which is a central processing unit, and a payment memory 43. The payment memory 43 stores an operating system OS 47, a payment program 48, and a reading program 49. The reading program 49 is a program that reads information from a QR code (registered trademark).

[0050] The payment memory 43 stores the OS 47, the payment program 48, and the reading program 49, as well as information necessary for the execution of these programs, information such as communication addresses necessary for communication with the facility terminal 20, printer 12, and payment server 14, and a browser. The payment server 14 is a web server operated by an electronic payment service provider and is a server that provides electronic payment services.

[0051] The touch panel 44 has a display and a transparent sheet-like touch sensor superimposed on the display. The touch panel 44 receives screen data input from the payment controller 41 and displays an input screen including icons and a QR code (registered trademark). The touch panel 44 also receives input such as icon selection from the operator of the medical facility 11 or the patient making the payment. The position information indicating the icon selected by the operator, etc. on the touch panel 44 is input to the payment controller 41.

[0052] Camera 45 is a so-called digital camera having multiple image sensors. Camera 45 inputs the image data it generates through imaging to the payment controller 41. Camera 45, for example, images a code printed by printer 12. The code has a graphic that allows information to be read, such as a QR code (registered trademark) or a barcode. The payment controller 41 obtains the electronic payment information necessary for electronic payment from the image data of the code. Camera 45 and reading program 49 correspond to the "reading device" described in the claims.

[0053] The card reader 100 is a device that reads information such as user IDs from IC chips embedded in credit cards or IC cards used for electronic payments.

[0054] The communication interface 46 includes a communication interface connected to the Internet 16 via a gateway device (not shown), a communication interface connected to the LAN 15 or WAN, and a communication interface connected to a communication cable. The communication interface 26 connected to the LAN 15 includes wireless LAN such as Wi-Fi or Bluetooth®. In other words, the electronic payment terminal 40 is compatible with various communication methods and can communicate with the payment server 14 via the Internet 16.

[0055] [Printer 12]

[0056] Printer 12 is pre-installed in the medical facility 11 for printing medical claim forms (statements of medical services). Printer 12 is connected to the facility terminal 20 via a communication cable or LAN 15. Based on the print data entered from the facility terminal 20, Printer 12 prints medical claim forms and codes.

[0057] [User terminal 50]

[0058] Patients who pay medical fees possess a user terminal 50. The user terminal 50 is a smartphone or tablet, etc. The user terminal 50 is equipped with a terminal controller 51, a touch panel 54, a communication interface 55, and a camera 56.

[0059] The terminal controller 51 has a CPU 52, which is a central processing unit, and memory 53. The memory 53 stores the payment application 57. The payment application 57 is application software for performing electronic payments.

[0060] Memory 53 stores the payment application 57, as well as the OS and browser. Furthermore, memory 53 stores information necessary for the execution of programs such as the payment application, and information such as communication addresses necessary for communication with the payment server (not shown).

[0061] The touch panel 54 has a display and a transparent sheet-like touch sensor superimposed on the display. The camera 56 is a so-called digital camera having multiple image sensors. The communication interface 55 includes a communication interface for connecting to a mobile communication network and a communication interface for connecting to a LAN access point. The user terminal 50 can connect to the Internet 16 via the mobile communication network or LAN.

[0062] [Operation of Electronic Payment Support System 10]

[0063] The following describes the processes that the OS 31, claims processing program 32, and linked application 33 of the facility-installed terminal 20 shown in Figure 1 cause the CPU 22 to execute, and the processes that the payment program 48 of the electronic payment terminal 40 causes the CPU 42 to execute. The processes that the OS 31, claims processing program 32, and linked application 33 cause the CPU 22 to execute are also the processes that the facility-installed terminal 20, terminal controller 21, and CPU 22 execute. In addition, the processes that the payment program 48 causes the CPU 42 to execute are also the processes that the electronic payment terminal 40, payment controller 41, and CPU 42 execute.

[0064] [Initial setup process]

[0065] Figures 3 and 4 are flowcharts of the initial setup process that the linked application 33 has the CPU 22 execute when the electronic payment support system 10 is introduced to the medical facility 11. Figure 5 shows the menu screen 60 and the claim screen 70 displayed on the display 25 of the facility-installed terminal 20. Figure 6(A) shows the first coordinate setting screen 71, Figure 6(B) shows other setting screens 73, and Figure 6(C) shows the product master import screen 90. Figure 7 shows the second coordinate setting screen 80 before the operator specifies the coordinates. Figure 8 shows the second coordinate setting screen 80 after the operator specifies the coordinates.

[0066] As shown in Figure 3, an operator, such as an office worker or nurse at the medical facility 11, operates the facility-installed terminal 20 and inputs a startup command to launch the linked application 33 (S10). The startup command is, for example, the selection of an icon. Upon receiving the startup command, the OS 31 launches the linked application 33 (S11). The launched linked application 33 inputs a screen display command and a path indicating screen data to the OS 31 (S12). The screen display command is, for example, a command accompanied by a path indicating screen data. The screen data is menu screen data. The path is information indicating the memory area (address) where the screen data is stored. The OS 31 inputs the menu screen data indicated by the accompanying path to the display 25 according to the input screen display command (command), and displays the menu screen 60 (see Figure 5) on the display 25 (S13).

[0067] As shown in Figure 5, the menu screen 60 has a "screen capture" icon 61, an "item purchase" icon 62, a "set coordinates for characters to read" icon 63, and an "other settings" icon 64.

[0068] The "Screen Capture" icon 61 is an icon that accepts instructions to acquire screen data from the medical claim screen 70. The "Screen Capture" icon 61 is also an icon that accepts instructions to generate electronic payment information from the medical claim.

[0069] The "item purchase icon" 62 is an icon selected by the operator when a patient purchases items sold at the medical facility 11, such as masks, toothbrushes, and towels.

[0070] The "Setting the coordinates of the characters to be read" icon 63 and the "Other settings" icon 64 are icons selected during the initial setup process shown in Figure 3.

[0071] As shown in Figure 3, when the linked application 33 receives the operator's selection of the "Set Coordinates of Characters to Read" icon 63 on the menu screen 60 (S14), it inputs a screen display instruction and a path indicating screen data to the OS 31 (S15). The screen display instruction is, for example, a command accompanied by a path indicating screen data. The screen data is the first coordinate setting screen data. The OS 31 displays the first coordinate setting screen 71 (see Figure 6(A)) indicated by the first coordinate setting screen data on the display 25 according to the input screen display instruction (S16).

[0072] As shown in Figure 6(A), the first coordinate setting screen 71 has the text "After displaying the receipt, please select the OK icon" and an "OK" icon 72. As shown in Figure 3, the operator operates the facility terminal 20 according to the text displayed on the first coordinate setting screen 71 to start the receipt program 32 (S17). Specifically, the operator selects a previously saved receipt as a sample to start the receipt program 32. The started receipt program 32 inputs a screen display instruction and a path indicating the screen data to the OS 31. The screen display instruction is, for example, a command that includes a path indicating the receipt screen data. The OS 31 displays the receipt screen 70 (see Figure 5) indicated by the receipt screen data on the display 25 according to the input screen display instruction (S19).

[0073] The receipt screen 70 (see Figure 5) window and the first coordinate setting screen 71 (see Figure 6(A)) window are displayed side by side on the display 25. With the receipt screen 70 displayed on the display 25, the operator selects the "OK" icon 72 using an input interface 24 such as a mouse (S20). Based on the operator's selection of the "OK" icon 72 (S20), the linked application 33 inputs an information request to the OS 31 (S21). This information request is a command that requests the program ID indicating the program that instructed the display of the window currently shown on the display 25, and the path indicating the screen data of that window.

[0074] Based on the receipt of the information request (S21), OS31 returns the program ID of the claim program 32 and a path indicating the claim screen data to the linked application 33 (S22). The program ID of the claim program 32 corresponds to the "program identification information indicating the invoice creation program" described in the claims. The processing in step S22 corresponds to the "identification information acquisition process" described in the claims.

[0075] The linked application 33 stores the received program ID and the path indicating the receipt screen data in the terminal memory 23 (S23). The linked application 33 generates second coordinate setting screen data using the receipt screen data indicated by the path (S24). Specifically, the linked application 33 generates second coordinate setting screen data by inputting the receipt screen data into pre-existing screen format data. The linked application 33 inputs a screen display instruction and the path indicating the screen data to the OS 31 (S25). The screen display instruction is, for example, a command accompanied by a path indicating the screen data. The screen data is data indicating the second coordinate setting instruction screen 80 (see Figure 7). The OS 31 displays the second coordinate setting screen 80 (see Figure 7) indicated by the second coordinate setting screen data on the display 25 according to the input screen display instruction (S26).

[0076] As shown in Figure 7, the second coordinate setting screen 80 has a receipt image 88, a "Patient No." icon 81, a "Patient Name" icon 82, an "Insurance Medical Treatment Amount" icon 83, a "Private Medical Treatment Amount" icon 84, a "Goods Cost" icon 85, a "Total Settlement Amount" icon 86, and an "OK" icon 87. The receipt image 88 is an image displayed within the second coordinate setting screen 80 and has the same content as the receipt screen 70 displayed in a window (see Figure 5).

[0077] When the operator specifies the position (coordinates) in the claim image where the linked application 33 will read the patient number, they select the "Patient No." icon 81 using the input interface 24. As shown in Figure 3, based on the selection of the "Patient No." icon 81 (S27), the linked application 33 inputs a path and screen display instruction to the OS 31 indicating the second coordinate setting screen 80 (see Figure 8) on which the designation frame 89 is overlaid (S28). The screen display instruction is, for example, a command accompanied by a path indicating the data of the second coordinate setting screen. The OS 31 displays the second coordinate setting screen 80 on the display 25 with the designation frame 89 overlaid (S29). As shown in Figure 8, the operator moves the designation frame 89 to the position where the patient number "0123456789" is displayed using the input interface 24. The initial position of the designation frame 89 is a predetermined position, such as the center of the claim image 88.

[0078] The operator moves the designated frame 89 to the position where the "Patient No." is displayed, and then uses the input interface 24 to select the "OK" icon 87. The position where the "Patient No." is displayed corresponds to the "first position" described in the claims. The patient No. "0123456789" corresponds to user identification information.

[0079] As shown in Figure 3, the linked application 33 acquires location information (coordinates) and stores it in the terminal memory 23 based on the selection of the "OK" icon 87 (S30) (S31). The location information is indicated by (X,Y) coordinates with the upper left corner of the receipt image 88 as the reference position (origin). The location information (coordinates) of the position where "Patient No." is displayed corresponds to the "first location information" described in the claims. The processing in step S30 corresponds to the "first location information acquisition process" described in the claims.

[0080] The operator, in the same manner as specifying the position of the patient number, selects the "patient name" icon 82, the "insurance medical treatment amount" icon 83, the "private medical treatment amount" icon 84, the "cost of goods" icon 85, and the "total settlement amount" icon 86 in order to specify the positions of the patient name, insurance medical treatment amount, private medical treatment amount, cost of goods, and total settlement amount (S27~S31). The position where the "patient name" is displayed corresponds to the "first position" described in the claims. The patient name "Yamada Taro" corresponds to the "user identification information" described in the claims. The position where the "total cumulative amount" is displayed corresponds to the "second position" described in the claims. The total billing amount of "3000 yen" corresponds to the "billing amount" and "medical fee" described in the claims. The position information (coordinates) of the position where the "total billing amount" is displayed corresponds to the "second position information" described in the claims. The process of storing the total billing amount in the terminal memory 23 in step S30 corresponds to the "second position information acquisition process" described in the claims.

[0081] Based on having obtained location information such as patient number, patient name, insurance medical treatment amount, private medical treatment amount, goods cost, and total settlement amount, the linked application 33 inputs a screen display instruction and a path indicating screen data to the OS 31 (S32). The screen display instruction is, for example, a command that includes menu screen data. The OS 31 displays the menu screen 60 (see Figure 5) again on the display 25 according to the screen display instruction (S33).

[0082] The operator selects the "Other Settings" icon 64 on the menu screen 60 (see Figure 5) using the input interface 24 (S34). Based on the selection of the "Other Settings" icon 64 (S34), the linked application 33 inputs a screen display instruction and a path indicating screen data to the OS 31 (S35). The screen display instruction is, for example, a command accompanied by a path indicating other settings screen data. The OS 31 displays the other settings screen 73 (see Figure 6(B)) on the display 25 according to the input screen display instruction (S36). The processing in steps S35 and S36 corresponds to the "designated reception screen display processing" described in the claims.

[0083] As shown in Figure 6(B), the other settings screen 73 has a text box 74 associated with the text “Customer Code” and a text box 75 associated with the text “Store Code”. The operator uses the input interface 24 to enter the customer code into text box 74 and the store code into text box 75. The customer code and store code are, for example, identification information used by the provider of the electronic payment support system 10 to identify medical service providers and medical facilities 11.

[0084] Furthermore, the other settings screen 73 has a pull-down menu 76 associated with the text "Data Linkage Method" and a pull-down menu 77 associated with the text "Printer Name". The pull-down menu 76 accepts the selection of a means for transferring electronic payment information to the electronic payment terminal 40. When the operator selects the pull-down menu 76, all or some of the following options are displayed: "Internet", "Wi-Fi", "Bluetooth", "Wired LAN", "Communication Cable", and "QR Code Printing". The linkage application 33 requests all types of communication means available to the facility-installed terminal 20 from the OS 31, and displays the communication means returned by the OS 31 as options in the pull-down menu 76. In the example shown in Figure 6(B), an example is shown where "QR Code Printing" is selected by the operator. "QR Code Printing" corresponds to the "first output means" described in the claims. "Internet", "Wi-Fi", "Bluetooth", "Wired LAN", and "Communication Cable" correspond to the "second output means" described in the claims. Other settings screens 73 correspond to the "designated reception screen" described in the claims. The "QR code printing" specified by the operator corresponds to the "designated output means" described in the claims.

[0085] If the operator selects "QR code printing" as a means of passing electronic payment information to the electronic payment terminal 40, they select the name of the printer to print the code using the pull-down menu 77. For example, the linked application 33 requests the name of the printer (printer name) of the printer that is communicably connected to the facility terminal 20 from the OS 31, and displays the printer name returned by the OS 31 as an option in the pull-down menu 76. In the example shown in Figure 6(B), the printer name "Printer ABC" is selected in the pull-down menu 77.

[0086] The other settings screen 73 further includes the "Import Product Master" icon 78, the "Product Master Template" icon 79, and the "OK" icon 69.

[0087] If the operator wants to import an item list created in Excel (see Figure 2(A)), they select the "Import Product Master" icon 78. If there is no existing item list created in Excel, the operator selects the "Product Master Template" icon 79.

[0088] As shown in Figure 3, the linked application 33 accepts input of a customer code in text box 74, input of a store code in text box 75, selection of a data linkage method via pull-down menu 76, and selection of a printer name via pull-down menu 77 (S37).

[0089] As shown in Figure 4, the linked application 33 accepts the selection of either the "Import Product Master" icon 78 or the "Product Master Template" icon 79 on the other settings screen 73 (see Figure 6(B)) (S38). The linked application 33 inputs a screen display instruction and a path indicating the screen data to the OS 31 (S39). The screen display instruction is, for example, a command accompanied by a path indicating the screen data. The screen data is either product master import screen data or product master template screen data.

[0090] If the screen data indicated by the path is product master import screen data (S41: Import), OS31 displays the product master import screen 90 (see Figure 6(C)) on display 25 (S42).

[0091] As shown in Figure 6(C), the product master import screen 90 has the text "Open the item list data in Excel, select the item list and 'copy' it, then select 'OK'," and an "OK" icon 91.

[0092] The operator operates the input interface 24 of the facility-installed terminal 20 to input a startup command to open the item list data in Excel 34 (S43). Inputting the startup command is, for example, selecting an icon. Upon receiving the startup command, Excel 34 inputs a screen display command and a path indicating the screen data to OS 31 (S44). The screen display command is, for example, a command accompanied by a path indicating the screen data. The screen data is the item list screen data, which is a screen containing the item list (see Figure 2). OS 31 displays the item list screen on the display 25 according to the input screen display command (S45).

[0093] The operator selects the entire item list (see Figure 2(A)) on the item list screen (see Figure 2(A)) according to the instructions displayed on the product master import screen 90, and selects the copy icon (not shown) (S46). Excel 34 inputs the path indicating the selected item list data into OS 31 (S47).

[0094] After the operator copies the item list (see Figure 2(A)), they select the "OK" icon 91 on the product master import screen 90 (see Figure 6(C)) (S48).

[0095] Based on the acceptance of the selection of the "OK" icon 91 (S48), the linked application 33 inputs a path request indicating a request for copy data to the OS 31 (S49). The path request is, for example, a command. The OS 31 returns a path indicating the copy data (item list data) to the linked application 33 according to the input path request (command) (S50). The linked application 33 stores the item list data indicated by the acquired path in the terminal memory 23 (S51). The item list data corresponds to the "item information" described in the claims. The processing in step S51 corresponds to the "item information import processing" described in the claims.

[0096] On the other hand, if the icon selected by the operator on the other settings screen 73 (see Figure 6(B)) is the "product master template" icon 79, and the screen data indicated by the path entered into OS31 is data indicating the product master template screen (S41: template), OS31 displays the product master template screen (not shown) on the display 25 (S52). The product master template screen is a screen that has the template image and "OK" icon shown in Figure 2(B). The operator enters the name and amount of the items in each field of the template image (S53) to create an item list. After creating the item list, the operator selects the "OK" icon (S54).

[0097] Based on the selection of the "OK" icon on the product master template screen (not shown) (S54), the linked application 33 stores the item list data, which represents the item list created by the operator, in the terminal memory 23 (S55). Also, based on the selection of the "OK" icon on the product master template screen (not shown) (S54), the linked application 33 inputs a screen display instruction and a path indicating the screen data to the OS 31 (S56). The screen display instruction is, for example, a command accompanied by a path indicating the screen data. The screen data is other setting screen data. The OS 31 displays the other setting screen 73 (see Figure 6(B)) again on the display 25 according to the screen display instruction (S57).

[0098] On the other settings screen 73, the operator enters the customer code and other information, and then selects the "OK" icon 69 (S58). Based on the selection of the "OK" icon 69 (S58), the linked application 33 stores the setting information, including the customer code, store code, data linkage method, and printer name, in the terminal memory 23 (S59), and terminates the initial setup process (end). The process in step S59 corresponds to the "specified output means acquisition process" described in the claims.

[0099] [Payment support processing]

[0100] Figures 9 and 10 are flowcharts of the payment support processing performed by the facility-installed terminal 20 and the electronic payment terminal 40. Figure 11(A) is the confirmation screen 101. Figure 11(B) is the goods purchase screen 102. Figure 11(C) is the inquiry screen 103.

[0101] As shown in Figure 9, the operator inputs startup commands for the claims processing program 32 and the linked application 33 using the input interface 24 of the facility-installed terminal 20 (S71, S72). Based on the input commands, the OS 31 starts the claims processing program 32 and the linked application 33.

[0102] The launched medical claim program 32 inputs a screen display instruction and a path indicating screen data to the OS 31 (S73). The screen display instruction is, for example, a command accompanied by a path indicating medical claim screen data. Meanwhile, the launched linked application 33 inputs a screen display instruction and screen data to the OS 31 (S74). The screen display instruction is, for example, a command accompanied by a path indicating menu screen data. The medical claim screen 70 corresponds to the "invoice screen" described in the claims. The medical claim screen data corresponds to the "invoice screen data" described in the claims.

[0103] OS31 displays the claim form screen 70 (see Figure 5) on the display 25 according to the input screen display instructions (S73) (S75). Note that in step S75, the claim form screen 70 displayed on the display 25 is in an initial state with no patient number or other information entered.

[0104] Meanwhile, OS31 displays the menu screen 60 (see Figure 5) on the display 25 according to the input screen display instruction (S74) (S76). The menu screen 60 is displayed on the display 25 alongside the receipt screen 70, either side-by-side or above and below it.

[0105] The operator enters the patient number and other information into each blank field (text box) on the claim screen 70 (S77) to create the claim. The claim program 32 receives the operator's input (S77) and generates the claim screen data (S78).

[0106] After creating the medical claim form, the operator selects the "screen capture" icon 61 on the menu screen 60 (see Figure 5) (S79). The process in step S79 corresponds to the "output instruction" described in the claims.

[0107] Based on the acceptance of the selection of the "screen capture" icon 61 (S79), the linked application 33 reads the program ID stored in the terminal memory 23 in step S23 (see Figure 3) from the terminal memory 23 (S80). The linked application 33 inputs the read program ID and a screen data acquisition instruction to the OS 31 (S81). The screen data acquisition instruction is, for example, a command accompanied by a program ID, which requests screen data of the screen displayed on the display 25 according to the instructions of the program indicated by the program ID.

[0108] OS31 passes a path indicating the receipt screen data to the linked application 33 according to the input screen data acquisition instruction and program ID (S82). The processing in step S82 corresponds to the "screen data acquisition processing" described in the claims.

[0109] The linked application 33 passes the receipt screen data indicated by the acquired path and the location information stored in the terminal memory 23 in step S31 (see Figure 3) as arguments to the OCR function and obtains a string as a return value (S83). This string may be, for example, "0123456789" associated with the characters "Patient No.", "Yamada Taro" associated with the characters "Patient Name", or "3000 yen" associated with the characters "Total Billing Amount". The following explanation will use the strings indicating "Patient No.", "Patient Name", and "Total Billing Amount" as examples. The patient No. "0123456789" and patient name "Yamada Taro" correspond to the "user identification information" described in the patent claims. The total billing amount "3000 yen" corresponds to the "billing amount" described in the patent claims.

[0110] The linked application 33 inputs a screen display instruction and the path to the screen data to the OS 31 (S84). The screen display instruction is, for example, a command that includes a path indicating the confirmation screen data. The OS 31 displays the confirmation screen 101 (see Figure 11(A)) indicated by the confirmation screen data on the display 25 according to the input screen display instruction (S85). The processing in steps S84 and S85 corresponds to the "confirmation screen display processing" described in the claims.

[0111] As shown in Figure 11(A), the confirmation screen 101 is a screen that contains the string obtained in step S83. In the example shown in Figure 11(A), the confirmation screen 101 contains "0123456789" associated with the text "Patient No," the text "Yamada Taro" associated with the text "Patient Name," and the text "3000 yen" associated with the text "Total Billing Amount."

[0112] The confirmation screen 101 further includes an "OK" icon 98 and an "NG" icon 99. The operator selects the "OK" icon 98 based on whether the patient number, patient name, and total billing amount displayed on the confirmation screen 101 match the patient number, patient name, and total billing amount shown on the medical claim. The operator selects the "NG" icon 99 based on whether the patient number, patient name, and total billing amount displayed on the confirmation screen 101 do not match the patient number, patient name, and total billing amount shown on the medical claim. The "OK" icon 98 corresponds to the "confirmation icon" described in the claims.

[0113] As shown in Figure 9, the linked application 33 accepts the selection of either the "OK" icon 98 or the "NG" icon 99 on the confirmation screen 101 (S86). The linked application 33 determines whether the selected icon is the "OK" icon 98 or the "NG" icon 99 (S87). If the linked application 33 determines that the selected icon is the "NG" icon 99 (S87:NG), it repeats the process from step S81 onwards. In other words, the linked application 33 retrieves the medical claim image data again and retrieves the string from the retrieved medical claim image again.

[0114] When the linked application 33 determines that the selected icon is the "OK" icon 98 (S87: OK), it stores the "Patient No: 0123456789", "Patient Name: Yamada Taro", and "Total Billing Amount: 3000 yen" obtained in step S83 in the terminal memory 23 as electronic payment information (S88). The process in step S88 corresponds to the "first acquisition process" described in the claims.

[0115] If the patient is purchasing items, the operator selects the "Purchase Items" icon 62 on the menu screen 60 (see Figure 5) (S89). The linked application 33 determines whether the "Purchase Items" icon 62 has been selected or not (S90).

[0116] When the linked application 33 determines that the "Purchase Item" icon 62 has been selected (S90: Yes), it inputs a screen display instruction and a path indicating the screen data to the OS 31 (S91). The screen display instruction is, for example, a command that includes a path indicating the purchase item screen data. The OS 31 displays the purchase item screen 102 (see Figure 11(B)) indicated by the purchase item screen data on the display 25 according to the input screen display instruction (S92).

[0117] As shown in Figure 11(B), the item purchase screen 102 has "0123456789" indicating the patient number, "Yamada Taro" indicating the patient name, an "item selection" icon 92 associated with the text of the item to be purchased, a display area 93 where the price of the item is displayed, and a "confirm" icon 94. The operator selects the "item selection" icon 92 on the item purchase screen 102.

[0118] As shown in Figure 10, based on the selection of the "Item Specification" icon 92 (S93), the linked application 33 inputs a screen display instruction and a path indicating screen data to the OS 31 (S94). The screen display instruction is, for example, a command accompanied by a path indicating screen data. The screen data is the item list data stored in the terminal memory 23 in step S51 (see Figure 4). The OS 31 displays the item list screen 102, including the item list (see Figure 2(A)), on the display 25 according to the screen display instruction (S95). The operator specifies the name of the item to be purchased by the patient on the item list screen 102 (S96). The processes in steps S94 and S95 correspond to the "item list display process" described in the claims. The process in step S96 corresponds to the "user item specification" described in the claims.

[0119] The linked application 33 retrieves the item name specified by the operator on the item list screen 102 and the item price associated with that item name from the item list (S97). The linked application 33 inputs a screen display instruction and a path indicating the screen data to the OS 31 (S98). The screen display instruction is, for example, a command accompanied by a path indicating the screen data. The screen data is the item purchase screen data that reflects the item name and item price obtained in step S93. The OS 31 updates and displays the item purchase screen 102 (see Figure 11(B)) that reflects the item name and item price according to the input screen display instruction (S99). On the item purchase screen 102, the operator specifies all the items the patient will purchase and then selects the "Confirm" icon 94.

[0120] Based on the selection of the "Confirm" icon 94 on the item purchase screen 102 (S100), the linked application 33 updates the electronic payment information stored in the terminal memory 23 in step S88 (see Figure 9) (S101). Specifically, the linked application 33 includes the name of the item purchased by the patient and the purchase price in the electronic payment information, and updates the total billing amount by adding the purchase price of the item to the total billing amount. For example, a total billing amount of "3000 yen" is updated to "3800 yen" by adding the purchase price of the item "800 yen". The process in step S101 corresponds to the "payment information generation process" described in the claims.

[0121] As shown in Figures 9 and 10, if the linked application 33 determines in step S90 that the "Purchase Item" icon 62 has not been selected (S90: No), it skips the processes from step S91 to step S98.

[0122] Next, the collaboration application 33 reads the data collaboration method stored in the terminal memory 23 in step S59 (see Figure 4) (S102). The collaboration application 33 determines whether the read data collaboration method is printing a code or transmission via LAN 15, the internet 16, or a communication cable (S103). If the collaboration application 33 determines that the data collaboration method is "transmission" (S103: transmission), it determines whether it is possible to transmit the electronic payment information using the specified transmission method (S104). For example, it inputs information indicating LAN 15, the internet 16, or a communication cable, and commands to inquire whether communication via these is possible to the OS 31.

[0123] If the linked application 33 determines that it can transmit electronic payment information (S104: Yes), it transmits the electronic payment information updated in step S101 to the electronic payment terminal 40 via the LAN 15, the internet 16, or a communication cable specified by the operator (S105). If the data linkage method is "Internet," the linked application 33 uploads the electronic payment information to a predetermined server (S105). The predetermined server is, for example, a web server operated by a service provider that provides data upload and download services. The electronic payment terminal 40 downloads and obtains the electronic payment information from the predetermined server (S105). If the data linkage method is "LAN" or "communication cable," the linked application 33 transmits the electronic payment information directly to the electronic payment terminal 40 via the LAN 15 or a communication cable (S105). The process in step S105 corresponds to the "electronic payment information output process" described in the claims.

[0124] If the linked application 33 determines that it cannot send electronic payment information (S104: No), it inputs a screen display instruction and a path indicating screen data to the OS 31 (S106). The screen display instruction is, for example, a command accompanied by a path indicating inquiry screen data. The OS 31 displays the inquiry screen 103 (see Figure 11(C)) indicated by the inquiry screen data on the display 25 according to the input screen display instruction (S107). The processing in steps S106 and S107 corresponds to the "inquiry screen display processing" described in the claims.

[0125] As shown in Figure 11(C), the inquiry screen 103 contains the text "Internet connection is not available," "Do you want to print the QR code for electronic payment information?", "Do you want to change to another transmission method?", and "Do you want to check your internet connection?". Note that the inquiry screen 103 shown in Figure 11(C) is an example where the operator has selected "Internet" as the data linkage method.

[0126] The inquiry screen 103 also includes a "Print QR Code" icon 95, an "Other Transmission Methods" icon 96, and an "Check Internet Connection" icon 97.

[0127] After the operator checks the settings of gateway devices such as routers and facility-installed terminals 20, for example, they select the "Check Internet Connection" icon 97 (S107). Although not shown in the flowchart, the linked application 33 re-executes the processes from step S104 onwards based on the selection of the "Check Internet Connection" icon 97.

[0128] If the operator determines that a problem with the communication line, including the internet 16, cannot be resolved immediately, they select the "Print QR Code" icon 95 on the inquiry screen 103 (S107). Although not shown in the flowchart, the linked application 33 executes the processes from step S108 onwards based on the selection of the "Print QR Code" icon 95. When the data linkage method selected by the operator is one of "Internet," "LAN," or "communication cable," the operator's instruction to select the "Print QR Code" icon 95 on the inquiry screen 103 corresponds to the "change instruction" described in the claims.

[0129] If the operator wishes to change to another transmission method, such as LAN15, they select the "Other transmission methods" icon 96 on the inquiry screen 103. Although not shown in the flowchart, the linked application 33 re-executes the process from step S104 onwards based on the selection of the "Other transmission methods" icon 96.

[0130] If the linked application 33 determines in step S103 that the data linkage method is "QR code printing" (S103: code printing), it generates printable code data that can read the electronic payment information based on the electronic payment information updated in step S101 (S108). For example, the linked application 33 has a conversion function that converts the information into printable code data. The linked application 33 calls this conversion function, passes the electronic payment information as an argument, and obtains the printable code data as a return value. The conversion function may also be an IC.

[0131] The linked application 33 sends the generated print data via the OS 31 to a printer whose printer name was stored in the terminal memory 23 in step S59 (see Figure 4) (S109). Although not shown in the flowchart, the printer that receives the print data prints the code indicated by the print data onto the paper. The process in step S109 corresponds to the "electronic payment information output process" described in the claims.

[0132] The operator operates the electronic payment terminal 40 (S110) to have the printed code captured by the camera 45.

[0133] Based on receiving the operator's imaging instruction (S110), the payment program 48 of the electronic payment terminal 40 instructs the camera 45 to image a code (S111). The payment program 48 passes the path of the image data generated by the camera 45 to the reading program 49, and the reading program 49 obtains a path indicating the electronic payment information read from the image data (S112). The process in step S112 corresponds to the "second acquisition process" described in the claims.

[0134] The payment program 48 stores the electronic payment information received in step S105, or acquired in step S112, in the payment memory 43 (S113). The payment program 48 uses the electronic payment information to execute the electronic payment process (S114). This electronic payment process is a process corresponding to various electronic payment methods. The process in step S105 in which the payment program 48 receives the electronic payment information corresponds to the "second acquisition process" described in the claims.

[0135] For example, a payment program 48 generates a QR code (registered trademark) containing the medical facility ID, which is the identification information of the medical facility 11, the payment amount, and the program ID of the payment application 57, and displays it on the touch panel 44. The patient operates their user terminal 50 to have the displayed QR code photographed by the camera 56. The OS (not shown) of the user terminal 50 launches the payment application 57 indicated by the program ID read from the captured image data of the QR code. The launched payment application 57 sends an HTTP request to the payment server 14 via the internet 16, containing the user ID stored in memory 53, the medical facility ID and payment amount read from the captured image data of the QR code. The payment server 14 performs the payment based on the user ID, medical facility ID and payment amount included in the received HTTP request. The payment server 14 sends a payment completion notification to the user terminal 50 and the electronic payment terminal 40 via the internet 16, indicating that the payment has been completed. For example, the electronic payment terminal 40 periodically sends an HTTP request containing the medical facility ID to the payment server and obtains a payment completion notification in the HTTP response to the HTTP request. The payment completion notification corresponds to the "electronic payment completion notification" described in the claims.

[0136] Alternatively, the patient operates the user terminal 50 to display a QR code (registered trademark) for electronic payment on the touch panel 54. The operator has the camera 45 of the electronic payment terminal 40 capture an image of the QR code (registered trademark) displayed on the user terminal 50. The payment program 48 of the electronic payment terminal 40 uses the reading program 49 to read information necessary for electronic payment, such as the user ID and the type of electronic payment, from the image data of the QR code (registered trademark). The payment program 48 sends an HTTP request containing the read user ID, its own medical facility ID, and the payment amount to the payment server 14 via the internet 16. The payment server performs the payment based on the user ID, medical facility ID, and payment amount included in the received HTTP request. The payment server 14 sends a payment completion notification to the user terminal 50 and the electronic payment terminal 40 via the internet 16, indicating that the payment has been completed.

[0137] Alternatively, the patient holds an IC chip-equipped credit card or IC card for electronic payment over the card reader 100 of the electronic payment terminal 40. The payment program 48 of the electronic payment terminal 40 uses proximity wireless communication with the credit card or IC card to read information necessary for electronic payment, such as the identification ID and the type of electronic payment. The payment program 48 sends an HTTP request containing the read identification ID, its own medical facility ID, and the payment amount to the payment server 14 via the internet 16. The payment server performs the payment based on the identification ID, medical facility ID, and payment amount included in the received HTTP request. The payment server 14 sends a payment completion notification to the electronic payment terminal 40 via the internet 16 indicating that the payment has been completed.

[0138] As shown in Figure 10, the payment program 48 of the electronic payment terminal 40 receives a payment completion notification sent by the payment server 14, displays the payment completion notification on the touch panel 44 (S115), and terminates the payment support process. Of the processes in step S115, the process of receiving the payment completion notification corresponds to the "completion notification reception process" described in the claims. Of the processes in step S115, the process of displaying the payment completion notification corresponds to the "payment completion notification output process".

[0139] Based on the operator's visual confirmation of the payment completion notification displayed on the touch panel 44 of the electronic payment terminal 40, the operator inputs an instruction to the facility-installed terminal 20 indicating that the payment has been completed (S116). For example, the operator inputs an instruction to the facility-installed terminal 20 indicating that the payment has been completed by selecting an icon on the completion instruction reception screen (not shown) displayed on the display 25 by the linked application 33. Based on the receipt of this instruction (S116), the linked application 33 stores the claim data, electronic payment information, and payment completion information in the terminal memory 23 in association with each other (S117), and terminates the payment support process (end).

[0140] [Effects of the Embodiment]

[0141] In this embodiment, the linked application 33 reads electronic payment information necessary for electronic payment, such as patient number, patient name, and payment amount, from the medical claim screen data, and passes the read electronic payment information to the electronic payment terminal 40. Therefore, electronic payment can be made available without changing the existing medical claim program 32. In other words, the electronic payment support system 10 according to this embodiment can support electronic payment in cooperation with the facility-installed terminal 20. Furthermore, since the electronic payment support system 10 enables electronic payment through the linked application 33, which is application software implemented on the facility-installed terminal 20, and the electronic payment terminal 40, it is easy to introduce and maintain.

[0142] In addition, in this embodiment, the linked application 33 reads electronic payment information such as the patient number from the screen data of the medical claim screen 70 displayed on the display 25 by the OS 31. Therefore, compared to reading electronic payment information from image data captured by a camera on a printed medical claim, the accuracy of reading electronic payment information can be improved.

[0143] In this embodiment, the operator can select the optimal output method from among "transmission via the Internet," "transmission via LAN," "transmission via communication cable," and "code printing" during the initial setup process, taking into consideration the specifications, performance, and peripheral equipment of the facility-installed terminal 20. The selection of the optimal output method can be performed for each facility-installed terminal 20. In other words, even if multiple types of facility-installed terminals 20 with different specifications are installed in the same medical facility 11, the electronic payment information can be output using the optimal output method according to the specifications. Therefore, the electronic payment support system 10 according to this embodiment can be made compatible with various facility-installed terminals 20.

[0144] In this embodiment, the linked application 33 reads the patient number, patient name, and total billing amount displayed at the position specified by the operator in the claim image 88 as information for electronic payment. Therefore, the linked application 33 can reliably obtain electronic payment information regardless of the format of the claim.

[0145] In this embodiment, if the patient number, patient name, and total billing amount displayed on the claim form match the patient number, patient name, and total billing amount read from the claim form, the operator selects the "OK" icon 98 on the confirmation screen 101 (see Figure 11(A)). This prevents electronic payments from being made based on incorrect electronic payment information.

[0146] In this embodiment, an item list is imported, and the operator simply selects the item name in the item list (S96), and the amount of that item is automatically reflected in the total billing amount. Therefore, electronic payment becomes even easier.

[0147] In this embodiment, if a communication failure occurs, the system can be switched to another communication method or to QR code printing, thus preventing delays in the payment process.

[0148] [Differentiation]

[0149] In one embodiment, the linked application 33 reads the characters displayed at the location indicated by the location information, based on the screen data of the claim screen 70 and the location information stored in the terminal memory 23 in step S31, as the patient number, patient name, and billing amount. However, the linked application 33 may read all the characters (including numbers) displayed on the claim screen 70, identify the characters among the read characters that match predetermined characters pre-stored in the terminal memory 23, and use the characters associated with the identified characters as the patient number, patient name, and billing amount. For example, the linked application 33 identifies characters among all the characters displayed on the claim screen 70 that match predetermined characters such as "patient name," "patient's name," or "patient's name," and stores the characters "Yamada Taro" associated with the identified characters as the patient name in the terminal memory 23. The predetermined characters may be pre-stored in the terminal memory 23, or characters entered by the operator during the initial setup process may be stored in the terminal memory 23 as predetermined characters.

[0150] In this embodiment, an example was described in which the linked application 33 obtains receipt screen data, which shows the receipt screen 70 (a window screen), from the OS 31 as invoice screen data (S82). However, the linked application 33 may also obtain screen data of the entire display 25, including the receipt screen 70 (window screen), from the OS 31 as invoice screen data.

[0151] Figure 1 illustrates an example where one electronic payment terminal 40 is installed in one medical facility 11. However, multiple electronic payment terminals 40 may be installed in one medical facility 11. In that case, the linked application 33 receives instructions from the operator and determines which electronic payment terminal 40 will transmit the electronic payment information.

[0152] The electronic payment support system 10 described in the embodiment may include a management server that manages a plurality of electronic payment terminals 40. The management server is operated by a service provider that provides electronic payment support services to healthcare providers. The service provider uses the management server to provide healthcare providers with a service that settles electronic payments of a type for which the healthcare provider has not concluded a contract with a payment service provider, on behalf of the healthcare provider. The service provider also provides healthcare providers with a management service that manages payment management information, including electronic payment information, payment completion notifications, and payment dates, in a management database. Furthermore, the service provider provides healthcare providers with maintenance services such as version upgrades of the linked application 33 and periodic inspections of the electronic payment terminals 40. [Explanation of Symbols]

[0153] 10. Electronic payment support system 11. Medical facilities 12. Printer 14. Payment Server 15..LAN 16. Internet 20...Facility-installed terminals 21. Terminal Controller 22..CPU 23. Terminal Memory 24. Input Interface 25...Display 26. Communication Interface 31...OS 32. Medical Claims Program 33...Linked Apps 40. Electronic payment terminals 41. Payment Controller 42..CPU 43. Payment Memory 44. Touch panel 45...Camera 46. ​​Communication Interface 50...User terminals 51. Terminal Controller 57. Payment app 60...Menu screen 61. Screen capture icon 62. "Purchase Items" icon 63. "Setting the coordinates of the characters to be read" icon 64. "Other Settings" icon 70...Medical claim screen 71...First Coordinate Setting Screen 73. Other settings screen 78. "Import Product Master" icon 79. "Product Master Template" icon 80...Second coordinate setting screen 89... Designated slot 90. Product Master Import Screen 95···"QR Code Printing" icon 96. "Other sending methods" icon 101...Confirmation screen 102... Item purchase screen 103...Inquiry screen

Claims

1. Application software implemented in a facility-installed terminal having terminal memory for storing the OS and invoice creation program, a terminal computer, a display, and an input interface, An electronic payment terminal having a communication interface, a reader, and a controller, The above application software is, Initialization processing including: an identification information acquisition process for acquiring program identification information indicating the above-mentioned invoice creation program; a first position information acquisition process for acquiring first position information indicating the first position, which is a first position on the invoice screen displayed on the display via the above-mentioned OS and for acquiring user identification information, which is received through the above-mentioned input interface; and a second position information acquisition process for acquiring second position information indicating the second position, which is a second position on the invoice screen and for acquiring the invoice amount, which is received through the above-mentioned input interface; Based on the receipt of an output instruction through the above input interface, a screen data acquisition process is performed in which an image data acquisition instruction is input to the OS, which includes the program identification information obtained in the above identification information acquisition process, and which requests invoice screen data showing the invoice screen displayed on the display via the OS by the invoice creation program indicated by the program identification information, and the invoice screen data is acquired from the OS. A first acquisition process that includes a process for acquiring the user identification information based on the above invoice screen data and the above first location information, and a process for acquiring the invoice amount based on the above invoice screen data and the above second location information, and acquires electronic payment information including the user identification information and the said invoice amount, The terminal computer is instructed to execute the electronic payment information output process that outputs the above electronic payment information. The above controller is A second acquisition process to acquire the electronic payment information output by the terminal installed in the above facility, Electronic payment processing using the above-mentioned electronic payment information obtained, Completion notification reception process, which receives the completion notification of electronic payment through the above communication interface, An electronic payment support system that performs a payment completion notification output process to output a payment completion notification.

2. The above application software is, A specification acceptance screen display process that displays a specification acceptance screen on the display for accepting the specification of one of the output means, which is either a first output means for printing a code indicating the above-mentioned electronic payment information or a second output means for transmitting the above-mentioned electronic payment information. The terminal computer is further instructed to execute a process to acquire the specified output means, which is the output means specified in the above-mentioned designated reception screen, The above application software is, Based on the fact that the designated output means is the first output means, the terminal computer is instructed to execute the electronic payment information output process that generates the code and outputs it to the printing device. The electronic payment support system according to claim 1, wherein, based on the above-mentioned designated output means being the above-mentioned second output means, the terminal computer is instructed to perform the above-mentioned electronic payment information output process for transmitting the above-mentioned electronic payment information to the above-mentioned electronic payment terminal.

3. The above application software is, The electronic payment support system according to claim 1 or 2, further comprising causing the terminal computer to execute a confirmation screen display process that displays a confirmation screen on the display having the user identification information and the billing amount obtained in the first acquisition process described above, and a confirmation icon.

4. The above initial setup process is: This process includes an item information import process that stores item information, including the item name and item price, in the terminal memory. The above application software is, Based on receiving the user's instruction to display item information through the above input interface, the system performs an item list display process that displays the list of item names stored in the terminal memory on the above display, Based on the receipt of the user's item specification through the above input interface, the terminal computer is instructed to execute a payment information generation process that generates the electronic payment information including the item specified by the item specification and the corresponding price of the item. The electronic payment support system according to claim 1 or 2, wherein the above billing amount is the sum of the above-mentioned goods price and medical fees.

5. The invoices created by the above invoice creation program are medical claim forms. The above application software is, If the designated output means is the second output means, and it is determined that the second output means cannot be executed, the terminal computer is instructed to execute an inquiry screen display process that displays an inquiry screen on the display asking whether or not the first output means should be the designated output means. The electronic payment support system according to claim 2, wherein, based on the receipt of a change instruction to change the first output means to the designated output means via the input interface on the inquiry screen, the terminal computer is instructed to execute the electronic payment information output process that generates the code and outputs it to the printing device.

6. Application software implemented in a facility-installed terminal having terminal memory for storing the OS and invoice creation program, a terminal computer, a display, and an input interface, Initialization processing including: an identification information acquisition process for acquiring program identification information indicating the above-mentioned invoice creation program; a first position information acquisition process for acquiring first position information indicating the first position, which is a first position on the invoice screen displayed on the display via the above-mentioned OS and for acquiring user identification information, which is received through the above-mentioned input interface; and a second position information acquisition process for acquiring second position information indicating the second position, which is a second position on the invoice screen and for acquiring the invoice amount, which is received through the above-mentioned input interface; Based on the receipt of an output instruction through the above input interface, a screen data acquisition process is performed in which an image data acquisition instruction is input to the OS, which includes the program identification information obtained in the above identification information acquisition process, and which requests invoice screen data showing the invoice screen displayed on the display via the OS by the invoice creation program indicated by the program identification information, and the invoice screen data is acquired from the OS. A first acquisition process that includes a process for acquiring the user identification information based on the above invoice screen data and the above first location information, and a process for acquiring the invoice amount based on the above invoice screen data and the above second location information, and acquires electronic payment information including the user identification information and the said invoice amount, An electronic payment information output process that outputs the above-mentioned electronic payment information, and application software that causes the above-mentioned terminal computer to execute this process.

7. A specification acceptance screen display process that displays a specification acceptance screen on the display for accepting the specification of one of the output means, which is either a first output means for printing a code indicating the above-mentioned electronic payment information or a second output means for transmitting the above-mentioned electronic payment information. The terminal computer is further instructed to execute a process to acquire the specified output means, which is the output means specified in the above-mentioned designated reception screen, Based on the fact that the designated output means is the first output means, the terminal computer is instructed to execute the electronic payment information output process that generates the code and outputs it to the printing device. The application software according to claim 6, which causes the terminal computer to execute the electronic payment information output process that transmits the electronic payment information to the electronic payment terminal, based on the fact that the designated output means is the second output means.

Images