Computer system, method for calculating selling price of medicine, and program

Abstract

To determine a sales price for a medicine by taking characteristics of a sales destination into consideration.SOLUTION: A computer system holds sales destination information for managing sales destinations of a medicine, result information for managing sales results of the medicine, and adjustment index information for managing an index which is set based on characteristics of the sales destinations and to be used to adjust a sales price for the medicine. The sales destination information stores data including information related to characteristics of the sales destinations. The sales results include identification information of the medicine, identification information of the sales destinations, and the sales price for the medicine. The computer system acquires the sales result for each combination of a sales destination and the medicine, acquires an index from the adjustment index information on the basis of the sales destination information for each combination of the sales destination and the medicine, and calculates a new sales price for the medicine by using the index to change the sales prices for the medicine included in the sales result.SELECTED DRAWING: Figure 9

Description

[Technical Field]

[0001] The present invention relates to a technology for managing medicines. [Background technology]

[0002] When selling pharmaceuticals, pharmaceutical companies determine the price at which they sell to wholesalers (hereinafter referred to as "invoice price"), taking into account manufacturing costs, research and development expenses, etc. Wholesalers, when selling pharmaceuticals purchased from pharmaceutical companies at invoice prices to pharmacies and hospitals, determine the price at which they sell to pharmacies and hospitals, taking into account the costs and profits involved in sales, etc. In this pharmaceutical pricing process, it is necessary to consider the costs involved in sales, etc. for wholesalers and support them in calculating appropriate prices.

[0003] Patent Document 1 describes the system as comprising: "environment-maintaining storage means for storing pharmaceuticals while maintaining environmental conditions; storage environment detection means for acquiring information on environmental conditions in the environment-maintaining storage means; storage state detection means for detecting storage of pharmaceuticals by the environment-maintaining storage means; environment-maintaining transport means for transporting pharmaceuticals while maintaining environmental conditions; transport environment detection means for acquiring information on environmental conditions in the environment-maintaining transport means; transport state detection means for detecting transport of pharmaceuticals by the environment-maintaining transport means; and billing amount deriving means for deriving the amount to be billed to the pharmaceutical delivery destination based on the information from each of the above detection means, wherein the billing amount deriving means bills for pharmaceuticals that are detected to have been released from the environment-maintaining storage means within a specified period by the storage state detection means of the pharmaceutical delivery destination." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-045424 Summary of the Invention [Problem to be solved by the invention]

[0005] When wholesalers decide on the selling price of pharmaceuticals, taking into consideration the characteristics of the customer, such as the type of business, management style, and sales volume, enables them to make more precise sales predictions and determine appropriate selling prices. However, the technology described in Patent Document 1 does not disclose that the selling price of pharmaceuticals is determined by taking into consideration the characteristics of the customer.

[0006] The present invention has been made to solve the above problems, and its purpose is to enable the determination of sales prices of pharmaceuticals according to the characteristics of the sales destination. [Means for solving the problem]

[0007] A representative example of the invention disclosed in the present application is as follows: That is, a computer system includes a processor, a storage device connected to the processor, and a network interface connected to the processor, and holds: customer information for managing customer purchases of pharmaceuticals; sales performance information for managing sales performance of the pharmaceuticals; and adjustment index information that is set based on the characteristics of the customer and is for managing a first index used to adjust the sales price of the pharmaceuticals, wherein the customer information stores data including identification information of the customer and information regarding the characteristics of the customer, and the sales performance includes identification information of the pharmaceuticals, identification information of the customer, and the sales price of the pharmaceuticals, and the processor acquires the sales performance for each combination of the customer and the pharmaceuticals, acquires the first index from the adjustment index information based on the customer information for each combination of the customer and the pharmaceuticals, and calculates a new sales price of the pharmaceuticals by changing the sales price of the pharmaceuticals included in the sales performance using the first index. [Effects of the Invention]

