Computer system, method for calculating the selling price of pharmaceuticals, and program
A computer system calculates pharmaceutical selling prices based on customer characteristics, addressing the lack of consideration for business type and sales volume in existing methods, ensuring accurate pricing and profitable sales forecasts.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- HITACHI LTD
- Filing Date
- 2024-05-16
- Publication Date
- 2026-05-29
AI Technical Summary
Existing technologies do not adequately consider the characteristics of customers, such as business type, management structure, and sales volume, when determining the selling price of pharmaceuticals, leading to inaccurate sales forecasts and pricing decisions.
A computer system that includes a processor, storage device, and network interface, which manages customer information, sales performance, and adjustment indicators to calculate selling prices based on customer characteristics, using adjustment rates to dynamically adjust prices for pharmaceutical products.
Enables accurate determination of selling prices based on customer characteristics, ensuring profitability and effective sales channel development by considering business type, management structure, and sales volume.
Smart Images
Figure 0007867517000001 
Figure 0007867517000002 
Figure 0007867517000003
Abstract
Description
Technical Field
[0001] The present invention relates to a technology for managing pharmaceuticals.
Background Art
[0002] When selling pharmaceuticals, pharmaceutical companies determine the price of the pharmaceuticals sold to wholesalers (hereinafter referred to as "partition price") in consideration of manufacturing costs, research and development expenses, etc. When wholesalers sell the pharmaceuticals purchased from pharmaceutical companies at the partition price to pharmacies and hospitals, they determine the price of the pharmaceuticals sold to pharmacies and hospitals in consideration of costs and profits related to sales, etc. In such a pharmaceutical price determination process, it is required to support the calculation of an appropriate price in consideration of the costs related to the sales of wholesalers.
[0003] Patent Document 1 describes that "it includes an environmental maintenance storage means for storing pharmaceuticals while maintaining environmental conditions, a storage environment detection means for acquiring information on environmental conditions in the environmental maintenance storage means, a storage state detection means for detecting the storage of pharmaceuticals by the environmental maintenance storage means, an environmental maintenance transportation means for transporting pharmaceuticals while maintaining environmental conditions, a transportation environment detection means for acquiring information on environmental conditions in the environmental maintenance transportation means, a transportation state detection means for detecting the transportation of pharmaceuticals by the environmental maintenance transportation means, and a claim amount derivation means for deriving the claim amount to the delivery destination of the pharmaceuticals based on the information obtained by each of the above detection means. The claim amount derivation means targets pharmaceuticals for which the delivery from the environmental maintenance storage means has been detected by the storage state detection means of the delivery destination of the pharmaceuticals within a predetermined period."
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] When wholesalers determine the selling price of pharmaceuticals, considering the characteristics of the customer, such as the type of business, management structure, and sales volume, allows for more accurate sales forecasts and leads to the determination of appropriate selling prices. However, the technology described in Patent Document 1 does not disclose how to determine the selling price of pharmaceuticals by considering the characteristics of the customer.
[0006] A typical example of the invention disclosed in this application is as follows: a computer system comprising a processor, a storage device connected to the processor, and a network interface connected to the processor. The aforementioned storage device is Sales destination information for managing the sales destinations of pharmaceuticals, sales performance information for managing the sales performance of said pharmaceuticals, and settings based on the characteristics of said sales destinations. It is an indicator The system maintains adjustment indicator information for managing a first indicator used to adjust the sales price of the aforementioned pharmaceutical product, and the sales destination information. to This includes data containing the identification information of the customer and information regarding the characteristics of the customer. but Store So The aforementioned sales record includes the identification information of the pharmaceutical product, the identification information of the sales destination, and the sales price of the pharmaceutical product. The characteristics of the customer include at least the business structure of the customer, the sales volume, and the customer management classification representing the importance of the customer to the distributor of the pharmaceuticals, and the adjustment indicator information stores data including at least the first indicator of the business structure of the customer, the sales volume, and the customer management classification. The processor acquires sales results for each combination of customer and pharmaceutical product, acquires the first index from the adjustment index information based on the customer information for each combination of customer and pharmaceutical product, and calculates a new sales price for the pharmaceutical product by changing the sales price of the pharmaceutical product included in the sales results using the first index. [Means for solving the problem]
[0007] A typical example of the invention disclosed in this application is as follows: A computer system comprising a processor, a storage device connected to the processor, and a network interface connected to the processor, which holds customer information for managing customers of a pharmaceutical product, sales performance information for managing sales performance of the pharmaceutical product, and adjustment index information for managing a first index set based on the characteristics of the customer and used to adjust the sales price of the pharmaceutical product, wherein the customer information stores data including identification information of the customer and information regarding the characteristics of the customer, the sales performance includes identification information of the pharmaceutical product, identification information of the customer, and the sales price of the pharmaceutical product, the processor acquires the sales performance for each combination of the customer and the pharmaceutical product, acquires the first index from the adjustment index information based on the customer information for each combination of the customer and the pharmaceutical product, and calculates a new sales price of the pharmaceutical product by changing the sales price of the pharmaceutical product included in the sales performance using the first index. [Effects of the Invention]
[0008] According to one embodiment of the present invention, the selling price of a pharmaceutical product can be determined according to the characteristics of the sales destination. Other problems, configurations, and effects will be clarified by the following description of the examples. [Brief explanation of the drawing]
[0009] [Figure 1] This figure shows an example of the system configuration of Example 1. [Figure 2] This figure shows an example of the hardware configuration of the computer that constitutes the pharmaceutical management system of Example 1. [Figure 3] This figure shows an example of the data structure of product information in Example 1. [Figure 4] This figure shows an example of the data structure of customer information in Example 1. [Figure 5] This figure shows an example of the data structure of sales performance information in Example 1. [Figure 6A]This is a diagram showing an example of the data structure of the adjustment rate information in Example 1. [Figure 6B] This is a diagram showing an example of the data structure of the adjustment rate information in Example 1. [Figure 6C] This is a diagram showing an example of the data structure of the adjustment rate information in Example 1. [Figure 6D] This is a diagram showing an example of the data structure of the adjustment rate information in Example 1. [Figure 6E] This is a diagram showing an example of the data structure of the adjustment rate information in Example 1. [Figure 7] This is a diagram showing an example of the data structure of the prediction information in Example 1. [Figure 8] This is a diagram showing an example of the data structure of the price revision information in Example 1. [Figure 9] This is a flowchart for explaining an example of the process executed by the pharmaceutical management system in Example 1. [Figure 10A] This is a diagram for explaining an example of the screen presented by the pharmaceutical management system in Example 1. [Figure 10B] This is a diagram for explaining an example of the screen presented by the pharmaceutical management system in Example 1. [Figure 10C] This is a diagram for explaining an example of the screen presented by the pharmaceutical management system in Example 1. [Figure 10D] This is a diagram for explaining an example of the screen presented by the pharmaceutical management system in Example 1. [Figure 10E] This is a diagram for explaining an example of the screen presented by the pharmaceutical management system in Example 1. [Figure 11] This is a flowchart for explaining an example of the process executed by the pharmaceutical management system in Example 2.
Embodiments for Carrying Out the Invention
[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not to be construed as being limited to the description of the embodiments shown below. It will be readily understood by those skilled in the art that the specific configuration can be changed without departing from the spirit or gist of the present invention.
[0011] In the configuration of the invention described below, the same or similar components or functions are denoted by the same reference numerals, and duplicate descriptions are omitted.
[0012] The notations such as "first", "second", "third", etc. in this specification and the like are attached to identify components, and do not necessarily limit numbers or orders.
Example
[0013] FIG. 1 is a diagram showing an example of the configuration of the system of Example 1. FIG. 2 is a diagram showing an example of the hardware configuration of a computer constituting the pharmaceutical management system of Example 1.
[0014] The system is composed of a pharmaceutical management system 100 and a terminal 101. The communication between the pharmaceutical management system 100 and the terminal 101 can use a general public communication network, whether wired or wireless, for example, the fifth-generation mobile communication system that enables "multiple simultaneous connections" and "ultra-low latency", so-called 5G (5th Generation).
[0015] The terminal 101 is a terminal operated by a user. The pharmaceutical management system 100 calculates the selling price or predicted sales of pharmaceuticals for the next year based on the sales performance of pharmaceuticals in the current year.
[0016] The pharmaceutical management system 100 is realized, for example, using a computer 200 as shown in FIG. 2. The computer 200 has a processor 201, a main memory device 202, an auxiliary storage 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. By executing processing according to the program, the processor 201 operates as a functional unit (module) that realizes a specific function. In the following description, when explaining processing with the functional unit as the subject, it indicates that the processor 201 is executing a program that realizes the functional unit.
[0018] The main memory 202 is a memory device that stores programs executed by the processor 201 and information used by those programs. The main memory 202 is also used as a work area. The secondary memory 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 202 may also be stored in the secondary memory 203. In this case, the processor 201 reads the programs and information from the secondary memory 203 and loads them into the main memory 202. The network interface 204 is an interface for connecting to the network 102.
[0019] The pharmaceutical management system 100 includes a sales price / sales calculation unit 110, an aggregation unit 111, and an output unit 112. The pharmaceutical management system 100 also stores product information 120, sales destination information 121, sales performance information 122, and adjustment rate information 123.
[0020] The sales price / sales calculation unit 110 calculates the sales price for each product for each customer and also calculates projected sales. The processing results of the sales price / sales calculation unit 110 are stored as projected information 124. The aggregation unit 111 uses the projected information 124 to aggregate data according to the specified aggregation items. The output unit 112 outputs various information to the terminal 101.
[0021] Furthermore, regarding the functional units of the pharmaceutical management system 100, multiple functional units may be combined into a single functional unit, or a single functional unit may be divided into multiple functional units according to its function.
[0022] Product information 120 is information for managing the pharmaceutical product. Sales destination information 121 is information for managing the sales destinations of the product. Sales performance information 122 is information for managing sales performance. Adjustment rate information 123 is information for managing the adjustment rate used to calculate the sales price of the product. The adjustment rate is what is commonly known as the price increase rate.
[0023] The pharmaceutical management system 100 may also store information for managing the aggregation results of the aggregation unit 111.
[0024] The pharmaceutical management system 100 receives data including sales records 130, price revision information 131, product master data 132, and customer master data 133.
[0025] Sales performance data 130 includes the year, sales destination, product, and sales figures. Sales performance data 130 is reflected in sales performance information 122. Price revision information 131 is information on the price of the product for the following year.
[0026] Product Master 132 is the master information for a product. Product Master 132 records data including the product code, name, and product characteristics. Product Master 132 is reflected in Product Information 120.
[0027] The customer master 133 is the master information for customers. The customer master 133 records data including the customer's code, name, and characteristics. The customer master 133 is reflected in the customer information 121.
[0028] In this embodiment, since the characteristics of the product and the characteristics of the sales destination are managed separately from the adjustment rate, the characteristics of the product and the characteristics of the sales destination can be changed by inputting the product master 132 and the sales destination master 133, and the adjustment rate to be applied can be changed dynamically as a result.
[0029] Figure 3 shows an example of the data structure of product information 120 in Example 1.
[0030] Product information 120 stores entries that include product code 301, product name 302, product category code 303, and product management category code 304. There is one entry for each product. Note that the fields included in the entry are not limited to those mentioned above. For example, it may include fields that store the drug price, wholesale price, and sales price for the current year.
[0031] Product Code 301 is a field that stores the product code. Product Name 302 is a field that stores the product name.
[0032] Product Classification CD303 and Product Management Classification CD304 are fields that store the characteristics of the product. Product Classification CD303 is a field that stores a code representing the product classification. Product Classification CD303 may store codes for two or more product classifications. Product Management Classification CD304 is a field that stores a code representing a classification (product management classification) that represents the price management policy for the product.
[0033] Figure 4 shows an example of the data structure of customer information 121 in Example 1.
[0034] The customer information 121 stores entries that include customer CD401, customer name 402, business type CD403, sales volume CD404, and customer management category CD405. There is one entry for each customer. Note that the fields included in the entries are not limited to those described above.
[0035] The Destination CD401 field stores the destination code. The Destination Name 402 field stores the destination name.
[0036] The fields CD403 (Business Type), CD404 (Sales Volume), and CD405 (Customer Management Classification) are fields that store characteristics of the customer. CD403 (Business Type) is a field that stores a code representing the business type of the customer. CD404 (Sales Volume) is a field that stores a code representing the sales volume of the customer. CD405 (Customer Management Classification) is a field that stores a code representing the classification (customer management classification) that indicates the importance of the customer to the wholesaler.
[0037] Figure 5 shows an example of the data structure of sales performance information 122 in Example 1.
[0038] Sales performance information 122 stores entries that include the year 501, customer code 502, product code 503, quantity 504, sales revenue 505, sales price 506, and wholesale price 507. There is one entry for each sales performance. Note that the fields included in the entries are not limited to those described above.
[0039] Year 501 is the field that stores the year. Sales destination CD 502 is the field that stores the sales destination code. Product CD 503 is the field that stores the product code.
[0040] Quantity 504 is the field that stores the number of items sold. Sales 505 is the field that stores the sales revenue for the items. Selling Price 506 is the field that stores the selling price (unit price) of the items. Wholesale Price 507 is the field that stores the wholesale price of the items.
[0041] Figures 6A, 6B, 6C, 6D, and 6E show an example of the data structure of the adjustment rate information 123 in Example 1.
[0042] The adjustment rate information 123 stores multiple tables for managing adjustment rates. Specifically, the adjustment rate information 123 stores tables 600, 610, 620, 630, and 640.
[0043] Table 600 stores entries that include product category CD601, description 602, and adjustment rate 603. There is one entry for each product category. Note that the fields included in an entry are not limited to those described above.
[0044] Product Category CD601 is a field that stores a code representing the product category. Description 602 is a field that stores a description of the product category. For example, text may be stored in Description 602. Adjustment Rate 603 is a field that stores the adjustment rate.
[0045] Patented products and basic medicines are expected to be purchased more than other medicines, even if their selling price is high, so the adjustment rate is set to ensure a higher selling price. On the other hand, generic drugs and other medicines are expected to be purchased less if their selling price is high, so the adjustment rate is set to ensure a lower selling price.
[0046] Table 610 stores entries that include the product management category CD611, description 612, and adjustment rate 613. There is one entry for each product management category. Note that the fields included in an entry are not limited to those described above.
[0047] Product Management Classification CD611 is a field that stores a code representing the product management classification. Description 612 is a field that stores a description of the product management classification. For example, text may be stored in Description 612. Adjustment Rate 613 is a field that stores the adjustment rate.
[0048] The "price adherence" management category indicates that the selling price is managed to prevent it from exceeding the suggested retail price, as requested by the distributor, such as a pharmaceutical company. Therefore, an adjustment rate is set to prevent products in this category from becoming overpriced.
[0049] Table 620 stores entries that include the business type CD621, description622, and adjustment rate623. There is one entry for each business type. Note that the fields included in an entry are not limited to those described above.
[0050] The business type CD621 is a field that stores a code representing the business type. The description 622 is a field that stores a description of the business type. For example, text may be stored in the description 622. The adjustment rate 623 is a field that stores the adjustment rate.
[0051] Hospitals with fewer beds purchase fewer goods, so to ensure profitability, an adjustment rate is set so that the selling price is higher than the wholesale price.
[0052] Table 630 stores entries that include sales scale CD631, description632, sales scale633, and adjustment rate634. There is one entry for each sales scale. Note that the fields included in an entry are not limited to those mentioned above.
[0053] Sales Size CD631 is a field that stores a code representing the sales size. Description 632 is a field that stores a description of the sales size. For example, text may be stored in Description 632. Sales Size 633 is a field that stores the amount representing the sales size. Adjustment Rate 634 is a field that stores the adjustment rate.
[0054] Hospitals with smaller sales volumes purchase fewer items, so to ensure profitability, adjustment rates are set so that the selling price is higher than the wholesale price.
[0055] Table 640 stores entries that include the sales destination management category CD641, description 642, and adjustment rate 643. There is one entry for each product management category. Note that the fields included in the entries are not limited to those described above.
[0056] The customer management category CD641 is a field that stores a code representing the customer management category. The description 642 is a field that stores a description of the customer management category. For example, text may be stored in the description 642. The adjustment rate 643 is a field that stores the adjustment rate.
[0057] By lowering the selling price of goods to important customers for wholesalers, they can expect those customers to continue purchasing from them. The adjustment rate is set to match the incentives that wholesalers receive.
[0058] Furthermore, the indicators used to calculate the selling price are not limited to adjustment rates. For example, quantitative values may be used.
[0059] Figure 7 shows an example of the data structure of prediction information 124 in Example 1.
[0060] Forecast information 124 stores entries including year 701, customer code 702, product code 703, quantity 704, sales 705, selling price 706, transfer price 707, and adjustment rate 708. There is one entry for each combination of year, customer, and product. Note that the fields included in the entries are not limited to those described above.
[0061] Year 701 is the field that stores the year. Sales destination CD 702 is the field that stores the sales destination code. Product CD 703 is the field that stores the product code.
[0062] Quantity 704 is a field that stores the predicted number of units sold for the product. Sales 705 is a field that stores the predicted sales for the product. Selling price 706 is a field that stores the selling price of the product calculated by the process described later. Wholesale price 707 is a field that stores the wholesale price of the product.
[0063] The adjustment rate 708 is a group of fields that store the adjustment rate used to calculate the selling price of a product. Field (1) stores the product category code, field (2) stores the business type code, field (3) stores the sales volume code, field (4) stores the product management category code, and field (5) stores the sales destination management category code. The adjustment rate can be determined by referring to the adjustment rate information 123 based on each code. Note that the adjustment rate itself may also be stored in each field.
[0064] Figure 8 shows an example of the data structure of price revision information 131 in Example 1.
[0065] Price revision information 131 stores entries that include product code 801, drug price revision date 802, drug price 803, wholesale price 804, and standard 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 Code 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. Wholesale Price 804 is a field that stores the wholesale price of the product. Standard Price 805 is a field that stores the standard selling price of the product.
[0067] Figure 9 is a flowchart illustrating an example of the process performed by the pharmaceutical management system 100 of Example 1.
[0068] When the pharmaceutical management system 100 receives an execution instruction from terminal 101, it starts the process described below. In this embodiment, the pharmaceutical management system 100 calculates the sales price of pharmaceuticals for the next fiscal year for each sales customer based on the characteristics of the sales customer and the sales performance of pharmaceuticals for the current fiscal year. Here, we describe the process assuming that the number of products sold in the next fiscal year will be the same as the number sold in the current fiscal year. Note that the number of products sold in the next fiscal year may be calculated using a known predictive model or may be entered by the user.
[0069] The sales price / sales calculation unit 110 starts the product loop processing (step S101). Specifically, the sales price / sales calculation unit 110 selects one entry from the product information 120. Hereafter, the selected product will be referred to as the target product.
[0070] Next, the sales price / sales calculation unit 110 starts the customer loop processing (step S102). Specifically, the sales price / sales calculation unit 110 selects one entry from the customer information 121. Hereafter, the selected customer will be referred to as the target customer.
[0071] Next, the sales price / sales calculation unit 110 refers to the sales performance information 122 and determines whether the sales performance for the current year, target customer code, and target product code is stored in the year 501, customer CD 502, and product CD 503 (step S103).
[0072] If no sales record exists, the sales price / sales calculation unit 110 sets the base price from the price revision information 131 as the sales price (step S104), and then proceeds to step S112.
[0073] At this time, the sales price / sales calculation unit 110 adds an entry to the forecast information 124, setting the year 701, customer code 702, and product code 703 to the next year, target customer code, and target product code. The sales price / sales calculation unit 110 also sets the sales price 706 and wholesale price 707 of the entry to the values of the base price 805 and wholesale price 804 from the price revision information 131. Since there is no sales record, the quantity 704 and sales 705 are left blank. Also, since the adjustment rate is not used, the adjustment rate 708 is left blank.
[0074] If sales records exist, the sales price / sales calculation unit 110 calculates the sales price for the next fiscal year using the sales price for the current fiscal year and the adjustment rate.
[0075] First, the sales price / sales calculation unit 110 changes the sales price for the current year based on the adjustment rate for the product category (step S105). The sales price calculated in step S105 is recorded as the first price.
[0076] For example, if the selling price for the current year is 1000 yen and the adjustment rate is 0.3, the selling price for the current year will be changed as shown in the following formula. 1000 yen × (1 + 0.3) = 1300 yen
[0077] Next, the sales price / sales calculation unit 110 changes the first price based on the adjustment rate of the business type (step S106). The sales price calculated in step S106 is recorded as the second price.
[0078] For example, if the adjustment rate is 0.3, the first price will be changed as shown in the following formula. 1300 yen × (1 + 0.3) = 1690 yen
[0079] Next, the sales price / sales calculation unit 110 changes the second price based on the sales volume adjustment rate (step S107). The sales price calculated in step S107 is recorded as the third price.
[0080] For example, if the adjustment rate is 0, the second price will be changed as shown in the following formula. 1690 yen × (1 + 0) = 1690 yen
[0081] Next, the sales price / sales calculation unit 110 changes the third price based on the adjustment rate of the product management category (step S108). The sales price calculated in step S108 is recorded as the fourth price.
[0082] For example, if the adjustment rate is -0.1, the third price will be changed as shown in the following formula. 1690 yen × (1 - 0.1) = 1521 yen
[0083] Next, the sales price / sales calculation unit 110 changes the fourth price based on the adjustment rate of the sales destination management category (step S109). The sales price calculated in step S109 is recorded as the fifth price.
[0084] For example, if the adjustment rate is 0, the fourth price will be changed as shown in the following formula. 1521 yen × (1 + 0) = 1521 yen
[0085] Next, the sales 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 for drug price revisions is set to -0.1, the fifth price will be changed as shown in the formula below. 1521 yen × (1 - 0.1) = 1368.9 yen
[0087] The sales price / sales calculation unit 110 sets the price calculated in steps S105 to S110 as the sales price (step S111), and then proceeds to step S112.
[0088] At this time, the sales price / sales calculation unit 110 adds an entry to the forecast information 124, setting the year 701, customer CD 702, and product CD 703 to the code for the next year, the code for the target customer, and the code for the target product. The sales price / sales calculation unit 110 sets the value of the transfer price 804 from the price revision information 131 to the transfer price 707 of the entry. The sales price / sales calculation unit 110 sets the calculated price to the sales price 706 of the entry and sets the information of the adjustment rate used to the adjustment rate 708. In addition, the sales price / sales calculation unit 110 sets the value of the actual sales quantity 504 to the quantity 704, and sets the value obtained by multiplying the value of quantity 704 and the value of sales price 706 to sales 705.
[0089] In step S112, the sales price / sales calculation unit 110 determines whether processing has been completed for all customers (step S112). If processing has not been completed for all customers, the sales price / sales calculation unit 110 selects a new customer and returns to step S103.
[0090] If processing is complete for all customers, the sales price / sales calculation unit 110 determines whether processing is complete for all products (step S113). If processing is not complete for all products, the sales price / sales calculation unit 110 selects a new product and returns to step S102.
[0091] Once processing is complete for all products, the sales price / sales calculation unit 110 terminates the process.
[0092] Note that the execution order of steps S105 to S110 may be changed. Also, only a portion of the processes from steps S105 to S110 may be executed.
[0093] Alternatively, the sales price may be calculated using a benchmark price instead of the current year's sales price. In this case, it is conceivable to use surcharges and discounts as indicators instead of adjustment rates.
[0094] Next, we will describe the screens displayed by the pharmaceutical management system 100. Figures 10A, 10B, 10C, 10D, and 10E illustrate an example of a screen displayed by the pharmaceutical management system 100 of Example 1.
[0095] The output unit 112 displays screen 1000. Screen 1000 includes a selection field 1001, a total button 1002, and a display field 1003.
[0096] Selection field 1001 is for selecting the aggregation items. The aggregation items displayed in selection field 1001 are product category, business type, sales volume, product management category, and sales destination management category. Aggregation button 1002 is a button for instructing the aggregation process.
[0097] The user selects an aggregation item from the selection field 1001 and operates the aggregation button 1002. When the aggregation unit 111 of the pharmaceutical management system 100 receives this operation, it aggregates the entries for sales performance information 122 and forecast information 124. The output unit 112 displays the aggregation results in the display field 1003.
[0098] Figure 10A displays the results of aggregating entries based on product category. Figure 10B displays the results of aggregating entries based on business structure. Figure 10C displays the results of aggregating entries based on sales volume. Figure 10D displays the results of aggregating entries based on product management category. Figure 10E displays the results of aggregating entries based on sales destination management category.
[0099] Display area 1003 displays a table containing fields such as sales, quantity, selling price, adjustment rate, and profit margin. The aggregation may be performed for specific products or for all products.
[0100] By presenting projected sales figures for products using various aggregation items in this way, users can understand the calculated sales price as a key business indicator.
[0101] Furthermore, by checking projected sales, users can, for example, see how much the adjustment rates set for each business model affect sales and revise those adjustment rates.
[0102] As explained 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, by considering the characteristics of the customer, such as the type of business, management structure, and sales volume, it is possible to calculate a selling price that ensures profitability and allows for the development of sales channels. [Examples]
[0103] Example 2 differs from Example 1 in that it calculates projected sales.
[0104] The system configuration of Example 2 is the same as that of Example 1. The hardware and software configurations of the pharmaceutical management system 100 in Example 2 are the same as those of Example 1. The data structure of the information other than the prediction information 124 in the pharmaceutical management system 100 in Example 2 is the same as that of Example 1. The prediction information 124 in Example 2 does not include the sales price 706.
[0105] Figure 11 is a flowchart illustrating an example of the process performed by the pharmaceutical management system 100 of Example 2.
[0106] When the pharmaceutical management system 100 receives an execution instruction from terminal 101, it starts the process described below. Here, we describe the process assuming that the number of products sold in the next fiscal year will be the same as the number of products sold in the current fiscal year. Note that the number of products sold in the next fiscal year may be calculated using a publicly known prediction model, or it may be entered by the user.
[0107] The sales price / sales calculation unit 110 starts the product loop processing (step S201). Specifically, the sales price / sales calculation unit 110 selects one entry from the product information 120. Hereafter, the selected product will be referred to as the target product.
[0108] Next, the sales price / sales calculation unit 110 starts the customer loop processing (step S202). Specifically, the sales price / sales calculation unit 110 selects one entry from the customer information 121. Hereafter, the selected customer will be referred to as the target customer.
[0109] Next, the sales price / sales calculation unit 110 refers to the sales performance information 122 and determines whether sales performance is stored in the year 501, customer CD 502, and product CD 503, with the code for the target customer and the code for the target product for the current year (step S203). If no sales performance exists, the sales price / sales calculation unit 110 proceeds to step S211.
[0110] If sales records exist, the sales price / sales calculation unit 110 calculates the projected sales for the next fiscal year using the sales for the current fiscal year and the adjustment rate.
[0111] First, the sales price / sales calculation unit 110 changes the sales for the current year based on the adjustment rate for the product category (step S204). The sales calculated in step S204 are recorded 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 following formula. 1,000,000 yen × (1 + 0.3) = 1,300,000 yen
[0113] Next, the sales price / sales calculation unit 110 changes the first sales based on the adjustment rate of the business type (step S205). The sales calculated in step S205 are recorded as the second sales.
[0114] For example, if the adjustment rate is 0.3, the first sales figure will be changed as shown in the following formula. 1,300,000 yen × (1 + 0.3) = 1,690,000 yen
[0115] Next, the sales price / sales calculation unit 110 modifies the second sales based on the sales scale adjustment rate (step S206). The sales calculated in step S206 are recorded as the third sales.
[0116] For example, if the adjustment rate is 0, the second sales will be changed as shown in the following formula. 1,690,000 yen × (1 + 0) = 1,690,000 yen
[0117] Next, the sales price / sales calculation unit 110 changes the third sales based on the adjustment rate of the product management category (step S207). The sales calculated in step S207 are recorded as the fourth sales.
[0118] For example, if the adjustment rate is -0.1, the third sales figure will be changed as shown in the following formula. 1,690,000 yen × (1 - 0.1) = 1,521,000 yen
[0119] Next, the sales price / sales calculation unit 110 changes the fourth sales based on the adjustment rate of the sales destination management category (step S208). The sales calculated in step S208 are recorded as the fifth sales.
[0120] For example, if the adjustment rate is 0, the fourth sales figure will be changed as shown in the following formula. 1,521,000 yen × (1 - 0) = 1,521,000 yen
[0121] Next, the sales price / sales calculation unit 110 changes the fifth sales figure depending on whether or not the drug price has been revised (step S209).
[0122] For example, if the adjustment rate for drug price revisions is set to -0.1, the fifth sales figure will change as shown in the following formula. 1,521,000 yen × (1 - 0.1) = 1,368,900 yen
[0123] The sales price / sales calculation unit 110 sets the sales calculated in steps S204 to S209 as the forecast sales (step S210), and then proceeds to step S211.
[0124] In step S211, the sales price / sales calculation unit 110 determines whether processing has been completed for all customers (step S211). If processing has not been completed for all customers, the sales price / sales calculation unit 110 selects a new customer and returns to step S203.
[0125] If processing is complete for all customers, the sales price / sales calculation unit 110 determines whether processing is complete for all products (step S212). If processing is not complete for all products, the sales price / sales calculation unit 110 selects a new product and returns to step S202.
[0126] Once processing is complete for all products, the sales price / sales calculation unit 110 calculates the total of the calculated forecast sales (step S213), and then terminates the process.
[0127] Note that the execution order of steps S204 to S209 may be changed. Alternatively, only a portion of the processes from steps S204 to S209 may be executed.
[0128] As explained above, the pharmaceutical management system 100 can calculate projected sales by taking into account the characteristics of the sales destination.
[0129] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. Furthermore, for example, the embodiments described above are detailed explanations of the configuration in order to clearly illustrate the present invention, and are not necessarily limited to those having all the configurations described. In addition, some of the configurations in each embodiment can be added to, deleted from, or replaced with other configurations.
[0130] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, in whole or in part, for example, by designing them as integrated circuits. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.
[0131] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, Python, and Java (registered trademark).
[0132] Furthermore, the program code for the software that implements the functions of the embodiment 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 computer's processor 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 shown are those deemed necessary for explanation and do not necessarily represent all control lines and information lines in the actual product. All components may be interconnected. [Explanation of Symbols]
[0134] 100 Pharmaceutical Management Systems 101 terminals 102 Network 110 Sales Price / Sales Calculation Department 111 Aggregation Department 112 Output section 120 Product information 121 Sales Information 122 Sales Performance Information 123 Adjustment rate information 124 Prediction Information 130 Sales Record 131 Price Revision Information 132 Product Master 133 Sales destination master 200 calculator 201 Processor 202 Main storage 203 Secondary storage device 204 Network Interfaces Bus 205 1000 screens
Claims
1. A computer system, The system comprises a processor, a storage device connected to the processor, and a network interface connected to the processor. The storage device holds sales destination information for managing sales destinations of pharmaceuticals, performance information for managing sales performance of the pharmaceuticals, and adjustment indicator information for managing a first indicator used to adjust the sales price of the pharmaceuticals, which is set based on the characteristics of the sales destinations. The aforementioned customer information contains data including identification information of the customer and information regarding the characteristics of the customer. The aforementioned sales record includes the identification information of the pharmaceutical product, the identification information of the sales destination, and the sales price of the pharmaceutical product. The characteristics of the customer include at least one of the following: the customer's business structure, sales volume, and customer management classification representing the customer's importance to the company selling the pharmaceuticals. The adjustment indicator information stores data that includes at least one of the first indicators, which is the business structure of the customer, the sales volume, and the customer management classification. The aforementioned processor, For each combination of the aforementioned sales destination and the aforementioned pharmaceutical product, the sales performance is obtained. A computer system characterized by obtaining the first index from the adjustment index information based on the customer information for each combination of the customer and the pharmaceutical product, and calculating a new sales price for the pharmaceutical product by changing the sales price of the pharmaceutical product included in the sales performance using the first index.
2. A computer system according to claim 1, The characteristics of the aforementioned customer include the business structure of the customer, the scale of sales, and a customer management classification that indicates the importance of the customer to the company selling the pharmaceuticals. The computer system is characterized in that the adjustment indicator information stores the first indicator for each of the customer's business structure, sales volume, and customer management classification.
3. The computer system according to Claim 2, It holds drug information for managing the aforementioned drug, The aforementioned drug information contains data including identification information of the drug and information regarding the characteristics of the drug. The adjustment index information includes data that includes a second index, which is set based on the characteristics of the pharmaceutical product and is used to adjust the sales price of the pharmaceutical product. The characteristics of the aforementioned pharmaceutical product include the classification of the pharmaceutical product and the product management classification indicating the price management policy of the aforementioned company. The adjustment indicator information stores data including the second indicator for each of the drug classification and product management classification. The computer system is characterized in that the processor obtains the first indicator and the second indicator from the adjustment indicator information based on the customer information and the pharmaceutical information for each combination of customer and pharmaceutical, and calculates a new sales price for the pharmaceutical by changing the sales price of the pharmaceutical included in the sales performance using the first indicator and the second indicator.
4. The computer system according to claim 3, The aforementioned processor, The predictive results, including the identification information of the sales destination, the identification information of the pharmaceutical product, and the new selling price of the pharmaceutical product, are recorded in the storage device. A computer system characterized by which the sales performance and forecast results are aggregated and the aggregated results are output based on any of the following aggregation items: the business structure of the sales destination, the sales volume of the sales destination, the sales destination management category of the sales destination, the pharmaceutical product category, and the pharmaceutical product category.
5. The computer system according to claim 4, The computer system is characterized in that the processor accepts the selection of the aggregation items and provides an interface for displaying the results of the aggregation.
6. A method for calculating the sales price of a pharmaceutical product, which is performed by a computer system, The computer system comprises a processor, a storage device connected to the processor, and a network interface connected to the processor. The storage device holds sales destination information for managing sales destinations of pharmaceuticals, performance information for managing sales performance of the pharmaceuticals, and adjustment indicator information for managing a first indicator used to adjust the sales price of the pharmaceuticals, which is set based on the characteristics of the sales destinations. The aforementioned customer information contains data including identification information of the customer and information regarding the characteristics of the customer. The aforementioned sales record includes the identification information of the pharmaceutical product, the identification information of the sales destination, and the sales price of the pharmaceutical product. The characteristics of the customer include at least one of the following: the customer's business structure, sales volume, and customer management classification representing the customer's importance to the company selling the pharmaceuticals. The adjustment indicator information stores data that includes at least one of the first indicators, which is the business structure of the customer, the sales volume, and the customer management classification. The method for calculating the selling price of the aforementioned pharmaceutical product is: The processor performs the step of acquiring the sales performance for each combination of the customer and the pharmaceutical product, The processor calculates a new selling price for the pharmaceutical product by obtaining a first index from the adjustment index information based on the customer information for each combination of customer and pharmaceutical product, and by changing the selling price of the pharmaceutical product included in the sales performance using the first index. A method for calculating the selling price of a pharmaceutical product, characterized by including [a specific element].
7. A method for calculating the sales price of a pharmaceutical product according to Claim 6, The characteristics of the aforementioned customer include the business structure of the customer, the scale of sales, and a customer management classification that indicates the importance of the customer to the company selling the pharmaceuticals. A method for calculating the sales price of a pharmaceutical product, characterized in that the adjustment indicator information stores the business structure of the sales destination, the sales volume, and the sales destination management classification for each of the aforementioned indicators.
8. A program to be executed by a computer, The computer has a processor, a storage device connected to the processor, and a network interface connected to the processor. The storage device holds sales destination information for managing sales destinations of pharmaceuticals, performance information for managing sales performance of the pharmaceuticals, and adjustment indicator information for managing a first indicator used to adjust the sales price of the pharmaceuticals, which is set based on the characteristics of the sales destinations. The aforementioned customer information contains data including identification information of the customer and information regarding the characteristics of the customer. The aforementioned sales record includes the identification information of the pharmaceutical product, the identification information of the sales destination, and the sales price of the pharmaceutical product. The characteristics of the customer include at least one of the following: the customer's business structure, sales volume, and customer management classification representing the customer's importance to the company selling the pharmaceuticals. The adjustment indicator information stores data that includes at least one of the first indicators, which is the business structure of the customer, the sales volume, and the customer management classification. The aforementioned program, A procedure for obtaining the sales performance for each combination of the aforementioned sales destination and the aforementioned pharmaceutical product, A procedure for calculating a new selling price for a pharmaceutical product by obtaining the first indicator from the adjustment indicator information based on the sales information for each combination of the sales destination and the pharmaceutical product, and by changing the selling price of the pharmaceutical product included in the sales performance using the first indicator. A program characterized by causing the computer to execute the above.
9. The program according to claim 8, The characteristics of the aforementioned customer include the business structure of the customer, the scale of sales, and a customer management classification that indicates the importance of the customer to the company selling the pharmaceuticals. The program is characterized in that the adjustment indicator information stores the respective indicators for the business structure, sales volume, and sales management category of the customer.