Information processing device, information processing method, and program

Abstract

We provide an information processing device that simplifies the payment process for medical applications. [Solution] In the information processing system 1, the information processing device 10 of pharmaceutical wholesaler W includes a billing processing device 12 that enables billing of the medical institution F for the medical application when the medical application is prescribed at the medical institution F, a payment processing device 14 that enables payment of the medical application fee to the provider of the medical application, and a reduction processing device 13 that reduces a predetermined fee from the medical application fee, and the payment processing device 14 enables payment of the medical application fee, with the fee reduced, to the application maker C, who is the provider.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] Conventionally, techniques for prescribing medical applications to patients in medical institutions have been proposed (for example, Patent Documents 1 to 3).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the prior art, medical institutions had to directly pay the fees for medical applications to the providers of the medical applications (for example, app developers). However, the payment methods for fees may vary for each app developer. In the above cases, there was a situation where the procedures on the medical institution side became complicated. In view of the above circumstances, an object of the present invention is to reduce the workload on the medical institution side.

Means for Solving the Problems

[0005] In order to solve the above problems, the information processing apparatus of the present invention includes a billing processing unit that enables billing of the medical institution for the fees of a medical application when the medical application is prescribed in the medical institution, and a payment processing unit that enables payment of the fees of the medical application to the provider of the medical application.

Effects of the Invention

[0006] According to the present invention, the payment process for medical applications becomes simpler. [Brief explanation of the drawing]

[0007] [Figure 1] This is a diagram illustrating the overview of the information processing system. [Figure 2] This is a diagram illustrating the details of an information processing system. [Figure 3] This is a functional block diagram of an information processing system. [Figure 4] This is a simulated example of an app store image. [Figure 5] This diagram illustrates specific examples of the types of information processed by an information processing system. [Figure 6] This is a diagram illustrating a specific example of how an information processing system works. [Figure 7] This is a diagram illustrating specific examples of other operations of an information processing system. [Figure 8] This is a simulated diagram of a concrete example of an app image. [Figure 9] This is a system sequence diagram used to explain the operation of an information processing system. [Modes for carrying out the invention]

[0008] Figure 1 is a diagram illustrating the various components of the information processing system 1000. The information processing system 1000 consists of a server device 100, a facility-side terminal 200, a patient terminal 300, and a manufacturer-side terminal 400. As shown in Figure 1, the server device 100, the facility-side terminal 200, the patient terminal 300, and the manufacturer-side terminal 400 can communicate with each other via network N. Network N is assumed to be, for example, the internet.

[0009] In reality, multiple patient terminals 300 communicate with the server device 100. However, in Figure 1, for illustrative purposes, only one patient terminal 300 is shown. The patient terminal 300 is managed by patient C, and a smartphone may be used. However, a notebook or desktop personal computer may also be used as the patient terminal 300.

[0010] The server device 100 is managed, for example, by a pharmaceutical wholesaler and installed in a data center. As shown in Figure 1, the server device 100 of this embodiment implements an app store M. The app store M is a marketplace that allows healthcare professionals D (for example, doctors) to prescribe multiple types of medical applications App (x, y, z…). The above configuration will be described in detail later.

[0011] In this embodiment, "the server device 100 being managed by a pharmaceutical wholesaler" includes not only the direct management of the server device 100 by the pharmaceutical wholesaler, but also the indirect management of the server device 100 by the pharmaceutical wholesaler. For example, "the server device 100 being managed by a pharmaceutical wholesaler" includes not only the management of the server device 100 by the pharmaceutical wholesaler's employees, but also the management of the server device 100 by a company commissioned by the pharmaceutical wholesaler.

[0012] The facility-side terminal 200 is managed by, for example, a medical facility (healthcare institution) and operated by a medical professional D. In this embodiment, "the facility-side terminal 200 being managed by a medical facility" includes not only the medical facility directly managing the facility-side terminal 200, but also the medical facility indirectly managing the facility-side terminal 200. For example, "the facility-side terminal 200 being managed by a medical facility" includes not only the facility-side terminal 200 being managed by an employee of the medical facility, but also the facility-side terminal 200 being managed by a contractor commissioned by the medical facility.

[0013] The medical application App of this embodiment is created by an app developer and includes a medical application App for medical facilities (hereinafter sometimes referred to as "facility application Af") and a medical application App for patients corresponding to the facility application Af (hereinafter sometimes referred to as "patient application Ap"). By the cooperation of the facility application Af and the patient application Ap, the treatment policy of the patient P is determined.

[0014] Medical staff D downloads the facility application Af that may be prescribed at his / her own medical facility from the app store M to the facility-side terminal 200 in advance. When the facility application Af is downloaded to the facility-side terminal 200, the patient application Ap corresponding to the facility application Af can be prescribed. Specifically, when the patient application Ap is prescribed to the patient P, a prescription code is assigned to the patient P. The patient application Ap is downloaded to the patient terminal 300. Also, when the prescription code is input to the patient terminal 300, the patient application Ap becomes available.

[0015] When the patient application Ap operates, various kinds of information are transmitted from the patient terminal 300 to the server device managed by the app developer. For example, assume a case where a medical application App for improving hypertension is prescribed to the patient P. By the operation of the above medical application App (patient application Ap) on the patient terminal 300, the blood pressure regularly measured by the patient P can be transmitted from the patient terminal 300 to the server device managed by the app developer. Also, by the operation of the facility application Af on the facility-side terminal 200, the information of the patient P managed by the app developer can be used (viewed) on the facility-side terminal 200. For example, the medical staff D determines the treatment method based on the information of the patient P (for example, the blood pressure of the patient P).

[0016] Each manufacturer-side terminal 400 (x, y, z, …) can upload a medical application App (x, y, z, …) created by an app manufacturer to the server device 100 (app store M). The medical application App uploaded to the server device 100 can be downloaded from the app store M. Note that the medical application App has been pre-approved for insurance application. Therefore, when a medical facility prescribes the medical application App, a part (30%) of the fee for the medical application App is paid by the patient to the medical facility, and another part (70%) is paid by the insurer to the medical facility.

[0017] In the specific example of FIG. 1, it is assumed that each medical application App (x, y, z, …) is uploaded to the app store M from different app manufacturers M (x, y, z, …). Although details will be described later, a list of medical application Apps uploaded to the app store M can be displayed on the facility-side terminal 200. Also, the medical staff D can download a desired medical application App from the list of medical application Apps. According to the above configuration, the convenience when the medical staff D selects a medical application App is improved. Note that in FIG. 1, an example in which the server device 100 is composed of one server device is shown, but the server device 100 may be composed of a plurality of devices (systems). The same applies to the facility-side terminal 200 and the manufacturer-side terminal 400.

[0018] FIG. 2 is a hardware configuration diagram of the information processing system 1000. As described above, the information processing system 1000 includes the server device 100, the facility-side terminal 200, the patient terminal 300, and the manufacturer-side terminal 400.

