Medical examination point exchange system, method, and program

Abstract

To provide a mechanism that relates to a medical examination point exchange technique, and that can enhance motivation to take medical examination and connect an action to take medical examination to an action to purchase related commodities, thereby organically activating the medical examination and electric commerce business.SOLUTION: When a user makes a reservation for medical examination from a user terminal 102, medical examination points are provided to a user record on a user database 130 on a server computer 101 through medical examination point providing processing 122. When the user opens an EC site on the user terminal 102, a recommended commodity is extracted on the basis of the details of the reservation for medical examination in a medical examination reservation database 131 and the details of the user attribute in the user database 130 on the server computer 101 through recommended commodity extraction processing 123, and the recommendation is displayed on the EC site displayed on the user terminal 102 through electric commerce processing 124. The user can consume the medical examination points during purchase of commodities based on the display of recommendation and the like on the EC site.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a medical checkup point exchange system, method, and program. [Background technology]

[0002] Conventionally, there is known a technique for identifying products or services for a user based on health checkup data obtained from the user, measurement results for additional measurement items, or answers to additional medical questionnaires (for example, the technique described in Patent Document 1). This conventional technology is expected to reduce cases where diagnostic results are overlooked by suggesting the intake of certain health foods or the introduction of health equipment based on health checkup data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7190859 Summary of the Invention [Problem to be solved by the invention]

[0004] However, if users are not motivated to undergo a health checkup in the first place, they will not be able to take action to improve their health. Furthermore, simply presenting products or services based on the results of a health checkup does not necessarily lead to users' purchasing behavior.

[0005] Therefore, the present invention aims to organically stimulate the business of health checkups and e-commerce by providing a system that can increase motivation to undergo health checkups and at the same time link the act of undergoing a health checkup with the act of purchasing related products. [Means for solving the problem]

[0006] One example of a health checkup point exchange system is a system including a server computer and a user terminal connected to the server computer via a network and operated by a user undergoing a health checkup, wherein the server computer performs a user registration process in which a user registration form is displayed on the user terminal to allow the user to input user attributes, the input user attribute data is received from the user terminal and stored in association with the user, a health checkup reservation process in which a health checkup reservation form is displayed on the user terminal to allow the user to input a health checkup reservation, the input health checkup reservation data is received from the user terminal and stored in association with the user, and a health checkup point granting process in which health checkup points are calculated based on the received health checkup reservation, and the health checkup points are accumulated and stored in association with the user who made the health checkup reservation. When a display request for an e-commerce site is received from a user terminal, the system executes a recommended product extraction process that extracts recommended products to be recommended to the user based on medical checkup reservation data and / or user attribute data stored corresponding to the user of the user terminal, and an e-commerce process that displays, on the user terminal that sent the display request, an e-commerce site where products can be purchased while consuming and updating medical checkup points accumulated and stored corresponding to the user of the user terminal, and recommends and displays recommended products extracted from the products by the recommended product extraction process on the e-commerce site. [Effects of the Invention]

[0007] According to the present invention, it is possible to increase motivation to undergo a health checkup by awarding health checkup points when reserving / receiving a health checkup. At the same time, by providing a system that allows users to spend their acquired health checkup points on products recommended according to the details of their health checkup reservation and user attributes, and links the act of undergoing a health checkup with the purchase of related products, it is possible to stimulate users' health promotion behavior, the health checkup business, and the e-commerce business. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram of an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a data configuration of a database according to an embodiment. [Figure 3] FIG. 1 is a diagram illustrating a business model of an embodiment. [Figure 4] FIG. 2 illustrates an example of the hardware configuration of a server computer according to an embodiment. [Figure 5] 10 is a flowchart illustrating an example of a main process according to an embodiment. [Figure 6] 10 is a flowchart showing a detailed example of a user registration process. [Figure 7] 10 is a flowchart showing a detailed example of a medical checkup reservation process / medical checkup point granting process. [Figure 8] 10 is a flowchart showing a detailed example of a recommended product extraction process / electronic commerce process. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Fig. 1 is a block diagram of an embodiment 100 of a health checkup point exchange system according to the present invention (hereinafter referred to as "health checkup point exchange system 100").

[0010] The health checkup point exchange system 100 includes a server computer 101 and one or more user terminals 102 that are connected to the server computer 101 via a network 103, such as the Internet, and are operated by one or more users who will undergo a health checkup. For convenience, only one user terminal 102 is shown in Fig. 1.

[0011] The user terminal 102 is, for example, a smartphone owned by the user. The user uses the user terminal 102 to read a QR code (registered trademark), which is a two-dimensional code printed on, for example, a health checkup information leaflet, and then downloads and installs the health checkup application 110 from an app store website. By executing this medical checkup application 110 on the user terminal 102, the user can make medical checkup reservations and display electronic commerce sites (hereinafter referred to as "EC (Electric Commerce) sites") to purchase products and use services. The health checkup application 110 is, for example, a LINE application using the LINE service (a registered trademark of LINE Corporation) provided by LINE Corporation. Alternatively, the health checkup application 110 may be an application developed specifically for that purpose. Furthermore, the health checkup application 110 is not a requirement of the present invention, and may be realized using ordinary browser software or the like that can be executed on the user terminal 102.

[0012] The server computer 101 is a general computer that has the function of connecting to a network 103 . This server computer 101 first executes a user editing process 120 in which a health checkup application 110 running on a user terminal 102 displays a user editing form to allow the user to edit (newly input or update) the user attributes, and then receives the edited user attribute data from the user terminal 102 and stores it in association with the user.

