Server, program, information processing method, and information processing system

Abstract

To provide a server which facilitates online communication between a healthcare worker and employees of a company, a program, and an information processing method.SOLUTION: In an information processing system, a server 30 transmits an application for cooperation between a company and a doctor to a doctor client device 10 in accordance with a cooperation request from a company client device 50, associates and stores doctor identification information identifying the doctor and employee identification information identifying multiple employees belonging to the company, in accordance with an approval request from the doctor client device 10, and releases the association between the doctor identification information and employee identification information of an employee designated by the doctor in response to a block request from the doctor client device 10.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] In recent years, communication has become increasingly online. For online communication, it is important that the people communicating agree to communicate with each other. For example, Patent Document 1 discloses a technique for providing information about an applicant who has applied to build a predetermined relationship in a virtual community to a person who is seeking to approve the application. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-175966 Summary of the Invention [Problem to be solved by the invention]

[0004] When a medical professional (e.g., a doctor) communicates with a company online, the doctor will have multiple employees communicating with him or her. For example, if the company is a pharmaceutical company, multiple pharmaceutical company sales representatives (hereinafter referred to as "MRs") will communicate with the doctor. This can sometimes make the communication demands on the doctor excessive. Therefore, doctors have a psychological hurdle in communicating with companies online. As a result, online communication between doctors and companies is suppressed. The technology of Patent Document 1 does not distinguish between the application and approval relationship between doctors and companies, making it difficult to promote online communication between doctors and companies.

[0005] An object of the present invention is to promote online communication between medical professionals and company employees. [Means for solving the problem]

[0006] One aspect of the present invention is A server connectable to a first client device used by a doctor and a second client device used by an employee of a company, a means for transmitting a request for collaboration between the company and the doctor to the first client device in response to a collaboration request from the second client device; a means for storing doctor identification information for identifying the doctor and employee identification information of a plurality of employees belonging to the company in association with each other in response to an approval request from the first client device; and means for canceling the association between the doctor identification information and the employee identification information of the target employee designated by the doctor in response to a block request from the first client device. It is a server. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a functional block diagram of the information processing system of FIG. 1. [Figure 3] FIG. 2 is an explanatory diagram illustrating an outline of a link function according to the present embodiment. [Figure 4] FIG. 2 is an explanatory diagram illustrating an outline of block functions according to the present embodiment. [Figure 5] FIG. 2 is a diagram showing a data structure of a doctor information database according to the present embodiment. [Figure 6] FIG. 2 is a diagram showing a data structure of a company information database according to the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating a data structure of an employee information database according to the present embodiment. [Figure 8] 3A and 3B are diagrams illustrating data structures of a linkage information database and a block information database according to the present embodiment. [Figure 9] FIG. 2 is a diagram showing a data structure of a distribution information database according to the present embodiment. [Figure 10] FIG. 4 is a sequence diagram of a cooperation process according to the present embodiment. [Figure 11] 11A and 11B are diagrams showing examples of screens displayed in the information processing of FIG. 10. [Figure 12] FIG. 4 is a sequence diagram of block processing according to the present embodiment. [Figure 13] 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12. FIG. [Figure 14] FIG. 10 is a sequence diagram of a block release process according to the present embodiment. [Figure 15] 15 is a diagram showing an example of a screen displayed in the information processing of FIG. 14. FIG. [Figure 16] FIG. 4 is a sequence diagram of an information distribution process according to the present embodiment. [Figure 17] 17A and 17B are diagrams showing examples of screens displayed in the information processing of FIG. 16. [Figure 18] FIG. 10 is a sequence diagram of a cooperation process according to the first modification. [Figure 19] 19 is a diagram showing an example of a screen displayed in the information processing of FIG. 18. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and repeated description thereof will be omitted.

[0009] (1) Information processing system configuration The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system of this embodiment. Fig. 2 is a functional block diagram of the information processing system of Fig. 1.

[0010] As shown in FIG. 1, the information processing system 1 includes a doctor client device 10, a server 30, and a company client device 50. The doctor client device 10, the server 30, and the company client device 50 are connected via a network (for example, the Internet or an intranet) NW.

[0011] The doctor client device 10 is a computer (an example of a "first client device") that sends a request to the server 30. The doctor client device 10 is operated by a doctor. The doctor client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer.

[0012] The corporate client device 50 is a computer (an example of a "second client device") that sends a request to the server 30. The corporate client device 50 is operated by an employee of the company. The corporate client device 50 is, for example, a smartphone, a tablet terminal, or a personal computer. The company may be, for example, a medical-related company. The company may be, for example, at least one of the following: Pharmaceutical companies Medical device manufacturing company Pharmaceutical wholesaler Employees include, for example: ·Administrator ·MR Medical Science Liaison (hereinafter referred to as "MSL") Medical Affairs (hereinafter referred to as "MA")

