Information processing system, information processing device, information processing method and program

The information processing system uses user and drug history data to calculate and present precise drug delivery schedules, addressing inaccuracies in existing systems by incorporating detailed usage data for improved drug replenishment timing.

JP7759468B2Active Publication Date: 2025-10-23ORGANO CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2024203019
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2023-06-16
Filing Date
2024-11-21
Publication Date
2025-10-23
Estimated Expiration
2044-04-02

AI Technical Summary

Technical Problem

Existing systems fail to predict drug replenishment dates accurately due to lack of detailed past usage data, leading to inaccurate drug delivery schedules.

Method used

An information processing system that includes a database storing user identification, drug type, and usage history information, with a calculation unit to determine recommended delivery times based on this data, and an output unit to provide precise delivery schedules.

Benefits of technology

Enables accurate and easy presentation of drug delivery schedules, taking into account past usage patterns and real-time adjustments for improved drug supply management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007759468000001
    Figure 0007759468000001
  • Figure 0007759468000002
    Figure 0007759468000002
  • Figure 0007759468000003
    Figure 0007759468000003
Patent Text Reader

Abstract

To provide an information processing system, an information processing device, an information processing method and a program that easily present a further precise recommended schedule for delivering medicines.SOLUTION: An information processing system includes: a database 200 that stores user identification information for identifying a user who utilizes medicines, medicine kind information representing the kind of a medicine, and actual usage record information representing the actual usage of the medicine in association with each other; and an information processing device 100 which accepts an external input, reads, from the database 200, the medicine kind information and the actual usage record information both associated with the accepted user identification information, calculates, for the read medicine kind information, a recommended delivery time period of the medicine based on the read actual usage record information, and outputs, for each user identification information and for each medicine kind information, recommended delivery time period information including the calculated recommended delivery time period.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing device, an information processing method, and a program. [Background technology]

