Medication support system, medication support method, and medication support program

Abstract

The aim of this system is to reduce the workload of medication assistants by providing a function that confirms the name of the person planning to take the medication in text form. [Solution] The name confirmation presentation unit 250 of the mobile terminal 200 acquires the read name 55 from an image of the medicine packet of the person to be administered the medicine, and displays it on the display screen. Based on the read name 55 and the face information database 31, the name confirmation presentation unit 250 extracts names similar to the read name 55 from the names set in the face information database 31 as a list of candidates for the name of the person to be administered the medicine, and displays them on the display screen. Then, the name confirmation presentation unit 250 prompts the administration assistant to confirm whether the read name 55 is the name of the person to be administered the medicine.

Description

[Technical field]

[0001] The present disclosure relates to a medication support system, a medication support method, and a medication support program. [Background technology]

[0002] In medical institutions or nursing homes, medication assistants such as nurses or caregivers assist users in taking their medication correctly. Systems have been introduced to support medication assistants in preventing mistakes such as taking the wrong medication. For example, there is a system that can confirm whose medicine it is for by reading the QR code (registered trademark) printed on a single medicine package, and can confirm who the medicine is to be given to by reading the QR code (registered trademark) printed on the user's name tag, etc. QR is an abbreviation for Quick Response.

[0003] In addition, Patent Document 1 discloses a technology for supporting the distribution of medicine to residents in a facility, in which the resident who will take the medicine is identified from the medicine package and the name and face image of the identified resident are displayed on a mobile terminal. A feature of Patent Document 1 is that the person in charge of distributing the medicine recognizes the person who takes the medicine by checking the face image displayed on the mobile terminal. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2022-058870 Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 discloses that, in order to check who is to receive the medicine, a facial image obtained from the name of the person who is to take the medicine is displayed on a mobile terminal, and the displayed facial image is used for visual confirmation. In this way, the facial image and the identity of the resident are ultimately confirmed by the visual inspection of the medication assistant. On the other hand, it is known that people are surprisingly easily misled by image information, and there is a possibility that even an incorrect facial image may be mistakenly recognized as correct. Therefore, when the medication assistant visually checks, it is important to display a facial image with high accuracy. In the technology of Patent Document 1, the confirmation of the name of the person who is to take the medicine is left to the medication assistant, and there is a problem that the physical and mental workload of the medication assistant is large.

[0006] The present disclosure aims to provide a function for determining the name of the intended recipient in the form of text information, thereby enabling the selection of a more likely intended recipient. [Means for solving the problem]

[0007] The medication support system according to the present disclosure is a medication support system that supports a medication assistant who provides medication assistance, The system is provided with a name confirmation presentation unit that obtains a name read from an image of a medicine packet of a person to take the medicine as a read name and displays the read name on a display screen, and extracts names similar to the read name from names set in the face information database based on the read name and a face information database in which face data representing a person's facial image and the person's name are set, as a list of candidates for the name of the person to take the medicine, and displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name is the name of the person to take the medicine. Effect of the Invention

[0008] In the medication support system according to the present disclosure, the display unit acquires the read name read from an image of the medicine packet of the person to be administered the medicine, and displays the read name on the display screen. The name confirmation presentation unit extracts names similar to the read name from the names set in the face information database as a list of candidates for the name of the person to be administered the medicine. The name confirmation presentation unit then displays the list of candidates on the display screen, and allows the medication assistant to confirm whether the read name is the name of the person to be administered the medicine. Thus, according to the medication support system according to the present disclosure, the name of the person to be administered the medicine can be confirmed in the form of text information, and an effect of allowing a person to be selected who is more likely to be administered the medicine can be achieved. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of the overall configuration of a medication support system according to a first embodiment. [Diagram 2] FIG. 1 is a diagram showing a configuration example of a medication support device according to a first embodiment. [Diagram 3] FIG. 2 is a diagram showing a configuration example of a mobile terminal according to the first embodiment. [Figure 4] 3 is a flow diagram showing the operation of the medication support system according to the first embodiment. [Diagram 5] 3 is a diagram showing an example of the configuration of a user database and a staff database stored in a storage unit of the medication support device of embodiment 1. FIG. [Figure 6] 3 is a diagram showing an example of the configuration of a face information database and a staff information database stored in a storage unit of the mobile terminal according to the first embodiment. [Figure 7] FIG. 4 is a detailed flow diagram of step S130 according to the first embodiment. [Figure 8] FIG. 2 is a diagram showing how a medicine packet is photographed in the first embodiment. [Figure 9] 4 is a diagram showing an example of the structure of character information and authentication information stored in a storage unit of the mobile terminal according to the first embodiment. [Figure 10] FIG. 4 is a detailed flow diagram of steps S140 and S150 according to the first embodiment. [Figure 11] FIG. 2 is a diagram showing how the face of a person to be administered the medicine is photographed in accordance with the first embodiment. [Figure 12] FIG. 4 is a detailed flow diagram of step S160 according to the first embodiment. [Figure 13] 5A and 5B are diagrams showing examples of an authentication success display and an authentication failure display according to the first embodiment. [Figure 14] 6 is a diagram showing examples of types of authentication results in the authentication process according to the first embodiment. [Figure 15] FIG. 11 is a diagram showing variations of authentication information when authentication according to the first embodiment fails. [Figure 16] FIG. 2 is a diagram showing an example of the configuration of a medication record database according to the first embodiment. [Figure 17] FIG. 11 is a flow diagram showing the operation of the medication support system according to the second embodiment. [Figure 18] FIG. 11 is a diagram showing an example of the configuration of a user database and a staff database stored in the storage unit of the medication support device of embodiment 2. [Figure 19] 13 is a diagram showing an example of the configuration of a face information database and a staff information database stored in a storage unit of a mobile terminal according to the second embodiment. [Figure 20] FIG. 11 is a diagram showing an example of a visual confirmation screen according to the second embodiment. [Figure 21] 13A to 13C are diagrams showing examples of photographing unfeasible conditions in the face photographing determination process according to the second embodiment. [Figure 22] FIG. 13 is a diagram showing an example of a scheduler imaging start screen according to the second embodiment. [Figure 23] 13 is a diagram showing an example of a skip condition for skipping face photographing according to the second embodiment. [Figure 24] FIG. 11 is a diagram showing an example of the configuration of a medication record database according to the second embodiment. [Diagram 25] FIG. 11 is a diagram showing an example of a visual authentication success display according to the second embodiment. [Figure 26] FIG. 11 is a diagram showing a configuration example of a mobile terminal according to the third embodiment. [Figure 27] FIG. 11 is a flow chart showing the operation of the medication support system according to the third embodiment. [Figure 28] FIG. 11 is a flow diagram showing a name confirmation presentation process according to the third embodiment. [Figure 29]FIG. 13 is a diagram showing an example of a display screen in the name confirmation presentation process according to the third embodiment. [Diagram 30] 13A to 13C are schematic diagrams showing (1) specific example 1 and (2) specific example 2 of a name confirmation presentation process according to the third embodiment. [Diagram 31] 13A and 13B are schematic diagrams showing (3) Specific Example 3 and (4) Specific Example 4 of the name confirmation presentation process according to the third embodiment. [Diagram 32] 13A and 13B are diagrams showing examples of an authentication success display and an authentication failure display according to the third embodiment. [Diagram 33] FIG. 11 is a flow chart showing the operation of the medication support system according to the fourth embodiment. [Diagram 34] FIG. 13 is a diagram showing a specific example of medication support processing according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, the present embodiment will be described with reference to the drawings. In each drawing, the same or corresponding parts are given the same reference numerals. In the description of the embodiment, the description of the same or corresponding parts will be omitted or simplified as appropriate. The arrows in the drawing mainly indicate the flow of data or the flow of processing. In addition, the relationship of the size of each component in the following drawings may differ from the actual one. In addition, in the description of the embodiment, directions or positions such as up, down, left, right, front, back, front, and back may be indicated. These notations are for convenience of explanation and do not limit the arrangement, direction, or orientation of devices, instruments, or parts.

[0011] Embodiment 1 ***Configuration Description*** FIG. 1 is a diagram showing an example of the overall configuration of a medication support system 500 according to the present embodiment. The medication support system 500 is a system for supporting medication assistance by a medication assistant (nurse or caregiver) in a facility such as a medical institution or a care facility. The medication assistant provides medication assistance to ensure that users of the facility take their medicine correctly. The medication support system 500 includes a medication support device 100 and a plurality of mobile terminals 200. The medication support device 100 and the mobile terminals 200 communicate with each other via a network 300. The mobile terminals 200 are terminals carried by a medication assistant. The mobile terminals 200 are computers having a photographing function, such as a smartphone, a tablet, a portable computer, or a personal computer. A plurality of mobile terminals 200 may be present in the same facility, or a plurality of mobile terminals 200 may be present in a plurality of different facilities.

[0012] FIG. 2 is a diagram showing an example of the configuration of the medication support device 100 according to the present embodiment. FIG. 3 is a diagram showing an example of the configuration of the mobile terminal 200 according to the present embodiment.

[0013] The medication support device 100 is a computer. The medication support device 100 includes a processor 910, as well as other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to the other hardware via signal lines and controls the other hardware. The medication support device 100 includes, as functional elements, a character extraction unit 110 and an information configuration unit 120. In the storage unit 150, a user database 11, a staff database 12, and a medication record database 13 are stored.

[0014] The mobile terminal 200 is a computer. The mobile terminal 200 includes a processor 910 and other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, a communication device 950, and an image capturing device 960. The processor 910 is connected to the other hardware via a signal line and controls the other hardware. The image capturing device 960 is a camera. The mobile terminal 200 includes, as functional elements, a display unit 210, a photographing unit 220, a corresponding name acquisition unit 230, and an authentication unit 240. The storage unit 260 stores a face information database 31, a staff information database 32, character information 33, authentication information 34, and a name identification result 35.

[0015] The hardware components of the processor 910, memory 921, auxiliary storage device 922, input interface 930, output interface 940, display device 941, and communication device 950 are described using the same reference numerals in both the medication support device 100 and the mobile terminal 200. This is done merely to simplify the description, and it is clear that the medication support device 100 and the mobile terminal 200 each have their own hardware.

[0016] The functions of each unit in the medication support device 100 are realized by software. The functions of each unit in the mobile terminal 200 are realized by software. Each of the storage units 150 and 260 is provided in a memory 921. Each of the storage units 150 and 260 may be provided in an auxiliary storage device 922, or may be provided separately in the memory 921 and the auxiliary storage device 922.