[0013] The server 30 is a computer (an example of an "information processing device") that provides a response to a request sent from the doctor client device 10 or the company client device 50 to the doctor client device 10 or the company client device 50. The server 30 is, for example, a web server.

[0014] (1-1) Configuration of doctor client device The configuration of the doctor client device 10 will be described.

[0015] As shown in FIG. 2, the doctor client device 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14.

[0016] The storage device 11 is configured to store programs and data, and is, for example, a combination of a read-only memory (ROM), a random access memory (RAM), and a storage (for example, a flash memory or a hard disk).

[0017] The programs include, for example, the following programs: OS (Operating System) programs Applications that process information (e.g., web browsers)

[0018] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0019] The processor 12 is configured to realize the functions of the doctor client device 10 by running a program stored in the storage device 11. The processor 12 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0020] The input / output interface 13 is configured to receive user instructions from an input device connected to the doctor client device 10 and to output information to an output device connected to the doctor client device 10 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0021] The communication interface 14 is configured to control communications between the physician client device 10 and the server 30 .

[0022] (1-2) Configuration of corporate client device The configuration of the company client device 50 will be described.

[0023] As shown in FIG. 2, the company client device 50 includes a storage device 51, a processor 52, an input / output interface 53, and a communication interface .

[0024] The storage device 51 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage (for example, flash memory or a hard disk).

[0025] The programs include, for example, the following programs: OS programs Applications that process information (e.g., web browsers)

[0026] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)

[0027] The processor 52 is configured to implement the functions of the enterprise client device 50 by running a program stored in the storage device 51. The processor 52 is, for example, a CPU, an ASIC, an FPGA, or a combination thereof.

[0028] The input / output interface 53 is configured to receive user instructions from an input device connected to the corporate client device 50 and to output information to an output device connected to the corporate client device 50 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0029] The communication interface 54 is configured to control communications between the enterprise client device 50 and the server 30 .

[0030] (1-3) Server configuration The configuration of the server 30 will be described.

[0031] As shown in FIG. 2, the server 30 includes a storage device 31, a processor 32, an input / output interface 33, and a communication interface .

[0032] The storage device 31 is configured to store programs and data, and is, for example, a combination of ROM, RAM, and storage (for example, flash memory or a hard disk).

[0033] The programs include, for example, the following programs: OS programs Application programs that perform information processing

[0034] The data includes, for example, the following data: Databases referenced in information processing - Results of information processing

[0035] The processor 32 is configured to implement the functions of the server 30 by running a program stored in the storage device 31. The processor 32 is, for example, a CPU, an ASIC, an FPGA, or a combination thereof.

[0036] The input / output interface 33 is configured to receive user instructions from an input device connected to the server 30 and to output information to an output device connected to the server 30 . The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof. The output device is, for example, a display.

[0037] The communication interface 34 is configured to control communications between the server 30 and the physician client device 10 .

[0038] (2) Overview of the embodiment An outline of this embodiment will be described. The server 30 of this embodiment provides a linking function and a blocking function.

[0039] (2-1) Overview of the collaboration function An outline of the link function of this embodiment will be explained below: Fig. 3 is an explanatory diagram showing an outline of the link function of this embodiment. Figure 3 shows an example where the company is a pharmaceutical company.

[0040] As shown in FIG. 3A, a pharmaceutical company PH1 has a plurality of employees (for example, a manager AD1 and sales representatives MR1 ​​and MR2). When the administrator AD1 makes a cooperation application for cooperation with the doctor DR1 and the doctor DR1 approves the cooperation application, the server 30 cooperates with the pharmaceutical company PH1 and the doctor DR1.

[0041] As shown in FIG. 3B, when pharmaceutical company PH1 and doctor DR1 cooperate with each other, multiple employees (manager AD1 and sales representatives MR1 ​​and MR2) belonging to pharmaceutical company PH1 cooperate with doctor DR1.

[0042] This establishes a partnership between multiple employees of pharmaceutical company PH1 and doctor DR1.

[0043] (2-2) Overview of the block function An outline of the block functions of this embodiment will be explained below: Fig. 4 is an explanatory diagram of the outline of the block functions of this embodiment.

[0044] As shown in FIG. 4A, when the doctor DR1 makes a block request to block cooperation with the desired sales representative MR2, the server 30 blocks cooperation between the sales representative MR2 and the doctor DR1.

[0045] As shown in Figure 4B, when the collaboration between sales representative MR2 and doctor DR1 becomes blocked, collaboration between manager AD1 and sales representative MR1, who are employees of pharmaceutical company PH1 and are not blocked, and doctor DR1 is maintained.

