JP7516696B2 - Contract management system, contract management program, and contract management method - Google Patents

Description

The present invention relates to a contract management system, a contract management program, and a contract management method.

Conventionally, contracts for services require an explanation of the service and are concluded by signing a paper contract. However, this poses the problem that the more contracts there are, the more difficult it becomes to manage the contracts. One example of technology that solves this problem is proposed in, for example, Patent Document 1.

In Patent Document 1, the product inventory table is a table that stores data items for inventory management of rental products for each item. The table stores the child product code, rental number, contractor number, contract number, and status code indicating whether the item is currently being rented.

JP 2002-109415 A

When making a contract for a service, it is preferable to issue a contract to the appropriate user and have the contract signed, thereby changing the status of the contract. However, the technology described in the above document has the problem that the contract is not issued to the appropriate user, and it is not clear who has agreed to the contract.

In view of the above problems, the present invention aims to provide a new technology that enables management of contracts related to contracts with appropriate users.

In order to solve the above problems, the present invention provides
A contract management system for managing a contract between a service provider and a user of the service,
The contract management system associates information for uniquely identifying the provider with user information of the user who wishes to use the service provided by the provider, and stores the information as contract information;
contract input information input by designating a contract template, which is a template for a contract related to a contract for the service, and user information to be included in the contract among the user information, is received from a provider terminal of the provider linked to the user via the contract information;
Based on the contract input information, a contract linked to the user information is created and processed, and transmitted to the user;
When a signature is input to the contract, agreement to the contract is determined, and contract status information indicating the contract status of the contract is updated.

In order to solve the above problems, the present invention provides
A method for managing a contract between a service provider and a service user, comprising:
a step of linking information for uniquely identifying the provider with user information of the user who desires to use the service provided by the provider, and storing the information as contract information;
receiving contract input information input by designating a contract template, which is a template for a contract related to a contract for the service, and user information to be included in the contract from a provider terminal of the provider linked to the user via the contract information;
A step of creating and processing a contract linked to the user information based on the contract input information and transmitting the contract to the user;
The computer executes a step of determining agreement to the contract by inputting a signature to the contract, and updating contract status information indicating the contract status of the contract.

In order to solve the above problems, the present invention provides
A contract management program for managing a contract between a service provider and a service user, comprising:
information for uniquely identifying the provider and user information of the user who wishes to use the service provided by the provider are linked together and stored as contract information;
contract input information input by designating a contract template, which is a template for a contract related to a contract for the service, and user information to be included in the contract among the user information, is received from a provider terminal of the provider linked to the user via the contract information;
Based on the contract input information, a contract linked to the user information is created and processed, and transmitted to the user;
The information processing device determines whether the contract has been agreed to by inputting a signature to the contract, and updates contract status information indicating the contract status of the contract.
With this configuration, it is possible to manage contracts relating to contracts with appropriate users.

In a more preferred embodiment, the contract management system creates an address associated with information for uniquely identifying the provider, and transmits the address to a user terminal used by the user,
Accepting user information received from the user terminal via the address;
Information for uniquely identifying the provider linked to the address is linked to user information and stored as contract information.
With this configuration, an address can be issued so that the user can identify the service provider he or she desires, and user information can be sent to the provider terminal associated with that address, thereby preventing user information from being sent to the wrong provider.

In a more preferred form, the contract management system determines agreement to the contract when the signature is input from the user terminal of the user and approval input information regarding approval of the contract is input from the provider terminal of the provider, and updates the contract status information for the contract.
With this configuration, a service contract can be made when there is an agreement between the user and the provider. This makes it possible to make a service contract without any discrepancy in understanding between the provider and the user.

In a more preferred embodiment, the contract management system creates and processes a plurality of contracts linked to the user information based on the contract input information,
When the agreement has been reached for all of the contracts, contract status information indicating the contract status of the contracts is updated.
With this configuration, a contract can be concluded when multiple contracts are signed. This ensures that all contracts have been confirmed and allows a contract for the service to be concluded.

In a more preferred embodiment, the contract management system further stores, for each of the services, usage information indicating whether the service is available to the user,
receiving input of the contract input information by designating the contract template, the user information, and service information indicating the service to be used by the user;
The service information is stored in association with the contract information;
Based on the contract input information, the contract linked to the user information and the service information is created and processed,
When the contract is signed, the usage information corresponding to the service indicated by the service information linked to the contract is updated.
With this configuration, it is possible to grasp whether or not each service can be accepted.

In a more preferred embodiment, the contract management system comprises:
The contract status information is updated at each of the following times: when the contract is created, when the transmission process of the contract is performed, when a signature is input from the user terminal, and when approval input information is accepted from the provider terminal.
With this configuration, the status of the contract can be tracked one by one. If the contract is not being reviewed, a notification can be sent to prompt the user to review it.

