JP4864669B2 - Marketing support device and data processing method of the device - Google Patents

Description

  The present invention relates to a marketing support apparatus and a data processing method for the apparatus, in which a sales person registered for a customer can provide information by selectively registering the sales person.

  Patent Document 1 discloses an MR support system that supports communication between medical representatives (MRs) who belong to pharmaceutical companies and medical personnel related to hospitals such as doctors, pharmacists, and nurses. Is described. The MR support system includes a support server device that supports one-to-one communication between a medical staff and an MR that has been approved by the medical staff. If the registered MR is registered, a message can be created for the registered medical personnel, and medical information can be provided to the medical personnel through this message.

Japanese Patent No. 3643831

  Here, in the system disclosed in Patent Document 1, MRs that can exchange messages with medical personnel are only MRs of members who belong to a pharmaceutical company or the like that is a member. The MR to which he belongs cannot exchange messages with medical personnel using this system.

  From the viewpoint of medical personnel, it is preferable that information can be exchanged by exchanging messages with a larger number of MRs regardless of the MRs of member companies and MRs of non-member companies. . In addition, since the system of Patent Document 1 can smoothly exchange information without actually meeting a medical person, it is preferable that MRs belonging to non-member companies can also be used.

  However, Patent Literature 1 does not show the concept that MRs belonging to non-member companies use the system of Patent Literature 1.

  Further, when MRs belonging to non-member companies can be used by various terminal devices when MRs belonging to non-member companies can be used in the system of Patent Document 1, the system can be used. There is a possibility that a person other than the MR permitted to use the system may use the system, and in some cases, the system may be misused by an unskilled person.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to provide a marketing support apparatus that enables a sales representative other than a member to exchange messages with a customer, and a data processing method of the apparatus. Is to provide.

  Another object of the present invention is to provide a marketing support apparatus and a data processing method for this apparatus that can prevent the abuse of non-member sales representatives.

  Furthermore, another object of the present invention is to provide a computer program capable of realizing the above object and a recording medium on which the computer program is recorded.

The marketing support apparatus according to the present invention includes a customer database storing a customer table into which customer personal data is input, a member sales representative table provided for each member sales representative, the customer table, and the member sales. A member database for storing a member selective registration table associated with the person-in-charge table, a non-member sales person table provided for each non-member sales person, the customer table, and the non-member sales person table. A non-member database for storing a non-member selective registration table for associating; a predetermined customer table for associating the predetermined customer table with the member sales representative table; and the predetermined customer table The above selection registration table for non-members that associates with the non-member sales representative table The registered registration section, the message sent to the customer from the member sales representative or the non-member sales representative, and the member sales representative sent from the customer to the member sales representative or the non-member sales representative. A message database holding messages addressed to a person or a non-member sales representative, and a member sales representative terminal device supporting the creation of the message addressed to the customer, receiving a first format message, and receiving the received first format message The member sales message is stored in the message database, and the member sales representative message created by the customer is read from the message database and transmitted to the member sales representative terminal device in the first format. The message interface to the customer from the message interface on the person-in-charge side and the non-member sales representative terminal A non-member sales representative side message interface that accepts a sage in a second format and transmits the non-member sales representative message created by the customer to the non-member sales representative terminal device in a second format; The message addressed to the customer in the second format received by the non-member sales representative side message interface is converted into the first format and stored in the message database, and the non-member sales representative created by the customer A message conversion unit for converting the addressed message from the first format to the second format and transmitting the message to the non-member sales representative terminal device from the non-member sales representative side message interface; and the member sales representative Read the message to the customer created by the person or the non-member sales representative from the message database And sending to the customer terminal device in the first format, and supporting the creation of a message addressed to the member sales representative or the non-member sales representative in the customer terminal device, and accepting the message in the first format, A message interface in the second format is stored between the message interface stored in the message database and the message interface for the non-member sales representative and the non-member sales representative terminal device individually for the customer. Address issuer that issues customer addresses for exchanges and issuance and management of invitations from the customers to the non-member sales representatives, and the registration of the non-member sales representatives for a single customer exceeds a predetermined number And an invitation management unit for refusing registration in the non-member sales staff table .

In the data processing method using the marketing support apparatus as described above, the member sales representative side message interface supports the creation of the message addressed to the customer in the member sales representative terminal apparatus, and the first form of the customer Receiving a message addressed to the customer, storing the received message addressed to the customer in the first format in the message database, and reading the message addressed to the customer created by the member sales representative from the message database on the customer side message interface. , Sending to the customer terminal device in the first format, and supporting the creation of the message addressed to the member sales staff at the customer terminal device at the customer side message interface, accepting the message in the first format, Storing in the above message database; Membership salesperson side message interface, and a step of transmitting the membership salesperson addressed message the customer created the member salesperson terminal device in the first format is read out from the message database.
In addition, after the address issuing unit has issued the customer address, the invitation management unit includes a web page address for non-member salesperson registration addressed to the nonmember salesperson address acquired from the customer. Generating an invitation e-mail in the second format and sending it to the non-member sales representative terminal device from the non-member sales representative side message interface; and the non-member sales representative registration web page When the registration of the member sales representative is completed, the selective registration unit generates the non-member selective registration table associating the customer address with the non-member sales representative address; when a member salesperson registration exceeds a predetermined number, and the step to deny registration to the salesperson table for non-members, the non-member sales representative Accepting the message addressed to the customer from the non-member sales representative terminal device in the second format at the side message interface, and accepting the message addressed to the customer in the second format at the message conversion unit in the second format Converting the format from the above format into the first format and storing it in the message database; reading out the message addressed to the customer created by the non-member sales representative from the message database using the customer side message interface; Transmitting to the device in the first format, and supporting the creation of the message addressed to the non-member sales representative at the customer terminal device at the customer-side message interface, accepting the message in the first format, and the message database And the above-mentioned non-description created by the customer The message for the sales staff member is converted from the first format to the second format, and the message interface for the non-member sales staff is sent to the non-member sales staff who has been converted to the second format. Transmitting a message to the non-member sales representative terminal device.

  The data processing method as described above can be realized by hardware, but can also be realized by installing a computer program on a computer such as a server. This computer program is stored and expanded via a network or a recording medium such as an optical disk.

  Here, in the present invention configured as described above, for example, the first format is a format for exchanging messages on a web page, and the second format is a format for exchanging messages using e-mail. It is a form to exchange.

  Further, an address for individually issuing a customer address for exchanging the message in the second format between the non-member sales representative side message interface and the non-member sales representative terminal device. An issuing unit may be provided. In this case, the selection registration unit generates the non-member selection registration table in which the customer address is associated with the non-member sales representative address of the non-member sales representative, and the non-member sales representative side message interface Accepts the message addressed to the customer with the issued customer address as the destination, and uses the non-member sales representative address associated with the customer address in the non-member selection registration table as the destination. Send a message to the sales representative. Here, for example, in the non-member selection / registration table, the customer address and the non-member sales representative address are associated one-to-one.