[0046] This allows the doctor DR1 to easily terminate cooperation with a desired sales representative MR2 from among the employees of the pharmaceutical company PH1.

[0047] (3) Database The databases of this embodiment will be described below. The following databases are stored in the storage device 31.

[0048] (3-1) Doctor Information Database The doctor information database of this embodiment will be described below with reference to Fig. 5, which is a diagram showing the data structure of the doctor information database of this embodiment.

[0049] Doctor information is stored in the doctor information database in Fig. 5. The doctor information is information about doctors. The doctor information database includes a "Doctor ID" field, a "Doctor Name" field, a "Clinic ID" field, a "Doctor Attributes" field, and a "Doctor Contact" field. Each field is associated with the others.

[0050] The "Doctor ID" field stores doctor identification information, which is information for identifying a doctor.

[0051] The "Doctor Name" field stores doctor name information. The doctor name information is information about the doctor's name.

[0052] The "Clinic ID" field stores the clinic identification information of the clinic to which the doctor belongs.

[0053] The "Doctor Attributes" field stores doctor attribute information. The doctor attribute information is information about the attributes of doctors. The "Doctor Attributes" field includes a "Gender" field, an "Age" field, and a "Medical Department" field.

[0054] The "gender" field stores gender information, which is information about the gender of the doctor.

[0055] The "age" field stores age information, which is information about the age of the doctor.

[0056] The "medical department" field stores medical department information, which is information about the medical department of the doctor.

[0057] The "Doctor Contact" field stores at least one piece of doctor contact information. The doctor contact information is information about the doctor's contact information.

[0058] (3-2) Corporate Information Database The company information database of this embodiment will be described below with reference to Fig. 6, which shows the data structure of the company information database of this embodiment.

[0059] Company information is stored in the company information database in Figure 6. The company information is information about companies. The company information database includes a "company" field, a "company name" field, and an "employee ID" field. Each field is associated with the other fields.

[0060] The "Company" field stores company identification information, which is information that identifies a company.

[0061] The "company name" field stores company name information. The company name information is information about the company name.

[0062] The "Employee ID" field stores employee identification information. The employee identification information identifies employees who belong to a company.

[0063] (3-3) Employee information database The employee information database of this embodiment will now be described with reference to Fig. 7, which shows the data structure of the employee information database of this embodiment.

[0064] Employee information is stored in the employee information database in Figure 7. The employee information is information about employees. The employee information database includes an "employee ID" field, an "employee name" field, an "employee attribute" field, and an "employee contact" field. Each field is associated with the other fields. The employee information database is associated with company identification information.

[0065] The "Employee ID" field stores employee identification information, which is information that identifies an employee.

[0066] The "employee name" field stores employee name information. The employee name information is information related to the employee's name.

[0067] The "employee attribute" field stores employee attribute information. The employee attribute information is information relating to the attributes of employees. The "employee attribute" field includes a "gender" field, an "age" field, and a "job type" field.

[0068] The "gender" field stores gender information, which is information about the gender of the employee.

[0069] The "age" field stores age information, which is information about the age of the employee.

[0070] The "job type" field stores job type information. Job type information is information about the job type of an employee in a company. Job types include, for example, at least one of the following: ·Administrator Sales representatives (e.g., pharmaceutical company representatives) MSL ·MA

[0071] The "Employee Contact" field stores employee contact information, which is information about how to contact an employee.

[0072] (3-4) Linkage information database and block information database The link information database of this embodiment will be described below with reference to Fig. 8, which shows the data structures of the link information database and the block information database of this embodiment.

[0073] The collaboration information database in Fig. 8A stores collaboration information, which is information about collaboration relationships between doctors and companies. The association information database includes a "association ID" field, a "associated company ID" field, and a "block employee ID" field. Each field is associated with the other fields. The federated information database is associated with the physician identification information.

[0074] The "association ID" field stores association identification information, which is information for identifying an association between a doctor and a company.

[0075] The "associated company ID" field stores company identification information of a company that cooperates with the doctor (hereinafter referred to as "associated company").

[0076] The block information database in Figure 8B stores block information. The block information is information about the block status between a doctor and employees of a collaborating company. A block status is a state in which the collaboration between a doctor and at least some of the employees of a collaborating company has been severed. The block information database includes a "block ID" field and a "block employee ID" field. Each field is associated with the other. The block information database is associated with physician identification information.

[0077] The "Block ID" field stores block identification information, which identifies the block status of doctors and employees.

[0078] The "blocked employee ID" field stores employee identification information of employees whose collaboration with doctors is blocked (hereinafter referred to as "blocked employees").

