JP6205380B2 - Health management system, server device and program thereof - Google Patents

Description

  Embodiments of the present invention relate to a health management system that provides information useful for user health management based on menu information for eating and drinking, and a server device and a program for the system.

  There is already known a health management system in which menu information such as breakfast, lunch, dinner, etc. is registered for each user, and the calorie content of food contained in each menu is managed as the amount of ingested nutrients. . In this type of health management system, the amount of ingested nutrients is divided into a plurality of groups according to nutritional characteristics, and the aggregated value for each group is imaged to show the index of nutritional balance to the user.

  A typical example of such an index is the “four-group score method” by Women's Nutrition University. The “four-group score method” divides food into four groups (four groups) according to nutritional characteristics. Specifically, the first group is milk, dairy products and eggs, the second group is seafood, meat, beans and bean products, the third group is vegetables, strawberries and fruits, and the fourth group is cereals, fats and oils. And sugar. In the “four-group score method”, how much food should be consumed, how much food should be consumed, and the like are represented by a pie chart illustration.

  In addition, there is a “meal balance guide” which was formulated as a tool that the Ministry of Health, Labor and Welfare and the Ministry of Agriculture, Forestry and Fisheries jointly practice the dietary guidelines in an easy-to-understand manner. In the “Meal Balance Guide”, foods are divided into five groups: staple foods, side dishes, main dishes, milk / dairy products, and fruits. Shown in illustration.

  The “four-group score method” or “meal balance guide” classifies food according to nutritional characteristics, but the classification type may differ depending on the country or region. For this reason, when the health management system is to be deployed in many countries or regions, it is desired to present nutrition data with an index of classification suitable for the user.

JP 2006-251871 A

  The problem to be solved by the embodiments of the present invention is to provide a health management system capable of presenting nutrition data with an index of classification suitable for a user.

  In one embodiment, the health management system includes a first storage device, a second storage device, an acquisition unit, a registration unit, a generation unit, and a presentation unit. The first storage device stores receipt data including information related to a product provided or sold to the user in association with the user identification code. The second storage device stores information for specifying food and drink eaten by the user in association with the identification code of the user. The acquisition means acquires the user identification code. The registration unit is configured to obtain, from the receipt data stored in the first storage device in association with the user identification code acquired by the acquisition unit, information specifying food and drink that the user eats and drinks. The information is registered in the second storage device in association with the identification code. The generation unit generates a browsing image representing nutrition data of the food and drink specified by the information stored in the second storage device in association with the user identification code acquired by the acquisition unit. It is generated using an illustration defined in the country or region specified by the information for specifying. The presenting means presents the browse image generated by the generating means for viewing by the user.

The block diagram which shows the whole structure of the health management system in one Embodiment. The block diagram which shows the principal part structure of the accounting apparatus in a health care system. The block diagram which shows the principal part structure of the user terminal device in a health care system. The block diagram which shows the principal part structure of the receipt server in a health management system. The figure which shows the data structure of the receipt data memorize | stored in the electronic receipt area | region of a receipt server. The block diagram which shows the principal part structure of the nutrition data server in a health management system. The figure which shows the data structure of the product nutrition data memorize | stored in the product nutrition data area | region of a nutrition data server. The figure which shows the data structure of the food nutrition data memorize | stored in the food nutrition data area | region of a nutrition data server. The block diagram which shows the principal part structure of the health management server in a health management system. The figure which shows the data structure of the health management data memorize | stored in the health management data area | region of a health management server. The figure which shows the data structure of the meal balance data memorize | stored in the meal balance area | region of a health management server. The figure which shows the example of the illustration data in meal balance data. The flowchart which shows the procedure of the information processing which the processor of an accounting device performs based on a payment program. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a receipt client application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a receipt client application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a receipt client application. The flowchart which shows the procedure of the information processing which the processor of a receipt server performs based on a receipt server application. The flowchart which shows the procedure of the information processing which the processor of a receipt server performs based on a receipt server application. The flowchart which shows the procedure of the information processing which the processor of a receipt server performs in parallel by the task different from a receipt server application. The figure which shows the example of a transition of the screen displayed on the touchscreen of a user terminal device by the information processing based on a receipt client application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a health application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a health application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a health application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a health application. The flowchart which shows the procedure of the information processing which the processor of a user terminal device performs based on a health application. The flowchart which shows the procedure of the information processing which the processor of a health management server performs based on a health management application. The flowchart which shows the procedure of the information processing which the processor of a health management server performs based on a health management application. The flowchart which shows the procedure of the information processing which the processor of a health management server performs based on a health management application. The flowchart which shows the procedure of the information processing which the processor of a health management server performs based on a health management application. The schematic diagram which shows an example of the 1st nutrition analysis screen displayed on the touch panel of a user terminal device. The schematic diagram which shows an example of the 2nd nutrient analysis screen displayed on the touch panel of a user terminal device. The schematic diagram which shows an example of the goods list screen displayed on the touch panel of a user terminal device. The schematic diagram which shows an example of the food input screen displayed on the touch panel of a user terminal device. The schematic diagram which shows the state which converted the nutrition balance guide into the meal balance guide in the nutrition analysis screen shown in FIG. The schematic diagram which shows an example of the country designation | designated screen displayed on the touch panel of a user terminal device. The schematic diagram which shows the state which converted the meal balance guide into another pattern in the nutrition analysis screen shown in FIG.

Hereinafter, an embodiment of a health management system will be described with reference to the drawings.
The health management system of this embodiment is linked with an electronic receipt system. The electronic receipt system digitizes the information (receipt data) described in the receipt and downloads the digitized receipt data to the user terminal device via the Internet or the like so that the consumer user can receive the receipt. It is a system that can be received electronically. A user terminal device is a personal computer, a smart phone, a mobile phone, a tablet terminal etc., for example.

[Description of health management system]
FIG. 1 is a block diagram showing the overall configuration of the health management system 100.
The health management system 100 includes an accounting device 10, a user terminal device 20, a receipt server 30, a nutrition data server 40, and a health management server 50. In FIG. 1, the accounting device 10, the user terminal device 20, the receipt server 30, the nutrition data server 40, and the health management server 50 are shown one by one, but each number is arbitrary. The accounting device 10, the user terminal device 20, the receipt server 30, the nutrition data server 40 and the health management server 50 can exchange data via the network 200. The network 200 includes, for example, the Internet and a mobile communication network. The network 200 may include a local area network (LAN).

  The accounting device 10 is installed in a store that provides a product to be eaten or eaten, a so-called restaurant or the like. The accounting device 10 may be installed in a retail store or the like that sells products for eating and drinking. The accounting apparatus 10 performs accounting processing, which is data processing for accounting for the price for the provision or sale of merchandise. In addition, accounting includes the calculation and settlement of the above price. When a plurality of accounting apparatuses 10 are included in the health management system 100, the plurality of accounting apparatuses 10 may be installed in the same store or distributed in different stores.

  Based on the operation of the user of the health management system 100, the user terminal device 20 registers the menu information that the user has ingested for each meal such as breakfast, lunch, dinner, and the image for causing the user to browse the nutrition data. Display and so on. Nutritional data includes the amount of calories and salt contained in the menu. When a plurality of user terminal devices 20 are included in the health management system 100, the plurality of user terminal devices 20 may be used by the same user or individually by different users. Alternatively, one user terminal device 20 may be shared by a plurality of users.

  The receipt server 30 collects and accumulates receipt data representing the result of the accounting performed by the accounting device 10 from the accounting device 10. The receipt server 30 generates a receipt image representing the contents of the receipt data and transmits the receipt image to the user terminal device 20.

  The nutrition data server 40 holds nutrition data relating to food and drink provided or sold as a product at the store where the accounting apparatus 10 is installed. Further, the nutrition data server 40 holds nutrition data relating to food and drink cooked mainly at home as a menu for meals such as “rice”, “miso soup”, “curry rice”, and the like. The nutrition data server 40 transmits necessary nutrition data to the health management server 50 in response to a request from the health management server 50.

  The health management server 50 browses the nutrition data regarding the food and drink ingested by the user based on the receipt data stored in the receipt server 30 and the menu information for each meal registered via the user terminal device 20. An image is generated and transmitted to the user terminal device 20.

[Description of Accounting Device 10]
FIG. 2 is a block diagram showing the main configuration of the accounting apparatus 10.
The accounting apparatus 10 includes a processor 101, a main memory 102, an auxiliary storage device 103, a communication interface 104, an I / O (input / output) interface 105, a system transmission path 106, and the like. The processor 101, the main memory 102, the auxiliary storage device 103, the communication interface 104, and the I / O interface 105 are connected by a system transmission path 106. The system transmission path 106 includes an address bus, a data bus, a control signal line, and the like.

  In the accounting apparatus 10, a computer is constituted by a processor 101, a main memory 102, an auxiliary storage device 103, and a system transmission path 106 connecting them.

  The processor 101 corresponds to the central part of the computer. The processor 101 controls each unit to implement various functions as the accounting apparatus 10 according to the operating system and application programs.

  The main memory 102 corresponds to the main storage portion of the computer. The main memory 102 includes a nonvolatile memory area and a volatile memory area. The main memory 102 stores an operating system and application programs in a nonvolatile memory area. The main memory 102 may store data necessary for the processor 101 to execute processing for controlling each unit in a nonvolatile or volatile memory area. The main memory 102 uses a volatile memory area as a work area in which data is appropriately rewritten by the processor 101.

  The auxiliary storage device 103 corresponds to the auxiliary storage portion of the computer. The auxiliary storage device 103 is, for example, an EEPROM (electrically erasable programmable read-only memory), an HDD (hard disc drive), or an SSD (solid state drive). The auxiliary storage device 103 stores data used when the processor 101 performs various processes, or data generated by the process in the processor 101. The auxiliary storage device 103 stores application programs.

  An application program stored in the auxiliary storage device 103 is a settlement program P11. However, the settlement program P11 may be downloaded via the Internet, for example, and written to the auxiliary storage device 103 in response to an operation by the administrator of the accounting apparatus 10 or the installation operator of the accounting apparatus 10. That is, the transfer of the accounting apparatus 10 to the user of the accounting apparatus 10 may be performed in a state where the settlement program P11 is not stored in the auxiliary storage device 103.

  The communication interface 104 is an interface for data communication via the network 200. As the communication interface 104, for example, a known communication device for performing data communication via the Internet can be used.

  The I / O interface 105 is an interface for data communication performed with various input / output devices. Although not shown, for example, a handy scanner, a touch panel, a card reader, and the like are appropriately connected to the I / O interface 105.

  As the hardware of the accounting apparatus 10, an existing point-of-sale (POS) terminal apparatus or an electronic cash register can be used.

[Description of User Terminal Device 20]
FIG. 3 is a block diagram showing a main configuration of the user terminal device 20.
The user terminal device 20 is a portable information processing device such as a smartphone, a mobile phone, or a tablet terminal. The user terminal device 20 used for registering menu information for each meal, browsing nutrition data, and the like may be a stationary information processing device such as a desktop personal computer.

  The user terminal device 20 includes a processor 201, a main memory 202, an auxiliary storage device 203, a touch panel 204, a communication interface 205, a system transmission path 206, and the like. Descriptions of the processor 201, the main memory 202, the auxiliary storage device 203, the communication interface 205, and the system transmission path 206 are the same as those of the accounting apparatus 10, and are omitted here.

  In the user terminal device 20, the application program stored in the auxiliary storage device 203 includes an application program for a receipt client (hereinafter referred to as a receipt client application) P21, and health management using menu information for each meal. Application program (hereinafter referred to as health application) P22. However, typically, the receipt client application P21 and the health application P22 are downloaded via the Internet, for example, and written to the auxiliary storage device 203 in response to an operation by the user of the user terminal device 20. That is, the transfer of the user terminal device 20 to the user of the user terminal device 20 is performed in a state where the receipt client application P21 and the health application P22 are not stored in the auxiliary storage device 203. However, the user terminal device 20 in which the receipt client application P21 and the health application P22 are stored in the auxiliary storage device 203 may be transferred to the user of the user terminal device 20.

  The touch panel 204 functions as an input device and a display device of the user terminal device 20. On the touch panel 204, an icon for starting the receipt client application P21 is displayed by processing of the processor 201 based on the operating system.