Moreover, the said invitation management part refuses registration to the non-member sales staff table when the registration from the said non-member sales staff exceeds the predetermined number with respect to one customer. Furthermore, the received communication content confirmation page for confirming the message from the member sales representative or the non-member sales representative provided by the customer-side message interface to the customer terminal device displays the message from the non-member sales representative. When the message is displayed, it may be further notified that there is an unread message from the member sales representative.

  Furthermore, a billing processing unit for the non-member sales representative may be provided. In this case, the billing processing unit determines the amount to be billed according to the number of customers associated with the non-member selection registration table.

According to the present invention, by providing the non-member sales person side message interface and the message conversion unit, the customer can exchange messages with the non-member sales person. Sales representatives can also exchange messages with customers, improving convenience. At this time, by limiting the number of non-member sales representatives associated with one customer as a predetermined number, it is possible to prevent an excessive number of messages that need to be converted between the first format and the second format, It is possible to prevent the system from being overloaded.

  Hereinafter, a support system to which the present invention is applied will be described with reference to the drawings. As shown in FIG. 1, the support system provides content to a terminal device for medical personnel via a network 3 such as the Internet, and MRs who are medical information personnel of pharmaceutical companies such as pharmaceuticals and this MR The medical staff in charge can exchange messages on a one-to-one basis.

  Specifically, as shown in FIG. 1, a support system to which the present invention is applied includes a support server device 1 managed by an operator of the system in which a database 2 for storing various information is constructed, a doctor, a pharmacist, and nursing A medical personnel terminal device 4 managed by a medical personnel such as a woman, a radiographer, and the like, and a plurality of member MR terminal devices 5 managed by member MR individuals belonging to a member pharmaceutical company participating in the system A non-member MR terminal device 6 managed by a non-member MR belonging to a non-member pharmaceutical company not participating in the system, and an administrator terminal device for the administrator of the system to access the support server device 1 7. The support server device 1, the medical staff terminal device 4, the member MR terminal device 5, the non-member MR terminal device 6, and the administrator terminal device 7 are connected to each other with an ISDN (Integrated Services Digital Network) line, a CATV (Cable Television) line, Connected via a network 3 using an optical cable line, xDSL (x Digital Subscriber Line), satellite line for digital satellite broadcasting, etc., TCP / IP (Transmission Control Protocol / Internet Protocol), FTP (File Transfer Protocol), etc. Data can be exchanged according to the transmission protocol.

  The support server device 1 has substantially the same configuration as that of a normal computer. The database 2 is stored in the hard disk, and various programs such as an operating system and application programs for communicating with the terminal devices 4 to 7 are used. The program is installed. This support server device 1 registers all medical personnel participating in the system in the database 2, and medical members whose member MRs belonging to each pharmaceutical company participating in the system are registered in the database 2. Upon receiving approval from a related person, the member MR in charge is associated with the approved medical person, and the approved medical person is positioned as the member MR and the customer of the pharmaceutical company to which the member MR belongs and approved. Messages can be exchanged between medical personnel and member MRs.

  In addition, even if this support server device 1 is a non-member MR belonging to a non-member pharmaceutical company that does not participate in the system, it receives an invitation from a medical person registered in the system and registers it in the system. The non-member MR is associated with the invited medical person, and the invited medical person is positioned as a customer of the non-member MR. Then, the non-member MR can exchange messages with the approved medical staff using general-purpose electronic mail software, that is, a mailer. At this time, when the support server device 1 accepts an invitation request for a non-member MR to participate in the system from a medical staff, the support server device 1 sends a normal e-mail to the non-member MR based on the invitation request. Send invitations with the system.

  This support server device 1 provides information such as medical information and academic society information to the medical personnel terminal device 4 as content in response to access from the medical personnel terminal device 4 used by the medical personnel. It manages the mutual message exchange between the medical personnel terminal device 4 of the parties concerned, the member MR terminal device 5, the non-member MR terminal device 6, and the administrator terminal device 7.

  As shown in FIG. 1, a medical personnel terminal device 4 connected to the support server device 1 via a network 3 is a terminal device operated by a medical personnel. The application program is installed. The medical staff terminal device 4 can communicate with the support server device 1 by executing a WWW (World Wide Web) browser. Specifically, the medical-related person terminal device 4 executes a browser, thereby enabling the support server device 1 or a pharmaceutical company server device such as a pharmaceutical to open a medicine, a medical device (hereinafter also simply referred to as a medicine), or the like. You can browse web pages related to research and development. Further, the medical staff terminal device 4 exchanges messages with the member MR terminal device 5, the non-member MR terminal device 6, and the administrator terminal device 7 on the web page of the support server device 1, that is, This can be done in one form.

  The member MR terminal device 5 connected to the support server device 1 via the network 3 is constituted by an information processing device such as a personal computer operated by the member MR, and various application programs such as a browser are installed. When the member MR terminal device 5 receives the approval from the medical personnel who is the customer by executing the WWW browser, the medical MR terminal device 4 managed by the medical personnel on the web page is triggered by this approval. Messages can be exchanged in the first format.

  A non-member MR terminal device 6 connected to the support server device 1 via the network 3 is a terminal device operated by a non-member MR belonging to a non-member pharmaceutical company that does not participate in the system, such as a personal computer. Various application programs such as a browser for browsing web pages and a mailer for sending and receiving e-mails are installed. The non-member MR terminal device 6 uses a general-purpose mailer to manage medical care managed by a medical person when a non-member MR receives an invitation from a medical person to participate in the system and displays an intention to participate. Messages can be exchanged with the party terminal device 4 in the second format using a normal electronic mail system.

  The administrator terminal device 7 connected to the support server device 1 via the network 3 is an information processing device such as a personal computer operated by an administrator who operates this system. The administrator terminal device 7 can communicate with the support server device 1 by executing a WWW browser.

  The medical personnel, the member MR, and the administrator of the administrator terminal device 7 receive services from the support server device 1 by logging in to the support server device 1 by entering the medical personnel ID and password, respectively. Can do. The support server device 1 functions as a portal site for medical personnel with respect to medical personnel. Further, as will be described later, the support server device 1 has a member MR and a non-member MR in a first format for medical personnel. A user interface for exchanging messages is provided, and a user interface for exchanging messages with medical personnel is provided to the member MR. Further, the support server device 1 does not provide a non-member MR with the same user interface as the member MR, and the non-member MR sends a message to the medical staff in the second format using a general-purpose mailer. You will send and receive messages from medical personnel. Therefore, the support server device 1 exchanges messages on a web page (first format) and exchanges messages using a general-purpose mailer (second format) between non-member MRs. Therefore, it has a function of converting the message format from the first format to the second format and a function of converting from the second format to the first format.

  An operator who operates the support server device 1 obtains a profit by collecting a usage fee from a pharmaceutical company to which a member MR who has signed a use contract of the support system belongs, using a flat rate system, a pay-per-use system, or a combination thereof. For example, in addition to the basic fee, the operator charges in accordance with the number of messages transmitted by the member MR and the number of times the medical staff has opened the message. The support server device 1 manages, for example, the use status of MR and generates billing data according to this. The support server device 1 is connected to a settlement center via a dedicated line, generates billing data in units of a predetermined period such as a monthly pole, and performs settlement processing by transmitting the billing data to the settlement center. In addition to the basic fee, the operator will charge the non-member MR according to the number of medical personnel who have approved the non-member MR. Billing data is generated according to and payment is made. The non-member MR does not participate in the system in units of companies, but participates in the system in units of individuals, so that credit settlement or the like is used as the settlement method.

  In addition to this, the operator can also obtain an advertisement fee income from a banner advertisement provided on the homepage. Further, the support system may charge the information provider fee to the medical staff to be used.

  Next, a procedure until medical personnel use the support system will be described. The support server device 1 has a function as a portal site that provides content for medical personnel. When the medical personnel inputs his / her medical personnel ID and password and logs in to the support server device 1, medical information customized for the medical personnel is displayed on the browser screen. Further, the medical staff is registered by obtaining the MR ID from the member MR of the pharmaceutical company of the member contracted with the operator of the support server device 1 and registering the service code in the support server device 1. It is also possible to browse medical information distributed in a limited manner from a pharmaceutical company or an MR belonging to that company. In addition to information as a portal site, message guidance from members and non-member MRs is displayed on the browser screen, and one-to-one communication with members and non-member MRs is possible based on this guidance. .

  On the other hand, a member MR of a pharmaceutical company that is a member of a pharmaceutical company who uses the support system for business activities for medical personnel notifies the medical personnel of his / her own ID and his / her member MRID, and encourages the use of the support system. When a medical personnel registers a member MRID in the support server device 1 in order to approve the member MR, the medical personnel can receive a message from the member MR and send a message to the member MR. It becomes.

  In order for the medical staff to exchange messages with the non-member MR, the non-member MR who has received the invitation sent by the medical staff via the administrator can start by registering in the system.

  FIG. 2 is a functional configuration diagram of the support server device 1. This functional configuration can be realized in terms of hardware by a CPU (Central Processing Unit), RAM (Random Access Memory), hard disk, etc., and realized by an application program with a support function installed on the hard disk. Is done. Therefore, these functional blocks can be realized in various forms by a combination of hardware and software.

  As shown in FIG. 2, the support server device 1 has a member MR side message interface 11 (hereinafter also simply referred to as a member MR side message I / F 11) that supports the creation of a message on the member MR terminal device 5 side. Supports non-member MR message interface 12 (hereinafter also simply referred to as non-member MR message I / F 12) for exchanging messages with the non-member MR terminal device 6 and the creation of messages on the medical staff side. A medical person side message interface 13 (hereinafter also simply referred to as a medical person side message I / F 13), a selection registration unit 14 for accepting registration of medical persons, member MRs, and non-member MRs, and member MRs. A member MR database 15 in which personal data is input and data relating member MRs and medical personnel is stored; A non-member MR database 16 in which data relating MR and medical personnel are stored, a medical personnel database 17 in which personal data of medical personnel are input, and between member and non-member MRs and medical personnel A message database 18 for managing messages, an address issuing unit 27 for issuing mail addresses of medical personnel when exchanging messages between non-member MRs and medical personnel, and medical personnel to non-member MRs Conversion between an invitation management unit 19 that manages invitations for participation in the system, and a first format for exchanging messages on a web page and a second format for exchanging messages via e-mail. It includes a message conversion unit 20 that performs processing, and a charging processing unit 26 that generates charging data for MRs of members and non-members. The member MR database 15, the medical staff database 17, and the message database 18 are shown as the database 2 in FIG. 1, and are stored in a hard disk or the like.

  The member MR database 15 includes a member MR table 21 in which personal information of the member MR is stored, and a member MR selection registration table 22 that associates medical personnel with the member MR. The non-member MR database 16 includes a non-member MR table 23 in which personal information of non-member MRs is stored, and a non-member MR selection registration table 24 that associates medical personnel with non-member MRs. Furthermore, the medical staff database 17 has a medical staff table 25 in which personal data of medical staff is stored.

  The selection registration unit 14 receives input of a member MRID that is an identification code of the member MR from the medical staff terminal device 4 of the medical staff. The selection registration unit 14 extracts the medical personnel table 25 identified by the medical personnel ID of the medical personnel from the medical personnel database 17 and also extracts the member MR table 21 identified by the member MRID from the member MR database 15. The member MR selection registration table 22 is generated by extracting and associating the medical staff table 25 and the member MR table 21. When the member MR selection registration table 22 is generated, the member MR identified by the member MRID is registered with the medical personnel identified by the medical personnel ID, and the registered member MR is the medical member. It becomes possible to take charge of related parties as customers. The member MR-side message I / F 11 enables a message to be transmitted from the member MR to the medical staff when the member MR selection registration table 22 is generated.

  Further, when the selection registration unit 14 receives an acceptance signal for participation in this system from the non-member MR terminal device 6 of the non-member MR, it generates a non-member MR table 23 in which personal data of the non-member MR is recorded. The non-member MR table 23 is stored in the non-member MR database 16 and a non-member MR selective registration table 24 that associates the medical staff table 25 with the non-member MR table 23 is generated. When the non-member MR selection registration table 24 is generated, the non-member MR is registered with the medical staff identified by the medical staff ID, and the registered non-member MR selects the medical staff. It becomes possible to take charge as a customer. The non-member MR message I / F 12 enables a message to be transmitted from the non-member MR to the medical staff with the generation of the non-member MR selective registration table 24 as a trigger.

  The member MR side message I / F 11 supports the member MR so that the message transmitted from the member MR to the medical staff can be created, deleted, stored, and the message received from the medical staff can be viewed, deleted, stored, and the like. It is a user interface. That is, the member MR side message I / F 11 can create a message for a medical person on the web page and can browse a message transmitted from the medical person. That is, the member MR side message I / F 11 supports the creation and browsing of messages so that the member MR can exchange messages of the first format on the web page.

  The non-member MR side message I / F 12 can browse a list of messages transmitted from medical personnel, and from this, in order to create a reply message to the medical personnel, the non-member MR terminal device 6 This is a user interface that supports the non-member MR. That is, the non-member MR side message I / F 12 can see a list of messages from medical personnel on the web page, and by clicking on the desired message, the mailer is activated and the content of the corresponding message is displayed. You can browse and create a reply to the viewed message. That is, the non-member MR message I / F 12 supports message creation and browsing so that the non-member MR can exchange messages in the second format using a mailer.

  The medical person side message I / F 13 is a message that a medical person who is a user browses, deletes, stores, etc. a message received from a member or non-member MR and a message that a medical person sends to a member or non-member MR. It is a user interface that supports medical personnel who can create, delete, save, and the like. The medical personnel side message I / F 13 reads a message from a member database or a non-member MR registered and approved by the medical personnel from the message database 18 and provides the message to the medical personnel terminal 4 of the medical personnel.

  The message database 18 is a single database that manages messages created by member or non-member MRs and medical personnel. In this respect, the message exchange performed in the support system is different from a mechanism in which mail data is delivered from a transmission source server to a transmission destination server like a normal electronic mail.

  FIG. 3 is a diagram for explaining the data structures of the member MR table 21, the member MR selection / registration table 22, and the medical staff table 25 and the correlation between them. The member MR table 21 provided in the member MR database 15 is uniquely identified by the member MRID, and includes the name of the member MR, the user name and password for the member MR to access the support server device 1, the telephone number of the member MR, etc. Stores data. This member MR table 21 is provided for each member company by the number of MRs registered by the company.

  The medical personnel table 25 provided in the medical personnel database 17 is uniquely identified by the medical personnel ID, and the name of the medical personnel, the name of the medical institution where the medical personnel works, and the medical personnel for accessing the support server device 1. A user name and password, a telephone number of a medical person, an e-mail address for exchanging e-mails with a non-member MR, a specialty of a medical person, and the like are stored. As many medical personnel tables 25 as the number of medical personnel registered in the present system are provided.

  The member MR selection registration table 22 provided in the member MR database 15 associates the medical personnel table 25 of the medical personnel with the member MR table 21 when the medical personnel registers and approves the member MR. Yes, generated by the selective registration unit 14 and uniquely identified by the member MRID of the member MR table 21 and the medical personnel ID of the medical personnel table 25. The member MR selection registration table 22 stores the names of medical personnel, names of medical institutions where they work, specialties of medical personnel, and the like. The member registration / registration table 22 is provided only upon approval from medical personnel, and the member MR selection / registration table 22 performs user registration for the administrator who operates the system. It will be provided for all medical personnel working.