[0013] The user attributes include basic personal information such as the user's name, address, phone number, age, and gender. The user edit form may also include medical questionnaire items, and the user attributes may include answer items to those medical questionnaire items. The answer items may include, for example, medical history, work history, subjective symptoms, height, weight, etc.

[0014] In the user editing process 120, the server computer 101 stores the user attribute data received from the user terminal 102, for example, in the user database 130. FIG. 2(a) is a diagram showing an example of the data configuration of the user database 130. In the user database 130, for example, a database record is configured for each user (User 1, User 2, ..., User N (N is a natural number) in the diagram). Each record has database items (database fields) that store, for example, a user ID that is automatically generated at the time of new registration, health check points (described later), and the various user attributes described above (User Attribute 1, User Attribute 2, ..., User Attribute M (M is a natural number) in the diagram). The user ID may be automatically generated, or may be, for example, an email address, a LINE ID, or a combination of these, or a combination of one or more user attributes.

[0015] The above user editing process 120 will be described in detail later with reference to the flowchart of FIG.

[0016] Next, the server computer 101 executes a medical examination reservation process 121 in which a medical examination reservation form is displayed on the medical examination application 110 running on the user terminal 102 to allow the user to input the medical examination reservation, and the input medical examination reservation data is received from the user terminal 102 and stored in correspondence with the user.

[0017] A medical checkup reservation includes, for example, medical checkup items such as the date of the checkup, whether it is a medical checkup or a comprehensive medical examination, selection of a basic medical checkup plan, selection of an optional medical checkup plan, etc. The medical checkup reservation form may also include medical interview items, and the medical checkup reservation may also include answer items to those interview items. The answer items may be, for example, current physical condition, body temperature, height, weight, subjective symptoms, etc.

[0018] In the medical checkup reservation process 121, the server computer 101 stores the medical checkup reservation data received from the user terminal 102, for example, in the medical checkup reservation database 131. FIG. 2(b) is a diagram showing an example of the data configuration of the medical checkup reservation database 131. In the medical checkup reservation database 131, for example, a database record is configured for each medical checkup reservation (medical checkup reservation 1, medical checkup reservation 2, ..., medical checkup reservation K (K is a natural number) in the figure). Each record is generated, for example, every time a medical checkup reservation is made, and has database items that store the user ID and various medical checkup reservation items (medical checkup reservation item 1, medical checkup reservation item 2, ..., medical checkup reservation item P (P is a natural number) in the figure) that are included in the medical checkup reservation form and notified from the user terminal 102.

[0019] Here, in the medical checkup reservation process 121, the server computer 101 notifies the medical checkup reservation data stored in the record of the medical checkup reservation database 131 corresponding to the user, together with necessary user attribute data stored in the record on the user database 130 that stores the same user ID as the user ID stored in the user ID item of that record in the user ID item (FIG. 2(a)), to the medical checkup implementation organization terminal 104 that implements the medical checkup, which is connected via the network 103. This enables the medical checkup implementation organization to manage medical checkup reservations for each user.

[0020] Next, the server computer 101 executes a medical checkup point allocating process 122 in which the server computer 101 calculates medical checkup points based on the medical checkup reservation received in the above-mentioned medical checkup reservation process 121, and accumulates and stores the medical checkup points in association with the user who made the medical checkup reservation.

[0021] Here, in the medical checkup point allocation process 122, the server computer 101 may allocate a fixed number of points (for example, 100 points) each time a medical checkup appointment is made, or may calculate medical checkup points of a number corresponding to the details of the medical checkup appointment entered by the user.

[0022] In the medical checkup point granting process 122, the server computer 101 accumulates and stores the calculated medical checkup appointment data, for example, in the medical checkup point item shown in Figure 2(a) of the record in the user database 130 in which the user ID included in the medical checkup appointment received in the medical checkup appointment process 121 is stored in the user ID item in Figure 2(a). In this way, every time a user makes a medical checkup appointment, medical checkup points can be accumulated.

[0023] The details of the medical checkup reservation process 121 and the medical checkup point allocation process 122 will be described later with reference to the flowchart of FIG.

[0024] In addition, when the server computer 101 receives medical examination data indicating that the user has undergone a medical examination, it may further execute the above-mentioned medical examination point allocation process 122 and further calculate medical examination points corresponding to the content of the medical examination data.

[0025] Specifically, when the user terminal 102 is notified by the organization that conducted the health examination that the user operating the user terminal 102 has undergone the health examination, the user terminal 102 generates examination data indicating that the user has undergone the health examination and transmits the data to the server computer 101.More specifically, the user terminal 102 may generate the examination data by reading a QR code 150, which is a two-dimensional code that can only be used once and is presented by the organization that conducted the health examination when the health examination is conducted, as shown in FIG. 1, for example.

[0026] Alternatively, the system may further include a health checkup organization terminal that is installed in an organization that conducts health checkups, connected to the server computer 101 via the network 103, and that generates medical examination data indicating that the user has undergone a health checkup and transmits the data to the server computer 101. This health checkup organization terminal may generate medical examination data corresponding to the user, for example, by reading a QR code displayed on the health checkup application 110 of the user terminal 102 operated by the user.

[0027] Next, when the server computer 101 receives a request to display an EC site from the user terminal 102, it executes a recommended product extraction process 123 to extract recommended products to be recommended to the user based on the medical checkup appointment data stored in, for example, a medical checkup appointment database 131 (see Figure 2(b)) corresponding to the user of the user terminal 102 and / or the user attribute data stored in, for example, a user database 130 (see Figure 2(a)).