[0008] According to one aspect of the present invention, the selling price of a pharmaceutical product can be determined according to the characteristics of the customer. Objects, configurations, and effects other than those described above will become apparent from the following description of the examples. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a system configuration according to a first embodiment. [Figure 2] 1 is a diagram illustrating an example of a hardware configuration of a computer that constitutes a medicine management system according to a first embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of a data structure of product information according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a data structure of sales destination information according to the first embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of a data structure of sales performance information according to the first embodiment. [Figure 6A] FIG. 10 is a diagram illustrating an example of a data structure of adjustment rate information according to the first embodiment. [Figure 6B] FIG. 10 is a diagram illustrating an example of a data structure of adjustment rate information according to the first embodiment. [Figure 6C] FIG. 10 is a diagram illustrating an example of a data structure of adjustment rate information according to the first embodiment. [Figure 6D] FIG. 10 is a diagram illustrating an example of a data structure of adjustment rate information according to the first embodiment. [Figure 6E] FIG. 10 is a diagram illustrating an example of a data structure of adjustment rate information according to the first embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of a data structure of prediction information according to the first embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a data structure of price revision information according to the first embodiment. [Figure 9] 1 is a flowchart illustrating an example of processing executed by the medicine management system according to the first embodiment. [Figure 10A] FIG. 2 is a diagram illustrating an example of a screen presented by the medicine management system of the first embodiment. [Figure 10B] FIG. 2 is a diagram illustrating an example of a screen presented by the medicine management system of the first embodiment. [Figure 10C] FIG. 2 is a diagram illustrating an example of a screen presented by the medicine management system of the first embodiment. [Figure 10D] FIG. 2 is a diagram illustrating an example of a screen presented by the medicine management system of the first embodiment. [Figure 10E]FIG. 2 is a diagram illustrating an example of a screen presented by the medicine management system of the first embodiment. [Figure 11] 10 is a flowchart illustrating an example of processing executed by the medicine management system according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or intent of the present invention.

[0011] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0012] In this specification, the terms "first," "second," "third," etc. are used to identify components and do not necessarily limit the number or order. [Example]

[0013] Fig. 1 is a diagram illustrating an example of the configuration of a system according to Example 1. Fig. 2 is a diagram illustrating an example of the hardware configuration of a computer that constitutes the drug management system according to Example 1.

[0014] The system is composed of a drug management system 100 and a terminal 101. Communication between the drug management system 100 and the terminal 101 can be performed using a general public line network, whether wired or wireless, such as a fifth-generation mobile communication system, known as 5G (5th Generation), which enables "multiple simultaneous connections" and "ultra-low latency."

[0015] The terminal 101 is a terminal operated by a user. The drug management system 100 calculates the sales price or predicted sales of drugs for the next fiscal year based on the sales performance of drugs for the current fiscal year.

[0016] The medicine management system 100 is realized, for example, by using a computer 200 as shown in Fig. 2. The computer 200 has a processor 201, a main memory device 202, a secondary memory device 203, and a network interface 204. Each hardware element is connected via a bus 205.

[0017] The processor 201 executes a program stored in the main memory device 202. The processor 201 executes processing in accordance with the program, thereby operating as a functional unit (module) that realizes a specific function. In the following description, when a processing is described using a functional unit as the subject, it indicates that the processor 201 is executing a program that realizes the functional unit.

[0018] The main memory device 202 is a memory or the like, and stores programs executed by the processor 201 and information used by the programs. The main memory device 202 is also used as a work area. The secondary memory device 203 is a large-capacity storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive). The programs and information stored in the main memory device 202 may be stored in the secondary memory device 203. In this case, the processor 201 reads the programs and information from the secondary memory device 203 and loads them into the main memory device 202. The network interface 204 is an interface for connecting to the network 102.

[0019] The drug management system 100 has a sales price / sales calculation unit 110, a counting unit 111, and an output unit 112. The drug management system 100 also stores product information 120, customer information 121, sales performance information 122, and adjustment rate information 123.

[0020] The selling price / sales calculation unit 110 calculates the selling price of each product for each sales destination and also calculates predicted sales. The processing results of the selling price / sales calculation unit 110 are stored as prediction information 124. The aggregation unit 111 uses the prediction information 124 to aggregate data for specified aggregation items. The output unit 112 outputs various information to the terminal 101.

[0021] It should be noted that with regard to each functional unit of the medicine management system 100, multiple functional units may be combined into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0022] Product information 120 is information for managing pharmaceutical products. Seller information 121 is information for managing sellers of products. Sales performance information 122 is information for managing sales performance. Adjustment rate information 123 is information for managing adjustment rates used to calculate the selling price of products. The adjustment rate is what is known as a markup rate.

[0023] The medicine management system 100 may store information for managing the counting results of the counting unit 111.

[0024] Sales record 130, price revision information 131, product master 132, and customer master 133 are input to the drug management system 100.

[0025] The sales performance 130 includes the fiscal year, the customer, the product, and the sales amount. The sales performance 130 is reflected in the sales performance information 122. The price revision information 131 is information about the price of the product for the next fiscal year.