In a more preferred embodiment, the contract management system, upon receiving a cancellation instruction for canceling the contract between the provider and the user,
Identifying the service information linked to the contract information;
The usage information linked to the service information is updated.
With this configuration, if a user has signed up for multiple services, the user can cancel all of the services at the same time, thereby reducing the amount of work required for cancellation.

The present invention has the effect of providing a new technology that enables management of contracts related to contracts with appropriate users.

FIG. 1 is a block diagram showing a configuration of a system according to an embodiment. FIG. 1 illustrates a hardware configuration of a system according to an embodiment. FIG. 1 is a functional block diagram illustrating a configuration of a system according to an embodiment. 2 is an example of a database of the system of an embodiment. 1 is an example of a flowchart of a system according to an embodiment. 1 is an example of a display screen of the system according to an embodiment. 1 is an example of a display screen of the system according to an embodiment. 1 is an example of a display screen of the system according to an embodiment. 1 is an example of a display screen of the system according to an embodiment.

The present invention will be described in detail below with reference to the drawings. Note that the embodiment shown below is an example of the present invention, and the present invention is not limited to the embodiment below, and various configurations can be adopted.

For example, the configuration, operation, etc. of the contract management system are described in this embodiment, but similar effects can be achieved by the executed method, device, computer program, etc. The program in this embodiment may be provided as a non-transitory storage medium readable by a computer, or may be provided so as to be downloadable from an external server. In this embodiment, a case is described in which the contract management system is realized by starting a contract management program on a server computer.

The present invention relates to a contract management system that manages service contracts between service providers (hereinafter referred to as providers) and service users (hereinafter referred to as users). Here, a provider is a company or individual that provides a service. In this embodiment, a case will be described in which a provider provides welfare business services such as nursing care, medical care, and meal support, and a facility provision service that makes facilities such as nursing homes and care facilities available for use. Note that while the service of the present invention is a welfare business, it may be any business type that enters into a contract, such as real estate or travel agency.

The user receives services provided by a provider by making an inquiry to the provider or intermediary. Specifically, the user receives one or both of welfare business services and facility-provided services by making an inquiry. The intermediary here is the person in charge of the practical aspects of the contract. In this embodiment, the intermediary is a company or individual such as a care manager, who checks user information and the like to select a provider appropriate for the user.

In the present invention, user information for each user and service information for a service suitable for the user are input into a provider terminal, and a contract linked to the user information and service information is created. The user then signs the contract, resulting in a service contract. In this embodiment, a service provider is assigned to a person selected by the intermediary, and the provider's provider terminal accepts input related to the creation of the contract. A facility provider accepts service inquiries directly from users, and the provider's provider terminal accepts input related to the contract. A facility provider may be assigned by an intermediary, or a service provider may accept service inquiries directly from users.

<System Configuration>
Fig. 1 is a block diagram showing the configuration of a system according to an embodiment. As shown in Fig. 1, a contract management system 0 includes a contract management device 1, a provider terminal 2, a user terminal 3, and an intermediary terminal 4. The contract management device 1, the provider terminal 2, the user terminal 3, and the intermediary terminal 4 are configured to be able to communicate with each other via a communication network NW. In this embodiment, the communication network NW is an IP (Internet Protocol) network, but there is no restriction on the type of communication protocol, and further, there is no restriction on the type and scale of the network.

In this embodiment, the contract management device 1 stores information about the service contract between the provider and the user, and executes the contract creation process. A general-purpose server computer or a personal computer can be used as the contract management device 1. Note that, although the contract management device 1 is configured using one computer in this embodiment, it can also be configured using multiple computers.

In this embodiment, the provider terminal 2 accepts input of information related to contract creation from the provider, and displays information related to the created contract. In this embodiment, the user terminal 3 accepts input of user information required for a service contract, and also accepts input of a signature on the displayed contract. The intermediary terminal 4 accepts inquiries from users, and registers contract information between the user and an appropriate provider based on the inquiries. The provider terminal 2, user terminal 3, and intermediary terminal 4 can be general computers such as smartphones, tablet terminals, personal computers, and wearable devices.

<Hardware Configuration>
Fig. 2 shows a hardware configuration in this embodiment. Fig. 2(a) is a diagram showing an example of the hardware configuration of the server 10 (contract management device 1). The server 100 includes, as its hardware configuration, a processing unit 101, a storage unit 102, and a communication unit 103.

The processing unit 101 includes one or more processors such as a CPU, and controls the overall operation and processing of the server 10 by executing the transaction promotion program according to the present invention, the OS, browser software, and other applications.

The storage unit 102 is a HDD, ROM, RAM, etc., and stores data, etc., used when the processing unit 101 executes processing based on the contract management program according to the present invention. The processing unit 101 executes processing based on the contract management program, etc., stored in the storage unit 102, thereby realizing the functional configuration described below.