[0028] In this recommended product extraction process 123, the server computer 101 inputs the medical checkup appointment data stored in, for example, the medical checkup appointment database 131 in Figure 2(b) and / or the user attribute data stored in, for example, the user database 130 in Figure 2(a) corresponding to the user of the user terminal 102 that sent the display request into a recommended product prediction model 140 that has been machine-trained using medical checkup appointment data and / or user attribute data as explanatory variables and recommended products as the objective variable, and extracts the output obtained as a recommended product.

[0029] Here, the server computer 101 may further execute a medical checkup result input process 125 in which the medical checkup application 110 running on the user terminal 102 displays a medical checkup result input form to allow the user to input the medical checkup results, receives the input medical checkup result data from the user terminal 102, and stores the data together with the user ID corresponding to the user in, for example, the medical checkup result database 134. The medical checkup result input process may be omitted. When equipped with this function, the server computer 101 can extract recommended products in the recommended product extraction process 123 based further on the medical checkup result data stored in, for example, the medical checkup result database 134 corresponding to the user of the user terminal 102 that sent the display request.

[0030] Here, the server computer 101 may extract recommended products according to the current season in the recommended product extraction process 123. Furthermore, in the recommended product extraction process 123, the server computer 101 may extract recommended products corresponding to a preset sale or event.

[0031] The server computer 101 executes an electronic commerce process 124 for displaying, on the user terminal 102 that sent the display request, an EC site where products can be purchased while consuming and updating the medical checkup points accumulated and stored in the medical checkup point item of the user database 130 in Fig. 2(a) corresponding to the user of the user terminal 102. Then, in this electronic commerce process 124, the server computer 101 displays the recommended products extracted by the recommended product extraction process 123 on the EC site.

[0032] Here, the server computer 101 includes a product database 132. Fig. 2(c) is a diagram showing an example of the data configuration of the product database 132. In the product database 132, for example, a database record is configured for each recommended product and other product (product 1, product 2, ..., product Q (Q is a natural number) in the diagram) handled on the EC site. Each record has database items that store, for example, a product ID for uniquely identifying each product on the EC site, a product name, a product unit price, a point exchange rate, a detailed product description, and one or more product images. In the electronic commerce processing 124, when the server computer 101 displays each product on the EC site, it reads each of the above-mentioned database items from the corresponding record in the product database 132 of Figure 2 (c), lays them out on the EC site, and displays them on the user terminal 102.

[0033] In addition to physical products such as health foods, health drinks, postpartum cakes, and daily necessities, the products also include various welfare services, accommodation, use of various facilities (massage, beauty treatments, relaxation, hot springs, etc.), travel plans, use of transportation, postpartum care services, meals, and various other service products.

[0034] The server computer 101 also includes a payment database 133. FIG. 2(d) is a diagram showing an example of the data structure of the payment database 133. In the payment database 133, a database record is configured for each payment for a product purchase made by a user (Payment 1, Payment 2, ..., Payment R in the figure). Each record has database items that store, for example, a payment ID that is automatically generated when the product purchase payment is made, a product ID of the purchased product (see FIG. 2(c)), the product unit price (see FIG. 2(c)), the number of products purchased, the payment price (product unit price x number of products), the number of health checkup points used designated by the user, the point application price (number of points used x point exchange rate (see FIG. 2(c))), the billed price (payment price - point application price), and the user ID transmitted from the user terminal 102 that made the purchase payment.

[0035] When a user sends a payment form transmission request on the user terminal 102, for example, by tapping (or clicking) a shopping cart icon on the EC site, the server computer 101 sends a payment form that displays a shopping cart screen in the electronic commerce processing 124. Furthermore, when a user sends a product payment request on the user terminal 102 by inputting necessary payment information including the consumption of medical checkup points on the shopping cart screen, the server computer 101 executes payment processing including the consumption of medical checkup points in the electronic commerce processing 124, and registers the resulting payment information in the payment database 133, an example of which is shown in Fig. 2(d).

[0036] The recommended product extraction process 123 and the electronic commerce process 124 will be described in detail later with reference to the flowchart of FIG.

[0037] In the above-mentioned electronic commerce processing 124, when the user uses medical checkup points for a recommended product, the server computer 101 may increase the above-mentioned point exchange rate.

[0038] Figure 3 is a diagram showing a business model realized by the medical checkup point exchange system 100 of Figure 1. In Figure 3, the server computer 101, user terminal 102, and medical checkup organization terminal 104 are the same as those shown in Figure 1. In addition, among the arrows in the figure, the solid arrows represent the flow of information in accordance with the solid arrows in Figure 1, and the dashed arrows represent the actions of people or organizations.

[0039] A user 301 can receive medical checkup points from a medical checkup implementing organization 302 by making a medical checkup reservation with the medical checkup implementing organization 302 . The user 301 can exchange the medical checkup points thus accumulated for products on the EC site 303 or use them to purchase products.

[0040] At this time, the user terminal 102 transmits to the server computer 101 the user edit form, medical checkup reservation form, medical checkup notification, health result input form, or payment form for the EC site, all of which are described in FIG. On the other hand, the user terminal 102 can grasp how many health checkup points the user currently has by receiving and displaying information on health checkup points from the server computer 101, as explained in Fig. 1. The user terminal 102 can also be provided by the server computer 101 with an EC site 303 equipped with a recommendation display function, a shopping cart function, a health checkup point consumption function in the shopping cart, and the like, as explained in Fig. 1. Furthermore, the server computer 101 can provide the health checkup organization terminal 104 with information on health checkup reservations and the user 301 who made the reservations.