[0002] In recent years, devices have been devised that predict the date and time for replenishment of chemicals based on the amount of change in the remaining amount of chemicals supplied to circulating water or makeup water in a water treatment system (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-52950 Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned technology does not predict replenishment dates based on detailed past usage data, and therefore has the problem of not being able to easily present a more accurate recommended schedule for drug delivery.

[0005] An object of the present invention is to provide an information processing system, an information processing device, an information processing method, and a program that can easily present a more accurate recommended schedule for delivering medicines. [Means for solving the problem]

[0006] The information processing system of the present invention comprises: a database that stores user identification information for identifying a user who uses a drug, drug type information indicating the type of the drug, and usage record information indicating the usage record of the drug, in association with each other; A receiving means for receiving an input from an external device; a reading means for reading, from the database, the medicine type information and the usage history information associated with the user identification information received by the receiving means; a calculation means for calculating a recommended delivery time of the drug based on the usage history information read by the reading means for the drug type information read by the reading means; and an output means for outputting recommended delivery time information including the recommended delivery time calculated by the calculation means for each of the user identification information and the medicine type information.

[0007] Further, the information processing device of the present invention comprises: a reception unit that receives input from an external device; a reading unit that reads, from a database that stores user identification information for identifying a user who uses a drug, drug type information indicating the type of the drug, and usage history information indicating the usage history of the drug, the drug type information and the usage history information associated with the user identification information accepted by the accepting unit; a calculation unit that calculates a recommended delivery time for the medicine based on the usage history information read by the reading unit for the medicine type information read by the reading unit; and an output unit that outputs recommended delivery time information including the recommended delivery time calculated by the calculation unit for each of the user identification information and the medicine type information.

[0008] Further, the information processing method of the present invention comprises: a process of reading, from a database that stores user identification information for identifying a user who uses a drug, drug type information indicating the type of the drug, and usage history information indicating the usage history of the drug in association with the user identification information received based on an external input, the drug type information and the usage history information associated with the user identification information; A process of calculating a recommended delivery time for the drug based on the read-out drug type information and the read-out usage history information; and outputting recommended delivery time information including the calculated recommended delivery time for each of the user identification information and the medicine type information.

[0009] The program of the present invention also includes: On the computer, a step of reading, from a database that stores user identification information for identifying a user who uses a drug, drug type information indicating the type of the drug, and usage history information indicating the usage history of the drug in association with each other, the drug type information and the usage history information that are associated with the user identification information received based on an external input; calculating a recommended delivery time for the drug based on the read-out drug type information; and a step of outputting recommended delivery time information including the calculated recommended delivery time for each of the user identification information and the medicine type information. [Effects of the Invention]

[0010] The present invention can easily provide a more accurate recommended schedule for drug delivery. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating a first embodiment of an information processing system according to the present invention. [Figure 2] 2 is a diagram illustrating an example of information stored in a database illustrated in FIG. 1. FIG. [Figure 3] 2 is a diagram illustrating an example of components included in the information processing device illustrated in FIG. 1. FIG. [Figure 4] 2 is a flowchart illustrating an information processing method in the information processing device shown in FIG. [Figure 5] FIG. 10 is a diagram illustrating a second embodiment of an information processing system according to the present invention. [Figure 6] FIG. 6 is a diagram showing an example of information stored in the database shown in FIG. 5. [Figure 7]6 is a diagram illustrating an example of components included in the information processing device illustrated in FIG. 5. FIG. [Figure 8] 6 is a flowchart illustrating an information processing method in the information processing device shown in FIG. 5. [Figure 9] FIG. 10 is a diagram illustrating a third embodiment of an information processing system according to the present invention. [Figure 10] 10 is a diagram illustrating an example of components included in the information processing device illustrated in FIG. 9. FIG. [Figure 11] 10 is a flowchart illustrating an information processing method in the information processing device shown in FIG. [Figure 12] FIG. 10 is a diagram illustrating a fourth embodiment of an information processing system according to the present invention. [Figure 13] 13 is a diagram illustrating an example of components included in the information processing device illustrated in FIG. 12. FIG. [Figure 14] 13 is a flowchart illustrating an information processing method in the information processing device shown in FIG. [Figure 15] FIG. 10 is a diagram illustrating a fifth embodiment of an information processing system according to the present invention. [Figure 16] FIG. 16 is a diagram illustrating an example of components included in the information processing device illustrated in FIG. [Figure 17] 16 is a flowchart illustrating an information processing method in the information processing device shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The chemicals described below are preferably, but not limited to, water treatment chemicals or industrial chemicals added to water treatment systems. Examples of water treatment chemicals include cooling water treatment chemicals, boiler water treatment chemicals, RO membrane water treatment chemicals, and wastewater treatment chemicals. Examples of industrial chemicals include hydrochloric acid, sulfuric acid, and sodium hydroxide. (First embodiment)

[0013] FIG. 1 is a diagram illustrating a first embodiment of an information processing system according to the present invention. As shown in FIG. 1, this embodiment includes an information processing device 100, a database 200, and display devices 300-1 to 300-m (m is a natural number). The information processing device 100 and the database 200 may be connected directly or via a communication network 400. The information processing device 100 and the database 200 may be connected wirelessly or via a wired connection. The information processing device 100 and each of the display devices 300-1 to 300-m may be connected directly or via the communication network 400. The information processing device 100 and each of the display devices 300-1 to 300-m may be connected wirelessly or via a wired connection. The communication network 400 is a telecommunications line capable of transmitting and receiving electrical signals carrying information, such as telephone lines or the Internet. The display devices 300-1 to 300-m are displays that display information. The display devices 300-1 to 300-m may be monitor devices provided in a PC (Personal Computer). The display devices 300-1 to 300-m may also be displays provided in mobile terminals such as smartphones and tablet terminals. The display devices 300-1 to 300-m are equipped with a communication function and display received information. The display devices 300-1 to 300-m are provided in correspondence with users of the system. These users include not only users who use the target chemicals (including customers who entrust a management company, etc., with purchasing chemicals from chemical providers (e.g., chemical distributors) for their own use), but also managers who manage the remaining amounts of the chemicals on behalf of users (including operation management companies that use or purchase the chemicals on behalf of users), chemical suppliers (including chemical manufacturing factories and storage warehouses), chemical procurement companies, and chemical transport companies. The display devices 300-1 to 300-m may be provided in one-to-one correspondence with users. Furthermore, a plurality of display devices among display devices 300-1 to 300-m may be provided for one user, or one display device among display devices 300-1 to 300-m may be shared by a plurality of users.

[0014] The database 200 stores drug type information, user identification information, usage history information, and supplier identification information in association with each other. The drug type information is information indicating the type of drug. The user identification information is information for identifying the user who uses the drug. The usage history information is information indicating the usage history of the drug according to the user identification information. The supplier identification information is information for identifying the supplier to which the drug is ordered. The information stored in the database 200 can be read from the information processing device 100 or other devices. Furthermore, information can be written to the database 200 from a specific device. Furthermore, the information stored in the database 200 can be edited (updated) from a specific device. This specific device is a device operated by a person authenticated by this information processing system. The database 200 may be provided inside the information processing device 100.

[0015] FIG. 2 is a diagram illustrating an example of information stored in the database 200 shown in FIG. 1. As shown in FIG. 2, the database 200 shown in FIG. 1 stores user identification information, drug type information, usage history information, and supplier identification information in association with each other. External access restrictions may be placed on at least a portion of this information, allowing only authorized personnel to view the information. In this case, the information to which access restrictions are placed may be any information, and is not specifically defined here. The user identification information is identification information uniquely assigned to each user in advance to identify the user who uses the drug. The drug type information is information indicating the type of drug used by the user, and is information that can identify the type of drug. The drug type information includes, for example, information indicating a target segment. The drug type information may be, for example, a product name (drug name), a model number, or other information such as a product code consisting of a predetermined number of letters and / or numbers. The drug type information may also include information such as the physical properties of the drug (e.g., pH, specific gravity), relevant laws and regulations, and wastewater regulations. The usage history information is information indicating the usage history of the drug by the user identified by the user identification information. The usage history information indicates, for example, the past delivery intervals and delivery amounts of the drug, the date of the previous delivery, the change in the remaining amount of the drug over a certain period, the correlation between the scheduled delivery plan and the actual delivery, and records of delivery shortages and overdeliveries. The supplier identification information is identification information uniquely assigned to each drug provider in advance to identify the supplier of the drug of that type. While the correspondence shown in FIG. 2 associates one piece of information with each piece of information, multiple pieces of information may also be associated with one piece of information. For example, if one user uses multiple types of drug, the user identification information of the user may be associated with multiple pieces of drug type information. Furthermore, if there is a supplier other than the user and the drug provider that provides the drug of that type, information identifying the supplier may also be associated. In addition to the information shown in FIG. 2, the database 200 may also store other necessary information, such as the capacity of the drug tank owned by the user, the amount of drug that can be delivered at one time, and the days on which drug delivery is available.2 shows an example in which user identification information, medicine type information, usage record information, and orderer identification information are associated with one another, but this is not limiting. For example, one user identification information may be associated with multiple medicine type information, or multiple medicine type information may be associated with one supplier identification information.

[0016] Fig. 3 is a diagram showing an example of components included in the information processing device 100 shown in Fig. 1. As shown in Fig. 3, the information processing device 100 shown in Fig. 1 has a reception unit 110, a reading unit 120, a calculation unit 130, and an output unit 140. Fig. 3 shows main elements in this embodiment among the elements included in the information processing device 100 shown in Fig. 1.

[0017] The reception unit 110 receives input from outside. For example, the reception unit 110 may receive information transmitted from a communication device owned by a user (for example, the display devices 300-1 to 300-m shown in FIG. 1). The reception unit 110 may also receive information based on an operation performed from outside the information processing device 100.

[0018] When a target user is designated, the reading unit 120 reads out the medicine type information and supplier identification information associated with the user identification information indicating the user from the database 200. At this time, when the receiving unit 110 receives the user identification information, the reading unit 120 reads out the medicine type information and usage history information associated with the user identification information received by the receiving unit 110 from the database 200. The reading unit 120 outputs the read medicine type information and supplier identification information to the calculation unit 130.

[0019] The calculation unit 130 calculates a recommended delivery time, which is a recommended delivery date for each type of drug, based on the usage history information read by the reading unit 120 for each drug type. That is, the calculation unit 130 calculates a recommended delivery time for the drug of a given type to a given user based on usage history information corresponding to user identification information indicating the user and drug type information indicating the type of drug. For example, the calculation unit 130 may calculate the next recommended delivery time based on the delivery interval indicated by the usage history information stored in the database 200 and the previous delivery date. Furthermore, the calculation unit 130 may calculate multiple recommended delivery times over a predetermined future period, in addition to the next recommended delivery time. Furthermore, the calculation unit 130 may calculate the recommended delivery time and delivery amount for a given type of drug based on the past delivery frequency and delivery amount indicated by the usage history information, the change in the remaining amount of the drug over a certain period, and the tank capacity. The calculation unit 130 may adjust the recommended delivery time calculated as described above based on the correlation between the planned delivery plan and actual delivery results indicated by the usage history information and records of delivery shortages or overdeliveries. In this case, for example, if the usage history information shows a record of delivery earlier than the scheduled delivery plan in the past, the calculation unit 130 may advance the recommended delivery time. Furthermore, if the usage history information shows a record of overdeliveries in the past, the calculation unit 130 may delay the recommended delivery time. Furthermore, when calculating the recommended delivery time, the calculation unit 130 may weight each of the multiple pieces of information stored as the usage history information based on their importance (priority), and calculate the recommended delivery time based on the weighted pieces of information. The calculation unit 130 stores the calculated recommended delivery time in a table, such as a memory. At this time, the calculation unit 130 may store the recommended delivery time information, including the recommended delivery time, in the table in association with user identification information and drug type information. This recommended delivery time information is information that is clearly displayed so that a delivery schedule including the recommended delivery time for each type of drug can be understood using a calendar, etc. In addition to the recommended delivery time, the recommended delivery time information includes, for example, the name of the drug to be delivered, the amount of the drug to be delivered, the product code, etc.When the amount of medicine to be delivered is included in the recommended delivery time information, the recommended delivery time information may be a graph showing the amount in accordance with the recommended delivery time.

[0020] The output unit 140 outputs recommended delivery time information including the recommended delivery time calculated by the calculation unit 130, user identification information indicating the user for whom the recommended delivery time is calculated, and drug type information indicating the type of drug for which the recommended delivery time is calculated. At this time, the output unit 140 may also output the supplier identification information read from the database 200 by the reading unit 120. The output mode of the information from the output unit 140 may be transmission to the display devices 300-1 to 300-m, audio output, printing, or, if the information processing device 100 has a display function, display of the information. When the output unit 140 transmits information to the display devices 300-1 to 300-m, the output unit 140 transmits information for displaying each piece of information to the corresponding display device. The display format of the information is not particularly specified, but a calendar format stored in a table by the calculation unit 130 is preferable. Furthermore, the output unit 140 may output a signal for displaying the recommended delivery time information in a manner that allows a desired delivery time (desired delivery time) to be selected from a plurality of recommended delivery times included in the recommended delivery time information.

[0021] The following describes an information processing method in the information processing device 100 shown in Fig. 1. Fig. 4 is a flowchart for explaining the information processing method in the information processing device 100 shown in Fig. 1.

[0022] First, when the receiving unit 110 receives user identification information from outside (step S1), the reading unit 120 reads out the drug type information associated with the user identification information, usage history information, and supplier identification information indicating the supplier from the database 200 (step S2).

[0023] Then, the calculation unit 130 calculates a recommended delivery time for delivering the drug of that type to the user based on the usage history information read by the reading unit 120 (step S3). The calculation method of the recommended delivery time by the calculation unit 130 is as described above. Next, the output unit 140 outputs recommended delivery time information including the recommended delivery time calculated by the calculation unit 130, user identification information indicating the user for whom the recommended delivery time is calculated, drug type information indicating the type of drug for which the recommended delivery time is calculated, and supplier identification information read by the reading unit 120 from the database 200 (step S4).

[0024] As described above, in this embodiment, the recommended delivery time for a desired type of drug is calculated based on the user's usage history at the delivery destination. Therefore, a more accurate recommended schedule for drug delivery can be easily presented. The recommended delivery time included in the output recommended delivery time information is preferably a recommended delivery time that specifies multiple dates rather than just one. Furthermore, the calculation unit 130 does not necessarily calculate the recommended delivery time when the receiving unit 110 receives the user identification information. The calculation unit 130 may calculate the recommended delivery time at a predetermined timing or when the receiving unit 110 receives an external request for calculation of the recommended delivery time. In this case, the calculation unit 130 calculates the recommended delivery time for each type of drug based on the drug type information and usage history information associated with each user identification information registered in the database 200. Furthermore, when a user uses multiple drugs, the calculation unit 130 can easily present the recommended delivery time for each type of drug.

[0025] Furthermore, when the receiving unit 110 receives desired delivery date information indicating a desired delivery date in response to the recommended delivery date information output by the output unit 140, the calculation unit 130 may add the desired delivery date received by the receiving unit 110 to a table as a tentative delivery date and store it. The output unit 140 may output the table to which this tentative delivery date has been added. Note that when the receiving unit 110 is requested to provide information stored in the table (recommended delivery date information) based on an external input, the output unit 140 reads out and outputs the information (recommended delivery date information) stored in the table by the calculation unit 130. (Second embodiment)

[0026] FIG. 5 is a diagram showing a second embodiment of the information processing system of the present invention. As shown in FIG. 5, this embodiment includes an information processing device 101, a database 201, and display devices 300-1 to 300-m (m is a natural number). The display devices 300-1 to 300-m and the communication network 400 are the same as those in the first embodiment. The information processing device 101 and the database 201 may be connected directly or via the communication network 400. The information processing device 101 and the database 201 may be connected wirelessly or via a wire. The information processing device 101 and each of the display devices 300-1 to 300-m may be connected directly or via the communication network 400. The information processing device 101 and each of the display devices 300-1 to 300-m may be connected wirelessly or via a wire.

[0027] The database 201 stores the drug type information, user identification information, usage history information, and supplier identification information that were stored in the database 200 in the first embodiment, in association with each other. Furthermore, the database 201 stores a usage schedule in association with this association. The information stored in the database 201 can be read from the information processing device 101 or another device. Furthermore, information can be written to the database 201 from a specific device. Furthermore, the information stored in the database 201 can be edited (updated) from a specific device. This specific device is a device operated by a person authenticated by this information processing system. The database 201 may be provided inside the information processing device 101. Furthermore, access restrictions may be set for viewing this information, as in the first embodiment.

[0028] FIG. 6 is a diagram illustrating an example of information stored in the database 201 illustrated in FIG. 5. As illustrated in FIG. 6, the database 201 illustrated in FIG. 5 stores user identification information, drug type information, usage history information, supplier identification information, and a usage schedule in association with each other. The user identification information, drug type information, usage history information, and supplier identification information are the same as those stored in the database 200 in the first embodiment. The usage schedule is information indicating the planned use of a drug. For example, the usage schedule is information indicating the date on which a drug is used in large quantities, the amount of the drug to be used on that day, and a period during which the amount of the drug used will be small. The usage schedule may also include a coefficient used by the calculation unit 131 when calculating a recommended delivery time. While FIG. 6 illustrates an example in which each of the user identification information, drug type information, usage history information, orderer identification information, and usage schedule is associated with each other, the present invention is not limited to this. For example, one piece of user identification information may be associated with a plurality of pieces of medicine type information, or a plurality of pieces of medicine type information may be associated with one piece of supplier identification information.

[0029] Fig. 7 is a diagram showing an example of components included in the information processing device 101 shown in Fig. 5. As shown in Fig. 7, the information processing device 101 shown in Fig. 5 has a reception unit 110, a reading unit 121, a calculation unit 131, and an output unit 140. The reception unit 110 and the output unit 140 are the same as those in the first embodiment. Note that Fig. 7 shows main elements in this embodiment among the components included in the information processing device 101 shown in Fig. 5.

[0030] The reading unit 121 acquires a use schedule for each type of medicine. The reading unit 121 reads and acquires the use history information and use schedule associated with the user identification information and medicine type information in the database 201. The reading unit 121 outputs the read use history information and use schedule to the calculation unit 111.

[0031] The calculation unit 131 calculates a recommended delivery time, which is a recommended delivery date for each type of drug, based on the usage history information and usage schedule for each type of drug. The calculation unit 131 calculates a recommended delivery time for each type of drug based on the usage history information and usage schedule for each type of drug that the reading unit 121 reads and acquires from the database 201. That is, the calculation unit 131 calculates a recommended delivery time for delivering a type of drug to a user based on usage history information and a usage schedule corresponding to user identification information indicating the target user and drug type information indicating the type of drug. For example, the calculation unit 131 may calculate the next recommended delivery time based on the delivery interval indicated by the usage history information stored in the database 201 and the previous delivery date, and adjust the calculated delivery time in accordance with the usage schedule. The calculation unit 131 may also calculate a recommended delivery time and delivery amount for the type of chemical based on the past delivery amount indicated by the usage history information, the past usage rate of the chemical, and the tank capacity, and adjust the calculated recommended delivery time and delivery amount according to the usage schedule. The calculation unit 131 may also adjust the recommended delivery time calculated as described above based on the correlation between the planned delivery plan and the delivery results indicated by the usage history information, records of delivery shortages and overdeliveries, and the usage schedule. In this case, for example, if the usage history information shows a record of past delivery earlier than the scheduled delivery plan, the calculation unit 131 may advance the recommended delivery time. If the usage history information shows a record of past overdeliveries, the calculation unit 131 may delay the recommended delivery time. When calculating the recommended delivery time, the calculation unit 131 may weight each of multiple pieces of information stored as usage history information based on the importance (priority) of each piece, and calculate the recommended delivery time based on the weighted information. Furthermore, if a plan to use a large amount of the drug of the type immediately before the calculated recommended delivery time is registered as a usage schedule, the calculation unit 131 may advance the recommended delivery time. Furthermore, if a plan to refrain from using the drug of the type before the calculated recommended delivery time is registered as a usage schedule, the calculation unit 131 may delay the recommended delivery time. The calculation unit 131 stores the calculated delivery time in a table in a memory or the like.At this time, the calculation unit 131 may store recommended delivery time information including the recommended delivery time in a table. This recommended delivery time information is information that is clearly displayed so that the delivery schedule can be understood. For example, the recommended delivery time information is information in which the recommended delivery time for each type of drug is clearly displayed in a display format such as a calendar. In addition to the recommended delivery time, the recommended delivery time information includes, for example, information indicating the target segment, the name of the drug to be delivered, the amount of the drug to be delivered, the product code, and the usage schedule. If the amount of the drug to be delivered is included in the recommended delivery time information, the recommended delivery time information may be information in which the amount is displayed in a predetermined graph corresponding to the recommended delivery time.

[0032] The following describes an information processing method in the information processing device 101 shown in Fig. 5. Fig. 8 is a flowchart for explaining the information processing method in the information processing device 101 shown in Fig. 5.

[0033] First, when the reception unit 110 receives user identification information from outside (step S11), the reading unit 121 reads out the drug type information, usage history information, supplier identification information indicating the supplier, and usage schedule associated with the user identification information from the database 201 (step S12).

[0034] Then, the calculation unit 131 calculates a recommended delivery time for delivering the drug of that type to the user based on the usage history information and usage schedule read by the reading unit 120 (step S13). The calculation method of the delivery time in the calculation unit 131 is as described above. Next, the output unit 140 outputs recommended delivery information including the recommended delivery time calculated by the calculation unit 131, user identification information indicating the user for whom the recommended delivery time is calculated, drug type information indicating the type of drug for which the recommended delivery time is calculated, and supplier identification information read by the reading unit 121 from the database 201 (step S14).

[0035] In this manner, in this embodiment, the delivery time of a desired type of drug is calculated based on the user's usage history and usage schedule. Therefore, a drug delivery schedule can be presented for each user who uses the drug. Furthermore, if a user uses multiple types of drugs, a drug delivery schedule can be presented to the user for each type of drug. If the user plans to increase or decrease the use of a given type of drug around the delivery time, a drug delivery schedule can be presented that corresponds to the planned increase or decrease in the amount of the drug used. The recommended delivery time included in the output recommended delivery time information is preferably a recommended delivery time that specifies multiple dates, rather than just one day. Furthermore, the calculation unit 131 may calculate the recommended delivery time at a predetermined timing, or may calculate the recommended delivery time when the reception unit 110 receives a request for calculation of the recommended delivery time from an external source. In this case, the calculation unit 131 calculates the recommended delivery time for each type of drug based on the drug type information, usage history information, and usage schedule associated with each piece of user identification information registered in the database 201.

[0036] Furthermore, when the receiving unit 110 receives desired delivery date information indicating a desired delivery date in response to the recommended delivery date information output by the output unit 140, the calculation unit 131 may add the desired delivery date received by the receiving unit 110 to a table as a tentative delivery date and store it. The output unit 140 may output the table to which this tentative delivery date has been added. Note that when the receiving unit 110 is requested to provide information stored in the table (recommended delivery date information) based on an external input, the output unit 140 reads out and outputs the information (recommended delivery date information) stored in the table by the calculation unit 131. (Third embodiment)

[0037] FIG. 9 is a diagram illustrating a third embodiment of an information processing system according to the present invention. As shown in FIG. 9, this embodiment includes an information processing device 102, a database 200, display devices 300-1 to 300-m (m is a natural number), and detection devices 500-1 to 500-n (n is a natural number). The database 200, display devices 300-1 to 300-m, and communication network 400 are the same as those in the first embodiment. The information processing device 102 and the database 200 may be connected directly or via the communication network 400. The information processing device 102 and the database 200 may be connected wirelessly or via a wired connection. The information processing device 102 and each of the display devices 300-1 to 300-m may be connected directly or via the communication network 400. The information processing device 102 and each of the display devices 300-1 to 300-m may be connected wirelessly or via a wired connection. The information processing device 102 and each of the detection devices 500-1 to 500-n may be directly connected to each other, or may be connected to each other via a communication network 400. The information processing device 102 and each of the detection devices 500-1 to 500-n may be connected to each other wirelessly or via a wire.

[0038] The detection devices 500-1 to 500-n detect the usage status of the chemicals for each type of chemical. For example, the detection devices 500-1 to 500-n may be sensors installed in tanks storing the chemicals at the place where the chemicals are used and detect the remaining amount of the chemical stored in the tank. The detection devices 500-1 to 500-n may be sensors that detect when the remaining amount of the chemical stored in the tank falls below a predetermined amount. The detection devices 500-1 to 500-n may also be communication devices that input the remaining amount of the chemical stored in the tank as a detection result. The detection devices 500-1 to 500-n transmit the detection results to the information processing device 102. The detection devices 500-1 to 500-n may synchronize data that accumulates the remaining tank amount values ​​of the chemicals for a certain period in the past and transmit the data to the information processing device 102 instead of the detection device data. The timing at which the detection devices 500-1 to 500-n detect the drug usage status or transmit the detection results to the information processing device 102 may be a preset timing (for example, at a fixed cycle), or may be a timing at which detection or transmission is instructed from outside. When transmitting the detection results to the information processing device 102, the detection devices 500-1 to 500-n transmit sensor identification information previously assigned to each of the detection devices 500-1 to 500-n to the information processing device 102. This allows the information processing device 102 to identify which of the detection devices 500-1 to 500-n the transmitted detection results are from. Furthermore, the detection devices 500-1 to 500-n may transmit the detection results to a counting device that counts the usage status, rather than to the information processing device 102.

[0039] Fig. 10 is a diagram showing an example of components included in the information processing device 102 shown in Fig. 9. As shown in Fig. 10, the information processing device 102 shown in Fig. 9 has a reception unit 110, a reading unit 120, a calculation unit 132, and an output unit 140. The reception unit 110, the reading unit 120, and the output unit 140 are the same as those in the first embodiment. Note that Fig. 10 shows main elements in this embodiment among the components included in the information processing device 102 shown in Fig. 9.

[0040] In addition to the functions of the calculation unit 130 in the first embodiment or the calculation unit 131 in the second embodiment, the calculation unit 132 calculates a recommended delivery time, which is a recommended delivery date for each type of medicine, based on the usage status of each type of medicine. This usage status is indicated by information transmitted from each of the detection devices 500-1 to 500-n. If the usage status detected by the detection devices 500-1 to 500-n is held by the above-mentioned counting device, the calculation unit 132 calculates the recommended delivery time based on the usage status acquired from the counting device. The calculation unit 132 identifies which user and which medicine the usage status belongs to based on sensor identification information transmitted together with the usage status transmitted from each of the detection devices 500-1 to 500-n. The usage status may also be the remaining amount or usage rate of each medicine transmitted from a communication device owned by the user. In other words, the calculation unit 132 updates the recommended delivery time that has already been calculated and stored in the table based on the usage status. The update timing may be when the usage status is transmitted (when the usage status is acquired), or may be at a preset timing. This timing may be periodic, such as once a day or every hour.

[0041] The following describes an information processing method in the information processing device 102 shown in Fig. 9. Fig. 11 is a flowchart for explaining the information processing method in the information processing device 102 shown in Fig. 9. The processing from when the calculation unit 132 first calculates the recommended delivery time until the output unit 140 outputs the calculated recommended delivery time is the same as in the first embodiment. The following describes the processing thereafter.

[0042] The calculation unit 132 acquires the usage status of each drug periodically or at an appropriate timing (step S21). Specifically, as described above, the calculation unit 132 may acquire, as the usage status, the detection results transmitted from each of the detection devices 500-1 to 500-n. Alternatively, the calculation unit 132 may acquire, as the usage status, the remaining amount and usage pace of each drug transmitted from a communication device owned by a user who is using the drug. Then, the calculation unit 132 recalculates the recommended delivery time of the drug based on the usage status acquired in step S21 (step S22). The calculation unit 132 updates the recommended delivery time that has already been calculated and stored in the table to the recommended delivery time calculated in step S22 (step S23). For example, if the usage status acquired by the calculation unit 132 from the detection devices 500-1 to 500-n indicates that the drug is being used at a faster pace than planned, the calculation unit 132 updates the recommended delivery time stored in the table to be earlier. Furthermore, for example, if the usage status acquired by the calculation unit 132 from the detection devices 500-1 to 500-n indicates that the drug is being used at a slower pace than planned, the calculation unit 132 updates the recommended delivery time stored in the table to be later. Subsequently, the output unit 140 outputs recommended delivery time information including the recommended delivery time recalculated by the calculation unit 132 (step S24).

[0043] The display form of the recommended delivery time recalculated by the calculation unit 132 may be a screen showing the daily remaining amount calculated by the calculation unit 132 based on the detection results transmitted from each of the detection devices 500-1 to 500-n and the remaining amount of each drug transmitted from a communication device owned by the user who uses the drug, as well as the dates and time periods when delivery is possible and the recommended delivery amount.

[0044] In this embodiment, the recommended delivery time for a desired type of drug is calculated based on the usage history of the user at the delivery destination. Therefore, a drug supply schedule can be presented for each user who uses the drug. Furthermore, if a user uses multiple types of drugs, a drug supply schedule for each type of drug can be presented to the user. Furthermore, after the recommended delivery time is presented, the recommended delivery time is updated according to the actual situation, such as the amount of drug usage. This makes it possible to present a schedule that is in line with the actual usage of the drug. By combining this embodiment with the second embodiment, if there is a plan to increase or decrease the use of the drug of that type before or after the delivery time, a schedule for providing the drug at a time that corresponds to the planned increase or decrease in the amount of drug usage can be presented. Note that the recommended delivery time included in the output recommended delivery time information is preferably a recommended delivery time that specifies multiple dates, rather than just one date. Furthermore, the timing at which the calculation unit 132 calculates the recommended delivery time is not limited to when the receiving unit 110 receives the user identification information. The calculation unit 132 may calculate the recommended delivery time at a predetermined timing or when the receiving unit 110 receives a request to calculate the recommended delivery time from an external source. In this case, the calculation unit 132 calculates the recommended delivery time for each type of user identification information registered in the database 200 based on the drug type information and usage history information associated with each user identification information. Alternatively, the calculation unit 132 may calculate the recommended delivery time when detection results are transmitted from the detection devices 500-1 to 500-n, or when information indicating the remaining amount of each drug is transmitted from a communication device owned by a user who is using the drug. In this case, the calculation unit 132 calculates (updates) the recommended delivery time for each type of user identification information registered in the database 200 based on the drug type information and usage history information associated with each user identification information, the detection results transmitted from the detection devices 500-1 to 500-n, and the information indicating the remaining amount of each drug transmitted from a communication device owned by a user who is using the drug.Alternatively, the calculation unit 132 may calculate the recommended delivery time when a predetermined signal (for example, a signal requesting linkage with the detection results of the detection devices 500-1 to 500-n) is transmitted from an external device. Note that the information processing device 102 may accumulate the usage status acquired from the detection devices 500-1 to 500-n in the usage history information stored in the database 200. As the usage status is accumulated in the usage history information, the calculation of future recommended delivery times can be made more accurate.

[0045] Furthermore, when the receiving unit 110 receives desired delivery date information indicating a desired delivery date in response to the recommended delivery date information output by the output unit 140, the calculation unit 132 may add the desired delivery date received by the receiving unit 110 to a table as a tentative delivery date and store it. The output unit 140 may output the table to which this tentative delivery date has been added. Note that when the receiving unit 110 is requested to provide information stored in the table (recommended delivery date information) based on an external input, the output unit 140 reads out and outputs the information (recommended delivery date information) stored in the table by the calculation unit 132.

[0046] Furthermore, when the calculation unit 132 updates the recommended delivery time, the output unit 140 may issue a predetermined notification to the user who has been assigned user identification information corresponding to the updated recommended delivery time. This notification may be, for example, a notification that the user can recognize, such as a predetermined screen display, sound generation, vibration, or light emission. Furthermore, this notification may continue unless some operation is performed in response to this notification. Furthermore, when some operation is performed in response to this notification, a predetermined signal may be transmitted to the information processing device 102. (Fourth embodiment)

[0047] FIG. 12 is a diagram illustrating a fourth embodiment of the information processing system of the present invention. As shown in FIG. 12, this embodiment includes an information processing device 103, a database 200, display devices 300-1 to 300-m (m is a natural number), and detection devices 500-1 to 500-n (n is a natural number). The database 200, display devices 300-1 to 300-m, and communication network 400 are the same as those in the first embodiment. The detection devices 500-1 to 500-n are the same as those in the third embodiment. The information processing device 103 and the database 200 may be connected directly or via the communication network 400. The information processing device 103 and the database 200 may be connected wirelessly or via a wired connection. The information processing device 103 and the display devices 300-1 to 300-m may be connected directly or via the communication network 400. The information processing device 103 and each of the display devices 300-1 to 300-m may be connected wirelessly or via a wire. The information processing device 103 and each of the detection devices 500-1 to 500-n may be connected directly or via a communication network 400. The information processing device 103 and each of the detection devices 500-1 to 500-n may be connected wirelessly or via a wire.

[0048] Fig. 13 is a diagram showing an example of components included in the information processing device 103 shown in Fig. 12. As shown in Fig. 13, the information processing device 103 shown in Fig. 12 has a reception unit 110, a reading unit 120, a calculation unit 133, and an output unit 140. The reception unit 110, the reading unit 120, and the output unit 140 are the same as those in the first embodiment. Note that Fig. 13 shows main elements in this embodiment among the components included in the information processing device 103 shown in Fig. 12.

[0049] In addition to the functions of the calculation unit 132 in the third embodiment, when the reception unit 110 receives a request to change the desired delivery date, the calculation unit 133 changes the desired delivery date information included in the recommended delivery date information stored in the table based on the change request received by the reception unit 110. The change request received by the reception unit 110 may be, for example, information input and transmitted to the display device 300-1 owned by the user, if the display device 300-1 displays the recommended delivery date information output by the output unit 140 and is equipped with an input means. The change request received by the reception unit 110 may also include information indicating the desired change date. Furthermore, the change request received by the reception unit 110 may also include information indicating the desired change time and amount of chemicals. If the display device 300-1 is equipped with an input means, the change request may be input, for example, by dragging and dropping the information displayed as the current tentative delivery date onto the desired date on a calendar showing the recommended delivery date information.

[0050] An information processing method in the information processing device 103 shown in Fig. 12 will be described below. Fig. 14 is a flowchart for explaining the information processing method in the information processing device 103 shown in Fig. 12. Note that the process in which the information processing device 103 shown in Fig. 12 calculates and outputs recommended delivery time information is the same as the process in the third embodiment. The process after the information processing device 103 calculates and outputs the recommended delivery time information, and then the desired delivery date (tentative delivery date) is determined and presented will be described. Note that the following process may also be performed after the recommended delivery date in the third embodiment is updated and notified.

[0051] When the receiving unit 110 receives a change request based on an external input (step S31), the calculation unit 133 changes the desired delivery date information included in the recommended delivery date information stored in the table based on the change request received by the receiving unit 110 (step S32). The output unit 140 outputs the recommended delivery date information including the desired delivery date information changed by the calculation unit 133 (step S33).

[0052] In this embodiment, the recommended delivery time for a desired type of drug is calculated based on the usage history of the user at the delivery destination. Therefore, a schedule for providing the type of drug according to each user can be presented. By combining this embodiment with the second embodiment, if there is a plan to increase or decrease the use of the drug before or after the delivery time, a schedule for providing the drug at a time according to the planned increase or decrease in the amount of the drug can be presented. Furthermore, after the recommended delivery time is presented, the recommended delivery time is updated according to the actual situation, such as the amount of drug used. This makes it possible to present a schedule that is in line with the actual usage situation of the drug. It is preferable that the recommended delivery time included in the output recommended delivery time information be a recommended delivery time that specifies not just one day but multiple dates. Furthermore, the timing when the calculation unit 133 calculates the recommended delivery time is not limited to when the receiving unit 110 receives the user identification information. The calculation unit 133 may calculate the recommended delivery time at a predetermined time or when the receiving unit 110 receives a request to calculate the recommended delivery time from an external source. In this case, the calculation unit 133 calculates a recommended delivery time for each type of user identification information registered in the database 200 based on the corresponding corresponding drug type information and usage history information. Alternatively, the calculation unit 133 may calculate the recommended delivery time when detection results are transmitted from the detection devices 500-1 to 500-n, or when information indicating the remaining amount of each drug is transmitted from a communication device owned by a user who is using the drug. In this case, the calculation unit 133 calculates (updates) a recommended delivery time for each type of user identification information registered in the database 200 based on the corresponding corresponding drug type information and usage history information, the detection results transmitted from the detection devices 500-1 to 500-n, and the information indicating the remaining amount of each drug transmitted from a communication device owned by a user who is using the drug. Furthermore, when the reception unit 110 receives a request to change the desired delivery date based on an external input, the calculation unit 133 changes the desired delivery date information included in the recommended delivery time information stored in the table based on the change request received by the reception unit 110.Then, the output unit 140 outputs the recommended delivery time information including the desired delivery time information changed by the calculation unit 133. Therefore, when a user or the like requests a change to the desired delivery time, the change request is easily reflected on the system, and the reflected recommended delivery time information can be easily grasped. (Fifth embodiment)

[0053] FIG. 15 is a diagram illustrating a fifth embodiment of the information processing system of the present invention. As shown in FIG. 15, this embodiment includes an information processing device 104, a database 200, display devices 300-1 to 300-m (m is a natural number), and detection devices 500-1 to 500-n (n is a natural number). The database 200, display devices 300-1 to 300-m, and communication network 400 are the same as those in the first embodiment. The detection devices 500-1 to 500-n are the same as those in the third embodiment. The information processing device 104 and the database 200 may be connected directly or via the communication network 400. The information processing device 104 and the database 200 may be connected wirelessly or via a wired connection. The information processing device 104 and the display devices 300-1 to 300-m may be connected directly or via the communication network 400. The information processing device 104 and each of the display devices 300-1 to 300-m may be connected wirelessly or via a wire. The information processing device 104 and each of the detection devices 500-1 to 500-n may be connected directly or via a communication network 400. The information processing device 104 and each of the detection devices 500-1 to 500-n may be connected wirelessly or via a wire.

[0054] Fig. 16 is a diagram showing an example of components included in the information processing device 104 shown in Fig. 15. As shown in Fig. 13, the information processing device 103 shown in Fig. 12 has a reception unit 110, a reading unit 120, a calculation unit 134, and an output unit 144. The reception unit 110 and the reading unit 120 are the same as those in the first embodiment. Note that Fig. 16 shows main elements in this embodiment among the components included in the information processing device 104 shown in Fig. 15.

[0055] The calculation unit 134 calculates a modified schedule that allows the desired delivery date to be changed based on the transportation schedule for transporting the chemicals of the supplier identified by the supplier identification information associated with the target chemical type information, which the reading unit 120 read from the database 200, and the desired delivery date information stored in the table. The transportation schedule used here includes the load capacity and availability of the vehicle transporting the chemicals, the driver allocation status of the vehicle, and the availability of transfer workers who transfer the chemicals from the vehicle to the tank. For example, the calculation unit 134 calculates a date on the transportation schedule on which the chemicals can be transported as a modified schedule that allows the desired delivery date to be changed. Furthermore, for example, the calculation unit 134 may calculate a modified schedule that allows the desired delivery date to be changed based on the date on which the chemicals can be transported and the amount of chemicals in the transportation schedule. In this case, for example, a modified schedule that allows the chemicals to be transported by dividing the amount set as the tentative delivery date into multiple days based on the transportation schedule may be calculated. The calculation unit 134 stores the calculated modified schedule in a table. The change schedule calculated by the calculation unit 134 may indicate either or both of a date on which the desired delivery date can be changed and a date on which the desired delivery date cannot be changed. Furthermore, as described above, the change schedule calculated by the calculation unit 134 may indicate a date on which the desired delivery date can be changed depending on the amount of medicine to be delivered. The change schedule calculated by the calculation unit 134 is not limited to dates, and may also indicate time periods.

[0056] The output unit 144 outputs the changed schedule calculated by the calculation unit 134 together with the recommended delivery time information.

[0057] An information processing method in the information processing device 104 shown in Fig. 15 will be described below. Fig. 17 is a flowchart for explaining the information processing method in the information processing device 104 shown in Fig. 15. The process in which the information processing device 104 shown in Fig. 15 calculates (or updates) and outputs recommended delivery time information is the same as the process in the third embodiment. The process after the information processing device 103 calculates and outputs the recommended delivery time information, and then the desired delivery date (tentative delivery date) is determined and presented will be described.

[0058] The calculation unit 134 calculates a change schedule that allows the desired delivery date to be changed, based on the transportation schedule for transporting the drug of the supplier identified by the supplier identification information associated with the drug type information read by the reading unit 120 from the database 200 and the desired delivery date information stored in the table (step S41). For example, as described above, the calculation unit 134 may calculate dates on which the desired delivery date can be received (which may include information indicating the date and time, the time zone, and whether it is morning or afternoon; the same applies to the following explanation) and dates on which the desired delivery date cannot be received, based on the transportation schedule and the desired delivery date information, and may include these dates in the change schedule. If the calculation unit 134 calculates a date on which the desired delivery date cannot be received, it may calculate dates excluding the calculated date as dates on which the desired delivery date can be received. The output unit 144 outputs the change schedule calculated by the calculation unit 134 together with recommended delivery time information (step S42).

[0059] In this embodiment, the recommended delivery time for a desired type of drug is calculated based on the usage history of the user at the delivery destination. Therefore, a schedule for providing the type of drug according to each user can be presented. By combining this embodiment with the second embodiment, if there is a plan to increase or decrease the use of the drug before or after the delivery time, a schedule for providing the drug at a time according to the planned increase or decrease in the amount of the drug can be presented. Furthermore, after the recommended delivery time is presented, the recommended delivery time is updated according to the actual situation, such as the amount of drug used. This makes it possible to present a schedule that is in line with the actual usage situation of the drug. It is preferable that the recommended delivery time included in the output recommended delivery time information be a recommended delivery time that specifies not just one day but multiple dates. Furthermore, the timing when the calculation unit 134 calculates the recommended delivery time is not limited to when the receiving unit 110 receives the user identification information. The calculation unit 134 may calculate the recommended delivery time at a predetermined time or when the receiving unit 110 receives a request to calculate the recommended delivery time from an external source. In this case, calculation unit 134 calculates a recommended delivery time for each type of user identification information registered in database 200 based on the corresponding corresponding drug type information and usage history information. Alternatively, calculation unit 134 may calculate the recommended delivery time when detection results are transmitted from detection devices 500-1 to 500-n, or when information indicating the remaining amount of each drug is transmitted from a communication device owned by a user who is using the drug. In this case, calculation unit 134 calculates (updates) a recommended delivery time for each type of user identification information registered in database 200 based on the corresponding corresponding drug type information and usage history information, the detection results transmitted from detection devices 500-1 to 500-n, and the information indicating the remaining amount of each drug transmitted from a communication device owned by a user who is using the drug.Furthermore, the calculation unit 134 calculates a change schedule by which the desired delivery date can be changed, based on the transportation schedule for transporting the drug of the supplier indicated by the supplier identification information associated with the drug type information read out from the database 200 by the reading unit 120, and the desired delivery date information stored in the table. Then, the output unit 144 outputs recommended delivery time information including the change schedule calculated by the calculation unit 134. Therefore, it is possible to easily grasp the date by which the desired delivery date can be changed according to the schedule of the supplier that transports the drug.

[0060] Although the first to fifth embodiments have been described above, the display format of the recommended delivery time information displayed by the display devices 300-1 to 300-m may be for each type of medicine, or may be such that a list of all or some of the medicines used by the user can be grasped. Furthermore, when the recommended delivery time information displayed by the display devices 300-1 to 300-m is switched and displayed for each type of medicine, for example, the display devices 300-1 to 300-m may display tabs for switching types, and the types of medicines displayed may be switched using the tabs.

[0061] Although the above description has been given by allocating each function (process) to each component, this allocation is not limited to the above. Furthermore, the configuration of the components is also not limited to the above-described embodiments, which are merely examples. Furthermore, the above-described embodiments may be combined in any combination.

[0062] The processing performed by each of the information processing devices 100 to 104 described above may be performed by a logic circuit manufactured for each purpose. Alternatively, a computer program (hereinafter referred to as a program) describing processing procedures may be recorded on a recording medium readable by each of the information processing devices 100 to 104, and the program recorded on the recording medium may be read and executed by each of the information processing devices 100 to 104. Examples of recording media readable by each of the information processing devices 100 to 104 include removable recording media such as floppy disks, magneto-optical disks, DVDs (Digital Versatile Discs), CDs (Compact Discs), Blu-ray (registered trademark) Discs, USB (Universal Serial Bus) memories, and SD cards, as well as memories such as ROMs (Read Only Memory), RAMs (Random Access Memory), and HDDs (Hard Disc Drives) built into each of the information processing devices 100 to 104. The program recorded on this recording medium is read by a CPU (not shown) provided in each of the information processing devices 100 to 104, and the same processing as described above is performed under the control of the CPU. Here, the CPU operates as a computer that executes the program read from the recording medium on which the program is recorded.

[0063] Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0064] This application claims priority based on Japanese Patent Application No. 2023-099390, filed on June 16, 2023, the disclosure of which is incorporated herein in its entirety.