FIG. 4 is a diagram for explaining the data structure of the non-member MR table 23, the non-member MR selection registration table 24, and the medical staff table 25 and the correlation between them. The non-member MR table 23 provided in the non-member MR database 16 is uniquely identified by the non-member MR ID. The name of the non-member MR, the user name and password for the non-member MR to access the support server device 1, the non-member MR Data such as an MR telephone number and an e-mail address for exchanging messages with medical personnel are stored. Here, the non-member MR table 23 may allow only one e-mail address to be registered and uniquely identify the e-mail address in order to prevent abuse of the e-mail address. Then, as many non-member MR tables 23 as the number of non-member MRs registered in this system are provided. The non-member MR table 23 stores a credit card number, a bank account number, etc. for personal settlement in order to charge the non-member MR individual.

The non-member MR selection / registration table 24 provided in the non-member MR database 16 includes a medical person table 25 and a non-member MR table of medical persons when a non-member MR invited by a medical person registers in this system. 23, is generated by the selective registration unit 14, and is uniquely identified by the non-member MRID of the non-member MR table 23 and the medical staff ID of the medical staff table 25. The non-member MR selection / registration table 24 stores the names of medical personnel, names of medical institutions where they work, specialties of medical personnel, etc., and also exchanges emails with non-member MRs of medical personnel. And an e-mail address for exchanging messages with non-member MR medical personnel are stored in a one-to-one relationship. The number of non-member MR selection registration tables 24 is provided when one non-member MR is registered with a plurality of medical personnel. Here, the number of non-member MR email addresses to be registered is one here for prevention of misuse, but a plurality of non-member MR email addresses may be registered.

  As shown in FIG. 2, the message database 18 uniquely identifies and manages a message by a message header ID, and further associates this ID with the message content, sender, recipient, transmission date / time, reception date / time, message It manages the presence / absence of opening, date of deletion, etc.

  As shown in FIG. 2, the address issuing unit 27 exchanges messages with non-member MRs when medical personnel wish to exchange messages with non-member MRs using this system. The e-mail address for the medical staff is issued and stored in the medical staff table 25 of the medical staff database 17.

  When a medical staff wishes to exchange a message with a non-member MR, the invitation manager 19 issues an invitation to the non-member MR and transmits it to the non-member MR by e-mail. In addition, when an invitation is sent out as a printed matter, an empty mail from the non-member MR is accepted and encouraged to participate in this system. Furthermore, in this system, the number of non-member MRs that can be invited by one medical staff is a predetermined number, here seven. When the predetermined number is reached, the registration application from the non-member MR is rejected. Like that.

  The message conversion unit 20 performs conversion processing between a first format for exchanging messages on a web page and a second format for exchanging messages by e-mail. That is, the member MR side message I / F 11 and the medical staff side message I / F 13 provide an interface for exchanging messages on a web page, and the non-member MR side message I / F 12 is a normal one. Messages are exchanged using electronic mail. Therefore, when the message conversion unit 20 receives a message addressed to a medical staff from the non-member MR terminal device 6, the message conversion unit 20 exchanges a message in the second format, which is a normal e-mail format, on the web page. The message is converted into one format message and stored in the message database 18, and the message is provided to the medical staff terminal device 4 in the first format. Further, when transmitting a message addressed to the non-member MR to the non-member MR terminal device 6, the message conversion unit 20 converts the message in the first format into the second format which is a normal electronic mail format, The message is transmitted to the non-member MR terminal device 6 from the MR message I / F 12.

  The billing processing unit 26 accesses the member MR database 15 and the message database 18, and in addition to the basic fee for the member company, the number of messages sent by the member MR and the number of times the medical staff opened the message. The billing data is generated accordingly. Further, the billing processing unit 26 accesses the non-member MR database 15 and, for the non-member MR, in addition to the basic fee, the number of medical personnel related to the non-member MR, that is, the non-member MR selection Billing data corresponding to the number of registration tables 24 is generated. The method of generating billing data for member companies, member MRs, and non-member MRs is not limited to this. For example, the medical staff may be charged.

  The above is the overall configuration of the support system, and the processing will be specifically described below. First, a procedure when a medical person registers with the support server apparatus 1 using the medical person terminal device 4 will be described with reference to FIG. This process is started when the support server device 1 detects an access from the medical staff terminal device 4.

  The support server device 1 transmits a login screen for prompting the medical personnel ID and password to be input to the medical personnel terminal device 4 via the network 3 (step S1). On the login screen displayed on the monitor of the medical staff terminal device 4, a medical staff ID and password input field, a send button for instructing transmission of the entered medical staff ID, etc. and notification that the user is an unregistered user are notified. A notification button or the like is provided. When a medical person who operates the medical person terminal device 4 is a registered user, the medical person ID and password are displayed on the monitor by using an operation unit such as a keyboard and a mouse. Fill in the input field on the screen and click the send button. When the user is an unregistered user, the user uses the operation unit to click a notification button on the login screen. The medical staff terminal device 4 transmits the input medical staff ID and password or unregistered user notification to the support server device 1 via the network 3 when either the send button or the notification button is clicked. .

  When receiving the medical personnel ID and password or the unregistered user notification from the medical personnel terminal device 4, the support server device 1 in the reception standby state receives the medical personnel ID and password, and when receiving the medical personnel ID and password, the medical personnel table 25 It is determined whether or not the medical staff who has applied for is a legitimate medical staff by collating with the profile of the medical staff recorded in the table. (Step S2). When the support server device 1 determines that the medical personnel ID and password are not legitimate (NG in step S2), the support server device 1 returns to step S1 and logs in again to the accessed medical personnel terminal device 4. Send.

  When receiving the unregistered user notification from the medical staff terminal device 4 (No in step S2), the support server device 1 determines that the medical staff who accessed through the medical staff terminal device 4 is unregistered. In step S3, a user registration screen is transmitted to the medical staff terminal device 4 via the network 3 in order to prompt the medical staff to perform user registration (step S3).

  The medical personnel registration screen displayed on the monitor of the medical personnel terminal device 4 is obtained from the MR in addition to the medical personnel ID and password input fields where the medical personnel can set arbitrary characters and numbers. There are provided input fields for the member MRID, name, gender, date of birth, occupation, specialized department, work location and the like, and a send button for instructing transmission of the entered medical personnel ID and the like. Here, the column of occupation type is for entering occupational categories such as physicians, practitioners, nurses, pharmacists, and clinical technologists, and the column of specialized departments is for entering specialties such as internal medicine and surgery. is there. The medical personnel inputs the medical personnel ID, password, member MRID, etc. using the operation unit to the predetermined entry field of the medical personnel registration screen displayed on the medical personnel terminal device 4, and the transmission button is clicked. Then, the medical staff terminal device 4 transmits personal data such as a medical staff ID, a password, and a member MRID input via the network 3 to the support server device 1.

  The support server device 1 stores, that is, registers the medical personnel ID and the like from the medical personnel terminal device 4 in the medical personnel table 25 of the medical personnel database 17 as the profile of the medical personnel. Thereby, the medical staff of the medical staff terminal device 4 becomes a registered medical staff in this system. In addition, the support server device 1 provides authentication information indicating that the medical staff of the medical staff terminal device 4 is a registered user to the medical staff terminal device 4 operated by a registered medical staff. Issue. The issued authentication information is transmitted to the medical staff terminal device 4 and stored in a hard disk or the like of the medical staff terminal device 4. As an example of such authentication information, a cookie can be used. Further, the support server device 1 records the issued authentication information in the medical staff table 25 in association with the profile of the medical staff.

  After the user registration, the user registers the member MRID of the member MR that exchanges messages in the user-specific designation form managed by the support server device 1 (step S4). A plurality of MRIDs can be registered in this designation form. The medical staff can receive only the message transmitted by the member MR who has registered the member MRID in the designated form. That is, the member MR cannot send a message to the medical personnel because the member MR selection registration table 22 is not generated unless the medical personnel register the member MRID in the designated form. . Therefore, the medical staff can prevent an unintended message from the member MR from being transmitted by not registering the member MRID of the desired form.

  Such a medical person can register a desired member MRID and approve the member MR indicated by the ID, thereby establishing a one-to-one communication channel with the member MR. Further, when viewed from the member MR, marketing (so-called permission marketing) performed with the permission of the customer, that is, the medical staff, can be performed by having the medical staff register the member MRID. A user who has registered in the system can add, change, or delete user registration contents, cancel user registration, and add or delete MRIDs as needed from the medical staff terminal device 4.

  In step S <b> 2, the support server device 1 receives the medical staff ID and password transmitted from the medical staff terminal device 4, compares the profile with the profile recorded in the medical staff table 25, and is accessed. When it is determined that the medical person is a regular user (Yes in step S2), it is determined that the medical person is already registered, and the process of step S3 is skipped.

  Next, the support server device 1 reads the profile of the medical staff from the medical staff table 25 of the medical staff database 17 and provides the medical staff terminal device 4 with the content for the medical staff based on this. Then, a message from the member MR is provided to the medical staff terminal device 4 (step S6). The medical staff terminal device 4 that has received these data via the network 3 displays the content transmitted from the support server device 1 on the monitor and prompts the user to communicate with the member MR approved by the user. I do. The medical staff terminal device 4 operated by the medical staff logs out from the support server device 1 (step S7), and ends the series of processes. The support server device 1 is accessed by the medical staff terminal device 4 using a browser. Therefore, without prompting the medical staff terminal device 4 to log out, the session is automatically closed with a timeout. You may make it do.

  In addition, the medical staff who has completed the registration as described above can communicate with the member MR and can perform the same communication as the non-member MR invited by himself / herself.

  Next, with reference to FIG. 6, a series of procedures from when a medical staff invites a non-member MR to the system until the invited non-member MR registers in the system will be described.

  First, in step S11, the support server device 1 uses the address issuing unit 27 to register a non-member MR and a message when a medical person is registered in the medical person database 17 or by an intention display from the medical person. An e-mail address for exchange is issued, and the issued e-mail address is stored in the medical staff table 25 of the issued medical staff.

  In step S <b> 12, the medical staff terminal device 4 transmits to the support server device 1 a list of seven non-member MRs invited to this system. Here, the non-member MR list transmitted by the medical staff terminal device 4 includes contact data such as the name, company, telephone number, address, and e-mail address of the non-member MR. Here, in consideration of non-member MRs who are not registered, a list of eight or more persons may be used. When the support server device 1 receives the list of non-member MRs to be invited to this system by the medical staff side message I / F 13, the support server device 1 manages this by the invitation management unit 19. Based on this, an invitation for encouraging non-member MR to participate in the system is generated. Specifically, the invitation manager 19 generates invitation mails for printing and e-mail.

  Here, as shown in FIG. 7A, the print invitation e-mail is a dedicated e-mail address issued to the medical staff who issues the invitation “xxxxx@dr.m3. com "is printed, and the non-member MR that has received the invitation by mail or handing over the e-mail address can access the support server device 1 with the non-member MR terminal device 6 managed by the non-member MR. 7 may be sent from the medical staff I / F 13 of the support server device 1 to the medical staff terminal device 4 and printed by the medical staff. Further, the administrator of this system may send the printed matter for distribution to the medical staff by mail or the like.

  In addition, as shown in FIG. 8, the invitation mail for e-mail includes a message from the teacher XXX and a registration button 31 is provided. When sending the invitation to the non-member MR by e-mail, the support server device 1 generates the invitation shown in FIG. 8 in the text format or the HTML format, and the non-member MR terminal device 6 from the non-member MR side message I / F 12. To send to.

  In step S13, the non-member MR receives an invitation for printing by handing or mailing from a medical staff. In step S14, the non-member MR activates the mailer of the non-member MR terminal device 6 managed by the non-member MR and sends a dedicated e-mail. Address An empty mail with no body is sent to “xxxxx@dr.m3.com” in FIG.

  When the support server device 1 receives this second form of empty mail with the non-member MR side message I / F 12, the invitation management unit 19 then sends a reply to the empty mail from the non-member MR as shown in FIG. As shown in (B), in step S15, the non-member MR side message I / F 12 is transmitted in the second format as an e-mail having the registration button 32. Here, the link destination address of the registration button 31 of the invitation mail for email shown in FIG. 8 is the same as the link destination address of the registration button 32 included in the reply message to the empty mail shown in FIG. This is the web page address for non-member MR registration established in the support server device 1.

  In step S16, the non-member MR who has received the invitation mail for e-mail clicks the registration button 31 on the operation unit of the non-member MR terminal device 6, or in step S17, the registration button included in the reply message for the empty mail When 32 is clicked on the operation unit of the non-member MR terminal device 6, the non-member MR terminal device 6 accesses a web page address for non-member MR registration.

  In step S <b> 18, when the non-member MR terminal device 6 inputs a predetermined registration item and clicks a registration button, the registration item is transmitted to the support server device 1. Here, the items input by the non-member MR are information stored in the non-member MR table 23 of the non-member MR database 16 and include the name, telephone number, credit card number for settlement, Bank account number etc. In the support server device 1, in step S19, the selective registration unit 14 performs a non-member MR registration process. Specifically, in the support server device 1, the selective registration unit 14 generates a non-member MR selective registration table 24 for associating medical personnel with non-member MRs, stores the table in the non-member MR database 16, and registers by this. Complete the process. Here, the selective registration unit 14 extracts the e-mail address of the non-member MR for exchanging messages with medical personnel, for example, from the received empty mail, and the e-mail described in the registration items The selective registration unit 14 stores the address in the non-member MR table 23 and associates it with the e-mail address assigned to the medical staff in the non-member MR selective registration table 24. For example, the user name, the issued password, etc. are transmitted to the non-member MR terminal device 6. In step S <b> 20, in the support server device 1, the billing processing unit 26 executes billing processing for the non-member MR registered at the monthly pole or the like.

  In addition, the invitation management unit 19 determines whether a non-member MR has reached a predetermined number, for example, 7 for one medical staff during the registration process. From the eighth person, registration refusal processing is performed.

  In step S <b> 21, the support server device 1 generates a notification of registration completion of the invited non-member MR with respect to the use related person who has issued the invitation by the invitation management unit 19, and the medical person side message I / The information is transmitted to the medical staff terminal device 4 from F13 to inform the user that the user who issued the invitation has completed registration. In step S22, the support server device 1 allows the registered non-member MR to view the web page of the system and exchanges messages with related medical personnel. Like that.

  As shown above, the non-member MR who has registered in the system as described above inputs the user name and password to the login screen on the web page and transmits them to the support server device 1 as shown in FIG. You can enter the top page. In the top page shown in FIG. 10, the exchange status of each customer of the non-member MR can be confirmed in a list, and can be confirmed on the non-member MR terminal device 5 on the web page.

  This top page displays a list of medical personnel associated with each non-member MR, and is assigned to a medical personnel name such as a doctor, a hospital name, and a medical personnel for each medical personnel. E-mail address, contact frequency, exchange ranking, etc. are displayed.

  In the non-member MR terminal device 5, when a message is transmitted to a desired medical person in the top page, if an e-mail address assigned to the medical person is clicked by the operation unit, a general-purpose MR terminal device 5 As shown in FIG. 11, the mailer is activated, and a new mail creation window in which the clicked e-mail address is input is displayed at the destination. Then, the non-member MR inputs a message to the activated new mail creation window using the operation unit, in the same manner as the creation of a normal electronic mail.