[0041] In this way, the user 301 can accumulate medical checkup points every time he or she makes a medical checkup appointment, thereby increasing his or her motivation to undergo a medical checkup. Furthermore, the user 301 can efficiently select recommended products on the EC site 303 that match the details of his or her medical checkup appointment and his or her user attributes, i.e., products that are of greater interest to the user in maintaining his or her health, and this makes it possible to link the act of undergoing a medical checkup with the act of purchasing related products.

[0042] On the other hand, the medical checkup organization 302 can expect an increase in income from medical checkups due to the increased motivation of the user 301 to undergo a medical checkup, and can also receive medical checkup reservations and information about the user 301 quickly and reliably.

[0043] Product supplier 305 is expected to increase sales by supplying products to EC site 303. In this case, product price is billed by product supplier 305 to system operation organization 304, and system operation organization 304 makes payment for the product price.

[0044] The system operation organization 304 of the medical checkup point exchange system 100 can increase the operating profit of the medical checkup point exchange system 100 by claiming and receiving an operation fee commensurate with the increase in medical checkup income at the medical checkup implementation organization 302. Furthermore, the system operation organization 304 can make a profit commensurate with the operation of the EC site 303 through the trading of goods with the product trading partner 305.

[0045] In this way, it is possible to build a win-win-win-win business relationship between the user 301 undergoing the health checkup, the health checkup implementation organization 302, the product trading partner 305, and the system operation organization 304.

[0046] Fig. 4 is a diagram showing an example of the hardware configuration of the server computer 101 in Fig. 1. This hardware has the configuration of a typical server computer, in which a processor (central processing unit) 401, a ROM (read-only memory) 402 that stores programs, a RAM (random access memory) 403 into which the programs are loaded from the ROM 402 and executed, an external storage device 404 such as a hard disk or SSD (solid state disk) that stores the various databases 130 to 134 in Fig. 1, a network interface 405 that controls access to the network 103 in Fig. 1, and a user interface 406 that includes an input unit consisting of a keyboard and a mouse, and a display, a printer, etc., all connected to each other via a system bus 407.

[0047] The operation of the health checkup point exchange system 100 having the configurations shown in Figures 1 and 4 will be described in detail below. In the following description, the processor 401, ROM 402, RAM 403, external device 404, etc. will refer to the blocks with the same reference numbers in Figure 4 unless otherwise specified.

[0048] 5 is a flowchart showing an example of the main processing of the medical checkup point exchange processing of this embodiment. This main processing is an operation in which the processor 401 reads out the medical checkup point exchange processing program stored in the ROM 402 into the RAM 403 and executes it. The main processing is a process in which a user editing process (step S501 in FIG. 5) corresponding to the user editing process 120 in FIG. 1, a medical checkup reservation / medical checkup point assignment process (step S502 in FIG. 5) corresponding to the medical checkup reservation process 121 and the medical checkup point assignment process 122 in FIG. 1, and a recommended product extraction / electronic commerce process (step S503 in FIG. 5) corresponding to the recommended product extraction process 123 and the electronic commerce process 124 in FIG. 1 are sequentially and repeatedly executed.

[0049] Fig. 6 is a flowchart showing a detailed example of the user editing process in step S501 in Fig. 5. The processor 401 first determines whether or not a user editing form transmission request has been received from the health checkup application 110 of any user terminal 102 via the network 103 in Fig. 1 and the network interface 406 in Fig. 3 (step S601 in Fig. 6). The user editing form transmission request is transmitted from the health checkup application 110 via a network interface (not shown) of the user terminal 102 when the user taps, for example, an initial setting button or an update setting button for user registration in the health checkup application 110 executed on the user terminal 102.

[0050] When the server computer 101 receives a request to send a user edit form and the determination in step S601 becomes YES, the processor 401 reads the data of the user edit form prepared in advance from the ROM 402, RAM 403, or external storage device 404, and transmits it via the network interface 406 and the network 103 to the user terminal 102 that sent the request to send the user edit form (step S602 in Figure 6). As a result, a user edit form is displayed on the screen of the health checkup application 110 on a display (not shown) of the user terminal 102. The user can register or update the user by inputting user attributes using the user edit form.

[0051] If the server computer 101 has not received a user edit form transmission request and the determination in step S601 is NO, the processor 401 skips the process in step S602.

[0052] After the processing of step S602 or after the determination of step S601 is NO, the processor 401 determines whether or not data of the user edit form has been received from the health checkup application 110 of any user terminal 102 via the network 103 of Fig. 1 and the network interface 406 of Fig. 3 (step S603 of Fig. 6). The data of the user edit form is transmitted from the health checkup application 110 via a network interface (not shown) of the user terminal 102 when the user finishes inputting user attributes and taps, for example, a send button on the screen of the user edit form of the health checkup application 110 executed on the user terminal 102.

[0053] When the determination in step S603 becomes YES due to the reception of data in the user edit form in the server computer 101, the processor 401 determines whether the data in the user edit form is for a new user registration or an update to an existing user registration (step S604 in FIG. 6).

[0054] If it is determined in step S604 that the data in the user edit form is for a new user registration, the processor 401 first creates a new record in the user database 130 (FIGS. 1 and 2(a)) (step S605 in FIG. 6).

[0055] Next, the processor 401 automatically generates a user ID (user identifier) ​​to uniquely identify the user of the user terminal 102 that submitted the user edit form, registers the user ID in the user ID field (see Figure 2(a)) of the record generated in step S605, and sets the record as the target record for this processing (step S606 in Figure 6).