The communication unit 103 controls communication with the communication network NW, and performs input necessary to operate the server 10 and outputs related to the operation results.

Figure 2 (b) is a diagram showing an example of the hardware configuration of the terminal 9 (provider terminal 2, user terminal 3, and intermediary terminal 4). Similarly, the terminal 9 also includes, as its hardware configuration, a processing unit 91, a storage unit 92, a communication unit 93, an input unit 94, and an output unit 95.

The processing unit 91 of the terminal 9 includes one or more processors such as a CPU, and controls the overall operational processing of the terminal 9. The memory unit 92 of the terminal 9 is a HDD, ROM, RAM, etc., and stores applications and the like for operating the contract management device 1. The communication unit 93 of the terminal 9 controls communication with the communication network NW. The input unit 94 of the terminal 9 is a touch panel, mouse, keyboard, etc., and inputs operation requests from the user to the processing unit 91. The output unit 95 of the terminal 9 is a display, etc., and displays the results of processing by the processing unit 91, etc.

<Contract management device 1>
3, the contract management device 1 includes, as functional components, a storage unit 102, an address issuing means 11, a receiving means 12, a linking means 13, a creating processing means 14, an updating means 15, a canceling means 16, a deleting means 17, a sending processing means 18, and a display processing means 19. Note that one computer does not need to include all of these means and units, and a plurality of computers may work together to function as the contract management device 1 of this embodiment.

The memory unit 102 stores user information, provider information, contract information, agreement information, service information, facility information, and company information (Figure 4). All of these may be stored in the memory unit 102, or some or all of them may be stored in another memory unit. The lines connecting the boxes in Figure 4 indicate "one-to-one" if they are straight lines, "one-to-many" between the start point side and the end point side if they are one-way arrows, and "many-to-many" if they are two-way arrows.

User information is information indicating the personal information of a user who uses the service, and is information entered through the user's agent. In this embodiment, the user information includes the user ID, name, relationship with the agent, and level of care required.

The provider information is information about the company that provides the service. In this embodiment, the provider information includes a provider ID, a company name, and contact information. Note that in this embodiment, the provider information includes the company name, but may also include the name of the provider in addition to or instead of the company name.

The contract information is information about the contract between the user and the provider. In this embodiment, the contract information is uniquely identified by the contract ID, and includes a user ID, a service ID, a facility ID, an intermediary ID, contract status information, a contract date, a comment, an occupancy flag, and a renewal period. Here, the contract status information is information that changes depending on the contract status information of the contract information linked to the contract information. The specific status will be described later.

The occupancy flag is information indicating whether the user will be residing in the facility. In this embodiment, the user can choose to use the service at "resident" or "at home". When the provider terminal 2 accepts input related to the creation of the contract, it accepts the user's selection of "resident" or "at home" as the desired location of use on the contract creation screen described below, and stores "1" as the occupancy flag if "resident" is selected and "0" if "at home" is selected.

In this embodiment, the contract information is linked to the service ID and the facility ID, but if the occupancy flag is "0", only the service ID may be linked and stored. Also, the contract information may be linked to only the facility ID and stored.

In addition, in this embodiment, the contract information is stored linked to the intermediary ID of the intermediary who accepted the service inquiry from the user terminal 3, but if the inquiry is sent directly from the user terminal 3 to the provider terminal 2, the intermediary ID does not need to be linked.

The contract information is information about a contract for concluding a contract between a user and a provider. In this embodiment, the contract information is uniquely identified by a contract ID, and has a contract ID, a contract template, contract status information, an update date, and a file storage location. Note that in this embodiment, multiple contract information are linked to one contract information, but the contract information and the contract information may be linked in a one-to-one relationship.

The contract template here refers to information that serves as a template for a contract. In this embodiment, the contract template is an electronic document that is not linked to the user information, facility information, and service information contained in the contract information, and is stored in the memory unit 92 or memory unit 102 of the provider terminal 2. The contract template specified on the contract creation screen is then stored as the contract information.

The contract status information is information that indicates the contract status of each contract. In this embodiment, the contract status information indicates multiple states from when the contract is created until approval input information related to approval of the signed contract is received from the provider terminal 2. The specific states will be described later.

Service information is information about a service provided by a provider. In this embodiment, the service information is uniquely identified by a service ID, and includes a provider ID, a service providing location ID, a service name, and usage information. Note that in this embodiment, the service ID and the service providing location ID are linked one-to-one, but multiple service providing location IDs may be linked to one service ID, one service providing location ID to multiple service IDs, or multiple service providing location IDs to multiple service IDs.