Then, as shown in FIG. 9, when the send button 33 in the new mail creation window is clicked, the non-member MR terminal device 5 supports in the normal e-mail format, that is, the second format in step S31. It transmits to the server device 1. Support server device 1, a non-member MR e-mail transmitted from the terminal device 5 in the second form, when received by the non-member MR side message I / F12, in step S 32, the message converter 20, the first In step S33, this is stored in the message database 18 for centralized management.

  In step S34, the medical staff accesses the predetermined address of the support server apparatus 1 with the medical staff terminal device 4, selects an unread message from the reception list page, and receives the message as shown in FIG. Download the contact confirmation page. The reception list page for medical personnel provides a common interface without distinguishing between messages from member MRs and messages from non-member MRs. In the example of FIG. This shows a state where Mr. XXXXX is selected from AAA Pharmaceutical Co., Ltd. On the received communication content confirmation page shown in FIG. 12, the company and name of the selected non-member MR are displayed in the upper column, and the title and text of the message are displayed in the lower column. A question button 34 for replying to the message and a delete button 35 for deleting the message are provided.

  Further, the right column in FIG. 12 is a member MR display unit 36 for notifying that there is an unread message from the member MR. For example, by clicking the icon in this column, the message of the member MR is received. You can move to the content confirmation page.

  As described above, in the received content confirmation page for medical personnel, the member MR and the non-member MR can be displayed separately on the same screen, but the medical personnel do not make a mistake using the same message interface. I am doing so.

  For example, when the medical staff clicks the question button 34, the message creation screen can be displayed on the medical staff terminal device 4. In the medical staff terminal device 4, a reply message is displayed on the web page in step S35. And a message can be transmitted to the medical staff side I / F 13 of the support server device 1 in the first format.

  In step S <b> 36, the support server device 1 generates a reply message addressed to the non-member MR from the first format to the second format of the e-mail format in the message conversion unit 20 and registers it in the non-member MR selection registration table 24. A non-member MR reply message is transmitted to the e-mail address of the non-member MR. At the same time, when the support server device 1 receives the reply message addressed to the non-member MR in the first format in step S37, the support server device 1 stores it in the message database 18 for centralized management.

  In step S38, the non-member MR can confirm the reply message from the medical staff by activating the mailer of the non-member MR terminal device 6 and confirming the transmission / reception.

  Although the message exchange between the non-member MR and the medical personnel has been described above, the support server device 1 provides the member MR terminal message 5 to the member MR side message I / F 11 for the member MR. The member MR can create a message for the medical staff on the web page. The member MR terminal device 5 transmits a message in the first format to the member MR side message I / F 11, and the support server device 1 manages the message in the message database 18. Since details are described in the above-mentioned patent document 1, details thereof are omitted.