[0056] Next, the processor 401 transmits the user ID generated in step S606 to the medical checkup application 110 of the user terminal 102 that transmitted the user edit form via the network interface 406 and the network 103 (step S607). The user terminal 102 stores the received user ID and transmits it to identify its own user when updating the user registration, when making a medical checkup reservation (described later), or when requesting payment on an e-commerce site.

[0057] On the other hand, if it is determined in step S604 that the data in the user edit form is an update to a user registration, the processor 401 searches the user database 130 (FIGS. 1 and 2(a)) for a record that stores the user ID included in the received user edit form in the user ID field (see FIG. 2(a)), and sets the searched record as the target record for this processing (step S608 in FIG. 6).

[0058] After the processing of step S607 or S608 described above, the processor 401 newly registers or updates the data of one or more user attributes contained in the received user edit form data in each corresponding user attribute item (user attribute 1, user attribute 2, ..., user attribute M in Figure 2(a)) of the target record determined in step S606 or S608 (step S609 in Figure 6).

[0059] If the server computer 101 has not received the user edit form and the determination in step S603 is NO, the processor 401 skips the series of processes from steps S604 to S609 described above.

[0060] After the process of step S609 or after the determination of step S603 becomes NO, the processor 401 ends the user editing process of step S501 in FIG. 5 shown in the flowchart of FIG.

[0061] Fig. 7 is a flowchart showing a detailed example of the medical checkup reservation / medical checkup point granting process in step S502 in Fig. 5. The processor 401 first determines whether or not a request to send a medical checkup reservation form has been received from the medical checkup application 110 of any of the user terminals 102 via the network 103 in Fig. 1 and the network interface 406 in Fig. 3 (step S701 in Fig. 7). The request to send a medical checkup reservation form is sent from the medical checkup application 110 via a network interface (not shown) of the user terminal 102 when the user taps, for example, a medical checkup reservation button in the medical checkup application 110 executed on the user terminal 102.

[0062] When the server computer 101 receives a request to send a medical checkup appointment form and the result of the judgment in step S701 becomes YES, the processor 401 reads out the data of the medical checkup appointment form prepared in advance from the ROM 402, RAM 403, or external storage device 404, and transmits it to the user terminal 102 that sent the request to send the medical checkup appointment form via the network interface 406 and the network 103 (step S702 in Figure 7). As a result, a medical checkup reservation form is displayed on the screen of the medical checkup application 110 on a display (not shown) of the user terminal 102. The user can make a medical checkup reservation by inputting the medical checkup reservation information using the medical checkup reservation form.

[0063] If the server computer 101 has not received a request to send a medical checkup appointment form and the determination in step S701 is NO, the processor 401 skips the process in step S702.

[0064] After the processing of step S702 or after the determination of step S701 is NO, the processor 401 determines whether or not data of a medical checkup appointment form has been received from the medical checkup application 110 of any of the user terminals 102 via the network 103 of Fig. 1 and the network interface 406 of Fig. 3 (step 703 of Fig. 7). The data of the medical checkup appointment form is transmitted from the medical checkup application 110 via a network interface (not shown) of the user terminal 102 when the user finishes inputting the medical checkup appointment information and taps, for example, a send button on the screen of the medical checkup appointment form of the medical checkup application 110 executed on the user terminal 102.

[0065] When the server computer 101 receives the data of the medical checkup appointment form and the judgment in step S703 becomes YES, the processor 401 generates a new record in the medical checkup appointment database 131 (Figures 1 and 2(b)), registers the data of one or more medical checkup appointment items contained in the data of the received medical checkup appointment form in each corresponding medical checkup appointment item of the generated record (medical checkup appointment item 1, medical checkup appointment item 2, ..., medical checkup appointment item P in Figure 2(b)), and also registers the user ID contained in the data of the received medical checkup appointment form in the user ID item of the generated record (step S704 in Figure 7).

[0066] Next, the processor 401 notifies the medical checkup appointment data, which is the data of each medical checkup appointment item registered in the record of the medical checkup appointment database 131 in step S704, as medical checkup appointment data, together with the main user attribute items, such as name, address, telephone number, age, and sex, registered in the record of the user database 130 (FIG. 2(a)) in which the same user ID as the user ID registered in the user ID item of that record (FIG. 2(b)) is registered in the user ID item, via the network interface 406 and the network 103 to the medical checkup implementation organization terminal 104 in FIG. 1 (step S705 in FIG. 7). The notification may be by email or a dedicated management application. In this way, the person in charge at the medical examination organization can immediately grasp the details of the online medical examination reservation made by the user of the medical examination application 110.

[0067] Next, the processor 401 calculates the medical checkup points corresponding to the current medical checkup reservation (step S706 in FIG. 7). As described above in the explanation of the medical checkup point allocating process 122 in FIG. 1, a fixed number of points (for example, 100 points) may be allocated each time a medical checkup reservation is made, or the number of medical checkup points may be calculated according to the details of the medical checkup reservation entered by the user. For example, the number of medical checkup points may differ depending on whether it is a regular medical checkup, an in-company medical checkup, or a comprehensive medical checkup.

[0068] Next, the processor 401 adds the medical checkup points calculated in step S706 to the number of points already registered in the medical checkup points item (see FIG. 2(a)) of the record in which the same user ID as the user ID included in the medical checkup reservation form received is registered in the user ID item (see FIG. 2(a)) on the user database 130 (FIG. 1), and registers the accumulated result (accumulation registration) (step S707 in FIG. 7). In this way, each time a user makes a medical checkup appointment, medical checkup points can be accumulated, which increases motivation to undergo a medical checkup.