[0017] The processor 910 is a device that executes a medication support program. The medication support program is a program that realizes the functions of each unit of the medication support device 100 and the mobile terminal 200. The processor 910 is an IC that performs arithmetic processing. Specific examples of the processor 910 are a CPU, a DSP, and a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0018] The memory 921 is a storage device that temporarily stores data. Specific examples of the memory 921 are SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory. The auxiliary storage device 922 is a storage device that stores data. A specific example of the auxiliary storage device 922 is a HDD. The auxiliary storage device 922 may also be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, or a DVD. Note that HDD is an abbreviation for Hard Disk Drive. SD (registered trademark) is an abbreviation for Secure Digital. CF is an abbreviation for CompactFlash (registered trademark). DVD is an abbreviation for Digital Versatile Disk.

[0019] The input interface 930 is a port connected to an input device such as a mouse, a keyboard, or a touch panel. Specifically, the input interface 930 is a USB terminal. The input interface 930 may be a port connected to a LAN. USB is an abbreviation for Universal Serial Bus. LAN is an abbreviation for Local Area Network.

[0020] A display device 941 such as a display is connected to the output interface 940. Specifically, the output interface 940 is a USB terminal or an HDMI (registered trademark) terminal. Specifically, the display is an LCD. HDMI (registered trademark) is a high LCD is an abbreviation for Liquid Crystal Display.

[0021] The communication device 950 is connected to a communication network such as a LAN, Wi-Fi (registered trademark), the Internet, or a telephone line.

[0022] The medication support program is executed in each of the medication support device 100 and the mobile terminal 200. The medication support program is loaded into the processor 910 and executed by the processor 910. Memory 921 stores not only the medication support program but also an OS. OS is an abbreviation for Operating System. The processor 910 executes the medication support program while executing the OS. The medication support program and the OS may be stored in an auxiliary storage device 922. The medication support program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that a part or all of the medication support program may be incorporated into the OS.

[0023] The "parts" of the parts of the medication support device 100 and the mobile terminal 200 may be read as "circuits," "steps," "procedures," "processing," or "circuitry." The medication support program causes a computer to execute processing in which the parts of the medication support device 100 and the mobile terminal 200 are replaced. The "processing" of the processing in which the parts of the medication support device 100 and the mobile terminal 200 are replaced may be read as "program," "program product," or "computer-readable storage medium storing a program." The medication support program may be provided by being stored in a computer-readable storage medium. The medication support program may also be provided as a program product.

[0024] ***Explanation of Operation*** Next, an operation of the medication support system 500 according to the present embodiment will be described. The operation procedure of the medication support system 500 corresponds to a medication support method. Moreover, a program for realizing the operation of the medication support system 500 corresponds to a medication support program.

[0025] FIG. 4 is a flow diagram showing the operation of medication support system 500 according to this embodiment.

[0026] <Initial Processing: Step S110> When the medication support process is started, in step S110, the display unit 210 of the mobile terminal 200 displays an initial screen on the display device 941. In addition, the authentication unit 240 of the mobile terminal 200 acquires information to be set in the face information database 31 and the staff information database 32 from the medication support device 100 via the communication device 950. Specifically, the authentication unit 240 acquires face information of the user and staff information of the staff at the facility to which the medication assistant belongs from the medication support device 100, and stores them in the memory unit 260 as face information database 31 and staff information database 32.

[0027] The process of step S110 is started, for example, when the power of the mobile terminal 200 is turned on. If the power of the mobile terminal 200 is turned on at a fixed time every morning, the face information database 31 and the staff information database 32 are reset every morning.

[0028] FIG. 5 is a diagram showing an example of the configuration of the user database 11 and the staff database 12 stored in the storage unit 150 of the medication support device 100 according to this embodiment.

[0029] In the user database 11, information on all users in all facilities that use the medication support system 500 is set. Information such as facility ID 111, user ID 112, user name 113, reading 114, and face data 115 is set in the user database 11. Information about the user such as date of birth, gender, special notes, and identifier may also be set. The identifier is information for identifying an individual when, for example, there is a user with the same name. The face data 115 is data generated in advance based on a face image of a person who is a user. The face data 115 is data that represents the face image of the person. Specifically, the face data 115 is data that digitizes the face image of the person.

[0030] In the staff database 12, information on all staff members in all facilities that use the medication support system 500 is set. In the staff database 12, information such as a facility ID 121, a staff ID 122, and a name 123 is set.

[0031] FIG. 6 is a diagram showing an example of the configuration of face information database 31 and staff information database 32 stored in storage unit 260 of mobile terminal 200 according to this embodiment. A user name 311 and face data 312 are set in the face information database 31. The users set in the face information database 31 are users of the facility to which the medication assistant who possesses the mobile terminal 200 belongs. A staff ID 321 and a name 322 are set in the staff information database 32. The staff set in the staff information database 32 is the staff of the facility to which the medication assistant who possesses the mobile terminal 200 belongs.

[0032] For example, the authentication unit 240 transmits an information transmission request for face information and staff information, which includes a facility ID of a facility to which the medication assistant carrying the mobile terminal 200 belongs, to the medication support device 100. Upon receiving the information transmission request, the medication support device 100 searches the user database 11 and the staff database 12 using the facility ID included in the information transmission request, and transmits to the mobile terminal 200 the information on the user and staff included in the facility ID.

[0033] That is, the face information database 31 is obtained by extracting the user name and face data corresponding to the facility ID from the user database 11 of the medication support device 100. The staff information database 32 is obtained by extracting the staff ID and the staff name corresponding to the facility ID from the staff database 12 of the medication support device 100.

[0034] <Staff authentication process: Step S120> In step S120, the authentication unit 240 authenticates staff such as a medication assistant. Any method of staff authentication may be used. For example, the authentication unit 240 performs staff authentication by displaying a staff ID or name, or both, based on the staff information database 32 using the display unit 210 and accepting a selection from the staff member. Alternatively, face data representing a face image of the staff member may be set in advance in the staff information database 32, and the authentication unit 240 may perform staff authentication by performing face authentication using a face image photographed by the staff member using the photographing device 960.

[0035] <Drug Package Image Capture Process and Character Extraction Process: Step S130> In step S130, photographing unit 220 of mobile terminal 200 performs a medicine package image photographing process to photograph the medicine package using photographing device 960. Then, photographing unit 220 transmits the image of the medicine package obtained by photographing to medication support device 100. Character extraction unit 110 of medication support device 100 receives the image of the medicine package from mobile terminal 200 and extracts characters printed on the medicine package. Character extraction unit 110 of medication support device 100 transmits the extracted characters to photographing unit 220 of mobile terminal 200 as character information.

[0036] FIG. 7 is a detailed flow diagram of step S130 according to the present embodiment. FIG. 8 is a diagram showing how medicine packet 51 according to the present embodiment is photographed. In step S131, display unit 210 of mobile terminal 200 displays medicine packet photographing start screen 61 for photographing medicine packet 51.

[0037] In step S132, the photographing section 220 of the mobile terminal 200 photographs an image of the medicine packet 51 by the photographing device 960. Specifically, when the medicine packet photographing start screen 61 is displayed, the medication assistant photographs the medicine packet 51 to be taken by the intended patient via the medicine packet photographing start screen 61. Then, the photographing section 220 transmits the image of the medicine packet 51 to the medication support device 100 via the communication device 950.

[0038] The position where the medicine bag 51 should be set is displayed as a guide on the medicine bag photographing start screen 61, and the medication assistant sets the medicine bag 51 according to the guide and photographs it. Medicine packet 51 is a package containing a combination of medicines to be taken at one time. Medicine packet 51 is packaged at the pharmacy and has information such as the name of the person taking the medicine, the date of taking the medicine, and the timing of taking the medicine (e.g., "before breakfast", "after breakfast") printed on it.

[0039] In step S133, medication support device 100 receives the image of medicine packet 51 from mobile terminal 200. Character extraction unit 110 of medication support device 100 extracts characters printed on medicine packet 51 from the received image of medicine packet 51. In the example of Figure 8, characters such as "Taro Ogawa, Friday, July 22, 2022, after breakfast" are extracted. Character extraction unit 110 transmits the extracted characters to mobile terminal 200 as character information. Note that the meaning of the characters is not determined here. Character extraction unit 110 recognizes character boundaries using existing character recognition technology, and transmits the recognized character strings to mobile terminal 200 in order from the top left of the image. The recognized locations of the recognized character strings are also transmitted as pixel information. This pixel information is preferably the top left and bottom right of the recognized character string to specify the region of the character string as a rectangle. However, it may be only the top left location, or it may include pixel information for four locations: the top left, top right, bottom right, and bottom left.

[0040] In step S134, when the photographing unit 220 of the mobile terminal 200 receives the text information from the medication support device 100, the photographing unit 220 stores the text information in the storage unit 260 as text information 33.

[0041] FIG. 9 is a diagram showing an example of the configuration of character information 33, authentication information 34, and name identification result 35 stored in storage unit 260 of mobile terminal 200 according to this embodiment. Character information 33 in FIG. 9 shows character information extracted from the example image of medicine packet 51 in FIG. 8. The character information transmitted from medication support device 100 corresponds to "date", "name", and "timing of taking medicine", but as described above, the meaning of the items and characters is not acquired. Therefore, character information 33 only stores each character string that is separated and read by medication support device 100. Item 1, item 2, and item 3 in FIG. 9 are described for convenience only and have no meaning. In addition, although not shown in FIG. 9, each character string and position information (pixel information) where the character string was acquired are recorded together. The authentication information 34 and the name identification result 35 will be described later.

[0042] Returning to FIG. 4, the explanation will be continued.

[0043] <Facial image capture process: step S140> In step S140, the photographing section 220 of the mobile terminal 200 photographs, by the photographing device 960, a face image of the intended recipient 52 who is to take the medicine contained in the medicine packet 51. The intended recipient 52 is a person for whom the medication assistant will assist with taking the medicine from the medicine packet 51.

[0044] <Corresponding name acquisition process: Step S150> The corresponding name acquiring section 230 of the mobile terminal 200 acquires, from the face information database 31, a name corresponding to face data representing a face image of the prospective recipient 52 as the image corresponding name 125.

[0045] FIG. 10 is a detailed flow diagram of steps S140 and S150 according to this embodiment. The facial image photographing process for photographing the face of the prospective recipient 52 in step S140 and the corresponding name acquisition process in step S150 will be described with reference to FIG.

[0046] In step S141, the display unit 210 of the mobile terminal 200 displays a scheduled person photographing start screen 62 for photographing the face of the scheduled person 52. At this time, if character information 33, which is characters printed on the medicine packet 51, is stored, the contents of the character information 33 may also be displayed. In step S142, the photographing section 220 of the mobile terminal 200 photographs the face of the intended person 52 by the photographing device 960. Specifically, when the intended person photographing start screen 62 is displayed, the medication assistant photographs the face of the intended person 52 so that the face of the intended person 52 is within an area such as a circle displayed on the intended person photographing start screen 62.