[0019] The server device 100 is managed by the pharmaceutical wholesaler W and consists of a processing unit, a storage device, and a communication device. Each of these components is connected via a system bus for communication. The processing unit of the server device 100 controls the entire server device 100. The processing unit may consist of one or more processors. Specifically, the processing unit may consist of one or more types of processors, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), or an ASIC (Application Specific Integrated Circuit).

[0020] The communication device of the server device 100 communicates with the communication devices of external devices (facility-side terminal 200, patient terminal 300, manufacturer-side terminal 400) via network N. Note that in Figure 2, network N is omitted for illustrative purposes. The storage device of the server device 100 stores various programs, including basic programs and application programs. Known recording media such as semiconductor recording media and magnetic recording media can be used as the storage device. Furthermore, the storage device may consist of one recording media or multiple recording media.

[0021] The storage device of the server device 100 stores various types of information. For example, the storage device of the server device 100 stores the medical application App in the app store M. As described above, the medical application App includes the facility application Af, which is downloaded to the medical facility F (facility terminal 200), and the patient application Ap, which is downloaded by the patient P (patient terminal 300). As shown in Figure 2, of the above medical application App, the facility application Af is located in the app store Mf, and the patient application Ap is located in the app store Mp.

[0022] The facility-side terminal 200 is managed by medical facility F and, like the server device 100 described above, is configured to include a processing unit, a storage device, and a communication device. As shown in Figure 2, the facility-side terminal 200 (storage device) stores the application program PGf. This application program PGf is downloaded to the facility-side terminal 200 in advance, for example, from the server device 100. When the facility-side terminal 200 executes the application program PGf, it becomes possible to download, for example, the facility application Af (medical application App) from the app store Mf.

[0023] The manufacturer-side terminal 400 is managed by app maker C and, like the server device 100 described above, is configured to include a processing unit, storage device, and communication device. Specifically, a manufacturer-side terminal 400 is provided for each app maker C (x, y, z…), and stores the app program PGc. The app program PGc is downloaded in advance to the manufacturer-side terminal 400 from, for example, the server device 100. By executing the app program PGc, the manufacturer-side terminal 400 can upload, for example, a medical application App to the server device 100 (app store M).

[0024] Furthermore, when a medical application app is uploaded to the server device 100, the system may be configured to review whether the medical application app meets predetermined criteria before being published to the app store M. For example, a pharmaceutical wholesaler W reviews whether the uploaded medical application app is identical to a medical application app that has received approval for insurance coverage. If the review determines that the predetermined criteria are met, the medical application app is published to the app store M.

[0025] By the way, in order for a medical application app created by app maker C to be prescribed at medical facility F, a usage agreement must be concluded. This usage agreement is concluded for each medical application app. In conventional technology, a medical professional D at medical facility F requests a price estimate for the desired medical application app from app maker C, the creator of the medical application app. Subsequently, if medical facility F agrees to the price of the medical application app presented by app maker C, a usage agreement is concluded. Once a usage agreement has been concluded, the medical application program app becomes available for use (prescription) at medical facility F.

[0026] However, the contract procedures for making medical applications available may differ for each application manufacturer C (x, y, z…). In this case, the conventional technology described above, which requires medical facility F to go through the contract procedures for each application manufacturer C, can result in an excessive workload for medical facility F. Taking these circumstances into consideration, this embodiment adopts a configuration that suppresses the above-mentioned inconveniences.

[0027] Specifically, as described above, the medical application App is uploaded from the manufacturer's terminal 400 to the app store M. When the medical application App is uploaded, the estimated price of the medical application App is notified to the server device 100 (pharmaceutical wholesaler W). Specifically, when the app program PGc runs on the manufacturer's terminal 400, an input image where the estimated price can be entered is displayed. When the send button on this input image is selected, the app program PGc automatically notifies the server device 100 of the estimated price. The estimated price that app manufacturer C notifies pharmaceutical wholesaler W of is, for example, the price that pharmaceutical wholesaler W pays to app manufacturer C when the medical application App is prescribed once.

[0028] If pharmaceutical wholesaler W agrees to the quoted price notified by app manufacturer C, a transaction contract (data) based on that quoted price is sent to the manufacturer's terminal 400. Subsequently, when a predetermined confirmation operation is performed on the manufacturer's terminal 400, the transaction contract is concluded using known electronic contract technology (Sa1 in Figure 2). Specifically, when the app program PGc is run, it becomes possible to receive the transaction contract from the server device 100, the transaction contract becomes possible to display on the manufacturer's terminal 400, and the above confirmation operation becomes possible.

[0029] When the application program PGf is run on the facility terminal 200, the app store image Gp (see Figure 4 below) is displayed. The app store image Gp displays a list of medical applications App in the app store M. Specifically, the app store image Gp displays medical applications App for which a usage agreement has been concluded (i.e., prescriptions can be made), as well as medical applications App for which no usage agreement has been concluded.

[0030] Furthermore, the facility terminal 200 can request a price estimate for medical application apps via the app store image Gp. Specifically, the facility terminal 200 can accept operations to request a price estimate for medical application apps for which a usage agreement has not been concluded (operation of the estimate request button in Figure 4 described below; hereinafter referred to as "estimate request operation"). When the estimate request operation is executed on the facility terminal 200, an estimate request notification is sent to the server device 100 of the pharmaceutical wholesaler W.

[0031] When pharmaceutical wholesaler W receives a request for a quote, it executes the quote and contract procedure (Sa2 in Figure 2). Specifically, when pharmaceutical wholesaler W receives a request for a quote, it determines the estimated price for the medical application App for which a price quote has been requested. For example, pharmaceutical wholesaler W determines the estimated price for the medical application App by referring to the prices determined by others (such as other pharmaceutical wholesalers). Pharmaceutical wholesaler W also notifies medical facility F of the estimated price for the medical application App. The estimated price that pharmaceutical wholesaler W notifies medical facility F is, for example, the price that medical facility F will pay to pharmaceutical wholesaler W if the medical application App is prescribed once.

[0032] When a medical application app is prescribed, the fee that medical facility F pays to pharmaceutical wholesaler W will be higher than the fee that pharmaceutical wholesaler W pays to app manufacturer C, by the amount of the fees described below. In principle, these fees will be kept confidential from app manufacturer C and medical facility F. However, it is also possible to configure the system so that app manufacturer C is notified of the fees in advance.

[0033] If medical facility F agrees to the fees notified by pharmaceutical wholesaler W, pharmaceutical wholesaler W will enter into a service agreement with medical facility F using publicly known electronic contract technology. For example, the electronic contract is concluded by running the application program PGf on medical facility F's terminal 200 and running the application program PGm on application manufacturer C's manufacturer terminal 400.