[0069] Although not shown in the flowchart of Figure 7, as described above in the explanation of the health check point allocation process 122 in Figure 1, the processes of the above-mentioned steps S706 and S707 may be executed when examination data indicating that the user has undergone a health check is received.

[0070] If the server computer 101 has not received the medical examination reservation form and the determination in step S703 is NO, the processor 401 skips the series of processes from steps S704 to S707.

[0071] After the processing of step S707 or the determination of step S703 becomes NO, the processor 401 determines whether or not a request to display health check points has been received from the health check application 110 of any of the user terminals 102 via the network 103 of Fig. 1 and the network interface 406 of Fig. 3 (step S708 of Fig. 7). The request to display health check points is transmitted from the health check application 110 via a network interface (not shown) of the user terminal 102 when the user taps, for example, a button to display retained health check points in the health check application 110 executed on the user terminal 102.

[0072] When the server computer 101 receives a request to display health check points and the result of the determination in step S708 becomes YES, the processor 401 reads out the number of points registered in the health check point item (see FIG. 2(a)) of the record in the user database 130 (FIG. 1) in which the same user ID as the user ID included in the received health check point display request is registered, and transmits the number of points via the network interface 406 and the network 103 to the user terminal 102 that sent the health check point display request (step S709). As a result, the user terminal 102 can cause the health checkup application 110 to display the health checkup points currently held by the user corresponding to the user terminal 102.

[0073] If the server computer 101 has not received a request to display health checkup points and the determination in step S708 is NO, the processor 401 skips the process in step S709.

[0074] After the process of step S709 or after the determination of step S708 becomes NO, the processor 401 ends the process of step S502 in FIG. 5 shown in the flowchart of FIG.

[0075] Fig. 8 is a flowchart showing a detailed example of the recommended product extraction process / electronic commerce process in step S503 in Fig. 5. The processor 401 first determines whether or not a display request for an EC site (electronic commerce site) has been received from the health checkup application 110 of any of the user terminals 102 via the network 103 in Fig. 1 and the network interface 406 in Fig. 3 (step S801 in Fig. 8). The display request for the EC site is transmitted from the health checkup application 110 via a network interface (not shown) of the user terminal 102 when the user taps, for example, a display button for the EC site in the health checkup application 110 executed on the user terminal 102.

[0076] When the server computer 101 receives an EC site display request and the determination in step S801 becomes YES, the processor 401 first executes a recommended product extraction process (step S802 in FIG. 8). Specifically, as described above in the description of the recommended product extraction process 123 in FIG. 1, the processor 401 extracts, as recommended products, an output obtained as a result of inputting the medical checkup appointment data stored in, for example, the medical checkup appointment database 131 in FIG. 2(b) and / or the user attribute data stored in, for example, the user database 130 in FIG. 2(a), in which the user ID included in the EC site display request determined in step S801 is registered in the user ID field, into the recommended product prediction model 140, which is, for example, a neural network, which has been machine-learned using the medical checkup appointment data and / or the user attribute data as explanatory variables and the recommended product as a target variable.

[0077] Next, the processor 401 reads EC site display data written in, for example, HTML (Hyper Transfer Markup Language) format and JavaScript (a trademark or registered trademark of Sun Microsystems, Inc., USA) format from the RAM 403, ROM 402, or external storage device 404, reads product information (see Figure 2(c)) registered in each record of the product database 132 on the EC site display layout data, arranges each product, and sends the EC site display data, which implements code to display the recommended products extracted in step S802, to the user terminal 102 that sent the EC site display request via the network interface 406 and the network 103 (step S803 in Figure 8). At this time, as described above in the description of the product database 132 in Figure 2(c), the processor 401 reads information for each database item, such as the product ID, product name, product unit price, point exchange rate, product detailed description, and one or more product images, from the corresponding record in the product database 132 in Figure 2(c), embeds it in the layout elements of the recommended products and other products displayed on the EC site, and displays it in an appropriate layout. As a result, the browser built into the health checkup app 110 of the user terminal 102 (for example, a LINE built-in browser) or the browser application that the user terminal 102 comes standard with can interpret the EC site display data to display recommended products and also display an EC site where other products can be searched. In other words, the user of the user terminal 102 can efficiently select recommended products that are of greater interest to the user in maintaining their health, which are displayed based on the user's health checkup appointment, the results of the medical interview at the time of booking the health checkup or user registration, or the results of the health checkup, and can link the act of undergoing a health checkup to the act of purchasing related products. Of course, users can freely search and select other products on the EC site.

[0078] If the server computer 101 has not received an EC site display request and the determination in step S801 is NO, the processor 401 skips the processes in steps S802 and S803 described above.

[0079] After the process of step S803 or after the determination of step S801 becomes NO, the processor 401 determines whether or not a payment form transmission request has been received from any of the user terminals 102 via the network 103 of Fig. 1 and the network interface 406 of Fig. 3 (step S804 of Fig. 8). As described above in the explanation of the electronic commerce process 124 of Fig. 1, the payment form transmission request is transmitted via a network interface (not shown) of the user terminal 102 when the user taps (or clicks), for example, a shopping cart icon on the EC site displayed on the user terminal 102.

[0080] When the server computer 101 receives a payment form transmission request and the determination in step S804 becomes YES, the processor 401 reads out the data of a pre-prepared payment form from the ROM 402, RAM 403, or external storage device 404, and transmits it to the user terminal 102 that sent the payment form table request via the network interface 406 and the network 103 (step S805 in Figure 8). As a result, a shopping cart screen is displayed on the EC site screen of the user terminal 102. On this screen, the user can input necessary payment information, including the amount of medical checkup points that the user has.