[0047] FIG. 11 is a diagram showing how the face of a prospective recipient 52 is photographed according to this embodiment. 11, the display unit 210 displays a scheduled patient imaging start screen 62. At this time, if character information 33, which is characters printed on the medicine packet 51, is stored in the storage unit 260, the content of the character information 33 may also be displayed. The position of the face of the intended patient 52 is displayed as a guide on the intended patient photographing start screen 62. Then, as shown in the right diagram, the medication assistant photographs the face of the intended patient 52 according to the guide.

[0048] In step S143, the associated name acquiring section 230 digitizes the facial image of the prospective recipient 52 obtained by photographing. Any method may be used to digitize the facial image.

[0049] The corresponding name acquisition unit 230 acquires a name corresponding to the digitized face data from the face information database 31 as an image corresponding name 53 . Specifically, the following applies:

[0050] In step S144, the corresponding name acquisition unit 230 searches the face information database 31 using the digitized face data of the intended recipient 52, and judges whether or not there is face data 312 that can be judged to be the same. The judgment in step S144 does not have to be a judgment of whether or not the numerical values ​​are exactly the same, but may be a judgment that allows for a certain degree of fluctuation. Any technique may be used to judge the range of fluctuation and whether or not the values ​​are the same including the fluctuation.

[0051] If face data 312 that can be determined to be the same exists, the process proceeds to step S145. If there is no face data 312 that can be determined to be the same, the process proceeds to step S146.

[0052] In step S145, the corresponding name acquisition unit 230 acquires, from the face information database 31, a name corresponding to the face data 312 that can be determined to be identical to the face data of the intended recipient 52, as the image corresponding name 53. The corresponding name acquisition unit 230 temporarily stores the acquired image corresponding name 53 in the name identification result 35 of the storage unit 260.

[0053] In step S146, face data 312 that can be determined to be the same as the face data of the intended recipient 52 is not present in the face information database 31. Therefore, the corresponding name acquisition unit 230 sets the name identification result 35 in the storage unit 260 to null. Name identification result 35 is information that temporarily sets the result of whether or not the name could be identified from face information database 31 using the facial data of expected user 52. If image-corresponding name 53 can be identified from the facial data of expected user 52, the identified image-corresponding name 53 is set in name identification result 35. On the other hand, if image-corresponding name 53 cannot be identified from the facial data of expected user 52, name identification result 35 becomes null. If it is known that image-corresponding name 53 cannot be identified, data other than null may be used.

[0054] The order of photographing the medicine packet 51 and photographing the face image of the intended recipient 52 may be reversed. As long as the functions described in steps S130 to S150 can be realized, the order of the processes included in steps S130 to S150 does not matter. Furthermore, in step S144, if there is no face data 312 that can be determined to be the same, the corresponding name acquiring section 230 may prompt the user to retake a face image of the intended recipient 52 on the intended recipient photographing start screen 62.

[0055] Returning to FIG. 4, the explanation will be continued.

[0056] <Authentication process: Step S160> Authentication unit 240 of mobile terminal 200 acquires the name printed on medicine package 51 as printed name 54 from character information 33, which is the characters printed on medicine package 51. Then, authentication unit 240 determines whether printed name 54 and image-corresponding name 53 can be authenticated as being the same. Specifically, the following applies:

[0057] FIG. 12 is a detailed flow diagram of step S160 according to the present embodiment. In step S161, authentication unit 240 acquires the name printed on medicine packet 51 from character information 33 as printed name 54. As described above, all character strings printed on medicine package 51 are set in character information 33. Therefore, authentication unit 240 needs to extract the name therefrom. A method for acquiring the name from character information 33 as printed name 54 is, for example, as follows.

[0058] The authentication unit 240 acquires the position where the name is printed in the image of the medicine package as the name position. The name position is stored in advance in the storage unit 260. The authentication unit 240 acquires the characters printed in the name position among the characters printed on the medicine package 51 as the printed name 54. In the example of the medicine package 51 in FIG. 8, it is assumed that pixel information starting from the upper left corner of the image of the medicine package is stored in the mobile terminal 200 as the name position, which is the position where the name is printed. The authentication unit 240 identifies the printed name 54 by comparing the character information 33 with the pixel information stored as the name position. The position information and pixel information of the character information 33 may not match due to camera shake when the medicine package 51 is photographed, but the authentication unit 240 may be configured to identify the printed name 54 within a certain tolerance range.

[0059] Moreover, the authentication unit 240 may identify the characters “sama” or “dono” and obtain the character string before that as the printed name 54. In addition, to prevent the date and timing information in the character information 33 from being subject to comparison, processing may be performed to eliminate dates containing numbers and words such as "after breakfast" or "before meals," and the remaining character string may be obtained as the printed name 54. According to this identification method, there is no need for the mobile terminal 200 to store name and location information.

[0060] In step S162, the authentication unit 240 determines whether or not it can be authenticated that the printed name 54 and the image corresponding name 53 are the same. First, the authentication unit 240 refers to the name identification result 35 in the storage unit 260. If the name identification result 35 is null, it indicates that the image corresponding name 53 could not be acquired. Therefore, the printed name 54 and the image corresponding name 53 cannot be compared, and it is not possible to verify whether they are the same. For this reason, if the name identification result 35 is null, the process proceeds to step S164.

[0061] If the image corresponding name 53 is set in the name identification result 35, the authentication unit 240 compares the printed name 54 with the image corresponding name 53. If it can be authenticated that the printed name 54 and the image-corresponding name 53 are the same, proceed to step S163. If it cannot be authenticated that the printed name 54 and the image-corresponding name 53 are the same, proceed to step S164. Whether or not it can be authenticated that the printed name 54 and the image-corresponding name 53 are the same may be based on exact match, or conditions for being the same may be set in advance. For example, conditions such as authenticating as the same in the case of a one-character difference with only similar characters like "大" and "太" may be set in advance. In this embodiment, it is assumed that it can be authenticated as the same when the strings of the printed name 54 and the image-corresponding name 53 exactly match.

[0062] FIG. 13 is an example of an authentication success display 21 and an authentication failure display 22 according to this embodiment. In step S163, the display unit 210 displays an authentication success display 21 indicating that the scheduled taker 52 is the correct taker. In the authentication success display 21 shown in FIG. 13(a), an authentication success message 211 indicating authentication success, and the name, date, and taking timing of the scheduled taker 52 who is the correct taker are displayed within a circle indicating authentication success.

[0063] In step S164, the display unit 210 displays an authentication failure display 22 indicating that the authentication of the printed name 54 and the image-corresponding name 53 has failed. Authentication failures may include a failure due to the inability to obtain the image-corresponding name 53 related to face authentication (steps S140 to S150, FIG. 13(b)), and a failure due to misrecognition of the printed name 54 related to photographing of the medicine pack 51 (step S130, FIG. 13(c)).

[0064] 13B shows an authentication failure display 22 when the name identification result 35 is null, that is, when the image-corresponding name 53 cannot be acquired, and therefore the printed name 54 and the image-corresponding name 53 cannot be authenticated as being the same. For example, this is the case when the face authentication itself fails due to factors such as the face of the person to take the medicine 52 being hidden by a mask, the angle of the face when photographed being inappropriate, or insufficient illumination, and therefore the image-corresponding name 53 cannot be acquired. Alternatively, the face data of the person to take the medicine 52 may not be registered in the user database 11, or may have been omitted from registration. In this case, the display unit 210 displays an authentication failure display 22 including a facial authentication failure message 221, character information 33 which is information obtained by character recognition from an image of the medicine package, an image of the medicine package 222, a registration button 223, and a retake button 224. The face authentication failure message 221 is a message indicating that the image-corresponding name 53 could not be obtained. The registration button 223 is a button that the medication assistant uses to forcibly register the recipient who will take the medicine. Here, a list of candidates for the names of the intended recipient 52 is displayed, and the medication assistant can select the name of the intended recipient 52 to be forcibly registered. The registration button 223 may not be a selection type, but may be a type in which the name of the intended recipient 52 to be forcibly registered is input. The retake button 224 is a button that the medication assistant uses to retake the face image of the intended recipient 52. The display unit 210 displays, for example, the printed name 54 first as a candidate for the name of the prospective user 52, and further displays any names similar to the printed name 54 extracted from the names of users in the same facility. Names that differ from the printed name 54 by one or two characters, or all the names of users in the same facility, may be displayed.

[0065] FIG. 13(c) shows an authentication failure display 22 displayed when, as a result of comparing the printed name 54 with the image-corresponding name 53, the printed name 54 and the image-corresponding name 53 do not match, and the printed name 54 and the image-corresponding name 53 cannot be authenticated as being identical. In this case, the display unit 210 displays an authentication failure display 22 including a mismatch message 231, the printed name 54 and the image-corresponding name 53 and explanatory text for identifying each, an image of the medicine package 232, a registration button 233, and a retake button 234. The mismatch message 231 is a message indicating a mismatch between the printed name 54 and the image-corresponding name 53. The registration button 233 is a button that allows the medication assistant to forcibly register the recipient who will take the medication. In FIG. 13(c), when the registration button 233 is selected, the image-corresponding name 53 is registered. Alternatively, a method of inputting the name of the intended recipient 52 to be forcibly registered may be used. Here, when the registration button 233 is selected, the image-corresponding name 53 is registered because this is an operation that assumes that the authentication failure is due to erroneous recognition of the printed name 54. 13(c), it is assumed that the face authentication was OK (registered face), but the printed name 54 does not match the image-corresponding name 53. Therefore, the authentication failure display 22 may suggest a reading error when acquiring the printed name 54. For example, the authentication failure display 22 may suggest an error such as a difference of just one character, a misrecognition of similar characters, or a missing character. 13(c) is not caused by a failure due to misrecognition of the printed name 54 when photographing the medicine packet 51, but may be caused by photographing a face image of a person other than the intended user 52. The retake button 234 is a button for the medication assistant to take a new face image of the intended user 52 when he or she notices this.

[0066] Next, in step S165, the authentication unit 240 generates authentication information 34 based on the authentication result. Then, the authentication unit 240 transmits the generated authentication information 34 to the medication support apparatus 100. 9 includes a facility ID 341, face authentication date and time 342, authentication result 343, image-corresponding name 344, printed name 345, staff ID 346, medicine package read characters 347, and medication assistance memo 348. The medication assistance memo 348 is a memo arbitrarily input by the medication assistant. In addition, the system may be configured to allow information on medication, such as high-risk medication, to be input. The authentication information 34 shown in FIG. 9 is a setting example in which the authentication result is OK, that is, authentication is successful.