[Description of Receipt Server 30]
FIG. 4 is a block diagram showing a main configuration of the receipt server 30.

  The receipt server 30 includes a processor 301, a main memory 302, an auxiliary storage device 303, a communication interface 304, a system transmission path 305, and the like. Descriptions of the processor 301, main memory 302, auxiliary storage device 303, communication interface 304, and system transmission path 305 are the same as those of the accounting apparatus 10, and are omitted here.

  In the receipt server 30, an application program stored in the auxiliary storage device 303 includes an application program (hereinafter referred to as a receipt server application) P31 for the receipt server 30.

  The receipt server 30 can use, for example, a general-purpose server device or computer device as basic hardware. In the receipt server 30, a server device or a computer device in which the receipt server application P 31 is not stored in the auxiliary storage device 303 and the receipt server application P 31 may be individually transferred to the user of the receipt server 30. At this time, the transfer of the receipt server application P31 can be realized by recording on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network. In this case, the receipt server application P31 is written in the auxiliary storage device 303 in accordance with an operation by the administrator of the receipt server 30 or the installation operator of the receipt server 30.

  The processor 301 allocates a part of the storage area of the auxiliary storage device 303 to the electronic receipt area W31 in order to execute processing based on the receipt server application P31. The electronic receipt area W31 stores receipt data. Further, the processor 301 sets a part of the storage area of the auxiliary storage device 303 as the country code area W32. The country code area W32 stores a country code for identifying the country or area where the receipt server 30 is installed.

FIG. 5 shows the data structure of receipt data.
The receipt data includes an electronic receipt code 311, a user code 312, date / time data 313, settlement data 314, and detailed data 315.

The electronic receipt code 311 is a unique code that identifies each piece of receipt data.
The user code 312 is a unique code that identifies the user of the health management system 100.

  The date / time data 313 is data of date and time when settlement is performed. The date / time data 313 serves as an index for determining the timing at which the user eats or drinks a product that is a food or drink. The date and time data when the settlement is made is an example of this time information. Apart from the time information, it also corresponds to the date and time when the user entered the store or the date and time when the product was ordered.

  The settlement data 314 is data representing the settlement result. The item of data included in the payment data 314 is arbitrary, but for example, it is assumed that the payment amount, the payment method, the store code of the store where the payment was made, and the like are included. The store code is a unique code for identifying each of the plurality of stores when the plurality of accounting devices 10 are distributed and arranged in the plurality of stores.

  The detail data 315 includes a list representing a product code, a name, a unit price, and the like related to a product for which payment is made.

  Here, the electronic receipt area W31 functions as a first storage device.

[Description of nutrition data server 40]
FIG. 6 is a block diagram showing a main configuration of the nutrition data server 40.

  The nutrition data server 40 includes a processor 401, a main memory 402, an auxiliary storage device 403, a communication interface 404, a system transmission path 405, and the like. The description of the processor 401, the main memory 402, the auxiliary storage device 403, the communication interface 404, and the system transmission path 405 is the same as that of the accounting apparatus 10, and will be omitted here.

  In the nutrition data server 40, the application programs stored in the auxiliary storage device 403 include an application program (hereinafter referred to as a nutrition data server application) P41 for the nutrition data server 40.

  Part of the storage area of the auxiliary storage device 403 is used as a product nutrition data area W41 and a food nutrition data area W42. The product nutrition data area W41 stores nutrition data (hereinafter, referred to as product nutrition data) for each food or drink provided or sold as a product at the store where the accounting apparatus 10 is installed. The food nutrition data area W42 stores nutrition data (hereinafter, defined as food nutrition data) for each food and drink cooked mainly at home.

  FIG. 7 is a diagram showing a data structure of commercial nutrition data. The product nutrition data includes a store code 411, a product code 412, calorie data 413, and nutrition balance data 414.

  The store code 411 is a code for identifying the store where the accounting apparatus 10 is installed, and is the same series as the store code included in the receipt data. The product code 412 is a code for identifying food and drink provided or sold as a product. The product code 412 may be unique with respect to each food or drink provided or sold at the store identified by the store code 411. That is, the product code 412 included in different nutrition data including different store codes 411 may be different for the same food and drink. However, the product code 412 matches the product code included in the receipt data generated by the accounting device 10 installed in the store identified by the store code 411.

  The calorie data 413 represents the calorie about the food / beverage identified by the product code 412 among the food / beverage provided or sold as a product at the store identified by the store code 411.

  The nutritional balance data 414 represents the nutritional balance of the food and drink identified by the product code 412 among the foods and drinks provided or sold as products at the store identified by the store code 411. The nutritional balance is represented by a score for each of a plurality of groups (food groups) determined by, for example, a four-group score method. The nutrition balance data 414 may include the contents of nutrients such as salt, carbohydrates, lipids, proteins, minerals, and vitamins.

  FIG. 8 is a diagram showing a data structure of food nutrition data. The food nutrition data includes a food code 421, an icon 422, calorie data 423, and nutrition balance data 424.

  The food code 421 is a code for identifying food and drink provided at home as a menu. The food code 421 may be unique with respect to the above food and drink. Even if there is the same item among the food and drink provided or sold as a product in the store, the food code 421 does not need to match the product code 412 of the food or drink.

  The icon 422 is a pictorial symbol representing food and drink identified by the food code 421. The icons 422 are desirably different for each food and drink, but do not prevent them from being the same. Each icon 422 includes text data indicating the name of the food or drink represented by the icon 422.

  The calorie data 423 represents the calories of food and drink identified by the food code 421.

  The nutrition balance data 424 represents the nutrition balance for the food and drink identified by the food code 421. The nutritional balance is represented by a score for each of a plurality of groups (food groups) determined by, for example, a four-group score method. The nutrition balance data 424 may include the contents of nutrients such as salt, carbohydrates, lipids, proteins, minerals, and vitamins.

  The communication interface 404 is an interface for data communication via the network 200. As the communication interface 404, for example, a known communication device for performing data communication via the Internet can be used.

  The nutrition data server 40 can use, for example, a general-purpose server device or computer device as basic hardware. In the nutrition data server 40, the server device or computer device in which the nutrition data server application P41 is not stored in the auxiliary storage device 403 and the nutrition data server application P41 may be individually transferred to the user. At this time, the transfer of the nutrition data server application P41 can be realized by recording on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, or by downloading via a network. In this case, the nutrition data server application P41 is written in the auxiliary storage device 403 in accordance with an operation by the administrator of the nutrition data server 40 or the installation operator of the nutrition data server 40.

[Description of health management server 50]
FIG. 9 is a block diagram showing a main configuration of the health management server 50.

  The health management server 50 includes a processor 501, a main memory 502, an auxiliary storage device 503, a communication interface 504, a system transmission path 505, and the like. Descriptions of the processor 501, main memory 502, auxiliary storage device 503, communication interface 504, and system transmission path 505 are the same as those of the accounting apparatus 10, and only differences are described here. Note that the communication interface 504 constitutes communication means with the user terminal device 20.

  In the health management server 50, the application programs stored in the auxiliary storage device 503 include an application program (hereinafter referred to as a health management application) P51 for the health management server 50.

  A part of the storage area of the auxiliary storage device 503 is used as a health management data area W51 and a meal balance guide area W52. The health management data area W51 stores health management data for each user of the health management system 100. The health management data includes information on food and drink taken by the user for each meal such as breakfast, lunch, and dinner. The meal balance guide area W52 stores data on meal balance guides (hereinafter, defined as meal balance data) formulated for each country or region for each meal balance guide.

  FIG. 10 is a diagram illustrating a data structure of health management data. The health management data includes a user code 511 and a plurality of menu data 512. The user code 511 is a unique code that identifies the user of the health management system 100. The user code 511 matches the user code 312 of the electronic receipt data.

  Menu data 512 includes a date, category, and item code. The date is the date on which the user identified by the user code 511 has eaten. The category is information for identifying the meal. That is, the category in the menu data 512 is information for identifying “breakfast”, “lunch”, “dinner”, and “snack”, respectively. In the present embodiment, the menu data 512 has four categories of “breakfast”, “lunch”, “dinner”, and “snack”, but is not necessarily limited to this category.

  The item code is a code that identifies the food or drink that was consumed during the meal. The item code includes a “store code and product code” of food and drink for which calorie data and nutrition balance data are managed in the product nutrition data area W41 of the nutrition data server 40, and calorie data and nutrition in the food nutrition data area W42. There is a “food code” for food and drink for which balance data is managed. In one menu data, the item code may be a mixture of “store code and product code” and “food code”, or only one of them. In short, it is only necessary to be able to specify food and drink that are eaten and eaten one by one as a menu of meals specified by the corresponding date and classification.

  Here, the health management data area W51 functions as a second storage device.

  FIG. 11 is a diagram illustrating a data structure of meal balance data. The meal balance data includes a country code 521, country name data 522, illustration data 523, and classification data 524.

  The country code 521 is a unique code for identifying the country or region where the meal balance guide set in the meal balance guide area W52 is formulated. The country name data 522 is the name of the country or region identified by the corresponding country code 521.

  The illustration data 523 is illustration data used in the meal balance guide formulated in the country or region identified by the corresponding country code 521. As shown in FIG. 12, the illustration data 523 includes data of a frame-shaped illustration G2 formulated by Japan, data of a dish-shaped illustration G3 formulated by the United States, and the like.

  The classification data 524 represents a food group applied by the meal balance guide formulated in the country or region identified by the corresponding country code 521. For example, the meal balance guide classification data 524 using the Komagata illustration G2 is data representing five food groups of staple food, side dish, main dish, milk / dairy product, and fruit. Meal balance guide classification data 524 using a dish-shaped illustration G3 represents five food groups: Grains, Proteins, Vegetables, Fruits, and Milk / Dairy. It becomes data.

  The country code has the same format as the country code stored in the country code area W32 of the receipt server 30. That is, the country code of the meal balance data for the meal balance guide in the country or region where the receipt server 30 is installed matches the country code stored in the country code area W32 of the receipt server 30. In the present embodiment, the country code “0” is unused.

[Description of operation of health management system 100]
(Explanation of operations related to electronic receipts)
Next, the operation of the health management system 100 will be described. First, operations related to storage and browsing of electronic receipts will be described. Note that the contents of the various processes described below are examples, and various processes capable of obtaining similar results can be used as appropriate.

  The user of the health management system 100 installs the receipt client application P21 and the health application P22 on the user terminal device 20. The user performs user registration with respect to the receipt server 30 by a predetermined method. As a result of this user registration, the receipt server 30 defines a unique user code for identifying the user, and a user name and password designated by the user are associated with the user code. In this embodiment, an email address is used as the user name. The receipt server 30 may determine the user name and password randomly.

  When a user eats or drinks food or purchases at a store where the accounting apparatus 10 belonging to the health management system 100 is installed, the user accounts using the accounting apparatus 10.

  FIG. 13 is a flowchart showing an information processing procedure executed by the processor 101 of the accounting apparatus 10 based on the settlement program P11. First, the processor 101 clears the product list area set in the main memory 102 (Act 101). The product list area is a storage area for describing a list of information about products for which purchase registration has been completed (hereinafter referred to as a product list).

  When the product list area has been cleared, the processor 101 confirms whether or not a product to be purchased and registered is designated (Act 102). If a product to be registered for purchase is not designated (NO in Act 102), processor 101 confirms whether a user code has been input (Act 103). If the user code has not been input (NO in Act 103), the processor 101 confirms whether or not the closing of purchase registration has been designated (Act 104). If the closing of purchase registration is not specified (NO in Act 104), the processor 101 confirms whether or not a product to be registered for purchase is specified again (Act 102). Here, the processor 101 waits for a product to be registered for purchase, a user code input, or a tightening of purchase registration specified in the processes of Act 102 to Act 104.

  For example, when a user who has finished eating and drinking in a store offers a checkout to a store clerk, the store clerk operates an input device connected to the I / O interface 105 of the checkout device 10 to specify a product that the user has eaten or consumed. Alternatively, when a user who has finished shopping at the store offers an account to the store clerk, the store clerk operates the input device to specify the product purchased by the user. Upon receiving these operations, the processor 101 detects that an operation for designating a product to be registered for purchase has been performed.

  When the processor 101 detects that an operation for specifying a product to be registered for purchase is made in the standby state of Act 102 to Act 104 (YES in Act 102), the processor 101 updates the product list to include information on the specified product. (Act 105). The product information includes a product code, a product name, a price, and the like.

