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

Abstract

To provide a system that is easy to be initially introduced and can reliably authenticate a medicine taker without relying on visual inspection.SOLUTION: A photographing unit 220 photographs an image of a medicine package and a face image of a person scheduled to take a medicine. A character extraction unit 110 extracts characters printed on the medicine package from the image of the medicine package. A corresponding name acquisition unit 230 uses a face information database 31 to acquire a name corresponding to face data representing the face image of the person scheduled to take a medicine, and a name corresponding to the acquired face data representing the face image from the face information database 31 as an image-corresponding name. An authentication unit 240 acquires a name printed on the medicine package as a printed name, and determines whether it is possible to authenticate that the printed name and the image-corresponding name are the same. A display unit 210 displays an authentication success display when it is possible to authenticate that the printed name and the image-corresponding name are the same.SELECTED DRAWING: Figure 3

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] Conventional technology uses two-dimensional codes such as QR codes (registered trademark) to identify the person who has taken the medicine inside the medicine package. However, whether or not a QR code (registered trademark) can be printed on a medicine package depends on the packaging machine installed in the dispensing pharmacy, and it is not always possible to print a QR code (registered trademark). In addition, the output format of the QR code (registered trademark) printed on the medicine package is not fixed and differs depending on the system that uses the QR code (registered trademark). Therefore, there are packaging machines that cannot handle the output format of each system, and there is an issue that it takes time and costs to introduce QR codes (registered trademark).

[0006] In addition, Patent Document 1 discloses that the facial image displayed on the mobile device is checked to see who to give the medication to, but the facial image and the identity of the resident are ultimately checked visually by the medication assistant. Therefore, there is a problem that it is not possible to prevent mistakes such as judging the same person to be a different person due to changes in hairstyle, or handing the medication to a different person who looks similar.

[0007] An object of the present disclosure is to provide a system that is easy to implement initially and can reliably authenticate recipients without relying on visual inspection. [Means for solving the problem]

[0008] The medication support system according to the present disclosure is a medication support system that supports medication assistance, a corresponding name acquisition unit that acquires face data representing a face image of a person who is to take the medicine contained in the medicine packet, using a face information database in which face data representing a person's face image and the name of the person are set, and further acquires a name corresponding to the acquired face data representing the face image from the face information database as an image corresponding name; an authentication unit that acquires the name printed on the medicine package as a printed name from among characters printed on the medicine package from an image of the medicine package, and determines whether the printed name and the image-corresponding name can be authenticated as being the same; When the printed name and the image-corresponding name can be authenticated as being the same, a display unit is provided which displays an authentication success message indicating that the intended recipient is the correct recipient. Effect of the Invention

[0009] In the medication support system according to the present disclosure, the characters printed on the medicine package are extracted from the image of the medicine package to obtain the printed name, so there is no need to use a two-dimensional code or the like. In addition, in the medication support system according to the present disclosure, the image-corresponding name corresponding to the facial image of the person who is to take the medicine is obtained using a face information database, and it is determined whether the printed name and the image-corresponding name can be authenticated as being the same. Therefore, the medication support system according to the present disclosure can provide a system that is easy to introduce initially and can authenticate the person who takes the medicine without relying on visual inspection. [Brief description of the drawings]

[0010] [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. [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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] 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.

[0012] 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 nursing home. 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.

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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.

[0021] 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 an abbreviation for High Definition Multimedia Interface. LCD is an abbreviation for Liquid Crystal Display.

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

[0023] 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.

[0024] 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.

[0025] ***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.

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

[0027] <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.

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] <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.

[0036] <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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

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

[0044] <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.

[0045] <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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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:

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

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

[0057] <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:

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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 representing authentication success.

[0064] 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 package 51 (step S130, FIG. 13(c)).

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.”

[0070] 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.

[0071] <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."

[0072] <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."

[0073] <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."

[0074] 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.

[0075] 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 .

[0076] ***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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] ***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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] In the above-mentioned first embodiment, 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 embodiment. 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 embodiment. In addition, a plurality of parts of the first embodiment may be combined and implemented. Alternatively, only one part of this embodiment may be implemented. In addition, this embodiment may be combined in any manner as a whole or in part and implemented. That is, in the first embodiment, the embodiments can be freely combined, or any of the components in each embodiment can be modified, or any of the components in each embodiment can be omitted.

[0086] 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.

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