The service provider location ID is information that indicates the location where the service can be provided. In this embodiment, the service provider location ID is linked to the facility ID on a one-to-one basis, but the service provider location ID and the facility ID may be linked in a one-to-many relationship by the company address information linked to the company ID, the company ID, and an address-facility database (not shown) to which the facility ID is linked.

In this embodiment, the service information is linked to the service location ID and the provider ID, but it may be linked to only the provider ID. Specifically, when the occupancy flag is "0", the service information is linked to only the provider ID.

The usage information is information indicating whether or not a service can be used. In this embodiment, the usage information corresponding to the welfare business service specified on the contract creation screen is registered as "unacceptable" or the like. The usage information for the facility-provided service is registered as "unacceptable", "full" or the like corresponding to the room number of the facility.

Facility information is information about facilities operated by the provider. In this embodiment, facility information is uniquely identified by a facility ID, and includes a company ID, facility name, room number, and usage information.

The intermediary information is information about the intermediary who mediates the contract between the user and the provider. In this embodiment, the intermediary information is uniquely identified by the intermediary ID, and includes a name and contact information.

The address issuing means 11 issues an address for accepting input of user information based on the provider identification information. In this embodiment, the address issuing means 11 receives the provider identification information accepted by the accepting means 12 and an instruction to issue an address, and issues a URL for displaying a user registration screen described below, which is an address including the provider identification information and a randomly generated character string.

In this embodiment, the address issuing means 11 issues a URL that includes the provider identification information and a randomly generated character string, but it may also issue a URL that includes only the provider identification information, or it may issue a URL that includes the provider identification information and a character string that is a hash of the combination of the randomly generated character strings.

The reception means 12 receives information input at the provider terminal 2 and the user terminal 3. In this embodiment, the reception means 12 receives from the provider terminal 2 provider identification information, contact information for the user terminal 3 that received the inquiry call, and an address issuance instruction.

In this embodiment, the reception means 12 receives the user's contact information and address issuance instructions from the provider terminal 2, but may also receive them directly from the user terminal 3. In this case, the reception means 12 receives the user's contact information, provider identification information, and address issuance instructions via an inquiry form that is displayed on the user terminal 3 and set to transmit provider identification information.

The reception means 12 also receives input of user information from the user terminal 3. In this embodiment, the reception means 12 receives input of the name, relationship to the agent, and level of care required, among the user information, via a user registration screen displayed on the user terminal 3 having the contact information received at the time of the inquiry.

The reception means 12 also receives, as contract input information, one or more of user information, facility information, service information, and a contract template from the provider terminal 2. In this embodiment, the reception means 12 receives selected input of facility information and user information of a user linked to the provider via the contract information on the contract creation screen displayed on the provider terminal 2.

In a more preferred embodiment, the reception means 12 receives the selection of an occupancy flag from the provider terminal 2, and further receives service information as contract information. Specifically, when the reception means 12 receives a selection input of "1" as the occupancy flag, it receives a selection input of facility information, service information, and user information of a user linked to the provider via the contract information. In addition, when the reception means 12 receives a selection input of "0" as the occupancy flag, it receives a selection input of user information of a user linked to the provider.

The reception means 12 also accepts input of a signature for the contract. In this embodiment, the reception means 12 accepts input of the user's name and/or an electronic signature that identifies the user as a signature for the contract displayed on the user terminal 3. The reception means 12 also accepts input of approval input information related to approval of the signed contract displayed on the provider terminal 2.

The linking means 13 links the information for uniquely identifying the provider and the user information and stores them as contract information in the storage unit 102. In this embodiment, the linking means 13 links the provider identification information included in the URL generated by the address issuing means 11 and the user information accepted by the accepting means 12 and stores them as contract information in the storage unit 102.

The creation processing means 14 creates a contract based on the user information and contract template received from the provider terminal 2, and contract input information having facility information and/or service information. In this embodiment, the creation processing means 14 accepts, as contract input information, selected input from the provider terminal 2: user information to be included in the contract from among the user information received from the user terminal 3 by the reception means 12, a contract template to be used as a template for the contract from among the contract templates stored in the storage unit 102, facility information appropriate for the user from among the facility information linked to the provider information, and service information appropriate for the user from among the service information linked to the provider information. Then, the creation processing means 14 creates multiple contracts for each template based on the contract input information.

In this embodiment, the contract is created by the creation processing means 14 provided in the contract management device 1, but the creation processing means 14 may send a contract creation instruction to an external server, which then creates the contract. For example, a contract template may be uploaded to an external server, and contract input information may be sent as a creation instruction, causing the external server to create the contract.

The update means 15 determines that the contract has been agreed to (agreement to the contract) when a signature and/or approval input information is entered for the contract, and updates the contract status. In this embodiment, the update means 15 determines that the contract has been agreed to when a signature and/or approval input information is entered, and updates the contract status.