The product information may include the calorie data and nutrition balance data of the product set in the product nutrition data area W41 of the nutrition data server 40. That is, the processor 101 notifies the nutrition data server 40 of the store code and the product code. Upon receiving this notification, the processor 401 of the nutrition data server 40 searches the product nutrition data area W41. Then, the processor 401 reads the calorie data and the nutrition balance data associated with the notified store code and product code from the product nutrition data area W41, and transmits them to the accounting apparatus 10. The processor 101 of the accounting apparatus 10 adds the calorie data and the nutrition balance data received from the nutrition data server 40 to the product list.
After updating the product list, the processor 101 returns to the standby state of Act102 to Act104.

  By the way, the user who wants to use the electronic receipt service for the above-described transaction activates the receipt client application P21 on the user terminal device 20. When the receipt client application P21 is activated, the processor 201 executes information processing based on the receipt client application P21. This information processing is supported by the receipt server 30 activated by the receipt server application P31.

  14 to 16 are flowcharts showing a procedure of information processing executed by the processor 201 of the user terminal device 20 based on the receipt client application P21. 17 and 18 are flowcharts showing the information processing procedure executed by the processor 301 of the receipt server 30 based on the receipt server application P31. FIG. 19 is a flowchart showing an information processing procedure executed in parallel by the processor 301 of the receipt server 30 by a task different from the receipt server application P31. FIG. 10 is a diagram illustrating a transition example of a screen displayed on the touch panel 204 of the user terminal device 20 by information processing based on the receipt client application P21. Hereinafter, main processing of the processor 201 in the user terminal device 20 and main processing of the processor 301 in the receipt server 30 will be described with reference to FIGS. 14 to 20.

  As shown in FIG. 14, when the information processing based on the receipt client application P21 is activated, the processor 201 sets the screen of the touch panel 204 as the login screen SC1 (Act 201). The processor 201 waits for a login instruction (Act 202).

  As shown in FIG. 20, the login screen SC1 includes input fields F11 and F12 and a button B11. The input column F11 is a column for the user to input a mail address set as a user name. The input field F12 is a field for the user to input a password associated with the user code together with the mail address. The button B11 is touched by the user to instruct login. In the login screen SC1 in the initial state, the input fields F11 and F12 are blank.

  The user touches the button B11 after inputting the e-mail address and password designated at the time of user registration in the input fields F11 and F12, respectively. Upon receiving these operations, the processor 201 detects a login instruction.

  If the processor 201 detects a login instruction in the standby state of Act 202 (YES in Act 202), it makes a login request to the receipt server 30 (Act 203). Specifically, the processor 201 stores the mail address and password input in the input fields F11 and F12 in the main memory 302, respectively. Then, upon receiving the touch input of the button B11, the processor 201 transmits a login request from the communication interface 205 to the receipt server 30 to the network 200. The login request includes the mail address and password login data stored in the main memory 302.

  As shown in FIG. 17, the processor 301 that has started the information processing based on the receipt server application P3 waits for a login request (Act 301). When the communication interface 304 receives the login request transmitted from the user terminal device 20 to the network 200 (YES in Act 301), the processor 301 performs an authentication process based on the login data included in the received login request. (Act 302). Specifically, the processor 301 confirms whether a user code associated with an email address and a password included in the login request is set. If the user code is set, the processor 301 succeeds in authentication. If the user code is not set, the processor 301 fails authentication.

  The processor 301 that has performed the authentication process confirms whether or not the authentication is successful (Act 303). If the authentication fails (NO in Act 303), the processor 301 transmits an error notification from the communication interface 304 to the user terminal device 20 to the network 200 (Act 304). After transmitting the error notification, the processor 301 returns to the processing of Act 301. That is, the processor 301 waits for a login request. Thereafter, the processor 301 repeats the subsequent processing in the same manner as described above.

  If the authentication is successful (YES in Act 303), as shown in FIG. 18, the processor 301 generates top screen data, and sends the top screen data from the communication interface 304 to the user terminal device 20 in the network 200. (Act 305). The top screen data represents an image for setting the screen of the touch panel 204 of the user terminal device 20 as the top screen SC2. The processor 301 stores the user code that has been successfully authenticated in the main memory 302 as the user code of the logged-in user.

  In Act 203 of FIG. 14, the processor 201 which has made the login request confirms whether an error has been notified (Act 204). When the error notification transmitted from the receipt server 30 to the network 200 is received by the communication interface 205 (YES in Act 204), the processor 201 returns to the processing of Act 201. That is, the processor 201 sets the login screen SC1 to an initial state. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above.

  When the top screen data is received by the communication interface 205 instead of the error notification (NO in Act 204), the processor 201 stores the top screen data in the main memory 202 or the auxiliary storage device 203 as shown in FIG. . Then, the processor 201 sets the screen of the touch panel 204 as the top screen SC2 based on the received top screen data (Act 205).

  As shown in FIG. 20, the top screen SC2 includes a barcode C11 and buttons B21, B22, B23. B24 and B25. The barcode C11 represents a user code associated with the email address and password included in the login request. The button B21 is touched by the user to view the latest receipt.

  The button B22 is touched by the user to instruct the transition to the top screen SC2. The button B23 is touched by the user to instruct the transition to the simple receipt information list screen. The button B24 is touched by the user to instruct the transition to the nutrition analysis screen. The button B25 is touched by the user to instruct a transition to a screen different from the top screen, the list screen, and the nutrition analysis screen. This screen is a screen for accepting user operations for various settings, for example. The buttons B22, B23, B24, and B25 also have a function as an index that indicates which screen is the current screen. In the case of the top screen SC2, the frame of the button B22 is thicker than the other buttons B23, B24, B25.

  The user who has confirmed the top screen SC2 presents the bar code C11 displayed on the top screen SC2 to the store clerk. The store clerk causes the handy scanner, which is one of the input / output devices connected to the I / O interface 105 of the accounting apparatus 10, to read the barcode C11. When the bar code C11 is read by the handy scanner, the processor 101 of the accounting apparatus 10 receives the code represented by the bar code C11 as a user code.

  When the processor 101 detects that a user code has been input via the input device in the standby state of Act 102 to Act 104 in FIG. 13 (YES in Act 103), the processor 101 stores this user code in the main memory 202 or the auxiliary storage device 203. Store (Act 106). After storing the user code, the processor 101 returns to the standby state of Act 102 to Act 104.

  When the store clerk finishes all the operations for designating the merchandise that the user eats or drinks or the merchandise purchased by the user to the accounting apparatus 10, the clerk operates the input device of the accounting apparatus 10 to designate the closing of purchase registration. In response to this operation, the processor 101 in the standby state of Act 102 to Act 104 detects that the closing of purchase registration is designated. When it is detected that the closing of the purchase registration is designated (YES in Act 104), the processor 101 performs a settlement process for settlement of the price related to the provision or sale of the product shown in the product list (Act 107). For this settlement process, a process executed by an existing POS device or the like can be used as it is.

  When the settlement process is completed, the processor 101 confirms whether the user code is stored in the main memory 202 or the auxiliary storage device 203 (Act 108). When the user code is stored (YES in Act 108), the processor 101 generates receipt data based on the information included in the product list (Act 109). The receipt data includes an electronic receipt code 311, a user code 312, date / time data 313, settlement data 314, and detailed data 315.

  The processor 101 that has generated the receipt data confirms whether to issue a paper receipt (Act 110). Specifically, the processor 101 displays a screen for inquiring whether the user wants to issue a paper receipt on a touch panel connected to the I / O interface 105. If the processor 101 detects that an input indicating that a paper receipt is not issued is made by an operation on the touch panel (NO in Act 110), the processor 101 transmits the receipt data to the receipt server 30 (Act 111). Specifically, the processor 101 generates a transmission file including the receipt data generated by the processing of Act 109 and the user code stored in the main memory 102 or the auxiliary storage device 103. Then, the processor 101 causes the communication interface 104 to transmit the transmission file to the receipt server 30 via the network 200 using a protocol such as FTP (file transfer protocol).

  On the other hand, when an input to issue a paper receipt is made (YES in Act 110), or when a user code is not stored (NO in Act 108), the processor 101 issues a paper receipt. Control (Act 112). Specifically, the processor 101 controls a printer that is one of the input / output devices connected to the I / O interface 105 to issue a paper receipt.

  When the receipt data is transmitted to the receipt server 30 or issuance of the paper receipt is completed, the processor 101 clears the product list area again (Act 101) and repeats the subsequent processing in the same manner as described above.

  In the above description, the processor 101 confirms whether to issue a paper receipt after generating receipt data. In another embodiment, the transmission file including the receipt data and the user code may be transmitted to the receipt server 30 without confirming whether to issue a paper receipt.

  The transmission file transmitted via the network 200 is received by the communication interface 304 of the receipt server 30. As shown in FIG. 19, the processor 301 of the receipt server 30 waits for reception of a transmission file including receipt data and a user code (Act 321). When the processor 301 receives the transmission file (YES in Act 321), it stores the receipt data included in this transmission file in the electronic receipt area W31 of the auxiliary storage device 303 in association with the user code included in the transmission file. (Act 322). Thereafter, the processor 301 waits for reception of the transmission file again (Act 321).

  Thus, the receipt data when the user who wants to use the electronic receipt service eats or drinks at the store or the purchase data when shopping at the store is stored in the electronic receipt area W31 of the receipt server 30.

  Now, the user who has finished the transaction can view the receipt for the transaction by touching the button B21 displayed on the top screen SC2 of the user terminal device 20.

  In Act 205 of FIG. 15, the processor 201 that has displayed the top screen SC2 on the touch panel 204 confirms whether or not an instruction to shift to the latest receipt screen has been given. That is, the processor 201 confirms whether or not the button B21 is touched (Act 206). If button B21 is not touched (NO in Act 206), processor 201 confirms whether or not an instruction to shift to the receipt list screen has been given. That is, the processor 201 confirms whether the button B23 is touched (Act 207). If button B23 has not been touched (NO in Act 207), processor 201 confirms whether transition to the nutrition analysis screen has been instructed. That is, the processor 201 confirms whether the button B24 is touched (Act 208). If button B24 has not been touched (NO in Act 208), processor 201 determines whether or not an instruction to shift to another screen has been issued. That is, the processor 201 confirms whether the button B25 is touched (Act 209). If button B25 has not been touched (NO in Act 209), processor 201 confirms whether or not an instruction to shift to the latest receipt screen has been issued again (Act 206).

  Therefore, the processor 201 waits for the button B21, B23, B24, or B25 on the top screen SC2 to be touched in the processes of Act206 to Act209. Note that since the button B22 is a button for instructing transition to the top screen SC2, the processor 201 ignores the input even if it is touched.

  When it is detected that the button B21 is touched via the touch panel 204 in the standby state of Act 206 to Act 209 (YES in Act 206), the processor 201 sends a display request for an image indicating the latest receipt from the communication interface 205 to the receipt server. 30 to the network 200 (Act 210). This display request includes the user code stored in the main memory 202 or the auxiliary storage device 203.

  In Act 305 of FIG. 18, the processor 301 that has transmitted the top screen data confirms whether an image display request indicating the latest receipt has been received (Act 306). If not received, the processor 301 confirms whether a display request for the list screen has been received (Act 307). If not received, the processor 301 confirms whether another image display request has been received (Act 308). If not received, the processor 301 confirms again whether an image display request indicating the latest receipt has been received (Act 306).

  Therefore, the processor 301 that has transmitted the top screen data waits for a display request for an image or a list screen showing the latest receipt by the processing of Act 306 to Act 308. When the communication interface 304 receives a display request for an image indicating the latest receipt in this standby state (YES in Act 306), the processor 301 searches the electronic receipt area W31. Then, the processor 301 obtains the receipt data with the latest date / time data among the receipt data stored in the electronic receipt area W31 in association with the user code included in the received display request (Act 309).

  If the receipt data is acquired, the processor 301 generates receipt screen data from the receipt data. Then, the processor 301 transmits the receipt screen data from the communication interface 304 to the user terminal device 20 to the network 200 (Act 310). The receipt screen data represents an image for setting the screen of the touch panel 204 of the user terminal device 20 as a receipt screen SC3.

  In Act 210 of FIG. 15, the processor 201 that has transmitted a display request for an image indicating the latest receipt waits for receipt screen data transmitted from the receipt server 30 in response to the display request. If the receipt screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the receipt screen SC3 based on the receipt screen data (Act 211).

  As shown in FIG. 20, on the receipt screen SC3, a receipt image R1 representing the details of the commercial transaction is displayed. In addition, an image R2 indicating simple receipt data (transaction date, transaction time, store name, transaction amount) for specifying the commercial transaction is also displayed on the receipt screen SC3.

  Receipt screen SC3 includes buttons B22, B23, B24, and B25 similar to top screen SC2. In the receipt screen SC3, the frame of the button B23 is thicker than the other buttons B22, B24, and B25.

  In Act 211 of FIG. 15, the processor 201 that has displayed the receipt screen SC3 on the touch panel 204 confirms whether or not an instruction to shift to the receipt list screen has been given. That is, the processor 201 confirms whether the button B23 is touched (Act 212). If button B23 has not been touched (NO in Act 212), processor 201 determines whether or not an instruction to shift to the top screen has been given. That is, the processor 201 confirms whether or not the button B22 is touched (Act 213). When button B22 is not touched (NO in Act 213), processor 201 confirms whether or not an instruction to shift to the nutrition analysis screen is given. That is, the processor 201 confirms whether the button B24 is touched (Act 214). If button B24 has not been touched (NO in Act 214), processor 201 determines whether or not an instruction to shift to another screen has been issued. That is, the processor 201 confirms whether or not the button B25 is touched (Act 215). When button B25 is not touched (NO in Act 215), processor 201 confirms whether or not an instruction to shift to the receipt list screen has been issued again (Act 212).

  Accordingly, the processor 201 waits for the button B23, B22, B24, or B25 on the receipt screen SC3 to be touched in the processes of Act212 to Act215.

  A user who wants to view a receipt of another transaction instead of the latest receipt touches button B23 on top screen SC2 or receipt screen SC3.

  When it is detected that the button B23 is touched via the touch panel 204 in the standby state of Act 206 to Act 209 or in the standby state of Act 212 to Act 215 (YES in Act 207 or YES in Act 212), the processor 201 is shown in FIG. As described above, the display request for the list screen is transmitted from the communication interface 205 to the receipt server 30 to the network 200 (Act 216). This display request includes the user code stored in the main memory 202 or the auxiliary storage device 203.

  In Act 305 of FIG. 18, the processor 301 that has transmitted the top screen data waits for a display request for a list screen or the like by the processing of Act 306 to Act 308.

  On the other hand, in Act 310 of FIG. 18, the processor 301 that transmitted the receipt screen data confirms whether or not a list screen display request has been received (Act 311). If not received, the processor 301 confirms whether or not a display request for the top screen has been received (Act 312). If not received, the processor 301 confirms whether a request to display another image has been received (Act 313). If not received, the processor 301 confirms again whether a request to display the list screen has been received (Act 311).

  Therefore, the processor 301 that has transmitted the receipt screen data waits for a display request such as a list screen or a top screen by the processing of Act 311 to Act 313.

  When the display request for the list screen is received in the standby state of Act 306 to Act 308 or Act 311 to Act 313 (YES in Act 307 or Act 311), the processor 301 searches the electronic receipt area W31. Then, the processor 301 acquires simple receipt data from all receipt data stored in the electronic receipt area W31 in association with the user code included in the received display request (Act 314). As described above, the simple receipt data includes the transaction date, transaction time, store name, and transaction amount included in the receipt data. The simple receipt data is not limited to the four items of transaction date, transaction time, store name, and transaction amount. Other items may be added, or any item may be deleted.

  If the simple receipt data is acquired, the processor 301 generates list screen data from the simple receipt data. Then, the processor 301 transmits the list screen data from the communication interface 304 to the user terminal device 20 to the network 200 (Act 315). The list screen data represents an image for setting the screen of the touch panel 204 of the user terminal device 20 as the list screen SC4.

  In Act 216 of FIG. 16, the processor 201 that has transmitted the receipt list display request waits for list screen data transmitted from the receipt server 30 in response to the display request. When the list screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the list screen SC4 based on the list screen data (Act 217).

  As shown in FIG. 20, the list screen SC4 displays an image R2 indicating simple receipt data (transaction date, transaction time, store name, transaction amount) for each receipt data. The list screen SC4 includes buttons B22, B23, B24, and B25 similar to the top screen SC2 or the receipt screen SC3.

  In Act 217 of FIG. 16, the processor 201 that displays the list screen SC4 on the touch panel 204 confirms whether any simple receipt data is designated from the list screen SC4. That is, the processor 21 confirms whether any image R2 of simple receipt data is touched (Act 218). When image R2 is not touched (NO in Act 218), processor 201 confirms whether or not an instruction to shift to the top screen is given. That is, the processor 201 confirms whether or not the button B22 is touched (Act 219). When button B22 is not touched (NO in Act 219), processor 201 confirms whether or not an instruction to shift to the nutrition analysis screen has been given. That is, the processor 201 confirms whether the button B24 is touched (Act 220). If button B24 has not been touched (NO in Act 220), processor 201 determines whether or not an instruction to shift to another screen has been issued. That is, the processor 201 confirms whether the button B25 is touched (Act 221). When button B25 has not been touched (NO in Act 221), processor 201 confirms whether simple receipt data has been designated again (Act 218).

  Therefore, the processor 201 waits for the image R2 on the list screen SC4 or the button B22, B24, or B25 to be touched in the processes of Act218 to Act221. Note that since the button B23 is a button for instructing transition to the list screen SC4, the processor 201 ignores the input even if it is touched.

  The user who browsed the list screen SC4 searches for receipt data to be browsed from the simple receipt data. When the simple receipt data of the receipt to be browsed is found, the user touches the image R2 of the simple receipt data.

  When it is detected that any one of the plurality of images R2 indicating the simple receipt data displayed on the list screen SC4 is touched in the standby state of Act 218 to Act 221 (YES in Act 218), the processor 201 Then, an image display request indicating the receipt specified by the simple receipt data of the touched image R2 is transmitted from the communication interface 205 to the receipt server 30 to the network 200 (Act 210). This display request includes the user code stored in the main memory 202 or the auxiliary storage device 203 and the simple receipt data of the touched image R2.

  In Act 315 of FIG. 18, the processor 301 that has transmitted the list screen data confirms whether or not it has received a display request for an image indicating a receipt specified by the simple receipt data (Act 316). If not received, the processor 301 confirms whether or not a display request for the top screen has been received (Act 317). If not received, the processor 301 confirms whether a display request for another image has been received (Act 318). If not received, the processor 301 confirms again whether an image display request indicating a receipt specified by the simple receipt data has been received (Act 316).

  Therefore, the processor 301 that has transmitted the list screen data waits for a display request for an image or a top screen showing the receipt specified by the simple receipt data by the processing of Act 316 to Act 318. In this standby state, when the communication interface 304 receives a display request for an image indicating a receipt specified by the simple receipt data (YES in Act 316), the processor 301 searches the electronic receipt area W31. Then, the processor 301 acquires receipt data that matches the simple receipt data among the receipt data stored in the electronic receipt area W31 in association with the user code included in the received display request (Act 309).

  If the receipt data is acquired, the processor 301 generates receipt screen data from the receipt data. Then, the processor 301 transmits the receipt screen data from the communication interface 304 to the user terminal device 20 to the network 200 (Act 310). Thereafter, the processor 301 enters a standby state for Act 311 to Act 313.

  In Act 210 of FIG. 15, the processor 201 that has transmitted a display request for an image indicating the receipt specified by the simple receipt data waits for receipt screen data transmitted from the receipt server 30 in response to the display request. If the receipt screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the receipt screen SC3 based on the receipt screen data (Act 211). The layout of the receipt screen SC3 at this time is the same as the receipt screen SC3 for the latest receipt.

  A user who wants to return the screen of the touch panel 204 from the receipt screen SC3 or the list screen SC4 to the top screen SC2 touches the button B22.

  When it is detected that the button B22 is touched via the touch panel 204 in the standby state of Act 212 to Act 215 or the standby state of Act 218 to Act 221 (YES in Act 213 or YES in Act 219), the processor 201 proceeds to the processing of Act 205. And return. That is, the processor 201 sets the screen of the touch panel 204 as the top screen SC2. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above.

  In Act 310 of FIG. 18, the processor 301 that transmitted the receipt screen data waits for a display request for the top screen or the like by the processing of Act 311 to Act 313. Similarly, in Act 315 of FIG. 18, the processor 301 that has transmitted the list screen data waits for a display request for the top screen or the like by the processing of Act 316 to Act 318.

  When a top screen display request is received in these standby states (YES in Act 312 or Act 317), the processor 301 returns to the processing of Act 305. That is, the processor 301 transmits the top screen data from the communication interface 304 to the user terminal device 20 to the network 200. Thereafter, the processor 301 repeats the subsequent processing in the same manner as described above.