Claims

1. A database that stores user identification information for identifying users who use multiple types of chemicals, which are water treatment chemicals or industrial chemicals added to a water treatment system, chemical type information indicating the type of chemical, and usage history information indicating the usage history of the chemical, in association with each other; A receiving means for receiving an input from an external device; a reading means for reading, from the database, the medicine type information and the usage history information associated with the user identification information received by the receiving means; a calculation means for calculating a recommended delivery time of the drug based on the usage history information read by the reading means for the drug type information read by the reading means; an output means for outputting recommended delivery time information including the recommended delivery time calculated by the calculation means for each of the user identification information and the medicine type information; the receiving means receives desired delivery date information indicating a desired delivery date for the recommended delivery date information output by the output means; The calculation means adds the desired delivery date information received by the reception means to the recommended delivery time information, When the receiving means is requested to provide the recommended delivery time information based on an external input, the output means outputs the recommended delivery time information to which the desired delivery date information has been added.

2. 2. The information processing system according to claim 1, The receiving means receives a request to change the desired delivery date information included in the recommended delivery date information output by the output means, The calculation means changes the desired delivery date information included in the recommended delivery date information based on the change request received by the reception means, The output means outputs recommended delivery time information including the desired delivery date information changed by the calculation means.

3. 3. The information processing system according to claim 1, The calculation means calculates the recommended delivery time of the drug based on the usage history information read by the reading means and a usage schedule for each type of drug that has been registered in advance.