[0034] The operations required on the facility-side terminal 200 for the above electronic contract are substantially the same regardless of the medical application App for which the usage agreement is concluded. Specifically, substantially the same operation images are displayed on the facility-side terminal 200 regardless of the type of medical application App for which the usage agreement is concluded. The person in charge at medical facility F can conclude the usage agreement by operating the facility-side terminal 200 according to the instructions displayed on the operation images. According to this embodiment, the work required to conclude a usage agreement for a medical application App is simplified.

[0035] Once a usage agreement for the medical application App is concluded, the facility application Af becomes available for download to the facility terminal 200 (Sb in Figure 2). Furthermore, once the facility application Af is installed on the facility terminal 200, the patient application Ap corresponding to the facility application Af becomes available for prescription to patient P. It is also possible to configure the system to allow prescription of patient application Ap to patient P before the usage agreement is concluded. Specific examples of this configuration will be described later as variations of this implementation.

[0036] The patient terminal 300 is managed by patient P and, like the server device 100 described above, is configured to include a processing unit, a storage device, and a communication device. As shown in Figure 2, the patient terminal 300 (storage device) stores the application program PGp. The application program PGp is ​​downloaded to the patient terminal 300 in advance, for example, from the server device 100. When the patient terminal 300 executes the application program PGc, for example, a medical application App (patient application Ap) becomes available for download from the server device 100 (app store Mp) (Sc in Figure 2). However, the patient application Ap cannot be used until its prescription code is entered into the patient terminal 300.

[0037] Specifically, if, as a result of a medical examination at medical facility F, patient P is prescribed the patient application Ap, a prescription operation to prescribe the patient application Ap is performed on the facility terminal 200 (Sd in Figure 2). Once the prescription operation is performed, a prescription code becomes available for patient P. When the prescription code is entered into the patient terminal 300, the patient application Ap becomes available for use. In this configuration, patient P, who has been prescribed the patient application Ap as a result of a medical examination at medical facility F, becomes able to use the patient application Ap. In other words, the patient application Ap becomes available on the condition that the patient receives a medical examination at medical facility F.

[0038] Furthermore, some medical applications (Apps) may be used in conjunction with medical devices (e). For example, a medical application (App) designed to improve a patient's hypertension may be used with a blood pressure monitor that automatically communicates with the server of the app manufacturer (C). Similarly, a medical application (App) designed to improve a patient's eye condition may be used with a medical camera to photograph the patient's eyes.

[0039] In this embodiment, when a medical application App is prescribed, the server device 100 determines whether or not medical goods e are necessary, depending on the type of medical application App. If it determines that medical goods e are necessary, the server device 100 executes a delivery process. In this delivery process, various processes are executed to deliver the medical goods e to the patient P. For example, delivery information specifying the type of medical goods e required and the delivery destination (address, etc.) is notified to the delivery person of the pharmaceutical wholesaler W. When the delivery process is executed, the delivery person of the pharmaceutical wholesaler W delivers the medical goods e to the delivery destination (Se in Figure 2).

[0040] Now, let's assume that the administrator of app store M and the delivery person for medical supplies e are separate entities (hereinafter referred to as "proportional arrangement"). In this proportional arrangement, it may be necessary to download the medical application App from app store M and then arrange for the delivery of medical supplies e with the delivery person. Therefore, there is the disadvantage of a greater burden on patient P. According to the configuration of this embodiment, for example, the above disadvantage is suppressed compared to the proportional arrangement described above. Also, in the proportional arrangement described above, app maker C needs to perform the task of delivering medical supplies e, or the task of requesting the delivery of medical supplies e from another party. According to this embodiment, there is the advantage that app maker C does not need to perform each of the above tasks.

[0041] Figure 3 is a functional block diagram of the information processing system 1. As shown in Figure 3, the information processing system 1 consists of an information processing device 10, a facility-side terminal 20, a patient terminal 30, and a manufacturer-side terminal 40. Each of these components is configured to communicate via network N.

[0042] For example, the processing unit of the server device 100 managed by pharmaceutical wholesaler W functions as an information processing unit 10 by executing a program. Similarly, the processing unit of the facility-side terminal 200 managed by medical facility F functions as a facility-side terminal 20 by executing the application program PGf. Likewise, the processing unit of the patient terminal 300 functions as a patient terminal 30 by executing the application program PGc. The processing unit of the manufacturer-side terminal 400 managed by application manufacturer C functions as a manufacturer-side terminal 40 by executing the application program PGm.

[0043] The information processing device 10 comprises a storage unit 11, a billing processing unit 12, a reduction processing unit 13, a payment processing unit 14, a delivery processing unit 15, a quotation processing unit 16, and a contract processing unit 17. For example, the storage device of the server device 100 described above functions as the storage unit 11. The storage unit 11 stores medical applications App(x, y, z…) in a downloadable format. Specifically, a medical application Appx is uploaded from the manufacturer's terminal 40 to the information processing device 10. Once a medical application Appx is uploaded, the information processing device 10 stores the medical application Appx in the storage unit 11.

[0044] The billing processing unit 12 of the information processing device 10 makes it possible to bill medical institution F for the medical application App when the medical application App is prescribed at medical institution F. Furthermore, the payment processing unit 14 of the information processing device 10 makes it possible to pay the medical application App fee to the provider of the medical application App (app maker C in the specific example shown in Figure 3).

[0045] Specifically, the reduction processing unit 13 deducts a predetermined fee from the fee of the medical application App. The payment processing unit 14 makes the fee of the medical application App, with the fee reduced, available for payment to the provider. In this embodiment, approximately 30 percent of the fee of the medical application App is reduced as a fee, and the reduced fee is paid to the app manufacturer C. The above fee is collected by the pharmaceutical wholesaler W. Note that the above fee may be determined for each app manufacturer C in the contract processing described later. Alternatively, the fee may be determined for each medical application App in the contract processing described later.

[0046] The delivery processing unit 15 of the information processing device 10 makes medical goods e, which are used with a medical application App, available for delivery when the medical application App is prescribed. Specifically, when a medical application App is prescribed, the information processing device 10 identifies the medical goods e used with the medical application App and arranges for the delivery of those medical goods e. For example, when a medical application App is prescribed, the information processing device 10 automatically notifies the delivery person of the pharmaceutical wholesaler W of delivery information that identifies the type of medical goods e required and the delivery destination.

[0047] The estimation processing unit 16 enables terminal devices at medical institution F (e.g., facility-side terminal 20) to accept operations for requesting an estimate for the medical application App. Specifically, the information processing unit 10 (estimation processing unit 16) sends the application program PGf to the facility-side terminal 20 in response to a request from medical facility F. Once the application program PGf is installed on the facility-side terminal 20, the facility-side terminal 20 becomes capable of accepting estimate request operations. When an estimate request operation is accepted, an estimate request notification is sent to the information processing unit 10.