[0088] (Appendix 1) In a medication support system that supports medication assistance, a corresponding name acquisition unit that acquires face data representing a face image of a person who is to take the medicine contained in the medicine packet, using a face information database in which face data representing a person's face image and the name of the person are set, and further acquires a name corresponding to the acquired face data representing the face image from the face information database as an image corresponding name; an authentication unit that acquires the name printed on the medicine package as a printed name from among characters printed on the medicine package from an image of the medicine package, and determines whether the printed name and the image-corresponding name can be authenticated as being the same; a display unit that displays a successful authentication message indicating that the intended recipient is a correct recipient when the printed name and the image-corresponding name are authenticated as being the same; A medication support system equipped with: (Appendix 2) In the face information database, data obtained by converting the face image into digital data is set as the face data, The corresponding name acquisition unit, A medication support system as described in Appendix 1, which digitizes a facial image of the person scheduled to take the medication, and obtains a name corresponding to the facial data digitized from the facial image of the person scheduled to take the medication as the image-corresponding name from the facial information database. (Appendix 3) The display unit is A medication support system as described in Appendix 1 or Appendix 2, which, if it is not possible to authenticate that the printed name and the image-corresponding name are the same, displays an authentication failure display indicating that authentication of the printed name and the image-corresponding name has failed. (Appendix 4) The display unit is The medication support system described in Appendix 3, which displays a facial authentication failure display when it is not possible to authenticate that the printed name and the image-corresponding name are the same because the image-corresponding name cannot be obtained, and which includes a facial authentication failure message indicating that the image-corresponding name could not be obtained, a registration button that allows a medication assistant to forcibly register the recipient who will be taking the medication, and a retake button that allows the medication assistant to retake a facial image of the recipient. (Appendix 5) The display unit is The medication support system described in Appendix 3, which, if the printed name and the image-corresponding name cannot be authenticated as being identical as a result of comparing the printed name with the image-corresponding name, displays an authentication failure display including a mismatch message indicating a mismatch between the printed name and the image-corresponding name, a registration button that allows a medication assistant to forcibly register the person taking the medication, and a retake button that allows the medication assistant to retake a facial image of the person to take the medication. (Appendix 6) The authentication unit A medication support system as described in any one of Appendix 1 to Appendix 5, which acquires the position where a name is printed on the medicine packet as the name position, and acquires the characters printed on the medicine packet that are printed at the name position as the printed name. (Appendix 7) A medication support method for use in a medication support system that supports medication assistance, the computer acquires face data representing a face image of a person who is to take the medicine contained in the medicine packet, using a face information database in which face data representing a person's face image and the name of the person are set, and further acquires a name corresponding to the acquired face data representing the face image from the face information database as an image-corresponding name; The computer obtains the name printed on the medicine package from the image of the medicine package, and determines whether the printed name and the image-corresponding name can be authenticated as being the same. When the computer is able to authenticate that the printed name and the image-corresponding name are identical, it displays a message indicating that the intended user is a correct user. (Appendix 8) In a medication support program used in a medication support system that supports medication assistance, a corresponding name acquisition process for acquiring face data representing a face image of a person who is to take the medicine contained in the medicine packet, using a face information database in which face data representing a person's face image and the name of the person are set, and further acquiring a name corresponding to the acquired face data representing the face image from the face information database as an image corresponding name; an authentication process for acquiring the name printed on the medicine package as a printed name from among the characters printed on the medicine package from an image of the medicine package, and determining whether the printed name and the image-corresponding name can be authenticated as being the same; a display process for displaying an authentication success message indicating that the intended user is a correct user when the printed name and the image corresponding name are authenticated as being the same; A medication support program that executes the above on a computer. [Explanation of symbols]

[0089] 11 User database, 111,121,341 Facility ID, 112 User ID, 113,311 User name, 114 Furigana, 115,312 Face data, 12 Staff database, 122,321,346 Staff ID, 123,322 Name, 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 Person scheduled to take the medicine, 53 Image-compatible name, 54 Printed name, 61 Medicine package capture start screen, 62 Scheduled person capture start screen, 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 authentication failure message, 222, 232 Medicine package image, 223, 233 Registration button, 224, 234 Retake button, 231 Mismatch message, 200 Mobile terminal, 210 Display unit, 220 Photography unit, 230 Corresponding name acquisition unit, 240 Authentication unit, 300 Network, 500 Medication support system, 910 Processor, 921 Memory, 922 Auxiliary storage device, 930 An input interface, 940 an output interface, 941 a display device, 950 a communication device, and 960 an imaging device.

Claims