4. 3. The information processing system according to claim 1, The calculation means is an information processing system that updates the recommended delivery time information based on the usage status of the drug for each type of drug.

5. 5. The information processing system according to claim 4, a detection device that detects the usage status of the medicine for each type of the medicine; The calculation means is an information processing system that updates the recommended delivery time information based on the usage status detected by the detection device.

6. 3. The information processing system according to claim 1, the database stores supplier identification information for identifying a supplier of the medicine in association with the user identification information and the medicine type information; the calculation means calculates a change schedule for changing the desired delivery date based on a transportation schedule for transporting the drug from the supplier identified by the supplier identification information associated with the drug type information read by the reading means and the desired delivery date information; The output means outputs the change schedule calculated by the calculation means together with the recommended delivery time information.

7. 3. The information processing system according to claim 1, an information processing system having a display device that displays the recommended delivery time information output by the output means;

8. a reception unit that receives input from an external device; a database that stores user identification information for identifying a user who uses multiple types of chemicals, which are water treatment chemicals or industrial chemicals added to a water treatment system, chemical type information that indicates the type of the chemical, and usage history information that indicates the usage history of the chemical, in association with each other; and a reading unit that reads out from the database the chemical type information and the usage history information that are associated with the user identification information accepted by the accepting unit; a calculation unit that calculates a recommended delivery time for the medicine based on the usage history information read by the reading unit for the medicine type information read by the reading unit; an output unit that outputs recommended delivery time information including the recommended delivery time calculated by the calculation unit for each of the user identification information and the medicine type information, the receiving unit receives desired delivery date information indicating a desired delivery date for the recommended delivery date information output by the output unit; the calculation unit adds the desired delivery date information received by the reception unit to the recommended delivery time information; When the reception unit is requested to provide the recommended delivery time information based on input from outside, the output unit outputs the recommended delivery time information to which the desired delivery date information has been added.