[0026] The product master 132 is master information of a product. Data including the product code, name, and product features is recorded in the product master 132. The product master 132 is reflected in the product information 120.

[0027] The sales destination master 133 is master information of sales destinations. The sales destination master 133 records data including the code, name, and characteristics of the sales destination. The sales destination master 133 is reflected in the sales destination information 121.

[0028] In this embodiment, the product characteristics, customer characteristics, and adjustment rates are managed separately, so by inputting the product master 132 and customer master 133, the product characteristics and customer characteristics can be changed, and the adjustment rate to be applied can also be dynamically changed.

[0029] FIG. 3 is a diagram illustrating an example of the data structure of the product information 120 according to the first embodiment.

[0030] The product information 120 stores entries including a product CD301, a product name CD302, a product category CD303, and a product management category CD304. One entry exists for one product. Note that the fields included in an entry are not limited to those described above. For example, it may include fields for storing the current year's drug price, invoice price, sales price, etc.

[0031] The product CD 301 is a field for storing the product code, and the product name 302 is a field for storing the product name.

[0032] The product category CD303 and the product management category CD304 are fields for storing the characteristics of the product. The product category CD303 is a field for storing a code representing the category of the product. The product category CD303 may store codes for two or more product categories. The product management category CD304 is a field for storing a code representing a category (product management category) that represents the price management policy of the product.

[0033] FIG. 4 is a diagram illustrating an example of the data structure of the sales destination information 121 according to the first embodiment.

[0034] The sales destination information 121 stores entries including a sales destination CD401, a sales destination name 402, a management structure CD403, a sales scale CD404, and a sales destination management category CD405. One entry exists for one sales destination. Note that the fields included in the entry are not limited to those described above.

[0035] The sales destination CD 401 is a field for storing the code of the sales destination. The sales destination name 402 is a field for storing the name of the sales destination.

[0036] The management type CD403, sales scale CD404, and customer management category CD405 are fields that store the characteristics of the customer. The management type CD403 is a field that stores a code that indicates the management type of the customer. The sales scale CD404 is a field that stores a code that indicates the sales scale of the customer. The customer management category CD405 is a field that stores a code that indicates a category (customer management category) that indicates the importance of the customer to the wholesaler.

[0037] FIG. 5 is a diagram illustrating an example of the data structure of the sales performance information 122 according to the first embodiment.

[0038] The sales performance information 122 stores entries including a fiscal year 501, a customer CD 502, a product CD 503, a quantity 504, a sales amount 505, a sales price 506, and a gross price 507. One entry exists for one sales performance. Note that the fields included in the entry are not limited to those described above.

[0039] The fiscal year 501 is a field for storing the fiscal year. The customer CD 502 is a field for storing the customer code. The product CD 503 is a field for storing the product code.

[0040] Quantity 504 is a field for storing the number of items sold. Sales 505 is a field for storing the sales amount of the item. Sales price 506 is a field for storing the sales price (unit price) of the item. Gross price 507 is a field for storing the gross price of the item.

[0041] 6A, 6B, 6C, 6D, and 6E are diagrams illustrating an example of the data structure of the adjustment rate information 123 according to the first embodiment.

[0042] The adjustment rate information 123 stores a plurality of tables for managing adjustment rates. Specifically, the adjustment rate information 123 stores tables 600, 610, 620, 630, and 640.

[0043] The table 600 stores entries each including a product category CD 601, a description 602, and an adjustment rate 603. There is one entry for each product category. Note that the fields included in the entry are not limited to those described above.

[0044] Product category CD 601 is a field that stores a code that indicates the product category. Description 602 is a field that stores a description of the product category. Description 602 stores, for example, text. Adjustment rate 603 is a field that stores the adjustment rate.

[0045] Patented products and basic medicines are likely to be purchased more than other medicines even if their selling prices are high, so adjustment rates are set to increase their selling prices. On the other hand, generic drugs and other medicines are likely to be purchased less if their selling prices are high, so adjustment rates are set to decrease their selling prices.

[0046] The table 610 stores entries including a product management category CD 611, a description 612, and an adjustment rate 613. There is one entry for each product management category. Note that the fields included in the entry are not limited to those described above.

[0047] The product management category CD 611 is a field for storing a code representing the product management category. The description 612 is a field for storing a description of the product management category. For example, text is stored in the description 612. The adjustment rate 613 is a field for storing the adjustment rate.