[0079] (3-5) Distribution information database The link information database of this embodiment will be described below with reference to Fig. 9, which shows the data structure of the distribution information database of this embodiment.

[0080] Delivery information is stored in the delivery information database of Fig. 9. The delivery information is information about messages to be delivered to doctors. The delivery information database includes a "delivery ID" field and a "message" field. Each field is associated with the other. The distribution information database is associated with the company identification information.

[0081] The "Delivery ID" field stores delivery identification information, which is information for identifying a delivery message.

[0082] The "Message" field stores broadcast message information. The broadcast message information is information related to the broadcast message. The "Message" field includes a "Content" field, a "Page" field, a "Period" field, a "Distribution Destination" field, and a "Role" field.

[0083] The "content" field stores the content of the message.

[0084] The "Page" field stores the title of the page on which the message is posted.

[0085] The "period" field stores the posting period of the message.

[0086] The "recipient" field stores recipient information, which is the doctor identification information of the doctor to whom the message is to be delivered.

[0087] The "role" field stores role information, which is information about the role of the message.

[0088] (4) Information processing The information processing of this embodiment will be described.

[0089] (4-1) Collaboration processing The cooperative processing of this embodiment will be described below with reference to Fig. 10, which is a sequence diagram of the cooperative processing of this embodiment. Fig. 11 is a diagram showing an example of a screen displayed in the information processing of Fig. 10.

[0090] The trigger for the process in FIG. 10 is, for example, a user instruction from an administrator (for example, an instruction to specify a linkage function).

[0091] As shown in FIG. 10, the company client device 50 acquires a user instruction (S1150). Specifically, the processor 52 displays a screen P150 (FIG. 11) on the display.

[0092] The screen P150 includes a display object A1500 and an operation object B1500.

[0093] Display object A1500 is an object that displays doctor name information of doctors who can be collaborated with (uncollaborated doctors and collaborating doctors). In the example of Figure 11, doctor DR1 is an uncollaborated doctor. Doctor DR2 is a collaborating doctor.

[0094] The operation object B1500 is an object that receives a user instruction to request cooperation with an uncooperative doctor. Doctor identification information is assigned to the operation object B1500.

[0095] After step S1150, the company client device 50 executes a link request (S1151). Specifically, when the administrator operates the operation object B1500, the processor 52 transmits cooperation request data to the server 30. The cooperation request data includes, for example, the following information: Administrator's employee identification information Physician identification information assigned to operation object B1500

[0096] After step S1151, the server 30 executes a cooperation request notification (S1130). Specifically, the processor 32 refers to the company information database (FIG. 6) and identifies a record whose "employee ID" field contains the employee identification information contained in the collaboration request data. The processor 32 identifies the company identification information and company name information of the record. The company identification information is the company identification information of the company that is the target of collaboration (hereinafter referred to as the "target collaboration company"). The processor 32 refers to the doctor information database (FIG. 5) to identify the doctor contact information associated with the doctor identification information included in the link request data. The processor 32 sends a link request notification to the contact person corresponding to the doctor contact information. The link request notification includes company name information of the company to be linked.

[0097] After step S1130, the doctor client device 10 executes acquisition of a user instruction (S1110). Specifically, the processor 12 displays a screen P110 (FIG. 11) on the display.

[0098] Screen P110 includes a message indicating that a cooperation request has been received from a cooperation target company, and operational objects B1100 to B1101.

[0099] The operation object B1100 is an object that receives a user instruction to approve a linkage application.

[0100] An operation object B 1101 is an object that receives a user instruction to reject a linkage request.

[0101] After step S1110, the doctor client device 10 executes a cooperation approval request (S1111). Specifically, when the doctor operates the operation object B1100, the processor 12 transmits cooperation approval request data to the server 30. The cooperation approval request data includes, for example, the following information. Physician Identification Information

[0102] After step S1111, the server 30 updates the database (S1131). Specifically, when the processor 32 acquires the collaboration approval request data from the doctor client device 10, the processor 32 adds a new record to the collaboration information database (FIG. 10) associated with the doctor identification information included in the collaboration approval request data. The following information is stored in each field of the new record. "Federation ID" field: New federation identification information "Associated Company ID" field: Company identification information of the affiliated company identified in step S1130 - "Block employee ID": Code "N / A" indicating no match

[0103] (4-2) Block processing The block processing of this embodiment will be described below with reference to Fig. 12, which is a sequence diagram of the block processing of this embodiment. Fig. 13 is a diagram showing an example of a screen displayed in the information processing of Fig. 12.

[0104] The process in FIG. 12 is triggered, for example, by a user instruction from a doctor to specify a target employee.