[0067] FIG. 14 shows an example of types of authentication results in the authentication process according to the present embodiment. As shown in FIG. 14, the types set for the authentication result in the authentication information 34 include, for example, OK, NG1, and NG2. The type "OK" is when the face authentication in step S144 is successful, and the comparison result between the printed name 54 and the image corresponding name 53 in step S162 also matches. At this time, the final result is authentication success. An authentication success display 21 as shown in FIG. 13(a) is displayed. Type "NG1" is when the face authentication in step S144 is successful, but the comparison result between the printed name 54 and the image-corresponding name 53 in step S162 does not match. In this case, the final result is authentication failure. An authentication failure display 22 as shown in FIG. 13(c) is displayed. The medication assistant may confirm that the correct person is the person who will take the medication by directly asking the person who will take the medication 52 or by visually checking, and may forcibly register the person who will take the medication. Type "NG2" occurs when the face authentication in step S144 fails, and therefore the comparison between the printed name 54 and the image-corresponding name 53 in step S162 cannot be performed. In this case, the final result is authentication failure. An authentication failure display 22 as shown in FIG. 13(b) is displayed. In this case, the medication assistant may confirm the correct medication recipient by directly asking the intended recipient 52 or by visual confirmation, and may forcibly register the medication recipient. It should be noted that the frequency of occurrence of type "NG2" can be reduced by encouraging the recipient to take a photo again when face authentication fails.

[0068] As described above, when the medication assistant confirms that the intended recipient 52 is the correct recipient by directly asking the recipient 52 or by visually checking, and then forcibly registers the recipient, the authentication result type will be “forced OK.”

[0069] Fig. 15 is a diagram showing variations of authentication information 34 when authentication according to the present embodiment has failed. Note that in Fig. 15, the medicine package reading characters are omitted.

[0070] <Variation 1> FIG. 15(a) shows authentication information 34 in a case where printed name 54 and image-corresponding name 53 were acquired, but printed name 54 and image-corresponding name 53 did not match, resulting in "NG1." For example, this is the case when "Oo△Hanako" is read as "Futa△Hanako" due to dirt or the like when acquiring printed name 54. After checking authentication failure display 22 in FIG. 13(c), the medication assistant confirms that intended user 52 is "Oo△Hanako" and clicks registration button 233 to register "Oo△Hanako" as the authentication result "forced OK."

[0071] <Variation 2> Fig. 15(b) shows authentication information 34 in a case where facial authentication failed, image-corresponding name 53 could not be acquired, and the result was "NG2." For example, this is the case when facial authentication was not possible because the patient turned sideways multiple times when acquiring a facial image. After checking the authentication failure display 22 in Fig. 13(b), the medication assistant confirms that the intended user 52 is "Oo△Hanako," and presses the registration button 223 to register "Oo△Hanako" as the authentication result "forced OK."

[0072] <Variation 3> FIG. 15(c) shows authentication information 34 in a case where printed name 54 and image-corresponding name 53 could be acquired, but printed name 54 and image-corresponding name 53 did not match, resulting in "NG1." Here, this is the case where the medication assistant mistakenly takes a facial image of another elderly person who resembles expected medication recipient 52. After checking authentication failure display 22 in FIG. 13(c), the medication assistant presses retake button 234 to take a new photograph of expected medication recipient 52, and authentication is successful, generating authentication information 34 with the authentication result "OK."

[0073] In step S166, the information configuration unit 120 of the medication support apparatus 100 receives the authentication information 34 from the mobile terminal 200, and stores it in the medication record database 13. In step S167, the authentication unit 240 initializes information such as the character information 33, the authentication information 34, and the name identification result 35.

[0074] 16 is a diagram showing an example of the configuration of medication history database 13 according to this embodiment. Note that in FIG. 16, the description of the medicine package read characters is omitted. Medication history database 13 accumulates authentication information in all facilities that use medication support system 500. Items in medication history database 13 are the same as the items in authentication information .

[0075] ***Other configurations*** In this embodiment, the functions of each unit of each device of medication support system 500 are realized by software. As a modification, the functions of each unit of each device of medication support system 500 may be realized by hardware. Specifically, the medication support device 100 and the mobile terminal 200 may include an electronic circuit instead of the processor 910.

[0076] The electronic circuit is a dedicated electronic circuit that realizes the function of each part of each device of the medication support system 500. Specifically, the electronic circuit is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0077] As another modification, some of the functions of each unit of each device of medication support system 500 may be realized by electronic circuits, and the remaining functions may be realized by software. Also, some or all of the functions of each unit of each device of medication support system 500 may be realized by firmware.

[0078] Each of the processor and electronic circuitry is also called a processing circuitry. In other words, the functions of each unit of each device in the medication support system 500 are realized by the processing circuitry.

[0079] ***Explanation of the Effects of the Present Embodiment*** As described above, in the medication support system 500 according to the present embodiment, the name is acquired as the printed name from among the characters printed on the medication package from the image of the medication package. Then, it is determined whether or not the acquired printed name can be authenticated as being the same as the image-corresponding name, which is the name corresponding to the face data representing the face image of the person who is to take the medication. In this way, in the medication support system 500 according to the present embodiment, personal information is identified from the characters printed on the medication package of the medication to be taken, and the name acquired by face authentication is compared with the name printed on the medication package to authenticate the person who takes the medication. Therefore, the medication assistant does not need to authenticate the person by visual inspection. Therefore, according to the medication support system 500 according to the present embodiment, authentication with high reliability can be performed.

[0080] In addition, since the medication support system 500 according to the present embodiment is a system that can be constructed using a mobile terminal equipped with a camera, no new capital investment is required in the facility. Furthermore, it is sufficient that the name of the person who takes the medication is printed on the medicine packet, and printing of additional information such as a two-dimensional code such as a QR code (registered trademark) is not required. Therefore, the medication support system 500 according to the present embodiment does not require coordination with pharmacies or packaging machine manufacturers, making initial introduction easy.

[0081] Furthermore, in the medication support system 500 according to this embodiment, the facial image of the person who is to take the medicine is digitized, and the name corresponding to the digitized facial data is obtained from the face information database as the image-corresponding name. In this way, the medication support system 500 according to this embodiment can compare the facial image with the digitized data, thereby reducing the processing load.

[0082] Furthermore, in the medication support system 500 according to the present embodiment, authentication of the final recipient is performed by character string comparison, such as comparison of the printed name with the image-corresponding name. Therefore, the medication support system 500 according to the present embodiment can perform accurate authentication without relying on visual inspection, by character string comparison with a low processing load.

[0083] In addition, in the medication support system 500 according to the present embodiment, different messages can be displayed for authentication failure when an image-corresponding name cannot be acquired and authentication failure when a printed name and an image-corresponding name do not match. Therefore, the medication support system 500 according to the present embodiment can realize appropriate medication assistance support corresponding to various cases that may occur in a facility.

[0084] Embodiment 2 In this embodiment, differences from and additions to the first embodiment will be mainly described. In this embodiment, components having the same functions as those in the first embodiment are given the same reference numerals, and the description thereof will be omitted.

[0085] ***Configuration Description*** The configurations of the medication support system 500, medication support device 100, and mobile terminal 200 in this embodiment are the same as those in the first embodiment.

[0086] ***Explanation of Operation*** Next, an operation of the medication support system 500 according to the present embodiment will be described. The operation procedure of the medication support system 500 corresponds to a medication support method. Moreover, a program for realizing the operation of the medication support system 500 corresponds to a medication support program.

[0087] FIG. 17 is a flow diagram showing the operation of medication support system 500 according to this embodiment.

[0088] <Initial Processing: Step S110> Step S110, which is the initial process, is the same as in the first embodiment.

[0089] FIG. 18 is a diagram showing an example of the configuration of the user database 11 and the staff database 12 stored in the storage unit 150 of the medication support device 100 according to this embodiment.

[0090] In addition to the information described in the first embodiment, a face photographing flag 116, a photographing prohibited period 117, and a special note 118 regarding the prohibition of photographing are set in the user database 11. In this embodiment, the face data 115 includes the face image as well as the data obtained by converting the face image into digital form. The face photographing flag 116 is a flag indicating whether or not face photographing of a person who is a user is prohibited. For example, if face photographing is permitted, it is set to "1", if it is permitted under certain conditions, it is set to "9", and if face photographing is prohibited, it is set to "0". The photographing prohibited period 117 indicates a period during which photographing of the face is prohibited. Photographing of the face is prohibited during the set period. In the special notes 118 regarding the prohibition of photography, for example, if face photography is permitted under certain conditions, the conditions are set.

[0091] In the staff database 12, in addition to the information explained in the first embodiment, a staff flag 124 is set. The staff flag 124 is a flag indicating whether or not the staff member is a staff member who will photograph the face of the person who is going to take the medicine. For example, "1" is set for staff who will photograph the face, and "0" is set for staff who will not photograph the face. For example, for staff who are not familiar with operating the mobile terminal 200, "0" is set for staff who will not photograph the face.

[0092] FIG. 19 is a diagram showing an example of the configuration of face information database 31 and staff information database 32 stored in storage unit 260 of mobile terminal 200 according to this embodiment.

[0093] In addition to the information described in the first embodiment, a face photographing flag 313, a photographing prohibited period 314, and a special note 315 regarding the photographing prohibited period are set in the face information database 31. In this embodiment, the face data 312 includes a face image as well as digitalized data of the face image. The face photographing flag 313, the photographing prohibited period 314, and the special note 315 regarding photographing prohibited are similar to the face photographing flag 116, the photographing prohibited period 117, and the special note 118 regarding photographing prohibited, respectively.

[0094] In the staff information database 32, in addition to the information explained in the first embodiment, a staff flag 323 is set. The stuff flag 323 is similar to the stuff flag 124 .

[0095] <Staff authentication process: Step S120> <Drug Package Image Capture Process and Character Extraction Process: Step S130> Step S120, which is the staff authentication process, and step S130, which is the medicine package image photographing process and character extraction process, are the same as those in embodiment 1. In step S130, the photographing unit 220 photographs the medicine package containing the medicine to be taken by the intended user 52, and acquires the character information 33 printed on the medicine package.

[0096] <Facial image display process: step S210> In step S210, the display unit 210 uses the face information database 31 to extract face data 312 corresponding to the text information 33, and displays a face image corresponding to the extracted face data 312 as a terminal display image 64 on the mobile terminal 200. Specifically, the display unit 210 extracts face data 312 from the face information database 31 based on the character information 33 acquired in step S130. The display unit 210 searches the face information database 31 using all items included in the character information 33, and extracts face data 312 corresponding to a user name 311 that matches any of the items included in the character information 33. Then, the display unit 210 acquires a face image included in the extracted face data 312 as a terminal display image 64. The display unit 210 displays a visual confirmation screen 63 used by a medication assistant to visually confirm, on the display screen of the mobile terminal 200. The display unit 210 displays a terminal display image 64 acquired from the character information 33 together with the character information 33 as the visual confirmation screen 63.