[0048] The price strictness control category indicates that the selling price is controlled not to exceed the suggested retail price at the request of the distributor such as a pharmaceutical company. Therefore, an adjustment rate is set so that products with the price strictness control category do not become too expensive.

[0049] The table 620 stores entries including a business form CD 621, a description 622, and an adjustment rate 623. There is one entry for each business form. Note that the fields included in the entry are not limited to those described above.

[0050] Management style CD 621 is a field for storing a code representing the management style. Description 622 is a field for storing a description of the management style. For example, text is stored in description 622. Adjustment rate 623 is a field for storing an adjustment rate.

[0051] Hospitals with fewer beds purchase fewer products, so an adjustment rate is set so that the selling price is higher than the wholesale price in order to ensure profits.

[0052] The table 630 stores entries including a sales scale CD 631, a description 632, a sales scale 633, and an adjustment rate 634. There is one entry for each sales scale. Note that the fields included in the entry are not limited to those described above.

[0053] Sales scale CD 631 is a field that stores a code that represents the sales scale. Description 632 is a field that stores a description of the sales scale. Description 632 stores, for example, text. Sales scale 633 is a field that stores an amount that represents the sales scale. Adjustment rate 634 is a field that stores the adjustment rate.

[0054] Hospitals with small sales volumes tend to purchase fewer products, so an adjustment rate is set so that the selling price is higher than the wholesale price in order to ensure profits.

[0055] The table 640 stores entries including a sales destination management category CD 641, a description 642, and an adjustment rate 643. There is one entry for one product management category. Note that the fields included in the entry are not limited to those described above.

[0056] The sales destination management category CD 641 is a field that stores a code that indicates the sales destination management category. The description 642 is a field that stores a description of the sales destination management category. For example, text is stored in the description 642. The adjustment rate 643 is a field that stores the adjustment rate.

[0057] By lowering the selling price of products to important customers, wholesalers hope to encourage them to continue purchasing from them. The adjustment rate is set in accordance with the incentives that wholesalers receive.

[0058] The index used to calculate the selling price is not limited to the adjustment rate, and may be a quantitative value, for example.

[0059] FIG. 7 is a diagram illustrating an example of the data structure of the prediction information 124 according to the first embodiment.

[0060] The forecast information 124 stores entries including a fiscal year 701, a customer CD 702, a product CD 703, a quantity 704, sales 705, a sales price 706, a gross price 707, and an adjustment rate 708. There is one entry for each combination of a fiscal year, a customer, and a product. Note that the fields included in an entry are not limited to those described above.

[0061] The fiscal year 701 is a field for storing the fiscal year. The customer CD 702 is a field for storing the customer code. The product CD 703 is a field for storing the product code.

[0062] Quantity 704 is a field that stores the predicted sales quantity of the product. Sales 705 is a field that stores the predicted sales of the product. Selling price 706 is a field that stores the selling price of the product calculated by the process described below. Gross price 707 is a field that stores the gross price of the product.

[0063] Adjustment rate 708 is a group of fields that store adjustment rates used to calculate the product sales price. Field (1) stores the product category code, field (2) stores the business model code, field (3) stores the sales scale code, field (4) stores the product management category code, and field (5) stores the customer management category code. The adjustment rate can be determined by referencing adjustment rate information 123 based on each code. Note that the adjustment rate itself may also be stored in each field.

[0064] FIG. 8 is a diagram illustrating an example of a data structure of the price revision information 131 according to the first embodiment.

[0065] The price revision information 131 stores entries including a product CD 801, a drug price revision date 802, a drug price 803, a wholesale price 804, and a base price 805. There is one entry for each product. Note that the fields included in the entry are not limited to those described above.

[0066] Product CD 801 is a field that stores the product code. Drug price revision date 802 is a field that stores the date on which the drug price of the product is revised. Drug price 803 is a field that stores the drug price of the product. Invoice price 804 is a field that stores the invoice price of the product. Base price 805 is a field that stores the base value of the selling price of the product.

[0067] FIG. 9 is a flowchart illustrating an example of processing executed by the medicine management system 100 according to the first embodiment.

[0068] When the pharmaceutical management system 100 receives an execution instruction from the terminal 101, it starts the processing described below. In this embodiment, the pharmaceutical management system 100 calculates the sales price of pharmaceuticals for each customer for the next fiscal year based on the characteristics of the customer and the sales performance of pharmaceuticals for the current fiscal year. Here, the processing is described assuming that the sales volume of the product for the next fiscal year will be the same as the sales volume for the current fiscal year. The sales volume of the product for the next fiscal year may be calculated using a known prediction model or may be input by the user.