1. In a medication support system that supports medication assistance, an authentication unit that acquires an image-corresponding name obtained from a face information database in which face data representing a person's face image and the name of the person are set, the image-corresponding name being a name corresponding to face data representing a face image of a person who is to take the medicine contained in the medicine packet, and acquires a name from characters printed on the medicine packet as a printed name from an image of the medicine packet, and determines whether the printed name and the image-corresponding name can be authenticated as being the same; a display unit which displays an authentication success display indicating that the intended user is a correct user when it is possible to authenticate that the printed name and the image-corresponding name are the same, and which displays an authentication failure display indicating that authentication of the printed name and the image-corresponding name has failed when it is not possible to authenticate that the printed name and the image-corresponding name are the same; Equipped with The display unit is A medication support system in which, if the printed name and the image corresponding name cannot be authenticated as being the same because the image corresponding name cannot be obtained, the authentication failure display is displayed, which includes a facial authentication failure message indicating that the image corresponding name could not be obtained, and, if the printed name and the image corresponding name cannot be authenticated as being the same as a result of comparing the printed name and the image corresponding name, the authentication failure display is displayed, which includes a mismatch message indicating a mismatch between the printed name and the image corresponding name.

2. The display unit, The medication support system of claim 1, wherein if the image-corresponding name cannot be obtained and therefore the printed name and the image-corresponding name cannot be authenticated as being the same, the authentication failure display is displayed, the authentication failure display including the face authentication failure message, a registration button for a medication assistant to forcibly register the recipient who will take the medication, and a retake button for the medication assistant to retake a facial image of the recipient.

3. The display unit, The medication support system of claim 1, wherein if, as a result of comparing the printed name with the image-corresponding name, it is not possible to authenticate that the printed name and the image-corresponding name are identical, the authentication failure display is displayed, which includes the mismatch message, a registration button that allows a medication assistant to forcibly register the person taking the medication, and a retake button that allows the medication assistant to retake a facial image of the person to take the medication.

4. In the face information database, data obtained by converting the face image into digital data is set as the face data, The authentication unit The medication support system according to claim 1 , further comprising: a step of acquiring the image-corresponding name, which is a name corresponding to the facial data obtained by digitizing a facial image of the person scheduled to take the medication.

5. The authentication unit A medication support system as described in any one of claims 1 to 3, wherein the position where a name is printed on the medicine package is obtained as the name position, and the characters printed on the medicine package that are printed at the name position are obtained as the printed name.

6. A medication support method for use in a medication support system that supports medication assistance, The computer acquires an image-corresponding name, which is acquired from a face information database in which face data representing a person's face image and the name of the person are set, and which corresponds to face data representing a face image of a person who is to take the medicine contained in the medicine packet, and acquires a name from characters printed on the medicine packet as a printed name from an image of the medicine packet, and determines whether the printed name and the image-corresponding name can be authenticated as being the same; When the computer is able to authenticate that the printed name and the image-corresponding name are identical, it displays an authentication success display indicating that the intended recipient is a correct recipient, and when the computer is unable to authenticate that the printed name and the image-corresponding name are identical, it displays an authentication failure display indicating that authentication of the printed name and the image-corresponding name has failed, A medication support method in which, when a computer is unable to authenticate that the printed name and the image corresponding name are the same because the computer is unable to obtain the image corresponding name, the computer displays the authentication failure display including a face authentication failure message indicating that the image corresponding name could not be obtained, and, when a computer is unable to authenticate that the printed name and the image corresponding name are the same as a result of comparing the printed name and the image corresponding name, the computer displays the authentication failure display including a mismatch message indicating a mismatch between the printed name and the image corresponding name.

7. In a medication support program used in a medication support system that supports medication assistance, an authentication process in which an image-corresponding name is obtained from a face information database in which face data representing a person's face image and the name of the person are set, the image-corresponding name being a name corresponding to face data representing a face image of a person who is to take the medicine contained in the medicine packet, and a printed name is obtained from an image of the medicine packet, from among the characters printed on the medicine packet, and a determination is made as to whether the printed name and the image-corresponding name can be authenticated as being the same; a display process for displaying an authentication success display indicating that the intended user is a correct user when the printed name and the image-corresponding name can be authenticated as being the same, and displaying an authentication failure display indicating that authentication of the printed name and the image-corresponding name has failed when the printed name and the image-corresponding name cannot be authenticated as being the same; A medication support program for causing a computer to execute the following: The display process includes: A medication support program that displays the authentication failure display including a face authentication failure message indicating that the image corresponding name could not be obtained if the printed name and the image corresponding name cannot be authenticated as being the same because the image corresponding name cannot be obtained, and displays the authentication failure display including a mismatch message indicating a mismatch between the printed name and the image corresponding name if the printed name and the image corresponding name cannot be authenticated as being the same as a result of comparing the printed name and the image corresponding name.

Images