[0081] If the server computer 101 has not received a payment form transmission request and the determination in step S804 is NO, the processor 401 skips the process in step S805.

[0082] After the processing of step S805 or the determination of step S804 is NO, the processor 401 determines whether or not a product payment request has been received from any of the user terminals 102 via the network 103 in Fig. 1 and the network interface 406 in Fig. 3 (step S807 in Fig. 8). The product payment request is sent when the user inputs necessary payment information, including the consumption of medical checkup points, on, for example, a shopping cart screen displayed on the user terminal 102, and taps, for example, a send button (or a payment confirmation button).

[0083] When the server computer 101 receives a product payment request and the determination in step S806 is YES, the processor 401 further determines whether the payment received together with the product payment request specifies the consumption of health checkup points (step S807 in Figure 8).

[0084] If consumption of health checkup points is specified and the judgment in step S807 is YES, the processor 401 updates the number of points in the health checkup point item with the number of points obtained by subtracting the number of health checkup points consumed as specified in the product payment request from the number of points registered in the health checkup point item of the record in the user database 130 (Figures 1 and 2(a)) in the user ID item that is the same as the user ID indicating the user who made the payment received together with the product payment request (step S808 in Figure 8).

[0085] If consumption of medical checkup points is not specified and the determination in step S807 is NO, the processor 401 skips the process in step S808.

[0086] After the processing of step S808 or the determination of step S807 is NO, the processor 401 generates a new record in the payment database 133 (FIGS. 1 and 2(d)), registers the payment information data received together with the product payment request in the corresponding items of the generated record (FIG. 2(d)), and registers the user ID received together with the product payment request in the user ID item (FIG. 2(d)) of the generated record (step S809 of FIG. 8). As described above in the explanation of the payment database 133 of FIG. 2(d), the payment information includes, for example, a payment ID automatically generated at the time of payment for the purchase of the product, the product ID of the purchased product (see FIG. 2(c)), the product unit price (see FIG. 2(c)), the number of purchased products, the payment price (product unit price × number of products), the number of health checkup points used designated by the user, the point allocation price (number of used points × point exchange rate (see FIG. 2(c))), and the billing price (payment price - point allocation price). Based on the payment information registered in the payment database 133 and the user attribute items in the user database 130 linked to the user ID, the organization operating the EC site (the organization operating the health checkup point exchange system 100) can execute payment and product delivery for the user who purchased the product.

[0087] On the other hand, if the server computer 101 has not received the product payment request and the determination in step S806 is NO, the processor 401 skips the series of processes from steps S807 to S809.

[0088] After the process of step S809 or the determination of step S806 is NO, the processor 401 ends the recommended product extraction process / electronic commerce process of step S503 in FIG. 5 shown in the flowchart of FIG.

[0089] According to the embodiment of the health checkup point exchange system described above, it is possible to increase motivation to undergo health checkups by awarding health checkup points when reserving / receiving a health checkup. At the same time, by providing a system that allows users to spend their acquired health checkup points on products recommended according to the details of their health checkup reservation and user attributes, and thereby linking the act of undergoing a health checkup with the purchase of related products, it is possible to stimulate users' health promotion actions, the health checkup business, and the e-commerce business in a win-win-win relationship.

[0090] In the above-described embodiment of the health checkup point exchange system 100, the health checkup booked by the user may not be a general health checkup at a private testing hospital, but may be an in-house health checkup at a company. In this case, the products for which the user can spend their health checkup points on the EC site may be, for example, products for employees or benefits for employee welfare services.

[0091] In the embodiment of the health checkup point exchange system 100 described above, the components of the server computer 101 in FIG. 1 may be distributed across two or more server computers.

[0092] In the above-described health check point exchange system 100, if the health check app 110 is, for example, a LINE app, various health-related information may be distributed to users from health checkup organizations or e-commerce site management organizations using an information distribution function to a chat line on LINE. At this time, pinpointed information distribution may be performed by narrowing down users based on various user attribute items registered in the user database 130 and various health checkup reservation items registered in the health checkup reservation database 131. [Explanation of symbols]

[0093] 100 Health check point exchange system, 101 Server computer, 102 User terminal, 103 Network, 104 Health check implementation organization terminal, 110 Health check application, 120 User editing process, 121 Health check reservation process, 122 Health check point grant process, 123 Recommended product extraction process, 124 E-commerce process, 130 User database, 131 Health check reservation database, 132 Product database, 133 Payment database, 134 Health check result database, 140 Recommended product prediction model, 150 QR code, 301 User, 302 Health check implementation organization, 303 EC site, 304 System operation organization, 305 Product trading partner, 401 Processor, 405 Network interface

Claims

1. A system including a server computer and a user terminal connected to the server computer via a network and operated by a user who will undergo a health checkup, The server computer a user editing process that displays a user editing form on the user terminal to allow the user to edit user attributes, receives data of the edited user attributes from the user terminal, and stores the data in association with the user; a medical examination reservation process that displays a medical examination reservation form on the user terminal, prompts the user to input a medical examination reservation, receives the input medical examination reservation data from the user terminal, and stores the data in association with the user; a medical checkup point granting process for calculating the medical checkup points based on the received medical checkup reservation, and accumulating and storing the medical checkup points in association with the user who made the medical checkup reservation; a recommended product extraction process for extracting recommended products to be recommended to the user based on the medical examination reservation data and / or the user attribute data stored in correspondence with the user of the user terminal when a display request for the e-commerce site is received from the user terminal; an electronic commerce process for displaying, on the user terminal that transmitted the display request, the electronic commerce site where products can be purchased and paid for while consuming and updating the medical checkup points accumulated and stored corresponding to the user of the user terminal, and for recommending and displaying, on the electronic commerce site, the recommended products extracted from the products by the recommended product extraction process; To execute Health checkup points exchange system.