[0069] The selling price / sales calculation unit 110 starts a loop process of products (step S101). Specifically, the selling price / sales calculation unit 110 selects one entry from the product information 120. Hereinafter, the selected product will be referred to as a target product.

[0070] Next, the selling price / sales calculation unit 110 starts a loop process of buyers (step S102). Specifically, the selling price / sales calculation unit 110 selects one entry from the buyer information 121. Hereinafter, the selected buyer will be referred to as a target buyer.

[0071] Next, the sales price / sales calculation unit 110 refers to the sales performance information 122 and determines whether or not the sales performance in which the current year, the code of the target sales customer, and the code of the target product are stored in the year 501, the customer CD 502, and the product CD 503 (step S103).

[0072] If there is no sales record, the sales price / sales amount calculation unit 110 sets the base price in the price revision information 131 as the sales price (step S104), and then proceeds to step S112.

[0073] At this time, the selling price / sales calculation unit 110 adds an entry to the forecast information 124, and sets the next fiscal year, the code of the target customer, and the code of the target product in the fiscal year 701, the customer CD 702, and the product CD 703. The selling price / sales calculation unit 110 also sets the values ​​of the base price 805 and the invoice price 804 in the price revision information 131 in the selling price 706 and the invoice price 707 of the entry. Because no sales record exists, the quantity 704 and the sales 705 are left blank. Furthermore, because an adjustment rate is not used, the adjustment rate 708 is left blank.

[0074] If a sales record exists, the sales price / sales calculation unit 110 calculates the sales price for the next year using the sales price for the current year and the adjustment rate.

[0075] First, the sales price / sales amount calculation unit 110 changes the sales price for the current year based on the adjustment rate of the product category (step S105). The sales price calculated in step S105 is described as the first price.

[0076] For example, if the sales price for the current year is 1,000 yen and the adjustment rate is 0.3, the sales price for the current year will be changed as shown in the formula below. 1000 yen x (1 + 0.3) = 1300 yen

[0077] Next, the selling price / sales calculation unit 110 changes the first price based on the adjustment rate of the management form (step S106). The selling price calculated in step S106 is described as the second price.

[0078] For example, if the adjustment rate is 0.3, the first price is changed as follows: 1,300 yen x (1 + 0.3) = 1,690 yen

[0079] Next, the selling price / sales calculation unit 110 changes the second price based on the adjustment rate of the sales scale (step S107). The selling price calculated in step S107 is described as the third price.

[0080] For example, if the adjustment rate is 0, the second price is changed as follows: 1690 yen x (1 + 0) = 1690 yen

[0081] Next, the selling price / sales amount calculation unit 110 changes the third price based on the adjustment rate of the product management category (step S108). The selling price calculated in step S108 is described as the fourth price.

[0082] For example, if the adjustment rate is -0.1, the third price will be changed as follows: 1,690 yen x (1 - 0.1) = 1,521 yen

[0083] Next, the selling price / sales amount calculation unit 110 changes the fourth price based on the adjustment rate of the buyer management category (step S109). The selling price calculated in step S109 is described as the fifth price.

[0084] For example, if the adjustment rate is 0, the fourth price is changed as follows: 1521 yen x (1 + 0) = 1521 yen

[0085] Next, the selling price / sales calculation unit 110 changes the fifth price depending on whether or not the drug price has been revised (step S110).

[0086] For example, if the adjustment rate is set to -0.1 when there is a drug price revision, the fifth price will be changed as shown in the formula below. 1521 yen x (1 - 0.1) = 1368.9 yen

[0087] The selling price / sales amount calculation unit 110 sets the price calculated in the processes from step S105 to step S110 as the selling price (step S111), and then proceeds to step S112.

[0088] At this time, the selling price / sales calculation unit 110 adds an entry to the forecast information 124, and sets the next fiscal year, the code of the target customer, and the code of the target product in the fiscal year 701, the customer CD 702, and the product CD 703. The selling price / sales calculation unit 110 sets the value of the invoice price 804 in the price revision information 131 in the invoice price 707 of the entry. The selling price / sales calculation unit 110 sets the calculated price in the selling price 706 of the entry, and sets information on the adjustment rate used in the adjustment rate 708. In addition, the selling price / sales calculation unit 110 sets the value of the quantity 504 of the actual sales results in the quantity 704, and sets the value obtained by multiplying the values ​​of the quantity 704 and the selling price 706 in the sales 705.