[0105] As shown in FIG. 12, the doctor client device 10 executes acquisition of a user instruction (S1210). Specifically, the processor 12 displays a screen P210 (FIG. 13) on the display.

[0106] The screen P210 includes a display object A2100, operation objects B2100 to B2101, and a field object F2100.

[0107] The display object A2100 is an object that displays messages exchanged with the target employee in chronological order (that is, a message timeline).

[0108] The field object F2100 is an object that accepts a user instruction to input a new message for the target employee.

[0109] The operation object B2100 is an object that receives a user instruction to send the message input into the field object F2100 to the target employee. The operation object B2100 is assigned the employee identification information of the target employee.

[0110] Operation object B2101 is an object that receives a user instruction to block collaboration with the target employee. The employee identification information of the target employee is assigned to operation object B2101.

[0111] After step S1210, the doctor client device 10 executes a block request (S1211). Specifically, when the doctor operates the operation object B2101, the processor 12 displays a screen P211 (FIG. 13) on the display.

[0112] The screen P212 includes an operation object B2110 and a field object F2110.

[0113] The field object F2110 is an object that receives a user instruction to input the reason for blocking.

[0114] The operation object B 2110 is an object that receives a user instruction to confirm the blocking of the target employee.

[0115] When the doctor inputs the reason for blocking in the field object F2110 and operates the operation object B2110, the processor 12 transmits block request data to the server 30. The block request data includes, for example, the following information: Physician Identification Information Employee identification information assigned to operation object B2101 Blocking reason entered in field object F2110

[0116] After step S1211, the server 30 updates the database (S1230). Specifically, the processor 32 refers to the doctor information database (FIG. 5) to identify doctor name information associated with the doctor identification information included in the block request data. Processor 32 refers to the company information database (FIG. 6) to identify company identification information associated with the employee identification information included in the block request data. The processor 32 refers to the association information database (FIG. 8) associated with the doctor identification information included in the block request data, and identifies association identification information associated with the identified company identification information. The processor 32 stores the employee identification information included in the block request data in the "block employee ID" field associated with the identified linked identification information.

[0117] After step S1230, the server 30 executes a block response (S1231). Specifically, the processor 32 transmits the block response data to the enterprise client device 50. The block response data includes the following information: Doctor name information identified in step S1230 - Block reason included in block request data

[0118] After step S1231, the company client device 50 executes a block completion display (S1250). Specifically, the processor 52 displays a screen P250 (FIG. 13) on the display.

[0119] The screen P250 includes a message indicating that the doctor DR1 has been blocked, and the reason for the block included in the block response data.

[0120] (4-3) Unblocking process The cooperation process of this embodiment will be described below. Fig. 14 is a sequence diagram of the block release process of this embodiment. Fig. 15 is a diagram showing an example of a screen displayed in the information processing of Fig. 14.

[0121] The process in FIG. 14 is triggered, for example, by a user instruction from a doctor to specify a target employee.

[0122] As shown in FIG. 14, the doctor client device 10 executes acquisition of a user instruction (S1310). Specifically, the processor 12 displays a screen P310 (FIG. 15) on the display.

[0123] The screen P310 includes display objects A2100 to A3100 and an operation object B3100.

[0124] Display object A3100 is an object that displays that collaboration with the target employee is blocked.

[0125] The operation object B3100 is an object that receives a user instruction to release the block on collaboration with the target employee. The operation object B3100 is assigned the employee identification information of the target employee.

[0126] After step S1310, the doctor client device 10 executes an unblock request (S1311). Specifically, when the doctor operates the operation object B3100, unblock request data is transmitted to the server 30. The unblock request data includes, for example, the following information: Physician Identification Information Employee identification information assigned to operation object B3100

[0127] After step S1311, the server 30 updates the database (S1330). Specifically, the processor 32 refers to the doctor information database (FIG. 5) to identify doctor name information associated with the doctor identification information included in the unblocking request data. The processor 32 refers to the company information database (FIG. 6) to identify the company identification information associated with the employee identification information included in the unblocking request data. The processor 32 refers to the association information database (FIG. 8) associated with the doctor identification information included in the unblocking request data, and identifies association identification information associated with the identified company identification information. The processor 32 deletes the employee identification information included in the unblock request data from the "blocked employee ID" field associated with the identified linked identification information.

[0128] After step S1330, the server 30 executes a block release response (S1331). Specifically, the processor 32 transmits unblocking response data to the enterprise client device 50. The unblocking response data includes the following information: Doctor name information identified in step S1330

[0129] After step S1331, the company client device 50 displays the completion of unblocking (S1350). Specifically, the processor 52 displays a screen P350 (FIG. 15) on the display.