[0048] The contract processing unit 17 enables the conclusion of the aforementioned usage agreement between the pharmaceutical wholesaler W and the medical facility F. As described above, when the pharmaceutical wholesaler W receives a quotation request notification, it determines the terms of use (such as the terms of service) including the fee for the medical application App. The pharmaceutical wholesaler W also notifies the facility terminal 20 of the final terms of use using the information processing unit 10. The terms of use notified to the facility terminal 20 are displayed, for example, in a dedicated image.

[0049] Medical facility F reviews the notified terms of use, and if it agrees to them, it sends an agreement notification to the information processing device 10 (pharmaceutical wholesaler W) using the facility terminal 20. All operations on the facility terminal 20 required for the above usage agreement are implemented by the application program PGf. A party-signed electronic signature may be used. Alternatively, a paper contract may be used instead of an electronic contract.

[0050] Figure 4 is a simulated diagram of the app store image Gp. The app store image Gp is ​​displayed on the facility terminal 20 of medical facility F when the facility terminal 20 runs the app program PGf. Healthcare worker D can perform the prescription and quotation request operations described above via the app store image Gp. In addition, a medical application App (facility application Ap) for which a usage agreement has been concluded can be downloaded to the facility terminal 20 via the app store image Gp.

[0051] As shown in Figure 4, the app store image Gp is ​​composed of individual app regions Ra(1, 2, 3, 4…). Each individual app region Ra(1, 2, 3, 4…) corresponds to each medical application App (facility application Mf) in the app store Mf.

[0052] Figure 4 illustrates a specific example where medical application apps, including Appx (hereinafter "App Ax") from app maker Cx, Appy (hereinafter "App Ay") from app maker Cy, Appz (hereinafter "App Az") from app maker Cz, and Appw (hereinafter "App Aw") from app maker Cw, are uploaded to the app store M. In this case, each app-specific area Ra, including app-specific area Ra1 corresponding to App Ax, app-specific area Ra2 corresponding to App Ay, app-specific area Ra3 corresponding to App Az, and app-specific area Ra4 corresponding to App Aw, will be displayed in the app store image Gp.

[0053] As shown in Figure 4, the application-specific area Ra displays various information about the medical application App corresponding to that application-specific area Ra. For example, the application-specific area Ra displays the name and purpose of use of the medical application App corresponding to that application-specific area Ra (e.g., smoking cessation support, insomnia improvement support, hypertension improvement support, etc.). In addition, the application-specific area Ra displays the total number of times the medical application App corresponding to that application-specific area Ra has been prescribed at each medical facility F (hereinafter referred to as "total prescription count"). The above total prescription count is counted, for example, by the information processing device 10.

[0054] Furthermore, various buttons (such as a quote request button) are displayed in the app-specific area Ra. Specifically, the buttons displayed in the app-specific area Ra change depending on whether the medical application App corresponding to that app-specific area Ra has been downloaded to the facility terminal 20. In addition, the buttons displayed in the app-specific area Ra change depending on whether the quote request for the medical application App corresponding to that app-specific area Ra has been completed, and whether the contract processing for the medical application App corresponding to that app-specific area Ra has been completed.

[0055] For example, consider an app A in app store M for which a quote request has not been completed. In the app-specific area Ra corresponding to this app A, a quote request button is displayed. The specific example in Figure 4 assumes that a quote request has not been completed for app Ax in app store M. In this case, a quote request button is displayed in the app-specific area Ra1 corresponding to app Ax. When the quote request button is selected (clicked with the mouse) (when a quote request operation is performed), a quote request notification is sent to the pharmaceutical wholesaler W (information processing device 10) as described above. This quote request notification includes the type of medical application App for which a quote has been requested (app ID) and the identifier of the medical facility F (facility ID).

[0056] When pharmaceutical wholesaler W receives a quotation request notification, it notifies medical facility F of the terms of use, including the quoted price for app A. Hereinafter, the period from when medical facility F performs the quotation request operation until the terms of use are notified to medical facility F may be referred to as the "quotation period." In this embodiment, the fact that it is the quotation period is indicated in the app store image Gp. Specifically, in the app-specific area Ra of each app in the app store image Gp, the string "Quotation in Progress" is displayed in the app-specific area Ra corresponding to app A, which is in the quotation period. For example, the specific example in Figure 4 assumes that app Ay, among the apps A in app store M, is in the quotation period.

[0057] Furthermore, the facility terminal 20 may be configured to notify the facility that the terms of use for app A have been notified by the pharmaceutical wholesaler W. For example, as described above, if app A is in the quotation period, the string "Quotation in progress" will be displayed in the app-specific area Ra corresponding to app A. In the above configuration, if the terms of use for app A are received by the facility terminal 20, the string "Quotation in progress" may be replaced with a "Confirm Terms of Use" button in the app-specific area Ra. When the "Confirm Terms of Use" button is selected, the terms of use received from the information processing device 10 are displayed on the facility terminal 20 by the operation of the app program PGf.

[0058] Once a usage agreement for application A is concluded, application A becomes available for download on the facility terminal 20. Specifically, immediately after the usage agreement for application A is concluded, a download button is displayed in the application-specific area Ra corresponding to application A. For example, the specific example in Figure 4 assumes the situation immediately after the usage agreement for application Az is concluded. In this case, a download button is displayed in the application-specific area Ra4 corresponding to application Az. When the download button is selected, application A (facility application Af) corresponding to that application-specific area Ra is downloaded from the app store Mf to the facility terminal 20.

[0059] When app A is downloaded to the facility terminal 20, it becomes possible to prescribe app A to patient P. Specifically, the app-specific area Ra corresponding to the downloaded app A displays a prescribe button, an evaluation button, and a re-estimate button. For example, in the specific example in Figure 4, we assume that app Aw from among the apps A in the app store M has been downloaded to the facility terminal 20. In this case, the app-specific area Ra4 corresponding to app Aw displays a prescribe button, an evaluation button, and a re-estimate button. Also, as shown in Figure 4, the cost required to prescribe app A once (the price of app A) is displayed near the prescribe button.

[0060] When the prescription button in the application-specific area Ra is selected (prescription operation), the application A corresponding to that application area Ra becomes available for prescription to patient P. Specifically, the application program PGf launches the facility application Af in response to the prescription operation, and generates a prescription code using the functions of facility application Af. This prescription code is then notified to patient P. Facility application Af also notifies the application manufacturer C of application A of the prescription code for application A. Alternatively, the system may be configured so that when a prescription operation is performed, the application program PGf generates a prescription code and notifies the application manufacturer C of that prescription code.

[0061] When the "Re-estimate" button is selected in the application-specific area Ra, a request for an estimate for application A corresponding to that application-specific area Ra is sent again to the pharmaceutical wholesaler W (information processing device 10). If the pharmaceutical wholesaler W receives the estimate request again, it will, for example, hear the requirements of medical facility F and then determine the terms of use (such as the price of application A) again.