In the support server device 1 as described above, the non-member MR message I / F 12 and the message conversion unit 20 are provided, so that medical personnel can exchange messages with the non-member MR. In addition, non-member MRs can also exchange messages with medical personnel. At this time, by limiting the number of non-member MRs to be associated with one medical person as a predetermined number , the first form is compared with when exchanging messages between the medical person and the member MR. It is possible to prevent an excessive amount of message exchanges that require conversion processing with the second format, and to prevent an excessive load on the system.

  Further, for non-member MRs, unauthorized use can be prevented by limiting the email addresses associated with the email addresses of medical personnel to one-to-one here.

  In the field of distribution of pharmaceuticals using the support system described above, there is an MS (Medical Sales, Marketing Specialist) belonging to an MR wholesaler. Therefore, the system described individually may be used between the MS and medical personnel. Further, the present invention is not limited to the medical product distribution field, and the support server device 1 can be used between a sales representative and a customer in other distribution systems.

It is a block diagram of the assistance system to which this invention is applied. It is a functional block diagram of the assistance server apparatus which comprises the assistance system of the said FIG. It is a figure which shows the data structure of a member MR table, the member MR selection registration table, and a medical staff table, and the correlation between them. It is a figure which shows the data structure of a nonmember MR table, the member MR selection registration table, and a medical staff table, and the correlation between them. It is a flowchart which shows the procedure when a medical staff registers with the assistance server apparatus of FIG. It is a flowchart which shows a series of procedures until a medical staff invites a non-member MR to this system and the invited non-member MR registers in this system. (A) It is a figure which shows the invitation mail for printing when a medical staff invites a nonmember MR to this system, (B) is a figure which shows the reply mail with respect to a blank mail. It is a figure which shows the invitation mail for an email when a medical staff invites a nonmember MR to this system. It is a flowchart which shows the procedure when a nonmember MR and a medical staff perform a message exchange. It is a figure which shows the top page which a nonmember MR accesses first. It is a figure which shows the mailer when a nonmember MR transmits an email to a medical staff. It is a figure which shows the receipt confirmation content confirmation page of a medical staff.

