System, program, and method
The system addresses financial instability in medical institutions by calculating usage fees based on pre-determined service periods, ensuring consistent revenue through differentiated fees, regardless of service utilization, thereby improving the quality of life for medical professionals.
Patent Information
- Application Number
- JP2024180359
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-07-26
- Filing Date
- 2024-10-15
- Publication Date
- 2025-10-14
- Estimated Expiration
- 2043-06-15
AI Technical Summary
Medical institutions face financial instability due to outsourcing medical staff, and existing subscription models charge fixed fees regardless of service usage, leading to inefficiencies and potential decline in quality of life for medical professionals.
A system that calculates usage fees based on pre-determined service periods, allowing input, but not allowing changes or deletions during those periods, and differentiates fees for actual usage, ensuring charges are incurred regardless of service utilization.
The system provides a flexible and efficient method for calculating usage fees, reducing financial instability for medical institutions and improving the quality of life for medical professionals by ensuring consistent revenue streams.
Smart Images

Figure 0007752892000001 
Figure 0007752892000002 
Figure 0007752892000003
Abstract
Description
[Technical Field]
[0001] The present invention relates to a system, a program, and a method. [Background technology]
[0002] In medical settings, medical professionals must always be on standby to respond when a patient's condition suddenly changes outside of consultation hours or when a patient is brought in. Furthermore, when there are not enough specialized medical professionals, there are cases where medical professionals outside of working hours are contacted to respond. To address these long working hours and the decline in quality of life of medical professionals, many medical institutions outsource their medical staff. However, when medical institutions frequently outsource, unexpected expenses can lead to financial deterioration.
[0003] Incidentally, a product provision management system that improves user satisfaction in services that provide products through regular purchases or subscriptions has been disclosed (Patent Document 1). Subscriptions are a sales format in which users pay a usage fee according to the period of service use, or a sales format in which the usage fee is fixed monthly and the service is available for unlimited use, but the contract period for the service cannot be changed flexibly, and users are charged a fixed fee even for periods when they do not need to receive the service. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Publication No. 2020-194363 Summary of the Invention [Problem to be solved by the invention]
[0005] The present invention has the following objectives, for example: A first objective of the present invention is to provide a system capable of calculating usage fees for services that incur usage fees regardless of whether the user uses the service. A second objective of the present invention is to provide a system that makes it easy to calculate usage fees for services. [Means for solving the problem]
[0006] The object of the present invention is to [1] A system comprising at least one computer device, the system comprising: a period input means for receiving input of a period for which a user desires to use a service; and a calculation means for calculating a service usage fee for a predetermined period based on the period for which the input was received, wherein the calculation means calculates the service usage fee for the predetermined period based on the period for which the input was received, regardless of whether the user used the service during the period for which the input was received; [2] A non-controllable means for disabling the acceptance of input, deletion of input, and / or change of input during the period for which the user wishes to use the service, depending on the date and time for accepting input by the user; The system according to [1], [3] The system according to [1] or [2] above, wherein the calculation means calculates the service usage fee for a predetermined period in accordance with rules that differ for each user; [4] The system according to any one of [1] to [3] above, wherein the calculation means calculates the service usage fee for a predetermined period based on the attributes of the period in which the input is accepted; [5] The system according to any one of [1] to [4] above, comprising a user terminal operated by the user, the user terminal comprising a calendar display means for displaying a calendar that allows the user to input a period for which the user wishes to use the service, and the period input means for accepting input of the period for which the user wishes to use the service by selecting a period from the calendar; [6] The system according to any one of [1] to [5] above, wherein when an application for use of the service is made for a period other than that accepted by the period input means, the calculation means calculates the service usage fee for the specified period by adding together the first usage fee calculated based on the period for which the input was accepted and the third usage fee calculated in accordance with the user's use of the service for the service accepted for a period other than that for which the input was accepted; [7] A system according to any one of [1] to [6] above, comprising a user terminal operated by a user and an applicant terminal operated by an applicant for the service, and comprising application acceptance means for accepting an application to use the service for a period for which the applicant wishes to use the service, input of which is accepted through operation of the user terminal; information transmission means for transmitting information about the service corresponding to the accepted application to the applicant terminal; and application acceptance means for accepting an application for the service corresponding to the received information through operation of the applicant terminal; [8] The system according to [7], further comprising: an applicant identification means for identifying a predetermined number of applicants by reducing the probability of identifying an applicant who satisfies predetermined conditions from among a plurality of applicants whose applications for the service have been accepted; [9] The system according to any one of [1] to [8], wherein the calculation means calculates the service usage fee for a predetermined period by adding a first usage fee calculated based on the period for which the input was accepted and a second usage fee calculated in accordance with the user's use of the service;
[10] A program executed on at least one computer device, causing the computer device to function as a period input means for accepting input of a period for which a user wishes to use a service, and a calculation means for calculating a service usage fee for a predetermined period based on the period for which the input was accepted, wherein the calculation means calculates the service usage fee for the predetermined period based on the period for which the input was accepted, regardless of whether the user used the service during the period for which the input was accepted;
[11] A method executed in a system having at least one computer device, the method comprising: a period input step of receiving input from a user of a period for which the user desires to use a service; and a calculation step of calculating a service usage fee for a predetermined period based on the period for which the input was received, wherein the calculation step calculates the service usage fee for the predetermined period based on the period for which the input was received, regardless of whether the user used the service during the period for which the input was received;
[12] A system comprising at least a user terminal operated by a user and an applicant terminal operated by an applicant for a service, the system comprising: an application acceptance means for accepting an application to use a service by operating the user terminal; an information transmission means for transmitting information about a service corresponding to the accepted application to the applicant terminal; and an application acceptance means for accepting an application for a service corresponding to the received information by operating the applicant terminal;
[13] A system comprising a user terminal operated by a user and an administrator terminal operated by an administrator, the system comprising: a period input means for accepting input of a period for which the user wishes to use a service from the user terminal; and a display control means for controlling the administrator terminal to display a first period corresponding to the period for which the user wishes to use the service for which input has been accepted, and a second period corresponding to the period for which input via the period input means is not accepted, the display control means controlling the system to display the first period and the second period in different display modes;
[14] The system according to
[13] , further comprising a selection means for accepting a selection from one user in the administrator terminal, and a display control means for controlling the display of the first period and the second period corresponding to the one user whose selection has been accepted by the selection means on the administrator terminal;
[15] The system according to either
[13] or
[14] , wherein the display control means controls the display to be in a different display mode during the first period depending on the attributes of the period during which the user wishes to use the service for which the input was received;
[16] The system according to any one of
[13] to
[15] , wherein the display control means controls to display the first period and the first time period on a calendar.
[17] A program that causes a computer device to function as a period input means that accepts input of a period for which the user wishes to use a service from a user terminal, and a display control means that controls the display on an administrator terminal of a first period corresponding to the period for which the user wishes to use the service and a second period corresponding to a period other than the period for which the user wishes to use the service, and the display control means controls the display of the first period and the second period in different display modes;
[18] A method executed in a system having at least one computer device, comprising: a period input step of receiving input of a period for which a user desires to use a service from a user terminal; and a display control step of controlling an administrator terminal to display a first period corresponding to the period for which the user desires to use the service for which the input has been received, and a second period corresponding to a period other than the period for which the user desires to use the service for which the input has been received, wherein the display control step controls to display the first period and the second period in different display modes. A method comprising:
[19] A system comprising at least one computer device used for a service for which a usage fee is charged regardless of whether the user actually uses the service during the period for which the user desires to use the service, the system comprising: a period input means for receiving input of the period for which the user desires to use the service; and a calculation means for calculating the usage fee for the service for a predetermined period based on the period for which the input is received;
[20] A program executed on at least one computer device used in a service for which a usage fee is charged regardless of whether the user actually uses the service during the period for which the user desires to use the service, the program causing the computer device to function as a period input means for accepting input of the period for which the user desires to use the service by the user, and as a calculation means for calculating the usage fee for the service for a specified period based on the period for which the input is accepted;
[21] A method executed in a system having at least one computer device used for a service that incurs a usage fee regardless of whether the user actually uses the service during the period for which the user desires to use the service, the method comprising: a period input step for receiving input of the period for which the user desires to use the service by the user; and a calculation step for calculating the usage fee for the service for a predetermined period based on the period for which the input is received;
[22] A system comprising at least one computer device used for a service for which a fee is charged regardless of whether the user actually uses the service during the period for which the user wishes to use the service, the system comprising: a period input means for receiving input of the period for which the user wishes to use the service from the user terminal; and a display control means for controlling the administrator terminal to display a first period corresponding to the period for which the user wishes to use the service for which the input has been received, and a second period corresponding to the period for which the input by the period input means has not been received, the display control means controlling the system to display the first period and the second period in different display modes;
[23] A program executed on at least one computer device, used for a service for which a usage fee is charged regardless of whether the user actually uses the service during the period for which the user desires to use the service, the program causing the computer device to function as a period input means for accepting input of the period for which the user desires to use the service from the user terminal, and a display control means for controlling the administrator terminal to display a first period corresponding to the period for which the user desires to use the service for which the input has been accepted, and a second period corresponding to the period for which the input by the period input means has not been accepted, and the display control means controls the first period and the second period to be displayed in different display modes;
[24] A method executed in a system having at least one computer device used for a service for which a usage fee is charged regardless of whether the user actually uses the service during the period for which the user desires to use the service, the method comprising: a period input step for accepting input of a period for which the user desires to use the service from a user terminal; and a display control step for controlling an administrator terminal to display a first period corresponding to the period for which the user desires to use the service for which the input has been accepted, and a second period corresponding to the period for which the user has not accepted input by the period input means, wherein the display control step controls to display the first period and the second period in different display modes; This can be achieved by: [Effects of the Invention]
[0007] According to the present invention, it is possible to provide a system that can calculate a usage fee for a service that incurs a usage fee regardless of whether the user uses the service. According to the present invention, it is possible to provide a system that makes it easy to calculate a usage fee for a service. [Brief explanation of the drawings]
[0008] [Figure 1] 1 is a block diagram showing a configuration of a system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing a configuration of an administrator terminal according to the embodiment of the present invention. [Figure 3] 2 is a block diagram showing a configuration of a server device according to an embodiment of the present invention; FIG. [Figure 4] FIG. 10 is a flowchart showing an execution process according to an embodiment of the present invention. [Figure 5] FIG. 10 is a flowchart showing a service period input process according to an embodiment of the present invention. [Figure 6] FIG. 2 is a diagram showing an example of a display screen in the system according to the embodiment of the present invention. [Figure 7] FIG. 10 is a flowchart showing a service execution process according to the embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing an example of an implementation management table according to the embodiment of the present invention. [Figure 9] FIG. 10 is a flowchart showing an invoice issuing process according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram showing an example of a usage fee management table according to an embodiment of the present invention. [Figure 11] FIG. 10 is a flowchart showing a display process according to the embodiment of the present invention. [Figure 12] FIG. 2 is a diagram showing an example of a display screen in the system according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0009] The following describes embodiments of the present invention with reference to the drawings. However, the present invention is not limited to the following embodiments as long as it does not violate the spirit of the present invention. The following description of the effects is one aspect of the effects of the embodiments of the present invention and is not limited to those described here. The order of each process constituting the flowcharts described below is random as long as no contradictions or inconsistencies occur in the process content. Furthermore, it is possible to omit some of the processes constituting the flowcharts or add new processes to each process constituting the flowcharts as long as no contradictions or inconsistencies occur in the process content. Furthermore, the device that executes each process constituting the flowcharts can be changed to another device as long as it does not violate the spirit of the present invention. In this case, the process content can be changed so as not to cause contradictions or inconsistencies in the process content.
[0010] Fig. 1 is a block diagram showing the configuration of a system according to an embodiment of the present invention. As shown in the figure, the system is composed of an administrator terminal 1, a server device 2, a user terminal 3, an applicant terminal 4, and a communication network 5. The administrator terminal 1, the server device 2, the user terminal 3, and the applicant terminal 4 are communicatively connected to one another via the communication network 5. The system may also be composed of multiple administrator terminals 1a-1z (not shown), multiple user terminals 3a-3z, and multiple applicant terminals 4a-4z. The system may also be composed of only at least one computer device.
[0011] A system according to an embodiment of the present invention is operated by an administrator. Users and applicants can use the system as users. By using the system according to an embodiment of the present invention, users can recruit workers for specific tasks and use services related to the introduction of workers who will undertake the tasks. Applicants can apply for the tasks that have been recruited. Once an applicant is selected to perform the task, the applicant can perform the task. The administrator and / or users can easily calculate the usage fees for users to use the system and / or the compensation for workers.
[0012] The administrator terminal 1 is a terminal operated by an administrator who operates the system. The administrator terminal 1 may be a stationary terminal installed in a company office or the like, or may be a portable terminal that can be carried by the user when traveling. Examples of the administrator terminal 1 include conventional mobile phones, tablet terminals, smartphones, and desktop or notebook personal computers.
[0013] 2 is a block diagram showing the configuration of an administrator terminal according to an embodiment of the present invention. The administrator terminal 1 includes a control unit 11, a main memory 12, a storage unit 13, an input device 14, a display device 15, and a communication interface 16, all of which are connected via an internal bus.
[0014] The control unit 11 is composed of a CPU and a ROM. The control unit 11 executes programs stored in the storage unit 13 and controls the administrator terminal 1. For example, a RAM is used as the main memory 12. The main memory 12 is a work area for the control unit 11. The storage unit 13 is a storage area for saving programs and data. The control unit 11 performs arithmetic processing based on the programs and data read from the main memory 12 and data input via the input device 14.
[0015] The display device 15 has a display screen. The control unit 11 outputs a video signal for displaying an image on the display screen according to the result of the arithmetic processing. Here, the display screen may be a touch panel equipped with a touch sensor. In this case, the touch panel functions as the input device 14.
[0016] The communication interface 16 can be connected to the communication network 5 wirelessly or via a wired connection, and can send and receive data to and from the server device 2, the user terminal 3, or the applicant terminal 4 via the communication network 5. Data received via the communication interface 16 is loaded into the main memory 12, and the control unit 11 performs arithmetic processing.
[0017] The user terminal 3 and applicant terminal 4 may have the same configuration as the administrator terminal 1. The user terminal 3 and applicant terminal 4 may each include, for example, a control unit, main memory, storage unit, input device, display device, and communication interface, and may be connected to each other by an internal bus. In a system according to one embodiment of the present invention, it is preferable to use a mobile terminal on which a dedicated application program is installed as the applicant terminal 4.
[0018] The user terminal 3 is a terminal in the system that is operated by a user who uses the service. The user can also operate the user terminal 3 and input the period for which they wish to use the service. The user can receive worker introductions as a service. Specifically, the user can operate the user terminal 3 and input the job for which they are recruiting workers and / or the period for which they may recruit workers. Once the user receives a worker introduction and decides to assign the worker to the job, they can become the employer of the worker.
[0019] The applicant terminal 4 is a terminal operated by an applicant who applies for work related to a recruited service in the system. When the applicant is selected to take on the recruited work, he or she can become a worker in charge of carrying out the work.
[0020] The server device 2 mainly stores information on users and applicants, service usage information, information on business related to the service, and service usage fees. The server device 2 is preferably managed by an administrator who operates the administrator terminal 1.
[0021] 3 is a block diagram showing the configuration of a server device according to an embodiment of the present invention. The server device 2 includes a control unit 21, a main memory 22, a storage unit 23, and a communication interface 24, all of which are connected by an internal bus.
[0022] The control unit 21 is composed of a CPU and a ROM, and executes programs stored in the storage unit 23 to control the server device 2. The control unit 21 also has an internal timer that measures time. The main memory 22 is the work area of the control unit 21. The storage unit 23 is a memory area for saving programs and data. The control unit 21 reads out the programs and data from the main memory 22 and performs arithmetic processing based on information received from the administrator terminal 1, the user terminal 3, or the applicant terminal 4.
[0023] In the embodiment of the present invention, the server device 2 is described as storing various types of information, determining a person in charge, transmitting various types of information, etc. However, the processing by the server device 2 may not only be executed by only one computer device, but may also be executed in a distributed manner by multiple computer devices. For example, the processing by the server device 2 such as storing various types of information, determining a person in charge, and transmitting various types of information may be achieved by a distributed ledger technology using a blockchain instead of the server device 2. The blockchain network may be constructed as a private network or as a public network. By managing information using a blockchain, security can be maintained.
[0024] [System Overview] An overview of a system according to an embodiment of the present invention will be described. Fig. 4 is a diagram showing a flowchart of execution processing according to an embodiment of the present invention. Details of each process included in the flowchart will be described later.
[0025] First, users and applicants register to use the system (step S1). Next, a service period input process is executed in which the user inputs the period for which they wish to use the service (step S2). Next, a service execution process is executed in which a person in charge is selected from among the applicants for the work related to the requested service (step S3). Next, an invoice issuance process is executed in which the cost to be charged to the user is calculated and an invoice is issued (step S4). Then, payment is made (step S5). Steps S1 to S5 complete the execution process.
[0026] Here, the system of the present invention can provide services to users and / or applicants. A service is, for example, labor or benefits provided for another person that can be the subject of an independent commercial transaction. Specific examples of services include advertising, consulting, job placement, providing various information, teaching various knowledge, preparing various documents, running and hosting various events, providing various facilities, conducting various surveys, and conducting various tests and research.
[0027] The system of the present invention can be applied to all services related to labor introduction. In this case, the service provided to the user may be labor introduction. Also, the service provided to the worker may be job introduction. The system of the present invention can also be applied to services such as labor dispatch and the contracting of work by workers. Hereinafter, a job for which a user is recruiting workers may be referred to as a "job."
[0028] The employment status of workers is not particularly limited and can be designed as appropriate. For example, workers may work as full-time employees, contract employees, temporary workers, part-time workers, or other employment status. Alternatively, workers may work as contractors. The length of a worker's employment is not particularly limited and can be designed as appropriate. For example, a worker may work for a specified period of time, such as a few hours, a few days, a few weeks, a few months, or a few years, or may work for an indefinite period. Workers include those with no experience in the work, those with little experience, those with experience, and experts in a particular field. The industry in which a worker works is not particularly limited and can be designed as appropriate. For example, a worker may work in an industry such as the medical industry, the beauty industry, or the food and beverage industry.
[0029] In the system according to this embodiment, when a user inputs in advance the period for which he or she wishes to use the service, a predetermined usage fee (hereinafter also referred to as the first usage fee) calculated from the usage fee for the service per unit time or per unit period is incurred, regardless of whether or not the service is actually used during the input period. The period is a concept that includes years, months, weeks, days, or hours, and may be continuous or discontinuous. Hereinafter, the period may be referred to as a "schedule." The first usage fee may also be paid by the user to the system administrator.
[0030] "Actually using the service" means recruiting workers for a specific job. The number of times a user can actually use the service during the period for which the user wishes to use the service may or may not be limited to a certain number of times. For example, a user may use the service up to five times, up to ten times, or any number of times during the period for which the user wishes to use the service.
[0031] If a user can use the service any number of times within the period for which the user wishes to use the service, a fixed first usage fee may be charged regardless of the number of times the service is used, or different first usage fees may be charged depending on the number of times the service is used.
[0032] In addition, if there is a limit to the number of times that a user can actually use the service for a certain first usage fee within the period in which the user wishes to use the service, an additional usage fee may be charged for the number of times the service is used in excess of the limit.
[0033] In the system according to this embodiment, when a user actually uses the service and requests work from a worker, compensation to the worker (hereinafter also referred to as a second usage fee) may be incurred in addition to the first usage fee. The user may set the amount of the second usage fee as appropriate depending on the work content of the case. The second usage fee may be paid by the user to the worker, or may be paid by the system administrator to the worker.
[0034] Alternatively, if the user has input in advance the period for which he or she wishes to use the service, the second usage fee may not be charged to the user even if the user actually uses the service within the input period. If the second usage fee is not charged to the user, it is preferable that the worker be paid a remuneration by the system administrator.
[0035] In addition, in the system according to this embodiment, a user may be able to recruit workers for a specific job even outside the period for which the user entered their desire to use the service. If the user actually uses the service outside the entered period, a predetermined usage fee (hereinafter also referred to as a third usage fee) calculated from the service usage fee per unit time, per unit period, or per number of times the service is used may be incurred. The period is a concept that includes years, months, days, or hours, and may be continuous or discontinuous. The third usage fee may be paid by the user to the system administrator.
[0036] Furthermore, if the user actually uses the service outside the period for which they entered their desired service use, a third usage fee and a second usage fee may be incurred. When the system of the present invention is applied to a medical professional referral service, it is preferable that the second usage fee be paid by the user to the worker. Furthermore, the second usage fee may be incurred by the user even if the user actually uses the service within the period for which they previously entered their desired service use.
[0037] The service period input process in step S2 and the service execution process in step S3 can be executed as appropriate after the usage registration process in step S1. The service period input process in step S2 or the service execution process in step S3 can be omitted. The invoice issuance process in step S4 is preferably executed at predetermined intervals. If the invoice amount is 0 yen in the invoice issuance process, the payment execution in step S5 can be omitted.
[0038] In the following embodiment, we will mainly explain a service in which a medical institution's staff member receives referrals from medical professionals for surgeries and other operations. In this case, the user is the medical institution's staff member, and the applicant is a medical professional. Note that medical professionals include all workers involved in medical care, such as doctors, anesthesiologists, dentists, pharmacists, nurses, licensed practical nurses, public health nurses, midwives, nutritionists, diagnostic radiologists, dental hygienists, and dental technicians.
[0039] [User registration] In the system according to the present embodiment, information about users who use the system is registered in advance in the server device 2. In addition, each user may be assigned a user ID for identifying the user.
[0040] First, the medical institution staff logs in to the system by accessing the server device 2 via a web browser from the user terminal 3. Alternatively, the medical institution staff may log in to the system by launching an application program (hereinafter referred to as a dedicated app) downloaded to the user terminal 3 and accessing the server device 2.
[0041] Next, the medical institution staff operates the user terminal 3 to perform initial settings, inputting information about the medical institution to which the staff member belongs. As initial settings, the staff member inputs medical institution information about the medical institution, such as the name of the medical institution and the address of the medical institution, basic remuneration information about compensation for workers, payment information about salary payments, such as the payroll closing date, payroll payment month, and payroll payment date, and staff member information about the staff member, such as the staff member's department, name, email address, etc. Staff member information can be registered for multiple people in association with one medical institution.
[0042] Next, the input information is sent to the server device 2, whereby the medical institution is registered. Specifically, the input information is stored in the storage unit 23 in association with the medical institution. It is preferable that the registered medical institution be set with medical institution identification information (hereinafter also referred to as medical institution ID) as a user ID. The medical institution ID is identification information that can identify the medical institution. The medical institution ID is stored in the storage unit 23 in association with the above input information.
[0043] It is also preferable that the system creates a dedicated page for registered medical institutions. Even if different staff members operate different user terminals 3, by using the same medical institution ID, each staff member can display the same dedicated page on the user terminal 3. Furthermore, by setting the medical institution ID, even if different staff members operate different user terminals 3, each staff member can operate the user terminal 3 to input the period for which the service is desired to be used and apply for the service. Furthermore, since the information of multiple staff members is stored in association with one medical institution ID, even if different staff members operate different user terminals 3, notifications can be received on each user terminal 3.
[0044] Similarly, medical professionals applying for jobs also operate the applicant terminal 4 to input information for initial setup. For initial setup, the medical professional inputs applicant information about the applicant (medical professional), such as name, gender, date of birth, address, mobile phone number, email address, area of responsibility, and career history. By transmitting the input information to the server device 2, the applicant is registered as an applicant in the server device 2. Specifically, the input information is stored in the storage unit 23 in association with the applicant. It is preferable that applicant identification information (hereinafter also referred to as applicant ID) is set as the user ID for registered applicants. The applicant ID is identification information that can identify a medical institution. The applicant ID is stored in the storage unit 23 in association with the above input information.
[0045] It is also preferable that the system creates a dedicated page for registered applicants. Even if a medical professional uses multiple devices, the same page can be displayed on each device using the same applicant ID. Furthermore, since multiple contact information can be stored in association with a single applicant ID, even if a medical professional uses multiple devices, they can receive notifications and apply for jobs on each device.
[0046] When logging in to the system, the user may be required to enter a pre-registered user ID and password, or may be required to enter a pre-registered email address and password.
[0047] Although the above describes an aspect in which a user ID is set for each user, a user ID may be set for each terminal used by the user.
[0048] [Service period input process] Next, the service period input process (step S2) in the system will be described. Fig. 5 is a diagram showing a flowchart of the service period input process according to the embodiment of the present invention.
[0049] First, a medical institution staff member logs in to the system by inputting a user ID and password into the user terminal 3. Then, the medical institution staff member operates the user terminal 3 to send a display request to the server device 2, requesting the display of a schedule input screen for inputting the period for which the user wishes to use the service (step S11). In step S11, time information regarding the time when the display request was sent may be sent from the user terminal 3 to the server device 2. When the server device 2 receives the display request (step S12), it sends schedule input screen display information for displaying the schedule input screen to the user terminal 3 from the server device 2 (step S13). When the user terminal 3 receives the schedule input screen display information (step S14), the schedule input screen is displayed (step S15).
[0050] A medical institution staff member selects and inputs a desired date for using the service on the user terminal 3 (step S16). Schedule information relating to the inputted date is transmitted from the user terminal 3 to the server device 2 (step S17), and the server device 2 receives the date information (step S18). The server device 2 registers the date information (step S19). Steps S11 to S19 complete the service period input process. Note that, hereinafter, the date on which the user wishes to use the service is also referred to as the desired period.
[0051] 6 is a diagram showing an example of a display screen in the system according to the embodiment of the present invention. Specifically, it shows an example of the display screen of the user terminal 3 displayed in step S15. The schedule input screen 30 displays a reservation input field 31, but other information may also be displayed.
[0052] In the schedule input screen 30 of FIG. 6 , a calendar from March 2020 to May 2020 is displayed in the reservation input field 31. A medical institution staff member can input a desired date for which the service is to be used by operating the user terminal 3 to select a date on the displayed calendar. When the medical institution staff member operates the user terminal 3 to select a date on the displayed calendar, the display mode may change so that it is clear whether the date has been selected. In FIG. 6 , the area corresponding to the unselected unselected date 32 and the area corresponding to the selected selected date 33 are displayed in different colors. When the medical institution staff member operates the user terminal 3 to further select the selected date 33, the selection of the date is canceled. When the selection of the date is canceled, the display of the selected selected date 33 may return to the display of the unselected date 32.
[0053] Furthermore, when a medical institution staff member operates the user terminal 3 and selects icon 35, a calendar from December 2019 to February 2020 is displayed. When a medical institution staff member operates the user terminal 3 and selects icon 35 on the screen displaying the calendar from December 2019 to February 2020, a calendar from September 2019 to November 2019 is displayed. When a medical institution staff member operates the user terminal 3 and selects icon 36, a calendar from June 2020 to August 2020 is displayed. In other words, by operating the user terminal 3, the user can switch the display screen displaying the calendar for period 1 to a display screen displaying the calendar for period 2. Period 1 and period 2 are adjacent periods.
[0054] 6, the date on which the request to display the schedule input screen was sent in step S11, or the date on which the display request was received in step S12, is March 26, 2020, and the month including March 26, 2020 is displayed on the far left, but the number of calendars displayed in the reservation input field 31 and the location of the calendars can be set as appropriate. For example, six months' worth of calendars may be displayed in the reservation input field 31, or the month including the date on which the display request was received in step S12 (also referred to as the current month) may be displayed in the center of the reservation input field 31. In other words, the number of months included in the calendar for one period displayed on the display screen and the location of the current month can be set as appropriate.
[0055] In FIG. 6, the user can input the desired date for using the service. However, if the date is a weekday, the user may be able to input the date separately for weekday clinic hours and non-clinic hours. That is, the desired date for using the service can be input for each time period. The time periods that can be input may be predetermined. For example, if the unit of service use is during weekday clinic hours, outside clinic hours, and on holidays, the user can input the desired date for using the service for each of these three types on a calendar. The user may also be able to select the desired time for using the service. Furthermore, the minimum unit of time that can be input for the desired time for using the service may be limited. For example, the user may be able to input a time period of at least three hours per session. The user may also be able to input the desired period for using the service in monthly or weekly units. That is, the desired date (period) for using the service can be input in units of a predetermined period, such as one hour, one day, or one week.
[0056] The input of a desired date for using the service may be permitted until the total time of the input date in a predetermined period reaches a predetermined condition. For example, if it is pre-registered in the server device 2 that up to 10 days per month can be input, the medical institution staff member can input up to 10 days of dates for which the medical institution staff member desires to use the service in a month. The total time may be set by an administrator. Alternatively, the first usage fee may be different for each total time, and the medical institution staff member may be able to select any total time from multiple options.
[0057] Here, it is preferable that input, deletion of input, and change of the schedule for which the user wishes to use the service be limited to a predetermined period. Specifically, it is possible to prohibit the acceptance of input, deletion of input, and / or change of the schedule for which the user wishes to use the service, depending on the date and time for accepting input by the user. That is, it may be possible to prohibit the acceptance of input of the period for which the user wishes to use the service, to prohibit the deletion of input of the period for which the user wishes to use the service, and to prohibit the change of the period for which the user wishes to use the service, depending on the date and time for accepting input by the user.
[0058] For example, the period during which the user can input dates for using the service may be until the end of April 2020 for input for May 2020, or until the day before the day the service is to be used, or may be a predetermined time (e.g., 12 hours) before the start time of the service. Furthermore, for example, after a predetermined date and time (e.g., midnight on the day), the user may be unable to input, delete, and / or change dates before the day for which the user desires or does not desire the service. Note that the first usage fee is determined to be incurred for the desired period included in the period during which the user is unable to input dates for using the service. The desired period may include past dates and future dates.
[0059] In addition, during the period corresponding to the date and time for accepting input of the date and time for which the user wishes to use the service, it may be made impossible to accept input, delete input, and / or change the date and time for which the user wishes to use the service.
[0060] The period corresponding to the date and time for accepting input of a date for which a user wishes to use the service may be, for example, a past period including the day on which the date is entered, or, if the date is entered in predetermined intervals, a past period including a period that includes the date and time for entering the date. Specifically, if date input is accepted on a monthly basis, date input for May 2020 is possible until the end of April 2020, but is not possible after May 1, 2020. The period corresponding to the date and time for accepting input of a date for which a user wishes to use the service may be changed depending on the period for accepting date input.
[0061] This prevents a user from canceling the input of a desired service period for a date for which the user previously input the desired service period but did not actually use the service. Also, for a date for which the user did not previously input the desired service period, if the user later needs to use the service, it can be prevented from inputting the desired service period.
[0062] In Figure 6, the date on which the request to display the schedule input screen was sent in step S11, or the date on which the request to display the screen was received in step S12, is March 26, 2020, and it is not possible to input, change, or cancel the input of a desired date for service use before March 26, 2020. In Figure 6, the calendar for period 34 corresponding to the period during which input, change, and cancellation of input are not possible is displayed in light gray. In other words, in the system of the present invention, the calendar display mode may be different between the display area corresponding to the period during which it is not possible to input, change, or cancel the input of a desired date for service use and the display area corresponding to the period during which it is possible to input a desired date for service use.
[0063] [Service execution process] Next, the service execution process (step S3) in the system will be described. Fig. 7 is a diagram showing a flowchart of the service execution process according to the embodiment of the present invention. Note that the user can apply for the service for both a schedule for which the user has input a desire to use the service in step S2 and a schedule for which the user has not input a desire to use the service.
[0064] First, a medical institution staff member logs into the system by entering a user ID and password into the user terminal 3. Then, the medical institution staff member enters case information related to the case into the user terminal 3 (step S21). When applying for a case, applicants can refer to the case information and use it as a reference for deciding whether or not to apply for the case. The case information includes, for example, surgery information related to the surgery, such as the date of surgery, admission time, disease name, surgical procedure, scheduled surgery time, anesthesia method, and position; remuneration information related to the remuneration, such as remuneration, minimum guaranteed amount, and cancellation fee; patient information related to the patient, such as the patient's age, sex, height, weight, and medical history; and inputter information related to the person inputting the case (the medical institution staff member). The case information may also include the number of applicants being recruited.
[0065] The project information is transmitted from the user terminal 3 to the server device 2 (step S22), and is received by the server device 2 (step S23). When the server device 2 receives the project information, the project information is registered in the server device 2 (step S24). Once the project information is registered, in the system according to this embodiment, users of the system can view the project information. That is, the project information can be displayed and viewed on the user terminal that input the project information, other user terminals, applicant terminals, and administrator terminal.
[0066] Here, additional fees may be incurred depending on the time from when the user inputs the case information into the user terminal 3 until the case is performed. Specifically, if the time from when the case information is input until the case is performed is less than a predetermined time, additional fees may be incurred. In this case, the storage unit 23 stores the fees in association with the time from when the case information is input until the case is performed. For example, if the time from when the case information is input until the time of entry into the operating room (the time the case is performed) is less than 24 hours, an additional fee of 30,000 yen (also referred to as an emergency fee) may be added to the first usage fee, the second usage fee, and / or the third usage fee. Expense information regarding the additional fees is stored in association with the case information in step S24. The expense information may be displayed on the user terminal 3 in step S21.
[0067] When the job information is registered in step S24, a notification is sent from the server device 2 to the applicant terminal 4 (step S25). The notification is received at the applicant terminal 4 (step S26). The notification includes the job information. In step S25, the applicant terminal 4 that sends the notification is an applicant terminal that has previously registered for use. In addition, if the job information includes conditions for the desired medical professional (area of responsibility, age, gender, etc.), the notification may be sent to an applicant terminal 4 that matches those conditions. Specifically, an applicant table that stores applicant information is stored in the server device 2, and the server device 2 references the applicant table to identify applicants that match the conditions of the job information. In addition, when or after sending the notification to the applicant terminal 4 in step S25, the user terminal 3 may be notified that the notification has been sent to the applicant terminal 4. The notification is sent to the contact information registered during user registration.
[0068] When the applicant terminal 4 receives the notification in step S26, the project information is displayed on the applicant terminal 4 (step S27). The notification may include the project information, information for displaying the project information, and / or information for entering the application information (described below). For example, if the notification in step S25 is email, the email may include a URL for displaying the project information, and the project information may be displayed when the applicant logs into the system using the URL. Alternatively, in step S25, a push notification may be sent to an applicant terminal 4 on which a dedicated app has been installed. The applicant may then log into the system from the applicant terminal 4 that received the push notification, and the project information may be displayed. Alternatively, when the applicant operates the applicant terminal 4 and selects the URL and push notification, the applicant may log into the system from the applicant terminal 4, and a page for entering the project information and the application information in step S28 may be displayed.
[0069] If an applicant wishes to apply for the displayed job, the application information required for the application is entered into applicant terminal 4 (step S28). The application information is information about the applicant, such as name, sex, date of birth, address, mobile phone number, email address, area of responsibility, career history, etc.
[0070] In the system according to this embodiment, applicants register their applicant information during user registration in step S1. Therefore, applicants can complete the entry of their application information simply by entering their intention to apply. For example, applicants can operate applicant terminal 4 and select an icon such as "Apply" on the page displaying the job information, thereby entering their intention to apply on applicant terminal 5. This allows applicants to apply for jobs with simple operations. Furthermore, applicants can quickly apply for urgent jobs where the time between the entry of job information and the execution of the job is short. Furthermore, if applicants have questions or requests regarding the job, they may be able to enter these items along with their application. Furthermore, if the job information includes items that applicants are required to enter, applicants may enter those items as part of their application information.
[0071] The application information is transmitted from the applicant terminal 4 to the server device 2 (step S29), and the application information is received by the server device 2 (step S30). Upon receiving the application information, the application information is registered in the server device 2 (step S31). The server device 2 stores the applicant and the case information related to the application information in association with each other.
[0072] When a predetermined time has elapsed since the notification was sent in step S25 (step S32), the server device 2 refers to the implementation management table that records the applicant's implementation record of the case, and changes the winning probability for the applicant registered for the case (step S33). The process of step S33 can also be said to be a process of changing the applicant's winning probability according to the applicant's implementation record of the case. Then, the server device 2 executes a lottery process to determine the worker who will be in charge of the case (step S34).
[0073] The predetermined time in step S32 can be set as appropriate by the administrator or the user who input the case. For example, it may be set to a predetermined time before the date of the surgery included in the case information (for example, 24:00 on the day before the surgery date). The predetermined time in step S32 may also be changed depending on the time from when the case information is input until the case is actually performed. For example, if the time from when the case information is input until the case is actually performed is less than 24 hours, the predetermined time may be set to 5 minutes, and if it is 24 hours or more, the predetermined time may be set to 30 minutes.
[0074] Furthermore, the start of measurement of the predetermined time in step S32 is not limited to the time when the notification is sent in step S25. The start of measurement of the predetermined time in step S32 can be set appropriately, for example, from the time when the input of the case information is accepted in step S21, from the time when the case information is stored in the server device 2 in step S24, or from the time when the initial application information is stored in the server device 2 in step S31. Once the predetermined time has elapsed, it will no longer be possible to input application information in step S28 or to send application information from the applicant in step S29.
[0075] Alternatively, the process of step S32 may be omitted, and the process from step S33 onward may be executed when the application information of a predetermined number of applicants or more has been registered in step S31. The predetermined number of applicants may be set as appropriate by the administrator or the user who entered the job. In other words, the process from step S33 onward may be executed when predetermined conditions, such as time conditions and number of applicants conditions, are met.
[0076] The process of changing the winning probability in step S33 will be described. First, the implementation management table stores workers who have previously handled cases related to the service and information about the cases, in association with each other. FIG. 8 is a diagram showing an example of an implementation management table according to an embodiment of the present invention. The information in the implementation management table 40 is stored in the server device 2. The implementation management table 40 shown in FIG. 8 stores the worker's user name 41, the name of the medical institution 42 that is the user of the service, the implementation date 43 of the case, the remuneration 44 for the case, and the content 45 of the case, each associated with each other. Other information may also be stored in the implementation management table 40.
[0077] In step S33, for example, the implementation management table 40 can be referenced for registered applicants, and the lottery winning probability can be reduced by a predetermined percentage for applicants who have implemented a predetermined number of projects or more in a predetermined period (e.g., six months). Also, the lottery winning probability can be increased by a predetermined percentage for registered applicants who have implemented a predetermined number of projects or less in a predetermined period (e.g., six months). This can ensure equality in the number of projects each applicant is responsible for, eliminating inequalities between applicants.
[0078] Furthermore, for example, by referencing the remuneration 44 in the implementation management table 40, the probability of winning the lottery for registered applicants whose past remuneration for projects is above a predetermined amount (for example, 1 million yen or more) may be lowered by a predetermined percentage, or the probability of winning the lottery may be increased by a predetermined percentage for applicants whose remuneration is below a predetermined amount. The remuneration referenced in this case may be the total amount over a predetermined period (for example, three months), or the highest remuneration over the predetermined period. This allows for equalization of remuneration amounts for projects handled by applicants, eliminating inequalities between applicants.
[0079] Furthermore, for example, the lottery probability may be lowered for applicants who have handled cases at the medical institution involved in the case in the past, allowing the medical institution to be introduced to more medical professionals. Alternatively, the lottery probability may be increased for applicants who have handled cases at the medical institution involved in the case in the past, allowing the medical institution to be introduced to medical professionals who are familiar with the medical institution.
[0080] In step S33, the applicant may be excluded from the lottery instead of lowering the applicant's chance of winning. In step S33, the period of past cases, the specified number of times or the specified amount, and the amount by which the lottery chance is lowered or increased, which are referenced in the implementation management table 40, can be appropriately designed by the administrator or the person in charge at the medical institution who entered the case.
[0081] Furthermore, when inputting the case information in step S21, the medical institution's staff member can specify applicants to whom they do not wish to be introduced. At this time, a list of applicants previously introduced to the medical institution is displayed on the case information input screen, and the medical institution's staff member may select a specific applicant. Alternatively, the medical institution's staff member may search for and select a specific applicant. The selected applicant is excluded from the application lottery base. In other words, the selected applicant's lottery probability becomes zero, and the applicant is not selected in the lottery processing in step S34 and cannot be assigned to the case. Furthermore, in step S25, a notification may not be sent to the selected applicant. This allows the medical institution to prevent applicants with bad reputations or applicants with whom the medical institution is not compatible from being introduced.
[0082] When the lottery process is carried out in step S34, at least one applicant is determined as the worker in charge of the job (step S35). The server device 2 sends a notification to the user terminal 3 of the user registered in association with the job information and the applicant terminal 4 of the applicant registered in association with the application information (step S36). The user terminal 3 receives the notification (step S37), and the applicant terminal 4 receives the notification (step S38). The service execution process ends with steps S21 to S38. If the job is recruiting multiple people, a predetermined number of workers are identified in step S35.
[0083] The process of changing the winning probability in step S33 may be omitted. Also, the processes of steps S25 and S26 may be omitted. In this case, the applicant logs into the system from the applicant terminal 4 and views the case information by displaying it on the applicant terminal 4. Alternatively, the medical institution staff may be able to choose whether or not to execute the notification processes of steps S25 and S26 when inputting the case information in step S21.
[0084] The notifications sent in steps S37 and S38 include a notice that a worker has been selected. Furthermore, the content of the notification sent after the worker has been selected may differ depending on the destination terminal. For example, in the notification in step 37, information about the applicant who has been assigned to the job is sent to the user terminal 3. Furthermore, the user can check the information about the applicant by logging into the system. In step 38, a notice is sent to the applicant terminal 4 who has been selected by lottery as the applicant to be assigned to the job that the applicant has been selected as a worker, and to the applicant terminal 4 who has not been selected by lottery that the applicant has not been assigned to the job.
[0085] Note that, once a worker is determined in step S35, the job information viewable on the system may be displayed in a manner that indicates that the worker has been determined. In this way, by changing the display manner of the job information viewable on the system, users of the system can confirm that a worker for the job has been determined.
[0086] Here, the recording process of the implementation management table 40 will be described.
[0087] The recording process is a process in which, when the server device 2 receives notification that a service-related job has been completed, information about the job and information about the worker are stored in the implementation management table 40. In the recording process, the worker selected as the person in charge actually implements the service-related job and transmits notification of the completion of the job from the applicant terminal 4 to the server device 2. This may cause the worker's username 41, medical institution name 42, implementation date 43, remuneration 44, and details 45 to be stored in association with each other in the implementation management table 40. Alternatively, the user who entered the job may operate the user terminal 3 to transmit notification of the completion of the job from the user terminal 3 to the server device 2. At this time, the information stored in the implementation management table 40 may be automatically extracted from the job information and application information registered in the server device 2. The notification of the completion of the job may include information about the worker and / or the job information. The implementation time of the job may also be stored in the implementation management table 40.
[0088] Furthermore, the timing for recording in the implementation management table 40 does not have to be when the implementation of the case is completed. For example, recording in the implementation management table 40 may be performed when the remuneration for the case has been transferred to the worker in charge of the case, or at a timing determined by the worker in step S35. Furthermore, recording in the implementation management table 40 may be performed even when the case is not implemented. For example, if the case itself is canceled, the remuneration 44 stores the cancellation fee paid to the worker, and the content 45 stores the fact that it was canceled.
[0089] The above describes an embodiment in which a user can apply for a service both for a date for which the user entered a request for service use in step S2 and for a date for which the user did not enter a request for service use. However, in principle, a user may only apply for a service for a date for which the user entered a request for service use in step S2. An exception may be made in which a user can apply for a service for a date for which the user did not enter a request for service use. In this case, the system may prevent the execution of the service execution process from step S21 onward for a date for which the user did not enter a request for service use. Specifically, the system may prevent the user from entering case information on the dedicated page for a date for which the user did not enter a request for service use. To apply for a service, the user may separately contact the administrator. The contact method may be, for example, by sending an e-mail via operation input from the user terminal 3, or by telephone, fax, or the like. The administrator who received the contact from the user may operate the administrator terminal 1 to enable the user to execute the service execution process from step S21 onward for a date for which the user did not enter a request for service use but was contacted.
[0090] [Invoice Issuance Processing] Next, the invoice issuance process of step S4 will be described. Figure 9 is a diagram showing a flowchart of the invoice issuance process according to an embodiment of the present invention. In the invoice issuance process, the system administrator calculates the cost to be charged to the user.
[0091] In the system according to this embodiment, the term "usage fee" refers to the fee incurred when using the system. Here, the usage fee consists of a usage fee (first usage fee) that is incurred by inputting the period for which the user wishes to use the service, regardless of whether the user uses the service during that period, a worker's compensation (second usage fee) that is incurred for actually using the service, and a usage fee (third usage fee) that is incurred in response to the use of the service outside the period for which the user wishes to use the service.
[0092] Below, we will first explain the case where the system administrator charges the user only the first and third usage fees. Here, we will assume that a user who uses a service on a date for which they have entered their intention to use the service will not be required to pay the third usage fee for that service. Furthermore, we will assume that if a user uses a service on a date for which they have entered their intention to use the service, they will be charged the second usage fee for that service.
[0093] First, the administrator logs into the system by inputting a user ID and password into the administrator terminal 1. Then, the administrator inputs the selection of the user for whom an invoice is to be issued into the administrator terminal 1 (step S41). At this time, it is preferable to also input the period for which the expenses are to be calculated. Alternatively, the server device 2 may be registered in advance so that expenses incurred in the month prior to the day of input in step S41 are calculated.
[0094] Next, an invoice issuance request for issuing an invoice is sent from the administrator terminal 1 to the server device 2 (step S42), and the server device 2 receives the invoice issuance request (step S43). The invoice issuance request includes the user information entered in step S41 and information on the period for which the cost is calculated. Next, the server device 2 identifies the user to whom the invoice is to be issued (step S44). Furthermore, for the identified user, the server device 2 identifies the desired period for which the user wishes to use the service, which was entered in the service period input process in step S2 (step S45). Next, the server device 2 identifies the content of the service for which the service execution process in step S3 was executed (step S46). Then, the server device 2 calculates the amount to be billed (step S47).
[0095] The calculation process of the billing amount in step S47 will now be described. In step S47, the billing amount to be charged to the user is calculated with reference to the usage fee management table described below and the implementation management table described above.
[0096] The usage fee management table stores users in association with a first usage fee and a third usage fee per unit time. The usage fee management table may store the first usage fee and / or the third usage fee per unit time so that the amount varies for each user. By storing a different usage fee per unit time for each user, the usage fee for the service for a specified period can be calculated according to different rules for each user.
[0097] Furthermore, the first usage fee and / or the third usage fee per unit time may be stored so that the amount varies depending on the day or time. For example, different first usage fees and / or third usage fees per unit time may be stored depending on weekdays and holidays, during business hours and outside of business hours, or during normal periods and special periods (such as the New Year holidays, Obon, academic conference periods, etc.). In other words, different first usage fees and / or third usage fees may be stored depending on the period attribute. Furthermore, the first usage fee and / or the third usage fee per unit time may be the same amount regardless of the day or time.
[0098] The usage fee per unit time may refer to the usage fee per hour, the usage fee per day, the usage fee per week, the usage fee per month, or the usage fee per year.
[0099] Fig. 10 is a diagram showing an example of a usage fee management table according to an embodiment of the present invention. Information in the usage fee management table 50 is stored in the server device 2. The usage fee management table 50 shown in Fig. 10 stores, in association with each other, the name 51 of the medical institution that is the user, a first usage fee per day during business hours on weekdays 52, a first usage fee per day outside business hours on weekdays 53, a first usage fee per day on weekends or holidays 54, and a third usage fee 55. Other information may also be stored in the usage fee management table 50.
[0100] By identifying the user in step S43 and the desired period in step S45, the first usage fee can be calculated by multiplying the first usage fee per day for that user by the number of days in the entered period.
[0101] The third usage fee 55 column of the usage fee management table 50 stores the formula required to calculate the third usage fee. For example, in FIG. 10, the third usage fee for medical institution A is registered as 20% of the fee for the case related to the service. The third usage fee may vary depending on the case, the fee, or the medical institution that is the user. For example, if the fee exceeds 100,000 yen, the fee may be 20% of the fee, and if the fee is 100,000 yen or less, the fee may be 15% of the fee. Furthermore, when the third usage fee per unit time is stored, it is preferable that the implementation management table also stores the time required to execute the case in association with the third usage fee.
[0102] Here, since the third usage fee is not calculated for services performed during the desired period specified in step S45, the third usage fee can be calculated using the desired period specified in step S45, the number of services performed and the remuneration specified in step S46, and the registered calculation formula. Specifically, for services performed outside the desired period specified in step S45, the third usage fee can be calculated using the remuneration for the service and the registered calculation formula. Note that, although the calculation formula required for calculating the third usage fee is registered in the usage fee management table 50 in the above example, a usage fee per unit time may also be registered, similar to the first usage fee. In this case, it is preferable that the third usage fee be set higher than the first usage fee.
[0103] In step S46, the number of services executed by the user and the second usage fee, which is the remuneration for the cases related to the services, can be identified by referring to the execution management table.
[0104] The billing amount can be calculated by adding the first and third usage fees calculated as described above. If an emergency fee is stored in association with the service case, the emergency fee may be added. Furthermore, if a limit is set on the number of times the service can be used during the period in which the request for the service is entered, and the service is used in excess of the limit, the fee for the service exceeding the limit may be added. If information regarding a discount is registered, the fee for the discount may be deducted.
[0105] The server device 2 generates an invoice based on the calculated billing amount (step S48). Invoice information for displaying the invoice is sent from the server device 2 to the manager terminal 1 (step S49), and the manager terminal 1 receives the invoice information (step S50). Steps S41 to S50 complete the invoice issuance process.
[0106] The invoice is displayed on the administrator terminal 1 that received the invoice information in step S50, allowing the administrator to check the contents of the invoice. If there is any content to be added or subtracted other than the first usage fee and the third usage fee, the administrator may add information to the invoice as appropriate. The administrator can send the generated invoice to the user terminal 3 of the user selected in step S41. The administrator may also send the invoice to the user by means of mail, fax, or the like. Alternatively, the invoice information may be sent in step S49 to the user terminal 3 of the user selected in step S41.
[0107] The administrator can issue an invoice simply by selecting the user and the specified period for which the invoice will be issued. The remuneration (second usage fee) paid to the worker who provided the service will be transferred separately from the medical institution that is the user. The invoice information may include, as reference information, the number of services performed and the remuneration for each case, as identified in step S46, for the remuneration paid by the user to the worker.
[0108] The invoice issuance process may be executed by the user terminal 3 instead of the administrator terminal 1. In this case, it is preferable that the user who will perform the invoice issuance process is automatically selected in the user selection in step S41. This allows the user to easily understand the amount to be invoiced for a specified period.
[0109] Additionally, the total amount of remuneration paid to workers who performed cases related to the service may also be calculated in the same way as the service usage fee. The implementation management table stores medical institutions in association with the remuneration amount, which is the second usage fee. Therefore, for cases in which services were performed during a specified period for which invoices are issued, the medical institution's staff can calculate the total amount of remuneration to be paid to workers by adding the remuneration amount for the case. This allows the medical institution's staff to easily grasp the total amount of remuneration.
[0110] In the above invoice issuance process, a configuration has been described in which an invoice is generated by the server device 2, but the following configuration can also be adopted in which the period during which the user uses the service and the history of the services performed (hereinafter also referred to as usage history) are displayed on the administrator terminal 1, and an administrator creates an invoice. Figure 11 is a diagram showing a flowchart of the display process according to an embodiment of the present invention. In the display process, information regarding the use of the service by a specified user is displayed on the administrator terminal 1.
[0111] First, the administrator inputs the selection of the user for whom an invoice is to be created at the administrator terminal 1 (step S51). Step S51 is the same process as step S41. Note that, in step S51, inputting the period for which an invoice is to be created can be omitted. Next, a display request for displaying display information for displaying the usage history of the selected user is sent from the administrator terminal 1 to the server device 2 (step S52), and the server device 2 receives the display request (step S53). The display request includes the user information input at step S51.
[0112] Next, the server device 2 identifies the user whose usage history is to be displayed (step S54), and for the identified user, identifies the desired period entered in the service period input process in step S2 (step S55). Then, the display information is transmitted from the server device 2 to the administrator terminal 1 (step S57), and is received by the administrator terminal 1 (step S58). The display information is displayed on the administrator terminal 1 (step S59). The display process is completed by the processes in steps S51 to S59.
[0113] When the display information is displayed on the administrator terminal 1, the administrator can check the desired period displayed and calculate the cost to be charged to the user by multiplying the first usage fee per user and / or per day or hour. This allows the administrator to create an invoice based on the information displayed on the administrator terminal 1.
[0114] After the display information is displayed, the processes of steps S42 to S50 may be executed. In this case, the administrator operates the administrator terminal 1 to select an icon such as "Generate invoice" displayed together with the display information on the administrator terminal 1, whereby the administrator can accept the invoice issuance request at the administrator terminal 1.
[0115] 12 is a diagram showing an example of a display screen in the system according to the embodiment of the present invention. Specifically, it shows an example of the display screen of the administrator terminal 1 on which the display information is displayed in step S59. User information 61 and a calendar 62 are displayed on a display screen 60, but other information may also be displayed.
[0116] 12 displays user information 61 related to the identified user. Display screen 60 also displays a calendar 62 covering January 2020 to December 2020 (July to December not shown). Calendar 62 displays, in different display modes, an area corresponding to selected dates 63, which is the period desired by the identified user, and an area corresponding to unselected dates 64, which is the period for which the date for using the service has not been entered.
[0117] The method for achieving different display modes is not particularly limited, but for example, the background colors of the areas corresponding to the periods on the calendar may be displayed in different colors, the backgrounds of the areas corresponding to the periods on the calendar may be displayed in different patterns, or the area corresponding to either the selected date 63 or the unselected date 64 may be displayed blinking while the other area does not blink. Further, as a method for achieving different display modes, for example, the color of the text in the areas corresponding to either the selected date 63 or the unselected date 64 may be displayed in different colors, or the thickness of the text in the areas corresponding to either the selected date 63 or the unselected date 64 may be displayed in different thicknesses. It is preferable to display the area or text corresponding to the selected date 63 more conspicuously than the area or text corresponding to the unselected date 64.
[0118] Here, the area corresponding to the selected date 63 can be a first period corresponding to the period during which the user wishes to use the service, and the area corresponding to the unselected date 64 can be a second period corresponding to the period during which the user does not wish to use the service. In this system, it is possible to control so that the first period corresponding to the period during which the user wishes to use the service for which input has been accepted in the service period input process, and the second period corresponding to the period during which input has not been accepted in the service period input process are displayed on the administrator terminal.
[0119] The displayed first period includes both a period during which it is not possible to input a desired date for using the service, and a period during which it is possible to input a desired date for using the service. These first periods can be displayed in different display modes depending on the attributes of the day or period. Examples of the attributes include the first usage fee per unit time, the settlement status, the issuance status of the invoice, and whether it is not possible to input a desired date for using the service.
[0120] For example, if the first usage fee differs between weekdays and holidays, the area or text corresponding to the selected date 63 on a weekday may be displayed in blue, and the area or text corresponding to the selected date 63 on a holiday may be displayed in red.
[0121] Alternatively, the areas or characters corresponding to selected dates 63 for which the manager has already issued an invoice may be displayed in different display modes than the selected dates 63 for which the manager has not yet issued an invoice. Also, the display mode of the areas or characters corresponding to selected dates 63 may differ for each month. Specifically, the past month and the current month (the month including the day on which the display request was sent in step S52 or the day on which the display request was received in step S53) may be displayed in the same display mode, and the next month and thereafter may be displayed in a different display mode, or the current month and the next month and thereafter may be displayed in the same display mode and the past month may be displayed in a different display mode, or the past month, the current month, and the next month and thereafter may be displayed in different display modes.
[0122] Furthermore, the areas or characters corresponding to selected dates 63 for which input of a desired date for using the service, etc., is not possible, i.e., for which invoice issuance is possible, and selected dates 63 for which input of a desired date for using the service, etc., is possible, i.e., for which invoice issuance is not possible, may be displayed in different display modes. Furthermore, the first period may be displayed by appropriately combining the above display modes. For example, areas corresponding to selected dates 63 for which invoice issuance is possible and an invoice has already been issued may be displayed in gray, areas corresponding to selected dates 63 for which invoice issuance is possible and an invoice has not yet been issued may be displayed in red, and areas corresponding to selected dates 63 for which invoice issuance is not possible may be displayed in green.
[0123] In addition, by operating the administrator terminal 1, the first usage fee per unit time for each user and / or per day or hour may be displayed by selecting the selected date 63 on the display screen 60 or by superimposing a cursor or the like thereon.
[0124] 11 has been described as an example in which a one-year calendar is displayed, the displayed period may be a specified period for which input is accepted by the administrator terminal 1, or may be the month preceding the day the input was made in step S51. Also, control may be exercised so that a first period and a second period that are older than the current month are displayed on the administrator terminal 1. For example, a calendar for a month older than the month including the time when the display request was sent in step S52 or the date and time when the display request was received in step S53 may be displayed on the administrator terminal 1.
[0125] 11, the desired period is displayed in a calendar format, but the display format is not limited to this. For example, the desired period for a predetermined period (e.g., one month) for which an invoice is to be created may be displayed in a list, or the number of days or total time of the desired period may be displayed numerically.
[0126] Although the above describes a configuration in which the user and desired period are identified and displayed on the administrator terminal 1, the server device 2 may also be configured to identify the user, desired period, and executed service and display them on the administrator terminal 1. In this case, before or after step S55, the server device 2 identifies the content of the service for which the service execution process was executed in step S3. If the service was executed outside the desired period, the administrator terminal 1 may display an area corresponding to the date on which the service was executed in addition to the desired period, in a manner that indicates that the service was executed outside the desired period. Specifically, in FIG. 11, March 18, 2020, is the day on which the service was executed outside the desired period and is displayed more prominently than the selected date 63. The administrator can calculate the fee to be charged to the user by calculating a third usage fee for the day on which the service was executed outside the desired period and adding it to the first usage fee.
[0127] Next, we will explain the case where the system administrator charges the user the first usage fee, the second usage fee, and the third usage fee. In this case, the payment of compensation to the worker will be carried out by the system administrator. Also, in this case, a user who uses the service on a date for which they have entered their intention to use the service will not be required to pay the third usage fee for that service. Furthermore, regardless of whether the date for which they wish to use the service is a date for which they have entered their intention to use the service, if the user uses the service, they will be charged the second usage fee for that service.
[0128] From the user's selection in step S41 to the specification of the executed service in step S46, the above description can be referred to as far as necessary.
[0129] In step S47, the remuneration amount for the case, which corresponds to the second usage fee identified in step S46, is added to the first usage fee and the third usage fee.
[0130] Furthermore, the above description can be referred to as necessary from the generation of the invoice in step S48 to the reception of the invoice information in step S50. At this time, the remuneration amount for the case corresponding to the second usage fee is added to all cases executed during the specified period for which the invoice is issued.
[0131] The method of calculating the usage fees is not limited to the above example and can be designed as appropriate. Furthermore, when the system of the present invention is applied to a service related to the introduction of medical professionals in the medical industry, it is preferable that the second usage fee be paid by the user to the worker. Therefore, in the invoice issuance process, it is preferable that the system administrator bills the user for only the first and third usage fees.
[0132] [Make payment] In making the payment in step S5, the user first receives the bill information from the administrator. Then, the user operates the user terminal 3 and selects the payment method according to the details of the bill information. Payment methods include payment by credit card, bank transfer, transfer at a convenience store, etc.
[0133] When a user pays remuneration to a worker, the user pays the worker by the due date based on payment information such as the payroll closing date, payroll month, and payroll date set during user registration in step S1. Here, in the system according to this embodiment, account information for the user and worker may be registered, and remuneration may be transferred from the user's account to the account of the worker in charge of the case based on information on the execution of the case related to the service.
[0134] In addition, when the payment of remuneration to the worker is made by the system administrator, the system administrator will make the payment to the worker by the due date based on the payment information registered by the user, as described above. Also, the system may be configured so that the worker's account information is registered and the remuneration is transferred to the account of the worker who handled the case based on the information on the case related to the service.
[0135] In other words, making a payment includes payment from the user to the system administrator, payment of compensation from the user to the applicant who handled the case, and / or payment of compensation from the system administrator to the applicant who handled the case.
[0136] [Other embodiments] In the above embodiment, a configuration has been described in which a user is charged a second usage fee for a service when using the service, regardless of whether the service is used on a date on which the user has input that he or she wishes to use the service. However, a configuration may also be adopted in which a second usage fee for a service is not charged to a user who uses the service on a date on which the user has input that he or she wishes to use the service. For example, a configuration may be adopted in which, when a user uses a service on a date on which the user has input that he or she wishes to use the service, the system administrator pays remuneration to a worker in charge of a case related to the service.
[0137] In this case, if the system administrator bills the user only for the first and third usage fees, the billing amount will be calculated in step S47 in the same manner as described above. Since the remuneration paid by the user to the worker who provided the service is for the services performed on dates other than the date on which the user entered their desired use of the service, the invoice information may include, as reference information, the number of services performed and the remuneration for the services identified in step S46 for the services for which the user must pay.
[0138] On the other hand, when the system administrator bills the user for the first, second, and third usage fees, the second usage fee (remuneration for the project) added in calculating the billing amount in step S47 excludes the remuneration for projects performed during the date when the user entered their desire to use the service. Since the implementation management table stores the service users in association with the remuneration amount (second usage fee), the total amount of remuneration to be billed to the user can be calculated by adding the remuneration for projects related to services performed outside the desired period for the period when the user entered their desire to use the specified service in step S45 and the implementation management table.
[0139] In the above embodiment, the application of the system of the present invention to a labor introduction service has been described, but the system of the present invention can also be applied to a service that provides products, for example. Note that a description of the process described above will be omitted.
[0140] When the system of the present invention is applied to a service that provides products, the system is composed of an administrator terminal 1, a server device 2, a user terminal 3, and a communication network 5. The user operates the user terminal 3 to perform a service period input process in step S2. In the case of a service that provides products, steps S25 to S39 can be omitted. For example, in a music distribution service, the music that the user wishes to use is input as project information in step S21. When the project information is registered in the server device 2 in step S24, information about the music that the user wishes to use is transmitted from the server device 2 to the user terminal 3, and the music becomes available on the user terminal 3.
[0141] According to the present invention, the usage fee for a service for a predetermined period is calculated based on the period in which the input was accepted, regardless of whether the user used the service during that period. Therefore, it is possible to calculate the usage fee for a service that incurs a usage fee regardless of whether the user used the service. Furthermore, the usage fee can be easily calculated.
[0142] According to the present invention, the administrator can secure an appropriate service usage fee because the administrator cannot accept input, delete input, and / or change the period for which the user wishes to use the service depending on the date and time when the user input is accepted. Also, even if the user suddenly needs or no longer needs to use the service, the administrator can secure an appropriate service usage fee because the user cannot change the desired period.
[0143] According to the present invention, the service usage fee for a predetermined period is calculated in accordance with different rules for each user, so that different service usage fees can be set for each user.
[0144] Furthermore, according to the present invention, the service usage fee for a specified period is calculated based on the attributes of the period in which the input is accepted, so that different service usage fees can be set depending on periods such as busy seasons and off-seasons.
[0145] According to the present invention, the usage fee for a service for a specified period is calculated by adding a first usage fee calculated based on the period during which input is accepted and a second usage fee calculated in accordance with the user's use of the service, so that the payment destination to which the user makes payment can be consolidated into one.
[0146] According to the present invention, a calendar is displayed that allows the user to input the period for which the user wishes to use the service, and the user can input the period for which the user wishes to use the service by selecting a period from the calendar, allowing the user to intuitively input the period.
[0147] According to the present invention, when an application for use of a service is made outside the period accepted by the period input means, the service usage fee for a specified period is calculated by adding together the first usage fee calculated based on the period for which the input was accepted and the third usage fee calculated in accordance with the user's use of the service for the service accepted outside the period for which the input was accepted.Therefore, the service usage fee can be easily calculated even when an application for use of a service is made outside the period accepted by the period input means.
[0148] According to the present invention, information about the service corresponding to the accepted application is sent to the applicant terminal, and an application for the service corresponding to the received information is accepted by operating the applicant terminal, so that applicants can be gathered for applications to use the service.
[0149] According to the present invention, the probability of identifying an applicant who meets predetermined conditions from among multiple applicants whose applications for a service are accepted is reduced, and a predetermined number of applicants are identified, thereby eliminating inequalities among applicants in terms of the likelihood of an applicant being identified.
[0150] According to the present invention, the first period corresponding to the period during which the user wishes to use the service is accepted and the second period corresponding to the period during which the user wishes to use the service are not accepted are displayed in different display modes on the administrator terminal, so that the administrator can easily grasp the period during which the user wishes to use the service, thereby enabling the administrator to smoothly calculate the service usage fee.
[0151] According to the present invention, the first period is controlled to be displayed in different display modes depending on the attributes of the period for which the user wishes to use the service, and the administrator can easily grasp the desired period for each attribute. Also, according to the present invention, the first period and the second period are controlled to be displayed on a calendar, and the administrator can smoothly calculate the usage fee for the service for a certain period (for example, one month). [Explanation of symbols]
[0152] 1: Administrator terminal 2: Server device 3: User terminal 4: Applicant terminal 5: Communication network 11: Control unit 12: Main memory 13: Storage unit 14: Input device 15: Display device 16: Communication interface 21: Control unit 22: Main memory 23: Storage unit 23: Communication interface 30: Schedule input screen 31: Reservation input field 32: Unselected date 33: Selected date 34: Period 35, 36: Icon 40: Implementation management table 41: Worker's user name 42: Medical institution name 43: Implementation date 44: Reward 45: Contents 50: Usage fee management table 51: Medical institution name 52~54: 1st usage fee per day 55: 3rd usage fee 60: Display screen 61: User information 62: Calendar 63: Selected date 64: Unselected date
Claims
1. A system for providing medical services by medical professionals, in which a usage fee is charged based on the period of use desired by the user, regardless of whether the service is used or not, The system comprises a server device and a user terminal operated by a user, a period input means, in the server device, for receiving an input of a period during which the user desires to use the business provision service from the user terminal; a storage means for storing the period during which the input was accepted; application acceptance means for accepting an application for use of the business provision service during the period by operation on the user terminal; A system comprising:
2. 2. The system according to claim 1, wherein the application receiving means, when receiving an application for use of the business providing service, receives input of information relating to the business corresponding to the application by operating the user terminal.
3. A control-disabling means for disabling the acceptance of input, the deletion of input, and / or the change of input during the period according to the date and time when input is accepted from the user terminal. The system according to claim 1 or 2, comprising:
4. 3. The system according to claim 1, wherein the period accepted by the period input means is a period used as a basis for calculating a usage fee for the business providing service.
5. An applicant terminal operated by an applicant for work related to the business provision service, an information transmission means for transmitting information about the business corresponding to the accepted application to the applicant terminal; application acceptance means for accepting an application for a job corresponding to the information about the job received by the applicant terminal through an operation on the applicant terminal; The system according to claim 1 or 2, comprising:
6. When the application acceptance means accepts an application for use of the business provision service, the application acceptance means accepts input of the applicant's conditions as information related to the business corresponding to the application through operation of the user terminal; 6. The system according to claim 5, wherein the information transmitting means transmits information relating to the business corresponding to the accepted application to an applicant terminal operated by an applicant corresponding to the applicant's conditions input by the application accepting means.
7. Equipped with an administrator terminal operated by an administrator, the application acceptance means executes an operation on the administrator terminal to accept an application for use of the business provision service during a period when input is not being accepted by operating the user terminal; 3. The system according to claim 1 or 2.
8. A program for providing a medical professional service, in which a usage fee is charged based on the period of use desired by the user, regardless of whether the program is used or not, Computer equipment a period input means for receiving input of a period for which the user desires to use the business provision service from the user terminal; a storage means for storing the period during which the input was accepted; An application acceptance means for accepting an application for use of the business provision service during the period by operation on the user terminal. A program that functions as a
9. A method executed in a system for providing a medical professional service, comprising a server device and a user terminal operated by a user, in which a usage fee is charged based on the period of use desired by the user, regardless of whether the service is used or not, a period input step in the server device for accepting input of a period during which the user desires to use the business provision service from the user terminal; a storage step of storing the period during which the input was accepted; an application acceptance step of accepting an application for use of the business provision service during the period by operating the user terminal; A method comprising:
Citation Information
Patent Citations
Content information providing apparatus, content information providing method, and program
JP2017224138A
Product provision management system and product provision management method
JP2020194363A
Information processing apparatus, information processing method, and program
JP2021028741A
Debt-credit transaction intermediary system, debt-credit transaction intermediary apparatus, and debt-credit transaction method
WO2010113283A1