[0097] FIG. 20 is a diagram showing an example of a visual confirmation screen 63 according to the present embodiment. On visual confirmation screen 63, the contents of character information 33, which is characters read from medicine packet 51, and terminal display image 64 acquired from face information database 31 based on character information 33 are displayed. The visual confirmation screen 63 also displays a visual OK button 641 and a visual NG button 642 for the medication assistant to input the result of the visual confirmation.

[0098] <Visual confirmation process: Step S220> <Visual confirmation determination process: Step S230> <Facial image capture determination process: step S240> The photographing unit 220 acquires the result of visual confirmation by the medication assistant visually confirming whether or not the terminal display image 64 is the same person as the intended medication recipient 52. If the visual confirmation is successful, that is, if the visual authentication is successful, the photographing unit 220 judges whether or not it is impossible to photograph the face of the intended medication recipient 52. Specifically, the following applies:

[0099] In step S220, the medication assistant visually compares the intended user 52 with the terminal display image 64 displayed on the visual confirmation screen 63, and performs authentication by visual confirmation to determine whether they are the same person. If the result of the visual confirmation is OK, the medication assistant presses the visual OK button 641. If the result of the visual confirmation is not OK, the medication assistant presses the visual NG button 642. If the visual confirmation is OK, that is, if the visual OK button 641 is pressed, the process proceeds to step S240. If the visual confirmation result is not OK, that is, if the visual inspection NG button 642 is pressed, the process proceeds to step S270. In step S270, since there is a high possibility that the intended user 52 is a different person, the medication assistant takes measures such as searching for the correct intended user 52, and repeats the process from visual confirmation (step S220).

[0100] In step S240, the photographing section 220 judges whether or not it is possible to photograph the face of the prospective recipient 52 who has been visually confirmed as OK. If it is determined that face photography is not possible (YES in step S240), the process proceeds to step S260. If it is determined that face photographing is not impossible, that is, if it is determined that face photographing is possible (NO in step S240), the process proceeds to step S140a.

[0101] FIG. 21 is a diagram showing an example of face photographing unacceptable conditions 81 in the face photographing determination process according to the present embodiment. The face photographing prohibition condition 81 is a condition for determining that it is not possible to photograph the face of the prospective patient 52. The process of determining whether or not it is possible to photograph the face based on the face photographing prohibition condition 81 is performed automatically. Below are examples of face photography unacceptable conditions 81. Of the face photographing unacceptable conditions 81, those related to users are stored in the face information database 31, and those related to staff are stored in the staff information database 32. Among the face photographing unacceptable conditions 81, those unacceptable conditions not related to users and staff are stored in the storage unit 260 as face photographing unacceptable condition information including unacceptable text information. The face photographing unacceptable condition information includes, for example, text information for comparison with the text information 33 shown below.

[0102] (1) The photographing unit 220 judges whether or not face photographing is possible based on the time condition. The time during which face photographing is not possible as a system can be set in advance. As shown in Fig. 21, for example, the time period "18:00-6:00" is set as a time period during which face photographing is not possible as a system. (2) The photographing unit 220 refers to the character information 33 acquired in step S130, and determines that face photographing is not possible if the medication timing included in the character information 33 is included in the medication timing stored in the face photographing impossible condition information. For example, assume that the medication timing of "dinner" is acquired from the character information 33 included in the character information 33, and "dinner," "before going to bed," and "before falling asleep" are stored as medication timings stored in the face photographing impossible condition information. In this case, since "dinner" acquired from the character information 33 is included in the medication timings stored in the face photographing impossible condition information, it is determined that face photographing is not possible. (3) A facility flag is provided for each facility to set whether or not face photography is permitted. For example, a flag can be set so that face photography is not permitted according to the facility's policy. The photography unit 220 refers to the facility flag to determine whether or not face photography is permitted. (4) A temporary flag is provided to temporarily disable face photography. For example, a flag can be set to temporarily disable face photography due to a shortage of staff or lack of familiarity with the operation. The photographing unit 220 refers to the temporary flag to determine whether face photography is possible. Since a date and time can be specified in the temporary flag, the photographing unit 220 determines that face photography is not possible if the current time is included in the date or time specified in the temporary flag. (5) The photographing unit 220 refers to the staff flag 323 in the staff information database 32 for the medication assistant. If the staff flag 323 of the medication assistant is "0", which indicates that the staff does not photograph the face, the photographing unit 220 determines that the face cannot be photographed. For example, "0", which indicates that the staff does not photograph the face, is set for staff who are unfamiliar with the operation or have little experience. (6) The photographing unit 220 refers to the face photographing flag 313 of the face information database 31 for the intended recipient. If the face photographing flag 313 of the intended recipient is “0”, indicating that face authentication is not possible, the photographing unit 220 determines that face photographing is not possible. (7) The photographing unit 220 refers to the face photographing flag 313 in the face information database 31 for the intended recipient. If the face photographing flag 313 for the intended recipient is “9”, which indicates conditional face authentication, the photographing unit 220 makes a judgment, for example, as follows. When the photographing unavailable period 314 is set, if the current time is included in the set period, the photographing unit 220 determines that face photographing is unavailable. For example, the photographing unavailable period 314 is set due to poor health, injury, or the like. If the special notes 315 regarding the impossibility of photographing include an event that makes face authentication impossible, the photographing unit 220 determines that face photographing is impossible. For example, if there are special notes such as camera phobia, paralysis, facial stiffness, or a high level of dementia, the photographing unit 220 determines that face photographing is impossible. Note that the special notes 315 in Fig. 19 and the face photographing impossible condition 81 in (7) in Fig. 21 describe the conditions under which face photographing is impossible in sentences, but in reality, the conditions are stored as a flag indicating that face photographing is impossible so that the photographing unit 220 can determine that face photographing is impossible. Also, when "9" is specified, indicating that face recognition is conditional, the photographing unit 220 may be configured to display in text the conditions under which face photography is not permitted, and to accept input from the staff as to whether or not to photograph.

[0103] The photographing unit 220 determines that face photographing is not permitted if any one of the face photographing prohibition conditions 81 from (1) to (7) above is met. In addition, the face photographing prohibition conditions 81 from (1) to (7) above may be prioritized. For example, the priority may be set as follows: facility flag ((3), (4)) → time ((1)) → text ((2)) → user ((6), (7)) → staff ((5)). Furthermore, the face photography prohibition condition 81 in FIG. 21 is one example, and other conditions may be added or conditions may be deleted.

[0104] On the other hand, if it is determined that face photographing is possible, the process proceeds to face image photographing processing (step S140a). However, in the face image photographing processing (step S140a) according to the present embodiment, face photographing may be skipped depending on a predetermined condition.

[0105] <Facial image capture process: step S140a> In step S140a, the photographing section 220 displays, on the mobile terminal 200, a scheduled person photographing start screen 62 for photographing the face of the scheduled person 52. Then, the photographing section 220 determines whether or not to skip photographing the face. In this embodiment, face photography is skipped under a predetermined condition. The skip condition for skipping face photography is a condition for skipping face photography when it is difficult to photograph the face for some reason. The process of determining whether or not to skip face photography is performed automatically. Alternatively, the medication assistant can skip face photography by pressing a skip button.

[0106] FIG. 22 is a diagram showing an example of a scheduled patient imaging start screen 62 according to the present embodiment. The scheduled person image capture start screen 62 according to this embodiment displays a skip button 625 for instructing to skip face image capture, in addition to the configuration described in the embodiment 1. The scheduled person image capture start screen 62 also includes a face authentication button 626 for instructing to start face image capture. The photographing unit 220 determines to skip face photographing when the skip button 625 is pressed. Then, the photographing unit 220 displays a skip notification on the scheduled person photographing start screen 62 to the effect that face photographing will be skipped due to the skip button 625 being pressed.

[0107] FIG. 23 is a diagram showing an example of skip conditions 82 for skipping face photographing according to the present embodiment. (8) When the same medication assistant fails to capture a face image a predetermined number of times in succession, the photographing unit 220 determines to skip photographing the face. (9) When a medication assistant who has failed to capture a face photograph a predetermined number of times in succession is changed and facial photographing is resumed, if multiple medication assistants who have failed to capture a face photograph a predetermined number of times in succession fail consecutively, the photographing unit 220 determines to skip capturing the face photograph. (10) The photographing unit 220 determines to skip face photographing if the face authentication button 626 is not pressed for a certain period of time after the scheduled person photographing start screen 62 is displayed. Then, the display unit 210 displays a skip notification on the scheduled person photographing start screen 62 to the effect that face photographing will be skipped because the face authentication button 626 is not pressed for a certain period of time. Alternatively, the photographing unit 220 does not operate face authentication processing when it recognizes something other than a human or the person does not fit within the frame. Then, the photographing unit 220 determines to skip face photographing when a certain period of time has passed during which the face authentication button 626 cannot be pressed because the face authentication processing is not operating. (11) The photographing unit 220 determines to skip photographing the face when the skip button 625 is pressed. If the medication assistant determines that photographing the face is difficult, the medication assistant presses the skip button 625 to skip photographing the face. For example, when displaying the scheduled patient photographing start screen 62, if a special note is set in the special notes 315 regarding not being able to photograph the scheduled patient 52, the display unit 210 may display the contents of the special note on the scheduled patient photographing start screen 62. The medication assistant checks the displayed special note, and if it is determined that it is not possible to photograph the face image of the scheduled patient 52, it presses the skip button 625. Alternatively, even if no special note is displayed, if it is determined that it is not possible to photograph the face image of the scheduled patient 52 based on the state of the scheduled patient 52, the assistant presses the skip button 625.

[0108] In step S250, photographing section 220 determines whether or not face photographing has been skipped in the face image photographing process (step S140a). If it is determined that face photographing has been skipped (YES in step S250), the process proceeds to step S260. At this time, the photographing section 220 may display a skip notification on the scheduled person photographing start screen 62 to the effect that face photographing has been skipped. If it is determined that face photography has not been skipped (NO in step S250), the process proceeds to step S150.

[0109] The processes from step S150 to step S170 are the same as those in embodiment 1. That is, authentication unit 240 performs face authentication using the name corresponding to the face image obtained by photographing the face in step S140a and character information 33 acquired in step S130.

[0110] If it is determined in step S240 that face photography is not possible or that face photography is to be skipped in step S250, visual confirmation result display processing and registration processing are performed in step S260. If it is determined that face photography is not possible or that face photography is to be skipped, the display unit 210 displays the visual confirmation result, and the authentication unit 240 registers the visual confirmation result in the medication history database 13.

[0111] <Visual inspection result display process and visual inspection result registration process: S260> In step S260, the display unit 210 displays a visual authentication success display indicating that the authentication was successful by visual confirmation. Also, the authentication unit 240 registers in the medication history database 13 the content of "OK2" indicating that face photography was not possible or face photography was skipped but authentication was successful by visual confirmation.