Explanation of symbols

1 support server device, 2 database, 3 network, 4 medical staff terminal device, 5 member MR terminal device, 6 non-member MR terminal device, 7 administrator terminal device, 11 member MR side message interface, 12 non-member message interface, 13 medical personnel side message interface, 14 selection registration section, 15 member MR database, 16 non-member MR database, 17 medical staff database, 18 message database, 19 invitation management section, 20 message conversion section, 21 member MR table, 22 member MR selection registration table, 23 non-member MR table, 24 non-member MR selection registration table, 25 medical staff table, 26 billing processing unit, 27 address issuing unit, 31, 32 registration button, 33 send button, 34 Question Tan, 35 delete button, 36 member MR display unit

Claims (7)

A customer database that stores a customer table populated with customer personal data;
A member database that stores a member sales representative table provided for each member sales representative, and a member selection registration table that associates the customer table with the member sales representative table;
A non-member database that stores a non-member sales person table provided for each non-member sales person, a non-member selection registration table that associates the customer table and the non-member sales person table,
The member registration / registration table for associating the predetermined customer table with the member sales representative table and the non-member selection registration for associating the predetermined customer table with the non-member sales representative table A selection registration unit for generating a table;
A message addressed to a customer sent from the member sales representative or the non-member sales representative to the customer, and a member sales representative or a non-member sales representative sent from the customer to the member sales representative or the non-member sales representative A message database that holds messages to
The member sales representative terminal device supports the creation of the message addressed to the customer, accepts the message in the first format, stores the received message addressed to the customer in the first format in the message database, and the customer A member sales representative-side message interface that reads the created message addressed to the member sales representative from the message database and transmits the message to the member sales representative terminal device in the first format;
The message addressed to the customer from the non-member sales representative terminal device is received in the second format, and the message addressed to the non-member sales representative created by the customer is received in the second format in the non-member sales representative terminal device. A non-member sales representative side message interface to send,
The message addressed to the customer in the second format received by the non-member sales representative side message interface is converted into the first format and stored in the message database, and the non-member sales representative created by the customer A message conversion unit that converts the addressed message from the first format to the second format and transmits the message to the non-member sales representative terminal device from the non-member sales representative-side message interface;
The message addressed to the customer created by the member sales representative or the non-member sales representative is read from the message database and transmitted to the customer terminal device in the first format, and the member sales at the customer terminal device is transmitted. A customer-side message interface that supports the creation of a message addressed to the person in charge or the non-member sales representative, receives the message in the first format, and stores it in the message database ;
Address issuance for individually issuing a customer address for exchanging the message in the second format between the non-member sales representative side message interface and the non-member sales representative terminal device to the customer And
Issuing and managing invitations from the customer to the non-member sales representative, and rejecting registration to the non-member sales representative table when the number of non-member sales representatives for a single customer exceeds a predetermined number An invitation management department,
The first format is a format for exchanging messages on a web page, and the second format is a format for exchanging messages using e-mail.
After the address issuing unit issues the customer address, the invitation management unit includes the second web page address for non-member sales person registration addressed to the non-member sales person address obtained from the customer. Generate an invitation email in the form and send it to the non-member sales representative terminal device from the non-member sales representative side message interface,
When the registration of the non-member sales representative is completed on the non-member sales representative registration web page, the selection registration unit selects the non-member sales in which the customer address is associated with the non-member sales representative address. Create a registration table,
The non-member sales representative side message interface accepts the message addressed to the customer with the issued customer address as a destination, and the non-member sales representative associated with the customer address in the non-member selective registration table A marketing support apparatus that transmits a message addressed to a non-member sales representative with the address as a transmission destination . Above the non-member selection registration tables, marketing supporting apparatus according to claim 1 wherein the relationships between the above customer address and the non-members salesperson address on a one-to-one. Furthermore, a billing processing unit for the non-member sales representative is provided,
3. The marketing support apparatus according to claim 1 , wherein the billing processing unit determines a billing amount according to the number of the customers associated with the non-member selection registration table.   The received contact confirmation page for confirming a message from the member sales representative or the non-member sales representative provided by the customer-side message interface to the customer terminal device displays a message from the non-member sales representative. The marketing support apparatus according to any one of claims 1 to 3, further informing that there is an unread message from the member sales representative. A data processing method for a marketing support device according to any one of claims 1 to 4 ,
The member sales representative side message interface supports the creation of the message addressed to the customer at the member sales representative terminal device, accepts the message addressed to the customer in the first format, and receives the received message in the first format. Storing the message in the message database;
Reading the message addressed to the customer created by the member sales representative from the message database at the customer-side message interface and transmitting the message to the customer terminal device in the first format;
Supporting the creation of a message addressed to the member sales representative at the customer terminal device at the customer-side message interface, receiving the message in the first format, and storing the message in the message database;
Reading out the message addressed to the member sales representative created by the customer from the message database in the message interface on the member sales representative side and transmitting the message to the member sales representative terminal device in a first format;
After the address issuing unit has issued the customer address, the invitation management unit includes the second web page address for non-member sales person registration addressed to the non-member sales person address obtained from the customer. Generating an invitation e-mail in the form of, and transmitting to the non-member sales representative terminal device from the non-member sales representative side message interface;
When the registration of the non-member sales person on the non-member sales person registration web page is completed, the selection registration unit associates the customer address and the non-member sales person address with the selection for the non-member. Generating a registration table;
Refusing registration in the non-member sales representative table when the registration of the non-member sales representative for a customer exceeds a predetermined number;
Accepting the message addressed to the customer from the non-member sales representative terminal device in a second format at the non-member sales representative side message interface;
Receiving in the second format, converting the message addressed to the customer from the second format to the first format and storing it in the message database in the message conversion unit;
Reading the message addressed to the customer created by the non-member sales representative from the message database at the customer-side message interface and transmitting the message to the customer terminal device in the first format;
In the customer-side message interface, supporting the creation of the message addressed to the non-member sales representative at the customer terminal device, receiving the message in the first format, and storing the message in the message database;
Converting the message to the non-member sales representative created by the customer from the first format to the second format;
A method for processing data in a marketing support apparatus, comprising: a step of transmitting a message addressed to a non-member sales person who has been converted into the second format to the non-member sales person terminal device through the non-member sales person side message interface. . A computer-readable recording medium recording a program for causing a server device to execute the data processing method according to claim 5 . A program for causing a server device to execute the data processing method according to claim 5 .

Images