[0089] In step S112, the selling price / sales calculation unit 110 determines whether or not the process has been completed for all buyers (step S112). If the process has not been completed for all buyers, the selling price / sales calculation unit 110 selects a new buyer and returns to step S103.

[0090] When the processing is completed for all buyers, the selling price / sales calculation unit 110 determines whether the processing is completed for all products (step S113). When the processing is not completed for all products, the selling price / sales calculation unit 110 selects a new product and returns to step S102.

[0091] When the processing has been completed for all products, the selling price / sales amount calculation unit 110 ends the processing.

[0092] The order of the processes from step S105 to step S110 may be changed, or only a part of the processes from step S105 to step S110 may be executed.

[0093] The sales price may be calculated using the base price instead of the sales price for the current fiscal year. In this case, surcharges and discounts may be used as indicators instead of adjustment rates.

[0094] Next, a description will be given of screens presented by the drug management system 100. Figures 10A, 10B, 10C, 10D, and 10E are diagrams illustrating examples of screens presented by the drug management system 100 of the first embodiment.

[0095] The output unit 112 displays a screen 1000. The screen 1000 includes a selection field 1001, a tally button 1002, and a display field 1003.

[0096] Selection field 1001 is a field for selecting an aggregation item. The aggregation items displayed in selection field 1001 are product category, business form, sales scale, product management category, and customer management category. Aggregation button 1002 is a button for issuing an instruction to aggregate.

[0097] The user selects a tally item from the selection field 1001 and operates the tally button 1002. When the tallying unit 111 of the medicine management system 100 receives this operation, it tally the entries of the sales performance information 122 and the entries of the forecast information 124. The output unit 112 displays the tally result in the display field 1003.

[0098] FIG. 10A displays the results of entries aggregated based on product category. FIG. 10B displays the results of entries aggregated based on business type. FIG. 10C displays the results of entries aggregated based on sales volume. FIG. 10D displays the results of entries aggregated based on product management category. FIG. 10E displays the results of entries aggregated based on customer management category.

[0099] A table including, for example, sales, quantity, sales price, adjustment rate, and profit margin as fields is displayed in the display field 1003. The aggregation may be performed for a specific product, or for all products.

[0100] In this way, by presenting the predicted sales of products for various summary items, the user can grasp the calculated sales price as a management indicator.

[0101] Furthermore, by checking the forecasted sales, the user can, for example, check how much the adjustment rate set for each management type will affect sales, and can review the adjustment rate.

[0102] As described above, the pharmaceutical management system 100 can calculate the selling price of a product based on the characteristics of the customer. In this way, when a wholesaler determines the selling price of a product, the characteristics of the customer, such as the type of business, management style, and sales volume, are taken into consideration, allowing the wholesaler to calculate a selling price that will ensure profits and develop sales channels. [Example]

[0103] The second embodiment differs from the first embodiment in that predicted sales are calculated.

[0104] The system configuration of Example 2 is the same as that of Example 1. The hardware configuration and software configuration of the drug management system 100 of Example 2 are the same as those of Example 1. The data structure of the information other than the forecast information 124 of the drug management system 100 of Example 2 is the same as that of Example 1. The forecast information 124 of Example 2 does not include the selling price 706.

[0105] FIG. 11 is a flowchart illustrating an example of processing executed by the medicine management system 100 according to the second embodiment.

[0106] When the pharmaceutical management system 100 receives an execution instruction from the terminal 101, it starts the process described below. Here, the process is described assuming that the sales volume of the product in the next fiscal year will be the same as the sales volume in the current fiscal year. The sales volume of the product in the next fiscal year may be calculated using a known prediction model or may be input by the user.

[0107] The selling price / sales calculation unit 110 starts a loop process of products (step S201). Specifically, the selling price / sales calculation unit 110 selects one entry from the product information 120. Hereinafter, the selected product will be referred to as a target product.

[0108] Next, the selling price / sales calculation unit 110 starts a loop process of buyers (step S202). Specifically, the selling price / sales calculation unit 110 selects one entry from the buyer information 121. Hereinafter, the selected buyer will be referred to as a target buyer.

[0109] Next, the sales price / sales calculation unit 110 refers to the sales result information 122 and determines whether or not a sales result in which the current year, the code of the target customer, and the code of the target product are stored in the year 501, the customer CD 502, and the product CD 503 is stored (step S203). If no sales result exists, the sales price / sales calculation unit 110 proceeds to step S211.