The update means 15 also updates multiple types of contract status information between the time when the creation processing means 14 creates the contract and the time when the acceptance means 12 accepts approval input information from the provider terminal 2. Specific types of contract status information will be described later.

When the update means 15 determines that a contract has been agreed to, it updates the contract status information of the contract information. In this embodiment, the update means 15 determines whether or not a contract has been agreed to for all of the multiple contracts linked to one piece of contract information, and updates the contract status information of the contract information according to the number of contracts determined to have been agreed to. Specific contract status information will be described later.

In addition, when the update means 15 receives an instruction to cancel the contract information from the provider terminal 2 or the cancellation means 16, it updates the facility information and service information linked to the contract information, and the corresponding usage information.

The update means 15 also updates the usage information linked to the service information or facility information. In this embodiment, when specific contract status information is linked to each room number in the facility information, the update means 15 updates the usage information of the facility information. The update means 15 also determines whether or not contract information is linked to each service information, and updates the usage information of the service information.

In this embodiment, when contract information of specific contract status information is linked to facility information or service information, the update means 15 updates the usage information of the facility information or service information. It may also determine whether or not a predetermined number of contract information or more are linked to facility information or service information, and update the usage information.

The cancellation means 16 determines whether the contract information has been cancelled and sends a cancellation instruction to the reception means 12. In this embodiment, the cancellation means 16 determines whether the contract information is being renewed based on the contract date and renewal period of the contract information, and sends a cancellation instruction to the reception means 12 if it determines that the contract is not being renewed.

The deletion means 17 deletes the user information based on a deletion instruction for the user information received from the provider terminal 2, and deletes one or both of the contract information and the service information linked to the user information. In this embodiment, when the deletion means 17 deletes the user information, it identifies the contract information and the service information linked to the user information, and deletes the identified contract information and the service information.

The transmission processing means 18 transmits the address generated by the address issuing means 11 to the user terminal 3. In this embodiment, when the reception means 12 receives contact information from the provider terminal 2, the transmission processing means 18 transmits a URL for displaying a user registration screen to the user terminal 3 having the contact information.

When the creation processing means 14 creates a contract, the transmission processing means 18 transmits a URL for displaying the contract to the user terminal 3 having the user information included in the contract. In a more preferred embodiment, the transmission processing means 18 transmits a notification to the user terminal 3 that transmitted the URL for displaying the contract, prompting the user to enter a signature on the contract.

The display processing means 19 processes and displays the contract creation screen. Specific display processing results will be described later. The display processing means 19 also processes and displays the contract and the signed contract. Furthermore, the display processing means 19 also processes and displays the user registration screen.

<Contract processing flow>
Next, a contract management method using the contract management system and the processing contents of each functional configuration will be described. Fig. 5 is a sequence diagram showing an overview of a contract completion process between a provider and a user.

First, in step S101 (hereinafter, the "step" in "step SXXX" will be omitted), the provider accepts an inquiry by telephone or email from the user terminal 3. Then, the input unit 94 of the provider terminal 2 accepts input of the user's telephone number and/or email address as contact information from the provider. Note that in this embodiment, the provider accepts telephone inquiries directly from the user terminal 3, but an intermediary may accept an inquiry from the user terminal 3 and accept the user's contact information via the intermediary terminal 4 of the intermediary.

In addition, in this embodiment, the provider terminal 2 accepts contact information via telephone inquiries, etc., but the contact information accepted by the input unit 94 of the user terminal 3 may also be accepted via the communication unit 93 of the user terminal 3 via an inquiry form displayed on the user terminal.

Next, in S102, the reception means 12 receives the contact information and the donor identification information of the user terminal 3 received in S101 from the communication unit 93 of the donor terminal 2. Then, in S103, the address issuing means 11 issues a URL that includes the donor identification information and the generated random character string, which is an address that displays a user registration screen for inputting the user information of the user. In this embodiment, the donor identification information and the random character string are combined and included in the URL as a parameter. The address issuing means 11 also links the contact information and the URL or the random character string received by the reception means 12 and stores them in the memory unit 102.

In S104, the transmission processing means 18 transmits a URL for displaying a user registration screen that accepts input of user information of the user to the communication unit 93 of the user terminal 3 having the contact information accepted in S102. The display processing means 19 then accepts a display request for the user registration screen from the user terminal 3 via the URL, and transmits the display processing result of the user registration screen to the user terminal 3. The output unit 95 of the user terminal 3 then displays the display processing result.

In S105, the input unit 94 of the user terminal 3 accepts the input of the name, relationship to the agent, and level of care required as user information via the user registration screen. Then, in S106, the reception means 12 accepts the user information and the provider identification information linked to the URL via the communication unit 93 of the user terminal 3.