(Explanation of operations related to health care)
Next, the operation | movement which concerns on health management based on the menu information for every meal is demonstrated. Note that the contents of the various processes described below are examples, and various processes capable of obtaining similar results can be used as appropriate.

  A user who has installed the health application P22 together with the receipt client application P21 on the user terminal device 20 can perform health management based on the menu information with the support of the nutrition data server 40 and the health management server 50. That is, the user can register information (menu information) on food and drink taken for each meal such as breakfast, lunch, and dinner by operating the user terminal device 20 in the health management server 50. And the user who registered menu information can browse the nutrition analysis screen showing the nutrition balance etc. for every meal or one day using the user terminal device 20. FIG. On the nutrition analysis screen, for example, the calorie intake amount and a distribution image of the nutritional balance obtained by the four-group score method are displayed. Moreover, it can replace with the distribution image of nutrition balance, and can also display the illustration of the meal balance guide of each country.

  In order to register the menu information and browse the nutrition analysis screen, it is necessary to start the health application P22 in the user terminal device 20. The health application P22 is activated by touching a button B23 displayed on the top screen CS, the receipt screen SC3, or the list screen SC4. That is, as shown in FIGS. 15 and 16, the processor 201 of the user terminal device 20 touches the button B23 in the standby state of Act 206 to Act 209, the standby state of Act 212 to Act 215, or the standby state of Act 218 to Act 221. Is detected (YES in Act 208, Act 214, or Act 220), the health application P22 is activated (Act 231).

  The processor 201 executes information processing based on the health application P22 until the health application P22 ends. This information processing is supported by the nutrition data server 40 activated by the nutrition data server application P41 and the health management server 50 activated by the health management application P51.

  FIG. 21 to FIG. 25 are flowcharts showing the information processing procedure executed by the processor 201 of the user terminal device 20 based on the health application P22. FIG. 26 to FIG. 29 are flowcharts showing the information processing procedure executed by the processor 501 of the health management server 50 based on the health management application P51. 30 to 36 are diagrams showing screens displayed on the touch panel 204 of the user terminal device 20 by information processing based on the health application P22. Hereinafter, main processing of the processor 201 in the user terminal device 20 and main processing of the processor 501 in the health management server 50 will be described with reference to FIGS. 21 to 36.

  As shown in FIG. 21, when the information processing based on the health application P22 is activated, the processor 201 sets date data representing “today's date” and “one day” in the date area and the division area set in the main memory 202, respectively. Is set (Act 241). The date data is detected from a system clock (clock) built in the user terminal device 20. The classification data represents a unit of data (such as calorie intake and nutritional balance distribution image) displayed on the nutrition analysis screen. The category data includes “one week”, “one month”, “breakfast”, “lunch”, “dinner”, “snack”, etc. in addition to “one day”.

  If the date data and the classification data are set, the processor 201 transmits a nutrition analysis request from the communication interface 205 to the health management server 50 to the network 200 (Act 242). This nutrition analysis request includes the user code stored in the main memory 202 or the auxiliary storage device 203, and date data and division data set in the date area and the division area. Therefore, at the stage where the health application P22 is activated, the classification data included in the nutrition analysis request is “one day”.

  As shown in FIG. 26, the processor 501 that has started the information processing based on the health management application P51 waits for a nutrition analysis request (Act 500). When the nutrition analysis request transmitted from the user terminal device 20 to the network 200 is received by the communication interface 504 (YES in Act 500), the processor 501 includes the user code, date data, and category included in the received nutrition analysis request. Data is stored in the main memory 502 or the auxiliary storage device 503. Further, the processor 501 searches the health management data area W51 with the stored user code, and acquires health management data associated with the user code. The processor 501 stores the acquired health management data in the main memory 502 or the auxiliary storage device 503 (Act 501).

  Next, the processor 501 confirms the stored segment data (Act 502). When the category data is “one day” (NO in Act 502), processor 501 extracts menu data 512 including the stored date data from the stored health management data. When the category data is “one week” (NO in Act 502), processor 501 extracts menu data 512 for the past week including the stored date data from the stored health management data. If the segment data is “one month” (NO in Act 502), processor 501 extracts menu data 512 for the past month including the stored date data from the stored health management data.

  The processor 501 stores the extracted menu data 512 in the main memory 502 or the auxiliary storage device 503. Based on the item code included in the stored menu data 512, the processor 501 generates a nutrition analysis screen for one day, one week, or one month (hereinafter referred to as a first nutrition analysis screen SC51). (Act 503).

  For example, when the category data is “one day”, the processor 301 matches the date with the date data stored from the health management data, and the categories are “breakfast”, “lunch”, “dinner”, and “snacks”. All menu data 512 are extracted. The processor 501 requests the nutrition data server 40 for calorie data and nutrition balance data of food and drink specified by the item code included in the extracted menu data 512.

  Upon receiving this request, the processor 401 of the nutrition data server 40 searches the product nutrition data area W41 or the food nutrition data area W42 by information processing according to the nutrition data server application P41, and calorie data of the requested food and drink And collect nutritional balance data. The processor 401 transmits the collected calorie data and nutrition balance data to the health management server 50 via the network 200.

  The processor 501 of the health management server 50 calculates the calorie intake based on the calorie data and nutrition balance data of food and drink received from the nutrition data server 40, and generates a nutrition balance distribution image G1 by the four-group score method. . Then, the processor 501 generates a first nutrition analysis screen SC51 for one day using the calorie intake amount, the nutrition balance distribution image G1, and the like.

  On the other hand, when the classification data is by meal, that is, “breakfast”, “lunch”, “dinner”, and “snack” (YES in Act 502), processor 501 stores the stored health management data. Menu data 512 including date data and segment data is extracted. The processor 501 stores the extracted menu data 512 in the main memory 502 or the auxiliary storage device 503. Then, the processor 501 generates a meal-specific nutrition analysis screen (hereinafter referred to as a second nutrition analysis screen SC52) based on the item code included in the menu data 512 (Act 504).

  For example, when the category data is “breakfast”, the processor 501 extracts the menu data 512 whose date matches the date stored from the health management data and whose category is “breakfast”. The processor 501 requests the nutrition data server 40 for calorie data and nutrition balance data of food and drink specified by the item code included in the extracted menu data 512.