[0062] Furthermore, if the "Re-estimate" button is selected, the "Prescribe" button may be hidden, making it impossible to accept prescription operations. In the above configuration, if a service agreement is concluded with new terms of use after the "Re-estimate" button is selected, the "Prescribe" button will be displayed again. However, the system may also be configured to accept prescription operations even during the period after the "Re-estimate" button is selected. In the above configuration, during the period between the selection of the "Re-estimate" button and the conclusion of a service agreement with new terms of use, App A can be prescribed under the old terms of use.

[0063] When the evaluation button in the application-specific domain Ra is selected, it becomes possible to input an evaluation of application A corresponding to that application-specific domain Ra. Specifically, when the evaluation button is selected, the application program PGf operates and an evaluation input image is displayed on the facility terminal 20. Healthcare worker D inputs an evaluation of application A via the evaluation input image. For example, when healthcare worker D examines patient P who has used application A, D inputs an evaluation indicating that the patient's symptoms had improved compared to before using application A.

[0064] Specifically, the items to be evaluated in the clinical trial of app A (a clinical trial to obtain approval for insurance coverage) (hereinafter referred to as "treatment information") are entered via evaluation input images. The treatment information entered via evaluation input images is transmitted from the facility terminal 20 to the pharmaceutical wholesaler W (information processing device 10) by the operation of the app program PGf. However, the treatment information may also be transmitted directly from the facility terminal 20 to the app manufacturer C (manufacturer terminal 40).

[0065] Furthermore, the app store image Gp consists of a filter button Ba1, a sort button Ba2, and an advertising area Rc. When the filter button Ba1 is selected, a portion of each app A (app-specific area Ra) in the app store M can be displayed in the app store image Gp. Specifically, when an app A is uploaded to the app store M, it is assigned one of several app types (smoking cessation support, insomnia improvement support, blood pressure improvement support, etc.). For example, a pharmaceutical wholesaler W assigns an app type to the uploaded app A. By selecting the filter button Ba1, one of the app types can be set. The app store image Gp displays an excerpt of app A corresponding to the app type set by the filter button Ba1. Note that the specific example in Figure 4 assumes that app A of all app types is displayed.

[0066] When the sort button Ba2 is selected, the display order of app A (app-specific area Ra) in the app store image Gp can be changed. For example, app A can be displayed in the app store image Gp in descending order of total prescription count. Alternatively, app A can be displayed in the app store image Gp in descending order of price (lowest to highest).

[0067] Various advertisements are displayed in the advertising area Rc of the app store image Gp. When a pharmaceutical wholesaler W (information processing device 10) receives an advertising fee from, for example, app manufacturer C, it displays an advertisement for app A from app manufacturer C in the advertising area Rc. Alternatively, when the advertising area Rc is selected, a details screen displaying details of app A advertised in that advertising area Rc may be displayed. Alternatively, a button to request a quote for app A may be displayed on the details screen.

[0068] Figures 5(a) to 5(d) are diagrams illustrating the various types of information generated by the information processing device 10. Each of these types of information is generated in the information processing device 10 using various types of information transmitted from the facility terminal 20 (application program PGf), the patient terminal 30 (application program PGc), and the manufacturer terminal 40 (application program PGm).

[0069] Figure 5(a) is a diagram illustrating manufacturer-specific information Dc. Manufacturer-specific information Dc is provided for each app manufacturer C and includes various information about that app manufacturer C (e.g., contract information). Furthermore, each combination of manufacturer-specific information Dc for each app manufacturer C (x, y…) is stored corresponding to each medical institution F (a, b…). For example, in the specific example in Figure 5(a), it is assumed that the combination of manufacturer-specific information Dcx for app manufacturer Cx, manufacturer-specific information Dcy… for app manufacturer Cy is stored corresponding to each medical institution F (a, b…).

[0070] Figure 5(b) is a diagram illustrating the details of manufacturer-specific information Dc. Figure 5(b) shows an example of manufacturer-specific information Dcx for app manufacturer Cx, as shown in the specific example of manufacturer-specific information Dc in Figure 5(a) above. This manufacturer-specific information Dcx includes, for example, the name of app manufacturer Cx.

[0071] As shown in Figure 5(b), the manufacturer-specific information Dc of app maker C includes app information Da (see Figure 5(c) below), which contains various information about app A of app maker C. This app information Da is provided for each app A. For example, consider the case where app maker C uploads multiple apps A to app store M. In this case, the manufacturer-specific information Dc of app maker C includes multiple app information Da corresponding to each app A. For example, the specific example in Figure 5(b) assumes that app maker Cx uploads multiple apps A, including apps Ax1, Ax2, etc., to app store M. In this case, app information Da1 for app Ax1, app information Da2 for app Ax2, etc., are included in the manufacturer-specific information Dcx.

[0072] The manufacturer-specific information Dc of app manufacturer C includes transaction information Dt (see Figure 5(d) below), which contains information about the transaction between the medical institution F corresponding to the manufacturer-specific information Dc and the app manufacturer C. This transaction information Dt is generated each time app A is prescribed. For example, the specific example in Figure 5(b) assumes that app Ax1 is prescribed two or more times. In this case, the manufacturer-specific information Dc contains multiple transaction information Dt, including transaction information Dt1 generated when app Ax1 was first prescribed, transaction information Dt2 generated when app Ax2 was prescribed the second time, and so on.

[0073] Figure 5(c) is a diagram illustrating the details of app information Da. The app information Da for manufacturer-specific information Dc includes the number of times app A has been prescribed at the medical facility F corresponding to that manufacturer-specific information Dc (hereinafter referred to as "prescription count"). The prescription count in app information Da for app A is cleared to the value "0" when the medical facility F is billed for app A. In other words, the prescription count in app information Da indicates the number of times app A has been prescribed for which the fee for app A has not been billed. Figure 5(c) shows a specific example of app information Da1 for app Ax1, as shown in the specific example of app information Da in Figure 5(b) above. The app information Da1 above includes, for example, the name of app Ax1, the app type (e.g., smoking cessation support), and the prescription count.

[0074] Furthermore, the application information Da in manufacturer-specific information Dc includes evaluation information for application A entered at medical facility F corresponding to the manufacturer-specific information Dc. This evaluation information includes the treatment information mentioned above. As described above, the treatment information is entered by a medical professional D (e.g., a doctor) using the facility terminal 20 and transmitted to the information processing device 10. The evaluation information also includes user evaluation information. This user evaluation information is entered at the patient terminal 300 and transmitted to the information processing device 10. The above configuration will be described in detail later with reference to Figure 8.

[0075] The app information Da of app A includes accessory information that identifies the medical item e used in conjunction with app A. This accessory information is notified in advance, for example, by app manufacturer C to pharmaceutical wholesaler W. Furthermore, the app information Da of app A includes contract information (electronic contract, terms of use, etc.) relating to the usage agreement for app A concluded between the medical institution F and pharmaceutical wholesaler W, which corresponds to the manufacturer-specific information Dc containing the app information Da, and the transaction agreement for app A concluded between pharmaceutical wholesaler W and app manufacturer C.