[0110] If a sales record exists, the sales price / sales calculation unit 110 calculates the predicted sales for the next year using the sales for the current year and the adjustment rate.

[0111] First, the selling price / sales calculation unit 110 changes the sales for the current year based on the adjustment rate of the product category (step S204). The sales calculated in step S204 is described as the first sales.

[0112] For example, if the sales for the current year are 1 million yen and the adjustment rate is 0.3, the sales for the current year will be changed as shown in the formula below. 1 million yen x (1 + 0.3) = 1.3 million yen

[0113] Next, the selling price / sales calculation unit 110 changes the first sales based on the adjustment rate of the management form (step S205). The sales calculated in step S205 are described as second sales.

[0114] For example, if the adjustment rate is 0.3, the first sales amount is changed as shown in the following formula. 1.3 million yen x (1 + 0.3) = 1.69 million yen

[0115] Next, the selling price / sales amount calculation unit 110 changes the second sales amount based on the adjustment rate of the sales amount (step S206). The sales amount calculated in step S206 is described as the third sales amount.

[0116] For example, if the adjustment rate is 0, the second sales amount is changed as follows: 1.69 million yen x (1 + 0) = 1.69 million yen

[0117] Next, the selling price / sales amount calculation unit 110 changes the third sales amount based on the adjustment rate of the product management category (step S207). The sales amount calculated in step S207 is written as the fourth sales amount.

[0118] For example, if the adjustment rate is -0.1, the third sales amount will be changed as shown in the formula below. 1.69 million yen x (1-0.1) = 1.521 million yen

[0119] Next, the selling price / sales amount calculation unit 110 changes the fourth sales amount based on the adjustment rate of the sales destination management category (step S208). The sales amount calculated in step S208 is entered as the fifth sales amount.

[0120] For example, if the adjustment rate is 0, the fourth sales amount will be changed as shown in the formula below. 1,521,000 yen x (1-0) = 1,521,000 yen

[0121] Next, the selling price / sales calculation unit 110 changes the fifth sales depending on whether or not the drug price has been revised (step S209).

[0122] For example, if the adjustment rate is set to -0.1 when there is a drug price revision, the fifth sales will be changed as shown in the formula below. 1,521,000 yen x (1-0.1) = 1,368,900 yen

[0123] The selling price / sales amount calculation unit 110 sets the sales amount calculated in the processes from step S204 to step S209 as the predicted sales amount (step S210), and then proceeds to step S211.

[0124] In step S211, the selling price / sales calculation unit 110 determines whether or not the process has been completed for all buyers (step S211). If the process has not been completed for all buyers, the selling price / sales calculation unit 110 selects a new buyer and returns to step S203.

[0125] When the processing is completed for all buyers, the selling price / sales calculation unit 110 determines whether the processing is completed for all products (step S212). When the processing is not completed for all products, the selling price / sales calculation unit 110 selects a new product and returns to step S202.

[0126] When the process has been completed for all products, the selling price / sales calculation unit 110 calculates the sum of the calculated predicted sales (step S213), and then ends the process.

[0127] The order of the processes from step S204 to step S209 may be changed, or only a part of the processes from step S204 to step S209 may be executed.

[0128] As described above, the medicine management system 100 can calculate the predicted sales taking into account the characteristics of the sales destination.

[0129] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments are provided to explain the present invention in detail, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

[0130] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, solid-state drives (SSDs), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.

[0131] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, and Java (registered trademark).

[0132] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or storage medium.

[0133] In the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All components may be interconnected. [Explanation of symbols]

[0134] 100 Pharmaceutical Management System 101 terminals 102 Network 110 Selling Price / Sales Calculation Unit 111 Counting Department 112 Output section 120 Product information 121 Sales Information 122 Sales performance information 123 Adjustment rate information 124 Forecast Information 130 Sales Results 131 Price Change Information 132 Product Master 133 Sales Master 200 calculator 201 processor 202 Main storage 203 Secondary storage device 204 Network Interface 205 Bus 1000 screens

Claims

1. 1. A computer system comprising: a processor, a storage device connected to the processor, and a network interface connected to the processor; The method holds sales destination information for managing sales destinations of pharmaceuticals, performance information for managing sales performance of the pharmaceuticals, and adjustment index information for managing a first index that is set based on the characteristics of the sales destinations and is used to adjust the sales price of the pharmaceuticals, The sales destination information stores data including identification information of the sales destination and information related to characteristics of the sales destination; The sales record includes identification information of the drug, identification information of the sales destination, and a sales price of the drug, The processor: Acquire the sales record for each combination of the sales destination and the pharmaceutical product; A computer system characterized by: for each combination of the sales destination and the pharmaceutical, obtaining the first index from the adjustment index information based on the sales destination information; and calculating a new sales price for the pharmaceutical by using the first index to change the sales price of the pharmaceutical included in the sales record.