In response to this request, as described above, the calorie data and nutrition balance data of the food and drink are sent from the nutrition data server 40 to the health management server 50, so that the processor 501 provides the second nutrition analysis screen SC52 for breakfast. Is generated.
The difference between the first nutrition analysis screen SC51 and the second nutrition analysis screen SC52 will be described later.

  When the data of the first nutrition analysis screen SC51 or the second nutrition analysis screen SC52 is generated, the processor 501 transmits the screen data from the communication interface 504 to the user terminal device 20 to the network 200 (Act 505, Act 509). ).

  In Act 242 of FIG. 21, the processor 201 that has made a nutrition analysis request including the division data “one day” waits for nutrition analysis screen data transmitted from the health management server 50 in response to this request. If the nutritional analysis screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the first nutritional analysis screen SC51 based on the screen data (Act 243).

  FIG. 30 shows an example of the first nutrition analysis screen SC51 when the category data is “one day”. As shown in FIG. 30, the first nutrition analysis screen SC51 displays the daily calorie intake and the nutrition balance distribution image G1. The amount of calorie intake is displayed in comparison with the daily standard calorie intake that is uniquely determined by the user's age, sex, weight, and the like.

  The first nutrition analysis screen SC51 displays a date consisting of a date. Then, switching marks M51 and M52 are displayed on the left and right sides of the date toward the screen. When the switching mark M1 is touched, the processor 201 recognizes that the previous day is designated with respect to the displayed date. Similarly, when the switching mark M2 is touched, the processor 201 recognizes that the next day is designated with respect to the displayed date. If the displayed date is today, the processor 201 ignores the input even if the switching mark M2 is touched.

  In addition, the first nutrition analysis screen SC51 includes buttons B51 corresponding to the respective items of “today”, “week”, “monthly”, “daily”, “breakfast”, “lunch”, “dinner”, and “snacks”. , B52, B53, B54, B55, B56, B57 and B58. The buttons B51 to B58 are touched by the user in order to switch the division data. Each of the buttons B51 to B58 also has a function as an index indicating which section the current screen is. Since the first nutrition analysis screen SC51 shown in FIG. 30 is a nutrition analysis screen for one day today, the frame of the button B51 representing “today” and the button B54 representing “one day” is divided into other buttons B52 and B53. , B55, B56, B57, B58 are thicker.

  Further, the first nutrition analysis screen SC51 includes buttons B61, B62, B63, and B64. The button B61 is touched by the user to instruct the transition to the top screen SC2. The button B62 is touched by the user to instruct the shift to the meal balance screen. The button B63 is touched by the user to instruct the transition to the nutrition analysis screen. The button B64 is touched by the user to instruct a transition to a screen different from the top screen, the meal balance guide screen, and the nutrition analysis screen. This screen is a screen for accepting user operations for various settings, for example. The buttons B61, B62, B63, and B64 also have a function as an index that indicates which screen is the current screen. In the case of the first nutrition analysis screen SC51, the frame of the button B63 is thicker than the other buttons B61, B62, B64.

  In Act 243 of FIG. 21, the processor 201 that has displayed the first nutrition analysis screen SC51 on the touch panel 204 confirms whether a date or classification change has been designated. That is, the processor 201 confirms whether the marks M1 and M2 or the buttons B51 to B58 on the first nutrition analysis screen SC51 are touched (Act 244). When mark M1, M2 or button B51-B58 is not touched (NO in Act 244), processor 201 confirms whether or not an instruction to shift to the meal balance screen has been given. That is, the processor 201 confirms whether or not the button B62 is touched (Act 245). If button B62 is not touched (NO in Act 245), processor 201 determines whether or not an instruction to shift to the top screen has been given. That is, the processor 201 confirms whether or not the button B61 is touched (Act 246). If button B61 is not touched (NO in Act 246), processor 201 confirms whether or not an instruction to shift to another screen has been given. That is, the processor 201 confirms whether or not the button B63 is touched (Act247). When button B63 is not touched (NO in Act 247), processor 201 checks again whether the date or the change of the category is designated (Act 244).

  Accordingly, the processor 201 waits for the marks M1 and M2 or the buttons B51 to 58, B61, B62, and B64 on the first nutrition analysis screen SC51 to be touched in the processes of Act244 to Act247. Note that since the button B63 is a button for instructing the transition to the nutrition analysis screen, the processor 201 ignores the input even if it is touched.

  When the user who has viewed the first nutrition analysis screen SC51 wants to check the nutrition analysis screen for the previous day, the user touches the mark M1. In order to confirm the nutrition analysis screen for today's dinner, the user touches the button B57.

  When it is detected that the mark M1, M2 or the button B51-58 is touched via the touch panel 204 in the standby state of Act 244 to Act 247 (YES in Act 244), the processor 201 detects the touched mark M1, M2 or In accordance with the buttons B51 to 58, the date data or the division data of the division area is changed (Act248). For example, when the mark M1 is touched, the processor 201 sets the date data in the date area as the date one day before. When button B57 is touched, the division data of the division area is set to “dinner”.

  When the data in the date area or the division area is changed, the processor 201 confirms whether the division data is meal-specific (Act 249). If the category data is not meal-specific, that is, “daily”, “weekly”, or “monthly” (NO in Act 249), processor 201 returns to the processing of Act 242. That is, the processor 201 transmits a nutrition analysis request in which the user code, date data, and classification data are set to the network 200 from the communication interface 205 to the health management server 50. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above. Therefore, the first nutrition analysis screen SC51 based on the date data and the classification data is displayed on the touch panel 204.

  On the other hand, if the category data is “breakfast”, “lunch”, “dinner”, or “snack” (by Act 249), the processor 201 communicates the nutrition analysis request as shown in FIG. The data is transmitted from the interface 205 to the health management server 50 to the network 200 (Act 250). This nutrition analysis request includes the user code stored in the main memory 202 or the auxiliary storage device 203, and date data and division data set in the date area and the division area. That is, this nutrition analysis request includes classification data for each meal.

  In Act 505 of FIG. 26, the processor 501 that has transmitted the data of the first nutrition analysis screen SC51 to the user terminal device 20 confirms whether or not a nutrition analysis request has been received (Act 506). If a nutrition analysis request has not been received (NO in Act 505), the processor 501 checks whether a balance browsing request has been received (Act 507). When the balance browsing request has not been received (NO in Act 507), the processor 501 confirms whether the termination of the health application P22 is instructed from the user terminal device 20 that is the nutrition analysis request source (Act 508). When termination of health application P22 is not instructed (NO in Act 508), processor 501 confirms whether a nutrition analysis request has been received again (Act 506). Accordingly, the processor 501 waits for the nutrition analysis request, the balance browsing request, or the health application P22 to be terminated by the processes of Act 506 to Act 508.

  On the other hand, in Act 509, the processor 501 that has transmitted the data on the second nutrition analysis screen SC52 to the user terminal device 20 confirms whether a nutrition analysis request has been received (Act 510). If a nutrition analysis request has not been received (NO in Act 510), processor 501 checks whether a registration request has been received from a receipt (Act 511). When the registration request from the receipt has not been received (NO in Act 511), the processor 501 confirms whether or not the registration request by manual input has been received (Act 512). When the registration request by manual input has not been received (NO in Act 512), the processor 501 checks whether a balance browsing request has been received (Act 513). When the balance browsing request has not been received (NO in Act 513), the processor 501 confirms whether the termination of the health application P22 is instructed from the user terminal device 20 that is the nutrition analysis request source (Act 514). When termination of health application P22 is not instructed (NO in Act 514), processor 501 confirms whether a nutrition analysis request has been received again (Act 510). Therefore, the processor 501 receives the nutrition analysis request, the registration request from the receipt or the registration request by manual input, the balance browsing request, or the health application P22 by the processing of Act 510 to Act 514. I wait for you. The registration request from the receipt, the manual registration request, and the balance browsing request will be described later.

  If a nutrition analysis request is received in the standby state of Act 506 to Act 508 or the standby state of Act 510 to Act 514 (YES in Act 506 or Act 510), the processor 501 returns to the processing of Act 501. That is, the processor 501 stores the user code, date data, and classification data included in the received nutrition analysis request in the main memory 502 or the auxiliary storage device 503. At this time, the processor 501 overwrites the user code, date data, and division data stored in the previous processing of Act 501. The processor 501 searches the health management data area W51 with the stored user code, and acquires health management data associated with the user code.

  When the nutrition analysis request including the division data for each meal is received, the processor 501 creates data of the second nutrition analysis screen SC52 (Act 504). The processor 501 transmits this screen data from the communication interface 504 to the user terminal device 20 to the network 200 (Act 509).

  In Act 250 of FIG. 22, the processor 201 that has made a nutrition analysis request including meal-specific classification data waits for nutrition analysis screen data transmitted from the health management server 50 in response to this request. If the nutritional analysis screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the second nutritional analysis screen SC52 based on the screen data (Act 251).

  FIG. 31 shows an example of the second nutrition analysis screen SC52 when the classification data is “dinner”. As shown in FIG. 31, the second nutrition analysis screen SC52 displays the calorie intake for one serving and the distribution image G1 of the nutritional balance. Standard calorie intake is not displayed for calorie intake.

  Similarly to the first nutrition analysis screen SC51, the date, marks M1 and M2, buttons B51 to B58, and buttons B61 to B64 are displayed on the second nutrition analysis screen SC51. Further, buttons B71 and B72 are displayed on the second nutrition analysis screen SC52. The button B71 is touched by the user to register the menu information from the receipt data. The button B72 is touched by the user to manually register the menu information.

  In Act 251 of FIG. 22, the processor 201 that has displayed the second nutrition analysis screen SC52 on the touch panel 204 confirms whether a date or classification change has been designated. That is, the processor 201 confirms whether the marks M1 and M2 or the buttons B51 to B58 on the second nutrition analysis screen SC52 are touched (Act 252). When marks M1, M2 or buttons B51-B58 are not touched (NO in Act 252), processor 201 confirms whether registration from a receipt is designated. That is, the processor 201 confirms whether or not the button B71 is touched (Act253). When button B71 is not touched (NO in Act 253), processor 201 checks whether registration by manual input is designated. That is, the processor 201 confirms whether or not the button B72 is touched (Act 254). When button B72 is not touched (NO in Act 254), processor 201 confirms whether or not an instruction to shift to the meal balance screen has been given. That is, the processor 201 confirms whether or not the button B62 is touched (Act255). When button B62 is not touched (NO in Act 255), processor 201 confirms whether or not an instruction to shift to the top screen is given. That is, the processor 201 confirms whether or not the button B22 is touched (Act256). If button B22 is not touched (NO in Act 256), processor 201 confirms whether or not an instruction to shift to another screen has been given. That is, the processor 201 confirms whether the button B25 is touched (Act257). If button B25 has not been touched (NO in Act 257), processor 201 checks again whether the date or the change of category has been designated (Act 252).

  Therefore, the processor 201 waits for the marks M1 and M2 or the buttons B51 to 58, B61, B62, B64, B71, and B72 on the second nutrition analysis screen SC52 to be touched in the processes of Act252 to Act257. Note that since the button B63 is a button for instructing the transition to the nutrition analysis screen, the processor 201 ignores the input even if it is touched.

  When the user who has viewed the second nutrition analysis screen SC52 wishes to confirm the nutrition analysis screen for the dinner of the previous day, the user touches the mark M1. When the user wants to check the nutrition analysis screen for the breakfast of the day, the user touches the button B55.

  When it is detected that the mark M1, M2 or the button B51-58 is touched via the touch panel 204 in the standby state of Act252 to Act257 (YES in Act252), the processor 201 detects the touched mark M1, M2 or In accordance with the buttons B51 to 58, the date data or the data of the divided area is changed (Act 258). For example, when the mark M1 is touched, the processor 201 sets the date data in the date area as the date one day before. When button B55 is touched, the division data of the division area is set to “breakfast”.

  When the data of the date area or the divided area is changed, the processor 201 confirms whether the divided data is meal-specific (Act 259). If the category data is not meal-specific, that is, “daily”, “weekly”, or “monthly” (NO in Act 259), processor 201 returns to the processing of Act 242. That is, the processor 201 transmits a nutrition analysis request in which the user code, date data, and classification data are set to the network 200 from the communication interface 205 to the health management server 50. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above. Therefore, the first nutrition analysis screen SC51 based on the date data and the classification data is displayed on the touch panel 204.

  On the other hand, if the category data is “breakfast”, “lunch”, “dinner”, or “snack” (YES in Act 259), processor 201 returns to the processing of Act 250. That is, the processor 201 transmits a nutrition analysis request in which the user code, date data, and classification data are set to the network 200 from the communication interface 205 to the health management server 50. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above. Therefore, the second nutrition analysis screen SC52 based on the date data and the classification data is displayed on the touch panel 204.

  When confirming the first nutrition analysis screen SC51 or the second nutrition analysis screen SC52 and terminating the health application P22, the user touches the button B61 to return to the top screen SC2.

  When the processor 201 of the user terminal device 20 detects that the button B61 is touched in the standby state of Act 244 to Act 247 or the standby state of Act 252 to Act 257 (YES in Act 246 or Act 256), the processor 201 of the user terminal device 20 The health application P22 is commanded to end (Act 260 or Act 261). Thereafter, the health application P22 ends.

  After activating the health application P22 in Act 231 of FIG. 15, the processor 201 waits for the health application P22 to end (Act 232). If health application P22 is completed (YES in Act 232), processor 201 returns to the processing of Act 205. That is, the processor 201 sets the screen of the touch panel 204 as the top screen SC2. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above.

  When the processor 501 of the health management server 50 receives a termination command for the health application P22 from the user terminal device 20 via the communication interface 504 in the standby state of Act 506 to Act 508 or the standby state of Act 510 to Act 514 shown in FIG. If YES in Act 508 or Act 514), the process returns to Act 500. Then, the processor 501 repeats the subsequent processing in the same manner as described above.

  Next, registration of menu information will be described. As a registration method of the menu information, there are a method of registering manually, and a method of registering using electronic receipt data.

  The user who registers the menu information activates the health application P22 on the user terminal device 20. That is, the user touches button B23 from top screen CS, receipt screen SC3, or list screen SC4 displayed on touch panel 204.

  When the health application P22 is activated, as described above, the first nutrition analysis screen SC51 is displayed on the touch panel 204, so that the user appropriately operates the marks M1, M2 or the buttons B55 to B58 to register the menu information. Specify the date and meal. For example, when registering today's breakfast, the user touches the button B55. When the designation of the date and meal is completed, the second nutrition analysis screen SC52 for the designated date and meal is displayed on the touch panel 204.

  Incidentally, when the menu information is not registered for the designated date and meal, the calorie intake amount displayed on the second nutrition analysis screen SC52 is 0 kcal. In addition, the nutrition balance distribution image G1 does not display information indicating the nutrition balance. Therefore, when the menu information is not registered, the calorie intake and the distribution image G1 of the nutritional balance are not displayed, and the button B71 touched by the user for designating registration from the receipt, and manual registration are designated. Therefore, the screen on which the button B72 touched by the user is displayed may be displayed on the touch panel 204.

  The user who browsed the second nutrition analysis screen SC52 touches the button B71 when registering menu information for the meal from the receipt data. When registering by manual input, the user touches the button B72.

  In Act 251 of FIG. 22, the processor 201 that has displayed the second nutrition analysis screen SC52 on the touch panel 204 enters the standby state of Act 252 to Act 257. In this standby state, when it is detected that the button B71 is touched on the touch panel 204 (YES in Act 253), the processor 201 sends a registration request from the receipt from the communication interface 205 to the health management server 50 as shown in FIG. To the network 200 (Act 271). This registration request includes the user code stored in the main memory 202 or the auxiliary storage device 203, and date data and division data set in the date area and the division area.

  In Act 509 of FIG. 26, the processor 501 that has transmitted the second nutrition analysis screen data to the user terminal device 20 enters the standby state of Act 510 to Act 514. In this standby state, when the registration request from the receipt is received by the communication interface 504 (YES in Act 511), the processor 501 accesses the receipt server 30 as shown in FIG. Then, the processor 501 acquires all receipt data associated with the user code included in the registration request and stored in the electronic receipt area W31 (Act 514).

  If the receipt data is acquired, the processor 501 generates list screen data based on the simple receipt data included in the receipt data. The processor 501 transmits the list screen data from the communication interface 504 to the user terminal device 20 to the network 200 (Act 515). The list screen data represents the same image as the list screen SC4 shown in FIG.

  In Act 271 of FIG. 23, the processor 201 that has transmitted the registration request from the receipt waits for list screen data transmitted from the health management server 50 in response to the registration request. When the list screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the list screen SC4 based on the list screen data (Act 272).

  The processor 201 having the screen of the touch panel 204 as the list screen SC4 confirms whether any simple receipt data is designated from the list screen SC4. That is, the processor 21 confirms whether any image R2 of simple receipt data is touched (Act 273). If image R2 has not been touched (NO in Act 273), processor 201 confirms whether transition to the top screen has been instructed. That is, the processor 201 confirms whether or not the button B22 has been touched (Act 274). When button B22 is not touched (NO in Act 274), processor 201 confirms again whether simple receipt data is designated (Act 273).

  Accordingly, the processor 201 waits for the image R2 on the list screen SC4 or the button B22 to be touched in the processing of Act 273 and Act 274. Note that the processor 201 ignores the input of the other buttons B23, B24, and B25 even if they are touched. Alternatively, the buttons B23, B24, and B25 may be omitted from the list screen SC4 displayed in the processing of Act 272.

  The user who browses the list screen SC4 searches for receipt data to be used for registering the menu information from the simple receipt data. When the user finds the simple receipt data of the receipt that is to be used for registering the menu information, the user touches the image R2 of the simple receipt data.

  When it is detected that the image R2 is touched in the standby state of Act 273 and Act 274 (YES in Act 273), the processor 201 sends a display request for the product list from the communication interface 205 to the health management server 50 to the network 200. Transmit (Act 275). This display request includes the user code stored in the main memory 202 or the auxiliary storage device 203 and the simple receipt data of the touched image R2.

  In Act 515 of FIG. 27, has the processor 501 that transmitted the list screen data received a display request for a product list from the user terminal device 20 (Act 516)? If not received, it is confirmed whether the end of the health application P22 is instructed from the user terminal device 20 (Act 517). If termination of health application P22 is not instructed (NO in Act 517), processor 501 confirms whether a request for displaying a product list has been received from user terminal device 20 again (Act 516). Accordingly, the processor 501 waits for a product list display request or a health application P22 termination instruction by the processing of Act 516 and Act 517.

  When the display request for the product list is received from the user terminal device 20 (YES in Act 516), the processor 501 displays the product list based on the detailed data 315 of the receipt data determined by the simple receipt data included in the display request. Generate. The product list is a list of information (a store code, a product code, a product name, etc.) related to a product provided or sold as a product at a store. The processor 501 transmits the screen data of the product list from the communication interface 504 to the user terminal device 20 to the network 200 (Act 518).

  In Act 275 of FIG. 23, the processor 201 that has requested display of the product list waits for screen data of the product list transmitted from the health management server 50 in response to this request. If the screen data of the product list is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the product list screen SC6 based on the screen data (Act 267).

  FIG. 32 shows an example of the product list screen SC6. On the product list screen SC6, a product name list L1 included in the detailed data 315 of the receipt data is displayed. The product list screen SC6 includes buttons B61, B62, B63, B81, and B82. The button B61 is touched by the user to instruct the transition to the top screen SC2. The button B62 is touched by the user to instruct the transition to the nutrition analysis screen. The button B63 is touched by the user to instruct a transition to a screen different from the top screen and the nutrition analysis screen. The button B81 is touched by the user to view the product list L1 of other receipts. The button B82 is touched by the user to register the product selected from the name list L1 as the menu information.

  In the product list L1, names of foods and drinks provided or sold as products at the store are displayed in association with radio buttons. Products other than food and drink may be displayed in the product list L1. Only the food and drink may be extracted and displayed in the product list L1 with respect to the receipt data when the product other than the food and drink is purchased together with the food and drink.

  Although the product list screen SC6 has been confirmed, the name of the food or drink to be registered as the menu information is not displayed in the product list L1, and the user touches the button B81 when viewing another receipt. When the name of the food or drink registered as the menu information is displayed in the product list L1, the user touches the name. When the name is touched, the corresponding radio button indicates the selected state. If all the names of foods and beverages to be registered are selected, the user touches button B82.

  In Act 276 of FIG. 23, the processor 201 having the product list screen SC6 as the screen of the touch panel 204 confirms whether registration of the product selected from the name list L1 is specified as the menu information. That is, the processor 201 confirms whether or not the button B82 is touched (Act 277). If button B82 is not touched (NO in Act 277), processor 201 confirms whether or not viewing of another receipt is designated. That is, the processor 201 confirms whether or not the button B81 is touched (Act 278). When button B81 is not touched (NO in Act 278), processor 201 confirms whether or not to return to the top screen is designated. That is, the processor 201 confirms whether the button B61 is touched (Act 279). When button B61 is not touched (NO in Act 279), processor 201 confirms whether or not it is specified that the product selected from name list L1 is registered again as menu information. (Act 277). Therefore, the processor 201 waits for any of the buttons B82, B81, and B61 to be touched by the processes of Act277 to Act279.

  If it is detected that the button B81 is touched in the standby state of Act 277 to Act 279 (YES in Act 278), the processor 201 returns to the processing of Act 272. That is, the processor 201 returns the screen of the touch panel 204 to the list screen SC4. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above.

  When it is detected that the button B82 is touched in the standby state of Act 277 to Act 279 (YES in Act 277), the processor 201 determines whether there is a product (name of food or drink) in the selected state from the product list L1. (Act 280). If there is a product in the selected state (YES in Act 280), the processor 201 sends selected product data for notifying that the product in the selected state is registered as the menu information from the communication interface 205 to the health management server 50. The data is transmitted to the network 200 (Act 281). The selected product data includes the user code stored in the main memory 202 or the auxiliary storage device 203, the date data and the segment data set in the date area and the segment area, and the store code and the product that are information on the selected product. Including paired data with code.

  After transmitting the selected commodity data or when there is no commodity in the selected state (NO in Act 270), the processor 201 returns to the processing of Act 250. That is, the processor 201 sends a nutrition analysis request including the user code stored in the main memory 202 or the auxiliary storage device 203 and the date data and the division data set in the date area and the division area from the communication interface 205 to the health management server 50. To the network 200. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above. Therefore, the second nutrition analysis screen SC52 based on the date data and the classification data is displayed on the touch panel 204.

  In Act 518 of FIG. 27, the processor 501 that has transmitted the product list screen data to the user terminal device 20 confirms whether or not the selected product data has been received from the user terminal device 20 (Act 519). If not received (NO in Act 519), the processor 501 confirms whether a nutrition analysis request has been received from the user terminal device 20 (Act 520). If not received (NO in Act 520), the processor 501 confirms whether or not the user terminal device 20 has instructed the end of the health application P22 (Act 521). If termination of health application P22 is not instructed (NO in Act 521), processor 501 confirms whether or not the selected product data has been received again (Act 519). Accordingly, the processor 501 waits for an instruction to end the health application P22 or receives the selected product data, receives the nutrition analysis request, or receives the nutrition analysis request through the processes of Act 519 to Act 521.

  When the nutrition analysis request is received (YES in Act 520), the processor 501 returns to the processing of Act 501. Thereafter, the processor 501 repeats the subsequent processing in the same manner as described above.

  When the selected product data is received (YES in Act 519), the processor 501 selects the date data and the classification data included in the selected product data from the menu data 512 associated with the user code included in the selected product data. Menu data 512 with which the two match is detected. At this time, if the corresponding menu data does not exist in the health management data area W51, the processor 501 includes the menu data 512 in which the date data and the classification data included in the selected product data are set, in the selected product data. The data is added to the health management data area W51 as data associated with the user code. The processor 501 adds pair data of the store code and the product code included in the selected product data to the menu data 512 in which the date data included in the selected product data matches the category data (Act 522).

  Here, the computer including the processor 501 that executes the processes of Act 514 to Act 522 according to the program functions as an acquisition unit and a registration unit.

  After the pair data of the store code and the product code included in the selected product data is added to the health management data area W51, the processor 501 returns to the processing of Act 500. Then, the processor 501 repeats the subsequent processing in the same manner as described above.

  When the processor 201 of the user terminal device 20 detects that the button B72 has been touched in the standby state of Act 252 to Act 257 (YES in Act 254), as shown in FIG. To the health management server 50 and transmitted to the network 200 (Act 291). This registration request includes the user code stored in the main memory 202 or the auxiliary storage device 203, and date data and division data set in the date area and the division area.

  When the processor 501 of the health management server 50 receives a registration request manually input by the communication interface 504 in the standby state of Act 510 to Act 514 (YES in Act 512), it is stored in the auxiliary storage device 503 as shown in FIG. Food input screen data is acquired (Act 531). The food input screen data represents an image for setting the touch panel 204 of the user terminal device 20 as the food input screen SC7. The processor 501 transmits the food input screen data from the communication interface 504 to the user terminal device 20 who has browsed the network 200 (Act 532).

  In Act 291 of FIG. 24, the processor 201 that has made the registration request by manual input waits for food input screen data transmitted from the health management server 50 in response to this request. If the food input screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the food input screen SC7 based on the screen data (Act 292).

  FIG. 33 shows an example of the food input screen SC7. The food input screen SC7 includes a menu button B91, a category button B92, a standard menu button B93, and a completion button B94. Regarding the menu button B91 and the category button B92, a plurality of buttons are arranged in a matrix. For the standard menu button B93, a plurality of buttons are arranged in a line.