[0076] The contract information in App Information Da includes pricing information showing the price of App A for that App Information Da. However, even for a common App A, the price may differ depending on the medical facility F. Therefore, even for App Information Da of a common App A, if the medical facility F corresponding to the manufacturer-specific information Dc containing each App Information Da is different, the price shown in the pricing information may differ.

[0077] Figure 5(d) is a diagram illustrating the details of transaction information Dt. As mentioned above, transaction information Dt is generated each time app A is prescribed. Each transaction information Dt in manufacturer-specific information Dc is used to manage the transactions (such as payment of fees) required when app A is prescribed at the medical facility F corresponding to that manufacturer-specific information Dc. The specific example in Figure 5(d) is similar to the specific example in Figure 5(b) above, assuming that transaction information Dt1 is generated when app Ax1 is prescribed for the first time, and transaction information Dt2 is generated when app Ax2 is prescribed for the second time.

[0078] As shown in Figure 5(d), each transaction information Dt includes the name of the application A prescribed when the transaction information Dt was generated (in the specific example in Figure 5(d), this is application Ax1). In addition, each transaction information Dt includes the status (progress) of the transaction managed by that transaction information Dt. Specifically, the status of transaction information Dt is one of the following: "Prescribed," "Invoiced," "Received," or "Paid."

[0079] For example, immediately after app A is prescribed, the status of transaction information Dt will be "Prescribed". Subsequently, when pharmaceutical wholesaler W invoices medical facility F for the fee for app A, the status of transaction information Dt will be updated to "Invoiced". Furthermore, when pharmaceutical wholesaler W receives the fee for app A from medical facility F, the status of transaction information Dt will be updated to "Received", and when pharmaceutical wholesaler W pays the fee for app A to app manufacturer C, the status of transaction information Dt will be updated to "Paid".

[0080] As shown in Figure 5(d), the patient ID used to identify patient P to whom app A was prescribed is included in the transaction information Dt. It also includes a combination of the date app A was prescribed and the amount billed to medical facility F (the app fee), a combination of the date and amount received by pharmaceutical wholesaler W for the app A fee, a fee deducted from the app A fee, and a combination of the date and amount paid by pharmaceutical wholesaler W to app manufacturer C for the app A fee. Alternatively, the fee paid to app manufacturer C when app A is prescribed may be stored in the information processing device 10 instead of the fee. In this configuration, the fee deduction process described later can be omitted.

[0081] Figure 6 is a diagram illustrating a specific example of contract processing. As shown in Figure 6, the manufacturer's terminal 40 can accept a publication request operation through the operation of the application program PGc (Sa11 in Figure 6). As a result of this publication request operation, application A is uploaded from the manufacturer's terminal 40 to the information processing device 10 (pharmaceutical wholesaler W) (Sa12 in Figure 6). Furthermore, once application A is uploaded, a transaction contract for application A is concluded. Specifically, the fees and terms of use for application A are agreed upon between application manufacturer C and pharmaceutical wholesaler W, and a transaction contract is concluded. Once the transaction contract for application A is concluded, application A is published on the app store M (Sa13).

[0082] As described above, when a quotation request operation for application A (selection of the quotation request button shown in Figure 4) is received on the facility terminal 20 of medical facility F (Sa21 in Figure 6), a quotation request notification is sent to the information processing device 10 of pharmaceutical wholesaler W (Sa22 in Figure 6). Upon receiving the quotation request notification for application A, pharmaceutical wholesaler W agrees with medical facility F on the terms of use of application A (such as fees) and concludes a usage contract.

[0083] The information processing device 10 of pharmaceutical wholesaler W updates (generates) manufacturer-specific information Dc based on the content of the concluded usage agreement and transaction agreement (Sa23). Specifically, it adds new application information Da (see Figures 5(a) and 5(b) above) to the manufacturer-specific information Dc corresponding to medical facility F which has concluded a usage agreement.

[0084] After updating (generating) manufacturer-specific information Dc, the information processing device 10 makes application A available for prescription on the facility terminal 20 (Sa24 in Figure 6). Specifically, the information processing device 10 ends the aforementioned estimation period and makes application A (facility application Af) available for download on the facility terminal 20. As described above, once facility application Af is downloaded on the facility terminal 20, prescription operations become available. In addition, when the information processing device 10 updates manufacturer-specific information Dc, it notifies the manufacturer terminal 40 of application manufacturer C. Upon receiving this notification, the manufacturer terminal 40 performs user registration (Sa25). For example, various information necessary to issue prescription codes is registered at medical facility F, which has concluded a user agreement.

[0085] Figure 7 is a diagram illustrating a specific example of the operation of information processing system 1 from the time app A is prescribed until the fee for app A is paid to app manufacturer C.

[0086] As described above, each time a prescription operation is received at the facility terminal 20 (Sb1 in Figure 7), a prescription notification is sent to the information processing device 10 of the pharmaceutical wholesaler W (Sb2 in Figure 7). This prescription notification includes the app ID of the prescribed app A, the facility ID of the medical facility F where app A was prescribed, and information about the patient to whom app A was prescribed (patient ID, delivery address, etc.). When the information processing device 10 receives a prescription notification from medical facility F, it executes the delivery process described above and updates the manufacturer-specific information Dc corresponding to medical facility F. In the specific example in Figure 7, we assume that prescription operations for app Ax from app manufacturer Cx, app Ay from app manufacturer Cy, and app Az from app manufacturer Cz are received.

[0087] For example, when the information processing device 10 receives a prescription notification indicating that app Ax has been prescribed, it refers to the accessory information in the app information Da of app Ax and arranges for the delivery of the necessary medical goods e (Sb3 in Figure 7). It also adds the number "1" to the prescription count in the app information Da of app Ax and adds new transaction information Dt (status "prescribed") to the manufacturer-specific information Dc (see Figures 5(b) and 5(d)). Similarly, when a prescription notification indicating that app Ay has been prescribed is received, and when a prescription notification indicating that app Az has been prescribed is received, various types of information are updated.

[0088] As described above, when App A is prescribed, the pharmaceutical wholesaler W bills the medical facility F for the cost of App A (Sb4). Specifically, the cost of each App A and the number of unbilled prescriptions for App A are included in App Information Da (see Figure 5(c) above). The information processing device 10 creates an invoice by referring to the above App Information Da. The invoice will also include the payment due date.

[0089] Pharmaceutical wholesaler W bills medical facility F for the charges for app A in a lump sum at predetermined intervals (for example, every month). For example, in the specific example shown in Figure 7, an invoice (electronic information) listing the charges for app Ax, app Ay, and app Az is sent to the facility's terminal 20. If the common app A is prescribed multiple times during that period, the charges for all of those prescriptions are billed together.