[0130] Screen P350 includes a message indicating that the block by doctor DR1 has been removed.

[0131] (4-4) Information distribution processing The information distribution process of this embodiment will be described below. Fig. 16 is a sequence diagram of the information distribution process of this embodiment. Fig. 17 is a diagram showing an example of a screen displayed in the information processing of Fig. 16.

[0132] The trigger for the process in FIG. 16 is, for example, a user instruction (for example, an instruction to specify information distribution) from an employee (for example, a manager) of a pharmaceutical company.

[0133] As shown in FIG. 16, the company client device 50 acquires a user instruction (S1450). Specifically, the processor 52 displays a screen P450 (FIG. 17) on the display.

[0134] The screen P450 includes an operation object B4500 and a field object F4500.

[0135] The field object F4500 is an object that accepts user instructions to specify a target doctor for information distribution. The field object F4500 displays the doctor names of doctors who are candidates for the target doctor. Each doctor name is assigned doctor identification information corresponding to the doctor name. An employee (e.g., a manager) can specify a target doctor by checking the checkbox corresponding to the desired doctor name.

[0136] The operation object B4500 is an object that receives a user instruction for confirming a user instruction for the field object F4500.

[0137] When the employee specifies the target doctor using the field object F4500 and operates the operation object B4500, the processor 52 displays a screen P451 (FIG. 17) on the display.

[0138] The screen P451 includes an operation object B4510 and a field object F4510.

[0139] The field object F4510 is an object that receives user instructions regarding the delivery message (content, page, period, and role).

[0140] The operation object B4510 is an object that receives a user instruction for confirming a user instruction for the field object F4510.

[0141] After step S1450, the company client device 50 executes a distribution request (S1451). Specifically, when the administrator inputs a distribution message into field object F4510 and operates operation object B4510, processor 52 transmits distribution request data to server 30. The distribution request data includes, for example, the following information: Administrator's employee identification information ·Physician identification information for the physician specified in field object F4500 -Delivery message entered in field object F4510

[0142] After step S1451, the server 30 updates the database (S1431). Specifically, the processor 32 refers to the company information database (FIG. 6) to identify the company identification information and company name information associated with the employee identification information included in the distribution request data. The processor 32 adds a new record to the distribution information database (FIG. 9) associated with the identified company identification information. The following information is stored in each field of the new record. "Delivery ID" field: New delivery identification information "Content" field: The content of the delivery message included in the delivery request data "Page" field: The page of the delivery message included in the delivery request data "Duration" field: The duration of the delivery message included in the delivery request data "Delivery destination" field: Physician identification information included in delivery request data "Role" field: The role of the delivery message included in the delivery request data

[0143] After step S1430, the server 30 executes a distribution response (S1431). Specifically, the processor 32 refers to the doctor information database (FIG. 5) to identify the doctor contact information obtained in association with the doctor identification information included in the distribution request data. The processor 32 transmits the distribution response data to the contact person indicated by the identified doctor contact information. The distribution response data includes, for example, the following information: - Delivery message included in delivery request data Company name information identified in step S1430

[0144] After step S1431, the doctor client device 10 displays the distribution information (S1410). Specifically, the processor 12 displays a screen P410 (FIG. 17) on the display.

[0145] The screen P410 includes display objects A4100 to A4101.

[0146] The display object A4100 is an object that displays the company name information included in the distribution response data. The company name information is the company name information of the company that is the source of the distribution message.

[0147] The display object A4101 is an object that displays the distribution message included in the distribution response data.

[0148] (5) Summary of this embodiment According to this embodiment, when a doctor approves a collaboration request from a company administrator, the company and the doctor are linked, and in response to a block request from the doctor, collaboration between the doctor and employees (e.g., sales representatives) of the company designated by the doctor is blocked. This makes it easier for doctors to approve collaboration requests with the company, even if there are employees at the company who do not want to collaborate. As a result, online communication between doctors and companies can be promoted.

[0149] According to this embodiment, when a doctor and a company are blocked, the reason for the block is notified to the blocked employee, which can encourage the blocked employee to take corrective action to restore cooperation with the doctor.

[0150] According to this embodiment, in response to a request from a doctor to remove the block, the blocked doctor and the blocked employee are re-established in cooperation, thereby providing the blocked employee with an incentive to take corrective action in order to restore cooperation with the doctor.

[0151] According to this embodiment, a collaboration request is accepted from a company administrator, which makes it possible to prevent excessive collaboration requests from employees (e.g., sales representatives) other than the company administrator to doctors.

[0152] According to this embodiment, in response to a distribution request from a company, a desired message from the company is distributed to doctors who are affiliated with the company, thereby enabling the company to more easily convey its message to doctors.