In S107, the linking means 13 identifies the provider identification information based on the information linking the contact information and URL stored in S102, and if the user information is received from the correct URL, it links the user information accepted by the acceptance means 12 in S106 with the provider identification information included in the URL of the user registration screen into which the user information was entered, and stores the linked information in the memory unit 102 as contract information.

In S108, the display processing means 19 receives a request to display the contract creation screen from the communication unit 93 of the provider terminal 2, and in S109, transmits the display processing result of the contract creation screen to the communication unit 93 of the provider terminal 2. Then, in S110, the input unit 94 of the provider terminal 2 receives the input of facility information and user information as contract input information, and in S111, the reception means 12 receives the contract input information via the communication unit 93 of the provider terminal 2.

Figures 6 and 7 are examples of the display of a contract creation screen. Figure 6 is an example of the display of the facility contract creation screen W1 on the provider terminal 2 of a provider who operates and manages a facility. The facility contract creation screen W1 includes a contract content selection section W11 and a contract selection section W12.

The contract content selection unit W11 displays user information, facilities, and room numbers so that they can be selected and input. In this embodiment, the contract content selection unit W11 displays the name of the user linked to the provider information of the provider terminal 2 via the contract information, the facility name linked to the company ID of the provider information, and the room number linked to the facility name so that they can be selected and input. In a more preferred embodiment, the unit is configured so that room numbers whose usage information is "full" are not displayed.

The contract selection unit W12 displays a contract template so that it can be selected and input. In this embodiment, the contract selection unit W12 displays a plurality of contract templates stored in the memory unit 92 of the provider terminal 2 so that it can be selected and input.

Then, when the input unit 94 of the provider terminal 2 accepts the selected input of user information and facility information, and further accepts input related to registration, the reception means 12 accepts the user information and facility information as contract input information.

Figure 7 shows an example of a welfare service contract creation screen W2 displayed on the provider terminal 2 of a welfare service provider, and the provider enters into a contract with a user corresponding to the information selected on the screen. The welfare service contract creation screen W2 includes a contract content selection section W21 and a contract selection section W22.

Figure 7 (a) shows the welfare service contract creation screen W2 in which "Move in" has been selected from the occupancy flags in the contract content selection section W21. The contract content selection section W21 displays the company name, facility name, room number, and user name in a selectable input format, and displays user information. In addition, the contract selection section W22 displays a number of contract templates stored in the memory section 92 of the provider terminal 2 in a selectable input format.

In this embodiment, when "occupancy" is selected from the occupancy flags, the contract content selection unit W21 accepts the selection input of the company name of the company that operates and manages the facility, the facility name linked to the company name, and the room number as facility information, and the user name as user information. In addition, when the user's name is selected, the contract content selection unit W21 displays the name, date of birth, and level of care required as user information linked to the user's name.

On the other hand, FIG. 7(b) shows the welfare service contract creation screen W2 in which "at home" has been selected from the occupancy flags in the contract content selection unit W21. The contract content selection unit W21 displays user information so that it can be entered. In this embodiment, when "at home" is selected, the contract content selection unit W21 accepts the input of the name, date of birth, and level of care required as user information. The contract content selection unit W21 then extracts user names linked to the entered information from the user information registered in advance, and displays them in a list.

Then, when the input unit 94 of the provider terminal 2 accepts the selection input of one of the extracted user names and further accepts input related to registration, the reception means 12 accepts the user information linked to that user name as contract input information.

In this embodiment, the reception unit 12 receives the facility name and the user name as contract input information, but in addition to the facility name and the user name, it may also receive a selection input of the name of the service to be contracted from among multiple pieces of service information linked to the provider.

In addition, in this embodiment, the welfare business service contract creation screen W2 is displayed on the provider terminal 2 and accepts input of the company name, facility name, and room number, but the welfare business service contract creation screen W2 may be displayed on the intermediary terminal 4 and accept selection of the name of the provider or company providing the welfare business service in addition to the company name, facility name, and room number.

In addition, in this embodiment, when "occupied" is selected from the occupancy flags, user information is displayed by selecting a user name, but by inputting user information, only user names linked to that user information may be displayed in a list that can be selected and input.

In addition, in this embodiment, when "at home" is selected among the occupancy flags, user information is input and the user name is displayed in a list, but user information linked to the user name may be displayed by selectively inputting a user name. Also, user information linked to the user information may be identified and displayed by inputting any user information.

In S112, the creation processing means 14 creates a contract including user information and facility information for each contract template based on the contract input information, and stores the contract in the memory unit 102. Then, the transmission processing means 18 transmits a URL for displaying the contract to the communication unit 93 of the user terminal 3.

In S113, the display processing means 19 receives a request to display the contract created in S112 from the communication unit 93 of the user terminal 3 via the URL, and in S114 transmits the display processing result of the contract to the communication unit 93 of the user terminal 3.