[0090] When a charge for app A is billed, the status of the transaction information Dt generated at the time of prescription for app A is changed to "billed" (Sb5). When an invoice is received from the pharmaceutical wholesaler W (information processing device 10), the app program PGf notifies the facility, and the invoice becomes available for display on the facility terminal 20.

[0091] Medical facility F remits the amount invoiced by pharmaceutical wholesaler W (Sc1). When the payment for app A is received by pharmaceutical wholesaler W, the information processing device 10 updates the transaction information Dt that manages the transaction for app A (Sc2). Specifically, the information processing device 10 updates the status of the transaction information Dt to "Received" and registers the receipt date and amount received (see Figure 5(d) above).

[0092] When app A is prescribed, pharmaceutical wholesaler W performs a fee reduction process (Sd1 in Figure 7). In this fee reduction process, the payment amount is calculated by subtracting the fee (approximately 30 percent of the price) from the price of the prescribed app A (the amount billed to medical facility F). The information processing device 10 then pays the calculated payment amount to each app manufacturer C (Sd2 in Figure 7).

[0093] When the fee for app A is paid to app maker C, the information processing device 10 updates the transaction information Dt for app A, which has completed payment. Specifically, it changes the status of transaction information Dt to "paid" and registers the payment date and payment amount. The fee referenced in the fee reduction process is included in the contract information of app information Da. Furthermore, the fee referenced in the fee reduction process may differ for each medical facility F, even for the same app A.

[0094] Incidentally, some medical facilities F may have difficulty paying for app A by the due date. On the other hand, app manufacturer C usually prefers to receive payment for app A by the due date. Considering these circumstances, pharmaceutical wholesaler W may, if necessary, pay app manufacturer C for app A before receiving payment from medical facility F. In other words, step Sd(1, 2) may be executed before step Sc(1, 2) described above. If payment for app A is made to app manufacturer C before receiving payment from medical facility F, the status of transaction information Dt will be changed to "awaiting receipt". With this configuration, app A can be smoothly prescribed to patients C who need it.

[0095] Furthermore, the pharmaceutical wholesaler W can monitor the type and number of prescriptions for app A issued at each medical facility F based on prescription notifications. For example, consider a scenario where the number of app A prescriptions during a specific period reaches an unusually high number. In such a case, it is possible that medical facility F is fraudulently receiving payment from the insurer by prescribing app A even though it is not actually treating patients. The same applies if, for example, medical facility F does not offer smoking cessation clinics but is prescribed app A to support smoking cessation. In such cases, the information processing device 10 is configured to temporarily restrict prescription operations on the facility-side terminal 20.

[0096] Figure 8 is a schematic diagram of a specific example of an application image Gc. The application image Gc becomes displayable when the application program PGp is ​​executed on the patient terminal 30. As shown in Figure 8, the application image Gc is composed of each application-specific area Rb (1, 2, 3…). Each of these application-specific areas Rb corresponds to each application A (patient application Ap) prescribed to patient P.

[0097] As shown in Figure 8, the app-specific area Rb displays various information about app A corresponding to that app-specific area Rb (similar to the Rb shown in Figure 8). Specifically, the name and purpose of the prescribed app A are displayed in the app-specific area Rb corresponding to app A. Furthermore, the appearance of the app-specific area Rb changes depending on whether or not the prescribed app A has already been downloaded to the patient terminal 30.

[0098] For example, the specific example in Figure 8 assumes that of the prescribed apps A, app Ax has not been downloaded to the patient's terminal 30, but app Ay has been downloaded. In this case, a download button is displayed in the app-specific area Rb1 corresponding to app Ax. By selecting the download button (for example, by touching it), the patient P can download app A (patient application Ap) corresponding to the app-specific area Rb where the download button is displayed from the app store Mp.

[0099] Meanwhile, in the application-specific area Rb2 corresponding to application Ay, a start button and an evaluation button are displayed. By selecting the start button, patient P can run application A, which corresponds to the application-specific area Rb where the start button is displayed, on the patient terminal 30. Patient P can also select the evaluation button to input an evaluation of application A (e.g., ease of use, degree of symptom improvement) corresponding to the application-specific area Rb where the evaluation button is displayed. The evaluation entered on the patient terminal 30 is transmitted to the information processing device 10 by the operation of the application program PGp. The information processing device 10 adds the evaluation of application A entered by patient P to the evaluation information of application A.

[0100] When the evaluation button is selected, a nearly identical evaluation input image is displayed on the patient terminal 30, regardless of the type of app A being evaluated. This configuration has the advantage of simplifying the evaluation of app A compared to a configuration where, for example, the evaluation input image differs depending on the type of app A.

[0101] Furthermore, the expiration date for app A is set to be the period after a predetermined time (for example, about 6 months) has elapsed since the app A was prescribed. In the specific example in Figure 8, we assume that among the prescribed apps A, the expiration dates for apps Ax and Ay have not expired, but the expiration date for app Az has expired. A facility search button is displayed in the app-specific area Rb corresponding to the expired app A. When the facility search button is selected, a list of medical facilities F that can prescribe app A corresponding to the app-specific area Rb on which the facility search button is displayed is shown.

[0102] Figures 9(a) to 9(c) are flowcharts illustrating specific examples of the operation of the information processing system 1 of this embodiment. As shown in Figure 9(a), when the facility terminal 20 receives a prescription operation (Sx1), it sends a prescription notification to the information processing device 10 (pharmaceutical wholesaler W) (Sx2). The prescription notification includes information about the type of application A prescribed, the medical facility F that prescribed application A, and the patient P to whom application A was prescribed.

[0103] Upon receiving a prescription notification, the information processing device 10 updates the manufacturer-specific information Dc (Sx3). Specifically, based on the received prescription notification, the information processing device 10 updates the number of prescriptions in the manufacturer-specific information Dc (app information Da) and adds new transaction information Dt to the manufacturer-specific information Dc. The information processing device 10 also identifies the prescribed app A from the received prescription notification and performs a delivery process (Sx4) to deliver the medical goods e used with app A.

[0104] As shown in Figure 9(b), when pharmaceutical wholesaler W bills medical facility F for the fee of app A, the information processing device 10 calculates the billing amount (Sy1). As described above, in this embodiment, the billing amount is calculated from the fee of app A and the number of unbilled prescriptions for the app. However, it is also possible to configure the system so that the total of the unpaid fees for each app A for medical facility F is calculated from the manufacturer-specific information Dc (transaction information Dt) of medical facility F. Once the billing amount is calculated, pharmaceutical wholesaler W uses the information processing device 10 to send an invoice (electronic data) to the facility terminal 20 (Sy2).

[0105] Furthermore, once billing for app A is complete, the information processing device 10 updates the manufacturer-specific information Dc (Sy3). Specifically, the status of the transaction information Dt for app A is updated to "billed". When the payment for app A is sent from medical facility F (facility terminal 20) (Sy4), the information processing device 10 updates the status of the transaction information Dt for app A, which has received the payment, to "received" (Sy5).