2. 2. The computer system of claim 1, The characteristics of the customer include a management type of the customer, a sales volume, and a customer management classification that indicates the importance of the customer to a vendor that sells the pharmaceutical product; A computer system characterized in that the adjustment index information stores the first index for each of the customer's management type, sales volume, and customer management classification.

3. 3. The computer system according to claim 2, maintaining pharmaceutical information for managing the pharmaceuticals; The drug information stores data including identification information of the drug and information regarding characteristics of the drug; the adjustment index information stores a second index that is set based on the characteristics of the drug and is used to adjust the selling price of the drug; The processor obtains the first index and the second index from the adjustment index information based on the sales destination information and the drug information for each combination of the sales destination and the drug, and calculates a new sales price of the drug by using the first index and the second index to change the sales price of the drug included in the sales record.

4. 4. The computer system according to claim 3, The characteristics of the drug include a classification of the drug and a product management classification indicating a price management policy of the trader for the drug; A computer system characterized in that the adjustment index information stores the second index for each of the drug classification and the product management classification.

5. 5. The computer system of claim 4, The processor: recording the prediction result including the identification information of the sales destination, the identification information of the drug, and the new selling price of the drug; A computer system characterized by aggregating the sales performance and forecast results based on any of the aggregation items of the management type of the customer, the sales volume of the customer, the customer management category of the customer, the pharmaceutical category, and the pharmaceutical product category, and outputting the aggregation results.

6. 6. The computer system according to claim 5, The computer system is characterized in that the processor accepts the selection of the tally items and provides an interface for displaying the results of the tally.

7. A method for calculating a pharmaceutical sales price executed by a computer system, comprising: The computer system a processor, a storage device connected to the processor, and a network interface connected to the processor; The system holds customer information for managing the customers of pharmaceutical products, sales performance information for managing sales performance of the pharmaceutical products, and adjustment index information that is set based on the characteristics of the customer and that is used to manage indexes used to adjust the sales prices of the pharmaceutical products, The sales destination information stores data including identification information of the sales destination and information related to characteristics of the sales destination; The sales record includes identification information of the drug, identification information of the sales destination, and a sales price of the drug, The method for calculating the selling price of the pharmaceutical product is as follows: The processor acquires the sales performance for each combination of the sales destination and the pharmaceutical product; The processor acquires the index from the adjustment index information based on the customer information for each combination of the customer and the drug, and calculates a new sales price of the drug by changing the sales price of the drug included in the sales record using the index; A method for calculating the selling price of a pharmaceutical product, comprising:

8. The method for calculating the selling price of a pharmaceutical product according to claim 7, The characteristics of the customer include a management type of the customer, a sales volume, and a customer management classification that indicates the importance of the customer to a vendor that sells the pharmaceutical product; A method for calculating the selling price of a pharmaceutical, characterized in that the adjustment index information stores the indexes for each of the sales destination's management type, sales volume, and sales destination management classification.

9. A program to be executed by a computer, The computer a processor, a storage device connected to the processor, and a network interface connected to the processor; The system holds customer information for managing the customers of pharmaceutical products, sales performance information for managing sales performance of the pharmaceutical products, and adjustment index information that is set based on the characteristics of the customer and that is used to manage indexes used to adjust the sales prices of the pharmaceutical products, The sales destination information stores data including identification information of the sales destination and information related to characteristics of the sales destination; The sales record includes identification information of the drug, identification information of the sales destination, and a sales price of the drug, The program a step of acquiring the sales record for each combination of the sales destination and the pharmaceutical product; a step of calculating a new sales price of the drug by acquiring the index from the adjustment index information based on the sales destination information for each combination of the sales destination and the drug, and changing the sales price of the drug included in the sales record using the index; A program for causing the computer to execute the above.

10. 10. The program according to claim 9, The characteristics of the customer include a management type of the customer, a sales volume, and a customer management classification that indicates the importance of the customer to a vendor that sells the pharmaceutical product; The program is characterized in that the adjustment index information stores the indexes for each of the customer's management type, sales volume, and customer management classification.

Images