In S115, the input unit 94 of the user terminal 3 accepts input of the user's name and/or an electronic signature that identifies the user as a signature for the contract displayed by the output unit 95. Then, in S116, the acceptance means 12 accepts the contract with the signature input.

In S117, when the display processing means 19 receives from the provider terminal 2 a request to display the contract with the signature received by the receiving means 12 in S116, the display processing means 19 transmits the display processing result of the contract to the provider terminal 2 in S118.

In S119, the input unit 94 of the provider terminal 2 accepts approval input information for the signed contract displayed by the output unit 95. Then, in S120, the reception means 12 accepts the approval input information from the communication unit 93 of the provider terminal 2.

In S121, the update means 15 updates the contract status information for each contract upon receipt of the approval input information. The update means 15 then updates the contract status information of the contract information.

If the creation processing means 14 creates multiple contracts in S112, S113 to S121 are repeated, and the update means 15 updates the contract status information of the contract information when it receives the signature and approval input information for all contracts created by the creation processing means 14 in S112.

Figure 8 shows an example of a contract information confirmation screen displayed on the provider terminal 2 of the provider who operates and manages the facility. Figure 8 (a) shows a usage information list W3 that includes usage information for each facility and room number. Figure 8 (b) shows a contract status list W4 that includes user information and contract status information for each contract information linked to the facility information of the selected row when the selection of the row of the usage information list W3 is accepted.

Figure 9 is an example of a contract information confirmation screen displayed on the provider terminal 2 of a provider that provides welfare business services. Figure 9 (a) shows a contract status list W5 that includes the user name, facility name, contract date, and contract status information for each contract information. In this embodiment, the update means 15 updates the contract status information to "contract completed" if all contract status information is "contract completed," to "confirming" if at least one contract status information does not have "contract completed," and to "not yet contracted" if all contract status information is not "contract completed."

In addition to the user name, facility name, contract date, and contract status information, the contract status list W5 may also include usage information of service information linked to the provider information.

The update means 15 also updates the contract status information linked to the contract information for which the reception means 12 has received a cancellation instruction from the provider terminal 2 to cancel the contract, to "cancel." The update means 15 further updates the contract status information linked to the contract information for which the cancellation means 16 has determined that the contract is not being continued, to "contract termination." The display processing means 19 then displays the contract status list W5 including the updated contract status information.

Figure 9 (b) shows a contract status list W6 that includes user information linked to the selected contract information and the contract status of each contract information when a row in the contract status list W5 is selected.

In this embodiment, the update means 15 updates the contract status information at each timing, setting it as "not yet contracted" before the creation processing means 14 creates the contract (S111), "under contract" from after the contract is created until the display processing means 19 accepts a request to display the contract from the user terminal 3 (S112), "under review" from when the request to display the contract is accepted until the reception means 12 accepts a signature input from the user terminal 3 (S115), and "contract completed" from when the signature input is accepted until the reception means 12 accepts approval input information from the provider terminal 2 (S119). The display processing means 19 then displays the contract status list W6 including the updated contract status information.

In this embodiment, the update means 15 updates the contract status information when it receives approval input information from the provider terminal 2 for a signed contract, but the contract status information may also be updated when it receives a signature input from the user terminal 3 after receiving approval input information from the provider terminal 2.

In this embodiment, the contract information confirmation screen is displayed on the provider terminal 2, but may also be displayed on the intermediary terminal 4. In this case, it is preferable that the usage information list W3 and the contract status list W5 further include a column for the service name. It is also preferable that the intermediary terminal 4 is set so that the contract status list W4 and the contract status list W6 are not displayed.

As described above, it is possible to centrally manage contracts between users who wish to use a service and the providers of that service. Furthermore, since all contracts in this invention are made via the network, it is possible to eliminate the hassle of having to go to the service provider and sign a contract.

In this embodiment, the creation process refers to the process of creating a contract in the contract management device 1, but may also be a process of creating a contract by sending an instruction to create a contract to an external server. For example, a contract template can be uploaded to an external server, and contract input information can be sent as an instruction to create the contract, so that the external server can create the contract. Also, in this embodiment, the transmission process refers to the process of sending a contract created by the creation processing means 14 in the contract management device 1 to the user terminal 3, but may also be a process of sending a contract created in the external server to the external server by sending the contract to the user terminal 3.

In addition, in this embodiment, the display process refers to a process of displaying the contract created by the creation process means 14 in response to a display request accepted by the acceptance means 12, but it may also be a process of displaying the contract by sending an instruction to an external server to display the contract created on the external server when the external server accepts a display request.