[0112] In this embodiment, the types set in the authentication result include OK2 in addition to OK, NG1, and NG2 described in the first embodiment. OK2 indicates that face capture was not possible or face capture was skipped, but identity authentication was successful through visual confirmation.

[0113] Fig. 24 is a diagram showing an example of the configuration of medication history database 13 according to this embodiment. Note that in Fig. 24, the description of medicine package read characters is omitted. In the medication history database 13, the reason why face photography was not possible or face photography was skipped is set in the record of OK2. In Figure 24, the authentication result for the printed name "Taro Ogawa" is "OK2." The special notes state, "Although the user does not permit face capture, identity authentication was successful through visual confirmation." This indicates that although "Taro Ogawa" is a "user who does not permit face capture" with the face capture flag set to "0," identity authentication through visual confirmation was successful.

[0114] FIG. 25 is a diagram showing an example of visual authentication success display 24 according to this embodiment. The display unit 210 displays visual authentication success display 24, which indicates that authentication was successful through visual confirmation. This is the screen display in the case of "OK2", which indicates that facial image capture was not possible or facial image capture was skipped, but authentication was successful through visual confirmation. When this visual authentication success display 24 is displayed on the mobile terminal 200, the medication supporter assumes that personal authentication has been completed and starts medication support. Although the visual authentication success display 24 in FIG. 25 shows the OK2 state, the medication assistance memo shown in FIG. 24 may be configured to accept and store special notes input from the staff after the display in FIG. 25 is displayed.

[0115] ***Explanation of the Effects of the Present Embodiment*** The medication support system according to the present embodiment can automatically determine whether or not facial photography is possible, based on a double check of visual confirmation by a medication assistant and face authentication using a face image obtained by photographing the person who is to take a medication. Therefore, the medication support system according to the present embodiment can reduce the workload of the medication assistant in authenticating the identity of the person who is to take a medication.

[0116] Embodiment 3 In this embodiment, differences from and additions to the first embodiment will be mainly described. In this embodiment, components having the same functions as those in the first embodiment are given the same reference numerals, and the description thereof will be omitted. In the medication support system 500 according to this embodiment, a mode will be described in which the name of the intended user is confirmed in the form of text information before performing the identity verification by face authentication described in embodiment 1. By having the medication assistant select the intended user in the form of text information rather than a face image, the possibility of selecting a more likely intended user is increased.

[0117] ***Configuration Description*** FIG. 26 is a diagram showing an example of the configuration of a mobile terminal 200 according to the present embodiment. The configuration examples of medication support system 500 and medication support device 100 according to this embodiment are similar to those described in the first embodiment. The mobile terminal 200 according to this embodiment includes a name confirmation presentation unit 250 in addition to the components described in the first embodiment. In this embodiment, all or some of the display unit 210, the image capturing unit 220, the corresponding name acquiring unit 230, and the authentication unit 240 described in the first embodiment may be referred to as a face authentication performing unit 290.

[0118] ***Explanation of Operation*** The operation of the medication support system 500 according to this embodiment will be described. The operation procedure of the medication support system 500 corresponds to a medication support method. Moreover, a program for realizing the operation of the medication support system 500 corresponds to a medication support program.

[0119] FIG. 27 is a flow diagram showing the operation of medication support system 500 according to this embodiment. In the operation of medication support system 500 shown in FIG. 27, steps S300 and S310 are added between steps S130 and S140 described in FIG. 4 of the first embodiment. Steps S110 to S130 are the same as those in the first embodiment.

[0120] Step S300 is a name confirmation presentation process by the name confirmation presentation unit 250. Step S310 is a process for determining whether or not a name confirmation notification 59 has been acquired from the name confirmation presentation process.

[0121] <Name confirmation presentation process: Step S300> The outline of the name confirmation presentation process is as follows. In the name confirmation presentation process, the name confirmation presentation unit 250 acquires the name read from an image of the medicine packet of the intended user 52 as the read name 55. The name confirmation presentation unit 250 displays the read name 55 on the display screen. Furthermore, based on the read name 55 and the face information database 31, the name confirmation presentation unit 250 extracts names similar to the read name 55 from the names set in the face information database 31 as a list of candidates for the name of the intended user 52. Then, the name confirmation presentation unit 250 displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name 55 is the name of the intended user 52 or not.

[0122] FIG. 28 is a flow diagram showing the name confirmation presentation process according to the present embodiment. In step S301, name confirmation presentation unit 250 acquires a name from character information 33 obtained in step S130 as read name 55, and determines whether acquisition of read name 55 has been successful. The method for acquiring the read name 55 from the character information 33 uses the method for identifying the printed name 54 from the character information 33 described in the first embodiment. However, other techniques may be used as long as they can extract the name from the character information 33.

[0123] If the acquisition of read name 55 is successful, proceed to step S302. Note that "acquisition of read name 55 is successful" means that some character string was read as read name 55. Even if an incorrect name is read from the image of the medicine package, it is successful as long as some character string is read. If the acquisition of the read name 55 fails, the process proceeds to step S306. Note that "the acquisition of the read name 55 fails" means that the name is not printed on the medicine package, or the character string cannot be read due to factors such as a network failure. In this case, the read name 55 does not exist.

[0124] In step S302, the name confirmation presentation unit 250 displays the read name 55 on the display screen of the mobile terminal 200. The name confirmation presentation unit 250 may display, together with the read name 55, the date and the time of taking the medicine, such as “after breakfast,” contained in the character information 33.

[0125] FIG. 29 is a diagram showing an example of a display screen 942 in the name confirmation presentation process according to the present embodiment. In FIG. 29, the read name "Yamada Jiro" is displayed on a display screen 942 in the name confirmation and presentation process, along with the date "June 29th" and the time of taking the medicine "After breakfast."

[0126] In step S303, the name confirmation presentation unit 250 determines whether or not a name matching the read name 55 is set in the face information database 31. Specifically, the name confirmation presentation unit 250 compares the user name 311 in the face information database 31 with the read name 55, and determines whether or not a user name 311 matching the read name 55 is set.

[0127] If it is determined that a name that matches the read name 55 has been set, the process proceeds to step S304. If it is determined that a name that matches the read name 55 has not been set, the process proceeds to step S305.

[0128] In step S304, the name confirmation presentation unit 250 displays the name confirmation button 56 on the display screen 942. As shown in FIG. 29, for example, a name confirmation button 56 is displayed next to a read name 55. The name confirmation button 56 is a button that is pressed when the medication assistant confirms that the read name 55 is the name of the intended recipient 52. Note that, although the name confirmation button 56 is displayed in Fig. 29, confirmation of the read name 55 may be notified by other methods, such as checking the read name 55.

[0129] In step S305, the name confirmation presentation unit 250 extracts similar names to the read name 55 from the names set in the face information database 31 based on the read name 55 and the face information database 31. Then, the name confirmation presentation unit 250 displays a list of similar names as a candidate list 57 on the display screen 942.

[0130] Specifically, the name confirmation presentation unit 250 performs a name matching process between the read name 55 and each of the user names 311 set in the face information database 31 , and extracts similar names from the user names 311 . The name confirmation presentation unit 250 partially calculates the similarity between the name set in the face information database 31 and the read name, and adds up the calculated similarities to calculate the points of the name set in the face information database 31. Then, the name confirmation presentation unit 250 displays the names set in the face information database 31 as names in the candidate list 57 in descending order of points. For example, the name confirmation presentation unit 250 performs the name matching process using an algorithm called LCS (Longest Common Subsequence) that calculates the similarity of characters. The name confirmation presentation unit 250 assigns points to each of the user names 311 using the LCS based on the read name 55. Specifically, the similarity between the read name 55 and the user name 311 is calculated for each partial character string, and the sum of the calculated similarities is set as the point of the user name 311. In the LCS, a higher point means a higher similarity. Therefore, the name confirmation presentation unit 250 displays each of the user names 311 in descending order of points as the candidate list 57. Alternatively, a threshold value for points may be set, and only user names 311 with points equal to or greater than the threshold may be displayed in descending order of points as the candidate list 57. It should be noted that the technology used for the name matching process may be technology other than LCS.

[0131] Name confirmation presentation unit 250 displays selection buttons 571 next to each name in candidate list 57 to allow the user to select that name. 29, a candidate list 57 is displayed at the bottom of a display screen 942. A selection button 571 is displayed next to each name in the candidate list 57. 29, a selection button 571 is displayed, but the name may be selected by tapping the name. Any other method may be used as long as it allows the name to be selected.

[0132] Step S306 is a process when the read name 55 cannot be acquired in step S301. If the read name 55 cannot be acquired, in step S306, the name confirmation presentation unit 250 displays a list 58 of names set in the face information database 31 on the display screen 942. The name confirmation presentation unit 250 displays the list 58 of names so that a corresponding name can be selected. Here, similar to the candidate list 57, a selection button 581 is displayed next to each name. The name confirmation presentation unit 250 has a function of accepting the selection of the read name 55 from the medication assistant as the person scheduled to take the medication, and a function of accepting the selection of any of the names displayed in the candidate list 57 as the person scheduled to take the medication.

[0133] In step S307, the name confirmation presentation unit 250 determines whether the name confirmation button 56 or the selection buttons 571, 581 displayed on the display screen 942 has been pressed. If either of the selection buttons 571, 581 is pressed, the process proceeds to step S308. If the name confirmation button 56 is pressed, the process proceeds to step S309.

[0134] In step S308, the name confirmation presentation unit 250 displays the name selected by either the selection button 571 or 581 on the display screen 942. Specifically, the following applies:

[0135] Pressing the select button 571 means that the medication assistant has determined that the read name 55 displayed on the display screen 942 is not the name of the intended recipient 52. In this case, the medication assistant selects the correct name of the intended recipient 52, which is different from the read name 55, from the candidate list 57. When a name different from the read name 55 is selected from the candidate list 57, the name confirmation presentation unit 250 displays the selected name on the display screen 942 in place of the read name 55.

[0136] Pressing the select button 581 means that the read name 55 does not exist and the read name 55 is not displayed on the display screen 942. In this case, the medication assistant selects the correct name of the intended recipient 52 from the list of names 58. The name confirmation presentation unit 250 displays the name selected from the list of names 58 on the display screen 942.

[0137] In step S309, the name confirmation presentation unit 250 outputs a name confirmation notification 59 indicating that the name displayed on the display screen 942 is a confirmed name 551 that has been confirmed to be correct as the name of the intended recipient 52.

[0138] Returning to FIG. 27, the explanation will be continued. In step S310, the face authentication execution unit 290 determines whether the name confirmation notification 59 has been acquired. When receiving the name confirmation notice 59, the face authentication execution unit 290 executes the process of step S140 and subsequent steps. The process of step S140 and subsequent steps is a process of performing face authentication using a facial image obtained by photographing the face of the intended recipient 52, as described in the first embodiment.