[0153] According to this embodiment, a delivery request is accepted from a company administrator, which makes it possible to prevent excessive delivery of messages to doctors from employees other than the company administrator (for example, sales representatives).

[0154] (6) Variations A modification of this embodiment will now be described.

[0155] (6-1) Variation 1 A description will be given of Modification 1. Modification 1 is an example in which a linking process is executed in response to a request from a doctor.

[0156] (6-1-1) Collaboration process of Modification 1 A description will be given of the cooperation processing of Modification 1. Fig. 18 is a sequence diagram of the cooperation processing of Modification 1. Fig. 19 is a diagram showing an example of a screen displayed in the information processing of Fig. 18.

[0157] The trigger for the process in FIG. 18 is, for example, a user instruction from a doctor (for example, an instruction to specify a link function).

[0158] As shown in FIG. 18, the doctor client device 10 executes acquisition of a user instruction (S2110). Specifically, the processor 12 displays a screen P510 (FIG. 19) on the display.

[0159] The screen P510 includes a display object A5100 and an operation object B5100.

[0160] Display object A5100 is an object that displays company name information of companies that can be linked (unlinked companies and linked companies). In the example of Fig. 19, company PH1 is an unlinked company. Company PH2 is a linked company.

[0161] The operation object B 5100 is an object that receives a user instruction to apply for cooperation with an uncooperative company. Company identification information is assigned to the operation object B 5100.

[0162] After step S2110, the doctor client device 10 executes a cooperation request (S2111). Specifically, when the doctor operates the operation object B 5100, the processor 12 transmits cooperation request data to the server 30. The cooperation request data includes, for example, the following information: Physician Identification Information ·Company identification information assigned to the operational object B5100

[0163] After step S2111, the server 30 updates the database (S2130). Specifically, the processor 32 adds a new record to the collaboration information database (FIG. 10) associated with the doctor identification information included in the collaboration request data from the doctor client device 10. The following information is stored in each field of the new record. "Federation ID" field: New federation identification information "Linked Company ID" field: Company identification information included in the link request data - "Block employee ID": Code "N / A" indicating no match

[0164] (6-1-2) Summary of Modification 1 According to Variation 1, in response to a collaboration request from a doctor, the doctor is linked to a company designated by the doctor, and in response to a block request from the doctor, collaboration between the doctor and an employee (e.g., a sales representative) of the company designated by the doctor is blocked. This makes it easier for the doctor to send a collaboration request to the company, even if there are employees at the company who do not want to collaborate. As a result, online communication between doctors and companies can be promoted.

[0165] (7) Other variations Other modifications will be described.

[0166] The storage device 11 may be connected to the doctor client device 10 via a network NW. The storage device 31 may be connected to the server 30 via a network NW. The storage device 51 may be connected to the company client device 50 via a network NW.

[0167] In this embodiment, an example of collaboration between a doctor and a company is shown, but this embodiment is not limited to this. This embodiment can also be applied to an example of collaboration between a medical professional and a company. In this case, the medical professional uses a first client device. The medical professional includes, for example, at least one of the following: ·pharmacist Dentists ·Public health nurse Midwife ·nurse Licensed Practical Nurse Dental hygienist Radiological technologist Dental technician Clinical laboratory technician Sanitary laboratory technician Physical therapist Occupational therapist Orthoptist Clinical Engineer Prosthetist Paramedic Speech-language-hearing therapist Registered dietitian

[0168] Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-described embodiments. Furthermore, the above-described embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-described embodiments and modifications can be combined. [Explanation of symbols]

[0169] 1: Information processing system 10: Doctor client device 11:Storage device 12: Processor 13: Input / output interface 14: Communication interface 30: Server 31:Storage device 32: Processor 33: Input / output interface 34: Communication interface 50: Corporate client device 51:Storage device 52: Processor 53: Input / output interface 54: Communication interface

Claims

1. A server connectable to a first client device used by a doctor or medical professional and a second client device used by a company employee, means for receiving a collaboration request from the second client device; the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; a means for identifying the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request by referring to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated; a means for transmitting to the first client device, in response to the collaboration request, a collaboration application between the collaboration target company and the doctor; means for receiving an approval request from the first client device; the authorization request includes the physician identification information; a means for storing, in response to the approval request, information identifying the doctor or medical professional and company identification information of the partner company in association with each other; means for receiving a block request from the first client device; The block request includes the doctor identification information and employee identification information of the employee to be blocked, and means for storing, in response to the block request, the doctor identification information included in the block request and the employee identification information included in the block request in association with each other as employee identification information of the block employee. server.