The category button B92 is touched by the user to select a category related to food and drink such as rice, bread, noodles, vegetable dishes, meat dishes, and seafood dishes.
The menu button B91 is touched by the user in order to select food and drink classified in the category selected by the category button B92. In the menu button 91, the food code and the icon of each food and drink set in the food nutrition data area W42 of the nutrition data server 40 are individually assigned and set. The menu button 91 displays an icon set for the button.

  The standard menu button B93 is touched by the user in order to select a standard food and drink for the user. In the standard menu button B93, the user can arbitrarily set a desired food and drink as a standard menu. For example, a user who eats and drinks “toast” and “milk” almost every day as breakfast sets the food and drink code of “toast” and “milk” as standard menu codes in any of the classic menu buttons B93. Similarly, for example, a user who eats and drinks “tempura soba” of a restaurant almost every day as lunch sets the store code and product code of “tempura soba” as a standard menu code in any of the classic menu buttons B93.

  The user who browsed the food input screen SC7 touches the category button B92 to which the rice is assigned, for example, when registering food and drink of the rice. Then, since the food and drink belonging to the rice is assigned to the menu button B91, the user touches the menu button B91 on which the icon of the food and drink to be registered as the menu information is displayed. Similarly, when registering food and drink of noodles, for example, the category button B92 to which noodles are assigned is touched. Then, since food and drink belonging to noodles are assigned to the menu button B91, the user touches the menu button B91 on which an icon of food and drink to be registered as menu information is displayed. Moreover, when registering the food and drink assigned to the standard menu button B93, the user touches the standard menu button B93. Thus, if selection of the food and drink to register by manual input is complete | finished, a user will touch the completion button B94.

  If the screen of the touch panel 204 is the food input screen SC7, the processor 201 confirms whether completion of food input is designated. That is, the processor 201 waits for the completion button B94 to be touched (Act 293). When it is detected that the completion button B94 is touched (YES in Act 293), the processor 201 confirms whether the food or drink to be registered as the menu information is selected (Act 294). When food or drink is selected by touch operation of category button B92 and menu button B91 or touch operation of classic menu button B93 (YES in Act 294), processor 201 selects selected food data including the food code of the food and drink. Is transmitted from the communication interface 205 to the health management server 50 to the network 200 (Act 295). This selected food data includes the user code stored in the main memory 202 or the auxiliary storage device 203, and date data and division data set in the date area and the division area.

  When the selected food data is transmitted or the food or drink to be registered as the menu information is not selected (NO in Act 294), the processor 201 returns to the processing of Act 250. That is, the processor 201 transmits a nutrition analysis request in which the user code, date data, and classification data are set to the network 200 from the communication interface 205 to the health management server 50. Thereafter, the processor 201 repeats the subsequent processing in the same manner as described above.

  In Act 532 of FIG. 28, the processor 501 that transmitted the food input screen data to the user terminal device 20 confirms whether or not the selected food data is received from the user terminal device 20 (Act 533). If not received (NO in Act 533), the processor 501 confirms whether a nutrition analysis request has been received from the user terminal device 20 (Act 534). If not received (NO in Act 534), the processor 501 confirms whether the selected food data has been received again (Act 533).

  Therefore, the processor 501 waits to receive selected food data or receive a nutrition analysis request by the processing of Act 533 and Act 534. If a nutrition analysis request is received in this standby state (YES in Act 534), processor 501 returns to the processing of Act 501. Thereafter, the processor 501 repeats the subsequent processing in the same manner as described above.

  When the selected food data is received (YES in Act 533), the processor 501 distinguishes the date data included in the selected food data from the menu data 512 associated with the user code included in the selected food data. Menu data 512 that matches the data is detected. If the corresponding menu data does not exist in the health management data area W51, the processor uses the menu data 512 in which the date data and the classification data included in the selected food data are set, and the user code included in the selected food data. Is added to the health management data area W51 as data associated with the. The processor 501 adds the food code included in the selected food data to the menu data 512 in which the date data included in the selected food data matches the category data (Act 535).

  After adding the food code included in the selected food data to the health management data area W51, the processor 501 returns to the processing of Act 500. Then, the processor 501 repeats the subsequent processing in the same manner as described above.

  By the way, the distribution image G1 of nutrition balance displayed on the nutrition analysis screens SC51 and SC52 can be replaced with an illustration of a meal balance guide. When replacing the distribution image G1 of nutrition balance with a meal balance guide, the user touches the button B62.

  When detecting that the button B62 is touched in the standby state of Act 244 to Act 247 of FIG. 21 or the standby state of Act 252 to Act 257 of FIG. 22 (YES in Act 245 or Act 513), the processor 201, as shown in FIG. The default value “0” is set in the country code area set in the main memory 202 (Act 2001). The default value “0” is an unused code as the country code in the meal balance data stored in the meal balance guide area. The default value is not limited to “0”. In the meal balance data, the country code may be an unused code.

  If the country data is set, the processor 201 transmits a balance browsing request from the communication interface 205 to the health management server 50 to the network 200 (Act 2002). This balance browsing request includes the user code stored in the main memory 202 or the auxiliary storage device 203, the date data and the division data set in the date area and the division area, and the country code set in the country code area. It is.

  In the standby state of Act 506 to Act 508 (standby state after transmitting the first nutrition analysis screen data) or the standby state of Act 510 to Act 514 (standby state after transmitting the second nutrition analysis screen data) in FIG. When the browsing request is received (YES in Act 507 or YES in Act 513), the processor 501 confirms whether the country code included in the balance browsing request is the default value “0”, as shown in FIG. 29 ( Act 541).

  If the country code is “0” (YES in Act 541), processor 501 accesses receipt server 30. The processor 501 acquires the country code stored in the country code area W32 and stores it in the main memory 502 or the auxiliary storage device 503 (Act 514). When the country code is not “0”, that is, when the country code of any country or region is included (NO in Act 541), the processor 501 does not access the receipt server 30. The processor 501 stores the country code included in the balance browsing request in the main memory 502 or the auxiliary storage device 503.

  If the country code is stored in the main memory 502 or the auxiliary storage device 503, the processor 501 searches the meal balance guide area W52. Then, the processor 501 acquires meal balance data including the stored country code (Act 543).

  If the meal balance guide data is acquired, the processor 501 classifies the calorie data and nutrition balance data of food and drink according to the classification data 524 included in the meal balance data. The calorie data and nutrition balance data to be classified are data acquired from the nutrition data server 40 based on the item code included in the stored menu data 512 in the processing of Act 503 or Act 504.

  The processor 501 edits the meal balance screen data based on the calorie data and nutrition balance data of the food and drink classified according to the classification data 524 and the illustration data 523 of the meal balance data (Act 544). Then, the processor 501 transmits the meal balance screen data from the communication interface 304 to the user terminal device 20 to the network 200 (Act 545). The meal balance screen data represents an image for setting the screen of the touch panel 204 of the user terminal device 20 as the meal balance screen SC7.