9. A database that stores user identification information for identifying users who use multiple types of chemicals, which are water treatment chemicals or industrial chemicals added to a water treatment system, chemical type information indicating the type of chemical, and usage history information indicating the usage history of the chemical, in association with each other, and a process of reading out from the database the chemical type information and usage history information that are associated with user identification information received based on external input; A process of calculating a recommended delivery time for the drug based on the read-out drug type information and the read-out usage history information; a process of outputting recommended delivery time information including the calculated recommended delivery time for each of the user identification information and the medicine type information; A process of adding desired delivery date information, which indicates a desired delivery date for the output recommended delivery date information and is received in response to the output recommended delivery date information, to the recommended delivery date information; and when a request for provision of the recommended delivery time information is received based on an external input, outputting the recommended delivery time information to which the desired delivery date information has been added.

10. On the computer, a step of reading, from a database that stores user identification information for identifying a user who uses multiple types of chemicals, which are water treatment chemicals or industrial chemicals added to a water treatment system, chemical type information indicating the type of the chemical, and usage history information indicating the usage history of the chemical, in association with the user identification information received based on an external input; calculating a recommended delivery time for the drug based on the read-out drug type information; a step of outputting recommended delivery time information including the calculated recommended delivery time for each of the user identification information and the medicine type information; a step of adding desired delivery date information, which indicates a desired delivery date for the output recommended delivery date information and is received in response to the output recommended delivery date information, to the recommended delivery date information; and a procedure for outputting the recommended delivery time information to which the desired delivery date information has been added when a request for provision of the recommended delivery time information is received based on an external input.

Citation Information

Patent Citations

  • Collecting method, ordering method, method and system for sale, information processor, collecting method and selling method by information processor, and program and medium therefor

    JP2001306685A

  • Expendable automatic ordering device and recording medium

    JP2002032634A

  • Server device, data processor, toner cartridge management method, storage medium, and expendables management program

    JP2002032641A

  • Medicine wholesale business management system

    JP2002149819A

  • Automated solution dispenser

    JP2015529548A