Sales activity support device for medical product, sales activity support system, control method of sales activity support device and program

Abstract

To provide a sales activity support device capable of improving efficiency of sales activities for medical products.SOLUTION: A sales activity support device 10 includes: an operation history reception unit 31 that receives an operation history relating to use of a plurality of medical support contents by each doctor from each of a plurality of doctor terminal devices 40 used by the plurality of doctors; a doctor DB 21 that stores a plurality of doctors belonging to a first doctor organization A1 among the plurality of doctors; and an aggregate information calculation unit 32 that aggregates operation histories relating to preselected medical support content, performed by the doctors of the first doctor organization A1 on the basis of the operation histories of the doctors belonging to the first doctor organization A1, and calculates aggregate information on the basis of a result thereof.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present disclosure relates to a sales activity support device, a sales activity support system, a control method for a sales activity support device, and a program for a medical product. [Background technology]

[0002] Patent Document 1 proposes an information provision system for doctors. This system provides doctors with information such as advertisements for pharmaceuticals and seminar information in addition to electronic medical records.

[0003] Furthermore, Patent Document 2 proposes a system that uses a machine learning model to estimate doctors' preferences regarding sources of information about pharmaceuticals (such as pharmaceutical lectures and pharmaceutical websites). Such preference information can be used in the sales activities of pharmaceutical companies. [Prior art documents] [Patent documents]

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

[0005] In the pharmaceutical industry, sales representatives visit doctors at each hospital to explain the effectiveness and price of drugs, etc. However, with so many hospitals, it is unclear when it is most efficient to visit each hospital, and in some cases, sales activities are not always efficient.

[0006] An object of the present disclosure is to provide a sales activity support device, a sales activity support system, a control method for a sales activity support device, and a program for supporting sales activities by sales representatives of medical products. [Means for solving the problem]

[0007] The sales activity support device proposed in the present disclosure includes an operation history receiving means for receiving operation histories relating to the use of a plurality of medical support contents by each of a plurality of medical workers from each of a plurality of terminal devices used by the plurality of medical workers; a medical worker storage means for storing a plurality of medical workers who belong to a first organization among the plurality of medical workers; and a calculation means for aggregating operation histories relating to medical support contents pre-selected from the plurality of medical support contents performed by the plurality of medical workers of the first organization based on the operation histories by the plurality of medical workers belonging to the first organization, and calculating aggregated information based on the results.

[0008] The sales activity support system proposed in the present disclosure includes the sales activity support device, the plurality of terminal devices used by the plurality of medical professionals, and a terminal device that communicates with the sales activity support device and is used by a provider of medical products to be used in the treatment of diseases related to the pre-selected medical support content.

[0009] The program proposed in the present disclosure causes a computer to function as an operation history receiving means that receives operation histories related to the use of multiple medical support contents by multiple medical workers from each of multiple terminal devices used by the multiple medical workers, a medical worker storage means that stores multiple medical workers who belong to a first organization among the multiple medical workers, and a calculation means that compiles operation histories by the multiple medical workers of the first organization related to medical support content pre-selected from the multiple medical support contents based on the operation histories by the multiple medical workers belonging to the first organization and calculates compiled information based on the results.

[0010] The present disclosure proposes a method for controlling a sales activity support device having a medical worker storage means for storing a plurality of medical workers belonging to a first organization among a plurality of medical workers. The control method includes a step of receiving, from a plurality of terminal devices used by the plurality of medical workers, operation histories relating to the use of a plurality of medical support contents by each of the plurality of medical workers, and a step of aggregating operation histories by the plurality of medical workers of the first organization relating to medical support content pre-selected from the plurality of medical support contents based on the operation histories by the plurality of medical workers belonging to the first organization, and calculating aggregate information based on the results of the calculation. [Effects of the Invention]

[0011] According to the sales activity support device, support system, control method, and program proposed in the present disclosure, it is possible to obtain information that will improve the efficiency of sales activities for medical products. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a block diagram showing an example of the overall configuration of a support system. [Figure 2A] FIG. 2 is a block diagram showing hardware of the sales activity support device. [Figure 2B] FIG. 2 is a block diagram showing hardware of the doctor terminal device. [Figure 2C] FIG. 2 is a block diagram showing hardware of a salesperson terminal device. [Figure 3A] FIG. 10 is a diagram showing an example of a home screen displayed on the doctor terminal device. [Figure 3B] FIG. 10 is a diagram showing an example of a screen displaying a list of multiple pieces of medical support information. [Figure 3C] FIG. 10 is a diagram showing an example of a screen displaying medical support information. [Figure 3D] FIG. 10 illustrates an example of a screen displaying a list of multiple medical calculation tools. [Figure 3E] 10 is an example of a screen displayed by a medical calculation tool (calculation program). [Figure 4] FIG. 2 is a block diagram showing the functions of the support system. [Figure 5] FIG. 2 is a diagram illustrating an example of data stored in a doctor database. [Figure 6] FIG. 2 is a diagram illustrating an example of data stored in a doctor organization database. [Figure 7] FIG. 2 is a diagram for explaining an example of data stored in a medical support content database. [Figure 8] FIG. 2 is a diagram for explaining an example of data stored in a medical support content database. [Figure 9A] FIG. 2 is a diagram illustrating a first example of information stored in a tally definition database. [Figure 9B] FIG. 10 is a diagram illustrating a second example of information stored in the tally definition database. [Figure 9C] FIG. 10 is a diagram illustrating a third example of information stored in the tally definition database. [Figure 9D] FIG. 10 is a diagram illustrating a fourth example of information stored in the tally definition database. [Figure 9E] FIG. 10 is a diagram illustrating a fifth example of information stored in the tally definition database. [Figure 9F] FIG. 10 is a diagram illustrating a sixth example of information stored in the tally definition database. [Figure 10] FIG. 10 is a diagram for explaining information output by the sales activity support device. [Figure 11] FIG. 10 is a sequence diagram showing an example of the operation of the support system. [Figure 12] 11 is a flowchart showing an example of processing executed by the sales activity support device, which corresponds to the processing of S107 shown in FIG. [Figure 13A] 12 is a flowchart showing an example of a process executed by the sales activity support device. The process shown in this diagram is executed in S204 of FIG. [Figure 13B]13B is a diagram for explaining information output by the sales activity support device as a result of the processing shown in FIG. 13A. FIG. [Figure 14] 13 is a flowchart showing an example of processing executed by the sales activity support device. The processing shown in this diagram is another example of the processing executed in S204 of FIG. [Figure 15] 13 is a flowchart showing an example of processing executed by the sales activity support device. The processing shown in this diagram is another example of the processing executed in S204 of FIG. [Figure 16] 13 is a flowchart showing an example of processing executed by the sales activity support device. The processing shown in this diagram is another example of the processing executed in S204 of FIG. [Figure 17] 11 is a flowchart showing an example of processing executed by the sales activity support device, which corresponds to the processing of S107 shown in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0013] Below, examples of a sales activity support device and a sales activity support system for medical products proposed in this disclosure will be described. Hereinafter, the "sales activity support system" will be simply referred to as the "support system." Also, the sales activity support device will be referred to as the "support device." Figure 1 is a block diagram showing an example of the overall configuration of the system.

[0014] [System Hardware] As shown in FIG. 1, the support system S includes a support device 10. The support system S also includes a plurality of terminal devices used by a plurality of medical professionals. The medical professionals are typically doctors. In FIG. 1, a doctor terminal device 40 is shown as an example of a terminal device used by a medical professional. The medical professional using the terminal device may be a nurse, a medical technician, or the like.

[0015] An organization may include multiple medical professionals. Here, an "organization" refers to a medical institution or a medical department (e.g., gastroenterology) within a medical institution. Hereinafter, this organization will be referred to as a "doctor organization." FIG. 1 shows a first doctor organization A1 and a second doctor organization A2 as examples of doctor organizations. Also shown are doctor terminal devices 40 for doctors belonging to each doctor organization A1 and A2. In the support system S, the operations of doctors via the doctor terminal devices 40 (use of content provided by the support device 10) are tallied for each doctor organization A1 and A2. The tallied results can be used for sales activities of medical products. Note that the number of members of one doctor organization may be multiple or one.

[0016] The support system S includes a terminal device ("salesperson terminal device 50" in FIG. 1) used by a person who conducts sales activities for medical products. Medical products are typically drugs that are administered to patients. A person who conducts sales activities for medical products is, for example, a pharmaceutical manufacturer or a drug wholesaler. Medical products may also be medical equipment or medicines (such as diagnostic reagents) that are for medical use but are not administered to patients. In this case, a person who conducts sales activities may be a medical equipment manufacturer, a drug manufacturer, or a wholesaler thereof. The support system S may include multiple salesperson terminal devices 50.

[0017] Sales activities are activities for selling medical products. For example, if the medical product is a drug, sales activities are the act of a sales representative from a pharmaceutical manufacturer or wholesaler visiting a medical institution to explain the drug's effectiveness, price, etc. If the medical product is a medical device, sales activities are the act of a sales representative from a device manufacturer or wholesaler visiting a medical institution to explain the medical device's effectiveness, price, etc.

[0018] In the following description, a doctor is taken as an example of a medical professional. A pharmaceutical manufacturer is taken as an example of a person engaged in sales activities. As shown in Fig. 1, the support device 10, the doctor terminal device 40, and the salesperson terminal device 50 can be connected to a network N such as the Internet.