[0139] The processes from step S140 to step S170 are basically the same as those in the first embodiment. However, in this embodiment, the confirmed name 551 that has been confirmed to be correct as the name of the intended recipient 52 is acquired. Therefore, the printed name 54 acquired in step S161 of FIG. That is, in this embodiment, in step S161 of FIG. 12, authentication unit 240 acquires confirmation name 551 as printed name 54.

[0140] In addition, in this embodiment, the confirmed name 551, i.e., the printed name 54, is confirmed to be the correct name of the intended user 52. Therefore, in the authentication failure display in step S164 of FIG. 12, the case of erroneous recognition of the printed name 54 does not occur. Therefore, even if the printed name 54 and the image-corresponding name 53 are compared and the printed name 54 and the image-corresponding name 53 do not match (FIG. 13(c)), the face image obtained from the printed name 54 is displayed on the display screen 942 to allow the medication assistant to make a final confirmation. Also, even if the face authentication fails and the image-corresponding name 53 cannot be obtained (FIG. 13(b)), the face image obtained from the printed name 54 may be displayed on the display screen 942 to allow the medication assistant to make a final confirmation.

[0141] FIG. 30 is a schematic diagram showing (1) Specific Example 1 and (2) Specific Example 2 of the name confirmation presentation process according to the present embodiment. FIG. 31 is a schematic diagram showing (3) Specific Example 3 and (4) Specific Example 4 of the name confirmation presentation process according to the present embodiment. FIG. 32 is a diagram showing examples of an authentication success display 21 and an authentication failure display 22 according to the present embodiment. Specific examples 1 to 4 will be described with reference to FIG. 30 to FIG. In the specific examples of FIG. 30 to FIG. 32, it is assumed that “Yamada Jiro” is the correct name of the intended recipient 52.

[0142] <Specific example 1 of name confirmation presentation processing: (1) in FIG. 30> The read name "Yamada Jiro" is acquired from the image of the medicine package, and the read name "Yamada Jiro" is displayed (steps S301 and S302). Since "Yamada Jiro" is set in the face information database 31, the name confirmation button 56 is displayed (steps S303 and S304). Also, the candidate list 57 is displayed together with selection buttons 571 for selecting each name (step S305). The medication assistant confirms from the medicine packet that the name "Yamada Jiro" is correct as the name of the intended recipient 52 and then presses the name confirmation button 56 . When the name confirmation button 56 is pressed, the name confirmation presentation unit 250 outputs a name confirmation notification 59 notifying that the displayed name "Yamada Jiro" is the confirmed name 551 (steps S307 and S309).

[0143] <Specific example 2 of name confirmation presentation processing: (2) in FIG. 30> The read name "Yamada Ichiro" is acquired from the image of the medicine package, and the read name "Yamada Ichiro" is displayed (steps S301 and S302). Since "Yamada Ichiro" is set in the face information database 31, the name confirmation button 56 is displayed (steps S303 and S304). Also, the candidate list 57 is displayed together with selection buttons 571 for selecting each name (step S305). The medication assistant confirms from the medicine packet that the name "Yamada Ichiro" is not correct as the name of the intended recipient 52, and confirms that "Yamada Jiro" displayed in the candidate list 57 is the name of the intended recipient 52. The medication assistant then presses selection button 571 to select "Yamada Jiro" from the candidate list 57. When the select button 571 is pressed, the name confirmation presentation unit 250 displays the selected name "Yamada Jiro" on the display screen 942 (steps S307 and S308). Then, the name confirmation presentation unit 250 outputs a name confirmation notification 59 notifying that the displayed name "Yamada Jiro" is the confirmed name 551 (step S309).

[0144] <Specific example 3 of name confirmation presentation processing: (3) in FIG. 31> The read name "Yamada *·ro" is acquired from the image of the medicine package, and the read name "Yamada *·ro" is displayed (steps S301 and S302). Since "Yamada *ro" is not set in the face information database 31, the name confirmation button 56 is not displayed (step S303). The candidate list 57 is displayed together with selection buttons 571 for selecting each name (step S305). The medication assistant checks from the medicine packet that the name "Yamada*·ro" is not correct as the name of the intended recipient 52, and checks that "Yamada Jiro" displayed in the candidate list 57 is the name of the intended recipient 52. The medication assistant then presses selection button 571 to select "Yamada Jiro" from the candidate list 57. When the select button 571 is pressed, the name confirmation presentation unit 250 displays the selected name "Yamada Jiro" on the display screen 942 in place of the currently displayed "Yamada *·ro" (steps S307 and S308). Then, the name confirmation presentation unit 250 outputs a name confirmation notification 59 notifying that the displayed name is the confirmation name 551 (step S309).

[0145] <Specific example 4 of name confirmation presentation processing: (4) in FIG. 31> Since the read name cannot be obtained from the image of the medicine package, the read name 55 is not displayed (step S301). A list of names 58 set in the face information database 31 is displayed (step S306). As shown in (4) of Fig. 31, the medication assistant may select "List" to display the list of names 58. The medication assistant refers to the medicine packet and presses the selection button 581 to select “Yamada Jiro” from the list of names 58 . When the select button 581 is pressed, the name confirmation presentation unit 250 displays the selected name "Yamada Jiro" on the display screen 942 (steps S307 and S308). Then, the name confirmation presentation unit 250 outputs a name confirmation notification 59 notifying that the displayed name is the confirmation name 551 (step S309).

[0146] When the face authentication execution unit 290 (the display unit 210, the image capture unit 220, the corresponding name acquisition unit 230, and the authentication unit 240) receives the name confirmation notification 59, it executes the processes from step S140 to step S170. As described above, in this embodiment, since the confirmation name 551 is confirmed, the face authentication execution unit 290 acquires the confirmation name 551 as the printed name 54 (step S161).

[0147] FIG. 32(a) is similar to FIG. 13(a). FIG. 32(b) shows a case where face authentication has failed and image-corresponding name 53 cannot be obtained. In this embodiment, printed name 54 is confirmed as the correct name. Therefore, face authentication execution unit 290 refers to face information database 31 using printed name 54, obtains a face image corresponding to printed name 54, and displays it on display screen 942. Then, the medication assistant performs a final check using the face image displayed on display screen 942. If the medication assistant determines that the intended user 52 and the face image have been confirmed, the medication assistant may regard authentication as successful and enter and register a comment as necessary. In addition, the medication assistant may retake the photograph of the face image.

[0148] FIG. 32(c) shows a case where the printed name 54 and the image-corresponding name 53 are compared and the printed name 54 and the image-corresponding name 53 do not match. In this embodiment, the printed name 54 is confirmed as the correct name, so the medication assistant retakes a photograph of the face image of the person who is to take the medication and is identified by the printed name 54. The face authentication execution unit 290 may refer to the face information database 31 using the printed name 54, acquire a face image corresponding to the printed name 54, and display it on the display screen 942. Also, as shown in FIG. 32(c), a face image obtained from the image-corresponding name 53 may be displayed on the display screen for comparison.

[0149] ***Explanation of the Effects of the Present Embodiment*** In the medication support system according to the present embodiment, the correct name of the person who is to take the medicine can be reliably confirmed in the form of character information. Therefore, according to the medication support system according to the present embodiment, the correct name of the person who is to take the medicine can be confirmed in the form of character information, and the physical and mental workload of the medication assistant can be reduced. In this embodiment, the correct name of the intended user is selected by the medication assistant. However, it is difficult to completely eliminate erroneous selection of the name of the intended user due to misidentification by the medication assistant. However, in this embodiment, by having the medication assistant select the intended user in the form of text information rather than a face image, it is more likely that the intended user can be selected with a higher degree of certainty.

[0150] Embodiment 4 In this embodiment, differences from the second and third embodiments and additional features to the second and third embodiments will be mainly described. In this embodiment, components having the same functions as those in the second and third embodiments are given the same reference numerals, and the description thereof will be omitted. In the medication support system 500 according to this embodiment, a manner in which the name of the person to take the medication is confirmed in the form of text information before carrying out identity verification using face recognition as described in embodiment 2 (however, face photography is not permitted and face photography can be skipped) is described.

[0151] ***Configuration Description*** Examples of the configurations of medication support system 500, medication support device 100, and mobile terminal 200 according to this embodiment are similar to those described in the third embodiment.

[0152] ***Explanation of Operation*** The operation of the medication support system 500 according to this embodiment will be described. The operation procedure of the medication support system 500 corresponds to a medication support method. Moreover, a program for realizing the operation of the medication support system 500 corresponds to a medication support program.

[0153] FIG. 33 is a flow diagram showing the operation of medication support system 500 according to this embodiment. In the operation of medication support system 500 shown in FIG. 33, steps S300 and S310 are added between steps S130 and S210 described in FIG. 17 of the second embodiment.

[0154] The processes from step S110 to step S130, and steps S300 and S310 are the same as those in the third embodiment. Moreover, the processes from step S210 to step S170 are basically the same as those in the first embodiment. However, in this embodiment, the confirmed name 551 that has been confirmed to be correct as the name of the intended recipient 52 is acquired. Therefore, the terminal display image 64 displayed in step S210 is a face image acquired from the face information database 31 using the confirmed name 551. Therefore, according to this embodiment, the terminal display image 64 that is visually viewed by the medication assistant can be reliably a facial image of the intended recipient 52.

[0155] Also in this embodiment, similarly to the third embodiment, in step S161 of FIG. Furthermore, in this embodiment, as in the third embodiment, there is no case where the printed name 54 is erroneously recognized in the authentication failure display in step S164 of Fig. 12. Therefore, if the printed name 54 and the image corresponding name 53 are not identical as a result of comparing the printed name 54 and the image corresponding name 53, the face image obtained from the printed name 54 can be displayed on the display screen 942 to allow the medication assistant to make a final confirmation.

[0156] FIG. 34 is a schematic diagram showing a specific example of the medication support process according to the present embodiment. 34 (11) shows a state in which the face authentication execution unit 290 receives the name confirmation notification 59 and displays the terminal display image 64 on the mobile terminal 200 (steps S310 and S210). The terminal display image 64 used by the medication assistant to visually confirm the medication is obtained from the confirmed name 551, and therefore is reliably the correct facial image of the intended recipient 52. If the visual confirmation is OK and it is determined that face capture is not possible, a screen is displayed indicating that face capture is not possible but authentication has been successful through visual confirmation (step S260). At this time, a face image acquired from the confirmed name 551 may be displayed in the visual authentication success display 24 in FIG. In addition, the medication assistant may regard the identity verification as successful by visually confirming that the patient is OK on the screen of (11) in Fig. 34, and may enter and register a comment as necessary. In addition, if the medication assistant needs to stop the task for some reason, such as discontinuing medication, he or she may return to photographing the medicine package by pressing the redo button.