0: Contract management system 1: Contract management device 2: Provider terminal 3: User terminal 4: Intermediary terminal 100: Server 101: Processing unit 102: Memory unit 103: Communication unit 9: Terminal 91: Processing unit 92: Memory unit 93: Communication unit 94: Input unit 95: Output unit 10: Memory unit 11: Address issuing unit 12: Reception means 13: Linking means 14: Creation processing means 15: Update means 16: Cancellation means 17: Deletion means 18: Transmission processing means 19: Display processing means W1: Facility contract creation screen W11: Contract content selection section W12: Contract selection section W2: Welfare business service contract creation screen W21: Contract content selection section W22: Contract selection section W3: Usage information list W4: Contract status list W5: Contract status list W6: Contract status list NW : Communications network

Claims (11)

A contract management system for managing a contract between a service provider and a user of the service,
the contract management system receives user information, which is information on the user who wishes to use the service provided by the provider, including the user's level of care required, and stores the information for uniquely identifying a provider who will provide the service desired by the user and the user information in association with each other as contract information;
displaying, on a provider terminal of a provider, users linked to the provider via the contract information in a manner that allows selection and input, and displaying the level of care need of a user selected by the provider;
receiving, from the provider terminal of the provider, contract input information including a contract template for a contract related to a contract for the service, user information to be included in the contract among the user information of the selected and input user , service information, or facility information for receiving the service ;
creating a contract that links the user, the provider who input the contract input information, and the service information or the facility information based on the contract input information, and transmitting the contract to the user terminal of the user;
A contract management system that determines whether the contract has been agreed to when a signature is entered on the contract and updates contract status information that indicates the contract status of the contract. The contract management system of claim 1, wherein the contract management system creates an address linked to information for uniquely identifying the provider and sends the address to the user terminal, thereby accepting the user information of the user who has inquired about a service via the address. The contract management system includes an intermediary terminal used by an intermediary for accepting inquiries about services from users and determining the provider suitable for the users;
The provider terminal is caused to display the contract and the contract status information;
The contract management system according to claim 1 , wherein the contract status information is not displayed on the intermediary terminal .
The contract management system according to claim 1 or claim 2, wherein the contract management system determines whether the contract has been agreed to by inputting the signature from the user terminal and inputting approval input information related to the approval of the contract from the provider terminal of the provider, and updates the contract status information of the contract. The contract management system creates and processes a plurality of contracts linked to the user information based on the contract input information,
3. The contract management system according to claim 1, further comprising: updating contract status information indicating the contract status of the contract when the agreement is reached for all of the contracts. the contract management system stores usage information indicating whether the service is available to the user, in association with each service;
3. The contract management system according to claim 1, wherein the contract management system updates the usage information corresponding to the service indicated by the service information linked to the contract when the contract is signed. The contract management system includes:
A contract management system as described in claim 3, which updates the contract status information at each of the following times: when the contract is created, when the transmission process of the contract is performed, when a signature is input from the user terminal, and when approval input information is received from the provider. When the contract management system receives a cancellation instruction for canceling the contract between the provider and the user,
Identifying the service information linked to the contract information;
The contract management system according to claim 6 , further comprising: updating the usage information linked to the service information. When the contract management system receives a deletion instruction for deleting the user information,
Identifying the contract information and/or service information associated with the user information;
The contract management system according to claim 5 , further comprising: deleting the identified contract information and/or service information. A method for managing a contract between a service provider and a service user, comprising:
receiving user information including the user's level of care required, and storing the information for uniquely identifying a provider who will provide the service desired by the user in association with the user information as contract information;
displaying, on a provider terminal of the provider, a user associated with the provider via the contract information so as to be selectable and inputtable;
displaying the level of care required of the user selected from the provider;
receiving, from the provider, contract input information including a contract template for a contract relating to a contract for the service, user information to be included in the contract among the user information of the selected and input user , service information, or facility information for receiving the service ;
a step of creating and processing a contract that links the user, the provider who input the contract input information , and the service information or the facility information based on the contract input information, and transmitting the contract to a user terminal of the user;
a step of determining agreement to the contract by inputting a signature on the contract, and updating contract status information indicating the contract status of the contract. A contract management program for managing a contract between a service provider and a service user, comprising:
receiving user information including the user's level of care required, and storing the information for uniquely identifying a provider who will provide the service desired by the user and the user information as contract information;
displaying, on a provider terminal of a provider, users linked to the provider via the contract information in a manner that allows selection and input, and displaying the level of care need of a user selected by the provider;
receiving, from the provider terminal of the provider, contract input information including a contract template for a contract related to a contract for the service, user information to be included in the contract among the user information of the selected and input user , service information, or facility information for receiving the service ;
creating a contract that links the user, the provider who input the contract input information, and the service information or the facility information based on the contract input information, and transmitting the contract to the user terminal of the user;
A contract management program that functions as an information processing device to determine whether the contract has been agreed to when a signature is entered into the contract, and to update contract status information indicating the contract status of the contract.