2. the server computer accumulates and stores the number of medical checkup points corresponding to the details of the medical checkup reservation input by the user in the medical checkup point granting process; The health checkup point exchange system according to claim 1.

3. The medical examination reservation includes medical examination items and medical interview items, The health checkup point exchange system according to claim 1 or 2.

4. the server computer further executes the medical checkup point granting process when receiving medical checkup data indicating that the user has undergone the medical checkup. The health checkup point exchange system according to claim 1 or 2.

5. The server computer accumulates and stores the number of health checkup points corresponding to the content of the medical examination data in the health checkup point allocation process. The health checkup point exchange system according to claim 4.

6. When the user terminal is notified by the implementing organization that conducted the health examination that the user operating the user terminal has undergone the health examination, the user terminal generates the examination data indicating that the user has undergone the health examination and transmits the examination data to the server computer. The health checkup point exchange system according to claim 4.

7. the user terminal generates the medical examination data by reading a two-dimensional code that can be used only once and is presented by the organization conducting the medical examination when the medical examination is conducted; The health checkup point exchange system according to claim 6.

8. a medical examination implementation organization terminal that is installed in an organization that implements the medical examination, is connected to the server computer via the network, and generates the examination data indicating that the user has undergone the medical examination and transmits the examination data to the server computer; The health checkup point exchange system according to claim 4.

9. the medical examination organization terminal generates the medical examination data corresponding to the user by reading a two-dimensional code displayed on the user terminal operated by the user; The health checkup point exchange system according to claim 8.

10. The server computer a medical examination result input process is further executed to display a medical examination result input form on the user terminal, to have the user input the medical examination results, to receive the input data of the medical examination results from the user terminal, and to store the data in association with the user; In the recommended product extraction process, the recommended products are extracted further based on the content of the medical examination result input by the user. The health checkup point exchange system according to claim 1.

11. the server computer increases a point exchange rate when the user uses the medical checkup points for the recommended product in the electronic commerce processing; The health checkup point exchange system according to claim 1.

12. In the recommended product extraction process, the server computer inputs the medical checkup appointment data and / or the user attribute data stored corresponding to the user of the user terminal that made the display request into a recommended product prediction model that has been machine-trained using the medical checkup appointment data and / or the user attribute data as explanatory variables and the recommended product as a target variable, and extracts, as the recommended product, an output obtained as a result. The health checkup point exchange system according to claim 1.

13. The server computer extracts the recommended products according to the current season in the recommended product extraction process. The health checkup point exchange system according to claim 1.

14. The server computer extracts the recommended products corresponding to a preset sale or event in the recommended product extraction process. The health checkup point exchange system according to claim 1.

15. In the medical examination reservation process, the server computer notifies the medical examination reservation data stored in association with the user to a medical examination implementation organization terminal that is connected via the network and that will implement the medical examination. The health checkup point exchange system according to claim 1.

16. A system including a server computer and a user terminal connected to the server computer via a network and operated by a user who undergoes a health checkup, The server computer a user registration process for displaying a user registration form on the user terminal, prompting the user to input user attributes, receiving the input user attribute data from the user terminal, and storing the data in association with the user; a medical examination reservation process that displays a medical examination reservation form on the user terminal, prompts the user to input a medical examination reservation, receives the input medical examination reservation data from the user terminal, and stores the data in association with the user; a medical checkup point granting process for calculating the medical checkup points based on the received medical checkup reservation, and accumulating and storing the medical checkup points in association with the user who made the medical checkup reservation; a recommended product extraction process for extracting recommended products to be recommended to the user based on the medical examination reservation data and / or the user attribute data stored in correspondence with the user of the user terminal 102 when a display request for the e-commerce site is received from the user terminal 102; an electronic commerce process for displaying, on the user terminal that transmitted the display request, the electronic commerce site where products can be purchased and paid for while consuming and updating the medical checkup points accumulated and stored corresponding to the user of the user terminal, and for recommending and displaying, on the electronic commerce site, the recommended products extracted from the products by the recommended product extraction process; To execute How to exchange health checkup points.

17. A system including a server computer and a user terminal connected to the server computer via a network and operated by a user who undergoes a health checkup, The server computer a user registration process for displaying a user registration form on the user terminal, prompting the user to input user attributes, receiving the input user attribute data from the user terminal, and storing the data in association with the user; a medical examination reservation process that displays a medical examination reservation form on the user terminal, prompts the user to input a medical examination reservation, receives the input medical examination reservation data from the user terminal, and stores the data in association with the user; a medical checkup point granting process for calculating the medical checkup points based on the received medical checkup reservation, and accumulating and storing the medical checkup points in association with the user who made the medical checkup reservation; a recommended product extraction process for extracting recommended products to be recommended to the user based on the medical examination reservation data and / or the user attribute data stored in correspondence with the user of the user terminal when a display request for the e-commerce site is received from the user terminal; an electronic commerce process for displaying, on the user terminal that transmitted the display request, the electronic commerce site where the user can purchase and pay for products while consuming and updating the medical checkup points accumulated and stored corresponding to the user of the user terminal, and for recommending and displaying, on the electronic commerce site, the recommended products extracted from the products by the recommended product extraction process; A program to execute.

Images