Here, the computer including the processor 501 that executes the processing of Act 541 to Act 544 in accordance with the program functions as a generation unit.
Further, the computer including the processor 501 that executes the processing of Act 545 according to the program functions as a presentation unit.

  In Act 2002 of FIG. 25, the processor 201 that has transmitted the balance browsing request to the health management server 50 waits for meal balance screen data (Act 2003). When the meal balance screen data is received by the communication interface 205 (YES in Act 2003), the processor 201 sets the screen of the touch panel 204 as the meal balance screen SC81 based on the meal balance screen data (Act 2004).

  FIG. 34 shows an example of the meal balance screen SC81. When the user touches the button B62 on the nutrition balance screen SC61 in FIG. 30, a meal balance screen SC81 in FIG. 34 is displayed. The meal balance screen SC81 is obtained by replacing the distribution image G1 of the nutrition balance displayed on the nutrition balance screen SC61 with an illustration G2 of the meal balance guide, and other calorie intake display, date display, and buttons B51 to B58. , B61 to B64 are equal to the nutrition balance screen SC61. However, the button B61 for instructing the transition to the top screen SC2 is replaced with the button B61 for designating the country of the meal balance guide.

  In the nutrition balance screen SC62 of FIG. 31, the meal balance screen displayed when the user touches the button B62 is the same. That is, the nutrition balance distribution image G1 displayed on the nutrition balance screen SC61 is replaced with the meal balance guide illustration G2. Further, the button B61 for instructing the transition to the top screen SC2 becomes the button B61 for designating the country of the meal balance guide. Others are the same as the nutrition balance screen SC62.

  Now, when the user touches the button B62 on the nutrition balance screen SC61 or SC2, the country code has a default value “0”. Therefore, the meal balance guide illustration G2 displayed on the meal balance screen SC81 is an illustration formulated in the country or region determined by the country code set in the country code area W32 of the receipt server 30. Incidentally, the meal balance screen SC81 of FIG. 34 shows a case where the country code set in the country code area W32 of the receipt server 30 is a Japanese code. Since the country code is a Japanese code, the illustration of the meal balance screen SC81 is a frame type illustration G2 used in the meal balance guide formulated by Japan.

  However, some users desire to manage their health with a meal balance guide formulated in another country or region. In that case, the user touches the button B61.

  In Act 2004 of FIG. 25, the processor 201 using the meal balance screen SC81 as the screen of the touch panel 204 confirms whether the country is designated. That is, it is confirmed whether the button B61 is touched (Act 2005). When the button B61 is not touched, the processor 201 confirms whether or not an instruction to shift to the nutrition analysis screen is given. That is, the processor 201 confirms whether or not the button B63 is touched (Act 2006). When button B63 is not touched (NO in Act 2006), processor 201 confirms whether transition to another screen is instructed. That is, the processor 201 confirms whether the button B64 is touched (Act 2007). If button B64 has not been touched (NO in Act 2007), processor 201 checks again whether country designation has been made (Act 2005).

  Therefore, the processor 201 waits for a country designation, an instruction to shift to the nutrition analysis screen, or an instruction to shift to another screen by the processing of Act 2005 to Act 2007. In this standby state, when it is detected that the button B61 is touched via the touch panel 204 (YES in Act 2005), the processor 201 sends a country designation request from the communication interface 205 to the health management server 50 to the network 200. Transmit (Act 2008).

  In FIG. Act 545, the processor 501 that has transmitted the meal balance screen data to the user terminal device 20 confirms whether or not a country designation request has been received (Act 546). When the country designation request has not been received (NO in Act 546), the processor 501 checks whether a nutrition analysis request has been received (Act 547). If no nutrition analysis request has been received (NO in Act 547), processor 501 checks again whether a country designation request has been received (Act 546).

  Therefore, the processor 501 waits to receive a country designation request or a nutrition analysis request by the processing of Act 546 and Act 547. In this standby state, when the country designation request is received by the communication interface 504 (YES in Act 546), the processor 501 acquires the country designation screen data stored in the auxiliary storage device 503 (Act 2008). The country designation screen data represents an image for setting the touch panel 204 of the user terminal device 20 as the country designation screen SC9. The processor 501 transmits the country designation screen data from the communication interface 504 to the user terminal device 20 to the network 200 (Act 548).

  In Act 2008 of FIG. 25, the processor 201 that has transmitted the country designation request waits for the country designation screen data transmitted from the health management server 50 in response to this request. When the country designation screen data is received by the communication interface 205, the processor 201 sets the screen of the touch panel 204 as the country designation screen SC9 based on the screen data (Act 2009).

  FIG. 35 shows an example of the country designation screen SC9. Country designation screen SC9 includes a plurality of country selection buttons B81. The country code 521 and country name data 522 assigned to the meal balance data stored in the meal balance guide area W52 are assigned to the country selection button B81.

  The user who has viewed the country designation screen SC9 touches the country selection button B81 on which the name of the country or region in which the meal balance guide is to be confirmed is displayed.

  In Act 2009, the processor 201 having the touch panel 204 as the country designation screen SC9 waits for any country selection button B81 to be touched (Act 2010). When it is detected that the country selection button B81 is touched via the touch panel 204 (YES in Act 2010), the processor 201 sets the country code area to be set in the main memory 202 as the touched country selection button B81. To the country code set in (Act 2011). Then, the processor 201 returns to the processing of Act2002. That is, the processor 201 transmits a balance browsing request including the country code set in the country code area from the communication interface 205 to the health management server 50 to the network 200.

  In Act 548 of FIG. 29, the processor 501 that has transmitted the country designation screen data to the user terminal device 20 waits for a balance browsing request from the user terminal device 20 (Act 549). When the balance browsing request is received by communication interface 504 (YES in Act 549), processor 501 returns to the processing of Act 541. The processor 501 repeats the subsequent processing in the same manner as described above.

  Here, the computer including the processor 501 that executes the processing of Act 548 and Act 549 according to the program functions as an accepting unit.

  The balance browsing request received in the standby state of Act 548 includes the country code of the country or region selected by the country selection button B81. Therefore, the meal balance data acquired from the meal balance guide area W52 in the processing of Act 543 is data identified by the country selected by the country selection button B81 or the country code of the area. As a result, the illustration of the meal balance guide displayed on the meal balance screen is an illustration of the meal balance guide formulated in the country or region determined by the country code.

  When the user who browsed the meal balance screen SC81 of FIG. 34 wants to browse the illustration of the meal balance guide for the United States, the user touches the button B82 in which the country name “USA” is set on the country designation screen SC9. Then, the meal balance screen SC81 changes to a meal balance screen SC82 shown in FIG. That is, the meal balance guide illustration G3 formulated in the United States is displayed on the meal balance screen SC82.