[0157] Furthermore, if the facial image capturing process (step S140a) results in skipping the facial capture (YES in step S240), the facial image acquired from the confirmed name 551 may be displayed on the display screen 942 as shown in (12) of FIG. 33. This allows the medication assistant to check again with the correct facial image and press the skip button with peace of mind. If the skip button is pressed, a screen display will appear indicating that facial capture has been skipped but authentication has been successful through visual confirmation (step S260). At this time, the facial image acquired from the confirmed name 551 may be displayed in the visual authentication success display 24 of FIG. 25.

[0158] Furthermore, if face photography is not skipped, the processes from step S150 to step S170 are carried out in the same manner as in the second and third embodiments. Examples of the display of authentication success and authentication failure in this embodiment are similar to those in FIG. 32 described in the third embodiment.

[0159] (13) in Fig. 34 is an example of a comment displayed by the comment input button. The screen in (13) in Fig. 34 is a screen used when a medication assistant inputs a comment. It is also used in the screen that displays the authentication result described in the third embodiment.

[0160] ***Explanation of the Effects of the Present Embodiment*** In some cases, a facial image obtained from the name of the person who is going to take the medicine is displayed, and the person visually confirms the image using the displayed facial image. It is known that people are surprisingly easily misled by image information, and may mistakenly recognize an incorrect facial image as correct. Therefore, it is important to display the correct facial image when the person who is going to take the medicine visually confirms the image. The medication support system according to the present embodiment has a function of reliably confirming the name of the person who is scheduled to take the medication in the form of text information. Therefore, according to the medication support system according to the present embodiment, the face image used for visual inspection can be a highly reliable face image. Furthermore, by having the function of making the face image used for visual inspection a highly reliable face image, the medication assistant can visually confirm with peace of mind, and the physical and mental work burden on the medication assistant can be reduced.

[0161] In the above first to fourth embodiments, each unit of each device of the medication support system 500 has been described as an independent functional block. However, the configuration of each device of the medication support system 500 does not have to be the same as that of the above-mentioned embodiments. For example, the character extraction process performed by the medication support device 100 may be performed by the mobile terminal 200. The functional blocks of each device of the medication support system 500 may have any configuration as long as they can realize the functions described in the above-mentioned embodiments. In addition, it is possible to combine two or more parts of the first to fourth embodiments. Alternatively, it is possible to implement only one part of these embodiments. In addition, it is possible to implement any combination of these embodiments, either as a whole or in part. That is, in the first to fourth embodiments, the embodiments can be freely combined, any of the components in each embodiment can be modified, or any of the components in each embodiment can be omitted.

[0162] The above-described embodiment is essentially a preferred example, and is not intended to limit the scope of the present disclosure, the scope of application of the present disclosure, and the scope of use of the present disclosure. The above-described embodiment can be modified in various ways as necessary. For example, the procedure described using a flow chart or sequence chart may be modified as appropriate.

[0163] Various aspects of the present disclosure are summarized below as appendices.

[0164] (Appendix 1) In a medication support system that supports a medication assistant who assists with medication, A medication support system comprising: a name confirmation presentation unit that obtains a name read from an image of a medicine packet of a person scheduled to take the medicine as a read name, displays the read name on a display screen, and extracts similar names to the read name from names set in the face information database based on the read name and a face information database in which face data representing a person's facial image and the person's name are set, as a list of candidates for the name of the person scheduled to take the medicine, and displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name is the name of the person scheduled to take the medicine. (Appendix 2) The name confirmation presentation unit, A medication support system as described in Appendix 1, which partially calculates the similarity between the name set in the face information database and the read name, adds up the calculated similarities to calculate a point for the name set in the face information database, and displays the names set in the face information database in descending order of the points as names in the candidate list. (Appendix 3) The name confirmation presentation unit, The medication support system of claim 1 or 2 determines whether a name matching the read name is set in the face information database, and if it determines that a name matching the read name is set, displays a name confirmation button on the display screen to be pressed when the medication assistant confirms that the read name is the name of the person scheduled to take the medication. (Appendix 4) The name confirmation presentation unit, A medication support system as described in Appendix 3, which, when the name confirmation button is pressed, outputs a name confirmation notification indicating that the name displayed on the display screen is a confirmed name that has been confirmed to be correct as the name of the person intended to take the medication. (Appendix 5) The name confirmation presentation unit, A medication support system as described in any one of Appendix 1 to Appendix 3, wherein when a name is selected from the list of candidates, the selected name is displayed on the display screen in place of the read name, and a name confirmation notification is output indicating that the name displayed on the display screen is a confirmed name that has been confirmed to be correct as the name of the person intended to take the medication. (Appendix 6) The medication support system includes: A medication support system as described in Appendix 4 or Appendix 5, comprising a face authentication execution unit that performs face authentication using a facial image of the person scheduled to take the medication upon receiving the name confirmation notification. (Appendix 7) A medication support method used in a medication support system that supports a medication assistant who performs medication assistance, A medication support method in which a computer obtains a name read from an image of a medicine packet of a person to take the medicine as a read-out name, displays the read-out name on a display screen, and extracts similar names to the read-out name from names set in the face information database based on the read-out name and a face information database in which face data representing a person's facial image and the person's name are set, as a list of candidates for the name of the person to take the medicine, displays the list of candidates on the display screen, and allows the medication assistant to confirm whether the read-out name is the name of the person to take the medicine. (Appendix 8) In a medication support program used in a medication support system that supports a medication assistant who provides medication assistance, A medication support program that causes a computer equipped in the medication support system to execute a name confirmation and presentation process that obtains a name read from an image of a medicine packet of a person scheduled to take the medicine as a read name, displays the read name on a display screen, and extracts similar names to the read name from names set in the face information database as a list of candidates for the name of the person scheduled to take the medicine, based on the read name and a face information database in which face data representing a person's facial image and the person's name are set, and displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name is the name of the person scheduled to take the medicine. [Explanation of symbols]

[0165] 11 User database, 111,121,341 Facility ID, 112 User ID, 113,311 User name, 114 Furigana, 115,312 Face data, 116,313 Face photography flag, 117,314 Photography prohibited period, 118,315 Special notes regarding photography prohibited, 12 Staff database, 122,321,346 Staff ID, 123,322 Name, 124,323 Staff flag, 13 Medication history database, 31 Face information database, 32 Staff information database, 33 Character information, 34 Authentication information, 342 Face authentication date and time, 343 Authentication result, 344 Image-compatible name, 345 Printed name, 347 Medicine package read characters, 348 Medication assistance note, 35 Name identification result, 51 Medicine package, 52 Scheduled user, 53 Image-compatible name, 54 Printed name, 61 Medicine package image capture start screen, 62 Scheduled user image capture start screen, 625 Skip button, 626 Face recognition button, 63 Visual confirmation screen, 64 Terminal display image, 641 Visual OK button, 642 Visual NG button, 81 Face image capture not possible condition, 82 Skip condition, 100 Medication support device, 110 Character extraction unit, 120 Information configuration unit, 150, 260 Memory unit, 21 Authentication success display, 211 Authentication success message, 22 Authentication failure display, 221 Face recognition failure message, 222, 232 Medicine package image, 223, 233 Registration button, 224, 234 Retake button, 231 Mismatch message, 24 Visual authentication success display, 200 Portable terminal, 210 Display unit, 220 Image capture unit, 230 Corresponding name acquisition unit, 240 authentication unit, 300 network, 500 medication support system, 55 read name, 551 confirmed name, 56 name confirmation button, 57 candidate list, 571, 581 selection buttons, 58 list of names, 59 name confirmation notification, 250 name confirmation presentation unit, 910 processor, 921 memory, 922 auxiliary storage device, 930 input interface, 940 output interface, 941 display device, 942 display screen, 950 communication device, 960 imaging device.

Claims

1. In a medication support system that supports a medication assistant who assists with medication, A medication support system comprising: a name confirmation presentation unit that obtains a name read from an image of a medicine packet of a person scheduled to take the medicine as a read name, displays the read name on a display screen, and extracts similar names to the read name from names set in the face information database based on the read name and a face information database in which face data representing a person's facial image and the person's name are set, as a list of candidates for the name of the person scheduled to take the medicine, and displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name is the name of the person scheduled to take the medicine.

2. The name confirmation presentation unit, The medication support system of claim 1, further comprising: partially calculating the similarity between the name set in the face information database and the read name; adding up the calculated similarities to calculate a point for the name set in the face information database; and displaying the names set in the face information database in descending order of the points as names in the candidate list.

3. The name confirmation presentation unit, The medication support system of claim 1 or claim 2 determines whether a name matching the read name is set in the face information database, and if it is determined that a name matching the read name is set, displays a name confirmation button on the display screen to be pressed when the medication assistant confirms that the read name is the name of the person scheduled to take the medication.

4. The name confirmation presentation unit, The medication support system of claim 3, wherein when the name confirmation button is pressed, a name confirmation notification is output indicating that the name displayed on the display screen is a confirmed name that has been confirmed to be correct as the name of the person intended to take the medication.

5. The name confirmation presentation unit, The medication support system of claim 1 or claim 2, wherein when a name is selected from the list of candidates using a selection means for selecting a name from the list of candidates, the selected name is displayed on the display screen in place of the read name, and a name confirmation notification is output indicating that the name displayed on the display screen is a confirmed name that has been confirmed to be correct as the name of the person intended to take the medication.

6. The medication support system includes: The medication support system of claim 4, further comprising a face authentication execution unit that, upon receiving the name confirmation notification, performs face authentication of the person scheduled to take the medication using a facial image obtained by photographing the face of the person scheduled to take the medication and the facial information database.

7. A medication support method used in a medication support system that supports a medication assistant who performs medication assistance, A medication support method in which a computer obtains a name read from an image of a medicine packet of a person to take the medicine as a read-out name, displays the read-out name on a display screen, and extracts similar names to the read-out name from names set in the face information database based on the read-out name and a face information database in which face data representing a person's facial image and the person's name are set, as a list of candidates for the name of the person to take the medicine, displays the list of candidates on the display screen, and allows the medication assistant to confirm whether the read-out name is the name of the person to take the medicine.

8. In a medication support program used in a medication support system that supports a medication assistant who provides medication assistance, A medication support program that causes a computer equipped in the medication support system to execute a name confirmation and presentation process that obtains a name read from an image of a medicine packet of a person scheduled to take the medicine as a read name, displays the read name on a display screen, and extracts similar names to the read name from names set in the face information database as a list of candidates for the name of the person scheduled to take the medicine, based on the read name and a face information database in which face data representing a person's facial image and the person's name are set, and displays the list of candidates on the display screen to allow the medication assistant to confirm whether the read name is the name of the person scheduled to take the medicine.

Images