[0019] [Support Device Hardware] The support device 10 is configured, for example, by a server computer. The support device 10 may be configured by a plurality of server computers connected to each other via a network N. The support device 10 may also be configured by one or a plurality of personal computers. As shown in FIG. 2A, the support device 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The support device 10 may also include a display unit 14 and an input unit 15.

[0020] The control unit 11 includes at least one processor. The control unit 11 executes processing in accordance with programs and data stored in the storage unit 12. The storage unit 12 includes a main storage unit and an auxiliary storage unit. For example, the main storage unit is a volatile memory such as RAM (Random Access Memory), and the auxiliary storage unit is a volatile memory such as ROM (Read Only Memory) or EEPROM (Electrically Erasable and Non-volatile memory such as Programmable Read Only Memory, flash memory, or hard disk.

[0021] The storage unit 12 stores content to be provided to the doctor terminal device 40. The content provided to the doctor terminal device 40 is, for example, information that supports medical procedures by doctors. The storage unit 12 stores operation history (e.g., browsing history) by each doctor related to the content. The content provided to the doctor terminal device 40 will be described later.

[0022] The communication unit 13 is a communication interface for wired or wireless communication, and performs data communication via the network N. The display unit 14 is, for example, a liquid crystal display unit or an organic EL display unit. The display unit 14 displays images according to instructions from the control unit 11. The input unit 15 is a pointing device such as a touch panel or a mouse. The input unit 15 may include a keyboard, buttons, etc. The input unit 15 inputs a signal to the control unit 11 in response to an operation by a user.

[0023] [Physician terminal device hardware] The doctor terminal device 40 may be a mobile phone (including a smartphone), a mobile information terminal (including a tablet computer, a wearable device, etc.), a personal computer, etc. As shown in Figure 2B, the doctor terminal device 40 includes a control unit 41, a memory unit 42, a communication unit 43, a display unit 44, an input unit 45, etc.

[0024] The control unit 41 executes processing in accordance with programs and data stored in the memory unit 42. The memory unit 42 includes a volatile memory and a non-volatile memory, similar to the memory unit 12 of the support device 10. The communication unit 43 is a communication interface for wired or wireless communication, and performs data communication via the network N. The display unit 44 is, for example, a liquid crystal display unit or an organic EL display unit. The display unit 44 displays images in accordance with instructions from the control unit 41. The input unit 45 is a pointing device such as a touch panel or a mouse. The input unit 45 may include a keyboard, buttons, etc. The input unit 45 inputs signals to the control unit 41 in accordance with operations by the user.

[0025] [Hardware for business terminal equipment] The salesperson terminal device 50 is, for example, a personal computer. The salesperson terminal device 50 may also be a mobile phone (including a smartphone) or a personal digital assistant (including a tablet computer or a wearable device). As shown in FIG. 2C , the salesperson terminal device 50 includes a control unit 51, a memory unit 52, a communication unit 53, a display unit 54, an input unit 55, and the like. The physical configurations of the control unit 51, the memory unit 52, the communication unit 53, the display unit 54, and the input unit 55 may be similar to those of the control unit 41, the memory unit 42, the communication unit 43, the display unit 44, and the input unit 45, respectively.

[0026] [Screen displayed on doctor's terminal] 3A to 3E show examples of screens displayed on the display unit 44 of the doctor terminal device 40. These screens are displayed, for example, by the control unit 41 executing application software (hereinafter referred to as "medical support software") installed in the doctor terminal device 40. The medical support software may be transmitted to the doctor terminal device 40, for example, from the support device 10 or a server provided separately from the support device 10, via the network N.

[0027] Alternatively, the screens illustrated in Figures 3A to 3E may be displayed by the doctor terminal device 40 accessing the support device 10 through a web browser installed on the doctor terminal device 40. Note that these screen configurations are merely examples and may be changed as appropriate.

[0028] 3A is an example of a home screen of the medical support software or the service provided through a web browser. The home screen is, for example, the screen that is first displayed when a doctor starts up the medical support software. The home screen may also be the screen that is first displayed (first provided by the support device 10) when the doctor terminal device 40 accesses the support device 10 through a web browser.

[0029] 3A, for example, a timeline area R101 may be provided on the home screen. For example, the timeline area R101 may display titles 101a to 101e of content provided by the support device 10. The content titles 101a to 101e may be displayed in chronological order in the timeline area R101.

[0030] The content (hereinafter referred to as "medical support content") delivered from the support device 10 to the doctor terminal device 40 includes various information for supporting medical services. The medical support content includes, for example, medical treatment support information. The medical treatment support information is document information that supports medical treatment by doctors, and may be a manual that defines treatment methods (treatment manual), a manual that defines treatment methods, medical guidelines that indicate recommended treatment methods, a table that indicates medical treatment standards, etc. The treatment manual includes a regimen that describes the type of drug to be administered to the patient and the treatment plan (dosage, usage, frequency of administration, etc.).

[0031] The medical support content may also include medical articles. The medical articles may be, for example, explanatory or introductory articles about diseases or medications, medical papers, etc. The medical support content may also include medical calculation tools. Medical calculation tools will be described in detail later.

[0032] The home screen (see FIG. 3A) may include a search box R105 for searching for medical support content, menu areas R120 and R130 with buttons for moving to other screens, etc. The menu area R120 may include, for example, a medical article button 121, a medical support information button 122, and a medical calculation tool button 123.

[0033] A doctor (user) may be able to bookmark medical support information, medical calculation tools, and the like that interest him or her. The menu area R130 may include a bookmark list button 132. When the bookmark list button 132 is selected (tapped), a list of content that has been bookmarked by the user (doctor) in the past may be displayed. The menu area R130 may also include a notification button 133. When the notification button 133 is selected (tapped), a notification (e.g., update information for medical support software) delivered from the support device 10 to the doctor terminal device 40 may be displayed.

[0034] [Medical support information screen] When the user selects (tap) buttons 121, 122, and 123 on the home screen (see FIG. 3A), a list listing, for example, the names and summaries of medical support content is displayed. When the user selects one of the multiple displayed medical support content, the details of the selected medical support content are displayed.

[0035] Fig. 3B is a diagram showing an example of a screen displayed when the medical support information button 122 is selected. Hereinafter, this screen will be referred to as the "medical support information list screen." The medical support information list screen 200 includes a list area R205 in which multiple pieces of medical support information are listed. In the example shown in Fig. 3B, names 205a to 205d of medical support information are listed in the list area R205.

[0036] As shown in FIG. 3B, the medical support information list screen 200 may include classification selection areas R203 and R204 that display the names of medical classifications. Medical support content is classified according to medical classifications such as diseases and medical departments related to the content. In the classification selection area R203, for example, medical department names (symbol 203a) may be listed as names of medical classifications. In addition, in the classification selection area R204, names of diseases (symbol 204a) may be listed as names of medical classifications.

[0037] When any medical department name is selected in the category selection area R203, the diseases handled by that medical department are displayed in the category selection area R204. Then, when the user selects any of the diseases displayed in the category selection area R204, medical support information applicable to that disease is listed in the list area R205. In the example shown in FIG. 3B, "digestive system" is selected in the category selection area R203, and diseases handled by the gastroenterology department are listed in the category selection area R204. Then, "AAA disease" is selected in the category selection area R204, and names 205a to 205e of medical support information (more specifically, regimens) applicable to "AAA disease" are listed in the list area R205. When the user selects (tap) any of the medical support information, the selected medical support information is displayed.

[0038] FIG. 3C is a diagram showing an example of a screen displaying medical support information. Hereinafter, this screen will be referred to as a "medical support information presentation screen." As shown in FIG. 3C, an example of the medical support information presentation screen 210 displays a treatment manual (specifically, a regimen). That is, the medical support information presentation screen 210 displays, for example, the name 211 of a drug to be administered to a patient and a dosing plan field 212. The dosing plan field 212 may include, for example, a drug dosage 212a, a period 212b, and dosing dates for each period 212c.

[0039] 3B, among the plurality of pieces of medical support information listed in the list region R205, the BBB therapy 205a may be a primary treatment regimen (a treatment plan first applied to a patient), and the other treatments 205b to 205d may be secondary treatment regimens selectively applied when the effect of the BBB therapy 205a is small or when the effect of the BBB therapy 205a decreases.

[0040] [Medical calculation tool screen] As described above, the medical support content includes a medical calculation tool. The medical calculation tool is a program that calculates information related to a patient's disease. This program accepts input of patient information at a medical professional's terminal device (doctor terminal device 40 in FIG. 1) and calculates information related to the patient's disease based on the patient information. The input patient information is information related to the patient's condition and may include, for example, the patient's test results, age, weight, height, and gender. The calculated information related to the patient's disease may include the severity, an assessment value of the risk caused by the disease or treatment, and the amount of medication to be administered. The patient information does not need to include information that identifies the individual patient, such as the patient's name. Furthermore, the calculated information related to the patient's disease does not need to be associated with the individual patient.

[0041] Figure 3D is an example of a screen that displays a list of medical calculation tools. This screen is displayed by selecting (tapping) the calculation tool button 123 shown in Figure 3A. Hereinafter, this screen will be referred to as the medical calculation tool list screen.

[0042] As shown in FIG. 3D, the medical calculation tool list screen 300 has a list area R301. The list area R301 may display titles 301a to 301f of multiple medical calculation tools (e.g., names of evaluation values calculated by the medical calculation tools). The tool list screen may also be provided with a classification selection area R303 that displays the name of a medical classification. The classification selection area R303 displays the name of a medical department (reference symbol 303a) or disease name (reference symbol 303b) as the name of the medical classification. When the name of any medical classification is selected by the user, medical calculation tools related to that medical classification may be displayed in the list area R301.

[0043] Figure 3E is an example of a screen that the medical calculation tool displays on the display unit 44 of the doctor terminal device 40. Hereinafter, this screen will be referred to as the "medical calculation tool screen." For example, the input screen of a medical calculation tool selected on the medical calculation tool list screen 300 is displayed as shown in Figure 3E.

[0044] The medical calculation tool screen 310 has input fields R311 to R315 for inputting patient information. As described above, the patient information includes, for example, the patient's test results, gender, age, height, and weight. The medical calculation tool screen 310 has a result output field R317. The result output field R317 displays the results calculated by the medical calculation tool based on the input patient information. As described above, the calculation results may be, for example, the severity of the disease, an evaluation value of the risk caused by the disease or treatment, the amount of medication to be administered, etc.

[0045] 3C and 3E, each medical support content may be associated with a bookmark button 202 / 302. When a bookmark button 202 / 302 is selected (tapped) by a doctor, the medical support content corresponding to the bookmark button 202 / 302 is registered in a bookmark list. The content registered in the bookmark list in this way may be displayed in a list by, for example, selecting (tapping) the bookmark list button 132 shown in FIG. 3A.

[0046] The screen transition when the medical article button 121 shown in FIG. 3A is selected (tapped) may be similar to the examples shown in FIGS. 3B and 3C. That is, when the medical article button 121 is selected (tapped), a list of titles or summaries of medical articles may be displayed. Then, when the user selects one of the displayed medical articles, the content of the selected medical article is displayed. As described above, medical articles include, for example, explanatory articles and introductory articles about diseases and drugs, medical papers, and the like.

[0047] [Support system functions] 4 is a block diagram showing an example of functions realized by the support system S. The functions realized by each of the support device 10, the doctor terminal device 40, and the salesperson terminal device 50 will be described below.

[0048] The support device 10 has, as one of its functions, a data storage unit 20. The data storage unit 20 is realized by the control unit 11 operating according to a program and storing data in the storage unit 12. The data storage unit 20 has, for example, a doctor database 21, a doctor organization database 22, a medical support content database 23, an operation history database 24, and a tally definition database 25.

[0049] The support device 10 also includes, as its functions, an operation history receiving unit 31, an aggregate information calculating unit 32, a doctor tissue classifying unit 33, and a classification result transmitting unit 34. These functions are realized, for example, by the control unit 11 operating in accordance with a program stored in the storage unit 12 and controlling the communication unit 13 and the like.

[0050] Some of these functions (including the database function) may be executed by the doctor terminal device 40 or the salesperson terminal device 50. These functions may be realized by cooperation between the doctor terminal device 40 or the salesperson terminal device 50 and the support device 10.

[0051] [Doctor database] The doctor database (DB) 21 stores information about doctors who are users of the doctor terminal device 40. FIG. 5 is a diagram illustrating an example of data stored in the doctor DB 21. The doctor DB 21 may include, for example, identification information (doctor ID) for identifying each doctor, the doctor's name, and doctor attribute information. The doctor's attribute information includes organization information. In the example shown in FIG. 5, the doctor's attribute information includes the name of the medical institution to which the doctor belongs as an item of organization information. The doctor's attribute information may also include, as an item of organization information, the department within the medical institution and the location of the medical institution. The doctor's attribute information may also include items such as medical experience and the doctor's specialty (organ name or disease name). The doctor's attribute information may include the doctor's position within the medical institution instead of or in addition to the medical experience.

[0052] In the doctor DB21, multiple doctors may be associated with the same organization information. In the example shown in FIG. 5, three doctors assigned with "ID: K001 to K003" are associated with "ABC Hospital, Gastroenterology Department, Shinjuku Ward, Tokyo." This means that the doctors with "ID: K001 to K003" belong to the same doctor organization. Furthermore, the doctors with "ID: K011 to K013" are associated with "DEF Hospital, Gastroenterology Department, Minato Ward, Tokyo," and these doctors also belong to the same doctor organization. Note that the doctor DB21 is not limited to the example shown in FIG. 5. For example, the doctor DB21 does not necessarily have to include medical departments, locations, medical experience, or specialties.

[0053] The doctor DB 21 may be generated, for example, based on information input by each doctor to the doctor terminal device 40. That is, the support device 10 receives the attribute information input by each doctor to the doctor terminal device 40, and the attribute information is stored in the storage unit 12, thereby generating the doctor DB 21.

[0054] [Physician Organization Database] The doctor organization database (DB) 22 stores information about medical institutions to which multiple doctors who are users of the medical support software belong. FIG. 6 is a diagram illustrating an example of data stored in the doctor organization DB 22. In the doctor organization DB 22, for example, attribute information of a doctor organization is associated with identification information (doctor organization ID) for identifying each doctor organization. The attribute information of a doctor organization is typically the name of the medical institution. The attribute information of a doctor organization may also include the medical department within the medical institution, the location of the medical institution, etc.

[0055] The doctor organization DB 22 may be generated by the control unit 11, for example, using data stored in the doctor DB 21. That is, the control unit 11 may refer to the organization information of each doctor stored in the doctor DB 21 and extract the organization (doctor organization) to which the doctor belongs. Then, the control unit 11 may assign a doctor organization ID to each doctor organization and use this as the doctor organization DB 22.

[0056] Alternatively, the doctor organization DB 22 may be generated based on information (such as the name of a medical institution) input by an administrator of the support device 10 to the support device 10. The doctor organization DB 22 may be generated based on information (such as the name of a medical institution) input by a user of the salesperson terminal device 50 to the salesperson terminal device 50.

[0057] [Medical Support Content Database] The medical support content database (DB) 23 is a database in which attributes of medical support content are stored. FIG. 7 is a diagram illustrating an example of data stored in the medical support content DB 23. As shown in this diagram, in the medical support content DB 23, identification information (content ID) assigned to each medical support content may be associated with a content type. As described above, the medical support content includes clinical support information such as treatment manuals and medical guidelines (see FIGS. 3B and 3C), medical articles such as drug commentaries, and medical calculation tools (see FIGS. 3D and 3E). The medical support content DB 23 may store such content types (diagnosis support information, medical articles, or medical calculation tools) in association with content IDs. Furthermore, the items in the medical support content DB 23 may include the names of the medical departments that use the medical support content and the names of diseases to which the medical support content can be applied.

[0058] Furthermore, the medical support content DB23 may include application priority as one of its items. The clinical support information includes a treatment manual to be initially applied to a patient (primary treatment regimen, application priority: 1). The clinical support information also includes a treatment manual to be applied when the primary treatment is not very effective or when the effectiveness of the primary treatment has decreased (secondary treatment regimen, application priority: 2). As shown in Fig. 7, in the medical support content DB23, this application priority may be recorded in association with a content ID.

[0059] The medical support content DB23 may include the title of the medical support content as one of its items. The medical support content DB23 may also include related keywords as one of its items. The related keywords are terms related to each medical support content (for example, the names of applicable drugs or related disease names). A search box R105 (see FIG. 3A) is displayed on the doctor terminal device 40. When a related keyword is entered in the search box R105, medical support information associated with the related keyword is searched for and displayed.

[0060] 7, "GHI drug" and "JKP drug" are associated as related keywords with the medical support information of "ID: M021." Therefore, when "GHI drug" or "JKP drug" is entered in the search box R105, the medical support information of "ID: M021" is displayed on the display unit 44 of the doctor terminal device 40 as a search result.

[0061] The medical support content may be transmitted from the support device 10 to the doctor terminal device 40, for example, when the medical support software is installed on the doctor terminal device 40 or when the medical support software is upgraded. Alternatively, the medical support content may be transmitted from the support device 10 to the doctor terminal device 40 when the web browser of the doctor terminal device 40 accesses the support device 10. The doctor terminal device 40 stores the received medical support content in the storage unit 42 (see FIG. 2B). When the medical support software is installed on the doctor terminal device 40, the search process using the related keywords described above may be executed by the doctor terminal device 40. Furthermore, when the web browser of the doctor terminal device 40 accesses the support device 10, this search process may be executed by the support device 10.

[0062] [Operation history receiver] The operation history receiving unit 31 receives a history of operations related to the use of medical support content by each doctor from multiple doctor terminal devices 40 used by the multiple doctors. An example of an operation related to the use of medical support content is the doctor's viewing of medical support information. More specifically, an operation related to the use of medical support content may be, for example, an operation to select (tap) any medical support information on the medical support information list screen 200 of FIG. 3B, or an operation to close the medical support information presentation screen 210 of FIG. 3C. The history (operation history) received from the doctor terminal device 40 may include information identifying the viewed medical support information (e.g., content ID) and the viewing time of the medical support information (the start time and / or end time of viewing).

[0063] Furthermore, operations related to the use of medical support content include the use of a medical calculation tool by a doctor. Specifically, the use of a medical calculation tool is the operation of inputting patient information into the medical calculation tool screen 310 (see FIG. 3E) and obtaining calculation results. Operations related to the medical calculation tool are not limited to this, and may also include the operation of opening the medical calculation tool screen 310 (i.e., accessing the medical calculation tool).

[0064] In this case, the operation history received from the doctor terminal device 40 may include, for example, information identifying the medical calculation tool (e.g., content ID) and the operation time of the medical calculation tool. The operation time may include, for example, the start time of use of the medical calculation tool (the time the medical calculation tool screen 310 was opened) and / or the end time of use (the time the medical calculation tool screen 310 was closed). The operation history may also include the calculation results of the medical calculation tool and / or the input information to the medical calculation tool (patient information entered in the input fields R311 to R315 of the medical calculation tool screen 310).

[0065] An operation related to the use of medical support content may be a doctor's viewing of a medical article. In this case, the operation history received from the doctor terminal device 40 may include identification information (content ID) that identifies the medical article and the time at which it was selected (tapped). The operation history may include the content ID that identifies the medical article and the viewing time of the medical article. The viewing time may include, for example, the start time and end time of viewing the medical article.

[0066] Furthermore, the operation related to the use of medical support content may be a search for medical support content using related keywords (see FIG. 7). In this case, the operation history received from the doctor terminal device 40 may include the related keywords entered in the search box R105 (see FIG. 3A), the time the search was performed, the content ID of the medical support content that was found, etc.

[0067] Furthermore, the operation related to the use of medical support content may be an operation for registering the medical support content in the bookmark list (tapping the bookmark buttons 202 and 203). For example, the operation history received from the doctor terminal device 40 may include the content ID of the medical support content registered in the bookmark list and the time when the registration operation was performed.

[0068] [Operation history database] The operation history received by the operation history receiving unit 31 is accumulated in the operation history database (DB) 24. The operation history DB 24 may store the operation history for each of a plurality of doctors. Fig. 8 is a diagram for explaining an example of an operation history table provided for each doctor.

[0069] As shown in FIG. 8, the operation history table may include, as its fields, the operation content and the content ID of the medical support content that was the target of the operation. The operation content may include, for example, viewing medical support information, using a medical calculation tool, viewing a drug article, searching by related keyword, and registering in a bookmark list. The operation history table may also include, as its fields, the content type (distinguishing between medical support information, medical calculation tool, and medical article), the start date and time of the operation, and the end date and time of the operation. The start date and time of the operation may be the start date and time of viewing the medical support information, the start date and time of using the medical calculation tool, the search date and time, the date and time of registration in a bookmark list, etc. The end date and time of the operation may be the end date and time of viewing the medical support information.

[0070] The operation history table may include input information and output information. The input information may be patient information entered in the input fields R311 to R315 of the medical calculation tool screen 310, and the output information may be the calculation results of the medical calculation tool.

[0071] When a search operation using a related keyword is performed, "search" may be recorded as the operation content, and the related keyword ("GHI drug" in FIG. 8) may be recorded as input information. In addition, the content ID of the medical support content found by the search ("M021" in FIG. 8) may be recorded as output information.

[0072] For example, when the doctor terminal device 40 and the support device 10 are connected via the network N, the operation history receiving unit 31 (see FIG. 4) receives the operation history from the doctor terminal device 40 each time a doctor performs an operation. On the other hand, when an operation is performed while the doctor terminal device 40 and the support device 10 are not connected, the operation history may be stored in the memory unit 42 of the doctor terminal device 40. Then, the next time the doctor terminal device 40 connects to the support device 10, the operation history receiving unit 31 may receive the operation history stored in the memory unit 42 from the doctor terminal device 40. As a result, the operation history table records the history of operations performed when the doctor terminal device 40 and the support device 10 are not connected (so-called offline).

[0073] [Aggregate Information Calculation Department] The aggregated information calculation unit 32 refers to the operation history recorded in the operation history DB 24, aggregates the operation history related to the preselected medical support content, and calculates aggregated information based on the results. This aggregation is performed for each doctor organization to which one or more doctors belong.

[0074] In the example shown in FIG. 1, each of the first doctor organization A1 and the second doctor organization A2 is composed of a plurality of doctors. In the support device 10, one or more medical support contents are pre-selected as aggregation target contents from among a plurality of medical support contents stored in the medical support content DB 23. The aggregated information calculation unit 32 aggregates the operation history (e.g., the number of views) of doctors belonging to the first doctor organization for the aggregation target contents. The aggregated information calculation unit 32 also aggregates the operation history of doctors belonging to the second doctor organization. That is, the aggregated information calculation unit 32 aggregates the operation history of doctors belonging to the same doctor organization. Then, the aggregated information calculation unit 32 calculates aggregated information for each doctor organization based on the aggregation result (e.g., the total number of views).

[0075] [Content to be aggregated] The content to be counted is, for example, content related to diseases to which medical products (e.g., medicines) related to the sales activities of the user (salesperson) of the salesperson terminal device 50 can be applied. For example, if the medical product is a medicine that can be applied to AAA diseases, the content to be counted is one or more of medical support contents that may be used in the treatment of AAA diseases (in FIG. 7, medical support information M021 to M024, medical calculation tools C011 to C013, and medical article A008).

[0076] The operations to be counted (operations related to the content to be counted) may be the same as the operations related to the medical support content described above. For example, if the content to be counted is medical support information, the operations related to the content to be counted may be viewing it, searching for related keywords, registering it in a bookmark list, etc. Furthermore, if the content to be counted is a medical calculation tool, the operations related to the medical calculation tool may be using the medical calculation tool, searching for this tool using related keywords, registering it in a bookmark list, etc.

[0077] [Aggregate information] The aggregate information calculated by the aggregate information calculation unit 32 is a value representing the degree of use of the content to be aggregated within a doctor organization. For example, the aggregate information may be information representing use by multiple doctors belonging to the doctor organization (total use information, specifically, total use time or total number of uses, etc.). For example, if the content to be aggregated is medical support information, the aggregate information may be the total number of views or total view time. Also, if the content to be aggregated is a medical calculation tool, the aggregate information may be the total number of uses. Note that the information representing use by multiple doctors belonging to the doctor organization may be the average number of uses or the average use time.

[0078] When a content is frequently used by multiple doctors (when the total usage time or total usage count is large), it can be assumed that the doctor organization is highly likely to have patients with diseases related to the content to be counted. In other words, it can be assumed that the doctor organization is highly likely to have patients who can be treated with medical products related to the sales activities of the user of the salesperson terminal device 50. Therefore, sales activities to such doctor organizations can be expected to be highly effective.

[0079] Furthermore, the aggregated information calculated by the aggregated information calculation unit 32 may be calculated based on the number of doctors who belong to the same doctor organization and who have used the content to be aggregated. Here, the number of doctors may be the actual number of people who have used the content to be aggregated. If the actual number is large, it can be assumed that the doctor organization has patients with the disease related to the content to be aggregated, and that the doctor organization is also large in size. Therefore, sales activities to such doctor organizations can be expected to be highly effective. Note that the number of doctors may also be the total number of people who have used the content to be aggregated.

[0080] Furthermore, the medical support software installed on the doctor terminal device 40 may provide multiple medical support contents for the treatment of one disease. These multiple medical support contents may be pre-selected as content to be aggregated. In this case, the aggregated information may be the number (number of types) of medical support contents used within the same doctor organization among the multiple medical support contents. Referring to the medical support content DB23 illustrated in FIG. 7, four pieces of medical support information (content IDs: M021 to M024) are provided for the treatment of AAA diseases. The aggregated information may be the number of types of medical support information among these four pieces of medical support information that are viewed within the same doctor organization. A large number of types of medical support information (e.g., regimens) being viewed indicates a high probability that various treatment methods are being considered for patients with AAA diseases within the doctor organization. Therefore, sales activities to such doctor organizations can be expected to be highly effective.

[0081] [Collection period] The aggregated information calculation unit 32 may calculate the aggregated information by referring to the operation history for a predetermined period (aggregation period). For example, the aggregated information calculation unit 32 may calculate the aggregated information based on the operation history for one week. This process may be repeatedly executed. For example, when the first week of a certain month has passed, the aggregated information calculation unit 32 may calculate the aggregated information based on the aggregation history for the first week, and when the second week has passed, the aggregated information calculation unit 32 may calculate the aggregated information based on the aggregation history for the second week. The aggregated information calculation unit 32 may also calculate the aggregated information based on the operation history for one month. The aggregated information calculation unit 32 may also repeatedly execute this process. This allows the salesperson terminal device 50 to grasp the status of each doctor organization in a timely manner.

[0082] [Aggregation definition database] The tally definition database (DB) 25 stores information that defines the tallying process performed by the tally information calculation unit 32. FIGS. 9A to 9F are diagrams for explaining examples of information stored in the tally definition DB 25. FIG.

[0083] As shown in FIG. 9A, the tally definition DB 25 may include, as its items, identification information (tally process ID) for identifying the tally process and an operation to be tallyed. The operation to be tallyed is an operation that the tally information calculation unit 32 tally by referring to the operation history DB 24 (see FIG. 8). The operation to be tallyed may be defined by the content to be tallyed described above and the operation details therefor. For example, as shown in FIG. 9A, the operation to be tallyed may be a browsing operation of medical support information (in FIG. 9A, medical support information with "content ID: M021"). In this case, "content ID: M021" is the content to be tallyed, and the browsing operation is the operation to be tallyed.

[0084] Furthermore, the tally definition DB 25 may include the number of tally targets as one of its items. The number of tally targets is the number tallying performed by the tally information calculation unit 32. The number of tally targets may be, for example, the number of doctors who viewed the medical support information (in FIG. 9A, the medical support information with content ID: M021). The number of tally targets may also be the total viewing time or the total number of views. By utilizing the results of the tallying process defined in this way, the sales activities of the user of the salesperson terminal device 50 can be made more efficient.

[0085] 9A, the tally definition DB 25 may include a related drug ID as one of its items. The related drug ID may be an ID that identifies a drug that is a medical product of the user (salesperson) of the salesperson terminal device 50. The content to be tally ("content ID: M021" in FIG. 9A) is content used in the treatment of a disease to which the drug identified by this related drug ID is applicable. Note that the tally definition DB 25 may include, as one of its items, identification information that identifies the user of the salesperson terminal device 50, instead of or in addition to the related drug ID.

[0086] 9A, the tally definition DB 25 may include an tally period as one of its items. The tally information calculation unit 32 may refer to the operation history within the period defined here and perform the calculation process of the tally information.

[0087] [Example of aggregating the browsing history of multiple medical support information] The operation to be counted may be to view any one of a plurality of pieces of medical support information (content to be counted) selected in advance. For example, as shown in Fig. 9B, the operation to be counted may be to view any one of the pieces of medical support information with "content ID: M022, M023". The plurality of pieces of medical support information selected as content to be counted may be support information that can be used in the treatment of a common disease.

[0088] In this case, the number of targets may be, for example, the total number of views or the total viewing time by multiple doctors belonging to the same doctor organization, or the number of doctors belonging to the same doctor organization who have viewed at least one piece of medical support information.

[0089] By utilizing the results of the aggregation process defined in this manner, the sales activities of the user of the salesperson terminal device 50 can be made more efficient. For example, assume that drugs X1, X2, and X3 are used in three pieces of medical support information (treatment manuals) with content IDs M022, M023, and M024. In this case, it is estimated that in a doctor organization where two pieces of medical support information (content IDs M022 and M023) are frequently viewed, there is also a high demand for drug X3, which is used in the third piece of medical support information (content ID M024). The user of the salesperson terminal device 50 can make sales activities more efficient by conducting sales activities regarding drug X3 to this doctor organization.

[0090] Unlike the description here, the operation to be counted may be the viewing of all of a plurality of pieces of medical support information (contents to be counted) selected in advance. For example, the number of doctors who viewed all of a plurality of pieces of medical support information may be counted.

[0091] The number of items to be counted may be the number of types of medical support information viewed within the same doctor organization among multiple pre-selected pieces of medical support information (contents to be counted). For example, as shown in Fig. 9C, the operation to be counted may be viewing any of the three pieces of medical support information with "content ID: M022 to M024". The number of items to be counted may be the number of types (0, 1, 2, or 3) of medical support information viewed within the same doctor organization among these three pieces of medical support information.

[0092] As explained with reference to Fig. 7, medical support content is assigned an application priority. In the medical support content DB23 illustrated in Fig. 7, the medical support information with "content ID: M021" is assigned an "application priority: 1," while the medical support information with "content IDs: M022 to M024" is assigned an "application priority: 2." As shown in Fig. 9C, the content to be counted may be medical support information assigned an "application priority: 1" and medical support information assigned an "application priority: 2." The number of items to be counted may be the number of types of medical support information viewed within the same doctor organization.

[0093] By setting the operations to be counted in this manner, sales activities by the user of the salesperson terminal device 50 can be made more efficient. For example, assume that drugs X1 to X4 are used in four pieces of medical support information (treatment manuals) with "content IDs: M021 to M024." In this case, it is estimated that a doctor organization viewing three of these four pieces of medical support information also has a need for the drug used in the fourth piece of medical support information. The user of the salesperson terminal device 50 can make sales activities more efficient by conducting sales activities toward this doctor organization.

[0094] [Example of aggregating search operation history] The operations to be counted may be search operations using related keywords associated with pre-selected medical support information (content to be counted). For example, as shown in FIG. 9D, the operations to be counted may be search operations using related keywords (GHI drugs or JKL drugs, see FIG. 7) associated with medical support information with "content ID: M021." In this case, the number of items to be counted may be, for example, the number of doctors who were searched among multiple doctors belonging to the same doctor organization. Alternatively, the number of items to be counted may be the total number of searches by multiple doctors belonging to the same doctor organization.

[0095] [Example of aggregating the use of calculation tools] The medical support content includes medical calculation tools in addition to medical support information. The operations to be counted may be viewing pre-selected medical support information and using pre-selected medical calculation tools. For example, as shown in FIG. 9E, the operations to be counted may be viewing medical support information with "content ID: M021" and using a medical calculation tool with "content ID: C011." In this case, the number to be counted may be the number of doctors who performed these two operations among doctors belonging to the same doctor organization.

[0096] 9E, the operation to be counted may be at least one of viewing preselected medical support information and using a preselected medical calculation tool. In this case, the number to be counted may be, for example, the number of doctors who performed either of these two operations.

[0097] As yet another example, the operation to be counted may be the use of a preselected medical calculation tool, and the number of counted items may be the number of times a preset calculation result is output or the number of doctors who have output the preset calculation result. For example, as shown in FIG. 9F, the operation to be counted may be the use of a medical calculation tool with "Content ID: C011," and the number of counted items may be the number of times "Calculation result: Severe" is calculated within the same doctor organization. If the number of counted items is large, it can be concluded that the doctor organization is likely to have patients with diseases for which this medical calculation tool is applicable. Therefore, sales activities targeting such doctor organizations can be expected to be highly effective.

[0098] The target operation defined in the counting definition DB 25 may be a registration operation to a bookmark list of medical support content selected as the target content, and the number of targets may be the number of doctors who performed the registration operation within the same doctor organization.

[0099] [Example of integrating the results of multiple aggregation processes] The aggregated information calculation unit 32 may execute a plurality of aggregation processes and calculate, as the aggregated information, a value obtained by integrating the aggregation results of the processes. FIG. 10 is a diagram for explaining information output by the support device 10. As shown in FIG. 10, for example, the aggregated information calculation unit 32 may calculate a first score based on the aggregation results obtained by the first aggregation process, and calculate a second score based on the aggregation results obtained by the second aggregation process. Then, the aggregated information calculation unit 32 may calculate, as the aggregated information, an integrated score obtained based on the first score and the second score.

[0100] The first tallying process may be, for example, one of the tallying processes exemplified in Figures 9A to 9F, and the second tallying process may be, for example, another tallying process exemplified in Figures 9A to 9F. For example, the first tallying process may be the tallying process shown in the tallying definition DB25 in Figure 9C (calculating the number of types of medical support information viewed), and the second tallying process may be, for example, the tallying process shown in Figure 9D (calculating the number of searches using related keywords).

[0101] The aggregated information calculation unit 32 may multiply the aggregation result of the first aggregation process by a coefficient ("coefficient: 20" in the example of FIG. 10) and set the result as the first score. The aggregated information calculation unit 32 may also multiply the aggregation result of the second aggregation process by a coefficient ("coefficient: 5" in the example of FIG. 10) and set the result as the second score. Then, the aggregated information calculation unit 32 may calculate an integrated score (for example, the sum of the first score and the second score) obtained based on the first score and the second score as aggregated information.

[0102] [Physician Organization Classification Department] The doctor organization classification unit 33 classifies each doctor organization into one of a plurality of preset categories based on the aggregated information calculated for the plurality of doctor organizations. The plurality of categories may be categories indicating the priority of targets for sales activities, for example. For example, the first category is the highest priority category, the second category is the second highest priority category, and the third category is the third highest priority category. In other words, the doctor organization classification unit 33 assigns an evaluation level to each doctor organization according to the aggregated information. The number of preset categories (the number of preset levels) is not limited to three, but may be two, four or more.

[0103] The doctor tissue classification unit 33 may classify each doctor tissue into one of a plurality of categories according to a preset criterion. The preset criterion may be, for example, a threshold value for the aggregated information. The doctor tissue classification unit 33 may compare one or more threshold values with the value indicated in the aggregated information and classify each doctor tissue into one of the categories based on the comparison result. For example, the doctor tissue classification unit 33 may classify a doctor tissue into a category with a higher priority as the value indicated in the aggregated information increases.

[0104] Here, the "value indicated by the aggregate information" refers to the number of doctors, the total usage time, the total number of usages, etc. calculated by the aggregate information calculation unit 32. Furthermore, the "value indicated by the aggregate information" may be the number of types of content (the number of types of medical support information) that are viewed and used within one doctor organization from among multiple medical support contents (e.g., medical support information) that have been selected in advance as content to be aggregated.

[0105] Furthermore, the "value indicated by the aggregate information" may be the integrated score described with reference to Figure 10. In the example of Figure 10, ABC Hospital has a relatively high integrated score, so the hospital is classified into the first category ("A" in Figure 10). DEF Hospital and GHI Hospital are classified into the second category ("B" in Figure 10).

[0106] [Classification result transmission section] The classification result transmission unit 34 transmits the results of the processing by the doctor organization classification unit 33 to the salesperson terminal device 50. This transmission may be performed periodically or in response to a request from the salesperson terminal device 50. The results of the processing by the doctor organization classification unit 33 may be displayed on the display unit 54 of the salesperson terminal device 50. By displaying the classification results on the display unit 54 of the salesperson terminal device 50 in this manner, the user of the salesperson terminal device 50 can easily grasp the doctor organizations with high priority. Furthermore, because the classification results, rather than the aggregate information, are displayed on the display unit 54, it is possible to avoid presenting excessively detailed information to the user of the salesperson terminal device 50.

[0107] [Functions of the doctor's terminal device] 4, the doctor terminal device 40 has an operation history transmission unit 41a as one of its functions. This function is realized, for example, by the control unit 41 executing a program stored in the storage unit 42 and controlling the communication unit 43 and the like.

[0108] For example, when the doctor terminal device 40 and the support device 10 are connected, the operation history transmission unit 41a transmits information indicating the content of the operation as an operation history to the support device 10 every time an operation is performed on the doctor terminal device 40. The operation history transmission unit 41a may also transmit the operation history to the support device 10 at predetermined time intervals (for example, every few seconds). As described above, the operation history DB 24 is updated based on the operation history received by the support device 10.

[0109] When an operation related to medical support content is performed while the doctor terminal device 40 and the support device 10 are not connected, the operation history may be stored in the storage unit 42 of the doctor terminal device 40. Then, the next time the doctor terminal device 40 connects to the support device 10, the operation history sending unit 41a may send the operation history stored in the storage unit 42 to the support device 10. This allows the support device 10 to grasp the operation content performed while the doctor terminal device 40 and the support device 10 are not connected (so-called offline).

[0110] [Functions of the business operator terminal device] 4, the salesperson terminal device 50 has a function of a tally definition receiving unit 51a. This function is realized, for example, by a program stored in the storage unit 52 being executed by the control unit 51, which controls the communication unit 53 and the like.

[0111] The tally definition receiving unit 51a receives information for defining the tallying process exemplified in FIGS. 9A to 9F through the input unit 55. Then, the salesperson terminal device 50 transmits the information to the support device 10. The tally definition receiving unit 51a receives information such as the operation to be tallyed, the number of tallying targets, and the tallying period. The tally definition receiving unit 51a may also receive information identifying related drugs (e.g., drug names).

[0112] The salesperson terminal device 50 does not necessarily have to have such a tally definition receiving unit 51a. In this case, the tally definition DB 25 may be generated based on information input to the input unit 15 by the administrator of the support device 10.

[0113] [Operation flow of the support system] FIG. 11 is a sequence diagram showing an example of the operation of the support system S.

[0114] The salesperson terminal device 50 (counting definition receiving unit 51a) receives information for defining the counting process, such as the operations to be counted and the number of items to be counted (see FIGS. 9A to 9E), and transmits the information to the support device 10 (S101). The support device 10 updates the counting definition DB 25 based on the received information (S102).

[0115] The support device 10 also transmits medical support content including medical support information, medical calculation tools, medical articles, etc. to the doctor terminal device 40 (S103). This transmission may be performed when the above-mentioned medical support software is installed in the doctor terminal device 40, when the medical support software is updated, or when the web browser of the doctor terminal device 40 accesses the support device 10.

[0116] When the doctor performs an operation related to the medical support content (e.g., viewing) (S104), the doctor terminal device 40 (operation history sending unit 41a) sends information indicating this to the support device 10 as an operation history (S105). The support device 10 (operation history receiving unit 31) that receives the operation history updates the operation history DB 24 based on the received operation history (S106). As described above, the transmission of the operation history in S105 may be performed at predetermined time intervals, or may be performed every time the doctor performs an operation related to the medical support content.

[0117] The support device 10 (aggregated information calculation unit 32) executes aggregation processing defined in the aggregation definition DB 25 by referring to the operation history stored in the operation history DB 24, and classifies each doctor organization into one of a plurality of categories based on the results (S107). The support device 10 executes aggregation processing for each of the plurality of doctor organizations. The support device 10 may execute aggregation processing repeatedly at a preset cycle (for example, weekly or monthly). The support device 10 may also execute aggregation processing when receiving an aggregation command from the salesperson terminal device 50. Then, the support device 10 (classification result transmission unit 34) transmits the classification results to the salesperson terminal device 50 (S108). The salesperson terminal device 50 displays the classification results on the display unit 54 (S109).

[0118] Unlike the example shown in FIG. 11, the support device 10 may transmit the results of the tallying process (tally information) to the salesperson terminal device 50 in addition to or instead of the results of the classification.

[0119] The support device 10 may also store past classification results (classification of each doctor organization) in the storage unit 12. Then, the support device 10 may transmit past classification results in addition to the most recent classification result to the salesperson terminal device 50. The salesperson terminal device 50 may display temporal changes in the classification results on the display unit 54. This allows the user of the salesperson terminal device 50 to understand changes in the priority of each doctor organization in sales activities.

[0120] The support device 10 may store the results of past counting processes (counting information) in the storage unit 12. The support device 10 may transmit past counting results in addition to the most recent counting result to the salesperson terminal device 50. The salesperson terminal device 50 may display, on the display unit 54, the change over time in the counting results for each doctor organization.

[0121] The salesperson terminal device 50 may record the history of sales activities by salespeople to each doctor organization in the storage unit 52. The salesperson terminal device 50 may then adjust the display of the classification results for each doctor organization based on the sales activity history. For example, the classification results for doctor organizations for which sales activities have been conducted within a predetermined period (e.g., one week) may not be displayed on the display unit 54.

[0122] [Counting and classification process flow] Fig. 12 is a flow diagram showing an example of processing executed by the aggregate information calculation unit 32 and the doctor tissue classification unit 33. The processing illustrated in Fig. 12 corresponds to the processing of S107 shown in Fig. 11. The processing shown in Fig. 12 may be repeatedly executed at a predetermined cycle, such as weekly or monthly, or may be started in response to a command from the salesperson terminal device 50.

[0123] The aggregated information calculation unit 32 selects a doctor organization to be aggregated (S201). For example, the aggregated information calculation unit 32 selects a doctor organization for which aggregation processing has not yet been performed from among multiple doctor organizations stored in the doctor organization DB 22 (see FIG. 6). Alternatively, the aggregated information calculation unit 32 may select a doctor organization to be aggregated in accordance with an instruction from the salesperson terminal device 50.

[0124] The tally information calculation unit 32 also acquires the tally period (S202). The tally period is defined, for example, in the tally definition DB 25 (FIGS. 9A to 9F), and therefore the tally information calculation unit 32 may acquire the tally period by referring to the tally definition DB 25. Alternatively, the tally information calculation unit 32 may acquire the tally period in accordance with a command from the salesperson terminal device 50.

[0125] The aggregated information calculation unit 32 refers to the operation history DB 24 (see FIG. 8) and acquires the operation history during the aggregation period of the doctors who belong to the doctor organization selected in S201 (S203). Then, the support device 10 (aggregated information calculation unit 32 and doctor organization classification unit 33) executes the aggregation process defined in the aggregation definition DB 25 (FIGS. 9A to 9F) and classifies the doctor organization based on the result (aggregated information) (S204).

[0126] Then, the support device 10 determines whether or not there are any doctor organizations for which the counting process has not yet been performed (S205). For example, the support device 10 determines whether or not there are any doctor organizations for which the counting process has not yet been performed among the multiple doctor organizations stored in the doctor organization DB 22 (see FIG. 6). If there are any doctor organizations for which the counting process has not yet been performed ("yes" in S205), the support device 10 returns to S201 and performs the subsequent processes.

[0127] On the other hand, if such a doctor organization does not remain ("no" in S205), the support device 10 (classification result transmission unit 34) transmits the classification result obtained in S204 to the salesperson terminal device 50 (S206). At this time, the support device 10 may transmit the result of the calculation process (calculation information) to the salesperson terminal device 50. Then, the support device 10 ends this process.

[0128] Fig. 13A is a flow diagram showing an example of the processing of S204 shown in Fig. 12. Here, as described in Fig. 9A, an example will be described in which the operation to be counted is the viewing of medical support information that has been pre-selected as content to be counted, and the number of items to be counted is the number of doctors.

[0129] The aggregated information calculation unit 32 initializes the count number (i) (S301). The aggregated information calculation unit 32 selects a doctor whose operation history is to be referenced from among the doctors belonging to the doctor organization selected in S201 of FIG. 12 (S302). The aggregated information calculation unit 32 refers to the organization information of each doctor stored in the doctor DB 21 (see FIG. 5), for example, and selects a doctor who belongs to the doctor organization selected in S201. The operation history of the doctor selected here is referenced in subsequent processing and is used for aggregation processing.

[0130] At this time, the aggregate information calculation unit 32 may select doctors by referring to attribute information (see FIG. 5) other than the organization information of each doctor. For example, doctors with little medical experience (doctors with medical experience less than a predetermined value) may be excluded from selection. This prevents the operation history of doctors with little medical experience from being reflected in the aggregate information or the classification of doctor organizations. Conversely, in S302, only doctors with a lot of medical experience (doctors with medical experience equal to or greater than a predetermined value) may be selected.

[0131] The aggregated information calculation unit 32 refers to the operation history of the selected doctor and determines whether an operation to be aggregated has been performed (S303). For example, the aggregated information calculation unit 32 determines whether medical support information (e.g., regimen) selected as content to be aggregated has been viewed. A plurality of pieces of medical support information may be selected as content to be aggregated. In this case, in S303, the aggregated information calculation unit 32 may determine whether any of the plurality of pieces of medical support information has been viewed.

[0132] The operation to be counted may be the use of a medical calculation tool or a search using a keyword related to the content to be counted. In this case, the count information calculation unit 32 may determine in S303 whether the medical calculation tool is being used or whether a search using the related keyword is being performed.

[0133] If it is determined that a target operation has been performed ("yes" in S303), the aggregated information calculation unit 32 increments the count number (i) (i←i+1) (S304). Then, the aggregated information calculation unit 32 determines whether there is a doctor whose operation history has not yet been referenced among the doctors belonging to the doctor organization selected in S201 (see FIG. 12) (S305). If there is such a doctor ("yes" in S305), the aggregated information calculation unit 32 returns to S302 and executes the subsequent processes. On the other hand, if there is no such doctor remaining ("no" in S305), the count number (i) is the aggregation result (aggregated information) for the selected doctor organization. Therefore, the doctor organization classification unit 33 classifies the doctor organization into one of multiple categories based on the count number (i) according to predetermined criteria (S306). In S303, if the operation to be counted has not been performed ("no" in S303), the count information calculation unit 32 maintains the count number (i) and executes the determination in S305.

[0134] After executing S306, the support device 10 returns to the process of Fig. 12 and executes the processes from S205 onwards. As a result of this process, as shown in Fig. 13B, the aggregation results (the number of doctors who viewed the medical support information) for multiple doctor organizations and the classification of each doctor organization are calculated. Then, this classification result is sent to the salesperson terminal device 50.

[0135] Fig. 14 is a flow diagram showing another example of the process of S204 shown in Fig. 12. Here, as described in Fig. 9C, an example will be described in which the operation to be counted is the viewing of multiple pieces of medical support information (e.g., treatment manuals) selected in advance as content to be counted, and the number of items to be counted is the number of types of medical support information being viewed.

[0136] The processes of S401 and S402 in FIG. 14 are the same as the processes of S301 and S302 shown in FIG. 13A, and therefore the description thereof will be omitted.

[0137] The aggregated information calculation unit 32 determines whether any of the multiple pieces of medical support information (e.g., treatment manuals) selected as content to be aggregated has been viewed (S403). If any piece of medical support information has been viewed ("yes" in S403), the aggregated information calculation unit 32 determines whether the medical support information has been viewed by other doctors in the same doctor organization (S404). This makes it possible to avoid duplicate counting of the number of types of medical support information.

[0138] If the medical support information being viewed in S403 has not been viewed by another doctor ("no" in S404), the aggregated information calculation unit 32 increments the count number (i) (i←i+1) (S405). Then, the aggregated information calculation unit 32 determines whether there is a doctor whose operation history has not yet been viewed among the doctors belonging to the doctor organization selected in S201 (see FIG. 12) (S406). If there is such a doctor ("yes" in S406), the aggregated information calculation unit 32 returns to S402 and executes the subsequent processes.

[0139] On the other hand, if there are no such doctors remaining ("no" in S406), the count number (i) is the count result for the selected doctor organization (i.e., the number of types of medical support information being viewed). Therefore, the doctor organization classification unit 33 classifies this doctor organization into one of multiple categories based on this count number (i) (S407).

[0140] Furthermore, if the medical support information has not been viewed in S403 ("no" in S403), or if the medical support information has been viewed by another doctor in S404 ("yes" in S404), the aggregate information calculation unit 32 maintains the count number (i) and executes the determination in S406. After executing S407, the support device 10 returns to the processing in FIG. 12 and executes the processing from S205 onwards.

[0141] 14, the aggregated information calculation unit 32 may determine whether or not related keywords associated with multiple pieces of medical support information, which are the content to be aggregated, have been searched for. The aggregated information calculation unit 32 may then count the number of such searches and use the results to classify the doctor organizations.

[0142] Fig. 15 is a flow diagram showing yet another example of the process of S204 shown in Fig. 12. Here, as described in Fig. 9B, an example will be described in which the operation to be counted is the viewing of medical support information that has been selected in advance as content to be counted, and the number of times to be counted is the total viewing time thereof.

[0143] The aggregated information calculation unit 32 initializes the total viewing time (T) (S501). The aggregated information calculation unit 32 selects a doctor to be referenced for the operation history from among the doctors belonging to the doctor organization selected in S201 of Fig. 12 (S502). The aggregated information calculation unit 32 selects a doctor who has not yet been selected from among the doctors belonging to the doctor organization selected in S201.

[0144] The aggregate information calculation unit 32 refers to the operation history of the selected doctor and counts the viewing time (t) of the medical support information selected as the content to be aggregated (S503). A plurality of pieces of medical support information may be selected as the content to be aggregated. In this case, the aggregate information calculation unit 32 may count the total value of the viewing times of the plurality of pieces of medical support information as the viewing time (t) in S503.

[0145] The aggregated information calculation unit 32 updates the total viewing time (T) based on the viewing time (t) (S504). For example, the aggregated information calculation unit 32 adds the viewing time (t) to the total viewing time (T) to obtain a new total viewing time (T←T+t). The aggregated information calculation unit 32 then determines whether there are any doctors belonging to the doctor organization selected in S201 (see FIG. 12) whose operation history has not yet been referenced (S505). If there are any such doctors remaining ("yes" in S505), the aggregated information calculation unit 32 returns to S502 and executes the subsequent processes. On the other hand, if there are no such doctors remaining ("no" in S505), the total viewing time (T) is the aggregation result (aggregated information) for the selected doctor organization. Therefore, the doctor organization classification unit 33 classifies this doctor organization into one of multiple categories based on the total viewing time (T) (S506). After executing S506, the assistance device 10 returns to the processing of FIG. 12 and executes the processing from S205 onwards.

[0146] The number of items to be counted may be the total number of times the items have been viewed. In this case, the total number of times the items have been viewed can be calculated by the same process as that shown in FIG. 15, and the doctor organization can be classified into one of a plurality of categories.

[0147] Fig. 16 is a flow diagram showing yet another example of the process of S204 shown in Fig. 12. Here, an example will be described in which the multiple counting processes described with reference to Figs. 9A to 9F are executed, and the results of each process are integrated to calculate counted information. The process illustrated in Fig. 16 provides the evaluation results of each doctor organization illustrated in Fig. 10.

[0148] The aggregated information calculation unit 32 executes a first aggregation process (S601). The first aggregation process may be one or more of the multiple aggregation processes defined in the aggregation definition DB 25. For example, the first aggregation process may be any of the aggregation processes described with reference to FIGS. 13 to 15. The aggregated information calculation unit 32 calculates a first score based on the result of the first aggregation process (S602). The result of the first aggregation process may be the number of doctors, the total viewing time, the number of searches for related keywords, etc. Furthermore, the result of the first aggregation process may be the number of types of medical support information viewed within the same doctor organization among multiple pieces of medical support information pre-selected as content to be aggregated. The first score may be a value obtained by multiplying the result of the first aggregation process by a first coefficient.

[0149] The aggregated information calculation unit 32 executes a second aggregation process (S603). The second aggregation process may be defined in the aggregation definition DB 25 and may be different from the first aggregation process. The aggregated information calculation unit 32 calculates a second score based on the result of the second aggregation process (S604). The result of the second aggregation process may also be the number of doctors, the total viewing time, the total number of views, the number of searches for related keywords, etc. Furthermore, the result of the second aggregation process may be the number of types of medical support information viewed within the same doctor organization among multiple pieces of medical support information pre-selected as content to be aggregated. The second score may be a value obtained by multiplying the result of the second aggregation process by a second coefficient.

[0150] The aggregate information calculation unit 32 calculates an integrated score based on the first score and the second score (S605). The integrated score may be, for example, the sum of the first score and the second score. The integrated score is aggregate information about the selected doctor organization, and the doctor organization classification unit 33 classifies the doctor organization into one of a plurality of categories based on the integrated score (S606). After executing S606, the support device 10 returns to the processing of FIG. 12 and executes the processing from S205 onwards.

[0151] 16, the aggregated information calculation unit 32 integrates the results of two aggregation processes and calculates the result (integrated score) as aggregated information. However, the aggregated information calculation unit 32 may integrate the results of three or more aggregation processes. For example, the aggregated information calculation unit 32 may integrate a third score based on the result of a third aggregation process with the first score and second score described above.

[0152] The processing of the physician tissue classification unit 33 is not limited to the above example. For example, when the aggregate information calculation unit 32 executes multiple aggregation processes, the physician tissue classification unit 33 may classify each physician tissue depending on whether multiple aggregation results obtained by the multiple aggregation processes satisfy predetermined conditions. For example, when the result of a first aggregation process satisfies the predetermined condition, the physician tissue classification unit 33 may classify the physician tissue into the first category, and when the result of a second aggregation process satisfies the predetermined condition, the physician tissue classification unit 33 may classify the physician tissue into the second category.

[0153] Fig. 17 is a flow diagram showing an example of such processing by the aggregate information calculation unit 32 and the doctor tissue classification unit 33. The processing illustrated in Fig. 17 corresponds to the processing of S107 shown in Fig. 11. The processing shown in Fig. 17 may be repeatedly executed at a predetermined cycle, such as weekly or monthly, or may be executed in accordance with a command from the sales representative terminal device 50. Note that S701 to S703 in the processing shown in Fig. 17 are similar to S201 to S203 in the processing shown in Fig. 12, respectively, and therefore will not be described here.

[0154] The aggregated information calculation unit 32 executes a first aggregation process for the doctor organization selected in S701 (S704). The first aggregation process may be one or more of the multiple aggregation processes defined in the aggregation definition DB 25 (FIGS. 9A to 9F). For example, the first aggregation process may be any of the aggregation processes described in FIGS. 13 to 15. The result of the first aggregation process may be the number of doctors, the total viewing time, the number of searches for related keywords, etc. Furthermore, the result of the first aggregation process may be the number of types of medical support information viewed within the same doctor organization from among the multiple pieces of medical support information pre-selected as content to be aggregated.

[0155] The doctor tissue classification unit 33 determines whether the result of the first counting process (first counting information) satisfies the first condition (S705). For example, the doctor tissue classification unit 33 determines whether the result of the first counting process is greater than a first threshold. If the first counting process is composed of multiple counting processes, it may determine whether the results of the multiple counting processes are each greater than multiple thresholds. For example, the doctor tissue classification unit 33 may determine whether the number of types of medical support information viewed within the same doctor tissue is greater than a threshold and the number of searches for related keywords is greater than a threshold. Here, if the result of the first counting process satisfies the first condition ("yes" in S705), the doctor tissue classification unit 33 classifies the selected doctor tissue into the first category (S706).

[0156] On the other hand, if the result of the first counting process does not satisfy the first condition ("no" in S705), the count information calculation unit 32 executes a second counting process for the doctor tissue selected in S701 (S707). The second counting process may be, for example, a counting process different from the first counting process defined in the counting definition DB 25 (FIGS. 9A to 9F), or may be the same process. The doctor tissue classification unit 33 determines whether the result of the second counting process (second counting information) satisfies the second condition (S708). For example, the doctor tissue classification unit 33 determines whether the result of the second counting process is equal to or greater than a second threshold. If the second counting process is composed of multiple counting processes, it may determine whether the results of the multiple counting processes are each greater than multiple thresholds. Here, if the result of the second counting process satisfies the second condition ("yes" in S708), the doctor tissue classification unit 33 classifies the selected doctor tissue into the second category (S709).

[0157] On the other hand, if the result of the second counting process does not satisfy the second condition ("no" in S708), the count information calculation unit 32 classifies the selected doctor organization into the third category (S710). If the selected doctor organization is classified into any category in S706, S709, or S710, the support device 10 determines whether or not there are any doctor organizations for which the counting process has not yet been performed (S711). For example, the support device 10 determines whether or not there are any doctor organizations for which the counting process has not yet been performed among the multiple doctor organizations stored in the doctor organization DB 22 (see FIG. 6). If there are any doctor organizations for which the counting process has not yet been performed, the support device 10 returns to S701 and executes the subsequent processes. On the other hand, if there are no doctor organizations for which the counting process has not yet been performed ("no" in S711), the support device 10 (classification result transmission unit 34) transmits the classification results obtained in S706, S709, or S710 to the salesperson terminal device 50, and ends the current process.

[0158] [summary] As described above, the sales activity support device 10 proposed in the present disclosure includes an operation history receiving unit 31 that receives operation history related to the use of multiple medical support contents by each doctor from each of multiple doctor terminal devices 40 used by multiple doctors, a doctor DB 21 that stores multiple doctors who belong to a first doctor organization A1 among the multiple doctors, and an aggregated information calculation unit 32 that aggregates the history of operations related to pre-selected medical support contents performed by doctors of the first doctor organization A1 based on the operation history of the doctors belonging to the first doctor organization A1 and calculates aggregated information based on the results.

[0159] By utilizing the aggregate information obtained from the sales activity support device 10, it is possible to grasp the doctor organizations that have needs for the medical product related to the pre-selected medical support content, thereby making the sales activity for this medical product more efficient.

[0160] [others] The sales activity support device proposed in the present disclosure is not limited to the support device 10 described above, and various modifications may be made.

[0161] For example, the support device 10 has a doctor organization DB 22 and performs a counting process for each of a plurality of doctor organizations recorded therein. However, the support device 10 may perform a counting process for only one pre-selected doctor organization without having such a doctor organization DB 22. The counting process may be repeatedly performed at a predetermined interval (for example, weekly or monthly) or in response to a command from the salesperson terminal device 50. This allows the salesperson (the user of the salesperson terminal device 50) to know the best timing for sales activities for the selected one doctor organization. [Explanation of symbols]

[0162] 10: Sales activity support device, 20: Data storage unit, 21: Doctor database, 22: Doctor organization database, 23: Medical support content database, 24: Operation history database, 25: Aggregation definition database, 31: Operation history receiving unit, 32: Aggregation information calculation unit, 33: Doctor organization classification unit, 34: Classification result transmission unit, 40: Doctor terminal device, 50: Salesperson terminal device, 51a: Aggregation definition reception unit.

Claims

1. an operation history receiving means for receiving operation histories relating to the use of a plurality of medical support contents by each of a plurality of medical workers from each of a plurality of terminal devices used by the plurality of medical workers; a calculation means for determining whether a predetermined operation has been performed on a preselected medical support content by a first medical worker belonging to a first organization and included in the plurality of medical workers, based on the operation history of the first medical worker, and calculating aggregate information based on the result of the determination; a classification means for calculating a classification indicating a priority in sales activities for the first medical worker belonging to the first organization based on the aggregated information; A medical product sales activity support device having the above.

2. The preselected medical support content includes a medical calculation tool that accepts input of patient information, including information about the patient's condition, at the terminal device and calculates information about the disease based on the patient information; The calculation means determines whether the medical calculation tool has been used.

2. A medical product sales activity support device according to claim 1.

3. The preselected medical support content includes a plurality of medical support contents that can be used in the treatment of a common disease, the plurality of preselected medical contents include a medical calculation tool that receives input of patient information at the terminal device and calculates information related to the patient's disease based on the patient information, and medical care support information that includes document information that supports medical care by a doctor; The calculation means determines whether the medical calculation tool has been used and whether the medical support information has been viewed.

2. A medical product sales activity support device according to claim 1.

4. The classification means calculates a first category indicating a priority in sales activities when the aggregated information satisfies a first condition, and calculates a second category indicating a priority in sales activities when the aggregated information does not satisfy the first condition but satisfies a second condition.

2. A medical product sales activity support device according to claim 1.

5. The preselected medical support content includes a plurality of medical support contents that can be used in the treatment of a common disease, The preselected plurality of medical contents include first medical support contents to which a first application priority is assigned in the medical treatment of a disease, and second medical support contents to which a second application priority is assigned in the medical treatment of a disease.

2. A medical product sales activity support device according to claim 1.

6. The calculation means performing a first tallying process on a history of operations performed by the first medical worker belonging to the first organization on the pre-selected medical support content, and calculating a first score based on the tallying result; performing a second aggregation process on a history of operations performed by the first medical worker belonging to the first organization on the pre-selected medical support content, and calculating a second score based on the aggregation result; An integrated score obtained based on the first score and the second score is calculated as the aggregate information.

2. A medical product sales activity support device according to claim 1.

7. The calculation means calculates, as the aggregate information, a score according to the degree of use by the first medical worker belonging to the first organization for the pre-selected medical support content.

2. A medical product sales activity support device according to claim 1.

8. The calculation means determines whether or not the predetermined operation on the pre-selected medical support content during a predetermined period has been performed by the first medical worker, and calculates the aggregate information based on the result of the determination.

2. A medical product sales activity support device according to claim 1.

9. The calculation means determines whether the predetermined operation on the pre-selected medical support content has been performed by the first medical worker during a predetermined period, and repeatedly executes a process of calculating the aggregate information based on the result of the determination at time intervals.

9. A medical product sales activity support device according to claim 8.

10. The calculation means determines whether or not the predetermined operation has been performed by the second medical worker on the pre-selected medical support content based on the operation history of the second medical worker belonging to the first organization, and calculates the aggregate information based on the result of the determination.

2. A medical product sales activity support device according to claim 1.

11. The classification means selectively calculates, based on the aggregated information, a first category indicating the highest priority in sales activities and a second category indicating a lower priority than the first category.

2. A medical product sales activity support device according to claim 1.

12. The preselected medical support content includes a plurality of medical support contents that can be used in the treatment of a common disease, The calculation means calculates the number of medical contents that have been viewed by the first medical worker belonging to the first organization from among the plurality of pre-selected medical support contents.

2. A medical product sales activity support device according to claim 1.

13. The preselected medical support content includes a plurality of medical support contents that can be used in the treatment of a common disease; The calculation means determines whether or not all of the plurality of pre-selected medical support contents have been viewed by the first medical worker belonging to the first organization, or whether or not any of the plurality of pre-selected medical support contents have been viewed by the first medical worker belonging to the first organization.

2. A medical product sales activity support device according to claim 1.

14. A step of receiving operation histories relating to the use of a plurality of medical support contents by each of a plurality of medical professionals from a plurality of terminal devices used by each of the plurality of medical professionals; a step of determining whether a predetermined operation has been performed on a preselected medical support content by a first medical worker who belongs to a first organization and is included in the plurality of medical workers, based on the operation history of the first medical worker, and calculating aggregate information based on the result of the determination; calculating a classification indicating a priority in sales activities for the first medical worker belonging to the first organization based on the aggregated information; A control method for a sales activity support device including:

15. An operation history receiving means for receiving operation histories relating to the use of a plurality of medical support contents by each of a plurality of medical professionals from each of a plurality of terminal devices used by the plurality of medical professionals; a calculation means for determining whether a predetermined operation has been performed on a preselected medical support content by a first medical worker belonging to a first organization included in the plurality of medical workers, based on the operation history of the first medical worker, and calculating aggregate information based on the result of the determination; a classification means for calculating a classification indicating a priority in sales activities for the first medical worker belonging to the first organization based on the aggregated information; A program that makes a computer function.

16. A sales activity support device according to claim 1; the plurality of terminal devices used by the plurality of medical professionals; a terminal device that communicates with the sales activity support device and is used by a provider of a medical product to be used in the diagnosis and treatment of a disease related to the preselected medical support content; A sales activity support system that has the following features.

Images