[0106] As shown in Figure 9(c), when pharmaceutical wholesaler W pays app manufacturer C for app A, the information processing device 10 calculates the payment amount (Sz1). Specifically, the payment amount is calculated by subtracting the commission from the total amount of fees billed (received) to medical facility F. Once the payment amount is calculated, pharmaceutical wholesaler W uses the information processing device 10 to pay the amount to app manufacturer C (Sz2). The information processing device 10 also updates the status of the transaction information Dt for app A, for which payment has been made, to "paid" among the manufacturer-specific information Dc (Sz3).

[0107] <Variation> Each of the above forms can be modified in various ways. Specific examples of modifications are given below. Two or more forms can be arbitrarily selected from the following examples and combined as appropriate.

[0108] In each configuration, even before concluding a usage agreement for app A, the facility terminal 20 may be configured to allow downloading of the facility application Af and to accept prescription operations for the patient application Ap. In other words, the system may be configured to allow prescription of app A to patient P before determining the price of app A.

[0109] In the above modified scenario, if App A is prescribed before a service agreement is concluded, manufacturer-specific information Dc (including App information Da) is created, just as if a service agreement had been concluded. Also, if App A is prescribed before a service agreement is concluded, transaction information Dt is generated, just as if App A were prescribed after a service agreement had been concluded. However, the status of this transaction information Dt will be "Pre-Contract". Furthermore, the "Billing Amount" included in transaction information Dt will be the predetermined pre-contract rate.

[0110] The above pre-contract fees are usually higher than the amount charged when a service agreement is concluded (hereinafter referred to as the "post-contract fee"). If a service agreement is not concluded within the predetermined period, the pre-contract fee will be billed to medical facility F. When the pre-contract fee is received from medical facility F, the status of transaction information Dt will be changed to "Pre-contract fee received". Subsequently, when a service agreement is concluded and the post-contract fee for application A is determined, the information processing device 10 will automatically calculate the difference between the pre-contract fee and the post-contract fee.

[0111] Specifically, from the transaction information Dt of app A, transaction information Dt with the status "Fee received before contract" is extracted. The information processing device 10 then automatically calculates the difference between the fee before contract and the fee after contract from the extracted transaction information Dt. The calculated difference is then refunded from the pharmaceutical wholesaler W to the medical facility F. This modified configuration has the advantage of making it easier for app A to be prescribed to patients P who need it, compared to a configuration where app A cannot be prescribed until a usage contract has been concluded. If a usage contract is concluded within the aforementioned deadline, the status of the transaction information Dt is changed to "Prescribed," and the billed amount is changed to the fee after contract.

[0112] <Summary of the operation and effects of the embodiment> <First aspect> The information processing device (10) in this embodiment includes a billing processing unit (12) that enables billing of the medical institution (F) for a medical application (App) when the medical application is prescribed at the medical institution, and a payment processing unit (14) that enables payment of the medical application fee to the provider of the medical application (App maker C). According to this embodiment, for example, the medical institution does not need to pay the medical application fee directly to the provider, thus reducing the workload on the medical institution.

[0113] <Second aspect> The information processing device in this embodiment further comprises a reduction processing unit (13) that deducts a predetermined fee from the fee of a medical application, and a payment processing unit makes it possible to pay the fee of the medical application with the fee reduced to the provider. This embodiment has the advantage that the application manufacturer can omit the task of paying a fee to the pharmaceutical wholesaler.

[0114] <Third aspect> The information processing device of this embodiment further comprises a delivery processing unit (15) that enables the delivery of medical articles (e) to be used with the medical application when the medical application is prescribed. This embodiment has the advantage that neither the application manufacturer nor the patient needs to arrange for the delivery of the medical articles.

[0115] <Fourth aspect> The information processing device in this embodiment enables terminal devices in medical institutions to accept operations for requesting price estimates for medical applications. According to this embodiment, for example, the workload on medical institutions is reduced compared to a configuration in which medical institutions must perform price estimate requests for medical applications in their own way.

[0116] <Fifth aspect> The information processing method of this embodiment is an information processing method using an information processing device (10) and a terminal device (20) managed by a medical institution, comprising the steps of: the terminal device receiving an operation to prescribe a medical application (Sx1 in Figure 9); the terminal device sending a prescription notification in response to the operation (Sx2 in Figure 9); the information processing device receiving the prescription notification; the information processing device billing the medical institution for the medical application after receiving the prescription notification (Sy2 in Figure 9); and the information processing device paying the medical application fee to the provider of the medical application (Sz2 in Figure 9). According to this embodiment, the same effects as the first embodiment described above can be achieved.

[0117] <Sixth aspect> The program in this embodiment causes a terminal device managed by a medical institution (facility-side terminal 20) to perform the following steps: sending a request for a quote on the cost of a medical application (Sa2 in Figure 6), displaying the cost of the medical application (see Figure 4), accepting an operation to prescribe the medical application (Sb1 in Figure 7), and sending a prescription notification in response to the operation (Sb2 in Figure 7). This embodiment achieves the same effects as the first embodiment described above. [Explanation of Symbols]

[0118] 1...Information processing system, 10...Facility terminal, 10...Information processing device, 11...Storage unit, 12...Billing processing unit, 13...Reduction processing unit, 14...Payment processing unit, 15...Delivery processing unit, 16...Quotation processing unit, 17...Contract processing unit, 20...Facility terminal, 30...Patient terminal, 40...Manufacturer terminal.

Claims

1. When a medical application is prescribed at a medical institution, a billing processing unit enables billing of the medical institution for the medical application, An information processing device comprising a payment processing unit that enables payment of the fees for the aforementioned medical application to the provider of the medical application.

2. The system further includes a fee reduction processing unit that deducts a predetermined fee from the fee of the aforementioned medical application, The payment processing unit enables the payment of the fee for the medical application, with the reduced fee, to the provider. The information processing apparatus according to claim 1.

3. The system further comprises a delivery processing unit that enables the delivery of medical items to be used with the medical application once the medical application has been prescribed. The information processing apparatus according to claim 1.

4. The terminal device at the aforementioned medical institution will be made capable of accepting operations to request a price estimate for the medical application. The information processing apparatus according to claim 1.

5. Information processing device and Terminal devices managed by medical institutions, An information processing method using, The terminal device receives an operation to prescribe a medical application, The steps include: in response to the above operation, the terminal device transmits a prescription notification; The steps include: the information processing device receiving the prescription notification; After receiving the prescription notification, the information processing device charges the medical institution for the medical application fee; The process includes the information processing device paying the fee for the medical application to the provider of the medical application, and An information processing method comprising the following.

6. Terminal devices managed by medical institutions, Steps to submit a request for a price quote for a medical application, The steps include displaying the fees for the aforementioned medical application, A step of accepting an operation for prescribing the aforementioned medical application, The steps include sending a prescription notification in accordance with the above operation. A program that executes the command.

Images