Now, the user who has finished browsing the meal balance guide touches the button B63.
When the processor 201 detects that the button B63 is touched in the standby state of Act 2005 to Act 2007 in FIG. 25 (YES in Act 2006), it confirms the segment data set in the segment area (Act 2012).

  If the category data is not meal-specific, that is, “one day”, “one week”, and “one month” (NO in Act 2012), the processor 201 returns to Act 242. That is, the processor 201 transmits a nutrition analysis request from the communication interface 205 to the health management server 50 to the network 200. On the other hand, if the category data is by meal, that is, “breakfast”, “lunch”, “dinner”, and “snack” (YES in Act 2012), the processor 201 returns to the processing of Act 250. That is, the processor 201 transmits a nutrition analysis request from the communication interface 205 to the health management server 50 to the network 200.

  In Act 545 of FIG. 29, the processor 501 that has transmitted the meal balance screen data to the user terminal device 20 enters the standby state of Act 546 and Act 547. If a nutrition analysis request is received from the user terminal device 20 in this standby state (YES in Act 547), the processor 501 returns to the processing of Act 501. Thereafter, the processor 501 repeats the subsequent processing in the same manner as described above.

  Therefore, when the division data set in the division area of the user terminal device 20 is not meal-specific, the screen of the touch panel 204 is the first nutrition analysis screen SC62. When the classification data is for each meal, the screen of the touch panel 204 is the second nutrition analysis screen SC62.

  As described above, according to the health management system 100 of the present embodiment, the receipt client application P21 and the health application P22 are installed in the portable user terminal device 20 such as a smartphone, a mobile phone, or a tablet terminal. The user can receive the following services.

A. The user can display and browse the receipt issued at the time of accounting at a restaurant, retail store, or the like in which the accounting apparatus 10 is installed, as an electronic receipt on the user terminal device 20. .
B. The user registers the menu information taken by the user for each meal such as breakfast, lunch, dinner, etc., in the health management data area W51 of the health management server 50 using the product information of the electronic receipt stored in the receipt server 30. be able to.
C. The user can register the menu information that cannot be supplemented from the information on the electronic receipt by manual input using the user terminal device 20.
D. From the screen displayed on the touch panel 204 of the user terminal device 20, the user selects each meal, one day, one week, one month based on the menu information for each meal accumulated for each user in the health management data area W51. The calorie intake and nutrition balance distribution image G1 can be viewed in units such as minutes.
E. The user can view an image serving as an index of nutrition balance not only by the distribution image G1 of the nutrition balance but also by an illustration of the meal balance guide.
F. The illustration of the meal balance guide is formulated in the country or region set by the country code set in the receipt server 30. The receipt server 30 is set with the country code of the country or region where the health management system 100 is constructed. Therefore, many users can manage their health with a meal balance guide formulated in their home country.
G. The meal balance guide illustrations can be replaced with meal balance guide illustrations formulated in other countries or regions with a simple operation. Therefore, the user can perform health management even with a meal balance guide formulated outside the country or region where the health management system 100 is constructed.
H. In order to be able to use meal balance guides in other countries or regions, meal balance data may be added to the meal balance guide area W52. Therefore, the meal balance guide can be easily expanded.

  From the above, according to the health management system 100, there is an effect that nutrition data can be presented with an index of classification suitable for the user.

  In addition, it goes without saying that various functions and effects can be obtained from the configuration and operation of the present embodiment.

  In the above-described embodiment, the receipt server 30, the nutrition data server 40, and the health management server 50 have been described as separate servers. However, at least two of these servers may be realized by one server. Alternatively, the receipt server 30, the nutrition data server 40, and the health management server 50 can be realized by only one server.

  Moreover, although some embodiment of this invention was described, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 10 ... Accounting device, 20 ... User terminal device, 30 ... Receipt server, 40 ... Nutrition data server, 50 ... Health management server, 100 ... Health management system, 200 ... Network.

Claims (6)

A first storage device for storing receipt data including information relating to merchandise provided or sold to a user in association with the user identification code;
A second storage device for storing information specifying food and drink eaten by the user in association with the identification code of the user;
Obtaining means for obtaining the identification code of the user;
The information specifying the food or drink that the user eats or drinks is associated with the identification code of the user from the receipt data stored in the first storage device in association with the identification code of the user acquired by the acquisition means. Registration means for registering in the second storage device;
Information for specifying a browsing image representing nutrition data of the food and drink specified by the information stored in the second storage device in association with the identification code of the user acquired by the acquisition means, specifying a country or region Generating means for generating using an illustration defined in the country or region specified by
Presenting means for presenting the browsing image generated by the generating means to allow the user to browse;
A health management system comprising: A server device having the second storage device,
The said generation means produces | generates the said browsing image using the illustration defined in the said country or area specified by the information which specifies the country or area set to the said server apparatus. Health management system. Receiving means for receiving information identifying the country or region;
Further comprising
When the information specifying the country or region is received by the receiving unit, the generating unit generates the browsing image using an illustration defined in the country or region specified by the information. The health management system according to claim 1 or 2, characterized by the above. A user terminal device and a server device capable of communicating via a network;
The server device includes the first storage device, the second storage device, the acquisition unit, the registration unit, the generation unit, and the presentation unit.
The health management system according to claim 1, wherein the user terminal device includes a display device that displays a browsing image presented by the presentation unit. A communication means connected via a network and communicating with a user terminal device including a display device;
A first storage device for storing receipt data including information relating to merchandise provided or sold to a user in association with the user identification code;
A second storage device for storing information specifying food and drink eaten by the user in association with the identification code of the user;
Obtaining means for obtaining the identification code of the user;
The information specifying the food or drink that the user eats or drinks is associated with the identification code of the user from the receipt data stored in the first storage device in association with the identification code of the user acquired by the acquisition means. Registration means for registering in the second storage device;
Information for specifying a browsing image representing nutrition data of the food and drink specified by the information stored in the second storage device in association with the identification code of the user acquired by the acquisition means, specifying a country or region Generating means for generating using an illustration defined in the country or region specified by
Presenting means for presenting the browse image generated by the generating means for display on the display device of the user terminal device;
A server apparatus comprising: A first storage device that is connected to a user terminal device including a display device via a network and stores receipt data including information related to a product provided or sold to the user in association with the identification code of the user; and A computer that accesses a second storage device that stores information specifying food and drink that the user eats and drinks in association with the identification code of the user.
Obtaining means for obtaining the identification code of the user;
The information specifying the food or drink that the user eats or drinks is associated with the identification code of the user from the receipt data stored in the first storage device in association with the identification code of the user acquired by the acquisition means. Registration means for registering in the second storage device;
Information for specifying a browsing image representing nutrition data of the food and drink specified by the information stored in the second storage device in association with the identification code of the user acquired by the acquisition means, specifying a country or region Generating means for generating using illustrations defined in the country or region specified by the above, and presenting means for presenting the browse image generated by the generating means to be displayed on the display device of the user terminal device ,
Program to function as.