2. A server connectable to a first client device used by a doctor or medical professional and a second client device used by a company employee, means for receiving a collaboration request from the first client device; the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; a means for identifying the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request by referring to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated; a means for storing the doctor identification information and the company identification information of the collaboration target company in association with each other in response to the collaboration request; means for receiving a block request from the first client device; The block request includes the doctor identification information and employee identification information of the employee to be blocked, and means for storing, in response to the block request, the doctor identification information included in the block request and the employee identification information included in the block request in association with each other as employee identification information of the block employee. server.

3. The block request includes a block reason; and means for transmitting the reason for blocking to a second client device used by the blocked employee when the employee identification information included in the block request is stored as the employee identification information of the blocked employee. The server according to claim 1 or 2.

4. means for receiving an unblocking request from the first client device; The unblocking request includes the doctor identification information and the employee identification information of the blocked employee; a means for deleting the association of the doctor identification information included in the unblocking request as employee identification information of the blocked employee; The server according to any one of claims 1 to 3.

5. The linkage request includes the administrator's employee identification information. The server according to any one of claims 1 to 4.

6. and means for delivering a message to a first client device used by a doctor or medical professional corresponding to information identifying the doctor or medical professional associated with the company identification information in response to a delivery request from the second client device. The server according to any one of claims 1 to 5.

7. The delivery request includes the manager's employee identification information. The server of claim 6.

8. A program for causing a computer to function as each of the means according to any one of claims 1 to 7.

9. An information processing method using a server connectable to a first client device used by a doctor or medical professional and a second client device used by a company employee, comprising: The method includes a step of receiving a collaboration request from the second client device by the server; the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; the server refers to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated, and identifies the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request; a step in which the server transmits a cooperation request between the cooperation target company and the doctor to the first client device in response to the cooperation request; The server receives an approval request from the first client device; the server stores, in response to the approval request, information identifying the doctor or medical professional and company identification information of the partner company in association with each other; The server receives a block request from the first client device; the server, in response to the block request, associates the doctor identification information included in the block request with the employee identification information included in the block request as employee identification information of the block employee and stores the information; Information processing methods.

10. An information processing method using a server connectable to a first client device used by a doctor or medical professional and a second client device used by a company employee, comprising: The method includes a step of the server receiving a collaboration request from the first client device, the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; a step of referring to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated, and identifying the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request; The server stores, in response to the collaboration request, information identifying the doctor or medical professional and company identification information of the collaboration target company in association with each other; The server receives a block request from the first client device; The block request includes the doctor identification information and employee identification information of the employee to be blocked, the server, in response to the block request, associates the doctor identification information included in the block request with the employee identification information included in the block request as employee identification information of the block employee and stores the information; Information processing methods.

11. An information processing system comprising: a first client device used by a doctor or medical professional; a second client device used by a company employee; and a server, the second client device includes means for transmitting a collaboration request to the server in response to an instruction from the employee; the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; The server means for receiving a collaboration request from the second client device; a means for identifying the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request by referring to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated; a means for transmitting to the first client device, in response to the collaboration request, a collaboration application between the collaboration target company and the doctor; the first client device includes means for transmitting an approval request to the server in accordance with an instruction from the doctor or medical professional; the authorization request includes the physician identification information; The server means for receiving an approval request from the first client device; a means for storing, in response to the approval request, information identifying the doctor or medical professional and company identification information of the partner company in association with each other; the first client device includes means for transmitting a block request to the server in response to an instruction from the doctor or medical professional; The block request includes the doctor identification information and employee identification information of the employee to be blocked, The server means for receiving a block request from the first client device; and means for storing, in response to the block request, the doctor identification information included in the block request and the employee identification information included in the block request in association with each other as employee identification information of the block employee. Information processing system.

12. An information processing system comprising: a first client device used by a doctor or medical professional; a second client device used by a company employee; and a server, the first client device includes means for transmitting a collaboration request to the server in response to an instruction from the employee; the collaboration request includes employee identification information that identifies the employee and doctor identification information that identifies a doctor or medical professional designated by the employee; The server means for receiving a collaboration request from the first client device; a means for identifying the company identification information of the collaboration target company associated with the employee identification information included in the collaboration request by referring to a database in which employee identification information and company identification information identifying the company to which the employee belongs are associated; a means for storing, in response to the collaboration request, information identifying the doctor or medical worker and company identification information of the collaboration target company in association with each other; the first client device includes means for transmitting a block request to the server in response to an instruction from the doctor or medical professional; The block request includes the doctor identification information and employee identification information of the employee to be blocked, The server means for receiving a block request from the first client device; and means for storing, in response to the block request, the doctor identification information included in the block request and the employee identification information included in the block request in association with each other as employee identification information of the block employee. Information processing system.

Images